WO2007128176A1 - A service switching method and the network node thereof - Google Patents

A service switching method and the network node thereof Download PDF

Info

Publication number
WO2007128176A1
WO2007128176A1 PCT/CN2006/003474 CN2006003474W WO2007128176A1 WO 2007128176 A1 WO2007128176 A1 WO 2007128176A1 CN 2006003474 W CN2006003474 W CN 2006003474W WO 2007128176 A1 WO2007128176 A1 WO 2007128176A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
node
service
working path
network
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2006/003474
Other languages
English (en)
French (fr)
Inventor
Huiying Xu
Fatai Zhang
Yongliang Xu
Xianlong Luo
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CNA2006800114985A priority Critical patent/CN101176303A/zh
Priority to EP06828385A priority patent/EP1942604B1/en
Publication of WO2007128176A1 publication Critical patent/WO2007128176A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06Management of faults, events, alarms or notifications
    • H04L41/0654Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12Discovery or management of network topologies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • H04L45/03Topology update or discovery by updating link state protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/22Alternate routing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/28Routing or path finding of packets in data switching networks using route fault recovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/55Prevention, detection or correction of errors
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • H04Q2011/0079Operation or maintenance aspects
    • H04Q2011/0081Fault tolerance; Redundancy; Recovery; Reconfigurability
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q11/00Selecting arrangements for multiplex systems
    • H04Q11/0001Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062Network aspects
    • H04Q2011/0084Quality of service aspects

Definitions

  • the present invention relates to the field of Automatically Switched Optical Network (ASON), and in particular to a method and network node for service switching.
  • ASON Automatically Switched Optical Network
  • optical networks are required to adjust the logical topology of the network in real time and dynamically, and to achieve optimal use of resources, which can be quickly and accurately Users provide a variety of bandwidth services and applications, and have more comprehensive protection and recovery capabilities, greater interoperability and scalability.
  • the service scheduling of the traditional optical network adopts the static configuration of the network management system. It does not support the dynamic provisioning mode, and most of them adopt linear or circular networking.
  • the protection recovery uses multiplex section protection and sub-network connection protection (SNCP).
  • SNCP sub-network connection protection
  • the static recovery methods such as the Passage Protect (PP) ring can no longer meet the needs of the above services.
  • ASON Automatically switched optical network
  • the control plane uses the Generalized Multi-Protocol Label Switching (GMPLS) protocol to establish services mainly through two types of connections: Switched connections (SC) and Soft permanent connections (SPC).
  • GMPLS Generalized Multi-Protocol Label Switching
  • SC Switched connections
  • SPC Soft permanent connections
  • GMPLS Generalized Multi-Protocol Label Switching
  • end-to-end connections or partial connections can be automatically established, maintained and removed in a short time.
  • the control plane will quickly re-route through the GMPLS signaling protocol, establish a protection path, and transmit services through the established protection path, so that the service can be restored to normal.
  • the service can be returned from the protection path of the rerouting to the original working path, which facilitates the management of the network by the operator, and can maintain the temporary dynamic change of the network connection route and the stability of the network for a long time. Therefore, the service switching feature has become an important feature in the ASON network and has attracted attention.
  • node A to node H are nodes in the ASON network, and node A and node H can return a protection type connection transmission service through +1, wherein the intermediate node of the working path 101 is node C and Node E, the intermediate nodes of the protection path 102 are node D and node G.
  • the node H When a fault occurs between the node C and the node E, that is, when the working path 101 fails, the node H will select the service of the protection path 102; at the same time, the control plane will calculate its recovery path and establish recovery by signaling according to the calculated result.
  • the path 103, the intermediate node is the node B and the node F, so that the service is restored to the 1+1 protection function.
  • the C node After the fault between the node C and the node E is removed, the C node issues an alarm disappearance notification, and the first node failure of all the connections that have passed the link has disappeared, that is, the first node A of the connection working path 101 is notified in FIG.
  • the service is switched from the protection path 102 back to the original working path 101, and the recovery path 103 is deleted.
  • the purpose of setting WTR is to prevent work
  • the path is unstable, the service frequently switches between the working path 101 and the restoration path 103.
  • this method cannot solve the problem that the link is protected. For example, when the link through which the service passes is multiplex section protection, it is impossible to determine whether the service switching can be performed only by the alarm disappearing notification when the link fault disappears. Summary of the invention
  • the present invention provides an embodiment of a method for service switching, which can implement service switching that does not depend on an alarm message.
  • the working path is faulty, and the service is switched to the network of the protection path, and the following steps are included:
  • the end node of the service After detecting that the network topology changes, the end node of the service checks whether the faulty working path returns to normal. If the faulty working path returns to normal, the service is switched back from the protection path to the working path. Otherwise, the process ends.
  • the end node of the service is the first node or the last node of the working path.
  • the method further includes: establishing an protection path by using an end node of the working path as an end node of the protection path;
  • the method further includes: deleting a connection in the protection path that is not related to the working path.
  • the method further includes: establishing an restoration path by using an end node of the working path as an end node of the recovery path.
  • the method further includes: deleting a connection in the recovery path that is independent of the working path.
  • the method further includes: setting a waiting recovery timer in the end node, determining that the waiting for the recovery timer expires before working Whether the path is faulty, if yes, exit this process; otherwise, perform the subsequent steps.
  • the method is applied to an automatic switched optical network ASON.
  • the end node of the protection path detects the change of the network topology in the following manner: After receiving the flooding information of the open shortest path first-traffic engineering OSPF-TE protocol, the end node updates its own routing information database RDB, when its own RDB content When changes occur, the network topology changes.
  • the invention also provides an embodiment of a network node, including a routing controller, a link resource manager and a connection controller, the network node further comprising a path checking unit, configured to report that the network topology occurs when the link resource manager reports When the change is made, it is determined whether the working path with the network node device as the end node is restored to the normal state by the fault state before the network topology change, and if yes, the path return signal is sent to the routing controller;
  • the routing controller triggers the connection controller to implement a process of switching the service from the protection path back to the working path according to the received path return signal.
  • the network node further includes a waiting for a recovery timer
  • the path checking unit is further configured to: start the waiting for recovery timer, and determine whether the working path is faulty before waiting for the recovery timer to expire before sending the path return signal to the routing controller, if not, Then stop the wait recovery timer or issue a path return signal to the routing controller.
  • the path detection unit and/or the wait recovery timer is a submodule of the routing controller.
  • the network node is a network node of the AS0N.
  • the embodiment of the present invention is based on the change of the network topology, but does not depend on the alarm disappearance notification to trigger the service switching, which can reduce the spread of the alarm message; and can solve the protection path and the original working path.
  • the process can be returned when the resource is shared.
  • Figure 1 is a schematic diagram of a network in which the recovery path of the 1 + 1 protection type is independent of the working path link;
  • FIG. 2 is a schematic block diagram of a network node structure in the prior art
  • Figure 4 is a network diagram of a 1 + 1 protection type of recovery path sharing a part of the link with the working path;
  • FIG. 5 is a flowchart of service switching according to Embodiment 2 of the present invention.
  • FIG. 6 is a schematic diagram of a network of an unprotected working path according to Embodiment 3 of the present invention.
  • FIG. 7 is a schematic block diagram showing the structure of an ASON network node according to an embodiment of the present invention. Mode for carrying out the invention
  • the solution of the embodiment of the present invention fully utilizes the characteristics of the routing technology in the ASON. Therefore, before the technical solution of the embodiment of the present invention is elaborated, the routing technology in the ASON is introduced.
  • FIG. 1 The schematic diagram of the node routing structure in ASON is shown in Figure 2, including:
  • the Routing Controller (RC) 210 is responsible for responding to the request of the connection controller for establishing a connection or channel information, including exchanging routing information with the peer RC, and querying the routing information database (Routing Data Base, RDB) After 202, the query is replied to the route query, and is also responsible for returning the topology information required by the management network, and the topology information includes a Sub Network Point (SNP) and an attribute of the SNP;
  • SNP Sub Network Point
  • a routing information database configured to provide routing information to the routing controller 210, where the routing information includes a local topology, a network topology, a reachability, a routing policy configuration, and other information obtained through routing information exchange.
  • Information includes a local topology, a network topology, a reachability, a routing policy configuration, and other information obtained through routing information exchange.
  • the routing information database 220 may contain routing information of multiple routing domains;
  • a Link Resource Manager (LRM) 230 is configured to provide all the subnet point pool (SNP Pool, SNPP) link information to the routing controller 210, and inform the routing of any state change of the link resources it controls. Controller 210;
  • a Protocol Controller (PC) 240 which is used to translate routing primitives into messages of a particular routing protocol, and is therefore protocol dependent.
  • the protocol controller 240 also processes control information associated with the routing protocol for management and maintenance of routing information exchange;
  • the connection controller 250 is configured to establish a corresponding connection according to the indication of the routing controller 210.
  • the routing information distribution protocol in ASON adopts the Open Shortest Path First-Traffic Extension (OSPF-TE) protocol based on GMPLS.
  • OSPF-TE Open Shortest Path First-Traffic Extension
  • each network node can quickly detect topology changes in the network, for example, the routing interface fails.
  • LSA Link Status Announcement
  • LSA Link Status Announcement
  • the routing information database RDB of the node that is, all nodes will eventually have the same topology information and link information. In this way, each node of the network can sense changes in the network topology.
  • the embodiment of the present invention includes the following steps: When the working path M1 for the transmission service fails, the control plane performs dynamic recovery, establishes the path M2, and transmits the service through the path M2;
  • the end node of the service finds that the network topology changes, the end node checks whether the link on the original working path M1 is normal according to the routing information in the local RDB. If the link is normal, the WTR is set, and after the WTR expires, the WTR will be set. Through the switching action, the service transmitted by M2 is switched back to M1, and the connection of path M2 is deleted.
  • the end node of the service is the first node or the last node of the path M1, and is also the first node or the last node of the path M2.
  • M2 and Ml part of the resource sharing that is, reuse part of the normal connection of the original Ml.
  • Embodiment 1 A method for switching a service path when the link between the recovery path and the original working path is separated from the first and last nodes.
  • the process of implementing the 1+1 protection service switching in this embodiment is as shown in FIG. 3, and includes the following steps:
  • Step 301 A link fault occurs between the node C and the node E, that is, the working path 101 is faulty, the last node H selects a service from the protection path 102, and the control plane reroutes the recovery path 103 that is completely separated from the working path 101. ;
  • Step 302 The link fault between the node C and the node E disappears, that is, the working path 101 returns to normal.
  • the routing controller of each node updates its own routing information database RDB to sense the network topology. The change;
  • Step 303 The first and last nodes of the working path 101, that is, the routing controllers of the node A and the node H sense the network topology change, check whether the working path 101 is normal according to the local RDB, and the connection configuration parameter is returnable. Then step 304 is performed, otherwise the process is exited;
  • Step 304 Node A sets a timer with a duration of WTR, and determines whether the working path 101 fails again before the timer expires. If yes, the process is exited, otherwise step 305 is performed;
  • Step 305 After the timer expires, the routing controller of the node A triggers the connection controller to switch the service from the recovery path 103 back to the working path 101.
  • Step 306 Node A sends a delete message (such as Path Tear) along the recovery path 103, and removes the forward and reverse cross-connection of the recovery path 103.
  • the deletion process can adopt the standard GMPLS RSVP-TE connection removal process (refer to the relevant content of RFC 3473). ), after the deletion is completed This process.
  • Embodiment 2 A method for switching services when the recovery path is shared with some resources of the original working path.
  • the working path 401 of the 1+1 protection service starts from the first node A, and sequentially passes through the node N1, the node D, and the node N2 to the last node G;
  • the intermediate nodes of the protection path are the node C and the node F;
  • 403 starts from the first node A and sequentially passes through the node N1, the node ⁇ node E, and the node N2 to the last node G.
  • the restoration path 403 shares the connection resources of the node A to the node N1 and the node N2 to the node G in the working path 401.
  • Step 501 When a link fault occurs between the node D and the node N2, that is, the working path 401 fails, and the last node G is protected.
  • the path 402 selects a service, and the control plane reroutes the recovery path 403 shared with the resource of the working path 401;
  • Step 502 The link fault between the node D and the node N2 disappears, that is, the working path 401 returns to normal.
  • the routing controller of each node updates its own routing information database RDB to sense the network topology. Change
  • Step 503 The first and last nodes of the working path 401, that is, the routing controllers of the node A and the node G sense that the network topology changes, the local RDB checks whether the working path 401 is restored, and the connection configuration parameter is returnable. Then step 504 is performed, otherwise the process is exited;
  • Step 504 Node A sets a timer with a duration of WTR, and before the timer expires, determines whether the working path 401 fails again, and if so, exits the flow, otherwise step 505 is performed;
  • Step 505 After the timer expires, the routing controller of the node A triggers the connection controller to switch the service from the recovery path 403 back to the working path 401;
  • Step 506 Node A sends a delete message along the recovery path 403, but only deletes the connection unrelated to the work path 401, that is, deletes the node N1 to the node B, the node B to the node E,
  • the connection from node E to node N2 retains the partial connection of shared working path 401, that is, the connection from node A to node N1 and node N2 to node G.
  • the deletion process can adopt the standard GMPLS RSVP-TE connection removal process (see RFC 3473). Related content), the process is completed after the deletion is completed.
  • Each of the operations performed by the node A, which is the head node of the working path, in the above steps 504 to 506 can also be exempted from the node G, which is the last node of the working path.
  • Embodiment 3 A service switching method when the working path does not have a protection attribute.
  • the above two embodiments are all cases in which the working path of the 1 + 1 protection is used for service switching.
  • the inventive solution can also be applied to an unprotected working path.
  • the first node A and the last node H transmit data through the working path 601, and a fault occurs between the intermediate node C and the node E during the transmission; then the protection path 602 is established, and the service is transmitted through the protection path 602. If the first node A or the last node H learns that the working path 601 is normal through the sensing network topology change, the timer of the WTR is started; when the timer expires, the service is switched back to the working path 601, and The protection path 602 is deleted.
  • the protection path 602 and the working path 601 shown in FIG. 6 are independent of the first and last nodes. In actual applications, the protection path 602 may also share a partial connection with the working path 601. In this case, the deletion protection path is deleted. 602 is a connection that deletes the protection path 602 from the work path 603.
  • FIG. 7 A schematic block diagram of a network node device for implementing the method of the embodiment of the present invention is shown in FIG.
  • the network node device of the embodiment of the present invention adds a path checking unit 711 and a WTR timer 712 to the routing controller 710.
  • the path checking unit 711 is configured to determine, when the link resource manager 730 reports that the network topology changes, use the network node device as the first node, and configure whether the returnable working path is changed by the network topology.
  • the previous fault state returns to the normal state, and according to the judgment result, the WTR timer 712 of the WTR duration is started; Before the WTR timer 712 times out, the path detecting unit 711 further determines whether the working path is abnormal, and if so, stops the WTR timer 712;
  • the path detection unit 711 or the WTR timer '712 sends a path return signal to the routing controller 710, and the routing controller 710 receives the signal to trigger the switching of the service from the protection path back to the working path. Process.
  • the path checking unit 711 and the WTR timer 712 can also function as modules independent of the routing control 719 in the network node device.
  • the routing controller 710 also adds an interface to the connection controller 750 for triggering the connection controller 750 to switch traffic from the protection path back to the working path and delete the protection path or recovery path independent of the working path.
  • the other modules of the ASON network node are the same as the prior art, and therefore will not be described again.
  • the solution of the embodiment of the present invention triggers the service switching process based on the change of the network topology, so that the diffusion of the alarm information can be reduced; and the returnable process when the protection path is shared with the original working path, and one or all implementations of the present invention can be solved.
  • the example scheme can be applied to a returnable implementation of various protection type connections.

Landscapes

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

Description

一种业^到换的方法和网络节点
技术领域
本发明涉及自动交换光网给( Automatically switched optical network, ASON )领域, 特别涉及一种业务倒换的方法和网络节点。 发明背景
随着信息领域相关技术的发展, 特别是因特网对数据业务增长的强 大推动, 要求光网络能够实时、 动态地调整网络的逻辑拓朴结构, 实现 资源的最佳利用,能够快速、高质量地为用户提供各种带宽服务与应用, 并且具有更加完善的保护和恢复功能, 更强的互操作性和扩展性等。 而 传统光网络的业务调度采用网管静态配置的方式, 不支持动态开通的方 式, 并且大多采用线性或环形组网, 保护恢复采用复用段保护、 子网连 接保护 ( Sub-Network Connection Protection SNCP ), 通道保护 ( Passage Protect, PP )环等静态恢复方法, 已不能满足上述业务的需要。
为满足实际业务的需要, 国际电联标准化部 ( International Telecommunication Unite-T sector, ITU - T )、互联网工作任务组 ( Internet Engineering Task Force , IETF )和光因特网论坛 ( Optical Internetworking Forum, OIF )共同发展了自动交换光网络 ( Automatically switched optical network, ASON )技术, 能够很好地解决上述问题。 ASON引入交换的 智能化来提供动态的端到端连接, 能够支持网状网结构, 并根据需要配 置连接的带宽大小, 大大地增强了网络的生存性, 同时具有灵活的扩展 能力和快速的保护恢复功能。
与传统光传送网相比, ASON最主要的不同就是在光传送平面上引 入控制平面, 将传统光传送网的管理体系演变成基于管理平面、 控制平 面和传送平面的新型多层面管理结构。 控制平面使用通用多协议标签交 换( Generalized Multi-Protocol Label Switching, GMPLS )协议, 主要通 过永久连接 ( Switched connections, SC )和软永久连接 ( Soft permanent connections, SPC ) 两种连接类型建立业务。 通过控制平面功能, 可以 在短时间内自动地建立、 维护和拆除端到端连接或其中的部分连接。 当 业务的工作路径发生故障时 , 控制平面将通过 GMPLS信令协议快速地 进行重路由, 建立保护路径, 并通过所建立的保护路径传输业务, 从而 使业务恢复正常。 当原工作路径故障恢复正常后, 可以把业务从重路由 的保护路径返回到原工作路径, 方便了运营商对网络的管理, 可以保持 网络连接路由的暂时动态变化和较长时间的稳定。 因此业务倒换特性成 为 ASON网络中一个重要的特性而受到关注。
在现有的 ASON 中, 是利用告警消失通告以及等待恢复(Wait to Restore, WTR )时间来判断原工作路径是否恢复正常, 如果是则进行业 务倒换操作。 下面以 1 + 1可返回的保护类型为例对此进行说明。 如图 1 所示, 节点 A至节点 H为 ASON网络中的节点, 并且节点 A与节点 H 之间通过 1 + 1可返回保护类型的连接传送业务, 其中工作路径 101 的 中间节点为节点 C和节点 E,保护路径 102的中间节点为节点 D和节点 G。 当节点 C和节点 E之间发生故障, 即工作路径 101发生故障时, 节 点 H将选收保护路径 102的业务; 同时, 控制平面将计算其恢复路径, 并根据计算的结果通过信令建立恢复路径 103 , 其中间节点为节点 B和 节点 F, 使业务重新恢复 1+1的保护功能。 当节点 C和节点 E之间的故 障排除后, C节点发出告警消失通告, 通知经过此链路的所有连接的首 节点故障已消失, 即图 1中通知连接工作路径 101的首节点 A故障已消 失; A节点等待 WTR时间后, 将业务从保护路径 102倒换回原工作路 径 101 , 并删除恢复路径 103。 其中, 设置 WTR的目的在于防止由于工 作路径不稳定时, 业务在工作路径 101和恢复路径 103之间频繁切换。 然而, 经过深入研究, 发明人发现: 采用这种业务倒换方式, 如果 链路上连接数较多, 则很可能引起大量的告警通告, 导致传递的信息量 较大。 并且, 这种方法不能解决链路存在保护时的处理, 例如业务经过 的链路为复用段保护时, 在链路故障消失时仅仅通过告警消失通告无法 确定是否可以进行业务倒换。 发明内容
有鉴于此, 本发明提出一种业务倒换的方法实施例, 可以实现不依 赖于告警消息的业务倒换。 该实施例用于工作路径发生故障, 业务倒换 到保护路径的网络中,包括如下步骤:
所述业务的端节点检测到网絡拓朴发生变化后, 检查所述发生故障 的工作路径是否恢复正常, 若所述发生故障的工作路径恢复正常, 则将 业务从保护路径倒换回工作路径; 否则结束本流程。
所述业务的端节点为工作路径的首节点或末节点。
所述业务倒换到保护路径之前进一步包括: 以所述工作路径的端节 点作为保护路径的端节点, 建立保护路径;
则所述将业务从保护路径倒换回工作路径之后进一步包括: 删除所 述保护路径中与所述工作路径无关的连接。
所述业务倒换到保护路径之后, 进一步包括: 以所述工作路径的端 节点作为恢复路径的端节点, 建立恢复路径。
所述将业务从保护路径倒换回工作路径之后, 进一步包括: 删除所 述恢复路径中与工作路径无关的连接。
所述将业务从保护路径倒换回工作路径之前, 进一步包括: 在所述 端节点中设置等待恢复定时器, 判断所述等待恢复定时器超时之前工作 路径是否出现故障, 若是则退出本流程; 否则, 执行所述后续步骤。 所述方法应用于自动交换光网络 ASON。
所述保护路径的端节点检测网络拓朴发生变化的方式是: 端节点接 收开放式最短路径优先-流量工程 OSPF-TE协议的洪泛信息后, 更新自 身路由信息数据库 RDB, 当其自身 RDB内容发生变化, 则网络拓朴发 生变化。
本发明还提出一种网络节点的实施例, 包括路由控制器、 链路资源 管理器和连接控制器, 所述网络节点还包括路径检验单元, 用于当链路 资源管理器报告网络拓朴发生变化时, 判断以本网络节点设备作为端节 点的工作路径是否由所述网络拓朴变化之前的故障状态恢复为正常状 态, 若是则向路由控制器发出路径返回信号;
所述路由控制器根据所收到的路径返回信号 , 触发连接控制器实现 业务由保护路径倒换回工作路径的流程。
较佳地, 所述网络节点进一步包括等待恢复定时器;
则所述路径检验单元在向路由控制器发出路径返回信号之前, 进一 步用于: 启动所述等待恢复定时器, 并在等待恢复定时器超时之前, 判 断所述工作路径是否出现故障, 若否, 则停止所述等待恢复定时器或向 路由控制器发出路径返回信号。
所述路径检测单元和 /或等待恢复定时器为路由控制器的子模块。 所述网络节点为 AS0N的网络节点。
从以上技术方案可以看出, 本发明实施例基于网絡拓朴的变化, 而 是不依赖于告警消失通告来触发业务倒换, 可减少告警消息的扩散; 并 且能够解决保护路径与原工作路径存在部分资源共用时的可返回处理。 附图简要说明
图 1 为 1 + 1保护类型的恢复路径与工作路径链路无关的网络示意 图;
图 2为现有技术中的网络节点结构示意框图;
图 3为本发明实施例一的业务倒换的流程图;
图 4为 1 + 1保护类型的恢复路径与工作路径共享部分链路的网络示 意图;
图 5为本发明实施例二的业务倒换的流程图;
图 6为本发明实施例三的无保护工作路径的网络示意图;
图 7为本发明实施例的 ASON网絡节点结构示意框图。 实施本发明的方式
本发明实施例的方案充分利用 ASON中的路由技术的特点, 故对本 发明实施例的技术方案进行详细阐述之前,先对 ASON中的路由技术进 行筒单介绍。
ASON中的节点路由结构示意图如图 2所示, 包括:
路由控制器( Routing Controller, RC ) 210, 负责响应连接控制器为 了建立连接而对通道或路由信息的请求, 包括与对等的 RC交换路由信 息, 并在查询路由信息数据库(Routing Data Base, RDB ) 202以后对路 由查询作出回答, 同时也负责回送管理网络所需要的拓朴信息, 所述拓 朴信息包括子网点 ( Sub Network Point, SNP ) 以及 SNP的属性;
路由信息数据库 (Routing Data Base , RDB) 220, 用于向路由控制器 210提供路由信息, 所述路由信息包括本地拓朴、 网络拓朴、 可达性、 路由策略配置和其他通过路由信息交换获得的信息; 路由信息数据库 220可以包含多个路由域的路由信息; 链路资源管理器( Link Resource Manager, LRM ) 230, 用于向路由 控制器 210提供所有子网点池(SNP Pool, SNPP )链路信息, 并将其控 制的链路资源的任何状态改变告知路由控制器 210;
协议控制器(Protocol Controller, PC ) 240, 用于将路由原语转换成 特定路由协议的消息, 因此是与协议相关的。 协议控制器 240还处理和 路由协议相关的控制信息, 这些控制信息用于路由信息交换的管理和维 护;
连接控制器 250, 用于根据路由控制器 210的指示建立相应的连接。
ASON中的路由信息分发协议采用基于 GMPLS的开放式最短路径 优先-流量工程 ( Open Shortest Path First-Traffic Extension, OSPF-TE )协 议。 通过 OSPF-TE协议, 各网络节点能迅速探测到网络中拓朴的变化, 例如路由接口失败; 通过洪泛机制, 邻接节点之间发送链路状态通告 ( Link Status Announcement, LSA ) 可以同步各网络节点的路由信息数 据库 RDB, 即所有节点最终会拥有相同的拓朴信息和链路信息。 这样, 网络各个节点均能感知网络拓朴的变化。
根据上述 ASON路由技术的特点 , 本发明实施例包括如下步驟: 当用于传输业务的工作路径 Ml发生故障时, 控制平面将进行动态 恢复, 建立路径 M2, 并将业务通过路径 M2传输;
如果业务的端节点发现网络拓朴发生变化, 则端节点将基于本地 RDB中的路由信息检查原工作路径 Ml上的链路是否都恢复正常,如果 恢复正常, 则设置 WTR, 等待 WTR超时后将通过倒换动作, 把 M2所 传输的业务倒换回 Ml , 并删除路径 M2的连接。
其中, 业务的端节点为路径 Ml的首节点或末节点, 同时也是路径 M2的首节点或末节点。
所述建立路径 M2有两种情况: (1)、 M2与 Ml除了首末节点都是链路分离的;
(2)、 M2与 Ml部分资源共享, 即重用了原 Ml的部分正常连接。 下面对这两种情况分别以具体实施例加以阐述。
实施例一: 恢复路径与原工作路径除首末节点外链路分离时业务倒 换的方法。
以图 1所示网络结构为例, 本实施例实现 1+1保护业务倒换的流程 如图 3所示, 包括如下步驟:
步骤 301: 节点 C和节点 E之间发生链路故障, 即工作路径 101发 生故障, 末节点 H从保护路径 102选收业务, 控制平面重路由出与工作 路径 101完全链路分离的恢复路径 103;
步驟 302: 节点 C和节点 E之间的链路故障消失, 即工作路径 101 恢复正常,通过 OSPF-TE的洪泛机制,各个节点的路由控制器更新自身 的路由信息数据库 RDB, 感知网络拓朴的变化;
步骤 303: 工作路径 101的首末节点, 即节点 A和节点 H的路由控 制器感知到网络拓朴变化后, 基于本地的 RDB检查工作路径 101是否 恢复正常且连接的配置参数为可返回, 若是则执行步驟 304, 否则退出 本流程;
步骤 304: 节点 A设置时长为 WTR的定时器, 并在定时器超时之 前, 判断是否工作路径 101再次出现故障, 若是则退出本流程, 否则执 行步骤 305;
步骤 305: 所述定时器超时后, 节点 A的路由控制器触发连接控制 器将业务从恢复路径 103倒换回工作路径 101;
步骤 306: 节点 A沿着恢复路径 103发送删除消息 (如 Path Tear ), 拆除恢复路径 103的正反交叉连接, 其删除过程可采用标准的 GMPLS RSVP-TE连接拆除过程 (参见 RFC 3473的相关内容),删除完毕后结束 本流程。
实施例二:恢复路径与原工作路径部分资源共享时业务倒换的方法。 如图 4所示, 1 + 1保护业务的工作路径 401从首节点 A开始,依次 经过节点 Nl、 节点 D、 节点 N2到末节点 G; 保护路径的中间节点为节 点 C和节点 F; 恢复路径 403从首节点 A开始, 依次经过节点 N1、 节 点^ 节点 E、 节点 N2到末节点 G; 恢复路径 403共享了工作路径 401 中节点 A至节点 N1和节点 N2至节点 G的连接资源。
如图 4所示网络结构, 业务倒换的流程如图 5所示, 包括如下步骤: 步骤 501 : 当节点 D和节点 N2之间发生链路故障, 即工作路径 401 发生故障, 末节点 G从保护路径 402选收业务, 控制平面重路由出与工 作路径 401部分资源共享的恢复路径 403;
步骤 502: 节点 D和节点 N2之间的链路故障消失, 即工作路径 401 恢复正常,通过 OSPF-TE的洪泛机制,各个节点的路由控制器更新自身 的路由信息数据库 RDB, 感知网络拓朴发生变化;
步骤 503: 工作路径 401的首末节点, 即节点 A和节点 G的路由控 制器感知到网络拓朴变化后, 基于本地的 RDB检查工作路径 401是否 恢复正常且连接的配置参数为可返回, 若是则执行步骤 504, 否则退出 本流程;
步骤 504: 节点 A设置时长为 WTR的定时器, 并在定时器超时之 前, 判断是否工作路径 401再次出现故障, 若是则退出本流程, 否则执 行步骤 505;
步骤 505: 所述定时器超时后, 节点 A的路由控制器触发连接控制 器将业务从恢复路径 403倒换回工作路径 401;
步骤 506: 节点 A沿着恢复路径 403发送删除消息, 但只删除与工 作路径 401无关的连接, 即删除节点 N1到节点 B、 节点 B到节点 E、 节点 E到节点 N2的连接, 保留共享工作路径 401的部分连接, 即节点 A到节点 Nl、 节点 N2 到节点 G 的连接, 其删除过程可采用标准的 GMPLS RSVP-TE连接拆除过程 (参见 RFC 3473的相关内容), 删除完 毕后结束本流程。
上述步骤 504至步驟 506中由工作路径的首节点即节点 A实现的各 个操作, 也可以由工作路径的末节点即节点 G免成。
实施例三: 工作路径不具有保护属性时的业务倒换方法。
以上两个实施例都是 1 + 1保护的工作路径进行业务倒换的情况。本 发明方案也可应用于无保护的工作路径。 如图 6所示, 首节点 A和末节 点 H通过工作路径 601传输数据, 在传输过程中, 中间节点 C和节点 E 之间发生故障; 则建立保护路径 602, 再通过保护路径 602传输业务。 若首节点 A或末节点 H通过感知网络拓朴变化又得知工作路径 601恢复 正常, 则启动时长为 WTR的定时器; 当所述定时器超时则将业务再倒 换回工作路径 601, 并删除保护路径 602。
图 6所示的保护路径 602与工作路径 601除首末节点之外是无关的, 实际应用中, 保护路径 602也可能和工作路径 601共享部分连接, 在这 种情况下, 所述删除保护路径 602为删除保护路径 602与工作路径 603 无关的连接。
用于实现本发明实施例方法的网络节点设备示意框图如图 7所示。 与图 2所示现有技术的网络节点比较, 本发明实施例的网络节点设备在 在路由控制器 710中增加了路径检验单元 711和 WTR定时器 712。其中, 路径检验单元 711用于当链路资源管理器 730报告网络拓朴发生变 化时, 判断以本网络节点设备作为首节点, 并且参数配置为可返回的工 作路径是否由所述网络拓朴变化之前的故障状态恢复为正常状态, 并根 据判断结果启动时长为 WTR的 WTR定时器 712; 所述 WTR定时器 712超时前, 路径检测单元 711进一步判断所述 工作路径是否出现异常, 若是则停止 WTR定时器 712;
当 WTR定时器 712超时, 则由路径检测单元 711或 WTR定时器' 712向路由控制器 710发出路径返回信号, 路由控制器 710收到该信号 则触发将业务由保护路径倒换回工作路径的流程。
所述路径检验单元 711和 WTR定时器 712也可作为网络节点设备 中与路由控制 719相互独立的模块。
路由控制器 710还增加一个向连接控制器 750的接口, 用于触发连 接控制器 750将业务从保护路径倒换回工作路径, 并删除保护路径或恢 复路径中与工作路径无关的连接。
本发明实施例 ASON网络节点的其它模块与现有技术相同, 故不再 赘述。
本发明实施例方案基于网络拓朴的变化来触发业务倒换过程, 因此 可减少告警信息的扩散; 并且能够解决保护路径与原工作路径存在部分 资源共用时的可返回处理, 本发明一个或所有实施例方案可适用于各种 保护类型连接的可返回实现。
以上所述仅为本发明的实施例而已, 并不用以限制本发明, 凡在本 发明的精神和原则之内所作的任何修改、 等同替换和改进等, 均应包含 在本发明的保护范围之内。

Claims

权利要求书
1、一种业务倒换的方法, 用于工作路径发生故障, 业务倒换到保护 路径的网络中,其特征在于, 该方法包括如下步骤:
所述业务的端节点检测到网络拓朴发生变化后, 检查所述发生故障 的工作路径是否恢复正常, 若所述发生故障的工作路径恢复正常, 则将 业务从保护路径倒换回工作路径; 否则结束本流程。
2、根据权利要求 1所述的方法, 其特征在于, 所述业务的端节点为 工作路径的首节点或末节点。
3、根据权利要求 1所述的方法, 其特征在于, 所述业务倒换到保护 路径之前进一步包括: 以所述工作路径的端节点作为保护路径的端节 点, 建立保护路径;
则所述将业务从保护路径倒换回工作路径之后进一步包括: 删除所 述保护路径中与所述工作路径无关的连接。
4、根据权利要求 1所述的方法, 其特征在于, 所述业务倒换到保护 路径之后, 进一步包括: 以所述工作路径的端节点作为恢复路径的端节 点, 建立恢复路径。
5、根据权利要求 4所述的方法, 其特征在于, 所述将业务从保护路 径倒换回工作路径之后, 进一步包括: 删除所述恢复路径中与工作路径 无关的连接。 .
6、根据权利要求 1所述的方法, 其特征在于, 所述将业务从保护路 径倒换回工作路径之前, 进一步包括: 在所述端节点中设置等待恢复定 时器, 判断所述等待恢复定时器超时之前工作路径是否出现故障, 若是 则退出本流程; 否则, 执行所述后续步骤。
7、根据权利要求 1至 6任一项所述的方法, 其特征在于, 所述方法 应用于自动交换光网络 ASON。
8、根据权利要求 1至 6任一项所述的方法, 其特征在于, 所述保护 路径的端节点检测网络拓朴发生变化的方式是: 端节点接收开放式最短 路径优先-流量工程 OSPF-TE协议的洪泛信息后, 更新自身路由信息数 据库 RDB, 当其自身 RDB内容发生变化, 则网络拓朴发生变化。
9、一种网絡节点,包括路由控制器、链路资源管理器和连接控制器, 其特征在于, 所述网络节点还包括路径检验单元, 用于当链路资源管理 器报告网絡拓朴发生变化时, 判断以本网络节点设 乍为端节点的工作 路径是否由所述网络拓朴变化之前的故障状态恢复为正常状态, 若是则 向路由控制器发出路径返 信号;
所述路由控制器^^据所收到的路径返回信号, 触发连接控制器实现 业务由保护路径倒换回工作路径的流程。
10、 根据权利要求 9所述的网络节点, 其特征在于, 所述网絡节点 进一步包括等待恢复定时器;
则所述路径检验单元在向路由控制器发出路径返回信号之前, 进一 步用于 ·. 启动所述等待恢复定时器, 并在等待恢复定时器超时之前, 判 断所述工作路径是否出现故障, 若否, 则停止所述等待恢复定时器或向 路由控制器发出路径返回信号。
11、根据权利要求 10所述的网络节点, 其特征在于, 所述路径检测 单元和 /或等待恢复定时器为路由控制器的子模块。
12、 根据权利要求 9、 10或 11所述的网络节点, 其特征在于, 所述 网络节点为 ASON的网络节点。
PCT/CN2006/003474 2006-05-10 2006-12-18 A service switching method and the network node thereof Ceased WO2007128176A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CNA2006800114985A CN101176303A (zh) 2006-05-10 2006-12-18 一种业务倒换的方法和网络节点
EP06828385A EP1942604B1 (en) 2006-05-10 2006-12-18 A service switching method and the network node thereof

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610078543.0 2006-05-10
CNA2006100785430A CN101047440A (zh) 2006-05-10 2006-05-10 一种业务路径返回的方法

