JP4361781B2 - Receiving apparatus and program - Google Patents

Description

  The present invention relates to a technique suitable for use in a receiving apparatus used jointly by a plurality of users.

  For example, a communication terminal constituting an in-house LAN can be used jointly by a plurality of employees by the employee logging in using an ID or password assigned to the employee.

  As described above, in a communication terminal shared by a plurality of users, only one application program used by each user is stored in the memory of the communication terminal. There is one prepared for each user, and when starting an application program, a user preference for a user who is currently using a communication terminal is read and the application program is executed using this user preference. (For example, refer to Patent Document 1).

Japanese Patent Laid-Open No. 11-328071

  By the way, in order to reduce the waste of memory capacity by storing only one program shared by a plurality of users in the communication terminal in this way, each user has already communicated with the program he / she wants to use. You can search for installed programs to see if they are installed on your device, or if your program is already installed, create your own user preferences for this program. It is not easy to use because it requires complicated operations.

  The present invention has been made in view of the above-described circumstances, and an object thereof is to improve convenience when a plurality of users use the same program in the receiving apparatus.

In order to solve the above problems, the present invention provides a receiving device in which receiving means, storage means, identification means for identifying a user who uses the receiving apparatus, and a program received by the receiving means are the same. A first determination unit that determines whether or not the program is permitted to be used by a plurality of users, and a program that is permitted to be used by a plurality of users by the first determination unit. In addition, it is determined that the program received by the receiving unit is stored in the storage unit by a second determination unit that determines whether or not the program is stored in the storage unit. in this case, without storing the program to be the received in the storage means, when it is judged as not being stored in the storage means, or the program is of the multiple users When used with is not permitted, the program which is the received and stored in the storage means, the user using the reception device by the identification by the identification means, for the user, the program When executing a setting unit that sets a storage area for storing data used in execution in the storage unit, and a program that is stored in the storage unit and that is permitted to be used by a plurality of users, Data stored in the storage area for the user identified by the identifying means among the storage areas set for each user by the setting means by identifying the user using the receiving device by the identifying means And a receiving device having an executing means for executing the program.

According to another aspect of the present invention, there is provided a first step of determining whether or not a program received by a receiving means included in the computer is a program permitted to be used by a plurality of users in the same receiving device. When it is determined in the first step that the program is permitted to be used by a plurality of users, it is determined whether or not the program received by the receiving unit is stored in a memory provided in the computer. If it is determined that the program is stored in the memory in the second step and the second step, the received program is not stored in the memory and is not stored in the memory. If it is determined, or if the program is not permitted for use by the plurality of users, the received program. Stores the grams in the memory, identifies the user using the computer, a third of setting for the user, a storage area for storing data used when executing the program in the memory And when executing a program stored in the memory and permitted to be used by a plurality of users, the user using the computer is identified, and each user is identified in the third step. A program for executing a fourth step of executing the program using data stored in the storage area for the identified user among the storage areas set for each is provided.

Further, the present invention provides storage means, joint use permission / inhibition information indicating whether or not the program is permitted to be used by a plurality of users in the same receiving device prior to receiving the program, and the reception A receiving unit that receives user information indicating a user permitted to use the program in the apparatus; and the joint use permission / rejection information received by the receiving unit permits use by a plurality of users. discriminating means for discriminating whether it is stored in the storage means, if it is determined that stored in said memory means by said discriminating means, without storing the program to be the received in the storage means If it is judged as not being stored in the storage means, or if the program is not allowed to be used by the plurality of users The program to be the received is stored in the storage means, for a user indicated by the user information received by the receiving means, said storage means a storage area for storing data used when executing the program Setting means for setting to, identification means for identifying a user who is using the receiving device when a program stored in the storage means and permitted to be used by a plurality of users is executed, And executing means for executing the program using the data stored in the storage area for the user identified by the identification means among the storage areas set for each user by the setting means. A receiving device is provided.

Further, the present invention provides a computer with whether or not to allow joint use to indicate whether or not the program is permitted to be used by a plurality of users in the same computer prior to reception of the program by the receiving means included in the computer. A first step of receiving information and user information indicating a user permitted to use the program in the computer, and the joint use permission information received in the first step permits use by a plurality of users A second step of determining whether or not the program is stored in a memory included in the computer, and a case where it is determined that the program is stored in the memory in the second step. discrimination and it does not store the program to be the received in the memory, not stored in the memory When, or if the program is not allowed to be used by the plurality of users, it stores the programs to be the reception in the memory, for a user indicated by the user information received by the receiving means A third step of setting in the memory a storage area for storing data used when the program is executed; and a program stored in the storage unit and permitted to be used by a plurality of users. A fourth step for identifying a user who uses the computer, and the fourth step among the storage areas set for each user in the third step. A program for executing the fifth step of executing the program using the data stored in the user storage area To provide.

  According to the present invention, only one program that is permitted to be used by a plurality of users is stored in the storage means even if it is used by a plurality of users in the receiving apparatus.

  ADVANTAGE OF THE INVENTION According to this invention, the convenience in case a some user uses the same program in a receiver can be improved.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In addition, the same code | symbol is attached | subjected to the common part in each figure.
[A-1. Configuration of Embodiment]
<1. Configuration of communication system>

  A communication system 1 according to an embodiment of the present invention is detachable from a content server 10, the Internet 20, a mobile packet communication network 30, a mobile phone 40, and a mobile phone 40, for example, as shown in FIG. And a UIM (User Identity Module) 50. The mobile packet communication network 30 can originally accommodate a large number of mobile phones 40. Further, different UIMs 50 can be replaced and attached to the mobile phone 40. However, in FIG. 1, only one mobile phone 40 and UIM 50 are shown in order to prevent the drawing from becoming complicated. For the same reason, only one content server 10, gateway server 31, and base station 32 are shown in FIG.

  The content server 10 has a function of performing packet communication with the mobile phone 40 via the Internet 20 and the mobile packet communication network 30. The content server 10 stores Java (registered trademark) application software (hereinafter referred to as “Java AP”) that can be executed by the mobile phone 40.

  The mobile packet communication network 30 includes a gateway server 31 and a base station 32. The gateway server 31 mutually converts data having different communication protocols such as a communication protocol for the mobile packet communication network 30 and a communication protocol for the Internet 20, and relays data exchange between the mobile packet communication network 30 and the Internet 20. . A large number of base stations 32 are installed in the communication service area of the mobile packet communication network 30 and perform radio communication with the mobile phone 40 located in the radio cell covered by the own station 32.

  The mobile phone 40 is a mobile device accommodated in the mobile packet communication network 30. The mobile phone 40 can perform packet communication with the content server 10 via the base station 32 that covers the wireless cell in which the mobile device 40 is located, and can download arbitrary content from the content server 10.

  The UIM 50 is a data storage module that is detachable from the mobile phone 40. The UIM 50 stores a telephone number assigned to the UIM 50 by a communication carrier operating the mobile packet communication network 30 and a mobile telephone network (not shown). This telephone number is subscription contract identification information for identifying a subscription contract of a packet communication service provided by the mobile packet communication network 30 or a call service provided by the mobile telephone network. Further, the UIM 50 stores a serial number (hereinafter referred to as “UIMID”) unique to each UIM 50, the credit card number of the owner of the UIM 50, a mail address, telephone directory data, and the like.

<2. JavaAP Configuration>
Next, JavaAP stored in the content server 10 will be described with reference to FIG. As shown in the figure, JavaAP is a JAR (Java Archive) file in which a JavaAP main program and image files and audio files used for executing the main program are combined into one, and the installation of this JAR file. And ADF (Application Descriptor File) in which various control information for controlling activation, network access, and the like are stored.

  The ADF stores a joint use permission flag indicating whether or not joint use by a plurality of users is permitted in the same mobile phone 40 for a JAR file paired with the ADF. The content provider sets the value of the joint use permission flag in the ADF to “0” or “1”, so that the JavaAP (JAR file) provided by the content provider is downloaded to the mobile phone 40 and then used jointly. You can set whether to accept or not.

  In this specification, when the value of the joint use permission flag is “1”, it indicates that the content provider permits joint use of this Java AP, and when the value of the joint use permission flag is “0”. Indicates that the content provider does not permit joint use of this Java AP. When the value of the joint use permission flag is “0”, users who can use this Java AP in the mobile phone 40 are limited to only users who have downloaded this Java AP from the content server 10.

  Further, in this specification, the JAR file and the ADF are collectively described as “JavaAP” unless it is particularly necessary to distinguish them. Further, in this specification, it is assumed that a JAR file and an ADF constituting one Java AP are stored in the same content server 10. However, the JAR file and the ADF may be stored in different servers.

