WO2015154423A1 - 跨域业务处理方法、装置及系统 - Google Patents

跨域业务处理方法、装置及系统 Download PDF

Info

Publication number
WO2015154423A1
WO2015154423A1 PCT/CN2014/089088 CN2014089088W WO2015154423A1 WO 2015154423 A1 WO2015154423 A1 WO 2015154423A1 CN 2014089088 W CN2014089088 W CN 2014089088W WO 2015154423 A1 WO2015154423 A1 WO 2015154423A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
domain
shared
cross
protection
Prior art date
Application number
PCT/CN2014/089088
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 WO2015154423A1 publication Critical patent/WO2015154423A1/zh

Links

Images

Definitions

  • the present invention relates to the field of communications, and in particular to a cross-domain service processing method, apparatus, and system.
  • protection methods for intra-domain faults such as Ethernet linear protection G.8031, OTN linear protection (G.873.1) and OTN ring network protection (G.873.2) and MPLS-TP linear protection (G) .8131) and so on, mainly for protection on a single autonomous domain, and for the protection of cross-domain paths or services, especially in the case of a failure of an interconnected node or link, the protection method in a single domain cannot restore cross-domain services, and requires two Inter-domain switching can restore and protect inter-AS services.
  • the linkage switching affects the independence of protection switching in each domain and brings the complexity of protection switching. This is the result that operators do not expect.
  • FIG. 1 is a schematic diagram of a scenario in which two faults occur simultaneously in the same domain in the related art. As shown in FIG. 1 , when the working path on the domain 1 and the shared link on the two domains fail simultaneously The working path and the protection path in the domain are faulty. If the current 1:1 linear protection method is adopted, the cross-domain service cannot be protected. If the two domains are switched together, the independence of the inter-domain protection switching will be affected.
  • the present invention provides a cross-domain service processing method, apparatus, and system, to at least solve the problem in the related art that there is no cross-domain protection scheme for maintaining independent handover on each domain.
  • a cross-domain service processing method including: establishing a shared path for sharing node information between the interconnected active and standby nodes among the inter-domain interconnection active and standby nodes; The shared node information shared by the shared path between the interconnected active and standby nodes, and the detected fault, and the cross-domain service is forwarded.
  • the method further includes: establishing, in the respective domain, the shared path a protection path, wherein the protection path performs a function of the shared path when the shared path fails.
  • the method further includes: determining, by the corresponding protection path in each domain, a function of preferentially executing the shared path when the shared path fails Priority of determining a protection path for performing the function of the shared path according to the priority.
  • the forwarding processing of the cross-domain service includes one of the following: cross-domain in the first domain If the working path on the path is faulty, the interconnected standby node sends the cross-domain service received from the protection path in the first domain to the interconnected primary node by using the shared path, where the interconnected primary node is The protection path identifier encapsulated in the cross-domain service, and the binding relationship between the working path and the protection path, and the cross-domain service is forwarded through the working path in the second domain; If the working path and the shared path are both faulty, the interconnected standby node sends the cross-domain service received from the protection path in the first domain to the interconnected primary node through the protection path of the shared path.
  • the interconnection master node passes the protection path identifier encapsulated in the cross-domain service and the binding relationship between the work path and the protection path.
  • the working path in the two domains forwards the cross-domain service; in the case that the interconnected primary node is faulty, the interconnected standby node is based on the binding relationship between the working path and the protected path shared by the interconnected primary node.
  • the protection path in the first domain is spliced with the protection path in the second domain, and the cross-domain service received from the protection path in the first domain is protected by the protection path in the second domain.
  • Cross-domain services are forwarded.
  • a cross-domain service processing apparatus including: a first establishing module, configured to establish, between the inter-domain interconnection active and standby nodes, mutually share node information between the interconnected active and standby nodes
  • the processing module is configured to forward the cross-domain service according to the shared node information shared between the interconnected active and standby nodes according to the established shared path and the detected fault.
  • the apparatus further includes: a second establishing module, configured to establish a corresponding protection path in each domain for the shared path, wherein the protection path performs the shared path when the shared path fails Features.
  • a second establishing module configured to establish a corresponding protection path in each domain for the shared path, wherein the protection path performs the shared path when the shared path fails Features.
  • the apparatus further includes: a determining module, configured to determine, for a corresponding protection path in each domain, a priority of a function of preferentially executing the shared path when the shared path fails, according to the priority determining A protection path that performs the function of the shared path.
  • a determining module configured to determine, for a corresponding protection path in each domain, a priority of a function of preferentially executing the shared path when the shared path fails, according to the priority determining A protection path that performs the function of the shared path.
  • the processing module comprises one of: a first processing unit, configured to receive, in the case of a working path failure on the cross-domain path in the first domain, the interconnecting standby node to receive from the protection path in the first domain
  • the cross-domain service that is sent to the interconnected primary node is sent by the shared path, and the interconnected primary node is based on the protection path identifier encapsulated in the cross-domain service and the binding relationship between the working path and the protection path.
  • the second processing unit is configured to: when the working path on the cross-domain path in the first domain is faulty, and the shared path is faulty, the interconnecting standby node
  • the inter-domain service received from the protection path in the first domain is sent to the interconnection master node by using the protection path of the shared path, and the interconnection master node is identified according to the protection path encapsulated in the cross-domain service.
  • the binding relationship between the working path and the protection path, and the cross-domain service is forwarded through the working path in the second domain; the third processing And, in the case that the interconnection master node is faulty, the interconnection standby node associates the protection path in the first domain with the protection path according to a binding relationship between the working path and the protection path shared by the interconnection master node.
  • the protection path in the second domain is spliced, and the cross-domain service received from the protection path in the first domain is forwarded by the protection path in the second domain.
  • a cross-domain service processing system comprising: one or more first domains, one or more second domains, and the one or more first domains and the one or The plurality of second domains are interconnected by the interconnecting active and standby nodes, wherein the interconnected active and standby nodes share the shared node information of the other node according to the shared path established between the interconnected active and standby nodes; And further configured to forward, by the shared path, the cross-domain service received from the protection path in the first domain to the failure of the working path in the first domain and/or the failure of the primary node The interconnected master node.
  • the interconnecting active and standby nodes are further configured to share the shared node information and the forwarding process of the cross-domain service by using a protection path of the shared path if the shared path fails.
  • a shared path for sharing node information between the interconnected active and standby nodes is established between the active and standby nodes of the inter-domain interconnection; sharing shared between the interconnected active and standby nodes according to the established shared path
  • the node information and the detected faults are forwarded to the cross-domain service, and the problem that the cross-domain protection scheme for maintaining independent handover on each domain does not exist in the related technology is solved, thereby achieving the interconnection link or In the case of a node failure, the effect of protection switching independence and simplicity on each domain is maintained.
  • FIG. 1 is a schematic diagram of a scenario in which two faults occur simultaneously in the same domain in the related art
  • FIG. 2 is a flowchart of a cross-domain service processing method according to an embodiment of the present invention
  • FIG. 3 is a structural block diagram of a cross-domain service processing apparatus according to an embodiment of the present invention.
  • FIG. 4 is a block diagram 1 of a preferred structure of a cross-domain service processing apparatus according to an embodiment of the present invention
  • FIG. 5 is a block diagram 2 of a preferred structure of a cross-domain service processing apparatus according to an embodiment of the present invention
  • FIG. 6 is a block diagram showing a preferred structure of a processing module 34 in a cross-domain service processing apparatus according to an embodiment of the present invention
  • FIG. 7 is a structural block diagram of a cross-domain service processing system according to an embodiment of the present invention.
  • FIG. 8 is a structural block diagram of a cross-domain service processing system in accordance with a preferred embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a cross-domain path protection structure according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of an intra-domain fault protection structure according to a preferred embodiment 1 of the present invention.
  • FIG. 11 is a schematic diagram of an interconnection node failure protection structure according to a preferred embodiment 2 of the present invention.
  • FIG. 12 is a schematic structural diagram of a cross-domain branch path and a shared tunnel simultaneous failure according to a preferred embodiment 3 of the present invention
  • FIG. 13 is a flow chart of cross-domain service protection according to a preferred embodiment 4 of the present invention.
  • FIG. 2 is a flowchart of a cross-domain service processing method according to an embodiment of the present invention. As shown in FIG. 2, the process includes the following steps:
  • Step S202 establishing a shared path for sharing node information between the active and standby nodes of the interconnection between the primary and secondary nodes of the inter-domain interconnection;
  • step S204 the cross-domain service is forwarded according to the shared node information shared between the active and standby nodes and the detected fault according to the established shared path.
  • a shared path for sharing node information between the active and standby nodes is established between the primary and secondary nodes of the inter-domain interconnection; the shared node information shared between the active and standby nodes according to the established shared path, and the detected.
  • the problem is that the cross-domain service is forwarded and processed, and the problem that the cross-domain protection scheme that can maintain the independent handover on each domain does not exist in the related technology, so that in the case that the interconnection link or the node is faulty, the maintenance is maintained. The effect of switching independence and simplicity on the domain is protected.
  • the priority of the function of preferentially executing the shared path when the shared path fails may be determined for the corresponding protection path in each domain, and the priority is determined according to the priority.
  • the protection path used to perform the function of the shared path may be determined for the corresponding protection path in each domain, and the priority is determined according to the priority.
  • the interconnected standby node When forwarding the inter-domain service based on the shared node information shared between the active and standby nodes based on the established shared path and the detected fault, different forwarding processes may be used depending on the scenario in which the failure occurs: for example, In the case that the working path on the cross-domain path in the first domain is faulty, the interconnected standby node sends the cross-domain service received from the protection path in the first domain to the interconnected primary node through the shared path, and the interconnected primary node is based on the cross-domain service.
  • the protection path identifier encapsulated in the medium and the binding relationship between the working path and the protection path, and the cross-domain service is forwarded through the working path in the second domain; for example, the working path on the cross-domain path in the first domain
  • the interconnected standby node sends the cross-domain service received from the protection path in the first domain to the interconnected primary node through the protection path of the shared path.
  • the interconnected primary node is encapsulated according to the cross-domain service.
  • the protection path identifier, and the binding relationship between the working path and the protection path, through the work in the second domain The path forwards the cross-domain service.
  • the interconnected standby node protects the protection path in the first domain according to the binding relationship between the working path and the protection path shared by the interconnected primary node.
  • the splicing is performed on the protection path in the second domain, and the cross-domain service received from the protection path in the first domain is forwarded to the cross-domain service through the protection path in the second domain.
  • a cross-domain service processing device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 3 is a structural block diagram of a cross-domain service processing apparatus according to an embodiment of the present invention. As shown in FIG. 3, the apparatus includes a first establishing module 32 and a processing module 34. The apparatus will be described below.
  • the first establishing module 32 is configured to establish a shared path for sharing node information between the active and standby nodes in the inter-domain interconnection
  • the processing module 34 is connected to the first establishing module 32, and is configured to establish The shared path shares the shared node information between the active and standby nodes, and the detected faults, and forwards the cross-domain services.
  • FIG. 4 is a block diagram of a preferred structure of a cross-domain service processing apparatus according to an embodiment of the present invention. As shown in FIG. 4, the apparatus includes a second setup module 42 in addition to all the modules shown in FIG. The second establishing module 42 is described.
  • the second establishing module 42 is connected to the first establishing module 32, and is configured to establish a corresponding protection path in each domain for the shared path, wherein the protection path performs the function of sharing the path when the shared path fails.
  • FIG. 5 is a block diagram of a preferred structure of a cross-domain service processing apparatus according to an embodiment of the present invention. As shown in FIG. 5, the apparatus includes a determining module 52 in addition to all the modules shown in FIG. Module 52 is described.
  • the determining module 52 is connected to the second establishing module 42, and is configured to determine, for the corresponding protection path in each domain, a priority of a function of preferentially executing the shared path when the shared path fails, and determine, according to the priority, a method for executing the shared path.
  • the protection path of the function is connected to the second establishing module 42, and is configured to determine, for the corresponding protection path in each domain, a priority of a function of preferentially executing the shared path when the shared path fails, and determine, according to the priority, a method for executing the shared path.
  • FIG. 6 is a block diagram of a preferred structure of the processing module 34 in the cross-domain service processing apparatus according to the embodiment of the present invention.
  • the processing module 34 includes one of the following: a first processing unit 62, a second processing unit 64, The third processing unit 66 will be described below with respect to the processing module 34.
  • the first processing unit 62 is configured to: when the working path is faulty on the cross-domain path in the first domain, the interconnected standby node sends the cross-domain service received from the protection path in the first domain to the interconnected primary node through the shared path.
  • the interconnecting node forwards the cross-domain service through the working path in the second domain according to the protection path identifier encapsulated in the cross-domain service and the binding relationship between the working path and the protection path; the second processing unit 64 If the working path and the shared path are both faulty on the cross-domain path in the first domain, the interconnected standby node sends the cross-domain service received from the protection path in the first domain to the interconnected master through the protection path of the shared path.
  • the node the interconnecting node forwards the cross-domain service through the working path in the second domain according to the protection path identifier encapsulated in the cross-domain service and the binding relationship between the working path and the protection path; the third processing unit 66 , in the case that the interconnected primary node fails, the interconnected standby node is based on the working path shared from the interconnected primary node.
  • the binding relationship between the paths is spliced between the protection path in the first domain and the protection path in the second domain, and the cross-domain service received from the protection path in the first domain passes the protection path in the second domain to cross-domain The service performs forwarding processing.
  • the system 70 includes: one or more first domains 72, one or more second domains 74, one or more The first domain and the one or more second domains are interconnected by the interconnecting master node 76 and the interconnecting standby node 78.
  • the interconnecting master node 76 and the interconnecting standby node 78 share each other according to a shared path established between the interconnected active and standby nodes.
  • the shared node information of the other node; the interconnected standby node 78 is further configured to pass the cross-domain service received from the protection path in the first domain if the working path in the first domain fails and/or the primary node fails.
  • the shared path is forwarded to the interconnected master node.
  • the interconnecting master node 76 and the interconnecting standby node 78 are further configured to share the shared node information and the forwarding processing of the cross-domain service through the protection path of the shared path if the shared path fails.
  • the protection problem of the cross-domain service cannot be solved by the existing single-domain protection method.
  • the information sharing between the active and standby nodes is used to implement independent protection on each domain, which can avoid faults in one domain and cause path switching on other adjacent domains to bring operational complexity.
  • FIG. 8 is a structural block diagram of the cross-domain service processing system according to a preferred embodiment of the present invention.
  • the system mainly includes the following structure: a path configuration module 82 (same as the first establishing module 32 and/or the second The establishing module 42), the information sharing module 84, the service forwarding module 86 (both functions are combined with the processing module 34 described above), and the protection switching module 88 (same function as the processing module 34 described above) are described below.
  • the path configuration module 82 is configured to configure a shared link or tunnel between the active and standby nodes, and configure a corresponding protection link or tunnel for the shared link or tunnel on each domain.
  • the information sharing module 84 the module is located on the active and standby nodes of the two domain interconnections, and the information of the link detection state, the assigned label, and the binding relationship between the active and standby nodes is marked with the corresponding configuration state information identifier.
  • the peer node is sent through the shared tunnel to ensure that both the active and standby nodes know the binding relationship between the working path identifier and the protection path identifier, and the working and protection path state information.
  • the service forwarding module 86 when detecting that the working path in the domain is faulty, the backup interconnecting node receives the service from the protection path and forwards the packet to the master node through the shared tunnel;
  • the protection switching module 88 when a fault is detected on the shared link or the shared tunnel, the corresponding service is triggered to be sent to the corresponding node through its corresponding protection path or tunnel according to the priority of the configured protection link or the tunnel;
  • FIG. 9 is a schematic diagram of a cross-domain path protection structure according to an embodiment of the present invention. As shown in FIG. 9 , for an inter-domain network, implementing cross-domain path or service protection mainly includes the following processes:
  • 1 is a cross-domain path. Configure a corresponding intra-domain protection path for the branch path on each domain to perform service protection. For a shared tunnel or link between the active and standby nodes, configure a protection on the two domains sharing the link. a tunnel or link and set a protection priority for the protection link or tunnel on the two domains;
  • the protected service is switched to the corresponding intra-domain protection path according to the traditional 1:1 protection method.
  • the device After receiving the service packet sent from the protection path, the device performs the service information identifier, and then pushes the service packet into the shared tunnel and forwards the packet to the interconnected node.
  • the interconnected master node receives the service packet forwarded by the shared tunnel, and identifies the packet as a service information packet according to the service information identifier, and then identifies the protection path encapsulated by the service packet, such as a label;
  • the service message is re-pressed into the original working path for transmission;
  • FIG. 10 is a schematic diagram of an intra-domain fault protection structure according to a preferred embodiment 1 of the present invention. As shown in FIG. 10, the following processing is included:
  • a 1 is to configure a protection path (AC) for the cross-domain branch path (AB) on domain 1, and a corresponding protection path (DC) for the cross-domain branch path (DB) on domain 2, and at the primary and secondary interconnection node B.
  • AC protection path
  • DC protection path
  • DB cross-domain branch path
  • Interconnection master node B identifies the domain 1 cross-domain branch path (AB), the cross-domain branch path (BD) identifier spliced on domain 2, and the binding relationship between the two cross-domain branch paths. After being configured, the configuration information status identifier is sent to the backup node C before being pushed into the shared tunnel.
  • AB domain 1 cross-domain branch path
  • BD cross-domain branch path
  • the interconnected standby node C sends the protection path (AC) identifier corresponding to the cross-domain branch path (AB) on the domain 1 configured on the domain 1 and the protection path (DC) identifier corresponding to the cross-domain branch path (DB) on the domain 2 To the primary interconnect node B;
  • the backup interconnect node C When the backup interconnect node C receives the service packet sent from the protection path (AC), it directly puts the service packet with the corresponding service information identifier, encapsulates it into the shared tunnel of the interconnected nodes B and C, and sends it to the primary interconnect. Node B;
  • B When B receives the service packet sent from the shared tunnel, it determines that the service packet is based on the service information identifier encapsulated on the B, and then determines the corresponding cross-domain branch path according to the identifier of the encapsulated protection path, and then passes The cross-domain branch path (BD) on the adjacent domain 2 is transmitted to the node 2 on the domain 2;
  • BD cross-domain branch path
  • connection node failure protection structure according to a preferred embodiment 2 of the present invention. As shown in FIG. 11, the following processing is included:
  • the interconnected backup node C When the interconnected backup node C receives the fault information sent from the A or D protection path, and C detects that there is a fault between the shared work and the protection tunnel between the interconnected primary node B, it is saved according to the node.
  • Preferred Embodiment 3 Cross-domain branch path and shared tunnel fail simultaneously
  • FIG. 12 is a schematic structural diagram of a cross-domain branch path and a shared tunnel simultaneous failure according to a preferred embodiment 3 of the present invention. As shown in FIG. 12, the following processing is included:
  • step 1, 2, 3, 4 is equivalent to preferred embodiment 1; when there is a fault in both the cross-domain branch path (AB) and the shared tunnel (BC); first, when A detects the cross-domain branch path (AB) on domain 1 If there is a fault, the service on the cross-domain branch path is switched to its corresponding protection path (AC), and the protection switching request information is sent to the peer C node.
  • AB cross-domain branch path
  • BC shared tunnel
  • the C node When the C node receives the protection switching request information sent by the A node, it determines to receive the service from the protection path; meanwhile, when it also detects that there is a fault between the shared tunnel and the Node B, it sends the C node to B. The information is also switched to its corresponding protection tunnel (CDB) and sent to the Node B; in addition, protection switching request information is generated to the Node B;
  • CDB protection tunnel
  • the Node B When the Node B receives the protection switching request from the C node, it switches to the protection tunnel (CDB) to receive the service packet sent by the C node; and after receiving the service packet sent by the C node, the Node B identifies the service message according to the service information. If the service packet is judged to be a service packet, the identifier of the cross-domain branch path corresponding to the B-node is determined according to the identifier of the protection path on the service packet, and then switched to the cross-domain branch path (BD) transmission on the domain 2.
  • CDB protection tunnel
  • FIG. 13 is a flowchart of cross-domain service protection according to a preferred embodiment 4 of the present invention. As shown in FIG. 13, the process includes the following steps:
  • Step S1302 Configure a protection path for the branch path on the cross-domain path in each domain.
  • Step S1304 Configure a corresponding protection path on each domain for the shared path.
  • Step S1306 The interconnected active and standby nodes share information through the shared path.
  • Step S1308 it is determined whether the fault is detected, if the determination result is no, the process proceeds to step S1310, otherwise proceeds to step S1312;
  • Step S1310 continuing fault detection
  • Step S1312 it is determined whether there is a single domain path failure, if the determination result is yes, proceed to step S1314, otherwise proceed to step S1316;
  • Step S1316 it is determined whether there is an interconnection node failure, if the determination result is yes, proceeds to step S1318, otherwise proceeds to step S1320;
  • step S1318 both domains start 1:1 protection
  • step S1320 the cross-domain branch path and the shared path are simultaneously faulty, and the 1:1 protection and shared path protection in the single domain are started.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the above embodiments and the preferred embodiments solve the problem that the cross-domain protection scheme for maintaining independent handover on each domain does not exist in the related art, and thus, in the case that the interconnection link or the node fails. , to maintain the effect of protection switching independence and simplicity on each domain.

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)
  • Hardware Redundancy (AREA)

Abstract

本发明提供了一种跨域业务处理方法、装置及系统，其中，该方法包括：在跨域互联主备节点间建立用于在互联主备节点间相互共享节点信息的共享路径；依据建立的共享路径在互联主备节点间共享的共享节点信息，以及检测到的故障，对跨域业务进行转发处理，通过本发明，解决了相关技术中不存在对于能保持各域上独立切换的跨域保护方案的问题，进而达到了在互联链路或节点出现故障的情况下，保持各域上保护切换独立性和简单性的效果。

Description

跨域业务处理方法、装置及系统 技术领域
本发明涉及通信领域，具体而言，涉及一种跨域业务处理方法、装置及系统。
背景技术
对于当前保护技术中，主要针对域内故障的保护方法，如：以太网线性保护G.8031，OTN线性保护(G.873.1)和OTN环网保护(G.873.2)以及MPLS-TP线性保护(G.8131)等等，主要针对单个自治域上保护，而对于跨域路径或业务的保护，特别在互联节点或链路出现故障情况下，仅凭单域内保护方法是恢复不了跨域业务，需要两域上联动倒换才能对跨域业务进行恢复和保护，但这样联动倒换会影响到各域保护倒换的独立性，带来保护切换的复杂性，这是运营商所不期望的结果。另外，当前存在一些方案，通过控制平面信令，预先建立一个跨域端到端保护路径对跨域工作路径进行端到端保护，但这种方式，实现起来比较复杂，需要每个域上控制平面进行相邻域拓扑学习；还有一种方案，通过在域间链路建立静态绑定备份域间路径来保护域间链路故障情况下，进行保护，带来配置麻烦和操作不灵活性；而且当前itu-t SG15 Q9工作组正在研究和制定G.MDSP(Multi-Domain Segment Protection)标准文档，一个主要network objective就是需要各域上保护倒换行为保持独立性(independent)原则。下面对该问题进行举例说明，图1是相关技术中同一域同时两处故障的场景示意图，如图1所示，当在域1上工作路径和其两域上共享链路同时出现故障时，其域上工作路径和保护路径都出现故障，若采用当前1:1线性保护方法，是无法进行跨域业务的保护。若采用两域之间相互联动切换，会影响到域间保护切换的独立性。
然而，在相关技术中并不存在对于能保持各域上独立切换的跨域保护方案。
发明内容
本发明提供了一种跨域业务处理方法、装置及系统，以至少解决相关技术中不存在对于能保持各域上独立切换的跨域保护方案的问题。
根据本发明的一个方面，提供了一种跨域业务处理方法，包括：在跨域互联主备节点间建立用于在所述互联主备节点间相互共享节点信息的共享路径；依据建立的所述共享路径在所述互联主备节点间共享的共享节点信息，以及检测到的故障，对所述跨域业务进行转发处理。
优选地，在在所述跨域互联主备节点间建立用于在所述互联主备节点间相互共享节点信息的所述共享路径之后，还包括：为所述共享路径建立在各个域中对应的保护路径，其中，所述保护路径在所述共享路径发生故障时执行所述共享路径的功能。
优选地，在为所述共享路径建立在各个域中对应的所述保护路径之后，还包括：对各个域中对应的保护路径确定在所述共享路径发生故障时优先执行所述共享路径的功能的优先级，依据所述优先级确定用于执行所述共享路径的功能的保护路径。
优选地，依据建立的所述共享路径在所述互联主备节点间共享的共享节点信息，以及检测到的故障，对所述跨域业务进行转发处理包括以下之一：在第一域内跨域路径上的工作路径故障的情况下，互联备节点将从所述第一域内的保护路径上接收到的所述跨域业务通过所述共享路径发送给互联主节点，所述互联主节点依据所述跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对所述跨域业务进行转发处理；在第一域内跨域路径上的工作路径以及所述共享路径均故障的情况下，互联备节点将从所述第一域内的保护路径上接收到的所述跨域业务通过所述共享路径的保护路径发送给互联主节点，所述互联主节点依据所述跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对所述跨域业务进行转发处理；在互联主节点故障的情况下，所述互联备节点依据从互联主节点共享的工作路径与保护路径之间的绑定关系，将所述第一域内的保护路径与所述第二域内的保护路径进行拼接，将从所述第一域内的保护路径上接收到的所述跨域业务通过所述第二域内的保护路径对所述跨域业务进行转发处理。
根据本发明的另一方面，提供了一种跨域业务处理装置，包括：第一建立模块，设置为在跨域互联主备节点间建立用于在所述互联主备节点间相互共享节点信息的共享路径；处理模块，设置为依据建立的所述共享路径在所述互联主备节点间共享的共享节点信息，以及检测到的故障，对所述跨域业务进行转发处理。
优选地，该装置还包括：第二建立模块，设置为为所述共享路径建立在各个域中对应的保护路径，其中，所述保护路径在所述共享路径发生故障时执行所述共享路径的功能。
优选地，该装置还包括：确定模块，设置为对各个域中对应的保护路径确定在所述共享路径发生故障时优先执行所述共享路径的功能的优先级，依据所述优先级确定用于执行所述共享路径的功能的保护路径。
优选地，所述处理模块包括以下之一：第一处理单元，设置为在第一域内跨域路径上的工作路径故障的情况下，互联备节点将从所述第一域内的保护路径上接收到的所述跨域业务通过所述共享路径发送给互联主节点，所述互联主节点依据所述跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对所述跨域业务进行转发处理；第二处理单元，设置为在第一域内跨域路径上的工作路径以及所述共享路径均故障的情况下，互联备节点将从所述第一域内的保护路径上接收到的所述跨域业务通过所述共享路径的保护路径发送给互联主节点，所述互联主节点依据所述跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对所述跨域业务进行转发处理；第三处理单元，设置为在互联主节点故障的情况下，所述互联备节点依据从互联主节点共享的工作路径与保护路径之间的绑定关系，将所述第一域内的保护路径与所述第二域内的保护路径进行拼接，将从所述第一域内的保护路径上接收到的所述跨域业务通过所述第二域内的保护路径对所述跨域业务进行转发处理。
根据本发明的还一方面，提供了一种跨域业务处理系统，包括：一个或多个第一域，一个或多个第二域，所述一个或多个第一域与所述一个或多个第二域通过互联主备节点互联，其中，所述互联主备节点，依据在所述互联主备节点间建立的共享路径，相互共享对方节点的共享节点信息；所述互联备节点，还设置为在所述第一域内的工作路径发生故障和/或主节点发生故障的情况下，将从所述第一域内的保护路径接收到的所述跨域业务通过所述共享路径转发给所述互联主节点。
优选地，所述互联主备节点，还设置为在所述共享路径发生故障的情况下，通过所述共享路径的保护路径共享所述共享节点信息，以及对所述跨域业务的转发处理。
通过本发明，采用在跨域互联主备节点间建立用于在所述互联主备节点间相互共享节点信息的共享路径；依据建立的所述共享路径在所述互联主备节点间共享的共享节点信息，以及检测到的故障，对所述跨域业务进行转发处理，解决了相关技术中不存在对于能保持各域上独立切换的跨域保护方案的问题，进而达到了在互联链路或节点出现故障的情况下，保持各域上保护切换独立性和简单性的效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是相关技术中同一域同时两处故障的场景示意图；
图2是根据本发明实施例的跨域业务处理方法的流程图；
图3是根据本发明实施例的跨域业务处理装置的结构框图；
图4是根据本发明实施例的跨域业务处理装置的优选结构框图一；
图5是根据本发明实施例的跨域业务处理装置的优选结构框图二；
图6是根据本发明实施例的跨域业务处理装置中处理模块34的优选结构框图；
图7是根据本发明实施例的跨域业务处理系统的结构框图；
图8是根据本发明优选实施例的跨域业务处理系统的结构框图；
图9是根据本发明实施例的跨域路径保护结构示意图；
图10是根据本发明优选实施例1的域内故障保护结构示意图；
图11是根据本发明优选实施例2的互联节点故障保护结构示意图；
图12是根据本发明优选实施例3的跨域分支路径和共享隧道同时故障的结构示意图；
图13是根据本发明优选实施例4的跨域业务保护流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
在本实施例中提供了一种跨域业务处理方法，图2是根据本发明实施例的跨域业务处理方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，在跨域互联主备节点间建立用于在互联主备节点间相互共享节点信息的共享路径；
步骤S204，依据建立的共享路径在互联主备节点间共享的共享节点信息，以及检测到的故障，对跨域业务进行转发处理。
通过上述步骤，在跨域互联主备节点间建立用于在互联主备节点间相互共享节点信息的共享路径；依据建立的共享路径在互联主备节点间共享的共享节点信息，以及检测到的故障，对跨域业务进行转发处理，解决了相关技术中不存在对于能保持各域上独立切换的跨域保护方案的问题，进而达到了在互联链路或节点出现故障的情况下，保持各域上保护切换独立性和简单性的效果。
为了确保在共享路径发生故障的情况下，互联主备节点间也能够进行信息的共享，可以在在跨域互联主备节点间建立用于在互联主备节点间相互共享节点信息的共享路径之后，为共享路径建立在各个域中对应的保护路径，其中，该保护路径在共享路径发生故障时执行共享路径的功能。
较优地，在为共享路径建立在各个域中对应的保护路径之后，还可以对各个域中对应的保护路径确定在共享路径发生故障时优先执行共享路径的功能的优先级，依据优先级确定用于执行共享路径的功能的保护路径。
在依据建立的共享路径在互联主备节点间共享的共享节点信息，以及检测到的故障，对跨域业务进行转发处理时，依据发生故障的场景的不同，可以采用不同的转发处理：例如，在第一域内跨域路径上的工作路径故障的情况下，互联备节点将从第一域内的保护路径上接收到的跨域业务通过共享路径发送给互联主节点，互联主节点依据跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对跨域业务进行转发处理；再例如，在第一域内跨域路径上的工作路径以及共享路径均故障的情况下，互联备节点将从第一域内的保护路径上接收到的跨域业务通过共享路径的保护路径发送给互联主节点，互联主节点依据跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对跨域业务进行转发处理；又例如，在互联主节点故障的情况下，互联备节点依据从互联主节点共享的工作路径与保护路径之间的绑定关系，将第一域内的保护路径与第二域内的保护路径进行拼接，将从第一域内的保护路径上接收到的跨域业务通过第二域内的保护路径对跨域业务进行转发处理。
在本实施例中还提供了一种跨域业务处理装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的跨域业务处理装置的结构框图，如图3所示，该装置包括第一建立模块32和处理模块34，下面对该装置进行说明。
第一建立模块32，设置为在跨域互联主备节点间建立用于在互联主备节点间相互共享节点信息的共享路径；处理模块34，连接至上述第一建立模块32，设置为依据建立的共享路径在互联主备节点间共享的共享节点信息，以及检测到的故障，对跨域业务进行转发处理。
图4是根据本发明实施例的跨域业务处理装置的优选结构框图一，如图4所示，该装置除包括图3所示的所有模块外，还包括第二建立模块42，下面对该第二建立模块42进行说明。
第二建立模块42，连接至上述第一建立模块32，设置为为共享路径建立在各个域中对应的保护路径，其中，保护路径在共享路径发生故障时执行共享路径的功能。
图5是根据本发明实施例的跨域业务处理装置的优选结构框图二，如图5所示，该装置除包括图4所示的所有模块外，还包括确定模块52，下面对该确定模块52进行说明。
确定模块52，连接至上述第二建立模块42，设置为对各个域中对应的保护路径确定在共享路径发生故障时优先执行共享路径的功能的优先级，依据优先级确定用于执行共享路径的功能的保护路径。
图6是根据本发明实施例的跨域业务处理装置中处理模块34的优选结构框图，如图6所示，该处理模块34包括以下之一：第一处理单元62、第二处理单元64、第三处理单元66，下面对该处理模块34进行说明。
第一处理单元62，设置为在第一域内跨域路径上的工作路径故障的情况下，互联备节点将从第一域内的保护路径上接收到的跨域业务通过共享路径发送给互联主节点，互联主节点依据跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对跨域业务进行转发处理；第二处理单元64，设置为在第一域内跨域路径上的工作路径以及共享路径均故障的情况下，互联备节点将从第一域内的保护路径上接收到的跨域业务通过共享路径的保护路径发送给互联主节点，互联主节点依据跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对跨域业务进行转发处理；第三处理单元66，设置为在互联主节点故障的情况下，互联备节点依据从互联主节点共享的工作路径与保护路径之间的绑定关系，将第一域内的保护路径与第二域内的保护路径进行拼接，将从第一域内的保护路径上接收到的跨域业务通过第二域内的保护路径对跨域业务进行转发处理。
图7是根据本发明实施例的跨域业务处理系统的结构框图，如图7所示，该系统70包括：一个或多个第一域72，一个或多个第二域74，一个或多个第一域与一个或多个第二域通过互联主节点76和互联备节点78互联，其中，互联主节点76，互联备节点78，依据在互联主备节点间建立的共享路径，相互共享对方节点的共享节点信息；互联备节点78，还设置为在第一域内的工作路径发生故障和/或主节点发生故障的情况下，将从第一域内的保护路径接收到的跨域业务通过共享路径转发给互联主节点。
优选地，互联主节点76，互联备节点78，还设置为在共享路径发生故障的情况下，通过共享路径的保护路径共享共享节点信息，以及对跨域业务的转发处理。
针对相关技术中当互联链路或节点出现故障，通过现有单域内保护方法所不能解决跨域业务的保护问题。在本实施例中，利用互联主备节点之间信息相互共享，来实现每个域上独立保护，可以避免了一个域内的故障，引发其他相邻域上路径倒换而带来操作方面复杂性。
图8是根据本发明优选实施例的该跨域业务处理系统的结构框图，如图8所示，该系统主要包括如下结构：路径配置模块82(同上述第一建立模块32和/或第二建立模块42)、信息共享模块84、业务转发模块86(两者功能结合同上述处理模块34)、保护切换模块88(同上述处理模块34的部分功能)，下面对该系统进行说明。
路径配置模块82：该模块主要用来配置互联主备节点之间共享链路或隧道，且分别在各域上为该共享链路或隧道配置一个对应的保护链路或隧道；
信息共享模块84：该模块存在于两域互联的主备节点上，通过该模块，使得主备节点之间将链路检测状态或所分配标签、绑定关系等信息，打上相应配置状态信息标识，通过共享隧道发送对端节点，确保主备节点都知道工作路径标识和保护路径标识之间的绑定关系、工作和保护路径状态信息；
业务转发模块86：在检测到域内工作路径出现故障情况下，备份互联节点将保护路径接收到业务，通过共享隧道转发给主节点；
保护切换模块88：当共享链路或共享隧道上检测到故障时，根据所配置保护链路或隧道的优先级，触发相应业务通过其对应的保护路径或隧道发送到对应节点；
图9是根据本发明实施例的跨域路径保护结构示意图，如图9所示，对于跨域网络来说，实现跨域路径或业务的保护，主要包括以下处理：
1为跨域路径在每个域上分支路径配置一个对应域内保护路径进行业务保护；而对于互联主备节点之间共享隧道或链路，在共享该链路的两个域上分别配置一个保护隧道或链路，并对这两个域上保护链路或隧道设定保护优先级；
2将连接两个域的互联主备节点虚拟成一个节点，将每个节点上标识和状态信息，打上相应配置状态标识，通过内部相互之间共享链路或隧道，发送给对端节点上，实现两个互联节点上信息共享，包括一个跨域路径上在一个域上工作分支路径和对应保护路径的保护关系以及两个域上工作分支路径的拼接关系；
3当一个域内跨域路径上分支路径检测到故障，则根据传统的1:1保护方法，将其被保护的业务切换到对应的域内保护路径。当保护路径上互联备节点接收从保护路径发送过来的业务报文后，打上业务信息标识后，再将该业务报文压入到该共享隧道中，转发给互联主节点；
4互联主节点接收到共享隧道转发过来业务报文，根据其上面的业务信息标识，识别该报文是业务信息报文，再根据业务报文所封装的保护路径的标识，如：标签；将该业务报文又重新压入原工作路径中进行传送；
5当互联主备节点检测到其之间的共享隧道存在故障时，根据两个相邻域上的所配置的保护隧道的状态情况和优先级关系，选择其中一个优先级高的保护隧道将从两个互联节点之间信息数据进行发送；
6当一个域上工作分支路径和共享隧道同时出现故障时，仍然可以先启动域内的1:1线性保护机制，将业务切换到其域内保护路径上，传送到其互联备份节点上，再通过共享隧道所对应的保护隧道，将该被保护的业务报文压入到对应保护隧道上，传送给互联主节点，继续按照原工作路径进行转发；
7当互联主节点故障时，则该互联节点的相邻域上节点都检测工作分支路径存在故障时，则两域都启动保护切换过程；而对于互联备份节点来说，根据主节点所反馈过来两域上工作分支路径的拼接关系，将这两域上保护路径也进行拼接，实现跨域保护；
通过采用上述处理，在互联链路或节点出现故障情况下，保持各域上保护切换独立性和简单性。
下面结合附图对发明优选实施例进行说明。
优选实例1：域内故障的保护
图10是根据本发明优选实施例1的域内故障保护结构示意图，如图10所示，包括如下处理：
1为在域1上跨域分支路径(A-B)配置一个保护路径(A-C)，而对于域2上的跨域分支路径(D-B)配置一个对应保护路径(D-C)，并在主备互联节点B和C之间建立一个共享隧道或路径，并为该共享隧道或路径分别在域1和域2建立对应的保护隧道，如：域1：C-A-B，域2：C-D-B；
2互联主节点B将其上配置的域1跨域分支路径(A-B)标识，域2上拼接的跨域分支路径(B-D)标识以及这两者跨域分支路径之间绑定关系等信息，在配置好后，在压入共享隧道之前，打上配置信息状态标识，发送给备份节点C；
3同样，互联备节点C将其上配置的域1上跨域分支路径(A-B)对应的保护路径(A-C)标识以及域2上跨域分支路径(D-B)对应的保护路径(D-C)标识发送给主互联节点B；
4通过互联主备节点B和C之间的信息共享，从而在B和C节点都学习到跨域分支路径与其对应的保护路径的标识以及对应关系；
5当域1上跨域分支路径(A-B)上检测到故障时，则由A节点触发保护切换，将被保护的跨域业务切换到保护路径(A-C)，传送到备分互联节点C上；
6当备份互联节点C接收从保护路径(A-C)发送过来的业务报文后，直接将该业务报文打上相应的业务信息标识，封装到互联节点B和C的共享隧道中，发送给主互联节点B；
7当B接收到从共享隧道发送过来业务报文，根据其上所封装的业务信息标识，判断出这是业务报文，再根据封装保护路径的标识，确定对应的跨域分支路径，再通过相邻域2上跨域分支路径(B-D)传送给域2上出节点D；
优选实施例2：互联节点故障
图11是根据本发明优选实施例2的互联节点故障保护结构示意图，如图11所示，包括如下处理：
1步骤1，2，3，4等同于优选实施例1；当互联主节点B发生故障时，其域1和域2上两端节点A和D都检测跨域分支路径(A-B)和(D-B)都存在故障，直接切换其对应的保护路径(A-C)和(D-C)上发送；
2当互联备份节点C接收到从A或D保护路径发送过来的故障信息，同时C又检测到其到互联主节点B之间的共享工作和保护隧道都存在故障时，则根据本节点所保存的跨域分支路径与其对应保护路径关系，以及两域跨域分支路径(A-B)和(B-D)之间拼接关系，将两域上保护路径(A-C)和(C-D)进行拼接；
3当C节点从其保护路径(A-C)或(D-C)接收到跨域业务时，直接通过另一个域上所拼接的保护路径发送出去；
优选实施例3：跨域分支路径和共享隧道同时故障
图12是根据本发明优选实施例3的跨域分支路径和共享隧道同时故障的结构示意图，如图12所示，包括如下处理：
1步骤1，2，3，4等同于优选实施例1；当跨域分支路径(A-B)和共享隧道(B-C)都存在故障时；首先当A检测到域1上跨域分支路径(A-B)存在故障时，则该跨域分支路径上业务切换到其对应的保护路径(A-C)发送，并向对端C节点发送保护倒换请求信息；
2当C节点接收到A节点发送过来的保护倒换请求信息，则确定从保护路径接收业务；同时，也检测到其与B节点之间共享隧道也存在故障时，其将C节点发送给B的信息，也切换到其对应的保护隧道(C-D-B)，发送给B节点；另外，向B节点发生保护切换请求信息；
3当B节点接收到C节点发送过来保护切换请求后，切换到保护隧道(C-D-B)上来接收C节点发送过来业务报文；且B节点接收到C节点发送过来业务报文后，根据业务信息标识，判断这是业务报文，再根据业务报文上保护路径的标识，判断出B节点对应的跨域分支路径的标识，又重新切换到域2上跨域分支路径(B-D)传送。
优选实施例4
图13是根据本发明优选实施例4的跨域业务保护流程图，如图13所示，该流程包括如下步骤：
步骤S1302，在每个域内为跨域路径上分支路径配置保护路径；
步骤S1304，为共享路径在各域上配置一条对应的保护路径；
步骤S1306，互联主备节点通过共享路径进行信息共享；
步骤S1308，判断是否检测到故障，判断结果为否的情况下，进入步骤S1310，否则进入步骤S1312；
步骤S1310，继续进行故障检测；
步骤S1312，判断是否存在单域路径故障，在判断结果为是情况下，进入步骤S1314，否则进入步骤S1316；
步骤S1314，启动域内1：1保护；
步骤S1316，判断是否存在互联节点故障，在判断结果为是的情况下，进入步骤S1318，否则进入步骤S1320；
步骤S1318，两域都启动1：1保护；
步骤S1320，跨域分支路径和共享路径同时故障，启动单域内1：1保护和共享路径保护。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，通过上述实施例及优选实施方式，解决了相关技术中不存在对于能保持各域上独立切换的跨域保护方案的问题，进而达到了在互联链路或节点出现故障的情况下，保持各域上保护切换独立性和简单性的效果。

