WO2005018189A1 - Procede d'analyse de demande de l'utilisateur - Google Patents
Procede d'analyse de demande de l'utilisateur Download PDFInfo
- Publication number
- WO2005018189A1 WO2005018189A1 PCT/CN2004/000527 CN2004000527W WO2005018189A1 WO 2005018189 A1 WO2005018189 A1 WO 2005018189A1 CN 2004000527 W CN2004000527 W CN 2004000527W WO 2005018189 A1 WO2005018189 A1 WO 2005018189A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- request
- user
- address
- content
- dns
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0227—Filtering policies
- H04L63/0236—Filtering by address, protocol, port number or service, e.g. IP-address or URL
-
- 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/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- 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/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
Definitions
- the present invention relates to data analysis technology, and in particular to a method for analyzing user requests. Background of the invention
- CDN Content delivery network
- QoS quality of service
- a CDN generally includes three types of devices: an edge server (ES) distributed at the edge of the network, a central content distribution device that delivers content to the edge server, and a user request scheduling system.
- the principle of the CDN technology is: In the existing Internet network, the content of the website is pushed from the backbone of the network to the "edge" of the network closest to the user, that is, the CDN can advance the information of the content provider (ICP) site in advance. Publishing to network edge devices, such as pre-publishing to ES, enables users to get a quick response on the nearest edge device when visiting the site, thereby reducing transmission delay, network jitter, and other factors that affect the effect, providing users with Order and high-quality services, so that users can get the information they need from the place closest to the user as quickly as possible.
- the CDN technology has greatly eased the congestion of the Internet, enabling the website to provide more content services with huge data traffic such as video programs and song on demand. At the same time, the reliability of various services such as online transactions and online banking is also available. Effective protection.
- the function of the user request scheduling system is: When receiving a user's request for content, the user requests the scheduling system to select the most appropriate one among the edge servers distributed at the edge of the network, and then let the The server provides content to the user.
- the information transmitted by the user includes the user's network information and the user's Content request information, where the network information includes the source IP address, destination IP address, port used by the service requested by the user, etc., and the request information for content is located by uniform resources
- One method is to resolve the user's request to the third layer of the network protocol, that is, to identify only the user's network information, and use the domain name resolution system (DNS) to obtain the user's IP address.
- DNS domain name resolution system
- the user's IP address according to certain rules, For example, a suitable edge server is found by polling.
- this method can only obtain the user's network information, and the obtained information is relatively limited, which will bring some problems to the subsequent distribution of the edge server, such as: There is no content requested by the user on the distributed edge server.
- Another solution is to split the user request into content, which is to parse the URL string.
- content which is to parse the URL string.
- the granularity of this decomposition generally depends on the service being launched. For example, when the user wants to launch an on-demand service, after the user request is processed, the user will be in a state of watching the program, the access request is small, and the user requests the processing system processing capacity. It is possible to process up to seven layers, thereby more effectively scheduling user requests between various servers; and when users want to access Web content, because there are many access requests, if they are decomposed to seven layers, it will inevitably increase the user request scheduling system. burden.
- the main object of the present invention is to provide a method for analyzing user requests, which can accurately locate the content and can cope with a large amount of access.
- the present invention adopts a composite method to resolve user requests.
- DNS analyzes user requests at the IP layer, and then a request redirection system performs content analysis.
- the analysis method consists of the following steps:
- the DNS After receiving the user request from the user terminal that needs to be resolved, the DNS first resolves the user request to the network layer to obtain the IP address of the user terminal. At the same time, the DNS assigns the user request to the selected request redirection system.
- the selected request redirection system performs content analysis on the received user request to obtain the content requested by the user terminal;
- the selected request redirection system locates the user request to a server that can provide the content required by the user according to the request content parsed in step B.
- the method further includes: the DNS returns the IP address of the selected request redirection system to the user terminal; and the user terminal sends the selected request to the selected request according to the returned IP address.
- the redirect system sends a user request that needs to be resolved.
- the method further includes: the selected request redirection system returns the IP address of the located server to the user terminal, and the user terminal accesses the located server according to the IP address returned by the request redirection system, and the server provides the user to the user The terminal provides the requested content.
- the method further includes: the DNS selects a request redirection system to be allocated by the current user request in a polling manner. Then, the selection of the request redirection system further includes:
- the IP The address record includes the domain name and the IP address of the request redirection system corresponding to the domain name; a2. According to the analysis result, find all records in the database that are the same as the current user's request for the domain name, and sequentially take one IP address record;
- step a3 Determine whether the identification variable X corresponding to the retrieved record is reset, and if so, return the IP address of the request redirection system in the record to the user terminal, set the identification variable X corresponding to the record, and end the selection Fixed flow; otherwise, perform step a4;
- step a4 Determine whether there are any records. If so, select the next record in sequence and return to step a3; otherwise, reset the identification variable X corresponding to all IP address records found in step a2, and then return to step a3.
- the number of DNS and request redirection systems is not determined, and may be one or more.
- the DNS can also directly locate the user's request to a server that can provide Web content, thereby reducing the pressure on the request redirection system.
- the method of the present invention is used to resolve user requests.
- DNS is only used to resolve domain names.
- Some large-granular request decompositions can be performed.
- User requests are allocated to each request redirection system in a certain manner, such as by polling.
- User requests are parsed into content by each request redirection system. In this way, the customer traffic is balanced to a certain extent through DNS, and the customer visits on each request redirection system are not very large, and they are feasible for content-level identification. Therefore, this composite method for analyzing user requests protects existing equipment investment and is also suitable for hierarchical networking. Due to different processing for different services, web content requests are diverted in advance, which ensures the stability of the system and the accuracy of positioning.
- FIG. 1 is a schematic diagram of a CDN network structure
- 2 is a schematic diagram of a simple principle of the technical solution of the present invention
- FIG. 3 is a schematic flowchart of an operation of an embodiment of the present invention.
- FIG. 4 is a schematic flow chart of the operation of DNS assigning a user request to a request redirection system according to an embodiment of the present invention.
- the core idea of the present invention is: combine three-layer analysis with seven-layer analysis, firstly distribute user requests to different request redirection systems through three-layer analysis, and then the corresponding request redirection system will further receive the user requests Parsing to content means that the request redirection system completes seven-layer parsing, and finally locates the user request to a device that can provide content services to it according to the parsing result.
- the DNS described in the method of the present invention is also called redirect DNS to distinguish it from the local DNS (LDNS).
- the request redirection system (Redirector) is equivalent to a The user who identified the content requested to call the system.
- DNS is connected to multiple request redirection systems at the same time, and each user request is allocated by DNS to different request redirection systems for content resolution.
- FIG. 3 a typical workflow for analyzing user requests by using the method of the present invention is shown in FIG. 3 and includes the following steps:
- Step 1 The user sends a user request to the user terminal to access a certain content.
- Step 2 The user terminal requests local DNS (LDNS) to perform domain name resolution on the received user request.
- LDNS local DNS
- Step 3 After receiving the user request from the user terminal, the local DNS sends the user request to the redirect DNS, and requests domain name resolution from the redirect DNS.
- Step 4 The redirect DNS resolves the user request to the network layer, obtains the user's IP address, destination IP address, and other information, and then determines a redirector to be allocated by the current user request according to the polling rule.
- an IP binding method can also be used. IP addresses in a certain range are bound to a redirector. After redirecting DNS to resolve the user's IP address, you only need to determine the range of the IP address to further determine the current range. The user requests the Redirector to be assigned.
- Step 5 Redirection DNS returns the assigned Redirector IP address to the user terminal.
- Step 6 The user terminal accesses the assigned Redirector according to the IP address of the Redirector returned in Step 5, and sends a user request containing the access content to the assigned Redirector.
- Step 7 The Redirector analyzes the content requested by the user, and detects the adjacent edge server based on the analysis result, that is, the content the user wants to access.
- the detection of the edge server generally refers to: detecting the proximity of the ES to the user, the presence or absence of user-required content on the ES, or the busy / busy status of the ES.
- the purpose of the detection is to access the content according to the resolved user. Find out which edge servers meet the requirements, that is, they can provide the corresponding content, and at the same time obtain information such as the distance between these edge servers and users and their own busy status. Among them, the detection is performed by using the existing operation means.
- Step 8 The Redirector redirects the user's access to a suitable edge server according to the detection result and a certain scheduling policy, that is, selects an optimal edge server, and returns the IP address of the selected edge server to the user terminal.
- the certain scheduling strategy refers to selecting an optimal edge server according to the load status of the edge server, an optimal route, and the like.
- edge servers A, B, and C There are three edge servers A, B, and C that can provide the required information to the current user. Currently, edge server A is the most idle, so select edge server A.
- Step 9 The user terminal accesses the selected edge server according to the obtained IP address of the edge server.
- Step 10 The edge server initiates authorization verification of the current user to the user management system through a centralized authentication and forwarding mechanism, such as an authentication and authorization server, and the user management system returns the authentication result to the edge server through the authentication and forwarding mechanism.
- a centralized authentication and forwarding mechanism such as an authentication and authorization server
- Step 11 If the authentication is passed, the edge server provides content services to the current user; otherwise, the current user is denied access.
- the web content access request is distributed in advance.
- the specific method is: DNS resolves the current user request to the network. After the layer, it is determined whether the content that the user needs to access is Web content. If it is, the user request may be directly located on a server that can provide Web content. If not, the current user request is allocated to the request redirection system.
- step 4 the redirecting DNS allocates user requests to the redirector in a polling manner.
- the process shown in FIG. 4 may be specifically adopted, including the following steps:
- Step 401 There are multiple IP address records in the redirected DNS database, and each record consists of a domain name and the IP address of the Redirector corresponding to the domain name.
- resetting the identification variable indicates that the corresponding Redirector is not currently allocated
- setting the identification variable indicates that the corresponding Redirector is currently allocated.
- Step 402 After redirecting the DNS to obtain a user request to be resolved from the local DNS, first resolve the user request to the network layer, and obtain network information such as the user's IP address and destination IP address corresponding to the user request.
- Step 403 further obtain the domain name of the user according to the IP address of the user in the analysis result,
- the redirection DNS looks in its own database for the same IP address record as the user's domain name, and finds all records with the same user domain name.
- the IP address in each record is the IP address of a redirector.
- Steps 404 to 405 The redirected DNS takes a record in order, determines whether the identification variable X corresponding to the record is reset, and if so, returns the IP address in the record to the user, and indicates the identification of the parsing status in the record. Set the variable X, return to step 402, and wait for the next user request; if the identification quantity X corresponding to the record is set, then take the next record in sequence until a record with the identification variable X is reset is found.
- the setting described here may be to set the value of the identification variable X to one.
- step 403 If the identification variables X corresponding to all the IP address records found in step 403 are set, that is, no redirector in an IP address record can be assigned, all the identification variables X corresponding to all the IP address records found in step 403 are set. Reset again and return to step 404.
- Steps 401 to 405 show that a request redirection system is selected in a polling manner.
- the DNS may also use other methods to balance the selection of the request redirection system.
- the method of the present invention enables the ICP website not to redirect the request message for the user to access the streaming media content.
- the method of the present invention implements the scheduling of user requests according to the content, which improves the direct access of users. Hit rate for specific content. Because of content-based scheduling, if all edge servers are divided into logical groups, multiple edge servers in a logical group need not all cache certain content, thereby increasing the total capacity of the edge server's cached content and optimizing memory characteristics. And one content only needs to be sent (PUSH) —once to an edge server, the total number of PUSH is reduced, which reduces the network load.
- PUSH PUSH
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Electrically Operated Instructional Devices (AREA)
- Information Transfer Between Computers (AREA)
- Measuring Pulse, Heart Rate, Blood Pressure Or Blood Flow (AREA)
- Computer And Data Communications (AREA)
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE602004008483T DE602004008483T2 (de) | 2003-08-14 | 2004-05-24 | Analyseverfahren für benutzeranforderungen |
EP04734497A EP1655919B1 (en) | 2003-08-14 | 2004-05-24 | Analysis method for user request |
BRPI0413527-0A BRPI0413527B1 (pt) | 2003-08-14 | 2004-05-24 | Method for analyzing user request |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN03153289.6 | 2003-08-14 | ||
CNB031532896A CN100346324C (zh) | 2003-08-14 | 2003-08-14 | 一种对用户请求的解析方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005018189A1 true WO2005018189A1 (fr) | 2005-02-24 |
Family
ID=34156668
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2004/000527 WO2005018189A1 (fr) | 2003-08-14 | 2004-05-24 | Procede d'analyse de demande de l'utilisateur |
Country Status (8)
Country | Link |
---|---|
EP (1) | EP1655919B1 (zh) |
CN (1) | CN100346324C (zh) |
AT (1) | ATE371331T1 (zh) |
BR (1) | BRPI0413527B1 (zh) |
DE (1) | DE602004008483T2 (zh) |
ES (1) | ES2293257T3 (zh) |
HK (1) | HK1073707A1 (zh) |
WO (1) | WO2005018189A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102970384A (zh) * | 2012-11-13 | 2013-03-13 | 北京奇虎科技有限公司 | 代理服务器和通信系统 |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100576846C (zh) * | 2005-05-11 | 2009-12-30 | 中国科学院计算技术研究所 | 多协议域名解析服务的服务代理方法 |
CN1870636A (zh) | 2005-11-10 | 2006-11-29 | 华为技术有限公司 | 一种客户端重定向的方法和系统 |
CN1317876C (zh) * | 2006-04-10 | 2007-05-23 | 王立俊 | 一种服务器端域名解析错误控制方法及系统 |
CN101242422B (zh) * | 2007-02-06 | 2011-01-26 | 中国电信股份有限公司 | 适应多业务融合的内容分发网络系统和方法 |
CN101494659B (zh) * | 2008-01-24 | 2012-11-07 | 中国移动通信集团公司 | 选取会话控制装置的方法以及相关设备 |
CN101378494B (zh) * | 2008-10-07 | 2011-04-20 | 中兴通讯股份有限公司 | 一种实现互联网电视媒体交互的系统及方法 |
CN101599816B (zh) * | 2009-05-05 | 2012-04-18 | 北京易路联动技术有限公司 | 网络集中服务管理的通信消息反馈方法及系统 |
CN101931663B (zh) * | 2010-08-28 | 2014-06-11 | 中兴通讯股份有限公司 | 一种可动态设置域名服务器的方法及无线通信终端 |
CN103166985B (zh) * | 2011-12-09 | 2018-02-27 | 上海盛大网络发展有限公司 | 一种全局负载均衡调度方法、数据传输方法、装置及系统 |
CN102546774A (zh) * | 2011-12-27 | 2012-07-04 | 厦门市美亚柏科信息股份有限公司 | 一种二次重定向的cdn路由方法及系统 |
CN102932473B (zh) * | 2012-11-13 | 2016-05-11 | 北京奇虎科技有限公司 | 跨运营商网络访问网络内容的方法 |
WO2014075505A1 (zh) * | 2012-11-13 | 2014-05-22 | 北京奇虎科技有限公司 | 跨运营商网络访问网络内容的方法、代理服务器和通信系统 |
US9680842B2 (en) | 2013-08-09 | 2017-06-13 | Verisign, Inc. | Detecting co-occurrence patterns in DNS |
CN103763209A (zh) * | 2014-01-03 | 2014-04-30 | 上海聚力传媒技术有限公司 | 一种cdn服务器的调度方法与装置 |
CN103812936A (zh) * | 2014-01-28 | 2014-05-21 | 张孝明 | 一种利用路由器推送广告的方法及装置 |
CN103825975B (zh) * | 2014-02-26 | 2018-03-13 | 北京六间房科技有限公司 | Cdn节点分配服务器及系统 |
CN106506633B (zh) * | 2016-11-03 | 2019-05-24 | 中国联合网络通信集团有限公司 | 一种业务分流方法、设备及系统 |
CN107071091B (zh) * | 2017-05-26 | 2019-03-12 | 无锡华云数据技术服务有限公司 | 一种优化dns域名解析的实现方法 |
CN110730212A (zh) * | 2019-09-20 | 2020-01-24 | 中国联合网络通信集团有限公司 | 一种数据处理方法及装置 |
CN111901396B (zh) | 2020-07-08 | 2021-08-06 | 厦门网宿有限公司 | 一种资源请求响应方法、重定向服务器及决策分发服务器 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6182148B1 (en) * | 1999-03-18 | 2001-01-30 | Walid, Inc. | Method and system for internationalizing domain names |
WO2001095144A1 (en) * | 2000-06-07 | 2001-12-13 | Spiral Communications Pte Ltd | A method of resolving a non-latin character url |
CN1430381A (zh) * | 2002-12-27 | 2003-07-16 | 北京明瑞智环科技有限公司 | 网络语音网守(gk)使用非静态ip地址技术 |
CN1435786A (zh) * | 2002-06-28 | 2003-08-13 | 华为技术有限公司 | 一种简易访问网络运营商门户网站的方法 |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AU2001251644A1 (en) * | 2000-04-17 | 2001-10-30 | Circadence Corporation | Conductor gateway buffer prioritization |
WO2002005613A2 (de) * | 2000-07-17 | 2002-01-24 | Stoba Ag | Bolzenplombe |
US20030061304A1 (en) * | 2001-09-10 | 2003-03-27 | Tenereillo Peter A. | Method and apparatus for discovering client proximity using in-line translations |
CN1152310C (zh) * | 2002-04-28 | 2004-06-02 | 中国科学院计算机网络信息中心 | 在计算机网络资源中定位中文资源的智能寻址方法及其装置 |
-
2003
- 2003-08-14 CN CNB031532896A patent/CN100346324C/zh not_active Expired - Lifetime
-
2004
- 2004-05-24 ES ES04734497T patent/ES2293257T3/es not_active Expired - Lifetime
- 2004-05-24 EP EP04734497A patent/EP1655919B1/en not_active Expired - Lifetime
- 2004-05-24 DE DE602004008483T patent/DE602004008483T2/de not_active Expired - Lifetime
- 2004-05-24 WO PCT/CN2004/000527 patent/WO2005018189A1/zh active IP Right Grant
- 2004-05-24 BR BRPI0413527-0A patent/BRPI0413527B1/pt active IP Right Grant
- 2004-05-24 AT AT04734497T patent/ATE371331T1/de not_active IP Right Cessation
-
2005
- 2005-07-22 HK HK05106224A patent/HK1073707A1/xx not_active IP Right Cessation
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6182148B1 (en) * | 1999-03-18 | 2001-01-30 | Walid, Inc. | Method and system for internationalizing domain names |
WO2001095144A1 (en) * | 2000-06-07 | 2001-12-13 | Spiral Communications Pte Ltd | A method of resolving a non-latin character url |
CN1435786A (zh) * | 2002-06-28 | 2003-08-13 | 华为技术有限公司 | 一种简易访问网络运营商门户网站的方法 |
CN1430381A (zh) * | 2002-12-27 | 2003-07-16 | 北京明瑞智环科技有限公司 | 网络语音网守(gk)使用非静态ip地址技术 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102970384A (zh) * | 2012-11-13 | 2013-03-13 | 北京奇虎科技有限公司 | 代理服务器和通信系统 |
CN102970384B (zh) * | 2012-11-13 | 2016-06-01 | 北京奇虎科技有限公司 | 代理服务器和通信系统 |
Also Published As
Publication number | Publication date |
---|---|
CN100346324C (zh) | 2007-10-31 |
EP1655919B1 (en) | 2007-08-22 |
ATE371331T1 (de) | 2007-09-15 |
ES2293257T3 (es) | 2008-03-16 |
DE602004008483T2 (de) | 2008-05-15 |
HK1073707A1 (en) | 2005-10-14 |
BRPI0413527B1 (pt) | 2018-01-02 |
DE602004008483D1 (de) | 2007-10-04 |
EP1655919A4 (en) | 2006-08-30 |
BRPI0413527A (pt) | 2006-10-10 |
CN1581114A (zh) | 2005-02-16 |
EP1655919A1 (en) | 2006-05-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2005018189A1 (fr) | Procede d'analyse de demande de l'utilisateur | |
US11863417B2 (en) | Routing mode and point-of-presence selection service | |
US10116584B2 (en) | Managing content delivery network service providers | |
US9800539B2 (en) | Request routing management based on network components | |
US10033627B1 (en) | Routing mode and point-of-presence selection service | |
CA2413952C (en) | Selective routing | |
US7426546B2 (en) | Method for selecting an edge server computer | |
US8239530B2 (en) | Origin server protection service apparatus | |
US6553376B1 (en) | Efficient content server using request redirection | |
US20060271700A1 (en) | Record medium with a load distribution program recorded thereon, load distribution method, and load distribution apparatus | |
US20020069241A1 (en) | Method and apparatus for client-side proxy selection | |
JP2003223378A (ja) | コンテンツデリバリネットワークサービス方法及びシステム | |
WO2005022825A1 (fr) | Systeme de reseau de remise de contenu en couches et procede de distribution de contenu en couches | |
CA2410850A1 (en) | A qos based content distribution network | |
CN109831647A (zh) | 一种调取监控的方法和装置 | |
CA2410959A1 (en) | Content tracking | |
US9288153B2 (en) | Processing encoded content | |
CA2410863A1 (en) | Client side address routing analysis | |
CA2410866C (en) | Client side deterministic routing and transparent redirection |
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): 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 IT 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: 2004734497 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2004734497 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: PI0413527 Country of ref document: BR |
|
WWG | Wipo information: grant in national office |
Ref document number: 2004734497 Country of ref document: EP |