JP2010205201A - Network terminal equipment and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To increase data security by preventing data stored and managed in an external device from being carelessly leaked through a network. <P>SOLUTION: In a portable telephone set 1, whether or not data existing at the portable telephone set 1 are different from data stored and managed by a company server 3 is determined. The data existing at the portable telephone set 1 are controlled (for example, storing or accessing data is restricted) based on the determination result. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

The present invention relates to a network terminal device and a program that can use data stored and managed on the external device side by performing data communication with the external device via a network.

Conventionally, in a portable terminal device such as a mobile phone, as a security measure for preventing data leakage and protecting personal data, the data is not stored in the terminal device itself, but via an external device (network side). A thin client system in which this data is stored on the server by uploading to the server is known. Such a thin client system is mainly suitable for managing confidential data such as company data, and the company-related business data is not stored on the local terminal device side, but all of the servers on the company network side. However, if you are in a company (in a network environment), the data that is originally stored only on the server side is also temporarily stored (copied) on the terminal device side for smooth data storage. There is known a system in which the terminal device side data is deleted so that it cannot be used by the terminal itself when it is away from the company (see Patent Document 1).

JP 2008-77600 A

However, in the above-described prior art, it is assumed that all data is stored and managed on the server side. However, when a user uses such a terminal device, not only company-related data but also work and In some cases, it may be desirable to store and manage private data that is not directly related to the terminal device. In such cases, unless private data is clearly distinguished and stored, private data will be stored and managed on the server side as well as company-related data. Private data is used outside the company. The problem of being unable to do so occurs.

By the way, there is a possibility that company-related data and private data are mixed. For example, in the case of address book data or the like, there is a high possibility that company-related data and private data are mixed as contact information for a person who has a social relationship as well as a business relationship. In such a case, there is a risk that the company-related data may be leaked from the terminal device if the company-related data is inadvertently held on the terminal device side as it cannot be clearly distinguished from each other. There is a security problem.

An object of the present invention is to prevent data stored and managed on the external device side from being inadvertently leaked via a network, and to improve the data security.

In order to solve the above-described problem, the invention according to claim 1 is a network terminal that can use data stored and managed on the external device side by performing data communication with the external device via the network. A determination unit for determining whether the data existing on the terminal device side is different from the data stored and managed on the external device side, and based on the determination result by the determination unit, And control means for controlling data existing on the terminal device side.

According to a first aspect of the present invention, the data existing on the terminal device side is update data newly created or edited on the terminal device side, and the control means uses the update data by the determination means. Is determined to be the same as the data stored and managed on the external device side, the storage is restricted or the access is restricted for at least the same part of the update data. The invention according to claim 2 is also possible.

As an invention dependent on claim 1, the data existing on the terminal device side is received and acquired from the external device side via the network in order to use the data stored and managed on the external device side. A data group including data, and when the control unit determines that the same data as the data stored and managed on the external device side is included in the data group by the determination unit, 4. The invention according to claim 3, wherein the storage is restricted or the access is restricted for at least the same data in the data group.

As an invention dependent on any one of claims 1 to 3, the determination means stores and manages data existing on the terminal device side on the external device side when the application for processing the data is terminated. The invention according to claim 4 is characterized in that it is determined whether or not the data is different from the stored data.

As a subordinate invention according to any one of claims 1 to 3, the discriminating means is not required when shifting from a power-on state to a power-off state or from a state in which data communication with the external device is possible. Prior to the transition to a possible state, it is determined whether the data existing on the terminal device side is different from the data stored and managed on the external device side. The invention according to claim 5 may be used.

As an invention dependent on claim 1, the determination means is present on the terminal device side by comparing data existing on the terminal device side with data stored and managed on the external device side. The invention according to claim 6, wherein it is determined whether the stored data is different from the data stored and managed on the external device side.

According to a sixth aspect of the present invention, the determination means includes a series of data consisting of a plurality of blocks existing on the terminal device side and a series of data consisting of a plurality of blocks stored and managed on the external device side. The invention according to claim 7 is characterized in that it is determined whether or not the data is different for each block unit when comparing.

As an invention dependent on claim 7, among a series of data composed of a plurality of blocks existing on the terminal device side, blocks other than the block determined to be different by the determination unit and the predetermined block are excluded. The invention according to claim 8, wherein the storage or the access to the data in each block is restricted.

As an invention dependent on claim 1, the control means determines that the data existing on the terminal device side is the same as the data stored and managed on the external apparatus side as a result of the determination by the determination means. If the storage of the data existing on the terminal device side is restricted or the access is restricted, and the data existing on the terminal device side is different from the data stored and managed on the external device side, the terminal device side The invention according to claim 9 is characterized in that control is performed so as to store and hold data existing in the memory.

As an invention dependent on claim 9, the control means releases the access restriction of data stored and managed on the external device side in a security environment in which data communication with the external device is possible. The invention according to claim 10 may be provided.

As an invention dependent on claim 1, the determination means is present on the terminal device side by comparing data existing on the terminal device side with data stored and managed on the external device side. The control unit determines whether the data present on the terminal device side is present on the external device side as a result of the determination by the determination unit. If storage management is not performed, upload and transmit data existing on the terminal device side to the external device and store and manage the data on the external device side, and limit storage of data existing on the terminal device side or If the access is restricted and data existing on the terminal device side is also stored and managed on the external device side, storage of data existing on the terminal device side is restricted It may be an invention according to claim 11, characterized in that as to limit its access.

In order to solve the above-described problem, the invention according to claim 12 is the data stored and managed on the external device side by performing data communication with the computer via the network. Based on the determination result, the function for determining whether the data existing on the terminal device side is different from the data stored and managed on the external device side, and And a program for realizing a function of controlling data existing on the terminal device side.

According to the present invention, data stored and managed on the external device side via the network is not inadvertently leaked, and the data security can be improved. It is possible to have both safety and convenience without having to be aware of whether the data is stored and managed on the side.

The block diagram which showed the network system which can use the mobile telephone apparatus applied as a network terminal device. FIG. 3 is a block diagram showing basic components of the mobile phone device 1. (1) is a diagram for explaining an address book (address book TAD in the recording medium 14) on the network terminal device (mobile phone device) 1 side, and (2) is stored in the local database DB on the company server 3 side. The figure for demonstrating the address book data made. FIG. 6 is a diagram showing how the storage of address book records existing on the mobile phone device 1 side is limited, and (1) shows an address book record existing on the mobile phone device 1 side and When the address book record stored and managed on the company server 3 side is substantially the same record, (2) is stored and managed on the company server 3 side with the address book record existing on the mobile phone device 1 side. The figure which showed the mode in the case where the address book record which is partly the same. The flowchart which showed the address book process started when the activation of an address book application is instruct | indicated by user operation in order to display address book data. The flowchart which showed the operation | movement following FIG. When the merge record displayed in the address book list screen is specified for editing, the contents of the server-side record and local-side record that make up this merge record are automatically updated as the merge record is edited FIG. The figure which showed a mode that the record which deleted the same field data as the server side record from a local side record was produced. The flowchart which showed the outline | summary of the whole operation | movement of the mobile telephone apparatus 1 started execution according to power supply ON (on) in 2nd Embodiment.

(Embodiment 1)
Hereinafter, a first embodiment of the present invention will be described with reference to FIGS.
This embodiment exemplifies a case where the present invention is applied to a mobile phone device as a network terminal device, and FIG. 1 is a block diagram showing a network system in which the mobile phone device can be used.
The cellular phone device 1 is equipped with a wireless LAN (local area network) module (wireless communication function) and can be connected to a local (company) network (wireless LAN) 2. Of the access points 2A installed at a plurality of locations in the company, the mobile phone device 1 and the nearest access point 2A are connected to the company server 3 (premises server) by performing high-speed wireless communication. .

In a state where the mobile phone device 1 is connected to the company server 3 via the company network 2, the mobile phone device 1 uploads its own data to the company database 3 on the company server 3 side, or the company database 3 side database DB It functions as an in-client terminal that downloads its own data from. That is, the cellular phone device 1 functions as a network terminal that can use (read / write) data stored and managed on the company server 3 side. The on-site database DB is provided with a business address book STD, which will be described later.

In addition, the mobile phone device 1 can be connected to a public network 4 that is an off-premises public mobile communication network (public wireless line), and is connected to a public server (communication) via a nearest base station or exchange (not shown). In addition to being able to make calls with other mobile phone devices (not shown) when connected to the business server 5), the public server 5 side of the public network 4 is also provided with its own data. It functions as an in-client terminal that uploads (for example, private data) or downloads its own data from the public server 5 side.

In such a network environment, it is possible to access the public server 5 on the public network 4 side from the company network 2 or access the company server 3 on the company network 2 side via the public network 4. Yes. The company server 3 and the public server 5 are external devices for the mobile phone device 1. In addition, the mobile phone device 1 is in a state in which a call can be made with another mobile phone device (not shown) or an e-mail can be transmitted / received via the public network 4, and the mobile phone device 1 is shown in the figure. When connected to the Internet, the Web site can be browsed and e-mail can be sent and received.

FIG. 2 is a block diagram showing basic components of the mobile phone device 1.
The mobile phone device 1 includes, for example, a call function, an e-mail function, an Internet connection function (Web access function), an address book management function, and the like. The CPU 11 is a central central processing unit that controls the overall operation of the mobile phone device 1 in accordance with various programs in the storage unit 12. The storage unit 12 is an internal memory, and has a program area and a data area (not shown), and the present embodiment is realized in this program area in accordance with operation procedures shown in FIGS. A program is stored for this purpose. The memory 13 has a work area 13a for temporarily saving various data necessary for the operation of the cellular phone device 1 and temporarily stores data downloaded from the company server 3 via the company network 2. 13b. The recording medium 14 is a detachable portable memory, and is composed of, for example, an SD card or an IC card, and stores an address book TAD and the like.

The telephone communication unit 15 includes a wireless unit, a baseband unit, a demultiplexing unit, and the like (not shown). For example, the nearest base station (not shown) is operated when the telephone function (voice telephone function), the electronic mail function, and the Internet connection function are operated. ) Is a telephone communication means for transmitting / receiving data to / from the receiver, and when the call function is operated, a signal is taken in from the receiving side of the baseband unit and demodulated into a received baseband signal, and then used for calling via the audio signal processing unit 16 Audio is output from the speaker SP, and input audio data from the call microphone MC is captured from the audio signal processing unit 16 and encoded into a transmission baseband signal, which is then given to the transmission side of the baseband unit and transmitted from the antenna. Let The operation unit 17 performs dial input, character input, command input, and the like, and the CPU 11 executes processing according to an input signal from the operation unit 17. The display unit 18 uses, for example, high-definition liquid crystal or organic EL, and displays a standby image, address book data, and the like.

The wireless LAN module 19 constitutes a wireless LAN communication function and is capable of high-speed wireless communication. For example, a wireless LAN module 19 having a standard with a use frequency of 2.4 GHz and a communication speed of 11 Mbit / sec at the maximum is used. The CPU 11 accesses the wireless LAN module 19 when starting an application for displaying an address book, and determines whether data communication is possible with an external device (company server 3 on the company network 2 side) on a specific premises. To determine whether the user is in a specific premises (inside the company).

FIG. 3 (1) is a diagram for explaining the address book (address book TAD in the recording medium 14) on the network terminal device (mobile phone device) 1 side. The address book TAD in the recording medium 14 is An address book consisting of “name”, “phone number”, “mail address”, “other phone number”, “other mail address”, etc. as information related to each communication partner in association with “management No” Hereinafter, the record is stored and referred to as a terminal-side address book TAD. The address book record stored in the terminal-side address book TAD is arbitrarily set by a user operation, and the CPU 11 additionally registers the newly created address book record in the terminal-side address book TAD. When editing such as correction or deletion is performed on an arbitrary address book record in the address book TAD, the contents of the address book TAD are updated accordingly.

FIG. 3B is a diagram for explaining the address book data stored in the local database DB on the company server 3 side. The address book STD in the local database DB is associated with the “management number”. In this configuration, “name”, “telephone number”, “mail address”, etc. are stored for each communication partner as information related to the partner. The address book record stored in the server-side address book STD is arbitrarily set by a user operation on the mobile phone device 1 side. The mobile phone device 1 uses the newly created address book record as a company Uploaded and sent via the network 2 to be additionally registered in the server-side address book STD, downloaded and received the contents of this server-side address book STD, and edited any address book data Later, the contents of the server-side address book STD are updated by uploading the edited result to the company server 3 side.

When the address book application is activated, the mobile phone device 1 determines whether data communication is possible with the company server 3 on the company network 2 side based on whether it is in a specific premises (inside the company) When not in the company, the contents of the terminal-side address book TAD are displayed as a list. When the user is in the company premises, the company server 3 side is accessed via the company network 2 to download and receive the contents of the server-side address book STD and the contents of the server-side address book STD and the terminal-side address book. The contents of the TAD are temporarily stored in the work area 13a and displayed as a list. In this case, the CPU 11 compares the contents of the server-side address book STD and the contents of the terminal-side address book TAD, and if records having the same key (for example, name) are displayed, a record obtained by merging them is displayed. It expands as a record for use and displays the contents of the record as a list.

The mobile phone device 1 can newly create address book data and execute editing processing in a state where the above address book list screen is displayed. At the end of such a processing application, the CPU 11 compares the address book record existing on the mobile phone device 1 side with the address book record stored and managed on the company server 3 side, and the mobile phone device 1 side It is determined whether or not the existing address book record is different from the address book record stored and managed on the company server 3 side, and storage in the terminal address book TAD is limited according to the determination result. ing. In this case, in the data comparison, for example, it may be determined that the phone numbers are substantially the same if there is a minute difference such as the presence / absence of a hyphen in the telephone number and the upper / lower case in the mail address. .

Here, the address book record existing on the mobile phone device 1 side is not limited to the contents of the terminal-side address book TAD, and when the contents of the server-side address book STD are downloaded and received, the downloaded records When the contents of the terminal-side address book TAD and the contents of the server-side address book STD are temporarily stored in the work area 13a, the contents of the work area 13a are transferred to the mobile phone device 1 side. It becomes an existing address book record. The address book record stored and managed on the company server 3 side means that the contents of the server side address book STD are temporarily stored in the temporary memory 13b on the mobile phone device 1 side. This is an address book record. Then, the comparison between the address book record existing on the mobile phone device 1 side and the address book record stored and managed on the company server 3 side is performed in block units (field units) in addition to the overall comparison in record units. To compare.