Publications (1)

Publication Number Publication Date
WO2007128176A1 true WO2007128176A1 (en) 2007-11-15

Family

ID=38667403

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003474 Ceased WO2007128176A1 (en) 2006-05-10 2006-12-18 A service switching method and the network node thereof

Country Status (3)

Country Link
EP (1) EP1942604B1 (zh)
CN (2) CN101047440A (zh)
WO (1) WO2007128176A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120087650A1 (en) * 2009-06-17 2012-04-12 Zte Corporation Service protection method and device based on automatic switched optical network
CN107395425A (zh) * 2017-07-31 2017-11-24 烽火通信科技股份有限公司 一种灵活以太网1+1保护倒换实现方法
CN112583474A (zh) * 2020-12-25 2021-03-30 中国电子科技集团公司第三十四研究所 一种光网络多路径快速切换系统和方法
CN113849361A (zh) * 2021-09-28 2021-12-28 北京百度网讯科技有限公司 测试服务节点的方法、装置、设备以及存储介质

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101466051B (zh) * 2007-12-21 2011-06-08 华为技术有限公司 一种业务路径搜索方法和装置
JP2010141879A (ja) * 2008-11-12 2010-06-24 Nec Corp 伝送装置、伝送ネットワーク及びそれらに用いる回線切り替え方法
CN101990133B (zh) * 2009-07-31 2014-02-19 中兴通讯股份有限公司 一种自动交换光网络业务降级告警状态的维护方法及系统
CN101998181B (zh) * 2009-08-10 2013-09-11 中兴通讯股份有限公司 Sncp业务迁移方法及装置
CN101998186A (zh) * 2009-08-13 2011-03-30 中兴通讯股份有限公司 网络保护方法及装置
CN102006188B (zh) 2010-11-19 2014-07-16 中兴通讯股份有限公司 一种传送网中的路径回切方法及装置
WO2012163242A1 (zh) * 2011-06-03 2012-12-06 中兴通讯股份有限公司 一种业务返回到初始路由的方法和装置
CN105141520A (zh) * 2014-05-28 2015-12-09 中兴通讯股份有限公司 一种保护倒换方法、装置及系统
CN104935507B (zh) * 2015-06-03 2018-05-08 瑞斯康达科技发展股份有限公司 一种线性保护倒换的方法、pe设备及系统
CN106330294A (zh) * 2015-06-18 2017-01-11 中兴通讯股份有限公司 光通讯网络中的业务控制方法及装置
CN104881759A (zh) * 2015-06-23 2015-09-02 四川久远银海软件股份有限公司 一种基于工作流的业务回退集成系统及其实现方法
CN105871452B (zh) * 2016-05-24 2018-04-20 烽火通信科技股份有限公司 一种ason中主备通道部分路径资源共享的方法
CN107579914A (zh) * 2016-07-04 2018-01-12 中兴通讯股份有限公司 一种快速抢通业务路由的装置和方法
CN106789634B (zh) * 2016-11-17 2020-06-26 深信服科技股份有限公司 基于链路负载双主环境的静态路由管理方法及系统
CN106789627B (zh) * 2016-11-30 2019-11-01 瑞斯康达科技发展股份有限公司 一种线性保护组的维护方法及装置
CN110121857B (zh) * 2016-12-30 2021-02-09 华为技术有限公司 一种凭据分发的方法和设备
CN112910781B (zh) * 2019-12-04 2022-12-06 中国电信股份有限公司 网络故障切换方法、装置、系统和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020167898A1 (en) 2001-02-13 2002-11-14 Thang Phi Cam Restoration of IP networks using precalculated restoration routing tables
US20030117950A1 (en) 2001-12-26 2003-06-26 Huang Gail G Link redial for mesh protection
US20040004937A1 (en) * 2002-07-05 2004-01-08 Nortel Networks Limited Method, device and software for establishing protection paths on demand and revertive protection switching in a communications network
US6757258B1 (en) * 2000-05-04 2004-06-29 Cisco Technology, Inc. Method and apparatus for reducing OSPF flooding
CN1710869A (zh) * 2005-07-14 2005-12-21 广东省电信有限公司研究院 自动交换光网络中连接的增强型主备保护的实现方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6757258B1 (en) * 2000-05-04 2004-06-29 Cisco Technology, Inc. Method and apparatus for reducing OSPF flooding
US20020167898A1 (en) 2001-02-13 2002-11-14 Thang Phi Cam Restoration of IP networks using precalculated restoration routing tables
US20030117950A1 (en) 2001-12-26 2003-06-26 Huang Gail G Link redial for mesh protection
US20040004937A1 (en) * 2002-07-05 2004-01-08 Nortel Networks Limited Method, device and software for establishing protection paths on demand and revertive protection switching in a communications network
CN1710869A (zh) * 2005-07-14 2005-12-21 广东省电信有限公司研究院 自动交换光网络中连接的增强型主备保护的实现方法

Non-Patent Citations (1)

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

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120087650A1 (en) * 2009-06-17 2012-04-12 Zte Corporation Service protection method and device based on automatic switched optical network
US8805180B2 (en) * 2009-06-17 2014-08-12 Zte Corporation Service protection method and device based on automatic switched optical network
CN107395425A (zh) * 2017-07-31 2017-11-24 烽火通信科技股份有限公司 一种灵活以太网1+1保护倒换实现方法
CN112583474A (zh) * 2020-12-25 2021-03-30 中国电子科技集团公司第三十四研究所 一种光网络多路径快速切换系统和方法
CN112583474B (zh) * 2020-12-25 2024-05-28 中国电子科技集团公司第三十四研究所 一种光网络多路径快速切换系统和方法
CN113849361A (zh) * 2021-09-28 2021-12-28 北京百度网讯科技有限公司 测试服务节点的方法、装置、设备以及存储介质
CN113849361B (zh) * 2021-09-28 2023-08-08 北京百度网讯科技有限公司 测试服务节点的方法、装置、设备以及存储介质

Also Published As

Publication number Publication date
EP1942604A1 (en) 2008-07-09
CN101047440A (zh) 2007-10-03
EP1942604B1 (en) 2013-02-20
EP1942604A4 (en) 2009-03-25
CN101176303A (zh) 2008-05-07

Similar Documents

Publication Publication Date Title
WO2007128176A1 (en) A service switching method and the network node thereof
US8289843B2 (en) Service failure recovery method and system
US7787362B2 (en) Method and device for recovering a shared mesh network
US20090196198A1 (en) Resource state monitoring method, device and communication network
US20080031619A1 (en) Method and device for recovering from inter-domain link failure
WO2008006268A1 (fr) Procédé,système et dispositif de noeud permettant de réaliser une protection de service dans un réseau optique commuté automatiquement
CN100589416C (zh) 一种自动交换光网络系统中业务产生告警时的维护方法
US20150186202A1 (en) Method and Device for Sending Inter-Domain Fault Information
WO2010028560A1 (zh) 在mesh网络中实现永久环网保护的方法
CN102315987B (zh) 环网保护组链路回切方法及装置
WO2008037162A1 (en) A method for service management in an intelligent optical network
WO2007048299A1 (en) A method and device for consistency verify of the time slot state in the traffic engineering link
US20030043427A1 (en) Method of fast circuit recovery using local restoration
CN100502528C (zh) 实现自动交换光网络中光连接间的关联的方法
CN100531092C (zh) 智能光网络的业务重路由触发方法
WO2010037305A1 (zh) 通知重路由的方法、节点设备及环网络
CN1710993B (zh) 智能光网络中的业务路径优化方法
CN100461689C (zh) 多层次自动交换光网络中代理节点的保护方法
CN101248630A (zh) 一种自动交换光网络快速重路由的实现方法
JPH11284656A (ja) 分散形電気通信ネットワークの復元方法とシステム
KR100501320B1 (ko) 다중 프로토콜 레이블 교환 시스템에서의 씨알-엘에스피복구 방법
CN1983908A (zh) 一种标签资源管理的自纠错方法
WO2010031283A1 (zh) 一种检测链路标签状态的方法、设备与系统
JP2008103893A (ja) 通信システムおよび故障復旧方法
WO2007071114A1 (fr) Procede pour le reacheminement sans interruption en reseau optique

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680011498.5

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 06828385

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2006828385

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2006828385

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE