WO2013139123A1 - 处理3d拓扑视图中网元对象信息的方法及设备 - Google Patents

处理3d拓扑视图中网元对象信息的方法及设备 Download PDF

Info

Publication number
WO2013139123A1
WO2013139123A1 PCT/CN2012/083664 CN2012083664W WO2013139123A1 WO 2013139123 A1 WO2013139123 A1 WO 2013139123A1 CN 2012083664 W CN2012083664 W CN 2012083664W WO 2013139123 A1 WO2013139123 A1 WO 2013139123A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
element object
information
network
window
Prior art date
Application number
PCT/CN2012/083664
Other languages
English (en)
French (fr)
Inventor
谭严芳
梁建波
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP12826658.2A priority Critical patent/EP2663050B1/en
Priority to US13/850,627 priority patent/US8782526B2/en
Publication of WO2013139123A1 publication Critical patent/WO2013139123A1/zh
Priority to US14/273,750 priority patent/US9335889B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/22Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies

Definitions

  • the present invention relates to network management technologies, and in particular, to a method and device for processing network element object information in a 3D topology view. Background technique
  • the topology view is an effective tool for operators to perform operation and maintenance, which can help the operation and maintenance personnel to visualize the networking of network devices (ie, network element objects).
  • network devices ie, network element objects
  • the present invention provides a method and a device for processing network element object information in a 3D topology view, so as to solve the problem that the operation and maintenance personnel cannot quickly identify the network element object through the topology view in the prior art.
  • An embodiment of the present invention provides a method for processing network element object information in a 3D topology view, including:
  • the size information of the first network element object includes a length, a width, and a height of the first network element object;
  • the location coordinate and size information of the network element object is obtained by the network management background server from the stored network element object information according to the enlarged view operation command and the identifier of the first network element object;
  • the network element object Information includes each network element in the 3D topology view Object identification, location coordinates, and size information;
  • An embodiment of the present invention provides a network management front-end client, including:
  • a user event response module configured to send a first instruction to the network management background server in response to the operation of the first network element object in the 3D topology view displayed by the user selection window, where the first instruction includes the first network element object Identification and zoom in to view operational commands;
  • An information receiving module configured to receive location coordinate and size information of the first network element object sent by the network management background server; the size information of the first network element object includes a length and a width of the first network element object The position coordinate and the size information of the first network element object are obtained by the network management background server from the stored network element object information according to the enlarged viewing operation operation command and the identifier of the first network element object. The identifier, location coordinates, and size information of each network element object in the 3D topology view of the network element object information;
  • a top display module configured to adjust a position coordinate of the first network element object in the window according to a size of the window and a position coordinate of the first network element object, where the first network element object is The size information is multiplied by a preset magnification to enlarge the first network element object, and the enlarged first network element object is redisplayed at the adjusted position coordinates in the window.
  • Another aspect of the embodiments of the present invention provides a method for processing network element object information in a 3D topology view, including:
  • the first network element object includes a length, a width, and a height of the first network element object;
  • the network element object information includes an identifier, a location coordinate of each network element object in the 3D topology view. And size information;
  • a network management backend server including:
  • the instruction receiving module is configured to receive a first instruction sent by the network management front client, where the first instruction is that the network management front client responds to the operation of the first network element object in the 3D topology view displayed by the user selected window.
  • the first instruction includes an identifier of the first network element object and an enlarged view operation command.
  • An information acquiring module configured to acquire, according to the enlarged viewing operation command and the identifier of the first network element object, location coordinate and size information of the first network element object from the stored network element object information;
  • the size information of the first network element object includes a length, a width, and a height of the first network element object;
  • the network element object information includes an identifier, a location coordinate, and a size of each network element object in the 3D topology view.
  • An information delivery module configured to: transmit, to the network management front-end client, position coordinate and size information of the first network element object, so that the network management front-end client redisplays at the adjusted position coordinate in the window ⁇ ⁇ The first network element object.
  • a further aspect of the embodiments of the present invention provides a network management system, including: a network management front-end client and a network management back-end server, where:
  • the network management front-end client is configured to send a first instruction to the network management background server in response to the operation of the first network element object in the 3D topology view displayed by the user selection window, where the first instruction includes the first The identifier of the network element object and the enlarged view operation command;
  • the network management background server is configured to acquire, according to the enlarged view operation command and the identifier of the first network element object, location coordinate and size information of the first network element object from the stored network element object information, and
  • the network management front-end client transmits location coordinates and size information of the first network element object, where the network element object information includes identifiers, location coordinates, and size information of each network element object in the 3D topology view. ;
  • the network management front-end client is further configured to adjust a position coordinate of the first network element object in the window according to a size of the window and a position coordinate of the first network element object, where the first The size information of a network element object is multiplied by a preset magnification to enlarge the first network element object, and the enlarged first network element object is redisplayed at the adjusted position coordinates in the window.
  • the method for processing the network element object information in the 3D topology view and the front-end client of the network management system are provided to the network management system by responding to the operation of the network element object in the 3D topology view displayed in the user selected window.
  • the server sends an instruction to enable the network management background server to obtain the coordinate position and size information of the selected network element object according to the identifier of the selected network element and the enlarged view operation command in the instruction, and provide the information to the network management front-end client, the network management front-end client.
  • Position coordinate and size information and provide the network management front-end client, re-adjust the display position of the selected network element object in the window for the network management front-end client, and enlarge the selected network element object, thereby implementing the selected network element object
  • the display effect of moving the display position and zooming in the window allows the operation and maintenance personnel to provide conditions for quickly identifying the selected network element object from the window.
  • the network management background server cooperates with the network management front-end client, and the network management front-end client responds to the user selecting the operation of the network element object, and sends the first instruction to the network management background server, and the network management background server Obtaining, according to the first instruction, location coordinate and size information of the selected network element object, and providing the network management terminal client, the network management front client re-adjusting the selected network element object according to the coordinate position and size information of the selected network element object
  • the display position in the display, and the selected network element object is enlarged, thereby realizing the display effect of the selected network element object in the window moving display position and zooming in, so that the operation and maintenance personnel can quickly identify the selected network element from the window.
  • the object solves the problem that the operation and maintenance personnel cannot quickly identify the network element object when all the network element objects in the same subnet are displayed in the same plane in the prior art.
  • FIG. 1A is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 1 of the present invention
  • FIG. 1B is a schematic structural diagram of a network element object displayed in a window according to Embodiment 1 of the present invention.
  • FIG. 1C is a display state of a window according to Embodiment 1 of the present invention.
  • FIG. 1D is another display state of a window according to Embodiment 1 of the present invention.
  • FIG. 2 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 2 of the present invention
  • FIG. 3 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 3 of the present invention
  • FIG. 4 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 4 of the present invention
  • FIG. 5 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 5 of the present invention
  • FIG. 6 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 6 of the present invention
  • FIG. 7 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 7 of the present invention.
  • FIG. 8 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 8 of the present invention.
  • FIG. 9 is a schematic structural diagram of a network management foreground server provided by Embodiment 9 of the present invention
  • FIG. 10 is a schematic structural diagram of a network management background server according to Embodiment 10 of the present invention
  • FIG. 11 is a schematic structural diagram of a network management system according to Embodiment 11 of the present invention; schematic diagram.
  • FIG. 1 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 1 of the present invention. As shown in FIG. 1A, the method in this embodiment includes:
  • Step 101 Send a first instruction to the network management backend server in response to the operation of the first network element object in the 3D topology view displayed by the user selection window.
  • the first instruction includes an identifier of the first network element object and an enlarged view operation command.
  • the network element object in the embodiment of the present invention represents a network element displayed on the window, and may be, for example, an icon or the like.
  • the connection object in the embodiment of the present invention indicates the connection relationship between the network element and the network element displayed on the window, and may be, for example, a connection and a network element at both ends of the connection.
  • the execution entity of this embodiment is a network management front-end client in the network management system, which may be various devices having strong computing capabilities and supporting topology view display, such as a personal computer, a smart mobile terminal, a tablet computer, and the like.
  • each network element object such as each network element
  • a storage system such as a storage array or a database
  • the top view is a three-dimensional view. Therefore, in this embodiment, the position coordinates of each network element object can be represented by three-dimensional coordinates (X, y, z) of each vertex of the network element object, as shown in FIG. 1B. .
  • the cube in Figure 1B represents a network element object.
  • each network element has its size, which can be represented by length, width, and height (a, b, c).
  • the foregoing information of the network element object may be classified into two types, one is information of the network element object, and the other is information of the connection object.
  • the information of a network element object mainly includes: an identifier, a display state, a position coordinate (X, y, z), and a size information (a, b, c) of the network element object.
  • the display state of the network element object includes that the network element object is currently displayed in the window and is not displayed. There are two situations in the window.
  • the embodiments of the present invention refer to the information of all the network element objects in the entire 3D topology view as the network element object information, that is, the network element object information includes the identifier, display state, and location coordinates of each network element object in the 3D topology view. Size information, etc.
  • the connection relationship between two interconnected network element objects is called a connection object, and the two network element objects are respectively network element objects at both ends of the connection object.
  • the information of each connection object mainly includes the identifiers of the network element objects at both ends.
  • the information of each connection object may further include information such as a connection distance and a connection angle between the network element objects at both ends.
  • connection object information includes the identifiers of the network element objects at both ends of each connection in the 3D topology view, and the network element objects at both ends Information such as the connection distance and connection angle.
  • the network management front-end client in this embodiment also subnets all network element objects in the network according to the area, and displays all network element objects in the same subnet on the same plane.
  • the plane refers to a window.
  • the network management front-end client of the embodiment is mainly for the user, and is configured to respond to the user's operation on each network element object in the 3D topology view displayed in the window.
  • the front-end client of the network management system of the embodiment provides functions such as selecting a network element object, viewing a connection relationship of the network element object, and creating an SDH path for each network element object in the 3D topology view displayed on the window.
  • the front-end client of the network management system in this embodiment can respond to the operation of the user selecting the network element object, and identify which network element object is selected by the user. For example, the user clicks on the network element object by using the mouse, and the front-end client of the network management system identifies, from the click operation, information for selecting the network element object, and knows the identifier of the selected network element object.
  • the network management front-end client After the user of the network management front-end client responds to the operation of selecting the network element object by the user, an instruction is generated, and the identifier of the network element object selected by the user and the enlarged view operation command are carried in the instruction, and then the instruction is sent.
  • the network management background server is configured to enable the network management background server to obtain the information required for the user to select the network element object selected by the user from the pre-stored network element object information according to the enlarged viewing operation command and the identifier of the network element object selected by the user.
  • the information is returned to the front-end client of the network management system, so that the network element object selected by the user can be enlarged and processed.
  • the information required for zooming in on the selected NE object of the user mainly includes the location coordinates and size information of the network element object selected by the user.
  • the user selects the first network element object in the 3D topology view displayed in the window of the front-end client of the network management system, and sends the instruction to the network management background server as the first instruction as an example, but for any
  • the processing of the selected operation of a network element object is the same as the processing of the first network element object, and is no longer described.
  • the user can select the first network element object by using operations that can be identified by the front-end client, for example, clicking the mouse on the first network element object, or by right-clicking on the first network element object, and selecting the selected one. Options for network element objects, etc.
  • the front-end client of the network management system responds to the operation of the first network element object, and generates a first instruction, and then sends the first instruction to the network management background server.
  • the first instruction includes an identifier of the first network element object and an enlarged view operation command.
  • the network management background server After receiving the first instruction, the first instruction is parsed, and the identifier of the first network element object and the enlarged view operation command are obtained therefrom. Then, the network management background server obtains the location coordinate and size information of the first network element object from the pre-stored network element object information according to the enlarged view operation command and the identifier of the first network element object, and sets the position coordinate of the first network element object. And size information is passed to the network management front-end client.
  • the network element object information may further include a display state of each network element object in the 3D topology view.
  • the gateway background server may obtain, according to the display status of each network element object in the operation command and the network element object information, the location of each network element object currently displayed in the window of the front-end client of the network management system. Coordinate and size information.
  • the first network element object is displayed in the window, and therefore belongs to a member of each network element object currently displayed in the window, that is, each network element object currently displayed in the window includes the first network element object.
  • the network management background server may further obtain the location coordinates and the size information of the first network element object from the location coordinates and size information of each network element object currently displayed in the obtained window according to the identification information of the first network element object.
  • the gateway background server can transmit the location coordinates and size information of the other network element objects currently displayed in the window to the network management device while transmitting the location coordinates and size information of the first network element object to the network management foreground client. Front desk client.
  • the network management background server may also send the location coordinates and size information of each network element object currently displayed in the obtained window to the network management foreground client, instead of separately obtaining the location coordinates and size of the first network element object. information.
  • Step 102 Receive location coordinates and size information of the first network element object sent by the network management background server.
  • the size information of the first network element object includes the length, width, and height of the first network element object.
  • the location coordinate and size information of the first network element object is obtained by the network management background server from the stored network element object information according to the enlarged view operation command and the identifier of the first network element object, and then returned to the network management front-end client.
  • the network element object information includes an identifier, a location coordinate, and a size information of each network element object in the 3D topology view. It is also based on this that the network management background server can obtain the location coordinate and size information of the first network element object according to the identifier of the first network element object.
  • the location coordinate and size information of the first network element object returned by the network management background server is received.
  • the network management background server delivers the location coordinates and size information of each network element object currently displayed in the window acquired by the network management background server
  • the network management foreground client receives the network currently displayed in the window.
  • the position coordinates and size information of the meta object including the first network element object.
  • Step 103 Adjust the position coordinates of the first network element object in the window according to the size of the window and the position coordinate of the first network element object, and multiply the size information of the first network element object by a preset magnification to enlarge the first network.
  • the network management front client of the embodiment may recalculate the location of the first network element object according to the size of the window and the current display position of the first network element object in the window. Coordinates, this can adjust the display position of the first network element object in the window.
  • the network management front-end client of the embodiment may further multiply the size information of the first network element object by a preset magnification, thereby using the first network element object. amplification.
  • magnification is preset, for example, it can be set to be enlarged by 2 times, but is not limited thereto.
  • the operation of selecting the network element object when the user needs to view or identify a certain network element object, the operation of selecting the network element object only needs to be performed, and the network management front-end client responds to the operation of selecting the network element object by the user and passes the network management.
  • the background server issues an instruction, obtains location coordinate and size information of the network element object from the network management background server, and further completes adjustment of the display position of the network element object and enlargement of the network element object based on the obtained information and the size of the window. So that the network element object can be highlighted in the window, thereby enabling the user to quickly recognize from many network element objects in the window
  • the size of the front-end client window of the network management system and the location of the first network element object Coordinates the display position of the first network element object in the window, multiplies the size information of the first network element object by a preset magnification, to enlarge the first network element object, and redisplays the first network element object in the window.
  • This embodiment shows a display state of the current window by FIG. 1C, in which the shaded cube is the first network element object.
  • the positional relationship and distance between the network element object shown by other cubes or polyhedrons and the first network element object are as shown in FIG. 1C.
  • the network management front client recalculates the position coordinates of the first network element object as coordinates corresponding to the center position of the window, and multiplies the length, width, and height in the size information of the first network element object by the magnification.
  • the display position of the first network element object can be adjusted to be the center position of the window, which is more advantageous for the user to identify the first network element object.
  • the magnification is 2
  • the length, After the width and height are multiplied by 2
  • the first network element object is enlarged by 8 times, which is beneficial for the user to recognize the first network element object.
  • the network management front-end client calculates the distance between the other network element objects except the first network element object and the first network element object and the recalculated first-network element object according to the currently displayed network element objects in the window.
  • Position coordinates recalculate the position coordinates of other network element objects except the first network element object in each network element object currently displayed in the window.
  • the size information of other network element objects in the window remains unchanged. This ensures that the distance between other network element objects in the window and the first network element object is the same, and the realism of other network element objects can be maintained as much as possible.
  • the front-end client of the network management system displays the position coordinates of each network element object (including the first network element object) currently displayed in the recalculated window, the enlarged size information of the first network element object, and the currently displayed window in the received window.
  • the size information of the network element objects other than the first network element object in each network element object, and the network element objects currently displayed in the window are displayed in the window again.
  • the display state in the window shown in Fig. 1C becomes as shown in Fig. 1D.
  • the first network element object is enlarged and displayed in the middle of the window. The positional relationship between the other network element object and the first network element object is shown in FIG. 1D and will not be described in detail.
  • the network management front-end client highlights the first network element by adjusting the position coordinates of the first network element object and amplifying the first network element object, which not only solves all the networks in the same subnet in the prior art.
  • the meta object is displayed in the same plane, the user cannot quickly identify the problem of the network element object, and by ensuring that the distance between other network element objects and the first network element object and the size of other network element objects are unchanged, try to ensure that the re Show the authenticity of the topology.
  • FIG. 2 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 2 of the present invention. As shown in FIG. 2, the method in this embodiment includes:
  • Step 201 Send a second instruction to the network management backend server in response to the operation of the connection relationship of the second network element object in the 3D topology view displayed by the user viewing window.
  • the second instruction includes an identifier of the second network element object and a connection relationship view operation command.
  • the connection relationship of the second network element object includes a second network element object and all third network element objects, and the third network element object is a network element object connected to the second network element object. .
  • connection relationship of the network element object mainly includes the network element object and other network element objects connected to the network element object. More specifically, the connection relationship of the network element object mainly includes an identifier of the network element object, an identifier of another network element object connected to the network element object, and Connection information of the network element object connected to other network element objects.
  • the second network element object is taken as an example.
  • the second network element object connection relationship mainly includes the second network element object and all the network element objects connected to the second network element object.
  • the network element object connected to the second network element object is referred to as a third network element object.
  • the connection between each third network element object and the second network element object itself also belongs to a kind of information in the connection relationship.
  • the execution entity of this embodiment is also the front-end client of the network management system, and the front-end client of the network management system cooperates with the network management background server.
  • the network management front-end client in this embodiment also subnets all network element objects in the network according to the area, and displays all network element objects in the same subnet on the same plane.
  • the same plane is referred to as a window.
  • the network element object information and the connection object information are also pre-stored on the network management background server.
  • the network element object information and the connection object information refer to step 101, and details are not described herein again.
  • the front-end client of the network management system in this embodiment also provides functions such as selecting a network element object, viewing a connection relationship of the network element object, and creating an SDH path for each network element object displayed on the window.
  • functions such as selecting a network element object, viewing a connection relationship of the network element object, and creating an SDH path for each network element object displayed on the window.
  • the front-end client of the network management system in this embodiment responds to the user's operation of viewing the connection relationship of the network element object, and obtains the identifier of the network element object that the user wants to view the connection relationship, and then generates an instruction, and carries the user in the instruction.
  • To view the mappings and connection relationships of the NEs of the connection relationship view the operation commands, and then send them to the network management background server. This allows the network management background server to view the operation commands to obtain the information required to view the connection relationship based on the identification and connection relationship of the NE objects. And passed to the network management front-end client.
  • the information required to view the connection relationship mainly includes the network element objects connected to the network element object whose connection relationship is to be viewed, and the connection between them.
  • connection relationship of the second network element object in the 3D topology view displayed in the window is viewed, and the instruction sent to the network management background server is taken as an example, but for viewing any one
  • the operation of the connection relationship of the network element object is the same as that of the second network element object, and is no longer described.
  • the user may perform an operation of viewing the connection relationship of the second network element object by selecting an option to view the connection relationship of the second network element object.
  • the network management front-end client in this embodiment responds to the user's operation of viewing the connection relationship of the second network element object, and obtains the identifier of the second network element object, and then generates a second instruction, and sends the second instruction to the network management background server.
  • the second instruction includes an identifier of the second network element object and a connection relationship view operation command.
  • the network management background server After receiving the second instruction, the second instruction is parsed, and the identifier and the connection relationship of the second network element object are obtained therefrom to view the operation command. Then, the network management background server identifies the connection relationship between the second network element object and the second network element object according to the connection relationship view operation command and the identifier of the second network element object, and then queries the pre-stored connection object information according to the identifier of the second network element object. The identifiers of all the third network element objects connected to the second network element object are obtained therefrom.
  • the network management background server queries the pre-stored network element object information according to the identifier of the second network element object and the identifier of each third network element object, and obtains the location coordinates of the second network element object and each third network element object. Position coordinates. It is noted that, in addition to the location coordinates of the second network element object and each third network element object, the network management background server may also acquire other information of the second network element object and each third network element object. , such as size information, display status, and so on. In this embodiment, the location coordinate information is required in the focus, so that the location coordinates of the second network element object and each of the third network element objects are taken as an example. Then, the network management background server transmits the acquired location coordinates of the second network element object and the location coordinates of each third network element object to the network management foreground client.
  • the second command includes a connection relationship view operation command different from the identifier of the enlargement view operation command included in the first instruction, and is used to identify different commands and different processing modes.
  • Step 202 Receive a location coordinate of a second network element object sent by the network management background server and a location coordinate of each third network element object.
  • the location coordinate of the second network element object is obtained by the network management background server from the network element object information according to the identifier of the second network element object.
  • the location coordinate of the third network element object is the network management network management background server viewing the operation command and the identifier of the second network element object according to the connection relationship, and acquiring the identifier of the third network element object from the pre-stored connection object information, and then according to the third network
  • the identifier of the meta object is obtained from the network element object information.
  • connection object information includes: an identifier of the network element object at each end of each connection in the 3D topology view. It is also based on this, the network management background server can be based on the identity of the second network element object. Get the ID of all third network element objects.
  • the location coordinates of the second network element object returned by the network management background server and the position coordinates of each third network element object are received.
  • Step 203 Recalculate the position coordinates of each third network element object according to the size of the window, the position coordinate of the second network element object, and the position coordinate of each third network element object, so that each third network element object Can be displayed in the window.
  • the network management front client After the location coordinates of each third network element object are obtained, in order to enable all the third network element objects to be displayed in the window simultaneously with the second network element object, the network management front client recalculates each third network according to the size of the window.
  • the position coordinates of the meta object The processing device recalculates the position coordinates of the third network element object according to the fact that the third network element object can be displayed in the window when the recalculated position coordinates are displayed, and the calculation manner used is not limited.
  • Step 204 Display the second network element object and each third network element object in the window according to the recalculated position coordinates of each third network element object and the position coordinates of the second network element.
  • the network management front client After recalculating the position coordinates of each third network element object, the network management front client simultaneously displays the second in the window according to the recalculated position coordinates of the third network element object and the position coordinates of the second network element object.
  • the network element object and each of the third network element objects, that is, the second network element object and each network element object connected thereto are simultaneously displayed.
  • the network management foreground client responds to the user to view the connection relationship of the network element object. Operation, and generating a second instruction, sending the second instruction to the network management background server, obtaining the location coordinates of the network element object and the network element object connected thereto from the network management background server, and recalculating other network elements according to the size of the window.
  • the location coordinates of the object so that the network element object and other network element objects connected thereto can be displayed in the window, so that the user can quickly and clearly view the connection of a network element object, because it is not restricted by the subnet. Therefore, the problem that the network element with the connection relationship in different subnets in the prior art is invisible is solved.
  • the network management front-end client of the embodiment may further determine, according to the location coordinates of the third network element object, whether the third network element object is displayed in the window, that is, whether the location coordinate of the third network element object is within the window range. If the judgment result is no, the network management foreground client performs the location according to the size of the window, the location coordinates of the second network element object, and the location of each third network element object. Mark, recalculate the position coordinates of each third network element object so that each third network element object can display the operation in the window. Preferably, if the determination result is yes, the network management foreground client may not recalculate the location coordinates of the third network element object, but is not limited thereto. For example, even if the third network element object is already displayed in the window, the network management foreground client can recalculate the position coordinates of the third network element object.
  • the network management front-end client determines whether the location coordinate of the third network element object is already within the window range, and only recalculates the position coordinate of the third network element object when the determination result is no, thereby reducing the burden on the processing device. It is beneficial to improve the efficiency of the operation and maintenance personnel or the user to view the connection relationship of the second network element object.
  • the embodiment provides that the network management front client recalculates the position coordinates of each third network element object according to the size of the window, the position coordinate of the second network element object, and the position coordinate of each third network element object, so that the location coordinates of each third network element object are recalculated.
  • Each third network element object can be displayed in the window, ie, the implementation of step 203.
  • the implementation manner includes: the network management foreground client calculates a distance between the second network element object and the third network element object according to the location coordinates of the second network element object and the location coordinates of the third network element object.
  • the front-end client of the network management shortens the distance between the second network element object and the third network element object according to the size of the window until the third network element object is in the window. Then, the front-end client of the network management system recalculates the position coordinates of the third network element object according to the shortening multiple of the distance between the second network element object and the third network element object.
  • the shortening ratio of the distance between the second network element object and the third network element object can be obtained by comparing the distance before the shortening with the shortened distance.
  • the network management foreground client may calculate the difference of each coordinate according to the location coordinates of the second network element object and the third network element object, and then reduce the calculated difference of each coordinate by a shortening multiple of the distance. Then, using the position coordinates of the second network element object and the reduced coordinate difference respectively, the new position coordinates of the third network element object are obtained.
  • the network management front-end client may also use the coordinate value of the horizontal distance in the position coordinates of the second network element object to subtract the reduced coordinate difference value, so as to implement the second network element object and the third network element object.
  • the coordinate value of the horizontal distance between each network element object may be an X coordinate value, a y coordinate value, or a z coordinate value. As shown in FIG. 1B, the network management foreground client can narrow the distance between the second network element object and the third network element object by reducing the z coordinate values of the second network element object and the third network element object. .
  • this embodiment does not limit the displayed network elements having a connection relationship Whether the object belongs to the same subnet, when the third network element object and the second network element object belong to different subnets, information about the subnet to which the third network element object belongs may be displayed. If the second network element object and the third network element object belong to different subnets, the network management background server may further obtain the first information from the pre-stored information of each network element object according to the identifier of the obtained third network element object. The information of the subnet to which the third network element belongs is transmitted to the network management foreground client. After receiving the information of the subnet to which the third network element belongs, the client of the network management terminal displays the information of the subnet to which the third network element belongs.
  • the information of the subnet to which each network element object belongs is also pre-stored on the network management background server as part of the information of the network element object.
  • auxiliary information is provided for simultaneously displaying the network element object across the subnet in the same window, which is convenient for convenience.
  • the user is more aware of the connection relationship between the network element objects, and provides a condition for the user to judge whether the established Synchronous Digital Hierarchy (SDH) path is reasonable.
  • SDH Synchronous Digital Hierarchy
  • the network management front-end client displays the second network element object and each third in the window according to the recalculated position coordinates of each third network element object and the second network element location coordinates.
  • the network element object that is, the implementation of step 204.
  • the implementation manner includes: the network management front-end client displays each third network element object in the window according to the recalculated position coordinates of each third network element object, and displays the window according to the position coordinates of the second network element. a second network element object, and changing a color of a connection between the second network element object and each of the third network element objects, so that the color of the connection between the second network element object and each of the third network element objects is different The color of other connections in the window.
  • the front-end client of the U2000 can display the connection between each NE object and the NE object in yellow.
  • the U2000 front-end client can change the second NE.
  • the color of the connection between the object and each of the third network element objects is a color with a large contrast with yellow, such as green, red, etc., to highlight the connection relationship of the second network element object, so that the user can clearly see the first The connection relationship between two network element objects.
  • the present embodiment not only displays the second network element object and each of the third network element objects, but also achieves high by setting the color of the connection between the second network element object and each of the third network element objects different from the colors of other connections. For the purpose of bright display, the convenience of the user to learn the connection relationship of the second network element object can be further improved.
  • the network management front-end client responds to the user's operation of viewing the connection relationship of the network element object and sends an instruction to the network management background server, thereby acquiring the network element object and each connected to the network element object.
  • the location coordinates of the network element object are displayed in the window at the same time and are highlighted by the connection in the connection relationship, so that the operation and maintenance personnel or the user can clearly view the network element objects.
  • the connection relationship between the NEs facilitates fault discovery and troubleshooting based on the connection between the NE objects. This helps improve the efficiency of fault discovery and troubleshooting.
  • the network element objects across the subnets can be displayed in the same window, which provides conditions for the operation and maintenance personnel or the user to accurately determine whether the established SDH path is reasonable.
  • FIG. 3 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 3 of the present invention. As shown in FIG. 3, the method in this embodiment includes:
  • Step 301 Send a third instruction to the network management backend server in response to the user creating the SDH path.
  • the third instruction includes the source network element object information, the sink network element object information, and the specified information.
  • the specified information includes the information of the network element object that the created SDH path should pass and/or the network element object that cannot pass. Information.
  • the execution entity of this embodiment is also the front-end client of the network management system, and the front-end client of the network management system cooperates with the network management background server.
  • the network management front-end client provides the user with the function of creating an SDH path.
  • the function of creating an SDH path can be issued by right-clicking the function of creating an SDH path.
  • the front-end client of the network management system in this embodiment responds to the operation of creating an SDH path by the user, and can provide the source network element object information and the sink network element required for creating the SDH path by using, but not limited to, the interaction mode. Object information and required information.
  • the front-end client of the network management system can pop up a message window, and the user inputs the source network element object information, the sink network element object information, and the required specified information through the message window, and provides the information by clicking the submit or confirm button on the message window.
  • the network management front-end client of this embodiment can pop up a message window, and the user inputs the source network element object information, the sink network element object information, and the required specified information through the message window, and provides the information by clicking the submit or confirm button on the message window.
  • Each of the network element objects usually includes multiple ports.
  • the connection between the different network element objects when establishing SDH services is actually the connection between the ports between the two network element objects. Therefore, the source network element object information of this embodiment mainly includes the identifier of the source network element object and the port on which the SDH path is established.
  • the sink network element object information mainly includes an identifier of the sink network element object and a port on which the SDH path is established.
  • the specified information is optional, that is, the specified information may or may not include the specified information. Usually, when creating an SDH path, Need to specify information.
  • the specified information may include information of the network element object that should pass through when the SDH path is established (that is, the network element object must be on the established SDH path), where the information mainly refers to the identifier, port, and the like of the network element object.
  • the specified information may also include the information of the network element object that cannot be passed when the SDH path is established (that is, the network element object cannot be on the established SDH path), and the information mainly refers to the identifier, port, and the like of the network element object.
  • the specified information may also include information of the network element object that must pass through when the SDH path is established and information of the network element object that cannot pass.
  • the front-end client of the network management system can determine whether the SDH path has a resource alarm through the threshold of the number of resources.
  • the threshold of the number of resources may be input by the user, or may be preset in the front-end client of the network management system.
  • the resource threshold is used to determine whether the calculated SDH path has a resource alarm.
  • the resource mainly refers to a bandwidth resource.
  • the resource threshold can be set to 5 VC12s, but is not limited to this. If the number of available resources is less than 5 VC12, the resource requirements are not met.
  • the instruction to create an SDH path is taken as an example of the third instruction.
  • the network management foreground client of the embodiment After the user sends an operation to create an SDH path and provides the required information, the network management foreground client of the embodiment generates a third command and sends the third command to the network management backend server.
  • the third instruction is parsed, and the source network element object information, the sink network element object information, the resource quantity threshold, and the specified information are obtained, and are identified.
  • An SDH service relationship needs to be established between the source network element object and the sink network element object, that is, an SDH path is created, and the created SDH path must meet the requirements of the specified information.
  • the network management background server calculates the SDH from the source network element object to the sink network element object by using a preset path calculation method according to the information of the source network element object, the information of the sink network element object, and the specified information. path.
  • the SDH path is referred to as a first SDH path.
  • the network management background server transmits the information of the first SDH path and the available resource information of each network element object on the first SDH path to the network management foreground client.
  • the path calculation method is pre-stored on the network management background server.
  • the path calculation method pre-stored on the network management background server may be one or multiple. When there are multiple path calculation methods, the network management background server needs to select one of the multiple path calculation methods as the setting. Path calculation method.
  • the path calculation method may be a shortest path calculation method, but is not limited thereto.
  • the network management background server may use the path calculation method to calculate the source network element object according to the information of the source network element object, the information of the sink network element object, and the specified information.
  • the shortest SDH path to the sink network element the first SDH path.
  • the shortest SDH path refers to the path with the least number of hops from the source network element object to the sink network element object. Moreover, the first SDH path satisfies the requirements of the specified information. If the specified information includes the information of the network element object that should pass, the first SDH path must pass the information of the network element object that the specified information requires to pass; if the specified information includes the information of the network element object that cannot pass. Then, the first SDH path must not pass the network element object that the specified information requires cannot pass.
  • the process of calculating the first SDH path is similar to the prior art according to the information of the network element object, the information in the third instruction, and the path calculation method used in the network management, and is not described here.
  • Step 302 Receive information of the first SDH path sent by the network management background server and available resource information of each network element object on the first SDH path, and display the first SDH path in the window according to the information of the first SDH path.
  • the first SDH path is the source network element object calculated from the source network element object to the sink end according to the information of the source network element object, the information of the sink network element object, and the specified information.
  • the SDH path of the network element object is the source network element object calculated from the source network element object to the sink end according to the information of the source network element object, the information of the sink network element object, and the specified information.
  • the network management front-end client receives the information of the first SDH path sent by the network management background server and the available resource information of each network element object on the first SDH path, and then displays the first SDH in the window according to the information of the first SDH path. path.
  • the information of the first SDH path mainly includes identifiers of the network element objects constituting the first SDH path.
  • Step 303 Determine, according to the available resource information and the number of resources thresholds of the network element objects in the first SDH path, whether the first SDH path has a resource alarm. If the determination result is yes, that is, the first SDH path has a resource alarm, go to step 304. Otherwise, go to step 305.
  • the resource usage of each network element object on the first SDH path mainly refers to the remaining resources of each network element object on the port on the first SDH path.
  • the resource is preferably a bandwidth resource.
  • the network management front client allocates the ports of the network element objects on the first SDH path.
  • the number of the remaining resources is compared with the threshold of the number of resources. If the number of remaining resources of the port of the network element is less than the threshold of the number of resources, the network element does not meet the resource requirements of the first SDH path. On the other hand, if the number of remaining resources of the ports of all network element objects is greater than or equal to the resource quantity threshold, no resource alarm is required.
  • Step 304 Display path alarm information corresponding to the first SDH path in the window.
  • Step 305 The SDH path creation operation is completed.
  • the network management front-end client further determines, according to the remaining resources of the ports of the network element objects in the first SDH path, for example, the remaining bandwidth resources, whether the first SDH path has a resource alarm, that is, determines the first SDH path. Whether the resources of the ports of the respective network element objects meet the requirements for developing the SDH service.
  • the network management front-end client of the embodiment displays the path alarm information corresponding to the first SDH path to the user through the window, so that the user can adjust the time in time.
  • the first SDH path provides conditions for successful SDH service.
  • FIG. 4 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 4 of the present invention.
  • the embodiment is implemented based on the embodiment shown in FIG. 3.
  • the method in this embodiment further includes after step 304:
  • Step 306 Send a fourth instruction to the network management backend server in response to the user modifying the operation of the first SDH path.
  • the fourth instruction includes an operation command for modifying the first SDH path.
  • the network management foreground client can display the first SDH path on the screen.
  • the user can directly modify the first SDH path to the front-end client of the NMS.
  • the option to modify the first SDH path can be selected by right clicking on a network element object on the first SDH path to issue a modification operation to the network management foreground client.
  • the network management front-end client responds to the user's modification operation, and generates a fourth instruction, and sends the fourth instruction to the network management background server, so that the network management background server recalculates an SDH path.
  • the user can first view the resource on the first SDH path by sending a resource view to the front-end client of the network management system.
  • Resource usage of the port to further determine whether there is an insufficient or insufficient network element object on the first SDH path, and then issue a modification operation to the network management foreground client to request recalculation from the source network element object to the sink.
  • Step 307 Receive information of the second SDH path sent by the network management background server and available resource information of each network element object on the second SDH path, and display the second SDH path in the window according to the information of the second SDH path.
  • the second SDH path is calculated by using the set path calculation method according to the operation command of the source network element object, the information of the sink network element object, and the specified information according to the operation command of modifying the first SDH path.
  • the information of the second SDH path mainly includes identifiers of the network element objects constituting the second SDH path.
  • the network management background server After receiving the fourth instruction, the network management background server parses the fourth instruction, and obtains an operation command for modifying the first SDH path, and identifies that the source network element object needs to be recalculated from the source network element object to the sink network element object. The SDH path. Then, the network management background server calculates the SDH for the source network element object and the sink network element object according to the command, the pre-stored information of each network element object, the information included in the fourth instruction, and the path calculation method used. path.
  • the network management front-end client when the first SDH path does not meet the resource requirements for the SDH service, the network management front-end client sends the path alarm information to enable the user to issue a modification operation, and sends a response to the user's modification operation to the network management background server.
  • the fourth instruction enables the network management background server to recalculate an SDH path, and implements an SDH service based on the newly established SDH path, thereby improving the success rate of developing the SDH service.
  • the network management background server updates the resource utilization of the two network element objects and updates the service relationship between the two network element ports, so as to facilitate Comprehensively manage the information of each network element object, which is more accurate for the topology view based on the information of each network element object.
  • first network element object, the second network element object, and the third network element object in the foregoing embodiments may be the same network element object or different network element objects.
  • FIG. 5 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 5 of the present invention. As shown in FIG. 5, the method in this embodiment includes:
  • Step 501 Receive a first instruction sent by a front end client of the network management.
  • the first instruction is generated by the network management foreground client in response to the operation of the first network element object in the 3D topology view displayed by the user selected window.
  • the first instruction includes an identification of the first network element object and an enlarged view operation command.
  • the execution entity of this embodiment is a network management backend server.
  • the network management background server cooperates with the network management foreground client.
  • the operation of the first instruction sent by the network management front-end client to the network management background server in response to the operation of the first network element object in the 3D topology view displayed by the user selection window may be referred to the description of the embodiment shown in FIG. This will not be repeated here.
  • Step 502 Obtain location coordinates and size information of the first network element object from the stored network element object information according to the enlarged view operation command and the identifier of the first network element object.
  • the size information of the first network element object includes the length, width, and height of the first network element object.
  • the network element object information includes the identifier, location coordinates, and size information of each network element object in the 3D topology view.
  • the network element object information and the connection object information are pre-stored on the network management background server.
  • the network element object information and the connection object information refer to the description in the embodiment shown in FIG. 1, and details are not described herein again.
  • Step 503 The position coordinate and the size information of the first network element object are transmitted to the front-end client of the network management, so that the front-end client of the network management system redisplays the first network element object of the placed network at the position coordinate adjusted in the window.
  • the network management background server parses the first instruction, and obtains the identifier of the first network element object and the enlarged view operation command. Then, the network management background server obtains the location coordinate and size information of the first network element object from the pre-stored network element object information according to the enlarged view operation command and the identifier of the first network element object, and sets the position coordinate of the first network element object. And size information is passed to the network management front-end client.
  • the network element object information may further include a display state of each network element object in the 3D topology view.
  • the gateway background server may obtain, according to the display status of each network element object in the operation command and the network element object information, the location of each network element object currently displayed in the window of the front-end client of the network management system. Coordinate and size information.
  • the first network element object is displayed in the window, and therefore belongs to a member of each network element object currently displayed in the window, that is, each network element object currently displayed in the window includes the first network element object.
  • the network management background server may further obtain the location coordinates and the size information of the first network element object from the location coordinates and size information of each network element object currently displayed in the obtained window according to the identification information of the first network element object.
  • the gateway background server can transmit the location coordinates and size information of the other network element objects currently displayed in the window to the network management device while transmitting the location coordinates and size information of the first network element object to the network management foreground client. Front desk client.
  • the network management background server may directly send the location coordinate and size information of each network element object currently displayed in the obtained window to the network management front-end client, without separately obtaining the location coordinate and size information of the first network element object.
  • the network management front-end client redisplays the enlarged first network image in the position coordinate of the adjusted position in the window. See the description of the embodiment shown in FIG.
  • the gateway background server cooperates with the network management front-end client to obtain the location coordinate and size information of the first network element object according to the first instruction of the network management front-end client, and provides the network management front-end client to the network management front-end client.
  • the client completes the adjustment of the display position of the network element object and the enlargement of the network element object based on the acquired information and the size of the window, so that the network element object can be highlighted in the window, thereby enabling the user to quickly get from the window.
  • the identification of the network element object in many network element objects provides conditions.
  • FIG. 6 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 6 of the present invention. As shown in FIG. 6, the method in this embodiment includes:
  • Step 601 Receive a second instruction sent by the front end client of the network management.
  • the second instruction is generated by the operation of the network management front client in response to the connection relationship of the second network element object in the 3D topology view displayed by the user viewing window.
  • the second instruction includes an identifier of the second network element object and a connection relationship view operation command.
  • the connection relationship of the second network element object includes a second network element object and all third network element objects, and the third network element object is a network element connected to the second network element object.
  • the execution entity of this embodiment is a network management backend server.
  • the network management background server cooperates with the network management front-end client.
  • Step 602 View the operation command and the identifier of the second network element object according to the connection relationship, obtain the identifiers of all the third network element objects from the stored connection object information, and according to the identifier of the second network element object and each third network
  • the identifier of the meta object obtains the location coordinates of the second network element object and the location coordinates of each third network element object from the network element object information.
  • connection object information includes: an identifier of the network element object at each end of each connection in the 3D topology view.
  • Step 603 The location coordinates of the second network element object and the location coordinates of each third network element are transmitted to the network management foreground client, so that the network management foreground client simultaneously displays the second network element object and each third network in the window. Meta object.
  • the network management background server may obtain information about the subnet to which the third network element object belongs and transmit the information to the network management front-end client, so that the network management system
  • the foreground client displays information about the subnet to which the third network element object belongs.
  • the gateway background server cooperates with the network management front-end client, and obtains the location coordinates of the second network element object and each third network element object according to the second instruction of the network management front-end client, and provides the network management front-end client. And adjusting, by the network management front-end client, the display position of the third network element object based on the obtained information and the size of the window, so that the third network element object and the second network element object are simultaneously displayed in the window, thereby enabling the user to view
  • the connection relationship of the network element provides conditions.
  • FIG. 7 is a flow chart of processing network element object information in a 3D topology view according to Embodiment 7 of the present invention. As shown in FIG. 7, the method in this embodiment includes:
  • Step 701 Receive a third instruction sent by a network management front-end client.
  • the third instruction is generated by the network management foreground client in response to the user creating an SDH path.
  • the third instruction includes source network element object information, sink network element object information, and designated information.
  • the specified information includes information of the network element object through which the created SDH path should pass and/or information of the network element object that cannot pass.
  • the execution entity of this embodiment is a network management backend server.
  • the network management background server cooperates with the network management foreground client.
  • the operation of the third-order command is sent to the network management back-end server in response to the operation of the user to create the SDH path.
  • the operation of the third-order command is sent to the network management back-end server in response to the operation of the user to create the SDH path.
  • Step 702 Calculate a first SDH path by using a set path calculation method according to the information of the source network element object, the information of the sink network element object, and the specified information, where the first SDH path is the calculated slave source end.
  • Step 703 The information about the first SDH path and the available resource information of each network element object on the first SDH path are transmitted to the network management front-end client, so that the network management front-end client displays the first SDH in the window according to the information of the first SDH path. path.
  • the network management background server parses the third instruction, and obtains the source network element object information, the sink network element object information, the resource quantity threshold, and the specified information, and identifies the same.
  • An SDH service relationship needs to be established between the source NE object and the sink NE object, that is, an SDH path is created, and the created SDH path must meet the requirements of the specified information.
  • the network management background server calculates the SDH from the source network element object to the sink network element object by using a preset path calculation method according to the information of the source network element object, the information of the sink network element object, and the specified information. path.
  • the SDH path is referred to as a first SDH path.
  • the network management background server transmits the information of the first SDH path and the available resource information of each network element object on the first SDH path to the network management foreground client.
  • the information of the first SDH path mainly includes the identifier of the network element object that constitutes the first SDH path.
  • the path calculation method is pre-stored on the network management background server.
  • the path calculation method pre-stored on the network management background server may be one or multiple.
  • the network management background server needs to select one of the multiple path calculation methods as the set path calculation method.
  • the path calculation method may be the shortest path calculation method, but is not limited Here.
  • the network management background server may use the path calculation method to calculate the source network element object according to the information of the source network element object, the information of the sink network element object, and the specified information.
  • the shortest SDH path to the sink network element the first SDH path.
  • the shortest SDH path refers to the path with the least number of hops from the source network element object to the sink network element object. Moreover, the first SDH path satisfies the requirements of the specified information. If the specified information includes the information of the network element object that should pass, the first SDH path must pass the information of the network element object that the specified information requires to pass; if the specified information includes the information of the network element object that cannot pass. Then, the first SDH path must not pass the network element object that the specified information requires cannot pass.
  • the process of calculating the first SDH path is similar to the prior art according to the information of the network element object, the information in the third instruction, and the path calculation method used in the network management, and is not described here.
  • the gateway background server cooperates with the network management front-end client to create an SDH path between the source network element object and the sink network element object according to the third instruction of the network management front-end client, and the created SDH path and The available resource information of each network element object on the SDH path is provided to the front-end client, so that the front-end client can display in the window, which provides conditions for the user to carry out the SDH service.
  • FIG. 8 is a flowchart of a method for processing network element object information in a 3D topology view according to Embodiment 8 of the present invention. This embodiment is implemented based on the embodiment shown in FIG. As shown in FIG. 8, the method in this embodiment further includes after step 703:
  • Step 704 Receive a fourth instruction sent by the front end client of the network management.
  • the fourth instruction is generated by the network management foreground client in response to the user modifying the first SDH path.
  • the fourth instruction includes an operation command to modify the first SDH path.
  • the operation of the fourth command is sent to the network management background server in response to the user modifying the operation of the first SDH path.
  • Step 705 Calculate the second SDH path by using the set path calculation method according to the information about the source network element object, the information of the sink network element object, and the specified information according to the operation command for modifying the first SDH path. Recalculated from the source network element object when the second SDH path The SDH path to the sink network element object.
  • Step 706 The information of the second SDH path and the available resource information of each network element object on the second SDH path are transmitted to the network management front-end client, so that the network management front-end client displays the second SDH in the window according to the information of the second SDH path. path.
  • the network management background server parses the fourth instruction, and obtains an operation command for modifying the first SDH path, and identifies that the source network element object needs to be recalculated from the source network element object to the sink network element object.
  • the SDH path between.
  • the network management background server calculates the SDH for the source network element object and the sink network element object according to the command, the pre-stored information of each network element object, the information included in the fourth instruction, and the path calculation method used.
  • the path and the information of the recalculated SDH path (ie, the second SDH path) and the available resource information of each network element object on the second SDH path are transmitted to the network management foreground client.
  • the information of the second SDH path mainly includes the identifier of the network element object that constitutes the second SDH path.
  • the gateway background server cooperates with the network management front-end client, and according to the fourth instruction of the network management front-end client, re-creates the SDH path between the source network element object and the sink network element object according to the fourth instruction and
  • the information of the re-created SDH path and the available resource information of each network element object on the SDH path are provided to the front-end client, so that the front-end client can be displayed in the window, allowing the user to modify the SDH path for the user to correctly develop.
  • the SDH business provides the conditions.
  • FIG. 9 is a schematic structural diagram of a front-end client of a network management system according to an embodiment of the present invention.
  • the network management front-end client of this embodiment includes: a user event response module 91, an information receiving module 92, and a topology display module 93.
  • the user event response module 91 is connected to the network management background server, and is configured to send a first instruction to the network management background server in response to the operation of the first network element object in the 3D topology view displayed by the user selection window.
  • the first instruction includes an identifier of the first network element object and an enlarged view operation command.
  • the information receiving module 92 is connected to the network management background server, and is configured to receive location coordinates and size information of the first network element object sent by the network management background server.
  • the size information of the first network element object includes the length, the width, and the height of the first network element object.
  • the location coordinate and the size information of the first network element object are the network management background server according to the enlarged viewing operation command and the first network element object. Identification, obtained from the stored network element object information; each of the network element object information in the 3D topology view The identifier, location coordinates, and size information of the NE object.
  • the topology display module 93 is connected to the information receiving module 92, and configured to adjust the position coordinates of the first network element object in the window according to the size of the window and the position coordinate of the first network element object, and the size information of the first network element object Multiply by the preset magnification to enlarge the first network element and redisplay the enlarged first network element at the adjusted position coordinates in the window.
  • the network element object information may further include: a display state of each network element object in the 3D topology view.
  • the information receiving module 92 is specifically configured to receive location coordinates and size information of each network element object currently displayed in a window sent by the network management background server.
  • the first network element object is included in each network element object currently displayed in the window.
  • Each network element object currently displayed in the window is determined by the network management background server according to the display state of each network element object in the network element object information.
  • the topology display module 93 may be configured to calculate, according to the location coordinates of each network element object currently displayed in the window, other network element objects except the first network element object currently displayed in the network element object currently displayed in the window.
  • the length, width, and height in the size information are multiplied by the magnification; according to the distance and recalculation between the other network element objects except the first network element object and the first network element object currently displayed in the window
  • the position coordinate of the network element object, the enlarged size information of the first network element object, and the first network element among the network element objects currently displayed in the received window Like
  • the function modules of the front-end client of the network management system in this embodiment can be used to perform the method flow of processing the network element object information in the 3D topology view shown in FIG. 1.
  • the specific working principle is not described here. For details, refer to the description of the method implementation.
  • the network management front-end client in this embodiment responds to the user selecting the operation of the network element object, and sends an instruction to the network management background server to obtain the location coordinate and size information of the network element object from the network management background server, and further obtains the information and the window based on the acquired information.
  • the size completes the adjustment of the display position of the network element object and the enlargement of the network element object, so that the network element object can be protruded in the window.
  • the user event response module in the front-end client of the network management system provided by the embodiment of the present invention is further configured to enable the user to quickly identify the network element pair from the plurality of network element objects in the window.
  • the 91 is further configured to issue a second instruction to the network management backend server in response to the operation of the user to view the connection relationship of the second network element object in the 3D topology view displayed by the window.
  • the second instruction includes an identifier of the second network element object and a connection relationship viewing operation command; the connection relationship of the second network element object includes the second network element object and all the third network element objects, and the third network element object is The network element object connected to the second network element object.
  • the information receiving module 92 is further configured to receive the location coordinates of the second network element object sent by the network management background server and the location coordinates of each third network element object.
  • the location coordinate of the first network element object is obtained by the network management background server according to the identifier of the second network element object, and is obtained from the network element object information; the location coordinate of the third network element object is the network management background server viewing the operation command according to the connection relationship.
  • the identifier of the second network element object, the identifier of the third network element object is obtained from the stored connection object information, and then obtained from the network element object information according to the identifier of the third network element object.
  • the connection object information includes: an identifier of the network element object at each end of each connection in the 3D topology view.
  • the topology display module 93 is further configured to recalculate the position coordinates of each third network element object according to the size of the window, the position coordinate of the second network element object, and the position coordinate of each third network element object, Each third network element object can be displayed in the window, and the second network element object and each are displayed in the window according to the recalculated position coordinates of each third network element object and the position coordinates of the second network element A third network element object.
  • the topology display module 93 may be specifically configured to determine whether the location coordinates of the third network element object are within the window range, and if the determination result is no, perform according to the size of the window, the location coordinates of the second network element object, and each The position coordinates of the third network element object, and the position coordinates of each third network element object are recalculated so that each third network element object can display the operation in the window.
  • the topology display module 93 is specifically configured to calculate a distance between the third network element object and the second network element object according to the location coordinates of the second network element object and the location coordinates of the third network element object, according to the window The size, shortening the distance between the third network element object and the second network element object until the third network element object is displayed in the window, according to the shortening multiple of the distance between the third network element object and the second network element object , Recalculate the position coordinates of the third network element object.
  • the topology display module 93 can be specifically configured to recalculate each third network element object according to Position coordinates, displaying each third network element object in the window, displaying the second network element object in the window according to the position coordinates of the second network element, and changing the second network element object and each third network element object The color of the connection between the two, so that the color of the connection between the second network element object and each of the third network element objects is different from the color of other connections in the window.
  • the topology display module 93 is further configured to receive information about a subnet to which the third network element object belongs when the second network element object and the third network element object belong to different subnets, and display the third network element object. Information about the subnet to which it belongs.
  • the network management front-end client in this embodiment responds to the user's operation of viewing the connection relationship of the network element object, and generates a second instruction, and sends the second instruction to the network management background server to obtain the network element object from the network management background server.
  • the position coordinates of the connected network element object and recalculate the position coordinates of other network element objects according to the size of the window, so that the network element object and other network element objects connected thereto can be displayed in the window, so that the user can be fast and clear
  • the connection to a network element object is not limited by the subnet, thereby solving the problem that the network element with the connection relationship in different subnets in the prior art is invisible.
  • the user event response module 91 of the embodiment of the present invention is further configured to issue a third instruction to the network management background server in response to the operation of the user creating the SDH path. among them.
  • the third instruction includes source network element object information, sink network element object information, and specified information.
  • the specified information includes information of the network element object through which the created SDH path should pass and/or information of the network element object that cannot pass.
  • the information receiving module 92 is further configured to receive information about the first SDH path sent by the network management background server and available resource information of each network element object on the first SDH path, and display the first SDH path in the window according to the information of the first SDH path.
  • the first SDH path is a source network object to the sink network calculated by the network path background server according to the information of the source network element object, the information of the sink network element object, and the specified information, using the set path calculation method.
  • the SDH path of the meta object is a source network object to the sink network calculated by the network path background server according to the information of the source network element object, the information of the sink network element object, and the specified information, using the set path calculation method.
  • the topology display module 93 is further configured to determine, according to the available resource information and the number of resources thresholds of the network element objects on the first SDH path, whether the first SDH path has a resource alarm, and when the judgment result is a resource alarm, in the window.
  • the path alarm information corresponding to the first SDH path is displayed.
  • the network management front-end client of the embodiment can also display the path alarm information to the user through the window, so that the user can adjust the first SDH path in time, and provide conditions for successfully performing the SDH service.
  • the user event response module 91 of the embodiment of the present invention is further configured to issue a fourth instruction to the network management background server in response to the user modifying the operation of the first SDH path.
  • the fourth instruction includes an operation command for modifying the first SDH path.
  • the information receiving module 92 is further configured to receive information about the second SDH path sent by the network management background server and available resource information of each network element object on the second SDH path, and display the information in the window according to the information of the second SDH path.
  • the second SDH path is determined by the network management background command according to the operation command of modifying the first SDH path, and according to the information of the source network element object, the information of the sink network element object, and the specified information, using the set path calculation method.
  • the S DH path from the source network element object to the sink network element object.
  • the network management front-end client of the embodiment may also display the path alarm information by using the path alarm information when the first SDH path does not meet the resource requirements for the SDH service, and send the modification operation to the network management background server by responding to the user modification operation.
  • the fourth instruction enables the network management background server to recalculate an SDH path, and implements an SDH service based on the newly established SDH path, thereby improving the success rate of developing the SDH service.
  • FIG. 10 is a schematic structural diagram of a network management backend server according to Embodiment 10 of the present invention.
  • the network management background server of this embodiment includes: an instruction receiving module 1001, an information obtaining module 1002, and an information delivery module 1003.
  • the command receiving module 1001 is connected to the front-end client of the network management system, and is configured to receive the first instruction sent by the client of the network management platform.
  • the first instruction is generated by the network management front-end client in response to the operation of the first network element object in the 3D topology view displayed by the user selected window; the first instruction includes the identifier of the first network element object and the enlarged viewing operation command. .
  • the information obtaining module 1002 is configured to be connected to the instruction receiving module 1001, and configured to acquire the first network element from the stored network element object information according to the enlarged viewing operation command and the identifier of the first network element object.
  • the size information of the first network element object includes a length, a width, and a height of the first network element object.
  • the network element object information includes an identifier, a location coordinate, and a size information of each network element object in the 3D topology view.
  • the information delivery module 1003 is connected to the information acquisition module 1002 and the network management front-end client, and is configured to transmit the location coordinates and size information of the first network element object to the front-end client of the network management system, so that the network management front-end client adjusts the position in the window.
  • the enlarged first network element object is redisplayed at the coordinates.
  • the network element object information further includes: a display state of each network element object in the 3D topology view.
  • the information acquiring module 1002 of the embodiment may be configured to obtain, according to the display state of each network element object in the enlarged viewing operation command and the network element object information, the location of each network element object currently displayed in the window from the network element object information. Coordinate and size information window. The first network element object is included in each network element object currently displayed in the window.
  • the information delivery module 1003 is specifically configured to transmit, to the network management foreground client, location coordinate and size information of each network element object currently displayed in the window.
  • the functional modules of the network management background server of this embodiment can be used to perform the processing shown in FIG.
  • the network management background server of the embodiment cooperates with the network management front-end client provided by the embodiment of the present invention, and obtains the location coordinate and size information of the first network element object according to the first instruction of the network management front-end client, and provides the network management front-end client. End, for the network management front-end client to complete the adjustment of the display position of the network element object and the enlargement of the network element object based on the acquired information and the size of the window, so that the network element object can be highlighted in the window, thereby enabling The user can quickly identify the network element object from a plurality of network element objects in the window.
  • the instruction receiving module 1001 of the network management background server of the embodiment of the present invention is further configured to receive a second instruction sent by the front-end client of the network management.
  • the second instruction is generated by the operation of the network management front-end client in response to the connection relationship of the second network element object in the 3D topology view displayed by the user viewing window; the second instruction includes the identifier and connection of the second network element object.
  • the relationship view operation command; the connection relationship of the second network element object includes the second network element object and all the third network element objects, and the third network element object is the network element object connected to the second network element object.
  • the information obtaining module 1002 is further configured to view the operation command and the first according to the connection relationship.
  • the identifier of the second network element object, the identifiers of all the third network element objects are obtained from the pre-stored connection object information, and the network element object information is obtained according to the identifier of the second network element object and the identifier of each third network element object.
  • the connection object information includes: an identifier of the network element object at each end of each connection in the 3D topology view.
  • the information delivery module 1003 is further configured to: transmit the location coordinates of the second network element object and the location coordinates of each third network element to the network management foreground client, so that the network management foreground client simultaneously displays the second network element in the window.
  • Object and each third network element object are further configured to: transmit the location coordinates of the second network element object and the location coordinates of each third network element to the network management foreground client, so that the network management foreground client simultaneously displays the second network element in the window.
  • the foregoing functional modules can be used to perform the method flow for processing the network element object information in the 3D topology view shown in FIG. 6.
  • the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the network management background server of the embodiment cooperates with the network management front-end client provided by the embodiment of the present invention, and obtains the location coordinates of the second network element object and each third network element object according to the second instruction of the network management foreground client.
  • the front-end client of the network management system Providing to the front-end client of the network management system, the adjustment of the display position of the third network element object by the front-end client of the network management system based on the acquired information and the size of the window, so that the third network element object and the second network element object are simultaneously displayed in the window.
  • the user can view the connection relationship of the network element.
  • the signaling receiving module 1001 of the embodiment of the present invention is further configured to receive a third instruction sent by the front-end client of the network management.
  • the third instruction is generated by the network management front-end client in response to the user creating the SDH path of the synchronous digital transmission system; the third instruction includes the source network element object information, the sink network element object information, and the specified information; The information of the network element object that the created SDH path should pass and/or the information of the network element object that cannot pass.
  • the information obtaining module 1002 is further configured to calculate the first SDH path by using the set path calculation method according to the information of the source network element object, the information of the sink network element object, and the specified information, where the first SDH path is calculated.
  • the SDH path from the source NE object to the sink NE object.
  • the information delivery module 1003 is further configured to: transmit the information of the first SDH path and the available resource information of each network element object on the first SDH path to the network management foreground client, so that the network management foreground client according to the information of the first SDH path The first SDH path is displayed in the window.
  • the foregoing functional modules can be used to perform the method flow for processing the network element object information in the 3D topology view shown in FIG. 7.
  • the specific working principle is not described here.
  • the network management background server of the embodiment cooperates with the network management front-end client provided by the embodiment of the present invention, and creates an SDH path between the source network element object and the sink network element object according to the third instruction of the network management front-end client.
  • the created SDH path and the available resource information of each network element object on the SDH path are provided to the front-end client, so that the front-end client can be displayed in the window, which provides conditions for the user to carry out the SDH service.
  • the signaling receiving module 1001 of the embodiment of the present invention is further configured to receive a fourth instruction sent by the front-end client of the network management.
  • the fourth instruction is generated by the network management foreground client in response to the user modifying the first SDH path, and the fourth instruction includes an operation command for modifying the first SDH path.
  • the information obtaining module 1002 is further configured to calculate, according to the operation command of the first SDH path, the information of the source network element object, the information of the sink network element object, and the specified information, using the set path calculation method.
  • the second SDH path is a recalculated SDH path from the source network element object to the sink network element object, so that the network management foreground client displays the second SDH in the window according to the information of the second SDH path. path.
  • the information delivery module 1003 is further configured to transmit the information of the second SDH path and the available resource information of each network element object on the second SDH path to the network management foreground client.
  • the foregoing function modules can be used to perform the method flow for processing the network element object information in the 3D topology view shown in FIG. 8.
  • the specific working principle is not described here. For details, refer to the description of the method embodiment.
  • the network management background server of the embodiment cooperates with the network management front-end client provided by the embodiment of the present invention, and re-creates the source network element object to the sink network element object according to the fourth instruction according to the fourth instruction of the network management front-end client.
  • the SDH path is provided to the front-end client of the re-created SDH path and the available resource information of each network element object on the SDH path, so that the front-end client can display in the window, allowing the user to modify the SDH path, The user provides the conditions for the correct implementation of the SDH service.
  • FIG. 11 is a schematic structural diagram of a network management system according to Embodiment 11 of the present invention. As shown
  • the system of this embodiment includes: a network management front-end client 1111 and a network management back-end server 1112.
  • the network management front-end client 1111 and the network management background server 1112 are connected.
  • the network management foreground client 1111 is configured to send a first instruction to the network management background server 1112 in response to the operation of the first network element object in the 3D topology view displayed by the user selection window.
  • the first instruction includes an identification of the first network element object and an enlarged view operation command.
  • the network management background server 11 12 is configured to obtain the location coordinate and the size information of the first network element object from the stored network element object information according to the enlarged view operation command and the identifier of the first network element object, and send the location information and the size information of the first network element object to the network management front end client 1 11 1 Transfer the position coordinates and size information of the first network element object.
  • the network element object information includes identifiers, location coordinates, and size information of each network element object in the 3D topology view.
  • the network management front-end client 11 11 is further configured to adjust the position coordinate of the first network element object in the window according to the size of the window and the position coordinate of the first network element object, and multiply the size information of the first network element object by a preset magnification. , to enlarge the first network element object, and redisplay the enlarged first network element object at the adjusted position coordinate in the window.
  • the structure of the network management front-end client 11 11 of this embodiment can be referred to as shown in FIG. 9.
  • the working principle can be referred to the process of processing the network element object information in the 3D topology view as shown in FIG. 1 , and details are not described herein.
  • the structure of the network management background server 11 12 of this embodiment can be referred to as shown in FIG. 10, and the working principle can be referred to the process of processing the network element object information in the 3D topology view as shown in FIG. 5, and details are not described herein.
  • the network management background server cooperates with the network management front-end client, and the network management front-end client responds to the user's operation of viewing the network element object and sends a first instruction to the network management background server, and the network management background server according to the network management front-end client
  • An instruction is used to obtain location coordinate and size information of the first network element object, and provide the network management front-end client, and the network management front-end client completes the network element object based on the received information of the first network element object and the size of the window.
  • the adjustment of the display position and the enlargement of the network element object enable the network element object to be highlighted in the window, thereby enabling the user to quickly identify the network element object from a plurality of network element objects in the window.
  • the network management front-end client 11 11 of the embodiment of the present invention is further configured to send a second instruction to the network management background server 1112 in response to the operation of the connection relationship of the second network element object in the 3D topology view displayed by the user viewing window.
  • the second instruction includes an identifier of the second network element object and a connection relationship view operation command; the connection relationship of the second network element object includes the second network element object and all the third network element objects; the third network element object is
  • the network element connected to the second network element object to the network management background server 11 12 is further configured to view the operation command and the second network element according to the connection relationship.
  • the identifier of the object obtains the identifiers of all the third network element objects from the stored connection object information, and obtains the second information from the network element object information according to the identifier of the second network element object and the identifier of each third network element object.
  • the location coordinates of the network element object and the location coordinates of each third network element object, and the location coordinates of the second network element object and the location coordinates of each third network element are transmitted to the network management foreground client 1111.
  • the connection object information includes: an identifier of the network element object at each end of each connection in the 3D topology view.
  • the network management foreground client 1111 is further configured to recalculate the position coordinates of each third network element object according to the size of the window, the position coordinates of the second network element object, and the position coordinates of each third network element object, so that each The third network element object can be displayed in the window, and the second network element object and each third are displayed in the window according to the recalculated position coordinates of each third network element object and the position coordinates of the second network element.
  • Network element object is further configured to recalculate the position coordinates of each third network element object according to the size of the window, the position coordinates of the second network element object, and the position coordinates of each third network element object, so that each The third network element object can be displayed in the window, and the second network element object and each third are displayed in the window according to the recalculated position coordinates of each third network element object and the position coordinates of the second network element.
  • the network management background server cooperates with the network management front-end client, and the network management front-end client responds to the user's operation of viewing the connection relationship of the second network element object and sends a second instruction to the network management background server, and the network management background server is configured according to the network management system.
  • the second instruction acquires the location coordinates of the second network element object and the location coordinates of each third network element object connected to the second network element object, and provides the network client with a front-end client, and the network management front-end client receives the information according to the
  • the window size recalculates the position coordinates of the third network element object, so that the second network element object and all the third network element objects are simultaneously displayed in the window, so that the operation and maintenance personnel or the user can clearly view the between the network element objects.
  • the connection relationship facilitates fault detection and troubleshooting based on the connection relationship between the NE objects, which is beneficial to improving the efficiency of fault discovery and troubleshooting.
  • the network management front-end client 1111 provided by the embodiment of the present invention is further configured to send a third instruction to the network management background server 1112 in response to the user creating an operation of the synchronous digital transmission system SDH path.
  • the third instruction includes source network element object information, sink network element object information, and specified information.
  • the specified information includes information of the network element object through which the created SDH path should pass and/or information of the network element object that cannot pass. .
  • the network management background server 1112 is further configured to calculate the first SDH path by using the set path calculation method according to the information of the source network element object, the information of the sink network element object, and the specified information, and transmit the first SDH path to the network management foreground client 1111.
  • the information of an SDH path and the available resource information of each network element object on the first SDH path; the first SDH path is the calculated SDH path from the source network element object to the sink network element object.
  • the network management front-end client 1111 is further configured to receive information about the first SDH path sent by the network management background server and available resource information of each network element object on the first SDH path, and according to the first SDH The information of the path is displayed in the window, and the first SDH path is displayed in the window. According to the available resource information and the number of resources of the network element object in the first SDH path, it is determined whether the first SDH path has a resource alarm, and if the judgment result is a resource alarm, The path alarm information corresponding to the first SDH path is displayed in the window.
  • the network management background server cooperates with the network management front-end client, and the network management front-end client responds to the user to create an SDH path and sends a third instruction to the network management background server, and the network management background server creates the source according to the third instruction.
  • the SDH path of the network element object to the sink network element object is provided to the network management front-end client by the created SDH path and the available resource information of each network element object, and the network management front-end client displays the path alarm information to the user through the window. Therefore, the user can adjust the first SDH path in time, and provide conditions for successfully carrying out the SDH service.
  • the network management front-end client 1111 provided by the embodiment of the present invention is further configured to send a fourth instruction to the network management background server 1112 in response to the user modifying the operation of the first SDH path; the fourth instruction includes an operation command for modifying the first SDH path. .
  • the network management background server 1112 is further configured to calculate the second SDH by using the set path calculation method according to the information of the source network element object, the information of the sink network element object, and the specified information according to the operation command for modifying the first SDH path.
  • the path, and the information of the second SDH path and the available resource information of each network element object on the second SDH path are transmitted to the network management foreground client 1111.
  • the second SDH path is a recalculated SDH path from the source network element object to the sink network element object.
  • the network management front-end client 1111 is further configured to receive information about the second SDH path sent by the network management background server 1112 and available resource information of each network element object on the second SDH path, and display the second information in the window according to the information of the second SDH path. SDH path.
  • the network management background server cooperates with the network management front-end client, and the network management front-end client responds to the user to modify the SDH path and sends a fourth command to the network management background server, and the network management background server recalculates the source according to the fourth instruction.
  • the SDH path of the end network element object to the sink network element object and provides the recalculated SDH path and the available resource information of each network element object on the network management front end client, so that the user can perform SDH based on the newly established SDH path.
  • Business improving the success rate of launching SDH business.
  • the aforementioned program can be stored in a computer readable storage medium.
  • the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • User Interface Of Digital Computer (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明提供一种处理3D拓扑视图中网元对象信息的方法及设备。其中,方法包括:响应于用户选中窗口所显示的3D拓扑视图中第一网元对象的操作,向网管后台服务器发出第一指令,接收网管后台服务器发送的第一网元对象的位置坐标和大小信息,根据窗口的大小和第一网元对象的位置坐标调整第一网元对象在窗口中的位置坐标,将第一网元对象的大小信息乘以预设放大倍数,以放大第一网元对象,并在窗口中调整后的位置坐标处重新显示放大后的第一网元对象。本发明技术方案通过调整网元对象的显示位置并对其进行放大,使得用户能够快速从窗口中识别网元对象。

Description

处理 3D拓朴视图中网元对象信息的方法及设备
技术领域
本发明涉及网络管理技术, 尤其涉及一种处理 3D拓朴视图中网元对 象信息的方法及设备。 背景技术
在电信运维中, 拓朴视图是运营商进行运维的有效工具, 能够帮助运维 人员形象展现网络设备(即网元对象) 的组网。
随着移动业务量不断增加, 管理网元对象的数量猛增, 网络结构也越来 越复杂。 为了便于对网元对象进行管理, 在数据模型层按照区域等维度创建 子网, 同一区域内所有类型的网元对象都放入所对应的子网中。 在拓朴视图 层, 将同一个子网内所有的网元对象在同一个平面内进行显示。
由于网元对象数量较多, 这种将一个子网内所有网元对象在同一个平面 呈现的方法, 不便于运维人员快速识别网元对象。 发明内容
本发明提供一种处理 3D拓朴视图中网元对象信息的方法及设备, 用 以一定程度上解决现有技术中运维人员通过拓朴视图无法快速识别网元 对象的问题。
本发明实施例一方面提供一种处理 3D拓朴视图中网元对象信息的方 法, 包括:
响应于用户选中窗口所显示的 3D拓朴视图中第一网元对象的操作, 向网管后台服务器发出第一指令, 所述第一指令包括所述第一网元对象的 标识和放大查看操作命令;
接收所述网管后台服务器发送的所述第一网元对象的位置坐标和大 小信息; 所述第一网元对象的大小信息包括所述第一网元对象的长度、 宽 度和高度; 所述第一网元对象的位置坐标和大小信息是所述网管后台服务 器根据所述放大查看操作命令和所述第一网元对象的标识, 从存储的网元 对象信息中获取的; 所述网元对象信息包括所述 3D拓朴视图中每个网元 对象的标识、 位置坐标和大小信息;
根据所述窗口的大小和所述第一网元对象的位置坐标调整所述第一 网元对象在所述窗口中的位置坐标, 将所述第一网元对象的大小信息乘以 预设放大倍数, 以放大所述第一网元对象, 并在所述窗口中调整后的位置坐 标处重新显示所述放大后的第一网元对象。
本发明实施例一方面提供一种网管前台客户端, 包括:
用户事件响应模块, 用于响应于用户选中窗口所显示的 3D拓朴视图 中第一网元对象的操作, 向网管后台服务器发出第一指令, 所述第一指令 包括所述第一网元对象的标识和放大查看操作命令;
信息接收模块, 用于接收所述网管后台服务器发送的所述第一网元对 象的位置坐标和大小信息; 所述第一网元对象的大小信息包括所述第一网 元对象的长度、 宽度和高度; 所述第一网元对象的位置坐标和大小信息是 所述网管后台服务器根据所述放大查看操作命令和所述第一网元对象的 标识, 从存储的网元对象信息中获取的; 所述网元对象信息所述 3D拓朴 视图中每个网元对象的标识、 位置坐标和大小信息;
拓朴显示模块, 用于根据所述窗口的大小和所述第一网元对象的位置 坐标调整所述第一网元对象在所述窗口中的位置坐标, 将所述第一网元对 象的大小信息乘以预设放大倍数, 以放大所述第一网元对象, 并在所述窗 口中调整后的位置坐标处重新显示所述放大后的第一网元对象。
本发明实施例另一方面提供一种处理 3D拓朴视图中网元对象信息的 方法, 包括:
接收网管前台客户端发送的第一指令; 所述第一指令是所述网管前台 客户端响应于用户选中窗口所显示的 3D拓朴视图中第一网元对象的操作 而生成的, 所述第一指令包括所述第一网元对象的标识和放大查看操作命 令;
根据所述放大查看操作命令和所述第一网元对象的标识, 从存储的网 元对象信息中获取所述第一网元对象的位置坐标和大小信息; 其中, 所述 第一网元对象的大小信息包括所述第一网元对象的长度、 宽度和高度; 所 述网元对象信息包括所述 3D拓朴视图中每个网元对象的标识、 位置坐标 和大小信息;
向所述网管前台客户端传递所述第一网元对象的位置坐标和大小信 息, 以使所述网管前台客户端在所述窗口中调整后的位置坐标处重新显示放 的第一网元对象。
本发明实施例另一方面提供一种网管后台服务器, 包括:
指令接收模块, 用于接收网管前台客户端发送的第一指令; 所述第一 指令是所述网管前台客户端响应于用户选中窗口所显示的 3D拓朴视图中 第一网元对象的操作而生成的, 所述第一指令包括所述第一网元对象的标 识和放大查看操作命令;
信息获取模块, 用于根据所述放大查看操作命令和所述第一网元对象 的标识, 从存储的网元对象信息中获取所述第一网元对象的位置坐标和大 小信息; 其中, 所述第一网元对象的大小信息包括所述第一网元对象的长 度、 宽度和高度; 所述网元对象信息包括所述 3D拓朴视图中每个网元对 象的标识、 位置坐标和大小信息;
信息传递模块, 用于向所述网管前台客户端传递所述第一网元对象的 位置坐标和大小信息, 以使所述网管前台客户端在所述窗口中调整后的位置坐 标处重新显示放^ ^的第一网元对象。
本发明实施例又一方面提供一种网络管理系统, 包括: 网管前台客户 端和网管后台服务器, 其中:
所述网管前台客户端用于响应于用户选中窗口所显示的 3D拓朴视图 中第一网元对象的操作, 向所述网管后台服务器发送第一指令, 所述第一 指令包括所述第一网元对象的标识和放大查看操作命令;
所述网管后台服务器用于根据所述放大查看操作命令和所述第一网 元对象的标识, 从存储的网元对象信息中获取所述第一网元对象的位置坐 标和大小信息, 并向所述网管前台客户端传递所述第一网元对象的位置坐 标和大小信息; 其中, 所述网元对象信息包括所述 3D拓朴视图中每个网 元对象的标识、 位置坐标和大小信息;
所述网管前台客户端还用于根据所述窗口的大小和所述第一网元对 象的位置坐标调整所述第一网元对象在所述窗口中的位置坐标, 将所述第 一网元对象的大小信息乘以预设放大倍数, 以放大所述第一网元对象, 并 在所述窗口中调整后的位置坐标处重新显示所述放大后的第一网元对象。
本发明实施例一方面提供的处理 3D拓朴视图中网元对象信息的方法 及网管前台客户端, 通过响应用户选中窗口中所显示的 3D拓朴视图中的 网元对象的操作, 向网管后台服务器发送指令使网管后台服务器根据该指 令中的被选中网元的标识和放大查看操作命令, 获取被选中的网元对象的 坐标位置和大小信息, 并提供给网管前台客户端, 网管前台客户端重新调 整被选中网元对象在窗口中的显示位置, 并将被选中网元对象进行放大, 从而实现被选中网元对象在窗口移动显示位置并放大的显示效果, 使得运 维人员从可以从窗口中快速识别出被选中的网元对象, 解决了现有技术中 同一子网中所有网元对象在同一平面中显示时, 运维人员无法快速识别网 元对象的问题。
本发明实施例另一方面提供的处理 3D拓朴视图中网元对象信息的方 法及网管后台服务器, 通过与网管前台客户端相配合, 根据网管前台客户 端的第一指令获取被选中网元对象的位置坐标和大小信息, 并提供给网管 前台客户端, 为网管前台客户端重新调整被选中网元对象在窗口中的显示 位置, 并将被选中网元对象进行放大, 从而实现被选中网元对象在窗口移 动显示位置并放大的显示效果, 使得运维人员从可以从窗口中快速识别出 被选中的网元对象提供了条件。
本发明实施例又一方面提供的网络管理系统, 网管后台服务器与网管 前台客户端相互配合, 网管前台客户端响应用户选中网元对象的操作, 并 向网管后台服务器发送第一指令, 网管后台服务器根据第一指令获取被选 中网元对象的位置坐标和大小信息, 并提供给网管前台客户端, 网管前台 客户端根据被选中网元对象的坐标位置和大小信息重新调整被选中网元 对象在窗口中的显示位置, 并将被选中网元对象进行放大, 从而实现被选 中网元对象在窗口移动显示位置并放大的显示效果, 使得运维人员从可以 从窗口中快速识别出被选中的网元对象, 解决了现有技术中同一子网中所 有网元对象在同一平面中显示时, 运维人员无法快速识别网元对象的问 题。 附图说明
实施例或现有技术描述中所需要使用的附图作一简单地介绍, 显而易见 地, 下面描述中的附图是本发明的一些实施例, 对于本领域普通技术人员 来讲, 在不付出创造性劳动性的前提下, 还可以根据这些附图获得其他的 附图。
图 1A为本发明实施例一提供的处理 3D拓朴视图中网元对象信息的 方法流程图;
图 1B为本发明实施例一提供的在窗口中显示的网元对象的结构示意 图;
图 1C为本发明实施例一提供的窗口的一种显示状态;
图 1D为本发明实施例一提供的窗口的另一种显示状态;
图 2为本发明实施例二提供的处理 3D拓朴视图中网元对象信息的方 法流程图;
图 3为本发明实施例三提供的处理 3D拓朴视图中网元对象信息的方 法流程图;
图 4为本发明实施例四提供的处理 3D拓朴视图中网元对象信息的方 法流程图;
图 5为本发明实施例五提供的处理 3D拓朴视图中网元对象信息的方 法流程图;
图 6为本发明实施例六提供的处理 3D拓朴视图中网元对象信息的方 法流程图;
图 7为本发明实施例七提供的处理 3D拓朴视图中网元对象信息的方 法流程图;
图 8为本发明实施例八提供的处理 3D拓朴视图中网元对象信息的方 法流程图;
图 9为本发明实施例九提供的网管前台客户端的结构示意图; 图 10为本发明实施例十提供的网管后台服务器的结构示意图; 图 11为本发明实施例十一提供的网络管理系统的结构示意图。 具体实施方式 为使本发明实施例的目的、 技术方案和优点更加清楚, 下面将结合本 发明实施例中的附图, 对本发明实施例中的技术方案进行清楚、 完整地描 述,显然, 所描述的实施例是本发明一部分实施例, 而不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有作出创造性劳动前提 下所获得的所有其他实施例, 都属于本发明保护的范围。
图 1A为本发明实施例一提供的处理 3D拓朴视图中网元对象信息的 方法流程图。 如图 1A所示, 本实施例的方法包括:
步骤 101、 响应于用户选中窗口所显示的 3D拓朴视图中第一网元对 象的操作, 向网管后台服务器发出第一指令。
其中, 第一指令包括第一网元对象的标识和放大查看操作命令。
需要解释的是, 本发明实施例的网元对象表示窗口上所显示的网元, 例如可以是图标等等。 本发明实施例的连接对象表示窗口上所显示的网元 和网元之间的连接关系, 例如可以是连线以及连线两端的网元等等。
本实施例的执行主体是网络管理系统中的网管前台客户端, 其可以是 各种具有较强计算能力、 支持拓朴视图显示的设备, 例如个人计算机, 智 能移动终端, 平板电脑等。
在本实施例中, 网络管理系统中的网管后台服务器上或者与网管后台 服务器具有通信连接的存储系统(比如存储阵列或数据库)上已经预先存 储了各网元对象的有关信息, 例如各网元对象的名称、 标识、 位置坐标、 大小信息、 显示的颜色、 已经存在的连接关系等。 其中, 拓朴视图是一种 三维视图, 故在本实施例中, 各网元对象的位置坐标可以用网元对象各个 顶点的三维坐标 (X , y , z ) 来表示, 如图 1B所示。 其中, 图 1B中的立 方体表示一个网元对象。 另外, 每个网元对象都有其大小, 可以用长度、 宽度、 高度即 (a, b, c ) 来表示。
可选的, 可以将网元对象的上述信息分为两类, 一类是网元对象的信 息, 一类是连接对象的信息。 一个网元对象的信息主要包括: 该网元对象 的标识、 显示状态、 位置坐标 (X , y, z ) 和大小信息 (a, b, c ) 等。 其 中, 网元对象的显示状态包括该网元对象当前已经显示在窗口中和未显示 在窗口中两种情况。 本发明各实施例将整个 3D拓朴视图中所有网元对象 的信息称为网元对象信息, 即网元对象信息包括 3D拓朴视图中每个网元 对象的标识、 显示状态、 位置坐标和大小信息等。 两个相互连接的网元对 象之间的连接关系称为一个连接对象, 这两个网元对象分别为该连接对象 的两端的网元对象。 其中, 每个连接对象的信息主要包括其两端网元对象 的标识。 另外, 每个连接对象的信息还可以包括两端网元对象之间的连接 距离、 连接角度等信息。 本发明各实施例将整个 3D拓朴视图中所有连接 对象的信息称为连接对象信息, 即连接对象信息包括 3D拓朴视图中每个 连接两端的网元对象的标识、 两端网元对象之间的连接距离、 连接角度等 信息。
与现有技术相类似, 本实施例的网管前台客户端也会按照区域将网络 中所有网元对象进行子网划分, 并将同一子网中所有网元对象在同一平面 上显示。 在本实施例中所述平面是指窗口。
另外, 本实施例的网管前台客户端主要面向用户, 用于响应用户对窗 口中所显示的 3D拓朴视图中的各网元对象的操作。 例如, 本实施例的网 管前台客户端主要为其窗口上显示的 3D拓朴视图中各网元对象提供了选 中网元对象、 查看网元对象的连接关系、 创建 SDH路径等功能。 当用户 需要查看或识别某个网元对象时, 可以通过鼠标或触摸方式单击该网元对 象, 或者通过鼠标右键选择选中网元对象的功能操作, 来发出选中窗口中 某个网元对象的操作。 而本实施例的网管前台客户端能够响应用户选中网 元对象的操作, 并会识别出用户选中的是哪个网元对象。 举例说明, 用户 通过鼠标点击网元对象, 网管前台客户端会从该点击操作中识别出用于要 选中该网元对象, 并会获知该选中的网元对象的标识等信息。
在本实施例中, 网管前台客户端响应用户选中网元对象的操作后, 会 生成一指令, 并在该指令中携带用户选中的网元对象的标识和放大查看操 作命令, 然后将该指令发送给网管后台服务器, 这样就可以使网管后台服 务器根据放大查看操作命令和用户选中的网元对象的标识, 从预先存储的 网元对象信息中获取对用户选中的网元对象进行放大查看所需的信息并 返回给网管前台客户端, 以便于对用户选中的网元对象进行放大查看处 理。 其中, 对用户选中的网元对象进行放大查看所需的信息主要包括用户 选中的网元对象的位置坐标和大小信息。
在本实施例中, 以用户选中网管前台客户端的窗口中所显示的 3D拓 朴视图中的第一网元对象, 并发送给网管后台服务器的指令为第一指令为 例进行说明, 但对任何一个网元对象的选中操作的处理均与对第一网元对 象的处理相同, 不再——赘述。
其中, 用户可以通过各种网管前台客户端可以识别的操作选中第一网 元对象, 例如在第一网元对象上点击鼠标, 或者通过在第一网元对象上点 击鼠标右键, 并选择其中选中网元对象的选项等。 网管前台客户端响应用 户选中第一网元对象的操作, 并生成第一指令, 然后将第一指令发送给网 管后台服务器。 其中, 第一指令中包括第一网元对象的标识和放大查看操 作命令。
对于网管后台服务器来说, 在接收到第一指令后, 会对第一指令进行 解析, 从中获取第一网元对象的标识和放大查看操作命令。 然后, 网管后 台服务器根据放大查看操作命令和第一网元对象的标识从预先存储的网 元对象信息中获取第一网元对象的位置坐标和大小信息, 并将第一网元对 象的位置坐标和大小信息传递给网管前台客户端。
进一步, 网元对象信息还可以包括 3D拓朴视图中每个网元对象的显 示状态。
可选的, 网关后台服务器可以根据放大查看操作命令和网元对象信息 中每个网元对象的显示状态, 从网元对象信息中获取网管前台客户端的窗 口中当前显示的各网元对象的位置坐标和大小信息。 其中, 第一网元对象 正显示在窗口中, 故属于窗口中当前显示的各网元对象中的一员, 即窗口 中当前显示的各网元对象中包括第一网元对象。 此时, 网管后台服务器可 以进一步根据第一网元对象的标识信息, 从获取的窗口中当前显示的各网 元对象的位置坐标和大小信息中, 获取第一网元对象的位置坐标和大小信 可选的, 网关后台服务器在向网管前台客户端传递第一网元对象的位 置坐标和大小信息的同时, 可以将窗口中当前显示的其他网元对象的位置 坐标和大小信息也一同传递给网管前台客户端。 可选的, 网管后台服务器还可以将获取的窗口中当前显示的各网元对 象的位置坐标和大小信息同时发送给网管前台客户端, 而不用单独从中获 取第一网元对象的位置坐标和大小信息。
步骤 102、 接收网管后台服务器发送的第一网元对象的位置坐标和大 小信息。
其中, 第一网元对象的大小信息包括第一网元对象的长度、 宽度和高 度。 第一网元对象的位置坐标和大小信息是网管后台服务器根据放大查看 操作命令和第一网元对象的标识, 从存储的网元对象信息中获取的, 然后 返回给网管前台客户端的。
其中, 网元对象信息包括 3D拓朴视图中每个网元对象的标识、 位置 坐标和大小信息。 也正是基于此, 网管后台服务器才可以根据第一网元对 象的标识, 获取到第一网元对象的位置坐标和大小信息。
对于网管前台客户端来说, 在向网管后台服务器发送第一指令之后, 会接收网管后台服务器返回的第一网元对象的位置坐标和大小信息。
可选的, 如果网管后台服务器传递给网管前台客户端的是其所获取的 窗口中当前显示的各网元对象的位置坐标和大小信息, 则网管前台客户端 会接收到窗口中当前显示的各网元对象(包括第一网元对象)的位置坐标 和大小信息。
步骤 103、 根据窗口的大小和第一网元对象的位置坐标调整第一网元 对象在窗口中的位置坐标, 将第一网元对象的大小信息乘以预设放大倍 数, 以放大第一网元对象, 并在窗口中调整后的位置坐标处重新显示放大后 的第一网元对象。
具体的, 本实施例的网管前台客户端在获取第一网元对象的位置坐标 之后, 可以根据窗口的大小和第一网元对象当前在窗口中的显示位置重新 计算第一网元对象的位置坐标, 这样可以调整第一网元对象在窗口中的显 示位置。
进一步, 为了便于用户能够更快速的识别出第一网元对象, 本实施例 的网管前台客户端还可以将第一网元对象的大小信息乘以预设放大倍数, 从而将第一网元对象放大。 其中, 放大倍数是预先设定的, 例如可以设置 为放大 2倍, 但不限于此。 在调整第一网元对象在窗口中的显示位置和对第一网元对象进行放 大后, 网管前台客户端重新在窗口中调整到的位置上显示经过放大的第一 网元对象。
在本实施例中, 当用户需要查看或识别某个网元对象时, 只需要发出 选中该网元对象的操作即可, 网管前台客户端会响应用户选中网元对象的 操作并会通过向网管后台服务器发出指令, 从网管后台服务器获取该网元 对象的位置坐标和大小信息, 进而基于获取的信息和窗口的大小完成对该 网元对象的显示位置的调整和对该网元对象的放大, 使得该网元对象在窗 口中能够被突出显示, 进而使得用户能够快速从窗口中众多网元对象中识
Figure imgf000012_0001
可选的, 如果网管前台客户端接收到的是网管后台服务器传递的窗口 中当前显示的各网元对象的位置坐标和大小信息, 则网管前台客户端窗口 的大小和第一网元对象的位置坐标调整第一网元对象在窗口中的显示位 置,将第一网元对象的大小信息乘以预设放大倍数,以放大第一网元对象, 并在窗口中重新显示第一网元对象的具体实现方式可以为:
网管前台客户端根据窗口中当前显示的各网元对象的位置坐标, 计算 窗口中当前显示的各网元对象中除第一网元对象之外其他网元对象与第 一网元对象之间的距离。 以第一网元对象的位置坐标为 (xa, ya, za ) , 其 他网元对象中某个网元对象的位置坐标为 (xb , yb, zb ) 为例, 则该某网 元对象和第一网元对象之间的距离为 D= V(xa-xb)2+ (ya-yb)2+ (za- zb)2)。本实 施例通过图 1C给出了当前窗口的一种显示状态, 其中带有阴影的立方体 为第一网元对象。 其他立方体或多面体所示网元对象和第一网元对象之间 的位置关系以及距离如图 1C所示。
然后, 网管前台客户端重新计算第一网元对象的位置坐标为窗口的中 心位置对应的坐标, 并分别将第一网元对象的大小信息中的长度、 宽度和 高度乘以放大倍数。 这样可以调整第一网元对象的显示位置为窗口的中心 位置,更有利于用户识别出第一网元对象。而通过将第一网元对象的长度、 宽度、 高度分别乘以放大倍数一方面可以保证第一网元对象不变形, 另一 方面可以将第一网元对象放大的更大。 例如, 如果放大倍数为 2, 则长度、 宽度、 高度分别乘以 2之后, 第一网元对象就会被放大 8倍, 有利于用户 识别出第一网元对象。
接着, 网管前台客户端根据窗口中当前显示的各网元对象中除第一网 元对象之外其他网元对象与第一网元对象之间的距离和重新计算出的第 —网元对象的位置坐标, 重新计算窗口中当前显示的各网元对象中除第一 网元对象之外其他网元对象的位置坐标。 在该过程中, 窗口中其他网元对 象的大小信息也保持不变。 这样可以保证窗口中其他网元对象和第一网元 对象之间的距离不变, 可以尽量保持其他网元对象的真实度。
最后, 网管前台客户端根据重新计算出的窗口中当前显示的各网元对 象(包括第一网元对象) 的位置坐标、 第一网元对象放大后的大小信息和 接收的窗口中当前显示的各网元对象中除第一网元对象之外其他网元对 象的大小信息, 重新在窗口中显示窗口中当前显示的各网元对象。
经上述处理后, 图 1C所示窗口中的显示状态变为图 1D所示。 将图 1C和图 1D相比可见,第一网元对象被放大显示在窗口的中间位置。其中, 其他网元对象与第一网元对象的位置关系如图 1D所示,不再做详细说明。
在上述实施方式中, 网管前台客户端通过调整第一网元对象的位置坐 标并将第一网元对象放大来突出显示第一网元对象, 不仅解决了现有技术 中同一子网中所有网元对象在同一平面中显示时, 用户无法快速识别网元 对象的问题, 而且通过保证其他网元对象和第一网元对象之间的距离以及 其他网元对象的大小不变, 尽量保证了重新显示出的拓朴的真实性。
图 2为本发明实施例二提供的处理 3D拓朴视图中网元对象信息的方 法流程图。 如图 2所示, 本实施例的方法包括:
步骤 201、 响应于用户查看窗口所显示的 3D拓朴视图中第二网元对 象的连接关系的操作, 向网管后台服务器发出第二指令。
其中, 第二指令包括第二网元对象的标识和连接关系查看操作命令。 第二网元对象的连接关系包括第二网元对象和所有第三网元对象, 第三网 元对象为与第二网元对象连接的网元对象。 。
在本实施例中, 网元对象的连接关系主要包括该网元对象以及与该网 元对象连接的其他网元对象。 更为具体的来说, 网元对象的连接关系主要 包括该网元对象的标识, 与该网元对象连接的其他网元对象的标识, 以及 该网元对象与其他网元对象相连的连接信息等。 本实施例以第二网元对象 为例进行说明, 则第二网元对象的连接关系主要包括第二网元对象和所有 与第二网元对象连接的网元对象。 在本实施例中, 为了简化描述, 将与第 二网元对象连接的网元对象称为第三网元对象。 另外, 每个第三网元对象 和第二网元对象之间的连接本身也属于连接关系中的一种信息。
本实施例的执行主体也是网管前台客户端, 并且网管前台客户端与网 管后台服务器相互配合。
与现有技术相类似, 本实施例的网管前台客户端也按照区域将网络中 所有网元对象进行子网划分, 并将同一子网中所有网元对象在同一平面上 显示。 在本实施例中, 将同一平面称为窗口。
其中, 在本实施例中, 网管后台服务器上也预先存储了网元对象信息 和连接对象信息。 关于网元对象信息和连接对象信息的描述可参见步骤 101 , 在此不再赘述。
另外, 本实施例的网管前台客户端也为其窗口上显示的各网元对象提 供了选中网元对象、 查看网元对象的连接关系、 创建 SDH路径等功能。 其中, 当用户需要查看某个网元对象的连接关系时, 可以通过鼠标右键选 择查看网元对象的连接关系的功能选项发出查看网元对象的连接关系的 操作, 但发出查看网元对象的连接关系的操作的方式不限于此。 而本实施 例的网管前台客户端会响应用户查看网元对象的连接关系的操作, 并会获 取用户想要查看连接关系的网元对象的标识等, 然后生成指令, 并在指令 中携带用户想要查看连接关系的网元对象的标识和连接关系查看操作命 令, 然后发送给网管后台服务器, 这样可以使网管后台服务器根据网元对 象的标识和连接关系查看操作命令获取查看连接关系所需的信息并传递 给网管前台客户端。
其中, 查看连接关系所需的信息主要包括与想要查看连接关系的网元 对象连接的各网元对象, 以及他们之间的连接。
在本实施例中, 以查看窗口所显示的 3D拓朴视图中的第二网元对象 的连接关系, 并以发送给网管后台服务器的指令为第二指令为例进行说 明, 但对于查看任何一个网元对象的连接关系的操作均与第二网元对象相 同, 不再——赘述。 其中, 用户可以通过选择查看第二网元对象的连接关系的选项发出查 看第二网元对象的连接关系的操作。 本实施例的网管前台客户端会响应用 户查看第二网元对象的连接关系的操作, 并会获取第二网元对象的标识, 然后生成第二指令, 将第二指令发送给网管后台服务器。 其中, 第二指令 中包括第二网元对象的标识和连接关系查看操作命令。
对于网管后台服务器来说, 在接收到第二指令之后, 会对第二指令进 行解析, 从中获取第二网元对象的标识和连接关系查看操作命令。 然后, 网管后台服务器根据连接关系查看操作命令和第二网元对象的标识识别 出用户需要查看第二网元对象的连接关系, 然后根据第二网元对象的标识 查询预先存储的连接对象信息, 从中获取所有与第二网元对象连接的第三 网元对象的标识。 接着, 网管后台服务器根据第二网元对象的标识和每个 第三网元对象的标识查询预先存储的网元对象信息, 从中获取第二网元对 象的位置坐标和每个第三网元对象的位置坐标。 在此说明, 网管后台服务 器除了可以获取第二网元对象的和每个第三网元对象的位置坐标之外, 还 可以获取第二网元对象的和每个第三网元对象的其他信息, 例如大小信 息、 显示状态等。 在本实施例中, 重点需要位置坐标信息, 故以获取第二 网元对象的和每个第三网元对象的位置坐标为例。 然后, 网管后台服务器 将获取的第二网元对象的位置坐标和每个第三网元对象的位置坐标传递 给网管前台客户端。
在此说明, 第二指令包括的连接关系查看操作命令与第一指令包括的 放大查看操作命令的标识不同, 用于标识不同的命令和不同的处理方式。
步骤 202、 接收网管后台服务器发送的第二网元对象的位置坐标和每 个第三网元对象的位置坐标。
其中, 第二网元对象的位置坐标是网管后台服务器根据第二网元对象 的标识, 从网元对象信息中获取的。 第三网元对象的位置坐标是网管网管 后台服务器根据连接关系查看操作命令和第二网元对象的标识, 从预先存 储的连接对象信息中获取第三网元对象的标识, 然后根据第三网元对象的 标识从网元对象信息中获取的。
其中, 连接对象信息包括: 3D 拓朴视图中每个连接两端的网元对象 的标识。 也正是基于此, 网管后台服务器才可以根据第二网元对象的标识 获取到所有第三网元对象的标识。
对于网管前台客户端来说, 在向网管后台服务器发送第二指令后, 会 接收网管后台服务器返回的第二网元对象的位置坐标和每个第三网元对 象的位置坐标。
步骤 203、 根据窗口的大小、 第二网元对象的位置坐标和每个第三网 元对象的位置坐标, 重新计算每个第三网元对象的位置坐标, 以使每个第 三网元对象均能显示在窗口中。
在获取到每个第三网元对象的位置坐标后, 为了使得所有第三网元对 象能够与第二网元对象同时显示在窗口中, 网管前台客户端根据窗口的大 小重新计算各个第三网元对象的位置坐标。 其中, 处理设备重新计算第三 网元对象的位置坐标的依据是当该第三网元对象以重新计算出的位置坐 标进行显示时能够显示在窗口中, 而所使用的计算方式不做限定。
步骤 204、 根据重新计算出的每个第三网元对象的位置坐标和第二网 元的位置坐标, 在窗口中显示第二网元对象和每个第三网元对象。
当重新计算出各个第三网元对象的位置坐标后, 网管前台客户端根据 重新计算出的各第三网元对象的位置坐标以及第二网元对象的位置坐标, 在窗口中同时显示第二网元对象和各个第三网元对象, 即将第二网元对象 和与其连接的各个网元对象同时显示出来。
在本实施例中, 当用户需要查看某个网元对象的连接关系时, 只需发 出查看网元对象的连接关系的操作即可, 而网管前台客户端会响应用户查 看网元对象的连接关系的操作, 并会生成第二指令, 将第二指令发送给网 管后台服务器, 从网管后台服务器获取该网元对象和与其连接的网元对象 的位置坐标, 并根据窗口的大小重新计算其他网元对象的位置坐标, 使得 该网元对象和与其连接的其他网元对象都能够显示在窗口中, 使得用户能 够快速、 清晰的查看到某个网元对象的连接, 由于不受子网的限制, 从而 解决了现有技术中不同子网中具有连接关系的网元对象不可见的问题。
进一步, 本实施例的网管前台客户端还可以根据第三网元对象的位置 坐标判断第三网元对象是否显示在窗口中, 即判断第三网元对象的位置坐 标是否在窗口范围内。 其中, 如果判断结果为否, 网管前台客户端再执行 根据窗口的大小、 第二网元对象的位置坐标和每个第三网元对象的位置坐 标, 重新计算每个第三网元对象的位置坐标, 以使每个第三网元对象均能 显示在窗口中的操作。 优选的, 如果判断结果为是, 网管前台客户端可以 不用重新计算该第三网元对象的位置坐标, 但不限于此。 例如, 即使第三 网元对象已经显示在窗口中, 网管前台客户端也可以重新计算该第三网元 对象的位置坐标。
其中, 网管前台客户端通过判断第三网元对象的位置坐标是否已经在 窗口范围内, 并且只有在判断结果为否时才重新计算第三网元对象的位置 坐标, 可以降低处理设备的负担, 有利于提高运维人员或用户查看到第二 网元对象的连接关系的效率。
本实施例提供一种网管前台客户端根据窗口的大小、 第二网元对象的 位置坐标和每个第三网元对象的位置坐标, 重新计算每个第三网元对象的 位置坐标, 以使每个第三网元对象均能显示在窗口中, 即步骤 203的实施 方式。 该实施方式包括: 网管前台客户端根据第二网元对象的位置坐标和 第三网元对象的位置坐标, 计算第二网元对象和第三网元对象之间的距 离。 然后, 网管前台客户端根据窗口的大小, 缩短第二网元对象和第三网 元对象之间的距离, 直到第三网元对象在窗口中为止。 接着, 网管前台客 户端根据第二网元对象和第三网元对象之间的距离的缩短倍数, 重新计算 第三网元对象的位置坐标。 其中, 第二网元对象和第三网元对象之间的距 离的缩短倍数可由缩短前的距离与缩短后的距离相比得到。
举例说明, 网管前台客户端可以根据第二网元对象的和第三网元对象 的位置坐标计算出各坐标的差值, 然后将计算出的各坐标的差值缩小所述 距离的缩短倍数, 然后用第二网元对象的位置坐标分别加上缩小后的坐标 差值得到第三网元对象的新的位置坐标。 另外, 网管前台客户端还可以仅 用第二网元对象的位置坐标中表征水平距离的坐标值减去缩小后的相应 坐标差值, 以实现将第二网元对象和第三网元对象拉近的目的。 其中, 表 征各个网元对象之间的水平距离的坐标值可以是 X坐标值、 y坐标值或 z 坐标值。 以图 1B所示为例, 则网管前台客户端可以通过减小第二网元对 象和第三网元对象的 z坐标值来拉近第二网元对象与第三网元对象之间的 距离。
进一步说明, 由于本实施例不再限制所显示的具有连接关系的各网元 对象是否属于同一子网, 故当第三网元对象和第二网元对象属于不同的子 网时, 可以显示第三网元对象所属子网的信息。 其中, 如果第二网元对象 和第三网元对象属于不同的子网, 网管后台服务器可以根据获取的第三网 元对象的标识, 进一步从预先存储的各网元对象的信息中获取该第三网元 对象所属子网的信息并向网管前台客户端传递第三网元对象所属子网的 信息。 网管前台客户端接收到第三网元对象所属子网的信息后, 显示第三 网元对象所属子网的信息。 其中, 每个网元对象所属子网的信息作为该网 元对象的信息的一部分也预先存储在网管后台服务器上。 本实施例通过显 示与第二网元对象属于不同子网的第三网元对象的所属子网的信息, 为在 同一窗口中同时显示跨子网的网元对象提供了辅助信息, 有利于便于用户 更加清楚各网元对象之间的连接关系, 为用户判断建立出的同步数字体系 ( Synchronous Digital Hierarchy, SDH )路径是否合理提供了条件。
进一步, 本实施例提供一种网管前台客户端根据重新计算出的每个第 三网元对象的位置坐标和第二网元的位置坐标, 在窗口中显示第二网元对 象和每个第三网元对象, 即步骤 204的实施方式。 该实施方式包括: 网管 前台客户端根据重新计算出的每个第三网元对象的位置坐标, 在窗口中显 示每个第三网元对象, 根据第二网元的位置坐标, 在窗口中显示第二网元 对象, 并改变第二网元对象和每个第三网元对象之间连线的颜色, 以使第 二网元对象和每个第三网元对象之间连线的颜色不同于窗口中其他连线 的颜色。 举例说明, 网管前台客户端可以统一使用黄色显示各个网元对象 以及网元对象之间的连线, 当用户选择查看第二网元对象的连接关系时, 网管前台客户端可以改变第二网元对象和各第三网元对象之间的连线的 颜色为与黄色反差较大的颜色, 例如绿色、 红色等, 以突出显示第二网元 对象的连接关系, 以便于用户清楚的查看到第二网元对象的连接关系。
本实施方式不仅显示第二网元对象和各第三网元对象, 同时通过设置 第二网元对象和各第三网元对象之间的连线的颜色不同于其他连线的颜 色, 实现高亮显示的目的, 可以进一步提高用户获知第二网元对象的连接 关系的便利性。
在本实施例中, 网管前台客户端响应用户查看网元对象的连接关系的 操作并向网管后台服务器发送指令, 从而获取该网元对象和其所连接的各 网元对象的位置坐标, 通过将该网元对象的连接关系同时显示在窗口中并 通过连接关系中的连线进行高亮显示, 使得运维人员或用户能够清楚的查 看到各网元对象之间的连接关系, 便于基于各网元对象之间的连接关系进 行故障发现、 故障排查等操作, 有利于提高故障发现、 故障排查的效率。 另外, 本实施例还可以使跨子网的网元对象在同一窗口中显示, 为运维人 员或用户准确判断建立出的 SDH路径是否合理提供了条件。
图 3为本发明实施例三提供的处理 3D拓朴视图中网元对象信息的方 法流程图。 如图 3所示, 本实施例的方法包括:
步骤 301、 响应于用户创建 SDH路径的操作, 向网管后台服务器发出 第三指令。
其中, 第三指令包括源端网元对象信息、 宿端网元对象信息和指定信 息; 所述指定信息包括所创建的 SDH路径应经过的网元对象的信息和 /或 不能经过的网元对象的信息。
本实施例的执行主体也是网管前台客户端, 并且网管前台客户端与网 管后台服务器相配合。
在本实施例中, 网管前台客户端向用户提供了创建 SDH路径的功能。 例如, 当用户需要创建 SDH路径时, 可以通过鼠标右键选择创建 SDH路 径的功能发出创建 SDH路径的操作。 此时, 本实施例的网管前台客户端 会响应用户创建 SDH路径的操作, 并可以通过但不限于交互的方式, 要 求用户提供创建 SDH路径所需的源端网元对象信息、 宿端网元对象信息 和所需要的指定信息。 例如, 网管前台客户端可以弹出一个消息窗口, 用 户通过消息窗口输入源端网元对象信息、 宿端网元对象信息和所需要的指 定信息, 并通过点击消息窗口上的提交或确认按鈕提供给本实施例的网管 前台客户端。
其中, 由于每个网元对象通常会包括多个端口, 不同网元对象之间建 立 SDH业务时的连接实际上是两个网元对象之间的端口之间的连接。 故 本实施例的源端网元对象信息主要包括源端网元对象的标识和其上用于 建立 SDH路径的端口。 相应的, 宿端网元对象信息主要包括宿端网元对 象的标识和其上用于建立 SDH路径的端口。 其中, 指定信息是可选的, 即可以包括指定信息也可以不包括指定信息。 通常, 建立 SDH路径时是 需要指定信息的。 指定信息可以包括建立 SDH路径时应经过的网元对象 的信息 (即该网元对象必须在所建立的 SDH路径上) , 其中所述信息也 主要是指网元对象的标识、 端口等。 指定信息还可以包括建立 SDH路径 时不能经过的网元对象的信息 (即该网元对象不能在所建立的 SDH路径 上) , 所述信息也主要是指网元对象的标识、 端口等。 再者, 指定信息还 可以同时包括建立 SDH路径时必须经过的网元对象的信息和不能经过的 网元对象的信息。
另外, SDH 路径经过的每个网元对象的端口是需要一定数量的资源 的, 故网管前台客户端可以通过资源数量门限来判断 SDH路径是否有资 源告警。 其中, 资源数量门限可以由用户输入, 也可以预先设置在网管前 台客户端上。 该资源数量门限用于在判断计算出的 SDH路径是否有资源 告警时使用。 其中, 所述资源主要是指带宽资源。 例如, 资源数量门限可 以设置为 5个 VC12, 但不限于此。 如果可用资源数量小于 5个 VC12, 则 不满足资源要求。
为便于描述和与其他指令相区别, 在本实施例中, 以创建 SDH路径 的指令为第三指令为例进行说明。
当用户发出创建 SDH路径的操作并提供所需信息后, 本实施例的网 管前台客户端会生成第三指令并将第三指令发送给网管后台服务器。
对于网管后台服务器来说, 在接收到第三指令后, 会对第三指令进行 解析, 从中获取源端网元对象信息、 宿端网元对象信息、 资源数量门限和 指定信息等, 并会识别出需要在源端网元对象和宿端网元对象之间建立 SDH业务关系, 即创建一条 SDH路径, 且所创建的 SDH路径必须满足指 定信息的要求。 然后, 网管后台服务器会根据源端网元对象的信息、 宿端 网元对象的信息和指定信息, 使用预先设定的路径计算方法计算出从源端 网元对象到宿端网元对象的 SDH路径。其中,将该 SDH路径称为第一 SDH 路径。 然后, 网管后台服务器会将第一 SDH路径的信息和第一 SDH路径 上各网元对象的可用资源信息传递给网管前台客户端。
其中, 路径计算方法预先存储在网管后台服务器上。 网管后台服务器 上预先存储的路径计算方法可以是一个, 也可以是多个。 当有多个路径计 算方法时, 网管后台服务器需要从多个路径计算方法中选择一个作为设定 的路径计算方法。 其中, 路径计算方法可以是最短路径计算方法, 但不限 于此。 优选的, 如果使用的是最短路径计算方法, 则网管后台服务器可以 根据源端网元对象的信息、 宿端网元对象的信息和指定信息, 使用路径计 算方法, 计算出从源端网元对象到宿端网元对象的最短 SDH路径, 即第 — SDH路径。 其中, 最短 SDH路径是指从源端网元对象到宿端网元对象 之间跳数最少的路径。 而且, 第一 SDH路径满足指定信息的要求。 其中, 如果指定信息包括的是应经过的网元对象的信息, 则第一 SDH路径一定 经过指定信息要求必须经过的网元对象的信息; 如果指定信息包括的是不 能经过的网元对象的信息, 则第一 SDH路径一定不经过指定信息要求不 能经过的网元对象。
其中, 网管后台服务器根据预先存储各网元对象的信息、 第三指令中 的信息以及所使用的路径计算方法, 计算出第一 SDH路径的过程与现有 技术相类似, 在此不再赘述。
步骤 302、接收网管后台服务器发送的第一 SDH路径的信息和所述第 一 SDH路径上各网元对象的可用资源信息, 并根据第一 SDH路径的信息 在窗口中显示第一 SDH路径。
其中, 第一 SDH路径是网管后台服务器根据源端网元对象的信息、 宿端网元对象的信息和指定信息, 使用预先设定的路径计算方法计算出的 从源端网元对象到宿端网元对象的 SDH路径。
对于网管前台客户端来说, 接收网管后台服务器发送的第一 SDH路 径的信息和第一 SDH路径上各网元对象的可用资源信息, 然后根据第一 SDH路径的信息在窗口中显示第一 SDH路径。 其中, 第一 SDH路径的信 息主要包括构成该第一 SDH路径的各网元对象的标识。
步骤 303、根据第一 SDH路径上各网元对象的可用资源信息和资源数 量门限, 判断第一 SDH路径是否有资源告警; 如果判断结果为是, 即第 一 SDH路径有资源告警, 执行步骤 304; 反之, 执行步骤 305。
其中, 第一 SDH路径上各网元对象的资源使用情况主要是指各网元 对象在第一 SDH路径上的端口上的剩余资源。 其中, 资源优选为带宽资 源。
具体的, 网管前台客户端将第一 SDH路径上各网元对象的端口的剩 余资源数量与资源数量门限进行比较, 如果比较结果为网元对象的端口的 剩余资源数量小于资源数量门限, 则说明该网元对象不满足第一 SDH路 径对资源的需求, 故需要发出资源告警; 反之, 如果所有网元对象的端口 的剩余资源数量都大于或等于资源数量门限, 则不需要发出资源告警。
步骤 304、 在窗口中显示与第一 SDH路径对应的路径告警信息。
步骤 305、 SDH路径创建操作完成。
在本实施例中, 网管前台客户端进一步根据第一 SDH路径上各网元 对象的端口的剩余资源数量, 例如剩余带宽资源等, 判断第一 SDH路径 是否有资源告警, 即判断第一 SDH路径上的各网元对象的端口的资源是 否满足开展 SDH业务的所需。
如果判断结果为是,说明基于第一 SDH路径可以成功开展 SDH业务, 保证了开展 SDH业务的成功率。 如果判断结果为否, 说明基于第一 SDH 路径可能无法成功开展 SDH业务, 本实施例的网管前台客户端通过其窗 口向用户显示与第一 SDH路径对应的路径告警信息, 以便于用户能够及 时调整第一 SDH路径, 为了成功开展 SDH业务提供条件。
图 4为本发明实施例四提供的处理 3D拓朴视图中网元对象信息的方 法流程图。 本实施例基于图 3所示实施例实现, 如图 4所示, 本实施例的 方法在步骤 304之后还包括:
步骤 306、 响应于用户修改第一 SDH路径的操作, 向网管后台服务器 发出第四指令。
其中, 第四指令包括修改第一 SDH路径的操作命令。
在本实施例中, 网管前台客户端可以将第一 SDH路径显示在屏幕上。 当网管前台客户端显示路径告警信息后, 用户可以直接向网管前台客户端 发出修改第一 SDH路径的操作。 例如, 可以通过在第一 SDH路径上某个 网元对象上右击鼠标选择修改第一 SDH路径的选项, 以向网管前台客户 端发出修改操作。
网管前台客户端响应用户的修改操作, 并生成第四指令, 将第四指令 发送给网管后台服务器, 以使网管后台服务器重新计算一条 SDH路径。
可选的, 当网管前台客户端显示路径告警信息后, 用户可以先通过向 网管前台客户端发出查看资源的操作, 查看第一 SDH路径上各网元对象 的端口的资源使用情况, 以进一步确定第一 SDH路径上是否存在资源不 足或不够充足的网元对象, 然后再向网管前台客户端发出修改操作, 以请 求重新计算从源端网元对象到宿端网元对象的 SDH路径。
步骤 307、 接收网管后台服务器发送的第二 SDH路径的信息和第二 SDH路径上各网元对象的可用资源信息, 并根据第二 SDH路径的信息在 窗口中显示第二 SDH路径。
其中, 第二 SDH路径是网管后台服务器根据修改第一 SDH路径的操 作命令,重新根据源端网元对象的信息、宿端网元对象的信息和指定信息, 使用设定的路径计算方法计算出的从源端网元对象到宿端网元对象的 SDH路径。 其中, 第二 SDH路径的信息主要包括构成该第二 SDH路径的 各网元对象的标识。
对网管后台服务器来说, 接收到第四指令后, 会解析第四指令, 从中 获取修改第一 SDH路径的操作命令, 识别出需要重新计算从源端网元对 象到宿端网元对象之间的 SDH路径。 然后, 网管后台服务器根据该命令, 结合预先存储的各网元对象的信息、 第四指令包括的信息以及所使用的路 径计算方法, 重新为源端网元对象和宿端网元对象计算出 SDH路径。
在本实施例中, 网管前台客户端在第一 SDH路径不满足开展 SDH业 务所需资源要求时, 通过显示路径告警信息, 使得用户发出修改操作, 并 通过响应用户的修改操作向网管后台服务器发出第四指令, 使网管后台服 务器重新计算一条 SDH路径, 基于新建立的 SDH路径开展 SDH业务, 提高了开展 SDH业务的成功率。
进一步, 当在两个网元对象之间建立 SDH业务或建立 SDH路径后, 网管后台服务器分别更新两个网元对象的资源利用情况和更新两个网元 端口之间的业务关系, 以便于更加全面的管理各网元对象的信息, 为基于 各网元对象的信息的拓朴视图更加准确。
在此说明, 上述各实施例中的第一网元对象、 第二网元对象和第三网 元对象可以是同一网元对象, 也可以是不同网元对象。
在此说明, 上述实施例分别描述了对选中查看网元对象、 查看被选中 网元对象的连接关系、 为被选中网元对象建立 SDH路径的操作, 这三种 操作可以独立执行。 图 5为本发明实施例五提供的处理 3D拓朴视图中网元对象信息的方 法的流程图。 如图 5所示, 本实施例的方法包括:
步骤 501、 接收网管前台客户端发送的第一指令。
其中, 第一指令是网管前台客户端响应于用户选中窗口所显示的 3D 拓朴视图中第一网元对象的操作而生成的。 第一指令包括第一网元对象的 标识和放大查看操作命令。
本实施例的执行主体为网管后台服务器。 网管后台服务器与网管前台 客户端相互配合。
其中, 网管前台客户端响应于用户选中窗口所显示的 3D拓朴视图中 第一网元对象的操作而向网管后台服务器发送第一指令的操作, 可参见图 1所示实施例的描述, 在此不再赘述。
对网管后台服务器来说, 会接收网管前台客户端发送的第一指令。 步骤 502、 根据放大查看操作命令和第一网元对象的标识, 从存储的 网元对象信息中获取第一网元对象的位置坐标和大小信息。
其中, 第一网元对象的大小信息包括第一网元对象的长度、 宽度和高 度。 网元对象信息包括 3D拓朴视图中每个网元对象的标识、 位置坐标和 大小信息。
在本实施例中, 网管后台服务器上已经预先存储了网元对象信息和连 接对象信息。 其中, 关于网元对象信息和连接对象信息的描述可参见图 1 所示实施例中的描述, 在此不再赘述。
步骤 503、 向网管前台客户端传递第一网元对象的位置坐标和大小信 息, 以使网管前台客户端在窗口中调整后的位置坐标处重新显示放 ^^的第一网 元对象。
具体的, 网管后台服务器在接收到第一指令后, 会对第一指令进行解 析, 从中获取第一网元对象的标识和放大查看操作命令。 然后, 网管后台 服务器根据放大查看操作命令和第一网元对象的标识从预先存储的网元 对象信息中获取第一网元对象的位置坐标和大小信息, 并将第一网元对象 的位置坐标和大小信息传递给网管前台客户端。
进一步, 网元对象信息还可以包括 3D拓朴视图中每个网元对象的显 示^犬态。 可选的, 网关后台服务器可以根据放大查看操作命令和网元对象信息 中每个网元对象的显示状态, 从网元对象信息中获取网管前台客户端的窗 口中当前显示的各网元对象的位置坐标和大小信息。 其中, 第一网元对象 正显示在窗口中, 故属于窗口中当前显示的各网元对象中的一员, 即窗口 中当前显示的各网元对象中包括第一网元对象。 此时, 网管后台服务器可 以进一步根据第一网元对象的标识信息, 从获取的窗口中当前显示的各网 元对象的位置坐标和大小信息中, 获取第一网元对象的位置坐标和大小信 可选的, 网关后台服务器在向网管前台客户端传递第一网元对象的位 置坐标和大小信息的同时, 可以将窗口中当前显示的其他网元对象的位置 坐标和大小信息也一同传递给网管前台客户端。
可选的, 网管后台服务器可以将获取的窗口中当前显示的各网元对象 的位置坐标和大小信息直接发送给网管前台客户端, 而不用从中单独获取 第一网元对象的位置坐标和大小信息。
其中, 网管前台客户端在窗口中调整后的位置坐标处重新显示放大后的第 一网 t^象的 # 可参见图 1所示实施例的描述。
在本实施例中, 网关后台服务器与网管前台客户端相互配合, 根据网 管前台客户端的第一指令, 获取第一网元对象的位置坐标和大小信息, 并 提供给网管前台客户端, 为网管前台客户端基于获取的信息和窗口的大小 完成对该网元对象的显示位置的调整和对该网元对象的放大, 使得该网元 对象在窗口中能够被突出显示, 进而使得用户能够快速从窗口中众多网元 对象中识别出该网元对象提供了条件。
图 6为本发明实施例六提供的处理 3D拓朴视图中网元对象信息的方 法的流程图。 如图 6所示, 本实施例的方法包括:
步骤 601、 接收网管前台客户端发送的第二指令。
其中, 第二指令是网管前台客户端响应于用户查看窗口所显示的 3D 拓朴视图中第二网元对象的连接关系的操作而生成的。 第二指令包括第二 网元对象的标识和连接关系查看操作命令。 第二网元对象的连接关系包括 第二网元对象和所有第三网元对象, 第三网元对象为与第二网元对象连接 的网元^ "象。 本实施例的执行主体为网管后台服务器。 网管后台服务器与网管前台 客户端相互配合。
其中, 网管前台客户端响应于用户查看窗口所显示的 3D拓朴视图中 第二网元对象的连接关系的操作而向网管后台服务器发送第二指令的操 作, 可参见图 2所示实施例的描述, 在此不再赘述。
对网管后台服务器来说, 会接收网管前台客户端发送的第二指令。 步骤 602、 根据连接关系查看操作命令和第二网元对象的标识, 从存 储的连接对象信息中获取所有第三网元对象的标识, 并根据第二网元对象 的标识和每个第三网元对象的标识, 从网元对象信息中获取第二网元对象 的位置坐标和每个第三网元对象的位置坐标。
其中, 连接对象信息包括: 3D 拓朴视图中每个连接两端的网元对象 的标识。
步骤 603、 向网管前台客户端传递第二网元对象的位置坐标和每个第 三网元的位置坐标, 以使网管前台客户端在窗口中同时显示第二网元对象 和每个第三网元对象。
其中, 网管前台客户端在窗口中同时显示第二网元对象和每个第三网 元对象的过程可参见图 2所示实施例的描述。
可选的, 在第三网元对象与第二网元对象属于不同的子网时, 网管后 台服务器还可以获取第三网元对象所属子网的信息并传递给网管前台客 户端, 以使网管前台客户端在第三网元对象与第二网元对象属于不同的子 网时, 显示第三网元对象所属子网的信息。
在本实施例中, 网关后台服务器与网管前台客户端相互配合, 根据网 管前台客户端的第二指令, 获取第二网元对象的和每个第三网元对象的位 置坐标并提供给网管前台客户端, 为网管前台客户端基于获取的信息和窗 口的大小对第三网元对象的显示位置的调整, 使得第三网元对象和第二网 元对象同时在窗口中显示, 进而使得用户能够查看网元的连接关系提供了 条件。
图 7为本发明实施例七提供的处理 3D拓朴视图中网元对象信息的流 程图。 如图 7所示, 本实施例的方法包括:
步骤 701、 接收网管前台客户端发送的第三指令。 其中, 第三指令是网管前台客户端响应于用户创建 SDH路径的操作 而生成的。 第三指令包括源端网元对象信息、 宿端网元对象信息和指定信 息。 其中, 指定信息包括所创建的 SDH路径应经过的网元对象的信息和 / 或不能经过的网元对象的信息。
本实施例的执行主体为网管后台服务器。 网管后台服务器与网管前台 客户端相互配合。
其中, 网管前台客户端响应于用户创建 SDH路径的操作而向网管后 台服务器发送第三指令的操作, 可参见图 3所示实施例的描述, 在此不再 赘述。
对网管后台服务器来说, 会接收网管前台客户端发送的第三指令。 步骤 702、 根据源端网元对象的信息、 宿端网元对象的信息和指定信 息, 使用设定的路径计算方法计算出第一 SDH路径, 所述第一 SDH路径 是计算出的从源端网元对象到宿端网元对象的 SDH路径。
步骤 703、 向网管前台客户端传递第一 SDH路径的信息和第一 SDH 路径上各网元对象的可用资源信息, 以使网管前台客户端根据第一 SDH 路径的信息在窗口中显示第一 SDH路径。
具体的, 网管后台服务器在接收到第三指令后, 会对第三指令进行解 析, 从中获取源端网元对象信息、 宿端网元对象信息、 资源数量门限和指 定信息等,并会识别出需要在源端网元对象和宿端网元对象之间建立 SDH 业务关系, 即创建一条 SDH路径, 且所创建的 SDH路径必须满足指定信 息的要求。 然后, 网管后台服务器会根据源端网元对象的信息、 宿端网元 对象的信息和指定信息, 使用预先设定的路径计算方法计算出从源端网元 对象到宿端网元对象的 SDH路径。 其中, 将该 SDH路径称为第一 SDH 路径。 然后, 网管后台服务器会将第一 SDH路径的信息和第一 SDH路径 上各网元对象的可用资源信息传递给网管前台客户端。 其中, 第一 SDH 路径的信息主要包括构成第一 SDH路径的网元对象的标识。
其中, 路径计算方法预先存储在网管后台服务器上。 网管后台服务器 上预先存储的路径计算方法可以是一个, 也可以是多个。 当有多个路径计 算方法时, 网管后台服务器需要从多个路径计算方法中选择一个作为设定 的路径计算方法。 其中, 路径计算方法可以是最短路径计算方法, 但不限 于此。 优选的, 如果使用的是最短路径计算方法, 则网管后台服务器可以 根据源端网元对象的信息、 宿端网元对象的信息和指定信息, 使用路径计 算方法, 计算出从源端网元对象到宿端网元对象的最短 SDH路径, 即第 一 SDH路径。 其中, 最短 SDH路径是指从源端网元对象到宿端网元对象 之间跳数最少的路径。 而且, 第一 SDH路径满足指定信息的要求。 其中, 如果指定信息包括的是应经过的网元对象的信息, 则第一 SDH路径一定 经过指定信息要求必须经过的网元对象的信息; 如果指定信息包括的是不 能经过的网元对象的信息, 则第一 SDH路径一定不经过指定信息要求不 能经过的网元对象。
其中, 网管后台服务器根据预先存储各网元对象的信息、 第三指令中 的信息以及所使用的路径计算方法, 计算出第一 SDH路径的过程与现有 技术相类似, 在此不再赘述。
在本实施例中, 网关后台服务器与网管前台客户端相互配合, 根据网 管前台客户端的第三指令,创建源端网元对象到宿端网元对象之间的 SDH 路径并将创建的 SDH路径和该 SDH路径上各网元对象的可用资源信息提 供给管前台客户端, 使得管前台客户端能够在窗口中显示, 为用户开展 SDH业务提供了条件。
图 8为本发明实施例八提供的处理 3D拓朴视图中网元对象信息的方 法的流程图。 本实施例基于图 7所示实施例实现。 如图 8所示, 本实施例 的方法在步骤 703之后还包括:
步骤 704、 接收网管前台客户端发送的第四指令。
其中, 第四指令是网管前台客户端响应于用户修改第一 SDH路径的 操作而生成的。 第四指令包括修改第一 SDH路径的操作命令。
其中, 网管前台客户端响应于用户修改第一 SDH路径的操作而向网 管后台服务器发送第四指令的操作, 可参见图 4所示实施例的描述, 在此 不再赘述。
对网管后台服务器来说, 会接收网管前台客户端发送的第四指令。 步骤 705、根据修改第一 SDH路径的操作命令, 重新根据源端网元对 象的信息、 宿端网元对象的信息和指定信息, 使用设定的路径计算方法计 算出第二 SDH路径, 所述第二 SDH路径时重新计算出的从源端网元对象 到宿端网元对象的 SDH路径。
步骤 706、 向网管前台客户端传递第二 SDH路径的信息和第二 SDH 路径上各网元对象的可用资源信息, 以使网管前台客户端根据第二 SDH 路径的信息在窗口中显示第二 SDH路径。
具体的, 网管后台服务器来在接收到第四指令后, 会解析第四指令, 从中获取修改第一 SDH路径的操作命令, 识别出需要重新计算从源端网 元对象到宿端网元对象之间的 SDH路径。 然后, 网管后台服务器根据该 命令, 结合预先存储的各网元对象的信息、 第四指令包括的信息以及所使 用的路径计算方法, 重新为源端网元对象和宿端网元对象计算出 SDH路 径,并向网管前台客户端传递重新计算出的 SDH路径(即第二 SDH路径) 的信息和第二 SDH路径上各网元对象的可用资源信息。 其中, 第二 SDH 路径的信息主要包括构成第二 SDH路径的网元对象的标识。
在本实施例中, 网关后台服务器与网管前台客户端相互配合, 根据网 管前台客户端的第四指令, 根据第四指令重新创建源端网元对象到宿端网 元对象之间的 SDH路径并将重新创建的 SDH路径的信息和该 SDH路径 上各网元对象的可用资源信息提供给管前台客户端, 使得管前台客户端能 够在窗口中显示, 允许用户对 SDH路径进行修改, 为用户正确开展 SDH 业务提供了条件。
图 9为本发明一实施例提供的网管前台客户端的结构示意图。 如图 9 所示, 本实施例的网管前台客户端包括: 用户事件响应模块 91、 信息接收 模块 92和拓朴显示模块 93。
其中, 用户事件响应模块 91 , 与网管后台服务器连接, 用于响应于用 户选中窗口所显示的 3D拓朴视图中第一网元对象的操作, 向网管后台服 务器发出第一指令。 其中, 第一指令包括第一网元对象的标识和放大查看 操作命令。
信息接收模块 92, 与网管后台服务器连接, 用于接收网管后台服务器 发送的第一网元对象的位置坐标和大小信息。 其中, 第一网元对象的大小 信息包括第一网元对象的长度、 宽度和高度; 第一网元对象的位置坐标和 大小信息是网管后台服务器根据放大查看操作命令和第一网元对象的标 识, 从存储的网元对象信息中获取的; 网元对象信息 3D拓朴视图中每个 网元对象的标识、 位置坐标和大小信息。
拓朴显示模块 93 , 与信息接收模块 92连接, 用于根据窗口的大小和 第一网元对象的位置坐标调整第一网元对象在窗口中的位置坐标, 将第一 网元对象的大小信息乘以预设放大倍数, 以放大第一网元对象, 并在窗口 中调整后的位置坐标处重新显示放大后的第一网元对象。
进一步, 网元对象信息还可以包括: 3D 拓朴视图中每个网元对象的 显示状态。 基于此, 信息接收模块 92具体可用于接收网管后台服务器发 送的窗口中当前显示的各网元对象的位置坐标和大小信息。 其中, 窗口中 当前显示的各网元对象中包括第一网元对象。 窗口中当前显示的各网元对 象是网管后台服务器根据网元对象信息中每个网元对象的显示状态确定 出的。
进一步, 拓朴显示模块 93 具体可以用于根据窗口中当前显示的各网 元对象的位置坐标, 计算窗口中当前显示的各网元对象中除第一网元对象 之外其他网元对象与第一网元对象之间的距离; 重新计算第一网元对象的 位置坐标, 重新计算出的第一网元对象的位置坐标为窗口的中心位置对应 的坐标, 并分别将第一网元对象的大小信息中的长度、 宽度和高度乘以放 大倍数; 根据窗口中当前显示的各网元对象中除第一网元对象之外其他网 元对象与第一网元对象之间的距离和重新计算出的第一网元对象的位置 坐标, 重新计算窗口中当前显示的各网元对象中除第一网元对象之外其他 网元对象的位置坐标; 根据重新计算出的窗口中当前显示的各网元对象的 位置坐标、 第一网元对象放大后的大小信息和接收的窗口中当前显示的各 网元对象中除第一网元对象之外其他网元对象的大小信息, 重新在窗口中 显示窗口中当前显示的各网元对象。
本实施例的网管前台客户端的各功能模块可用于执行图 1 所示处理 3D 拓朴视图中网元对象信息的方法流程, 其具体工作原理不再赘述, 详 见方法实施的描述。
本实施例的网管前台客户端, 响应用户选中网元对象的操作并会通过 向网管后台服务器发出指令, 从网管后台服务器获取该网元对象的位置坐 标和大小信息, 进而基于获取的信息和窗口的大小完成对该网元对象的显 示位置的调整和对该网元对象的放大, 使得该网元对象在窗口中能够被突 出显示, 进而使得用户能够快速从窗口中众多网元对象中识别出该网元对 进一步, 本发明实施例提供的网管前台客户端中的用户事件响应模块
91还用于响应于用户查看窗口所显示的 3D拓朴视图中第二网元对象的连 接关系的操作, 向网管后台服务器发出第二指令。 其中, 第二指令包括第 二网元对象的标识和连接关系查看操作命令; 第二网元对象的连接关系包 括第二网元对象和所有第三网元对象, 第三网元对象为与第二网元对象连 接的网元对象。
相应的, 信息接收模块 92还用于接收网管后台服务器发送的第二网 元对象的位置坐标和每个第三网元对象的位置坐标。 其中, 第一网元对象 的位置坐标是网管后台服务器根据第二网元对象的标识, 从网元对象信息 中获取的; 第三网元对象的位置坐标是网管后台服务器根据连接关系查看 操作命令和第二网元对象的标识, 从存储的连接对象信息中获取第三网元 对象的标识, 然后根据第三网元对象的标识从网元对象信息中获取的。 其 中, 连接对象信息包括: 3D拓朴视图中每个连接两端的网元对象的标识。
相应的, 拓朴显示模块 93还用于根据窗口的大小、 第二网元对象的 位置坐标和每个第三网元对象的位置坐标, 重新计算每个第三网元对象的 位置坐标, 以使每个第三网元对象均能显示在窗口中, 根据重新计算出的 每个第三网元对象的位置坐标和第二网元的位置坐标, 在窗口中显示第二 网元对象和每个第三网元对象。
更进一步, 拓朴显示模块 93 具体可以用于判断第三网元对象的位置 坐标是否在窗口范围内, 如果判断结果为否, 执行根据窗口的大小、 第二 网元对象的位置坐标和每个第三网元对象的位置坐标, 重新计算每个第三 网元对象的位置坐标, 以使每个第三网元对象均能显示在窗口中的操作。
进一步, 拓朴显示模块 93 具体可以用于根据第二网元对象的位置坐 标和第三网元对象的位置坐标, 计算第三网元对象和第二网元对象之间的 距离, 根据窗口的大小, 缩短第三网元对象和第二网元对象之间的距离, 直到第三网元对象显示在窗口中为止, 根据第三网元对象和第二网元对象 之间的距离的缩短倍数, 重新计算第三网元对象的位置坐标。
拓朴显示模块 93 具体可以用于根据重新计算出的每个第三网元对象 的位置坐标,在窗口中显示每个第三网元对象,根据第二网元的位置坐标, 在窗口中显示第二网元对象, 并改变第二网元对象和每个第三网元对象之 间连线的颜色, 以使第二网元对象和每个第三网元对象之间连线的颜色不 同于窗口中其他连线的颜色。
拓朴显示模块 93还用于接收网管后台服务器在第二网元对象和第三 网元对象属于不同的子网时传递的第三网元对象所属子网的信息, 并显示 第三网元对象所属子网的信息。
其中, 上述各功能模块可用于执行图 2所示处理 3D拓朴视图中网元 对象信息的方法流程,其具体工作原理不再赘述,详见方法实施例的描述。
本实施例的网管前台客户端, 通过响应用户查看网元对象的连接关系 的操作, 并会生成第二指令, 将第二指令发送给网管后台服务器, 从网管 后台服务器获取该网元对象和与其连接的网元对象的位置坐标, 并根据窗 口的大小重新计算其他网元对象的位置坐标, 使得该网元对象和与其连接 的其他网元对象都能够显示在窗口中, 使得用户能够快速、 清晰的查看到 某个网元对象的连接, 由于不受子网的限制, 从而解决了现有技术中不同 子网中具有连接关系的网元对象不可见的问题。
更进一步, 本发明实施例的用户事件响应模块 91 还用于响应于用户 创建 SDH路径的操作, 向网管后台服务器发出第三指令。 其中。 第三指 令包括源端网元对象信息、 宿端网元对象信息和指定信息; 指定信息包括 所创建的 SDH路径应经过的网元对象的信息和 /或不能经过的网元对象的 信息。
信息接收模块 92还用于接收网管后台服务器发送的第一 SDH路径的 信息和第一 SDH路径上各网元对象的可用资源信息, 并根据第一 SDH路 径的信息在窗口中显示第一 SDH路径。 其中, 第一 SDH路径是网管后台 服务器根据源端网元对象的信息、 宿端网元对象的信息和指定信息, 使用 设定的路径计算方法计算出的从源端网元对象到宿端网元对象的 SDH路 径。
拓朴显示模块 93还用于根据第一 SDH路径上各网元对象的可用资源 信息和资源数量门限, 判断第一 SDH路径是否有资源告警, 并在判断结 果为有资源告警时, 在窗口中显示与第一 SDH路径对应的路径告警信息。 其中, 上述各功能模块可用于执行图 3所示处理 3D拓朴视图中网元 对象信息的方法流程,其具体工作原理不再赘述,详见方法实施例的描述。
本实施例的网管前台客户端还可以通过其窗口向用户显示路径告警 信息, 以便于用户能够及时调整第一 SDH路径, 为了成功开展 SDH业务 提供条件。
更进一步, 本发明实施例的用户事件响应模块 91 还用于响应于用户 修改第一 SDH路径的操作, 向网管后台服务器发出第四指令。 其中, 第 四指令包括修改第一 SDH路径的操作命令。
信息接收模块 92还用于接收网管后台服务器发送的第二 SDH路径的 信息和第二 SDH路径上各网元对象的可用资源信息,并根据所述第二 SDH 路径的信息在所述窗口中显示所述第二 SDH路径。 其中, 第二 SDH路径 是网管后台服务器根据修改第一 SDH路径的操作命令, 重新根据源端网 元对象的信息、 宿端网元对象的信息和指定信息, 使用设定的路径计算方 法计算出的从源端网元对象到宿端网元对象的 S DH路径。
其中, 上述各功能模块可用于执行图 4所示处理 3D拓朴视图中网元 对象信息的方法流程,其具体工作原理不再赘述,详见方法实施例的描述。
本实施例的网管前台客户端还可以在第一 SDH路径不满足开展 SDH 业务所需资源要求时, 通过显示路径告警信息, 使得用户发出修改操作, 并通过响应用户的修改操作向网管后台服务器发出第四指令, 使网管后台 服务器重新计算一条 SDH路径, 基于新建立的 SDH路径开展 SDH业务, 提高了开展 SDH业务的成功率。
图 10为本发明实施例十提供的网管后台服务器的结构示意图。 如图 10所示, 本实施例的网管后台服务器包括: 指令接收模块 1001、 信息获 取模块 1002和信息传递模块 1003。
其中, 指令接收模块 1001 , 与网管前台客户端连接, 用于接收网管前 台客户端发送的第一指令。 其中, 第一指令是网管前台客户端响应于用户 选中窗口所显示的 3D拓朴视图中第一网元对象的操作而生成的; 第一指 令包括第一网元对象的标识和放大查看操作命令。
信息获取模块 1002, 与指令接收模块 1001连接, 用于根据放大查看 操作命令和第一网元对象的标识, 从存储的网元对象信息中获取第一网元 对象的位置坐标和大小信息。 其中, 第一网元对象的大小信息包括第一网 元对象的长度、 宽度和高度; 网元对象信息包括 3D拓朴视图中每个网元 对象的标识、 位置坐标和大小信息。
信息传递模块 1003 , 与信息获取模块 1002和网管前台客户端连接, 用于向网管前台客户端传递第一网元对象的位置坐标和大小信息, 以使网 管前台客户端在窗口中调整后的位置坐标处重新显示放大后的第一网元对象。
进一步, 网元对象信息还包括: 3D 拓朴视图中每个网元对象的显示 状态。
本实施例的信息获取模块 1002具体可以用于根据放大查看操作命令 和网元对象信息中每个网元对象的显示状态, 从网元对象信息中获取窗口 中当前显示的各网元对象的位置坐标和大小信息窗口。 其中, 窗口中当前 显示的各网元对象中包括第一网元对象。
相应的, 信息传递模块 1003 具体用于向网管前台客户端传递窗口中 当前显示的各网元对象的位置坐标和大小信息。
本实施例的网管后台服务器的各功能模块可用于执行图 5 所示处理
3D 拓朴视图中网元对象信息的方法流程, 其具体工作原理不再赘述, 详 见方法实施例的描述。
本实施例的网管后台服务器, 与本发明实施例提供的网管前台客户端 相互配合, 根据网管前台客户端的第一指令, 获取第一网元对象的位置坐 标和大小信息, 并提供给网管前台客户端, 为网管前台客户端基于获取的 信息和窗口的大小完成对该网元对象的显示位置的调整和对该网元对象 的放大, 使得该网元对象在窗口中能够被突出显示, 进而使得用户能够快 速从窗口中众多网元对象中识别出该网元对象提供了条件。
进一步, 本发明实施例的网管后台服务器的指令接收模块 1001 还用 于接收网管前台客户端发送的第二指令。 其中, 第二指令是网管前台客户 端响应于用户查看窗口所显示的 3D拓朴视图中第二网元对象的连接关系 的操作而生成的; 第二指令包括第二网元对象的标识和连接关系查看操作 命令; 第二网元对象的连接关系包括第二网元对象和所有第三网元对象, 第三网元对象为与第二网元对象连接的网元对象。
相应的, 信息获取模块 1002还用于根据连接关系查看操作命令和第 二网元对象的标识, 从预先存储的连接对象信息中获取所有第三网元对象 的标识, 并根据第二网元对象的标识和每个第三网元对象的标识, 从网元 对象信息中获取第二网元对象的位置坐标和每个第三网元对象的位置坐 标。 其中, 连接对象信息包括: 3D 拓朴视图中每个连接两端的网元对象 的标识。
相应的, 信息传递模块 1003还用于向网管前台客户端传递第二网元 对象的位置坐标和每个第三网元的位置坐标, 以使网管前台客户端在窗口 中同时显示第二网元对象和每个第三网元对象。
上述各功能模块可用于执行图 6所示处理 3D拓朴视图中网元对象信 息的方法流程, 其具体工作原理不再赘述, 详见方法实施例的描述。
本实施例的网管后台服务器, 与本发明实施例提供的网管前台客户端 相互配合, 根据网管前台客户端的第二指令, 获取第二网元对象的和每个 第三网元对象的位置坐标并提供给网管前台客户端, 为网管前台客户端基 于获取的信息和窗口的大小对第三网元对象的显示位置的调整, 使得第三 网元对象和第二网元对象同时在窗口中显示, 进而使得用户能够查看网元 的连接关系提供了条件。
更进一步, 本发明实施例的信令接收模块 1001 还用于接收网管前台 客户端发送的第三指令。 其中, 第三指令是网管前台客户端响应于用户创 建同步数字传输体制 SDH路径的操作而生成的; 第三指令包括源端网元 对象信息、 宿端网元对象信息和指定信息; 指定信息包括所创建的 SDH 路径应经过的网元对象的信息和 /或不能经过的网元对象的信息。
相应的, 信息获取模块 1002还用于根据源端网元对象的信息、 宿端 网元对象的信息和指定信息, 使用设定的路径计算方法计算出第一 SDH 路径, 第一 SDH路径是计算出的从源端网元对象到宿端网元对象的 SDH 路径。
相应的, 信息传递模块 1003还用于向网管前台客户端传递第一 SDH 路径的信息和第一 SDH路径上各网元对象的可用资源信息, 以使网管前 台客户端根据第一 SDH路径的信息在窗口中显示第一 SDH路径。
上述各功能模块可用于执行图 7所示处理 3D拓朴视图中网元对象信 息的方法流程, 其具体工作原理不再赘述, 详见方法实施例的描述。 本实施例的网管后台服务器, 与本发明实施例提供的网管前台客户端 相互配合, 根据网管前台客户端的第三指令, 创建源端网元对象到宿端网 元对象之间的 SDH路径并将创建的 SDH路径和该 SDH路径上各网元对 象的可用资源信息提供给管前台客户端, 使得管前台客户端能够在窗口中 显示, 为用户开展 SDH业务提供了条件。
更进一步, 本发明实施例的信令接收模块 1001 还用于接收网管前台 客户端发送的第四指令。 其中, 第四指令是网管前台客户端响应于用户修 改第一 SDH路径的操作而生成的, 第四指令包括修改第一 SDH路径的操 作命令。
相应的, 信息获取模块 1002还用于根据修改第一 SDH路径的操作命 令, 重新根据源端网元对象的信息、 宿端网元对象的信息和指定信息, 使 用设定的路径计算方法计算出第二 SDH路径, 第二 SDH路径是重新计算 出的从源端网元对象到宿端网元对象的 SDH路径, 以使网管前台客户端 根据第二 SDH路径的信息在窗口中显示第二 SDH路径。
相应的, 信息传递模块 1003还用于向网管前台客户端传递第二 SDH 路径的信息和第二 SDH路径上各网元对象的可用资源信息。
上述各功能模块可用于执行图 8所示处理 3D拓朴视图中网元对象信 息的方法流程, 其具体工作原理不再赘述, 详见方法实施例的描述。
本实施例的网管后台服务器, 与本发明实施例提供的网管前台客户端 相互配合, 根据网管前台客户端的第四指令, 根据第四指令重新创建源端 网元对象到宿端网元对象之间的 SDH路径并将重新创建的 SDH路径和该 SDH路径上各网元对象的可用资源信息提供给管前台客户端,使得管前台 客户端能够在窗口中显示, 允许用户对 SDH路径进行修改, 为用户正确 开展 SDH业务提供了条件。
图 11 为本发明实施例十一提供的网络管理系统的结构示意图。 如图
11所示, 本实施例的系统包括: 网管前台客户端 1111和网管后台服务器 1112。 其中: 网管前台客户端 1111和网管后台服务器 1112连接。
网管前台客户端 1111用于响应于用户选中窗口所显示的 3D拓朴视图 中第一网元对象的操作, 向网管后台服务器 1112发送第一指令。 第一指 令包括第一网元对象的标识和放大查看操作命令。 网管后台服务器 11 12用于根据放大查看操作命令和第一网元对象的 标识, 从存储的网元对象信息中获取第一网元对象的位置坐标和大小信 息, 并向网管前台客户端 1 11 1传递第一网元对象的位置坐标和大小信息。 其中, 网元对象信息包括 3D拓朴视图中每个网元对象的标识、 位置坐标 和大小信息。
网管前台客户端 11 11 还用于根据窗口的大小和第一网元对象的位置 坐标调整第一网元对象在窗口中的位置坐标, 将第一网元对象的大小信息 乘以预设放大倍数, 以放大第一网元对象, 并在窗口中调整后的位置坐标处 重新显示放大后的第一网元对象。
本实施例的网管前台客户端 11 11 的结构可参见图 9所示, 其工作原 理可参见图 1所示处理 3D拓朴视图中网元对象信息的流程, 在此均不作 赘述。
本实施例的网管后台服务器 11 12的结构可参见图 10所示, 其工作原 理可参见图 5所示处理 3D拓朴视图中网元对象信息的流程, 在此均不作 赘述。
本实施例的网络管理系统, 网管后台服务器与网管前台客户端相互配 合, 网管前台客户端响应用户查看网元对象的操作并向网管后台服务器发 送第一指令, 网管后台服务器根据网管前台客户端的第一指令, 获取第一 网元对象的位置坐标和大小信息, 并提供给网管前台客户端, 网管前台客 户端基于接收到的第一网元对象的信息和窗口的大小完成对该网元对象 的显示位置的调整和对该网元对象的放大, 使得该网元对象在窗口中能够 被突出显示, 进而使得用户能够快速从窗口中众多网元对象中识别出该网 元对象。
进一步, 本发明实施例提供的网管前台客户端 11 11 还用于响应于用 户查看窗口所显示的 3D拓朴视图中第二网元对象的连接关系的操作, 向 网管后台服务器 1112发出第二指令。 其中, 第二指令包括第二网元对象 的标识和连接关系查看操作命令; 第二网元对象的连接关系包括第二网元 对象和所有第三网元对象; 第三网元对象为与第二网元对象连接的网元对 网管后台服务器 11 12还用于根据连接关系查看操作命令和第二网元 对象的标识, 从存储的连接对象信息中获取所有第三网元对象的标识, 并 根据第二网元对象的标识和每个第三网元对象的标识, 从网元对象信息中 获取第二网元对象的位置坐标和每个第三网元对象的位置坐标, 并向网管 前台客户端 1111 传递第二网元对象的位置坐标和每个第三网元的位置坐 标。 其中, 连接对象信息包括: 3D 拓朴视图中每个连接两端的网元对象 的标识。
网管前台客户端 1111 还用于根据窗口的大小、 第二网元对象的位置 坐标和每个第三网元对象的位置坐标, 重新计算每个第三网元对象的位置 坐标, 以使每个第三网元对象均能显示在窗口中, 根据重新计算出的每个 第三网元对象的位置坐标和第二网元的位置坐标, 在窗口中显示第二网元 对象和每个第三网元对象。
本实施例的网络管理系统, 网管后台服务器与网管前台客户端相互配 合, 网管前台客户端响应用户查看第二网元对象的连接关系的操作并向网 管后台服务器发送第二指令, 网管后台服务器根据第二指令获取第二网元 对象的位置坐标和每个和第二网元对象连接的第三网元对象的位置坐标, 并提供给网管前台客户端, 网管前台客户端根据接收到的信息和窗口大小 重新计算第三网元对象的位置坐标, 使得第二网元对象和所有第三网元对 象同时显示在窗口中, 使得运维人员或用户能够清楚的查看到各网元对象 之间的连接关系, 便于基于各网元对象之间的连接关系进行故障发现、 故 障排查等操作, 有利于提高故障发现、 故障排查的效率。
更进一步, 本发明实施例提供的网管前台客户端 1111 还用于响应于 用户创建同步数字传输体制 SDH路径的操作, 向网管后台服务器 1112发 出第三指令。 其中, 第三指令包括源端网元对象信息、 宿端网元对象信息 和指定信息; 指定信息包括所创建的 SDH路径应经过的网元对象的信息 和 /或不能经过的网元对象的信息。
网管后台服务器 1112还用于根据源端网元对象的信息、 宿端网元对 象的信息和指定信息, 使用设定的路径计算方法计算出第一 SDH路径, 并向网管前台客户端 1111传递第一 SDH路径的信息和第一 SDH路径上 各网元对象的可用资源信息; 第一 SDH路径是计算出的从源端网元对象 到宿端网元对象的 SDH路径。
网管前台客户端 1111还用于接收网管后台服务器发送的第一 SDH路 径的信息和第一 SDH路径上各网元对象的可用资源信息,并根据第一 SDH 路径的信息在窗口中显示第一 SDH路径, 根据第一 SDH路径上各网元对 象的可用资源信息和资源数量门限, 判断第一 SDH路径是否有资源告警, 如果判断结果为有资源告警, 在窗口中显示与第一 SDH路径对应的路径 告警信息。
本实施例的网络管理系统, 网管后台服务器与网管前台客户端相互配 合, 网管前台客户端响应用户创建 SDH路径的操作并向网管后台服务器 发出第三指令, 网管后台服务器根据第三指令创建源端网元对象到宿端网 元对象的 SDH路径并将创建的 SDH路径和其上各网元对象的可用资源信 息提供给网管前台客户端, 网管前台客户端通过其窗口向用户显示路径告 警信息, 以便于用户能够及时调整第一 SDH路径, 为了成功开展 SDH业 务提供条件。
更进一步, 本发明实施例提供的网管前台客户端 1111 还用于响应于 用户修改第一 SDH路径的操作, 向网管后台服务器 1112发出第四指令; 第四指令包括修改第一 SDH路径的操作命令。
网管后台服务器 1112还用于根据修改第一 SDH路径的操作命令, 重 新根据源端网元对象的信息、 宿端网元对象的信息和指定信息, 使用设定 的路径计算方法计算出第二 SDH路径, 并向网管前台客户端 1111传递第 二 SDH路径的信息和第二 SDH路径上各网元对象的可用资源信息。其中, 第二 SDH路径是重新计算出的从源端网元对象到宿端网元对象的 SDH路 径。
网管前台客户端 1111 还用于接收网管后台服务器 1112发送的第二 SDH路径的信息和第二 SDH路径上各网元对象的可用资源信息, 并根据 第二 SDH路径的信息在窗口中显示第二 SDH路径。
本实施例的网络管理系统, 网管后台服务器与网管前台客户端相互配 合, 网管前台客户端响应用户修改 SDH路径的操作并向网管后台服务器 发出第四指令, 网管后台服务器根据第四指令重新计算源端网元对象到宿 端网元对象的 SDH路径, 并将重新计算的 SDH路径和其上各网元对象的 可用资源信息提供给网管前台客户端, 以便于用户基于新建立的 SDH路 径开展 SDH业务, 提高了开展 SDH业务的成功率。
本领域普通技术人员可以理解: 实现上述各方法实施例的全部或部分 步骤可以通过程序指令相关的硬件来完成。 前述的程序可以存储于一计算 机可读取存储介质中。 该程序在执行时, 执行包括上述各方法实施例的步 骤; 而前述的存储介质包括: ROM、 RAM, 磁碟或者光盘等各种可以存 储程序代码的介质。
最后应说明的是: 以上各实施例仅用以说明本发明的技术方案, 而非 对其限制; 尽管参照前述各实施例对本发明进行了详细的说明, 本领域的 普通技术人员应当理解: 其依然可以对前述各实施例所记载的技术方案进 行修改, 或者对其中部分或者全部技术特征进行等同替换; 而这些修改或 者替换, 并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims

权 利 要 求 书
1、一种处理 3D拓朴视图中网元对象信息的方法,其特征在于, 包括: 响应于用户选中窗口所显示的 3D拓朴视图中第一网元对象的操作, 向网管后台服务器发出第一指令, 所述第一指令包括所述第一网元对象的 标识和放大查看操作命令;
接收所述网管后台服务器发送的所述第一网元对象的位置坐标和大 小信息; 所述第一网元对象的大小信息包括所述第一网元对象的长度、 宽 度和高度; 所述第一网元对象的位置坐标和大小信息是所述网管后台服务 器根据所述放大查看操作命令和所述第一网元对象的标识, 从存储的网元 对象信息中获取的; 所述网元对象信息包括所述 3D拓朴视图中每个网元 对象的标识、 位置坐标和大小信息;
根据所述窗口的大小和所述第一网元对象的位置坐标调整所述第一 网元对象在所述窗口中的位置坐标, 将所述第一网元对象的大小信息乘以 预设放大倍数, 以放大所述第一网元对象, 并在所述窗口中调整后的位置坐 标处重新显示所述放大后的第一网元对象。
2、 根据权利要求 1所述的处理 3D拓朴视图中网元对象信息的方法, 其特征在于, 所述网元对象信息还包括: 所述 3D拓朴视图中每个网元对 象的显示状态;
所述接收所述网管后台服务器发送的所述第一网元对象的位置坐标 和大小信息包括:
接收所述网管后台服务器发送的所述窗口中当前显示的各网元对象 的位置坐标和大小信息; 所述窗口中当前显示的各网元对象是所述网管后 台服务器根据所述网元对象信息中每个网元对象的显示状态确定出的; 所 述窗口中当前显示的各网元对象中包括所述第一网元对象。
3、 根据权利要求 2所述的处理 3D拓朴视图中网元对象信息的方法, 其特征在于, 所述根据所述窗口的大小和所述第一网元对象的位置坐标调 整所述第一网元对象在所述窗口中的位置坐标, 将所述第一网元对象的大 小信息乘以预设放大倍数, 以放大所述第一网元对象, 并在所述窗口中调 整后的位置坐标处重新显示所述放大后的第一网元对象包括:
根据所述窗口中当前显示的各网元对象的位置坐标, 计算所述窗口中 当前显示的各网元对象中除所述第一网元对象之外其他网元对象与所述 第一网元对象之间的距离; 重新计算所述第一网元对象的位置坐标, 重新计算出的所述第一网元 对象的位置坐标为所述窗口的中心位置对应的坐标,并分别将所述第一网元 对象的大小信息中的长度、 宽度和高度乘以所述放大倍数;
根据所述窗口中当前显示的各网元对象中除所述第一网元对象之外 其他网元对象与所述第一网元对象之间的距离和重新计算出的所述第一 网元对象的位置坐标, 重新计算所述窗口中当前显示的各网元对象中除所 述第一网元对象之外其他网元对象的位置坐标;
根据重新计算出的所述窗口中当前显示的各网元对象的位置坐标、 所 述第一网元对象放大后的大小信息和接收的所述窗口中当前显示的各网 元对象中除所述第一网元对象之外其他网元对象的大小信息, 重新在所述 窗口中显示所述窗口中当前显示的各网元对象。
4、根据权利要求 1或 2或 3所述的处理 3D拓朴视图中网元对象信息 的方法, 其特征在于, 还包括:
响应于所述用户查看所述窗口所显示的所述 3D拓朴视图中第二网元 对象的连接关系的操作, 向所述网管后台服务器发出第二指令; 所述第二 指令包括所述第二网元对象的标识和连接关系查看操作命令; 所述第二网 元对象的连接关系包括所述第二网元对象和所有第三网元对象, 所述第三 网元对象为与所述第二网元对象连接的网元对象;
接收所述网管后台服务器发送的所述第二网元对象的位置坐标和每 个所述第三网元对象的位置坐标; 所述第二网元对象的位置坐标是所述网 管后台服务器根据所述第二网元对象的标识, 从所述网元对象信息中获取 的; 所述第三网元对象的位置坐标是所述网管网管后台服务器根据所述连 接关系查看操作命令和所述第二网元对象的标识, 从存储的连接对象信息 中获取所述第三网元对象的标识, 然后根据所述第三网元对象的标识从所 述网元对象信息中获取的; 所述连接对象信息包括: 所述 3D拓朴视图中 每个连接两端的网元对象的标识;
根据所述窗口的大小、 所述第二网元对象的位置坐标和每个所述第三 网元对象的位置坐标, 重新计算每个所述第三网元对象的位置坐标, 以使 每个所述第三网元对象均能显示在所述窗口中;
根据重新计算出的每个所述第三网元对象的位置坐标和所述第二网 元的位置坐标, 在所述窗口中显示所述第二网元对象和每个所述第三网元 对象。
5、 根据权利要求 4所述的处理 3D拓朴视图中网元对象信息的方法, 其特征在于, 所述根据所述窗口的大小、 所述第二网元对象的位置坐标和 每个所述第三网元对象的位置坐标, 重新计算每个所述第三网元对象的位 置坐标, 以使每个所述第三网元对象均能显示在所述窗口中包括:
判断所述第三网元对象的位置坐标是否在所述窗口范围内;
如果判断结果为否, 执行根据所述窗口的大小、 所述第二网元对象的 位置坐标和每个所述第三网元对象的位置坐标, 重新计算每个所述第三网 元对象的位置坐标, 以使每个所述第三网元对象均能显示在所述窗口中的 操作。
6、 根据权利要求 5所述的处理 3D拓朴视图中网元对象信息的方法, 其特征在于, 所述根据所述窗口的大小、 所述第二网元对象的位置坐标和 每个所述第三网元对象的位置坐标, 重新计算每个所述第三网元对象的位 置坐标, 以使每个所述第三网元对象均能显示在所述窗口中包括:
根据所述第二网元对象的位置坐标和所述第三网元对象的位置坐标, 计算所述第三网元对象和所述第二网元对象之间的距离;
根据所述窗口的大小, 缩短所述第三网元对象和所述第二网元对象之 间的距离, 直到所述第三网元对象显示在所述窗口中为止;
根据所述第三网元对象和所述第二网元对象之间的距离的缩短倍数, 重新计算所述第三网元对象的位置坐标。
7、 根据权利要求 4所述的处理 3D拓朴视图中网元对象信息的方法, 其特征在于, 还包括:
接收所述网管后台服务器在所述第二网元对象和所述第三网元对象 属于不同的子网时传递的所述第三网元对象所属子网的信息, 并显示所述 第三网元对象所属子网的信息。
8、 根据权利要求 4所述的处理 3D拓朴视图中网元对象信息的方法, 其特征在于, 所述根据重新计算出的每个所述第三网元对象的位置坐标和 所述第二网元的位置坐标, 在所述窗口中显示所述第二网元对象和每个所 述第三网元对象包括:
根据重新计算出的每个所述第三网元对象的位置坐标, 在所述窗口中 显示每个所述第三网元对象, 根据所述第二网元的位置坐标, 在所述窗口 中显示所述第二网元对象, 并改变所述第二网元对象和每个所述第三网元 对象之间连线的颜色, 以使所述第二网元对象和每个所述第三网元对象之 间连线的颜色不同于所述窗口中其他连线的颜色。
9、根据权利要求 1或 2或 3所述的处理 3D拓朴视图中网元对象信息 的方法, 其特征在于, 还包括:
响应于用户创建同步数字传输体制 SDH路径的操作, 向所述网管后 台服务器发出第三指令; 所述第三指令包括源端网元对象信息、 宿端网元 对象信息和指定信息; 所述指定信息包括所创建的 SDH路径应经过的网 元对象的信息和 /或不能经过的网元对象的信息;
接收所述网管后台服务器发送的第一 SDH 路径的信息和所述第一 SDH路径上各网元对象的可用资源信息, 并根据所述第一 SDH路径的信 息在所述窗口中显示所述第一 SDH路径; 所述第一 SDH路径是所述网管 后台服务器根据所述源端网元对象的信息、 宿端网元对象的信息和指定信 息, 使用设定的路径计算方法计算出的从所述源端网元对象到所述宿端网 元对象的 SDH路径;
根据所述第一 SDH路径上各网元对象的可用资源信息和资源数量门 限, 判断所述第一 SDH路径是否有资源告警;
如果判断结果为有资源告警, 在所述窗口中显示与所述第一 SDH路 径对应的路径告警信息。
10、根据权利要求 9所述的处理 3D拓朴视图中网元对象信息的方法, 其特征在于, 还包括:
响应于用户修改所述第一 SDH路径的操作, 向所述网管后台服务器 发出第四指令; 所述第四指令包括修改所述第一 SDH路径的操作命令; 接收所述网管后台服务器发送的第二 SDH 路径的信息和所述第二 SDH路径上各网元对象的可用资源信息, 并根据所述第二 SDH路径的信 息在所述窗口中显示所述第二 SDH路径; 所述第二 SDH路径是所述网管 后台服务器根据所述修改所述第一 SDH路径的操作命令, 重新根据所述 源端网元对象的信息、 宿端网元对象的信息和指定信息, 使用设定的路径 计算方法计算出的从所述源端网元对象到所述宿端网元对象的 SDH路径。
11、 一种处理 3D拓朴视图中网元对象信息的方法, 其特征在于, 包 括:
接收网管前台客户端发送的第一指令; 所述第一指令是所述网管前台 客户端响应于用户选中窗口所显示的 3D拓朴视图中第一网元对象的操作 而生成的, 所述第一指令包括所述第一网元对象的标识和放大查看操作命 根据所述放大查看操作命令和所述第一网元对象的标识, 从存储的网 元对象信息中获取所述第一网元对象的位置坐标和大小信息; 其中, 所述 第一网元对象的大小信息包括所述第一网元对象的长度、 宽度和高度; 所 述网元对象信息包括所述 3D拓朴视图中每个网元对象的标识、 位置坐标 和大小信息;
向所述网管前台客户端传递所述第一网元对象的位置坐标和大小信 息, 以使所述网管前台客户端在所述窗口中调整后的位置坐标处重新显示放 的第一网元对象。
12、根据权利要求 11所述的处理 3D拓朴视图中网元对象信息的方法, 其特征在于, 所述网元对象信息还包括: 所述 3D拓朴视图中每个网元对 象的显示状态;
所述根据所述放大查看操作命令和所述第一网元对象的标识, 从存储 的网元对象信息中获取所述第一网元对象的位置坐标和大小信息包括: 根据所述放大查看操作命令和所述网元对象信息中每个网元对象的 显示状态, 从所述网元对象信息中获取所述窗口中当前显示的各网元对象 的位置坐标和大小信息窗口; 所述窗口中当前显示的各网元对象中包括所 述第一网元对象;
所述向所述网管前台客户端传递所述第一网元对象的位置坐标和大 小信息包括:
向所述网管前台客户端传递所述窗口中当前显示的各网元对象的位 置坐标和大小信息。
13、 根据权利要求 11或 12所述的处理 3D拓朴视图中网元对象信息 的方法, 其特征在于, 还包括:
接收所述网管前台客户端发送的第二指令; 所述第二指令是所述网管 前台客户端响应于所述用户查看所述窗口所显示的所述 3D拓朴视图中第 二网元对象的连接关系的操作而生成的, 所述第二指令包括所述第二网元 对象的标识和连接关系查看操作命令; 所述第二网元对象的连接关系包括 三网元对象, 所述第三网元对象为与所述第二
Figure imgf000045_0001
根据所述连接关系查看操作命令和所述第二网元对象的标识, 从存储 的连接对象信息中获取所有所述第三网元对象的标识, 并根据所述第二网 元对象的标识和每个所述第三网元对象的标识, 从所述网元对象信息中获 取所述第二网元对象的位置坐标和每个所述第三网元对象的位置坐标; 所 述连接对象信息包括: 所述 3D拓朴视图中每个连接两端的网元对象的标 识;
向所述网管前台客户端传递所述第二网元对象的位置坐标和每个所 述第三网元的位置坐标, 以使所述网管前台客户端在所述窗口中同时显示所 述第二网元对象和每个所述第三网元对象。
14、 根据权利要求 11或 12所述的处理 3D拓朴视图中网元对象信息 的方法, 其特征在于, 还包括:
接收所述网管前台客户端发送的第三指令; 所述第三指令是所述网管 前台客户端响应于所述用户创建同步数字传输体制 SDH路径的操作而生 成的, 所述第三指令包括所述源端网元对象信息、 宿端网元对象信息和指 定信息; 所述指定信息包括所创建的 SDH路径应经过的网元对象的信息 和 /或不能经过的网元对象的信息;
根据所述源端网元对象的信息、 宿端网元对象的信息和指定信息, 使 用设定的路径计算方法计算出第一 SDH路径, 所述第一 SDH路径是计算 出的从所述源端网元对象到所述宿端网元对象的 SDH路径;
向所述网管前台客户端传递所述第一 SDH 路径的信息和所述第一 SDH路径上各网元对象的可用资源信息, 以使所述网管前台客户端根据所 述第一 SDH路径的信息在所述窗口中显示所述第一 SDH路径。
15、根据权利要求 14所述的处理 3D拓朴视图中网元对象信息的方法, 其特征在于, 还包括:
接收所述网管前台客户端发送的第四指令; 所述第四指令是所述网管 前台客户端响应于所述用户修改所述第一 SDH路径的操作而生成的, 所 述第四指令包括修改所述第一 SDH路径的操作命令;
根据所述修改所述第一 SDH路径的操作命令, 重新根据所述源端网 元对象的信息、 宿端网元对象的信息和指定信息, 使用设定的路径计算方 法计算出第二 SDH路径, 所述第二 SDH路径是重新计算出的从所述源端 网元对象到所述宿端网元对象的 SDH路径;
向所述网管前台客户端传递所述第二 SDH 路径的信息和所述第二
SDH路径上各网元对象的可用资源信息, 以使所述网管前台客户端根据所 述第二 SDH路径的信息在所述窗口中显示所述第二 SDH路径。
16、 一种网管前台客户端, 其特征在于, 包括:
用户事件响应模块, 用于响应于用户选中窗口所显示的 3D拓朴视图 中第一网元对象的操作, 向网管后台服务器发出第一指令, 所述第一指令 包括所述第一网元对象的标识和放大查看操作命令;
信息接收模块, 用于接收所述网管后台服务器发送的所述第一网元对 象的位置坐标和大小信息; 所述第一网元对象的大小信息包括所述第一网 元对象的长度、 宽度和高度; 所述第一网元对象的位置坐标和大小信息是 所述网管后台服务器根据所述放大查看操作命令和所述第一网元对象的 标识, 从存储的网元对象信息中获取的; 所述网元对象信息所述 3D拓朴 视图中每个网元对象的标识、 位置坐标和大小信息;
拓朴显示模块, 用于根据所述窗口的大小和所述第一网元对象的位置 坐标调整所述第一网元对象在所述窗口中的位置坐标, 将所述第一网元对 象的大小信息乘以预设放大倍数, 以放大所述第一网元对象, 并在所述窗 口中调整后的位置坐标处重新显示所述放大后的第一网元对象。
17、 根据权利要求 16所述的网管前台客户端, 其特征在于, 所述网 元对象信息还包括: 所述 3D拓朴视图中每个网元对象的显示状态;
所述信息接收模块具体用于接收所述网管后台服务器发送的所述窗 口中当前显示的各网元对象的位置坐标和大小信息; 所述窗口中当前显示 的各网元对象是所述网管后台服务器根据所述网元对象信息中每个网元 对象的显示状态确定出的; 所述窗口中当前显示的各网元对象中包括所述 第一网元对象。
18、 根据权利要求 17所述的网管前台客户端, 其特征在于, 所述拓 朴显示模块具体用于根据所述窗口中当前显示的各网元对象的位置坐标, 计算所述窗口中当前显示的各网元对象中除所述第一网元对象之外其他 网元对象与所述第一网元对象之间的距离, 重新计算所述第一网元对象的 位置坐标, 重新计算出的所述第一网元对象的位置坐标为所述窗口的中心 位置对应的坐标, 并分别将所述第一网元对象的大小信息中的长度、 宽度 和高度乘以所述放大倍数, 根据所述窗口中当前显示的各网元对象中除所 述第一网元对象之外其他网元对象与所述第一网元对象之间的距离和重 新计算出的所述第一网元对象的位置坐标, 重新计算所述窗口中当前显示 的各网元对象中除所述第一网元对象之外其他网元对象的位置坐标, 根据 重新计算出的所述窗口中当前显示的各网元对象的位置坐标、 所述第一网 元对象放大后的大小信息和接收的所述窗口中当前显示的各网元对象中 除所述第一网元对象之外其他网元对象的大小信息, 重新在所述窗口中显 示所述窗口中当前显示的各网元对象。
19、 根据权利要求 16或 17或 18所述的网管前台客户端, 其特征在 于, 所述用户事件响应模块还用于响应于所述用户查看所述窗口所显示的 所述 3D拓朴视图中第二网元对象的连接关系的操作, 向所述网管后台服 务器发出第二指令; 所述第二指令包括所述第二网元对象的标识和连接关 系查看操作命令; 所述第二网元对象的连接关系包括所述第二网元对象和 所有第三网元对象, 所述第三网元对象为与所述第二网元对象连接的网元 对象;
所述信息接收模块还用于接收所述网管后台服务器发送的所述第二 网元对象的位置坐标和每个所述第三网元对象的位置坐标; 所述第一网元 对象的位置坐标是所述网管后台服务器根据所述第二网元对象的标识, 从 所述网元对象信息中获取的; 所述第三网元对象的位置坐标是所述网管后 台服务器根据所述连接关系查看操作命令和所述第二网元对象的标识, 从 存储的连接对象信息中获取所述第三网元对象的标识, 然后根据所述第三 网元对象的标识从所述网元对象信息中获取的; 所述连接对象信息包括: 所述 3D拓朴视图中每个连接两端的网元对象的标识;
所述拓朴显示模块还用于根据所述窗口的大小、 所述第二网元对象的 位置坐标和每个所述第三网元对象的位置坐标, 重新计算每个所述第三网 元对象的位置坐标, 以使每个所述第三网元对象均能显示在所述窗口中, 根据重新计算出的每个所述第三网元对象的位置坐标和所述第二网元的 位置坐标, 在所述窗口中显示所述第二网元对象和每个所述第三网元对
20、 根据权利要求 19所述的网管前台客户端, 其特征在于, 所述拓 朴显示模块具体用于判断所述第三网元对象的位置坐标是否在所述窗口 范围内, 如果判断结果为否, 执行根据所述窗口的大小、 所述第二网元对 象的位置坐标和每个所述第三网元对象的位置坐标, 重新计算每个所述第 三网元对象的位置坐标, 以使每个所述第三网元对象均能显示在所述窗口 中的操作。
21、 根据权利要求 20所述的网管前台客户端, 其特征在于, 所述拓 朴显示模块具体用于根据所述第二网元对象的位置坐标和所述第三网元 对象的位置坐标, 计算所述第三网元对象和所述第二网元对象之间的距 离, 根据所述窗口的大小, 缩短所述第三网元对象和所述第二网元对象之 间的距离, 直到所述第三网元对象显示在所述窗口中为止, 根据所述第三 网元对象和所述第二网元对象之间的距离的缩短倍数, 重新计算所述第三 网元对象的位置坐标。
22、 根据权利要求 19所述的网管前台客户端, 其特征在于, 所述拓 朴显示模块还用于接收所述网管后台服务器在所述第二网元对象和所述 第三网元对象属于不同的子网时传递的所述第三网元对象所属子网的信 息, 并显示所述第三网元对象所属子网的信息。
23、 根据权利要求 19所述的网管前台客户端, 其特征在于, 所述拓 朴显示模块具体用于根据重新计算出的每个所述第三网元对象的位置坐 标, 在所述窗口中显示每个所述第三网元对象, 根据所述第二网元的位置 坐标, 在所述窗口中显示所述第二网元对象, 并改变所述第二网元对象和 每个所述第三网元对象之间连线的颜色, 以使所述第二网元对象和每个所 述第三网元对象之间连线的颜色不同于所述窗口中其他连线的颜色。
24、 根据权利要求 16或 17或 18所述的网管前台客户端, 其特征在 于, 所述用户事件响应模块还用于响应于所述用户创建同步数字传输体制 SDH路径的操作, 向所述网管后台服务器发出第三指令; 所述第三指令包 括源端网元对象信息、 宿端网元对象信息和指定信息; 所述指定信息包括 所创建的 SDH路径应经过的网元对象的信息和 /或不能经过的网元对象的 信息;
所述信息接收模块还用于接收所述网管后台服务器发送的第一 SDH 路径的信息和所述第一 SDH路径上各网元对象的可用资源信息, 并根据 所述第一 SDH路径的信息在所述窗口中显示所述第一 SDH路径; 所述第 一 SDH路径是所述网管后台服务器根据所述源端网元对象的信息、 宿端 网元对象的信息和指定信息, 使用设定的路径计算方法计算出的从所述源 端网元对象到所述宿端网元对象的 SDH路径;
所述拓朴显示模块还用于根据所述第一 SDH路径上各网元对象的可 用资源信息和资源数量门限, 判断所述第一 SDH路径是否有资源告警, 并在判断结果为有资源告警时, 在所述窗口中显示与所述第一 SDH路径 对应的路径告警信息。
25、 根据权利要求 24所述的网管前台客户端, 其特征在于, 所述用 户事件响应模块还用于响应于所述用户修改所述第一 SDH路径的操作, 向所述网管后台服务器发出第四指令; 所述第四指令包括修改所述第一 SDH路径的操作命令;
所述信息接收模块还用于接收所述网管后台服务器发送的第二 SDH 路径的信息和所述第二 SDH路径上各网元对象的可用资源信息, 并根据 所述第二 SDH路径的信息在所述窗口中显示所述第二 SDH路径; 所述第 二 SDH路径是所述网管后台服务器根据所述修改所述第一 SDH路径的操 作命令, 重新根据所述源端网元对象的信息、 宿端网元对象的信息和指定 信息, 使用设定的路径计算方法计算出的从所述源端网元对象到所述宿端 网元对象的 SDH路径。
26、 一种网管后台服务器, 其特征在于, 包括:
指令接收模块, 用于接收网管前台客户端发送的第一指令; 所述第一 指令是所述网管前台客户端响应于用户选中窗口所显示的 3D拓朴视图中 第一网元对象的操作而生成的, 所述第一指令包括所述第一网元对象的标 识和放大查看操作命令;
信息获取模块, 用于根据所述放大查看操作命令和所述第一网元对象 的标识, 从存储的网元对象信息中获取所述第一网元对象的位置坐标和大 小信息; 其中, 所述第一网元对象的大小信息包括所述第一网元对象的长 度、 宽度和高度; 所述网元对象信息包括所述 3D拓朴视图中每个网元对 象的标识、 位置坐标和大小信息;
信息传递模块, 用于向所述网管前台客户端传递所述第一网元对象的 位置坐标和大小信息, 以使所述网管前台客户端在所述窗口中调整后的位置坐 标处重新显示放^ ^的第一网元对象。
27、 根据权利要求 26所述的网管后台服务器, 其特征在于, 所述网 元对象信息还包括: 所述 3D拓朴视图中每个网元对象的显示状态;
所述信息获取模块具体用于根据所述放大查看操作命令和所述网元 对象信息中每个网元对象的显示状态, 从所述网元对象信息中获取所述窗 口中当前显示的各网元对象的位置坐标和大小信息窗口; 所述窗口中当前 显示的各网元对象中包括所述第一网元对象;
所述信息传递模块具体用于向所述网管前台客户端传递所述窗口中 当前显示的各网元对象的位置坐标和大小信息。
28、 根据权利要求 26或 27所述的网管后台服务器, 其特征在于, 所 述指令接收模块还用于接收所述网管前台客户端发送的第二指令; 所述第 二指令是所述网管前台客户端响应于所述用户查看所述窗口所显示的所 述 3D拓朴视图中第二网元对象的连接关系的操作而生成的, 所述第二指 令包括所述第二网元对象的标识和连接关系查看操作命令; 所述第二网元 对象的连接关系包括所述第二网元对象和所有第三网元对象, 所述第三网 元对象为与所述第二网元对象连接的网元对象;
所述信息获取模块还用于根据所述连接关系查看操作命令和所述第 二网元对象的标识, 从存储的连接对象信息中获取所有所述第三网元对象 的标识, 并根据所述第二网元对象的标识和每个所述第三网元对象的标 识, 从所述网元对象信息中获取所述第二网元对象的位置坐标和每个所述 第三网元对象的位置坐标; 所述连接对象信息包括: 所述 3D拓朴视图中 每个连接两端的网元对象的标识;
所述信息传递模块还用于向所述网管前台客户端传递所述第二网元 对象的位置坐标和每个所述第三网元的位置坐标, 以使所述网管前台客户 端在所述窗口中同时显示所述第二网元对象和每个所述第三网元对象。
29、 根据权利要求 26或 27所述的网管后台服务器, 其特征在于, 所 述信令接收模块还用于接收所述网管前台客户端发送的第三指令; 所述第 三指令是所述网管前台客户端响应于所述用户创建同步数字传输体制 SDH路径的操作而生成的, 所述第三指令包括所述源端网元对象信息、 宿 端网元对象信息和指定信息; 所述指定信息包括所创建的 SDH路径应经 过的网元对象的信息和 /或不能经过的网元对象的信息;
所述信息获取模块还用于根据所述源端网元对象的信息、 宿端网元对 象的信息和指定信息, 使用设定的路径计算方法计算出第一 SDH路径, 所述第一 SDH路径是计算出的从所述源端网元对象到所述宿端网元对象 的 SDH路径;
所述信息传递模块还用于向所述网管前台客户端传递所述第一 SDH 路径的信息和所述第一 SDH路径上各网元对象的可用资源信息,以使所述 网管前台客户端根据所述第一 SDH路径的信息在所述窗口中显示所述第 一 SDH路径。
30、 根据权利要求 29所述的网管后台服务器, 其特征在于, 所述信 令接收模块还用于接收所述网管前台客户端发送的第四指令; 所述第四指 令是所述网管前台客户端响应于所述用户修改所述第一 SDH路径的操作 而生成的, 所述第四指令包括修改所述第一 SDH路径的操作命令; 所述信息获取模块还用于根据所述修改所述第一 SDH路径的操作命 令,重新根据所述源端网元对象的信息、宿端网元对象的信息和指定信息, 使用设定的路径计算方法计算出第二 SDH路径, 所述第二 SDH路径是重 新计算出的从所述源端网元对象到所述宿端网元对象的 SDH路径;
所述信息传递模块还用于向所述网管前台客户端传递所述第二 SDH 路径的信息和所述第二 SDH路径上各网元对象的可用资源信息,以使所述 网管前台客户端根据所述第二 SDH路径的信息在所述窗口中显示所述第 二 SDH路径。
31、 一种网络管理系统, 其特征在于, 包括: 网管前台客户端和网管 后台服务器, 其中:
所述网管前台客户端用于响应于用户选中窗口所显示的 3D拓朴视图 中第一网元对象的操作, 向所述网管后台服务器发送第一指令, 所述第一 指令包括所述第一网元对象的标识和放大查看操作命令;
所述网管后台服务器用于根据所述放大查看操作命令和所述第一网 元对象的标识, 从存储的网元对象信息中获取所述第一网元对象的位置坐 标和大小信息, 并向所述网管前台客户端传递所述第一网元对象的位置坐 标和大小信息; 其中, 所述网元对象信息包括所述 3D拓朴视图中每个网 元对象的标识、 位置坐标和大小信息;
所述网管前台客户端还用于根据所述窗口的大小和所述第一网元对 象的位置坐标调整所述第一网元对象在所述窗口中的位置坐标, 将所述第 一网元对象的大小信息乘以预设放大倍数, 以放大所述第一网元对象, 并 在所述窗口中调整后的位置坐标处重新显示所述放大后的第一网元对象。
32、 根据权利要求 31 所述的网络管理系统, 其特征在于, 所述网管 前台客户端还用于响应于所述用户查看所述窗口所显示的所述 3D拓朴视 图中第二网元对象的连接关系的操作, 向所述网管后台服务器发出第二指 令; 所述第二指令包括所述第二网元对象的标识和连接关系查看操作命 令; 所述第二网元对象的连接关系包括所述第二网元对象和所有第三网元 对象, 所述第三网元对象为与所述第二网元对象连接的网元对象;
所述网管后台服务器还用于根据所述连接关系查看操作命令和所述 第二网元对象的标识, 从存储的连接对象信息中获取所有所述第三网元对 象的标识, 并根据所述第二网元对象的标识和每个所述第三网元对象的标 识, 从所述网元对象信息中获取所述第二网元对象的位置坐标和每个所述 第三网元对象的位置坐标, 并向所述网管前台客户端传递所述第二网元对 象的位置坐标和每个所述第三网元的位置坐标; 所述连接对象信息包括: 所述 3D拓朴视图中每个连接两端的网元对象的标识;
所述网管前台客户端还用于根据所述窗口的大小、 所述第二网元对象 的位置坐标和每个所述第三网元对象的位置坐标, 重新计算每个所述第三 网元对象的位置坐标, 以使每个所述第三网元对象均能显示在所述窗口 中, 根据重新计算出的每个所述第三网元对象的位置坐标和所述第二网元 的位置坐标, 在所述窗口中显示所述第二网元对象和每个所述第三网元对 象。
33、 根据权利要求 31或 32所述的网络管理系统, 其特征在于, 所述 网管前台客户端还用于响应于所述用户创建同步数字传输体制 SDH路径 的操作, 向所述网管后台服务器发出第三指令; 所述第三指令包括源端网 元对象信息、 宿端网元对象信息和指定信息; 所述指定信息包括所创建的 SDH路径应经过的网元对象的信息和 /或不能经过的网元对象的信息; 所述网管后台服务器还用于根据所述源端网元对象的信息、 宿端网元 对象的信息和指定信息, 使用设定的路径计算方法计算出第一 SDH路径, 并向所述网管前台客户端传递所述第一 SDH路径的信息和所述第一 SDH 路径上各网元对象的可用资源信息; 所述第一 SDH路径是计算出的从所 述源端网元对象到所述宿端网元对象的 SDH路径;
所述网管前台客户端还用于接收所述网管后台服务器发送的第一 SDH路径的信息和所述第一 SDH路径上各网元对象的可用资源信息, 并 根据所述第一 SDH路径的信息在所述窗口中显示所述第一 SDH路径, 根 据所述第一 SDH路径上各网元对象的可用资源信息和资源数量门限, 判 断所述第一 SDH路径是否有资源告警, 如果判断结果为有资源告警, 在 所述窗口中显示与所述第一 SDH路径对应的路径告警信息。
34、 根据权利要求 33 所述的网络管理系统, 其特征在于, 所述网管 前台客户端还用于响应于所述用户修改所述第一 SDH路径的操作, 向所 述网管后台服务器发出第四指令; 所述第四指令包括修改所述第一 SDH 路径的操作命令;
所述网管后台服务器还用于根据所述修改所述第一 SDH路径的操作 命令, 重新根据所述源端网元对象的信息、 宿端网元对象的信息和指定信 息, 使用设定的路径计算方法计算出第二 SDH路径, 并向所述网管前台 客户端传递所述第二 SDH路径的信息和所述第二 SDH路径上各网元对象 的可用资源信息; 所述第二 SDH路径是重新计算出的从所述源端网元对 象到所述宿端网元对象的 SDH路径;
所述网管前台客户端还用于接收所述网管后台服务器发送的第二 SDH路径的信息和所述第二 SDH路径上各网元对象的可用资源信息, 并 根据所述第二 SDH路径的信息在所述窗口中显示所述第二 SDH路径。
PCT/CN2012/083664 2012-03-19 2012-10-29 处理3d拓扑视图中网元对象信息的方法及设备 WO2013139123A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP12826658.2A EP2663050B1 (en) 2012-03-19 2012-10-29 Method and device for processing network element object information in 3d topological view
US13/850,627 US8782526B2 (en) 2012-03-19 2013-03-26 Method and device for processing network element object information in 3D topology view
US14/273,750 US9335889B2 (en) 2012-03-19 2014-05-09 Method and device for processing network element object information in 3D topology view

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210072759.1 2012-03-19
CN201210072759.1A CN102638455B (zh) 2012-03-19 2012-03-19 处理3d拓扑视图中网元对象信息的方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/850,627 Continuation US8782526B2 (en) 2012-03-19 2013-03-26 Method and device for processing network element object information in 3D topology view

Publications (1)

Publication Number Publication Date
WO2013139123A1 true WO2013139123A1 (zh) 2013-09-26

Family

ID=46622699

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/083664 WO2013139123A1 (zh) 2012-03-19 2012-10-29 处理3d拓扑视图中网元对象信息的方法及设备

Country Status (3)

Country Link
EP (1) EP2663050B1 (zh)
CN (1) CN102638455B (zh)
WO (1) WO2013139123A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015058595A1 (zh) * 2013-10-24 2015-04-30 中兴通讯股份有限公司 拓扑图中图形的放大方法、装置与计算机存储介质
CN111580723A (zh) * 2014-02-10 2020-08-25 三星电子株式会社 用户终端装置及其显示方法
CN116094938A (zh) * 2023-01-16 2023-05-09 紫光云技术有限公司 基于kafka的网络拓扑同步方法、设备、服务器及存储介质
US11960705B2 (en) 2014-02-10 2024-04-16 Samsung Electronics Co., Ltd. User terminal device and displaying method thereof

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8782526B2 (en) 2012-03-19 2014-07-15 Huawei Technologies Co., Ltd. Method and device for processing network element object information in 3D topology view
CN102638455B (zh) * 2012-03-19 2015-03-11 华为技术有限公司 处理3d拓扑视图中网元对象信息的方法及设备
CN102904751B (zh) * 2012-09-25 2015-11-25 华为软件技术有限公司 网络拓扑视图的生成方法和装置
CN103634147A (zh) * 2013-11-28 2014-03-12 华为技术服务有限公司 一种网络拓扑管理方法及设备
CN106487552A (zh) * 2015-08-27 2017-03-08 中兴通讯股份有限公司 一种网元信息的确定方法、装置及网管拓扑系统
CN111538501B (zh) * 2020-07-10 2020-10-27 北京东方通科技股份有限公司 一种基于人工智能的多元异构网络数据可视化方法及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050223092A1 (en) * 2004-03-30 2005-10-06 Sapiro Lee W System and method providing mapped network object performance information
US20070206512A1 (en) * 2006-03-03 2007-09-06 Nortel Networks Limited Network data model and topology discovery method
CN101060537A (zh) * 2007-06-01 2007-10-24 北京航空航天大学 一种通信网络仿真工具的实时视景显示平台及其实现方法
CN102014403A (zh) * 2009-09-07 2011-04-13 中兴通讯股份有限公司 一种传输网络拓扑信息的方法及系统
CN102136946A (zh) * 2011-03-07 2011-07-27 中国电力科学研究院 一种光网络拓扑图的绘制方法及其拓扑子系统
CN102638455A (zh) * 2012-03-19 2012-08-15 华为技术有限公司 处理3d拓扑视图中网元对象信息的方法及设备

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6732170B2 (en) * 1996-02-13 2004-05-04 Hitachi, Ltd. Network managing method, medium and system
WO2000075788A1 (en) * 1999-05-26 2000-12-14 Fujitsu Network Communications, Inc. Network element management system
US6973622B1 (en) * 2000-09-25 2005-12-06 Wireless Valley Communications, Inc. System and method for design, tracking, measurement, prediction and optimization of data communication networks
JP2002288229A (ja) * 2001-03-23 2002-10-04 Hitachi Ltd マルチレベル構成図情報の表示方法およびシステム
US20070016592A1 (en) * 2005-07-12 2007-01-18 International Business Machines Corporation Enabling real time decoration for customized topology displays
US7698647B2 (en) * 2006-01-30 2010-04-13 Fast-Cat, Llc Portable dataport device and method for retrieving, inter-relating, annotating and managing electronic documents at a point of need
CN101217410B (zh) * 2008-01-07 2010-08-25 杭州华三通信技术有限公司 一种网络拓扑结构的展示方法和设备
GB0819985D0 (en) * 2008-10-31 2008-12-10 Intergence Systems Ltd Network visualistion systems
CN101674197B (zh) * 2009-09-30 2012-01-25 华为技术有限公司 一种网络拓扑图的显示方法、显示装置及系统
US8811199B2 (en) * 2009-11-06 2014-08-19 Rosemount Inc. Location detection in a wireless network
CN102571433B (zh) * 2012-01-11 2014-07-30 华为技术有限公司 呈现网络路径的方法和装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050223092A1 (en) * 2004-03-30 2005-10-06 Sapiro Lee W System and method providing mapped network object performance information
US20070206512A1 (en) * 2006-03-03 2007-09-06 Nortel Networks Limited Network data model and topology discovery method
CN101060537A (zh) * 2007-06-01 2007-10-24 北京航空航天大学 一种通信网络仿真工具的实时视景显示平台及其实现方法
CN102014403A (zh) * 2009-09-07 2011-04-13 中兴通讯股份有限公司 一种传输网络拓扑信息的方法及系统
CN102136946A (zh) * 2011-03-07 2011-07-27 中国电力科学研究院 一种光网络拓扑图的绘制方法及其拓扑子系统
CN102638455A (zh) * 2012-03-19 2012-08-15 华为技术有限公司 处理3d拓扑视图中网元对象信息的方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2663050A4 *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015058595A1 (zh) * 2013-10-24 2015-04-30 中兴通讯股份有限公司 拓扑图中图形的放大方法、装置与计算机存储介质
CN111580723A (zh) * 2014-02-10 2020-08-25 三星电子株式会社 用户终端装置及其显示方法
CN111580723B (zh) * 2014-02-10 2023-09-29 三星电子株式会社 用户终端装置及其显示方法
US11789591B2 (en) 2014-02-10 2023-10-17 Samsung Electronics Co., Ltd. User terminal device and displaying method thereof
US11960705B2 (en) 2014-02-10 2024-04-16 Samsung Electronics Co., Ltd. User terminal device and displaying method thereof
CN116094938A (zh) * 2023-01-16 2023-05-09 紫光云技术有限公司 基于kafka的网络拓扑同步方法、设备、服务器及存储介质
CN116094938B (zh) * 2023-01-16 2024-04-19 紫光云技术有限公司 基于kafka的网络拓扑同步方法、设备、服务器及存储介质

Also Published As

Publication number Publication date
CN102638455A (zh) 2012-08-15
CN102638455B (zh) 2015-03-11
EP2663050B1 (en) 2017-01-11
EP2663050A4 (en) 2014-06-11
EP2663050A1 (en) 2013-11-13

Similar Documents

Publication Publication Date Title
WO2013139123A1 (zh) 处理3d拓扑视图中网元对象信息的方法及设备
US9335889B2 (en) Method and device for processing network element object information in 3D topology view
EP2747340B1 (en) Method and apparatus for presenting network path
US8782265B1 (en) Network visualization system and method of using same
JP6408602B2 (ja) Nfvシステムにおけるサービス実装のための方法および通信ユニット
CN102724138A (zh) 即时通信中的信息共享方法及装置
US20120192075A1 (en) Integrated view of network management data
WO2015165225A1 (zh) 即时消息显示方法和装置
CN103780467B (zh) 通信连接方法、通信装置及通信系统
CN105867864A (zh) 一种kvm显示方法及装置
WO2016101780A1 (zh) 一种虚拟化网络中业务部署的方法和装置
CN105955513A (zh) 信息处理方法、电子设备及无线鼠标
US20160294981A1 (en) Display method and device
WO2016091013A1 (zh) 业务处理方法及装置
CN104133873B (zh) 终端设备、通信系统及其数据处理方法
KR102162834B1 (ko) 멀티클라우드 또는 하이브리드클라우드를 위한 토폴로지 맵 이용 시스템 및 방법
CN114070741A (zh) 一种拓扑图生成方法、系统、设备和存储介质
CN110460456B (zh) 一种管理信息库mib同步生成网络拓扑的方法及装置
CN105553811B (zh) Sdn架构中基于多vtn组合的网络业务实现方法
US10692295B1 (en) Visualization of connectivity amelioration within augmented reality and other user interface environments
EP3070878B1 (en) Performance object aggregation path interface display method and apparatus in integrated network management
US20230209319A1 (en) Communication services ordering and provisioning
CN109976757A (zh) 一种虚拟io服务器的配置方法、装置、设备及介质
US20230275814A1 (en) User interface for 5g network slice provisioning
EP4235425A1 (en) User interface for 5g network slice provisioning

Legal Events

Date Code Title Description
REEP Request for entry into the european phase

Ref document number: 2012826658

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2012826658

Country of ref document: EP

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12826658

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE