WO2016177071A1 - 建立业务割接计划的方法及装置 - Google Patents

建立业务割接计划的方法及装置 Download PDF

Info

Publication number
WO2016177071A1
WO2016177071A1 PCT/CN2016/075550 CN2016075550W WO2016177071A1 WO 2016177071 A1 WO2016177071 A1 WO 2016177071A1 CN 2016075550 W CN2016075550 W CN 2016075550W WO 2016177071 A1 WO2016177071 A1 WO 2016177071A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
cutover
parameter
group
establishing
Prior art date
Application number
PCT/CN2016/075550
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 中兴通讯股份有限公司
Publication of WO2016177071A1 publication Critical patent/WO2016177071A1/zh

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

Definitions

  • the present invention relates to the field of communication management technologies, and in particular, to a method and an apparatus for establishing a service cutover plan.
  • a traditional cutover plan consists of multiple cutover groups.
  • the cutover group directly contains the business objects to be cut, and these business objects often have complex dependencies, which leads to the business parameters when the user establishes the cutover plan. Can not be fully integrated into the cutover plan, further leading to the implementation of the cutover plan.
  • Common dependencies are: the dependencies of business objects and their auxiliary objects, such as tunnels and their OAM (Operation Administration and Maintenance) data, pseudowires and their OAM data; protection relationships between business objects, such as: protection Tunnels and working tunnels, protection pseudowires and work pseudowires; fixed bearer relationships between business objects, such as emulation services and pseudowires or multi-segment pseudowires that carry it.
  • OAM Operaation Administration and Maintenance
  • protection relationships between business objects such as: protection Tunnels and working tunnels, protection pseudowires and work pseudowires
  • fixed bearer relationships between business objects such as emulation services and pseudowires or multi-segment pseudowires that carry it.
  • the embodiment of the present invention provides a method and an apparatus for establishing a service cutover plan, the main purpose of which is to use a cutover parameter group as a minimum cutover unit, and add a service parameter having a dependency relationship to the same parameter group, so that the cutover is performed.
  • the business parameters in the business can be fully integrated into the cutover plan.
  • the embodiment of the present invention provides a method for establishing a service cutover plan, where the method for establishing a service cutover plan includes:
  • the service parameter is based on a dependency relationship between each service parameter in the first service to be cut and cut.
  • the number is divided into a plurality of first parameter groups;
  • the step of dividing the service parameter into multiple first parameter groups based on a dependency relationship between service parameters in the first service to be cut includes:
  • the service parameters having mutually dependent relationships are respectively formed into the first parameter group.
  • the service parameter is divided according to the dependency relationship between the service parameters in the first service to be cut
  • the steps for the plurality of first parameter sets include:
  • the independent service parameters are taken as the first parameter group.
  • the method for establishing a service cutover plan further includes:
  • the second parameter group that is added to the cutover group forms a cutover pair with the first parameter group that is added to the cutover group.
  • the method for establishing a service cutover plan further includes:
  • the embodiment of the present invention further provides an apparatus for establishing a service cutover plan, where the apparatus for establishing a service cutover plan includes:
  • the cutover group module is set to create a cutover group in the cutover plan
  • the first grouping module is set to be based on the basis of each service parameter in the first service to be cut and cut
  • the storage relationship divides the service parameter into a plurality of first parameter groups
  • a first adding module configured to add the first parameter group to the created cutover group
  • a second grouping module configured to divide the service parameter into a plurality of second parameter groups based on a dependency relationship between each service parameter in the second service created in advance;
  • a second adding module configured to add the second parameter group to the created cutover group.
  • the first grouping module comprises:
  • the searching unit is configured to compare the service parameters in the first service to be cut and cut, and find the service parameters that have dependencies on each other;
  • the adding unit is configured to respectively form the first parameter group with the service parameters having mutually dependent relationships.
  • the first grouping module further includes:
  • the independent parameter unit is configured to use the independent service parameter as the first parameter group when there are independent service parameters that are not dependent on other service parameters except the service parameters forming the first parameter group.
  • the device for establishing a service cutover plan further includes:
  • the cutover pair module is configured to form a cutover pair with the second parameter group added to the cutover group and the first parameter group added to the cutover group.
  • the device for establishing a service cutover plan further includes:
  • a binding module configured to bind the second service that has a bearer relationship between the multiple second parameter groups.
  • the first parameter group and the second parameter group are created in the cutover plan, and the cutover parameter group is regarded as the smallest cutover unit, and the to be cutover is to be cut.
  • the service parameters that are dependent on each other are included in the same first parameter group, and the service parameters that have the dependent relationship in the second service are included in the same second parameter group, so that the first service to be cut And the business parameters in the second business created in advance can be completely added to the cutover plan.
  • FIG. 1 is a flowchart of a first embodiment of a method for establishing a service cutover plan according to the present invention
  • FIG. 2 is a detailed flowchart of a step of creating a first parameter group in a second embodiment of a method for establishing a service cutover plan according to the present invention
  • FIG. 3 is a flowchart of a third embodiment of a method for establishing a service cutover plan according to the present invention.
  • FIG. 4 is a schematic structural diagram of a cutover plan in a third embodiment of a method for establishing a service cutover plan according to the present invention.
  • FIG. 5 is a flowchart of a fourth embodiment of a method for establishing a service cutover plan according to the present invention.
  • FIG. 6 is a schematic structural diagram of a cutover plan in a fourth embodiment of a method for establishing a service cutover plan according to the present invention.
  • FIG. 7 is a schematic diagram of functional modules of a first embodiment of an apparatus for establishing a service cutover plan according to the present invention.
  • FIG. 8 is a schematic diagram of a refinement function module of a first grouping module in a second embodiment of the apparatus for establishing a service cutover plan according to the present invention
  • FIG. 9 is a schematic diagram of functional modules of a third embodiment of an apparatus for establishing a service cutover plan according to the present invention.
  • FIG. 10 is a schematic diagram of functional modules of a fourth embodiment of an apparatus for establishing a service cutover plan according to the present invention.
  • the present invention provides a method of establishing a business cutover plan.
  • FIG. 1 a flowchart of a first embodiment of a method for establishing a service cutover plan according to the present invention is shown.
  • the method for establishing a service cutover plan includes:
  • step S10 a cutover group is created in the cutover plan.
  • Step S20 The service parameter is divided into a plurality of first parameter groups based on a dependency relationship between service parameters in the first service to be cut.
  • Step S30 Add the first parameter group to the created cutover group.
  • the cutover plan includes the complete service parameters of the first service to be cut and the business parameters of the second service that are pre-created.
  • the first service refers to a service that already exists in the existing network before the cutover action is performed
  • the second service refers to a service that is prepared in the network management to replace the first service in the cutover process.
  • the PTN network includes various simulation services, such as emulating Ethernet services and emulating TDM (time-division multiplex) services.
  • emulating Ethernet services emulating Ethernet services
  • TDM time-division multiplex
  • the Ethernet service in the Ethernet service, the working pseudowire of the Ethernet service, the OAM of the working pseudowire, the protection pseudowire, the protection pseudowire OAM, and the pseudowire protection group are used.
  • the cutover parameter group is used as a minimum unit of resource sharing.
  • the service parameter is divided into multiple first parameter groups based on the dependencies between the services in the first service to be cut. For example, each unprotected tunnel to be cut and its OAM configuration (if any) form a cutover parameter set; each pair of work, protection tunnels and their OAM configuration (if any), protection group configuration (if any) jointly form a cutover parameter set; each of the simulated services to be cut and connected with its working pseudowire/working multi-segment pseudowire, protection pseudowire/protection multi-segment pseudowire (if any) and pseudowire
  • the OAM configuration (if any) and the pseudowire protection group configuration (if any) together form a cutover parameter set.
  • the relationship table between the service parameters is established in advance, and when the grouping is performed, the dependency relationship is determined based on the relationship table.
  • Step S40 The service parameter is divided into a plurality of second parameter groups based on a dependency relationship between each service parameter in the second service created in advance.
  • Step S50 Add the second parameter group to the created cutover group.
  • a parameter group is an atomic unit that cannot be subdivided during the cutover process and is divided into a first parameter group and a second parameter group.
  • the first parameter group refers to a parameter group of the to-be-cut service that already exists in the existing network before the execution of the cutover operation
  • the second parameter group refers to a parameter group that is prepared in the network management to replace the first parameter group in the cutover process.
  • the service parameter with the dependency relationship in the second service created in advance is formed into the second parameter group, and the first parameter group and the second parameter group to be created are created. Join the same cutover group.
  • first parameter group and the second parameter group in this embodiment may be paired or not. If the pair is paired, the resources released by the first parameter group of the cutover pair can only be prefetched by the paired second parameter group, and the other second parameter groups cannot be advanced.
  • a cutover pair constitutes a minimum cutover replacement action. In the process, the service connection relationship represented by the first parameter group is removed from the device and replaced with the service connection relationship represented by the second parameter group. In case of an error, the cutover pair is automatically rolled back to the state before the cutover operation started.
  • the cutover parameter group is directly added to the cutover group without being paired, the resources are shared within the entire cutover group. That is, the resources released by any first parameter group in the group can be cutover groups. Any second parameter group is pre-fetched.
  • the user can determine whether to continue to create the cutover group in the cutover plan according to the requirements. If the cutover group needs to be created, proceed to step S10 to step S50 until the cutover is performed. The plan is completed.
  • multiple cutover groups can jointly form a cutover plan. There is no operational interdependence between the various cutover groups in the cutover plan. They form a cutover plan more for human planning purposes. If all the cutover parameter groups are included in the same cutover plan, it will be inconvenient for users to manage due to the large number. Users can create multiple cutover groups according to requirements. Moreover, the user can select the number of parameter groups in a cutover group. You can cut or roll back based on the entire cutover plan, or you can separately select the split group in the cutover plan for cutover or rollback.
  • the cutover plan created in this embodiment may be deleted completely, or only the cutover group may be deleted.
  • all cutover groups and second parameters in the cutover plan The array will be cleared and the service parameters in the first parameter group will be restored to the state before joining the cutover group.
  • the one or more cutover groups in the cutover plan are deleted, the second parameter group in the cutover group and the cutover group is cleared, and the first parameter group in the cutover group is restored to be before the joinover group. status. If there is no operation dependency between the cutover pair, you can delete the partial split pairs in the cutover group separately. If there is no binding relationship between the cutover parameter groups, you can delete the part of the cutover group separately.
  • a parameter group is a parameter group.
  • the first parameter group and the second parameter group are created in the cutover plan, and the cutover parameter group is regarded as the smallest cutover unit, and the cutover relationship with the dependency relationship is performed.
  • the service object is included in the same first parameter group, so that the service parameters in the cutover service can be completely added to the cutover plan.
  • step S20 a second embodiment of the method of establishing a service cutover plan of the present invention is proposed based on the first embodiment.
  • the following refinement steps are included in step S20:
  • Step S201 Perform a pairwise comparison of the service parameters in the first service to be cut, and find the service parameters that have a dependency relationship with each other;
  • Step S202 respectively forming service parameters having mutually dependent relationships into the first parameter group.
  • the service parameters in the network service need to be cut, and there are often dependencies between the service parameters, such as the working tunnel and the protection tunnel, the working tunnel OAM, and the protection tunnel OAM.
  • the service parameters of the services before the cutover need to be formed into a first parameter group between the tunnel protection groups. Therefore, when the first parameter group is created, the service parameters with dependencies are searched for in all the services before the cutover.
  • the service parameters with dependencies can be searched according to the pairwise comparison manner. In other embodiments, the search may be performed in a manner of searching from front to back according to the order of the services before the cutover.
  • step S20 further includes:
  • Step S203 when there are independent service parameters that are not dependent on other service parameters except the service parameters forming the first parameter group, the independent service parameter is used as the first parameter. group.
  • the independent service parameters when there are independent service parameters that are not dependent on other service parameters except the service parameters forming the first parameter group, the independent service parameters are formed into a single first parameter group. Or, when there are independent service parameters that are not dependent on other service parameters except the service parameters forming the first parameter group, the independent parameters are randomly added to the first parameter formed by the dependent service parameters. In the group.
  • the method for establishing a cutover plan proposed in this embodiment when the service parameters of the to-be-cut service are grouped based on the dependency relationship, the independent service parameters that do not depend on other service parameters are also used as the first parameter group. To ensure the integrity of the cutover plan.
  • a third embodiment of the method for establishing a service cutover plan of the present invention is proposed based on the first embodiment.
  • the method further includes:
  • Step S60 Bind the second service that has a bearer relationship between the multiple second parameter groups.
  • the tunnel and the emulation service with the bearer relationship have certain dependencies when creating and deleting, for example, the tunnel must be created before the emulation service, and the emulation service must be deleted before the tunnel. Therefore, it should be noted that the second is created in advance.
  • the service layer service parameters such as the working tunnel and the corresponding protection tunnel (if any)
  • the client layer service parameters such as work pseudowires
  • the cutover component is the de facto minimum unit of cutover. If an error occurs during the cutover, the entire cutover group is automatically rolled back to the state before the cutover operation starts.
  • a cutover group is created by adding a pre-cutting simulated TDM service to the cutover group 1.1 in a non-grouping manner:
  • the TDM service in the simulated TDM service, the work pseudowire, the OAM of the working pseudowire, the protection pseudowire, the OAM protecting the pseudowire, and the pseudowire protection group are searched to form a first parameter group 1.1.1.
  • the working tunnel based on the working pseudowire in the first parameter group 1.1.1 is added to the cutover group 1.1 in a non-grouping manner.
  • the system searches for the OAM of the working tunnel, the protection tunnel, the OAM of the protection tunnel, and the tunnel protection group.
  • the working tunnel on which the protection pseudowire is based in the first parameter group 1.1.1 is added to the cutover group 1.1 in a non-group mode.
  • the system searches for the OAM of the working tunnel, the protection tunnel, the OAM of the protection tunnel, and the tunnel protection group.
  • the second parameter group includes a working tunnel, an OAM of the working tunnel, a protection tunnel, an OAM of the protection tunnel, and a tunnel protection group.
  • a second parameter group 1.1.5 is created.
  • the second parameter group includes a working tunnel, an OAM of the working tunnel, a protection tunnel, an OAM of the protection tunnel, and a tunnel protection group.
  • a second parameter group 1.1.6 is created.
  • the second parameter group includes a TDM service, a work pseudowire, an OAM of a working pseudowire, a protection pseudowire, an OAM for protecting a pseudowire, and a pseudowire protection group.
  • the working pseudowire is bound to the working tunnel in the second parameter group 1.1.4
  • the protection pseudowire is bound to the working tunnel in the second parameter group 1.1.5.
  • the working tunnel in the second parameter group 1.1.4 is used to carry the working pseudowire in the second parameter group 1.1.6
  • the working tunnel in the second parameter group 1.1.5 is used to carry the second parameter group 1.1.
  • the method for creating a cutover plan proposed in this embodiment binds the cutover service with the bearer relationship between the cutover parameter groups to ensure the integrity of the cutover plan.
  • a fourth embodiment of the method of establishing a service cutover plan of the present invention is proposed based on the first embodiment.
  • the method further includes the following steps:
  • step S70 the second parameter group added to the cutover group forms a cutover pair with the first parameter group added to the cutover group.
  • the main purpose of this embodiment is to create a cutover pair.
  • a first parameter group and a second parameter group are added to the cutover pair to form a cutover pair.
  • the resources released by the first parameter group in the cutover pair can only be It is pre-funded by the second parameter group paired with it, and the other second parameter group cannot be advanced.
  • a cutover pair constitutes a minimum cutover replacement action.
  • the service connection relationship represented by the first parameter group is removed from the device and replaced with the service connection relationship represented by the second parameter group.
  • the cutover pair is automatically rolled back to the state before the cutover operation started.
  • a cutover group is created by adding a pre-cutting simulated Ethernet leased line in the cutover group to find the OAM of the Ethernet service, the work pseudowire, and the work pseudowire in the emulated Ethernet leased line.
  • the OAM and the pseudowire protection group are protected, and the first parameter group is added to a newly formed cutover pair 2.1.1.
  • the system searches for the OAM and protection tunnel of the working tunnel, and protects the OAM and tunnel protection group of the tunnel.
  • a first parameter set is formed, and the first parameter set is added to a newly formed cutover pair 2.1.2.
  • the work tunnel on which the protection pseudowire is cut before the cutover in 2.1.1 is added to the cutover group 2.1.
  • the system searches for the OAM and protection tunnel of the working tunnel, and protects the OAM and tunnel protection group of the tunnel.
  • a first parameter set is formed and this first parameter set is added to a newly formed cutover pair 2.1.3.
  • cutover pairs in the cutover group if there is no operational dependency between them, for example, all are simulated service cutover pairs, or although there are tunnel cutover pairs and simulated service cutover pairs, they do not exist. Relationships, at this point, you can also initiate a cutover or rollback for a single cutover pair.
  • the method for creating a cutover plan proposed in this embodiment creates a first parameter group and a second parameter group in a pairwise manner, and the resource sharing range is more controllable, and the control granularity of the cutover and the back scrolling is finer, more flexible and convenient.
  • the cutover parameter groups can be flexibly grouped or not paired as needed to adapt to multiple cutover requirements in network operation and maintenance.
  • the embodiment of the invention further provides an apparatus for establishing a service cutover plan.
  • FIG. 7 is a schematic diagram of functional modules of a first embodiment of an apparatus for establishing a service cutover plan according to the present invention.
  • the device for establishing a service cutover plan includes:
  • the cutover group module 10 is set to create a cutover group in the cutover plan.
  • the first grouping module 20 is configured to divide the service parameter into a plurality of first parameter groups based on a dependency relationship between service parameters in the first service to be cut.
  • the first adding module 30 is configured to add the first parameter group to the created cutover group.
  • the cutover plan includes the complete service parameters of the first service to be cut and the business parameters of the second service that are pre-created.
  • the first service refers to a service that already exists in the existing network before the cutover action is performed
  • the second service refers to a service that is prepared in the network management to replace the first service in the cutover process.
  • the PTN network includes various simulation services, such as emulating Ethernet services and emulating TDM (time-division multiplex) services.
  • emulating Ethernet services emulating Ethernet services
  • TDM time-division multiplex
  • the Ethernet service in the Ethernet service, the working pseudowire of the Ethernet service, the OAM of the working pseudowire, the protection pseudowire, the protection pseudowire OAM, and the pseudowire protection group are used.
  • This embodiment uses the cutover parameter group as the smallest single resource sharing Bits, when the cutover plan is established, the cutover group module 10 creates a cutover group in the cutover plan, and the first grouping module 20 divides the service parameters based on the dependencies between the services in the first service to be cut.
  • each unprotected tunnel to be cut and its OAM configuration form a cutover parameter group; each pair of work, protection tunnels and their OAM configurations (if any)
  • the protection group configuration together form a cutover parameter group; each of the simulated services to be cut and connected with its working pseudowire/working multi-segment pseudowire, protection pseudowire/protection multi-segment pseudowire (if And the pseudowire OAM configuration (if any), the pseudowire protection group configuration (if any) together form a cutover parameter set, and the first add module 30 adds these first parameter sets to the cutover The cutover plan created by group module 10.
  • the relationship table between the service parameters is established in advance, and when the grouping is performed, the dependency relationship is determined based on the relationship table.
  • the second grouping module 40 is configured to divide the service parameter into a plurality of second parameter groups based on a dependency relationship between each service parameter in the second service created in advance.
  • the second adding module 50 is configured to add the second parameter group to the created cutover group.
  • a parameter group is an atomic unit that cannot be subdivided during the cutover process and is divided into a first parameter group and a second parameter group.
  • the first parameter group refers to a parameter group of the to-be-cut service that already exists in the existing network before the execution of the cutover operation
  • the second parameter group refers to a parameter group that is prepared in the network management to replace the first parameter group in the cutover process.
  • the second grouping module 40 divides the service parameters in the second service created in advance into a plurality of second parameter groups based on the dependency relationship, and the second adding module 50 Add the second parameter group to the cutover group.
  • first parameter group and the second parameter group in this embodiment may be paired or not. If the pair is paired, the resources released by the first parameter group of the cutover pair can only be prefetched by the paired second parameter group, and the other second parameter groups cannot be advanced.
  • a cutover pair constitutes a minimum cutover replacement action. In the process, the service connection relationship represented by the first parameter group is removed from the device and replaced with the service connection relationship represented by the second parameter group. In case of an error, the cutover pair is automatically rolled back to the state before the cutover operation started.
  • the cutover parameter group is directly added to the cutover group without being paired, the resources are shared within the entire cutover group. That is, the resources released by any first parameter group in the group can be cutover groups. Any second parameter group is pre-fetched.
  • the user can determine whether to continue to create a cutover group in the cutover plan according to requirements. If the cutover group needs to be created, continue to create the cutover group until the cutover plan is completed. .
  • multiple cutover groups can jointly form a cutover plan. There is no operational interdependence between the various cutover groups in the cutover plan. They form a cutover plan more for human planning purposes. If all the cutover parameter groups are included in the same cutover plan, it will be inconvenient for users to manage due to the large number. Users can create multiple cutover groups according to requirements. Moreover, the user can select the number of cutover parameter groups in a cutover group. You can cut or roll back based on the entire cutover plan, or you can separately select the split group in the cutover plan for cutover or rollback.
  • the cutover plan created in this embodiment may be deleted completely, or only the cutover group may be deleted.
  • all the cutover groups and the second parameter group in the cutover plan are cleared, and the service parameters in the first parameter group are restored to the state before joining the cutover group.
  • the one or more cutover groups in the cutover plan are deleted, the second parameter group in the cutover group and the cutover group is cleared, and the first parameter group in the cutover group is restored to be before the joinover group. status. If there is no operation dependency between the cutover pair, you can delete the partial split pairs in the cutover group separately. If there is no binding relationship between the cutover parameter groups, you can delete the part of the cutover group separately.
  • a parameter group is a parameter group.
  • the first parameter group and the second parameter group are created in the cutover plan, and the cutover parameter group is regarded as the smallest cutover unit, and the cutover node with the dependency relationship is
  • the service object is included in the same first parameter group, so that the service parameters in the cutover service can be completely added to the cutover plan.
  • the first grouping module 20 includes the following refinement unit:
  • the searching unit 210 is configured to perform a pairwise comparison of the service parameters in the first service to be cut, and find the service parameters that have a dependency relationship with each other;
  • the adding unit 220 is configured to respectively form the first parameter group with the service parameters having mutually dependent relationships.
  • the search unit 210 searches for the service with the dependency relationship according to the pairwise comparison manner.
  • the parameter, adding unit 220 adds it to the created cutover group.
  • the search may be performed in a manner of searching from front to back according to the order of the services before the cutover.
  • first grouping module 20 further includes:
  • the independent parameter unit 203 is configured to set the independent service parameter as the first parameter group when there are independent service parameters that are not dependent on other service parameters except the service parameters forming the first parameter group.
  • the independent parameter unit 203 may also form the independent service parameters into a single one when there are independent service parameters that are not dependent on other service parameters except the service parameters forming the first parameter group.
  • the apparatus for establishing a cutover plan when the service parameters of the to-be-cut service are grouped based on the dependency relationship, the independent service parameters that do not depend on other service parameters are also used as the first parameter group. To ensure the integrity of the cutover plan.
  • the device further includes:
  • Step S60 Bind the second service that has a bearer relationship between the multiple second parameter groups.
  • the tunnel and the emulation service with the bearer relationship have certain dependencies when creating and deleting, for example, the tunnel must be created before the emulation service, and the emulation service must be deleted before the tunnel. Therefore, it should be noted that the second is created in advance.
  • the service layer service parameters such as the working tunnel and the corresponding protection tunnel (if any)
  • the client layer service parameters such as work pseudowires
  • the cutover component is the de facto minimum unit of cutover. If an error occurs during the cutover, the entire cutover group is automatically rolled back to the state before the cutover operation starts.
  • a cutover group is created by adding a pre-cutting simulated TDM service to the cutover group 1.1 in a non-grouping manner:
  • the TDM service in the simulated TDM service, the work pseudowire, the OAM of the working pseudowire, the protection pseudowire, the OAM protecting the pseudowire, and the pseudowire protection group are searched to form a first parameter group 1.1.1.
  • the working tunnel based on the working pseudowire in the first parameter group 1.1.1 is added to the cutover group 1.1 in a non-grouping manner.
  • the system searches for the OAM of the working tunnel, the protection tunnel, the OAM of the protection tunnel, and the tunnel protection group.
  • the working tunnel on which the protection pseudowire is based in the first parameter group 1.1.1 is added to the cutover group 1.1 in a non-group mode.
  • the system searches for the OAM of the working tunnel, the protection tunnel, the OAM of the protection tunnel, and the tunnel protection group.
  • the second parameter group includes a working tunnel, an OAM of the working tunnel, a protection tunnel, an OAM of the protection tunnel, and a tunnel protection group.
  • a second parameter group 1.1.5 is created.
  • the second parameter group includes a working tunnel, an OAM of the working tunnel, a protection tunnel, an OAM of the protection tunnel, and a tunnel protection group.
  • a second parameter group 1.1.6 is created.
  • the second parameter group includes a TDM service, a work pseudowire, an OAM of a working pseudowire, a protection pseudowire, an OAM for protecting a pseudowire, and a pseudowire protection group.
  • the working pseudowire is bound to the working tunnel in the second parameter group 1.1.4, and the protection pseudowire is bound to the second parameter group.
  • Working tunnel in 1.1.5 The working tunnel in the second parameter group 1.1.4 is used to carry the working pseudowire in the second parameter group 1.1.6, and the working tunnel in the second parameter group 1.1.5 is used to carry the second parameter group 1.1.
  • the device for creating a cutover plan proposed in this embodiment binds the cutover service with the bearer relationship between the cutover parameter groups to ensure the integrity of the cutover plan.
  • the device further includes the following modules:
  • step S70 the second parameter group added to the cutover group forms a cutover pair with the first parameter group added to the cutover group.
  • the main purpose of this embodiment is to create a cutover pair.
  • a first parameter group and a second parameter group are added to the cutover pair to form a cutover pair.
  • the resources released by the first parameter group in the cutover pair can only be associated with
  • the paired second parameter group is pre-funded, and the other second parameter groups cannot be advanced.
  • a cutover pair constitutes a minimum cutover replacement action.
  • the service connection relationship represented by the first parameter group is removed from the device and replaced with the service connection relationship represented by the second parameter group.
  • the cutover pair is automatically rolled back to the state before the cutover operation started.
  • a cutover group is created by adding a pre-cutting simulated Ethernet leased line in the cutover group to find the OAM of the Ethernet service, the work pseudowire, and the work pseudowire in the emulated Ethernet leased line.
  • the OAM and the pseudowire protection group are protected, and the first parameter group is added to a newly formed cutover pair 2.1.1.
  • the system searches for the OAM and protection tunnel of the working tunnel, and protects the OAM and tunnel protection group of the tunnel.
  • a first parameter set is formed, and the first parameter set is added to a newly formed cutover pair 2.1.2.
  • Adding the cutover pair to the cutover group 2.1 in group mode is based on the protection of the pseudowire before the cutover in 2.1.1.
  • the working tunnel the system finds the OAM of the working tunnel, protects the tunnel, protects the OAM and tunnel protection group of the tunnel, forms a first parameter group, and adds the first parameter group to a newly formed cutover pair 2.1.3. .
  • cutover pairs in the cutover group if there is no operational dependency between them, for example, all are simulated service cutover pairs, or although there are tunnel cutover pairs and simulated service cutover pairs, they do not exist. Relationships, at this point, you can also initiate a cutover or rollback for a single cutover pair.
  • the device for creating a cutover plan proposed in this embodiment creates a first parameter group and a second parameter group in a pairwise manner, and the resource sharing range is more controllable, and the control granularity of the cutover and the back scrolling is finer, more flexible and convenient.
  • the cutover parameter groups can be flexibly grouped or not paired as needed to adapt to multiple cutover requirements in network operation and maintenance.
  • the method and apparatus for establishing a service cutover plan provided by the embodiment of the present invention have the following beneficial effects: the first parameter group and the second parameter group are created in the cutover plan, and the cutover parameter group is minimized.
  • the cutover unit, and the business parameters having the dependency relationship in the first service to be cut and merged are included in the same first parameter group, and the business parameters having the dependency relationship in the second service created in advance are included in the same second parameter.
  • the first service to be cut and the service parameters in the pre-created second service can be completely added to the cutover plan.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明公开了一种建立业务割接计划的方法，该方法流程包括：在割接计划中创建割接组；基于待割接的第一业务中各业务参数之间的依存关系将业务参数分为多个第一参数组；将第一参数组加入创建的割接组中；基于预先创建的第二业务中各业务参数之间的依存关系将业务参数分为多个第二参数组；将第二参数组加入创建的割接组中。本发明实施例还提出一种建立业务割接计划的装置。本发明实施例提出的建立业务割接计划的方法及装置，将参数组作为最小割接单位，并将具有依存关系的业务参数加入同一个参数组，使得割接业务中的业务参数能够完整的加入割接计划中。

Description

建立业务割接计划的方法及装置 技术领域
本发明涉及通信管理技术领域，尤其涉及一种建立业务割接计划的方法及装置。
背景技术
在PTN(Packet Transport Network，分组传送网)网络的运维中，常常要进行PTN业务的割接。传统的割接计划由多个割接组构成，割接组直接包含待割接的业务对象，而这些业务对象之间常常有着复杂的依存关系，导致用户在建立割接计划时，导致业务参数不能完整的加入割接计划中，进一步导致割接计划无法实施。常见的依存关系有：业务对象与其辅助对象的依存关系，比如：隧道及其OAM(Operation Administration and Maintenance，操作维护管理)数据、伪线及其OAM数据；业务对象间的保护关系，比如：保护隧道和工作隧道、保护伪线和工作伪线；业务对象间的固定承载关系，比如：仿真业务和承载它的伪线或多段伪线等。
发明内容
本发明实施例提供了一种建立业务割接计划的方法及装置，其主要目的在于将割接参数组作为最小割接单位，并将具有依存关系的业务参数加入同一个参数组，使得割接业务中的业务参数能够完整的加入割接计划中。
为实现上述目的，本发明实施例提供一种建立业务割接计划的方法，该建立业务割接计划的方法包括：
在割接计划中创建割接组；
基于待割接的第一业务中各业务参数之间的依存关系将所述业务参 数分为多个第一参数组；
将所述第一参数组加入创建的所述割接组中；
基于预先创建的第二业务中各业务参数之间的依存关系将所述业务参数分为多个第二参数组；
将所述第二参数组加入创建的所述割接组中。
优选地，所述基于待割接的第一业务中各业务参数之间的依存关系将所述业务参数分为多个第一参数组的步骤包括：
将所待割接的第一业务中的业务参数进行两两对比，查找相互具有依存关系的所述业务参数；
分别将相互具有依存关系的业务参数形成所述第一参数组。
优选地，所述分别将相互具有依存关系的业务参数形成所述第一参数组的步骤之后，所述基于待割接的第一业务中各业务参数之间的依存关系将所述业务参数分为多个第一参数组的步骤包括：
在除形成第一参数组的业务参数之外还存在与其它业务参数均无依存关系的独立业务参数时，将所述独立业务参数作为第一参数组。
优选地，所述将所述第二参数组加入创建的所述割接组中的步骤之后，所述建立业务割接计划的方法还包括：
将加入所述割接组中的所述第二参数组与加入所述割接组中的所述第一参数组形成割接对。
优选地，所述基于预先创建的第二业务中各业务参数之间的依存关系将所述业务参数分为多个第二参数组的步骤之后，所述建立业务割接计划的方法还包括：
将所述多个第二参数组之间具有承载关系的所述第二业务进行绑定。
此外，为实现上述目的，本发明实施例还提供一种建立业务割接计划的装置，该建立业务割接计划的装置包括：
割接组模块，设置为在割接计划中创建割接组；
第一分组模块，设置为基于待割接的第一业务中各业务参数之间的依 存关系将所述业务参数分为多个第一参数组；
第一添加模块，设置为将所述第一参数组加入创建的所述割接组中；
第二分组模块，设置为基于预先创建的第二业务中各业务参数之间的依存关系将所述业务参数分为多个第二参数组；
第二添加模块，设置为将所述第二参数组加入创建的所述割接组中。
优选地，所述第一分组模块包括：
查找单元，设置为将所待割接的第一业务中的业务参数进行两两对比，查找相互具有依存关系的所述业务参数；
添加单元，设置为分别将相互具有依存关系的业务参数形成所述第一参数组。
优选地，所述第一分组模块还包括：
独立参数单元，设置为在除形成第一参数组的业务参数之外还存在与其它业务参数均无依存关系的独立业务参数时，将所述独立业务参数作为第一参数组。
优选地，所述建立业务割接计划的装置还包括：
割接对模块，设置为将加入所述割接组中的所述第二参数组与加入所述割接组中的所述第一参数组形成割接对。
优选地，所述建立业务割接计划的装置还包括：
绑定模块，设置为将所述多个第二参数组之间具有承载关系的所述第二业务进行绑定。
本发明实施例提出的建立业务割接计划的方法及装置，在割接计划中创建第一参数组和第二参数组，将割接参数组作为最小的割接单位，并且将待割接的第一业务中相互具有依存关系业务参数纳入同一个第一参数组中，将预先创建的第二业务中相互具有依存关系业务参数纳入同一个第二参数组中，使得待割接的第一业务和预先创建的第二业务中的业务参数能够完整的加入割接计划中。
附图说明
图1为本发明建立业务割接计划的方法第一实施例的流程图；
图2为本发明建立业务割接计划的方法第二实施例中创建第一参数组步骤的细化流程图；
图3为本发明建立业务割接计划的方法第三实施例的流程图；
图4为本发明建立业务割接计划的方法的第三实施例中的割接计划的结构示意图；
图5为本发明建立业务割接计划的方法第四实施例的流程图；
图6为本发明建立业务割接计划的方法的第四实施例中的割接计划结构示意图；
图7为本发明建立业务割接计划的装置第一实施例的功能模块示意图；
图8为本发明建立业务割接计划的装置第二实施例中的第一分组模块的细化功能模块示意图；
图9为本发明建立业务割接计划的装置第三实施例的功能模块示意图；
图10为本发明建立业务割接计划的装置第四实施例的功能模块示意图。
本发明目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
本发明提供一种建立业务割接计划的方法。
参照图1所示，为本发明建立业务割接计划的方法第一实施例的流程图。
在第一实施例中，该建立业务割接计划的方法包括：
步骤S10，在割接计划中创建割接组。
步骤S20，基于待割接的第一业务中各业务参数之间的依存关系将所述业务参数分为多个第一参数组。
步骤S30，将所述第一参数组加入创建的所述割接组中。
在进行网络割接之前需要创建一个完整的割接计划中，割接计划中要包含有完整的待割接的第一业务的业务参数，以及预先创建的第二业务的业务参数。上述第一业务指割接动作执行前现网中已经存在的业务，第二业务指预先在网管中建立好准备在割接过程中替代第一业务的业务。
本实施例以建立PTN网络的割接计划为例进行说明，在其他的实施例中也可以是其他的网络割接。PTN网络包括各种各样的仿真业务，例如仿真以太网业务、仿真TDM(time-division multiplex，时分复用)业务等，一般这些待割接业务中的业务参数之间会存在着复杂的依存关系，在割接时这些参数之间不能分离。例如，仿真以太网业务中的以太网业务、以太网业务依存的工作伪线、工作伪线的OAM、保护伪线、保护伪线OAM和伪线保护组等业务参数。本实施例将割接参数组作为资源共享的最小单位，在建立割接计划时，基于待割接的第一业务中各业务之间的有依存关系将业务参数分为多个第一参数组，例如，每一条待割接的无保护隧道及其OAM配置(如果有的话)形成一个割接参数组；每一对工作、保护隧道及其OAM配置(如果有的话)、保护组配置(如果有的话)共同形成一个割接参数组；每一条待割接的仿真业务连带其工作伪线/工作多段伪线、保护伪线/保护多段伪线(如果有的话)以及伪线OAM配置(如果有的话)、伪线保护组配置(如果有的话)共同形成一个割接参数组。
在待割接的业务的多个业务参数中关于依存关系的判断，预先建立各个业务参数之间的关系表，在进行分组时，根据上述关系表进行依存关系的判断。
步骤S40，基于预先创建的第二业务中各业务参数之间的依存关系将所述业务参数分为多个第二参数组。
步骤S50，将所述第二参数组加入创建的所述割接组中。
参数组是割接过程中不可细分的原子单位，分为第一参数组和第二参数组。上述第一参数组指割接动作执行前现网中已经存在的待割接业务的参数组，第二参数组指预先在网管中建立好准备在割接过程中替代第一参数组的参数组。在一个割接组中，确认完成第一参数组的创建后，将预先创建的第二业务中的具有依存关系的业务参数形成第二参数组，将创建的第一参数组和第二参数组加入同一割接组中。
需要说明的是，本实施例中的第一参数组与第二参数组之间可以组对，也可以不组对。如果组对，割接对中第一参数组释放的资源只能被与之成对的第二参数组所预支，其他第二参数组不能预支。一个割接对构成一个最小的割接替换动作，过程中，第一参数组代表的业务连接关系被从设备中拆除，替换为第二参数组所代表的业务连接关系，若割接过程中发生错误，则割接对自动回滚到割接操作开始前的状态。
如果割接参数组在不成对的情况下直接加入割接组，这时，资源在整个割接组范围内共享，也即是说，组内任意第一参数组释放的资源可以被割接组内任意第二参数组所预支。
进一步地，当完成一个割接组的创建之后，用户可以根据需求判断是否在割接计划中继续创建割接组，如果需要继续创建割接组，那么继续执行步骤S10至步骤S50，直至割接计划完成。
需要说明的是，多个割接组可以共同构成一个割接计划。割接计划中的各个割接组并无操作上的相互依赖关系，他们组成一个割接计划更多是出于人为规划的目的。如果所有的割接参数组全部纳入同一个割接计划中，会由于数量多导致不便于用户管理，用户可以根据需求创建多个割接组。而且，用户可以选择在一个割接组中的参数组的数量。可以基于整个割接计划进行割接或回滚，也可以单独选择割接计划中的部分割接组进行割接或回滚操作。
可以理解的是，本实施例创建的割接计划可以完整地删除，也可以只删除割接组。当删除整个割接计划时，割接计划中所有的割接组、第二参 数组将被清除，第一参数组中的业务参数恢复为加入割接组前的状态。当删除割接计划中的一个或者多个割接组时，割接组以及割接组中的第二参数组将被清除，割接组中的第一参数组恢复为加入割接组前的状态。在割接对间无操作依赖关系的情况下，可以单独删除割接组中的部分割接对；在割接参数组间无绑定关系的情况下，可以单独删除割接组中的部分第一参数组。
本实施例提出的建立业务割接计划的方法，在割接计划中创建第一参数组和第二参数组，将割接参数组作为最小的割接单位，并且将具有依存关系的割接前业务对象纳入同一个第一参数组中，使得割接业务中的业务参数能够完整的加入割接计划中。
参照图2所示，基于第一实施例提出本发明建立业务割接计划的方法的第二实施例。在本实施例中，在步骤S20包括以下细化步骤：
步骤S201，将所待割接的第一业务中的业务参数进行两两对比，查找相互具有依存关系的所述业务参数；
步骤S202，分别将相互具有依存关系的业务参数形成所述第一参数组。
一般在进行网络业务割接时，会需要对网络业务中的所有业务参数进行割接，而这些业务参数之间往往存在着依存关系，例如工作隧道与保护隧道、工作隧道OAM、保护隧道OAM、隧道保护组之间，需要将这些割接前业务的业务参数形成一个第一参数组。因此，在创建第一参数组的时候，要在所有的割接前业务中查找具有依存关系的业务参数，在本实施例中可以按照两两比对的方式查找具有依存关系的业务参数，在其他实施例中也可以按照割接前业务的排列顺序，按照从前至后搜索的方式进行查找。
进一步地，步骤S20还包括：
步骤S203，在除形成第一参数组的业务参数之外还存在与其它业务参数均无依存关系的独立业务参数时，将所述独立业务参数作为第一参数 组。
在其他的实施例中，也可以在除形成第一参数组的业务参数之外还存在与其它业务参数均无依存关系的独立业务参数时，将这些独立业务参数形成一个单独的第一参数组；或者，在除形成第一参数组的业务参数之外还存在与其它业务参数均无依存关系的独立业务参数时，将这些独立参数随机的加入有依存关系的业务参数所形成的第一参数组中。
本实施例提出的建立割接计划的方法，在基于依存关系将待割接业务的业务参数进行分组时的同时，将不与其他业务参数具有依存关系的独立业务参数同样地作为第一参数组，确保割接计划的完整性。
进一步地，参照图3所示，基于第一实施例提出本发明建立业务割接计划的方法的第三实施例。在本实施例中，在步骤S50之后，该方法还包括：
步骤S60，将所述多个第二参数组之间具有承载关系的所述第二业务进行绑定。
由于有承载关系的隧道和仿真业务在创建和删除时有一定的依赖关系，比如：隧道必须先于仿真业务创建，仿真业务必须先于隧道删除，因此，需要说明的是，在预先创建第二业务时，要先创建服务层业务参数，如工作隧道和对应的保护隧道(如果有的话)，在创建承载于服务层业务参数之上的客户层业务参数，如工作伪线等。
在将第二业务的业务参数基于依存关系进行分组后，将第二参数组之间具有承载关系的服务层业务参数和客户层业务参数进行绑定。此时，割接组成为事实上的割接最小单位，若在割接的过程中发生错误，则整个割接组自动回滚到割接操作开始前的状态。
参照图4所示，以非组对方式向割接组1.1中添加一条割接前仿真TDM业务为例创建一个割接组：
查找该仿真TDM业务中的TDM业务、工作伪线、工作伪线的OAM、保护伪线、保护伪线的OAM、伪线保护组，形成一个第一参数组1.1.1。
以非组对方式向割接组1.1中添加第一参数组1.1.1中工作伪线所基于的工作隧道，系统查找该工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组，形成一个第一参数组1.1.2。
以非组对方式向割接组1.1中添加第一参数组1.1.1中保护伪线所基于的工作隧道，系统查找该工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组，形成一个第一参数组1.1.3。
创建第二参数组1.1.4，该第二参数组包括一条工作隧道、工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组。
创建第二参数组1.1.5，该第二参数组包括一条工作隧道、工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组。
创建第二参数组1.1.6，该第二参数组包括一条TDM业务、工作伪线、工作伪线的OAM、保护伪线、保护伪线的OAM、伪线保护组。其中，工作伪线绑定第二参数组1.1.4中的工作隧道，保护伪线绑定第二参数组1.1.5中的工作隧道。其中，第二参数组1.1.4中的工作隧道用于承载第二参数组1.1.6中的工作伪线，建第二参数组1.1.5中的工作隧道用于承载第二参数组1.1.6中的保护伪线。
本实施例提出的创建割接计划的方法，将割接参数组之间具有承载关系的割接业务进行绑定，保证割接计划的完整性。
参照图5所示，基于第一实施例提出本发明建立业务割接计划的方法的第四实施例。在本实施例中，步骤S50之后，该方法还包括如下步骤：
步骤S70，将加入所述割接组中的所述第二参数组与加入所述割接组中的所述第一参数组形成割接对。
用户在割接组中创建割接参数组的时候，可以根据自己的需求进行判断是否组对创建，当需要组对创建时，发出形成割接对的指令，将加入割接组中的第一参数组合第二参数组形成割接对。
本实施例的主要目的在于创建割接对，一个第一参数组和一个第二参数组加入割接后形成割接对，这样，割接对中第一参数组释放的资源只能 被与之成对的第二参数组所预支，其他第二参数组不能预支。一个割接对构成一个最小的割接替换动作，过程中，第一参数组代表的业务连接关系被从设备中拆除，替换为第二参数组所代表的业务连接关系，若割接过程中发生错误，则割接对自动回滚到割接操作开始前的状态。
参照图6所示，以在割接组中添加一条割接前仿真以太网专线为例创建一个割接组，查找该仿真以太网专线中的以太网业务、工作伪线、工作伪线的OAM、保护伪线、保护伪线的OAM、伪线保护组，形成一个第一参数组，并将此第一参数组加入一个新形成的割接对2.1.1中。
以组对方式向割接组2.1中添加割接对2.1.1中割接前工作伪线所基于的工作隧道，系统查找该工作隧道的OAM、保护隧道，保护隧道的OAM、隧道保护组，形成一个第一参数组，并将此第一参数组加入一个新形成的割接对2.1.2中。
以组对方式向割接组2.1中添加割接对2.1.1中割接前保护伪线所基于的工作隧道，系统查找该工作隧道的OAM、保护隧道，保护隧道的OAM、隧道保护组，形成一个第一参数组，并将此第一参数组加入一个新形成的割接对2.1.3中。
为割接对2.1.2创建第二参数组，包括割接后的工作隧道、工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组。
为割接对2.1.3创建第二参数组，包括割接后的工作隧道、工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组。
为割接对2.1.1创建第二参数组，包括割接后的以太网专线业务、工作伪线、工作伪线的OAM、保护伪线、保护伪线的OAM、伪线保护组。其中，工作伪线绑定割接对2.1.2中的割接后工作隧道，保护伪线绑定割接对2.1.3中的割接后工作隧道。
对于割接组中的割接对，假如彼此间没有操作依赖关系，比如：全部都是仿真业务割接对，或者虽然同时有隧道割接对和仿真业务割接对，但是他们并不存在承载关系，则此时也可以针对单个割接对发起割接或回滚。
可以理解的是，用户可以根据需求创建混合割接组，在割接组中，可以将创建第一参数组和第二参数组组对或不组对，以适应网络运维中多种割接需求。
本实施例提出的创建割接计划的方法，以组对的方式创建第一参数组、第二参数组，资源共享范围更可控，割接和回滚动作的控制粒度更细，灵活方便，而且，割接参数组间可根据需要灵活组对或不组对，适应网络运维中多种割接需求。
本发明实施例还提出一种建立业务割接计划的装置。
参照图7所示，为本发明建立业务割接计划的装置第一实施例的功能模块示意图。
在该实施例中，该建立业务割接计划的装置包括：
割接组模块10，设置为在割接计划中创建割接组。
第一分组模块20，设置为基于待割接的第一业务中各业务参数之间的依存关系将所述业务参数分为多个第一参数组。
第一添加模块30，设置为将所述第一参数组加入创建的所述割接组中。
在进行网络割接之前需要创建一个完整的割接计划中，割接计划中要包含有完整的待割接的第一业务的业务参数，以及预先创建的第二业务的业务参数。上述第一业务指割接动作执行前现网中已经存在的业务，第二业务指预先在网管中建立好准备在割接过程中替代第一业务的业务。
本实施例以建立PTN网络的割接计划为例进行说明，在其他的实施例中也可以是其他的网络割接。PTN网络包括各种各样的仿真业务，例如仿真以太网业务、仿真TDM(time-division multiplex，时分复用)业务等，一般这些待割接业务中的业务参数之间会存在着复杂的依存关系，在割接时这些参数之间不能分离。例如，仿真以太网业务中的以太网业务、以太网业务依存的工作伪线、工作伪线的OAM、保护伪线、保护伪线OAM和伪线保护组等业务参数。本实施例将割接参数组作为资源共享的最小单 位，在建立割接计划时，割接组模块10在割接计划中创建割接组，第一分组模块20基于待割接的第一业务中各业务之间的有依存关系将业务参数分为多个第一参数组，例如，每一条待割接的无保护隧道及其OAM配置(如果有的话)形成一个割接参数组；每一对工作、保护隧道及其OAM配置(如果有的话)、保护组配置(如果有的话)共同形成一个割接参数组；每一条待割接的仿真业务连带其工作伪线/工作多段伪线、保护伪线/保护多段伪线(如果有的话)以及伪线OAM配置(如果有的话)、伪线保护组配置(如果有的话)共同形成一个割接参数组，第一添加模块30将这些第一参数组加入到割接组模块10创建的割接计划中。
在待割接的业务的多个业务参数中关于依存关系的判断，预先建立各个业务参数之间的关系表，在进行分组时，根据上述关系表进行依存关系的判断。
第二分组模块40，设置为基于预先创建的第二业务中各业务参数之间的依存关系将所述业务参数分为多个第二参数组。
第二添加模块50，设置为将所述第二参数组加入创建的所述割接组中。
参数组是割接过程中不可细分的原子单位，分为第一参数组和第二参数组。上述第一参数组指割接动作执行前现网中已经存在的待割接业务的参数组，第二参数组指预先在网管中建立好准备在割接过程中替代第一参数组的参数组。在一个割接组中，确认完成第一参数组的创建后，第二分组模块40基于依存关系将预先创建的第二业务中的业务参数分为多个第二参数组，第二添加模块50将第二参数组加入割接组中。
需要说明的是，本实施例中的第一参数组与第二参数组之间可以组对，也可以不组对。如果组对，割接对中第一参数组释放的资源只能被与之成对的第二参数组所预支，其他第二参数组不能预支。一个割接对构成一个最小的割接替换动作，过程中，第一参数组代表的业务连接关系被从设备中拆除，替换为第二参数组所代表的业务连接关系，若割接过程中发生错误，则割接对自动回滚到割接操作开始前的状态。
如果割接参数组在不成对的情况下直接加入割接组，这时，资源在整个割接组范围内共享，也即是说，组内任意第一参数组释放的资源可以被割接组内任意第二参数组所预支。
进一步地，当完成一个割接组的创建之后，用户可以根据需求判断是否在割接计划中继续创建割接组，如果需要继续创建割接组，那么继续创建割接组，直至割接计划完成。
需要说明的是，多个割接组可以共同构成一个割接计划。割接计划中的各个割接组并无操作上的相互依赖关系，他们组成一个割接计划更多是出于人为规划的目的。如果所有的割接参数组全部纳入同一个割接计划中，会由于数量多导致不便于用户管理，用户可以根据需求创建多个割接组。而且，用户可以选择在一个割接组中的割接参数组的数量。可以基于整个割接计划进行割接或回滚，也可以单独选择割接计划中的部分割接组进行割接或回滚操作。
可以理解的是，本实施例创建的割接计划可以完整地删除，也可以只删除割接组。当删除整个割接计划时，割接计划中所有的割接组、第二参数组将被清除，第一参数组中的业务参数恢复为加入割接组前的状态。当删除割接计划中的一个或者多个割接组时，割接组以及割接组中的第二参数组将被清除，割接组中的第一参数组恢复为加入割接组前的状态。在割接对间无操作依赖关系的情况下，可以单独删除割接组中的部分割接对；在割接参数组间无绑定关系的情况下，可以单独删除割接组中的部分第一参数组。
本实施例提出的建立业务割接计划的装置，在割接计划中创建第一参数组和第二参数组，将割接参数组作为最小的割接单位，并且将具有依存关系的割接前业务对象纳入同一个第一参数组中，使得割接业务中的业务参数能够完整的加入割接计划中。
参照图8所示，基于第一实施例提出本发明建立业务割接计划的装置的第二实施例。在本实施例中，第一分组模块20包括以下细化单元：
查找单元210，设置为将所待割接的第一业务中的业务参数进行两两对比，查找相互具有依存关系的所述业务参数；
添加单元220，设置为分别将相互具有依存关系的业务参数形成所述第一参数组。
一般在进行网络业务割接时，会需要对网络业务中的所有业务参数进行割接，而这些业务参数之间往往存在着依存关系，例如工作隧道与保护隧道、工作隧道OAM、保护隧道OAM、隧道保护组之间，需要将这些割接前业务的业务参数形成一个第一参数组。因此，在创建第一参数组的时候，要在所有的割接前业务中查找具有依存关系的业务参数，在本实施例中，查找单元210按照两两比对的方式查找具有依存关系的业务参数，添加单元220将其加入创建的割接组中。在其他实施例中也可以按照割接前业务的排列顺序，按照从前至后搜索的方式进行查找。
进一步地，第一分组模块20还包括：
独立参数单元203，设置为在除形成第一参数组的业务参数之外还存在与其它业务参数均无依存关系的独立业务参数时，将所述独立业务参数作为第一参数组。
在其他的实施例中，独立参数单元203也可以在除形成第一参数组的业务参数之外还存在与其它业务参数均无依存关系的独立业务参数时，将这些独立业务参数形成一个单独的第一参数组；或者，独立参数单元203在除形成第一参数组的业务参数之外还存在与其它业务参数均无依存关系的独立业务参数时，将这些独立参数随机的加入有依存关系的业务参数所形成的第一参数组中。
本实施例提出的建立割接计划的装置，在基于依存关系将待割接业务的业务参数进行分组时的同时，将不与其他业务参数具有依存关系的独立业务参数同样地作为第一参数组，确保割接计划的完整性。
进一步地，参照图9所示，基于第一实施例提出本发明建立业务割接计划的装置的第三实施例。在本实施例中，该装置还包括：
步骤S60，将所述多个第二参数组之间具有承载关系的所述第二业务进行绑定。
由于有承载关系的隧道和仿真业务在创建和删除时有一定的依赖关系，比如：隧道必须先于仿真业务创建，仿真业务必须先于隧道删除，因此，需要说明的是，在预先创建第二业务时，要先创建服务层业务参数，如工作隧道和对应的保护隧道(如果有的话)，在创建承载于服务层业务参数之上的客户层业务参数，如工作伪线等。
在将第二业务的业务参数基于依存关系进行分组后，将第二参数组之间具有承载关系的服务层业务参数和客户层业务参数进行绑定。此时，割接组成为事实上的割接最小单位，若在割接的过程中发生错误，则整个割接组自动回滚到割接操作开始前的状态。
参照图4所示，以非组对方式向割接组1.1中添加一条割接前仿真TDM业务为例创建一个割接组：
查找该仿真TDM业务中的TDM业务、工作伪线、工作伪线的OAM、保护伪线、保护伪线的OAM、伪线保护组，形成一个第一参数组1.1.1。
以非组对方式向割接组1.1中添加第一参数组1.1.1中工作伪线所基于的工作隧道，系统查找该工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组，形成一个第一参数组1.1.2。
以非组对方式向割接组1.1中添加第一参数组1.1.1中保护伪线所基于的工作隧道，系统查找该工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组，形成一个第一参数组1.1.3。
创建第二参数组1.1.4，该第二参数组包括一条工作隧道、工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组。
创建第二参数组1.1.5，该第二参数组包括一条工作隧道、工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组。
创建第二参数组1.1.6，该第二参数组包括一条TDM业务、工作伪线、工作伪线的OAM、保护伪线、保护伪线的OAM、伪线保护组。其中，工作伪线绑定第二参数组1.1.4中的工作隧道，保护伪线绑定第二参数组 1.1.5中的工作隧道。其中，第二参数组1.1.4中的工作隧道用于承载第二参数组1.1.6中的工作伪线，建第二参数组1.1.5中的工作隧道用于承载第二参数组1.1.6中的保护伪线。
本实施例提出的创建割接计划的装置，将割接参数组之间具有承载关系的割接业务进行绑定，保证割接计划的完整性。
参照图10所示，基于第一实施例提出本发明建立业务割接计划的装置的第四实施例。在本实施例中，该装置还包括如下模块：
步骤S70，将加入所述割接组中的所述第二参数组与加入所述割接组中的所述第一参数组形成割接对。
用户在割接组中创建割接参数组的时候，可以根据自己的需求进行判断是否组对创建，当需要组对创建时，发出形成割接对的指令，将加入割接组中的第一参数组合第二参数组形成割接对。
本实施例的主要目的在于创建割接对，一个第一参数组和一个第二参数组加入割接后形成割接对，这样，割接对中第一参数组释放的资源只能被与之成对的第二参数组所预支，其他第二参数组不能预支。一个割接对构成一个最小的割接替换动作，过程中，第一参数组代表的业务连接关系被从设备中拆除，替换为第二参数组所代表的业务连接关系，若割接过程中发生错误，则割接对自动回滚到割接操作开始前的状态。
参照图6所示，以在割接组中添加一条割接前仿真以太网专线为例创建一个割接组，查找该仿真以太网专线中的以太网业务、工作伪线、工作伪线的OAM、保护伪线、保护伪线的OAM、伪线保护组，形成一个第一参数组，并将此第一参数组加入一个新形成的割接对2.1.1中。
以组对方式向割接组2.1中添加割接对2.1.1中割接前工作伪线所基于的工作隧道，系统查找该工作隧道的OAM、保护隧道，保护隧道的OAM、隧道保护组，形成一个第一参数组，并将此第一参数组加入一个新形成的割接对2.1.2中。
以组对方式向割接组2.1中添加割接对2.1.1中割接前保护伪线所基于 的工作隧道，系统查找该工作隧道的OAM、保护隧道，保护隧道的OAM、隧道保护组，形成一个第一参数组，并将此第一参数组加入一个新形成的割接对2.1.3中。
为割接对2.1.2创建第二参数组，包括割接后的工作隧道、工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组。
为割接对2.1.3创建第二参数组，包括割接后的工作隧道、工作隧道的OAM、保护隧道、保护隧道的OAM、隧道保护组。
为割接对2.1.1创建第二参数组，包括割接后的以太网专线业务、工作伪线、工作伪线的OAM、保护伪线、保护伪线的OAM、伪线保护组。其中，工作伪线绑定割接对2.1.2中的割接后工作隧道，保护伪线绑定割接对2.1.3中的割接后工作隧道。
对于割接组中的割接对，假如彼此间没有操作依赖关系，比如：全部都是仿真业务割接对，或者虽然同时有隧道割接对和仿真业务割接对，但是他们并不存在承载关系，则此时也可以针对单个割接对发起割接或回滚。
可以理解的是，用户可以根据需求创建混合割接组，在割接组中，可以将创建第一参数组和第二参数组组对或不组对，以适应网络运维中多种割接需求。
本实施例提出的创建割接计划的装置，以组对的方式创建第一参数组、第二参数组，资源共享范围更可控，割接和回滚动作的控制粒度更细，灵活方便，而且，割接参数组间可根据需要灵活组对或不组对，适应网络运维中多种割接需求。
以上仅为本发明的优选实施例，并非因此限制本发明的专利范围，凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本发明的专利保护范围内。
工业实用性
如上所述，本发明实施例提供的一种建立业务割接计划的方法及装置具有以下有益效果：通过在割接计划中创建第一参数组和第二参数组，将割接参数组作为最小的割接单位，并且将待割接的第一业务中相互具有依存关系业务参数纳入同一个第一参数组中，将预先创建的第二业务中相互具有依存关系业务参数纳入同一个第二参数组中，从而使得待割接的第一业务和预先创建的第二业务中的业务参数能够完整的加入割接计划中。

Claims (10)

  1. 一种建立业务割接计划的方法，所述建立业务割接计划的方法包括：
    在割接计划中创建割接组；
    基于待割接的第一业务中各业务参数之间的依存关系将所述业务参数分为多个第一参数组；
    将所述第一参数组加入创建的所述割接组中；
    基于预先创建的第二业务中各业务参数之间的依存关系将所述业务参数分为多个第二参数组；
    将所述第二参数组加入创建的所述割接组中。
  2. 根据权利要求1所述的建立业务割接计划的方法，其中，所述基于待割接的第一业务中各业务参数之间的依存关系将所述业务参数分为多个第一参数组的步骤包括：
    将所待割接的第一业务中的业务参数进行两两对比，查找相互具有依存关系的所述业务参数；
    分别将相互具有依存关系的业务参数形成所述第一参数组。
  3. 根据权利要求2所述的建立业务割接计划的方法，其中，所述分别将相互具有依存关系的业务参数形成所述第一参数组的步骤之后，所述基于待割接的第一业务中各业务参数之间的依存关系将所述业务参数分为多个第一参数组的步骤包括：
    在除形成第一参数组的业务参数之外还存在与其它业务参数均无依存关系的独立业务参数时，将所述独立业务参数作为第一参数组。
  4. 根据权利要求1所述的建立业务割接计划的方法，其中，所述将所述第二参数组加入创建的所述割接组中的步骤之后，所述建立业务割接计划的方法还包括：
    将加入所述割接组中的所述第二参数组与加入所述割接组中的所述 第一参数组形成割接对。
  5. 根据权利要求1所述的建立业务割接计划的方法，其中，所述基于预先创建的第二业务中各业务参数之间的依存关系将所述业务参数分为多个第二参数组的步骤之后，所述建立业务割接计划的方法还包括：
    将所述多个第二参数组之间具有承载关系的所述第二业务进行绑定。
  6. 一种建立业务割接计划的装置，所述建立业务割接计划的装置包括：
    割接组模块，设置为在割接计划中创建割接组；
    第一分组模块，设置为基于待割接的第一业务中各业务参数之间的依存关系将所述业务参数分为多个第一参数组；
    第一添加模块，设置为将所述第一参数组加入创建的所述割接组中；
    第二分组模块，设置为基于预先创建的第二业务中各业务参数之间的依存关系将所述业务参数分为多个第二参数组；
    第二添加模块，设置为将所述第二参数组加入创建的所述割接组中。
  7. 根据权利要求6所述的建立业务割接计划的装置，其中，所述第一分组模块包括：
    查找单元，设置为将所待割接的第一业务中的业务参数进行两两对比，查找相互具有依存关系的所述业务参数；
    添加单元，设置为分别将相互具有依存关系的业务参数形成所述第一参数组。
  8. 根据权利要求7所述的建立业务割接计划的装置，其中，所述第一分组模块还包括：
    独立参数单元，设置为在除形成第一参数组的业务参数之外还存在与其它业务参数均无依存关系的独立业务参数时，将所述独立业务参数作为 第一参数组。
  9. 根据权利要求6所述的建立业务割接计划的装置，其中，所述建立业务割接计划的装置还包括：
    割接对模块，设置为将加入所述割接组中的所述第二参数组与加入所述割接组中的所述第一参数组形成割接对。
  10. 根据权利要求1所述的建立业务割接计划的装置，其中，所述建立业务割接计划的装置还包括：
    绑定模块，设置为将所述多个第二参数组之间具有承载关系的所述第二业务进行绑定。
PCT/CN2016/075550 2015-07-27 2016-03-03 建立业务割接计划的方法及装置 WO2016177071A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510445799.XA CN106411541B (zh) 2015-07-27 2015-07-27 建立业务割接计划的方法及装置
CN201510445799.X 2015-07-27

Publications (1)

Publication Number Publication Date
WO2016177071A1 true WO2016177071A1 (zh) 2016-11-10

Family

ID=57218453

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/075550 WO2016177071A1 (zh) 2015-07-27 2016-03-03 建立业务割接计划的方法及装置

Country Status (2)

Country Link
CN (1) CN106411541B (zh)
WO (1) WO2016177071A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114399062A (zh) * 2021-12-28 2022-04-26 飞思达技术（北京）有限公司 一种基于互联网电视智能运维割接场景自动值守的方法

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112350843B (zh) * 2019-08-09 2022-02-08 烽火通信科技股份有限公司 一种基于虚拟组件的场景式割接方法和系统
CN110472856A (zh) * 2019-08-09 2019-11-19 北京直真科技股份有限公司 基于自助式场景化流程编排的自动化网络割接管理方法
CN118606289A (zh) * 2023-02-28 2024-09-06 华为云计算技术有限公司 数据割接方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1801853A (zh) * 2004-12-31 2006-07-12 华为技术有限公司 电信管理网业务割接方法及系统
CN101488163A (zh) * 2008-12-02 2009-07-22 中国移动通信集团福建有限公司 光缆割接模拟系统
CN101567806A (zh) * 2008-12-26 2009-10-28 华为技术有限公司 网络设备的割接方法、装置及系统
CN101860842A (zh) * 2009-04-09 2010-10-13 大唐移动通信设备有限公司 一种数据割接的方法及装置
US20140317227A1 (en) * 2013-04-18 2014-10-23 Avaya Inc. System and method for network migration

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101494551A (zh) * 2008-01-22 2009-07-29 华为技术有限公司 业务割接的方法、装置及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1801853A (zh) * 2004-12-31 2006-07-12 华为技术有限公司 电信管理网业务割接方法及系统
CN101488163A (zh) * 2008-12-02 2009-07-22 中国移动通信集团福建有限公司 光缆割接模拟系统
CN101567806A (zh) * 2008-12-26 2009-10-28 华为技术有限公司 网络设备的割接方法、装置及系统
CN101860842A (zh) * 2009-04-09 2010-10-13 大唐移动通信设备有限公司 一种数据割接的方法及装置
US20140317227A1 (en) * 2013-04-18 2014-10-23 Avaya Inc. System and method for network migration

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114399062A (zh) * 2021-12-28 2022-04-26 飞思达技术（北京）有限公司 一种基于互联网电视智能运维割接场景自动值守的方法

Also Published As

Publication number Publication date
CN106411541B (zh) 2020-03-17
CN106411541A (zh) 2017-02-15

Similar Documents

Publication Publication Date Title
WO2016177071A1 (zh) 建立业务割接计划的方法及装置
US10574525B2 (en) Configuration agreement protocol method
CN103595826B (zh) 一种防止虚拟机ip和mac伪造的方法
TWI751402B (zh) 一種資料同步方法、分散式系統、電腦可讀取儲取媒體、電腦設備及分散式設備
WO2015131603A1 (zh) 一种差分升级方法、服务端及终端
DE102009043278A1 (de) Netzsynchronisation über IP-Netze
KR20150118975A (ko) 다중 사용자 컴퓨터 이용 기술에 대한 편집 충돌 관리 시스템 및 방법
WO2013178121A1 (zh) 基于业务的通信网络评估方法和装置
CN106936620B (zh) 一种告警事件的处理方法和处理装置
WO2016177207A1 (zh) 控制面、业务面分离的方法和系统、服务器、云计算平台
CN104579977A (zh) 一种sdn控制器的带约束多路径路由方法及系统
EP4050850A1 (en) Service upgrading method, device and system
CN106302076A (zh) 建立vxlan隧道的方法、系统及sdn控制器
BR112017020602B1 (pt) Método de configuração de chamada de múltiplos grupos e dispositivo
WO2016206359A1 (zh) 一种建立ptn业务割接计划的方法及装置
CN104205745B (zh) 报文处理的方法与设备
WO2017201475A1 (en) Systems and methods for non-disruptive continuous software delivery
CN106648964A (zh) 数据库备份方法及系统
WO2016101409A1 (zh) 数据倒换的方法、设备及系统
DE102009043279A1 (de) Netzsynchronisation über IP-Netze
CN107977310A (zh) 一种遍历测试命令生成方法及装置
CN110420460B (zh) 游戏场景中功能节点编辑的方法及装置
CN106549788B (zh) 业务保护变迁方法及装置
EP3043521B1 (en) Method and device for sending crossover command
CN105591771A (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: 16789065

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16789065

Country of ref document: EP

Kind code of ref document: A1