WO2006007789A1 - Procede pour mettre en oeuvre une gestion de terminaux dans un dispositif reseau - Google Patents
Procede pour mettre en oeuvre une gestion de terminaux dans un dispositif reseau Download PDFInfo
- Publication number
- WO2006007789A1 WO2006007789A1 PCT/CN2005/001076 CN2005001076W WO2006007789A1 WO 2006007789 A1 WO2006007789 A1 WO 2006007789A1 CN 2005001076 W CN2005001076 W CN 2005001076W WO 2006007789 A1 WO2006007789 A1 WO 2006007789A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- management
- network
- packet
- terminal
- network device
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
- H04L41/046—Network management architectures or arrangements comprising network management agents or mobile agents therefor
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/34—Signalling channels for network management communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/005—Interface circuits for subscriber lines
- H04M3/007—Access interface units for simultaneous transmission of speech and data, e.g. digital subscriber line [DSL] access interface units
Definitions
- the present invention relates to the field of network communication technologies, and in particular, to a method for implementing terminal management in a network device.
- DSL Digital Subscriber Line
- SNMP Simple Network Management Protocol
- the SNMP protocol is used to ensure that management information is transmitted between any two nodes in the communication network. It is convenient for the network administrator to retrieve information in any node of the communication network, modify related configuration information, and find faults to complete fault diagnosis and capacity planning. And generating reports and other work.
- SNMP is typically used for communication between NMS (network management workstations) and network device agents (agents).
- the communication process between the NMS and the network device agent is as shown in FIG. 1.
- the NMS ie, the network management system, the SNMP management entity
- the NMS receives from the managed The network device Agent's Respons message and trap message, and display the result.
- the agent is further divided into a Proxy Agent (master agent) (ie, the central office device in FIG. 1 and an SNMP agent entity) and a Praxied Agent (ie, the terminal in FIG. 1 and an SNMP agent entity), where the Proxy Agent is located.
- the network device is the primary network device.
- the network device where the Proxied Agent is located is the secondary network device.
- the NMS and the Proxy Agent communicate directly through SNMP.
- the Proxy Agent and the Proxied Agent communicate through the communication protocol between the primary network device and the secondary network device.
- the SNMP-based request packets sent by the NMS are first authenticated on the Proxy Agent. If the request packet is for the Proxy Agent, the corresponding request packet is processed and responded accordingly. If the message is requested, the SNMP-based request sent by the NMS is forwarded to the corresponding Proxied Agent, and the Proxied Agent processes and responds to the request.
- the DSLAM Digital User Access Management
- the packet authentication function is implemented. That is, the network device DSLAM can accurately identify that the request packet is sent to the Proxy Agent. , also sent to the Proxied Agent.
- the received request message needs to be processed accordingly, and the processing result is returned to the sending end of the request message, that is, the NMS.
- the NMS the processing result is returned to the sending end of the request message, that is, the NMS.
- the SNMP request packet is delivered by using an IP (Internet Protocol) bearer, or there is only one NMS for the Proxy Agent, the response packet for the request packet may be in the DSLAM device. It is easy to determine which NMS it should send to without special handling.
- the SNMP packets between the DSLAM device and the terminal are in non-IP bearer SNMP mode.
- the long-term virtual path) management mode the protocol hierarchy of the mode is shown in Figure 2. It can be seen that the SNMP packets are directly carried on the PVC and sent to the terminal. Because the SNMP management packet does not have the content of the UDP packet header or the IP packet header, the terminal management does not need to implement the routing function. The implementation is very simple and secure.
- the problems brought by this method are: 1) The network device (DSLAM) cannot distinguish whether the network management message is a management network device or a management terminal device; 2) when the same DSLAM device is simultaneously managed by multiple NMSs, the DSLAM device The receiving network management of the response packet from the terminal cannot be distinguished. After the DSLAM device receives the response packet sent by the terminal, the DSLAM device cannot determine which NMS the response packet should be sent to.
- the DSLAM cannot distinguish the destination of the terminal, so the same terminal cannot support the management of multiple network management.
- the DSLAM device cannot manage the terminal without the IP address.
- an object of the present invention is to provide a method for implementing terminal management in a network device, so that the same terminal can support management of multiple network management systems, and the same can be used for a terminal without an IP address. Manage.
- the present invention provides a method for implementing terminal management in a network device, including: receiving, by the network device, a packet sent by the network management system to the terminal, and determining the packet according to the information carried by the packet.
- the network device that receives the response message according to the identification information in the response message, and sends the response message to the determined network packet. network management.
- the message is: Management message based on SNMP (Simple Network Management Protocol).
- the identification information of the packet includes terminal identification information and network management identification information; the terminal identification information is: an identifier of an interface relationship between the terminal device and the network device;
- the network management identification information is: the network management IP address, or the network management IP address, and the terminal physical interface relationship of the network device.
- the method further includes: storing network management identification information of the packet on the network device.
- the network management system that receives the response message is determined according to the network management identification information in the response message.
- the terminal device performs corresponding terminal processing according to the corresponding management packet forwarded by the network device, does not need to modify the SNMP header information, and then responds to the processing result to the network device.
- the terminal device receives the network management device returns the text Gen ⁇ 1, the network device from the response packet network identification information, resolution response packet network identification information, determine a response to the packet network based on the network identification information parsed.
- the network management information of the packet may be carried in the request number, the community field, or the error index field of the packet, or the identifier information of the packet may be carried in the packet.
- Customizable bearer information fields may be carried in the request number, the community field, or the error index field of the packet, or the identifier information of the packet may be carried in the packet.
- the network device When receiving the response packet of the terminal device, the network device can directly query the network management identification information stored in the network device, and determine the response to the network management device according to the network management identification information. Text.
- the method for determining the message identification information distinguishes the packets sent by different NMSs to the DSLAM device, so that when the terminal When the DSLAM device returns the response packet, the response packet carries the network management identifier, so that the DSLAM device can easily determine which response packet the response packet is sent to. Therefore, the present invention provides a great convenience for the network device to manage the terminal device, so that when the network device and the terminal use non-IP bearer to perform packet interaction, the same terminal can support multiple NMSs. Management; At the same time, on a DSLAM device, it is also possible to manage terminals without an IP address. Moreover, the implementation of the present invention can be defined by the SNMP protocol format and the SNMP message field, thereby ensuring the feasibility of the present invention, and the implementation is simple and convenient.
- Figure 1 is a schematic diagram of a management model between a network management system and a terminal in a DSLAM;
- Figure 2 is a schematic diagram of an SNMP packet directly carried on a PVC channel
- Figure 3 shows the format of a typical SNMP packet.
- FIG. 4 is a schematic diagram of a management model between a network management system and a terminal that can be supported by the present invention
- Figure 5 is a flow chart of the method of the present invention.
- the core of the present invention is that the network device obtains the identification information of the packet according to the received information of the received message sent by the network device, and saves the network management identification information of the packet in the network device or The packet is sent to the terminal together, so that the terminal device responds to the network device according to the corresponding management packet forwarded by the network device.
- the network device determines the network management device that receives the response packet according to the network management identifier information of the packet, and sends the network packet to the determined network management device, so that the network device is configured according to the present invention.
- the terminal can support the management of multiple network management systems and can manage terminals without IP addresses. That is to say, the present invention needs to identify the IP address information of the network management pipe by using a specific field of the SNMP message header between the DSLAM and the terminal, thereby achieving the object of the present invention.
- the network management device sends the network management packet to the terminal under its jurisdiction through the network device.
- the SNMP packet sent by the NMS to the network device is in the format shown in Figure 2.
- the IP packet of the UDP (User Datagram Protocol) packet carries the SNMP management packet.
- the IP address of the IP packet header cannot be Terminal IP address, so the network device ends with other fields in the packet header
- the managed terminal device is identified in the terminal identification information.
- the SNMP packet sent by the network device to the terminal has no IP layer, and cannot identify the source address of the network management device and the destination address of the managed terminal device, so the network device cannot determine the terminal response according to the information.
- the ⁇ text is for which network management.
- the network device After receiving the packet sent by the network management system, the network device, such as the DSLAM, parses the information carried in the packet, and obtains the SNMP packet header field (such as the community) for identifying the terminal information in the packet, and identifies the managed terminal device. .
- the network device such as the DSLAM
- SNMP is carried on the standard IP/UDP packet between the network management device and the network device, and the SNMP packet header data of the network management system and the terminal can be utilized.
- the SNMP packet header data of the network management system and the terminal may be used, such as "version, community, PDU type, request number, error status, error index information", or SNMP report.
- the custom field of the text can also be carried in these fields.
- the source IP address information of the packet is obtained according to the IP packet in the network management packet information, and the source IP address information of the packet is the IP address information of the network management, and the network management identification information is created.
- the network device identifies the network management identifier of the packet as: a network management IP address on the network device.
- the management process it can be known that the SNMP is carried on the PVC between the terminal device and the network device, so only the SNMP packet header data "version, common", PDU type, request number, error status, The field in the error index information, or a custom field for SNMP data.
- the network management identification information of the packet may be carried in the management packet and sent to the terminal device, or the network device saves the network management knowledge. No information.
- the DSLAM device When the DSLAM device receives the response packet returned by the terminal, determining, according to the network management identification information of the packet, the IP address information of the receiving network management device of the response packet, and returning the information according to the physical interface of the network device. Terminal identification information can also be obtained.
- the IP address of the network management device that receives the response packet can be obtained, for example, If the field is in the community field or the error index field of the SNMP packet, the IP address information of the network management system can be obtained by parsing the field;
- the identification information of the packet is saved in the network device in the step (3), the information in the packet is still only required to be obtained in the normal packet parsing manner, and the packet is in the report according to the information.
- the identification information of the text determines the IP address of the network management. For example, if the identification information of the saved packet is recorded in the network device, the correspondence between the request number of the packet and the source IP address is required, and only the packet needs to be parsed in this step.
- the request number can be used to determine the IP address information of the network management system according to the request number.
- the response message can be sent to the determined network management device, that is, the DSLAM device can uniquely determine according to the determined IP address information of the network management device.
- the network management of the response packet is forwarded, so that management of the terminal is implemented on the network device.
- the implementation of the present invention enables the terminal to support multiple network management devices to manage the network.
- the terminal can be conveniently distributed. Which response packet is sent to the network management, which greatly facilitates the management of the terminal through the network device DSLAM.
- the specific implementation manner of the method according to the present invention is further described below in conjunction with a specific application example. As shown in FIG. 5, the following specifically includes the following processing steps:
- Step 51 The network device receives a network management packet of the network management terminal, where the packet is used for performing management operations on the terminal under the jurisdiction;
- Step 52 The network device parses the packet, and obtains the network management IP ( 10.11.12.13 ) address information of the packet and the "Communtiy" field of the SNMP packet header field, where the value of the "Communtiy” includes the terminal identification.
- Information such as "Communtiy" value is "010203@public” means that the terminal device is connected to port 03 of slot 02 of the network device, the access permission is public, and the format is user-defined;
- Step 53 Convert the IP bearer NMP network management packet to the PVC of the terminal device on the network device.
- the SNMP management mode is carried:
- the network management identifier is carried in the SNMP header, and is bound to the "RequestlD" request number field, and the request number is "Requestld”. " Value is OxOAOBOCOD;
- Step 54 The network device sends the packet to the corresponding terminal, and the terminal device performs corresponding management processing, and then returns the result to the network device. .
- Step 56 The network device converts the response packet according to the opposite direction of step 52, and binds the terminal identification information to the SNMP packet header to form a Community field of the format "010203@public", and sends the information according to the IP address of the network management system.
- the network management system that receives the response packet is the network management device that sends the request packet (that is, the management packet) to the terminal.
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/570,292 US20080270584A1 (en) | 2004-07-22 | 2005-07-20 | Method for Realizing Terminal Management in the Network Device |
AT05766920T ATE443388T1 (de) | 2004-07-22 | 2005-07-20 | Verfahren zur endgeräteverwaltung bei einem netzwerkgerät |
EP05766920A EP1770906B1 (en) | 2004-07-22 | 2005-07-20 | A method for realizing terminals management in the network device |
DE602005016682T DE602005016682D1 (de) | 2004-07-22 | 2005-07-20 | Verfahren zur endgeräteverwaltung bei einem netzwerkgerät |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200410054823.9 | 2004-07-22 | ||
CNB2004100548239A CN100454828C (zh) | 2004-07-22 | 2004-07-22 | 在网络设备中实现终端管理的方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2006007789A1 true WO2006007789A1 (fr) | 2006-01-26 |
Family
ID=35784876
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2005/001076 WO2006007789A1 (fr) | 2004-07-22 | 2005-07-20 | Procede pour mettre en oeuvre une gestion de terminaux dans un dispositif reseau |
Country Status (6)
Country | Link |
---|---|
US (1) | US20080270584A1 (zh) |
EP (1) | EP1770906B1 (zh) |
CN (1) | CN100454828C (zh) |
AT (1) | ATE443388T1 (zh) |
DE (1) | DE602005016682D1 (zh) |
WO (1) | WO2006007789A1 (zh) |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100518087C (zh) * | 2006-03-03 | 2009-07-22 | 鸿富锦精密工业(深圳)有限公司 | 管理用户终端设备的装置及方法 |
US8050268B2 (en) * | 2006-04-18 | 2011-11-01 | Fluke Corporation | Methods and apparatus for IP management traffic consolidation |
CN100426753C (zh) * | 2006-07-24 | 2008-10-15 | Ut斯达康通讯有限公司 | 一种基于snmp的网络管理方法 |
CN100454853C (zh) * | 2006-10-25 | 2009-01-21 | 华为技术有限公司 | 检测业务通道的方法及提供检测业务通道方法的系统 |
CN101227412B (zh) * | 2008-02-05 | 2010-09-29 | 华为技术有限公司 | 报文转换的方法和设备 |
CN101232409B (zh) * | 2008-02-20 | 2014-04-30 | 中兴通讯股份有限公司 | 不对称数字用户线路终端设备的配置方法 |
CN101621420B (zh) * | 2008-07-02 | 2012-03-28 | 大唐移动通信设备有限公司 | 一种并发流程测试中链路建立和释放的方法、系统 |
CN107733669B (zh) * | 2016-08-11 | 2023-03-14 | 中兴通讯股份有限公司 | 基于request ID的SNMP服务器管理方法及系统 |
JP7110573B2 (ja) * | 2017-09-29 | 2022-08-02 | 京セラドキュメントソリューションズ株式会社 | 情報処理装置、情報処理プログラム及び情報処理方法 |
CN111181859B (zh) * | 2019-12-31 | 2022-03-25 | 京信网络系统股份有限公司 | 网络设备的监控方法、系统、路由设备和存储介质 |
CN111769973A (zh) * | 2020-06-05 | 2020-10-13 | 苏州浪潮智能科技有限公司 | 一种改进的双向snmp告警方法及装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5678006A (en) * | 1995-04-27 | 1997-10-14 | Cisco Systems, Inc. | Network switch having network management agent functions distributed among multiple trunk and service modules |
US20020188708A1 (en) * | 2001-06-11 | 2002-12-12 | Hiroko Takahashi | Network management method and apparatus |
US6725264B1 (en) | 2000-02-17 | 2004-04-20 | Cisco Technology, Inc. | Apparatus and method for redirection of network management messages in a cluster of network devices |
CN1510865A (zh) | 2002-12-24 | 2004-07-07 | 深圳市中兴通讯股份有限公司 | 一种网管网关的实现方法 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4430639A (en) * | 1981-05-21 | 1984-02-07 | Benvar Associates, C/O Dale Bennett | Visual message intercommunication unit and system |
US5907696A (en) * | 1996-07-03 | 1999-05-25 | Cabletron Systems, Inc. | Network device simulator |
US5996010A (en) * | 1996-08-29 | 1999-11-30 | Nortel Networks Corporation | Method of performing a network management transaction using a web-capable agent |
US6370152B1 (en) * | 1997-05-30 | 2002-04-09 | Adtran, Inc. | Distributed SNMP agent for frame relay switching network |
US6044468A (en) * | 1997-08-25 | 2000-03-28 | Emc Corporation | Secure transmission using an ordinarily insecure network communication protocol such as SNMP |
US6119171A (en) * | 1998-01-29 | 2000-09-12 | Ip Dynamics, Inc. | Domain name routing |
US6292472B1 (en) * | 1998-10-22 | 2001-09-18 | Alcatel | Reduced polling in an SNMPv1-managed network |
US6247062B1 (en) * | 1999-02-01 | 2001-06-12 | Cisco Technology, Inc. | Method and apparatus for routing responses for protocol with no station address to multiple hosts |
AU2001266601A1 (en) * | 2000-05-23 | 2001-12-03 | Ntechra, Inc. | Messaging based proxy application management |
JP3760767B2 (ja) * | 2000-12-21 | 2006-03-29 | 株式会社日立製作所 | ネットワーク管理装置及びネットワーク管理方法 |
GB0112017D0 (en) * | 2001-05-17 | 2001-07-11 | Koninkl Philips Electronics Nv | Wireless master-slave distributed communications network |
US20030210699A1 (en) * | 2002-05-08 | 2003-11-13 | Adc Dsl Systems, Inc. | Extending a network management protocol to network nodes without IP address allocations |
US20050105508A1 (en) * | 2003-11-14 | 2005-05-19 | Innomedia Pte Ltd. | System for management of Internet telephony equipment deployed behind firewalls |
-
2004
- 2004-07-22 CN CNB2004100548239A patent/CN100454828C/zh active Active
-
2005
- 2005-07-20 AT AT05766920T patent/ATE443388T1/de not_active IP Right Cessation
- 2005-07-20 US US11/570,292 patent/US20080270584A1/en not_active Abandoned
- 2005-07-20 EP EP05766920A patent/EP1770906B1/en active Active
- 2005-07-20 DE DE602005016682T patent/DE602005016682D1/de active Active
- 2005-07-20 WO PCT/CN2005/001076 patent/WO2006007789A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5678006A (en) * | 1995-04-27 | 1997-10-14 | Cisco Systems, Inc. | Network switch having network management agent functions distributed among multiple trunk and service modules |
US6725264B1 (en) | 2000-02-17 | 2004-04-20 | Cisco Technology, Inc. | Apparatus and method for redirection of network management messages in a cluster of network devices |
US20020188708A1 (en) * | 2001-06-11 | 2002-12-12 | Hiroko Takahashi | Network management method and apparatus |
CN1510865A (zh) | 2002-12-24 | 2004-07-07 | 深圳市中兴通讯股份有限公司 | 一种网管网关的实现方法 |
Also Published As
Publication number | Publication date |
---|---|
EP1770906A1 (en) | 2007-04-04 |
EP1770906B1 (en) | 2009-09-16 |
US20080270584A1 (en) | 2008-10-30 |
EP1770906A4 (en) | 2007-10-10 |
ATE443388T1 (de) | 2009-10-15 |
CN1725701A (zh) | 2006-01-25 |
CN100454828C (zh) | 2009-01-21 |
DE602005016682D1 (de) | 2009-10-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2006007789A1 (fr) | Procede pour mettre en oeuvre une gestion de terminaux dans un dispositif reseau | |
US7515542B2 (en) | Broadband access note with a virtual maintenance end point | |
US7889754B2 (en) | Address resolution mechanism for ethernet maintenance endpoints | |
EP2012502B1 (en) | Method for managing user side device through nat gateway | |
US20050105508A1 (en) | System for management of Internet telephony equipment deployed behind firewalls | |
JPH08508376A (ja) | Lan領域用汎用管理オブジェクト・モデル | |
CN113411215B (zh) | 基于opc ua的时间敏感网络集中用户配置方法及系统 | |
WO2014118622A1 (en) | Method of managing zigbee network in the internet of things | |
EP2248328B1 (en) | Bridge port mac address discovery mechanism in ethernet networks | |
WO2019223534A1 (zh) | 一种转发表项的监测方法及装置 | |
EP2218214A1 (en) | Network location service | |
KR20110046837A (ko) | 데이터 배포 서비스 기반의 네트워크 관제 방법 | |
CN101562616B (zh) | 用户驻地网关管理系统及方法 | |
CA2550323A1 (en) | Method and system for improved management of a communication network by extending the simple network management protocol | |
CN100477599C (zh) | 一种针对网络设备的网络管理方法 | |
KR101206159B1 (ko) | 사설 ip망을 가지는 스마트 그리드 통신망 관리 시스템 및 관리 방법 | |
WO2008151559A1 (fr) | Procédé, système et appareil pour sélectionner une passerelle de médias virtuels | |
TWI296882B (zh) | ||
JP3926653B2 (ja) | 通信ネットワークにおけるセッション設定方法及びその通信システム並びにプログラム | |
JPH10336228A (ja) | 中継装置及びネットワーク管理装置 | |
KR100464909B1 (ko) | Snmp를 사용하는 ip 망 및 그 망 관리 방법 | |
KR20050048994A (ko) | Dhcp 릴레이 에이전트 옵션 82를 이용하는가입자망에서의 가입자 관리 방법 | |
KR20030026743A (ko) | 정적 테이블 객체의 검색방법 | |
Murray et al. | SNMP: simplified | |
US8046445B2 (en) | Methods and systems for managing network elements |
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 KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM 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 LV 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: 11570292 Country of ref document: US Ref document number: 2005766920 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWP | Wipo information: published in national office |
Ref document number: 2005766920 Country of ref document: EP |