US20050138082A1 - Method, data transfer arrangement, server and terminal device for updating information in a terminal device - Google Patents

Method, data transfer arrangement, server and terminal device for updating information in a terminal device Download PDF

Info

Publication number
US20050138082A1
US20050138082A1 US11/015,630 US1563004A US2005138082A1 US 20050138082 A1 US20050138082 A1 US 20050138082A1 US 1563004 A US1563004 A US 1563004A US 2005138082 A1 US2005138082 A1 US 2005138082A1
Authority
US
United States
Prior art keywords
information
license
client device
file
application program
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
US11/015,630
Inventor
Tapio Rauma
Jukka Koutaniemi
Ari Parkkila
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.)
Capricode Oy
Original Assignee
Capricode Oy
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 Capricode Oy filed Critical Capricode Oy
Assigned to CAPRICODE OY ET AL. reassignment CAPRICODE OY ET AL. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KOUTANIEMI, JUKKA, PARKKILA, ARI, RAUMA, TAPIO
Publication of US20050138082A1 publication Critical patent/US20050138082A1/en
Priority to US13/224,766 priority Critical patent/US9118696B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/04Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability

Definitions

  • the invention relates to a method for synchronizing information comprised in an application program in a client device, in which method information comprised in an application program in a client device is updated from a server maintaining up-to-date information.
  • the invention also relates to a data transfer arrangement, in which the method is utilized.
  • the invention relates to a license server and a mobile terminal device included in the data transfer system.
  • the invention relates to software means for implementing the method.
  • terminal devices of various cellular networks, laptop computers or palm computers contain information, files and programs that are important to the user. Maintaining them in a way that the latest created version of each piece of information, file or program is always the one currently in use, is a challenging task.
  • the updating and at the same time unifying of information, files and programs in different devices is generally called synchronization of data.
  • One possible way of performing synchronization is for the user to perform it separately on each device. Although data transfer from one device and information system to another can function entirely electronically, it always requires action from the user in this case. The user must remember to synchronize the information of different devices frequently enough. If synchronization is not performed often enough, the user can end up in a situation in which there are too many differences in the information contained by different information systems. In the worst case, the user does not know which one of the files is the latest and/or most correct. Possibly it can be checked from the creation date of the information, but it is a laborious way, especially if there are a large number of files to be checked. Besides, the latest creation date of the file does not always ensure the correctness of all information, if information is maintained in more than two devices or files.
  • a subroutine included in the program which reminds of the updates, is utilized in the updating of computer software. It can be called a program-specific reminder. This reminder gives the user an update prompt when a sufficient number of days has passed since the previous prompt or update. The user can usually either accept the update or reject it. In some types of software, such a slow manner of updating is sufficient.
  • Such softwares are, for example, various text, image or presentation softwares.
  • Software Management has the following characteristics, for example: One terminal device or server can remote control at least one other device by it. It can also be used for complementing a program or a part of it in some terminal device by new information or parts of the program located in another device. The existence of the licenses, or rights of use for the programs are also managed by it. Software Management can also comprise matters related to Digital Right Management.
  • OMA Open Mobile Alliance
  • OMA DM Device Management
  • OMA DS Data Synchronization
  • SynchML Synch Mark up Language
  • the standards do not define how the starting of the synchronization could be implemented without any action from the user as a kind of automatic operation, when the application is started in the mobile terminal.
  • a good and simple software management procedure could thus make it easier to maintain and use programs in information networks and especially in various mobile terminal devices. By it, most software updates could be carried out as remote work of IT personnel or entirely without their contribution.
  • a good software management procedure could use the data transfer network so that it would not stress the data transfer network by unnecessary file transfer.
  • the objects of the invention are achieved by a procedure in which at the beginning of a program started in the terminal device, the terminal device is notified whether it is using an up-to-date piece of information, file or program or not.
  • the terminal device sends a query to another device maintaining up-to-date information.
  • This other device answers the query sent by the terminal device.
  • the information indicating the up-to-date status is transmitted by a special first license file maintained by the other device. Only in the case that this first license file indicates that there is old information, an old file or an old program in the terminal device that made the query, the actual updating of the information, file or program is started.
  • the updating is carried out as a separate measure from a device address indicated by the other license file according to the invention, which can be called the application file.
  • the method and data transfer arrangement according to the invention have the advantage that it is possible to use up-to-date information, files or programs in a mobile terminal always after the starting of a certain application, when desired.
  • the invention has the advantage that the limited mobile data transfer channel is not overloaded by the updating files being transferred.
  • the invention also has the advantage that the procedures according to the OMA DS and OMA DM specifications can be utilized in the updating of information, files and programs.
  • a further advantage of the information is the fact that the updating of the information/files can be started without explicit action required from the user.
  • the invention also has the advantage that the user need not remember the device address of the device maintaining the update file.
  • Yet another advantage of the invention is the fact that the user can also prevent the updating from taking place, if it is not wanted.
  • the invention has the advantage that after the user has given the permission to update, the files/information in the device are updated without any further action from the user.
  • the invention has the advantage that the memory capacity required by the procedure both in the terminal device and the other device maintaining the updating is small.
  • the method according to the invention for synchronizing information in the client device is characterized in that starting an application program or synchronization starting application in a client device causes checking of the up-to-date status of information comprised by an application program in the client device from a separate other license server before said information is taken into use in the application program.
  • the data transfer arrangement according to the invention is characterized in that the starting of an application program or synchronization starting application in the client device has been arranged to cause checking of the up-to-date status of the information in the application program of the client device from a separate license server before said information has been arranged to be taken into use in said application program.
  • the license server according to the invention is characterized in that it comprises an up-to-date first license file and a second up-to-date license file, by means of which the up-to-date status of the application program in the client device can be checked and updated.
  • a second device maintaining up-to-date license information/files according to the invention a license server according to the invention, advantageously comprises two license files.
  • the first license file comprises the following information, for example: license holder information, time of validity of the license and restrictions on use of the license.
  • the second license file comprises the following information, for example: the name and the version number of the license, information of the path from which the information, file or program can be retrieved, information about the objects to be downloaded and possibly various release notes.
  • the procedure according to the invention is started when the mobile terminal device requests the checking of the status of the information in its own license file by sending the request to the server maintaining the license information
  • the checking request can be sent either by the actual application program to be started or by a separate synchronization starting program to be started separately.
  • the license server according to the invention which received the checking request, checks the first license file it received from the mobile terminal device that sent the request. If the information of this received, first license file differs from the corresponding first license information on the license server, it is necessary to update the mobile terminal device. Then the license server sends to the terminal device that asked for the checking the updated first license file and the second license file according to the invention, by using which the terminal device that made the checking request can retrieve an updated version of the information, file or program.
  • the terminal device that made the checking query knows in each case whether it is using an up-to-date version of the information, files or program or not.
  • the license files to be transferred are so small that the load caused by them on the data transfer network does not have an effect on the performance of the network.
  • FIG. 1 is an exemplary signal chart of the steps of the procedure according to the invention in a client-server environment
  • FIG. 2 is an exemplary signal chart of the updating of information taking place through the procedure according to the invention
  • FIG. 3 a shows the information content of the first license file according to the invention by way of example
  • FIG. 3 b shows the information content of the second license file according to the invention by way of example
  • FIG. 4 shows, as an exemplary flow chart, the main steps of the method according to the invention.
  • FIG. 1 depicts, as an exemplary signal chart, the main steps of the method according to the invention.
  • the license server 12 maintains up-to-date license files according to the invention: the first license file and the second license file.
  • the first license file comprises the following license information, for example: the holder of the license, time of validity of the license and possible restrictions on use of the license.
  • the second license file comprises information needed in the actual implementation of the synchronization, such as: the name and version number of the license, path to the device address from which the update of the file or program can be retrieved, and information about the content of the object to be updated.
  • this second license file can comprise various additional information about the release.
  • This second license file can also be called the update application file.
  • the information synchronization procedure according to the invention is started when an application program, to which the checking routine according to the invention has been added, is started in a client device 11 belonging to some data transfer network.
  • the client device 11 has a separate synchronization starting application, the activation of which starts the synchronization procedure according to the invention.
  • the client device 11 can be, for example, a terminal device of a cellular network, a WLAN terminal device, a PDA or a palm computer.
  • the data transfer network can be some wireless data transfer network.
  • the client device 11 sends a synchronization starting message 14 to the license server 12 .
  • This message comprises the information according to the first license file in the form in which it has been saved in the client device 11 : the holder of the license, time of validity of the license and restrictions of the license.
  • the license server 12 checks the information of the first license file in the starting message 14 it received. If the license file contained by the starting message 14 is equivalent to the information contained by the corresponding first license file in the license server 12 , the license server 12 sends a synchronization acceptance message 15 and a message 16 containing the information of the valid first license file to the client device 11 , which asked for the synchronization.
  • the synchronization acceptance message 15 notifies the client device 11 that it has the newest updated version of the application program to be started or the information/file needed by it. If the status of the client device 11 is such as described above, no further data transfer between the license server 12 and the client device 11 is needed, and the client device 11 can start using the actual application program.
  • the license server 12 finds out that the synchronization starting message 14 received by it contains the first license file according to the invention, the information of which differs from the information in its own first license file, the operation follows the example of FIG. 2 .
  • the client device 11 sends an ordinary synchronization starting message 14 .
  • the license server 12 finds out that the information of the first license file held by it differs from the first license file contained by the synchronization starting message 14 it received from the client device 11 . In this situation, the license server 12 sends both valid license files according to the invention to the client device 11 , reference 17 .
  • the client device 11 does not receive the synchronization acceptance message 15 in this case, it knows that it has to update the information, file or program held by it on the basis of the information contained by the second license file received by it.
  • the user of the client device 11 can be asked for permission to carry out the actual updating at this stage.
  • an update permission of permanent nature can also be given in connection with any updating.
  • the client device 11 sends the actual request to update the information, file or program 18 to a media server 13 , the device address of which has been included in the second license file according to the invention, received by the client device 11 from the license server 12 .
  • the media server 13 sends the update information 19 to the client device 11 in the form defined by the OMA DM specification, for example.
  • the updating is carried out in the manner described by the update file sent by the media server 13 . After the updating carried out, the information, files and programs used by the client device 11 are up to date.
  • FIGS. 3 a and 3 b it is shown by way of example in which form the information comprised in the first and the second license file can be transmitted.
  • FIG. 3 a shows, as an example, the information comprised by the first license file in one exemplary case.
  • the licensee is V-tech
  • the license is valid from 18 Mar. to 31 Jan. 2003 and it concerns the NG_GAME_CHESS application.
  • This information comprised by the first license file according to the invention is sufficient to ensure the up-to-date status of the information, file or application program used by the client device 11 .
  • FIG. 3 b shows an example of the case when the license server 12 has found out that the synchronization starting message 14 sent by the client device 11 contains outdated information of the first license file. So the license server 12 sends the valid information of the first and the second license file according to the invention, indicated by reference 17 .
  • the second license file comprises the information shown in FIG. 3 b , for example: the name of the information, file or application to be updated, the version number, the search path of the update file, a description of the file to be transferred because of the updating and additionally some other information about the release.
  • the operation according to the invention requires an application program, the size of which in the license server 12 is in the order of 100 kB and in the client device under 100 kB.
  • the application according to the invention can advantageously be implemented as a Java 1.2 program.
  • a program based on Java 1.2 can also be applied in the client device 11 .
  • the program according to the invention can also be implemented as a Symbian C++ program.
  • step 400 the user of the client device 11 starts an application program, which can be either a certain utility application or a separate synchronization starting application. In both cases, when starting has taken place, the client device 11 sends a synchronization starting message 14 to a license server 12 maintaining up-to-date license information according to the invention, step 410 .
  • the information comprised by the synchronization starting message 14 has been described above in connection with FIGS. 1 to 3 .
  • the license server 12 compares the information of the first license file contained by the synchronization starting message 14 to the information of its own, up-to-date first license file.
  • the synchronization acceptance message 15 tells the client device 11 that it is using an up-to-date piece of information, file or program.
  • the payload application in the client device 11 can thus be started at once, step 480 .
  • the comparison result can be “NO”, which means that the first license file sent by the client device 11 in the synchronization starting message has contained old information.
  • the license server 12 sends both valid pieces of information of the first and the second license file according to the invention to the client device 11 , reference 17 .
  • the absence of the synchronization acceptance message 15 thus indicates to the client device 11 that update information can be retrieved by utilizing the information of the second license file.
  • the user of the client device 11 is advantageously given the possibility to prevent retrieving the update. This possibility can be useful when the update file to be transferred is so large that its transfer will take a long time. If the user prevents the retrieval of the update, the client device 11 immediately starts the not-up-to-date application program in it, or the application program is allowed to use old information or an old file, step 480 . In a preferred embodiment of the invention, the user of the client device can give an update permission of permanent nature, in which case the user is no more asked for an update permission.
  • Step 460 preferably comprises both the retrieval of the update from a device address indicated by the information contained by the second license file and the installation of the retrieved update file in the client device 11 .
  • the updated application program is started in the client device in step 480 .
  • the method according to the invention can be implemented by software applications, the first of which is located in a server 12 maintaining an up-to-date license file, and the second in a client device 11 .
  • the first software application comprising steps 420 , 430 , 440 and 470 of the method according to the invention shown in FIG. 4 is preferably in the license server 12 .
  • the client device 11 advantageously includes another software application comprising steps 400 , 410 , 450 , 460 and 480 . Otherwise the client device 11 and the license server 12 comply with the prior art.
  • Applying the invention does not require any other structural changes of the devices participating in the file transfer. So the client device 11 and the servers 12 and 13 comprise prior art data transfer means for transmitting various messages between them. The structure and operation of these data transfer means is determined on the basis of the data transfer network used. So the only measures required for utilizing the method according to the invention are installing the above described software applications both in the client device 11 and the license server 12 used.
  • the procedure according to the invention can also be applied in saving the information or files to be updated into a media server 13 .
  • a case like this could be, for example, updating calendar information from a mobile client device 11 to a media server 13 .
  • the client device 11 first presents to a license server 12 according to the invention a data synchronization request, in which the data transfer direction from the client device 11 to the servers 12 and 13 is defined as additional information.
  • Such updating of data causes at least a change of the version number in the first license file according to the invention in the license server 12 .
  • the actual information or file to be updated is transferred to the media server 13 .
  • the information to be transferred from the client device 11 to the media server 13 can be defined and transferred by procedures defined in an application-specific manner.

Abstract

The invention relates to a method and data transfer arrangement for synchronizing information comprised by an application program in a client device. In the method, information comprised by an application program in the client device is updated from a media server maintaining up-to-date information. In addition, the data transfer arrangement comprises a separate license server, which contains two separate license files: the first license file and the second license file. The up-to-date status of information in the client device can be ensured by means of the first license file. The second license file comprises information by which the update required by the client device can be retrieved from a media server maintaining up-to-date information.

Description

    FIELD OF THE INVENTION
  • The invention relates to a method for synchronizing information comprised in an application program in a client device, in which method information comprised in an application program in a client device is updated from a server maintaining up-to-date information. The invention also relates to a data transfer arrangement, in which the method is utilized. In addition, the invention relates to a license server and a mobile terminal device included in the data transfer system. Furthermore, the invention relates to software means for implementing the method.
  • BACKGROUND
  • Information available to people becomes easily dispersed to different devices and information systems. Part of the information available can be located in files in fixed networks on servers or personal computers, for example. On the other hand, terminal devices of various cellular networks, laptop computers or palm computers contain information, files and programs that are important to the user. Maintaining them in a way that the latest created version of each piece of information, file or program is always the one currently in use, is a challenging task. The updating and at the same time unifying of information, files and programs in different devices is generally called synchronization of data.
  • One possible way of performing synchronization is for the user to perform it separately on each device. Although data transfer from one device and information system to another can function entirely electronically, it always requires action from the user in this case. The user must remember to synchronize the information of different devices frequently enough. If synchronization is not performed often enough, the user can end up in a situation in which there are too many differences in the information contained by different information systems. In the worst case, the user does not know which one of the files is the latest and/or most correct. Possibly it can be checked from the creation date of the information, but it is a laborious way, especially if there are a large number of files to be checked. Besides, the latest creation date of the file does not always ensure the correctness of all information, if information is maintained in more than two devices or files.
  • A subroutine included in the program, which reminds of the updates, is utilized in the updating of computer software. It can be called a program-specific reminder. This reminder gives the user an update prompt when a sufficient number of days has passed since the previous prompt or update. The user can usually either accept the update or reject it. In some types of software, such a slow manner of updating is sufficient. Such softwares are, for example, various text, image or presentation softwares.
  • However, there are types of information, files and software in which correctness and currentness are desirable properties. Examples of such files and programs are various personal calendars and virus protection programs. They are useful to the user only when the information contained by them complies with the latest supplementary information that exists about them. There are many sad examples of deficiencies in the updating of virus protection programs. Because of the deficiencies of virus protection programs especially in mobile, wireless devices, entire company networks have become so badly contaminated that they have had to be closed down in order to destroy the viruses and worms spread in the network. Such an event is bad publicity for the company whose network has to be closed down even for a short time because of a virus problem in it.
  • In principle, it would be possible to update the information, file or soft ware in the terminal device always when the terminal device is started. However, this solution increases the need for data transfer so much that especially in wireless data transfer systems, the limited data transfer capacity becomes a problem. Then the program in the terminal device starts slowly, because transferring the updated version to the terminal device is slow through a limited data transfer channel. The slowness of the data transfer channel is further increased by the transfer of unnecessary updates to such terminal devices, which already have the latest updated version of the information, file or program.
  • The above examples illustrate the importance of managing up-to-date information in the prior art information networks. This is particularly true in the management of information and softwares contained by various mobile devices. Such management of information and files is generally called Software Management. Software management has the following characteristics, for example: One terminal device or server can remote control at least one other device by it. It can also be used for complementing a program or a part of it in some terminal device by new information or parts of the program located in another device. The existence of the licenses, or rights of use for the programs are also managed by it. Software Management can also comprise matters related to Digital Right Management.
  • Open Mobile Alliance (OMA) has published specifications, which concern the updating and maintenance of software in mobile devices. The specifications OMA DM (Device Management) and OMA DS (Data Synchronization) describe some possible ways of implementing data transfer and up-to-date file maintenance in mobile devices. These specifications describe the SynchML (Synchronization Mark up Language) protocol and how it is utilized in the actual implementation of synchronization. However, the standards do not define how the starting of the synchronization could be implemented without any action from the user as a kind of automatic operation, when the application is started in the mobile terminal.
  • A good and simple software management procedure could thus make it easier to maintain and use programs in information networks and especially in various mobile terminal devices. By it, most software updates could be carried out as remote work of IT personnel or entirely without their contribution. In addition, a good software management procedure could use the data transfer network so that it would not stress the data transfer network by unnecessary file transfer.
  • SUMMARY
  • It is the object of the present invention to provide a method and data transfer arrangement by which it is always possible to use the most up-to-date version of some piece of information, file or program used in a mobile terminal, but without putting unnecessary stress on the limited mobile data transfer network serving the terminal device.
  • The objects of the invention are achieved by a procedure in which at the beginning of a program started in the terminal device, the terminal device is notified whether it is using an up-to-date piece of information, file or program or not. In order to obtain this information, the terminal device sends a query to another device maintaining up-to-date information. This other device answers the query sent by the terminal device. The information indicating the up-to-date status is transmitted by a special first license file maintained by the other device. Only in the case that this first license file indicates that there is old information, an old file or an old program in the terminal device that made the query, the actual updating of the information, file or program is started. The updating is carried out as a separate measure from a device address indicated by the other license file according to the invention, which can be called the application file.
  • The method and data transfer arrangement according to the invention have the advantage that it is possible to use up-to-date information, files or programs in a mobile terminal always after the starting of a certain application, when desired.
  • In addition, the invention has the advantage that the limited mobile data transfer channel is not overloaded by the updating files being transferred.
  • The invention also has the advantage that the procedures according to the OMA DS and OMA DM specifications can be utilized in the updating of information, files and programs.
  • A further advantage of the information is the fact that the updating of the information/files can be started without explicit action required from the user.
  • The invention also has the advantage that the user need not remember the device address of the device maintaining the update file.
  • Yet another advantage of the invention is the fact that the user can also prevent the updating from taking place, if it is not wanted.
  • Furthermore, the invention has the advantage that after the user has given the permission to update, the files/information in the device are updated without any further action from the user.
  • In addition, the invention has the advantage that the memory capacity required by the procedure both in the terminal device and the other device maintaining the updating is small.
  • The method according to the invention for synchronizing information in the client device is characterized in that starting an application program or synchronization starting application in a client device causes checking of the up-to-date status of information comprised by an application program in the client device from a separate other license server before said information is taken into use in the application program.
  • The data transfer arrangement according to the invention is characterized in that the starting of an application program or synchronization starting application in the client device has been arranged to cause checking of the up-to-date status of the information in the application program of the client device from a separate license server before said information has been arranged to be taken into use in said application program.
  • The license server according to the invention is characterized in that it comprises an up-to-date first license file and a second up-to-date license file, by means of which the up-to-date status of the application program in the client device can be checked and updated.
  • The terminal device of a data transfer network according to the invention is characterized in that the terminal device comprises
      • a) means for starting the synchronization of information comprised in an application
      • b) program to be started in a terminal device, which means have been arranged to send a synchronization starting message to a license server, which synchronization starting message comprises information concerning the up-to-date status of the application program to be started, and
      • c) means for processing the reply message sent by the license server, which message comprises the information of the up-to-date first license file and either the information of the second license file or a synchronization acceptance message.
  • Some preferred embodiments of the invention are presented in the dependent claims.
  • The basic idea of the invention is the following: A second device maintaining up-to-date license information/files according to the invention, a license server according to the invention, advantageously comprises two license files. The first license file comprises the following information, for example: license holder information, time of validity of the license and restrictions on use of the license. The second license file comprises the following information, for example: the name and the version number of the license, information of the path from which the information, file or program can be retrieved, information about the objects to be downloaded and possibly various release notes.
  • The procedure according to the invention is started when the mobile terminal device requests the checking of the status of the information in its own license file by sending the request to the server maintaining the license information The checking request can be sent either by the actual application program to be started or by a separate synchronization starting program to be started separately. The license server according to the invention, which received the checking request, checks the first license file it received from the mobile terminal device that sent the request. If the information of this received, first license file differs from the corresponding first license information on the license server, it is necessary to update the mobile terminal device. Then the license server sends to the terminal device that asked for the checking the updated first license file and the second license file according to the invention, by using which the terminal device that made the checking request can retrieve an updated version of the information, file or program.
  • If it is not necessary to update the information, files or program of the terminal device, only the first license file according to the invention is sent to the terminal device that made the checking query. Thus the terminal device that made the query knows in each case whether it is using an up-to-date version of the information, files or program or not. The license files to be transferred are so small that the load caused by them on the data transfer network does not have an effect on the performance of the network.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • In the following, the invention will be described in more detail. Reference will be made to the accompanying drawings, in which
  • FIG. 1 is an exemplary signal chart of the steps of the procedure according to the invention in a client-server environment,
  • FIG. 2 is an exemplary signal chart of the updating of information taking place through the procedure according to the invention,
  • FIG. 3 a shows the information content of the first license file according to the invention by way of example,
  • FIG. 3 b shows the information content of the second license file according to the invention by way of example, and
  • FIG. 4 shows, as an exemplary flow chart, the main steps of the method according to the invention.
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • FIG. 1 depicts, as an exemplary signal chart, the main steps of the method according to the invention. In the example of FIG. 1, the license server 12 maintains up-to-date license files according to the invention: the first license file and the second license file. The first license file comprises the following license information, for example: the holder of the license, time of validity of the license and possible restrictions on use of the license. The second license file comprises information needed in the actual implementation of the synchronization, such as: the name and version number of the license, path to the device address from which the update of the file or program can be retrieved, and information about the content of the object to be updated. In addition, this second license file can comprise various additional information about the release. This second license file can also be called the update application file.
  • The information synchronization procedure according to the invention is started when an application program, to which the checking routine according to the invention has been added, is started in a client device 11 belonging to some data transfer network. Alternatively, the client device 11 has a separate synchronization starting application, the activation of which starts the synchronization procedure according to the invention. The client device 11 can be, for example, a terminal device of a cellular network, a WLAN terminal device, a PDA or a palm computer. The data transfer network can be some wireless data transfer network. When either of the above mentioned application programs in the client device 11 is started, the client device 11 sends a synchronization starting message 14 to the license server 12. This message comprises the information according to the first license file in the form in which it has been saved in the client device 11: the holder of the license, time of validity of the license and restrictions of the license.
  • The license server 12 checks the information of the first license file in the starting message 14 it received. If the license file contained by the starting message 14 is equivalent to the information contained by the corresponding first license file in the license server 12, the license server 12 sends a synchronization acceptance message 15 and a message 16 containing the information of the valid first license file to the client device 11, which asked for the synchronization. The synchronization acceptance message 15 notifies the client device 11 that it has the newest updated version of the application program to be started or the information/file needed by it. If the status of the client device 11 is such as described above, no further data transfer between the license server 12 and the client device 11 is needed, and the client device 11 can start using the actual application program.
  • However, if the license server 12 finds out that the synchronization starting message 14 received by it contains the first license file according to the invention, the information of which differs from the information in its own first license file, the operation follows the example of FIG. 2. In FIG. 2, the client device 11 sends an ordinary synchronization starting message 14. The license server 12 finds out that the information of the first license file held by it differs from the first license file contained by the synchronization starting message 14 it received from the client device 11. In this situation, the license server 12 sends both valid license files according to the invention to the client device 11, reference 17. Because the client device 11 does not receive the synchronization acceptance message 15 in this case, it knows that it has to update the information, file or program held by it on the basis of the information contained by the second license file received by it. In an advantageous embodiment of the invention, the user of the client device 11 can be asked for permission to carry out the actual updating at this stage. In another advantageous embodiment of the invention, an update permission of permanent nature can also be given in connection with any updating.
  • If the permission to carry out the updating has been obtained from the user or it is of permanent nature, the client device 11 sends the actual request to update the information, file or program 18 to a media server 13, the device address of which has been included in the second license file according to the invention, received by the client device 11 from the license server 12. As a reply to the update request 18 received, the media server 13 sends the update information 19 to the client device 11 in the form defined by the OMA DM specification, for example. In the client device 11, the updating is carried out in the manner described by the update file sent by the media server 13. After the updating carried out, the information, files and programs used by the client device 11 are up to date.
  • In FIGS. 3 a and 3 b, it is shown by way of example in which form the information comprised in the first and the second license file can be transmitted. FIG. 3 a shows, as an example, the information comprised by the first license file in one exemplary case. In the example of FIG. 3 a, the licensee is V-tech, the license is valid from 18 Mar. to 31 Jan. 2003 and it concerns the NG_GAME_CHESS application. This information comprised by the first license file according to the invention is sufficient to ensure the up-to-date status of the information, file or application program used by the client device 11.
  • FIG. 3 b shows an example of the case when the license server 12 has found out that the synchronization starting message 14 sent by the client device 11 contains outdated information of the first license file. So the license server 12 sends the valid information of the first and the second license file according to the invention, indicated by reference 17. The second license file comprises the information shown in FIG. 3 b, for example: the name of the information, file or application to be updated, the version number, the search path of the update file, a description of the file to be transferred because of the updating and additionally some other information about the release.
  • In the client device 11 and license server 12 used, the operation according to the invention requires an application program, the size of which in the license server 12 is in the order of 100 kB and in the client device under 100 kB. In the license server 12, the application according to the invention can advantageously be implemented as a Java 1.2 program. A program based on Java 1.2 can also be applied in the client device 11. However, in some client devices 11, like terminal devices of a cellular network, the program according to the invention can also be implemented as a Symbian C++ program.
  • In FIG. 4, the main steps of the method used in the synchronization of information according to the invention are shown as an exemplary flow chart. The features of the invention shown in FIGS. 1 and 2 are also utilized in connection with the description. In step 400, the user of the client device 11 starts an application program, which can be either a certain utility application or a separate synchronization starting application. In both cases, when starting has taken place, the client device 11 sends a synchronization starting message 14 to a license server 12 maintaining up-to-date license information according to the invention, step 410. The information comprised by the synchronization starting message 14 has been described above in connection with FIGS. 1 to 3.
  • In step 420, the license server 12 compares the information of the first license file contained by the synchronization starting message 14 to the information of its own, up-to-date first license file. In step 430, it is decided whether the information of the received first license file and the up-to-date first license file are equivalent or not. If these first license files are equivalent, the license server 12 sends a synchronization acceptance message 15 and the information 16 of the valid first license file to the client device 11 in step 470. The synchronization acceptance message 15 tells the client device 11 that it is using an up-to-date piece of information, file or program. The payload application in the client device 11 can thus be started at once, step 480.
  • In step 430, the comparison result can be “NO”, which means that the first license file sent by the client device 11 in the synchronization starting message has contained old information. In that case, in step 440, the license server 12 sends both valid pieces of information of the first and the second license file according to the invention to the client device 11, reference 17. The absence of the synchronization acceptance message 15 thus indicates to the client device 11 that update information can be retrieved by utilizing the information of the second license file.
  • In step 450, the user of the client device 11 is advantageously given the possibility to prevent retrieving the update. This possibility can be useful when the update file to be transferred is so large that its transfer will take a long time. If the user prevents the retrieval of the update, the client device 11 immediately starts the not-up-to-date application program in it, or the application program is allowed to use old information or an old file, step 480. In a preferred embodiment of the invention, the user of the client device can give an update permission of permanent nature, in which case the user is no more asked for an update permission.
  • If the user of the client device 11 allows the retrieval of the update offered in step 450, it is carried out in step 460. Step 460 preferably comprises both the retrieval of the update from a device address indicated by the information contained by the second license file and the installation of the retrieved update file in the client device 11. When the updating has been completed, the updated application program is started in the client device in step 480.
  • The method according to the invention can be implemented by software applications, the first of which is located in a server 12 maintaining an up-to-date license file, and the second in a client device 11. The first software application comprising steps 420, 430, 440 and 470 of the method according to the invention shown in FIG. 4 is preferably in the license server 12. The client device 11 advantageously includes another software application comprising steps 400, 410, 450, 460 and 480. Otherwise the client device 11 and the license server 12 comply with the prior art.
  • Applying the invention does not require any other structural changes of the devices participating in the file transfer. So the client device 11 and the servers 12 and 13 comprise prior art data transfer means for transmitting various messages between them. The structure and operation of these data transfer means is determined on the basis of the data transfer network used. So the only measures required for utilizing the method according to the invention are installing the above described software applications both in the client device 11 and the license server 12 used.
  • The procedure according to the invention can also be applied in saving the information or files to be updated into a media server 13. A case like this could be, for example, updating calendar information from a mobile client device 11 to a media server 13. In this situation, the client device 11 first presents to a license server 12 according to the invention a data synchronization request, in which the data transfer direction from the client device 11 to the servers 12 and 13 is defined as additional information. Such updating of data causes at least a change of the version number in the first license file according to the invention in the license server 12. In addition, it is also possible to define or change other information belonging to the first or the second license file according to the invention.
  • When the license files according to the invention has been updated on the license server 12, the actual information or file to be updated is transferred to the media server 13. The information to be transferred from the client device 11 to the media server 13 can be defined and transferred by procedures defined in an application-specific manner.
  • Some preferred embodiments of the method and data transfer arrangement and related devices according to the invention have been described above. The invention is not limited to the embodiments described above, but the inventive idea can be applied in numerous ways within the limits set by the claims.

Claims (20)

1. A method for synchronizing information comprised by an application program in a client device from a media server maintaining up-to-date information,
a) in which method the starting of the application program in the client device or a synchronization starting application causes checking of the up-to-date status of an application program in a client device before said piece of information is taken into use in the application program,
b) in which method for checking the up-to-date status of the information the client device sends a synchronization starting message to a license server, which checks the information comprised by the synchronization starting message it received and sends back to the client device a reply message, and
c) in which method said reply message always comprises the information of an up-to-date first license file and one of the following: a synchronization acceptance message or the information of a second license file, by using which the information of the application program can be updated to the client device from said media server.
2. The method according to claim 1, wherein if the client device receives the information of the second license file, the user of the client device is asked, at least on the first time of updating, for permission to carry out the updating from the media server.
3. The method according to claim 2, wherein if the update permission has been received, the client device updates the information comprised by said application program from the media server by sending an update request, to which the media server replies by sending to the client device the update information it requested.
4. The method according to claim 1, wherein if the client device receives a synchronization acceptance message, the application program used on the client device comprises up-to-date information, which is used as such.
5. The method according to claim 1, where the first license file comprises the following information: the licensee, time of validity of the license and restrictions of the license.
6. The method according to claim 1, where the second license file comprises the following information: the name of the information, file or application to be updated, the version number, the search path of the update file, a description of the file to be transferred because of the updating and other information concerning the release.
7. A data transfer arrangement for synchronizing information comprised by an application program in a client device,
a) in which data transfer arrangement, information comprised by an application program in a client device can be updated from a media server maintaining up-to-date information after the starting of said application program or synchronization starting application before said information is arranged to be taken into use in said application program,
b) in which data transfer arrangement the client device has been arranged to send a synchronization starting message to the license server for checking the up-to-date status of the application program in a client device before the application program is used, and the license server has been arranged to check the information comprised by the synchronization message it has received and to send the checking result as a reply message back to the client device, and
c) in which data transfer arrangement said reply message always comprises the information of an up-to-date first license file and one of the following files: a synchronization acceptance message or the information of a second license file, by using which the information of the application program has been arranged to be updated to the client device from said media server.
8. The data transfer arrangement according to claim 7, wherein if the client device has received the information of the second license file, in that case the client device has been arranged to update the information comprised by said application program from the media server by sending an update request, as a reply to which the media server has been arranged to send to the client device the update information asked by it.
9. The data transfer arrangement according to claim 7, wherein if the client device has received a synchronization acceptance message, the application program used on the client device comprises up-to-date information.
10. The data transfer arrangement according to claim 7, where the first license file comprises the following information: the licensee, time of validity of the license and restrictions of the license.
11. The data transfer arrangement according to claim 7, where the second license file comprises the following information: the name of the information, file or application to be updated, the version number, the search path of the update file, a description of the file to be transferred because of the updating and other information concerning the release.
12. A license server for synchronizing information comprised by an application program in a client device, which license server comprises
a) files concerning the application program in the client device, which files comprise an up-to-date first license file and a second license file, by which the up-to-date status of said application program in the client device can be checked and updated from a media server before using the application program,
b) means for checking the information contained by the first license file of the synchronization message received from the client device against the corresponding first piece of license information maintained by the license server, and
c) means for sending a reply message, which comprises an up-to-date first piece of license information and either a synchronization acceptance message or a second piece of license information, by using which the information of the application program can be updated to the client device from said media server.
13. The license server according to claim 12, where said first license file comprises the following information: the licensee, time of validity of the license and restrictions of the license.
14. The license server according to claim 12, where said second license file comprises the following information: the name of the information, file or application to be updated, the version number, the search path of the update file, a description of the file to be transferred because of the updating and other information concerning the release.
15. A terminal device of a data transfer network, which comprises means for sending, receiving and processing messages
a) means for updating information comprised by an application program used in the terminal device from another device (13),
b) means for starting the synchronization of information comprised in an application program to be started in the terminal device, which means have been arranged to send a synchronization starting message to a license server, which synchronization starting message comprises information concerning the up-to-date status of the application program to be started, and
c) means for processing a reply message sent by the license server because of the synchronization starting message, which message comprises the information of an up-to-date first license file and the information of either a synchronization acceptance message or a second license file, by using which the information of the application program can be updated to the terminal device from said other device.
16. The terminal device according to claim 15, which also comprises
a) means for asking the user of the terminal device for update permission at least on the first time of updating, if the information of the second license file has been received, and
b) means for retrieving the update from a second device on the basis of the information received.
17. The terminal device according to claim 15, wherein said first license file comprises the following information: the licensee, time of validity of the license and the restrictions of the license.
18. The terminal device according to claim 15, wherein said second license file comprises the following information: the name of the information, file or application to be updated, the version number, the search path of the update file, a description of the file to be transferred because of the updating and other information concerning the release.
19. The terminal device according to claim 15, where said means have been implemented by program means.
20. The terminal device according to claim 15, where the terminal is one of the following: a terminal device of a cellular network, a WLAN terminal device, a PDA or a palm computer.
US11/015,630 2003-12-18 2004-12-17 Method, data transfer arrangement, server and terminal device for updating information in a terminal device Abandoned US20050138082A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/224,766 US9118696B2 (en) 2003-12-18 2011-09-02 Method, data transfer arrangement, server and terminal device for updating information in a terminal device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
FI20031862 2003-12-18
FI20031862A FI117151B (en) 2003-12-18 2003-12-18 A method, a data transfer arrangement, a server, and a terminal for performing an update of the information in the terminal

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/224,766 Continuation US9118696B2 (en) 2003-12-18 2011-09-02 Method, data transfer arrangement, server and terminal device for updating information in a terminal device

Publications (1)

Publication Number Publication Date
US20050138082A1 true US20050138082A1 (en) 2005-06-23

Family

ID=29763556

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/015,630 Abandoned US20050138082A1 (en) 2003-12-18 2004-12-17 Method, data transfer arrangement, server and terminal device for updating information in a terminal device
US13/224,766 Active US9118696B2 (en) 2003-12-18 2011-09-02 Method, data transfer arrangement, server and terminal device for updating information in a terminal device

Family Applications After (1)

Application Number Title Priority Date Filing Date
US13/224,766 Active US9118696B2 (en) 2003-12-18 2011-09-02 Method, data transfer arrangement, server and terminal device for updating information in a terminal device

Country Status (2)

Country Link
US (2) US20050138082A1 (en)
FI (1) FI117151B (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080301771A1 (en) * 2007-06-04 2008-12-04 Takanao Kawai Electronic device, application authentication method, application execution system, and computer readable medium containing executable program instruction
US20090048691A1 (en) * 2007-08-16 2009-02-19 Honeywell International Inc. Embedded building conroller with stored software license information
US20090150764A1 (en) * 2007-10-26 2009-06-11 Jason Farrell System and method for remote update of display pages
CN102752302A (en) * 2012-07-03 2012-10-24 厦门简帛信息科技有限公司 Cloud server and copy method and system of digital resource
TWI413377B (en) * 2010-08-19 2013-10-21 Hon Hai Prec Ind Co Ltd Network equipment and method for enabling the process dynamically
US20140032342A1 (en) * 2012-07-24 2014-01-30 Scott Joseph Tyburski Menu creation and design system
US20140215595A1 (en) * 2013-01-31 2014-07-31 Hewlett-Packard Development Company, L.P. Security token based user authentication in a multi-tenanted application
US20140325470A1 (en) * 2013-04-30 2014-10-30 MobileDataForce, Inc. Method and system for platform-independent application development
CN104488248A (en) * 2014-04-15 2015-04-01 华为技术有限公司 File synchronization method, server and terminal
US20150363901A1 (en) * 2011-05-31 2015-12-17 Qualcomm Incorporated Apparatus and method of managing a licensable item
CN110309106A (en) * 2019-05-27 2019-10-08 深圳市好成绩网络科技有限公司 Method, apparatus, electronic equipment and the computer storage medium that file updates
US20200001185A1 (en) * 2018-06-27 2020-01-02 Josiah Eatedali Dynamic adjustment of availability of access to video games based on real-world events
US10574749B2 (en) 2012-07-03 2020-02-25 Xiamen Geeboo Information Technology Co. Ltd. Cloud server and digital resource duplication method and system

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102375757B (en) * 2010-08-13 2013-07-03 国基电子(上海)有限公司 Network equipment and dynamic process starting method thereof

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5023907A (en) * 1988-09-30 1991-06-11 Apollo Computer, Inc. Network license server
US5276871A (en) * 1991-03-18 1994-01-04 Bull Hn Information Systems Inc. Method of file shadowing among peer systems
US5579479A (en) * 1994-10-03 1996-11-26 Plum Hall Inc. Computer software licensing authentication method and apparatus
US5671412A (en) * 1995-07-28 1997-09-23 Globetrotter Software, Incorporated License management system for software applications
US5708709A (en) * 1995-12-08 1998-01-13 Sun Microsystems, Inc. System and method for managing try-and-buy usage of application programs
US5742820A (en) * 1995-07-06 1998-04-21 Novell, Inc. Mechanism for efficiently synchronizing information over a network
US6023766A (en) * 1997-02-14 2000-02-08 Fujitsu Limited Software license control system and software license control equipment
US6049670A (en) * 1995-01-10 2000-04-11 Fujitsu Limited Identifier managing device and method in software distribution system
US6260141B1 (en) * 1997-09-19 2001-07-10 Hyo Joon Park Software license control system based on independent software registration server
US6496977B1 (en) * 1999-10-21 2002-12-17 International Business Machines Corporation Method and system for implementing network filesystem-based aid for computer operating system upgrades
US6502124B1 (en) * 1996-11-11 2002-12-31 Hitachi, Ltd. Method of and apparatus for managing licensed software
US6510466B1 (en) * 1998-12-14 2003-01-21 International Business Machines Corporation Methods, systems and computer program products for centralized management of application programs on a network
US6678741B1 (en) * 1999-04-09 2004-01-13 Sun Microsystems, Inc. Method and apparatus for synchronizing firmware
US6708157B2 (en) * 1994-11-23 2004-03-16 Contentguard Holdings Inc. System for controlling the distribution and use of digital works using digital tickets
US20060018454A1 (en) * 2004-07-13 2006-01-26 Matsushita Electric Industrial Co., Ltd. Computer system using identification information and control method thereof

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2349044A (en) 1999-04-16 2000-10-18 Emisis Infocom Group Plc Transfer of data to a PDA
US20040025053A1 (en) * 2000-08-09 2004-02-05 Hayward Philip John Personal data device and protection system and method for storing and protecting personal data
US6941326B2 (en) 2001-01-24 2005-09-06 Microsoft Corporation Accounting for update notifications in synchronizing data that may be represented by different data structures
KR100421624B1 (en) 2001-11-02 2004-03-11 (주) 한정문 Platform Independent Software Automatic Searching/Distribution/Install Apparatus and The method of Searching and Distribution for that apparatus
US6996817B2 (en) * 2001-12-12 2006-02-07 Valve Corporation Method and system for upgrading and rolling back versions

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5023907A (en) * 1988-09-30 1991-06-11 Apollo Computer, Inc. Network license server
US5276871A (en) * 1991-03-18 1994-01-04 Bull Hn Information Systems Inc. Method of file shadowing among peer systems
US5579479A (en) * 1994-10-03 1996-11-26 Plum Hall Inc. Computer software licensing authentication method and apparatus
US6708157B2 (en) * 1994-11-23 2004-03-16 Contentguard Holdings Inc. System for controlling the distribution and use of digital works using digital tickets
US6049670A (en) * 1995-01-10 2000-04-11 Fujitsu Limited Identifier managing device and method in software distribution system
US5742820A (en) * 1995-07-06 1998-04-21 Novell, Inc. Mechanism for efficiently synchronizing information over a network
US5671412A (en) * 1995-07-28 1997-09-23 Globetrotter Software, Incorporated License management system for software applications
US5708709A (en) * 1995-12-08 1998-01-13 Sun Microsystems, Inc. System and method for managing try-and-buy usage of application programs
US6502124B1 (en) * 1996-11-11 2002-12-31 Hitachi, Ltd. Method of and apparatus for managing licensed software
US6023766A (en) * 1997-02-14 2000-02-08 Fujitsu Limited Software license control system and software license control equipment
US6260141B1 (en) * 1997-09-19 2001-07-10 Hyo Joon Park Software license control system based on independent software registration server
US6510466B1 (en) * 1998-12-14 2003-01-21 International Business Machines Corporation Methods, systems and computer program products for centralized management of application programs on a network
US6678741B1 (en) * 1999-04-09 2004-01-13 Sun Microsystems, Inc. Method and apparatus for synchronizing firmware
US6496977B1 (en) * 1999-10-21 2002-12-17 International Business Machines Corporation Method and system for implementing network filesystem-based aid for computer operating system upgrades
US20060018454A1 (en) * 2004-07-13 2006-01-26 Matsushita Electric Industrial Co., Ltd. Computer system using identification information and control method thereof

Cited By (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080301771A1 (en) * 2007-06-04 2008-12-04 Takanao Kawai Electronic device, application authentication method, application execution system, and computer readable medium containing executable program instruction
US9147049B2 (en) 2007-08-16 2015-09-29 Honeywell International Inc. Embedded building conroller with stored software license information
US20090048691A1 (en) * 2007-08-16 2009-02-19 Honeywell International Inc. Embedded building conroller with stored software license information
US20090150764A1 (en) * 2007-10-26 2009-06-11 Jason Farrell System and method for remote update of display pages
US8219902B2 (en) * 2007-10-26 2012-07-10 T-Mobile Usa, Inc. System and method for remote update of display pages
TWI413377B (en) * 2010-08-19 2013-10-21 Hon Hai Prec Ind Co Ltd Network equipment and method for enabling the process dynamically
US10140672B2 (en) * 2011-05-31 2018-11-27 Qualcomm Incorporated Apparatus and method of managing a licensable item
US20150363901A1 (en) * 2011-05-31 2015-12-17 Qualcomm Incorporated Apparatus and method of managing a licensable item
CN102752302A (en) * 2012-07-03 2012-10-24 厦门简帛信息科技有限公司 Cloud server and copy method and system of digital resource
US10574749B2 (en) 2012-07-03 2020-02-25 Xiamen Geeboo Information Technology Co. Ltd. Cloud server and digital resource duplication method and system
US20160350883A1 (en) * 2012-07-24 2016-12-01 Softcafe, L.L.C. Menu creation and design system
US10249010B2 (en) * 2012-07-24 2019-04-02 Softcafe, L.L.C. Menu creation and design system
US20140032342A1 (en) * 2012-07-24 2014-01-30 Scott Joseph Tyburski Menu creation and design system
US9058481B2 (en) * 2013-01-31 2015-06-16 Hewlett-Packard Development Company, L.P. Security token based user authentication in a multi-tenanted application
US20140215595A1 (en) * 2013-01-31 2014-07-31 Hewlett-Packard Development Company, L.P. Security token based user authentication in a multi-tenanted application
US9069375B2 (en) * 2013-04-30 2015-06-30 MobileDataForce, Inc. Method and system for platform-independent application development
US20140325470A1 (en) * 2013-04-30 2014-10-30 MobileDataForce, Inc. Method and system for platform-independent application development
WO2015157904A1 (en) * 2014-04-15 2015-10-22 华为技术有限公司 File synchronization method, server, and terminal
CN104488248A (en) * 2014-04-15 2015-04-01 华为技术有限公司 File synchronization method, server and terminal
US20200001185A1 (en) * 2018-06-27 2020-01-02 Josiah Eatedali Dynamic adjustment of availability of access to video games based on real-world events
US10786739B2 (en) * 2018-06-27 2020-09-29 Activision Publishing, Inc. Dynamic adjustment of availability of access to video games based on real-world events
CN110309106A (en) * 2019-05-27 2019-10-08 深圳市好成绩网络科技有限公司 Method, apparatus, electronic equipment and the computer storage medium that file updates

Also Published As

Publication number Publication date
US20110320519A1 (en) 2011-12-29
US9118696B2 (en) 2015-08-25
FI117151B (en) 2006-06-30
FI20031862A0 (en) 2003-12-18
FI20031862A (en) 2005-06-19

Similar Documents

Publication Publication Date Title
US9118696B2 (en) Method, data transfer arrangement, server and terminal device for updating information in a terminal device
US9418132B2 (en) System for an open architecture deployment with centralized synchronization
US10419289B2 (en) System and method for configuration management service
EP1921871B1 (en) A method and download agent for downloading in parallel
US7552220B2 (en) System and method to refresh proxy cache server objects
US8073432B2 (en) Data synchronization
US20070168721A1 (en) Method, network entity, system, electronic device and computer program product for backup and restore provisioning
KR100988961B1 (en) Side-by-side drivers
US7032033B1 (en) Handling collisions during synchronization of data between client and server computers
JP4794143B2 (en) System and method for managing cache objects using notification bonds
US7853986B2 (en) Document distribution system and method
US20120144456A1 (en) Method of receiving, storing, and providing device management parameters and firmware updates to application programs within a mobile device
US20070180075A1 (en) System and method for synchronization of version annotated objects
JP2006285601A (en) File distribution method, and client terminal realizing it
JPWO2002075525A1 (en) Software update system, software update method, and software update program
CN107025122B (en) Light application access method and system
CN112463808A (en) Data processing method and device of target cluster and server
CN109165259B (en) Index table updating method based on network attached storage, processor and storage device
JP2005301464A (en) Backup method and system
JP2017156914A (en) Information processing system, information processing device, and information processing method
KR20160025282A (en) System and method for providing client terminal to user customized synchronization service
EP1387296A1 (en) Distributed file system
JP2002251309A (en) Shared file management system
CN111404979B (en) Method and device for processing service request and computer readable storage medium
JP2003330836A (en) Data transmission method

Legal Events

Date Code Title Description
AS Assignment

Owner name: CAPRICODE OY ET AL., FINLAND

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:RAUMA, TAPIO;KOUTANIEMI, JUKKA;PARKKILA, ARI;REEL/FRAME:016110/0706;SIGNING DATES FROM 20041214 TO 20041215

STCB Information on status: application discontinuation

Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION