JP2012014399A - Communication terminal, communication system, and method for reproducing operation environment - Google Patents

Abstract

Provided is a communication terminal operation environment reproduction system capable of reproducing various types of terminal operation environments on a use terminal without mounting an emulator in advance on the use terminal.
In a memory 30 of an emulation target terminal 1, an emulator 11 that reproduces the operation environment of the emulation target terminal 1 on a virtual machine and an operation environment in which individual operation environments in the emulation target terminal 1 are defined. A virtual machine environment state saving file 12 storing information is stored. The temporary use terminal 2 logs into the emulation target terminal 1, downloads the virtual machine environment state storage file 12, and stores it in the sandbox 21. The temporary use terminal 2 reproduces the operation environment of the emulation target terminal 1 on the LCD touch panel 39 of the temporary use terminal 2 by executing the emulator 11 while referring to the operation environment information in the sandbox 21.
[Selection] Figure 6

Description

  The present invention relates to a system for reproducing the operation environment of an emulation target terminal on a specific communication terminal through a network.

  In a communication system such as a portable terminal, a preset operation environment for a communication terminal may be ported to a specific communication terminal so that it can be used. For example, in the mobile phone system, a service that transplants part of the operating environment of mobile terminals that users are constantly using to rental mobile phones that support international roaming services through SIM (Subscriber Identity Module) cards, etc. Has been. Here, the “operation environment” is not limited to user interface specifications such as the arrangement of keys constituting the keyboard and the assignment of functions to the keys, but personal information such as a telephone directory, outgoing / incoming records, and sent / received mails. It is a concept that also implies the memory state.

  Further, for example, the following proposals have been made to develop the above services.

  First, from a communication terminal that is temporarily used by a user (hereinafter referred to as “temporary use terminal”) to a communication terminal that is always used by the user (hereinafter referred to as “own terminal”) through the network. There is a proposal to reproduce the above operating environment. For example, it is a proposal that allows a user to download a phone book or the like stored in the terminal to a temporary use terminal so that the phone book or the like can be used on the temporary use terminal.

  Further, there is a proposal that the user reproduces the operation environment by uploading personal information stored in the terminal to a storage system on the network and then downloading the personal information from the storage system to a temporary use terminal. is there.

  In addition, an emulator that reproduces the operating environment of multiple types of communication terminals (specifications such as function assignment to each key) is installed in the temporary use terminal in advance, and an emulator corresponding to the type of the own terminal is started on the temporary use terminal. There is also a proposal for the temporary use terminal to be operated in the same manner as the own terminal.

Japanese Unexamined Patent Publication No. 2000-216858 JP 2002-368875 A JP 2006-227933 JP

  However, the operability of the own terminal cannot be sufficiently reproduced on the temporary use terminal simply by downloading the personal information from the own terminal directly or through the storage system to the temporary use terminal. For example, such a problem occurs when the function assigned to each key is different between the own terminal and the temporary use terminal.

In addition, according to a method in which an emulator for a plurality of types of communication terminals is mounted on a temporary use terminal in advance, the operability of a type of terminal that does not support the installed emulator can be reproduced on the temporary use terminal. Can not.

  Accordingly, an object of the present proposal is to provide a mechanism that can reproduce the operation environment of various types of terminals on the communication terminal without mounting an emulator in advance on the communication terminal that is a temporary use terminal.

  In the proposed system, an emulator for emulating the operation environment of the emulation target terminal on the communication terminal is prepared outside the communication terminal. Then, the emulator is downloaded to the communication terminal via the network and executed.

  According to the disclosed system, there is no need to mount an emulator for the emulation target terminal in advance on the communication terminal. Then, each time the temporary use terminal is used, the emulator for the emulation target terminal is downloaded to the communication terminal and executed, so that the operation environment of the emulation target terminal becomes the operation environment in the input unit of the communication terminal. As reproduced.

System Configuration Block diagram showing the configuration of the mobile terminal to be emulated Block diagram showing the configuration of a temporary mobile terminal Flow chart showing the main process of the mobile terminal to be emulated Flow chart showing processing at the time of emulation of a temporary use terminal Conceptual diagram explaining system operation Operation sequence diagram explaining system operation Illustration of non-shared mode Illustration of sharing mode Block diagram showing server configuration Flow chart showing the main process of the mobile terminal to be emulated Conceptual diagram explaining system operation Operation sequence diagram explaining system operation Illustration of non-shared mode Illustration of sharing mode

  Hereinafter, embodiments of the present plan will be described based on the drawings.

Example 1 is an example in which an actual mobile terminal is an emulated mobile terminal in a mobile phone system.
<System configuration>
FIG. 1 is a block diagram illustrating a schematic configuration of the mobile phone system according to the first embodiment. As shown in FIG. 1, the mobile phone system includes a plurality of mobile terminals 1 and 2 that are connected to each other through a mobile phone network N and can establish a call between them. One of these mobile terminals is a mobile terminal (self-terminal, emulated mobile terminal) 1 that is always used by a certain user, and the other is a mobile terminal that is temporarily used by the user. (Temporary use portable terminal) 2. Therefore, the temporary use portable terminal 2 corresponds to a communication terminal (use terminal) that performs communication with other terminals through the network.

