WO2005098628A1 - オーバーフロー防止方法、装置、及びプログラム - Google Patents
オーバーフロー防止方法、装置、及びプログラム Download PDFInfo
- Publication number
- WO2005098628A1 WO2005098628A1 PCT/JP2005/005481 JP2005005481W WO2005098628A1 WO 2005098628 A1 WO2005098628 A1 WO 2005098628A1 JP 2005005481 W JP2005005481 W JP 2005005481W WO 2005098628 A1 WO2005098628 A1 WO 2005098628A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- client
- computer
- overflow
- information
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
Definitions
- the present invention relates to an overflow for preventing an overflow of a memory on a client side due to data transmission from a server computer (hereinafter, "server” t) to a client computer (hereinafter, “client” t, u). It relates to a prevention device and the like.
- the in-house server refers to database products such as group airlines such as Lotus Domino of the United States IBM, Microsoft Exchange of the United States Microsoft, DB2 of the United States IBM, and Oracle of the United States Oracle. ing.
- Such clients are roughly classified into two types when focusing on how to connect to the server.
- One is a client of the Connected model. Clients of this model always process while communicating with the server.
- a typical example of the Connected model is that a server is
- the other is a client of the Disconnected model.
- the client of this model performs processing with communication with the server disconnected, and communicates with the server when it is necessary to perform so-called data synchronization that matches data on the client with data on the server (
- Patent Document 1 Japanese Patent Application Laid-Open No. 2000-227889 (second paragraph)
- the present invention transmits data only when it is determined that overflow does not occur. That is, in the overflow prevention method of the present invention, data is transmitted from a server database (hereinafter, referred to as a “server DB” t) held by a server to a client database (hereinafter, referred to as a “client DB”) held by a client.
- server DB server database
- client DB client database
- a step in which the client informs the server of the capacity of the client DB and the conditions for extracting the data of the server DB. Extracting from the server DB the data that matches the extracted conditions, and passing the extracted data from Sano to the client DB if the capacity of the extracted data does not exceed the notified capacity of the client DB.
- the overflow prevention method of the present invention may further include a step of presenting the client with advice information on a change in the condition when the capacity of the extracted data exceeds the notified capacity of the client DB.
- the present invention can be regarded as an overflow prevention device that transmits data only when it is determined that overflow does not occur.
- the overflow prevention device of the present invention prevents overflow of the client DB caused by synchronizing the client DB held by the client with the server DB held by the server.
- a pre-processing unit that extracts data that matches the conditions specified by the client, extracts the data from the server DB, and synchronizes the client DB with the extracted data to determine whether the client DB overflows.
- a synchronization processing unit that performs processing for synchronizing the client DB with the extracted data when the preprocessing unit determines that an overflow of the client DB does not occur.
- the pre-processing section causes an overflow of the client DB
- advice information on the change of the condition is presented to the client.
- the present invention can be regarded as a server having an overflow prevention function.
- the server of the present invention includes a receiving unit that receives, from a client, capacity information of a data storage area of the client and setting information for specifying data to be transmitted to the client, and the receiving unit
- the data to be transmitted to the client is specified based on the received setting information, and the specified data is stored in the data storage area based on the capacity information of the specified data and the capacity information of the data storage area received by the receiving unit.
- a determination unit for determining whether or not an overflow of the data is to be generated, and, when it is determined that the data specified by the determination unit does not cause an overflow! /,
- the specified data is passed to the client.
- a delivery processing unit that processes the information to be processed!
- the advice information presenting unit for generating the advice information on the setting information for preventing the overflow from occurring and presenting it to the client is further provided. May be provided.
- the present invention can also be regarded as a program for causing a computer to realize a predetermined function.
- the first program of the present invention stores, in a computer, information on a capacity of a data storage area of another computer and setting information for specifying data to be transmitted to the other computer from another computer.
- the function to receive and the data to be transmitted to other computers are specified based on the received setting information, and the content of the specified data is specified.
- the second program of the present invention receives, from another computer, capacity information of a data storage area of another computer and setting information for specifying data to be transmitted to another computer. And data to be transmitted to another computer based on the received setting information and the specified data based on the specified data capacity information and the received data storage area capacity information.
- the first set that has at least one new setting information as an element is found, and an overflow of the data storage area is generated from the element of the first set.
- Data to determine the second set by excluding elements corresponding to the setting information specific, to realize the function of presenting at least one of the second set element as advice information.
- the data capacity of the portable information terminal is several hundred kilobytes to at most several megabytes, and it is virtually impossible to store all data in the portable information terminal.
- a function of filtering data on the server may be used.
- the filtering function is a function that narrows down data on the server to data that the client performs data synchronization. For example, in the case of email, the originator, urgency (emergency,
- a filtering function by size can be provided.
- a filtering function based on a period may be provided.
- the first problem is that even if data is narrowed down by the filtering function, it is still impossible to prevent data exceeding the data capacity of the client from being transmitted. As a result, the filtering function must be used to try another aperture method, causing unnecessary communication.
- BR stvle page-break-after: always'> I will.
- the second problem is that when data overflow occurs in the client, it is unknown which data synchronization has succeeded and which data synchronization has not succeeded. The point is that it is unclear how to change the filtering settings so that no problems occur.
- the present invention has been made to solve the above technical problems, and an object of the present invention is to cause overflow of a client-side memory when transmitting data from Sano to a client. It is in doing so. Another purpose is to inform the client of what settings to set when sending data from Sano to the client without causing the client-side memory to overflow.
- the invention's effect is to cause overflow of a client-side memory when transmitting data from Sano to a client. It is in doing so. Another purpose. The invention's effect
- FIG. 1 is a diagram showing an overall configuration of a client / server system to which an embodiment of the present invention is applied.
- FIG. 2 is a block diagram showing a hardware configuration of an overflow prevention device according to an embodiment of the present invention.
- FIG. 3 is a block diagram showing a functional configuration of an overflow prevention device according to an embodiment of the present invention.
- FIG. 4 is a flowchart showing an operation of a servlet according to the embodiment of the present invention.
- FIG. 5 is a flowchart showing an operation of the synchronization adapter according to the embodiment of the present invention.
- FIG. 6 is a flowchart illustrating an operation of an advice information generation unit according to the embodiment of the present invention.
- FIG. 7 is a diagram for specifically explaining the operation of the exemplary embodiment of the present invention.
- the present embodiment includes a client 10, a server 20, a general-purpose data synchronization device 30, a synchronization database (hereinafter, referred to as a “synchronization DB”) 40, and an overflow prevention device 50. .
- the client 10 is, for example, a portable information terminal such as a mobile phone, and has a client DB 11 and an extended application program (hereinafter referred to as “extended AP”) 12.
- extended AP extended application program
- the program is a program newly introduced to the client 10 in the embodiment, and may be, for example, a program downloaded and installed on the client 10 by wireless communication.
- the client 10 has a user interface for the user to input various settings to the extended API 2.
- the server 20 is a computer that can be commonly accessed by a plurality of clients 10.
- the server 20 has a server DB 21 and stores data of the same items as the data in the client DB 11.
- the client 10 is a client of the Disconnected model, and it is necessary to perform data synchronization that matches the contents of the client DB 11 with the contents of the server DB 21 at a predetermined timing.
- the power of synchronizing this data Period device 30 As the general-purpose data synchronizer 30, for example, there is a Sync server that synchronizes data using SyncML.
- the synchronization DB 40 is a database that stores data to be synchronized by the general-purpose data synchronizer 30 (hereinafter, referred to as “synchronous data”).
- a power synchronization DB 40 (not shown in FIG. 1) is provided for each of a plurality of clients 10, and synchronization data sent to a certain client 10 is stored in a synchronization DB 40 corresponding to the client 10. That's all.
- the overflow prevention device 50 is a device that is a core part of the present embodiment, and has a function as a synchronization processing unit that performs synchronization processing and a function as a preprocessing unit that performs processing at a stage before the synchronization processing unit.
- the pre-processing unit determines whether or not an overflow of the client DB 11 occurs based on the information received from the extended AP 12, and sets such that the overflow does not occur when it is determined that the overflow occurs. Is notified to the client 10 as advice information.
- the synchronization processing section stores the synchronization data in the synchronization DB 40 when the overflow of the client DB 11 does not occur.
- FIG. 2 is a diagram schematically illustrating an example of a hardware configuration of a computer suitable for use as the overflow prevention device according to the present embodiment.
- the computer shown in FIG. 2 includes a CPU (Central Processing Unit) 501 as an arithmetic means, an M / B (mother board) chipset 502, and a main memory 503 connected to the CPU 501 via a CPU bus.
- Video card 504 and display 510 connected to CPU 501 via B chipset 502 and Accelerated Graphics Port (AGP), and magnetic disk connected to M / B chipset 502 via PCI (Peripheral Component Interconnect) bus Device (HDD) 505, network interface 506, and this PCI bus connected to the M / B chipset 502 via a low-speed bus such as a bridge circuit 507 and an ISAdndustry Standard Architecture) bus.
- PCI Peripheral Component Interconnect
- FIG. 2 merely shows an example of a hardware configuration of a computer that realizes the present embodiment, and various other configurations can be adopted as long as the present embodiment is applicable.
- the video card 504 instead of providing the video card 504, only the video memory may be mounted, and the CPU 501 may be configured to process image data, or the external storage device may be an ATA (AT Attachment), SCSI (Small Computer System Interface), or the like.
- ATA AT Attachment
- SCSI Small Computer System Interface
- a drive of a CD-R (Compact Disc Recordable) or a DVD-RAM (Digital Versatile Disc Random Access Memory) may be provided through the interface.
- the overflow prevention device 50 includes a servlet 51, a synchronization adapter 52, and a shared database (hereinafter, referred to as “shared DB”) 53.
- the servlet 51 and the synchronization adapter 52 are programs that operate on the overflow prevention device 50. That is, the CPU 501 of the overflow prevention device 50 reads these programs stored in, for example, the magnetic disk device 505 into the main memory 503 and executes them. In the execution state, when the functions performed by the servlet 51 are subdivided, the functions can be divided into a receiving unit 54, a data acquiring unit 55, a determining unit 56, an advice information generating unit 57, and a transmitting unit 58. .
- the receiving unit 54 is a unit that receives a synchronization start request including the capacity of the client DB 11 and the filtering setting from the client 10.
- the data acquisition unit 55 is a unit that extracts synchronization data from the server DB 21 based on the filtering setting included in the synchronization start request received by the reception unit 54, and stores the synchronization data in the shared DB 53.
- the determination unit 56 determines whether or not the capacity of the synchronization data exceeds the capacity of the client DB 11 included in the synchronization start request received by the reception unit 54, and if so, calls the advice information generation unit 57 and calls the advice information generation unit 57. If not, it is the part that calls the synchronization adapter 52.
- the advice information generation unit 57 is a unit that generates advice information on how to change the filtering setting so that the capacity of the synchronization data does not exceed the capacity of the client DB 11.
- the transmission section 58 is a section that transmits a synchronization enable notification or an error code / advice information based on the result of the determination by the determination section 56.
- FIG. 4 is a flowchart showing the operation of the servlet 51.
- the receiving unit 54 determines whether a synchronization start request has been received from the client 10 (step 101).
- the synchronization start request includes the capacity of the client DB 11 and the filtering setting.
- the filtering setting is a condition setting when filtering data stored in the server DB 21 to extract synchronous data. If the schedule data is stored in the server DB21, for example, the setting may be made by focusing on "people” such as “Mr. A's schedule”, “Mr. B's schedule”, or “4 days schedule”. , "5 day schedule”, etc., and setting may be made focusing on "day”. In the following, items of interest in filtering, such as “person” and “day” in such settings, will be referred to as “filtering items”, and filtering such as "Mr. A” and “4 days” in such settings. The value specified for an item is called the "item value".
- the receiving unit 54 does not determine that the synchronization start request has been received, it repeats the determination of step 101. However, if it determines that the synchronization start request has been received, the client included in the synchronization start request. The capacity of the DB 11 is transferred to the determination unit 56, and the filtering setting included in the synchronization start request is transferred to the data acquisition unit 55.
- the data acquisition unit 55 acquires data (synchronous data) matching the filtering setting from the server DB 21, stores the synchronous data in the shared DB 53, and transfers the capacity to the determination unit 56 (step 102). ). If the client 10 has already acquired data, the data acquisition unit 55 changes the added and modified data in the server 20 after the acquisition of the data to the data (data) that matches the filtering setting. Synchronous data).
- the data in the client DB 11 and the transmission date / time information of the data to the client 10 are stored in the synchronization DB 40, and the data acquisition unit 55 refers to the information and thereafter, in the server DB 21, Change ⁇ A method of extracting data that has been added can be considered.
- the determination unit 56 compares the capacity of the client DB 11 passed from the reception unit 54 with the capacity of the synchronization data passed from the data acquisition unit 55, and determines that the capacity of the synchronization data is It is determined whether the capacity is less than the capacity of DB11 (step 103).
- the determination unit 56 requests the synchronous adapter 52 to store the synchronous data in the synchronous DB 40 (step 104), and FIG. The processing of the synchronous adapter 52 shown is performed (step 105).
- the transmitting section 58 returns a return value (synchronization notice) indicating that data synchronization is possible to the client 10 (step 106).
- the determination unit 56 requests the advice information generation unit 57 to generate the advice information, and the advice information generation processing shown in FIG. Is performed (step 107). Then, when the advice information is generated, an error code indicating the overflow and the advice information are returned to the client 10 (step 108).
- the synchronization adapter 52 determines whether a synchronization data storage request has been received from the servlet 51 (step 201). If it is determined that the synchronous data storage request has not been received, step 201 is repeated. If it is determined that the synchronous data storage request has been received, the synchronous data is read from the shared DB 53 (step 202), and the synchronous data is read. Is stored in the synchronous DB 40 (step 203).
- advice information generation unit 57 The operation of the advice information generation unit 57 will be described with reference to FIG.
- the advice information generation unit 57 knows in advance how many pieces of data can be stored in the client DB11. This data count can be obtained by dividing the capacity of the client DB 11 by the size of the synchronous data.
- the size of the synchronization data As the size of the synchronization data, the size of the synchronization data extracted in consideration of all the filtering items in the filtering setting is adopted. For example, if the schedule data is stored in the server DB21, and if “day” and “person” are selected as the filtering items in the filtering setting, the size of the schedule data for the specific person on the specific day is determined. Will be employed.
- the advice information generating unit 57 performs the process of FIG. 6 for each filtering item in the filtering setting.
- the advice information generation unit 57 specifies the Prepare at least one combination of the selected item values, and obtain a set I with those combinations as elements (step 301). In selecting at least one combination,
- the amount of data extracted when filtering is performed is calculated (step 302).
- the combinations that exceed the capacity of the data capacity client DB11 are excluded from the elements of the set I, and the set after the exclusion is set as the set II (step 303).
- the advice information generation unit 57 excludes, from the set II, the elements included in the other elements of the set II among the elements of the set II, and sets the set after the exclusion to the set III (step 304). Then, all elements of the set III are passed to the transmitting unit 58 as advice information (step 304).
- the transmitting unit 58 transmits the advice information to the client 10.
- the present invention is applied to an SFA (Sales Force Automation) system, and it is assumed that a client 10 such as a mobile phone browses schedule information of a salesperson managed by a server 20.
- FIG. 7A shows a part of such schedule information. This schedule information was extracted by filtering settings of the schedule information of A, B, and C for 417 days.
- This filtering setting is included in the synchronization start request received by the receiver 54 in step 101. Then, in step 102, the data acquisition unit 55 acquires such information by extracting data matching this filtering setting from the server DB21.
- the number of all the extracted data is “32”, and if the number of data that can be stored in the client DB 11 is “32” or more, the determination in step 103 is “Yes” and the data Data synchronization succeeds.
- step 103 determines whether advice information is generated in step 107, and the generated advice information is transmitted to the client 10 in step 108.
- FIG. 6 when focusing on the filtering item “day” will be described with reference to FIG. 7 (b).
- the item values for the filtering item “day” are "4 days", “5 days”, “6 days”, and “7 days", at step 301, at least one combination of the item values is used as an element. Find the set I that satisfies Because the filtering item “Day” has continuity in the item value,
- a set II is obtained by excluding from the set I those elements whose data capacity exceeds the capacity of the client DB11.
- the forces S are excluded from Set I for "5 days, 6 days, 7 days” and "6 days, 7 days”.
- step 304 the set III is obtained by excluding the elements included in other elements in the set II. Good! ], "5th, 6th”, “4th, 5th”, “6th”, “5th”,
- the elements of the set ⁇ ⁇ ⁇ are “4 days, 5 days, 6 days” and “7 days”. In step 305, these are used as the advice information.
- step 301 Since the item values for the filtering item “person” are "Mr. A”, “Mr. B”, and “Mr. C", in step 301, a set I having at least one combination of the item values as an element is obtained. Since the filtering item “person” has no continuity in its item values, only the rule of ⁇ exclude combinations that have all the item values '' is applied, and the elements of set I are as shown in Fig. 7 (c). , "B, J", “A, J", “A, B”, “> J", "B", "A”.
- each element of the set I is associated with the amount of data extracted when filtering is performed on the element.
- “21 ( 8 + 13)” for “Mr. A and C”
- “19 ( 8 + 11)” for “Mr. A and B”
- “Mr. C” “13” is associated with “11” for “Ms. B” and “8” is associated with “Ms. A”.
- step 303 the element whose calculated data capacity exceeds the capacity of the client DB11 For, set II is obtained by excluding from set I.
- the elements of Set II “B, C” and “A, C” are excluded from Set I as shown in Fig. 7 (c).
- step 304 the set III is obtained by excluding the elements included in other elements in the set II.
- “Ms. B” and “Ms. A” are included in “Ms. A and B”, and as shown in FIG. 7 (c), these elements are excluded from the elements of Set III. I have.
- the elements of the set III are “Mr. A, Ms. B” and “Ms. C”. In step 305, these are used as the advice information.
- the data synchronization range be 4, 5, 6, or 7 days
- advice 2 change of member
- the filtering setting is performed based on the advice information of the filtering setting from the synchronization adapter 52, the next data synchronization always succeeds.
- the data synchronization function is configured so that the conventional one can be used as it is, and there is an advantage that the client-side software can be easily expanded and the amount of change is small.
- the present embodiment is applicable not only to a data synchronization system using the SyncML protocol, but also to general systems (databases such as DB2 and the like) for synchronizing data between a server and a client.
- the present invention is not limited to a system that performs data synchronization, but can be applied to a general system that simply transmits data from the server 20 to the client 10.
- the general-purpose data synchronizer 30 becomes a predetermined function of performing data transmission processing from the server 20 to the client 10
- the synchronous DB 40 becomes an intermediate file for transferring data to be transmitted to the device. .
- the overflow prevention device 50 includes the server DB21. It is also possible to realize all or a part of the function of the force overflow prevention device 50 described as a device physically independent of the server 20 as a function of the server 20.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2004101015 | 2004-03-30 | ||
JP2004-101015 | 2004-03-30 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005098628A1 true WO2005098628A1 (ja) | 2005-10-20 |
Family
ID=35125260
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2005/005481 WO2005098628A1 (ja) | 2004-03-30 | 2005-03-25 | オーバーフロー防止方法、装置、及びプログラム |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2005098628A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023051282A1 (zh) * | 2021-09-29 | 2023-04-06 | 华为技术有限公司 | 一种嵌入向量预取的方法、装置、系统及相关设备 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH09212461A (ja) * | 1996-01-29 | 1997-08-15 | Internatl Business Mach Corp <Ibm> | データ転送制御方法 |
JP2002215409A (ja) * | 2001-01-15 | 2002-08-02 | Nec Corp | ダウンロードシステム、携帯情報端末及びプログラム管理装置 |
JP2003167761A (ja) * | 2001-11-30 | 2003-06-13 | Casio Comput Co Ltd | 情報処理装置 |
-
2005
- 2005-03-25 WO PCT/JP2005/005481 patent/WO2005098628A1/ja active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH09212461A (ja) * | 1996-01-29 | 1997-08-15 | Internatl Business Mach Corp <Ibm> | データ転送制御方法 |
JP2002215409A (ja) * | 2001-01-15 | 2002-08-02 | Nec Corp | ダウンロードシステム、携帯情報端末及びプログラム管理装置 |
JP2003167761A (ja) * | 2001-11-30 | 2003-06-13 | Casio Comput Co Ltd | 情報処理装置 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023051282A1 (zh) * | 2021-09-29 | 2023-04-06 | 华为技术有限公司 | 一种嵌入向量预取的方法、装置、系统及相关设备 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110569311B (zh) | 一种数据库的数据同步方法、设备和计算机存储介质 | |
CN105787077B (zh) | 数据同步方法和装置 | |
CN107798108B (zh) | 一种异步任务查询方法及设备 | |
US20060149794A1 (en) | Database synchronization | |
CN111800462B (zh) | 微服务实例处理方法、装置、计算机设备及存储介质 | |
CN112380227B (zh) | 基于消息队列的数据同步方法、装置、设备及存储介质 | |
US6976038B2 (en) | Method and apparatus for real time creation and modification of a change log for multi-server synchronization | |
CN111026774A (zh) | 数据顺序同步方法、装置、计算机设备及存储介质 | |
EP2674868A1 (en) | Database update notification method | |
CN112311656A (zh) | 消息聚合、展示方法、装置、电子设备和计算机可读介质 | |
US20210103560A1 (en) | Reconciliation of data in a distributed system | |
CN111753019A (zh) | 一种应用于数据仓库的数据分区方法和装置 | |
WO2005098628A1 (ja) | オーバーフロー防止方法、装置、及びプログラム | |
CN109241381B (zh) | 信息匹配方法及装置 | |
CN116028696A (zh) | 资源信息获取方法、装置、电子设备及存储介质 | |
CN110489483A (zh) | 数据同步方法、装置、计算机设备以及存储介质 | |
WO2015068259A1 (ja) | 情報提供方法および装置並びプログラム | |
CN112269741B (zh) | 应用程序兼容性测试方法及相关设备 | |
CN114722003A (zh) | 中心化数据采集方法、装置、设备及存储介质 | |
CN114138804A (zh) | 基于并发处理的缓存数据同步方法、装置、设备及介质 | |
CN114547184A (zh) | 人员信息同步方法、终端设备及存储介质 | |
CN113742376A (zh) | 一种同步数据的方法、第一服务器以及同步数据的系统 | |
WO2016178920A1 (en) | Insertion of unsaved content via content channel | |
CN113761075A (zh) | 切换数据库的方法、装置、设备和计算机可读介质 | |
CN113434754A (zh) | 确定推荐api服务的方法、装置、电子设备和存储介质 |
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 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): 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 | ||
DPEN | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101) | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Country of ref document: DE |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: JP |