US20030028554A1 - Selecting data for synchronization - Google Patents

Selecting data for synchronization Download PDF

Info

Publication number
US20030028554A1
US20030028554A1 US10/170,329 US17032902A US2003028554A1 US 20030028554 A1 US20030028554 A1 US 20030028554A1 US 17032902 A US17032902 A US 17032902A US 2003028554 A1 US2003028554 A1 US 2003028554A1
Authority
US
United States
Prior art keywords
data
synchronization
metadata
data set
data unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/170,329
Other languages
English (en)
Inventor
Oskari Koskimies
Janne Juhola
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Oyj
Original Assignee
Nokia Oyj
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Oyj filed Critical Nokia Oyj
Assigned to NOKIA CORPORATION reassignment NOKIA CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: JUHOLA, JANNE, KOSKIMIES, OSKARI
Priority to US10/309,570 priority Critical patent/US7320011B2/en
Publication of US20030028554A1 publication Critical patent/US20030028554A1/en
Priority to US11/124,658 priority patent/US7483925B2/en
Abandoned legal-status Critical Current

Links

Images

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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G06F16/275—Synchronous replication
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99931—Database or file accessing
    • Y10S707/99932—Access augmentation or optimizing
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99931—Database or file accessing
    • Y10S707/99937—Sorting
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99951—File or database maintenance
    • Y10S707/99952—Coherency, e.g. same view to multiple users
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99951—File or database maintenance
    • Y10S707/99952—Coherency, e.g. same view to multiple users
    • Y10S707/99953—Recoverability
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99951—File or database maintenance
    • Y10S707/99952—Coherency, e.g. same view to multiple users
    • Y10S707/99954—Version management

Definitions

  • the invention relates to selecting data for synchronization.
  • Data synchronization is an operation in which a correspondence is provided between the data collections of at least two databases to the effect that, after the synchronization, the data units of the data collections substantially correspond to each other.
  • database should be understood in its broad sense to relate to any data collection which resides in a data source or data storage and which can be updated using one or more applications.
  • SyncML Synchronization Mark-up Language
  • XML Extensible Mark-up Language
  • a SyncML synchronization protocol employing messages of SyncML format allows the data of any application to be synchronized between any networked terminals.
  • the SyncML synchronization protocol functions both in wireless and in fixed networks and supports a plural number of transmission protocols.
  • SyncML provides both a synchronization protocol and a data representation protocol.
  • the SyncML protocol provides a kind of an adaption possibility in which the server is aware of the restrictions of the terminal. This means that the terminal application does not need to support all fields of a data unit and the amount of data can thus be reduced. Nevertheless, all data units are still fetched to the terminal in this case, too.
  • the invention is based on maintaining in the data system metadata on the relationships between the data units for the purpose of selecting the data to be synchronized.
  • the metadata comprises at least information about relevance relationships between the data units. Relevance is preferably given as a numerical value to express the probability of the user needing a data unit associated with an initial data unit, either directly or through other data units, provided that the initial data unit has been selected.
  • metadata relating to at least one initial data unit of a first data set is retrieved when the first data set is to be synchronized.
  • a second data set comprising at least one data unit that is most relevant to the initial data unit, is selected for synchronization.
  • data units outside the first data set that are most relevant to the initial data units are selected into the second data set.
  • data units outside the first data set that are most relevant to the initial data units are selected into the second data set.
  • only most relevant initial data units from the first data set are selected into the second data set on the basis of the metadata.
  • the solution of the invention provides an advantage in that it allows different relationships between the data units to be taken into account for selecting the second data set to be synchronized. This allows the most relevant data units to be selected for synchronization, and thereby the restricted terminal resources and the limited bandwidth available in wireless data transmission are more efficiently utilized. Since relevant data units can be automatically selected for synchronization, the user does not need to separately define or restrict the data units to be synchronized, which provides improved usability. Since the method can be used in different applications, the relationships between the applications can be taken into account.
  • situation-specific metadata are defined into the data system for different synchronization situations.
  • metadata representing the relationships between the data units is selected.
  • the synchronization situation may be defined for example in the form of profile alternatives available to the user, such as a business trip profile or a holiday trip profile.
  • FIG. 1 is a general view of a data system in which the data of the databases can be synchronized
  • FIG. 2 is a metadata graph
  • FIG. 3 shows a path illustrating the relationships between data units
  • FIG. 4 is a flow diagram illustrating a method according to a preferred embodiment of the invention.
  • FIG. 5 is a flow diagram illustrating a method according to a second preferred embodiment of the invention.
  • FIG. 6 shows an initial data set and adjacent data units associated with it.
  • FIG. 1 illustrates a networked data system, in which data comprised in separate databases DB and terminals TE can be synchronized.
  • the terminal TE is a Client Device, and it is typically a portable computer, PDA device, mobile station or pager, and a synchronization server S is a server, typically serving a plurality of client devices.
  • the synchronization server is not restricted to any particular equipment type; unlike in the example described, a wireless terminal can also function as a synchronization server.
  • FIG. 1 shows two examples, the first one of which comprises terminals TE, databases DB and synchronization servers S connected to a Local Area Network LAN.
  • a terminal TE connected to the network LAN comprises a functionality, such as a network card and software controlling data transmission, for communicating with the devices in the network LAN.
  • the local area network LAN may be a local area network of any type, and the TE may communicate with the server S also over the Internet, typically through a firewall FW.
  • the terminal TE, synchronization server S and databases DB are connected to a wireless network WNW.
  • the terminal TE connected to the network WNW comprises a mobile communications functionality for wireless communication with the network WNW.
  • the wireless network WNW may be any already known wireless network, such as a network supporting a GSM service, a network supporting a GPRS service (General Packet Radio Service), a third generation mobile communications network, such as a UMTS network (Universal Mobile Telecommunications System), a wireless local area network WLAN, or a private network.
  • the server S may also comprise a database DB, although in FIG. 1 the servers S and the databases DB are separate, for the sake of clarity.
  • the terminals TE in wired networks LAN and wireless networks WNW
  • the servers S comprise memory MEM; SMEM, a user interface UI; SUI, I/O means I/O; SI/O for arranging data transmission, and a Central Processing Unit CPU;SCPU comprising one or more processors.
  • Application data that is to be synchronized may be stored in the TE memory MEM (which, from the point of view of synchronization, may be a database to be synchronized), the database DB memory, as well as the server S memory SMEM.
  • the terminal TE and the synchronization server S execute the inventive means, some embodiments of which are shown in FIGS. 4 and 5.
  • the computer programs may be obtained through the network and/or they may be stored in memory means, such as a disc, CD-ROM disc or other external memory means from which they can be loaded into the memory MEM; SMEM. Hardware solutions can also be used.
  • FIG. 2 shows an example of a metadata graph.
  • the nodes in the graph represent the data units and the links depicted by arrows illustrate the relationships between the data units.
  • Each link is assigned at least one value expressing how closely the target node is associated with the source node (the closeness of the relationship).
  • the metadata graph is preferably a directional network.
  • relationships between different types of data units are also preferably determined.
  • a thicker link is used in FIG. 2 to denote a close relationship between the data units, whereas a thinner link is used for a remote relationship.
  • a simple metadata graph could comprise for example an electronic mail data unit linked at least with earlier electronic mail messages on the same subject, with the contact information of the sender or the recipients, and with attachment files, if any, attached to the data unit.
  • Synchronization requires the determining of an initial data set the data units of which are at least to be synchronized.
  • the metadata links allow paths from the initial data set to different data units to be determined.
  • FIG. 3 illustrates paths from initial data unit A to data unit B according to a preferred embodiment of the invention.
  • the relationship between the data units is denoted by relevance and utility. Relevance is a value representing the probability that the user will need a data unit associated with an initial data unit, either directly or through other data units, provided that the initial data unit has been selected.
  • relevance is denoted by ri.
  • Utility expresses the utility of a data unit associated with an initial data unit in the metadata, either directly or over a link through other data units, provided that the initial data unit has been selected. Utility can be thought of as added value obtained by a related data unit, or, on the other hand, as a loss, if the data unit is not available even if it were needed.
  • utility is shown by ui, each link between A and B being provided with a relevance value ri and a utility value ui.
  • the initial data unit A and the related data unit B may be connected by several paths. The different paths represent different reasons why a user who needs the initial data unit A might also need the data unit B.
  • there are two paths p1 and p2 between A and B the paths having the following probabilities:
  • the relevance of B to A is the product of the relevance values assigned to the data units along the path.
  • B's utility to A is determined by the utility value of the last link, i.e. utility through path p1 is u2 and through path p2 it is u5.
  • Gained Utility g is the utility of the data units that the user would really request. Since the user's actions cannot be known in advance, gained utility is a random variable and therefore has a distribution and expected value.
  • the closeness of the relationship between the data units A and B i.e. the importance of data unit B in the selection of data unit A, can be defined by calculating an Expected Gained Utility E(g) value.
  • the gained utility obtained with the data unit B can be determined in the form of the maximum utility of the paths (max(u2,u5). It is also possible to use the utility of an individual path or the combined utilities of different paths as the utility to be gained by data unit selection.
  • the expected gained utility E(g) is preferably calculated by taking into account both paths p1, p2, whereby the following is obtained:
  • E ( g ) u 2* P ( p 1)*(1 ⁇ P ( p 2))+ u 5* P ( p 2)*(1 ⁇ P ( p 1))+max( u 2 ,u 5)* P ( p 1)* P ( p 2).
  • a comparison of the expected gained utility E(g) values of related data units allows the data units comprising the highest values to be selected, in addition to the initial data units, into the selection data set that is to be synchronized.
  • the metadata can be collected by applying a minimum spanning tree method or by means of content analysis, for example. To optimize the processing resources and the time required, deviations from the above calculation method can be made. For example, the number of paths to be taken into consideration can be restricted to only comprise direct links, in which case path length is one. Methods for restricting the number of the paths to be taken into account include Dijkstra's minimum path algorithm and Kruskal's algorithm.
  • FIG. 4 shows a method according to a preferred embodiment of the invention.
  • Metadata comprising relevance and utility information are collected 401 into the system as described above.
  • the metadata can be maintained in the memory MEM, SMEM in data structures, in the application executing the method, or in the application input data. Metadata can also be loaded from network databases, through the Internet, for example.
  • To the metadata is added a new initial data unit that is to be synchronized, the related data units and utility and relevance values illustrating the relationships between them.
  • general rules are used, such as: the relevance value on a link from any electronic mail item to any related word processing file is always 0.7. Consequently, the value 0.7 is always used, irrespective of the electronic mail item or the word processing file, which reduces the space needed for storing the metadata.
  • the metadata is application-specific.
  • new metadata needed for selecting data units for a new application are added for example to application-specific directories in the synchronizing device (TE, S).
  • the metadata determines the relationships between electronic mail data items synchronized by an e-mail application, for example.
  • the metadata from which the relationships between the data units are to be fetched are selected according to the application employed.
  • Application-specific metadata can also be used for influencing the relationships between the data units of different applications by applying different relevance and/or utility values to the links between them. For example, a link from an electronic mail item to a word processing file has a higher relevance value than a link from a calendar entry to a word processing file.
  • Application-specific metadata can also be used in a table format, for example, in which the relevance and/or utility values between different applications are given.
  • Application-specific metadata can be modified according to the purpose of use, and, in addition, different metadata can be used in different situations, i.e. for different synchronization contexts. For example, when a person is leaving for a business trip, the relevance of business card data units is higher than when s/he is leaving for a holiday trip. Metadata can be arranged for use in different synchronization contexts by applying different application- or device-level user profiles, similarly as user profiles arranged at mobile stations. Profile-specific metadata may be stored for the different profiles; it is also possible to modify the metadata or to select the data units to be synchronized on the basis of different criteria in different situations. Typical synchronization contexts include a general context, business trip, holiday trip, reading of electric mail messages and meetings.
  • data is synchronized with the user's terminal TE such that the business cards of those participating in the meeting form the initial data set and they are provided with links of high relevance values to the electronic mail messages last sent by the participants.
  • the user also has the possibility to influence the metadata, for example by adding new links between the data units, or to change the utility or relevance values of the links.
  • a predetermined number of high-level user preferences can be defined, the metadata being automatically determined and modified according to the preferences. This could be illustrated by an example in which the user considers business cards not to be important and thus selects a low priority for them.
  • the synchronization application may therefore set low relevance values for business cards. All preferences related to synchronization can be determined user-specifically, and the appropriate preferences can be selected using the user ID (the preferences can also be stored on an Integrated Circuit (IC) card, for example).
  • IC Integrated Circuit
  • Metadata can be collected and updated 401 by analyzing the contents of the data units. In response to changes in the data unit contents, the relevance and/or utility values of the contents can be changed as well.
  • Metadata updating 401 can be arranged to take place as an automatic monitoring of user actions. This means that a new data unit with its relevance data can be automatically added to the metadata when the user requests for the data unit in question.
  • the frequency of use of the data units can be monitored and the relevance and/or utility values changed automatically on the basis of the monitoring. Relevance values can be changed on the basis of the frequency of use, and utility values on the basis of the duration of use, for example.
  • the monitoring of user actions and automatic collection of metadata can be arranged by means of neural networks, for example.
  • an initial data set is determined 402 .
  • the initial data set is preferably a pre-determined application-specific set.
  • the user may also add data units to or remove them from the initial data set.
  • metadata associated with the initial data units of the initial data set are retrieved 403 , i.e. the links from the initial data units are defined.
  • Metadata can be modified 404 according to application or situation.
  • An application- or situation-specific transform function can be used for weighting different data units differently to provide synchronization profiles such as those referred to above.
  • the transform function refers particularly to application- or situation-specific coefficients for the relevance and utility values of the different data units.
  • the transform function is applied to the links between the data units, and the transformed relevance and utility values are then used at later stages ( 405 ).
  • This embodiment provides an advantage in that the data units can be weighted differently for different purposes and situations, but employing as small memory space as possible.
  • exclusion criterion is path length, which allows data units that are too far away from the initial data set to be excluded.
  • the exclusion method in step 404 allows limit values to be set, whereby expected gained utility values of all data units included in the metadata do not need to be calculated and compared. This speeds up the selection process and reduces the processing capacity needed in the equipment implementing the method.
  • the minimum values applied in the exclusion can also be application-specific, in which case they vary according to the purpose of use.
  • the metadata (and the modification and/or exclusion, if any, of step 404 ) provide related data units associated, one way or another, with the data units of the initial data set.
  • the relevance and utility values denoted by the paths leading to the related data units are preferably used for calculating 405 expected gained utility values E(g) for them.
  • the expected gained utility values obtained for the different data units are compared 406 .
  • the data unit with the highest expected gained utility value is added 407 to the selection data set.
  • the routine checks 408 whether an end criterion determined into the data system in advance is met.
  • the end criterion may be, for example, exceeding the maximum size set for the data to be synchronized; exceeding the maximum number of data units; or the non-attainment of minimum expected gained utility value (i.e. there are no data units left which would exceed the minimum value of expected relevance). If the end criterion is not met, the routine proceeds by adding 407 a new data unit to the selection data set.
  • the selection data set which typically comprises related data units defined according to the initial data set and the end criterion, is synchronized 409 .
  • the changes made to the selection data set since the last synchronization event can be checked and the changed data units, or at least data about the changes, can be sent to the other party involved in the synchronization.
  • only the relevance values can be used for selecting the data units (in the comparison 406 or as an end criterion 408 ).
  • the data selection according to steps 401 - 408 described above can be carried out in one device participating in the synchronization, in some of the devices, or in all of them.
  • the selection data set can be synchronized using any synchronization method.
  • the synchronization may be carried out using a protocol based on the SyncML standard, although the scope of application of the invention is not restricted thereto.
  • a synchronization session is first initialized in step 409 to select the database to be synchronized.
  • a SyncML client device comprises a Sync Client Agent executing the SyncML protocol.
  • the client agent may send the SyncML server (S) a SyncML message (Client Modifications) containing information about the changes made to the selection data set since the last message was sent.
  • the SyncML server comprises a Sync Server Agent, which controls the synchronization, and a Synchronization Engine, and it usually waits for the client's initiative for the synchronization.
  • the SyncML server synchronizes the data, i.e. analyses the changes made to the selection data set and harmonizes the data units (makes the necessary additions, replacements and deletions).
  • the SyncML server then sends the client device a Server Modifications message which comprises the information about the changes made to the selection data set since the last synchronization message from the server S.
  • a Server Modifications message which comprises the information about the changes made to the selection data set since the last synchronization message from the server S.
  • the data to be synchronized can be selected during the initialization of the synchronization session.
  • the TE When the TE has determined the selection data set, it sends the modifications (Client Modifications) that have taken place since the last synchronization session to the synchronization server S.
  • the TE may also send additional requirements relating to the determining of the selection data set, for example that a particular data unit must be included in the set, which the server S must take into account when selecting the selection data set.
  • TE preferences and other data relating to adaptive synchronization may be transmitted in a Meta element and in an EMI field, for example.
  • the S selects ( 402 - 408 ) its selection data set in a similar manner.
  • the server S preferably carries out the selection such that at least the data unit modifications sent by the TE are taken into account.
  • the S informs the terminal TE about the selection data set it has selected prior to the synchronization. This, however, causes increased delay and adds to the amount of data to be transferred.
  • the S harmonizes the data units in the selection data set it has selected on the basis of the modifications sent by the TE and those made into the database (DB) synchronized by the server S.
  • the S sends the modifications (Server Modifications) that have taken place in the selection data set since the last synchronization session to the TE.
  • the TE modifies the data units in its memory MEM.
  • the TE may send information about the initial data set and other preferences, if any, during the initialization to the server S, which selects the selection data set on the basis of the metadata and the initial data set.
  • FIG. 5 shows a method according to a second preferred embodiment of the invention in which the metadata can be used also for excluding data units of the initial data set.
  • Metadata which can be updated in the above described manner and which comprises relevance and utility information, is collected 501 into the system. The relevance and utility values of the data units can be changed, even if the data units concerned were in the initial data set.
  • an initial data set is determined 502 .
  • At least metadata associated with the initial data units of the initial data set are retrieved 503 , i.e. the links between the initial data units are defined.
  • the importance of the initial data units with regard to other initial data units is calculated 504 . This can be achieved experimentally by removing one data unit at a time from the first data set and by determining, on the basis of the metadata, the expected gained utility value to be obtained if a data unit is added. The expected gained utility values calculated for each initial data unit are compared 505 . The initial data unit with the highest expected gained utility value is added 506 to the selection data set. When a new initial data unit is added to the selection data set, the routine checks 507 whether the end criterion determined into the data system in advance is met.
  • the end criterion may be for example the maximum size set for the data to be synchronized, the number of the initial data units, or the non-attainment of the minimum value set for the expected gained utility value. If the end criterion is not met, the routine proceeds by adding 506 the new initial data unit to the selection data set. When the end criterion is met, the initial data units in the selection data set can be synchronized 508 . This allows the least relevant initial data units to be removed from the initial data set.
  • FIG. 5 provides an advantage in that it allows initial data units that have typically been determined in the initial data set on a relatively permanent basis to be placed into an order of relevance and only the most relevant initial data units to be synchronized.
  • the functions shown in FIGS. 4 and 5 can also be combined, in which case the remaining initial data units are considered to provide the initial data set (step 402 ) and thus instead of entering step 508 , the routine may proceed through step 403 to assess the relevance of the data units related to the initial data units.
  • the user's action can be monitored and the metadata updated 501 on the basis of the use of a data unit.
  • the terminal TE may be arranged to monitor the use of audio data files stored in the terminal.
  • an audio data file When an audio data file has been played, it can be marked for removal, added to the initial data set and replaced by a new audio data file in the next synchronization session. This can also be achieved by changing the relevance and/or utility value to indicate that it is relevant to synchronize an audio data file marked for removal by the audio application. Consequently, an embodiment is provided which allows to determine data units to be removed and to replace the data units during the next synchronization by a new data unit of a similar type.
  • Data amount can be used as an end criterion in steps 408 and 507 .
  • the size of the selection data set is always checked after a new data unit has been added.
  • a predetermined size limit is reached, the synchronization of the selection data set may begin.
  • the synchronization is interrupted.
  • the terminal TE may also send the synchronization server S a message when the maximum size limit is exceeded so that the S no longer sends data units for synchronization.
  • the selection data set is selected during the synchronization, unlike in FIGS. 4 and 5.
  • the embodiment's advantages appear in cases where the size of the data units is not known, the calculation of the size of the data units requires a large processing capacity, or the server does not know the memory space available at the terminal.
  • data unit size is also taken into account in the comparison (steps 406 and 505 ).
  • the ratio of the expected gained utility value E(g) (or the gained utility value g) to the data amount can be calculated for the data units.
  • the data unit having the highest E(g) per kilobyte is selected ( 407 , 506 ) into the selection data set. This allows smaller data units to be preferred over larger ones.
  • the comparison must be defined such that a small data unit of low relevance is not preferred over a large data unit of high relevance. This can be accomplished for example by applying a logarithm of data unit size, instead of size, in the comparison.
  • the user interface UI;SUI can also be used for inquiring the user about the need for synchronizing one or more data units (before step 409 or 508 ).
  • This embodiment is useful when large data units are concerned and mainly when the synchronization is to be carried out with a terminal, which has a very limited storage capacity.
  • the above-described embodiments are typically applied at the synchronization server S, which selects the selection data set to be synchronized, and, thereby, has an effect on the amount of data to be sent to the terminal TE, which typically has relatively limited memory resources.
  • the present method can also be used in the terminal TE for selecting a selection data set, the modifications made to the set being informed to the synchronization server S.
  • the number of data units added to the terminal TE by the user is fairly small, and thus all new data units (or other modifications made at the terminal TE) can be easily synchronized.
  • the above solution can also be used to limit the amount of data to be transmitted from the terminal TE for synchronization.
  • server-to-terminal synchronization different values (relevance, utility) are preferably used in the metadata or in other criteria related to the selection of the data units than in terminal-to-server synchronization.
  • the purpose may be to limit the required memory space (for the TE), whereas the aim at the terminal TE may be to save the processing resources needed for the comparison and selection of the data units.
  • An embodiment of the solution of the invention provides various profiles (with different metadata or different exclusion/end criteria) for different transfer situations.
  • Fast synchronization can be determined for expensive transfer links (through public mobile communications networks) to only synchronize particularly important data units.
  • Full synchronization can be carried out in a local area network of a company, for example.
  • FIG. 6 further illustrates the initial data set and the selection data set.
  • the initial data set 60 defined with a dotted line comprises four data units with links that illustrate their relationships with other data units.
  • the circles in FIG. 6 illustrate all data units which according to the metadata links are in some way associated with the initial data set 60 .
  • a dashed line 61 defines the selection data set to be synchronized, obtained by employing the method of the invention. As already described above, one data unit at a time is preferably added to the selection data set 61 , the data units that are closest to the initial data units being typically the most important ones as well. It should be noted that the selection data set 61 does not comprise all the data units of the initial data set, i.e. the method illustrated in FIG. 5 has been used.
  • FIG. 5 the method illustrated in FIG. 5 has been used.
  • FIG. 6 further shows a so-called pre-excluded set, defined with a continuous line 62 .
  • Expected gained utility values have been calculated for the data units in the set 62 , which is selected using the exclusion of step 404 .
  • a data unit with a too low relevance value, for example, has been left outside the set 62 .
  • a reference user data unit which is always included in the initial data set and which has links to other data units, is added to the initial data set 60 .
  • the user data unit itself is not a subject of synchronization, but it defines the data units that are to be taken into account when the selection data set is selected.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (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)
  • Information Transfer Between Computers (AREA)
US10/170,329 2001-06-15 2002-06-12 Selecting data for synchronization Abandoned US20030028554A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US10/309,570 US7320011B2 (en) 2001-06-15 2002-12-04 Selecting data for synchronization and for software configuration
US11/124,658 US7483925B2 (en) 2001-06-15 2005-05-09 Selecting data for synchronization

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FI20011277A FI114417B (fi) 2001-06-15 2001-06-15 Datan valitseminen synkronointia varten
FI20011277 2001-06-15

Related Child Applications (3)

Application Number Title Priority Date Filing Date
US10/309,570 Continuation-In-Part US7320011B2 (en) 2001-06-15 2002-12-04 Selecting data for synchronization and for software configuration
US11/124,658 Continuation US7483925B2 (en) 2001-06-15 2005-05-09 Selecting data for synchronization
US11/124,658 Continuation-In-Part US7483925B2 (en) 2001-06-15 2005-05-09 Selecting data for synchronization

Publications (1)

Publication Number Publication Date
US20030028554A1 true US20030028554A1 (en) 2003-02-06

Family

ID=8561424

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/170,329 Abandoned US20030028554A1 (en) 2001-06-15 2002-06-12 Selecting data for synchronization
US11/124,658 Expired - Lifetime US7483925B2 (en) 2001-06-15 2005-05-09 Selecting data for synchronization

Family Applications After (1)

Application Number Title Priority Date Filing Date
US11/124,658 Expired - Lifetime US7483925B2 (en) 2001-06-15 2005-05-09 Selecting data for synchronization

Country Status (4)

Country Link
US (2) US20030028554A1 (zh)
EP (1) EP1267283A3 (zh)
CN (1) CN100336351C (zh)
FI (1) FI114417B (zh)

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050038863A1 (en) * 2003-07-21 2005-02-17 Richard Onyon Device message management system
US20050102257A1 (en) * 2003-11-07 2005-05-12 Onyon Richard M. Personal information space management system and method
US20050210079A1 (en) * 2004-03-17 2005-09-22 Edlund Stefan B Method for synchronizing documents for disconnected operation
US20060052091A1 (en) * 2004-05-12 2006-03-09 Richard Onyon Advanced contact identification system
US20060074996A1 (en) * 2004-10-05 2006-04-06 International Business Machines Corporation System and method for synchronizing data
US20060248122A1 (en) * 2005-04-27 2006-11-02 Microsoft Corporation Component based infrastructure for sharing files
US20070056043A1 (en) * 2005-05-19 2007-03-08 Richard Onyon Remote cell phone auto destruct
US20080082421A1 (en) * 2004-05-12 2008-04-03 Richard Onyon Monetization of an advanced contact identification system
US20080104277A1 (en) * 2005-10-27 2008-05-01 Huawei Technologies Co., Ltd. Method, system, client and server for implementing data sync
US20080130812A1 (en) * 2006-11-30 2008-06-05 Seoul National University Industry Foundation Data synchronization system
CN100413261C (zh) * 2006-01-04 2008-08-20 华为技术有限公司 数据恢复的方法和系统
US20080201362A1 (en) * 2000-01-26 2008-08-21 Fusionone, Inc. Data transfer and synchronization system
US20080214163A1 (en) * 2007-01-26 2008-09-04 Richard Onyon System for and method of backing up content for use on a mobile device
US20080288484A1 (en) * 2005-09-15 2008-11-20 Motorola, Inc. Distributed User Profile
US20090106110A1 (en) * 2004-02-27 2009-04-23 Liam Stannard Method and system for promoting and transferring licensed content and applications
US7895334B1 (en) 2000-07-19 2011-02-22 Fusionone, Inc. Remote access communication architecture apparatus and method
WO2011067454A1 (en) * 2009-12-01 2011-06-09 Nokia Corporation Methods and apparatuses for relevance calculation
US20110295947A1 (en) * 2010-06-01 2011-12-01 Htc Corporation Communication apparatus and method thereof
US8181111B1 (en) 2007-12-31 2012-05-15 Synchronoss Technologies, Inc. System and method for providing social context to digital activity
US8255006B1 (en) 2009-11-10 2012-08-28 Fusionone, Inc. Event dependent notification system and method
US8442943B2 (en) 2000-01-26 2013-05-14 Synchronoss Technologies, Inc. Data transfer and synchronization between mobile systems using change log
US8943428B2 (en) 2010-11-01 2015-01-27 Synchronoss Technologies, Inc. System for and method of field mapping
US9270664B2 (en) 2002-08-30 2016-02-23 Boss Logic, Llc System and method for secure reciprocal exchange of data
US9542076B1 (en) 2004-05-12 2017-01-10 Synchronoss Technologies, Inc. System for and method of updating a personal profile

Families Citing this family (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7155439B2 (en) * 2001-09-20 2006-12-26 Wellogix, Inc. Modular and customizable process and system for capturing field documentation data in a complex project workflow system
US7356098B2 (en) * 2001-11-14 2008-04-08 Ipwireless, Inc. Method, communication system and communication unit for synchronisation for multi-rate communication
FI114750B (fi) 2002-10-29 2004-12-15 Nokia Corp Datan synkronoiminen
WO2004051509A1 (en) * 2002-12-04 2004-06-17 Nokia Corporation Selecting data for synchronization and for software configuration
US7756825B2 (en) * 2003-07-31 2010-07-13 Microsoft Corporation Synchronization peer participant model
DE10336318A1 (de) * 2003-08-05 2005-03-10 Deutsche Telekom Ag Informationssystem zur Verteilung von Informationen für mobile Endgeräte
US7143117B2 (en) 2003-09-25 2006-11-28 International Business Machines Corporation Method, system, and program for data synchronization by determining whether a first identifier for a portion of data at a first source and a second identifier for a portion of corresponding data at a second source match
US7647256B2 (en) * 2004-01-29 2010-01-12 Novell, Inc. Techniques for establishing and managing a distributed credential store
ES2352558T3 (es) * 2004-03-02 2011-02-21 Divinetworks Ltd. Servidor, procedimiento y sistema para almacenar en memoria cache flujos de datos.
EP1743337A4 (en) * 2004-05-07 2009-03-25 Samsung Electronics Co Ltd METHOD AND APPARATUS FOR SYNCHRONIZING METADATA AND ASSOCIATED STORAGE MEDIUM
KR100561435B1 (ko) * 2004-05-07 2006-03-17 삼성전자주식회사 메타데이터 동기화 방법, 장치 및 그 방법을 수행하기 위한 프로그램이 저장된 저장매체
CN1973508B (zh) * 2004-06-30 2010-09-08 诺基亚公司 数据对象的传送
US20060041893A1 (en) * 2004-08-20 2006-02-23 Microsoft Corporation Extensible device synchronization architecture and user interface
CN1794724A (zh) * 2005-10-27 2006-06-28 华为技术有限公司 在SyncML层实现数据同步的方法
CN1956452B (zh) * 2005-10-27 2012-02-29 华为技术有限公司 一种实现数据同步的方法、系统、客户端及服务器
US20070168535A1 (en) * 2005-12-22 2007-07-19 Ilmo Ikonen System and method for data communication between devices
US7783641B2 (en) * 2006-10-26 2010-08-24 Microsoft Corporation Taxonometric personal digital media organization
US8336097B2 (en) * 2007-10-12 2012-12-18 Electronics And Telecommunications Research Institute Apparatus and method for monitoring and protecting system resources from web browser
WO2009062182A1 (en) 2007-11-09 2009-05-14 Topia Technology Architecture for management of digital files across distributed network
US8103718B2 (en) 2008-07-31 2012-01-24 Microsoft Corporation Content discovery and transfer between mobile communications nodes
US8649276B2 (en) * 2008-07-31 2014-02-11 Microsoft Corporation Content transfer
CN101493826B (zh) * 2008-12-23 2012-12-19 中兴通讯股份有限公司 基于web应用的数据库系统及其数据管理方法
US8327029B1 (en) * 2010-03-12 2012-12-04 The Mathworks, Inc. Unified software construct representing multiple synchronized hardware systems
US20130013558A1 (en) * 2011-07-08 2013-01-10 Belk Andrew T Semantic checks for synchronization: imposing ordinality constraints for relationships via learned ordinality
US9003018B2 (en) * 2011-09-15 2015-04-07 Ca, Inc. System and method for data set synchronization and replication
US9443230B2 (en) 2012-04-30 2016-09-13 At&T Intellectual Property I, L.P. Point-to point data synchronization
US9336226B2 (en) * 2013-01-11 2016-05-10 Commvault Systems, Inc. Criteria-based data synchronization management
US20150052105A1 (en) * 2013-08-16 2015-02-19 Filelize, Inc. Cloud-based synchronization of related file sets
US9798596B2 (en) 2014-02-27 2017-10-24 Commvault Systems, Inc. Automatic alert escalation for an information management system
US9753816B2 (en) 2014-12-05 2017-09-05 Commvault Systems, Inc. Synchronization based on filtered browsing
US9588849B2 (en) 2015-01-20 2017-03-07 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US9952934B2 (en) 2015-01-20 2018-04-24 Commvault Systems, Inc. Synchronizing selected portions of data in a storage management system
US10489423B2 (en) 2016-12-30 2019-11-26 Microsoft Technology Licensing, Llc Most-relevant-first calendar event synchronization
USD896201S1 (en) * 2019-04-04 2020-09-15 Flashbay Electronics Hong Kong Limited Wireless headphones

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7807A (en) * 1850-12-03 Machine fob boring dovetailed mortises
US14378A (en) * 1856-03-04 tilton
US5706509A (en) * 1995-04-28 1998-01-06 Intel Corporation Application independent record level synchronization
US5758355A (en) * 1996-08-07 1998-05-26 Aurum Software, Inc. Synchronization of server database with client database using distribution tables
US5758337A (en) * 1996-08-08 1998-05-26 Microsoft Corporation Database partial replica generation system
US5826261A (en) * 1996-05-10 1998-10-20 Spencer; Graham System and method for querying multiple, distributed databases by selective sharing of local relative significance information for terms related to the query
US5884325A (en) * 1996-10-09 1999-03-16 Oracle Corporation System for synchronizing shared data between computers
US5926816A (en) * 1996-10-09 1999-07-20 Oracle Corporation Database Synchronizer
US6012063A (en) * 1998-03-04 2000-01-04 Starfish Software, Inc. Block file system for minimal incremental data transfer between computing devices
US6052735A (en) * 1997-10-24 2000-04-18 Microsoft Corporation Electronic mail object synchronization between a desktop computer and mobile device
US6212529B1 (en) * 1996-11-13 2001-04-03 Puma Technology, Inc. Synchronization of databases using filters
US20020078075A1 (en) * 2000-12-15 2002-06-20 Colson James C. System, method, and program product for prioritizing synchronizable data

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
IT1282275B1 (it) * 1995-12-06 1998-03-16 Electrolux Zanussi Elettrodome Lavabiancheria con cicli di risciacquo a basso consumo
US5920859A (en) * 1997-02-05 1999-07-06 Idd Enterprises, L.P. Hypertext document retrieval system and method
US6078914A (en) * 1996-12-09 2000-06-20 Open Text Corporation Natural language meta-search system and method
US6195622B1 (en) * 1998-01-15 2001-02-27 Microsoft Corporation Methods and apparatus for building attribute transition probability models for use in pre-fetching resources
US6112203A (en) * 1998-04-09 2000-08-29 Altavista Company Method for ranking documents in a hyperlinked environment using connectivity and selective content analysis
CN1103525C (zh) * 1998-10-06 2003-03-19 英业达股份有限公司 电子邮件数据同步的处理方法和装置
AUPP911799A0 (en) 1999-03-10 1999-04-01 Retriever Communications Mobile application service
US6549896B1 (en) * 2000-04-07 2003-04-15 Nec Usa, Inc. System and method employing random walks for mining web page associations and usage to optimize user-oriented web page refresh and pre-fetch scheduling
US6904454B2 (en) * 2001-03-21 2005-06-07 Nokia Corporation Method and apparatus for content repository with versioning and data modeling
FI113129B (fi) 2001-03-26 2004-02-27 Nokia Corp Sovellusdatan synkronointi tietoliikennejärjestelmässä
US20020143782A1 (en) 2001-03-30 2002-10-03 Intertainer, Inc. Content management system
US6839564B2 (en) 2001-04-25 2005-01-04 Nokia Corporation Synchronization of database data
SE520531C2 (sv) 2001-05-11 2003-07-22 Ericsson Telefon Ab L M Multimediapresentation
US7139757B1 (en) * 2001-12-21 2006-11-21 The Procter & Gamble Company Contextual relevance engine and knowledge delivery system

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7807A (en) * 1850-12-03 Machine fob boring dovetailed mortises
US14378A (en) * 1856-03-04 tilton
US5706509A (en) * 1995-04-28 1998-01-06 Intel Corporation Application independent record level synchronization
US5826261A (en) * 1996-05-10 1998-10-20 Spencer; Graham System and method for querying multiple, distributed databases by selective sharing of local relative significance information for terms related to the query
US5758355A (en) * 1996-08-07 1998-05-26 Aurum Software, Inc. Synchronization of server database with client database using distribution tables
US5758337A (en) * 1996-08-08 1998-05-26 Microsoft Corporation Database partial replica generation system
US5884325A (en) * 1996-10-09 1999-03-16 Oracle Corporation System for synchronizing shared data between computers
US5926816A (en) * 1996-10-09 1999-07-20 Oracle Corporation Database Synchronizer
US6212529B1 (en) * 1996-11-13 2001-04-03 Puma Technology, Inc. Synchronization of databases using filters
US6052735A (en) * 1997-10-24 2000-04-18 Microsoft Corporation Electronic mail object synchronization between a desktop computer and mobile device
US6012063A (en) * 1998-03-04 2000-01-04 Starfish Software, Inc. Block file system for minimal incremental data transfer between computing devices
US20020078075A1 (en) * 2000-12-15 2002-06-20 Colson James C. System, method, and program product for prioritizing synchronizable data

Cited By (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8621025B2 (en) 2000-01-25 2013-12-31 Synchronoss Technologis, Inc. Mobile data transfer and synchronization system
US20080201362A1 (en) * 2000-01-26 2008-08-21 Fusionone, Inc. Data transfer and synchronization system
US8442943B2 (en) 2000-01-26 2013-05-14 Synchronoss Technologies, Inc. Data transfer and synchronization between mobile systems using change log
US8156074B1 (en) 2000-01-26 2012-04-10 Synchronoss Technologies, Inc. Data transfer and synchronization system
US8315976B2 (en) 2000-01-26 2012-11-20 Synchronoss Technologies, Inc. Data transfer and synchronization system
US7895334B1 (en) 2000-07-19 2011-02-22 Fusionone, Inc. Remote access communication architecture apparatus and method
US9270664B2 (en) 2002-08-30 2016-02-23 Boss Logic, Llc System and method for secure reciprocal exchange of data
US9489536B2 (en) 2002-08-30 2016-11-08 Boss Logic, Llc System and method for secure reciprocal exchange of data
US10133877B2 (en) 2002-08-30 2018-11-20 Knapp Investment Company Limited System and method for secure reciprocal exchange of data
US8645471B2 (en) 2003-07-21 2014-02-04 Synchronoss Technologies, Inc. Device message management system
US9615221B1 (en) 2003-07-21 2017-04-04 Synchronoss Technologies, Inc. Device message management system
US20050038863A1 (en) * 2003-07-21 2005-02-17 Richard Onyon Device message management system
US9723460B1 (en) 2003-07-21 2017-08-01 Synchronoss Technologies, Inc. Device message management system
US7634509B2 (en) * 2003-11-07 2009-12-15 Fusionone, Inc. Personal information space management system and method
US20050102257A1 (en) * 2003-11-07 2005-05-12 Onyon Richard M. Personal information space management system and method
US20090106110A1 (en) * 2004-02-27 2009-04-23 Liam Stannard Method and system for promoting and transferring licensed content and applications
US8620286B2 (en) 2004-02-27 2013-12-31 Synchronoss Technologies, Inc. Method and system for promoting and transferring licensed content and applications
US9104689B2 (en) * 2004-03-17 2015-08-11 International Business Machines Corporation Method for synchronizing documents for disconnected operation
US20050210079A1 (en) * 2004-03-17 2005-09-22 Edlund Stefan B Method for synchronizing documents for disconnected operation
US20080082421A1 (en) * 2004-05-12 2008-04-03 Richard Onyon Monetization of an advanced contact identification system
US20060052091A1 (en) * 2004-05-12 2006-03-09 Richard Onyon Advanced contact identification system
US9542076B1 (en) 2004-05-12 2017-01-10 Synchronoss Technologies, Inc. System for and method of updating a personal profile
US8611873B2 (en) 2004-05-12 2013-12-17 Synchronoss Technologies, Inc. Advanced contact identification system
US20060074996A1 (en) * 2004-10-05 2006-04-06 International Business Machines Corporation System and method for synchronizing data
US8117277B2 (en) * 2005-04-27 2012-02-14 Microsoft Corporation Component based infrastructure for sharing files
US20060248122A1 (en) * 2005-04-27 2006-11-02 Microsoft Corporation Component based infrastructure for sharing files
US20070056043A1 (en) * 2005-05-19 2007-03-08 Richard Onyon Remote cell phone auto destruct
US20080288484A1 (en) * 2005-09-15 2008-11-20 Motorola, Inc. Distributed User Profile
US9338249B2 (en) * 2005-09-15 2016-05-10 Google Technology Holdings, Inc. Distributed user profile
US8015319B2 (en) * 2005-10-27 2011-09-06 Huawei Technologies Co., Ltd. Method, system, client and server for implementing data sync
US20080104277A1 (en) * 2005-10-27 2008-05-01 Huawei Technologies Co., Ltd. Method, system, client and server for implementing data sync
CN100413261C (zh) * 2006-01-04 2008-08-20 华为技术有限公司 数据恢复的方法和系统
US8874795B2 (en) * 2006-11-30 2014-10-28 Seoul National University Industry Foundation Data synchronization system
KR101221672B1 (ko) 2006-11-30 2013-01-14 재단법인서울대학교산학협력재단 데이터 동기화 시스템
US20080130812A1 (en) * 2006-11-30 2008-06-05 Seoul National University Industry Foundation Data synchronization system
US20080214163A1 (en) * 2007-01-26 2008-09-04 Richard Onyon System for and method of backing up content for use on a mobile device
US8181111B1 (en) 2007-12-31 2012-05-15 Synchronoss Technologies, Inc. System and method for providing social context to digital activity
US8255006B1 (en) 2009-11-10 2012-08-28 Fusionone, Inc. Event dependent notification system and method
WO2011067454A1 (en) * 2009-12-01 2011-06-09 Nokia Corporation Methods and apparatuses for relevance calculation
US20110295947A1 (en) * 2010-06-01 2011-12-01 Htc Corporation Communication apparatus and method thereof
US8943428B2 (en) 2010-11-01 2015-01-27 Synchronoss Technologies, Inc. System for and method of field mapping

Also Published As

Publication number Publication date
CN1392704A (zh) 2003-01-22
CN100336351C (zh) 2007-09-05
US20050203971A1 (en) 2005-09-15
FI114417B (fi) 2004-10-15
EP1267283A3 (en) 2006-02-15
FI20011277A (fi) 2002-12-16
FI20011277A0 (fi) 2001-06-15
EP1267283A2 (en) 2002-12-18
US7483925B2 (en) 2009-01-27

Similar Documents

Publication Publication Date Title
US20030028554A1 (en) Selecting data for synchronization
US7320011B2 (en) Selecting data for synchronization and for software configuration
US7376697B2 (en) Arrangement of data synchronization in a telecommunications system
US8081955B2 (en) Managing content to constrained devices
JP4081017B2 (ja) データを移動装置へ押し進めるためのシステム及び方法
US6738766B2 (en) Apparatus and methods for providing personalized application search results for wireless devices based on user profiles
US8024484B2 (en) Caching signatures
CN100428233C (zh) 用于搜索的方法和设备
KR100914895B1 (ko) 데이터의 유틸리티를 기반으로 하여 데이터 저장소로부터 데이터를 선택하는 시스템
US8171008B2 (en) Data retrieval
EP1510050B1 (en) Method and apparatus for providing e-mail to a mobile device
US8326846B2 (en) Virtual list view support in a distributed directory
US20120054162A1 (en) Likelihood-based storage management
US20130339472A1 (en) Methods and systems for notifying a server with cache information and for serving resources based on it
US20120130975A1 (en) Search method, apparatus, and system
US20050058138A1 (en) Communications management system
US20050215236A1 (en) Providing information for mobile users
US7430426B2 (en) Apparatus, and associated method, for selectably delaying synchronization of database copies in a radio communication system
WO2004051509A1 (en) Selecting data for synchronization and for software configuration
KR20000059019A (ko) 인터넷을 이용한 데이터 통신 장비의 정보 통합 관리 및공유방법
JP2009140004A (ja) 分散型推薦システム
CN115292681A (zh) 一种声纹注册方法、装置、设备及存储介质
JP2000259644A (ja) 情報共有装置及び記憶媒体
WO2003007559A1 (en) Content hashing in a wireless content switch

Legal Events

Date Code Title Description
AS Assignment

Owner name: NOKIA CORPORATION, FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KOSKIMIES, OSKARI;JUHOLA, JANNE;REEL/FRAME:013274/0010

Effective date: 20020805

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION