JP2007123959A - Portable telephone directory management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a telephone directory management system that enables a portable telephone to acquire the newest telephone directory data from a telephone directory management server for synchronizing with telephone directory data owned by an own machine, and prevents information in the telephone directory data stored into the portable telephone and the telephone directory management server from being leaked and used illegally. <P>SOLUTION: The telephone directory management system 20 comprises a telephone directory management server 30 having a telephone directory database 106, and the portable telephone 40 for receiving the telephone directory data from the telephone directory management server 30. The telephone directory management server 30 has a telephone directory data read means 117 for reading the available telephone directory data from the telephone directory database 106 for each portable telephone 40, and a telephone directory data transmission means 118 for transmitting the read telephone directory data to the portable telephone 40 of a request source. The portable telephone 40 has a telephone directory data synchronization means 135 for acquiring the newest telephone directory data from the telephone directory management server 30 by a request to synchronize the newest telephone directory data with the telephone directory data 140 owned by the own machine. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a mobile phone book management system for transmitting phone book data managed by a phone book management server in response to a request from a mobile phone.

  With the improvement of mobile phone technology, it is common practice to manage phone book data using only a mobile phone. On the other hand, due to the problem of operability of mobile phones, there is also known a system in which phone book data is registered, corrected, and deleted by a phone book management server and the latest data is automatically reflected on the mobile phone.

  FIG. 9 shows an outline of a publicly known telephone directory management system 1 in which data registration, correction, and deletion are performed by the telephone directory management server and the latest data is automatically reflected. The telephone directory management system 1 includes a telephone directory management server 2 and a cellular phone 4 that receives telephone directory data from the telephone directory management server 2 via a portable public telephone line network and the Internet 3. Includes an input unit 5 for inputting various instructions, an external interface input / output control device 6 for inputting / outputting data to / from an external medium, a display device 7 for displaying operation contents and execution results, and a data processing unit 8 for controlling the whole. The storage device 9 stores input data and the memory device 10 stores a program for executing data processing.

In the telephone directory management system 1 having such a configuration, the registrant information input from the telephone directory management server 2 is stored in the storage device 9, and the registrant information is collected as a plurality of telephone directories. When the registrant information is changed or deleted, it is updated or deleted by input from the telephone directory management server 2.
Upon receiving a phone book acquisition request from the mobile phone 4, the phone book management server 2 transmits phone book data to the mobile phone 4.
In addition, there exists the following patent document 1 as a well-known technical document relevant to this invention.
JP 2002-57798 A

  As described above, the system for registering, correcting, and deleting phone book data in the phone book management server and automatically reflecting the latest data to the mobile phone is highly convenient from the viewpoint of the operability of the mobile phone. Is. It is also possible to download phone book data selected from a large amount of data of the phone book management server to the mobile phone.

However, even in such a case, having personal information in a mobile phone has a high risk of information leakage if it is lost or stolen. Also, it is necessary to prevent information leakage etc. in the telephone directory management server.
Therefore, it is desired to prevent information leakage and unauthorized use of the mobile phone and the phone book management server in a mechanism that reflects the latest data of the phone book data from the phone book management server to the mobile phone. Patent Document 1 does not solve the above-described problem.

  In view of the above situation, the present invention enables the mobile phone to acquire the latest phone book data from the phone book management server and to synchronize with the phone book data held in its own device. An object of the present invention is to provide a telephone directory management system that prevents information leakage or unauthorized use of telephone directory data stored in telephones and telephone directory management servers.

In order to solve the above problems, the present invention provides the following configurations.
The invention according to claim 1 is a telephone directory management system comprising a telephone directory management server having a telephone directory database and a mobile phone that receives telephone directory data from the telephone directory management server,
The telephone directory management server includes telephone directory data registration means for registering telephone directory data in the telephone directory database;
Phone book data updating means for searching and updating or deleting registered phone book data using a name and a phone number as a key;
Phone book data availability registration means for registering the availability of phone book data in the phone book database for each mobile phone;
Mobile phone identification means for identifying a mobile phone that can use the phone book data with reference to the phone book database;
A phone book data reading means for reading available phone book data for each mobile phone from the phone book database in response to a request from the mobile phone;
Phone book data transmission means for sending the read phone book data to the requesting mobile phone,
The mobile phone obtains the latest phone book data from the phone book management server by making a request, and synchronizes the latest phone book data with the phone book data held in the own phone. The present invention provides a mobile phone book management system characterized by comprising means.

The invention according to claim 2 is a mobile phone book management system comprising a phone book management server having a phone book database, and a mobile phone that receives phone book data from the phone book management server,
The telephone directory management server includes an authentication unit for authenticating whether the requesting mobile phone is a legitimate user;
Provideable phone book data setting means for setting phone book data that can be provided for each user having a plurality of phone book data in the phone book database;
Phone book data provision availability setting means for setting whether to provide phone book data for each user;
Phone book data transmitting means for encrypting the phone book data and transmitting it to the mobile phone;
The mobile phone has an authentication request means for making an authentication request at regular intervals to the telephone directory management server;
Lock means for locking the phone book data in the mobile phone and making it impossible to refer to when the authentication request fails a certain number of times,
The present invention provides a mobile phone book management system comprising phone book data forcibly deleting means for forcibly deleting phone book data upon receipt of an authentication fraud response from the phone book management server.

According to the first aspect of the present invention, the mobile phone can acquire the latest phone book data from the phone book management server and can synchronize with the phone book data held in the own device. Information leakage or unauthorized use of the phone book data stored in the book management server can be prevented.
According to the invention described in claim 2, the mobile phone can acquire the latest phone book data from the phone book management server and can synchronize with the phone book data held in its own device. Information leakage or unauthorized use of the phone book data stored in the book management server can be prevented.

Hereinafter, embodiments of the present invention will be described with reference to the drawings showing examples.
In FIG. 1, reference numeral 20 denotes a mobile phone book management system according to an embodiment of the present invention. In the mobile phone book management system 20, a phone book management server 30 and a mobile phone 40 are connected to a mobile phone public line network and the Internet 50. It is connected so that communication is possible via.
The phone book management server 30 includes a display device 101, an MPU 102, a key input device 103, an external input / output control device 104, a memory 105 for storing an application to be described later, and a phone book database 106 in the storage device.

In the memory 105, a user registration / update unit 111 for registering and updating data of a user who uses telephone book data, a telephone for registering telephone book data or a telephone book file used by the user Refer to the book data registration means 112, the phone book data registration means 113, the phone book data update means 114, the phone book data sending request receiving means 115 for receiving a phone book data sending request from the mobile phone 40, and the phone book database 106. The mobile phone identification means 116 for identifying the mobile phone 40 that can use the phone book data, the telephone book data reading means 117, the telephone book data transmission means 118, and the authentication request receiving means for receiving an authentication request from the mobile phone 40 119, PKI (Public
Key Infrastructure Public key infrastructure) Stores applications such as authentication means 120 for performing client authentication, authentication result transmission means 121, and the like.

  The phone book database 106 stores a history of user information table 122, user-specific phone book table 123, phone book name table 124, phone book registrant table 125, phone book affiliation table 126, downloads, and the like. A history table 127 is stored.

On the other hand, the mobile phone 40 includes an MPU 131 and a storage memory 132, and the storage memory 132 includes an application storage area 133 and a data storage area 134.
The application storage area 133 includes a phone book data synchronization unit 135, an authentication request unit 136, a lock unit 137 that locks the phone book data and makes it impossible to refer to the phone book data, a phone book data forced deletion unit 138, a phone book data The application having each function as the sending request means 139 is stored, the necessary application (not shown) as the mobile phone 40 is stored, and the phone book data 140 is stored in the data storage area 134.

The phone book data user performs user registration in the phone book management server 30. User registration is performed by the telephone directory management server administrator, and the user registration / update unit 111 registers the user's personal information and the model information of the mobile phone 40, and the information is stored in the user information table 122. The
The user's mobile phone 40 periodically authenticates the user. If the phone book management server 30 cannot be connected for a certain period of time, the phone book data cannot be used due to the function on the mobile phone 40 side.

Further, when the user reports that the mobile phone 40 has been lost, or when the server administrator determines to stop using the user, the status of the telephone directory management server 30 is changed to use stop. In this state, when there is an authentication access from the mobile phone 40, the mobile phone 40 cannot use the phone book.
As requests from the mobile phone 40, there are an authentication request, a telephone book data sending request 141, and the like.
As a response from the telephone directory management server 30, there are telephone directory data transmission, authentication result transmission 142, and the like. These requests and responses are made via a portable public line network and the Internet 50. The Internet is connected by TCP / IP, and HTTP is used as a protocol. Client authentication is performed using PKI encryption.

The mobile phone 40 stores the phone book data 140 acquired from the phone book management server 30 through the mobile public line network and the Internet 50 in the data storage area 134 of the mobile phone 40.
In the present embodiment, the phone book data 140 includes a name, a telephone number, and a mail address. A plurality of telephone numbers and e-mail addresses can be stored.

  The cellular phone 40 issues an authentication request to the telephone directory management server 30 by the authentication request unit 136. In response to this, the authentication result is sent from the phone book management server 30 by the authentication result sending means 121 of the phone book management server 30, but if the authentication is successful, the phone book data 140 in the mobile phone 40 is At this time, if the mobile phone 40 requests to send the phone book data by the phone book data sending request means 139, the phone book data sending means 118 of the phone book management server 30 makes a difference data based on the history or the telephone of all data. Book data is sent.

  The cellular phone 40 updates the difference of its own phone book data 140 by the phone book data synchronization means 135 based on the sent phone book data to make it the latest state. If the transmitted telephone directory data is all data, all the data is stored or overwritten.

If the authentication fails, the phone book data 140 in the mobile phone 40 is forcibly deleted by the phone book data forced deletion means 138 based on the authentication result of the authentication failure.
Further, even when the phone book management server 30 prohibits the user from using the phone book at the time of authentication, the phone book data 140 is deleted by the phone book data forced deletion means 138 based on the authentication result.

  Furthermore, if the authentication is not performed for a certain period, the lock means 137 locks the phone book data 140 to make the reference impossible state. When the phone book data 140 is locked, the authentication request unit 136 makes an authentication request to the phone book management server 30. When the authentication is successful, the lock unit 137 releases the lock. When authentication fails in the locked state, the phone book data 140 is deleted from the storage memory 132 by the phone book data forced deletion means 138.

The flow of processing in which the mobile phone 40 acquires phone book data from the phone book management server 30 will be described in more detail with reference to FIGS. It is assumed that the phone book data that can be referred to by the user is registered in the user-specific phone book table 123 by the phone book registration processing 201 by the phone book data registration unit 113.
First, the authentication request means 136 of the mobile phone 40 performs an authentication request transmission 202 by automatic processing or manual processing at regular intervals to the telephone directory management server 30.

  In the telephone directory management server 30, when the authentication request receiving unit 119 receives the authentication request 202 from the mobile phone 40, the mobile phone identification unit 116 refers to the user information table 122, and the mobile phone that has received the authentication request 202 An authentication process 203 is performed as to whether or not 40 is registered. Next, the authentication unit 120 refers to the user information table 122 and performs authentication processing as to whether the requested user of the mobile phone 40 is an authorized user, that is, whether or not use is permitted. 203.

  When the authentication is successful, the authentication result is transmitted 204 to the mobile phone 40 by the authentication result transmitting means 121. On the mobile phone 40 side, after receiving the authentication result of successful authentication, the phone book data sending request unit 139 sends 205 a phone book data sending request to the phone book management server 30. Note that the telephone directory data transmission request does not necessarily have to be made when the authentication result is received, and may be made as appropriate, or may be requested by the user of the mobile phone 40. Further, the phone book data transmission request includes an all data request and an update data request.

  When the phone book management server 30 receives the phone book data sending request 205, if it is an update data request, the phone book data reading unit 117 refers to the history table 127 based on the history of the history table 127, The difference information with the latest phone book data that can be used by the requesting mobile phone 40 is read 206 from the user-specific phone book table 123, and the difference information of the read phone book data is read by the phone book data transmitting means 118. Send 207 to 40. The phone book data of the difference information is transmitted after being encrypted by SSL, for example. Note that the telephone book data may be automatically transmitted from the telephone book management server 30 to the mobile phone 40 together with the authentication result transmission 204 or thereafter without the telephone book data transmission request 205.

If the phone book data sending request 205 is a full data request, the phone book data reading means 117 reads the phone book data usable by the requesting mobile phone 40 from the user-specific phone book table 123 206. The read telephone directory data is transmitted 207 to the cellular phone 40 by the telephone directory data transmitting means 118. A configuration may be adopted in which all data requests are determined from the history table 127.
The cellular phone 40 uses the phone book data synchronization means 135 to update the phone book data 140 of its own device by the synchronization process 208 with the acquired difference information. When all the data is received, the previous data is deleted or overwritten on the previous data as it is or when the previous data exists.

  A flow in the case where acquisition of the phone book from the phone book management server 30 fails will be described in detail with reference to FIGS. Since the process from the telephone directory registration 201 to the authentication process 203 is the same as the operation in FIG.

When authentication of the mobile phone 40 fails during authentication in the authentication process 203 and when the user of the mobile phone 40 is in a suspended state, the authentication result transmission unit 121 causes the mobile phone 40 to An error response authentication result transmission 301 is performed.
When receiving the error response authentication result transmission 301 signal, the cellular phone 40 deletes all the phone book data 140 on the storage memory 132 by the phone book data forced deletion processing 302 by the phone book data forced deletion means 138.

Next, the transition of the state in which the phone book data 140 of the mobile phone 40 is held will be described in detail with reference to FIGS. In the initial state 401, the cellular phone 40 does not have the phone book data 140 (initial state).
In the case of successful authentication 405, the phone book data 140 is acquired from the phone book management server 30, stored in the data storage area 134, the phone book data usable state 403 is entered, and the phone book data 140 can be referred to.
If the authentication success 404 by the periodic authentication request continues in the phone book data usable state 403, the state is maintained as it is.

In the phone book data available state 403, when an authentication error 406 occurs during authentication by a periodic authentication request, the phone book data 140 is deleted and the state transits to the initial state 401.
When the phonebook data available state 403 indicates that authentication has not been executed 407 for a certain period, the state transits to the phonebook lock state 408. In the phone book lock state 408, the phone book data 140 is locked, and the phone book data 140 cannot be used or referenced, but the phone book data 140 is retained.

Next, when the authentication is successful 409 in the phone book lock state 408, the lock of the phone book data 140 is released, and a transition is made to the lock phone book usable state 403.
When the authentication error 410 occurs in the phone book lock state 408, the phone book data 140 is deleted and the state transitions to the initial state 401.

A series of flow for acquiring the telephone directory data will be described in more detail with reference to FIGS. First, connection 501 with the telephone directory management server 30 is performed by the authentication request unit 136.
If the connection cannot be established, the telephone book data forced deletion means 138 performs a specified time elapse confirmation 504 after the previous connection. If the specified time has elapsed, the telephone book data is determined to be in an unauthorized state. The phone book forced deletion processing 506 is performed on the book data 140.

  If it is within the specified time from the previous connection, the connection with the telephone directory management server 30 is made at the next timing. When the connection with the telephone directory management server 30 can be established, the telephone directory management server 30 executes the authentication process 503 by the authentication unit 120 based on the authentication request by the authentication request unit 136.

If the authentication processing determination 505 indicates that the authentication is correctly performed, the mobile phone 40 acquires the difference information or all the information of the phone book data 140 that can be used by the mobile phone 40 from the phone book management server 30, and the phone book data synchronization means 135 Thus, the phone book synchronization processing 507, that is, reflection is performed on the phone book data 140 on the mobile phone 40.
If the authentication process 503 of the telephone directory management server 30 determines that an error has occurred, an error response is sent from the telephone directory management server 30 to the mobile phone 40 by the authentication result transmission unit 121. When receiving the error response, the mobile phone 40 deletes the phone book 123 on the mobile phone 40 by the phone book forced deletion processing 508 by the phone book data forced deletion means 138.

  User information management in the telephone directory management server 30 will be described with reference to FIGS. The user of the mobile phone 40 using the phone book data is registered on the phone book management server 30 by the server user information registration screen which is the user registration / update means 111. The registered information can be updated and deleted.

User information can be displayed as a list, but at the time of registration and update, it is displayed as one or more screens per person. Phone number 601, user name 602, employee number 603, certificate ID 604, usable individual phone book name 605 that is used phone book data registration means 112, usage status such as whether it is in use, etc. are displayed for each user. It has a registration / update column for the usage status 606 to be used.
The data is registered or updated by pressing registration / update 607 and deleted by pressing delete 608.

  The phone book data that can be used is phone book data that is set to give a reference authority for each user because a plurality of individual phone book names are registered. For example, it is possible to use different employees to refer to the person-in-charge information of the customer A company and the person-in-charge information of the customer B company. It is possible to show only the information of company A to the employee in charge of company A and only the information of company B to the employee in charge of company B. In addition, it is possible to divide the telephone directory of all employees in the own department within the company, and only other managers for other departments.

For information to be registered, user information is stored in the user information table 122. The user information is stored in the user information table 122 by telephone number, name, employee number, certificate ID, and usage status.
The phone book that can be referred to for each user is defined in the user-specific phone book table 123. Register as a record with employee number and phonebook ID. If the employee number is selected as a key, an available phone book ID can be acquired. The phone book ID and the Japanese name of the phone book data are defined in the phone book name table 124. Define Japanese notation for each phone book ID. In addition, the number of telephone directory data that can be referred to by one employee can be freely set.

A cellular phone book management method will be described with reference to FIG. A plurality of phone book data can be defined as described above. Registration information can be set for each phone book data.
On the registration screen, which is the phone book data registration means 113 of the phone book management server 30, display of the phone book name 701, display of the phone book ID 702, and display and input of the phone book data 703 are performed. Addition and update are performed by pressing the registration / update 704. The registrant selected by pressing delete 705 is deleted. Registered information includes name, telephone number, e-mail address, and the like. Multiple registrations are possible for telephone numbers and email addresses. Registrant information is stored in the telephone directory registrant table 125.

Each registrant has a registrant ID that is a unique ID, and the registrant ID is used as a key. The registrant ID and the phone book ID are associated in the phone book affiliation table 126. This is because when the registrant is registered in the plurality of phone book registrant tables 125, the data is centrally managed.
As a case of registration in a plurality of phone book registrant tables 125, there may be a plurality of phone book registrant tables in the same organization. An example is the case of holding the company A general affairs department phone book registrant table, company A sales department phone book registrant table, company A managerial phone book registrant table.

FIG. 8 shows a warning screen displayed on the mobile phone 40. If authentication cannot be performed within the specified time, a warning screen 801 for prompting manual authentication is displayed. When this screen 801 is displayed, the phonebook data lock state 408 shown in the state transition of FIG. At this time, the phone book data 140 cannot be used. In this state, if authentication fails, the phone book data 140 is deleted. If the authentication is successful from the phone book data lock state 408, the phone book data 140 can be used or referenced again.
When an error response is returned as a result of the authentication, a warning screen 802 is displayed. When this screen is displayed, the state transits to the initial state 401 of the state transition of the mobile phone 40 shown in FIG. 4, indicating that all the phone book data 140 held on the mobile phone 40 has been deleted.

