TWI653857B - Method and system for topological operation - Google Patents

Abstract

The invention provides a topology operation method and system based on a specification, and defines a topology generation and behavior operation by establishing a topology specification file. The topology specification file covers its topology integration and service integration technology, and establishes a distributed topology merging mechanism on the server based on the topology specification file, and instantly aligns the topology tree according to the client display or operation requirements, which will be effective. Solve the huge problem of topology tree data. The merging mechanism is established on the client and the server, and can be used to offload the topology database of the two ends, and apply the service order operation to associate the point and line relationship of the topology. Using the topology specification file to define the topology display structure can enhance the user's operating experience without affecting the actual service resources.

Description

Topological operation method and system

The present invention relates to a service order operation, and more particularly to a topology operation method and system.

Today, most Internet Service Providers (ISPs) can provide online service applications, so that customers can apply without having to come to the store or service, and they can reduce the labor burden of the operators. However, when users rent or operate network-related functions through web pages, they always need to use layer-by-layer settings, such as adding a firewall and adding, deleting, or changing the list, and then binding or affecting other functions after setting. Settings, other things like load balancing lists and local area networks. Coupled with more and more heterogeneous service sources (for example, virtual or physical network devices with different brands), it is more inconvenient for users to operate.

In view of this, the present invention provides a topology operation method and system, which provides a simple topology operation mode for a client, thereby improving the user experience and improving the power of topology restoration processing through distributed storage.

The topology operation method of the present invention is applicable to a client requesting a service from a server, and the topology operation method includes the following steps. The operation interface is presented on the client side, and the operation interface includes service options. Receiving a service operation for a service option on the operation interface to determine a service demand content, and the service operation is at least one of a new operation, a transaction, and a deletion operation. The service requirement content generates a topology map on the operation interface according to the topology specification file, and the topology specification file defines the location of the service option as a node in the topology map. The service demand content is transmitted to the server to utilize the service demand content for the corresponding provisioning service operation.

The topology operating system of the present invention includes a client, a server, and a service provider. The client renders the operation interface, and this operation interface includes service options. The client receives a service operation for the service interface of the operation interface to determine the content of the service requirement, and the service operation is at least one of a new operation, a transaction, and a deletion operation. The client generates a topology map on the operation interface according to the topology specification file, and the topology specification file defines the location of the service option as a node in the topology map. The client transmits the service demand content to the server. The server obtains the service operation message from the content of the service requirement, so that the service provider can perform the corresponding service operation according to the service.

Based on the above, the embodiment of the present invention defines a topology generation and behavior operation by establishing a topology specification file, covering topology topology and service integration technologies, and establishing a distributed topology consolidation mechanism on the server side according to the topology specification file, according to the client. The display or operation requires an instant consolidation topology tree, which effectively solves the problem of huge topology tree data.

The above described features and advantages of the invention will be apparent from the following description.

1 is a schematic diagram of a topology operating system 1 in accordance with an embodiment of the present invention. The topology operating system 1 includes a server 2, one or more clients 3, and a service provider 4.

The server 2 can be an electronic device such as a computer host, a server, a workstation, and the like, and includes a service order module 21 and a server topology generation module 22 (including a topology generation unit 221, a topology verification unit 222, a topology location calculation unit 223, and a topology). The merging unit 224), the topology specification storage module 23 and the topological distributed storage module 24. The foregoing modules are stored in a storage (for example, a hard disk, a memory, etc.) of the server 2, and are loaded and executed by a processor (for example, a CPU, a micro control unit, a chip, etc.), and the server 2 More networking capabilities (for example, via fiber optic, Ethernet, mobile communication network modules, etc.).

The client 3 can be an electronic device such as a computer host, a smart phone, or a tablet computer, and includes a topology database module 31, a topology display module 32, a topology operation module 33, and a client topology generation module 34 (including topology generation). Unit 341, topological position calculation unit 342, topological consolidation unit 343). The foregoing modules are stored in a storage (for example, a hard disk, a memory, etc.) of the client 3, and are loaded and executed by a processor (for example, a CPU, a micro control unit, a chip, etc.), and the client 3 More networked functions (for example, through fiber optics, Ethernet, mobile communication network modules, etc.) to transfer data to and from the server 2, and display such as LCD, LED, etc. to present the operation interface.

