WO2005060275A1 - Procede de choix de sortie d'un reseau local a fai multiples - Google Patents
Procede de choix de sortie d'un reseau local a fai multiples Download PDFInfo
- Publication number
- WO2005060275A1 WO2005060275A1 PCT/CN2004/001456 CN2004001456W WO2005060275A1 WO 2005060275 A1 WO2005060275 A1 WO 2005060275A1 CN 2004001456 W CN2004001456 W CN 2004001456W WO 2005060275 A1 WO2005060275 A1 WO 2005060275A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- nat
- routing
- route
- isp
- policy
- Prior art date
Links
Classifications
-
- 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
-
- 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/48—Routing tree calculation
-
- 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/302—Route determination based on requested QoS
- H04L45/308—Route determination based on user's profile, e.g. premium users
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2557—Translation policies or rules
Definitions
- the present invention relates to network routing technology, and in particular, to a method for selecting an outlet of a multi-ISP local area network. More specifically, it relates to a method for selecting an access exit of a local area network connecting multiple Internet service providers (ISPs).
- ISPs Internet service providers
- NAT Network Address Translation
- ISP Internet Service Provider
- Host routing A 32-bit mask entry corresponding to the host directly connected to the network device in the routing table. This type of entry has ARP (Address Resolution Protocol) corresponding to it.
- ARP Address Resolution Protocol
- a campus network is usually configured with multiple network exits connected to an ISP (Interne t Serv Ice Provider) access service provider, and multiple network exits are backups and load sharing between each other to improve the communication bandwidth between the campus network and the external network. And robustness. This situation is particularly common in the construction of campus networks.
- campus networks are connected to a public operator and education network.
- NAT Network Address Translation
- Multiple routers are used for networking.
- One of the routers divides the packets according to the source and destination information of the packets. After the packets are diverted, they are forwarded to multiple routers.
- the multiple routers perform NAT operations. To achieve the purpose of NAT multi-export policy control.
- Figure 1 is a schematic diagram of a prior art multi-IP campus network networking. It uses one core switch and multiple dedicated NAT devices to implement the NAT multi-exit policy control function. This type of network can implement the NAT multi-exit policy control function. At the same time, the dedicated NAT device of the hardware performs the NAT conversion operation, which can guarantee the bandwidth. However, due to the need to add a dedicated NAT device for implementation, that is, each ISP exit needs to be equipped with a dedicated NAT device, the increase in networking costs also leads to an increase in failure points.
- the above-mentioned multi-device mixed networking implements the multi-export policy control function.
- the core routing switch cannot detect the failure of the device, which will cause the ISP's egress traffic to be interrupted and requires manual Intervene to modify the complex traffic classification strategy to implement backup for multiple ISP egress.
- the purpose of the present invention is to overcome the above-mentioned shortcomings of the prior art, and to provide a method for selecting an outlet of a multi-ISP local area network, so as to solve the problem of increased cost and failure points caused by setting up multiple dedicated NAT devices, and to adapt to It is required to implement non-blocking forwarding at the same time as implementing complex forwarding strategies and backup of the egress link.
- the present invention provides a method for selecting an exit of a multi-IP local area network, which includes the following steps:
- the step of presetting a NAT address pool corresponding to the NAT egress of each ISP includes:
- the leaf nodes of the NAT policy tree store The binding relationship between the outgoing interface of each ISP and the corresponding NAT address pool and the NAT policy information of the slot number of the NAT translation board
- the step of determining whether a NAT translation is required includes:
- Detect whether there is a public network flag in the routing entry that the user traffic hits and after detecting the public network flag, use the combination of the outbound interface and the source IP address as a key to query whether the NAT policy tree leaf is hit If the node hits the leaf node of the NAT policy tree, it is determined that NAT conversion is required; otherwise, NAT conversion is not required.
- the step of selecting a NAT address pool corresponding to an ISP exit includes: using the combination of the outbound interface and the source IP address as a key, matching in a leaf node of the policy tree, and matching in the matched NAT policy tree.
- the leaf nodes get the address pool and NAT translation board slot number.
- the NAT policy tree created is a binary tree.
- it further includes:
- a local area network route as a general route and a policy route, the general route serving as a backup of the policy route, and setting a routing policy for the policy route;
- the step of querying the routing table to determine the next hop route includes:
- the step of judging whether the strategic routing is available includes:
- next hop can hit a directly connected host route with a 32-bit mask. If so, it is determined that the policy route is available; if not, it is determined that the policy route is not available.
- the step of determining a next hop route further includes:
- the software processing in the routing switch includes a routing module and a NAT module, the routing module is completely separated from the NAT module, wherein the routing module determines a routing exit for user traffic, and the NAT module determines whether to do NAT translation and selection of the corresponding NAT address pool.
- a NAT translation and an address pool binding relationship are required to be determined according to a source IP address, an outbound interface, a common route, and a policy route, and a NAT policy tree is added to describe the address pool binding relationship.
- the routing module and the The NAT module is separated to meet the requirements of distributed forwarding. While implementing complex forwarding strategies, it also meets line-speed non-blocking forwarding requirements.
- FIG. 1 is a schematic diagram of a prior art multi-ISP campus network networking
- FIG. 2 shows a flowchart of a NAT multi-ISP policy forwarding according to an embodiment of the present invention
- FIG. 3 depicts a policy NAT forwarding flowchart described in conjunction with a specific device according to another embodiment of the present invention.
- the key process of the present invention is to add a NAT policy table to the forwarding plane, and directly perform NAT policy control on the forwarding plane when data flow is forwarded, so that the core routing switch can complete complex NAT policy control while using the distributed forwarding plane.
- the core routing switch at the core of the campus network can independently implement the NAT policy function, which simplifies the complexity of the network.
- the ISP's egress is selected based on user source information and outbound interface information. It can flexibly cooperate with multiple ISP's billing flow control policies to save users' egress traffic costs.
- FIG. 2 shows the NAT multi-ISP policy forwarding flowchart of the present invention.
- a NAT policy table is added to the forwarding plane, and the storage manner of the policy table is a tree structure.
- the index of this table is the source IP + outbound interface.
- the contents of the entry are the bound ISP egress information, including the address pool and the number of links.
- query the NAT policy table After querying the routing table and policy routing in the forwarding process, query the NAT policy table to obtain the information of the egress ISP, and then perform NAT operations based on this information.
- the available ISP is automatically selected to achieve hot backup between multiple ISPs.
- step 2 determine whether policy routing is needed. If it is not needed, use the source IP + outbound interface A to query the NAT policy tree, and then go to step 5. If necessary, go to step 3; '
- ISP export backups are achieved by two means:
- the routing processing system of the core routing switch will automatically recalculate the route, select a new route and deliver it to the routing table, so as to implement backup for multiple ISP exits.
- the "policy NAT" of the present invention needs to implement the following three key functional points:
- NAT When the public network address does not match the user's address space with its egress space, NAT must be performed with the address pool bound to its egress.
- the routing module is completely separated from the NAT module.
- the routing module (including destination address routing and policy routing) determines the egress of user traffic, whether to do NAT, and which address pool to choose, which is determined by the NAT module.
- a complete policy routing must be completed, and the purpose of backup of general routes to policy routing must be achieved.
- the backup of policy routes by ordinary routes is used, that is, when policy routing is not available, user traffic Automatically follow normal routing.
- the routing table is searched based on the next hop of the policy route. Because the next hop of the available route is usually a direct-connected host, can a direct-connect host route with a 32-bit mask be hit?
- a route is available. If a direct-connected host route with a 32-bit mask is hit, then this policy route is available; otherwise, the policy route does not take effect and is forwarded as a normal route.
- the user's private network address should be translated into public networks in different address pools When the address, that is, the user's address space does not match its egress space, NAT translation must be performed with the address pool bound to its egress.
- the embodiment of the present invention realizes that different user traffic exits from different I SPs and performs NAT translation with different address pools.
- the address pool is no longer registered in the global mode, but is bound to the outbound interface.
- a NAT policy tree is created with the combination of the outbound interface and the source IP as keywords, and the binding relationship of the address pool and the slot number of the distributed dedicated NAT board are recorded.
- User traffic hits the road Whether or not there is a public network tag in the entry serves as the enable switch for searching the NAT policy tree. This tag is configured by the user on the outbound interface connected to the ISP. Any route that falls on this outbound interface has a public network tag.
- NAT translation is required before the message is exported.
- the address pool and the slot number of the NAT board are obtained from the leaves of the NAT policy tree, and the message is transferred to the NAT board for processing. If it cannot be hit, it means that the user is a public network address user and belongs to the same address space as the ISP of the interface here. No NAT conversion is required, and the corresponding I SP exit user board is directly processed according to the routing information.
- the routing module determines the egress of user traffic, whether to perform NAT and which address pool to choose is determined by the NAT module.
- the routing module and the NAT module are completely separated to ensure that the two are logically divided clearly, and the functions are no longer affected by each other. This leaves sufficient space for the realization of various complex forwarding logic combinations for different users.
- FIG. 3 depicts a flow chart of policy NAT forwarding combined with specific devices according to another embodiment of the present invention.
- step 210 the routing table is searched by using the destination IP, and a possible next hop is determined according to the routing table.
- step 220 it is determined whether there are multiple next hops according to the searched routing table. If it is determined in step 220 that there are multiple next hops, in step 230, these multiple next hops perform traffic sharing; and then proceed to step 240. Judging whether the strategic route is successfully matched; if it is judged in step 220 that there are no multiple next hops but only one next hop, go directly to step 240 to judge whether the strategic route is successfully matched;
- step 240 If it is determined in step 240 that the policy routing match is successful, proceed to step 250, and use the next hop of the policy routing to check the routing table to determine whether the host route can be hit. If it is determined in step 250 that the host route can be matched, proceed to step 260, and use the policy routing result to overwrite Destination address routing. Then, proceed to step 270 to determine whether the routing entry has a public network flag;
- step 240 If it is determined in step 240 that the policy routing match is unsuccessful, and if it is determined in step 250 that the host route cannot be hit, proceed to step 270; If it is determined in step 270 that there is a public network flag, proceed to step 280, use the source IP and the outbound interface to check the NAT policy tree, and determine whether it hits;
- step 280 If the hit is determined in step 280, the process proceeds to step 290, and the address pool number is obtained according to the search result. Then, in step 310, the distributed NAT processing device of the distributed NAT conversion board is transferred via the switching network to implement NAT conversion. Then, in step 300, enter the switching network; if it is determined in step 270 that there is no public network flag, and if it is determined in step 280 that it has not been hit, in step 300, enter the switching network;
- step 320 the packet is forwarded to the egress user board according to the routing result.
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/583,569 US20070147395A1 (en) | 2003-12-19 | 2004-12-15 | Method for selecting egresses of a multi-isp local area network |
EP04802469A EP1699247B1 (en) | 2003-12-19 | 2004-12-15 | Multiple isp local area network egress selecting method |
DE602004027080T DE602004027080D1 (de) | 2003-12-19 | 2004-12-15 | Verfahren zur auswahl eines mehrfach-isp-lokalnetz-ausgangs |
AT04802469T ATE467290T1 (de) | 2003-12-19 | 2004-12-15 | Verfahren zur auswahl eines mehrfach-isp- lokalnetz-ausgangs |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200310123979.3 | 2003-12-19 | ||
CNB2003101239793A CN100454882C (zh) | 2003-12-19 | 2003-12-19 | 多isp局域网的出口选择方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005060275A1 true WO2005060275A1 (fr) | 2005-06-30 |
Family
ID=34683176
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2004/001456 WO2005060275A1 (fr) | 2003-12-19 | 2004-12-15 | Procede de choix de sortie d'un reseau local a fai multiples |
Country Status (6)
Country | Link |
---|---|
US (1) | US20070147395A1 (zh) |
EP (1) | EP1699247B1 (zh) |
CN (1) | CN100454882C (zh) |
AT (1) | ATE467290T1 (zh) |
DE (1) | DE602004027080D1 (zh) |
WO (1) | WO2005060275A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
RU2518186C2 (ru) * | 2008-10-01 | 2014-06-10 | Телефонактиеболагет Лм Эрикссон (Пабл) | Обработка трафика локального непосредственного соединенения в домашней базовой станции |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100505899C (zh) | 2005-08-04 | 2009-06-24 | 华为技术有限公司 | 第三代移动通信系统的跨域路由控制方法 |
CN101228736B (zh) * | 2005-12-28 | 2012-05-30 | 中兴通讯股份有限公司 | 用于自动交换光网络组播业务的连接控制方法和装置 |
SG159399A1 (en) * | 2008-08-13 | 2010-03-30 | Smart Comm Inc | Message routing platform |
CN102035676B (zh) * | 2010-12-07 | 2014-08-13 | 中兴通讯股份有限公司 | 基于arp协议交互的链路故障检测与恢复的方法和设备 |
CN102035745B (zh) * | 2010-12-23 | 2012-08-15 | 北京星网锐捷网络技术有限公司 | 策略路由实现方法、装置及网络设备 |
CN102158406B (zh) * | 2011-04-01 | 2013-10-23 | 中国人民解放军国防科学技术大学 | 面向计算机网络链路的智能选路方法 |
CN102170394B (zh) * | 2011-04-19 | 2014-02-12 | 杭州华三通信技术有限公司 | 一种报文转发方法及其装置 |
CN102546443B (zh) * | 2012-03-23 | 2015-02-11 | 徐州中矿大华洋通信设备有限公司 | 一种分布式策略路由的方法 |
CN103036801B (zh) * | 2012-12-18 | 2019-06-14 | 网神信息技术(北京)股份有限公司 | 数据包的处理方法及装置 |
CN103888277B (zh) * | 2012-12-19 | 2018-09-04 | 中国移动通信集团公司 | 一种网关容灾备份方法、装置和系统 |
CN103188154B (zh) * | 2013-04-19 | 2016-03-02 | 杭州华三通信技术有限公司 | 一种网络地址转换的方法和板卡 |
CN104301236B (zh) * | 2014-09-11 | 2018-05-29 | 赛尔网络有限公司 | 一种校园网多出口导流方法及系统 |
CN104660729A (zh) * | 2015-02-13 | 2015-05-27 | 广东睿江科技有限公司 | 自动切换网络地址转换设备出口方法及网络地址转换设备 |
CN107547689B (zh) * | 2017-09-20 | 2020-12-04 | 新华三技术有限公司 | 一种运营商级的网络地址转换cgn方法和装置 |
CN109120746B (zh) * | 2018-09-30 | 2022-04-15 | 新华三技术有限公司 | 网络地址转换方法、装置及地址转换设备 |
CN110138660B (zh) * | 2019-06-06 | 2020-03-03 | 杭州商湾网络科技有限公司 | 一种多出口路由选择方法 |
CN111865990B (zh) * | 2020-07-23 | 2023-02-21 | 上海中通吉网络技术有限公司 | 内网恶意反向连接行为的管控方法、装置、设备和系统 |
CN113014630A (zh) * | 2021-02-10 | 2021-06-22 | 腾讯科技(深圳)有限公司 | 实现通信连续性的方法及相关设备 |
US11937165B1 (en) | 2022-09-27 | 2024-03-19 | Stackshare Technologies LLC | Systems and methods of selectively routing a packet flow |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001067258A1 (en) * | 2000-03-03 | 2001-09-13 | Nexland, Inc. | Network address translation gateway for local area networks using local ip addresses and non-translatable port addresses |
WO2002023822A1 (en) * | 2000-09-13 | 2002-03-21 | Alcatel Usa Sourcing, L.P. | Method and apparatus for facilitating peer-to-peer application communication |
CN1441569A (zh) * | 2002-02-27 | 2003-09-10 | 华为技术有限公司 | 一种网络设备的集群管理方法 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6243379B1 (en) * | 1997-04-04 | 2001-06-05 | Ramp Networks, Inc. | Connection and packet level multiplexing between network links |
US6665702B1 (en) * | 1998-07-15 | 2003-12-16 | Radware Ltd. | Load balancing |
US20020002615A1 (en) * | 1998-09-18 | 2002-01-03 | Vijay K. Bhagavath | Method and apparatus for switching between internet service provider gateways |
US7155740B2 (en) * | 2000-07-13 | 2006-12-26 | Lucent Technologies Inc. | Method and apparatus for robust NAT interoperation with IPSEC'S IKE and ESP tunnel mode |
US7418522B2 (en) * | 2000-12-21 | 2008-08-26 | Noatak Software Llc | Method and system for communicating an information packet through multiple networks |
JP2003110596A (ja) * | 2001-09-28 | 2003-04-11 | Hitachi Ltd | データ通信サービス提供方法 |
US7958199B2 (en) * | 2001-11-02 | 2011-06-07 | Oracle America, Inc. | Switching systems and methods for storage management in digital networks |
US20030172170A1 (en) * | 2002-03-08 | 2003-09-11 | Johnson Gerald R. | Providing multiple ISP access to devices behind NAT |
JP3665622B2 (ja) * | 2002-03-29 | 2005-06-29 | 株式会社東芝 | ソースアドレス選択システム、ルータ装置、通信ノード及びソースアドレス選択方法 |
-
2003
- 2003-12-19 CN CNB2003101239793A patent/CN100454882C/zh not_active Expired - Fee Related
-
2004
- 2004-12-15 US US10/583,569 patent/US20070147395A1/en not_active Abandoned
- 2004-12-15 AT AT04802469T patent/ATE467290T1/de not_active IP Right Cessation
- 2004-12-15 WO PCT/CN2004/001456 patent/WO2005060275A1/zh not_active Application Discontinuation
- 2004-12-15 EP EP04802469A patent/EP1699247B1/en not_active Not-in-force
- 2004-12-15 DE DE602004027080T patent/DE602004027080D1/de active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2001067258A1 (en) * | 2000-03-03 | 2001-09-13 | Nexland, Inc. | Network address translation gateway for local area networks using local ip addresses and non-translatable port addresses |
WO2002023822A1 (en) * | 2000-09-13 | 2002-03-21 | Alcatel Usa Sourcing, L.P. | Method and apparatus for facilitating peer-to-peer application communication |
CN1441569A (zh) * | 2002-02-27 | 2003-09-10 | 华为技术有限公司 | 一种网络设备的集群管理方法 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
RU2518186C2 (ru) * | 2008-10-01 | 2014-06-10 | Телефонактиеболагет Лм Эрикссон (Пабл) | Обработка трафика локального непосредственного соединенения в домашней базовой станции |
Also Published As
Publication number | Publication date |
---|---|
DE602004027080D1 (de) | 2010-06-17 |
EP1699247A4 (en) | 2007-03-21 |
EP1699247B1 (en) | 2010-05-05 |
CN1630268A (zh) | 2005-06-22 |
EP1699247A1 (en) | 2006-09-06 |
US20070147395A1 (en) | 2007-06-28 |
ATE467290T1 (de) | 2010-05-15 |
CN100454882C (zh) | 2009-01-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2005060275A1 (fr) | Procede de choix de sortie d'un reseau local a fai multiples | |
US10116556B2 (en) | Techniques for routing and forwarding between multiple virtual routers implemented by a single device | |
JP5579853B2 (ja) | バーチャル・プライベート・ネットワークの実現方法及びシステム | |
US6163543A (en) | Port aggregation protocol | |
CA2169493C (en) | Method and apparatus for interconnecting atm emulated lans | |
CN101155109B (zh) | 一种以太网交换系统及设备 | |
US20040213272A1 (en) | Layer 2 switching device | |
WO2009033428A1 (fr) | Procédé, système et dispositif pour retirer une adresse de commande d'accès au support | |
CN110061915B (zh) | 跨多个架构交换机的虚拟链路聚合的方法和系统 | |
WO2006099786A1 (fr) | Procédé de mise en œuvre d’un processus en anneau, d'un processus hors anneau et de transfert de données dans un réseau annulaire de données en paquets à résilience et dispositif en réseau idoine | |
WO2006005260A1 (fr) | Reseau prive virtuel et procede de commande et de transmission d'acheminement | |
WO2007016839A1 (en) | Method and system for carrying out hierarchical virtual private switch services | |
WO2010020107A1 (zh) | 号码自动路由方法、更新方法、撤销方法、路由器及设备 | |
WO2005112350A1 (fr) | Procede de gestion de chemin dans un reseau prive virtuel utilisant le protocole ipv6 | |
WO2007012286A1 (fr) | Procede de transmission de donnees par paquets et dispositif de commutation lan base sur vlan | |
WO2006002598A1 (fr) | Systeme vpn de reseau federateur hybride a site hybride et son procede de mise en oeuvre | |
WO2008011818A1 (fr) | Procédé de fourniture d'un service réseau local privé virtuel à hiérarchie et système réseau | |
WO2006131055A1 (fr) | Procédé et élément de réseau destiné au transfert de données | |
WO2007112691A1 (fr) | Système, procédé et dispositif réseau permettant à un client de réseau privé virtuel (vpn) d'accéder à un réseau public | |
WO2013107245A1 (zh) | 在透明多链路互联(trill)网络中实现组播的方法、装置及系统 | |
WO2013139159A1 (zh) | 在网络中转发报文的方法和运营商边缘设备 | |
CN111064596A (zh) | 对于用于多宿主节点故障的bum流量的节点保护 | |
EP4044523A1 (en) | Packet forwarding method, first network device, and first device group | |
WO2007031006A1 (en) | A virtual switching method which could be routed | |
WO2011057570A1 (zh) | 虚拟局域网的数据传输方法、设备与系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2004802469 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007147395 Country of ref document: US Ref document number: 10583569 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
WWP | Wipo information: published in national office |
Ref document number: 2004802469 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 10583569 Country of ref document: US |