WO2004001588A2 - A system and method to re-synchronize client devices while refreshing them from a server - Google Patents
A system and method to re-synchronize client devices while refreshing them from a server Download PDFInfo
- Publication number
- WO2004001588A2 WO2004001588A2 PCT/EP2003/006215 EP0306215W WO2004001588A2 WO 2004001588 A2 WO2004001588 A2 WO 2004001588A2 EP 0306215 W EP0306215 W EP 0306215W WO 2004001588 A2 WO2004001588 A2 WO 2004001588A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- server
- client device
- list
- objects
- refresh
- Prior art date
Links
Classifications
-
- 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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/273—Asynchronous replication or reconciliation
-
- 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/2866—Architectures; Arrangements
- H04L67/289—Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
-
- 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
-
- 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
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
Definitions
- the present invention generally relates to consumer electronic devices including computing capabilities and using the services of a server; more particularly, the present invention concerns the operation of refreshing those devices from the server with an updated set of objects.
- a first problem with the operation of refreshing devices from servers is the amount of information to be downloaded. As the information may be refreshed once or more a day (this is the case of stock value information) , the server is not aware of the level of information requested by the device and, in case of reconnection, will send to each client device its own complete information set. This method is acceptable as long as the volume of information downloaded in each device is low in term of transmission time and transmission cost. The constant increase of locally kept data in the devices quickly leads to unmanageable situations. As an example, a 10 Mbyte update will generally require more than half an hour of transmission time for each device, and if the server has 100 K devices to update, it will require a huge and costly pipe to serve the required volume which reaches 1 Terabyte in this case .
- This solution applying to containers is disclosed in the US patent US6148340 assigned to International Business Machines Corporation. It consists in keeping track, at the server side, of the last level of containers downloaded to the devices . To refresh a device with a new level container, the server sends only the containers having been modified since the last downloading. Furthermore, the refresh operation is oriented to on-line client devices because the level of refresh is maintained by the server and is reevaluated at each request of the client device.
- the solution of the prior art reduces efficiently the amount of information downloaded by a web server to the client device during a refresh operation.
- it does not answer the need for re-synchronization of a device which has been re-initialized during the time where it was disconnected.
- the web server knows as being the information stored locally by that client device which is the information it has already downloaded.
- the objects are reached by a method, according to claim 1, for re-synchronizing a client device while refreshing, from a server, objects locally stored by said client device remotely connected through a communicating means to said server which keeps track of deals subscribed by said client device, said method comprising the steps of: reading, in the client device, a list of data comprising an object identifier and a digest identifying an object content stored in the client device local storage; sending from said client device a request for refresh message to said server comprising a client device identifier and the list of read data; reading in the server a list of objects identifiers corresponding to the deals subscribed by said client device identified by the received client device identifier; comparing at said server the list of data received in the request for refresh with a list of data stored by said server comprising an object identifier and a digest identifying the object content which is also stored by said server; sending from the server a refresh answer message to the client device with a list of objects comprising, for the objects corresponding to the deals subscribed by said client device and
- the server adds in the list of objects, the information corresponding to these new objects.
- the server sends in the list of objects an object identifier with the specific code when the corresponding object no more belongs to a deal the client device has subscribed to.
- the client device will cancel in its local storage the object itself and any information referencing this object.
- the method is implemented by a program product operating in the server and a program product operating in the client device .
- the main advantage of the invention is that it applies to widely spread client devices which are often used in disconnection mode.
- Fig. 1 illustrates the environment of the preferred embodiment
- Fig. 2 illustrate the three tables stored on the server side to manage the device objects which are the Subscription_table, the Deal_Object_table and the Object_table;
- Fig. 3 illustrates how are chosen the objects to be updated in the client device
- Fig. 4 shows the format of object lists downloaded to the client device
- Fig. 5 illustrates the subscriber current object table located in the client device before and after refresh
- Fig. 6 is an illustration of the exchange of information between the client device and the web server;
- Fig. 7 is the flow chart of the method of the preferred embodiment to refresh and synchronize the client devices.
- a web server (100) provides services to client devices (110, 120) through a network (130) which could be Internet and which may include mobile communications.
- An Internet client device uses a web browser to ask the send request to the server for accessing information which could be any type of object such as a HTML page or an image file (JPG, GIF etc... ) or an audio file (WAV, MP3 etc... ) , forming what is generally called a web document (150) .
- the server keeps track of the client device identity using for instance for a mobile phone, its IMEI (International Mobile Equipment Identity) .
- the screen phone client devices may send their Internet appliance for identification standardized with ISRF. More generally, all the client devices send an identification similar to a serial number which is a unique identifier.
- the server keeps track also of the service subscribed by the client device and more than that, the client device may be interested in certain information provided by the service and described in its profile.
- the information may be static such as recipes for a cooking information service, or may be refreshed once a day such as newspapers or several time a day such as with the weather sites.
- the server will only send the information which is new compared to the last level previously sent. In Fig. 1, the client device has been disconnected and needs to be refreshed by the web server.
- the client device sends an explicit request for refresh with re-synchronization information it stores locally in the device which will help the server to re-synchronize the client device with the correct level of information needed.
- the web documents (150) are initially stored by the Origin server' (140) which sends them on request to the remote web server (100) providing services to the subscriber client devices (110, 120).
- the remote web server refreshes the client devices only with the updated objects of the web documents.
- the client devices once refreshed, can reconstitute the web documents (150) locally with the refreshed objects according to the preferred embodiment.
- the client devices which are subscribers to the web server information services have communication equipement local storage units to store objects constituting the web documents, at least one processor to re-constitute the web documents, to display them and to send requests for refresh according to the preferred embodiment.
- the server re-synchronizes the devices and refresh them by downloading information.
- the device can receive the information, modify the locally stored objects and locally stored re-synchronizing information.
- the refresh and synchronize method may be implemented as programs executed in the server and in the client device their computing resources.
- Fig.2 illustrates the three tables stored on the server side.
- the client devices are browsing 'Local web pages' composed of objects.
- An object is a piece of data handled as a single entity. It is, for the purpose of the preferred embodiment a unit of refresh.
- the server tables are the Subscription_table (200) , the Deal_Object_table (210) and the Object_table (220) .
- the Subscription_table is for storing the 'deals' uniquely identified by the the Deal_ID, associated with a given client device uniquely identified by the Device_ID.
- Each deal corresponds to a subscription taken on the services offered by the server. With this table, the server is able to retrieve all the deals associated to a given client device.
- the Deal_Object_table stores for each deal identified by the Deal_ID the list of objects associated to this deal and uniquely identified with the Object_ID assigned by the server. This table is used by the server to retrieve all the Object_IDs belonging to the deals associated to a given client device.
- the Object_table is maintained by the server to associate to each Object_ID an Object signature which is a 'digest', a code identifying the content of a' text which is used for security.
- MD5 is a one-way hash giving a reduced representation of the object.
- the MD5 signature allows identification of a large text with a good level of security. Any other 'digest' can be used for the preferred embodiment.
- the server acts as a 'proxy' function getting objects from local or remote 'origin servers'. At each reception by the server of a new object from an origin server, a signature is computed.
- the Object_table contains the last value of the object received and the corresponding computed signature.
- the server stores for each Object ID the computed signature, the object length and the local URI (Universal Resource Identifier) or the remote URL (Universal Resource Locator address) identifying the web address of the Internet or Intranet origin server having provided the web documents containing said objects.
- the address is not used for the refresh and the re-synchronization of the client devices but used by the server to periodically require to the origin servers the last level of the objects.
- Fig. 3 illustrates one example of sets of objects and how the server will choose among all these objects to refresh a client device.
- the set of objects belonging to deals pertaining to a given client device has been defined by reading the Subscription_table (200) and the Deal_Object_table (210) . As an example, it consists for device T01 in Obj2, Objl, Obj3 and Obj4.
- the server learns which objects have been resident in the client device before refresh by the request sent by the client device which will be described in reference to Fig. 6 later in the document.
- These objects form the second set of Fig. 3 comprising: Obj5, Objl, Obj3 and Obj4.
- the server will look at the intersection between the two sets to define the objects which need to be updated for the client device: Objl, Obj3 and Obj4.
- the object 0bj5 is no more part of the deals the client device has subscribed to and the server will request the client device to delete it as well as any information stored in the device and referring to this object.
- the object Obj2 is not an object having been resident in the client device: the server has to refresh the client device with this new object.
- the server has to refresh the client device with the last version of this object if the version resident in the client device has not the same signature.
- the server will know the signature of the objects resident in the client device because the signatures will be included in the request sent by the client device which will be described in reference to Fig. 6 later in the document.
- Fig. 4 illustrates the format of the object list that the server will download to the client device to refresh it.
- the example of Fig. 4 shows n objects from Objl to Objn.
- Each 'Object' of the object list comprises the Object__ID, the Object_Signature which is the last level of signature from the Object_table , the Object length from the Object_table and the Object itself which has been read from the origin server.
- Fig. 5 illustrates the update of the Current Subscriber Object Set table which is maintained in the client device.
- the table comprises the Object_ID and the signature of the Object.
- the Object_ID has been assigned by the server, the signature has been computed by the server and they have both been downloaded in a previous refresh operation.
- the Current Subscriber Object Set table contains the last level received from the server.
- the server Upon a request for refresh sent by the client device the server will select the objects to be downloaded to the client device as illustrated in reference with Fig. 3.
- the client device receives the object list sent by the server the local object versions are updated, the client device updates also the table (with the Object_ID and Signature) accordingly.
- the first table is the previous level before refresh (500) and the second table (510) is the last level after refresh.
- the new level (510) no more includes a reference to Obj5, has introduced a new reference to new object Ob 2 and updated the signature of the only object which has to be changed Obj3 because its signature has changed.
- Fig. 6 illustrates the messages exchanged between the client device and the server.
- the protocol used in the example is HTTP wherein a request is sent using the 'POST' command (600) .
- the posted message follows the refresh request syntax of the preferred embodiment.
- the command is 'Refresh'
- the Terminal_ID is TOl in the example
- the list of Object_ID and associated Signatures are the content of the Current Subscriber Object Set table locally stored in the client device.
- the client device post a request to refresh the objects which are locally stored. The request can be sent once a day for this kind of client devices working while disconnected.
- the server answers this request by reading the client device identification and identifying all the deals corresponding to this client device and all the objects associated to this deals using the two tables the Subscription_table (200) and the Deal_Object__table (210) .
- the server will decide what are the objects candidate to be updated for this client device (320) .
- the server reads, for each object candidate to be refreshed what is the signature.
- the signature stored in the Object_table is the signature computed by the server when it has received and stored the last level of the object from the origin server. If the signature of the Object_table is the same than the signature included in the request from the client device, the server will not send this object in its answer.
- Objl and Obj4 have not a different signature (respectively S12 and S41) and they will not be sent by the server.
- Obj3 locally stored by the client device corresponds to a level identified by the signature S32.
- the level stored has the signature S31 which is different.
- the current level of Obj3 must be sent for refresh to the client device.
- the new Obj2 must be sent and the server must advise that the Ob 5 must be deleted from the client device storage as no more belonging to a deal that the client device has subscribed to .
- the answer (610) from the server is illustrated as well in Fig. 6.
- the server sends a simple message answering the Post message.
- the command is 'Refresh_response' followed by the 'Object_list ' according to the format described in reference to Fig.4.
- Obj3 is sent with the updated signature, S32, the new object length and the object content itself.
- Obj2 is sent with the once computed signature, S21, the object length and the object content itself.
- Ob 5 as stated before is no more part of the deals of the client device, is not refresh and the identification of 0 for the signature and 0 for the object length in the Refresh-response means that this object must be canceled from the local storage of the client device and the record must be deleted from the Current Subscriber Object Set table.
- the Current Subscriber Object Set table is empty and the request is for sending all the objects corresponding to the deals the client device has subscribed to.
- the Refresh command posted by the client device will include no object. This is the way in the preferred embodiment to advise the server that he needs to receive all the last level objects corresponding to all the deals it has subscribed to .
- Fig. 7 is the flowchart of the method for re-synchronizing a client device to be refreshed with a set of objects according to the preferred embodiment .
- Step 700 is performed by the client device which reads the Current Subscriber Object Set table storing the couples (Object_ID, signature) .
- the client devices posts a message for instance, under the Http protocol (710) used in the Internet network, the Post message being the client request to the client-server environment.
- the message comprises the
- the server reads the Subscription_table (200) and the Deal_Ob ect_table
- the server reads the signature of the first object candidate to be updated in the Object_table. If the signature is not the same than in the Request_refresh message from the client device (answer No to test 730) , then, the object is kept (740) for the refresh operation. If the signature is the same (answer Yes to test 730) , the next object is read until there is no more object candidate to be updated (answer yes to test 750), the server prepares the object list. If not (answer No to test 750), the signature of the next object candidate to be updated is checked against the signature received in the
- the server first builds the object list with the objects to be updated (760) .
- the object list comprises for each object the Object_ID, the Object signature, the Object_length read in the Object_table and the
- the server adds the Object_ID, the Object signature, the
- Object_length read in the Object_table and the Object content for the new objects added with a change of deal or a change in a deal (770) .
- the triplet comprising the Object_ID, followed by a specific code to indicate an object to be deleted because of a change of deal or a change in a deal.
- One possibility to specify that one object is to be deleted is to put in the object list the Object_ID, and the zero value for the signature and the object length. Any other identification may be used in conjonction with the Object_ID to notify the client device that the object is to be deleted (770) .
- the server sends the response to the request for refresh (780) using the client-server Http protocol.
- the client device receives the object list and is able to read for each object the Object_ID, the Object signature, the Object_length and read the Object content using the object length to identify the end of object.
- the client device updates the Current Subscriber Object Set table with the Object_ID and the corresponding signature. It deletes the object entries to be deleted and add the new object entries. Then, the content of the object themselves are replaced in its local storage with the last level sent. The server has been refreshed and re-synchronized with the objects it needed.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2004514707A JP2005530258A (en) | 2002-06-20 | 2003-05-13 | System and method for resynchronization while refreshing a client device from a server |
EP03760612A EP1550034A2 (en) | 2002-06-20 | 2003-05-13 | A system and method to re-synchronize client devices while refreshing them from a server |
AU2003246419A AU2003246419A1 (en) | 2002-06-20 | 2003-05-13 | A system and method to re-synchronize client devices while refreshing them from a server |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP02368061.4 | 2002-06-20 | ||
EP02368061 | 2002-06-20 |
Publications (3)
Publication Number | Publication Date |
---|---|
WO2004001588A2 true WO2004001588A2 (en) | 2003-12-31 |
WO2004001588A3 WO2004001588A3 (en) | 2004-08-26 |
WO2004001588A8 WO2004001588A8 (en) | 2005-01-20 |
Family
ID=29797350
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2003/006215 WO2004001588A2 (en) | 2002-06-20 | 2003-05-13 | A system and method to re-synchronize client devices while refreshing them from a server |
Country Status (5)
Country | Link |
---|---|
EP (1) | EP1550034A2 (en) |
JP (1) | JP2005530258A (en) |
CN (1) | CN100342334C (en) |
AU (1) | AU2003246419A1 (en) |
WO (1) | WO2004001588A2 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1851954A2 (en) * | 2005-02-11 | 2007-11-07 | General Instrument Corporation | Automatic content update for a target device |
CN100407623C (en) * | 2005-02-23 | 2008-07-30 | 腾讯科技(深圳)有限公司 | Method and system for user data transaction in communication system |
JPWO2007018202A1 (en) * | 2005-08-08 | 2009-02-19 | 株式会社サイボックステクノロジー | Portable syndicated information distribution system |
WO2010037697A2 (en) * | 2008-09-30 | 2010-04-08 | Frederic Sigal | Method of producing a directory of content |
CN104993932A (en) * | 2015-06-19 | 2015-10-21 | 飞天诚信科技股份有限公司 | Method for improving signature safety |
US9177115B2 (en) | 2007-08-22 | 2015-11-03 | International Business Machines Corporation | Data subscription management system |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100484025C (en) * | 2005-12-30 | 2009-04-29 | 摩托罗拉公司 | Method for synchronizing large object data |
CN101166113B (en) * | 2006-10-19 | 2010-06-16 | 中兴通讯股份有限公司 | Message processing method for link maintenance in O-UNI system |
CN1937536A (en) * | 2006-10-31 | 2007-03-28 | 华为技术有限公司 | Network management topological data synchronous refreshing method and system |
US9063993B2 (en) | 2008-01-31 | 2015-06-23 | Microsoft Technology Licensing, Llc | Coexistence tools for synchronizing properties between on-premises customer locations and remote hosting services |
US8458237B2 (en) * | 2008-03-31 | 2013-06-04 | Sony Corporation | Binding unit manifest file |
CN101252465B (en) * | 2008-04-09 | 2011-05-11 | 杭州华三通信技术有限公司 | Warning data acquisition method and server and client end in system |
CN101252462B (en) * | 2008-04-11 | 2010-09-22 | 杭州华三通信技术有限公司 | Alarming page furbishing method as well as server and client end |
JP5364931B2 (en) * | 2010-04-27 | 2013-12-11 | 株式会社日立製作所 | Computer system and server |
CN104065613B (en) * | 2013-03-18 | 2017-11-21 | 中国移动通信集团内蒙古有限公司 | Synchronous method, system and the device of a kind of off-line operation data of application |
CN109656581A (en) * | 2018-12-21 | 2019-04-19 | 北京城市网邻信息技术有限公司 | A kind of installation kit monitoring method, device, terminal device and storage medium |
CN111367921A (en) * | 2018-12-26 | 2020-07-03 | 北京奇虎科技有限公司 | Data object refreshing method and device |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5491820A (en) * | 1994-11-10 | 1996-02-13 | At&T Corporation | Distributed, intermittently connected, object-oriented database and management system |
US5758355A (en) * | 1996-08-07 | 1998-05-26 | Aurum Software, Inc. | Synchronization of server database with client database using distribution tables |
US6029175A (en) * | 1995-10-26 | 2000-02-22 | Teknowledge Corporation | Automatic retrieval of changed files by a network software agent |
GB2348721A (en) * | 2000-07-15 | 2000-10-11 | Ideagen Software Limited | Automated software or data updating in distributed computing system |
US6263360B1 (en) * | 1998-06-01 | 2001-07-17 | Sri International | System uses filter tree and feed handler for updating objects in a client from a server object list |
-
2003
- 2003-05-13 EP EP03760612A patent/EP1550034A2/en not_active Withdrawn
- 2003-05-13 JP JP2004514707A patent/JP2005530258A/en not_active Withdrawn
- 2003-05-13 CN CNB038111160A patent/CN100342334C/en not_active Expired - Fee Related
- 2003-05-13 AU AU2003246419A patent/AU2003246419A1/en not_active Abandoned
- 2003-05-13 WO PCT/EP2003/006215 patent/WO2004001588A2/en not_active Application Discontinuation
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5491820A (en) * | 1994-11-10 | 1996-02-13 | At&T Corporation | Distributed, intermittently connected, object-oriented database and management system |
US6029175A (en) * | 1995-10-26 | 2000-02-22 | Teknowledge Corporation | Automatic retrieval of changed files by a network software agent |
US5758355A (en) * | 1996-08-07 | 1998-05-26 | Aurum Software, Inc. | Synchronization of server database with client database using distribution tables |
US6263360B1 (en) * | 1998-06-01 | 2001-07-17 | Sri International | System uses filter tree and feed handler for updating objects in a client from a server object list |
GB2348721A (en) * | 2000-07-15 | 2000-10-11 | Ideagen Software Limited | Automated software or data updating in distributed computing system |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1851954A2 (en) * | 2005-02-11 | 2007-11-07 | General Instrument Corporation | Automatic content update for a target device |
EP1851954A4 (en) * | 2005-02-11 | 2009-03-25 | Gen Instrument Corp | Automatic content update for a target device |
CN100407623C (en) * | 2005-02-23 | 2008-07-30 | 腾讯科技(深圳)有限公司 | Method and system for user data transaction in communication system |
JPWO2007018202A1 (en) * | 2005-08-08 | 2009-02-19 | 株式会社サイボックステクノロジー | Portable syndicated information distribution system |
US9177115B2 (en) | 2007-08-22 | 2015-11-03 | International Business Machines Corporation | Data subscription management system |
US9633069B2 (en) | 2007-08-22 | 2017-04-25 | International Business Machines Corporation | Data subscription management system |
US10579588B2 (en) | 2007-08-22 | 2020-03-03 | International Business Machines Corporation | Data subscription management system |
US11580069B2 (en) | 2007-08-22 | 2023-02-14 | Kyndryl, Inc. | Data subscription management system |
WO2010037697A2 (en) * | 2008-09-30 | 2010-04-08 | Frederic Sigal | Method of producing a directory of content |
WO2010037697A3 (en) * | 2008-09-30 | 2010-07-22 | Frederic Sigal | Method of producing a directory of content |
CN104993932A (en) * | 2015-06-19 | 2015-10-21 | 飞天诚信科技股份有限公司 | Method for improving signature safety |
Also Published As
Publication number | Publication date |
---|---|
EP1550034A2 (en) | 2005-07-06 |
AU2003246419A1 (en) | 2004-01-06 |
WO2004001588A3 (en) | 2004-08-26 |
CN1653420A (en) | 2005-08-10 |
AU2003246419A8 (en) | 2004-01-06 |
WO2004001588A8 (en) | 2005-01-20 |
CN100342334C (en) | 2007-10-10 |
JP2005530258A (en) | 2005-10-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8135803B2 (en) | Method, system, and computer program product for offline advertisement servicing and cycling | |
WO2004001588A2 (en) | A system and method to re-synchronize client devices while refreshing them from a server | |
US9594821B2 (en) | Method and apparatus for synchronizing how data is stored in different data stores | |
US7873353B2 (en) | Method and system for accessing applications and data, and for tracking of key indicators on mobile handheld devices | |
US6816944B2 (en) | Apparatus and methods for providing coordinated and personalized application and data management for resource-limited mobile devices | |
US7249197B1 (en) | System, apparatus and method for personalising web content | |
CN100531212C (en) | System and method of consulting device information | |
US7552220B2 (en) | System and method to refresh proxy cache server objects | |
KR100996645B1 (en) | Method and apparatus for enabling synchronizing data in different devices having different capabilities | |
JP2010508581A (en) | Offline execution of web-based applications | |
WO2001057673A1 (en) | Coordinated and personalized application and data management | |
WO2004031986A1 (en) | Method and apparatus for using business rules or user roles for selecting portlets in a web portal | |
US20070192401A1 (en) | System and method for synchronizing syndicated content over multiple locations | |
CN107438084A (en) | Multi-client data synchronization method and apparatus | |
TW437205B (en) | An internet caching system and a method and an arrangement in such a system | |
CN106412054B (en) | Dynamic web addresses are converted to naming method, system and its application of static network address | |
US20060064470A1 (en) | Method, system, and computer program product for improved synchronization efficiency for mobile devices, including database hashing and caching of web access errors | |
WO2002065359A1 (en) | Electronic information management system | |
US20050071754A1 (en) | Pushing information to distributed display screens | |
CN107103001B (en) | Method, device and system for acquiring target front-end resource file based on browser | |
CN113779445A (en) | Page rendering method, device, system, equipment and storage medium | |
CN117411847B (en) | Mail out-link picture transfer method, system and medium | |
CN104780181A (en) | Method of displaying equipment in network and network equipment | |
JPWO2002044905A1 (en) | Session management method for content provision | |
KR20020085996A (en) | Method of Providing a Web Page Using Client Cache Memory |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE 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 NO NZ OM PH PL PT RO RU SC SD SE SG SK SL 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: A2 Designated state(s): GH GM KE LS MW MZ 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 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: 20038111160 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004514707 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2003760612 Country of ref document: EP |
|
CFP | Corrected version of a pamphlet front page | ||
CR1 | Correction of entry in section i |
Free format text: IN PCT GAZETTE 01/2004 UNDER (71) REPLACE "(FOR MC ONLY) INTERNATIONAL BUSINESS MACHINES CORPORATION" BY "(FOR ALL DESIGNATED STATES EXCEPT US) INTERNATIONAL BUSINESS MACHINES CORPORATION"; UNDER (71) REPLACE "(FOR ALL DESIGNATED STATES EXCEPT US) COMPAGNIE IBM FRANCE" BY "(FOR MC ONLY) COMPAGNIE IBM FRANCE" |
|
WWP | Wipo information: published in national office |
Ref document number: 2003760612 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 2003760612 Country of ref document: EP |