The service supply terminal 4 may be an electronic device such as a computer host, a server, a workstation, etc., which is an application content (for example, services 1, 2, etc.) that determines the service content of the service demand content of the client 3, and performs a corresponding supply service. operating.

In order to facilitate the understanding of the operation flow of the embodiment of the present invention, the operation flow of the topology operating system 1 in the embodiment of the present invention will be described in detail below. 2 is a flow chart illustrating a method of topology operation in accordance with an embodiment of the invention. Referring to FIG. 2, the method of this embodiment is applicable to each device in the topology operating system 1 of FIG. Hereinafter, the methods described in the embodiments of the present invention will be described in conjunction with the components and modules of the topology operating system 1. The various processes of the method can be adjusted accordingly according to the implementation situation, and are not limited thereto.

The topology display module 32 of the client 3 presents an operation interface through its display, and the operation interface includes one or more service options (for example, firewall, Internet access, multimedia value added, etc., depending on the application. And the self-adjustment) allows the user to perform a service operation on the topology map (ie, if it exists, if it does not exist) according to the result displayed by the topology display module 32 (ie, the operation interface), and the topology display module 32 Receiving user service operations (including adding, changing, and deleting operations, etc. on the operation interface, and presenting corresponding options or dragging, clicking, discarding, etc.) on the operation interface to determine The content of the service demand related to the user (for example, adding a subnet of the firewall, adjusting the external network connection, etc.) can transfer the content of the service request related to the service operation to the topology operation module 33 (step S501). The topology operation module 33 determines the operation category of the received service operation (step S502), and if the service operation is a new operation, transmits the service requirement content to the client topology generation module 34, if the service operation is changed or deleted, Step S505.

In response to the need for additional operations, the client topology generation module 34 obtains the topology specification file from the topology specification storage module 23 of the server 2 through its network module (step S503). This topology specification file defines the location of the service option as a node in the topology map (eg, horizontal distance, vertical distance, connection relationship, etc.), so that the client topology generation module 34 can view the service requirement content according to the topology specification file. A topology map is generated on the operation interface (step S6).

3 is a flow chart of the topology generation S6 of the client 3 under the newly added operation. Referring to FIG. 3, the topology generation unit 341 of the client 3 generates a new derived topology or a primary topology by using the topology specification file (step S601), where the client End 3 generates a primary topology for the first time a service option is added, and then a new service option generates a derived topology (which is connected to the node in the primary topology). If it is the main topology, step S605 is performed. If it is a derived topology, the topology generation unit 341 to the topology database module 31 obtains a complete topology tree (step S602). Next, the topological position calculating unit 342 adjusts the position of the new derived topology generated in step S601 in accordance with the topological relative position (step S603). The topology merging unit 343 re-consolidates the topology to the topology tree to generate a complete new topology tree (step S604). It should be noted that the location adjustment and merging mechanisms in steps S603 and S604 are all based on the content definition of the topology specification file. Finally, the topology client topology generation module 34 can generate a primary topology or a derived topology and a complete new topology tree (step S605), wherein if it is the first newly added primary topology, the primary topology is equivalent to the complete new topology tree.

Returning to FIG. 2, the topology client topology generation module 34 then synchronizes the complete topology tree to the topology database module 31 and the topology display module 32, so that the topology display module 32 presents a complete topology tree on the operation interface, and allows The user can immediately see the operational response, and then the topology client topology generation module 34 transmits the derived topology or the primary topology to the topology operation module 33 (step S504). The topology operation module 33 then transmits the identification code of the main topology together with the service operation message (consolidated in the service requirement content) to the service order module 21, and the service operation message may include the input parameters required by the service provider 4; If the service operation is a new operation, the service requirement content is appended with a derived topology or a primary topology; if it is a transaction or deletion operation, a derived topology identifier is added (step S505). In addition, if it is a new operation, the service order module 21 transmits the service demand content to the server topology generation module 22 of the server 2 through its network module (step S506), so that the server topology generation module 22 The service requirement content may also generate a topology map according to the topology specification file (step S7).

