WO2019141211A1 - 端到端重路由的方法及装置 - Google Patents

端到端重路由的方法及装置 Download PDF

Info

Publication number
WO2019141211A1
WO2019141211A1 PCT/CN2019/072173 CN2019072173W WO2019141211A1 WO 2019141211 A1 WO2019141211 A1 WO 2019141211A1 CN 2019072173 W CN2019072173 W CN 2019072173W WO 2019141211 A1 WO2019141211 A1 WO 2019141211A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
service
cross
controller
update request
Prior art date
Application number
PCT/CN2019/072173
Other languages
English (en)
French (fr)
Inventor
钱佳
陆荣舵
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP19741265.3A priority Critical patent/EP3742682A4/en
Publication of WO2019141211A1 publication Critical patent/WO2019141211A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H04L45/04—Interdomain routing, e.g. hierarchical routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks

Definitions

  • the present disclosure relates to the field of communications technologies, for example, to a method and apparatus for end-to-end rerouting.
  • SDN Software Defined Network
  • the main features of SDN are: separation of control plane and data forwarding plane; centralized control and programmable network operation, thus achieving flexible network traffic.
  • the flexible deployment of control and network services provides a good platform for innovation in core networks and applications.
  • each service has its own survivability requirements, and different survivability requirements have different ability to resist network failures, so as to provide differentiated services for different customers.
  • the intelligent control plane is a distributed control plane.
  • the operations of creating, deleting, rerouting, etc. all require the interaction of distributed signaling. Even in a single domain, this is very complicated, let alone cross-domain. Interoperable.
  • cross-domain service recovery methods in the distributed control plane technology, in fact, due to the complexity of signaling interaction and interoperability, the distributed control plane has been unable to deploy cross-domain commercial applications in the project.
  • these requirements still exist in the software-defined network, and are becoming more and more urgent.
  • the cross-domain and multi-layer services in the related technologies have no ability to resist network failure.
  • the present disclosure provides a method and apparatus for end-to-end re-routing, which implements cross-domain end-to-end service rerouting in an SDN hierarchical controller architecture, so that traffic of cross-domain end-to-end services can be obtained under network failure. End-to-end recovery, or enable cross-domain end-to-end service paths to be switched to new paths.
  • the present disclosure provides a method for end-to-end re-routing, including: receiving a failure notification reported by a single domain controller; searching for the cross-domain end-to-end service corresponding to the failure notification according to the failure notification; The end-to-end service sends a service update request and a service establishment request to the single-domain controller corresponding to the single-domain service in the inter-domain end-to-end service to implement re-routing of the cross-domain end-to-end service.
  • the present disclosure also provides a method for end-to-end re-routing, including: receiving a first service update request, where the first service update request is used to request cross-domain end-to-end for a specified cross-domain end-to-end service. Re-routing the path; searching for the specified cross-domain end-to-end service according to the first service update request, and calculating the cross-domain re-routing path and the cross-domain re-routing path resource of the specified cross-domain end-to-end service; The connection service end point corresponding to the network side boundary port of each single domain in the cross-domain re-routing path resource is used as the connection service newly added to the single-domain service corresponding to each single domain in the specified cross-domain end-to-end service. The endpoint sends a second service update request to the single domain controller of the border domain through which the cross-domain rerouting path passes, and sends a service establishment request to the single domain controller of the intermediate domain through which the cross-domain rerouting path passes.
  • the present disclosure also provides an apparatus for end-to-end rerouting, which is applied to a multi-domain controller, including: a receiving module, configured to receive a fault notification reported by a single domain controller; and a searching module configured to search according to the fault notification
  • the fault notification is corresponding to the cross-domain end-to-end service;
  • the sending module is configured to send a service update request according to the single-domain controller corresponding to the single-domain service in the cross-domain end-to-end service according to the cross-domain end-to-end service And business establishment requests.
  • the present disclosure also provides an apparatus for end-to-end rerouting, which is applied to a multi-domain controller, including: a receiving module, configured to receive a first service update request, where the first service update request is used to request a designated service The cross-domain end-to-end service performs the re-routing of the cross-domain end-to-end path; the search module is configured to search for the specified cross-domain end-to-end service according to the first service update request, and calculate the specified cross-domain end-to-end The cross-domain re-routing path of the service and the cross-domain re-routing path resource; the sending module is configured to use the connection service end point corresponding to the network side boundary port of each single domain in the cross-domain rerouting path resource as the specified cross A new connection service endpoint that is added to the single-domain service corresponding to the single-domain service in the end-to-end service, and sends a second service update request to the single-domain controller of the border domain through which the cross-domain re-
  • the present disclosure also provides a storage medium including a stored program that executes any of the methods described above while the program is running.
  • the present disclosure also provides a processor configured to execute a program that executes any of the methods described above while the program is running.
  • FIG. 1 is a flowchart of a method for end-to-end rerouting provided by an embodiment
  • FIG. 2 is a flowchart of a method for end-to-end rerouting provided by another embodiment
  • FIG. 3 is a structural block diagram of an apparatus for end-to-end rerouting according to an embodiment
  • FIG. 4 is a structural block diagram of an apparatus for end-to-end rerouting provided by another embodiment
  • FIG. 5 is a schematic diagram of a cross-domain end-to-end connection service according to an embodiment
  • FIG. 6 is a schematic diagram of a cross-domain connection service before service rerouting according to an embodiment
  • FIG. 7 is a schematic diagram of a cross-domain connection service after service re-routing according to an embodiment
  • FIG. 8 is a schematic diagram of a cross-domain connection service before service rerouting according to another embodiment
  • FIG. 9 is a schematic diagram of a cross-domain connection service after service re-routing according to another embodiment.
  • the network architecture of this embodiment includes: multiple single domain controllers and multiple domain controllers, wherein each single domain controller controls one domain, multiple domain controllers control multiple domains, and two ports of inter-domain services may be located. Multiple domain controllers are connected to all single domain controllers in different domains. Applicable to SDN networks.
  • FIG. 1 is a flowchart of a method for end-to-end re-routing provided in this embodiment, as shown in FIG. The process includes the following steps.
  • Step S102 Receive a failure notification reported by the single domain controller.
  • Step S104 Search for the corresponding cross-domain end-to-end service according to the fault notification.
  • Step S106 Send a service update request and a service establishment request according to the single-domain controller corresponding to the single-domain service in the cross-domain end-to-end service according to the cross-domain end-to-end service. It may be to send a service update request and a service establishment request to all single domain controllers associated with the cross-domain end-to-end service (or all single-domain controllers of the domain via the cross-domain end-to-end service).
  • the technical problem that the cross-domain service cannot implement the end-to-end re-routing in the related technology is solved, and the cross-domain end under the SDN hierarchical controller architecture is realized.
  • the re-routing of the end-to-end service enables the cross-domain end-to-end service traffic to be recovered end-to-end under network failure, or the path of the cross-domain end-to-end service can be switched to the new path.
  • the failure notification reported by the receiving single domain controller includes at least one of the following: receiving a first failure notification of the single domain service recovery failure reported by the single domain controller, where the first failure notification carries the single domain service The universal unique identifier; the second fault notification generated by the inter-domain port fault reported by the single domain controller, wherein the second fault notification carries the universal unique identifier of the inter-domain port; and the inter-domain link reported by the single-domain controller is received.
  • searching for the corresponding cross-domain end-to-end service according to the failure notification comprises: locally searching for the cross-connection associated with the single-domain service according to the universal unique identifier of the single-domain service. Domain end-to-end business.
  • searching for the corresponding cross-domain end-to-end service according to the fault notification includes: locally searching for the port information of the saved inter-domain port according to the universal unique identifier of the inter-domain port; searching according to the port information All cross-domain end-to-end services carried on inter-domain ports.
  • searching for the corresponding cross-domain end-to-end service according to the fault notification includes: searching for the corresponding cross-domain end-to-end service according to the universal unique identifier of the inter-domain link.
  • the protection policy includes one of the following: dynamic recovery and preset recovery. Corresponding to the following two scenarios.
  • Scenario 1 The process of sending a service update request and a service establishment request according to the single-domain controller corresponding to the single-domain service in the cross-domain end-to-end service includes the following steps.
  • S120 Determine, when the protection type of the anti-fault type is dynamic recovery, and the recovery strategy is end-to-end recovery, determine an inter-area re-routing path and an inter-area re-routing path resource of the cross-domain end-to-end service.
  • the re-routing path and the inter-domain re-routing path resource are obtained by calculating the inter-domain path and the inter-domain resource of the re-routing path in real time.
  • Scenario 2 Sending a service update request and a service establishment request to a single domain controller according to the cross-domain end-to-end service includes the following steps.
  • S220 Determine, when the protection type of the anti-fault type is preset recovery, and the recovery strategy is end-to-end recovery, determine the cross-domain re-routing path and the cross-domain re-routing path resource of the cross-domain end-to-end service.
  • the rerouting path and the inter-domain rerouting path resource may be obtained by pre-presetting the cross-domain re-routing path and the inter-domain resource.
  • connection service end point corresponding to the network side border port of each single domain in the cross-domain re-routing path resource is used as the connection service added by the single-domain service corresponding to each single domain in the cross-domain end-to-end service.
  • the endpoint sends a service update request to the single domain controller of the border domain through which the rerouting path passes, and sends a service establishment request to the single domain controller of the intermediate domain through which the rerouting path passes.
  • the method further includes: receiving the response result of the service update request and the service establishment request sent by the single domain controller. And refining the information of the cross-domain end-to-end service according to the service information of each domain; in an embodiment, the response result carries the single-domain service information of the domain to which the single domain controller that receives the update request or the establishment request is located.
  • the fault is rectified, if the service is dynamically restored, you need to calculate the cross-domain path in real time. If it is preset, you can directly use the pre-configured preset path. If it is not a fault trigger, it is triggered manually.
  • the rerouting path calculation is performed for receiving the service update request; the main difference between the two types of rerouting requests is the trigger mode, one is a network failure trigger, and the other is a manual trigger.
  • the scheme of the manually triggered service update request is described below.
  • FIG. 2 is a flowchart of another method for end-to-end re-routing provided in this embodiment, as shown in FIG. The process includes the following steps.
  • Step S202 Receive a service first update request, where the first service update request is used to request re-routing of the cross-domain end-to-end path for the specified cross-domain end-to-end service.
  • Step S204 Search for the specified cross-domain end-to-end service according to the first service update request, and calculate the cross-domain re-routing path and the cross-domain re-routing path resource of the specified cross-domain end-to-end service.
  • step S206 the connection service end point corresponding to the network side boundary port of each single domain in the cross-domain re-routing path resource is added as the single-domain service corresponding to each single domain in the specified cross-domain end-to-end service.
  • the service end point is connected, and the second service update request is sent to the single domain controller of the border domain through which the rerouting path passes, and the service establishment request is sent to the single domain controller of the intermediate domain through which the rerouting path passes.
  • the first service update request includes: specifying a cross-domain end-to-end service: a universal unique identifier, an update service type, a connection service endpoint list, and a topology constraint, or the first service update request includes a specified cross-domain end A universal unique identifier for the end-to-end service, updated service type and topology constraints.
  • the topology constraint carries at least one of the following: loosely containing links, loosely containing nodes, strictly containing links, strictly including nodes, repelling nodes, repelling links, including node boundary points, and rejecting node boundary points.
  • the method according to the foregoing embodiment can be implemented by means of software plus a general hardware platform, and can also be implemented by hardware.
  • the technical solution of the present disclosure may be embodied in the form of a software product stored in a storage medium (such as Read-Only Memory (ROM) / Random Access Memory (Random Access Memory). , RAM, disk, CD-ROM, including a plurality of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the method described in any of the embodiments of the present disclosure.
  • ROM Read-Only Memory
  • Random Access Memory Random Access Memory
  • an apparatus for end-to-end rerouting is further provided, and the apparatus is configured to implement the foregoing embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the devices described in the following embodiments may be implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 3 is a structural block diagram of an apparatus for end-to-end rerouting according to an embodiment, which is applied to a multi-domain controller.
  • the apparatus includes: a receiving module 30 configured to receive a single domain controller for reporting The fault notification is provided; the search module 32 is configured to search for the corresponding cross-domain end-to-end service according to the fault notification; and the sending module 34 is configured to correspond to the single-domain service in the cross-domain end-to-end service according to the cross-domain end-to-end service.
  • the single domain controller sends a service update request and a service establishment request.
  • the apparatus includes: a receiving module 40 configured to receive a first service update. a request, where the first service update request is used to request re-routing of the cross-domain end-to-end path for the specified cross-domain end-to-end service; the searching module 42 is configured to search for the specified cross-domain end-to-end according to the first service update request.
  • the service calculates the cross-domain re-routing path and the cross-domain re-routing path resource of the specified cross-domain end-to-end service; the sending module 44 is configured to re-route the cross-domain re-routing path resource corresponding to the network side boundary port of each single domain
  • the connection service end point is a new connection service end point corresponding to the single domain service corresponding to each single domain in the specified cross-domain end-to-end service, and sends a second to the single domain controller of the boundary domain through which the cross-domain re-routing path passes.
  • the service update request sends a service establishment request to the single domain controller of the intermediate domain through which the cross-domain rerouting path passes.
  • the above plurality of modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the above modules are all located in the same processor; or, the plurality of modules are respectively in any combination. Located in different processors.
  • This embodiment provides a method for cross-domain end-to-end re-routing of cross-domain multi-layer services to solve the problem of end-to-end re-routing of cross-domain services in software-defined network technologies. Enable cross-domain end-to-end service traffic to be dynamically recovered under network failure or rerouted to other paths under manual requirements.
  • cross-domain end-to-end services and single-domain services involved in cross-domain services have been established through the interaction of hierarchical controllers, where each service information includes a universal unique identifier of the service, and the connection service endpoint (Connectivity Service End) Point) list, connectivity constraints, anti-fault constraints.
  • each service information includes a universal unique identifier of the service, and the connection service endpoint (Connectivity Service End) Point) list, connectivity constraints, anti-fault constraints.
  • connection service endpoint carries the Service Interface Point (SIP) index corresponding to the connection service endpoint and the adaptation information of multiple layer protocols
  • the service interface point includes the resource pool of the network multiple layer protocol.
  • Attribute providing resource information for each layer of the network; connectivity constraints carrying service type, requesting bandwidth information, routing policy, service level, etc.; anti-fault constraint carrying network level, anti-fault type, return mode, delay time, waiting Recovery time and other information; anti-failure types include recovery strategy and protection type; recovery strategy includes domain-by-domain recovery, end-to-end recovery, none; protection types include no protection, 1+1 protection, dynamic recovery, preset recovery, 1+1 Protect and recover.
  • SIP Service Interface Point
  • This embodiment provides a method for implementing re-routing of cross-domain end-to-end services by using interaction of hierarchical controllers, including: dynamic re-routing method for cross-domain end-to-end services, and cross-domain end-to-end A pre-re-routing method for services and a manual re-routing method for cross-domain end-to-end services to implement re-routing of cross-domain end-to-end services in three scenarios.
  • the dynamic rerouting method for cross-domain end-to-end services includes the following steps.
  • the multi-domain controller receives the notification of the single-domain service recovery failure reported by the single-domain controller or the notification of the inter-domain port failure.
  • the information carried in the notification of the failure of the single-domain service recovery includes the Universally Unique Identifier of the service, and the failure indication is restored.
  • the information carried in the notification that the inter-domain port fault is generated in this embodiment includes the universally unique identifier (Universally Unique Identifier) of the inter-domain port, and the degree of impact of the fault on the service.
  • the universally unique identifier Universally Unique Identifier
  • the multi-domain controller finds the inter-domain end-to-end service associated with the single-domain service in the multi-domain controller according to the universal unique identifier of the single-domain service carried in the notification, or according to the inter-domain port carried in the notification.
  • the universal unique identifier finds the saved port information in the multi-domain controller, and then finds all cross-domain end-to-end services carried on the inter-domain port, according to the found cross-domain end-to-end service in the anti-fault constraint Anti-fault type to determine subsequent processing.
  • the subsequent processing is: when the protection type is dynamic recovery and the recovery strategy is end-to-end recovery, the inter-domain path and the inter-domain path of the cross-domain re-routing path are found for the cross-domain end-to-end service found above. Calculate the resource and perform step 3.
  • the multi-domain controller uses the connection service endpoint corresponding to the network side border port of each single domain in the cross-domain rerouting path resource as the new connection of each single-domain service of the cross-domain service.
  • the service endpoint sends a service update request to the single domain controller of the border domain through which the rerouting path of the cross-domain service passes, and sends a service establishment request to the single domain controller of the intermediate domain that the re-routing path of the cross-domain service passes.
  • New single domain business
  • the information carried in the service update request includes a universal unique identifier of the single domain service, the service type is updated, and the service end point list is connected; the update service type is multi-domain recovery; and the endpoint in the connection service end point list is in addition to the single domain service original.
  • the connection service endpoints there are also new connection service endpoints; the information carried by the service establishment request includes the connection service endpoints of the single domain service, connectivity constraints, and anti-fault constraints.
  • the multi-domain controller receives the response result of the service update request or the service establishment request of each single domain controller, and completes the information of the cross-domain end-to-end service according to the service information of each domain, and cross-domain end-to-end The dynamic rerouting execution of the service ends.
  • the preset re-routing method for the cross-domain end-to-end service in this embodiment includes: in the second step of the dynamic re-routing method of the cross-domain end-to-end service, according to the found cross-domain end-to-end service in the anti-fault constraint
  • the anti-fault type determines the subsequent processing; in this embodiment, when the protection type is preset recovery and the recovery strategy is end-to-end recovery, the third step of the dynamic re-routing method of the cross-domain end-to-end service is directly performed;
  • the subsequent methods are the same as the subsequent methods of the dynamic rerouting method for the inter-domain end-to-end service, and are not described here.
  • the manual rerouting method for the cross-domain end-to-end service in this embodiment includes the following steps.
  • the multi-domain controller user requests the multi-domain controller to perform the optimized re-routing of the cross-domain end-to-end path for the specified cross-domain end-to-end service, and sends the first service update request to the multi-domain controller.
  • the information carried by the first service update request includes a universal unique identifier of the single domain service, an update service type, a connection service endpoint list, and a topology constraint;
  • the update service type is an update topology constraint;
  • the topology constraint may carry a loose inclusion chain. Road, loosely containing nodes, strictly containing links, strictly containing nodes, repelling nodes, repelling links, including node boundary points, and rejecting node boundary points.
  • the multi-domain controller finds the cross-domain end-to-end service of the multi-domain controller according to the universal unique identifier of the cross-domain service carried in the first service update request, and updates the topology constraint according to the updated service type and carries The topology constraint information is used to calculate the inter-domain path and the inter-domain resource.
  • FIG. 5 is a schematic diagram of an inter-domain end-to-end connection service, where the service interface points corresponding to the multi-domain connection service endpoint are service interface point 1 and service interface point 4.
  • the single-domain connection service corresponding to the multi-domain connection service is a single domain connection service 1 and a single domain connection service 2.
  • FIG. 6 FIG. 6
  • connection service endpoint of the single domain connection service 1 in the control domain A is a connection service end point 1 and a connection service end point 2, and a single domain connection.
  • the connection service endpoint of service 2 in control domain B is the connection service endpoint 3 and the connection service endpoint 4.
  • the single-domain connection service 1 of the control domain A fails, and the single-domain controller 1 recovers the single-domain connection service.
  • the recovery failure notification is sent to the multi-domain controller.
  • the information carried in the notification that the single-domain service fails to recover includes the Universally Unique Identifier of the service, and the failure indication is restored.
  • the multi-domain controller finds the cross-domain end-to-end service associated with the multi-domain controller according to the universal unique identifier of the single-domain service carried in the notification, and is resistant to failure according to the found cross-domain end-to-end service.
  • the anti-fault type in the constraint determines the subsequent processing.
  • the protection type is dynamic recovery and the recovery strategy is end-to-end recovery
  • the inter-domain path and domain of the cross-domain re-routing path is found for the cross-domain end-to-end service found above.
  • the calculation of the inter-resources is shown in Figure 7.
  • Figure 7 is a schematic diagram of the cross-domain connection service after the re-routing of the service.
  • the service interface points that the newly calculated inter-domain path needs to pass are: service interface point 1 - service interface point 5-Service Interface Point 6 - Service Interface Point 4, and then perform Step 3.
  • the multi-domain controller uses the connection service endpoint corresponding to the network side border port of each single domain in the cross-domain rerouting path resource as the new connection service of each single-domain service of the cross-domain service.
  • the endpoint that is, the connection service endpoint 5 of the control domain A, is the new connection service endpoint of the single-domain connection service of the domain, and the connection service endpoint 6 of the control domain B serves as the new connection service endpoint of the single-domain connection service of the domain.
  • the multi-domain controller sends a service update request to the single domain controllers 1 and 2.
  • the information carried in the service update request includes a universal unique identifier of the single domain service, an update service type, and a connection service endpoint list; wherein the update service type is multi-domain recovery; wherein the endpoints in the connection service endpoint list are in addition to each single domain service original In addition to connecting business endpoints, there are also new connection business endpoints mentioned above.
  • the node edge points in FIGS. 5-9 are network side boundary ports.
  • the multi-domain controller receives the response result of the service update request of each single domain controller, and completes the cross-domain end-to-end service information according to the service information of each domain, and the new cross-domain end-to-end service route.
  • the passing nodes are Node 1, Node 2, Node 4, and Node 3, respectively, and the dynamic rerouting execution of the cross-domain end-to-end service ends.
  • the example is based on the first example.
  • the inter-domain end-to-end service also passes through the intermediate domain control domain D, as shown in FIG. 8.
  • FIG. 8 is a schematic diagram of the cross-domain connection service before the second service re-routing.
  • the control domain D is controlled by the single domain controller 3, and the single domain controller is also controlled by the multi-domain controller.
  • the path connecting the services passes through Node 1, Node 5, and Node 3.
  • FIG. 9 is a schematic diagram of an inter-domain connection service after the second service re-routing, and the multi-domain controller uses the connection service end 5 of the control domain A as a new connection service end point of the single-domain connection service of the domain.
  • connection service end point 6 of the control domain B serves as the new connection service end point of the single domain connection service of the domain
  • connection service end points 9 and 10 of the control domain D serve as the new connection service end point of the single domain connection service of the domain.
  • the multi-domain controller sends a service update request to the single-domain controllers 1 and 2, and the multi-domain controller sends a service establishment request to the single-domain controller 3 to connect the service endpoints 9 and 10 as connection service endpoints.
  • the information carried in the service update request includes a universal unique identifier of the single domain service, an update service type, and a connection service endpoint list; wherein the update service type is multi-domain recovery; wherein the endpoints in the connection service endpoint list are in addition to each single domain service original In addition to connecting business endpoints, there are new connection business endpoints mentioned above.
  • the multi-domain controller receives the response of the service update request or the service establishment request of the multiple single-domain controllers, and the obtained connection service is as shown in FIG. 9.
  • the new cross-domain end-to-end service route passes through the nodes respectively. , Node 2, Node 6, Node 4, and Node 3, the dynamic rerouting execution of the cross-domain end-to-end service ends.
  • This example implements a preset re-routing method for cross-domain end-to-end services. Similar to the example 1, in the second step of the example 1, the type of anti-fault in the anti-fault constraint of the cross-domain end-to-end service is determined. Subsequent processing; when the protection type is preset recovery and the recovery strategy is end-to-end recovery, the multi-domain controller uses the cross-domain end-to-end connection service route that has been pre-calculated and set to perform cross-domain service recovery, and directly executes the instance. Steps 3 and 4 of 1 will not be repeated;
  • This example implements a manual rerouting method for cross-domain end-to-end services.
  • the multi-domain controller user requests the multi-domain controller to perform the optimized re-routing of the cross-domain end-to-end path for the specified cross-domain end-to-end service, and sends the first service update request to the multi-domain controller.
  • the information carried by the first service update request includes a universal unique identifier of the single domain service, an update service type, a connection service endpoint list, and a topology constraint; wherein the update service type is an update topology constraint; wherein the topology constraint may carry a loosely included link , loosely containing nodes, strictly containing links, strictly containing nodes, repelling nodes, repelling links, including node boundary points, and rejecting node boundary points.
  • the multi-domain controller finds the cross-domain end-to-end service of the multi-domain controller according to the universal unique identifier of the cross-domain service carried in the first service update request, and updates the topology constraint according to the updated service type and carries The topology constraint information is used to calculate the cross-domain path.
  • the subsequent processing method is the same as the third step and the fourth step of the first example, and will not be described again.
  • the cross-domain end-to-end service rerouting in the SDN hierarchical controller architecture is implemented, so that the traffic of the inter-domain end-to-end service can be recovered end-to-end under the network failure, or the cross-domain end is obtained.
  • the path of the end service can be switched to the new path under manual request.
  • the embodiment further provides a storage medium including a stored program, and the above program executes any one of the above methods when the program is running.
  • the storage medium may be configured to store program code for performing the following steps: S10, receiving a failure notification reported by a single domain controller; S20, searching for a cross-domain end-to-end corresponding to the failure notification according to the failure notification
  • the service sends a service update request and a service establishment request to the single domain controller corresponding to the single domain service in the cross-domain end-to-end service according to the cross-domain end-to-end service.
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk. At least one medium that can store program code.
  • the embodiment also provides a processor configured to run a program that executes the steps of any of the above methods when executed.
  • the foregoing procedure is used to perform the following steps: S10, receiving a fault notification reported by a single domain controller; S20, searching for a cross-domain end-to-end service corresponding to the fault notification according to the fault notification; S3, according to the cross-domain end
  • the end service sends a service update request and a service establishment request to a single domain controller corresponding to the single domain service in the cross-domain end-to-end service.
  • the at least one module or at least one step of the above-described disclosure may be implemented by a general-purpose computing device, and the at least one module or at least one step may be centralized on a single computing device or distributed over a network of multiple computing devices. .
  • at least one module or at least one step may be implemented by program code executable by a computing device, such that at least one module or at least one step may be stored in the storage device by the computing device, and at some
  • the steps shown or described may be performed in an order different than that herein, or at least one module or at least one step may be separately fabricated into at least one integrated circuit module, or at least one module or at least one step Multiple modules or steps are made into a single integrated circuit module.
  • the disclosure is not limited to any specific combination of hardware and software.

Landscapes

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

Abstract

本公开提供了一种端到端重路由的方法及装置，其中，该方法包括：接收单域控制器上报的故障通知；根据故障通知查找故障通知对应的跨域端到端业务；根据跨域端到端业务向跨域端到端业务的单域业务所对应的单域控制器发送业务更新请求和业务建立请求以实现所述跨域端到端业务的重路由。

Description

端到端重路由的方法及装置
本公开要求在2018年01月17日提交中国专利局、申请号为201810045886.X的中国专利申请的优先权，该申请的全部内容通过引用结合在本公开中。
技术领域
本公开涉及通信技术领域，例如涉及一种端到端重路由的方法及装置。
背景技术
软件定义网络(Software Defined Network，SDN)是一种网络架构，SDN的主要特征在于：控制面与数据转发面的分离；实现集中化的控制，可编程的网络操作，从而实现了网络流量的灵活控制和网络业务的灵活部署，为核心网络及应用的创新提供了良好的平台。
在传送网络通信领域，每个业务都有自己的生存性要求，不同的生存性要求下抗网络故障的能力不同，以便为不同的客户提供差异化的服务。随着智能控制平面的出现，用户可以根据业务或网络的需要而对业务进行人工的重路由操作。但是智能控制平面是分布式的控制平面，业务的创建，删除，重路由等操作均需要分布式信令的交互才能实现，即使在单域下，这也是非常复杂的，更别说跨域的互通了。虽然在分布式控制平面技术中，有较多的跨域业务的恢复方法，但实际上由于信令交互互通等复杂性问题，分布式的控制平面一直无法在工程中进行跨域商用的部署。可是这些需求在软件定义网络中依然存在，且越来越迫切，相关技术中的跨域多层的业务还没有抗网络故障的能力。
发明内容
本公开提供了一种端到端重路由的方法及装置，实现了SDN层次控制器架构下的跨域端到端业务的重路由，使得跨域端到端业务的流量能在网络故障下得到端到端恢复，或者使得跨域端到端业务的路径能换至新的路径。
本公开提供了一种端到端重路由的方法，包括：接收单域控制器上报的故障通知；根据所述故障通知查找所述故障通知对应的跨域端到端业务；根据所述跨域端到端业务向跨域端到端业务中的单域业务所对应的单域控制器发送业 务更新请求和业务建立请求以实现所述跨域端到端业务的重路由。
本公开还提供了一种端到端重路由的方法，包括：接收第一业务更新请求，其中，所述第一业务更新请求用于请求对指定跨域端到端业务进行跨域端到端路径的重路由；根据所述第一业务更新请求查找所述指定跨域端到端业务，计算所述指定跨域端到端业务的跨域重路由路径和跨域重路由路径资源；将所述跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为所述指定跨域端到端业务中所述每个单域对应的单域业务新增的连接业务端点，向所述跨域重路由路径所经过的边界域的单域控制器发送第二业务更新请求，向所述跨域重路由路径所经过的中间域的单域控制器发送业务建立请求。
本公开还提供了一种端到端重路由的装置，应用在多域控制器，包括：接收模块，设置为接收单域控制器上报的故障通知；查找模块，设置为根据所述故障通知查找所述故障通知对应的跨域端到端业务；发送模块，设置为根据所述跨域端到端业务向跨域端到端业务中的单域业务所对应的单域控制器发送业务更新请求和业务建立请求。
本公开还提供了一种端到端重路由的装置，应用在多域控制器，包括：接收模块，设置为接收第一业务更新请求，其中，所述第一业务更新请求用于请求对指定跨域端到端业务进行跨域端到端路径的重路由；查找模块，设置为根据所述第一业务更新请求查找所述指定跨域端到端业务，计算所述指定跨域端到端业务的跨域重路由路径和跨域重路由路径资源；发送模块，设置为将所述跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为所述指定跨域端到端业务中的所述每个单域对应的单域业务新增的连接业务端点，向所述跨域重路由路径所经过的边界域的单域控制器发送第二业务更新请求，向所述跨域重路由路径所经过的中间域的单域控制器发送业务建立请求。
本公开还提供了一种存储介质，所述存储介质包括存储的程序，所述程序运行时执行上述任意一种方法。
本公开还提供了一种处理器，所述处理器设置为运行程序，所述程序运行时执行上述任意一种方法。
附图说明
图1是一实施例提供的一种端到端重路由的方法的流程图；
图2是另一实施例提供的一种端到端重路由的方法的流程图；
图3是一实施例提供的一种端到端重路由的装置的结构框图；
图4是另一实施例提供的一种端到端重路由的装置的结构框图；
图5是一实施例提供的跨域端到端连接业务示意图；
图6是一实施例提供的业务重路由前跨域连接业务示意图；
图7是一实施例提供的业务重路由后跨域连接业务示意图；
图8是另一实施例提供的业务重路由前跨域连接业务示意图；
图9是另一实施例提供的业务重路由后跨域连接业务示意图。
具体实施方式
下文中将参考附图并结合实施例来说明本公开。
本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
本实施例的络架构包括：多个单域控制器、多域控制器，其中，每个单域控制器控制一个域，多域控制器控制多个域，跨域业务的两个端口可以位于不同的域中，多域控制器与所有单域控制器连接。适用于SDN网络。
在本实施例中提供了一种运行于上述网络架构的端到端重路由的方法，图1是本实施例提供的一种端到端重路由的方法的流程图，如图1所示，该流程包括如下步骤。
步骤S102，接收单域控制器上报的故障通知。
步骤S104，根据故障通知查找对应的跨域端到端业务。
步骤S106，根据跨域端到端业务向跨域端到端业务中的单域业务所对应的单域控制器发送业务更新请求和业务建立请求。可以是向跨域端到端业务所关联的所有单域控制器(或者是跨域端到端业务所经由域的所有单域控制器)发 送业务更新请求和业务建立请求。
通过上述步骤，通过向单域控制器发送业务更新请求和业务建立请求，解决了相关技术中跨域业务不能实现端到端重路由的技术问题，实现了SDN层次控制器架构下的跨域端到端业务的重路由，使得跨域端到端业务的流量能在网络故障下得到端到端恢复，或者使得跨域端到端业务的路径能换至新的路径。
在一实施例中，接收单域控制器上报的故障通知包括以下至少之一：接收单域控制器上报的单域业务恢复失败的第一故障通知，其中，第一故障通知携带单域业务的通用唯一识别码；接收单域控制器上报的域间端口故障产生的第二故障通知，其中，第二故障通知携带域间端口的通用唯一识别码；接收单域控制器上报的域间链路故障产生的第三故障通知，其中，第三故障通知携带域间链路的通用唯一识别码。
在一实施例中，在接收到第一故障通知的情况下，根据故障通知查找对应的跨域端到端业务包括：根据单域业务的通用唯一识别码在本地查找与单域业务关联的跨域端到端业务。在接收到第二故障通知的情况下，根据故障通知查找对应的跨域端到端业务包括：根据域间端口的通用唯一识别码在本地查找保存的域间端口的端口信息；根据端口信息查找域间端口上承载的所有跨域端到端业务。在接收到第三故障通知的情况下，根据故障通知查找对应的跨域端到端业务包括：根据域间链路的通用唯一识别码查找对应的跨域端到端业务。
在一实施例中，保护策略包括以下之一：动态恢复和预置恢复。分别对应以下两种场景。
场景一：根据跨域端到端业务向跨域端到端业务中的单域业务所对应的单域控制器发送业务更新请求和业务建立请求包括如下步骤。
S110，解析跨域端到端业务的抗故障类型.
S120，在所述抗故障类型的保护类型为动态恢复，恢复策略为端到端恢复的情况下，确定所述跨域端到端业务的跨域重路由路径和跨域重路由路径资源。在一实施例中，通过实时计算所述重路由路径的域间路径和域间资源，得到重路由路径和跨域重路由路径资源。
S130，向所述重路由路径所经过的边界域的单域控制器发送业务更新请求， 携带新增的连接业务端点，可以将跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为所述跨域端到端业务的所述每个单域业务新增的连接业务端点，向所述重路由路径所经过的中间域的单域控制器发送业务建立请求。
场景二：根据跨域端到端业务向单域控制器发送业务更新请求和业务建立请求包括如下步骤。
S210，解析跨域端到端业务的抗故障类型。
S220，在所述抗故障类型的保护类型为预置恢复，恢复策略为端到端恢复的情况下，确定所述跨域端到端业务的跨域重路由路径和跨域重路由路径资源。在一实施例中，可以通过提前预置的跨域重路由路径和域间资源，得到重路由路径和跨域重路由路径资源。
S230，将跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为所述跨域端到端业务中的每个单域对应的单域业务新增的连接业务端点，向所述重路由路径所经过的边界域的单域控制器发送业务更新请求，向所述重路由路径所经过的中间域的单域控制器发送业务建立请求。
在一实施例中，在根据跨域端到端业务向单域控制器发送业务更新请求和业务建立请求之后，方法还包括：接收单域控制器发送的业务更新请求和业务建立请求的响应结果，并根据每个域的业务信息完善跨域端到端业务的信息；在一实施例中，响应结果携带接收更新请求或建立请求的单域控制器所属域的单域业务信息。
在收到故障通知下，如果是动态恢复的业务，则需要实时计算跨域路径；如果是预置恢复的，则可以直接使用预先配置好的预置路径；如果不是故障触发，而是人工触发的，则为收到业务更新请求而进行重路由路径计算；这两大类的重路由请求，主要区别在于触发方式，一个是网络故障触发，一个是人工触发。下面对人工触发的业务更新请求的方案进行说明。
在本实施例中提供了一种运行于上述网络架构的端到端重路由的方法，图2是本实施例提供的另一种端到端重路由的方法的流程图，如图2所示，该流程包括如下步骤。
步骤S202，接收业务第一更新请求，其中，第一业务更新请求用于请求对指定跨域端到端业务进行跨域端到端路径的重路由。
步骤S204，根据第一业务更新请求查找指定跨域端到端业务，计算指定跨域端到端业务的跨域重路由路径和跨域重路由路径资源。
步骤S206，将跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为指定跨域端到端业务中的所述每个单域对应的单域业务新增的连接业务端点，向重路由路径所经过的边界域的单域控制器发送第二业务更新请求，向重路由路径所经过的中间域的单域控制器发送业务建立请求。
在一实施例中，第一业务更新请求包括指定跨域端到端业务的：通用唯一识别码，更新业务类型，连接业务端点列表以及拓扑约束，或者，第一业务更新请求包括指定跨域端到端业务的通用唯一识别码，更新业务类型以及拓扑约束。拓扑约束携带以下至少之一：松散包含链路，松散包含节点，严格包含链路，严格包含节点，排斥节点，排斥链路，包含节点边界点，排斥节点边界点。
通过以上的实施方式的描述，本领域的技术人员可以了解到根据上述实施例的方法可借助软件加通用硬件平台的方式来实现，当然也可以通过硬件来实现。基于这样的理解，本公开的技术方案可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如只读存储器(Read-Only Memory，ROM)/随机存取存储器(Random Access Memory，RAM)、磁碟、光盘)中，包括多个指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开任意实施例所述的方法。
实施例2
在本实施例中还提供了一种端到端重路由的装置，该装置设置为实现上述实施例，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置可以以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是一实施例提供的一种端到端重路由的装置的结构框图，应用在多域控制器，如图3所示，该装置包括：接收模块30，设置为接收单域控制器上报的故障通知；查找模块32，设置为根据故障通知查找对应的跨域端到端业务；发送模块34，设置为根据跨域端到端业务向跨域端到端业务中的单域业务所对 应的单域控制器发送业务更新请求和业务建立请求。
图4是另一实施例提供的一种端到端重路由的装置的结构框图，应用在多域控制器，如图4所示，该装置包括：接收模块40，设置为接收第一业务更新请求，其中，第一业务更新请求用于请求对指定跨域端到端业务进行跨域端到端路径的重路由；查找模块42，设置为根据第一业务更新请求查找指定跨域端到端业务，计算指定跨域端到端业务的跨域重路由路径和跨域重路由路径资源；发送模块44，设置为将跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为指定跨域端到端业务中的所述每个单域对应的单域业务新增的连接业务端点，向跨域重路由路径所经过的边界域的单域控制器发送第二业务更新请求，向跨域重路由路径所经过的中间域的单域控制器发送业务建立请求。
上述多个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述多个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本实施例提供一种跨域多层业务的跨域端到端重路由的方法，以解决软件定义网络技术中的跨域业务的端到端重路由问题。使跨域端到端业务流量能够在网络故障下动态得到恢复或者在人工要求下重路由到其他路径上。
网络中已经通过层次控制器的交互建立了跨域端到端业务以及跨域业务下涉及到的单域业务，其中每个业务信息都包括业务的通用唯一识别码，连接业务端点(Connectivity Service End Point)列表，连通性约束，抗故障约束。
本实施例中，连接业务端点携带与连接业务端点对应的业务接口点(Service Interface Point，SIP)索引以及多个层协议的适配信息，而业务接口点包含该网络多个层协议的资源池属性，为该网络的每个层提供资源信息；连通性约束携带业务类型，请求带宽信息，路由策略，服务等级等信息；抗故障约束携带网络层次，抗故障类型，返回方式，延迟时间，等待恢复时间等信息；抗故障类型包括恢复策略和保护类型；恢复策略包括逐域恢复，端到端恢复，无；保护类型包括无保护，1+1保护，动态恢复，预置恢复，1+1保护且恢复。
本实施例提供了一种利用层次控制器的交互配合来实现跨域端到端业务的 重路由的方法，所述方法包括：跨域端到端业务的动态重路由方法、跨域端到端业务的预置重路由方法和跨域端到端业务的人工重路由方法，以在三个场景实现跨域端到端业务的重路由。
跨域端到端业务的动态重路由方法包括如下步骤。
第1步，多域控制器收到单域控制器上报的单域业务恢复失败的通知或者域间端口故障产生的通知。
本实施例中，单域业务恢复失败的通知携带的信息包括该业务的通用唯一识别码(Universally Unique Identifier)，恢复失败指示。
本实施例中域间端口故障产生的通知携带的信息包括该域间端口的通用唯一识别码(Universally Unique Identifier)，故障对业务的影响程度。
第2步，多域控制器根据通知中携带的单域业务的通用唯一识别码找到多域控制器中与该单域业务关联的跨域端到端业务或者，根据通知中携带的域间端口的通用唯一识别码找到多域控制器中的保存的该端口信息，再找到该域间端口上承载的所有跨域端到端业务，根据找到的跨域端到端业务的抗故障约束中的抗故障类型来决定后续处理。
在一实施例中，后续处理为，当保护类型为动态恢复且恢复策略为端到端恢复时，则对上述找到的跨域端到端业务进行跨域重路由路径的域间路径和域间资源的计算，再执行第3步。
第3步，多域控制器将已经算好的跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为该跨域业务的每个单域业务新增的连接业务端点，向跨域业务的重路由路径所经过的边界域的单域控制器发送业务更新请求，向跨域业务的重路由路径所经过的中间域的单域控制器发送业务建立请求，创建新的单域业务。
本实施例中，业务更新请求携带的信息包括单域业务的通用唯一识别码，更新业务类型，连接业务端点列表；更新业务类型为多域恢复；连接业务端点列表中的端点除了单域业务原有的连接业务端点外，还有新增的连接业务端点；业务建立请求携带的信息包括该单域业务的连接业务端点，连通性约束，抗故障约束。
第4步，多域控制器收到每个单域控制器的业务更新请求或业务建立请求的响应结果，根据每个域的业务信息完善跨域端到端业务的信息，跨域端到端业务的动态重路由执行结束。
本实施例跨域端到端业务的预置重路由方法包括：在跨域端到端业务的动态重路由方法的第2步中，根据找到的跨域端到端业务的抗故障约束中的抗故障类型来决定后续处理；本实施例中，当保护类型为预置恢复且恢复策略为端到端恢复时，则直接执行跨域端到端业务的动态重路由方法的第3步；且后续处理方法和跨域端到端业务的动态重路由方法的后续方法相同，不再赘述。
本实施例跨域端到端业务的人工重路由方法包括如下步骤。
第1步，多域控制器用户请求多域控制器对指定的跨域端到端业务进行跨域端到端路径的优化重路由，向多域控制器发送第一业务更新请求。
本实施例中，第一业务更新请求携带的信息包括单域业务的通用唯一识别码，更新业务类型，连接业务端点列表，拓扑约束；更新业务类型为更新拓扑约束；拓扑约束可携带松散包含链路，松散包含节点，严格包含链路，严格包含节点，排斥节点，排斥链路，包含节点边界点，排斥节点边界点。
第2步，多域控制器根据第一业务更新请求中携带的跨域业务的通用唯一识别码找到多域控制器的跨域端到端业务，并根据更新业务类型为更新拓扑约束以及所携带的拓扑约束信息进行域间路径和域间资源的计算。
后续处理方法和跨域端到端业务的动态重路由方法的第3步及后续方法相同，不再赘述。
本实施例还包括以下实例：
实例一
该实例实现跨域端到端业务的动态重路由方法，该实例中多域控制器控制两个单域控制器：单域控制器1和单域控制器2，两个单域控制器分别控制两个控制域：控制域A和控制域B。多域控制器建立了一个跨域端到端连接业务：多域连接业务1。如附图5所示，图5是实例一跨域端到端连接业务示意图，该多域连接业务端点对应的业务接口点为业务接口点1和业务接口点4。该多域连接业务对应的单域连接业务为单域连接业务1和单域连接业务2。如附图6所示， 图6是实例一业务重路由前跨域连接业务示意图，单域连接业务1在控制域A中的连接业务端点为连接业务端点1和连接业务端点2，单域连接业务2在控制域B中的连接业务端点为连接业务端点3和连接业务端点4。
第1步，控制域A的单域连接业务1发生故障，单域控制器1对该单域连接业务进行恢复，恢复失败后，向多域控制器发送恢复失败通知。其中单域业务恢复失败的通知携带的信息包括该业务的通用唯一识别码(Universally Unique Identifier)，恢复失败指示。
第2步，多域控制器根据通知中携带的单域业务的通用唯一识别码找到多域控制器中与之关联的跨域端到端业务，根据找到的跨域端到端业务的抗故障约束中的抗故障类型来决定后续处理，当保护类型为动态恢复且恢复策略为端到端恢复时，则对上述找到的跨域端到端业务进行跨域重路由路径的域间路径和域间资源的计算，如附图7所示，图7是实例一业务重路由后跨域连接业务示意图，新计算出的域间路径需要经过的业务接口点为：业务接口点1-业务接口点5-业务接口点6-业务接口点4，再执行第3步。
第3步，多域控制器将已经算好的跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为该跨域业务的每个单域业务新的连接业务端点，即控制域A的连接业务端点5作为该域的单域连接业务的新增连接业务端点，控制域B的连接业务端点6作为该域的单域连接业务的新增连接业务端点。多域控制器向单域控制器1和2发送业务更新请求。其中业务更新请求携带的信息包括单域业务的通用唯一识别码，更新业务类型，连接业务端点列表；其中更新业务类型为多域恢复；其中连接业务端点列表中的端点除了每个单域业务原有的连接业务端点外，还有上述新增的连接业务端点。
本实施例中，图5-图9中的节点边缘点为网络侧边界端口。
第4步，多域控制器收到每个单域控制器的业务更新请求的响应结果，根据每个域的业务信息完善跨域端到端业务的信息，新的跨域端到端业务路由经过的节点分别为节点1、节点2、节点4和节点3，跨域端到端业务的动态重路由执行结束。
实例二
该实例基于实例一，在实例一的网络拓扑中，跨域端到端业务还经过了中 间域控制域D，如附图8所示，图8是实例二业务重路由前跨域连接业务示意图，控制域D由单域控制器3控制，单域控制器同样由多域控制器进行控制。连接业务的路径经过了节点1、节点5和节点3。
该实例的前两个步骤与实例一相同，第3步，多域控制器新计算的跨域路径经过节点1、节点2、节点6、节点4和节点3，即需要在控制域D进行新的连接业务的建立。如附图9所示，图9是实例二业务重路由后跨域连接业务示意图，多域控制器将控制域A的连接业务端点5作为该域的单域连接业务的新增连接业务端点，控制域B的连接业务端点6作为该域的单域连接业务的新连接业务端点，控制域D的连接业务端点9和10作为该域的单域连接业务的新连接业务端点。多域控制器向单域控制器1和2发送业务更新请求，多域控制器向单域控制器3发送业务建立请求，以连接业务端点9和10作为连接业务端点。其中业务更新请求携带的信息包括单域业务的通用唯一识别码，更新业务类型，连接业务端点列表；其中更新业务类型为多域恢复；其中连接业务端点列表中的端点除了每个单域业务原有的连接业务端点外，还有新增的上述连接业务端点。
多域控制器收到多个单域控制器的业务更新请求或业务建立请求的响应，得到的连接业务如附图9所示，新的跨域端到端业务路由经过的节点分别为节1、节点2、节点6、节点4和节点3，跨域端到端业务的动态重路由执行结束。
实例三
该实例实现跨域端到端业务的预置重路由方法，与实例1类似，在实例1的第2步中，根据找到的跨域端到端业务的抗故障约束中的抗故障类型来决定后续处理；当保护类型为预置恢复且恢复策略为端到端恢复时，则多域控制器利用已经预先计算并设置的跨域端到端连接业务路由进行跨域业务的恢复，直接执行实例1中的第3步和第4步，不再赘述；
实例四
该实例实现跨域端到端业务的人工重路由方法。
第1步，多域控制器用户请求多域控制器对指定的跨域端到端业务进行跨域端到端路径的优化重路由，向多域控制器发送第一业务更新请求。
其中，第一业务更新请求携带的信息包括单域业务的通用唯一识别码，更新业务类型，连接业务端点列表，拓扑约束；其中更新业务类型为更新拓扑约束；其中拓扑约束可携带松散包含链路，松散包含节点，严格包含链路，严格包含节点，排斥节点，排斥链路，包含节点边界点，排斥节点边界点。
第2步，多域控制器根据第一业务更新请求中携带的跨域业务的通用唯一识别码找到多域控制器的跨域端到端业务，并根据更新业务类型为更新拓扑约束以及所携带的拓扑约束信息进行跨域路径的计算。
后续处理方法同实例一的第3步和第4步，不再赘述。
通过本实施例，实现了SDN层次控制器架构下的跨域端到端业务的重路由，使得跨域端到端业务的流量能在网络故障下得到端到端恢复，或者使得跨域端到端业务的路径能在人工请求下换至新的路径。
实施例4
本实施例还提供了一种存储介质，该存储介质包括存储的程序，上述程序运行时执行上述的任意一种方法。
在一实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：S10，接收单域控制器上报的故障通知；S20，根据故障通知查找故障通知对应的跨域端到端业务；S30，根据跨域端到端业务向跨域端到端业务中的单域业务所对应的单域控制器发送业务更新请求和业务建立请求。
在一实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、移动硬盘、磁碟或者光盘等至少一种可以存储程序代码的介质。
本实施例还提供了一种处理器，该处理器设置为运行程序，该程序运行时执行上述任意一种方法中的步骤。
在一实施例中，上述程序用于执行以下步骤：S10，接收单域控制器上报的故障通知；S20，根据故障通知查找故障通知对应的跨域端到端业务；S3，根据跨域端到端业务向跨域端到端业务中的单域业务所对应的单域控制器发送业务更新请求和业务建立请求。
本实施例中的具体示例可以参考上述实施例所描述的示例，本实施例在此 不再赘述。
上述的本公开的至少一个模块或至少一个步骤可以用通用的计算装置来实现，上述至少一个模块或至少一个步骤可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上。在一实施例中，至少一个模块或至少一个步骤可以用计算装置可执行的程序代码来实现，从而，可以将至少一个模块或至少一个步骤存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将至少一个模块或至少一个步骤分别制作成至少一个集成电路模块，或者将至少一个模块或至少一个步骤中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。

Claims (16)

  1. 一种端到端重路由的方法，包括：
    接收单域控制器上报的故障通知；
    根据所述故障通知查找所述故障通知对应的跨域端到端业务；
    根据所述跨域端到端业务向所述跨域端到端业务中的单域业务所对应的单域控制器发送业务更新请求和业务建立请求以实现所述跨域端到端业务的重路由。
  2. 根据权利要求1所述的方法，其中，接收单域控制器上报的故障通知包括以下至少之一：
    接收单域控制器上报的单域业务恢复失败的第一故障通知，其中，所述第一故障通知携带所述单域业务的通用唯一识别码；
    接收单域控制器上报的域间端口故障产生的第二故障通知，其中，所述第二故障通知携带所述域间端口的通用唯一识别码；
    接收单域控制器上报的域间链路故障产生的第三故障通知，其中，所述第三故障通知携带所述域间链路的通用唯一识别码。
  3. 根据权利要求2所述的方法，其中，在接收到所述第一故障通知的情况下，根据所述故障通知查找所述故障通知对应的跨域端到端业务包括：
    根据所述单域业务的通用唯一识别码在本地查找与所述单域业务关联的跨域端到端业务。
  4. 根据权利要求2所述的方法，其中，在接收到所述第二故障通知的情况下，根据所述故障通知查找所述故障通知对应的跨域端到端业务包括：
    根据所述域间端口的通用唯一识别码在本地查找保存的所述域间端口的端口信息；
    根据所述端口信息查找所述域间端口上承载的所有跨域端到端业务。
  5. 根据权利要求2所述的方法，其中，在接收到所述第三故障通知的情况下，根据所述故障通知查找所述故障通知对应的跨域端到端业务包括：
    根据所述域间链路的通用唯一识别码查找对应的跨域端到端业务。
  6. 根据权利要求1-5任一项所述的方法，其中，根据所述跨域端到端业务向所述跨域端到端业务中的单域业务所对应的单域控制器发送业务更新请求和业务建立请求包括：
    获取所述跨域端到端业务的跨域重路由路径和跨域重路由路径资源；
    将所述跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为所述指定跨域端到端业务中的所述每个单域对应的单域业务新增的连接业务端点，向所述跨域重路由路径所经过的边界域的单域控制器发送业务更新请求，以及向所述跨域重路由路径所经过的中间域的单域控制器发送业务建立请求。
  7. 根据权利要求6所述的方法，其中，获取所述跨域端到端业务的跨域重路由路径和跨域重路由路径资源包括：
    解析所述跨域端到端业务的抗故障类型；
    在所述抗故障类型的保护类型为动态恢复情况下，通过实时计算所述跨域端到端业务的跨域重路由路径的域间路径和域间资源，得到跨域重路由路径和跨域重路由路径资源。
  8. 根据权利要求6所述的方法，其中，获取所述跨域端到端业务的跨域重路由路径和跨域重路由路径资源包括：
    解析所述跨域端到端业务的抗故障类型；
    在所述抗故障类型的保护类型为预置恢复的情况下，通过预置的跨域重路由路径和域间资源，得到所述跨域端到端业务的跨域重路由路径和跨域重路由路径资源。
  9. 根据权利要求1-8任一项所述的方法，在根据所述跨域端到端业务向所述跨域端到端业务中的单域业务所对应的单域控制器发送业务更新请求和业务建立请求之后，还包括：
    接收所述跨域端到端业务中的单域业务所对应的单域控制器发送的所述业务更新请求的响应结果和所述业务建立请求的响应结果，并根据每个域的业务信息完善跨域端到端业务的信息；
    其中，所述业务更新请求的响应结果携带接收所述业务更新请求的单域控 制器所属域中关于单域业务的业务信息，所述业务建立请求的响应结果携带接收所述业务建立请求的单域控制器所属域的单域业务信息。
  10. 一种端到端重路由的方法，包括：
    接收第一业务更新请求，其中，所述第一业务更新请求用于请求对指定跨域端到端业务进行跨域端到端路径的重路由；
    根据所述第一业务更新请求查找所述指定跨域端到端业务，计算所述指定跨域端到端业务的跨域重路由路径和跨域重路由路径资源；
    将所述跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为所述指定跨域端到端业务中的所述每个单域对应的单域业务新增的连接业务端点，向所述跨域重路由路径所经过的边界域的单域控制器发送第二业务更新请求，向所述跨域重路由路径所经过的中间域的单域控制器发送业务建立请求。
  11. 根据权利要求10所述的方法，其中，所述第一业务更新请求包括所述指定跨域端到端业务的通用唯一识别码，更新业务类型，连接业务端点列表以及拓扑约束，或者，所述第一业务更新请求包括所述指定跨域端到端业务的通用唯一识别码，更新业务类型以及拓扑约束。
  12. 根据权利要求11所述的方法，其中，所述拓扑约束携带以下至少之一：松散包含链路，松散包含节点，严格包含链路，严格包含节点，排斥节点，排斥链路，包含节点边界点以及排斥节点边界点。
  13. 一种端到端重路由的装置，应用在多域控制器，包括：
    接收模块，设置为接收单域控制器上报的故障通知；
    查找模块，设置为根据所述故障通知查找所述故障通知对应的跨域端到端业务；
    发送模块，设置为根据所述跨域端到端业务向所述跨域端到端业务中的单域业务所对应的单域控制器发送业务更新请求和业务建立请求。
  14. 一种端到端重路由的装置，应用在多域控制器，包括：
    接收模块，设置为接收第一业务更新请求，其中，所述第一业务更新请求 用于请求对指定跨域端到端业务进行跨域端到端路径的重路由；
    查找模块，设置为根据所述第一业务更新请求查找所述指定跨域端到端业务，计算所述指定跨域端到端业务的跨域重路由路径和跨域重路由路径资源；
    发送模块，设置为将所述跨域重路由路径资源中每个单域的网络侧边界端口所对应的连接业务端点作为所述指定跨域端到端业务中的所述每个单域对应的单域业务新增的连接业务端点，向所述跨域重路由路径所经过的边界域的单域控制器发送第二业务更新请求，向所述跨域重路由路径所经过的中间域的单域控制器发送业务建立请求。
  15. 一种存储介质，所述存储介质包括存储的程序，所述程序运行时执行权利要求1至12中任一项所述的方法。
  16. 一种处理器，设置为运行程序，所述程序运行时执行权利要求1至12中任一项所述的方法。
PCT/CN2019/072173 2018-01-17 2019-01-17 端到端重路由的方法及装置 WO2019141211A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP19741265.3A EP3742682A4 (en) 2018-01-17 2019-01-17 Peer-to-peer forwarding method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810045886.XA CN110048944A (zh) 2018-01-17 2018-01-17 端到端重路由的方法及装置
CN201810045886.X 2018-01-17

Publications (1)

Publication Number Publication Date
WO2019141211A1 true WO2019141211A1 (zh) 2019-07-25

Family

ID=67273538

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/072173 WO2019141211A1 (zh) 2018-01-17 2019-01-17 端到端重路由的方法及装置

Country Status (3)

Country Link
EP (1) EP3742682A4 (zh)
CN (1) CN110048944A (zh)
WO (1) WO2019141211A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114520760A (zh) * 2020-11-20 2022-05-20 华为技术有限公司 一种跨域故障分析的方法及***

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114615190B (zh) * 2020-11-23 2023-04-18 华为技术有限公司 重路由方法、通信装置及存储介质
CN114363404A (zh) * 2021-12-29 2022-04-15 凯通科技股份有限公司 一种混合组网下的以太网业务端到端还原方法及相关设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7180866B1 (en) * 2002-07-11 2007-02-20 Nortel Networks Limited Rerouting in connection-oriented communication networks and communication systems
CN101001170A (zh) * 2006-01-10 2007-07-18 华为技术有限公司 业务故障恢复方法
CN101645795A (zh) * 2008-11-07 2010-02-10 中国科学院声学研究所 一种基于snmp协议网络管理***之间信息共享方法及其***
CN103634134A (zh) * 2012-08-24 2014-03-12 中兴通讯股份有限公司 跨域保护互通方法及***

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100454837C (zh) * 2005-12-02 2009-01-21 华为技术有限公司 一种实现跨域路由分离的方法
CN103580904A (zh) * 2012-08-08 2014-02-12 中兴通讯股份有限公司 域间故障信息的发送方法及装置
CN106452817B (zh) * 2015-08-12 2019-05-31 中国电信股份有限公司 保护配置管理方法和***

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7180866B1 (en) * 2002-07-11 2007-02-20 Nortel Networks Limited Rerouting in connection-oriented communication networks and communication systems
CN101001170A (zh) * 2006-01-10 2007-07-18 华为技术有限公司 业务故障恢复方法
CN101645795A (zh) * 2008-11-07 2010-02-10 中国科学院声学研究所 一种基于snmp协议网络管理***之间信息共享方法及其***
CN103634134A (zh) * 2012-08-24 2014-03-12 中兴通讯股份有限公司 跨域保护互通方法及***

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114520760A (zh) * 2020-11-20 2022-05-20 华为技术有限公司 一种跨域故障分析的方法及***
CN114520760B (zh) * 2020-11-20 2023-08-22 华为技术有限公司 一种跨域故障分析的方法及***

