JP2009123047A - Terminal cache management apparatus, terminal cache management method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a terminal cache management apparatus, a terminal cache management method and a program that allow a server to manage a cached state of a mobile terminal. <P>SOLUTION: A data management server 1 for managing the cache of mobile terminal that has a cache has; a communication part 111 for communicating with mobile terminals; a data access management part 112 for accepting a request about access to user data from a mobile terminal; a cached state management part 115 for managing a cached state of the mobile terminal; a user data table 123 for storing the user data for use on the mobile terminal; and a cached state management table 124 for managing the cached state of each mobile terminal. When a request about an access is accepted, the cached state management part 115 refers to the cached state management table 124, checks to see whether or not the cache of the mobile terminal needs to be updated to the latest data, and updates the cache of the mobile terminal if needed. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a terminal cache management server, a terminal cache management method, and a program for managing a cache of mobile terminals connected via a network.

  In recent mobile phone systems, functions such as e-mail and Internet browser are installed in addition to a simple conversation function, so that the functions are improved. Next-generation mobile phone systems are equipped with more sophisticated and diverse applications such as game and video distribution, and tend to expand. In a mobile phone that requires such high-speed operation, a cache memory is provided inside the CPU. By accumulating frequently used data in the cache memory, access to the low-speed main memory can be reduced, and the processing speed can be increased.

By the way, Patent Document 1 discloses a server that efficiently updates service content. This conventional server includes content holding means, content management means, and communication means. The content holding means is a memory for storing various service contents provided to the client terminal. The content management means includes a cache identifier assigning means for assigning a cache identifier. The cache identification and grant unit assigns a cache identification according to the category in which the service content is stored. The cache state of the content is managed at the client terminal by this cache identifier.
JP 2004-133543 A

  However, conventionally, the state of the cache of the mobile terminal is usually managed on the mobile terminal side. If the mobile device cache is managed only on the mobile device side, if the data is changed on the server, the new data cannot be automatically reflected in the mobile device cache, so the old data remains in the device cache There was a problem. In addition, some of the above problems are dealt with by deleting the expired data from the cache by adding an expiration date of the data when caching on the mobile terminal, but the data that has not been changed is also deleted There was a problem that it was difficult to set an expiration date. Further, since the cache status of the mobile terminal cannot be grasped on the server side, the user data cannot be stored in the cache of the mobile terminal based on the determination on the server side.

  The present invention has been made to solve such problems, and provides a terminal cache management apparatus, a terminal cache management method, and a program capable of managing the cache state of a mobile terminal on the server side. For the purpose.

  In order to solve the above-described problem, a terminal cache management device according to the present invention is a data management server that manages a cache of a mobile terminal having a cache, and includes a communication unit that communicates with the mobile terminal, and the mobile terminal A data access management means for receiving a request relating to access of user data from; a cache state management means for managing a cache state of the mobile terminal; a user data table for storing user data used in the mobile terminal; and each mobile terminal A cache status management table for managing the cache status, and when the access request is received, the cache status management means refers to the cache status management table and updates the cache of the mobile terminal to the latest data Check whether you need to It is intended to update the cache of the mobile terminal in accordance with the.

  A terminal cache management method according to the present invention is a data management method for managing a cache of a mobile terminal having a cache, and receives a request regarding access of user data from the mobile terminal, and determines a cache state of the mobile terminal. Refer to the cache state management table to be managed, check whether it is necessary to update the user data in the cache to the latest user data, and if it is necessary to update to the latest user data, the mobile terminal The user data read from the user data table is transmitted to the portable terminal in order to update the cache data to the latest state.

  A program according to the present invention is a program for causing a computer to execute an operation of managing a cache of a mobile terminal having a cache, receiving a request regarding access of user data from the mobile terminal, and If it is necessary to update the cache user data to the latest user data by referring to the cache status management table that manages the status of the cache, the user data in the cache needs to be updated to the latest user data. The user data read from the user data table is transmitted to the portable terminal in order to update the cache data of the portable terminal to the latest state.

  According to the present invention, it is possible to provide a terminal cache management apparatus, a terminal cache management method, and a program capable of managing the cache state of a mobile terminal on the server side.

  First, the outline of the present invention will be described. FIG. 1 is a diagram showing a terminal cache management server (hereinafter referred to as a data management server) for explaining the principle of the present invention. The data management server 1 is connected to a mobile terminal via a network, and is configured to be able to manage the cache state of the mobile terminal.

  The data management server 1 includes data management software 11 and a database 12. The data management software 11 includes a communication unit 111 that communicates with a mobile terminal, a data access management unit 112 that receives a request for accessing user data from the mobile terminal, and a cache state management unit 115 that manages the cache state of the mobile terminal. The database 12 includes a user data table 123 that stores user data used by the mobile terminal, and a cache state management table 124 that manages a cache state for each mobile terminal.

  This data management server 1 accepts a request for access to user data from the mobile terminal, refers to the cache status management table 124, and determines whether or not the user data in the cache of the mobile terminal needs to be updated to the latest user data. Check. If it is necessary to update to the latest user data, the user data read from the user data table 123 by the data access management unit 112 is updated to the communication unit 111 in order to update the cache data of the mobile terminal to the latest state. Via the mobile terminal. As described above, the latest cache state of the mobile terminal is stored in the cache state management table 124 of the data management server 1.

  Hereinafter, specific examples to which the present invention is applied will be described in detail with reference to the drawings. In this embodiment, the present invention is applied to a data management server that can manage the state of user data cached in a portable terminal on the server side.

  In this embodiment, since it has the above-described configuration, it is possible to grasp on the data management server side whether or not user data (items) such as an email address and a schedule is cached in the mobile terminal. It is possible to automatically reflect the change contents of the user data by other mobile terminals used by the same user who caches the corresponding data. It is also possible to store user data in the cache of the mobile terminal at the server's discretion.

[First embodiment]
FIG. 2 is a diagram showing a terminal cache state management system according to the first exemplary embodiment of the present invention. Referring to FIG. 2, the terminal cache state management system 100 includes a data management server 1 and a mobile terminal 2 and a mobile terminal 3 that are used by the same user. The data management server 1, the mobile terminal 2, and the mobile terminal 3 are connected via a communication line 4 such as the Internet for communication.

The data management server 1 includes data management software 11 and a database 12.
The mobile terminal 2 is a mobile phone or the like that has a communication function such as packet communication and can be connected to the communication line 4 such as the Internet, and is used by the data use software 21, the data access software 22, and the data access software 22. Possible storage 23.
The mobile terminal 3 has the same configuration as the mobile terminal 2 and is a mobile phone or the like that has a communication function such as packet communication and can be connected to a communication line 4 such as the Internet. The software 32 and the storage 33 which can use the data access software 32 are included.

  FIG. 3 is a block diagram showing the data management server. Referring to FIG. 3, the data management software 11 includes a communication unit 111, a data access management unit 112, a data reference unit 113, a data change unit 114, a cache state management unit 115, and a push delivery request unit 116.

  The database 12 includes a user information table 121, a terminal information table 122, a user data table 123, and a cache state management table 124. The user information table 121 manages user information such as a user ID and a password for each user. The user data is associated with an item ID and a user data type. The item ID is an ID for identifying user data for each user data such as individual mail addresses or individual schedules. The user data type indicates the type of user data, and corresponds to an e-mail address, a schedule, or the like. The terminal information table 122 manages a user ID for identifying a user and a terminal ID for identifying one or more portable terminals used by the same user (hereinafter also referred to as association information). The user data table 123 stores user data used by the mobile terminal using an item ID as a key. The cache status management table 124 manages the cache status of the above-described user data in the mobile terminal.

  The cache status management table 124 records any status of synchronized / unregistered / unupdated / undeleted / deleted / cache deleted / push delivery. Synchronized indicates that the latest data is stored in the cache of the mobile terminal. Unregistered indicates that user data is not registered on the mobile terminal side. Unupdated indicates a state where the user data in the mobile terminal cache has not been updated yet. Undeleted indicates a state where data has been deleted on the data management server 1 but data remains in the cache of the mobile terminal. Deletion indicates a state in which user data is deleted from the cache of the mobile terminal. The cache deletion indicates a state in which there is data on the data management server 1, but the data is deleted from the cache of the mobile terminal due to circumstances on the mobile terminal side such as a memory shortage. Push distribution indicates that data is to be transmitted from the data management server 1 side.

  Note that the user data table 123 and the cache state management table 124 are prepared separately for each user data type such as address data and schedule data, but common processes related to the cache are used. In FIG. 3, only one set is described for the user data table 123 and the cache status management table 124. However, if there are a plurality of user data types, there are a plurality of sets.

  FIG. 4 is a block diagram illustrating the mobile terminal. Referring to FIG. 4, the data use software 21 is an application such as an address book or a scheduler, and accesses user data managed by the server via the data access software 22. The data access software 22 includes a data access unit 221, a server communication unit 222, and a cache management unit 223.

  The storage 23 includes user information 231 and a user data cache 232. The user information 231 stores a user ID, a password used for authentication, and a terminal ID. The user data cache 232 caches user data acquired from the server. The user data cache 232 is prepared separately for each type of user data such as address data and schedule data, but common processing is used for the cache. Although only one user data cache 232 is shown in FIG. 4, if there are a plurality of user data types, there are a plurality of user data caches. FIG. 5 is a block diagram showing the mobile terminal 3. The configuration of the mobile terminal 3 is the same as that of the mobile terminal 2.

  Each block of the data management software 11 generally operates as follows. The communication unit 111 performs processing related to communication with the data access software 22 and 32 of the mobile terminals 2 and 3. When a message is received from the data access software 22, 32, a request related to user data access is extracted from the message and passed to the data access management unit 112. A response to the request is received from the data access management unit 112 and returned to the data access software of the transmission source mobile terminal. Further, the communication unit 111 performs an authentication process using the user information included in the message and the user information table 121 of the database 12. With regard to the authentication processing method, any means such as use of a known authentication function provided by an AP server (application server) or implementation of original software may be used. The communication unit 111 also performs registration check of the association information including the user ID and the terminal ID using the user information included in the message, the terminal ID, and the terminal information table 122 of the database 12.

  The data access management unit 112 acquires the terminal ID and the user ID from the request passed from the communication unit 111, searches the cache state management table 124 of the database 12 using them as a key, and requires synchronization (update to the latest data). Check if there is user data required. Further, when the received request is a data reference request, the request is distributed to the data reference unit 113, and when the received request is a data change request, a data synchronization start request, and a data synchronization response, the request is distributed to the data change unit 114. In the case of other requests, the request is distributed to other means (not shown) not related to data access in the data management software 11 based on the contents. When the processing of the called block is completed, a response is generated from the processing result and returned to the communication unit 111. As described above, the data access management unit 112 may access the user data table 123 to register, update, or delete data. However, as in this embodiment, the data reference unit 113 and the data change The unit 114 may be provided to access the user data table 123.

  The data reference unit 113 searches the user data table 123 using the user data type and item ID acquired from the data reference request or the search condition, and acquires user data. Then, the terminal ID, user ID, user data type, item ID, and access type are set and passed to the cache status management unit 115 to request an update of the cache status of the corresponding record in the cache status management table 124. The access type includes reference (reading or searching) / registration / update / deletion / cache deletion, and the data reference unit 113 acquires the access type = reference from the data reference request. The access type indicates what purpose the mobile terminal is sending a request to the data management server, and is used for update determination of the cache state management unit 115. When the processing of the cache state management unit 115 is completed, the acquired user data is returned to the data access management unit 112.

  When the data change unit 114 receives a data change request, the data change unit 114 inquires of the cache state management unit 115 whether or not a collision has occurred. Then, the cache state management unit 115 is requested to update the cache state of the cache state management table 124. Collision is a state in which user data on the mobile terminal side 2 is older than user data in the user data table 123 of the data management server 1 and changes such as update or deletion of the corresponding user data are performed on the mobile terminal 2. Indicates the case. When the data change unit 114 receives a data synchronization start request, the data change unit 114 makes a user data inquiry that requires synchronization to the cache state management unit 115, and generates synchronization information according to the passed item ID and access type. Further, when receiving the data synchronization response, the data change unit 114 requests the cache state management unit 115 to change the cache state of the cache state management table 124 according to the content of the data synchronization response.

  When the data reference unit 113 or the data change unit 114 inquires about the presence or absence of data that needs to be synchronized, the cache state management unit 115 searches the cache state management table 124 based on the passed terminal ID, user ID, and user data type. Then, check whether there is user data that needs to be synchronized and return the processing result. Data that needs to be synchronized is a case where the user data to be processed has the same terminal ID and user ID, and the cache status is unregistered, unupdated, undeleted, or push delivery. In addition, when the data change unit 114 inquires about the occurrence of a collision, the cache state management unit 115 searches and accesses the cache state management table 124 with the passed terminal ID, user ID, user data type, and item ID. The collision is determined according to the type and the processing result is returned. A collision is a case where the cache state of user data to be processed is unregistered, not updated, or not deleted as a result of searching from the terminal ID, user ID, user data type, and item ID. When the cache state management unit 115 is requested to change the cache state of the cache state management table 124, the cache state management unit 115 performs cache state management according to the terminal ID, user ID, user data type, item ID, and access type that are passed. The cache state of the corresponding record in the table 124 is changed.

  The push distribution request unit 116 is used when it is desired to store user data in the cache of the mobile terminal based on the determination on the server side. In response to a request from means (not shown) such as a function for an administrator in the data management software 11, the specified terminal ID, user ID, user data type, and item ID are set to the cache state management unit 115 as a set. Then, the cache state management table 124 is requested to update the cache state of the corresponding record.

  The means of the data access software 22 generally operates as follows. The data access unit 221 receives an access request for user data from the data use software 21. In the case of data reference, the user data type and item ID are passed to the cache management unit 223, and user data acquisition from the user data cache 232 of the storage 23 is attempted. If the data cannot be acquired, a data reference request is made to the data management server 1 via the server communication unit 212, and when the data reference response is received, the cache management unit 223 is requested to reflect it in the user data cache 232. If the data reference response processing result is data synchronization required, the original data reference request is suspended, a data synchronization start request is sent to the data management server 1, and when the data synchronization request is received, user data is sent to the cache management unit 223. Request reflection to the cache 232. In the case of data change, the cache management unit 223 is requested to change the user data cache 232, and further, a data change request is made to the data management server via the server communication unit 212.

  The server communication unit 212 transmits a processing request to the data management software 11 of the data management server 1 based on the content of the processing request received from another unit, and returns the returned response to the requesting unit.

  The cache management unit 223 processes an access request to the user data cache 232 in the storage 23. In the case of data reference, the corresponding user data is searched with the passed user data type and item ID, and the user data is returned only when it exists and when it exists. In the case of data change, when the access type is registration, the passed user data type, item ID and user data are stored in the cache, and when the access type is update, the passed user data type, item ID and user data are stored. Then, the cache is updated, and if the access type is deletion, the cache is deleted with the passed user data type and item ID.

  Next, the operation of the first embodiment of the present invention will be described in detail. First, the operation of the system at the preparation stage will be described. First, information such as the user ID and password of the user used in the data management server 1 is registered in the user information table 121. Further, the user ID and the terminal ID of the mobile terminal used by the user are linked and registered in the terminal information table 122. Further, the user data table 123 is generated according to the schema information (database configuration information) of the user data type used by the user, and the cache state management table 124 is generated in combination with the user data table 123.

  Next, the data use software 21 and the data access software 22 are installed in the portable terminal 2 in advance. Installation can be downloaded from the data management server 1 via the communication line 4 such as the Internet, or can be downloaded by connecting to a PC not shown in FIG. Shall be used.

  Next, the data access software 22 receives user information such as a user ID, a password, and a terminal ID by means not shown at the time of installation or at the time of initialization request by the data use software 21, and as user information 231 in the storage 23. Store. It should be noted that means for inputting user information is not particularly limited, such as manual input from the screen by the user, and downloading information simultaneously with the software. If the terminal ID can be directly acquired from the library provided by the mobile terminal, the data access software 22 acquires the terminal ID using the library and stores it in the user information 231. The mobile terminal 3 has the same configuration as the mobile terminal 2.

(1) Operation of System When Data Utilization Software of Mobile Terminal Refers to User Data FIG. 6 is a flowchart showing an operation when data utilization software of the mobile terminal refers to data. First, the data use software 21 of the portable terminal 2 is activated, and the user confirms the screen display and performs an operation that requires reference to user data. Then, the data use software 21 specifies the user data to be referred to by the user data type and the item ID or the search condition, and makes a request to the data access unit 221 of the data access software 22 (step S1).

  Next, the data access unit 221 passes the specified user data type and item ID or search condition to the cache management unit 223. Then, the cache management unit 223 checks whether user data exists in the user data cache 232 of the storage 23 (step S2). If it exists, the user data is acquired from the user data cache 232 and transferred to the data access unit 221. The data access unit 221 returns the user data to the data use software 21 and ends the process (step S3). If not, the data access unit 221 makes a data reference request to the communication unit 111 of the data management software 11 of the data management server 1 via the server communication unit 222. In the data reference request, the terminal ID, user ID, password, designated user data type and item ID, or search condition is set (step S4).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data reference request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data reference request Is passed to the data access management unit 112. The data access management unit 112 acquires the terminal ID, the user ID, and the user data type from the data reference request and passes them to the cache state management unit 115. The cache state management unit 115 searches the cache state management table 124 matching the user data type for a record having the same terminal ID and user ID and having a cache state that satisfies the conditions of unregistered / unupdated / undeleted / push delivery. . These are user data that needs to be synchronized as described above. Then, the presence / absence of user data that needs to be synchronized is returned to the data access management unit 112. If synchronization is unnecessary, the data access management unit 112 passes a data reference request to the data reference unit 113. The operation when synchronization is required will be described in another pattern described later. The data reference unit 113 acquires the user data type and item ID or search condition from the data reference request. Then, user data is acquired from the user data table 123 that matches the user data type using the item ID or the search condition. When the search condition is used, the item ID is also acquired together with the user data (step S5).

  Next, the data reference unit 113 sets the terminal ID, the user ID, the user data type, the item ID, and the access type = reference, and passes them to the cache state management unit 115. The cache state management unit 115 searches the cache state management table 124 that matches the user data type using the terminal ID, user ID, and item ID as keys, and acquires the corresponding record. When the cache state of the record is synchronized, the processing result is returned to the data reference unit 113 as normal without updating the cache state. When the cache state of the corresponding record is cache deletion, the cache state is updated to synchronized and the processing result is returned to the data reference unit 113 as normal. When the access type is reference, the item ID whose cache status is not deleted / deleted is not passed to the cache status management unit 115 because it has already been deleted from the user data table 123. FIG. 7 shows an example in which the cache state is updated from the cache deletion to the synchronized state in the cache state management table 124 (steps S6 and S7). The processing flag is turned on when user data not reflected in the mobile terminal is on the data management server 1 side and the change information is sent to the mobile terminal, and turned off when the data is updated on the mobile terminal side. It is a flag.

  Next, the data reference unit 113 returns the acquired user data to the data access management unit 112. The data access management unit 112 generates a data reference response from the received user data and the original data reference request and returns it to the communication unit 111. The communication unit 111 returns the passed data reference response to the server communication unit 222 of the data access software 22 of the mobile terminal 2. (Step S8).

  Next, the server communication unit 222 of the data access software 22 passes the received data reference response to the data access unit 221. The data access unit 221 extracts the user data type, item ID, and user data from the data reference response and passes them to the cache management unit 223. The cache management unit 223 stores the item ID and user data in the user data cache 232 that matches the passed user data type, and returns it to the data access unit 221 as normal. (Step S9).

  Next, the data access unit 221 returns the user data type, item ID, and user data to the data use software 21. The data use software 21 uses the received user data for screen display and operation (step S10).