4 is a flowchart related to the topology generation S7 of the server 2 under the new operation. Referring to FIG. 4, the topology generation unit 221 generates a new derived topology or a primary topology by using the topology specification file according to the received service requirement content (step S701). ). The topology verification unit 222 compares the derived topology or the primary topology (entrained in the service requirement content) sent by the topology client 3 with the new derived topology or the new primary topology generated by the server 2 in step S701, thereby obtaining the use. The operational parameters entered (ie, the corresponding parameters of the service requirement content) are replaced with the topology map generated by the server 2 (the aforementioned new primary topology or newly derived topology) (step S702). Thereafter, if the service requirement content corresponds to the derived topology, step S703 is performed; and if it corresponds to the primary topology, step S706 is performed. The topological distributed storage module 24 obtains the derived topological group, the primary topology, and the complete topology tree by using the identification code of the primary topology (entrained in the service requirement content) (step S703). The topology calculation unit 223 adjusts the position of the newly derived topology generated by step S701 according to the topological relative position (step 704), and the topology merging unit 224 adds the newly derived topology of the adjusted position to the derived topological group, and the derived topology is The topology tree merges the complete new topology tree (step S705). The topology merging unit 224 performs topology consolidation according to the operational behavior definition of the topology specification file. For example, the operation behavior of the derived topology is connected to a node of the primary topology, and the topology merging unit 224 is between the derived topology and the primary topology. This connection is automatically added to tidy up the topology. It should be noted that the location adjustment and merging mechanism of step S704 and step S705 are both based on the content definition of the topology specification file, and are consistent with the logic of the client 3 generation method. Then, if the primary topology, the server topology generation module 22 generates the primary topology and the complete new topology tree, where the primary topology content is equivalent to the complete new topology tree; if it is the derived topology, the server topology generation module 22 The output includes a derived topology, a derived topological group, and a complete new topology tree (step S706) (in other words, the complete new topology tree records the contents of the primary topology and the derived topological group).

Please return to FIG. 2, the service order module 21 obtains the service operation message from the service request, and transmits the service operation message to the service supply terminal 4 through the network module for actual supply, transaction or deletion. Service operations (for example, assigning work orders, changing lines, new services, etc., depending on the needs and fields of the application); if it is a new service operation after completion, the server topology generation module 22 will The generated result is synchronized to the topological decentralized storage module 24, and the result includes a derived topology or a primary topology and a complete topology tree, and the new primary topology and the derived topology group are decentralized; if it is a transaction or a deletion service, the service The end topology generation module 22 synchronizes only its service operations to the topological distributed storage module 24, and notifies the service order module 21 to complete the topology operation (step S507). Then, the service order module 21 can notify the topology operation module 33 of the client 3 that the service order operation has been completed (step S508).

It should be noted that one of the purposes of the foregoing distributed storage is to increase the rate of restoring the topology tree. In the case that the complete topology tree is to be re-acquired, the topological distributed storage module 24 can take out the main identifier according to the identification code of the primary topology. The topology and related derived topological groups can be combined and restored into a complete existing topology tree. In addition, in the foregoing topology generation step S7, the topology ordination unit 224 may merge the new primary topology or the newly derived topology into the existing topology tree to form a new topology tree.

In order to help the reader to understand the embodiment of the present invention, an example will be described below. However, it is worth noting that the parameters and application scenarios used in the examples can be adjusted according to the requirements.

First, the user can obtain complete topology information (that is, the topology tree presented by the topology map) from the topology display module 32, and add and change service options through the operation interface presented on the display of the client 3. Or delete the operation. If it is a transaction or deletion operation, the client 3 directly transmits the relevant operation message together with the identification code of the main topology and the topology related information (such as the derived topology identification code) to the service order module 21 of the topology server 2; In the service operation, the client topology generation module 34 obtains the topology specification file from the topology specification storage module 23, and generates a topology map according to a predefined rule, and the rules may include generating a unique identification code and filling in the parameters input by the user. Values, additional auxiliary parameters such as visible or deletable, etc., are displayed, and the results are shown on the left in Figures 5 and 6. If the service is added for the first time, the main topology specification file is obtained, and then the new topology specification file is added. Taking network operation as an example, the user added a virtual private cloud service for the first time. The specification file is shown in Figure 5. Thereafter, if the user adds a new service to the virtual private cloud, the derived topology specification file is obtained. For example, a sub-network service is added, and the specification file is as shown in FIG. 6. The topology specification file structure is shown in formula (1): category (category) = string (string) vertex set =[ vertex ₁ , vertex ₂ ,..., vertex _n ] edge set =[ edge ₁ , edge ₂ ,..., Edge _m ] behavior set =[ behavior ₁ , behavior ₂ ,..., behavior _l ]...(1) vertex is the information of the topological point, including the identification code, category and relative position definition, horizontal distance ( hLevel ) and vertical distance ( vLevel) ), edge is the information of the topological line, which contains the source ( from ) and destination ( to ) information, and the associated deletion behavior trigger; when the source is deleted ( onFromDelete ), its cascade is associated with the deletion destination; when the destination When deleted ( onToDelete ), its cascade is the source of the associated deletion, and its value can be cascade or none (do not perform the delete). behavior defined topology information to conduct the operation module, which defines the topology of the operation of the operation module 33 acts as a trigger boxes (dnd, drag and drop) application interfaces api trigger. According to the specification file, the client topology generation module 24 generates the topology specification file as a topology map, and the generated result is shown in FIG. 5 and FIG. 6, and in addition to generating the unique identification code, the relative position information of the topology specification file is converted into The relative position of the topology map, as shown in equation (2): 1 hLevel distance = var1 1 vLevel distance = var2 a vertax ={ hLevel :0, vLevel : 1 } a vertax ={ x : hLevel * var1 , y : vLevel * var2 }...(2) var1 and var2 are variables , distance is distance, and x and y are coordinates.

If the new primary topology is added, step S605 is directly performed, for example, a virtual private cloud service is added; if a new derivative network is added, for example, a new subnet service is added, a complete topology tree is obtained through the topology database 31 (for example, The left side of Figure 7 is shown, and the derived topology is merged into this complete topology tree (shown on the right side of Figure 7). The topological position calculation unit 342 adjusts the topological position of the derived topology according to the position of the topology tree, and the topology consolidation unit 343 performs final integration. It is worth noting that the position adjustment and merging mechanism will perform position adjustment and consolidation based on the behavior definition of the topology specification file. As defined in the topology specification file of Figure 6, the subnet node is connected to the firewall node and is at the bottom of the firewall . ( bottom ), the value can be top ( top ), bottom ( bottom ), left ( left ) and right ( right ) , the final topology of the complete topology tree shown in Figure 7 on the left, if you add another For the subnet service, the complete topology tree is shown in the right figure of Figure 7. For example, the action behavior is defined as a drag ( dnd ) action, and the position is set to the bottom ( bottom ), and the position of the node displacement is below, as shown in Figures 5 and 6. If the topological position calculation unit 342 finds that the relative position of the derived topology overlaps with a node in the topology tree, it will perform readjustment until it overlaps, and the adjustment mode can be horizontally adjusted or vertically adjusted, and the horizontal adjustment is as shown in the formula (3). The vertical adjustment is shown in equation (4): adjustment distance = var1 vertex ={ x' : x + var1 , y : y }...(3) adjustment distance = var1 vertex ={ x : x , y' : y + var1} ... (4) adjustment Representative adjustment, x ', y' coordinate after the adjustment of the representative.

After the client 3 completes its operation of adding, changing, or deleting the service, the content of the service requirement can be transmitted to the server 2. If it is a new service, the service order module 21 transmits relevant information to the topology server topology generation module 22, and the generation principle is the same as that of the client topology generation module 34, and the difference is that the server 2 will According to the self-generated topology map, the parameters transmitted by the client 3 are taken instead. For example, if the name of a node on the topology map transmitted by the client 3 is subnet1 and the identifier is subnet-001 , the server 2 will take the subnet1 name value instead of the derived topology or the primary topology generated by the server 2. The node whose internal node ID is subnet-001 is not replaced if the identification code is different, in case the topology map is falsified. Then, if it is a new primary topology, the server 2 directly proceeds to step S706; if it is a new derivative topology, the server 2 proceeds to step S703. The topological distributed storage module 24 obtains the derived topological group, the primary topology, and the complete topology tree by using the identifier of the primary topology sent by the client 3, and the topological location calculating unit 223 adjusts the new derived topology according to the position of the complete topology tree. The position of the subnet-002 and the instances-002 node originally generated by the specification file is 100, but the original position has been occupied by subnet-001 and instance-001 , so the location is ( 3) Perform position shift adjustment. After the adjustment, the server topology generation module 22 adds the derived topology to the derived topology group, and generates a complete new topology tree through the topology consolidation unit 224. If the primary topology, the server topology generation module 22 generates the primary topology and the complete topology tree; if it is a derived topology, the server topology generation module 22 outputs the derived topology, the derived topology group, and the complete topology tree. The overall operation process of the service order module 21 to the server topology generation module 22 is as shown in FIG. 8. The order service operation (ie, the service operation is activated for the service option) is used to bind the topology map to achieve separation of service entities. For the purpose of loading and topological pictures, for example, the firewall may actually need to store multiple information records. In this way, you only need to display a firewall node on the screen (as shown on the left), or you can add virtual points to assist. User operation. The order operation map will be used to bind the topology map, so that the actual installation result does not need to be exposed on the operation interface of the client 3, and the topology map display can hide or highlight the information to be expressed. 9 is shown.

If the service order is a new operation in step S507, the topological distributed storage module 24 stores the derived topological group or the primary topology generated in step S7, and the topologically distributed storage mode is as shown in FIG. 10 (assumed topology) The decentralized storage module 24 has a storage library 1, 2). Through the service operation order binding topology diagram, the complete topology tree is disassembled into the main topology and the derived topology to achieve the purpose of separate storage. In addition, if the complete topology tree needs to be re-read, please refer to FIG. 411. Then, through the topology merging method, the topological distributed storage module 24 can also take out the main topology and the derived topology from the storage libraries 1 and 2, respectively, and restore to The original topology tree. In addition, if the service order is a transaction or delete operation, please refer to Figure 12, and the topology map can be synchronized by the service operation order binding topology diagram. Finally, when the service order operation is completed, the server 2 can notify the topology operation module 33 of the client 3 to let the user know that the job is completed.

