WO2012147272A1 - Data linkage terminal, data linkage method, and data linkage system - Google Patents

Data linkage terminal, data linkage method, and data linkage system

Info

Publication number
WO2012147272A1
WO2012147272A1 PCT/JP2012/002059 JP2012002059W WO2012147272A1 WO 2012147272 A1 WO2012147272 A1 WO 2012147272A1 JP 2012002059 W JP2012002059 W JP 2012002059W WO 2012147272 A1 WO2012147272 A1 WO 2012147272A1
Authority
WO
Grant status
Application
Patent type
Prior art keywords
data
terminal
unit
link
cooperation
Prior art date
Application number
PCT/JP2012/002059
Other languages
French (fr)
Japanese (ja)
Inventor
東 吾紀男
松井 典弘
良浩 氏家
小林 進
Original Assignee
パナソニック株式会社
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

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/50Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5094Allocation of resources, e.g. of the central processing unit [CPU] where the allocation takes into account power or heat criteria
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing
    • Y02D10/20Reducing energy consumption by means of multiprocessor or multiprocessing based techniques, other than acting upon the power supply
    • Y02D10/22Resource allocation

Abstract

A linkage destination terminal (200) determines cache size for linkage data (503) that can execute a predetermined series of processing tasks, based on the remaining capacity of a battery (201) of the linkage destination terminal (200) and the remaining capacity of a battery (251) of a linkage source terminal (250). The linkage destination terminal (200) caches, in a data storage unit (206), linkage data within the cache size from among the linkage data received from the linkage source terminal (250). When the use of an application is finished, the linkage destination terminal (200) rewrites, in the linkage source terminal (250), the linkage data cached in the data storage unit (206) and also deletes the cached linkage data from the data storage unit (206).

Description

Data linked terminal, data association method and a data association system,

The present invention, by taking over the data related to the application between the terminals, relates to a data linkage terminal using the application seamlessly between terminals, and more particularly, based on the remaining battery level of the data linked terminal, the application data linked terminal and data linkage method for controlling takeover of the associated link data, and to data linkage system including the data linked terminal.

Recently, many users desktop personal computers (hereinafter, referred to as PC), laptop (PC), a tablet PC, a smart phone, mobile phone, and the like, and a plurality own executable information communication terminal various applications, depending on the circumstances They are selectively using these information communication terminal.

Patent Document 1, the data such as an application of the work and the working environment, by passing between terminals, on a different device than the terminal that was using an application (cooperation source terminal) (cooperation destination terminal), continue technology that allows use of the application is disclosed. Specifically, the terminal that was using an application, continuing to another terminal using the application, and sends the link data associated with the application, make temporarily stored on another device (cache). Another terminal, by using the cached data, it is possible to use the application seamlessly.

By the way, this collaboration data, such as when the cooperation source terminal is a smartphone of personalized often include personal information. For example, using a shopping site on the web browser, in many cases to enter personal information such as address and credit card number on the form of the web. In addition, browsing history and bookmarks, etc. of the web browser to be stored at the terminal also, because related to privacy, it can be said that the personal information. Therefore, if the cooperation destination terminal is a terminal shared by multiple users, such as a tablet PC, or the link data is seen to other users, it is necessary, not to be or exploited. For this reason, cooperation destination terminal, after the use of the application, it is necessary to remove the linkage data that has been cached. Moreover, for the user of safety, that the linkage data from the cooperation destination terminal after application usage is removed reliably, it should be able to see in cooperation source terminal.

Also, the cooperation destination terminal newly added to the link data, there is information to be deleted, or updated. For example, web site information and the like were newly registered in the telephone number or bookmarks that you have entered in the form of the web is added. In addition, from the bookmarks, web site information which becomes unnecessary is deleted. Then, browsing history of the browser, last access date and time is updated. Such information, To avoid the possibility of conflict later, after linkage, writing back the link data that have been updated from the cooperation destination terminal linkage based terminal utmost desirable.

Here, consider the case cooperation source terminal and the cooperation destination terminal is a mobile terminal. Usually, since the portable terminal driven by a battery, in processing relating to transfer of the link data, it is necessary to consider the remaining battery amount data linked terminal. This is because, when the battery exhaustion occurs during cooperation, deletion of cooperation data in cooperation destination terminal, is because the write-back of cooperation data of cooperation to the original terminal can not normally.

Therefore, Patent Document 2, source terminal data, based on the remaining battery level of the destination terminal when the battery level of its own terminal, a technique for determining whether to transmit and receive data are disclosed ing. According to this technique, by grasping the battery remaining amount of both the source terminal and the destination terminal, either terminal during data transmission and reception becomes out of batteries, as a result, such data transmission is interrupted it becomes possible to prevent the situation.

JP 2003-242106 JP JP 2008-193173 JP

However, in Patent Document 1 and Patent Document 2, based on the battery remaining amount of the cooperation source terminal and the cooperation destination terminal, reliably remove the linkage data cached in cooperation destination terminal, or back reliably written to cooperation source terminal in view of a technique for determining a cache size of the link data is not disclosed.
Moreover, cooperation destination terminal, especially in the case of the terminal that is shared by multiple users, such as a tablet PC, whether the cached link data after coordination termination is removed reliably, and notifies the cooperation source terminal technology not disclosed.

Therefore, an object of the present invention, in consideration of the written back to delete or cooperation source terminal of the link data in cooperation destination terminal based on the battery remaining amount of the cooperation destination terminal and the collaboration source terminal is cached in cooperation destination terminal data linked terminal and data linkage methods can dynamically determine the size of the link data, and to provide a system including the data linked terminal.
Moreover, a further object of the present invention, cooperation destination terminals that cached link data is deleted securely on, the link data linked terminal and data linkage methods can be notified to the source terminal and the data linked terminal, to provide a system including a.

The present invention is driven by a battery, and receive link data related to the application between the second data linked terminal running the application performs continued use of applications, toward the first data linked terminal It is. In order to achieve the above object, the first data linked terminal of the present invention, a battery remaining amount management unit that manages the remaining amount of the battery, based on the remaining amount of the battery detected by the least remaining battery level managing section Te, the link data identifying unit for identifying the properties of the link data capable of executing predetermined processing with the power consumption of the first data linked terminal, based on the properties of the linkage data specified by the link data identifying unit, the and link data determining unit that determines the properties of the link data for communicating with a second data linked terminal, a communication unit for performing data communication with the second data linked terminal, first via the communication unit 2 a data storage unit that caches link data related to the application received from the data linkage terminal, based on the properties of the link data, linkage data cached in the data storage unit And a cache management unit for managing the cache management unit, at a predetermined timing, cache coordination data communication unit has received on the basis of the property of cooperative data link data determination unit is determined, and a predetermined timing in, and deletes the link data that has been cached in the data storage unit.

In the first data linked terminal, from the first data linked terminal writeback further comprising a management unit for managing the write back data to the second data linked terminal, the communication unit may drive the second data linked terminal the remaining amount of the battery to receive from the cooperation-source data linked terminal, link data identifying unit, and properties of the first linkage data for the first data linked terminal, acquired from the second data linked terminal battery the second data linked terminal related to identifying the properties of the second linkage data based on the remaining amount, link data determination unit, based on the properties of the properties and the second linkage data of the first linkage data, third to determine the properties of the link data, the cache management unit, based on the third link data properties, tubes collaboration data communication unit to be cached in the data storage unit is received And the management unit rewriting, it is desirable to transmit the link data that has been cached in the data storage unit at a predetermined timing to the second data linked terminal.

Typical properties of the linkage data, the size of the link data, type of item of link data, the number of each item of link data, and the remaining amount of viable cells the predetermined processing using the link data of at least 1 One is is. Further, predetermined processing is transmission processing of the link data, the reception processing of the link data writing process of the link data, the process of reading link data, and deletion of the link data is at least one of. The predetermined timing is between the first data linked terminal and the second data linked terminal, the timing for starting the cooperation, the timing of ending the cooperation, timing in coordination, timing after linkage completion, and cooperative before the start timing is at least one of.

Here, that the communication unit cache management unit is cached in the data storage unit deletes the link data received, it is preferable to further comprise a deletion message notification unit for notifying the second data linked terminal.

Further, the present invention is driven by a battery, performs continuous use of the application by sending and receiving link data related to the application between the first data linked terminal to be executed the application, a second data linked terminal It is directed to. In order to achieve the above object, a second data linked terminal of the present invention, the communication for performing data communication with the battery remaining amount management unit that manages the remaining amount of the battery, the first data linked terminal and parts, and a data storage unit for storing the link data associated with at least an application, and a link data management unit for managing the linkage data stored in the data storage unit, the battery remaining amount management unit at a predetermined timing, the battery the remaining amount of the battery detected by the remaining amount management unit transmits the first data linked terminal, link data management unit writes back the link data received from the first data linked terminal.

In the second data linked terminal, based on the notification that the linkage data a second data linked terminal sends cached in the first data linked terminal received from the first data linked terminal is deleted , it may further include a deletion message display unit for displaying a message that has been deleted to the user.

Incidentally, between the first data linked terminal and the second data linked terminal described above, it is possible to construct a data link system which send and receive link data related to the application performing the continued use of the application. Each procedure for data coordination to be executed in the data link system can be regarded as a series of data linkage method.

According to the present invention, based on the battery remaining amount of the cooperation source terminal and the cooperation destination terminal, to determine a cache size of the cooperative data necessary for a given set processing is completed in each of the data linked terminal. Accordingly, since the write back of the link data to remove the cooperation source terminal of the link data in cooperation destination terminal is reliably executed, enable compatibility between security and privacy secure improved convenience and personal information of the user and Become.

Figure 1 is a diagram showing a configuration example of a communication system to which the present invention including the data linked terminal to provide. Figure 2 is a diagram showing an internal configuration of a cooperation destination terminal 200 and the cooperation source terminal 250 constituting the data link system 1 according to a first embodiment of the present invention. Figure 3 is a diagram illustrating a configuration example of a power consumption table 300 the battery level management unit 202 manages. Figure 4 is a diagram illustrating a configuration example of a power consumption table 400 the battery level management unit 252 manages. Figure 5 is a diagram showing a configuration example of a communication data 500 link data management unit 255 generates. Figure 6A is a diagram showing an example of the cooperation source terminal 250 and the cooperation destination terminal 200 and by the data link system 1 overall processing sequence. Figure 6B is a diagram showing an example of a predetermined process relating to the cache size calculation in cooperation source terminal 250 and the cooperation destination terminal 200. Figure 7 is a flowchart showing a procedure of the cache processing of the link data 503 to the cooperation destination terminal 200 is performed. Figure 8 is a flowchart showing a procedure of the cache size calculation processing cooperation data specifying unit 203 performs. Figure 9 is a flowchart showing a write back / deleting process procedure of the link data 503 to the cooperation destination terminal 200 is performed. Figure 10 is a flowchart showing the write-back processing procedure of the link data 503 to the collaboration source terminal 250 is performed. Figure 11 is a flowchart showing a procedure of the cache processing of the link data 503 to the cooperation destination terminal 200 according to Modification 1 is carried out. Figure 12 is a flowchart showing a write back / deleting process procedure of the link data 503 to the cooperation destination terminal 200 according to Modification 1 is carried out. Figure 13 is a flowchart showing a procedure of the cache processing of the link data 503 to the cooperation destination terminal 200 according to Modification 2 is performed. Figure 14A is a diagram showing a configuration example of a communication data 1400 link data management unit 255 according to the modified example 2 is produced. 14B is a diagram showing a configuration example of a communication data 1401 link data management unit 255 according to the modified example 2 is produced. Figure 15 is a flowchart showing a procedure of the cache size calculation process link data identifying section 203 according to Modification 2 is performed. Figure 16 is a diagram showing an example of a predetermined process relating to the cache size calculation in cooperation source terminal 250 and the cooperation destination terminal 200 according to the modification 2. Figure 17 is a flowchart showing the write-back processing procedure of the link data 503 to the collaboration source terminal 250 according to Modification 2 is performed. Figure 18 is a flowchart showing the write-back processing procedure of the link data 503 to the collaboration source terminal 250 according to Modification 3 is performed. Figure 19 is a flowchart showing a write back / deleting process procedure of the link data 503 to the cooperation destination terminal 200 according to Modification 3 is performed. Figure 20 is a diagram showing an internal configuration of a cooperation destination terminal 2000 and the collaboration source terminal 2050 constituting the data link system 2 according to a second embodiment of the present invention. Figure 21 is a diagram illustrating an example of a message 2100 that cooperation source terminal 2050 displays. Figure 22 is a flowchart showing a write back / deleting process procedure of the link data 503 is cooperation destination terminal 2000 performs. Figure 23 is a flowchart showing the write-back processing procedure of the link data 503 is cooperation source terminal 2050 performs.

In the present invention, if the user, a first data linked terminal with the information communication terminal used (hereinafter, the cooperation source terminal and denoted) another second data linked terminal (hereinafter, referred to as the cooperation destination terminal) to switch in, it is assumed that scene also be used to continue with cooperation destination terminal the application that was used in the collaboration source terminal. In such a situation, information such as work content of the application in cooperation source terminal (link data) it is sent to the cooperation destination terminal. Accordingly, work, etc. of the application the user has utilized in collaboration source terminal before switching, is reproduced display on the screen of the cooperation destination terminal.
The present invention is based on the battery remaining amount of the cooperation destination terminal and the collaboration source terminal, and determines the size of the link data capable of executing a series processes in the cooperation destination terminal and cooperation source terminal.

Figure 1 is a diagram showing a configuration example of a communication system to which the present invention including the data linked terminal to provide. In the example of FIG. 1, one user, tablet PC 10, the smart phone 20, and note PC 30, owns a plurality of data linked terminal connectable to the network 40. Then, the user has selectively used these data linked terminal according to the situation. For example, at home using a notebook PC30, at the time of going out to use the tablet PC10 and smartphones 20. In such a communication system, for example, I had been watching the Internet news Web site in the home of the notebook PC30, use that to watch the rest of the news because it was a going out time in the smartphone 20 is assumed. The viewing, for example, had been watching the Internet news of the Web site by using a smart phone 20 while standing in the go train, because sit vacant seat of the news by switching to the tablet PC10 of the big screen more use that is assumed.

Incidentally, usage method described above, of course may be the case the switching direction is reversed. That is, the tablet PC 10, data linkage terminal such as a smart phone 20, and note PC30 is that can become to any cooperation destination terminal using the collaboration source terminal and the link data to provide a link data.
Therefore, in the following embodiments of the present invention, the type of data linked terminal regardless, necessary data linked terminal to function as a cooperation source terminal configuration, the data linkage terminal to function as a cooperation destination terminal required configuration, and cooperative processing performed between the source terminal and the cooperation destination terminal will be described in detail.

<First embodiment>
Figure 2 is a diagram showing an internal configuration of a cooperation destination terminal 200 and the cooperation source terminal 250 constituting the data link system 1 according to a first embodiment of the present invention. Cooperation destination terminal 200, a battery 201, a battery remaining amount management unit 202, the link data identifying section 203, a link data determination unit 204, a communication unit 205, a data storage unit 206, a cache management unit 207, write back and a management unit 208. Collaboration source terminal 250 includes a battery 251, a battery remaining amount management unit 252, a communication unit 253, a data storage unit 254, and a link data management unit 255. Incidentally, the cooperation destination terminal 200 and the collaboration source terminal 250 is essentially a keyboard, a cross key, a button, a mouse, and has an input means such as a touch panel, omitted for these means are not the gist of the present invention to.

First, a description will be given of each component of the cooperation destination terminal 200.
Battery 201 supplies power necessary for the operation of the cooperation destination terminal 200. Battery level management unit 202 manages the remaining amount of the battery 201. Specifically, the battery remaining amount management unit 202, and detect the remaining amount of the battery 201, when the remaining amount of the battery 201 reaches a predetermined value, such as cache management unit 207 and write back management unit 208 to other components, or to notification to that effect. The battery remaining amount management unit 202 manages the power consumption of each process performed in the cooperation destination terminal 200 as a power consumption table. The battery remaining amount management unit 202, power level, based on the voltage level, or the cumulative current level, etc., for detecting the remaining amount of the battery 201.

Figure 3 is a diagram illustrating a configuration example of a power consumption table 300 the battery level management unit 202 manages. The power consumption table 300 is composed of power 302. a processing type 301. Processing type 301 indicates the type of processing performed in cooperation destination terminal 200. In the example of FIG. 3 are performed by the communication unit 205 'receiving "process, the process" write "to the data storage unit 206 to be performed by the cache management unit 207 and write back management unit 208, not shown in FIG. 2 CPU (Central Processing Unit "browser execution" processing performed by) is shown as a process type 301. Power 302 indicates the power consumption of the processing described in process type 301. For example, in "receive" process, the power of 1 watt-hours per byte in the entire cooperation destination terminal 200 [Wh / B] indicates that it is consumed.

In the example of FIG. 3, has been set a power 302 transmission processing performed by the communication unit 205 and the reception processing as one reception processing, may each be set a power 302 individually. Similarly, write processing and performed in the cache management unit 207 and write back management unit 208, the processing in the browser executing performed by the CPU may also set a power 302 and subdivided.

Linkage data specifying unit 203, based on the remaining amount of the battery 251 of the remaining amount or cooperation source terminal 250 of the battery 201, the specific properties of the link data capable of executing predetermined processing in cooperation destination terminal 200 or cooperation source terminal 250 to. As the property of collaboration data, the size of the coordination data, types of items of cooperation data (browser browsing history (URL history of), bookmarks, passwords entered by the user, the user dictionary of the kana-to-kanji conversion application, etc.), items of cooperation data the number of each, viable cells remaining, and the like to predetermined processing using the link data.

For example, link data identifying section 203, when calculating the size of the link data with respect to cooperation destination terminal 200, based on the remaining amount of the battery 201, and caches the link data received from the cooperation source terminal 250, linkage at Federation Termination write data back to the cooperation source terminal 250, it deletes the link data that are cached, and calculates the size of the executable collaboration data series processing called. Further, link data identifying section 203, when calculating the size of the link data with respect to cooperation source terminal 250, based on the remaining amount of the battery 251 obtained from the cooperation source terminal 250, and transmits the link data to the cooperation destination terminal 200 receives link data from the cooperation destination terminal 200 at federation termination, writes the link data received, to calculate the size of the executable collaboration data series processing called.

From the cooperation data determination unit 204 in the link data identifying section 203, and properties of the linkage data specified from the battery remaining amount of the cooperation destination terminal 200, the properties of the link data identified from the battery remaining amount of the cooperation source terminal 250, cooperative cached in the previous terminal 200, it determines the properties of the link data to be written back to the cooperation source terminal 250. For example, cooperation destination terminal 200 size of 1 megabyte linkage data specified from the battery remaining amount of the size of the linkage data specified from the battery remaining amount of the cooperation source terminal 250 is to 0.5 megabytes. 0 In this case, link data determination unit 204 for executing the first series treatment given in both the cooperation destination terminal 200 and the cooperation source terminal 250 to the end, it is smaller the size of the associating data specified. 5 megabytes to determine the size of the final collaboration data.

The communication unit 205 transmits and receives communication data to and from the cooperation source terminal 250 and the cooperation destination terminal 200. The communication unit 205, for example a wireless LAN, a public line, Bluetooth wireless communication or by (registered trademark), and ZigBee / IEEE 802.15.4 or the like, by a wired communication by a wired LAN or the like, connected to the network 40 shown in FIG. 1 . Further, in a cooperation source terminal 250 and the cooperation destination terminal 200 may communicate in a peer-to-peer.

Data storage unit 206, the collaboration source terminal 250 stores link data or the like received from (cache) to the hard disk drive for non-volatile memory such as a flash memory, and a volatile memory such as a RAM (Random Access Memory).

Cache management unit 207 manages the linkage data cached in the data storage unit 206. Specifically, the cache management unit 207 manages the property of the link data to be cached in the data storage unit 206. The cache management unit 207 performs relative linkage data caching, add, delete, and update the like. For example, property in the case of bookmarks used by the Web browser, or re-register or add the URL of the new web site (Uniformed Resource Locator), or delete the registered URL, the URL is changed, operation that can be mentioned. In addition, in the case property is browsing history of the browser, or is additional URL information, and the like of the newly browsing the site, the last access date and time of viewing already-site or is updated, operation and the like that. In addition, the property is in the case of cokkie, or to record the cokkie of newly browsing the site, or to update the cokkie that is included on the link data, operation of, and the like.

The write-back management unit 208, like in the case where a cooperation destination terminal 200 and the cooperation source terminal 250 finishes the cooperative performs processing of writing back the link data that are cached in the data storage unit 206 in cooperation source terminal 250. Specifically, the write-back control section 208, at the timing when writing back link data, all or part of the link data that are cached in the data storage unit 206, in order to write back to the cooperation source terminal 250, the communication unit and passes to 205.

Next, the description will be given of respective components of the cooperation source terminal 250.
Battery 251 supplies power necessary for the operation of the cooperation source terminal 250. Battery level management unit 252 manages the remaining amount of the battery 251. Specifically, the battery remaining amount management unit 252, and detect the remaining amount of the battery 251, when the remaining amount of the battery 251 reaches a predetermined value, the other components such as link data management unit 255 , or notification to that effect. The battery remaining amount management unit 252 manages the power consumption of each process performed in cooperation source terminal 250 as a power consumption table. The battery remaining amount management unit 252, like the remaining battery capacity managing unit 202, based on the power level, voltage level, or the cumulative current level, etc., for detecting the remaining amount of the battery 251. Figure 4 is a diagram illustrating a configuration example of a power consumption table 400 the battery level management unit 252 manages. The power consumption table 400, like the power consumption table 300 described above, and a power consumption 302. a processing type 301.

Communication unit 253, similar to the communication unit 205 of the cooperation destination terminal 200, to transmit and receive communication data to and from the cooperation source terminal 250 and the cooperation destination terminal 200.
Data storage unit 254, like the data storage unit 206 of the cooperation destination terminal 200, a hard disk drive for storing link data or the like, a nonvolatile memory, and volatile memory such as a RAM such as a flash memory.

Cooperation data management unit 255, to manage the cooperation data. Further, link data management unit 255 transmits to the cooperation destination terminal 200, generates the communication data including at least the link data. Further, link data management unit 255 writes back the link data included in the communication data received from the cooperation destination terminal 200 at linkage ends in the data storage unit 254.

Figure 5 is a diagram showing a configuration example of a communication data 500 link data management unit 255 generates. The communication data 500, the battery level 501, the power consumption table 502, and a link data 503.
Battery level 501 is the remaining battery 251 detected by the battery remaining amount management unit 252. Link data management unit 255, the remaining amount of the battery 251 at the time of generation of the communication data 500, obtained from the battery remaining amount management unit 252 sets the battery level 501. The power consumption table 502, power consumption table 400 the battery level managing unit 252 manages (Figure 4) is set. Link data management unit 255 acquires the power consumption table 400 from the battery remaining amount management unit 252, sets the power consumption table 502. Link data 503 is data used for linking various applications with the cooperation destination terminal 200 and the cooperation source terminal 250. In the example of FIG. 5 shows the size, URL history, bookmark, the user password, the link data 503 including the user dictionary, and the input form information and the like.

Next, with reference to sequence diagrams and flowcharts to FIG 10. FIG 6A, cooperation destination terminal 200, based on the battery remaining amount of the cooperation destination terminal 200 and the cooperation source terminal 250, determines the size of the link data to be cached processing will be described.
First, with reference to FIG. 6A, the cooperation source terminal 250 and the cooperation destination terminal 200 in the first embodiment uses the application to seamlessly work together explaining a data link system 1 overall processing sequence.

Collaboration source terminal 250 transmits a cooperative start request to the cooperation destination terminal 200 (S601). Cooperation destination terminal 200 receives the cooperation start request cooperation source terminal 250 enters a reception waiting state of the link data (S602). Collaboration source terminal 250, after transmitting the cooperation start request, transmits the link data to the cooperation destination terminal 200 (S603). Cooperation destination terminal 200 receives the link data from the cooperation source terminal 250 (S604), based on the battery remaining amount of the cooperation source terminal 250 when the battery level of its own terminal, the link data to be cached in the data storage unit 206 size (hereinafter referred to as cache size, and so on) to determine (S605). In this example, the cooperation destination terminal 200 receives together with the linkage data a remaining battery level of cooperation source terminal 250. The cooperation destination terminal 200 caches the link data of the determined by the cache size of the data storage unit 206 (S606), using the various applications of using the link data cached (S607).

Cooperation destination terminal 200, etc. to end the use of the application, to end the cooperation with cooperation source terminal 250 transmits a coordination termination request to the cooperation source terminal 250 (S608). Collaboration source terminal 250 receives the federation termination request from the cooperation destination terminal 200 enters a reception waiting state of the link data (S609). Cooperation destination terminal 200, after transmitting the coordination termination request, in order to write back the link data, and sends the link data to the cooperation source terminal 250 (S610). Collaboration source terminal 250 receives the link data from the cooperation destination terminal 200 (S611), the link data received back into the data storage unit 254 (S612). Thereafter, cooperation destination terminal 200 deletes the link data that are cached in the data storage unit 254 (S613).

Incidentally, in FIG. 6A, cooperation destination terminal 200, upon receiving the cooperation start request from the cooperation source terminal 250 (S602), may be returned a response to the cooperation source terminal 250. Accordingly, collaboration source terminal 250, after confirming the reception of this response, the link data can be sent to (S603), an efficient coordination can be achieved. Moreover, collaboration source terminal 250, upon receiving the coordination termination request from the cooperation destination terminal 200 (S609), may be returned a response to the cooperation destination terminal 200. Thus, cooperation destination terminal 200, after confirming the reception of this response, the link data can be sent to (S610), an efficient coordination can be achieved.

Hereinafter Furthermore, among the sequence processing shown in FIG. 6A, a focus of the present invention, the write back / cache removing processing and the link data 503 of the link data 503 performed by the cooperation destination terminal 200, and cooperate with source terminal 250 the rewriting process of the link data 503 to be performed, will be described in detail.

First, with reference to the flowchart shown in FIGS. 7 and 8, illustrating the caching of link data 503 cooperation destination terminal 200 is performed.
First, the battery remaining amount management unit 202 obtains the remaining battery level Pr1 of the cooperation destination terminal 200 by detecting the remaining amount of the battery 201 (S701), and passes to the cache manager 207. Cache management unit 207 passes the remaining battery capacity Pr1 on the link data identifying section 203, an instruction to identify the cache size based on the remaining battery level Pr1. Linkage data specifying unit 203, based on the remaining battery level Pr1, identifies the cache size Sc1 in later-described technique (S702). Cache management unit 207 acquires and stores the cache size Sc1 the link data identifying section 203 specified.

Next, the cache management unit 207 via the communication unit 205, receives communication data 500 from the communication unit 253 of the cooperation source terminal 250 (S703). The communication data 500 (FIG. 5), battery level Pr2 for cooperation source terminal 250 is a remaining amount of the battery 251, power consumption table 400 the battery level managing unit 252 manages (Figure 4), the link data 503 size St of are included. Cache management unit 207 transfers the size St linkage data 503 to the linkage data determination unit 204. Link data determination unit 204 stores the size St collaboration data 503 acquired.

Next, the cache management unit 207 passes the remaining battery power Pr2 included in the communication data 500 to the linkage data specifying unit 203 and the power consumption table 400, an instruction to identify the cache size based on the battery remaining amount Pr2. Linkage data specifying unit 203 obtains the remaining battery capacity Pr2 from the cache management unit 207 (S704), based on the remaining battery level Pr2, identifies the cache size Sc2 in later-described technique (S705). Cache management unit 207 acquires and stores the cache size Sc2 the link data identifying section 203 specified.

Next, the cache management unit 207 transfers the cache size Sc1 and cache size Sc2 stored on the link data determination unit 204. Link data determination unit 204 compares the cache size Sc1 and cache size Sc2 (S706), to determine the appropriate value as a cache size of the link data. Specifically, link data determination unit 204, when the cache size Sc2 is cache size Sc1 above (S706: YES) determines the cache size Sc1 as cache size Sc (S707), the size cache size Sc2 cache Sc1 is less than (S706: NO), determines the cache size Sc2 as cache size Sc (S 708). This decision method, a predetermined sequence processing in both the cooperation source terminal 250 and the cooperation destination terminal 200 can perform.

Next, link data determination unit 204 work together to all data link data 503 received from the source terminal 250 to determine whether cacheable, the cache size Sc determined, the link data 503 stored comparing the size St of (S709). The link data determination unit 204, when the cache size Sc is equal to or larger than the size St of the link data 503 (S709: YES) instructs the cache management unit 207 to cache all the link data 503. In response to this instruction, the cache management unit 207 stores all the link data 503 to the data storage unit 206 (S710). On the other hand, cooperation data determination unit 204, when the cache size Sc is less than the size St of the link data 503 (S709: NO) instructs the cache management unit 207 to cache some of the data of the link data 503. In response to this instruction, the cache management unit 207, a part of the data in an amount within the range of cache size Sc of the link data 503 is stored in the data storage unit 206 (S711).

Note that, in step S711, whether to cache data link data 503 throat are considered several methods. For example, a method to be assigned beforehand priority user setting or the like (priority frequently used bookmarks, etc.) and, in the method (100 items evenly reduce the amount of data to be cached for each item bookmarks, 34 200 the browser browsing history, etc.) and to halve each, such as how to prioritize the data access to the most recently considered.

Next, a description will be given cache size calculation process performed in step S702 and S705 of FIG. Figure 8 is a flowchart showing a procedure of the cache size calculation processing cooperation data specifying unit 203 performs.

Referring to FIG. 8, first, the link data identifying section 203, the target terminal is a target of the cache size calculated to identify whether the cooperation source terminal 250 or a cooperation destination terminal 200 (S801). Particular the target terminal, for example, such as by acquiring identification information capable target terminal at the timing of receiving the instruction cache size is calculated from the cache management unit 207 can be performed. The linkage data specifying section 203, if the target terminal is "cooperation destination terminal" (S801: YES), acquires the power consumption table 300 of the cooperation destination terminal 200 from the cache management unit 207 (S802), the target terminal If "cooperation source terminal" (S801: NO), obtains the power consumption table 400 of the cooperation source terminal 250 from the cache management unit 207 (S806).

If the target terminal is cooperator terminal 200 (S801: YES), the link data identifying section 203, and a battery level Pr1 acquired from the cache management unit 207 power consumption table 300. A predetermined in cooperation destination terminal 200 series process calculates the cache size Sc1 cooperation data executable (S803). The method of calculating the cache size Sc1, will be described in detail with reference to Figure 6B.

6B is in the overall processing sequence shown in FIG. 6A, after the processing (S605) for cooperation destination terminal 200 determines the cache size of the cooperative data, collaboration source terminal 250 and the cooperation destination terminal 200 and a predetermined be executed and processing, illustrates the amount of power required to run the process. 6B, the power consumption 302 of "reception" process of cooperation destination terminal 200 as "pt1", power consumption 302 of the "write" process of cooperation destination terminal 200 as a "prw1", in collaboration cooperation destination terminal 200 is set to "Pm1" the battery level is below the necessary level to the "browser execution" of. At this time, as shown in FIG. 6B, predetermined processing cooperation destination terminal 200 to be executed is the following four.
(A) the link data 503 read out write processing (c) the link data 503 to cache the data storage unit 206 from the data storage unit 206 processes (d) a process of transmitting the link data 503 to the cooperation source terminal 250 (e) link data 503 writing process also deleted from the data storage unit 206, processing (b) is a margin for the battery residual quantity required for the user to use the browser in cooperation.

From these processes, the sum TOTAL amount of power consumption from the processing (a) shown in FIG. 6B to process (e) is obtained by the following formula [1].
TOTAL = (prw1 × Sc1) × 3 + (pt1 × Sc1) + Pm1 ... [1]
Therefore, cache size Sc1, when organizing the formula [1] by replacing the sum TOTAL of the power consumption in the battery remaining amount Pr1, is obtained by the following formula [2].
Sc1 = (Pr1-Pm1) / (prw1 × 3 + pt1) ... [2]

In the example shown in Figure 6B, is not considered the power consumption for the transmission of the cooperation termination request, the coordination termination request probably because the data size is smaller than the link data itself, less impact on the power consumption , here they are omitted for the sake of simplicity. However, if the effect is not negligible, for example by taking into account the power consumption for the transmission of the cooperation termination request is considered a separate process, such as to consider as a margin. The battery remaining amount Pm1 can be freely set, for example, may be a pre-determined amount by the user setting and system setting, etc., in amounts that are dynamically calculated based on the frequency of use such as the user's application good.

Referring again to FIG. 8, then linkage data specifying unit 203 obtains the necessary battery remaining amount Pc1 used to detect the timing to execute the write back / deleting process link data 503 in cooperation destination terminal 200 (S804). The required battery level Pc1 is calculated by the processing sum of (c) ~ (e) "(prw1 × 2 + pt1) × Sc1". Link data identifying section 203 passes the necessary battery remaining amount Pc1 that the calculated remaining battery power management unit 202. Then, the battery remaining amount management unit 202 stores the required battery level Pc1.

On the other hand, if the target terminal is a cooperation source terminal 250 (S801: NO), the link data identifying section 203, and a battery level Pr2 acquired from the cache management unit 207 power consumption table 400., in cooperation source terminal 250 a given set processing to calculate the cache size Sc2 cooperation data executable (S807). The method of calculating the cache size Sc2, again described in detail with reference to Figure 6B.

6B, the power consumption 302 of "reception" process of cooperation source terminal 250 as a "pt2", power consumption 302 of the "write" process of cooperation source terminal 250 is set to "prw2". At this time, as shown in FIG. 6B, predetermined processing cooperation source terminal 250 to be executed are the following two.
(F) receiving the link data 503 from the cooperation destination terminal 200 processes (g) cooperative writing process of writing back data 503 to the data storage unit 254

From these processes, the sum TOTAL amount of power consumption of the processing shown in FIG. 6B (f) and processing (g) is obtained by the following formula [3].
TOTAL = (pt2 × Sc2) + (prw2 × Sc2) ... [3]
Therefore, cache size Sc2, when organizing the formula [3] by replacing the sum TOTAL of the power consumption in the battery remaining amount Pr2, be calculated using the following expression [4].
Sc2 = Pr2 / (pt2 + prw2) ... [4]

In the example shown in Figure 6B, is not considered the power consumption for reception of coordination termination request, the coordination termination request probably because the data size is smaller than the link data itself, less impact on the power consumption , here they are omitted for the sake of simplicity. However, if the effect is not negligible, for example by taking into account the power consumption for the transmission of the cooperation termination request is considered a separate process, such as to consider as a margin. Also, as in the case of cooperation destination terminal 200, taking into account the battery level Pm2 needed to run the application or the like in cooperation source terminal 250 in cooperation with the molecules of the above formula [4] as "Pr2-Pm2" it may be. In this case, and how to include the remaining battery level Pm2 in communication data 500, by separately purchase collaboration source terminal 250 the types of applications that may be executed in such in cooperation, the remaining battery level Pm2 using power consumption table 400 a method in which the calculation is considered.

Further, in the process in FIG. 6B (g), it overwrites and updates the link data 503 stored in the data storage unit 254, i.e., shows a case in which only the writing process. However, if such updating the link data 503 partially, once after performing read, it is necessary to process of writing again. Therefore, in this case, the process (g) the power consumption required can be calculated as "(prw2 × Sc2) × 2".

Next, with reference to FIG. 9, illustrating a write back / deleting process link data 503 cooperation destination terminal 200 performs in the first embodiment.
First, write-back management unit 208, the battery remaining amount management unit 202 is instructed to perform a write back process to monitor the remaining amount of the battery 201. Battery level management unit 202, based on this instruction, obtains the necessary battery remaining amount Pc1 and battery level Pr1 of the current cell 201 (S901, S902). Then, the battery remaining amount management unit 202, the remaining amount difference D1 between the battery level Pr1 required battery level Pc1 (= Pr1-Pc1) determines whether more than a predetermined value δ1 (S903). This determination remaining battery level Pr1 is performed in order to detect a little before the time of reaching the minimum required battery level Pc1 for cooperation destination terminal 200 executes a write back / deleting process link data . Therefore, as long as the method this end, it may be performed other determination. The predetermined value δ1 can be freely set by the system or the like.

If the remaining amount difference D1 while monitoring the battery 201 determines the battery remaining amount management unit 202 has reached the predetermined value or less δ1 (S903: YES), the write-back management unit 208, data collaboration data caching from the storage unit 206 (S904). The management unit 208 writes back, via the communication unit 205, and transmits the read link data in cooperation source terminal 250 (S905). Then, write-back management unit 208 deletes the link data that are cached in the data storage unit 206 (S906). The present deletion process may be executed after completion of the write back process of the link data in cooperation source terminal 250. In this case, it is preferable to be notified of the write back completion of processing the link data from the cooperation source terminal 250.

Finally, with reference to FIG. 10, for explaining the rewriting process of the link data 503 to the collaboration source terminal 250 is performed in the first embodiment.
First, the battery remaining amount management unit 252 detects the battery remaining amount Pr2 battery 251 (S1001), passes the remaining battery capacity Pr2 detected on the link data management unit 255. Next, link data management unit 255 acquires the power consumption table 400 the battery level managing unit 252 manages (S1002). Next, link data management unit 255 reads the link data 503 stored in the data storage unit 254 (S1003). Link data management unit 255, a battery level Pr2, since the power consumption table 400 acquired the read link data 503 and (size St), to generate the communication data 500. The link data management unit 255 via the communication unit 253 transmits the communication data 500 including the link data 503 size St in cooperation destination terminal 200 (S1004). Further, link data management unit 255, the communication unit 253, and instructs the reception waiting of the link data 503 is written back from the cooperation destination terminal 200.

The communication unit 253, when the linkage destination terminal 200 receives the link data 503 while continuing the reception waiting of the link data (S1005: YES, S1006), passes the link data 503 received on the link data management unit 255. Link data management unit 255 writes back the link data 503 acquired (S1007), that is, updated with the link data 503 acquired the link data 503 stored in the data storage unit 254. As a result, the write-back process of cooperation data 503 is completed. Even when not receiving the link data 503 from the cooperation destination terminal 200, when the reception waiting by the communication unit 253 is stopped (S1005: NO), the write-back process is terminated.

As described above, according to the data link system 1 according to a first embodiment of the present invention, in consideration of the respective battery remaining amount of the cooperation destination terminal 200 and the cooperation source terminal 250, to the cache by the cooperation destination terminal 200 cooperative the size of the data is dynamically determined. Thus, it is possible to reliably execute a predetermined series treated with both the cooperation source terminal 250 and the cooperation destination terminal 200. Therefore, when the cooperative applications between data linked terminal, and comfort of the operation by the cache collaboration data, the security and privacy secure personal information, it is possible to achieve both.

(Modification 1 of the first embodiment)
In caching of link data 503 in cooperation destination terminal 200 shown in FIG. 7, it has been described a case where the size of the link data to be cached, and the size of the link data to be written back to the cooperation source terminal 250 matches.
In the first modification, the case where the size of both the linkage data are different. It should be noted that, as the size of the cooperation data is different scene, for example if you want to add on the link data 503 that caches the bookmark information and browser input form data, and the like can be considered.

In the first modification, the cache processing of the link data 503 shown in FIG. 7 is executed according to the flowchart shown in FIG. 11. Also, write back / deleting process link data 503 shown in FIG. 9 is executed according to the flowchart shown in FIG. 12. Note that in FIG. 11 and FIG. 12, the steps of executing the same processes as in FIG. 7 and FIG. 9 is omitted are denoted by the same reference numerals.

First, with reference to FIG. 11, illustrating the caching of link data 503 cooperation destination terminal 200 is performed. Processing of steps S701 ~ S 708 in FIG. 11 is the same as the processing in FIG.
When the cache size Sc is determined, cooperative data determination unit 204 acquires the value of the size Sa of the cache increase stored in advance (S1108). The size Sa, it is possible to use a preset value such as user settings and system settings, and the like. Link data determination unit 204, all the data in order to determine whether cacheable, determined value obtained by subtracting the size Sa of the cache increase the cache size Sc of link data 503 received from the cooperation source terminal 250 " and sc-Sa "is compared with the size St collaboration data 503 stored (S1109). The link data determination unit 204, when the value "Sc-Sa" is equal to or larger than the size St (S709: YES) instructs the cache management unit 207 to cache all the link data 503, a value "Sc- If Sa "is less than the size St (S709: NO) instructs the cache management unit 207 to cache some of the data of the link data 503.

In this modified example 1, it did not consider the case where the Sa ≧ Sc. However, if the Sa ≧ Sc, without caching cooperation destination terminal 200 in the link data 503, and the method of obtaining the link data 503 from each time collaboration source terminal 250, so as not to consider the size Sa of the cache increase method for processing in the like can be considered.

Next, with reference to FIG. 12, for explaining the write back / deleting process link data 503 cooperation destination terminal 200 is performed.
Write back management unit 208, the battery remaining amount management unit 202 is instructed to perform a write back process to monitor the remaining amount of the battery 201. Battery level management unit 202, based on this instruction, need battery level Pc1, cache size Sc, and obtains the remaining battery level Pr1 of the current cell 201 (S901, S1201, S902). Then, the battery remaining amount management unit 202 determines the remaining amount difference D1 between the battery level Pr1 required battery level Pc1 (= Pr1-Pc1) is whether exceeds a predetermined value δ1 (S1202). The predetermined value δ1 is the same as the value described in step S903.

If the remaining amount difference D1 while monitoring the battery 201 determines the battery remaining amount management unit 202 that exceeds a predetermined value δ1 (S1202: YES), write-back management unit 208, the cache management unit 207, currently cached to get the cache size Scp of cooperation data 503 are (S1203). Then, the write-back management unit 208, the value "Sc-Scp" determines whether more than a predetermined value Δ1 (S1204). This determination is cache size Scp collaboration data 503 that is currently cached, is for detecting a bit before the time when the cache size is reached Sc which is the upper limit of the cache size. Therefore, as long as the method this end, it may be performed other determination. The predetermined value Δ1 can be set freely in the system or the like. On the other hand, if the remaining amount difference D1 while monitoring the battery 201 determines the battery remaining amount management unit 202 when not exceed a predetermined value δ1 (S1202: NO), the write-back control section 208, the cooperative linkage data 503 yuan terminal processing for writing back to 250 (S904 ~ S906) performed.

If the value "Sc-Scp" is determined to exceed the predetermined value Δ1 (S1204: YES), the battery remaining amount management unit 202 to continuously monitor the remaining amount of the battery 201, the remaining battery power Pr1 It instructs the battery remaining amount management unit 202 to acquire (S902). On the other hand, if the value "Sc-Scp" is determined to have fallen below a predetermined value Δ1 (S1202: NO), write-back management unit 208, the write-back management unit 208 writes back the link data 503 to the cooperation source terminal 250 process (S904 ~ S906) is carried out for.

According to the first modification of the first embodiment, even if the link data 503 in cooperation destination terminal 200 as data is added, it is possible to obtain the effects described in the first embodiment .

(Modification 2 of the first embodiment)
In caching of link data 503 in cooperation destination terminal 200 shown in FIG. 7, after the cooperation destination terminal 200 receives the link data 503 from the cooperation source terminal 250 has been described a case of determining the cache size.
In the second modification, cooperation destination terminal 200, before receiving the link data 503, describing a method of specifying in advance the size of the link data 503 to obtain relative collaboration source terminal 250.

In the second modification, the cache processing of the link data 503 shown in FIG. 7 is executed according to the flowchart shown in FIG. 13. The cache size calculation process shown in FIG. 8 is executed according to the flowchart shown in FIG. 15. Further, the entire processing sequence shown in FIG. 6B is performed by the sequence shown in Figure 16. Furthermore, write-back processing of the cooperative data 503 shown in FIG. 10 is executed according to the flowchart shown in FIG. 17.

First, with reference to FIG. 13, a cache processing of the link data 503 to the cooperation destination terminal 200 is performed. Processing in steps S701 and S706 ~ S 708 in FIG. 13 is the same as the processing in FIG.
Linkage data specifying unit 203, based on the remaining battery level Pr1 acquired in step S701, the calculated cache size Sc1 in later-described method (S1302). Cache management unit 207 acquires and stores the cache size Sc1 to link data identifying section 203 is calculated, via the communication unit 205, receives communication data 1400 from the communication unit 253 of the cooperation source terminal 250 (S1303) . The communication data 1400 (FIG. 14A) is cooperative battery level 501 battery level Pr2 is set to source terminal 250, and the battery remaining amount management unit 252 power consumption table 400 managed (FIG. 4) is set it includes power consumption table 502. Cache management unit 207 passes the remaining battery power Pr2 on the link data identifying section 203 and the power consumption table 400, an instruction to calculate the cache size based on the battery remaining amount Pr2. Linkage data specifying unit 203 obtains the remaining battery capacity Pr2 from the cache management unit 207 (S1304), based on the remaining battery level Pr2, calculates the cache size Sc2 in later-described method (S1305). Cache management unit 207 acquires and stores the cache size Sc2 to link data identifying section 203 is calculated.

When the cache size Sc1 and Sc2 are calculated, link data determination unit 204 determines the appropriate cache sizes Sc (S706 ~ S708). Link data determination unit 204 sends the cache size Sc that this decision cache management unit 207. Cache management unit 207 via the communication unit 205 transmits the cache size Sc in cooperation source terminal 250 (S1308). Thereafter, the communication unit 205 enters a standby state for receiving the link data 503 from the cooperation source terminal 250. Then, the cache management unit 207 via the communication unit 205 receives the communication data 1401 including the link data 503 (S1309), and acquires the link data 503 from the communication data 1401 to cache the data storage unit 206 (S1310 ). An example of the communication data 1401 in FIG. 14B.

In this second modification, cooperation destination terminal 200, because it specifies the cache size Sc of link data 503 in advance with respect to cooperation source terminal 250, typically of link data 503 received from the cooperation source terminal 250 size is equal to or less than the cache size Sc. However, if to accommodate even when receiving the link data 503 of a larger size than the cache size Sc, in cooperation destination terminal 200, the size of the link data 503 to cache, so as to provide a process of limiting the cache size Sc it may be. When performing this process, for the multiple ways on how to cache any data in the cooperative data 503, as described above.

Next, with reference to FIGS. 15 and 16, illustrating the cache size calculation process performed by the link data identifying section 203.
15, if the target terminal is a cooperation destination terminal 200 (S801: YES), the link data identifying section 203, and a battery level Pr1 acquired from the cache management unit 207 power consumption table 300., cooperation destination terminal 200 predetermined processing to calculate the cache size Sc1 viable link data in conjunction with (S1503), obtains the necessary battery level Pc1 (S804). The method of calculating the cache size Sc1, will be described in detail with reference to FIG. 16.

16, collaboration source terminal 250, after transmitting the cooperation start request, transmits the battery remaining amount to the cooperation destination terminal 200 (S621). Cooperation destination terminal 200 receives battery power from the cooperation source terminal 250 (S622), based on the battery remaining amount of the cooperation source terminal 250 when the battery level of its own terminal, to determine the size of the linkage data to be received (S605). The cooperation destination terminal 200 transmits the determined size to the cooperation source terminal 250 (S623). Collaboration source terminal 250 receives the size (S624), and transmits the following link data size to the cooperation destination terminal 200 (S603). Processing of steps S606 ~ S613 and later are the same as FIG. 6A.

As shown in FIG. 16, predetermined processing cooperation destination terminal 200 to be executed after the processing (S605) for determining a cache size of the link data are the following five.
(H) cooperative reading process of receiving from the cooperation source terminal 250 to data 503 (a) the link data 503 write processing (d) the link data 503 to cache the data storage unit 206 from the data storage unit 206 processes (e) the link data 503 the cooperative process of transmitting to the source terminal 250 (f) writing deletes the link data 503 from the data storage unit 206 processes, process (b), the battery level necessary for the user to use the browser in cooperation which is the margin.

From these processes, the sum TOTAL amount of power consumption of the process shown in FIG. 16 (a) ~ (e) and (h) is obtained by the following formula [5].
TOTAL = (prw1 × Sc1) × 3 + (pt1 × Sc1) × 2 + Pm1 ... [5]
Therefore, cache size Sc1, when organizing the formula [5] by replacing the sum TOTAL of the power consumption in the battery remaining amount Pr1, is calculated by the following formula [6].
Sc1 = (Pr1-Pm1) / (prw1 × 3 + pt1 × 2) ... [6]

On the other hand, if the target terminal is a cooperation source terminal 250 (S801: NO), the link data identifying section 203, and a battery level Pr2 acquired from the cache management unit 207 power consumption table 400., in cooperation source terminal 250 predetermined processing to calculate the cache size Sc2 cooperation data executable (S1507). The method of calculating the cache size Sc2, again described in detail with reference to FIG. 16.

As shown in FIG. 16, predetermined processing to be executed cooperation source terminal 250 is one of the following three.
(I) cooperative processing of transmitting the data 503 to the cooperation destination terminal 200 (f) receiving the link data 503 from the cooperation destination terminal 200 processes (g) cooperative writing process of writing back data 503 to the data storage unit 254

From these processes, the process shown in FIG. 16 (f), (g), and the power consumption of the total sum TOTAL of (i) is obtained by the following formula [7].
TOTAL = (pt2 × Sc2) × 2 + (prw2 × Sc2) ... [7]
Therefore, cache size Sc2, when organizing the formula [7] by replacing the sum TOTAL of the power consumption in the battery remaining amount Pr2, obtained by the following formula [8].
Sc2 = Pr2 / (pt2 × 2 + prw2) ... [8]

Also in the example shown in FIG. 16, as described with reference to FIG. 6B, if the power consumption for reception of the reception and coordination termination request size link data can not be ignored, such as an application in cooperation source terminal 250 when considering battery level Pm2 required to run, the other aspects in the case of such updating the link data 503 partially, can be applied.

Next, with reference to FIG. 17, for explaining the rewriting process of the link data 503 to the collaboration source terminal 250 is performed. The process of step S1001, S1002, and S1005 ~ S1007 in FIG. 17 is the same as the processing in FIG. 10. Link data management unit 255, using the communication data 1400 shown in FIG 14A, the power consumption table 400 and battery level Pr2, via the communication unit 253 to the cooperation destination terminal 200 (S1703). The link data management unit 255, the communication unit 253, and instructs the data reception wait from the cooperation destination terminal 200. The communication unit 253, based on the data reception wait instruction from the cooperation destination terminal 200, enters the data reception wait state.

The communication unit 253, when the linkage destination terminal 200 receives the cache size Sc while continuing the data reception wait (S1704: YES, S1705), the link data management unit 255 transfers the cache size Sc. Link data management unit 255 reads the link data of the following sizes cache size Sc from the data storage unit 254 (S1706). Note that the read or which data of the link data is as described above. In addition, from the cooperation destination terminal 200, way to ask them to specify the read or which items may be considered. On the other hand, from the cooperation destination terminal 200 a case of not receiving the cache size Sc, the reception waiting by the communication unit 253 is stopped (S1704: NO), the write-back process is terminated.

Link data management unit 255, read from the data storage unit 254, the link data 503 in the cache size Sc following size Sf, via the communication unit 253 to the cooperation destination terminal 200 (S1707). The link data management unit 255, the communication unit 253, and instructs the data reception wait from the cooperation destination terminal 200. The communication unit 253, based on the data reception wait instruction from the cooperation destination terminal 200 enters a reception waiting state of the link data 503. Processing subsequent in this state is as described above (S1005 ~ S1007).

According to the second modification of the first embodiment, with respect to cooperation source terminal 250 from the cooperation destination terminal 200, it is possible to specify the size and settings of link data 503 in advance, between data linked terminal efficiency in cooperation the application is improved.

(Modification 3 of the first embodiment)
In rewriting process of link data 503 shown in FIG. 10, collaboration source terminal 250, after the transmission of the link data 503 to the cooperation destination terminal 200, and it waits to receive the link data 503 for writing back. However, cooperation by the original in the terminal 250 on a task that runs in the background conditions and the battery 251 state, the battery remaining amount Pr2 is thought be fewer earlier than expected. As a result, before the write-back of cooperation data 503 is completed, a situation that becomes a dead battery is assumed.
In the third modification, in order to cope with such a situation, if the linkage at the source terminal 250 monitors the remaining amount of the battery 251, reaches the battery level required for write back link data 503, cooperation destination terminal 200 the method of transmitting a write back request for the link data 503 will be described with respect.

In the third modification, the write-back process of the link data 503 shown in FIG. 10 is executed according to the flowchart shown in FIG. 18. Also, write back / deleting process link data 503 shown in FIG. 9 is executed based on the flowchart shown in FIG. 19. Note that, in FIGS. 18 and 19, the steps of executing the same processes as FIG. 10 and FIG. 9 is omitted are denoted by the same reference numerals.

First, with reference to FIG. 18, for explaining the rewriting process of the link data 503 to the collaboration source terminal 250 is performed. Processing of steps S1001 ~ S1004 and S1005 ~ S1007 in FIG. 18 is the same as the processing in FIG. 10.
Link data management unit 255 via the communication unit 253 transmits the communication data 500 including the size St linkage data to the cooperation-destination terminal 200 (S1004). Further, link data management unit 255, the communication unit 253, and instructs the reception waiting of the link data 503 is written back from the cooperation destination terminal 200. Then, link data management unit 255 calculates the remaining battery capacity Pc2 required before writeback link data 503 received from the cooperation destination terminal 200 is completed (S1805). The required battery level Pc2, using the size St of the link data 503 and power consumption table 400 is calculated by the Pc2 = (pt2 + prw2) × St. Calculated required battery remaining amount Pc2 is passed to the battery remaining amount management unit 252, it is stored.

In this modification 3, for simplicity, calculates the required battery level Pc2 collaboration data 503 is written back from the cooperation destination terminal 200 on the assumption that the size St. However, coordination than the size of the link data transmitted from the source terminal 250, if it is conceivable size of the link data written back from the cooperation destination terminal 200 is large. In this case, the cooperation source terminal 250, upon reception in advance an upper limit such as the size itself or the size of the link data written back from the cooperation destination terminal 200, it is necessary to calculate the required battery level Pc2.

When the communication unit 253 receives the link data 503 from the cooperation destination terminal 200 while continuing the reception waiting of the link data (S1005: YES, S1006), the link data management unit 255 writes back the link data 503 (S1007). As a result, the write-back process of cooperation data 503 is completed. Meanwhile, the communication unit 253, if there is no reception of the link data (S106: NO), determines whether the untransmitted requests written back to the cooperation destination terminal 200 (S1808). If writeback to the cooperation destination terminal 200 requests has not been transmitted (S1808: YES), the communication unit 253, the battery remaining amount management unit 252, and instructs to acquire the battery residual quantity Pr2 battery 251. Then, the battery remaining amount management unit 252 obtains the remaining battery capacity Pr2 (S1809).

Battery level management unit 252, the remaining amount difference D2 between the battery level Pr2 require battery level Pc2 (= Pr1-Pc1) determines whether or not a predetermined value δ2 below (S1810). This determination is the battery remaining amount Pr2 is performed in order to detect a little before the time of reaching the minimum required battery level Pc2 for cooperation source terminal 250 performs a write back / deleting process link data . Therefore, as long as the method this end, it may be performed other determination. The predetermined value δ2 can be freely set by the system or the like.

If the remaining amount difference D2 in the monitoring of the battery 251 is determined residual battery management unit 252 has reached the predetermined value or less δ2 (S1810: YES), the link data management unit 255, the communication unit 253 requests writeback through to send to the cooperation destination terminal 200 (S1811). Incidentally, while the communication unit 253 continues the reception waiting collaboration data from the cooperation destination terminal 200 until it receives the link data 503, the steps S1808 ~ S1811 are repeated.

Next, with reference to FIG. 19, for explaining the write back / deleting process link data 503 cooperation destination terminal 200 is performed. Processing of steps S901 ~ S906 in FIG. 19 is the same as the processing in FIG.
If the remaining amount difference D1 while monitoring the battery 201 determines the battery remaining amount management unit 202 has reached the predetermined value or less δ1 (S903: YES), the write-back management unit 208, link data that is cached described above 503 reading (S904), performs transmission (S905), and deletes (S906). On the other hand, if the remaining amount difference D1 while monitoring the battery 201 determines the battery remaining amount management unit 202 has not been reached to a predetermined value or less δ1 (S903: NO), write-back management unit 208, the communication unit 205 and notifies determines whether an instruction of the reception waiting from write-back management unit 208 is continued (S1907). When the instruction of the reception waiting is continued (S1907: YES), write-back management unit 208 checks whether it has received the write-back request (S1908). When the communication unit 205 receives a request writeback from the cooperation source terminal 250, the write-back management unit 208 reads the link data 503 is cached described above (S904), transmitting (S905), and deletes (S906 )I do. On the other hand, when the communication unit 205 has not received the request writeback from the cooperation source terminal 250 continues to monitor battery power Pr1 returns to step S902.

According to the third modification of the first embodiment, with respect to cooperation destination terminal 200 from the cooperation source terminal 250, before the remaining battery level of cooperation source terminal 250 is insufficient, to request transmission of link data 503 can. Therefore, when the cooperative applications between data linked terminal, it is possible to achieve both the comfort of operation by the cache of the link data, and security and privacy secure personal information.

<Second Embodiment>
Data link system 2 according to a second embodiment of the present invention, after completion of the data linkage process according to the first embodiment, with respect to cooperation source terminal from the cooperation destination terminal, has been cached by the cooperation destination terminal link data It does that to notify that but has been deleted.

Figure 20 is a diagram showing an internal configuration of a cooperation destination terminal 2000 and the collaboration source terminal 2050 constituting the data link system 2 according to a second embodiment of the present invention. Cooperation destination terminal 2000, a battery 201, a battery remaining amount management unit 202, the link data identifying section 203, a link data determination unit 204, a communication unit 205, a data storage unit 206, a cache management unit 207, write back it includes a management unit 208, and a deletion completion notification unit 2001. Collaboration source terminal 2050 is provided with a battery 251, a battery remaining amount management unit 252, a communication unit 253, a data storage unit 254, and the link data management unit 255, and a deletion message display unit 2051.

As shown in FIG. 20, the data link system 2 according to the second embodiment, the data association system 1 according to the first embodiment, in the configuration obtained by adding the deletion completion notification unit 2001 and deletes the message display unit 2051 . Another configuration of the data link system 2 according to the second embodiment will be omitted because the same configuration as the data link system 1 according to the first embodiment, the description using the same reference numerals.

Deletion completion notification unit 2001 of the cooperation destination terminal 2000, if the write-back control section 208 completes the deletion of the link data that are cached in the data storage unit 206, and displays a message to that effect to the cooperation source terminal 2050 for, through the communication unit 205 notifies that the deletion in the cooperation source terminal 2050 is completed. The contents of this notification, collaboration to source terminal 2050 may be a message itself to be displayed, or may be identification information indicating the deletion completion. In the latter case, a message to be displayed, or holds in advance by the cooperation source terminal 2050, may be obtained from its own generating or external (network server, etc.) for each notified.

Delete message display unit 2051 of the cooperation source terminal 2050 via the communication unit 253 receives the notice of completion of deletion from the cooperation destination terminal 2000, information including personal information cooperation destination terminal 2000 has been cached, i.e. link data to display a message indicating to the user that the deletion is complete. Figure 21 is a diagram illustrating an example of a message 2100 that cooperation source terminal 2050 displays. In the example of FIG. 21, a message 2100 is displayed about the deletion completion of the link data in the central portion of the display screen of the cooperation source terminal 2050.

By the display of this message, the user, because the cooperation destination terminal 2000, which had done the application cooperation can know that you have securely delete the data, including personal information and the like that has been cached, giving a sense of security to the user can.

Incidentally, if the notification from the deletion completion notification unit 2001 could not be transmitted to the delete message display unit 2051 by communication failure or the like, stores the notification raw transmission of information in cooperation destination terminal 2000, after a predetermined time it is sufficient to re-notified at the time and the next data linkage processing. This notification Not transmitting information, in addition to cooperation destination terminal 2000 also other terminals and servers on a network, etc., or may be stored in the media.

Next, with reference to FIG. 22, for explaining the write back / deleting process link data 503 is cooperation destination terminal 2000 performs in the second embodiment. Processing of steps S901 ~ S906 in FIG. 22 is the same as the processing in FIG.
When the deletion of the link data 503 is cached in the data storage unit 206 is completed (S906), the write-back management unit 208 performs deletion completion notification unit 2001 notifies the deletion of the link data 503 is completed. Deletion completion notification unit 2001, information telling that the deletion is complete, generates a message to be displayed in the example of this flow passes to the communication unit 205. The communication unit 205 transmits a message to the collaboration source terminal 2050 (S2207).

Next, with reference to FIG. 23, for explaining the rewriting process of the link data 503 to the collaboration source terminal 2050 in the second embodiment is performed. Processing of steps S1001 ~ S1007 in FIG. 23 is the same as the processing in FIG. 10.
When the write-back of cooperation data 503 obtained from the cooperation destination terminal 2000 is completed (S1007), cooperation data management unit 255, and notifies the communication unit 253, to wait for a notice of completion of deletion from the cooperation destination terminal 2000 instructs (S2308). The communication unit 253 receives a notification from the cooperation destination terminal 2000 of deletion completion while continuing the reception waiting of the deletion completion notification (S2309: YES), passes the message received by the notification to delete the message display unit 2051 . Delete message display unit 2051 displays the received message on a display or the like (not shown in FIG. 20) (S2310). Even when not receiving the notice of completion of deletion from the cooperation destination terminal 2000, the reception waiting by the communication unit 253 is stopped (S2308: NO), the write-back process is terminated.

As described above, according to the data link system 2 according to a second embodiment of the present invention, that deleting the link data that are cached in the cooperation destination terminal 2000 notifies the cooperation source terminal 2050. Thus, the user can know that the personal information that has been cached in cooperation destination terminal 2000 is deleted securely. Therefore, in addition to the effect according to the first embodiment, in a case of using the terminal in particular shared by multiple users, it is possible to perform with confidence data linkage using the terminal.

In the present embodiment, and it illustrates a case of calculating both the size of the cache of the cooperation destination terminal and works with the source terminal (the size of the link data) at the start of the data linkage. However, cooperation destination terminal may be previously held the upper limit of the cache size. In this case, it can be calculated remaining battery capacity "Pmin" required to perform a predetermined series processing from the upper limit value of the cache size. Therefore, stores the required battery level "Pmin", it is compared with the remaining battery level Pr1 of the cooperation destination terminal, cache size shown in FIG. 8 with respect to the cooperation destination terminal in the case of Pr1> Pmin the calculating process performing is not required, it is possible to simplify the processing at the time of starting the cooperation. The predetermined sequence processing here, for example, in the case of the first embodiment "caching collaboration data 503 to the data storage unit 206", "read processing of the link data 503 from the data storage unit 206" , the "transmission process link data 503 to the cooperation source terminal 250", and "deletion of the link data 503 from the data storage unit 206".

Further, in the present embodiment, due to limitations such as the size of the link data, the data cooperation destination terminal can not be cached, how sequentially obtained from the cooperation source terminal is considered. Accordingly, even when the battery remaining amount is small cache sizes Sc is small, it is possible to avoid the limitations of user features available. For example, if the bookmark information cooperation source terminal is held can not be cached, sequentially acquires the bookmark information at the timing requested by the user. Thus, as compared with the case of a cache of all link data at a time, although the display is likely to delay, since the user can use the bookmark information, there is no risk of significantly damaging the convenience of the user.

Further, in the present embodiment, the identification and determination of properties of the link data to be executed by the link data identifying section 203 or the link data determination unit 204, the example to run in cooperation destination terminal. However, it is also possible as comprising a linkage data specifying part 203 or the coordination data determination unit 204 in cooperation source terminal, performed in collaboration source terminal specific or determination of properties of the link data.

In the present embodiment, an example was given in which cooperation destination terminal to acquire the battery residual quantity of the cooperation source terminal. However, running the calculation of the size of the link data based on the remaining battery level cooperation with the source terminal, a cooperation destination terminal the calculated size may acquire.

Further, in the present embodiment, the size of the link data to be written back from the cooperation destination terminal to the cooperation source terminal may be smaller than the size of the link data to be cached by the receiving or the cooperation destination terminal from the cooperation destination terminal.

Further, in the present embodiment, in particular or the determination of the properties of the link data to be cached may be considered a condition selected by the user. For example, by giving priority to use time in the cooperation destination terminal, may be set smaller the size of the link data for calculating, with priority processing speed in cooperation destination terminal, the size of the link data for calculating set larger it may be.

Further, in the present embodiment, the cooperation of at least one of the source terminal or the cooperation destination terminal, cooperation if there is no battery remaining amount of data only can be cached, cooperation destination terminal so as to each time get the required data from the cooperation source terminal it may be. Further, in this case, it may be prohibited cooperation.

Further, in the present embodiment, for such securing longer usage time cooperation destination terminal, user selection, it may be able to determine whether write back the linkage data to the cooperation source terminal. That is, based on the intention of the user, deletion of cooperation data cached do, but may not perform the write back process. Accordingly, since the communication processing with large power consumption is not required, it is possible to extend the use in cooperation destination terminal. The timing of the user selection, at the beginning of the data linkage, when the user sets in advance, such as when it is time to execute the predetermined processing series in cooperation destination terminal and the collaboration source terminal, can be considered.

Further, in the present embodiment, the processing executed at the time when it is time to write back the linkage data to the cooperation source terminal from the cooperation destination terminal, as a method other than those described in this embodiment, it can be considered the following methods. (A) case than "cache size determined in cooperation at the start, etc." "actual write-back size" is large, to start a write back immediately. (B) the case than the "size write back that were determined to cooperation at the start, etc." "actual write-back size" is small, on the basis of the size back actual written as remaining battery power, to continue the use of the cooperation destination terminal whether the determined automatically by, or user selection, and the like.

Further, in this embodiment, or the like connected to the cooperation source terminal or the cooperation destination terminal power adapter (AC power supply) or the like, if considering the remaining battery level becomes unnecessary, Ya is calculated again such cache size at that time , may be executed again acquisition of the link data.

Further, the processes described in the embodiment, in a range that does not interfere with the essence of the present invention, starting the cooperation before, during starting the cooperation, in cooperation, at federation termination can take any timing such as after Federation Termination . In particular, write-back processing to the cooperation destination acquisition of the link data from the cooperation source terminal in the terminal (cash) and collaboration source terminal may be performed in any timing during cooperation.

Further, in the present embodiment, in consideration of the situation of abnormal system such retry processing such as the transmission and reception in advance by considering a predetermined margin in the calculation of the required battery level, to avoid breakage unexpected battery it may be.

Further, in this embodiment, linkage for the trigger of starting the cooperation and coordination termination between the source terminal and the cooperation destination terminal, not described because it is not essential to the invention. As an example, to display a GUI (Graphical User Interface) including the button display to start collaboration on the screen of the cooperation source terminal, the user presses the GUI button, cases can be considered to start collaboration. Moreover, the cooperation when the source terminal and the cooperation destination terminal closer to the predetermined distance, based on GPS (Global Positioning System) or NFC (Near Field Communication) distance and the like between data linked terminal such, automatically cooperate the may be started. In addition, the federation termination is also the same as this.

A part or all of the functional blocks of the cooperation source terminal and cooperator terminal constituting the data link system in the embodiments of the present invention comprises a central processing unit (CPU), a storage device (memory (ROM, RAM, etc.) , it is realized by using hardware resources such as a hard disk, etc.), and the input-output device, typically embodied as an IC is an integrated circuit (LSI, system LSI, super LSI, also called ultra LSI, etc.) It is. These functional blocks may be realized separately with individual chips, or may be integrated into one chip including part or all.
Further, the method of circuit integration is not limited to IC, it may be realized by a dedicated circuit or a general-purpose processor. Moreover, that can be programmed after IC fabrication FPGA (Field Programmable Gate Array) or may utilize reconfigurable reconfigurable processor where connections and settings of circuit cells in the IC.
Furthermore, according to another technique as an advance in, or derivation from semiconductor technology, with the arrival of integrated circuit technology that replaces IC (such as biotechnology) may be carried out naturally function block integration using this technology.

Also, data association method data linkage system according to embodiments of the present invention described above is executed, predetermined program data capable of executing the processing procedure of the data stored cooperation method in the storage device, is interpreted and executed by the CPU it may be realized by Rukoto. In this case, the program data may be introduced in the storage device via a recording medium such as a DVD-ROM, a flexible disk, or may be executed directly from the recording medium. The recording medium is, ROM and RAM and a semiconductor memory such as a flash memory, a flexible disk or a magnetic disk memory such as a hard disk, an optical disk memory such as a DVD or BD, and refers to such a memory card. The recording medium is a concept including a communication medium such as a telephone line and a carrier line.

Data linked terminal of the present invention can use the application between terminals seamlessly systems utilizing, for example, a system such as to link the application with the tablet PC to be shared on smartphones and multiple users of personal use, in particular, It is suitable or when you want to achieve both the security and privacy securing convenience and personal information of the user.

1 and 2 data linkage system 10 Tablet PC
20 smartphone 30 Notebook PC
40 Network 200,2000 cooperation destination terminal 250,2050 cooperation source terminal 201,251 cells 202,252 battery level managing section 203 link data specifying part 204 link data determination unit 205,253 communication unit 206,254 data storage unit 207 Cache Management part 208 write back management unit 255 link data management unit 300,400,502 power consumption table 301 processing type 302 power 500,1400,1401 communication data 501 remaining battery amount 503 link data 2001 deletion completion notification unit 2051 deletes the message display unit 2100 message

Claims (10)

  1. Driven by a battery, and receive link data related to the application between the second data linked terminal running the application performs continued use of applications, a first data linked terminal,
    A battery remaining amount management unit that manages the remaining amount of the battery,
    At least the battery level based on the remaining amount of the detected battery management unit, the first data linkage linkage data specifying section for specifying the properties of the link data capable of executing predetermined processing with the power consumption in the terminal,
    Said link data based on properties of the linkage data identified by the identifying unit, link data determining unit that determines the properties of the link data communication is performed between the second data linked terminal,
    A communication unit for performing data communication with the second data linked terminal,
    A data storage unit that caches link data associated with the application received from the via the communication unit the second data linked terminal,
    Based on the properties of the link data, and a cache management unit for managing the collaboration data cached in the data storage unit,
    The cache management unit, at a predetermined timing, caching the collaboration data by the communication unit has received on the basis of the link data of the property the cooperative data determination unit is determined, and, at a predetermined timing, the data storage and deletes the cached the linkage data to the parts, the first data linked terminal.
  2. Further comprising a write back management unit for managing the data write-back to the second data linked terminal from said first data linked terminal,
    The communication unit receives the remaining amount of the battery for driving the second data linked terminal from said second data linked terminal,
    The linkage data specifying unit, first about the first and properties of the first linkage data about data linked terminal, said second data linked terminal based on the remaining battery acquired from the second data linked terminal to identify and properties of 2 of the cooperation data,
    The link data determination unit, based on the properties of the properties and the second link data of said first linkage data to determine the properties of the third link data,
    The cache management unit, based on the third link data properties, manages the link data by the communication unit receives the cache in the data storage unit,
    The write back management unit at a predetermined timing, and transmits the link data that has been cached in the data storage unit to the second data linked terminal, the first data according to claim 1 cooperation terminal.
  3. The properties of the link data, the size of the link data, the type of item of the link data, the number of each item of the link data, and the remaining amount of the battery capable of executing predetermined processing using the link data, of wherein at least is one, the first data linkage terminal according to claim 1.
  4. Wherein the predetermined processing, the transmission processing of the link data, the reception processing of the link data writing process of the collaboration data, reading processing of the link data, and in that the deletion of the link data is at least one of wherein, the first data linkage terminal according to claim 1.
  5. Wherein the predetermined timing is between said first data linked terminal and said second data linked terminal, the timing for starting the cooperation, the timing of ending the cooperation, timing in coordination, timing after linkage completion, and wherein the linkage before the start timing is at least one of the first data linkage terminal according to claim 1.
  6. Said cache management unit deletes the link data by the communication unit that is cached in the data storage unit has received, and further comprising a deletion message notification unit for notifying the second data linked terminal , the first data linkage terminal according to claim 1.
  7. Driven by a battery, and receive link data related to the application between the first data linked terminal to be executed the application performs continued use of applications, a second data linked terminal,
    A battery remaining amount management unit that manages the remaining amount of the battery,
    A communication unit for performing data communication between the first data linked terminal,
    A data storage unit for storing the link data relating to at least said application,
    And a link data management unit for managing the linkage data stored in the data storage unit,
    The battery remaining amount management unit at a predetermined timing, transmits the remaining capacity of the battery detected by the battery remaining amount management unit in the first data linked terminal,
    The link data management unit, said that the write back link data received from the first data linked terminal, wherein the second data linked terminal.
  8. It said received from the first data linked terminal, based on the notification that the said first linkage data the cached second data linked terminal transmits the data linked terminal is deleted, the user characterized in that it further comprises a deletion message display unit for displaying a message that has been removed, a second data linkage terminal according to claim 7.
  9. Between the first data linked terminal and the second data linked terminal, a data association system for the continued use of transmitting and receiving application collaboration data related to the application,
    It said first data linked terminal to be executed the application,
    A first battery remaining amount management unit that manages the remaining amount of the battery for driving the first data linked terminal,
    Based on at least the remaining amount of the first battery detected by the battery remaining amount management unit, the first link data specific to the particular properties of the link data capable of executing predetermined processing with the power consumption in the data linked terminal and parts,
    Said link data based on properties of the linkage data identified by the identifying unit, link data determining unit that determines the properties of the link data communication is performed between the second data linked terminal,
    A first communication unit for performing data communication with the second data linked terminal,
    A first data storage unit that caches link data associated with the application received from the second data linkage terminal via the first communication unit,
    Based on the properties of the link data, and a cache management unit for managing the collaboration data to be cached in the first data storage unit,
    It said running the application second data linkage terminal,
    A second battery remaining amount management unit that manages the remaining amount of the battery for driving the second data linked terminal,
    A second communication unit for performing data communication between the first data linked terminal,
    A second data storage unit for storing the link data relating to at least said application,
    And a link data management unit for managing the linkage data stored in the second data storage unit,
    The second battery remaining amount management unit at a predetermined timing, the remaining amount of the battery detected by the second battery remaining amount management unit, the first data linkage via the first communication unit and transmitted to the terminal,
    The cache management unit, at a predetermined timing, caching the linkage data to which the first communication unit receives, based on the link data of the property the cooperative data determination unit is determined, and, at a predetermined timing, remove the linkage data cached in the first data storage unit,
    The link data management unit may write back link data received from the first data linkage terminal via the second communication unit.
  10. By sending and receiving link data related to the application between the first data linked terminal and the second data linked terminal, a data association method for performing continuous use of the application,
    It said first data linked terminal to be executed the application,
    A step of the first data linkage based on the remaining amount of a battery for driving the terminal, to identify the properties of the link data capable of executing predetermined processing with the power consumption in the first data linked terminal,
    Determining on the basis of the properties of the specified link data, properties of the link data communication is performed between the second data linked terminal,
    A step of caching the link data associated with the application received through the communication interface from said second data linked terminal, the first data storage unit,
    A step of managing the collaboration data based on the properties of the link data is cached in the first data storage unit,
    At predetermined timing, a step of the caching linkage data received via the communication interface from said second data linkage terminal based on the properties of the link data said determined
    At a predetermined timing, and a step of deleting the linkage data cached in the first data storage unit,
    It said running the application second data linkage terminal,
    And storing the link data relating to at least the application to the second data storage unit,
    A step of managing the linkage data stored in the second data storage unit,
    At predetermined timing, and sending detecting the remaining amount of the battery for driving the second data linked terminal, the remaining amount of the battery and the detected via the communication interface to the first data linked terminal ,
    And a step of writing back the linkage data received via the communication interface from the first data linked terminal.
PCT/JP2012/002059 2011-04-27 2012-03-26 Data linkage terminal, data linkage method, and data linkage system WO2012147272A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2011-100204 2011-04-27
JP2011100204 2011-04-27

Publications (1)

Publication Number Publication Date
WO2012147272A1 true true WO2012147272A1 (en) 2012-11-01

Family

ID=47071806

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2012/002059 WO2012147272A1 (en) 2011-04-27 2012-03-26 Data linkage terminal, data linkage method, and data linkage system

Country Status (1)

Country Link
WO (1) WO2012147272A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003242106A (en) * 2002-02-14 2003-08-29 Sony Communication Network Corp Information synchronizing method, information synchronizing device capable of using the method, and information terminal
JP2004147330A (en) * 2003-10-23 2004-05-20 Sanyo Electric Co Ltd Portable communication device
JP2006201896A (en) * 2005-01-19 2006-08-03 Fujitsu Ltd Network system and mobile communication node
JP2007034553A (en) * 2005-07-26 2007-02-08 Sharp Corp Information processor
JP2007328462A (en) * 2006-06-06 2007-12-20 Masayuki Sato Computer system, portable telephone set, input/output device, input/output method, and program

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003242106A (en) * 2002-02-14 2003-08-29 Sony Communication Network Corp Information synchronizing method, information synchronizing device capable of using the method, and information terminal
JP2004147330A (en) * 2003-10-23 2004-05-20 Sanyo Electric Co Ltd Portable communication device
JP2006201896A (en) * 2005-01-19 2006-08-03 Fujitsu Ltd Network system and mobile communication node
JP2007034553A (en) * 2005-07-26 2007-02-08 Sharp Corp Information processor
JP2007328462A (en) * 2006-06-06 2007-12-20 Masayuki Sato Computer system, portable telephone set, input/output device, input/output method, and program

Similar Documents

Publication Publication Date Title
US20120311366A1 (en) Methods and apparatus for power state based backup
US20120310894A1 (en) Methods and apparatus for interface in multi-phase restore
US8645327B2 (en) Management of access to data distributed across multiple computing devices
US20150148093A1 (en) Battery pack with supplemental memory
US20120311280A1 (en) Methods and apparatus for multi-source restore
CN102801199A (en) Terminal and terminal charging method
US20160126779A1 (en) Electronic device and method for sharing electric power in wireless charging
US20070025367A1 (en) Mobile communications device and method for condition-dependent resuming of a delayed data transfer over a different network
EP3101867A1 (en) Wireless audio output devices
CN102801786A (en) Method, device and system for transmitting file
US20120246390A1 (en) Information processing apparatus, program product, and data writing method
KR20120010397A (en) Cloud storage service apparatus and method
US20140289202A1 (en) Utilizing user devices for backing up and retrieving data in a distributed backup system
US20130282869A1 (en) Method, apparatus, and computer program product for scheduling file uploads
US20140192681A1 (en) Apparatus and method for providing integrated device information
CN101364232A (en) Method, terminal and system fro backing-up non-volatile data
US20150133049A1 (en) Method and apparatus for downloading content using nfc
CN102651785A (en) Remote wakeup of application processor of mobile device
US20140136662A1 (en) Mobile application migration to cloud computing platform
EP2249254A2 (en) Storage device having direct user access
US20140289225A1 (en) Prioritizing downloading of image files
US20140101135A1 (en) Method and system for dynamically optimizing client queries to read-mostly servers
CN102624881A (en) Mobile-device-oriented service cache system architecture and development method
JP2011243162A (en) Quantity control device, quantity control method and quantity control program
CN102722343A (en) Wireless private security cloud storage equipment

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12776491

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12776491

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase in:

Ref country code: JP