Claims (10)

  1. 一种跨域业务处理方法，包括：
    在跨域互联主备节点间建立用于在所述互联主备节点间相互共享节点信息的共享路径；
    依据建立的所述共享路径在所述互联主备节点间共享的共享节点信息，以及检测到的故障，对所述跨域业务进行转发处理。
  2. 根据权利要求1所述的方法，其中，在在所述跨域互联主备节点间建立用于在所述互联主备节点间相互共享节点信息的所述共享路径之后，还包括：
    为所述共享路径建立在各个域中对应的保护路径，其中，所述保护路径在所述共享路径发生故障时执行所述共享路径的功能。
  3. 根据权利要求2所述的方法，其中，在为所述共享路径建立在各个域中对应的所述保护路径之后，还包括：
    对各个域中对应的保护路径确定在所述共享路径发生故障时优先执行所述共享路径的功能的优先级，依据所述优先级确定用于执行所述共享路径的功能的保护路径。
  4. 根据权利要求1所述的方法，其中，依据建立的所述共享路径在所述互联主备节点间共享的共享节点信息，以及检测到的故障，对所述跨域业务进行转发处理包括以下之一：
    在第一域内跨域路径上的工作路径故障的情况下，互联备节点将从所述第一域内的保护路径上接收到的所述跨域业务通过所述共享路径发送给互联主节点，所述互联主节点依据所述跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对所述跨域业务进行转发处理；
    在第一域内跨域路径上的工作路径以及所述共享路径均故障的情况下，互联备节点将从所述第一域内的保护路径上接收到的所述跨域业务通过所述共享路径的保护路径发送给互联主节点，所述互联主节点依据所述跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对所述跨域业务进行转发处理；
    在互联主节点故障的情况下，所述互联备节点依据从互联主节点共享的工作路径与保护路径之间的绑定关系，将所述第一域内的保护路径与所述第二域内的保护路径进行拼接，将从所述第一域内的保护路径上接收到的所述跨域业务通过所述第二域内的保护路径对所述跨域业务进行转发处理。
  5. 一种跨域业务处理装置，包括：
    第一建立模块，设置为在跨域互联主备节点间建立用于在所述互联主备节点间相互共享节点信息的共享路径；
    处理模块，设置为依据建立的所述共享路径在所述互联主备节点间共享的共享节点信息，以及检测到的故障，对所述跨域业务进行转发处理。
  6. 根据权利要求5所述的装置，其中，还包括：
    第二建立模块，设置为为所述共享路径建立在各个域中对应的保护路径，其中，所述保护路径在所述共享路径发生故障时执行所述共享路径的功能。
  7. 根据权利要求6所述的装置，其中，还包括：
    确定模块，设置为对各个域中对应的保护路径确定在所述共享路径发生故障时优先执行所述共享路径的功能的优先级，依据所述优先级确定用于执行所述共享路径的功能的保护路径。
  8. 根据权利要求5所述的装置，其中，所述处理模块包括以下之一：
    第一处理单元，设置为在第一域内跨域路径上的工作路径故障的情况下，互联备节点将从所述第一域内的保护路径上接收到的所述跨域业务通过所述共享路径发送给互联主节点，所述互联主节点依据所述跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对所述跨域业务进行转发处理；
    第二处理单元，设置为在第一域内跨域路径上的工作路径以及所述共享路径均故障的情况下，互联备节点将从所述第一域内的保护路径上接收到的所述跨域业务通过所述共享路径的保护路径发送给互联主节点，所述互联主节点依据所述跨域业务中所封装的保护路径标识，以及工作路径与保护路径之间的绑定关系，通过第二域内的工作路径对所述跨域业务进行转发处理；
    第三处理单元，设置为在互联主节点故障的情况下，所述互联备节点依据从互联主节点共享的工作路径与保护路径之间的绑定关系，将所述第一域内的保护路径与所述第二域内的保护路径进行拼接，将从所述第一域内的保护路径 上接收到的所述跨域业务通过所述第二域内的保护路径对所述跨域业务进行转发处理。
  9. 一种跨域业务处理系统，包括：一个或多个第一域，一个或多个第二域，所述一个或多个第一域与所述一个或多个第二域通过互联主备节点互联，其中，
    所述互联主备节点，依据在所述互联主备节点间建立的共享路径，相互共享对方节点的共享节点信息；
    所述互联备节点，还设置为在所述第一域内的工作路径发生故障和/或主节点发生故障的情况下，将从所述第一域内的保护路径接收到的所述跨域业务通过所述共享路径转发给所述互联主节点。
  10. 根据权利要求9所述的系统，其中，所述互联主备节点，还设置为在所述共享路径发生故障的情况下，通过所述共享路径的保护路径共享所述共享节点信息，以及对所述跨域业务的转发处理。
PCT/CN2014/089088 2014-08-13 2014-10-21 跨域业务处理方法、装置及系统 WO2015154423A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410397808.8A CN105337856B (zh) 2014-08-13 2014-08-13 跨域业务处理方法、装置及系统
CN201410397808.8 2014-08-13

Publications (1)

Publication Number Publication Date
WO2015154423A1 true WO2015154423A1 (zh) 2015-10-15

Family

ID=54287190

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/089088 WO2015154423A1 (zh) 2014-08-13 2014-10-21 跨域业务处理方法、装置及系统

Country Status (2)

Country Link
CN (1) CN105337856B (zh)
WO (1) WO2015154423A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109788018A (zh) * 2017-11-15 2019-05-21 中国移动通信有限公司研究院 跨域的业务互通方法、网络设备及存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107465527B (zh) * 2016-06-02 2020-04-28 中兴通讯股份有限公司 一种网元、保护倒换方法及其系统
CN107592251A (zh) * 2016-07-08 2018-01-16 中兴通讯股份有限公司 共享环跨环组网结构及跨环业务流转发的方法
CN108762946B (zh) * 2018-05-16 2020-09-11 福建天泉教育科技有限公司 一种跨域web端通信方法及终端
CN112737947B (zh) * 2020-12-29 2022-08-30 优刻得科技股份有限公司 基于mpls的虚拟网络跨域传输方法、系统、设备和介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1976313A (zh) * 2006-09-19 2007-06-06 中国人民解放军国防科学技术大学 高性能路由器bgp路由协议分布并行实现方法
CN101036126A (zh) * 2004-12-14 2007-09-12 思科技术公司 在计算机网络中边界路由器节点发生故障的情况下快速恢复的高效机制
CN101164265A (zh) * 2005-03-18 2008-04-16 思科技术公司 用于备份pe选择的算法
CN101170578A (zh) * 2007-11-30 2008-04-30 北京理工大学 基于语义相似度的层次式对等网络结构及构建方法
US7627290B2 (en) * 2005-07-07 2009-12-01 Cisco Technology, Inc. Route convergence monitoring system and method
CN102571401A (zh) * 2010-12-24 2012-07-11 华为技术有限公司 建立备份路径的方法及设备、选取备份路径的方法及设备
US8422362B2 (en) * 2008-08-05 2013-04-16 At&T Intellectual Property I, Lp Reliability as an interdomain service

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102740175B (zh) * 2012-06-12 2014-09-24 武汉邮电科学研究院 一种跨域端到端标签交换路径的保护恢复方法

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101036126A (zh) * 2004-12-14 2007-09-12 思科技术公司 在计算机网络中边界路由器节点发生故障的情况下快速恢复的高效机制
CN101164265A (zh) * 2005-03-18 2008-04-16 思科技术公司 用于备份pe选择的算法
US7627290B2 (en) * 2005-07-07 2009-12-01 Cisco Technology, Inc. Route convergence monitoring system and method
CN1976313A (zh) * 2006-09-19 2007-06-06 中国人民解放军国防科学技术大学 高性能路由器bgp路由协议分布并行实现方法
CN101170578A (zh) * 2007-11-30 2008-04-30 北京理工大学 基于语义相似度的层次式对等网络结构及构建方法
US8422362B2 (en) * 2008-08-05 2013-04-16 At&T Intellectual Property I, Lp Reliability as an interdomain service
CN102571401A (zh) * 2010-12-24 2012-07-11 华为技术有限公司 建立备份路径的方法及设备、选取备份路径的方法及设备

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109788018A (zh) * 2017-11-15 2019-05-21 中国移动通信有限公司研究院 跨域的业务互通方法、网络设备及存储介质
CN109788018B (zh) * 2017-11-15 2021-08-06 中国移动通信有限公司研究院 跨域的业务互通方法、网络设备及存储介质

Also Published As

Publication number Publication date
CN105337856A (zh) 2016-02-17
CN105337856B (zh) 2019-09-24

Similar Documents

Publication Publication Date Title
JP6166960B2 (ja) フレーム伝送装置および正常性確認方法
WO2015154423A1 (zh) 跨域业务处理方法、装置及系统
JP6278818B2 (ja) 中継システムおよびスイッチ装置
JP2005260321A (ja) ラベルパスネットワークの迂回制御方式
CN105591768B (zh) 故障检测方法及装置
CN109672619A (zh) 一种处理报文的方法、设备及系统
JP5521663B2 (ja) 通信装置、通信システムおよび通信方法
WO2016037443A1 (zh) 一种临时通道的建立方法、设备、系统和计算机存储介质
CN105871674A (zh) 环保护链路故障保护方法、设备及系统
CN105656776B (zh) 一种伪线双归保护切换系统、方法和装置
CN105207871B (zh) 双切环网保护方法及装置
WO2016091094A1 (zh) 一种光传送网的保护倒换方法及装置
JP4895972B2 (ja) リングプロトコル高速切替方法およびその装置
CN108023800A (zh) 一种lte承载网络的保护方法及装置
JP2013046090A (ja) 通信装置および通信システム
US20160036622A1 (en) Protection switching method, network, and system
JP2016086316A (ja) 伝送装置および冗長提供方法
US9806937B2 (en) Protection method and system for multi-domain network, and node
WO2018077124A1 (zh) 一种业务告警处理方法、装置及系统
EP2528263B1 (en) Method for implementing protection group overlay, and method and system for ethernet protection switching
CN105763441B (zh) 一种报文传输方法和装置
JP5622687B2 (ja) 相互接続ノード、通信システムおよび通信方法
US20160028588A1 (en) Method for identifying logical loops in ethernet networks
EP2750336A1 (en) Inter-loop service protection method and apparatus
JP6356047B2 (ja) 中継システムおよびスイッチ装置

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: 14888999

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: 14888999

Country of ref document: EP

Kind code of ref document: A1