Also Published As

Publication number Publication date
CN110048944A (zh) 2019-07-23
EP3742682A4 (en) 2021-06-30
EP3742682A1 (en) 2020-11-25

Similar Documents

Publication Publication Date Title
US9769054B2 (en) Network topology discovery method and system
EP1863235B1 (en) Method and system for multi-domain route computation
US7765283B2 (en) Network provisioning in a distributed network management architecture
US8014300B2 (en) Resource state monitoring method, device and communication network
WO2019141211A1 (zh) 端到端重路由的方法及装置
CN100454837C (zh) 一种实现跨域路由分离的方法
JP2013510459A (ja) 分離的なパス計算アルゴリズム
JP5869041B2 (ja) ネットワークトポロジ要求を物理ネットワークにマッピングする方法、コンピュータプログラム製品、モバイル通信システム及びネットワーク構成プラットフォーム
US11924042B2 (en) System and method to reduce flooding topology size
WO2015045466A1 (ja) 通信制御装置、通信制御システム、通信制御方法及び通信制御プログラム
US10666562B2 (en) Network path computation method, apparatus, and system
WO2016206502A1 (zh) 一种业务控制方法及装置、计算机存储介质
CN112822108A (zh) 建立lsp的方法、服务器及路由器
WO2020244550A1 (zh) 路径计算方法及存储介质、电子装置
WO2023015897A1 (zh) 一种光网络智能控制方法、装置及***
WO2016165061A1 (zh) 一种业务保护方法及装置
CA2417680A1 (en) Two-stage reconnect system and method
EP3082306A1 (en) Re-routing method and system, and network device
EP2466813B1 (en) Method and system for determining initiator and terminator in forwarding adjacency label switched path
WO2018077313A1 (zh) 连接能力的通告方法及装置
US10992573B2 (en) Multi-layer LSP control method and apparatus
WO2020118505A1 (zh) 一种业务路径建立的方法、网络设备和***
WO2017066923A1 (zh) 一种业务路径建立的方法、网络控制器和***
WO2010022600A1 (zh) 多层网络连接建立方法、节点设备及多层网络***
WO2020038425A1 (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: 19741265

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019741265

Country of ref document: EP

Effective date: 20200817