(2) Operation of System When Data Utilization Software of Portable Terminal Registers User Data FIG. 8 is a flowchart showing an operation when data utilization software of the portable terminal registers user data. First, the data use software 21 of the portable terminal 2 is activated, and the user confirms the screen display and performs a user data registration operation. Then, the data use software 21 requests the data access unit 221 of the data access software 22 to register the user data together with the user data type (step S11).

  Next, the data access unit 221 passes the user data type and user data specified to the cache management unit 223. Then, the cache management unit 223 assigns a temporary ID, stores the temporary ID and user data in the user data cache 232 that matches the user data type of the storage 23, and returns the processing result and the temporary ID (step S12). The temporary ID is a temporary temporary ID attached to user data on the mobile terminal side. The user data to which the temporary ID is attached is assigned an item ID by the data management server 1. The data access unit 221 internally saves the temporary ID in an internal memory or the like to rewrite the item ID later, and then transmits the data to the communication unit 111 of the data management software 11 of the data management server 1 via the server communication unit 222. Make a change request. In the data change request, terminal ID, user ID, password, designated user data type, user data, and access type = registration are set (step S13).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data change request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data change request Is passed to the data access management unit 112. Then, the data access management unit 112 passes a data change request to the data change unit 114. The data change unit 114 newly assigns an item ID of the user data type acquired from the data change request, and registers the user data acquired from the data change request in the user data table 123 that matches the user data type with the item ID. (Steps S14 and S15)

  Next, the data changing unit 114 sets the terminal ID, user ID, user data type, item ID, and access type = registration as a set, and passes them to the cache state management unit 115. The cache state management unit 115 registers the record with the cache state synchronized with the terminal ID, user ID, and item ID as keys in the cache state management table 124 that matches the user data type. Then, the terminal information table 122 is searched using the user ID as a key to check whether there is another terminal ID used by the same user. If it does not exist, the processing result is returned to the data changing unit 114 as normal. If it exists, the record is registered in the cache state management table 124 with another terminal ID, user ID, and item ID as keys, and the cache state is not registered, and the processing result is returned to the data changing unit 114 as normal. By unregistering the cache status of another mobile terminal of the same user, when the data management server is accessed from the other mobile terminal, the cache of another mobile terminal is also updated according to this cache status. It will be. FIG. 9 shows an example of registering a record with the cache state synchronized with the requesting terminal ID in the cache state management table 124, and registering a record without registering the cache state with another terminal ID used by the same user. (Steps S16 to S18)

  Next, the data change unit 114 returns the processing result and the numbered item ID to the data access management unit 112. The data access management unit 112 generates a data change response from the passed processing result, item ID, and original data change request, and returns it to the communication unit 111. The communication unit 111 returns the passed data change response to the server communication unit 222 of the data access software 22 of the portable terminal 2 (step S19).

  Next, the server communication unit 222 of the data access software 22 passes the received data change response to the data access unit 221. The data access unit 221 acquires the user data type and item ID from the data change response, and passes them to the cache management unit 223 together with the temporarily saved ID. The cache management unit 223 updates the temporary ID stored in the user data cache 232 that matches the passed user data type to the item ID, and returns it as normal to the data access unit 221 (step S20). Next, the data access unit 221 returns a processing result to the data use software 21. The data use software 21 uses the passed processing result for screen display, operation, etc. (step S21).

(3) System Operation when Reflecting Registered User Data on Another Mobile Terminal of the Same User FIG. 10 is a flowchart showing an operation when reflecting registered user data on another mobile terminal of the same user. It is. First, the data use software 31 of the portable terminal 3 is activated, and the user confirms the screen display and performs an operation that requires reference to user data. Then, the data use software 31 specifies the user data to be referred to by the user data type and the item ID or the search condition, and makes a request to the data access unit 321 of the data access software 32. As a result of the inquiry to the cache management unit 323, the data access unit 321 does not have user data matching the user data type and item ID or search condition passed from the data use software 31 in the user data cache 332. A data reference request is made to the communication unit 111 of the data management software 11 of the data management server 1 via the unit 322. In the data reference request, the terminal ID, user ID, password, designated user data type and item ID, or search condition is set (step S31).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data reference request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data reference request Is passed to the data access management unit 112. The data access management unit 112 acquires a terminal ID, a user ID, and a user data type from the data reference request and passes them to the cache state management unit 115. The cache status management unit 115 searches the cache status management table 124 matching the user data type for a record having the same terminal ID and user ID and having a cache status of unregistered / unupdated / undeleted / push delivery conditions. . These are data that need to be synchronized. In this way, the presence / absence of user data requiring synchronization is returned to the data access management unit 112 (steps S32 and S33). If synchronization is unnecessary, the data access management unit 112 passes the data reference request to the data reference unit 113 and performs the same processing as steps S5 to S10, and does not perform the processing described below. If synchronization is required, the data access management unit 112 generates a data reference response from the processing result for data synchronization and the original data reference request, and returns the data reference response to the communication unit 111. The communication unit 111 returns the passed data reference response to the server communication unit 322 of the data access software 32 of the portable terminal 3 (step S34).

  Next, the server communication unit 322 of the data access software 32 extracts the received data reference response and passes it to the data access unit 321. Since the processing result acquired from the data reference response requires data synchronization, the data access unit 321 internally saves the original data reference request and puts it on hold, and the data of the data management server 1 via the server communication unit 322 A data synchronization start request is sent to the communication unit 111 of the management software 11. In the data synchronization start request, the terminal ID, user ID, password, and user data type to be synchronized are set (step S35).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data synchronization start request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data synchronization is performed. A start request is passed to the data access management unit 112. Then, the data access management unit 112 passes a data synchronization start request to the data change unit 114. The data change unit 114 acquires the terminal ID, the user ID, and the user data type to be synchronized from the data synchronization start request and passes them to the cache state management unit 115. The cache status management unit 115 searches the cache status management table 124 matching the user data type for a record having the same terminal ID and user ID and having a cache status of unregistered / unupdated / undeleted / push delivery conditions. . In this example, since the registered user data is reflected on another portable terminal of the same user, a record whose cache state is unregistered is acquired. The cache state management unit 115 sets the processing flag of the corresponding record to ON, and returns the item ID and access type = registration to the data change unit 114 as a set (step S36).

  Then, the data changing unit 114 acquires the user data of the item ID from the user data table 123 that matches the user data type, and sets the user data type, the item ID, the user data, and the access type = registration as a set to synchronize data access. Return to the management unit 112. The data access management unit 112 generates a data synchronization request from the received synchronization information and the original data synchronization start request and returns it to the communication unit 111. The communication unit 111 returns the passed data synchronization request to the server communication unit 322 of the data access software 32 of the portable terminal 3 (step S37).

  Next, the server communication unit 322 of the data access software 32 passes the received data synchronization request to the data access unit 321. The data access unit 321 acquires synchronization information from the data synchronization request, extracts the user data type, item ID, and user data from the synchronization information and passes them to the cache management unit 323. The cache management unit 323 stores the item ID and user data in the user data cache 331 that matches the passed user data type, and returns it to the data access unit 321 as normal. The data access unit 321 makes a pending data reference request together with the data synchronization response to the communication unit 111 of the data management software 11 of the data management server 1 via the server communication unit 322. In the data synchronization response, a terminal ID, a user ID, a password used for authentication, a user data type, an item ID, and a processing result are set. The data reference request has the same contents as in step S31 (step S38).

  Next, the communication unit 111 of the data management software 11 performs an authentication process using the user information of the data synchronization response and the user information table 121 of the database 12, and if the authentication result is normal, the data synchronization response and the data reference response are sent. The data is transferred to the data access management unit 112. Then, the data access management unit 112 passes the data synchronization response to the data change unit 114. The data change unit 114 acquires the terminal ID, user ID, user data type, and item ID from the data synchronization response and passes them to the cache state management unit 115. The cache status management unit 115 searches the cache status management table 124 that matches the user data type using the terminal ID, user ID, and item ID as keys, updates the cache status of the corresponding record, and updates the processing flag to OFF. The processing result is returned to the data changing unit 114 as normal. Then, the data change unit 114 returns the processing result to the data access management unit 112 as normal. FIG. 11 shows an example in which a record whose cache state is not registered in the cache state management table 124 is updated to be synchronized (step S39). Next, the data access management unit 112 starts processing of the data reference request passed together with the data synchronization response, and thereafter performs the same processing as steps S5 to S10 (step S40).

(4) System Operation when Data Utilization Software of Mobile Terminal Updates User Data FIG. 12 is a flowchart showing an operation when data utilization software of the mobile terminal updates user data. First, the data use software 21 of the portable terminal 2 is activated, and the user confirms the screen display and performs an operation of updating user data. Then, the data use software 21 requests the data access unit 221 of the data access software 22 to update the user data together with the user data type (step S41).

  Next, the data access unit 221 passes the user data type, item ID, and user data specified to the cache management unit 223. Then, the cache management unit 223 updates the user data corresponding to the item ID of the user data cache 232 that matches the user data type of the storage 23, and returns the processing result (step S42). Then, the data access unit 221 makes a data change request to the communication unit 111 of the data management software 11 of the data management server 1 via the server communication unit 222. In the data change request, terminal ID, user ID, password, designated user data type, item ID, user data, and access type = update are set (step S43).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data change request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data change request Is passed to the data access management unit 112. Then, the data access management unit 112 passes a data change request to the data change unit 114. The data change unit 114 acquires the terminal ID, user ID, user data type, item ID, and access type = update from the data change request and passes them to the cache state management unit 115. The cache state management unit 115 acquires a record from the cache state management table 124 that matches the user data type using the terminal ID, the user ID, and the item ID as keys. If the cache state is unregistered / unupdated / undeleted, there is a collision. Otherwise, it is normal and returned to the data changing unit 114 (steps S44 and S45).

  Next, when a collision has occurred, the data change unit 114 acquires user data using the item ID from the user data table 123 that matches the user data type (step S46). The data changing unit 114 returns the processing result of the collision occurrence and the acquired user data to the data access management unit 112. The data access management unit 112 generates a data change response from the received processing result of collision occurrence, user data, and the original data change request, and returns it to the communication unit 111. The communication unit 111 returns the passed data change response to the server communication unit 222 of the data access software 22 of the portable terminal 2 (step S47). The server communication unit 222 of the data access software 22 passes the received data change response to the data access unit 221. The data access unit 221 acquires the processing result from the data change response. The data access unit 221 acquires the user data type, item ID, and user data from the data change response because the processing result is a collision, and passes it to the cache management unit 223. The cache management unit 223 updates the user data corresponding to the item ID of the user data cache 232 that matches the passed user data type, and returns it to the data access unit 221 as normal. The data access unit 221 returns the processing result to the data use software 21 when a collision occurs. The data use software 21 uses the passed processing result for screen display, operation, etc., and does not perform the processes of steps S49 to S52 described below (steps S48 and S53).

  Next, if no collision has occurred, the data change unit 114 acquires the user data type, item ID, and user data from the data change request, and uses the item ID of the user data table 123 that matches the user data type as a key. Data is updated (step S49). Next, the data changing unit 114 sets the terminal ID, the user ID, the user data type, the item ID, and the access type = update and passes them to the cache state management unit 115. The cache status management unit 115 searches the cache status management table 124 that matches the user data type using the terminal ID, user ID, and item ID as keys, and updates the record with the cache status synchronized. Then, the terminal information table 122 is searched using the user ID as a key to check whether there is another terminal ID used by the same user. If it does not exist, the processing result is returned to the data changing unit 114 as normal. If it exists, the cache state management table 124 is searched using another terminal ID, user ID, and item ID as keys, the cache state is updated to not updated, and the processing result is returned to the data changing unit 114 as normal. By not updating the cache state of another mobile terminal of the same user, when the data management server is accessed from the other mobile terminal, the cache of another mobile terminal is updated according to the cache state. be able to. FIG. 13 shows an example in which the cache state is updated to be unupdated with another terminal ID used by the same user in the cache state management table 124 (steps S50 and S51).

  Next, the data change unit 114 returns the processing result to the data access management unit 112. The data access management unit 112 generates a data change response from the passed processing result and the original data change request and returns it to the communication unit 111. The communication unit 111 returns the passed data change response to the server communication unit 222 of the data access software 22 of the portable terminal 2 (step S52).

  Next, the server communication unit 222 of the data access software 22 passes the received data change response to the data access unit 221. The data access unit 221 returns the processing result acquired from the data change response to the data use software 21. The data use software 21 uses the passed processing result for screen display, operation, etc. (step S53).

(5) System Operation when Reflecting Updated User Data on Another Portable Terminal of the Same User FIG. 14 is a flowchart showing an operation when reflecting updated user data on another portable terminal of the same user. It is. First, the data use software 31 of the portable terminal 3 is activated, and the user confirms the screen display and performs an operation that requires reference to user data. Then, the data use software 31 specifies the user data to be referred to by the user data type and the item ID or the search condition, and makes a request to the data access unit 321 of the data access software 32. As a result of the inquiry to the cache management unit 323, the data access unit 321 does not have user data matching the user data type and item ID or search condition passed from the data use software 31 in the user data cache 332. A data reference request is made to the communication unit 111 of the data management software 11 of the data management server 1 via the unit 322. In the data reference request, a terminal ID, a user ID, a password for authentication, a specified user data type and item ID, or a search condition is set (step S61).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data reference request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data reference request Is passed to the data access management unit 112. The data access management unit 112 acquires the terminal ID, the user ID, and the user data type from the data reference request and passes them to the cache state management unit 115. The cache state management unit 115 records from the cache state management table 124 that matches the user data type, the records with the same terminal ID and user ID, and the cache state satisfies the unregistered / unupdated / undeleted / push delivery conditions (synchronization is possible). Necessary records) are retrieved and the presence / absence of user data requiring synchronization is returned to the data access management unit 112 (steps S62 and S63). If synchronization is unnecessary, the data access management unit 112 passes the data reference request to the data reference unit 113 and performs the same processing as steps S5 to S10, and does not perform the processing described below. If synchronization is required, the data access management unit 112 generates a data reference response from the processing result for data synchronization and the original data reference request, and returns the data reference response to the communication unit 111. The communication unit 111 returns the passed data reference response to the server communication unit 322 of the data access software 32 of the portable terminal 3. (Step S64).

  Next, the server communication unit 322 of the data access software 32 extracts the received data reference response and passes it to the data access unit 321. Since the data access unit 321 needs to synchronize the processing result acquired from the data reference response, the original data reference request is internally saved and put on hold, and the data management server 1 performs data management via the server communication unit 322. A data synchronization start request is sent to the communication unit 111 of the software 11. In the data synchronization start request, the terminal ID, user ID, password, and user data type to be synchronized are set (step S65).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data synchronization start request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data synchronization is performed. A start request is passed to the data access management unit 112. Then, the data access management unit 112 passes a data synchronization start request to the data change unit 114. The data change unit 114 acquires the terminal ID, the user ID, and the user data type to be synchronized from the data synchronization start request and passes them to the cache state management unit 115. The cache status management unit 115 searches the cache status management table 124 matching the user data type for a record having the same terminal ID and user ID and having a cache status of unregistered / unupdated / undeleted / push delivery conditions. . Since this example is an operation when the updated user data is reflected on another portable terminal of the same user, a record whose cache state is not updated is acquired. The cache status management unit 115 sets the processing flag of the corresponding record to ON, and returns the item ID and access type = update to the data change unit 114 as a set (step S66).

  Then, the data changing unit 114 acquires the user data of the item ID from the user data table 123 that matches the user data type, and sets the user data type, the item ID, the user data, and the access type = update as data as synchronization information. Return to the access management unit 112. The data access management unit 112 generates a data synchronization request from the received synchronization information and the original data synchronization start request and returns it to the communication unit 111. The communication unit 111 returns the received data synchronization request to the server communication unit 322 of the data access software 32 of the portable terminal 3. (Step E7)

  Next, the server communication unit 322 of the data access software 32 passes the received data synchronization request to the data access unit 321. The data access unit 321 acquires the synchronization information from the data synchronization request, extracts the user data type, item ID, and user data from the synchronization information and passes them to the cache management unit 323. The cache management unit 323 updates the user data corresponding to the item ID in the user data cache 331 that matches the passed user data type, and returns it to the data access unit 321 as normal. The data access unit 321 makes a pending data reference request together with the data synchronization response to the communication unit 111 of the data management software 11 of the data management server 1 via the server communication unit 322. The terminal ID, user ID, password, user data type, item ID, and processing result are set in the data synchronization response. The data reference request has the same contents as step S61 (step S68).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data synchronization response and the user information table 121 of the database 12. If the authentication result is normal, the communication unit 111 sends a data synchronization response and a data reference request. The data is transferred to the data access management unit 112. Then, the data access management unit 112 passes the data synchronization response to the data change unit 114. The data change unit 114 acquires the terminal ID, user ID, user data type, and item ID from the data synchronization response and passes them to the cache state management unit 115. The cache status management unit 115 searches the cache status management table 124 that matches the user data type using the terminal ID, user ID, and item ID as keys, updates the cache status of the corresponding record, and updates the processing flag to OFF. The processing result is returned to the data changing unit 114 as normal. Then, the data change unit 114 returns the processing result to the data access management unit 112 as normal. FIG. 15 shows an example in which a record whose cache state has not been updated in the cache state management table 124 is updated in synchronization (step S69). Next, the data access management unit 112 starts processing of the data reference request passed together with the data synchronization response, and thereafter performs the same processing as steps S5 to S10 (step S70).

(6) Operation of system when data usage software of mobile terminal deletes user data FIG. 16 is a flowchart showing an operation when data usage software of a mobile terminal deletes user data. First, the data use software 21 of the portable terminal 2 is activated, and the user confirms the screen display and performs a user data deletion operation. Then, the data use software 21 requests the data access unit 221 of the data access software 22 to delete the user data together with the user data type (step S71).

  Next, the data access unit 221 passes the user data type and item ID specified to the cache management unit 223. Then, the cache management unit 223 deletes the item ID and user data of the user data cache 232 that matches the user data type of the storage 23, and returns the processing result (step S72). Then, the data access unit 221 makes a data change request to the communication unit 111 of the data management software 11 of the data management server 1 via the server communication unit 222. In the data change request, the terminal ID, user ID, password, designated user data type and item ID, and access type = delete are set (step S73).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data change request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data change request Is passed to the data access management unit 112. Then, the data access management unit 112 passes a data change request to the data change unit 114. The data change unit 114 acquires the terminal ID, user ID, user data type, item ID, and access type = deletion from the data change request and passes them to the cache state management unit 115. The cache state management unit 115 acquires a record from the cache state management table 124 that matches the user data type using the terminal ID, user ID, and item ID as keys, and when the cache state is unregistered / unupdated / undeleted If a collision has occurred, otherwise normal and returned to the data changing unit 114 (steps S74 and S75).

  Next, when a collision has occurred, the data change unit 114 acquires user data using the item ID from the user data table 123 that matches the user data type (step S76). The data changing unit 114 returns the processing result of the collision occurrence and the acquired user data to the data access management unit 112. The data access management unit 112 generates a data change response from the received collision processing result, user data, and the original data change request, and returns the data change response to the communication unit 111. The communication unit 111 returns the passed data change response to the server communication unit 222 of the data access software 22 of the portable terminal 2 (step S77). The server communication unit 222 of the data access software 22 passes the received data change response to the data access unit 221. The data access unit 221 acquires the processing result from the data change response. The data access unit 221 acquires the user data type, item ID, and user data from the data change response because the processing result is a collision, and passes it to the cache management unit 223. The cache management unit 223 stores the item ID and user data of the user data cache 232 that matches the passed user data type, and returns it to the data access unit 221 as normal. The data access unit 221 returns the processing result to the data use software 21 when a collision occurs. The data utilization software 21 uses the passed processing result for screen display, operation, etc., and does not perform the processing of steps S79 to S83 described below (steps S78 and S84).

  Next, if no collision has occurred, the data changing unit 114 acquires the user data type and item ID from the data change request, searches using the item ID of the user data table 123 that matches the user data type as a key, and records Is deleted (step S79). Next, the data change unit 114 sets the terminal ID, user ID, user data type, item ID, and access type = deletion as a set and passes them to the cache state management unit 115. The cache state management unit 115 searches the terminal information table 122 using the user ID as a key, and checks whether there is another terminal ID used by the same user. If not, the cache status management unit 115 searches the cache status management table 124 that matches the user data type using the terminal ID, user ID, and item ID as keys to delete the record, and the data change unit 114 returns the processing result to normal. Return as. If it exists, the cache state management unit 115 searches the cache state management table 124 using the requesting terminal ID, user ID, and item ID as keys, and updates the record by deleting the cache state. Then, the cache status management unit 115 searches the cache status management table 124 using another terminal ID, user ID, and item ID as keys, updates the record without deleting the cache status, and normalizes the processing result in the data change unit 114. Return as. By leaving the cache state of the other mobile terminal undeleted, the cache is updated when the other mobile terminal accesses the data management server.

  FIG. 17 shows an example of updating the record by deleting the cache state with the requesting terminal ID in the cache state management table 124, and updating the record without deleting the cache state with another terminal ID used by the same user. (Steps S80 to S82).

  Next, the data change unit 114 returns the processing result to the data access management unit 112. The data access management unit 112 generates a data change response from the passed processing result and the original data change request and returns it to the communication unit 111. The communication unit 111 returns the passed data change response to the server communication unit 222 of the data access software 22 of the portable terminal 2 (step S83).

  Next, the server communication unit 222 of the data access software 22 passes the received data change response to the data access unit 221. The data access unit 221 returns the processing result acquired from the data change response to the data use software 21. The data use software 21 uses the passed processing result for screen display, operation, etc. (step S84).

(7) System Operation when Reflecting Deleted User Data on Another Portable Terminal of the Same User FIG. 18 is a flowchart showing an operation when reflecting deleted user data on another portable terminal of the same user. It is. First, the data use software 31 of the portable terminal 3 is activated, and the user confirms the screen display and performs an operation that requires reference to user data. Then, the data use software 31 specifies the user data to be referred to by the user data type and the item ID or the search condition, and makes a request to the data access unit 321 of the data access software 32. As a result of the inquiry to the cache management unit 323, the data access unit 321 does not have user data matching the user data type and item ID or search condition passed from the data use software 31 in the user data cache 332. A data reference request is made to the communication unit 111 of the data management software 11 of the data management server 1 via the unit 322. In the data reference request, the terminal ID, user ID, password, designated user data type and item ID, or search condition is set (step S91).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data reference request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data reference request Is passed to the data access management unit 112. The data access management unit 112 acquires the terminal ID, the user ID, and the user data type from the data reference request and passes them to the cache state management unit 115. The cache state management unit 115 searches the cache state management table 124 matching the user data type for a record having the same terminal ID and user ID and having a cache state of unregistered / unupdated / undeleted / push delivery conditions. Then, the presence / absence of user data requiring synchronization is returned to the data access management unit 112 (steps S92 and S93). If synchronization is unnecessary, the data access management unit 112 passes the data reference request to the data reference unit 113 and performs the same processing as steps S5 to S10, and does not perform the processing described below. If synchronization is necessary, the data access management unit 112 generates a data reference response from the processing result requiring data synchronization and the original data reference request, and returns the data reference response to the communication unit 111. The communication unit 111 returns the passed data reference response to the server communication unit 322 of the data access software 32 of the portable terminal 3 (step S94).

  Next, the server communication unit 322 of the data access software 32 extracts the received data reference response and passes it to the data access unit 321. Since the processing result obtained from the data reference response requires data synchronization, the data access unit 321 internally saves the original data reference request and puts it on hold. The data access server 321 receives the data of the data management server 1 via the server communication unit 322. A data synchronization start request is sent to the communication unit 111 of the management software 11. In the data synchronization start request, the terminal ID, user ID, password, and user data type to be synchronized are set (step S95).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data synchronization start request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data synchronization is performed. A start request is passed to the data access management unit 112. Then, the data access management unit 112 passes a data synchronization start request to the data change unit 114. The data changing unit 114 acquires the user data type synchronized with the terminal ID and the user ID from the data synchronization start request, and passes it to the cache state management unit 115. The cache state management unit 115 searches the cache state management table 124 matching the user data type for a record having the same terminal ID and user ID and having a cache state that satisfies the conditions of unregistered / unupdated / undeleted / push delivery. . Since this example is an operation for reflecting the deleted user data to another portable terminal of the same user, a record whose cache state is not deleted is acquired. The cache state management unit 115 sets the processing flag of the corresponding record to ON, and returns the item ID and access type = deletion to the data change unit 114 as a set (step S96). Then, the data change unit 114 sets the user data type, item ID, and access type = deletion as a set, and returns them to the data access management unit 112 as synchronization information. The data access management unit 112 generates a data synchronization request from the received synchronization information and the original data synchronization start request and returns it to the communication unit 111. The communication unit 111 returns the passed data synchronization request to the server communication unit 322 of the data access software 32 of the portable terminal 3 (step S97).

  Next, the server communication unit 322 of the data access software 32 passes the received data synchronization request to the data access unit 321. The data access unit 321 acquires synchronization information from the data synchronization request, extracts the user data type and item ID from the synchronization information, and passes them to the cache management unit 323. The cache management unit 323 deletes the user data corresponding to the item ID from the user data cache 331 that matches the passed user data type, and returns it to the data access unit 321 as normal. The data access unit 321 makes a pending data reference request together with the data synchronization response to the communication unit 111 of the data management software 11 of the data management server 1 via the server communication unit 322. The terminal ID, user ID, password, user data type, item ID, and processing result are set in the data synchronization response. The data reference request has the same contents as in step G1 (step S98).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data synchronization response and the user information table 121 of the database 12. If the authentication result is normal, the communication unit 111 sends a data synchronization response and a data reference request. The data is transferred to the data access management unit 112. Then, the data access management unit 112 passes the data synchronization response to the data change unit 114. The data change unit 114 acquires the terminal ID, user ID, user data type, and item ID from the data synchronization response and passes them to the cache state management unit 115. The cache status management unit 115 searches the cache status management table 124 that matches the user data type using the terminal ID, user ID, and item ID as keys, deletes the cache status of the corresponding record, and updates the processing flag to OFF. Then, the cache status management unit 115 searches the cache status management table 124 that matches the user data type using the user ID and item ID as keys, and checks whether there is a record whose cache status has not been deleted.

  If it exists, the cache state management unit 115 returns the processing result to the data change unit 114 as normal. If there is not, the cache state management unit 115 searches the cache state management table 124 that matches the user data type using the user ID and item ID as keys, deletes all corresponding records, normalizes the processing result, and the data change unit 114. Return to. Then, the data change unit 114 returns the processing result to the data access management unit 112 as normal. FIG. 19 shows an example in which the deletion of user data in the user data cache 331 of another terminal is completed and the records of all terminals in the cache status management table 124 are deleted (steps S99 to S101). Next, the data access management unit 112 starts processing of the data reference request passed together with the data synchronization response, and thereafter performs the same processing as steps S5 to S10 (step S102).

(8) Operation of system when data access software of mobile terminal deletes user data from cache FIG. 20 is a flowchart showing an operation when data access software of a mobile terminal deletes user data from the cache. First, the data use software 21 of the portable terminal 2 is activated, and the user confirms the screen display and performs an operation that requires reference to user data. Then, the data use software 21 designates user data to be referred to by the user data type and the item ID or the search condition, and makes a request to the data access unit 221 of the data access software 22 (step S111).

  Next, the data access software 22 and the data management software perform steps S2 to S9. At that time, the cache management unit 223 of the data access software 22 deletes some user data from the user data cache 232 due to a lack of capacity of the storage 23 of the data access software 22. The method for determining the cache deletion of user data is not particularly limited, such as using a known LRU algorithm or a unique algorithm. Then, the cache management unit 223 passes the user data type and item ID deleted from the cache to the data access unit 221. The data access unit 221 internally saves the user data type and item ID deleted from the cache in an internal memory or the like (step S112).

  Next, the data access unit 221 returns the user data type, item ID, and user data to the data use software 21. The data use software 21 uses the passed user data for screen display and operation (step S113).

  Next, the data access unit 221 makes a data change request to the communication unit 111 of the data management software 11 of the data management server 1 via the server communication unit 222. In the data change request, the terminal ID, user ID, password, internally saved user data type and item ID, and access type = cache deletion are set (step S114).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data change request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data change request Is passed to the data access management unit 112. Then, the data access management unit 112 passes a data change request to the data change unit 114. The data change unit 114 acquires the terminal ID, user ID, user data type, item ID, and access type = cache deletion from the data change request and passes them to the cache state management unit 115. The cache status management unit 115 acquires a record from the cache status management table 124 that matches the user data type using the terminal ID, user ID, and item ID as keys, updates the cache status to cache deletion, and displays the processing result as a data change unit. Return to 114. FIG. 21 shows an example in which the cache state of the record of the request source terminal ID is updated by deleting the cache in the cache state management table 124 (step S115).

  Next, the data change unit 114 returns the processing result to the data access management unit 112. The data access management unit 112 generates a data change response from the passed processing result and the original data change request and returns it to the communication unit 111. The communication unit 111 returns the passed data change response to the server communication unit 222 of the data access software 22 of the portable terminal 2 (step S116). Next, the server communication unit 222 of the data access software 22 passes the received data change response to the data access unit 221. The data access unit 221 acquires the processing result from the data change response (step S117).

(9) System Operation when Requesting Push Distribution of User Data to Mobile Terminal FIG. 22 is a flowchart showing the operation when the data management software of the data management server sets the push distribution of user data. First, a function unit for an administrator (not shown) in the data management software 11 passes a terminal ID, a user ID, a user data type, and an item ID to be pushed to the mobile terminal to the push delivery request unit 116 (step S121). .

  Next, the push distribution request unit 116 sets the terminal ID, the user ID, the user data type, the item ID, and the access type = push distribution to the cache state management unit 115 as a set. The cache status management unit 115 searches the cache status management table 124 that matches the user data type using the terminal ID, user ID, and item ID as keys, and checks whether a cache deletion record exists. If it does not exist, the processing result is returned to the push delivery request unit 116 as normal. If it exists, the cache state of the corresponding record is updated by push delivery, and the processing result is returned to the push delivery request unit 116 as normal. FIG. 23 shows an example in which the cache state of the record of the terminal ID targeted for push delivery is updated by push delivery in the cache state management table 124 (steps S122 to S124).

  Next, the push delivery request unit 116 returns the processing result to a function means for an administrator (not shown) in the data management software 11. Thereafter, access from a mobile terminal subject to push distribution is awaited (step S125).

(10) System Operation when Reflecting User Data with Push Distribution Set to Mobile Terminal FIG. 24 is a flowchart showing an operation when reflecting user data with push distribution set to a mobile terminal. First, the data use software 21 of the portable terminal 2 is activated, and the user confirms the screen display and performs an operation that requires reference to user data. Then, the data use software 31 specifies the user data to be referred to by the user data type and the item ID or the search condition, and makes a request to the data access unit 221 of the data access software 22. As a result of the inquiry to the cache management unit 223, the data access unit 221 does not have user data matching the user data type and item ID or search condition passed from the data use software 21 in the user data cache 232. A data reference request is made to the communication unit 111 of the data management software 11 of the data management server 1 via the unit 222. In the data reference request, the terminal ID, user ID, password, designated user data type and item ID, or search condition is set (step S131).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data reference request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data reference request Is passed to the data access management unit 112. The data access management unit 112 acquires a terminal ID, a user ID, and a user data type from the data reference request and passes them to the cache state management unit 115. The cache status management unit 115 searches the cache status management table 124 matching the user data type for a record having the same terminal ID and user ID and having a cache status of unregistered / unupdated / undeleted / push delivery. Then, the presence / absence of user data that needs to be synchronized is returned to the data access management unit 112 (steps S132 and S133). If synchronization is unnecessary, the data access management unit 112 passes the data reference request to the data reference unit 113 and performs the same processing as steps S5 to S10, and does not perform the processing described below. If synchronization is necessary, the data access management unit 112 generates a data reference response from the processing result requiring data synchronization and the original data reference request, and returns the data reference response to the communication unit 111. The communication unit 111 returns the passed data reference response to the server communication unit 222 of the data access software 22 of the portable terminal 3 (step S134).

  Next, the server communication unit 222 of the data access software 22 extracts the received data reference response and passes it to the data access unit 221. Since the processing result acquired from the data reference response requires data synchronization, the data access unit 221 internally saves the original data reference request and puts it on hold, and the data of the data management server 1 via the server communication unit 222 A data synchronization start request is sent to the communication unit 111 of the management software 11. In the data synchronization start request, the terminal ID, user ID, password, and user data type to be synchronized are set (step S135).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data synchronization start request and the user information table 121 and the terminal information table 122 of the database 12, and if the authentication result is normal, the data synchronization is performed. A start request is passed to the data access management unit 112. Then, the data access management unit 112 passes a data synchronization start request to the data change unit 114. The data change unit 114 acquires the user data type that is synchronized with the terminal ID and the user ID from the data synchronization start request and passes it to the cache state management unit 115. The cache state management unit 115 searches the cache state management table 124 matching the user data type for a record having the same terminal ID and user ID and having a cache state that satisfies the conditions of unregistered / unupdated / undeleted / push delivery. . In this example, since it is an operation when reflecting user data for which push delivery is set to the mobile terminal, the cache state acquires a push delivery record.

  The cache status management unit 115 sets the processing flag of the corresponding record to ON, and returns the item ID and access type = push delivery to the data change unit 114 as a set (step S136). Then, the data changing unit 114 acquires the user data of the item ID from the user data table 123 that matches the user data type, and sets the user data type, the item ID, the user data, the access type = push delivery as a set as synchronization information. Return to the access management unit 112. The data access management unit 112 generates a data synchronization request from the received synchronization information and the original data synchronization start request and returns it to the communication unit 111. The communication unit 111 returns the passed data synchronization request to the server communication unit 222 of the data access software 22 of the mobile terminal 2 (step S137).

  Next, the server communication unit 222 of the data access software 22 passes the received data synchronization request to the data access unit 221. The data access unit 221 acquires the synchronization information from the data synchronization request, extracts the user data type, item ID, and user data from the synchronization information and passes them to the cache management unit 223. The cache management unit 223 stores the item ID and user data in the user data cache 232 that matches the passed user data type, and returns it to the data access unit 221 as normal. The data access unit 221 makes a pending data reference request together with a data synchronization response to the communication unit 111 of the data management software 11 of the data management server 1 via the server communication unit 222. The terminal ID, user ID, password, user data type, item ID, and processing result are set in the data synchronization response. The data reference request has the same contents as in step S131 (step S138).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data synchronization response and the user information table 121 of the database 12. If the authentication result is normal, the communication unit 111 sends a data synchronization response and a data reference request. The data is transferred to the data access management unit 112. Then, the data access management unit 112 passes the data synchronization response to the data change unit 114. The data change unit 114 acquires the terminal ID, user ID, user data type, and item ID from the data synchronization response and passes them to the cache state management unit 115. The cache status management unit 115 searches the cache status management table 124 that matches the user data type using the terminal ID, user ID, and item ID as keys, updates the cache status of the corresponding record, and updates the processing flag to OFF. The processing result is returned to the data changing unit 114 as normal. Then, the data change unit 114 returns the processing result to the data access management unit 112 as normal. FIG. 25 shows an example in which the cache status is updated in the cache status management table 124 with the cache status being synchronized (step S139).

  Next, the data access management unit 112 starts processing of the data reference request passed together with the data synchronization response, and thereafter performs the same processing as steps S5 to S10 (step S140).

  In the first embodiment, a case where a mobile phone is used as the mobile terminals 2 and 3 has been described. Is also applicable.

  Further, the case where the data management server 1 and the portable terminals 2 and 3 are connected by the communication line 4 such as the Internet has been described. However, in order to increase security, a firewall is provided between the data management server 1 and the Internet. It may be configured.

  Furthermore, although the case where the database 12 of the data management server 1 is used for storing user data has been described, a file system may be used.

  Furthermore, in the first embodiment, a case has been described in which authentication processing is performed by the communication unit 111 of the data management software 11 of the data management server 1 each time a request is made from the data access software 22 and 32 to the data management server 1. If the authentication result is normal, a known session management function provided by the AP server may be used thereafter, and the authentication process may be omitted while the session is valid.

  In addition, although the case where the user data table 123 and the cache state management table 124 are prepared as a set for each user data type has been described, a plurality of user data types are used in a set of the user data table 123 and the cache state management table 124. You may comprise as follows. In that case, the user data type is added as a key to the user data table 123 and the cache status management table 124.

  Furthermore, although the case where the data reference request, the data change request, the data synchronization request, and the data synchronization response are processed for one item has been described, information regarding a plurality of items may be processed.

  Furthermore, in the first embodiment, the data reference request, the data change request, the data synchronization start request, the data synchronization request, and the data synchronization response have been described with respect to processing for one user data type. You may comprise so that a classification may be processed.

  In addition, the case where the data access request is transmitted from the data access software when the changed user data is reflected on another mobile terminal of the same user has been described. Another message such as a request may be used.

  Furthermore, the case where the data change request is transmitted to the data management server at the timing when the user data is changed has been described. The request may be saved internally and transmitted to the data management server after line restoration.

  Next, the effect of the present embodiment will be described. The first effect is that the server side can manage the cache state of the user data of the portable terminal. For example, the latest data is stored in Mr. A's address data in a portable terminal, and the server can manage the cache state such that Mr. B's address data is deleted from the cache.

  The reason is that a cache status storage area is prepared for each terminal, user, and item in the cache status management table of the data management server, and the cache status of the cache status table is updated every time user data is accessed from the mobile terminal. This is because the information is kept up to date.

  The second effect is that when the user data is changed by the mobile terminal, the change can be reflected to another mobile terminal used by the same user who stores the old user data in the cache. For example, when a schedule is updated on a mobile terminal, the change can be reflected in the cache of another mobile terminal at the timing when another mobile terminal used by the same user storing the old schedule in the cache accesses the server.

  The reason is that the cache state of the cache state management table is updated not only for the mobile terminal whose user data is changed, but also for another mobile terminal used by the same user, and when the server is accessed from another mobile terminal. This is because data can be synchronized by checking the management table.

  The third effect is that user data can be stored in the cache of the portable terminal based on the determination on the server side. For example, when a new schedule is registered in the server, but Mr. A's address data related to the schedule is deleted from the mobile terminal, the address data of Mr. A is stored in the cache of the mobile terminal together with the new schedule data. Can do.

  The reason is that by setting the cache state of the cache state management table to push delivery, it can be processed as a target of data synchronization even if the user data is not changed.

[Second embodiment. ]
Next, the configuration of the second embodiment of the present invention will be described in detail with reference to the drawings. FIG. 26 is a diagram showing a terminal cache state management system according to the second exemplary embodiment of the present invention. Referring to FIG. 26, the terminal cache state management system 101 includes a data management server 1, a portable terminal 2 used by the same user, a portable terminal 3, and a PC 5. The data management server 1, the mobile terminal 2, the mobile terminal 3, and the PC 5 are connected via a communication line 4 such as the Internet for communication.

  The data management server 1 has the same configuration as that of the first embodiment, and differs only in that a request for data access is received from the PC 5. The portable terminals 2 and 3 have the same configuration as in the first embodiment. The PC 5 includes a web browser 51.

  FIG. 27 is a block diagram of the data management server according to the present embodiment. Referring to FIG. 27, the data management software 11 has a content providing unit 117 added to the first embodiment shown in FIG. The content providing unit 117 of the data management software 11 added in the present embodiment generally operates as follows.

  The content providing unit 117 can use functions for referencing, registering, updating, and deleting user data based on a content acquisition request from the Web browser 51 of the PC 5 passed from the communication unit 111, and dynamically generates content. And return. The function of dynamically generating content uses a known method of the AP server.

  Next, the operation of the second embodiment of the present invention will be described in detail. First, the operation of the system at the preparation stage will be described. The data management server 1, the portable terminal 2, and the portable terminal 3 operate in the same manner as in the first embodiment. A web browser 51 is installed in the PC 5 in advance. Alternatively, a Web browser already installed on the PC 5 is used. Further, the user of the PC 5 is notified in advance of a URL for accessing the data management software 11 of the data management server 1.

  The operation of the system when the data use software of the portable terminal refers to the user data is the same as that of the first embodiment.

(11) System Operation when PC Web Browser References User Data FIG. 28 is a flowchart showing an operation when the PC Web browser references user data. First, the web browser 51 of the PC 5 is activated to download and display content relating to access to user data from the data management server 1, and the data management software of the data management server 1 is operated by operating the screen components associated with the data reference. 11 data reference requests to the 11 communication units 111. In the data reference request, the user ID, password, designated user data type and item ID, or search condition is set (step S141).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data reference request and the user information table 121 of the database 12. 112. Then, the data access management unit 112 passes a data reference request to the data reference unit 113. The data reference unit 113 acquires the user data type and item ID or search condition from the data reference request. Then, user data is acquired from the user data table 123 that matches the user data type using the item ID or the search condition. If the search condition is used, the item ID is also acquired together with the user data (step S142).

  Next, the data reference unit 113 returns the acquired user data to the data access management unit 112. The data access management unit 112 generates a data reference response from the received user data and the original data reference request and returns it to the communication unit 111. The communication unit 111 returns the received data reference response to the web browser 51 of the PC 5 (step S143).

  The operation of the system when the data use software of the portable terminal registers user data is the same as that of the first embodiment.

(12) Operation of System When PC Web Browser Registers User Data FIG. 29 is a flowchart showing an operation when the PC Web browser registers user data. First, the web browser 51 of the PC 5 is activated to download and display content relating to access to user data from the data management server 1, and the data management software of the data management server 1 is operated by operating screen components associated with data registration. 11 data change requests to the 11 communication units 111. In the data change request, the user ID, password, designated user data type, user data, and access type = registration are set (step 151).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data change request and the user information table 121 of the database 12, and if the authentication result is normal, the data change request is sent to the data access management unit. 112. Then, the data access management unit 112 passes a data change request to the data change unit 114. The data change unit 114 newly assigns an item ID of the user data type acquired from the data change request, and registers the user data acquired from the data change request in the user data table 123 that matches the user data type with the item ID. (Step S152).

  Next, the data changing unit 114 sets the user ID, user data type, item ID, and access type = registration as a set and passes them to the cache state management unit 115. The cache state management unit 115 searches the terminal information table 122 using the user ID as a key, and checks whether there is a terminal ID used by the user ID. If it does not exist, the processing result is returned to the data changing unit 114 as normal. If it exists, the record is registered in the cache status management table 124 with the terminal ID, the user ID, and the item ID as keys as unregistered records for all terminals, and the processing result is returned to the data changing unit 114 as normal. By updating the cache state of the mobile terminal of the same user, cache management can be performed in the same manner, and data synchronization can be performed when the mobile terminal accesses the data management server. FIG. 30 shows an example in which the cache status is registered as unregistered with the terminal IDs of all the terminals used by the same user in the cache status management table 124 (step S153).

  Next, the data change unit 114 returns the processing result and the numbered item ID to the data access management unit 112. The data access management unit 112 generates a data change response from the passed processing result, item ID, and original data change request, and returns it to the communication unit 111. The communication unit 111 returns the passed data change response to the web browser 51 of the PC 5 (step S154).

  The operation of the system when the registered user data is reflected on another portable terminal of the same user is the same as that of the first embodiment.

  The operation of the system when the data use software of the portable terminal updates the user data is the same as that of the first embodiment.

(13) System Operation when PC Web Browser Updates User Data FIG. 31 is a flowchart showing the operation when the PC Web browser updates user data. First, the web browser 51 of the PC 5 is activated to download and display content related to access to user data from the data management server 1, and the data management software of the data management server 1 is operated by operating screen components associated with the data update. 11 data change requests to the 11 communication units 111. In the data change request, the user ID, password, designated user data type and item ID, user data, and access type = update are set (step S161).

  Next, the communication unit 111 of the data management software 11 performs authentication processing using the user information of the data change request and the user information table 121 of the database 12, and if the authentication result is normal, the data change request is sent to the data access management unit. 112. Then, the data access management unit 112 passes a data change request to the data change unit 114. The data change unit 114 acquires the user data type, item ID, and user data from the data change request, and updates the user data using the item ID of the user data table 123 that matches the user data type as a key (step S162).

  Next, the data changing unit 114 sets the user ID, user data type, item ID, and access type = update as a set and passes them to the cache state management unit 115. The cache state management unit 115 searches the terminal information table 122 using the user ID as a key, and checks whether there is a terminal ID used by the user ID. If it does not exist, the processing result is returned to the data changing unit 114 as normal. If it exists, the record is updated without updating the cache state with the terminal ID, user ID, and item ID as keys for all terminals in the cache state management table 124, and the processing result is returned to the data changing unit 114 as normal. By updating the cache state of the mobile terminal of the same user, cache management can be performed in the same manner, and data synchronization can be performed when the mobile terminal accesses the data management server. FIG. 32 shows an example of updating the record without updating the cache status with the terminal IDs of all terminals used by the same user in the cache status management table 124 (step S163).

  Next, the data change unit 114 returns the processing result to the data access management unit 112. The data access management unit 112 generates a data change response from the passed processing result and the original data change request and returns it to the communication unit 111. The communication unit 111 returns the passed data change response to the web browser 51 of the PC 5 (step S164).

  The operation of the system when the updated user data is reflected on another portable terminal of the same user is the same as that of the first embodiment.

  The operation of the system when the data utilization software of the portable terminal deletes user data is the same as that of the first embodiment.

(14) System Operation when PC Web Browser Deletes User Data FIG. 33 is a flowchart showing the operation when the PC Web browser deletes user data. First, the web browser 51 of the PC 5 is activated to download and display content relating to access to user data from the data management server 1, and the data management software of the data management server 1 is operated by operating screen components associated with data deletion. 11 data change requests to the 11 communication units 111. In the data change request, user ID, password, designated user data type and item ID, and access type = delete are set (step S171).

Next, the communication unit 111 of the data management software 11 performs the authentication process using the user information table 121 of the user information and the database 12 of the data change request, the authentication result data access managing data change request if successful To the unit 112. Then, the data access management unit 112 passes a data change request to the data change unit 114. The data change unit 114 acquires the user data type and item ID from the data change request, searches using the item ID of the user data table 123 that matches the user data type as a key, and deletes the record (step S172).

  Next, the data change unit 114 sets the user ID, the user data type, the item ID, and the access type = deletion as a set and passes them to the cache state management unit 115. The cache state management unit 115 searches the terminal information table 122 using the user ID as a key, and checks whether there is a terminal ID used by the user ID. If it does not exist, the processing result is returned to the data changing unit 114 as normal. If it exists, the cache status management table 124 updates the record without deleting the cache status using the terminal ID, user ID, and item ID as keys for all terminals, and returns the processing result to the data change unit 114 as normal. By updating the cache state of the mobile terminal of the same user, cache management can be performed in the same manner, and data synchronization can be performed when the mobile terminal accesses the data management server. FIG. 34 shows an example in which the cache state is not deleted and the record is updated with the terminal IDs of all terminals used by the same user in the cache state management table 124 (step S173).

  Next, the data change unit 114 returns the processing result to the data access management unit 112. The data access management unit 112 generates a data change response from the passed processing result and the original data change request and returns it to the communication unit 111. The communication unit 111 returns the passed data change response to the Web browser 51 of the PC 5 (step S174).

  The operation of the system when the deleted user data is reflected on another portable terminal of the same user is the same as that of the first embodiment.

  The operation of the system when the data access software of the portable terminal deletes user data from the cache is the same as that of the first embodiment.

  The operation of the system when requesting push distribution of user data to the portable terminal is the same as that of the first embodiment.

  The operation of the system when reflecting user data for which push distribution is set to the mobile terminal is the same as that of the first embodiment.

  In the second embodiment of the present invention, the Web browser 51 of the PC 5 is used, but a dedicated application capable of processing the content downloaded from the content providing unit 117 of the data management server 1 is used. Also good.

In the second embodiment, the content providing unit 117 is arranged in the data management software 11 of the data management server 1. However, only the content providing unit 117 is arranged in a separate server, and the data management server 1 performs data management. You may comprise so that communication with the software 11 may be performed.
The contents described as other configurations in the first embodiment are also applicable to the second embodiment.

  This embodiment also has the same effect as the first embodiment. Further, the content providing unit 117 can use user data reference, registration, update, and deletion functions based on a content acquisition request from the Web browser 51 of the PC 5 passed from the communication unit 111, and dynamically Generate and update user data. Also in this case, the cache state of the portable terminal is appropriately updated from the data management server 1, and the cache data of the portable terminal is managed by the data management server 1 by updating when the cache data of the portable terminal is to be updated. can do.

  It should be noted that the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the scope of the present invention. For example, in the above-described embodiments, the hardware configuration has been described. However, the present invention is not limited to this, and any processing can be realized by causing a CPU (Central Processing Unit) to execute a computer program. It is. In this case, the computer program can be provided by being recorded on a recording medium, or can be provided by being transmitted via the Internet or another transmission medium.

It is a figure which shows the terminal cache management server for demonstrating the principle of this invention. It is a figure which shows the terminal cache state management system concerning 1st Example of this invention. It is a block diagram which shows the data management server in the terminal cache state management system concerning 1st Example of this invention. It is a block diagram which shows the portable terminal in the terminal cache state management system concerning the 1st example of the present invention. It is a block diagram which shows the portable terminal 3 in the terminal cache state management system concerning 1st Example of this invention. The configuration of the mobile terminal 3 is the same as that of the mobile terminal 2. It is a flowchart which shows the operation | movement at the time of the data utilization software of a portable terminal referring data. It is a figure which shows a cache status management table in the case of updating a cache status from cache deletion to synchronized in the cache status management table 124. It is a flowchart which shows the operation | movement at the time of data utilization software of a portable terminal registering user data. It is a figure which shows a cache status management table in the case of registering a record with a cache ID synchronized with a requesting terminal ID, and registering a record without registering a cache status with another terminal ID used by the same user. It is a flowchart which shows the operation | movement at the time of reflecting the registered user data on another portable terminal of the same user. It is a figure which shows the cache state management table in the case of updating the record in which a cache state is unregistered to be synchronized. It is a flowchart which shows operation | movement when the data utilization software of a portable terminal updates user data. It is a figure which shows the cache state management table in the case of updating a cache state by another terminal ID which the same user uses to unupdate. It is a flowchart which shows the operation | movement at the time of reflecting the updated user data on another portable terminal of the same user. It is a figure which shows the cache state management table in the case of updating the record in which a cache state is not updated synchronously. It is a flowchart which shows the operation | movement at the time of the data utilization software of a portable terminal deleting user data. It is a figure which shows a cache state management table in the case of updating a record by deleting a cache state with a terminal ID of a request source, and updating a record without deleting a cache state with another terminal ID used by the same user. It is a flowchart which shows the operation | movement at the time of reflecting the deleted user data on another portable terminal of the same user. It is a figure which shows the cache status management table in case deletion of the user data of the user data cache 331 of another terminal is completed, and the record of all the terminals of the cache status management table 124 is deleted. It is a flowchart which shows the operation | movement when the data access software of a portable terminal deletes user data from a cache. It is a figure which shows the cache state management table in the case of updating the cache state of the record of the terminal ID of a request origin by cache deletion. It is a flowchart which shows operation | movement at the time of the data management software of a data management server setting the push delivery of user data. It is a figure which shows the cache state management table in the case of updating the cache state of the record of the terminal ID of push delivery object by push delivery in the cache state management table. It is a flowchart which shows the operation | movement at the time of reflecting the user data in which push delivery was set to a portable terminal. It is a figure which shows a cache state management table in case a cache state updates the record of push delivery in synchronization. It is a figure which shows the terminal cache state management system concerning the 2nd Example of this invention. It is a block diagram which shows the data management server in the terminal cache state management system concerning 2nd Example of this invention. It is a flowchart which shows the operation | movement at the time of the web browser of PC referring user data. It is a flowchart which shows operation | movement at the time of the web browser of PC registering user data. It is a figure which shows the cache state management table in the case of registering a record without registering a cache state with terminal IDs of all terminals used by the same user. It is a flowchart which shows the operation | movement at the time of the web browser of PC updating user data. It is a figure which shows the cache status management table in the case of updating a record without updating the cache status with the terminal IDs of all terminals used by the same user. It is a flowchart which shows the operation | movement when the web browser of PC deletes user data. It is a figure which shows a cache state management table in the case of updating a record by deleting the cache state with terminal IDs of all terminals used by the same user.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Data management server 2 Mobile terminal 4 Communication line 11 Data management software 12 Database 21 Data use software 22 Data access software 23 Storage 31 Data use software 32 Data access software 33 Storage 51 Browser 100, 101 Terminal cache state management system 111 Communication part 112 Data access management unit 113 Data reference unit 114 Data change unit 115 Cache state management unit 116 Push distribution request unit 117 Content provision unit 121 User information table 122 Terminal information table 123 User data table 124 Cache state management table 151 Step 212 Server communication unit 221 Data access unit 222 Server communication unit 223 Cache management unit 231 User information 232 User The data cache 321 Data access unit 322 Server communication unit 323 Cache management unit 331 User data cache 332 User data cache

Claims (28)

A data management server for managing the cache of a mobile terminal having a cache,
Communication means for communicating with the portable terminal;
Data access management means for accepting a request for user data access from the mobile terminal;
Cache status management means for managing the cache status of the mobile terminal;
A user data table for storing user data used in the mobile terminal;
A cache status management table for managing the cache status for each mobile terminal;
When the request regarding the access is received, the cache state management means refers to the cache state management table, checks whether or not the cache of the mobile terminal needs to be updated to the latest data, and if necessary A terminal cache management device for updating a cache of the mobile terminal. When the access request is a data reference request for reading user data, and the cache data of the mobile terminal is the latest data,
Read the user data requested for data reference from the user data table,
The cache state management unit updates the cache state of the corresponding user data in the cache state management table to be synchronized indicating that the cache data of the mobile terminal is the latest data. Terminal cache management device. Further comprising data changing means for changing user data in the user data table;
If the access request is a data registration request for registering user data,
The data access management means receives user data for registration with a temporary ID attached from the portable terminal,
The data changing means registers the user data for registration in the user data table with an item ID for identifying the user data,
The cache state management unit updates the cache state of the corresponding user data in the cache state management table to be synchronized indicating that the cache data of the mobile terminal is the latest data. 3. The terminal cache management device according to 2. A terminal information table storing a user ID for identifying a user and a terminal ID for identifying one or more portable terminals used by the same user;
The cache status management means refers to the terminal information table and checks whether there is another terminal ID used by the same user as the portable terminal that has registered the user data for registration. 4. The terminal according to claim 3, wherein if there is, the corresponding cache state of the cache state management table is set to unregistered indicating that the user data is not registered in the cache of another mobile terminal. 5. Cache management device. In the cache state management table, if there is cache state unupdated indicating that there is unupdated user data that has not been updated yet on the mobile terminal,
The access management means receives a request for access from the mobile terminal,
After the cache status management means has above with reference to the cache status management table to detect the non-updated user data, and transmitting said non-updated user data from the communication unit to the portable terminal, the cache state of the corresponding user data The terminal cache management apparatus according to claim 1, wherein the cache data of the mobile terminal is updated in synchronization indicating that the cache data is the latest data. In the cache state management table, if there is a cache state unregistered indicating that there is unregistered user data that is not yet registered in the mobile terminal,
The access management means receives a request for access from the mobile terminal,
The cache status management means detects the unregistered user data with reference to the cache status management table, and transmits the unregistered user data to the mobile terminal from the communication means, and then determines the cache status of the corresponding user data. The terminal cache management apparatus according to claim 1, wherein the cache data of the mobile terminal is updated in synchronization indicating that the cache data is the latest data. In the cache state management table, if there is cache state undeleted indicating that there is undeleted user data that has not been deleted yet on the mobile terminal,
The access management means receives a request for access from the mobile terminal,
The cache status management means detects the undeleted user data with reference to the cache status management table, and transmits the undeleted user data to the mobile terminal from the communication means, and then determines the cache status of the corresponding user data. The terminal cache management apparatus according to claim 1, wherein the cache data of the mobile terminal is updated in synchronization indicating that the cache data is the latest data. Further comprising data changing means for changing user data in the user data table;
If the access request is a data update request for updating user data,
The access management means receives a data update request including an item ID of user data from the portable terminal,
6. The terminal cache management device according to claim 5, wherein the data changing unit updates user data of an item ID included in the data update request in the user data table. A terminal information table storing a user ID for identifying a user and a terminal ID for identifying one or more portable terminals used by the same user;
The cache state management means refers to the terminal information table and checks whether there is another terminal ID used by the same user as the mobile terminal that has updated the user data. The terminal cache management device according to claim 8, wherein the corresponding cache state of the cache state management table is set to an unupdated state indicating that the user data is not updated in a cache of another mobile terminal. . Further comprising data changing means for changing user data in the user data table;
If the access request is a data update request for updating user data,
The access management means receives a data update request from the mobile terminal,
The cache management means confirms that the user data included in the data update request has been synchronized with reference to the cache state management table, indicating that the user data is the latest data,
The terminal cache management device according to any one of claims 1 to 9, wherein the data change unit updates the user data table with user data included in the data update request. Further comprising data changing means for changing user data in the user data table;
If the access request is a data deletion request for deleting user data,
The access management means receives a data deletion request including an item ID of user data from the portable terminal,
The data changing means deletes the user data of the item ID included in the data deletion request from the user data table,
The cache state management unit updates the cache state of the corresponding user data in the cache state management table to a deletion indicating deletion from the cache of the mobile terminal. The terminal cache management device according to item. A terminal information table storing a user ID for identifying a user and a terminal ID for identifying one or more portable terminals used by the same user;
The cache state management means refers to the terminal information table and checks whether there is another terminal ID used by the same user as the portable terminal from which the user data has been deleted. The terminal cache management apparatus according to claim 11, wherein the corresponding cache state of the cache state management table is set to undeleted indicating that the user data in the cache of another mobile terminal has not been deleted. . When the request for access is a data change request notifying that the mobile terminal is a cache deletion indicating a state in which user data is deleted from the cache,
The access management means receives the data change request from the mobile terminal,
The cache state management unit updates a cache state of an item ID included in the data change request to the cache deletion in the cache state management table. Terminal cache management device. When the request regarding the access is a push delivery request for setting the user data stored in the user data table to be push delivered to the mobile terminal,
The access management means receives the push delivery request,
When the cache state of the item ID included in the push distribution request is a cache deletion indicating a state in which user data is deleted from the cache of the mobile terminal, the cache state management unit sets the cache state to the push distribution state. The terminal cache management apparatus according to any one of claims 1 to 13, wherein the terminal cache management apparatus is updated. When there is a request regarding the access, the cache status management means refers to the cache status management table and checks whether there is an item ID whose cache status is push delivery,
The terminal cache management device according to claim 14, wherein the communication unit transmits user data whose cache state is push distribution to the mobile terminal. 16. The terminal cache management apparatus according to claim 1, wherein the user data table is referred to by a computer connected via a network. The user data table has user data registered, updated or deleted by the computer,
The cache status management means updates the cache status of the corresponding user data in the cache status management table, indicates that no user data is registered in the cache of the portable terminal, and updates the user data in the cache. The terminal cache management device according to claim 16, wherein the terminal cache management device is updated to unupdated indicating that there is no data and undeleted indicating that user data in the cache has not been deleted. A data management method for managing a cache of a mobile terminal having a cache,
Accepts a request for user data access from the mobile terminal,
Refer to the cache status management table for managing the cache status of the mobile terminal, and check whether it is necessary to update the user data of the cache to the latest user data,
A terminal cache management method for transmitting user data read from a user data table to the mobile terminal so as to update the cache data of the mobile terminal to the latest state when updating to the latest user data is required. The request for access includes a user data type indicating the type of the user data, a terminal ID for identifying the portable terminal, and a user ID for identifying the user of the portable terminal,
When receiving a data reference request for reading user data from the portable terminal, whether or not the cache state management table needs to be searched and updated to the latest user data by the user data type, the terminal ID, and the user ID The terminal cache management method according to claim 18, wherein the check is performed. The request for access includes a user data type indicating the type of the user data, a terminal ID for identifying the mobile terminal, a user ID for identifying a user of the mobile terminal, and an item ID for identifying user data,
When receiving a data reference request for reading user data from the portable terminal, it is necessary to search the cache state management table and update it to the latest user data based on the user data type, terminal ID, user ID, and item ID. 19. The terminal cache management method according to claim 18, wherein whether or not there is present is checked. As a request regarding the access, a data reference request for reading user data is received,
Check whether it is necessary to search the cache status management table and update to the latest user data by the user data type, terminal ID and user ID,
If there is no need to update, read the corresponding user data from the user data table,
Update the cache status of the corresponding user data in the cache status management table to be synchronized indicating that the cache data of the mobile terminal is the latest data,
21. The terminal cache management method according to claim 19 or 20, wherein the read user data is transmitted to the mobile terminal. As a request regarding the access, a data registration request for registering user data is received,
Obtaining user data for registration included in the data registration request and a temporary ID attached thereto, and assigning an item ID for identifying the user data to the user data;
In the cache status management table, the cache status of the user data is registered with synchronization indicating that the cache data of the mobile terminal is the latest data,
The terminal cache management method according to claim 19 or 20, wherein the assigned item ID is transmitted to the portable terminal. A data reference request for referring to user data is received as a request regarding the access,
Check whether it is necessary to search the cache status management table and update to the latest user data by the user data type, terminal ID and user ID,
If you need to update, send a notification to the mobile device that you need to sync,
Receive a data synchronization start request to synchronize user data from the mobile terminal,
With reference to the cache state management table, user data that needs to be synchronized is read from the user data table,
Transmitting the user data to the mobile terminal;
A data synchronization response indicating that the cache has been updated with the user data and the data reference request are received from the mobile terminal,
Update the cache state of the corresponding user data in the cache state management table to be synchronized,
The terminal cache management method according to claim 21, wherein the data reference request processing is executed. As a request for the access, a data deletion request for deleting user data is received,
Check whether it is necessary to search the cache status management table and update to the latest user data by the user data type, terminal ID, user ID and item ID,
If it is not necessary to update to the latest user data, use the item ID that identifies the user data included in the data deletion request, delete the corresponding data in the user data table,
The terminal cache management method according to claim 20, wherein the cache state of the corresponding user data in the cache state management table is updated to delete. When there is another terminal ID used by the same user by referring to a terminal information table storing a user ID for identifying the user and a terminal ID for identifying one or more portable terminals used by the same user, the cache state The terminal cache management method according to claim 24, wherein the cache state of the corresponding user data in the management table is updated to undeleted indicating that the user data has not been deleted from the cache of another mobile terminal. As a request regarding the access, a data change request for notifying cache deletion indicating that user data has been deleted from the cache of the mobile terminal is received,
The terminal cache management method according to any one of claims 18 to 20, wherein the corresponding cache state of the cache state management table is updated to cache deletion. User data in the user data table is registered, updated or deleted by a computer connected via a network,
The cache status of the corresponding user data in the cache status management table is unregistered indicating that the user data is not registered in the cache of the mobile terminal, unupdated indicating that the user data in the cache is not updated, The terminal cache management method according to any one of claims 18 to 26, wherein the cache is updated to undeleted indicating that the user data of the cache has not been deleted. A program for causing a computer to execute an operation of managing a cache of a mobile terminal having a cache,
Accepts a request for user data access from the mobile terminal,
Referring to a cache status management table for managing the cache status of the mobile terminal, and checking whether or not the user data in the cache needs to be updated to the latest user data;
A program for transmitting user data read from a user data table to the mobile terminal in order to update the cache data of the mobile terminal to the latest state when updating to the latest user data is required.

Images