FIG. 4 compares the address book record that exists on the mobile phone device 1 side with the address book record that is stored and managed on the company server 3 side, and determines whether or not they differ. It is a figure for demonstrating a mode that the memory | storage to the side address book TAD is restrict | limited.
FIG. 4A is a diagram exemplifying a case where the address book record existing on the mobile phone device 1 side and the address book record stored and managed on the company server 3 side are substantially the same record. In this case, the mail addresses of both records are considered to be substantially the same, although there is a difference between uppercase and lowercase letters. Thus, when both records are the same, the address book record which exists in the mobile telephone apparatus 1 side is deleted.

FIG. 4B is a diagram exemplifying a case where the address book record existing on the mobile phone device 1 side and the address book record stored and managed on the company server 3 side are partially the same. Thus, when both records are partially the same, the address book record existing on the mobile phone device 1 side is stored and managed on the company server 3 side, except for the predetermined key (for example, name). The same field data as the address book record (phone number: 03-555...) Is the deleted record content.

Next, the operation concept of the cellular phone device 1 in the first embodiment will be described with reference to the flowcharts shown in FIGS. Here, each function described in these flowcharts is stored in the form of a readable program code, and operations according to the program code are sequentially executed. Moreover, the operation | movement according to the above-mentioned program code transmitted via transmission media, such as a network, can also be performed sequentially. The same applies to other embodiments described later. In addition to the recording medium, an operation peculiar to the present embodiment can be executed using a program / data supplied externally via a transmission medium. 5 and 6 are flowcharts showing an outline of the operation of the characteristic part of the present embodiment in the overall operation of the mobile phone device 1. When the flow of FIG. 5 and FIG. Return to the main flow (not shown) of the overall operation.

FIG. 5 and FIG. 6 are flowcharts showing an address book process that is started when an activation of an address book application is instructed by a user operation to display address book data.
First, the CPU 11 determines whether or not the user is in the premises (inside the company) depending on whether or not the company network 2 is accessible via the wireless LAN module 19 (step A1 in FIG. 5). If the address book application is not in the premises (company) at the time of activation (NO in step A1), all address book records (local side) from the address book (terminal address book) TAD in the recording medium 14 (Record) is read and temporarily stored in the work area 13a (Step A2), and then the contents of the local record are expanded as display data and displayed on the address book list screen (Step A3).

In this state where the local side records are displayed on the address book list screen, each local side record in the work area 13a is designated as a record group to be updated (step A4), and then a new address book record is created and edited The process proceeds (step A5). In this case, the newly created record is additionally registered in the above update target record group, any record content in the update target record group is corrected, deleted, or new field data is added. Edit processing such as After execution of such new creation and editing processing, when the end of the processing is instructed by a user operation (step A6), the above-described update target record group is registered in the terminal-side address book TAD, and the content is replaced. After that (step A7), the address book application in the flow of FIGS. 4 and 5 ends.

On the other hand, if the address book application is on the premises (inside the company) (YES in step A1), the line connection with the company network 2 is established and the address stored in the premises database DB on the company server 3 side. The contents of the book (server side address book) STD are downloaded and received and temporarily stored as a server side record in the temporary memory 13b (step A8). Then, the contents of the terminal-side address book TAD in the recording medium 14 are read as a local-side record and temporarily stored in the work area 13a (step A9), and the server-side record in the temporary memory 13b is temporarily stored in the work area 13a. Store it (step A10). Thus, in the server side record and the local side record (address book record existing on the mobile phone device 1 side) temporarily stored in the work area 13a, the local side record and the server side record can be identified. For this purpose, they are stored in a region divided.

Next, the local side record and the server side record are compared in this work area 13a to check whether a local side record having the same key (for example, name) as the server side record exists (step A11). . If there is no record having the same key (NO in step A12), each server-side record and each local-side record in the work area 13a are read, and the contents of this record are expanded as display data and addressed. It is displayed on the book list screen (step A14).

If there is a record having the same key (YES in step A12), a new record is created as display data by merging the records (step A13). For example, the server side record consists of “name”, “phone number”, “email address”, etc., and the local side record consists of “name”, “phone number”, “email address”, “other phone numbers”, “ The record created by merging them with "Other email address" ... is "Name", "Phone number", "Email address", "Other phone number", "Other email address" ... When there are several sets of records having the same key, the records having the same key are merged for each set. The records merged in this way and the other records (the server side record and the local side record with different keys) are expanded into display data and displayed on the address book list screen (step A14).

In the state where the address book list screen is displayed, after specifying each local-side record and server-side record in the work area 13a as a record group to be updated (step A15), the address book record is newly created and edited. Move (step A16). In this case, the newly created record is additionally registered in the update target record group, the contents of any record in the update target record group are corrected, deleted, new field data is added, etc. Edit processing.

Here, when a new record is created, the new record is stored in the corresponding area (local side record area, server side record area) in the work area 13a according to the type of the record (local side record, server side record). Sorted and stored. In order to perform such sort storage, the type may be selected by a user operation only when a new record is created. In addition, when a merge record is specified and edited on the address book list screen, the corresponding field data in the server side record and the local side record constituting the merge record is changed according to the edit of the merge record. I try to update it.

FIG. 7 shows that when the merge record displayed in the address book list screen is designated as an edit target, the contents of the server side record and local side record constituting the merge record are automatically set according to the edit of the merge record. It is the figure which showed a mode that it updated.
FIG. 7A shows a merge record composed of a plurality of fields (each field of items No. 1 to 5), and FIG. 7B shows a server-side record composed of a plurality of fields (each field of items No. 1 to 3). , (3) shows a local side record composed of a plurality of fields (fields of item Nos. 1 to 5). Here, when the field data of item No. 3 of the merge record is corrected, the corresponding field data of No. 3 of the server side record and the local side record is automatically updated accordingly. When the field data of item No. 5 of the merge record is corrected, the field data of No. 4 of the corresponding local record is automatically updated accordingly.

Thereafter, when the end of new creation and editing processing is instructed by the user operation (YES in step A17), the flow proceeds to the flow of FIG. 6, and the update target record group is searched based on the contents of the temporary memory 13b (step A18). Then, it is checked whether or not a record having the same key as the server-side record (record before update) in the temporary memory 13b exists in the update target record group (step A19). If there is no record having the same key (NO in step A19), the case where all of the update target records are local records (including newly created records) or in the update target records Contains a newly created server-side record. In such a case, it is checked whether a newly created server-side record is included in the update target record group (step A20). Here, if there is a server-side record stored in a divided area in the work area 13a, the record is a newly-created server-side record at this time. (Step A21), the newly created record is deleted from the update target record group (step A22).

Then, the remaining update target record group from which the newly created record is deleted is registered in the terminal-side address book TAD, and the content is replaced (step A23). If the newly created server side record is not included in the update target record group (NO in step A20), all of the update target record groups are local side records (including newly created records). Therefore, the process proceeds to step A23 described above, and the update target record group is registered in the terminal-side address book TAD and its contents are replaced. Thereafter, the address book application in the flow of FIGS. 5 and 6 ends.

Further, if there is a corresponding record having the same key (for example, name) as the temporarily stored server-side record in the update target record group (YES in step A19), each corresponding record is set one by one. In order to designate sequentially, first, the first applicable record is designated (step A24). Then, the designated record is compared with the server-side record (record before update) temporarily stored in the temporary memory 13b (step A25). In this case, it is checked whether or not each field data has the same contents by comparing both records for each field unit.

If all the field data of both records have the same contents (YES in step A26), this designated record is the same record as the server-side record (record before update). Deletes the designated record from the update target record group (step A27). Then, the process proceeds to step A28, where it is checked whether or not all the corresponding records in the update target record group have been specified, and the process returns to the above step A24 until all the corresponding records are specified, and the next corresponding record is specified.

If the specified record is different from the contents of the server-side record (record before update) temporarily stored in the temporary memory 13b (NO in step A26), the specified record is the updated server-side record or local record. Since it is a side record (regardless of whether it is updated or not), the process moves to step A29, and it is checked whether the designated record is a server side record. In this case, as described above, in the work area 13a, the local side record and the server side record are stored so that they can be distinguished from each other. Whether or not it is a server-side record is determined.

If the designated record is a server-side record (YES in step A29), after uploading the designated record (updated server-side record) to the company server 3 (step A30), the relevant record is updated from the update target record group. The designated record is deleted (step A31). The company server 3 performs processing for updating the corresponding address book data in the local database DB based on the received updated record. Thereafter, the process proceeds to step A28, where it is checked whether all the relevant records in the update target record group have been designated, and the process returns to the above-described step A24 until all the relevant records are designated.

If the designated record is a local record (NO in step A29), a record is created by removing the same data as the field data in the server record from the designated record (local record) (step A32). ). That is, the designated record (local side record) is compared with the server side record (record before update) temporarily stored in the temporary memory 13b, and the data in the key field (for example, name) is excluded. Create a record with the same field data deleted. Here, the same field data is not limited to data in a field having the same item number, but may be data in a field having a different item number.

FIG. 8 is a diagram showing how a record is created by deleting the same field data as the server-side record from the local-side record.
In this example, the field data of the item No. 2 constituting the updated local record shown in FIG. 8A is the same as the field data of the item No. 2 constituting the temporary storage server side record shown in FIG. In this case, the local side record (created record) is a record obtained by deleting the field data of item No. 2 as shown in (3). The record (local record) created in this way is replaced with the corresponding record (designated record) in the update target record group (step A33). Thereafter, the process proceeds to step A28, where it is checked whether all the relevant records in the update target record group have been designated, and the process returns to the above-described step A24 until all the relevant records are designated.

