US20040267783A1 - Information processing device and program - Google Patents

Information processing device and program Download PDF

Info

Publication number
US20040267783A1
US20040267783A1 US10/815,187 US81518704A US2004267783A1 US 20040267783 A1 US20040267783 A1 US 20040267783A1 US 81518704 A US81518704 A US 81518704A US 2004267783 A1 US2004267783 A1 US 2004267783A1
Authority
US
United States
Prior art keywords
contents
software
java
execution
cpu
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10/815,187
Other languages
English (en)
Inventor
Naoki Naruse
Yuichi Ichikawa
Tatsuro Oi
Nobuyuki Watanabe
Yasunori Hattori
Masato Takeshita
Masakazu Nishida
Mao Asai
Masayuki Tsuda
Atsuki Tomioka
Kazuhiro Yamada
Satoshi Washio
Dai Kamiya
Naoki Yamane
Keiichi Murakami
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NTT Docomo Inc
Original Assignee
NTT Docomo Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NTT Docomo Inc filed Critical NTT Docomo Inc
Assigned to NTT DOCOMO, INC. reassignment NTT DOCOMO, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ASAI, MAO, HATTORI, YASUNORI, ICHIKAWA, YUICHI, KAMIYA, DAI, MURAKAMI, KEIICHI, NARUSE, NAOKI, NISHIDA, MASAKAZU, OI, TATSURO, TAKESHITA, MASATO, TOMIOKA, ATSUKI, TSUDA, MASAYUKI, WASHIO, SATOSHI, WATANABE, NOBUYUKI, YAMADA, KAZUHIRO, YAMANE, NAOKI
Publication of US20040267783A1 publication Critical patent/US20040267783A1/en
Priority to US12/049,060 priority Critical patent/US7899973B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/106—Enforcing content protection by specific content processing
    • G06F21/1063—Personalisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2135—Metering
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F2221/2149—Restricted operating environment

Definitions

  • the present invention relates to a technique regarding use of contents.
  • contents having same functions are always delivered regardless of differences in the intended purposes of using the contents.
  • a user may not be able to try out contents freely as shown by the following example.
  • a user tries out contents having a function of acquiring information specific to a communication device of the user such as personal information of the user
  • a message is displayed for gaining permission from the user to acquire information specific to the communication device, in view of privacy and security of the user.
  • the user needs to carry out an operation for accepting the contents of the message, when or before trying out the contents.
  • trial use of contents by the user is interrupted temporarily; therefore, the user may not be able to freely try out the contents.
  • Japanese Patent Application Laid-Open Publication No. 11-134155 discloses a technique for using application software whose usable functions are changed in accordance with the frequency of usage.
  • software disclosed in the publication includes a program for displaying an operation screen, and counts and stores frequency of usage for each function displayed on the operation screen. Each time the frequency of usage of a function exceeds a predetermined frequency, the software displays new contents on the operation screen additionally which are pre-stored in the software and have not been displayed, thereby renewing operational functions of the software.
  • the present invention has been made in view of the problems stated above, and provides an information processing device which estimates usage of contents, and in accordance with the estimated usage, properly limits the functions realized through use of the contents.
  • the present invention provides an information processing device having cache memory means, acquiring means for acquiring contents which realize a function through processing or execution, first writing means for writing contents acquired by the acquiring means in a free space or a space, where some data is already stored, of the cache memory means, and content storage means for storing contents
  • the information processing device comprising: estimating means, when instructed to process or execute contents, for estimating whether the contents are for trial use, by determining in which of the cache memory means and the content storage means the contents are stored; content using means for reading contents instructed to be processed or executed from the cache memory means or the content storage means, and processing or executing the contents; determining means, when contents are processed or executed by the content using means, for determining whether to limit functions realized through processing or execution of the contents, on the basis of an estimation of the estimating means and function limit information showing a rule regarding limits on functions realized through processing or execution by the content using means; and limiting means for limiting functions realized through processing or execution by the content using means on the basis of a
  • the determining means may determine to limit the functions of the contents; and when the estimating means estimates that the contents are not for trial use, the determining means may determine to disobey the function limit information.
  • the information processing device may further comprise operation means; deleting means, when a command is issued using the operation means for deleting contents stored in the content storage means, for freeing a storage space for storing the contents; and second writing means for writing contents acquired by the acquiring means in a free space or a storage space freed by the deleting means, and the acquiring means may acquire the contents via communication.
  • the present invention provides a program product for causing a computer having cache memory means, acquiring means for acquiring contents which realize a function through processing or execution, first writing means for writing contents acquired by the acquiring means in a free space or a space, where some data is already stored, of the cache memory means, and content storage means for storing contents, to execute: a process, when an instruction to process or execute contents are provided, of estimating whether the contents are for trial use, by determining in which of the cache memory means and the content storage means the contents are stored; a process of reading contents instructed to be processed or executed from the cache memory means or the content storage means, and processing or executing the contents; a process, when contents are processed or executed by the content using means, of determining whether to limit functions realized through processing or execution of the contents, on the basis of an estimation of the estimating means and function limit information showing a rule regarding limits on functions realized through processing or execution by the content using means; and a process of limiting functions realized through processing or execution by the content using means on the basis of a determination
  • usage of contents is estimated by determining in which of cache memory means and content storage means the contents are stored.
  • it is determined whether to limit functions realized through processing or execution of the contents on the basis of the estimated usage of the contents and function limit information showing a rule regarding limits on functions realized through processing or execution.
  • the functions realized through processing or execution of the contents are limited.
  • the present invention makes it possible to estimate usage of contents and properly limit functions realized through use of the contents in accordance with the estimation.
  • FIG. 1 is a block diagram showing an example of the configuration of communication system 1 according to an embodiment of the present invention.
  • FIG. 2 is a diagram showing an example of a list page displayed in liquid crystal display unit 405 of mobile phone 40 according to the embodiment.
  • FIG. 3 is a diagram showing the contents of an explanatory file according to the embodiment.
  • FIG. 4 is a diagram showing an example of an explanatory page displayed in liquid crystal display unit 405 of mobile phone 40 according to the embodiment.
  • FIG. 5 is a diagram showing an example of the data configuration of an ADF according to the embodiment.
  • FIG. 6 is a block diagram showing an example of the hardware configuration of mobile phone 40 according to the embodiment.
  • FIG. 7 is a conceptual diagram showing the contents of function limit information according to the embodiment.
  • FIG. 8 is a block diagram showing an example of the Java Runtime Environment according to the embodiment.
  • FIG. 9 is a flowchart illustrating an execution process performed by CPU 400 of mobile phone 40 according to the embodiment.
  • FIG. 10 is a flowchart illustrating a storage process performed by CPU 400 of mobile phone 40 according to the embodiment.
  • FIG. 1 is a block diagram showing the configuration of communication system 1 according to the embodiment.
  • Mobile packet communication network 30 is a communication network for providing mobile packet communication services to mobile phone 40 served by mobile packet communication network 30 .
  • Mobile packet communication network 30 comprises gateway server 31 and base station 32 .
  • Many base stations 32 are provided in a communication service area of mobile packet communication network 30 .
  • Mobile phone 40 when located in a radio cell covered by base station 32 , can perform radio communication with base station 32 .
  • Gateway server 31 relays data between mobile packet communication network 30 and Internet 20 .
  • Mobile phone 40 and content server 10 perform HTTP (Hyper Text Transfer Protocol) communication via Internet 20 and mobile packet communication network 30 .
  • HTTP Hyper Text Transfer Protocol
  • Java AP software is software for enabling an application to be executed, and comprises a Java Archive (JAR) file containing a program written in the Java programming language and an Application Descriptor File (ADF) where information on the JAR file is described.
  • JAR Java Archive
  • ADF Application Descriptor File
  • Java AP software is treated as contents.
  • Content server 10 also stores an explanatory file associated with Java AP software stored therein.
  • the contents of an explanatory file are shown in FIG. 3.
  • ilet property is specified in an anchor tag (tag beginning with “ ⁇ A”).
  • an object tag (tag beginning with “ ⁇ OBJECT”) is specified whose id property includes the value specified as the ilet property in the anchor tag.
  • a URL http://WWW.CCC.cojp/cardgame/jam) specified as the data property of the object tag indicates a location for storing an ADF constituting Java AP software.
  • the explanatory file is written so as to provide the explanatory page shown in FIG. 4 when interpreted and executed by mobile phone 40 .
  • Content server 10 also performs a function of sending Java AP software to mobile phone 40 .
  • Content server 10 upon receiving from mobile phone 40 an HTTP request message requesting Java AP software, reads an ADF constituting the Java AP software.
  • Content server 10 then generates an HTTP response message including the read ADF, and sends it to mobile phone 40 .
  • Content sever 10 upon receiving from mobile phone 40 an HTTP request message requesting the JAR file corresponding to the ADF, reads the JAR file.
  • Content server 10 then generates an HTTP response message including the read JAR file, and sends it to mobile phone 40 .
  • CPU 400 controls components of mobile phone 40 by executing a variety of programs stored in storage unit 406 .
  • Storage unit 406 comprises Read Only Memory (ROM) 407 , Random Access Memory (RAM) 408 , and nonvolatile memory 409 such as an Electrically Erasable Programmable ROM (EEPROM).
  • ROM Read Only Memory
  • RAM Random Access Memory
  • EEPROM Electrically Erasable Programmable ROM
  • ROM 407 stores programs such as an operating system for mobile phone 40 , World Wide Web (WWW) browser software executed for downloading Java AP software, and software for establishing the runtime environment of Java AP software described later.
  • WWW World Wide Web
  • Nonvolatile memory 409 stores Java AP software, a variety of programs, and a variety of data.
  • Nonvolatile memory 409 comprises cache area 409 a for storing Java AP software temporarily and storage area 409 b for storing Java AP software enduringly.
  • Cache area 409 a has areas to which memory addresses “adrs0001” to “adrs5000” are assigned.
  • Storage area 409 b has areas to which memory addresses “adrs5001” to “adrs100000” are assigned.
  • Nonvolatile memory 409 stores a memory management table (not shown) for managing address information of cache area 409 a and storage area 409 b .
  • the memory management table stores address information indicating correspondence between Java AP software and the memory address of the area storing the software. Address information is written in the memory management table when storage of Java AP software is instructed by CPU 400 . Address information written in the memory management table is referred to when CPU 400 reads Java AP software.
  • Cache area 409 a stores Java AP software downloaded from content server 10 for trial use in mobile phone 40 .
  • Java AP software stored in cache area 409 a upon exiting a program executed by CPU 400 for downloading the software, is deleted by CPU 400 from cache area 409 a . It should be noted that deletion of Java AP software specifically means that a memory area for storing the software is cleared; therefore it becomes impossible to read the software, and the memory area becomes available for storing new data.
  • Storage area 409 b stores Java AP software downloaded from content server 10 , storage of which in mobile phone 40 is instructed by a user. Java AP software stored in storage area 409 b , unless a user of mobile phone 40 directs deletion of the software, remains stored in storage area 409 b.
  • Nonvolatile memory 409 also stores function limit table T1 for storing function limit information.
  • the function limit information shows methods described later, calls of which are disabled during runtime of Java AP software stored in cache area 409 a .
  • the contents of function limit information are shown in FIG. 7 conceptually. In the function limit information of the FIG. 7, calls of the methods “GetSysInfo( )”, “GetUTN( )”, “AccessUserInfo( )”, and “LaunchAPP( )” are disabled.
  • Function limit table T1 is used when CPU 400 realizes a limit function which will be described later.
  • Java Runtime Environment [0048]
  • FIG. 8 is a diagram showing the runtime environment of Java AP software stored in mobile phone 40 .
  • mobile phone 40 comprises the K Virtual Machine (KVM); the Connected Limited Device Configuration (CLDC) as a configuration; and native application interfaces.
  • KVM K Virtual Machine
  • CLDC Connected Limited Device Configuration
  • the CLDC class library is a class library for the CLDC, and stores classes.
  • a class includes methods such as “GetUTN( )”, “AccessUserinfo( )”, “LaunchApp( )”, and “GetSysinfo( )”.
  • a method is called by CPU 400 through an application program interface (API). As a result, the function of the method is realized.
  • API application program interface
  • Mobile phone 40 by calling “GetUTN( )”, realizes a function of acquiring serial number information of mobile phone 40 stored therein.
  • Mobile phone 40 by calling “AccessUserInfo( )”, realizes a function of referring to data on a user of mobile phone 40 stored therein.
  • Mobile phone 40 by calling “LaunchApp( )”, realizes a function of launching other applications.
  • Mobile phone 40 calling “GetSysInfo( )”, realizes a function of acquiring reception status information of e-mails and messages addresses to mobile phone 40 .
  • Java Application Manager is software for enabling CPU 400 to manage Java AP software stored in mobile phone 40 under the control of an operating system.
  • CPU 400 realizes the following functions.
  • CPU 400 realizes the functions of displaying a list of Java AP software stored in storage area 409 b , managing execution (a start or forced termination, etc.) of Java AP software, storing or modifying Java AP software, deleting Java AP software stored in mobile phone 40 , and monitoring the status of Java AP software.
  • CPU 400 when executing Java AP software, also determines whether the software is stored in cache area 409 a to estimate usage of the Java AP software.
  • CPU 400 determines that the Java AP software is stored in cache area 409 a
  • CPU 400 realizes a limit function of limiting calls of methods from the software.
  • function limit information stored in function information table T1 is referred to.
  • CPU 400 also realizes a function, when an HTTP communication is established during Java AP software runtime, of suspending the running software.
  • CPU 400 when instructed by a user to store Java AP software, which is read from cache area 409 a and executed by CPU 400 , determines whether an ADF constituting the software contains at least one of “GetUTN”, “AccessUserInfo”, “LaunchApp”, and “GetSysInfo”. When it is determined that at least one of them is contained in the ADF, CPU 400 causes liquid crystal display unit 405 to display a message saying, “This software may use information specific to this mobile phone. Do you want to proceed with this storage process?”. When the user selects a “Yes” in response to the message, CPU 400 determines whether the ADF contains “useNetwork”.
  • CPU 400 When it is determined that “useNetwork” is contained in the ADF, CPU 400 causes liquid crystal display unit 405 to display a message saying “This software may access a network. Please select from: (a) permitting an access to a network, (b) not permitting an access to a network, or (c) confirming whether to permit an access to a network at each execution of the software”. In accordance with an instruction from the user, CPU 400 sets a value as data corresponding to “useNetwork” of the ADF, and stores the Java AP software in storage area 409 b.
  • An ADF is a text file where a variety of control information are written for controlling storage, a start, and network access, etc. of a JAR file.
  • the data configuration of an ADF is shown in FIG. 5.
  • Items Name column of FIG. 5
  • names of control information are listed.
  • Essential/Option column
  • information are listed which indicate whether essential or optional for an ADF.
  • Data information on control information are listed.
  • AppName is control information indicating the name of Java AP software, and information indicating the name is shown in the “Data” column of “AppName”.
  • PackageURL is control information indicating the Uniform Resource Locator (URL) of a location accessed for downloading a JAR file, and the URL of a location accessed for downloading a JAR file is shown in the “Data” column of “PackageURL”.
  • AppSize is control information indicating the data size of a JAR file, and data size is shown in the “Data” column of “AppSize”.
  • “GetUTN” is control information designating whether CPU 400 , during Java AP software runtime, acquires serial number information of mobile phone 40 stored therein.
  • CPU 400 acquires serial number information of mobile phone 40 by calling “GetUTNO”.
  • CPU 400 does not call “GetUTNO”; therefore, does not acquire serial number information of mobile terminal 40 .
  • AccessUserInfo is control information designating whether CPU 400 , during Java AP software runtime, refers to data on a user of mobile phone 40 stored therein.
  • CPU 400 refers to data on a user of mobile phone 40 by calling “AccessUserInfo( )”.
  • CPU 400 does not call “AccessUserInfo( )”; therefore, does not refer to data on a user of mobile phone 40 .
  • “LaunchApp” is control information designating whether CPU 400 , during Java AP software runtime, can launch other Java AP software.
  • CPU 400 calls “LaunchApp( )”; therefore, Java AP software can launch other Java AP software by calling.
  • “LaunchApp” is not contained in an ADF, CPU 400 does not call “LaunchApp( )”; therefore, Java AP software cannot launch other Java AP software.
  • “GetSysInfo” is control information designating whether CPU 400 , during Java AP software runtime, acquires reception status information of e-mails and messages addressed to mobile phone 40 .
  • CPU 400 acquires reception status information by calling “GetSysInfo( )”.
  • CPU 400 does not call “GetSysInfo( )”; therefore, does not acquire reception status information.
  • “UseNetwork” is control information indicating that CPU 400 , during Java AP software runtime, may communicate with mobile packet communication network 30 , and designating whether a user can select from: (a) permitting an access to a network, (b) not permitting an access to a network, or (c) confirming whether to permit an access to a network at each execution of the software.
  • “UseNetwork” is contained in an ADF, a user can make the above setting.
  • “UseNetwork” is not contained in an ADF, a user cannot make the setting.
  • control information as stated above is set by content providers providing Java AP software.
  • FIG. 9 is a flowchart illustrating an execution process performed by CPU 400 of mobile phone 40 .
  • CPU 400 executes the WWW browser.
  • CPU 400 performs operations in accordance with instructions from the WWW browser, as described below.
  • a user directs an access to content server 10 by inputting the URL of content server 10
  • CPU 400 starts to communicate with content server 10 .
  • a list file (not shown) is received from content server 10
  • CPU 400 interprets and executes the list file, and causes liquid crystal display unit 405 to display the list page as shown in FIG. 2.
  • the list page of FIG. 2 lists names of Java AP software.
  • CPU 400 When the user clicks button BT 1 on the list page indicating the name of desired Java AP software using operation input unit 402 (in this operation example, it is assumed that “Card Game” is clicked), CPU 400 detects the click of button BT 1 , and requests content server 10 to send the explanatory file as shown in FIG. 3 corresponding to the Java AP software. When the explanatory file is received from content server 10 , CPU 400 interprets and executes the explanatory file, and causes liquid crystal display unit 405 to display the explanatory page as shown in FIG. 4.
  • CPU 400 detects the click of button BT 2 (Step S 10 ), and identifies the anchor tag described in the explanatory file corresponding to button BT 2 , the value data specified as the ilet property is specified as id property of which, and extracts the URL specified as data property of the object tag.
  • CPU then sends an HTTP request message requesting the ADF specified by the URL to content server 10 via mobile packet communication network 30 and Internet 20 (Step S 11 ).
  • Content server 10 upon receiving the HTTP request message, reads the ADF requested by the message. Content server 10 generates an HTTP response message including the read ADF, and sends it to mobile phone 40 .
  • CPU 400 of mobile phone 40 upon receiving the HTTP response message (Step S 12 ), stores the ADF in cache area 409 a (Step S 13 ).
  • CPU selects, in accordance with a predetermined rule, an area for storing the ADF from among areas of nonvolatile memory 409 to which memory addresses “adrs0001” to “adrs5000” are assigned, and stores the ADF in the area.
  • CPU 400 then writes address information identifying the area in a memory management table in association with the ADF.
  • CPU 400 extracts the PackageURL of the ADF; generates an HTTP request message requesting the JAR file specified by the PackageURL; and sends it to content server 10 (Step S 14 ).
  • Content server 10 upon receiving the HTTP request message, generates an HTTP response message including the JAR file requested by the request message, and sends it to mobile phone 40 .
  • CPU 400 of mobile phone 40 upon receiving the HTTP response message (Step S 15 ), stores the JAR file included in the message in cache area 409 a temporarily (Step S 116 ).
  • CPU 400 reads the Java AP software with reference to the memory management table, and executes the software (Step S 17 ).
  • CPU 400 monitors the status of the software in accordance with instructions from the JAM.
  • CPU 400 calls a method on the basis of information of the ADF constituting the Java AP software
  • CPU 400 refers to function limit table T1 in accordance with instructions from the JAM, and determines whether to call the method on the basis of information of function limit table T1. For example, when the ADF constituting the Java AP software contains “GetUTN”, CPU 400 , during the software runtime, acquires serial number information of mobile phone 40 by calling “GetUTN( )”.
  • CPU 400 when calling “GetUTN( )”, refers to function limit table T1 in accordance with instructions from the JAM, and function limit table T1 indicates that a call of the method is disabled, CPU 400 does not call the method in accordance with instructions from the JAM. As a result, CPU 400 cannot realize the function of acquiring serial number information of mobile phone 40 . CPU 400 then causes liquid crystal display unit 405 to display a message saying “This function cannot be used”.
  • CPU 400 when calls of them are disabled in function limit table T1, CPU 400 does not call them in accordance with instructions from the JAM. Also, CPU 400 , when an HTTP communication is established during Java AP software runtime, suspends the running software in accordance with instructions from the JAM.
  • Step 17 when the user directs termination of the running Java AP software using operation input unit 402 of mobile phone 40 , CPU 400 terminates the running software.
  • CPU 400 then performs the storage process as described below.
  • the storage process is illustrated in the flowchart of FIG. 10.
  • CPU 400 causes liquid crystal display unit 405 to display a message saying “Do you want to store this application?”.
  • CPU 400 detects the operation (Step S 30 ); refers to the ADF of the software; and determines whether the ADF contains at least one of “GetUTN”, “AccessUserInfo”, “LaunchApp”, and “GetSysInfo” (Step S 31 ). When it is determined that the ADF contains at lease one of them, CPU 400 causes liquid crystal display unit 405 to display a message saying “This software may use information specific to this mobile phone. Do you want to proceed with this storage process?” (Step S 32 ).
  • Step S 31 The reason for the determination in Step S 31 is as follows: In a case where Java AP software is stored in cache area 409 a , read from cache area 409 a , and executed, calls of “GetUTN( )”, “AccessUserInfo( )”, “LaunchApp( )”, and “GetSysInfo( )” as shown in function limit table T1 are disabled. As a result, information specific to mobile phone 40 is not acquired during the Java AP software runtime.
  • CPU 400 detects the operation (Step S 33 ), and determines whether the ADF contains “useNetwork” (Step S 34 ). When it is determined that “useNetwork” is contained in the ADF, CPU 400 causes liquid crystal display unit 405 to display a message saying “This software may access a network. Please select from: (a) permitting an access to a network, (b) not permitting an access to a network, or (c) confirming whether to permit an access to a network at each execution of the software”. When the user permits an access to a network, CPU 400 sets a value “1” as data corresponding to “useNetwork” of the ADF.
  • CPU 400 sets a value “0” as the data.
  • CPU 400 sets a value “2” as the data (Step S 35 ).
  • Step S 34 The reason for the determination in Step S 34 is as follows: In a case where Java AP software is stored in cache area 409 a , read from cache area 409 a , and executed, when an HTTP communication is established during the software runtime, the running software is suspended. As a result, during the Java AP software runtime, CPU 400 does not communicate with mobile packet communication network 30 . On the other hand, in a case where the Java AP software is stored in storage area 409 b , read from storage area 409 b , and executed, CPU 400 is not disabled to communicate with mobile packet communication network 30 during the software runtime. Thus, when the ADF constituting the Java AP software contains “useNetwork”, CPU 400 may communicate with mobile packet communication network 30 during the software runtime. The access to the network is concerned with privacy and security; therefore, needs to be approved by a user.
  • CPU 400 stores the Java AP software in storage area 409 b (Step S 36 ), and writes address information associated with the software in the memory management table.
  • CPU 400 terminates the WWW browser.
  • CPU 400 deletes the Java AP software stored in cache area 409 a , and deletes from the memory management table the address information of cache area 409 a associated with the software.
  • CPU 400 detects the operation (Step S 37 ), and reads the software from storage area 409 b and executes it (Step S 38 ).
  • CPU 400 monitors the status of the Java AP software in accordance with instructions from the JAM.
  • CPU 400 calls a method on the basis of information described in the ADF constituting the Java AP software, unlike the execution process described above, CPU 400 does not refer to function limit table T1, and can call the method through an API. As a result, CPU 400 realizes the function of the method by calling the method.
  • Java AP software written in the Java programming language is treated as contents.
  • a programming language is not limited to the Java programming language, and may be the C++ language, etc.
  • Contents may be image data, video data, music data, or document data such as HTML data, instead of software.
  • mobile phone 40 is configured to comprise a program and a unit for processing image data, video data, or music data, or a program for interpreting and displaying document data in liquid crystal display unit 405 .
  • the processing program is configured to have a function, when processing image data, video data, or music data stored in cache area 409 a , of limiting functions realized by processing those data (for example, colors of a processed image or tones of a processed music are limited).
  • the display program is configured to have a function, when interpreting and displaying document data stored in cache area 409 a , of limiting functions realized by interpreting and displaying the data (for example, colors or sizes of a displayed character are limited).
  • Java AP software is downloaded from content server 10 to mobile phone 40 ; however, Java AP software may be delivered from content server 10 to mobile phone 40 .
  • Java AP software stored in cache area 409 a may be reused as described below.
  • CPU 400 of mobile phone 40 detects the click, and determines whether the Java AP software associated with button BT 2 is stored in cache area 409 a . Only when it is determined that the Java AP software is not stored in cache area 409 a , CPU 400 directs download of the software from content server 10 . On the other hand, when it is determined that the Java AP software is stored in cache area 409 a , CPU 400 reads the software from cache area 409 a , and carries out the same process as the execution process of FIG. 9.
  • CPU 400 of mobile phone 40 when terminating a running WWW browser, deletes Java AP software stored in cache area 409 a .
  • CPU 400 may delete Java AP software in the order of ascending priorities, when the total data amount of Java AP software stored in cache area 409 a reaches the capacity of cache area 409 a .
  • the order of ascending priorities is the order in which Java AP software is downloaded.
  • a computer without a communication function may be used as an information processing device, instead of a mobile phone with a communication function.
  • Java AP software is pre-stored in cache area 409 of the computer.
  • the software can be stored in only cache area 409 of the computer.
  • Java AP software stored therein is deleted in the order of ascending priorities.
  • Java AP software stored in cache area 409 a can be stored in storage area 409 b in accordance with an instruction from a user. The copying or moving of Java AP software stored in storage area 409 is restricted.
  • a computer without a communication function can limit functions of Java AP software stored in cache area 409 a.
  • nonvolatile memory 409 of mobile phone 40 cache area 409 a and storage area 409 b may not be assigned.
  • CPU 400 when storing in nonvolatile memory 409 Java AP software downloaded from content server 10 , associates with the software storage identification data (for example, a memory flag “0”) indicating that the software is stored temporarily.
  • the software storage identification data for example, a memory flag “0”
  • the software is not deleted from nonvolatile memory 409 , but the storage identification data corresponding to the software is modified to storage identification data indicating that the software is stored enduringly (for example, the memory flag is modified from “0” to “1”).
  • the software associated with the memory flag “0” is deleted from nonvolatile memory 409 .
  • function limit table T1 is pre-stored in nonvolatile memory 409 .
  • function limit information in a JAR file stored in content server 10 , and, when the JAR file is executed, to limit calls of methods in accordance with the function limit information included in the JAR file.
  • Function limit information is not limited to those stated in the embodiment, may be those, for example, for limiting a call of a method for using a scratchpad or a method for using a version upgrade method.
  • Software such as JAM software or operating system software executed by CPU 400 of mobile phone 40 in the above embodiment can be provided to mobile phone 40 through a CPU 400 readable storage medium storing the software such as a magnetic recording medium, a magneto-optical recording medium, or ROM.
  • the software also can be downloaded to mobile phone 40 via a network such as the Internet.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Technology Law (AREA)
  • Multimedia (AREA)
  • Computer Hardware Design (AREA)
  • Information Transfer Between Computers (AREA)
  • Stored Programmes (AREA)
  • Devices For Executing Special Programs (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Hardware Redundancy (AREA)
  • Storage Device Security (AREA)
  • Telephone Function (AREA)
US10/815,187 2003-03-31 2004-03-31 Information processing device and program Abandoned US20040267783A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/049,060 US7899973B2 (en) 2003-03-31 2008-03-14 Information processing device and program

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2003-097144 2003-03-31
JP2003097144A JP3923921B2 (ja) 2003-03-31 2003-03-31 情報処理装置及びプログラム

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/049,060 Division US7899973B2 (en) 2003-03-31 2008-03-14 Information processing device and program

Publications (1)

Publication Number Publication Date
US20040267783A1 true US20040267783A1 (en) 2004-12-30

Family

ID=32844659

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/815,187 Abandoned US20040267783A1 (en) 2003-03-31 2004-03-31 Information processing device and program
US12/049,060 Expired - Fee Related US7899973B2 (en) 2003-03-31 2008-03-14 Information processing device and program

Family Applications After (1)

Application Number Title Priority Date Filing Date
US12/049,060 Expired - Fee Related US7899973B2 (en) 2003-03-31 2008-03-14 Information processing device and program

Country Status (8)

Country Link
US (2) US20040267783A1 (de)
EP (1) EP1465042B1 (de)
JP (1) JP3923921B2 (de)
CN (1) CN1245051C (de)
AT (1) ATE302442T1 (de)
DE (1) DE602004000056T2 (de)
ES (1) ES2243914T3 (de)
TW (1) TWI244591B (de)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070204102A1 (en) * 2006-02-28 2007-08-30 Nokia Corporation Cache feature in electronic devices
US20080052368A1 (en) * 2006-08-28 2008-02-28 Sony Ericsson Mobile Communications Ab System and method to shuffle and refill content
US20160359921A1 (en) * 2012-12-20 2016-12-08 Intel Corporation Secure local web application data manager
US10430502B2 (en) 2012-08-28 2019-10-01 Sweetlabs, Inc. Systems and methods for hosted applications
US11256491B2 (en) 2010-06-18 2022-02-22 Sweetlabs, Inc. System and methods for integration of an application runtime environment into a user computing environment

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100571179C (zh) * 2006-05-12 2009-12-16 佳能株式会社 信息处理设备和网络管理方法
JP4913623B2 (ja) * 2007-02-20 2012-04-11 株式会社エヌ・ティ・ティ・ドコモ 端末装置およびプログラム
US20090253414A1 (en) * 2008-04-03 2009-10-08 Cequint, Inc. Systems and methods for deployment and sale of advanced calling features
CN103377067B (zh) * 2012-04-13 2019-01-25 富泰华工业（深圳）有限公司 应用程序加载系统及方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010049641A1 (en) * 2000-06-05 2001-12-06 Shunsuke Nakamura Sound data delivering system, sound data delivery method, delivering server utilized in the sound data delivering system, client-side terminal utilized in the sound data delivering system, and computer-readable recording medium containing a program applied to a computer utilized in the sound data delivering system
US20020184520A1 (en) * 2001-05-30 2002-12-05 Bush William R. Method and apparatus for a secure virtual machine
US20040078636A1 (en) * 2002-03-20 2004-04-22 National Inst. Of Advanced Ind. Science And Tech. Input and output control means for computer system storage and a software execution method using same
US6735768B1 (en) * 1999-04-09 2004-05-11 Nec Corporation Method and system for installing a software product to a computer with authorization
US20040260793A1 (en) * 2003-03-31 2004-12-23 Yuichi Ichikawa Communication device and program

Family Cites Families (29)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4674055A (en) 1983-06-09 1987-06-16 Brother Kogyo Kabushiki Kaisha Software vending system
JPS6314258A (ja) 1986-07-03 1988-01-21 Seiko Epson Corp 応用プログラムの起動方法
JPH06215160A (ja) 1992-08-25 1994-08-05 Texas Instr Inc <Ti> データ処理方法および装置
US7080051B1 (en) 1993-11-04 2006-07-18 Crawford Christopher M Internet download systems and methods providing software to internet computer users for local execution
JPH11134155A (ja) 1997-10-29 1999-05-21 Mitsubishi Electric Corp 使用頻度に応じて機能が変化するソフトウェアの構成方法
US6366947B1 (en) 1998-01-20 2002-04-02 Redmond Venture, Inc. System and method for accelerating network interaction
JP2000056895A (ja) 1998-08-11 2000-02-25 Fujitsu Ltd データ保存方法とデータ保存制御装置およびそのための記録媒体
US7130831B2 (en) * 1999-02-08 2006-10-31 Copyright Clearance Center, Inc. Limited-use browser and security system
JP3403717B2 (ja) 1999-05-21 2003-05-06 ヤマハ株式会社 ネットワークを介したコンテンツ提供方法及び装置
DE19964030A1 (de) 1999-12-30 2001-07-05 Ibm Effizientes Laden von Dokumenten auf dem Internet
JP3578266B2 (ja) 2000-01-06 2004-10-20 インターナショナル・ビジネス・マシーンズ・コーポレーション アプリケーションの起動方法、アプリケーションの起動のためのソフトウエア・プロダクト
GB2359908B (en) * 2000-03-04 2004-09-15 Motorola Inc Communication system architecture and method of controlling data download to subscriber equipment
TW522319B (en) 2000-05-09 2003-03-01 Nutex Comm Corp A database system and method for secure access through internet using wireless apparatus
CN1213371C (zh) * 2000-06-02 2005-08-03 松下电器产业株式会社 信息提供系统和构成该系统的装置
KR20040016767A (ko) * 2000-06-26 2004-02-25 모토로라 인코포레이티드 자율적인 메모리 사용 최적화 및 소프트웨어 기능다운로딩을 위한 방법 및 장치
US6735758B1 (en) * 2000-07-06 2004-05-11 International Business Machines Corporation Method and system for SMP profiling using synchronized or nonsynchronized metric variables with support across multiple systems
TW584801B (en) 2000-12-11 2004-04-21 Ntt Docomo Inc Terminal and repeater
US20020073235A1 (en) * 2000-12-11 2002-06-13 Chen Steve X. System and method for content distillation
US7269608B2 (en) 2001-05-30 2007-09-11 Sun Microsystems, Inc. Apparatus and methods for caching objects using main memory and persistent memory
US20040015965A1 (en) 2001-06-02 2004-01-22 Malcom Sparks Installation-free middleware demonstration system
US20030014496A1 (en) 2001-06-27 2003-01-16 Spencer Donald J. Closed-loop delivery system
WO2003030026A2 (en) 2001-10-02 2003-04-10 Symbian Limited Mobile web browsing device
US6985999B2 (en) * 2001-10-23 2006-01-10 Ip-First, Llc Microprocessor and method for utilizing disparity between bus clock and core clock frequencies to prioritize cache line fill bus access requests
US6931488B2 (en) 2001-10-30 2005-08-16 Sun Microsystems, Inc. Reconfigurable cache for application-based memory configuration
AU2002359001A1 (en) 2001-12-28 2003-07-24 Access Co., Ltd. Usage period management system for applications
US6986006B2 (en) * 2002-04-17 2006-01-10 Microsoft Corporation Page granular curtained memory via mapping control
US20040006541A1 (en) * 2002-07-08 2004-01-08 International Business Corporation Method and system for purchasing broadcast content
US7509683B2 (en) * 2002-08-26 2009-03-24 Hewlett-Packard Development Company, L.P. System and method for authenticating digital content
JP2004341588A (ja) 2003-05-13 2004-12-02 Dainippon Screen Mfg Co Ltd ネットワークを利用した画像の出力演算サービス

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6735768B1 (en) * 1999-04-09 2004-05-11 Nec Corporation Method and system for installing a software product to a computer with authorization
US20010049641A1 (en) * 2000-06-05 2001-12-06 Shunsuke Nakamura Sound data delivering system, sound data delivery method, delivering server utilized in the sound data delivering system, client-side terminal utilized in the sound data delivering system, and computer-readable recording medium containing a program applied to a computer utilized in the sound data delivering system
US20020184520A1 (en) * 2001-05-30 2002-12-05 Bush William R. Method and apparatus for a secure virtual machine
US20040078636A1 (en) * 2002-03-20 2004-04-22 National Inst. Of Advanced Ind. Science And Tech. Input and output control means for computer system storage and a software execution method using same
US20040260793A1 (en) * 2003-03-31 2004-12-23 Yuichi Ichikawa Communication device and program

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070204102A1 (en) * 2006-02-28 2007-08-30 Nokia Corporation Cache feature in electronic devices
US20080052368A1 (en) * 2006-08-28 2008-02-28 Sony Ericsson Mobile Communications Ab System and method to shuffle and refill content
US11256491B2 (en) 2010-06-18 2022-02-22 Sweetlabs, Inc. System and methods for integration of an application runtime environment into a user computing environment
US11829186B2 (en) 2010-06-18 2023-11-28 Sweetlabs, Inc. System and methods for integration of an application runtime environment into a user computing environment
US10430502B2 (en) 2012-08-28 2019-10-01 Sweetlabs, Inc. Systems and methods for hosted applications
US11010538B2 (en) 2012-08-28 2021-05-18 Sweetlabs, Inc. Systems and methods for hosted applications
US11347826B2 (en) 2012-08-28 2022-05-31 Sweetlabs, Inc. Systems and methods for hosted applications
US11741183B2 (en) 2012-08-28 2023-08-29 Sweetlabs, Inc. Systems and methods for hosted applications
US20160359921A1 (en) * 2012-12-20 2016-12-08 Intel Corporation Secure local web application data manager

Also Published As

Publication number Publication date
DE602004000056D1 (de) 2005-09-22
US7899973B2 (en) 2011-03-01
ATE302442T1 (de) 2005-09-15
TW200504519A (en) 2005-02-01
EP1465042B1 (de) 2005-08-17
JP3923921B2 (ja) 2007-06-06
DE602004000056T2 (de) 2006-07-06
US20080177950A1 (en) 2008-07-24
JP2004303066A (ja) 2004-10-28
ES2243914T3 (es) 2005-12-01
CN1245051C (zh) 2006-03-08
TWI244591B (en) 2005-12-01
EP1465042A1 (de) 2004-10-06
CN1535063A (zh) 2004-10-06

Similar Documents

Publication Publication Date Title
US7899973B2 (en) Information processing device and program
TWI228364B (en) Communication system, relay device and communication control method
RU2456768C2 (ru) Устройство управления распространением контента, терминал, программа и система распространения содержимого
US20050038874A1 (en) System and method for downloading data using a proxy
EP1098457B1 (de) Mobiles kommunikationsendgerät
EP1553498B1 (de) Email-ablieferungssystem, mail-server und mail-client
WO2006011343A1 (ja) 競合解決装置
US20040242205A1 (en) Communication terminal
US8725846B2 (en) Network system, terminal customization method, and customization service method
EP1808792A2 (de) Inhaltsübertragungssystem, Übertragungsserver, Kommunikationsendgerät und Inhaltsübertragungsverfahren
US20040260793A1 (en) Communication device and program
EP1462909B1 (de) Computer zur Verwaltung der gemeinsamen nutzung von Daten zwischen Anwendungsprogrammen
US20040212485A1 (en) Method and apparatus for controlling transfer of content
JP4373480B2 (ja) 通信装置及びプログラム
KR100601848B1 (ko) 이동 통신 단말에서의 다운로드 디스크립터 처리 방법
JP4580164B2 (ja) 電子機器およびプログラム
JP2004126736A (ja) 通信端末及び通信制御方法
JP4382049B2 (ja) ネットワークへのアクセスを管理する方法および装置
JP4680485B2 (ja) 端末装置、プログラムおよび記録媒体

Legal Events

Date Code Title Description
AS Assignment

Owner name: NTT DOCOMO, INC., JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NARUSE, NAOKI;ICHIKAWA, YUICHI;OI, TATSURO;AND OTHERS;REEL/FRAME:015680/0239

Effective date: 20040628

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION