JP2008187479A - Data management server, data management method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that there is possibility that an address book stored at a server side is deleted according to the operation of any person other than the normal user of a portable terminal. <P>SOLUTION: This data management server is provided with a data storage part for storing data in response to a request from a portable communication terminal; a data updating part for correcting data stored in the data storage part; a matching permission/non-permission storage part for accepting and storing the permission/non-permission of the matching of the data stored in the data storage part with data stored in the portable communication terminal from a maintenance communication terminal; and a data matching part for, in the case of receiving a matching request from the portable communication terminal, matching the data stored in the data storage part with the data stored in the portable communication terminal when information showing the permission of matching is stored in the matching permission/non-permission storage part, and not for matching the data stored in the data storage part with the data stored in the portable communication terminal when information showing the non-permission of matching is stored in the matching permission/non-permission storage part. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a data management server, a data management method, and a program. The present invention relates to a data management server, a data management method, and a program for managing data stored and used in a mobile communication terminal.

A portable terminal that locks some functions by wireless communication is known (for example, see Patent Document 1). In addition, a server that stores an address book of a mobile terminal by operating the mobile terminal is known (for example, see Patent Document 2).
JP 2006-261990 A JP 2006-203512 A

  However, when the mobile terminal is not turned on or the mobile terminal is out of range, the function of managing the address book cannot be locked. Therefore, there is a problem that the address book stored on the server side may be erased by the operation of a person other than the authorized user of the mobile terminal.

  In order to solve the above-described problem, according to an embodiment of the present invention, a data management server stores data stored and used in a mobile communication terminal, and stores data in response to a request from the mobile communication terminal. A data storage unit, a data updating unit for adding, changing or deleting data stored in the data storage unit in response to a request from a maintenance communication terminal for maintaining data, and data stored in the data storage unit and mobile communication Matching permission / non-registration storage unit that accepts and accepts matching / non-matching with data stored in terminal from maintenance communication terminal, and matching matching / non-registration storage unit when receiving matching request requesting matching from mobile communication terminal When the information indicating that the data is permitted is stored, the data stored in the data storage unit and the data stored in the portable communication terminal are matched, while the matching permission / inhibition memory is stored. When information indicating that does not allow the matching is stored in the is provided with a data matching unit that does not align the data stored with the data stored in the data storage unit in the portable communication terminal. As a result, it is possible to prevent erasure of data stored as a backup in the server. For example, even if data in a mobile communication terminal that has been lost or stolen is erased by a finder or theft, the server rejects the consistency request to reflect the contents after erasure on the server. The stored data can be prevented from being erased. Furthermore, since the communication function of the mobile communication terminal is not limited, it is possible to maintain and secure a means for contacting the finder or theft.

  The above summary of the invention does not enumerate all the necessary features of the present invention, and sub-combinations of these feature groups can also be the invention.

  Hereinafter, the present invention will be described through embodiments of the invention. However, the following embodiments do not limit the invention according to the scope of claims, and all combinations of features described in the embodiments are included. It is not necessarily essential for the solution of the invention.

  FIG. 1 schematically shows an example of the data management system 10. The data management system 10 includes a mobile communication terminal 20 and a data management server 30. The mobile communication terminal 20 includes a display 22 and an operation panel 24. The mobile communication terminal 20 uses a display 22 and an operation panel 24 to input input from a user to register data related to a communication partner such as an individual, a store, or a service provider (hereinafter referred to as “contact data”). And store it in the address book. The contact data includes the name, telephone number, mail address, etc. of the communication partner. The mobile communication terminal 20 communicates with another mobile communication terminal 700 via a radio access network and a core network, and further communicates with a fixed telephone 710 via a public line network. The mobile communication terminal 20 may communicate with another mobile communication terminal 700 using the contact data registered in the address book. Note that the mobile communication terminal 20 may communicate with a web server (not shown) in addition to the other mobile communication terminals 700 and the like.

  The data management server 30 exists on the Internet, and is accessed from the mobile communication terminal 20 via a radio access network and a core network. The data management server 30 stores the contact data recorded in the address book of the mobile communication terminal 20 in response to a request from the mobile communication terminal 20.

  The personal computer 40 is an example of a maintenance communication terminal. The personal computer 40 accesses the data management server 30 to add, change or delete contact data stored in the data management server 30 (hereinafter referred to as “addition, change or deletion”). It is called "correction"). For example, the personal computer 40 displays a correction screen for receiving a request for correction of contact data stored in the data management server 30 and stores it in the data management server 30 in response to the correction request received via the correction screen. Maintained contact data The data management server 30 may exist on the core network as a service node. In this case, the personal computer 40 accesses the data management server 30 via the gateway.

  FIG. 2 shows an example of a block diagram of the mobile communication terminal 20. FIG. 3 shows an example of a block diagram of the data management server 30. As illustrated in FIG. 2, the mobile communication terminal 20 includes a terminal data storage unit 200, a terminal data matching unit 210, a terminal data update unit 220, and a communication unit 250. As shown in FIG. 3, the data management server 30 includes a server data storage unit 300, a server data matching unit 310, a server data update unit 320, and a matching permission / denial storage unit 340.

  The terminal data storage unit 200 stores contact data as an address book. The communication unit 250 receives contact data. Specifically, the communication unit 250 displays one or a plurality of contact data stored in the terminal data storage unit 200 on the display 22, and one of the displayed contact data designated by the operation panel 24. Accept contact data. Further, the communication unit 250 may accept contact data input from the operation panel 24 in place of the contact data stored in the terminal data storage unit 200. The communication unit 250 communicates with a terminal specified by the received contact data.

  The terminal data update unit 220 corrects the contact data stored in the terminal data storage unit 200 in response to a request received from the user via the display 22 and the operation panel 24. For example, the terminal data update unit 220 displays a correction screen for accepting a request for correction of the contact data stored in the terminal data storage unit 200 on the display 22, and in response to the correction request received via the correction screen, The contact data stored in the terminal data storage unit 200 is corrected. Further, the terminal data update unit 220 generates terminal history information that is a history obtained by correcting the contact data stored in the terminal data storage unit 200 in response to the request. The terminal data update unit 220 stores the generated terminal history information in the terminal data storage unit 200. The terminal history information includes information for specifying the corrected data and the correction date and time for each corrected data.

  The terminal data matching unit 210 inputs via the display 22 and the operation panel 24 that the contact data stored in the terminal data storage unit 200 and the contact data stored in the server data storage unit 300 should be matched. Accept. When the terminal data matching unit 210 receives an input indicating that matching should be performed via the operation panel 24 or the like, the terminal data matching unit 210 stores the contact data stored in the terminal data storage unit 200 and the server data storage unit 300. Align with existing contact data. For example, the terminal data matching unit 210 transmits a matching request for requesting matching between the contact data stored in the terminal data storage unit 200 and the contact data stored in the server data storage unit 300 to the server data matching unit 310. Thus, as will be described later, the data management server 30 matches the contact data stored in the server data storage unit 300 with the contact data stored in the terminal data storage unit 200.

  The terminal data matching unit 210 accepts an input of a setting (hereinafter referred to as “timer setting”) for matching at a predetermined time without inputting each time, in addition to an input for each matching. When the timer setting date / time comes, the terminal data matching unit 210 transmits a matching request in the same manner as when receiving an input each time.

  When the terminal data matching unit 210 receives a request from the server data matching unit 310 to transmit the terminal history information stored in the terminal data storage unit 200, the terminal data matching unit 210 sends the terminal history information to the server data matching unit 310. Send. Further, when the terminal data matching unit 210 receives the contact data from the server data matching unit 310, the terminal data matching unit 210 reflects it in the terminal data storage unit 200.

  The server data storage unit 300 stores contact data stored in the terminal data storage unit 200 of the mobile communication terminal 20.

  The server data update unit 320 corrects the contact data stored in the server data storage unit 300 in response to a request from the personal computer 40. For example, the server data update unit 320 displays on the personal computer 40 a correction screen for accepting a request for correction of the contact data stored in the server data storage unit 300 based on a request from the personal computer 40, and the change screen is displayed. In response to the correction request received from the personal computer 40, the contact data stored in the server data storage unit 300 is corrected.

  The server data update unit 320 generates server history information that is a history of correcting the contact data stored in the server data storage unit 300 in response to the request. The server data update unit 320 stores the generated server history information in the server data storage unit 300. The server history information includes, for example, information for specifying the corrected data and the correction date and time for each corrected data.

  The server data matching unit 310 receives an input from the personal computer 40 that the contact data stored in the server data storage unit 300 and the contact data stored in the terminal data storage unit 200 should be matched. When the server data matching unit 310 receives an input indicating that matching should be performed from the personal computer 40, the server data matching unit 310 stores the contact data stored in the server data storage unit 300 and the contact information stored in the terminal data storage unit 200. Align with data. For example, the server data matching unit 310 first requests the terminal data matching unit 210 to transmit the terminal history information stored in the terminal data storage unit 200, and the terminal history information received from the terminal data matching unit 210 and the server data storage unit. Based on the server history information stored in the server 300, the contact data stored in the server data storage unit 300 and corrected by the server data update unit 320 between the last matching time and the current matching time. The destination data is transmitted to the terminal data matching unit 210, and is the contact data stored in the terminal data storage unit 200, which is corrected by the terminal data update unit 220 between the last matching time and the current matching time. Contact data is received from the terminal data matching unit 210. The server data matching unit 310 reflects the contact data received from the terminal data matching unit 210 in the server data storage unit 300, and stores the contact data transmitted from the server data matching unit 310 in the terminal data by the terminal data matching unit 210. This is reflected in the part 200. The same contact data stored in the terminal data storage unit 200 and the server data storage unit 300 between the previous matching time and the current matching time is stored in the terminal data updating unit 220 or the server data updating unit. If the contact data is different depending on 320, it is matched with the latest contact data with reference to the correction date and time of the terminal history information and the server history information.

  The matching permission / refusal storage unit 340 receives from the personal computer 40 information indicating whether or not matching between the contact data stored in the server data storage unit 300 and the contact data stored in the terminal data storage unit 200 is permitted. For example, the matching permission / refusal storage unit 340 displays a rejection acceptance screen for accepting input of information indicating permission / inhibition of matching on the personal computer 40 based on a request from the personal computer 40, and indicates whether the matching is permitted or not via the permission / refusal acceptance screen. Accept information. When accepting information indicating whether or not matching is permitted, the matching permission / denial storage unit 340 stores information indicating rejection of the accepted matching.

  In addition, when the server data matching unit 310 receives a matching request from the terminal data matching unit 210, the server data matching unit 310 determines whether information indicating that matching is not permitted is stored in the matching permission / denial storage unit 340. When the server data matching unit 310 receives the matching request, if the server data matching unit 310 determines that the matching permission storage unit 340 stores information indicating that matching is permitted, or stores information indicating that matching is not permitted. If it is determined that there is no contact data, the contact data stored in the server data storage unit 300 and the contact data stored in the terminal data storage unit 200 are matched. On the other hand, when the server data matching unit 310 receives the matching request, if the server data matching unit 310 determines that information indicating that matching is permitted is not stored in the matching permission / denial storage unit 340, or stores information indicating that matching is not permitted. If the mobile communication terminal 20 does not match the contact data stored in the server data storage unit 300 with the contact data stored in the terminal data storage unit 200, Is notified to the personal computer 40. For example, the server data matching unit 310 notifies the personal computer 40 that a matching request has been received by electronic mail. As a result, it is possible to prevent the contact data in the data management server 30 from being deleted. For example, even if the contact data in the mobile communication terminal 20 that has been lost or stolen is deleted by the finder or theft, the data management server sends a consistency request for reflecting the contents after the deletion to the data management server 30. Therefore, it is possible to prevent the contact data in the data management server 30 from being deleted. Furthermore, since the communication function of the portable communication terminal 20 is not limited, it is possible to maintain and secure a means for contacting the finder or theft. In addition, since it is notified that there has been an alignment request from the finder or theft, it is possible to take some measures such as contacting the finder or theft.

  The storage medium 70 stores programs that cause the server data storage unit 300, the server data matching unit 310, the server data update unit 320, and the matching permission / denial storage unit 340 to operate. The data management server 30 may cause the server data matching unit 310 and the like to operate by installing the program stored in the storage medium 70. Furthermore, as another method, the data management server 30 may acquire such a program via a network.

  FIG. 4 is a flowchart showing an example of the operation of the data management server 30 and the like. The flowchart on the left side of FIG. 4 shows the operation of the mobile communication terminal 20, the flowchart on the center shows the operation of the data management server 30, and the flowchart on the right side shows the operation of the personal computer 40. In the flowchart illustrated in FIG. 4, the terminal data matching unit 210 receives an input indicating that the contact data stored in the terminal data storage unit 200 and the contact data stored in the server data storage unit 300 should be matched. (S200).

  The terminal data matching unit 210 that has received an input to be matched transmits a matching request to the server data matching unit 310 of the data management server 30 (S220).

  The server data matching unit 310 that has received the matching request from the terminal data matching unit 210 determines whether information indicating that matching is not permitted is stored in the matching permission / denial storage unit 340 (S310).

  If the server data matching unit 310 determines in step S310 that information indicating that matching is not permitted is not stored in the matching permission / denial storage unit 340 (S310: No), the contact information stored in the server data storage unit 300 is stored. The data and the contact data stored in the terminal data storage unit 200 are matched (S240, S340). And this flowchart is complete | finished.

  On the other hand, in step S310, if the server data matching unit 310 determines that information indicating that matching is not permitted is stored in the matching permission / denial storage unit 340 (S310: Yes), the server data matching unit 310 stores the information in the server data storage unit 300. The personal computer 40 is notified that the matching request has been received from the mobile communication terminal 20 without matching the contact data and the contact data stored in the terminal data storage unit 200 (S350). And this flowchart is complete | finished.

  As described above, according to this embodiment, it is possible to prevent the contact data in the data management server 30 from being erased, and to maintain and secure the means for contacting the finder or theft person.

  Furthermore, the data management server 30 may include a data collection unit (not shown) in addition to the server data storage unit 300, the server data matching unit 310, the server data update unit 320, and the matching permission / denial storage unit 340. When the server data matching unit 310 receives the matching request and determines that the information indicating that matching is permitted is not stored in the matching permission / refusal storage unit 340, the data collecting unit stores information indicating that matching is not permitted. When it is determined that the contact data is stored in the terminal data storage unit 200 but is not stored in the server data storage unit 300, the terminal data matching unit 210 is requested and acquired. The data collection unit reflects the contact data acquired from the terminal data matching unit 210 in the server data storage unit 300. In other words, when the server data matching unit 310 receives a matching request for requesting matching from the mobile communication terminal 20 and information indicating that matching is permitted is stored in the matching permission / denial storage unit 340, the server data matching unit 310 When the contact data stored in the storage unit 300 and the contact data stored in the terminal data storage unit 200 are matched, and information indicating that matching is not permitted is stored in the matching permission / denial storage unit 340 The data collection unit is notified that contact data stored in the terminal data storage unit 200 and not stored in the server data storage unit 300 should be collected. Thereby, when the finder or theft of the mobile communication terminal 20 has not erased the contact data in the mobile communication terminal 20, when there is a matching request from the finder or theft of the mobile communication terminal 20, The contact data corrected by the authorized user of the mobile communication terminal 20 can be stored in the data management server 30 during the period from the last matching until it is lost or stolen.

  In this embodiment, the contact data is used as data stored and used in the mobile communication terminal 20, but the data stored and used in the mobile communication terminal 20 is other text, images, and the like. May be.

  As mentioned above, although this invention was demonstrated using embodiment, the technical scope of this invention is not limited to the range as described in the said embodiment. It will be apparent to those skilled in the art that various modifications or improvements can be added to the above-described embodiment. It is apparent from the scope of the claims that the embodiments added with such changes or improvements can be included in the technical scope of the present invention.

An example of data management system 10 is shown typically. An example of the block diagram of the portable communication terminal 20 is shown. An example of the block diagram of the data management server 30 is shown. It is a flowchart which shows an example of operation | movement of the data management server 30 grade | etc.,.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Data management system 20 Mobile communication terminal 22 Display 24 Operation panel 30 Data management server 40 Personal computer 50 Mobile communication terminal 60 Data management server 200 Terminal data storage part 210 Terminal data matching part 220 Terminal data update part 250 Communication part 300 Server data storage Unit 310 server data matching unit 320 server data updating unit 340 matching permission storage unit 700 portable communication terminal 710 fixed telephone

Claims (5)

A data management server for storing data stored and used in a mobile communication terminal,
A data storage unit for storing the data in response to a request from the mobile communication terminal;
A data update unit for adding, changing or deleting the data stored in the data storage unit in response to a request from a maintenance communication terminal for maintaining the data;
A matching permission / rejection storage unit that receives and stores matching permission / rejection between the data stored in the data storage unit and the data stored in the mobile communication terminal;
When the information requesting the matching is stored in the matching permission / refusal storage unit when the matching request for the matching is received from the mobile communication terminal, the data stored in the data storage unit And the data stored in the portable communication terminal are matched, while the information indicating that the matching is not permitted is stored in the matching permission / denial storage unit, the data stored in the data storage unit A data management server comprising a data matching unit that does not match data and the data stored in the mobile communication terminal.   When the data matching unit receives the matching request from the mobile communication terminal and information indicating that the matching is not permitted is stored in the matching permission / refusal storage unit, the data matching unit indicates that the matching request has been received. The data management server according to claim 1, which notifies the maintenance communication terminal.   The data management server according to claim 1 or 2, wherein the data is contact data stored in an address book. A data management method for managing data stored and used in a mobile communication terminal by a device different from the mobile communication terminal,
A data storage procedure for storing the data in response to a request from the mobile communication terminal;
A data update procedure for adding, changing or deleting the data stored in the data storage unit in response to a request from a maintenance communication terminal for maintaining the data;
A matching permission / inhibition storage procedure for receiving and storing matching permission between the data stored by the data storage procedure and the data stored in the mobile communication terminal from the maintenance communication terminal;
The data stored by the data storage procedure is stored when information indicating that the matching is permitted by the matching permission / inhibition storing procedure when the matching request for requesting the matching is received from the portable communication terminal. And the data stored in the portable communication terminal are matched, while the information indicating that the matching is not permitted by the matching permission storage procedure is stored, the data stored by the data storage procedure A data management method comprising: a data matching procedure that does not match data and the data stored in the mobile communication terminal. A program for controlling a data management server for storing data stored and used in a mobile communication terminal, the data management server,
A data storage procedure for storing the data in response to a request from the mobile communication terminal;
A data update procedure for adding, changing or deleting the data stored in the data storage unit in response to a request from a maintenance communication terminal for maintaining the data;
A matching permission / rejection storage procedure for receiving and storing matching permission between the data stored by the data storage procedure and the data stored in the portable communication terminal from the maintenance communication terminal; and
The data stored by the data storage procedure is stored when information indicating that the matching is permitted by the matching permission / inhibition storing procedure when the matching request for requesting the matching is received from the portable communication terminal. And the data stored in the portable communication terminal are matched, while the information indicating that the matching is not permitted by the matching permission storage procedure is stored, the data stored by the data storage procedure A program for executing a data matching procedure that does not match data and the data stored in the mobile communication terminal.

Images