As a result of repeating such an operation for each record, when all the corresponding records in the update target record group have been designated (YES in step A28), the update target record group is registered in the terminal address book TAD and After the contents are replaced (step A34), the address book application in the flow of FIGS. 5 and 6 ends. By deleting records in the update target record group or deleting some fields in this way, a record having the same content as the local record is registered in the terminal address book TAD. It is prohibited.

As described above, in the first embodiment, the mobile phone device is based on the determination result of whether or not the data existing on the mobile phone device 1 side is different from the data stored and managed on the company server 3 side. Since the data existing on the 1 side is controlled (data deleted), the data stored and managed on the company server 3 side is not inadvertently leaked, and the data security is improved. In addition, the user does not need to be aware of whether or not the data is stored and managed on the company server 3 side, and can have both safety and convenience.

If the data existing on the mobile phone device 1 side (data newly created or edited on the mobile phone device 1 side) is partially the same as the data stored and managed on the company server 3 side, Since the storage of the same data is restricted (data deletion), it is prohibited to register data having the same contents as the data stored and managed on the company server 3 side in the terminal address book TAD. Can do.

The same data as the data stored and managed on the company server 3 side is included in the data existing on the mobile phone device 1 side (data group including data downloaded and received from the company server 3 side) For example, since the storage of the same data is restricted (data deletion), when the data stored and managed on the company server 3 side is used, the data can be browsed even after the use. It can prevent harmful effects.

When the application for processing data ends, it is determined whether the data existing on the mobile phone device 1 side is different from the data stored and managed on the company server 3 side. Immediately after that, the same data as the data stored and managed on the company server 3 side can be prevented from being available, which is effective in terms of security measures.

By comparing the data existing on the mobile phone device 1 side with the data stored and managed on the company server 3 side, the data existing on the mobile phone device 1 side is stored and managed on the company server 3 side. Since it is determined whether or not the data is different from the recorded data, it can be determined accurately, for example, if it is a minute difference, it can be determined that the data is substantially the same.

,
When comparing the data existing on the mobile phone device 1 side with the data stored and managed on the company server 3 side, it is determined whether the data is different for each block (field) unit. The determination can be performed partially.

Of a series of data (records) composed of a plurality of blocks (fields) existing on the mobile phone device 1 side, each field other than a field determined to have different data and a predetermined field (key field) Since data storage is restricted (data deletion), partial correspondence is possible, which is effective in terms of security measures.

Of the data existing on the mobile phone device 1 side, data other than the data stored and managed on the company server 3 side is stored and held, so that the user is stored and managed on the company server 3 side. You don't have to be conscious of whether or not it is data.

If the data existing on the mobile phone device 1 side is not stored and managed on the company server 3 side, the data is uploaded to the company server 3 for storage management and the data present on the mobile phone device 1 side is stored. If data storage is restricted and data existing on the mobile phone device 1 side is also stored and managed on the company server 3 side, data storage existing on the mobile phone device 1 is restricted (data deletion). Since the mobile phone device 1 can edit the data stored and managed on the company server 3 side and upload it to the company server 3 side, the company server 3 can be edited even if such editing is performed. The data stored and managed on the side can be prevented from being inadvertently leaked.

In the first embodiment described above, when the data processing application is terminated, whether the data existing on the mobile phone device 1 side is different from the data stored and managed on the company server 3 side. However, when shifting from a state in which data communication with the company server 3 is possible (communication on) to a state in which data communication is impossible (communication off), the mobile phone device 1 side is informed prior to that. It may be determined whether the existing data is different from the data stored and managed on the company server 3 side. As a result, it is possible to change from the security release state to the security management state simply by shifting from the company premises to the outside of the company.

Further, in the first embodiment described above, a record having the same content as the content of the local record is obtained by deleting a record in the update target record group or deleting some fields. Although registration in the side address book TAD is prohibited, records registered in the terminal side address book TAD may be deleted, or some fields may be deleted.

In the first embodiment described above, the name is exemplified as the predetermined key in the address book record. However, a key other than the name is very good, and is not limited to the address book record. In addition, it is not limited to records, and may be individual data, files, etc., and the type and format of data are arbitrary.

In the first embodiment described above, as data stored and managed on the company server 3 side, data downloaded and received in advance from the server-side address book STD and temporarily stored in the temporary memory 13b is used. Although the comparison is made with data existing on the telephone device 1 side, the records may be compared while directly accessing the server-side address book STD for each record. Further, it may be determined whether or not the data existing on the mobile phone device 1 side is different from the data stored and managed on the company server 3 side depending on whether or not the data is newly created. .

(Embodiment 2)
Hereinafter, a second embodiment of the present invention will be described with reference to FIG.
In the first embodiment described above, the mobile phone device 1 is based on the determination result whether or not the data existing on the mobile phone device 1 side is different from the data stored and managed on the company server 3 side. The data existing on the side is deleted, but in the first embodiment, access to the data existing on the mobile phone device 1 side is restricted. In the first embodiment, when an application for processing data is terminated, whether the data existing on the mobile phone device 1 side is different from the data stored and managed on the company server 3 side is determined. In the second embodiment, the data existing on the mobile phone device 1 side is stored and managed on the company server 3 side at the time of transition from the power-on state to the power-off state. It is made to discriminate whether or not. Here, in both the embodiments, the same or the same names are denoted by the same reference numerals, the description thereof will be omitted, and the following description will focus on the features of the second embodiment. .

FIG. 9 is a flowchart showing an outline of the overall operation of the mobile phone device 1 that is started in response to power ON in the second embodiment.
First, the CPU 11 checks whether or not the company server 3 is accessible depending on whether or not the company server 3 can be accessed via the company network 2 (step B1). If the company server 3 can be accessed and is located on the company premises, data stored and managed on the company server 3 side, for example, address book data, schedule table data, etc., is to be downloaded to the mobile phone device 1. The download is received and temporarily stored in the temporary memory 13b (step B2).

Then, it is checked whether activation of any application is instructed (step B3), or whether the power is turned off (step B11). In this state, when an application activation is instructed (YES in step B3), it is checked whether data necessary for the application processing is downloaded in the temporary memory 13b (step B4). If the user is in the company premises, the necessary data has been downloaded (YES in step B4), so the data (in-terminal data) existing on the mobile phone device 1 side and the company server 3 side are stored and managed. After the data (downloaded data) are merged and displayed as a list (step B5), for example, address book processing and schedule table processing are performed as data processing corresponding to the application (step B6).

If data necessary for application processing instructed to start by user operation has not been downloaded (NO in step B4), it is a case where the user is not in the company premises when the power is turned on. 3 is checked whether it is in the company premises or not. If there is no data stored and managed on the company server 3 side, or if it was not in the company premises when the power was turned on, but came to be in the company premises when the application was started (in step B8) (YES), after displaying a list of all data (all data in the terminal) existing on the mobile phone device 1 side including the downloaded data (step B9), the process proceeds to data processing corresponding to the application (step B9). Step B6).

In addition, when there is no data stored and managed on the company server 3 side, or when it is not in the company premises when the power is turned on or when the application is started (NO in step B8), the downloaded and acquired data Among all data (all data in the terminal) existing on the mobile phone device 1 side including each data (stored and managed on the company server 3 side) to which a mask flag (access restriction flag) described later is added All other data are displayed as a list (step B10). Thereafter, as data processing according to the application, for example, address book processing, schedule table processing, and the like are performed (step B6).

Then, in response to the operation for instructing the end of the data processing (YES in Step B7), the data processing is ended and the process returns to Step B3 described above. If a power-off operation has been performed (YES in step B11), any of all data (all data in the terminal) existing on the mobile phone device 1 side including the downloaded and acquired data will be displayed. One data is designated (step B12), the designated data is compared with the download data in the temporary memory 13b (step B13), and it is checked whether or not the designated data is the same as the download data (step B14). . If they are not the same data (NO in step B14), it is checked whether all the data in the terminal has been specified (step B16). If not, the process returns to the above step B12 and the next Specify the data.

If the designated data is the same as one of the download data (YES in step B14), a mask flag for restricting the access is added to the designated record (step B15). Then, it is checked whether or not all of the data in the terminal has been designated (step B16). If not, the process returns to step B13 to repeat the operation of designating the next data. As a result, the above-described mask flag is added to each data stored and managed on the company server 3 side among all the data in the terminal.

As described above, in the second embodiment, the mobile phone is based on the determination result whether or not the data existing on the mobile phone device 1 side is different from the data stored and managed on the company server 3 side. Since the data existing on the device 1 side is controlled (access restricted), the data stored and managed on the company server 3 side is not inadvertently leaked, and the data security is improved. In addition, the user does not need to be aware of whether the data is stored and managed on the company server 3 side, and can have both safety and convenience.

Prior to the transition from the power-on state to the power-off state, it is determined whether or not the data existing on the mobile phone device 1 side is different from the data stored and managed on the company server 3 side. Therefore, it is possible to change from the security release state to the security management state simply by turning off the power.

In addition, since the access restriction of data stored and managed on the company server 3 side is released in a security environment where data communication with the company server 3 is possible, for example, special operations are performed on the company premises. It is possible to view and edit security-managed data without performing it.

Also in the second embodiment described above, when the data processing application is terminated, the state shifts from a state in which data communication with the company server 3 is possible (communication on) to an impossible state (communication off). In doing so, prior to that, it may be determined whether the data existing on the mobile phone device 1 side is different from the data stored and managed on the company server 3 side. Further, when the access restriction of data stored and managed on the company server 3 side is released, the access restriction may be released according to the result of user authentication such as password input.

In each of the above-described embodiments, the mobile phone device 1 is based on the determination result whether the data existing on the mobile phone device 1 side is different from the data stored and managed on the company server 3 side. When data existing on the side is controlled, the data is deleted or the access is restricted, but the output may be restricted. In other words, storage and access of data are permitted, but output such as display and printing of the data may be prohibited. As a result, data stored and managed on the server 3 side can be processed without being in a security environment.

Further, in each of the above-described embodiments, the network environment is connectable to the company server 3 via the company network 2, but the network environment is accessible to the home server via the home network, or in a public facility, shopping In a facility or the like, a network environment that can be connected to a hot spot (not shown) that provides a public Internet service using a wireless LAN may also be used. In addition, in each of the above-described embodiments, the mobile phone device is exemplified as the mobile terminal device. It may be.

1 Mobile phone device 2 Company network 3 Company server 11 CPU
12 storage unit 13 memory 13a work area 13b temporary memory 13
15 telephone communication unit 17 operation unit 18 display unit 19 wireless LAN module DB local database SAD server side address book TAD terminal side address book

Claims (12)

A network terminal device that can use data stored and managed on the external device side by performing data communication with the external device via a network,
Determining means for determining whether the data existing on the terminal device side is different from the data stored and managed on the external device side;
Control means for controlling the data present on the terminal device side based on the discrimination result by the discrimination means;
A network terminal device comprising: The data present on the terminal device side is update data newly created or edited on the terminal device side,
The control unit restricts storage of at least the same part of the update data when the determination unit determines that the update data is the same as the data stored and managed on the external device side. Or restrict access,
The network terminal device according to claim 1, wherein the network terminal device is configured as described above. The data present on the terminal device side is a data group including data received and acquired via the network from the external device side in order to use data stored and managed on the external device side,
When the determining means determines that the same data as the data stored and managed on the external device side is included in the data group by the determining means, at least the same data in the data group Restricting memory or restricting access to
The network terminal device according to claim 1, wherein the network terminal device is configured as described above. The determination unit determines whether data existing on the terminal device side is different from data stored and managed on the external device side when an application for processing data ends.
The network terminal device according to claim 1, wherein the network terminal device is configured as described above. Prior to that, when the determination unit shifts from a power-on state to a power-off state, or shifts from a state where data communication with the external device is possible to an impossible state, Determining whether the data present on the terminal device side is different from the data stored and managed on the external device side;
The network terminal device according to claim 1, wherein the network terminal device is configured as described above. The determination means compares the data existing on the terminal device side with the data stored and managed on the external device side, so that the data existing on the terminal device side To determine whether it is different from the data stored and managed in
The network terminal device according to claim 1, wherein the network terminal device is configured as described above. The determination unit is configured to compare a series of data composed of a plurality of blocks existing on the terminal device side with a series of data composed of a plurality of blocks stored and managed on the external device side. To determine whether the data is different for each
The network terminal device according to claim 6, which is configured as described above. Among a series of data composed of a plurality of blocks existing on the terminal device side, the block in which data is determined to be different by the determination means and the data in each other block excluding a predetermined block Restrict memory or restrict its access,
The network terminal device according to claim 7, which is configured as described above. If the data present on the terminal device side is the same as the data stored and managed on the external device side as a result of the discrimination by the discrimination means, the control means exists on the terminal device side. If the data on the terminal device side is different from the data stored and managed on the external device side, the data on the terminal device side is stored and retained. To control,
The network terminal device according to claim 1, wherein the network terminal device is configured as described above. The control means releases access restrictions on data stored and managed on the external device side in a security environment in which data communication with the external device is possible.
The network terminal device according to claim 9, which is configured as described above. The discrimination means compares the data existing on the terminal device side with the data stored and managed on the external device side, so that the data existing on the terminal device side is transferred to the external device side. To determine whether or not
If the data present on the terminal device side is not stored and managed on the external device side as a result of the discrimination by the discrimination means, the control means uses the data existing on the terminal device side as the external device. Uploading data to a device and storing and managing it on the external device side, restricting storage of data existing on the terminal device side or restricting access thereof, and data existing on the terminal device side being the external device If storage management is also performed on the side, the storage of data existing on the terminal device side is restricted or its access is restricted,
The network terminal device according to claim 1, wherein the network terminal device is configured as described above. Against the computer,
A function of making data stored and managed on the external device side available by performing data communication with the external device via a network; and
A function of determining whether data existing on the terminal device side is different from data stored and managed on the external device side;
Based on the determination result, a function of controlling data existing on the terminal device side,
A program to realize

Images