<3. Configuration of mobile phone>
Next, for example, as shown in FIG. 3, the mobile phone 40 includes a wireless communication unit 401, an operation input unit 402, a call processing unit 403, a UIM interface 404, a CPU 405, a liquid crystal display unit 406, and a storage. These units are connected by a bus 411.

  The wireless communication unit 401 includes an antenna 401 a and controls wireless communication with the base station 32. Under the control of the CPU 405, the wireless communication unit 401 generates a transmission signal by superimposing data for packet communication, data related to transmitted voice, and the like on a carrier wave, and transmits this signal to the base station 32. The wireless communication unit 401 receives a wireless signal transmitted from the base station 32 via the antenna 401a, demodulates this signal, and transmits data for packet communication addressed to the own device 40, data related to received voice, and the like. obtain.

  The operation input unit 402 has a plurality of keys for inputting numbers, characters, operation instructions, and the like, and outputs operation signals corresponding to operations of these keys to the CPU 405. The call processing unit 403 includes, for example, a microphone, a speaker, a voice processing unit, and the like, and performs call processing including call connection and disconnection under the control of the CPU 405. The UIM interface 404 controls communication with the UIM 50 attached to the mobile phone 40 under the control of the CPU 405.

  The CPU 405 controls each unit connected via the bus 411 by executing various programs stored in the storage unit 407. The liquid crystal display unit 406 includes a liquid crystal display panel and a drive circuit that performs display control of the liquid crystal display panel.

  The storage unit 407 includes a ROM 408, a RAM 409, and a non-volatile memory 410 such as an SRAM (Static-RAM) or an EEPROM (Electrically Erasable Programmable-ROM). The ROM 408 stores a program that performs basic control of each part of the apparatus. The RAM 409 is used as a work area for the CPU 405.

  The nonvolatile memory 410 stores an operating system (hereinafter referred to as OS) for the mobile phone 40, a WWW (World Wide Web) browser, software for constructing a Java execution environment, and the like. The nonvolatile memory 410 stores various programs and data such as JavaAP downloaded from the content server 10, for example. In addition, the nonvolatile memory 410 has a UIMID storage area 410a, a JAR storage 410b, a scratch pad 410c, and a memory area specifying table 410d.

  The UIMID storage area 410a stores the UIMID of the UIM 50 currently mounted on the mobile phone 40. Here, the UIMD is sent from the UIM 50 to the mobile phone 40 via the UIM interface 404 when the UIM 50 is attached to the mobile phone 40, and is written into the UIMD storage area 410a by the CPU 405. When the UIM 50 is removed from the mobile phone 40, the UIM ID stored in the UIMID storage area 410a is deleted by the CPU 405.

  In the JAR storage 410b, as shown in FIG. 4, the JAR file is stored for each Java AP downloaded to the mobile phone 40. In the example shown in the figure, three JAR files “JAR file A”, “JAR file B”, and “JAR file C” are stored in the JAR storage 410b.

  As shown in FIG. 5, in the scratch pad 410c, for each JAR file stored in the JAR storage 410b, a JAR for permanently storing data used when the main program of the JAR file is executed. A file memory area is provided. Further, for the JAR file that is permitted to be shared by the content provider, a user memory area is provided in the JAR file memory area for each user who shares the JAR file.

  For example, in the figure, “JAR file A” and “JAR file C” are programs that are permitted to be used jointly by the content provider, and “JAR file A” is stored in the JAR file A memory area. For each of “user A”, “user B”, and “user C” who have shared the program, a memory area for each user (“memory area for user A”, “memory area for user B”, and “user B”) A user C memory area ") is provided.

  The data stored in the user memory area (or the JAR file memory area in the case of a JAR file that is not permitted to be shared) is set by the user if the JAR file is a game program, for example. And environment setting data such as data relating to the difficulty level and volume adjustment of the game, and save data to be saved when the game is finished halfway.

  As shown in FIG. 6, the memory area specifying table 410d includes, for each Java AP downloaded to the mobile phone 40, identification information of this Java AP, user identification information indicating a user who can use this Java AP, and this Memory address information indicating a user memory area (or JAR file memory area) in the scratch pad 410c allocated to the user is registered in association with each other. Of course, as shown in the figure, a plurality of user identification information and memory address information are registered for Java AP to be used jointly. In this embodiment, UIMID is used as user identification information, and a JAR file name is used as JavaAP identification information.

<4. Software execution environment on mobile phones>
FIG. 7 is a diagram for explaining a software execution environment in the mobile phone 40. In the figure, KVM (K Virtual Machine) is a JVM (Java Virtual Machine) redesigned for small electronic devices, and Java bytecode is converted into instruction code that can be interpreted / executed by the CPU 405 via the OS. It is software for conversion. In addition, API (Application Program Interface) is a software module for providing, for example, functions specified by CLDC (Connected Limited Device Configuration) and functions specialized for the mobile phone 40 to Java AP. JAM (Java Application Manager) is software for managing download / installation / activation / termination / deletion, etc. of JavaAP under the control of the OS.

  As shown in the figure, software for realizing the telephone directory function, browser function, and network communication function directly operates under the control of the OS.

[A-2. Operation of the embodiment]
<1. Download process>
FIG. 8 is a sequence chart illustrating the operations of the mobile phone 40 and the content server 10 when Java AP is downloaded. It should be noted that in the process related to downloading, each process performed by the mobile phone 40 after step S103 is a process executed by the CPU 405 according to JAM.

  First, the user attaches the UIM 50 owned by the user to the mobile phone 40 and operates the operation input unit 402 of the mobile phone 40 to start the WWW browser. Next, the user operates the operation input unit 402 to instruct connection to the content server 10. Thereby, a connection request message is transmitted from the mobile phone 40 to the content server 10 (step S101). Upon receiving the connection request message, the content server 10 performs authentication processing or the like of the mobile phone 40 as necessary, and then transmits site menu information to the mobile phone 40 (step S102). Further, when receiving the menu information, the mobile phone 40 displays an image based on the menu information on a liquid crystal display panel (hereinafter referred to as “liquid crystal screen”) of the liquid crystal display unit 407. Thereafter, information relating to menu selection and the like is transmitted and received between the mobile phone 40 and the content server 10.

  When the JavaAP to be downloaded is selected by the operation input in the mobile phone 40, the CPU 405 sends an ADF acquisition request message requesting that the ADF of the selected JavaAP is transmitted to the mobile phone 40 to the content server 10. Transmit (step S103). When the content server 10 receives the ADF acquisition request message, the content server 10 reads out the ADF specified by the ADF acquisition request message from the memory and transmits it to the mobile phone 40 (step S104).

  When receiving the ADF, the CPU 405 of the mobile phone 40 first checks the content of the ADF file and determines whether or not the JAR file paired with the ADF can be downloaded to the mobile phone 40 (step S105). Specifically, the CPU 405 reads the data of the “AppSize” item and the “SPsize” item from the ADF, and checks the free memory capacity of the JAR storage 410b and the scratch pad 410c. In the “AppSize” item, size information indicating the size of the JAR file scheduled to be downloaded (memory capacity necessary for storing the JAR file in the JAR storage 410b) is stored. In the “SPsize” item, size information indicating the size of a JAR file memory area (or a user memory area for one user) allocated in the scratch pad 410c for a JAR file scheduled to be downloaded is stored. Has been. When the free memory capacity of the JAR storage 410b or the scratch pad 410c is insufficient, the CPU 405 determines that the JAR file cannot be downloaded, displays a message to that effect on the liquid crystal screen, and stops the Java AP download.

  On the other hand, when it is determined that the JAR file can be downloaded (step S105: Yes), the CPU 405 then determines whether or not the value of the joint use permission flag included in the ADF is “1” (step S105). S106). As a result, if the CPU 405 determines that the value of the joint use permission flag is not “1”, that is, if the content provider does not permit joint use of JavaAP, the process proceeds to step S108. If the content provider does not specify whether or not the joint use of JavaAP is permitted and the joint use permission flag itself is not included in the ADF, the value of the joint use permission flag is not “1”. Therefore, the CPU 405 performs the same processing as when the value of the joint use permission flag is “0”.

  If the CPU 405 determines that the value of the joint use permission flag is “1” (step S106: Yes), that is, if the content provider permits joint use of this Java AP, then the above step is performed. It is determined whether or not the JAR file specified by the ADF downloaded in S104 is installed in the JAR storage 410b (step S107). As a result, if the CPU 405 determines that the corresponding JAR file is installed in the JAR storage 410b, the CPU 405 proceeds to step S111.

  As described above, when the determination result is Yes in both steps S106 and S107, that is, the JAR file to be downloaded is a program permitted to be used jointly, and this JAR file is installed in the JAR storage 410b. In such a case, it is only necessary to jointly use a JAR file that has already been installed, so it is not necessary to download the JAR file itself. Therefore, the CPU 405 does not download the JAR file and proceeds to step S111.

  When jointly using a JAR file already installed in this way, first, the CPU 405 creates a new user memory area in the corresponding JAR file memory area in the scratch pad 410c shown in FIG. Generate (step S111). Next, the CPU 405 obtains the UIMID stored in the UIMID storage area 410a, that is, the UIMID of the UIM 50 currently mounted on the mobile phone 40 (step S112). Note that the UIMID may be acquired directly from the UIM 50 currently mounted on the mobile phone 40. This UIMID is used as user identification information for identifying a user who is currently using the mobile phone 40.

  Then, in the memory area specifying table 410d shown in FIG. 6, the CPU 405 adds the memory address information indicating the user memory area generated in step S111 to the identification information of the Java AP to be jointly used, and the step S112. In step S113, the memory area specifying table 410d is updated by associating with the UIIM acquired in step S1.

  On the other hand, the CPU 405 determines in step S107 that the JAR file to be downloaded is not installed in the JAR storage 410b, or in step S106 that the value of the joint use permission flag is not “1”. Then, a JAR file acquisition request message is generated using a URL (Uniform Resource Locator) indicating a JAR file download request destination included in the ADF, and the JAR file acquisition request message is transmitted to the content server 10. (Step S108). Upon receiving the JAR file acquisition request message, the content server 10 reads the JAR file specified by the JAR file acquisition request message from the memory and transmits it to the mobile phone 40 (step S109).

  When receiving the JAR file, the CPU 405 of the mobile phone 40 first reads the size information of the “AppSize” item from the ADF received in step S104. The CPU 405 secures a memory area having a capacity specified by the read size information in the JAR storage 410b, and then installs the received JAR file in the memory area (step S110). Further, the CPU 405 reads the size information of the “SPsize” item from the ADF received in step S104, and secures a memory area for the installed JAR file in the scratch pad 410c according to the size information (step S111). Further, the CPU 405 stores the ADF received in step S104 in the nonvolatile memory 410 in association with the installed JAR file.

  Thereafter, the CPU 405 acquires the UIMID stored in the UIMID storage area 410a (step S112). Then, the CPU 405 associates the currently installed Java AP identification information, the memory address information indicating the JAR file memory area generated in step S111, and the UIID acquired in step S112 with the memory area specifying table 410d. And the memory area specifying table 410d is updated (step S113).

<2. JavaAP startup processing>
Next, FIG. 9 is a flowchart illustrating the operation of the Java AP activation process executed by the CPU 405 in the mobile phone 40. This Java AP activation process is executed by the CPU 405 as a JAM function. For example, it is executed when Java AP activation is instructed by an operation input.

  Note that the mode for instructing activation of JavaAP is not limited to operation input. For example, activation of JavaAP is instructed when JavaAP activation is instructed at a preset time, or processing performed according to another program. In some cases, activation of JavaAP is instructed from outside the mobile phone 40 using e-mail or the like. In addition, it is assumed that the user uses the mobile phone 40 with the UIM 50 owned by the user attached to the mobile phone 40.

  First, the CPU 405 obtains the UIMID stored in the UIMID storage area 410a in order to determine the user who is currently using the mobile phone 40 (step S201). Of course, you may acquire UIMID directly from UIM50 currently mounted in the mobile telephone 40 at present.

  Next, the CPU 405 determines whether or not the Java AP designated as the program to be activated is a program that is permitted to be shared by the content provider (step S202). That is, the CPU 405 reads out the Java AP ADF designated as the program to be activated from the nonvolatile memory 410 and determines whether or not the value of the joint use permission flag included in the ADF is “1”.

  As a result, if the CPU 405 determines that the Java AP designated as the program to be activated is a program permitted to be used jointly (step S202: Yes), first refer to the memory area specifying table 410d shown in FIG. Then, the memory address information associated with the combination of the Java AP identification information specified as the program to be activated and the UIIM acquired in step S201 is acquired (step S203). Next, the CPU 405 designates the user memory area indicated by the acquired memory address information as a memory area used when executing this Java AP (step S204).

  Thereafter, the CPU 405 reads and activates the main body program in the JAR file from the JAR storage 410b for the Java AP designated as the program to be activated (step S207), and performs processing based on the activated main body program in the above step S204. The process starts with the data stored in the user memory area designated in step (b).

  For example, the Java AP designated as the program to be activated is a game program, and environment setting data and save data for setting the difficulty level of the game designated by the user are stored in the user memory area in the scratch pad 410c. If it is, the CPU 405 first reads the environment setting data and the save data from the user memory area after starting the game program. Then, the CPU 405 sets the game difficulty level and the like based on the environment setting data, sets the game restart scene and the game character ability value according to the save data, and then restarts the game. In addition, when the game program is being executed or terminated, the CPU 405 appropriately uses or updates data stored in the corresponding user memory area.

  In step S203, the CPU 405 determines that there is no memory address information corresponding to the combination of the UIIM acquired in step S201 and the Java AP identification information specified as the program to be activated in the memory area specifying table 410d. If it is determined, for example, when a user who is not permitted to use jointly instructs activation of JavaAP, a message indicating that JavaAP cannot be activated because it corresponds to unauthorized use is displayed on the LCD screen. Cancel the start of.

  On the other hand, if the CPU 405 determines in step S202 that the Java AP designated as the program to be activated is not a program for which joint use is permitted, the process proceeds to step S205. Then, the CPU 405 acquires memory address information associated with the combination of the JavaAP identification information specified as the program to be activated and the UIID acquired in step S201 from the memory area specifying table 410d (step S205). ). Next, the CPU 405 designates the JAR file memory area designated by the acquired memory address information as a memory area used when executing this Java AP (step S206).

  Thereafter, the CPU 405 reads and activates the main body program in the JAR file from the JAR storage 410b for the Java AP designated as the program to be activated (step S207), and performs processing based on the activated main body program in the above step S206. The processing starts with the data stored in the memory area for the JAR file designated in step (1).

  As described above, according to the present embodiment, only one JAR file is installed in the mobile phone 40 for the Java AP that is allowed to be shared by the content provider. Can be reduced. Of course, when the user himself / herself searches the nonvolatile memory 410 to check whether or not the Java AP he / she wants to use is installed in the mobile phone 40, or when the Java AP he / she wants to use is already installed. Further, it is not necessary to perform complicated operations such as instructing the generation of the user memory area for the user in the scratch pad 410c. In addition, the content provider can set whether or not to permit joint use of the Java AP provided by the content provider.

  Note that the mobile phone 40 (computer) performs the download-related processing shown in FIG. 8 and the Java AP activation processing shown in FIG. 9 according to the program stored in the ROM 408 or the nonvolatile memory 410. A program for executing the processing according to the invention may be provided to the mobile phone 40 by communication. Alternatively, such a program may be provided by being recorded on a recording medium.

[B. Modified example]
As mentioned above, although embodiment of this invention was described, this invention can be implemented with another various form, without deviating from the main characteristic. The above-described embodiments are merely examples of one aspect of the present invention, and for example, the following modifications can be considered.

<Modification 1>
The download process shown in FIG. 8 may be modified like the sequence chart shown in FIG. In the sequence chart shown in FIG. 10, step numbers in the 300s are given only to parts different from the sequence chart shown in FIG. 8. Further, the description of the operation of the steps for performing the same processing as that in the sequence chart shown in FIG.

  In the mobile phone 40, when the Java AP to be downloaded is selected by the operation input, first, the CPU 405 obtains the UIMID stored in the UIMID storage area 410a (step S301). Next, the CPU 405 transmits an ADF acquisition request message for requesting transmission of the JavaAP ADF to be downloaded to the mobile phone 40 and the UIMID acquired in step S301 to the content server 10 (step S302).

  Upon receiving the ADF acquisition request message and UIMID, the content server 10 first reads out the ADF specified by the ADF acquisition request message from the memory. Next, the content server 10 stores the UIM ID received from the mobile phone 40 as user information indicating a user permitted in the mobile phone 40 to use the JAR file paired with the ADF in the read ADF (step S303). The ADF is transmitted to the mobile phone 40 (step S304). That is, in the ADF transmitted from the content server 10 to the mobile phone 40 in step S304, whether or not the JAR file paired with this ADF is a program that is allowed to be shared by a plurality of users in the mobile phone 40. And the user information (UIMID) indicating the user who is permitted to use the JAR file in the mobile phone 40 are stored.

  Thereafter, the processes from step S105 to S110 are the same as the processes of the sequence chart shown in FIG. Then, the CPU 405 of the mobile phone 40, when the JAR file specified by the ADF received in step 304 is a program permitted to be used jointly, and this JAR file is installed in the JAR storage 410b. In step S305, a user memory area (user memory area) indicated by the UIID included in the received ADF is generated in the scratch pad 410c.

  Then, in the memory area specifying table 410d, the CPU 405 adds the memory address information indicating the user memory area generated in step S305 and the ADF received in step S304 to the identification information of the Java AP to be shared. Are registered in association with each other and the memory area specifying table 410d is updated (step S306).

  On the other hand, if the JAR file designated by the ADF is a program that is not permitted to be used jointly, or the JAR file is a program that is permitted to be used jointly, the CPU 405 is installed in the JAR storage 410b. If not, a JAR file memory area is generated in the scratch pad 410c in step S305. The CPU 405 includes, in the memory area specifying table 410d, the currently installed Java AP identification information, the memory address information indicating the JAR file memory area generated in step S305, and the ADF received in step S304. Are registered in association with each other, and the memory area specifying table 410d is updated (step S306).

  As described above, the content server 10 may transmit the ADF including the user information indicating the user permitted to use the JAR file to the mobile phone 40 in addition to the joint use permission flag. The user information is not limited to UIMID. For example, as described in Modification 2 and Modification 3 described later, a telephone number, biometric information, or the like can be used.

  Further, when the content server 10 stores the UIMID in the ADF in the above step S303, control of parameters etc. used when executing the JAR file paired with the ADF customized for the user indicated by the UIIMD. Information may be further stored in the ADF.

  In this case, in step S306, the CPU 405 adds the memory address information indicating the user memory area generated in step S305 and the non-volatile memory 410 received in step S304 to the identification information of the Java AP to be jointly used. The information for identifying the ADF stored in (for example, memory address information indicating the storage location of the ADF, ID information uniquely assigned to each ADF, etc.) is associated with the UIIM included in the received ADF Are registered in the memory area specifying table 410d.

  When the CPU 405 starts such Java AP, in addition to the data stored in the user memory area specified with reference to the memory area specifying table 410d, the ADF specified with reference to the memory area specifying table 410d. Java AP is executed using the control information included in the file.

<Modification 2>
In the embodiment described above, the mobile phone 40 is configured to identify the user who uses the mobile phone 40 by the UIMID acquired from the UIM 50 attached to the mobile phone 40. However, a telephone number or an e-mail address stored in the UIM 50 may be used instead of the UIMID.

  The UIM 50 (data storage module) may be a non-contact type IC card that transmits / receives data to / from the mobile phone 40 by wireless communication. The data storage module may be a recording medium such as a memory card, an optical disk, or a magnetic disk that is detachable from the mobile phone 40. Of course, when such a recording medium is used, identification information unique to each recording medium or each owner of the recording medium is recorded in the recording medium, and the mobile phone 40 is attached to the mobile phone 40. The user using this mobile phone 40 is identified by the identification information acquired from the recording medium.

<Modification 3>
The present invention can also be applied to devices other than the mobile phone 40 that is used with the UIM 50 or a recording medium. FIG. 11 is a block diagram illustrating a hardware configuration of the mobile phone 41 according to this modification. The cellular phone 41 shown in the figure is different from the cellular phone 40 in the above-described embodiment in that a fingerprint analysis unit 421 is provided instead of the UIM interface 404. The fingerprint analysis unit 421 optically reads a fingerprint of a user who uses the mobile phone 41, and analyzes a fingerprint image read by the fingerprint reading unit to extract features of the fingerprint. And a fingerprint analysis unit for generating fingerprint information for uniquely identifying the user. The fingerprint information generated by the fingerprint analysis unit 421 may be used instead of UIMID to identify the user who is using the mobile phone 41. Further, instead of the fingerprint, biometric information such as a voice print, a retina pattern, and a palm print may be used.

<Modification 4>
In the above embodiment, according to the value of the joint use permission flag included in the ADF, the JAR file to be downloaded is a program for which joint use is permitted and has already been installed in the JAR storage 410b. In this case, the JAR file is not downloaded. However, after the JAR file is downloaded to 40, the JAR file is a program permitted to be used jointly and already installed in the JAR storage 410b. If this is the case, the JAR file may not be installed in the JAR storage 410b.

<Modification 5>
In the embodiment described above, the mobile phone 40 determines whether or not the JAR file specified by the ADF is a program permitted to be used jointly according to the value of the joint use permission flag described in the ADF. . However, for example, by providing each JAR file that is permitted to be used jointly from a specific server to the mobile phone 40, the mobile phone 40 provides a URL (communication) indicating a JAR file download request destination described in the ADF. Based on the address, it may be determined whether or not the JAR file is a program that is permitted to be shared.

<Modification 6>
In the above-described embodiment, the case where Java AP is downloaded to the mobile phone 40 has been described. Of course, the present invention can also be applied to a case where Java AP is distributed to the mobile phone 40 instead of downloading. Further, the receiving device to which the present invention is applicable is not limited to a mobile phone. For example, the present invention can be applied to various communication devices such as a PHS (Personal Handyphone System: registered trademark) terminal and a personal computer. The programming language is not limited to Java.

1 is a block diagram illustrating a configuration of a communication system according to an embodiment of the present invention. It is a figure which illustrates about the structure of JavaAP which concerns on the embodiment. 3 is a block diagram illustrating a hardware configuration of the mobile phone according to the embodiment. FIG. It is a figure which illustrates the structure of the JAR storage which concerns on the same embodiment. It is a figure which illustrates the composition of the scratch pad concerning the embodiment. It is a figure which illustrates the structure of the memory area specific table which concerns on the embodiment. FIG. 3 is a diagram for explaining an execution environment of software in the mobile phone according to the embodiment. 6 is a sequence chart illustrating operations of the mobile phone and the content server when downloading Java AP according to the embodiment. 4 is a flowchart illustrating an operation of Java AP activation processing executed by a CPU in the mobile phone according to the embodiment. FIG. 10 is a sequence chart according to a first modification of the present invention, and shows a modification of the process related to download shown in FIG. 8. It is a block diagram which illustrates the hardware constitutions of the mobile telephone which concerns on the modification 3 of this invention.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 ... Communication system, 10 ... Content server, 20 ... Internet, 30 ... Mobile packet communication network, 40, 41 ... Mobile phone, 50 ... UIM, 401 ... Wireless communication part, 402 ... Operation input part, 404 ... UIM interface, 405 ... CPU, 406 ... Liquid crystal display unit, 407 ... Storage unit, 410 ... Non-volatile memory, 410a ... UIID storage area, 410b ... JAR storage, 410c ... Scratch pad, 410d ... Memory area specifying table, 421 ... Fingerprint analysis unit.

Claims (6)

Receiving means;
Storage means;
Identifying means for identifying a user using the receiving device;
First determining means for determining whether or not the program received by the receiving means is a program permitted to be used by a plurality of users in the same receiving device;
A second determining unit configured to determine whether a program received by the receiving unit is stored in the storage unit when the first determining unit determines that the program is permitted to be used by a plurality of users; Discriminating means, and
If the if it is determined to have been stored in the storage unit by the second discriminating means, without storing the program to be the received in the storage means, is determined as not being stored in said storage means Or, when the program is not permitted to be used by the plurality of users, the received program is stored in the storage means, and the user using the receiving device is identified by the identification means. Setting means for setting a storage area for storing data used for executing the program for the user in the storage means;
When executing a program which is stored in the storage unit and permitted to be used by a plurality of users, the user who uses the receiving device is identified by the identifying unit, and the setting unit And a executing unit that executes the program using data stored in the storage area for the user identified by the identifying unit among the storage areas set in (1). Prior to receiving the program, the receiving means receives joint use permission information indicating whether the program is a program permitted to be used by a plurality of users in the same receiving device,
The first determining means determines whether the program received by the receiving means is a program permitted to be used by a plurality of users in the same receiving device in accordance with the joint use permission information received by the receiving means. The receiving apparatus according to claim 1, wherein: The receiving device can be equipped with a data storage module,
The identification means acquires identification information unique to each data storage module stored in the data storage module attached to the receiving device, and identifies a user who uses the receiving device by this identification information. The receiving device according to claim 1, wherein: Storage means;
Prior to receiving the program, joint use permission information indicating whether or not the program is a program permitted to be used by a plurality of users in the same receiving device, and a user who permits the use of the program in the receiving device Receiving means for receiving user information indicating:
A discriminating unit for discriminating whether or not the program is stored in the storage unit when the joint use permission / rejection information received by the receiving unit permits use by a plurality of users;
If the if it is determined to have been stored in the storage means by the judgment means, without storing the program to be the received in the storage means, is determined as not being stored in the storage means, or the When the program is not permitted to be used by the plurality of users, the received program is stored in the storage unit, and the program for the user indicated by the user information received by the receiving unit is executed. Setting means for setting a storage area for storing data used in the case of the storage means;
An identification unit for identifying a user who is using the receiving device when a program stored in the storage unit and permitted to be used by a plurality of users is executed;
And executing means for executing the program using data stored in the storage area for the user identified by the identifying means among the storage areas set for each user by the setting means. Receiving device. On the computer,
A first step of determining whether or not the program received by the receiving means included in the computer is a program permitted to be used by a plurality of users in the same receiving device;
When it is determined in the first step that the program is permitted to be used by a plurality of users, it is determined whether or not the program received by the receiving unit is stored in a memory provided in the computer. A second step;
If it is determined in the second step that the program is stored in the memory, the received program is not stored in the memory and it is determined that the program is not stored in the memory, or If the program is not allowed to be used by the plurality of users, the received program is stored in the memory, the user using the computer is identified, and the program for the user is A third step of setting in the memory a storage area for storing data used in execution;
When executing a program stored in the memory and permitted to be used by a plurality of users, the user using the computer is identified and set for each user in the third step. And a fourth step of executing the program using data stored in the storage area for the identified user among the storage areas. On the computer,
Prior to the reception of the program by the receiving means provided in the computer, joint use permission information indicating whether or not the program is a program permitted to be used by a plurality of users in the same computer; A first step of receiving user information indicating a user permitted to use;
A second step of determining whether or not the program is stored in a memory of the computer when the joint use permission information received in the first step permits use by a plurality of users; When,
If it is determined in the second step that the program is stored in the memory, the received program is not stored in the memory and it is determined that the program is not stored in the memory, or If the program is not permitted for use by the plurality of users, the received program is stored in the memory and the program for the user indicated by the user information received by the receiving means is executed. A third step of setting a storage area in the memory for storing data used in the case;
A fourth step of identifying a user using the computer when a program stored in the storage unit and permitted to be used by a plurality of users is executed;
Executing the program using the data stored in the storage area for the user identified in the fourth step among the storage areas set for each user in the third step; A program for executing steps and.

Images