Thus, in the mobile phone book management system 20 of the present invention, the mobile phone 40 acquires the latest phone book data from the phone book management server 30, and the latest phone book data and the phone book held in its own device. The data 140 can be synchronized.
The phone book management server 30 includes a mobile phone identification unit 116 and an authentication unit 120. The mobile phone 40 includes an authentication request unit 136, a lock unit 137, and a phone book data forced deletion unit 135. Information leakage or unauthorized use of the mobile phone book data stored in the book management server 30 and the phone book data 140 stored in the mobile phone 40 can be prevented.

It is explanatory drawing which shows schematically the mobile telephone directory management system by this invention. In the mobile phone book management system according to the present invention, it is a phone book data acquisition sequence diagram at the time of successful authentication. In the mobile phone book management system according to the present invention, it is a phone book data acquisition sequence diagram at the time of authentication failure. It is explanatory drawing which shows the transition of the holding state of the telephone directory data of a mobile telephone in the mobile telephone directory management system by this invention. It is an authentication and telephone directory data processing flow in the mobile telephone directory management system of this invention. (A) It is a server user information registration screen in the cellular phone book management system of the present invention. (B) It is explanatory drawing of a table. (A) Server phone book data registration screen in the mobile phone book management system of the present invention. (B) It is explanatory drawing of a table. (A) It is a warning screen displayed on the mobile phone in the mobile phone book management system of the present invention. (B) A screen for notifying deletion of phone book data displayed on a mobile phone in the mobile phone book management system of the present invention. It is explanatory drawing which shows schematically the mobile telephone directory management system by a prior art example.

Explanation of symbols

20 phone book management system 30 phone book management server 40 mobile phone 106 phone book database 111 user registration / update unit 112 phone book data registration unit 113 phone book data registration unit 114 phone book data update unit 115 phone book data sending request reception Means 116 Cellular phone identification means 117 Telephone book data reading means 118 Telephone book data sending means 119 Authentication request receiving means 120 Authentication means 121 Authentication result sending means 135 Telephone book data synchronization means 136 Authentication request means 137 Lock means 138 Forced deletion of telephone book data Means 140 Phonebook data

Claims (2)

A telephone directory management system comprising a telephone directory management server having a telephone directory database and a mobile phone that receives telephone directory data from the telephone directory management server,
The telephone directory management server includes a user registration / update unit for registering and updating a user of the mobile phone in the telephone directory database;
Use phone book data registration means for registering phone book data to be used for each mobile phone;
Phone book data registration means for registering phone book data;
Phone book data updating means for searching and updating or deleting registered phone book data using a name and a phone number as a key;
A mobile phone identification that identifies a mobile phone that can use the phone book data by referring to the phone book database according to a request from the mobile phone and a phone book data sending request receiving means for receiving a phone book data sending request from the mobile phone. Means,
Phone book data reading means for reading out phone book data available for each mobile phone from the phone book database;
Phone book data transmission means for sending the read phone book data to the requesting mobile phone,
The mobile phone obtains the latest phone book data from the phone book management server by making a request, and the phone book data that synchronizes the latest phone book data with the phone book data held in its own device A mobile phone book management system comprising synchronization means. A mobile phone book management system comprising a phone book management server having a phone book database and a mobile phone that receives phone book data from the phone book management server,
The telephone directory management server includes an authentication request receiving means for receiving an authentication request from the mobile phone;
An authentication means for authenticating whether or not the requesting mobile phone is an authorized user;
Authentication result transmitting means for transmitting an authentication result to the mobile phone;
A phone book data sending request receiving means for receiving a phone book data sending request from a mobile phone; and a phone book data sending means for encrypting the phone book data and sending it to the mobile phone.
The mobile phone has an authentication request means for making an authentication request at regular intervals to the telephone directory management server;
Lock means for locking the phone book data in the mobile phone and making it impossible to refer to when the authentication request fails a certain number of times,
A mobile phone book management system comprising: phone book data forcibly deleting means for forcibly deleting phone book data upon receipt of an authentication fraud response from the phone book management server.

Images