In summary, the embodiment of the present invention defines the topology generation and behavior operation by the topology specification file, and the topology specification file is applied to the topology integration and service integration technology, and establishes a distributed topology consolidation mechanism on the server side, and The client can display the topology tree in real time according to the operation behavior, thus effectively solving the problem of huge topology tree data. Since both the client and the server use the same topology specification file, the operation screen topology generation speed and the enhanced drag experience can be accelerated, and the server performs topology verification and maintains the data structure. In addition, the merging mechanism is established on both the client and the server. It can not only divert the topology database of the two ends, but also apply the point-to-line relationship of the service order operation topology. Without affecting the actual service resources, Use the specification to define the topology display structure to enhance the user's operating experience and maintain consistency in the behavior of the supply behavior.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention, and any one of ordinary skill in the art can make some changes and refinements without departing from the spirit and scope of the present invention. The scope of the invention is defined by the scope of the appended claims.

1‧‧‧Topology operating system

2‧‧‧ server

21‧‧‧Service Order Module

22‧‧‧Server Topology Generation Module

221‧‧‧Topology generation unit

222‧‧‧Topology verification unit

223‧‧‧Topological position calculation unit

224‧‧‧Topological unit

23‧‧‧Topological Specifications Storage Module

24‧‧‧Topology Distributed Storage Module

3‧‧‧Client

31‧‧‧Topology database module

32‧‧‧Topology display module

33‧‧‧Topology operation module

34‧‧‧Client Topology Generation Module

341‧‧‧Topology generator

342‧‧‧Topological position calculation unit

343‧‧‧Topological unit

4‧‧‧Service supply end

S501~S508, S6, S601~S605, S7, S701~S706‧‧‧ steps

1 is a schematic diagram of a topology operating system in accordance with an embodiment of the present invention. 2 is a flow chart of a method of topology operation in accordance with an embodiment of the present invention. 3 is a flow chart of topology generation of a client according to an embodiment of the invention. 4 is a flow chart of topology generation of a server according to an embodiment of the invention. Figure 5 is a topological diagram illustrating the topology specification file and generation. Figure 6 is another topological diagram illustrating the topology specification file and generation. FIG. 7 is a further illustration of a topological profile and generated topology diagram. FIG. 8 is a diagram illustrating an operation procedure of a server to generate a new topology tree. FIG. 9 is a diagram illustrating the main topology of the server and the integration of the derived topological group. FIG. 10 is a diagram illustrating a server that performs distributed storage. Figure 11 is a reduction of an example topology tree. FIG. 12 is a flowchart showing a rendering operation of a deletion operation on a topology map.

Claims (10)

A topology operation method is applicable to a client requesting a service request to a server, the topology operation method comprising: presenting an operation interface to the client, wherein the operation interface includes at least one service option; receiving the operation interface At least one service option service operation to determine a service demand content, wherein the service operation is at least one of a new operation, a transaction change, and a deletion operation; generating a topology on the operation interface according to a service specification content according to a topology specification file a map, wherein the topology specification file defines a location of the at least one service option as the at least one node in the topology map; and transmitting the service requirement content to the server to utilize the service requirement content for a corresponding provisioning service operation . The topology operation method of claim 1, wherein the topology map includes a topology tree, and the step of generating the topology map on the operation interface according to the topology specification file according to the topology specification file includes: The service operation is a new operation, and a primary topology or a derived topology is generated, where the derived topology is connected to a node in the primary topology; if the service operation is the transaction or the deletion operation, the transaction is changed or deleted. And merging the derived topology to the topology tree. The topology operation method of claim 2, wherein the service requirement content includes the primary topology or the derived topology, and after the service requirement content is transmitted to the server, the method further comprises: the server is received according to the The service requirement content and the topology specification file generate a new primary topology or a new derived topology; comparing the new primary topology or the newly derived topology with the received primary topology or the derived topology to obtain the service requirement content Corresponding parameters; and parameters corresponding to the new primary topology or the newly derived topology according to corresponding parameters of the service requirement content. The topology operation method of claim 3, wherein after replacing the new primary topology or the parameters of the newly derived topology according to the corresponding parameter of the service requirement content, the method further includes: according to the new primary topology or the newly derived topology Generating a new topology tree, wherein the new topology tree records the new primary topology and joins one of the newly derived topologies to derive a topological group; and decentralizes the new primary topology and the derived topological group. The method of claim 3, wherein the service requirement content includes an identifier of the primary topology, and the step of generating the new topology tree according to the new primary topology or the newly derived topology comprises: The existing primary topology of the distributed storage or the existing derived topological group is restored to an existing topology tree; and the new primary topology or the newly derived topology is integrated into the existing topology tree to form the new topology tree. A topology operating system, comprising: a client, presenting an operation interface, wherein the operation interface includes at least one service option; receiving a service operation for the at least one service option on the operation interface to determine a service requirement content, where The service operation system is configured to generate at least one of a new operation, a transaction, and a deletion operation. The service requirement content generates a topology map on the operation interface according to a topology specification file, where the topology specification file defines the at least one service option as the at least one node. And the location in the topology map; and transmitting the service requirement content; a server, obtaining a service operation message from the service requirement content; and a service provider, performing a corresponding installation service operation according to the service operation message. The topology operating system of claim 6, wherein the topology map includes a topology tree, and if the service operation is the new operation, the client generates a primary topology or a derived topology, wherein the derivative The topology is connected to the node in the primary topology; if the service operation is the transaction or the deletion operation, the client changes or deletes the derived topology; and the client merges the derived topology to the topology tree. The topological operating system of claim 7, wherein the service requirement content includes the primary topology or the derived topology, and the server generates a new primary topology according to the received service requirement content and the topology specification file. Or a new derived topology, comparing the new primary topology or the newly derived topology with the received primary topology or the derived topology to obtain a corresponding parameter of the service requirement content, and replacing the corresponding parameter according to the service requirement content The new primary topology or the parameters of the newly derived topology. The topology operating system of claim 8, wherein the server generates a new topology tree according to the new primary topology or the newly derived topology, wherein the new topology tree records the new primary topology and joins the new derived topology. One of the derived topological groups, the server and the new primary topology and the derived topological group are stored in a distributed manner. The topology operating system of claim 9, wherein the service requirement content includes an identifier of the primary topology, and the server restores the existing primary topology or the existing derived topology group of the previously distributed storage to an existing one. The topology tree is merged into the existing topology tree or the newly derived topology to form the new topology tree.