WO2021027652A1 - 一种基于虚拟组件的场景式割接方法和系统 - Google Patents
一种基于虚拟组件的场景式割接方法和系统 Download PDFInfo
- Publication number
- WO2021027652A1 WO2021027652A1 PCT/CN2020/107102 CN2020107102W WO2021027652A1 WO 2021027652 A1 WO2021027652 A1 WO 2021027652A1 CN 2020107102 W CN2020107102 W CN 2020107102W WO 2021027652 A1 WO2021027652 A1 WO 2021027652A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- topology
- components
- virtual
- component
- transaction
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0859—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
- H04L41/0863—Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions by rolling back to previous configuration versions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
- H04L41/122—Discovery or management of network topologies of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/085—Retrieval of network configuration; Tracking network configuration history
- H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information
Definitions
- the invention relates to the technical field of network management and control of a telecommunication transmission network, and in particular to a scene type cutover method and system based on virtual components.
- the topology of the existing network is often changed, such as adding or reducing network elements, single disks, and connecting fibers for expansion and contraction; for example, to transform the convergence ring, increase or decrease the ring Upper node; for example, to replace old equipment with new equipment to replace network elements and single disks.
- the existing network topology often has telecommunications services running. In order to minimize the scope of telecommunications services affected by topology changes, these telecommunications services need to be cut over. Telecommunication service cutover refers to avoiding reconfiguration of new telecommunication services by adjusting partial telecommunication services to adapt to the new topology as much as possible, thereby saving the time for opening telecommunication services on the new topology.
- the main processing process of the prior art is to use the database for backup. If an error occurs during the cutover, the topology and telecommunication services are rolled back to the point of backup; the second is to change the topology and cause damage to the telecommunication services, and then follow the new topology.
- the problem with this is that the use of database backup in process one is a way of overall backup, and the process of backup and rollback is not efficient. There are multiple backups under multi-user operations, and there are multiple versions between backups.
- the purpose of the present invention is to provide a scenario-based cutover method and system based on virtual components to meet diversified cutover requirements.
- a virtual component-based scene cutover method including the following steps:
- saving the topology component in the transaction cache and creating a virtual component in the transaction cache includes the following steps:
- the correspondence between the topology component and the virtual component in the current basic scene is added to the transaction cache.
- the telecommunication services that need to be adjusted are stored in the transaction buffer, and the telecommunication services are adjusted according to the topology components and virtual components, which specifically include the following steps:
- the transaction buffer is rolled back to restore the telecom service to the level before adjustment without changing the topology, which specifically includes the following steps:
- the present invention provides a scene type cutover system based on virtual components, including:
- the scene decomposition module is used to: decompose the telecommunication service to be adjusted into multiple basic scenes to cutover each basic scene in turn; obtain the topology component information on the physical topology that needs to be locked corresponding to the current basic scene , The virtual component information to be created and the relationship between the topology component and the virtual component;
- the topology cache module is used to: for the current basic scene, save the topology component in the transaction cache, and create virtual components in the transaction cache;
- the service adjustment module is used to: save the telecommunications services that need to be adjusted in the transaction buffer, and adjust the telecommunications services according to the topology components and virtual components; when there is no error in the adjustment, submit the transaction buffer, and save the adjusted telecommunications services to Database and change the topology; when an adjustment error occurs, the transaction cache is rolled back to restore the telecommunications business to before the adjustment without changing the topology.
- the topology cache module saves the topology component in the transaction cache for the current basic scene, and creates a virtual component in the transaction cache, which specifically includes the following steps:
- the correspondence between the topology component and the virtual component in the current basic scene is added to the transaction cache.
- the service adjustment module saves the telecommunication services that need to be adjusted in the transaction buffer, and adjusts the telecommunication services according to the topology component and the virtual component, which specifically includes the following steps:
- the service adjustment module submits the transaction buffer, saves the adjusted telecommunication service and changes the topology, which specifically includes the following steps:
- the service adjustment module rolls back the transaction buffer and restores the telecommunication service before adjustment without changing the topology, which specifically includes the following steps:
- the invention adopts virtual components, adjusts the telecommunication service first without changing the topology, and then changes the topology after success, ensuring the integrity of the topology and the telecommunication service without fragmentation; using the compensation type transaction mode, In the case of an error in the cutover process, the topology and telecom services are rolled back to improve the rollback efficiency; the basic scenes for cutover are designed, and the basic scenes are combined through a unified framework to realize complex scenes and respond to diversified cutover requirements , To realize the customization and diversification of user cutover scenarios, and improve the scalability of the system.
- FIG. 1 is a schematic flowchart of a scenario-based cutover method based on virtual components according to an embodiment of the present invention
- step S2 of a virtual component-based scene cutover method according to an embodiment of the present invention
- step S3 is a schematic flowchart of step S3 of a virtual component-based scene cutover method according to an embodiment of the present invention
- step S6 of a virtual component-based scene cutover method according to an embodiment of the present invention
- FIG. 5 is a schematic flowchart of step S7 of the scenario cutover method based on virtual components according to an embodiment of the present invention.
- the embodiment of the present invention provides a scenario-based cutover method based on virtual components, including the following steps:
- the order of cutover for each basic scene is determined according to the order of each basic scene required to realize the complex scene.
- saving the topology component in the transaction cache and creating a virtual component in the transaction cache specifically includes the following steps:
- the correspondence between the topology component and the virtual component in the current basic scene is added to the transaction cache.
- storing the telecommunication services that need to be adjusted in the transaction buffer, and adjusting the telecommunication services according to the topology components and virtual components specifically includes the following steps:
- submitting the transaction cache, saving the adjusted telecommunication service to the database and changing the topology specifically includes the following steps:
- rolling back the transaction buffer and restoring the telecommunication service to before adjustment without changing the topology includes the following steps:
- the scenario-based cutover method based on virtual components specifically includes the following steps:
- Step S1 Decompose the complex scene into multiple basic scenes, and cutover each basic scene in turn;
- Step S2 for the current basic scene, establish a transaction cache of the topology component and the virtual component;
- Step S3 For the current basic scenario, establish a transaction buffer for the telecommunication service, and then adjust the telecommunication service.
- Step S4 If there is no error, go to S5; if the above process goes wrong, go to S6;
- Step S5. If there is still a basic scene, return to S2 to continue execution; if there is no basic scene, go to S7;
- Step S6 Roll back the transaction buffer, and the telecommunication service is restored to before the adjustment without changing the topology; the process ends.
- Step S7 Submit the transaction buffer, save the adjusted telecommunication service in the database, and change the topology accordingly; end the process.
- Step S1 Decompose the complex scene into multiple basic scenes, and cutover each basic scene in turn;
- complex scenes can be composed of several basic scenes in sequence. As shown in the following table:
- the routing format in the third column example in Table 1 is unified. The first is a letter for network elements, the second is a number for ports, -> indicates fiber connection, and * indicates an unknown route after the change. For example, B1 B2 indicates Port 1 and port 2 of NE B.
- Step S2 for the current basic scene, establish a transaction cache of the topology component and the virtual component;
- the types of virtual components are virtual single disk and virtual fiber connection, as shown in the following table:
- Topology components ⁇ user ID, ⁇ A1->B1,B2->C1>>
- Virtual component ⁇ user ID, ⁇ A1->D1, D2->C1>>
- topology components ⁇ user ID, ⁇ (A1->B1,A1->D1), (B2->C1, D2->C1)>>
- step S2 specifically includes the following steps:
- Step S21 Acquire the topology component in the current basic scene, and add the topology component to the topology component set in the transaction cache ⁇ user ID, topology component set>;
- the topology components are recorded in the transaction cache in the form of user IDs, and other users cannot modify these topology components, which ensures the mutual exclusion of topology component access.
- the ⁇ user ID, ⁇ A1->B1, B2->C1>>, A1->B1 and B2->C1 are locked and other users cannot modify it.
- Step S22 Obtain virtual components in the current basic scene, and add virtual components to the virtual component set in the transaction cache ⁇ user ID, virtual component set>;
- the virtual components are recorded in the transaction cache in the form of user IDs, and users can only use the virtual components recorded in the transaction cache by themselves, and cannot access virtual components created by other users, ensuring the isolation of virtual components.
- ⁇ user ID, ⁇ A1->D1, D2->C1>>, A1->D1 and D2->C1 are two virtual fiber connections, which only exist in the transaction cache, and only the user can access.
- Step S23 Obtain the corresponding relationship between the topology component and the virtual component in the current basic scene.
- the transaction cache ⁇ user ID, ⁇ topology component ID, virtual component ID> set>, ⁇ user ID, ⁇ topology component ID, virtual Add the correspondence between topological components and virtual components in the component ID>> set.
- the corresponding relationship between the topology component and the virtual component is recorded in the form of the user ID, that is, the relationship that the topology component can be replaced by the virtual component.
- Topological components and virtual components may have a one-to-one correspondence, or a relationship where one topology component corresponds to multiple virtual components, or multiple topological components correspond to one virtual component. For example, in the process of LAG port processing, corresponding to the original connecting fiber, it may become two connecting fibers; it is also possible that the original multiple connecting fibers become one connecting fiber.
- the topology component A1->B1 corresponds to the virtual component A1->D1 ;
- the topology component B2->C1 corresponds to the virtual component D2->C1.
- Step S3 For the current basic scenario, establish a transaction buffer for the telecommunication service, and then adjust the telecommunication service.
- the telecommunication service was originally on the topological component. Since the topological component needs to be replaced with a virtual component after the cutover, the telecommunication service must be adjusted to the virtual component first. If no virtual components are created in the basic scenario, then the telecommunication service does not need to be adjusted to virtual components, but to other topological components.
- the telecommunication services A1->B1 B2->C1 in the above example need to be adjusted from the topology components A1->B1, B2->C1 to the virtual components A1->D1, D2->C1.
- step S3 specifically includes the following steps:
- the telecommunication service is saved in the transaction buffer before the corresponding telecommunication service is processed.
- the telecommunication service here refers to the telecommunication service that is affected by modifying the topology component or avoiding the point of failure in the basic scenario.
- the telecommunication service A1->B1 B2->C1 in the above example is stored in the transaction buffer of the telecommunication service as follows:
- the transaction cache of the virtual component is not empty, so jump to S34.
- the corresponding basic scenario does not need to create virtual components, and only needs to adjust the telecommunication services according to the real physical topology, that is, adjust the telecommunication services from the original topology components to other topology components.
- the corresponding basic scenario needs to create a virtual component, adjust the telecommunication service from the original topology component to the virtual component, that is, modify the topological component data in the telecommunication service, and replace it with the virtual component data according to the corresponding relationship.
- the telecom service A1->B1 B2->C1 in the above example the topology components in it are based on the relationship between topology components and virtual components ⁇ user ID, ⁇ (A1->B1,A1->D1), (B2->C1 , D2->C1)>> is replaced with a virtual component, that is, a new telecommunication service A1->D1 D2->C1 is formed.
- the configuration data of this telecommunication service is generated on the virtual components A1->D1, D2->C1.
- Step S4 If there is no error, go to S5; if the above process goes wrong, go to S6;
- Step S5. If there is still a basic scene, return to S2 to continue execution; if there is no basic scene, go to S7;
- this step it is judged whether the basic scenes composing the complex scene have been executed, and these basic scenes are executed in sequence to complete the execution of the complex scene.
- Step S6 Roll back the transaction buffer, and the telecommunication service is restored to before the adjustment without changing the topology; the process ends.
- the user restores to the state before the user performs the cutover by rolling back the transaction cache, and the scope of influence is limited to the cutover scenario executed by the user.
- step S6 specifically includes the following steps:
- the user's telecommunication services before adjustment are retrieved from the transaction cache, and the telecommunication services adjusted to the virtual component are restored to these telecommunication services before adjustment.
- the configuration data of the telecommunication service on the virtual components A1->D1, D2->C1 are cleared.
- Step S7 Submit the transaction buffer, save the adjusted telecommunication service in the database, and change the topology accordingly; end the process.
- step S7 specifically includes the following steps:
- the telecommunication service adjusted to the virtual component is saved in the database, that is, the new telecommunication service after the topology component in the telecommunication service is replaced with the virtual component is saved in the database.
- the new telecommunication services A1->D1 D2->C1 are saved to the database.
- the embodiment of the present invention also provides a scenario-based cutover system based on virtual components, including:
- the scene decomposition module is used to: decompose the telecommunication service to be adjusted into multiple basic scenes to cutover each basic scene in turn; obtain the topology component information on the physical topology that needs to be locked corresponding to the current basic scene , The virtual component information to be created and the relationship between the topology component and the virtual component;
- the topology cache module is used to: for the current basic scene, save the topology component in the transaction cache, and create virtual components in the transaction cache;
- the service adjustment module is used to: save the telecommunications services that need to be adjusted in the transaction buffer, and adjust the telecommunications services according to the topology components and virtual components; when there is no error in the adjustment, submit the transaction buffer and save the adjusted telecommunications services Go to the database and change the topology; when an adjustment error occurs, the transaction cache is rolled back, and the telecommunication service is restored to before the adjustment without changing the topology.
- the topology cache module saves the topology component in the transaction cache for the current basic scene, and creates a virtual component in the transaction cache, which specifically includes the following steps:
- the correspondence between the topology component and the virtual component in the current basic scene is added to the transaction cache.
- the service adjustment module saves the telecommunication services that need to be adjusted in the transaction buffer, and adjusts the telecommunication services according to the topology component and the virtual component, which specifically includes the following steps:
- the service adjustment module submits the transaction buffer, saves the adjusted telecommunication service in the database and changes the topology, which specifically includes the following steps:
- the service adjustment module rolls back the transaction buffer and restores the telecommunication service to before adjustment without changing the topology, which specifically includes the following steps:
- the embodiments of the present application provide a computer-readable storage medium on which a computer program is stored.
- the computer program is executed by a processor, all the method steps or some methods of the scenario-based cutover method based on virtual components are implemented step.
- the present invention implements all or part of the process in the above virtual component-based scene cutover method, and can also be completed by instructing relevant hardware through a computer program.
- the computer program can be stored in a computer-readable storage medium. When executed by the processor, the steps of the foregoing method embodiments can be implemented.
- the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file, or some intermediate forms.
- Computer-readable media may include: any entity or device capable of carrying computer program code, recording media, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access Memory (RAM, Random Access Memory), electric carrier signal, telecommunications signal, software distribution medium, etc.
- computer-readable media can be appropriately added or deleted according to the requirements of the legislation and patent practice in the jurisdiction.
- computer-readable media does not include Electric carrier signal and telecommunications signal.
- an embodiment of the present application also provides an electronic device, including a memory and a processor, and a computer program running on the processor is stored in the memory.
- a scenario-based cutover based on virtual components is implemented. All or part of the method steps in the method.
- the so-called processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (Digital Signal Proc essor, DSP), application specific integrated circuits (ASIC) , Ready-made programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
- the general-purpose processor may be a microprocessor, or the processor may also be any conventional processor, etc.
- the processor is the control center of the computer device, and various interfaces and lines are used to connect various parts of the entire computer device.
- the memory may be used to store computer programs and/or modules, and the processor implements various functions of the computer device by running or executing the computer programs and/or modules stored in the memory and calling data stored in the memory.
- the memory may mainly include a storage program area and a storage data area, where the storage program area can store the operating system, at least one application program (such as sound playback function, image playback function, etc.) required by the function; the storage data area can be stored according to the mobile phone Use the created data (such as audio data, video data, etc.).
- the memory may include high-speed random access memory, and may also include non-volatile memory, such as hard disks, memory, plug-in hard disks, smart media cards (SMC), and secure digital (SD) cards. , Flash Card, at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
- the embodiments of the present invention can be provided as methods, systems, servers, or computer program products. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes.
- These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
- the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
- These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
- the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims (10)
- 一种基于虚拟组件的场景式割接方法,其特征在于,包括以下步骤:将待调整的电信业务分解为多个基本场景,依次对每个基本场景进行割接;获取当前的基本场景对应的需要锁定的物理拓扑上的拓扑组件信息、需要创建的虚拟组件信息以及拓扑组件与虚拟组件之间的关系;对于当前的基本场景,将拓扑组件保存到事务缓存中,并在事务缓存中创建虚拟组件;将需要调整的电信业务保存到事务缓存中,根据拓扑组件和虚拟组件,进行电信业务的调整;调整没有出错时,提交事务缓存,将调整后的电信业务保存至数据库并改变拓扑;调整出错时,回滚事务缓存,将电信业务恢复到调整前,不改变拓扑。
- 如权利要求1所述的方法,其特征在于,对于当前的基本场景,将拓扑组件保存到事务缓存中,并在事务缓存中创建虚拟组件,具体包括以下步骤:获取当前基本场景中需要锁定的拓扑组件信息,在事务缓存中的拓扑组件集合中增加需要锁定的拓扑组件;获取当前基本场景中需要创建的虚拟组件信息,在事务缓存中的虚拟组件集合中增加虚拟组件;根据获取的当前基本场景中的拓扑组件与虚拟组件的对应关系,在事务缓存中增加拓扑组件与虚拟组件的对应关系。
- 如权利要求1所述的方法,其特征在于,将需要调整的电信业务保存到事务缓存中,根据拓扑组件和虚拟组件,进行电信业务的调整,具体包括以下步骤:将基本场景中需要调整的电信业务保存到事务缓存中;如果基本场景没有虚拟组件,根据物理拓扑上的拓扑组件来调整电信业务;如果基本场景有虚拟组件,根据事务缓存中拓扑组件与虚拟组件的对应关系,将电信业务中拓扑组件的数据替换成虚拟组件的数据;在虚拟组件上生成该电信业务的配置数据。
- 如权利要求1所述的方法,其特征在于,提交事务缓存,保存调整后的电信业务并改变拓扑,具体包括以下步骤:将调整后的电信业务保存至数据库;将虚拟组件转换为拓扑组件并保存至数据库;从事务缓存中清除调整前的电信业务;从事务缓存中清除拓扑组件、虚拟组件以及拓扑组件与虚拟组件之间的关系。
- 如权利要求1所述的方法,其特征在于,回滚事务缓存,将电信业务恢复到调整前,不改变拓扑,具体包括以下步骤:从事务缓存中恢复到调整前的电信业务;清除虚拟组件上的电信业务的配置数据;从事务缓存中清除调整前的电信业务;从事务缓存中清除拓扑组件、虚拟组件以及拓扑组件与虚拟组件之间的关系。
- 一种基于虚拟组件的场景式割接系统,其特征在于,包括:场景分解模块,其用于:将待调整的电信业务分解为多个基本场景,用以依次对每个基本场景进行割接;获取当前的基本场景对应的需要锁定的物理拓扑上的拓扑组件信息、需要创建的虚拟组件信息以及拓扑组件与虚拟组件之间的关系;拓扑缓存模块,其用于:对于当前的基本场景,将拓扑组件保存到事务缓存中,并在事务缓存中创建虚拟组件;业务调整模块,其用于:将需要调整的电信业务保存到事务缓存中,根据拓扑组件和虚拟组件,进行电信业务的调整;调整没有出错时,提交事务缓存,将调整后的电信业务保存至数据库并改变拓扑;调整出错时,回滚事务缓存,将电信业务恢复到调整前,不改变拓扑。
- 如权利要求6所述的系统,其特征在于,所述拓扑缓存模块对于当前的基本场景,将拓扑组件保存到事务缓存中,并在事务缓存中创建虚拟组件,具体包括以下步骤:获取当前基本场景中需要锁定的拓扑组件信息,在事务缓存中的拓扑组件集合中增加需要锁定的拓扑组件;获取当前基本场景中需要创建的虚拟组件信息,在事务缓存中的虚拟组件集合中增加虚拟组件;根据获取的当前基本场景中的拓扑组件与虚拟组件的对应关系,在事务缓存中增加拓扑组件与虚拟组件的对应关系。
- 如权利要求6所述的系统,其特征在于,所述业务调整模块将需要调整的电信业务保存到事务缓存中,根据拓扑组件和虚拟组件,进行电信业务的调整,具体包括以下步骤:将基本场景中需要调整的电信业务保存到事务缓存中;如果基本场景没有虚拟组件,根据物理拓扑上的拓扑组件来调整电信业务;如果基本场景有虚拟组件,根据事务缓存中拓扑组件与虚拟组件的对应关系,将电信业务中拓扑组件的数据替换成虚拟组件的数据;在虚拟组件上生成该电信业务的配置数据。
- 如权利要求6所述的系统,其特征在于,所述业务调整模块 提交事务缓存,保存调整后的电信业务并改变拓扑,具体包括以下步骤:将调整后的电信业务保存至数据库;将虚拟组件转换为拓扑组件并保存至数据库;从事务缓存中清除调整前的电信业务;从事务缓存中清除拓扑组件、虚拟组件以及拓扑组件与虚拟组件之间的关系。
- 如权利要求6所述的系统,其特征在于,所述业务调整模块回滚事务缓存,将电信业务恢复到调整前,不改变拓扑,具体包括以下步骤:从事务缓存中恢复到调整前的电信业务;清除虚拟组件上的电信业务的配置数据;从事务缓存中清除调整前的电信业务;从事务缓存中清除拓扑组件、虚拟组件以及拓扑组件与虚拟组件之间的关系。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BR112022001268A BR112022001268A2 (pt) | 2019-08-09 | 2020-08-05 | Método e sistema de transição do tipo cena com base em um componente virtual |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910735688.0A CN112350843B (zh) | 2019-08-09 | 2019-08-09 | 一种基于虚拟组件的场景式割接方法和系统 |
CN201910735688.0 | 2019-08-09 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2021027652A1 true WO2021027652A1 (zh) | 2021-02-18 |
Family
ID=74367006
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/107102 WO2021027652A1 (zh) | 2019-08-09 | 2020-08-05 | 一种基于虚拟组件的场景式割接方法和系统 |
Country Status (3)
Country | Link |
---|---|
CN (1) | CN112350843B (zh) |
BR (1) | BR112022001268A2 (zh) |
WO (1) | WO2021027652A1 (zh) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117240600B (zh) * | 2023-11-08 | 2024-03-19 | 国家工业信息安全发展研究中心 | 一种工控系统的漏洞检测方法及装置 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105376087A (zh) * | 2014-08-14 | 2016-03-02 | 瞻博网络公司 | 用于网络服务配置的事务完整性 |
CN105393243A (zh) * | 2013-05-13 | 2016-03-09 | 亚马逊科技公司 | 事务定序 |
CN105550130A (zh) * | 2015-12-14 | 2016-05-04 | 中电科华云信息技术有限公司 | 基于容器的应用环境动态编排的方法及其应用系统 |
US20170075602A1 (en) * | 2015-09-15 | 2017-03-16 | Emc Corporation | Maintaining data consistency |
WO2017162030A1 (zh) * | 2016-03-22 | 2017-09-28 | 中兴通讯股份有限公司 | 一种虚拟网络的生成方法和装置 |
CN107483222A (zh) * | 2016-06-08 | 2017-12-15 | 中兴通讯股份有限公司 | 一种基于微服务化的虚拟网络功能的管理方法及网管系统 |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2461892A1 (en) * | 2001-09-26 | 2003-04-03 | Wisor Telecom Corporation | Intelligent service management system |
CN103167545B (zh) * | 2013-02-20 | 2015-08-19 | 大唐移动通信设备有限公司 | 一种基站相关ip割接的方法及装置 |
CN105792266B (zh) * | 2014-12-25 | 2019-06-07 | 北京神州泰岳软件股份有限公司 | 一种基站自动化割接方法及装置 |
CN106301869B (zh) * | 2015-06-24 | 2020-02-04 | 中兴通讯股份有限公司 | 一种建立ptn业务割接计划的方法及装置 |
CN106411541B (zh) * | 2015-07-27 | 2020-03-17 | 中兴通讯股份有限公司 | 建立业务割接计划的方法及装置 |
CN105446662B (zh) * | 2015-11-24 | 2018-09-21 | 华为技术有限公司 | 一种业务割接方法、存储控制装置及存储设备 |
CN107040416B (zh) * | 2017-04-12 | 2019-12-27 | 大连理工大学 | 一种基于Cairngorm框架的虚拟数据中心可视化管理方法 |
-
2019
- 2019-08-09 CN CN201910735688.0A patent/CN112350843B/zh active Active
-
2020
- 2020-08-05 WO PCT/CN2020/107102 patent/WO2021027652A1/zh active Application Filing
- 2020-08-05 BR BR112022001268A patent/BR112022001268A2/pt unknown
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105393243A (zh) * | 2013-05-13 | 2016-03-09 | 亚马逊科技公司 | 事务定序 |
CN105376087A (zh) * | 2014-08-14 | 2016-03-02 | 瞻博网络公司 | 用于网络服务配置的事务完整性 |
US20170075602A1 (en) * | 2015-09-15 | 2017-03-16 | Emc Corporation | Maintaining data consistency |
CN105550130A (zh) * | 2015-12-14 | 2016-05-04 | 中电科华云信息技术有限公司 | 基于容器的应用环境动态编排的方法及其应用系统 |
WO2017162030A1 (zh) * | 2016-03-22 | 2017-09-28 | 中兴通讯股份有限公司 | 一种虚拟网络的生成方法和装置 |
CN107483222A (zh) * | 2016-06-08 | 2017-12-15 | 中兴通讯股份有限公司 | 一种基于微服务化的虚拟网络功能的管理方法及网管系统 |
Also Published As
Publication number | Publication date |
---|---|
BR112022001268A2 (pt) | 2022-03-22 |
CN112350843B (zh) | 2022-02-08 |
CN112350843A (zh) | 2021-02-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN107193490B (zh) | 一种基于区块链的分布式数据存储系统及方法 | |
CN109901949B (zh) | 双活数据中心的应用灾备系统及方法 | |
KR101871383B1 (ko) | 계층적 데이터 구조의 노드 상에서 재귀적 이벤트 리스너를 사용하기 위한 방법 및 시스템 | |
CN106131123B (zh) | 三层架构的远程资源同步方法及系统 | |
CN101588302B (zh) | 路由更新的方法及设备 | |
CN103346914A (zh) | 分布式文件系统的拓扑结构更新方法和装置 | |
US20240037001A1 (en) | Large-scale k8s cluster monitoring method, apparatus, device, and readable medium | |
US20200065193A1 (en) | System for increasing intra-application processing efficiency by transmitting failed processing work over a processing recovery network for resolution | |
CN112671881B (zh) | 节点组织管理方法、装置、电子设备及可读存储介质 | |
CN108259200A (zh) | 一种物理网络功能pnf迁移方法及相关设备 | |
US20220326940A1 (en) | Service Upgrade Method, Apparatus, and System | |
WO2021027652A1 (zh) | 一种基于虚拟组件的场景式割接方法和系统 | |
CN108810112A (zh) | 一种市场监管区块链系统的节点同步方法及装置 | |
CN105530116A (zh) | 一种虚拟化网络备份、恢复的方法和相应装置 | |
CN104486448B (zh) | 一种数据处理方法及装置 | |
WO2016177075A1 (zh) | 一种业务数据关联关系校验方法、装置及可读存储介质 | |
CN111897643A (zh) | 线程池配置系统、方法、装置和存储介质 | |
CN110603798B (zh) | 一种提供具有高可用性的弹性一致性平台的系统和方法 | |
CN111176904A (zh) | 一种私有云架构下的数据备份的方法、系统、设备及介质 | |
CN107547605A (zh) | 一种基于节点队列的消息读写方法及节点设备 | |
WO2013091162A1 (zh) | 一种分布式存储数据恢复方法、装置及系统 | |
CN101848052B (zh) | 多域网络业务映射配置方法及系统 | |
CN101110705A (zh) | 后台服务器管理系统及其管理方法 | |
CN111917826A (zh) | 一种基于区块链知识产权保护的pbft共识算法 | |
CN111309522A (zh) | 基于快照技术的对象存储数据保护方法和装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20851503 Country of ref document: EP Kind code of ref document: A1 |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112022001268 Country of ref document: BR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 112022001268 Country of ref document: BR Kind code of ref document: A2 Effective date: 20220124 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20851503 Country of ref document: EP Kind code of ref document: A1 |