The mobile terminal 1 to be emulated has a self-terminal emulator 11 that is a program for reproducing a default operating environment corresponding to the type of the self-terminal on the temporary mobile terminal 2. The above-mentioned operation environment includes the key shape [design, color], the key layout, the shape and layout of the buttons on the touch panel, the user interface such as the basic function set for each key, and the shape and design of the display. included. The terminal emulator 11 is a program programmed in the JAVA (registered trademark of Sun Micro) language, for example, and is executed on a virtual machine such as JAVA virtual machine (registered trademark of Sun Micro). The terminal emulator 11 is stored in a virtual machine environment state saving file 12.

  The virtual machine environment state saving file 12 further defines operation environment in the current state of the own terminal and stores operation environment information referred to by the own terminal emulator 11 on the temporary use portable terminal 2. The operation environment information includes personal information such as a telephone directory, outgoing / incoming records, sent / received mails, function settings for each key customized by the user, and the like. That is, the operation environment information in the virtual machine environment state storage file 12 corresponds to information that individually indicates the operation environment of the emulation target terminal.

  The emulation target mobile terminal 1 further includes a mobile terminal entity 10 including hardware and programs similar to those of a general mobile terminal. In addition to a general mobile phone function, the mobile terminal entity 10 stores a login acceptance function from a remote terminal (that is, the temporary mobile terminal 2) and the operation environment of the terminal 1 in the virtual machine environment state storage file 12. The function to reflect can be realized.

  The temporary mobile terminal 2 also has a mobile terminal entity 20 similar to the mobile terminal entity 10 described above. The mobile terminal entity 20 implements a general mobile phone function, a log-in request function to a remote terminal (that is, the emulation target mobile terminal 1), and a virtual machine environment state storage file 12 download request function. Further, the mobile terminal entity 20 realizes an emulator activation function, a function of returning the virtual machine environment state storage file 12 to the remote terminal after the end of emulator execution, and a function of deleting the file.

  Further, the terminal 2 realizes a sandbox 21 as an execution environment of the JAVA program by executing the virtual machine described above. The sandbox 21 is a logical environment realized by software, a processor, or a chipset, but is represented as one block in FIGS. 1 and 3. The virtual machine environment state saving file 12 described above is stored in the sandbox 21 and the terminal emulator 11 described above is executed in the sandbox 2.

<Hardware configuration>
[Emulated mobile terminal 1]
FIG. 2 is a block diagram illustrating a hardware configuration of the emulation target mobile terminal 1. As shown in FIG. 2, the terminal 1 includes a communication unit 31, a control unit 32, a signal processing unit 33, a memory 30, a CPU (Central Processing Unit) 35, and a ROM (Read Only Memory) connected to each other through a bus B. 36 and a RAM (Random Access Memory) 37. Further, a key input device 38, an LCD (Liquid Crystal Display) touch panel 39, a speaker 40, and a microphone 41 are connected to the bus B.

  The CPU 35 reads out and executes the main program stored in the ROM 36, thereby performing processing according to various commands and data input through the key input device 38 and the LCD touch panel 39.

The key input device 38 is a keyboard composed of a plurality of keys including a cross key and a numeric keypad.

  The ROM 36 is a rewritable nonvolatile memory such as a flash memory. In the ROM 36, in addition to the main program, terminal identification information (telephone number, Mac address, etc.) of the own terminal 1, a personal information database for storing personal information such as a telephone directory and sent / received mail, and the operating environment of the own terminal 1 Each storage area and flag setting area are provided.

  The main program has definition information (not shown) that defines the arrangement of each key constituting the key input device 38 and the allocation relationship (default) between each key and function. By referring to the definition information, , Recognize the significance of commands etc. input to each key. The main program customizes the operating environment such as shortcut key assignment, user dictionary for Japanese conversion program, etc., when a predetermined command is input by the user, and stores the result in the storage area.

  In the phone book, the name, phone number, and address of the other party that the user arbitrarily registered are registered in association with each other, and the address of the temporary use terminal, terminal identification information, and password are mutually Registered in association.

  In the flag setting area, the current mode of the own terminal 1 is a non-shared mode (a mode in which the operating environment is reproduced only for one temporarily used terminal) or a shared mode (an operating environment is set for a plurality of temporarily used terminals). A mode flag for setting whether the mode is a reproduction mode) is set. The mode flag corresponds to information specifying whether the operation mode is the shared mode or the non-shared mode. In the same flag setting area, whether the own terminal 1 is currently locked (does not accept operation input to the own terminal 1) or unlocked (accepts operation input to the own terminal 1). The in-lock flag shown is set. The in-lock flag corresponds to information for specifying whether or not the lock is in progress.

  The LCD touch panel 39 is a device in which an LCD panel that displays the processing result of the CPU 35 is covered with a touch panel to which the above commands are input.

  The control unit 32 is an engine that implements a call function using the LCD touch panel 39, the speaker 40, the microphone 41, the signal processing unit 33, and the communication unit 31 under the control of the CPU 35. The signal processing unit 33 converts the packet communication data received from the CPU 35 and the call voice signal received from the microphone 41 into a communication signal in a data format according to the communication standard of the mobile phone network N, and passes it to the communication unit 31. . Further, the signal processing unit 33 decodes the communication signal received from the communication unit 31, and outputs it from the speaker 40 if it is a call voice signal, and inputs it to the CPU 35 if it is data for packet communication. The communication unit 31 wirelessly communicates with any base station (not shown) constituting the mobile phone network N through the antenna 34, thereby transmitting a communication signal to the communication partner, and receiving a communication signal from the communication partner. Receive.

The memory 30 is a memory as a rewritable storage unit such as a flash memory, and stores the virtual machine environment state saving file 12 described above. The memory 34 may be the same element as the ROM 36 described above.
[Temporary use mobile terminal 2]
FIG. 3 is a block diagram illustrating a hardware configuration of the temporary mobile terminal 2. As illustrated in FIG. 3, the terminal 2 also includes hardware 51 to 61 similar to the hardware 31 to 41 of the emulation target mobile terminal 1 except for the memory 30. In addition, the bus B of the temporary mobile terminal 2 is provided with the above-described sandbox 21. A sandbox 21 shown in FIG. 3 shows an example in which the sandbox 21 is realized by a chip set. In addition,
The key input device 38 and the LCD touch panel 39 of the temporary mobile terminal 2 correspond to an input unit.

<Software configuration>
[Emulated mobile terminal 1]
FIG. 4 is a flowchart showing processing executed by the CPU 35 that reads the main program stored in the ROM 36 of the emulation target mobile terminal 1.

  The process starts automatically when the main power supply is turned on to the mobile terminal 1 to be emulated.

  In first S001, the CPU 35 stores the contents of the personal information database stored in the ROM 36 of the terminal 1 and the operation environment (customized) of the terminal 1 in the memory 30. It is reflected (synchronized) with the operation environment information in the environment state storage file 12.

  In next S002, the CPU 35 waits for an operation on the key input device 38 or the LCD touch panel 39 of the own terminal 1 or a login request from the remote terminal, and when there is the input or login request, the process proceeds to S003.

  In S003, the CPU 35 determines whether there is an operation on the key input device 38 or the LCD touch panel 39 of the terminal 1 or a login request from the remote terminal. If the former, the process proceeds to S004, and the latter is the latter. If so, the process proceeds to S007.

  In S004, the CPU 35 checks the state of the mode flag in the flag setting area of the ROM 36. If the shared mode is set, the process proceeds to S006, and if the non-shared mode is set, the process proceeds to S005.

  In S005, the CPU 35 checks the status of the lock flag in the flag setting area of the ROM 36, and if it is set to “locked”, the process returns to S002 (input refusal) and has been reset to “unlock”. If so, the process proceeds to S006.

  In S006, the CPU 35 executes an action (for example, command execution, data input reception, operation environment customization, etc.) for an operation on the key input device 38 or the LCD touch panel 39 of the terminal 1 itself. When S006 is completed, the CPU 35 returns the process to S001.

  On the other hand, in S007 executed when there is a login request from the remote terminal, the CPU 35 checks the state of the mode flag in the flag setting area of the ROM 36, and if it is set to “shared mode”, the process proceeds to S009. If it is set to “non-shared mode”, the process proceeds to S008.

  In S008, the CPU 35 checks the status of the locked flag in the flag setting area of the ROM 36, and if it is locked, the process proceeds to S011, and if not locked, the process proceeds to S009.

In S009, the CPU 35 checks whether or not the remote terminal (connection source terminal) that transmitted the login request is registered in the telephone book stored in the personal information database in the ROM 36. That is, the CPU 35 checks whether or not the individual identification information of the connection source terminal included in the login request is registered in advance in the telephone directory as that of the temporary use mobile terminal. Then, the CPU 35 advances the process to S011 if the connection source terminal is not registered in advance in the telephone directory, and advances the process to S010 if registered.

  In S010, the CPU 35 checks whether or not the password included in the login request matches the password registered in the telephone book in association with the individual identification information of the connection source terminal (temporary use portable terminal). Then, the CPU 35 advances the process to S012 if they match, and advances the process to S011 if both are hesitant.

  In S011, the CPU 35 responds to the connection source terminal (temporary mobile terminal) with a connection impossible notification.

  On the other hand, in S012, the CPU 35 sets the locking flag in the flag setting area of the ROM 36 to “locking”.

  In the next step S013, the CPU 35 responds to the connection source terminal (temporary use portable terminal) with a connection permission notification.

  In next S014, the CPU 35 transmits a login completion response to the connection source terminal (temporary use portable terminal).

  In next S015, the CPU 35 waits for a download request from the connection source terminal (temporary use portable terminal), and when there is a download request, the process proceeds to S016.

  In S016, the CPU 35 compresses the virtual machine environment state storage file 12 in the memory 30 and transmits it to the connection source terminal (temporary use portable terminal). Accordingly, the CPU 35 that executes S016 corresponds to a transmission unit that transmits the emulator 11 to the temporary use terminal 2 that has requested download of the emulator.

  In next S017, the CPU 35 waits for a sandbox execution result notification (described later) from the connection source terminal (temporary use portable terminal), and when there is a sandbox execution result notification, the process proceeds to S018.

  In S018, the CPU 35 reflects the contents of the received sandbox execution result in the personal information database in the ROM 36 and the operation environment of the terminal 1 itself. That is, the CPU 35 updates the personal information database in the ROM 36 and the operation environment of the terminal 1 according to the difference in the operation environment information included in the sandbox execution result. Therefore, the CPU 35 that executes S018 corresponds to a reflection unit that reflects the content of the information transmitted from the temporary use terminal 2 in the information stored in the storage unit.

In the next S019, the CPU 35 resets the locking flag in the flag setting area of the ROM 36 to “unlocked”. When S019 is completed, the CPU 35 returns the process to S001.
[Temporary use mobile terminal 2]
FIG. 5 is a flowchart showing a portion executed at the time of emulation in the processing executed by the CPU 55 that has read the main program stored in the ROM 56 of the temporary mobile terminal 2.

In S <b> 101, the CPU 55 waits for a login operation to a specific emulation target terminal (connection destination portable terminal) 2 to be performed on the key input device 58 or the LCD touch panel 59 of the terminal 2. Here, the specific method of the connection-destination mobile terminal 2 may be a method of selecting from the telephone directory stored in the ROM 56 of the temporary use mobile terminal 2, or the user may identify the terminal of the connection-destination mobile terminal 2. A method of directly inputting information may be used. When the login operation is performed, the CPU 55 advances the process to S102.

  In S102, the CPU 55 displays a message on the LCD touch panel 59 that prompts the user to input a password registered for the temporary mobile terminal 2 in the phone book held by the connection-destination mobile terminal 1 specified in S101. indicate. When the user inputs a password in response to the message, the CPU 55 advances the process to S103.

  In S103, the CPU 55 transmits a login request to the connection destination portable terminal 1 specified in S101. The log-in request message includes the terminal identification information of the temporary mobile terminal 2 stored in the ROM 56 of the temporary mobile terminal 2 and the password input in S102.

  In next S104, the CPU 55 waits for the connection-destination portable terminal 1 to notify the connection failure notification (S011) or the connection permission notification (S013). When the CPU 55 receives the connection impossible notification (S011), the process returns to S101. When the CPU 55 receives the connection permission notification (S013), the process proceeds to S105.

  In S105, the CPU 55 transmits a download request (S015) to the connection-destination mobile terminal 1. When the virtual machine environment state storage file 12 transmitted from the connection-destination portable terminal 1 in response to the download request is received, the CPU 55 advances the process to S106. Therefore, the CPU 55 that executes S105 corresponds to a download unit that downloads the emulator 11 that emulates the operation environment of the emulation target terminal via the network.

  In S106, the CPU 55 decompresses the virtual machine environment state storage file 12 received in S105, stores it in the sandbox 21 (physically on the RAM 57), and loads the emulator 11 in the virtual machine environment state storage file 12 into it. Execute. At this time, the emulator 11 causes the CPU 55 to display the images of the key input device 38 and the LCD touch panel 39 of the connection-destination mobile terminal 1 on the LCD touch panel 59. Then, the emulator 11 sends the personal information (e-mail, incoming / outgoing record, etc.) included in the operation environment information in the virtual machine environment state saving file 12 in the image of the displayed LCD touch panel 39 to the CPU 55. Are displayed (see FIG. 6). In addition, when any key in the displayed key input device 38 is selected by the emulator 11 in response to a press on the LCD touch panel 39 or an operation of a cross key in the key input device 58 with respect to the CPU 55, Recognize that the key was pressed. Then, the emulator 11 assigns the default function assigned to the CPU 55 by the definition information in the main program in the connection destination terminal 1 for the recognized key (if there is a definition based on the operation environment information, the definition is used). The customized function) is executed. Further, the emulator 11 causes the CPU 55 to display the execution result of the above function in the image of the LCD touch panel 39 and reflect it in the operation environment information in the virtual machine environment state saving file 12. Therefore, the CPU 55 that executes the program of the virtual machine and the process of S106 executes the emulator downloaded by the download unit, so that the operation environment of the terminal to be emulated is reproduced as the operation environment in the input unit. ,Equivalent to.

  The processing by the emulator 11 as described above is continued until an end command is input through the key input device 38 of the temporary mobile terminal 2. In S107, the CPU 35 waits for the end of the emulator 11 in the sandbox 21, and when the emulator 11 ends, the process proceeds to S108.

  In S <b> 108, the CPU 35 extracts the difference between the contents of the operation environment information at the time of downloading the virtual machine environment state storage file 12 and the contents of the operation environment information at the present time based on the update history of the operation environment information by the emulator 11. Then, the CPU 35 incorporates the difference of the extracted operation environment information into the “sandbox execution result notification (S017)” and transmits it to the connection destination portable terminal 1.

In the next S109, the CPU 35 deletes the virtual machine environment state saving file 12 from the sandbox 21 (physically on the RAM 57). When S109 is completed, the CPU 35 returns the process to S101.
<Operation example>
Hereinafter, an operation example of the present system configured as described above will be described with reference to FIGS. 6 and 7.
[Unshared mode]
In the mobile terminal 1 that is always used by the user, whenever the personal information on the ROM 56 is updated or the operation environment is customized, the updated personal information and the contents of the customized operation environment are displayed in the virtual machine environment state. It is reflected (synchronized) in the saved file 12 (S001).

  Then, it is assumed that the user desires to use one specific terminal as the temporary use mobile terminal 2 instead of the mobile terminal 1 that is always used. In this case, the user inputs a predetermined command to the terminal 1 in advance to set the operation mode to the non-shared mode (mode flag = non-shared mode), and the temporary use portable terminal 2 is stored in the telephone directory. Register terminal identification information and password. Then, the user performs a login operation designating the terminal identification information of the portable terminal 1 through the key input device 58 and the LCD touch panel 59 of the temporary use portable terminal 2 (S101), and inputs the password (S102). Then, the temporary mobile terminal 2 performs a remote operation login while transmitting the password and its own terminal identification information to the own terminal 1 (S103).

Then, in the portable terminal 1, after determining the sharing mode and the locked state (S007, S008), the combination of the password received from the temporary use portable terminal 2 and the terminal identification information of the temporary use portable terminal 2 is registered in the phone book. Verification is performed by collating with the information (S009, S010). At this time, the portable terminal 1 is set to the locked state (S012), and thereafter, the operation on the key input device 38 and the LCD touch panel 39 of the portable terminal 1 is rejected (S005 = YES). After the above, the portable terminal 1 transmits a connection permission notification and a login completion response to the temporary use portable terminal 2 (S013, S014).

  The temporary mobile terminal 2 that has received the notification transmits a download request to the mobile terminal 1 (S105). The mobile terminal 1 that has received the download request compresses the virtual machine environment state storage file 12 in order to increase the download efficiency, and transmits the compressed virtual machine environment state storage file 12 to the temporary use mobile terminal 2. (S016).

  The temporary mobile terminal 2 decompresses the received virtual machine environment state storage file 12, stores the decompressed virtual machine environment state storage file 12 in the sandbox 21, and executes the emulator 11 (S106). At this time, as described above, the operating environment of the mobile terminal 1 is reproduced on the LCD touch panel 59 of the temporary mobile terminal 2.

When the user inputs an end command to end the operation of the temporary mobile terminal 2 (S107), the temporary mobile terminal 2 sends an execution result notification including the difference information of the operation environment information updated in the sandbox 21. It transmits to the portable terminal 1 (S108). The temporary mobile terminal 2 deletes the virtual machine environment state storage file 12 in the sandbox 21 (S109).

  The portable terminal 1 reflects the received difference information in the execution result notification in the personal information database and the operating environment in the ROM 36 (S018), and releases the terminal 1 from the locked state (S019). Thereafter, since operations on the key input device 38 and the LCD touch panel 39 of the portable terminal 1 are accepted (S005 = NO), the portable terminal 1 can be used again.

  As described above, according to the present example, the emulator 11 executed on the temporary use portable terminal 2 is provided from the own terminal 1. Therefore, it is not necessary to prepare an emulator on the temporary use portable terminal 2 in advance. Further, the temporary use portable terminal 2 can be used as a substitute for all kinds of portable terminals 1.

  Further, according to this example, the operation environment information is transmitted to the temporary use terminal 2 together with the emulator 11 in a state where the operation environment information is stored in the virtual machine environment state saving file 12. Then, the emulator 11 executed in the temporary use terminal 2 refers to the operation environment information. Accordingly, not only the default operation environment of the mobile terminal 1 but also the operation environment customized in each mobile terminal 1 and the storage state of individual information (individual operation environment) are reproduced in the temporary use terminal 2.

Also, according to this example, authentication of the temporary mobile terminal 2 by the mobile terminal 1 is performed by a combination of the terminal identification information and password of the temporary mobile terminal 2 registered in advance in the phone book of the mobile terminal 1. And this terminal identification information is not the information which a user can input arbitrarily at the time of login unlike simple user ID. Therefore, the authentication of the temporary mobile terminal 2 according to the present example has higher security than the authentication based on the simple combination of user ID and password. Further, according to this example, since the operation history in the temporary mobile terminal 2 is reflected in the own terminal 1, the operation environment in the temporary mobile terminal 2 is continuously used even when the reuse of the own terminal 1 is started. It becomes possible to do. Further, since the difference information in the virtual machine environment state storage file 12 is automatically deleted when the emulator 11 is terminated in the temporary mobile terminal 2, there is a risk of leakage of personal information even if the temporary mobile terminal 2 is a rental product. There is no.
[Sharing mode]
In the above-described non-shared mode, as shown in FIG. 8, when one's own terminal 1 is emulated in any one of the temporary use portable terminals 2 registered in the phone book of the own terminal 1, The own terminal 1 cannot be emulated. As a result, continuity of personal information and operation environment is maintained. However, if importance is not placed on the continuity of the personal information and the operating environment, as shown in FIG. 9, the self-terminal 1 may be emulated in a plurality of temporary use mobile terminals 2. In this case, the user inputs a predetermined command to the terminal 1 in advance to set the operation mode to the shared mode (mode flag = shared mode), and the terminals of the plurality of temporary use portable terminals 2 are stored in the phone book. Register identification information and password.

  Then, even if the own terminal 1 is set to the locked state by emulating the own terminal 1 in any one of the temporary use portable terminals 2, the step (S005, S008) for determining the locked state is bypassed. (S004, S007). As a result, since the own terminal 1 operates in the same manner as when the locked state is released, the second and subsequent temporary use terminals 2 can emulate the own terminal 1.

The second embodiment is an example in which, in a mobile phone system, a virtual mobile terminal constructed on a server is an emulation target mobile terminal. That is, the above-described first embodiment is based on the service model in which each user always uses one terminal. However, if the user tends to replace the mobile terminal in a very short period of time, a service model in which the user does not have his own terminal and rents and uses a temporary use terminal as necessary can be assumed. Even in that case, Example 2 was devised to maintain the continuity of the operating environment.
<System configuration>
[server]
In the second embodiment, a server 3 is provided instead of the emulation target terminal (own terminal) 1 in the first embodiment. The server 3 is a computer that stores and manages the emulator 11 and the virtual machine environment state storage file 12 described in the first embodiment for each user who uses the mobile phone system.

As shown in FIG. 10, the server 3 has the same hardware as a general server computer. That is, a CPU 75, a ROM 76, a RAM 77, a LAN (Local Area Network) adapter 71, a hard disk 72, a removable memory external interface 70, a display 79, and a keyboard 78 are connected to the bus B of the server 3. The server 3 is connected to a mobile phone network and a computer network (not shown) through a LAN adapter 71. In the hard disk 72, a dedicated area for storing the virtual machine environment state saving file 12 is secured for each user who has contracted with a communication carrier operating the mobile phone system. The dedicated area for each user is specified by virtual terminal identification information, and a mode flag and a locked flag are set. The hard disk 72 stores a program that causes the CPU 75 to respond to the virtual machine environment state storage file 12 corresponding to the terminal identification information when a login request specifying the terminal identification information is received. Hereinafter, the CPU 75 of the server 3 that operates according to the program is referred to as a “virtual portable terminal”, and the “terminal identification information” is referred to as the “terminal identification information of the virtual portable terminal”.
[Temporary use mobile terminal]
On the other hand, the hardware configuration of the temporary mobile terminal 2 in the second embodiment is exactly the same as that in the first embodiment.
<Software configuration>
[Virtual mobile terminal]
FIG. 11 is a flowchart showing the processing contents of the virtual portable terminal.

  The processing of the virtual mobile terminal does not require processing based on operations on the key input device 38 and the LCD touch panel 39 of the mobile terminal 1, unlike the emulation target mobile terminal 1 in the first embodiment. Therefore, the process of the virtual portable terminal does not have steps corresponding to S001, S003 to S006 in FIG. Steps S201 and S202 to S214 in FIG. 11 are the same processes as steps S002 and S007 to S019 in FIG.

[Temporary use mobile terminal]
The software configuration of the temporary mobile terminal 2 in the second embodiment is exactly the same as that in the first embodiment.

<Operation example>
Hereinafter, an operation example of the present system configured as described above will be described with reference to FIGS. 12 and 13.

[Unshared mode]
First, when the user selects any type of mobile phone when making a contract with the above-mentioned communication carrier, the virtual machine environment state storage file 12 storing the emulator 11 and the operation environment information corresponding to the selected mobile phone is stored in the hard disk 72. Prepared in its own private area. Then, the user accesses the server 3 from the computer terminal operated by the user, and temporarily uses the phone book of the virtual machine environment state storage file 12 that the user is actually planning to use. The terminal identification information and password of the terminal 2 are registered. Similarly, the user sets the mode flag to “non-shared mode” in the flag setting area in the hard disk of the server 3.

  Then, the user performs a login operation specifying the terminal identification information of the virtual portable terminal through the key input device 58 and the LCD touch panel 59 of the temporary portable terminal 2 (S101), and inputs the password (S102). Then, the temporary mobile terminal 2 transmits the password and its own terminal identification information to the server 3 (virtual mobile terminal) and performs remote operation login (S103).

  After the server 3 (virtual portable terminal) determines the sharing mode and the locked state (S202, S203), the terminal identification information and password of the temporary use terminal 2 are stored in the telephone directory corresponding to the designated virtual portable terminal. Authentication that the combination is registered is performed (S204, S205). Then, the server 3 (virtual mobile terminal) sets the locked flag to “locked” (S207), and transmits a connection permission notification and a login completion response to the temporary mobile terminal 2 (S208, S209). ).

  Thereafter, when the temporary use portable terminal 2 transmits a download request to the server 3 (virtual portable terminal) (S105), the server 3 (virtual portable terminal) is in a virtual machine environment state in a dedicated area corresponding to the virtual portable terminal. The saved file 12 is read and compressed. Then, the server 3 (virtual portable terminal) transmits the compressed virtual machine environment state storage file 12 to the temporary use portable terminal 2 (S211).

  The temporary mobile terminal 2 decompresses the received virtual machine environment state storage file 12 and executes it in the sandbox 21 (S106). At this time, the operating environment of the virtual portable terminal is reproduced on the LCD touch panel 59 of the temporary portable terminal 2.

  When the user inputs an end command to end the operation of the temporary use portable terminal 2 (S107), the temporary use portable terminal 2 executes the execution result including the difference of the operation environment information in the updated virtual machine environment state storage file 12. The notification is transmitted to the server 3 (virtual portable terminal) (S108). Further, the temporary mobile terminal 2 deletes the virtual machine environment state storage file 12 in the sandbox 21 (S109).

  The server 3 (virtual portable terminal) updates the virtual machine environment state storage file 12 in the dedicated area corresponding to the designated virtual portable terminal based on the received difference information in the execution result notification (S213). The terminal 1 is released from the locked state (S214).

  As described above, according to this example, the presence of the own terminal 1 that is always used by the user becomes unnecessary. Nevertheless, even if the temporary use portable terminal 2 is changed one after another, the user can continuously use the operation environment in which continuity is maintained. Further, as shown in FIG. 14, since only one temporary portable terminal 2 can be used at a time, leakage of personal information is prevented.

[Sharing mode]
For example, when a business user issues a mobile phone to a member of a specific department, there is a case where all the mobile phones to be provided have an operating environment such as a telephone directory created based on a customer list. An operation mode that meets such a demand is a “shared mode”.

  In this case, by accessing the server 3 (virtual mobile terminal) in advance, the user sets the mode flag in his dedicated area to “shared mode” and also stores a plurality of temporary mobile terminals 2 in the phone book. Register terminal identification information and password.

  Then, even if the locked flag in the private area is set to “locked” by emulating the virtual portable terminal in any one of the temporary use portable terminals 2, the step of determining the locked state ( S203) is bypassed (S202). As a result, the server 3 (virtual portable terminal) operates in the same manner as when the locked state is released. Therefore, as shown in FIG. It can be emulated.

[Appendix]
[Appendix 1]
A communication terminal that communicates with other terminals via a network,
An input section;
A download section that downloads an emulator that emulates the operating environment of the terminal being emulated;
A communication terminal comprising: an emulator execution unit that reproduces an operation environment of the emulation target terminal as an operation environment in the input unit by executing an emulator downloaded by the download unit.

[Appendix 2]
The download unit, together with the emulator, downloads information indicating the operating environment of the emulation target terminal individually,
The communication according to claim 1, wherein the emulator execution unit reproduces an individual operation environment of the emulation target terminal by executing the emulator with reference to the information downloaded by the download unit. Terminal.

[Appendix 3]
The communication terminal according to appendix 2, wherein the emulator execution unit places the information in a sandbox, executes the emulator, and deletes the information from the sandbox at the end of execution of the emulator.

[Appendix 4]
A communication system having a communication device and a use terminal that can communicate with each other through a network,
The communication device
A storage unit for storing an emulator for reproducing the operation environment of the terminal to be emulated;
A transmitter that transmits the emulator to a user terminal that has requested download of the emulator;
The user terminal is
An input section;
A download unit for requesting the communication device to download an emulator that emulates the operating environment of the terminal to be emulated, and receiving the emulator transmitted in response to the request;
A communication system comprising: an emulator execution unit that reproduces an operation environment of the terminal to be emulated as an operation environment in the input unit by executing an emulator received by the download unit.

[Appendix 5]
The storage unit further stores information individually indicating an operation environment of the emulation target terminal together with the emulator,
The transmission unit transmits the information together with the emulator to a user terminal that has requested download of the emulator,
The download means receives the information together with the emulator,
The communication according to claim 4, wherein the emulator execution unit reproduces an individual operation environment of the emulation target terminal by executing the emulator with reference to the information received by the download unit. system.

[Appendix 6]
The storage unit further stores a combination of terminal identification information and a password of any of the emulation target terminals,
The transmission unit requests downloading of the emulator only when the combination of the terminal identification information of the user terminal that requested the download of the emulator and the password notified by the user terminal is registered in the storage unit. The communication system according to appendix 4, wherein the emulator is transmitted to the used terminal.

[Appendix 7]
The storage unit further stores a combination of terminal identification information and a password of any of the emulation target terminals,
The transmission unit downloads the emulator only when the combination of the terminal identification information of the user terminal that requested the download of the emulator and the password notified by the temporary user terminal is registered in the storage unit. The communication system according to appendix 5, wherein the emulator and the information are transmitted to the requested use terminal.

[Appendix 8]
The communication system according to appendix 5 or 7, wherein the emulator execution unit executes the emulator by placing the information in a sandbox, and deletes the information from the sandbox at the end of execution of the emulator. .

[Appendix 9]
The emulator execution unit executes the emulator by placing the information in a sandbox, and transmits the information to the communication device at the end of execution of the emulator,
8. The communication system according to appendix 5 or 7, wherein the communication device further includes a reflection unit that reflects the content of the information transmitted from the user terminal in the information stored in the storage unit.

[Appendix 10]
The emulator execution unit executes the emulator by placing the information in a sandbox, and at the end of execution of the emulator, transmits a difference from the download time of the information to the communication device,
The communication device further includes a reflection unit that reflects the content of the difference of the information transmitted from the user terminal in the information stored in the storage unit. Communications system.

[Appendix 11]
The storage unit stores information for specifying whether the operation mode is shared mode or non-shared mode, and information for specifying whether the operation mode is locked,
When the information specifying that the transmission unit is in the non-shared mode is stored in the storage unit, the information only when the information specifying that the storage unit is not locked is stored in the storage unit. Is stored in the storage unit, and information that specifies that the lock is locked is stored in the storage unit. ,
The communication system according to appendix 5 or 7, wherein the emulator execution unit performs the notification to the communication device at the end of execution of the emulator.

[Appendix 12]
The communication system according to any one of appendices 4 to 11, wherein the communication device is the emulation target terminal itself.

[Appendix 13]
12. The communication system according to any one of appendices 4 to 11, wherein the communication device is a server device installed on a network.

[Appendix 14]
11. The communication system according to appendix 5, 7, 9 or 10, wherein the operation environment included in the information includes a telephone directory.

[Appendix 15]
In a communication system having a communication device and a user terminal that can communicate with each other through a network, a method for reproducing an operation environment of a terminal to be emulated by a user terminal,
When the use terminal having the input unit requests the communication device having a storage unit for storing the emulator for reproducing the operation environment of the emulation target terminal to download the emulator,
The communication device reads the emulator requested to be downloaded from the storage unit and transmits it to the user terminal,
An operation environment reproduction method, wherein the use terminal reproduces an operation environment of the emulation target terminal as an operation environment in the input unit by executing an emulator transmitted from the communication device.

DESCRIPTION OF SYMBOLS 1 Emulation object terminal 2 Temporary use terminal 3 Server 11 Emulator 12 Virtual machine environment state preservation file 21 Sandbox 30 Memory 31 Communication part 35 CPU
36 ROM
38 Key input device 39 LCD touch panel 51 Communication unit 55 CPU
56 ROM
58 Key input device 59 LCD touch panel 71 LAN adapter 72 Hard disk 73 CPU

Claims (5)

A communication terminal that communicates with other terminals via a network,
An input section;
A download unit that downloads an emulator that emulates the operating environment of the terminal being emulated;
A communication terminal comprising: an emulator execution unit that reproduces an operation environment of the emulation target terminal as an operation environment in the input unit by executing an emulator downloaded by the download unit. The download unit, together with the emulator, downloads information indicating the operating environment of the emulation target terminal individually,
The emulator execution unit reproduces an individual operation environment of the emulation target terminal by executing the emulator with reference to the information downloaded by the download unit. Communication terminal. A communication system having a communication device and a use terminal that can communicate with each other through a network,
The communication device
A storage unit for storing an emulator for reproducing the operation environment of the terminal to be emulated;
A transmitter that transmits the emulator to a user terminal that has requested download of the emulator;
The user terminal is
An input section;
A download unit for requesting the communication device to download an emulator that emulates the operating environment of the terminal to be emulated, and receiving the emulator transmitted in response to the request;
A communication system comprising: an emulator execution unit that reproduces an operation environment of the terminal to be emulated as an operation environment in the input unit by executing an emulator received by the download unit. The storage unit further stores a combination of terminal identification information and a password of any of the emulation target terminals,
The transmission unit requests downloading of the emulator only when the combination of the terminal identification information of the user terminal that requested the download of the emulator and the password notified by the user terminal is registered in the storage unit. The communication system according to claim 3, wherein the emulator is transmitted to the used terminal. In a communication system having a communication device and a user terminal that can communicate with each other through a network, a method for reproducing an operation environment of a terminal to be emulated by a user terminal,
When a user terminal having an input unit operated by a user requests a communication device having a storage unit for storing an emulator for reproducing the operation environment of the emulation target terminal, to download the emulator,
The communication device reads the emulator requested to be downloaded from the storage unit and transmits it to the user terminal,
An operation environment reproduction method, wherein the use terminal reproduces an operation environment of the emulation target terminal as an operation environment in the input unit by executing an emulator transmitted from the communication device.

Images