WO2003098442A1 - Communication device - Google Patents
Communication device Download PDFInfo
- Publication number
- WO2003098442A1 WO2003098442A1 PCT/JP2003/006099 JP0306099W WO03098442A1 WO 2003098442 A1 WO2003098442 A1 WO 2003098442A1 JP 0306099 W JP0306099 W JP 0306099W WO 03098442 A1 WO03098442 A1 WO 03098442A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- communication device
- program
- encapsulated
- protection
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims description 109
- 238000000034 method Methods 0.000 claims abstract description 86
- 238000012217 deletion Methods 0.000 claims 1
- 230000037430 deletion Effects 0.000 claims 1
- 230000001413 cellular effect Effects 0.000 abstract 3
- 238000012545 processing Methods 0.000 description 28
- 230000006870 function Effects 0.000 description 26
- 230000008569 process Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 15
- 238000005538 encapsulation Methods 0.000 description 14
- 230000004048 modification Effects 0.000 description 11
- 238000012986 modification Methods 0.000 description 11
- NGGRGTWYSXYVDK-RRKCRQDMSA-N 4-amino-5-chloro-1-[(2r,4s,5r)-4-hydroxy-5-(hydroxymethyl)oxolan-2-yl]pyrimidin-2-one Chemical compound C1=C(Cl)C(N)=NC(=O)N1[C@@H]1O[C@H](CO)[C@@H](O)C1 NGGRGTWYSXYVDK-RRKCRQDMSA-N 0.000 description 6
- 239000004973 liquid crystal related substance Substances 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 239000003607 modifier Substances 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 239000002775 capsule Substances 0.000 description 1
- 230000012447 hatching Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000717 retained effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/102—Entity profiles
-
- 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]
-
- 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/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
- G06F21/53—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by executing in a restricted environment, e.g. sandbox or secure virtual machine
-
- 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/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
- G06F21/556—Detecting local intrusion or implementing counter-measures involving covert channels, i.e. data leakage between processes
-
- 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/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
-
- 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/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/629—Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
-
- 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/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
-
- 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/2143—Clearing memory, e.g. to prevent the data from being stolen
-
- 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/2145—Inheriting rights or properties, e.g., propagation of permissions or restrictions within a hierarchy
-
- 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 technology for ensuring security of a communication device and a technology for protecting copyright of content.
- a communication device such as a mobile phone or a personal computer having a packet communication function can download various programs from a server connected to the Internet.
- open networks such as the Internet
- various people around the world can freely disclose information and provide programs. While open networks have these advantages, they also have disadvantages.
- a malicious individual or group may provide a program that secretly steals data stored in a communication device.
- a program may be provided that causes no problems if operated on a communication device that is not malicious.
- problems may occur. For example, a situation may occur in which a user's telephone number, e-mail address, bank account number, and the like stored in the communication device are read out without permission and leak out of the communication device.
- a communication device capable of executing a program written in the Java (registered trademark) language has the following restrictions.
- the resources that can be accessed during the execution of the Java program are limited to very limited resources.
- programs for which reliability cannot be completely guaranteed are used, for example, in an address book in a communication device or a user's personal information. Access to information and other information is prohibited. Disclosure of the invention
- the above-described access restriction mechanism has a certain effect in ensuring security in the communication device, it imposes various operation restrictions on programs provided via the network. That is, such an access restriction is a factor that impairs the convenience inherent in a program provided via a network, such as the ability to freely change or add a function in a communication device.
- the following dangers may occur. In other words, damages caused by the aforementioned programs provided by malicious individuals or organizations, or programs that cause problems when operated on communication devices, can cause communication problems not only with the communication device that executed this program, but also with this communication device. It may reach other electronic devices that have performed this.
- the present invention has been made in view of the circumstances described above, and can ensure the security of a program provided via a network without impairing the convenience of the program. It aims to provide communication devices, programs and recording media.
- the present invention provides a receiving unit for receiving a program, and among data stored in the communication device, data used when executing the program received by the receiving unit.
- a method for operating the encapsulated data from outside the object the method being a method for operating the encapsulated data specified by the specifying means and the encapsulated data specified by the specifying means; and
- the present invention also provides a receiving step of causing the communication unit to receive a program, and a specifying step of specifying data used when the program received in the receiving step is executed, among data stored in the storage unit. And an object having encapsulated data specified in a specific step, a method for operating the encapsulated data from outside the object, and transmitting the data to the operation source program.
- a generation step that generates an object having only a method that is not passed, and a resource that can be accessed when the program received in the reception step is being executed are stored in the storage unit.
- a program for causing a computer to execute an access control step of permitting access to the object generated in the generation step may be provided.
- the communication device access an object that encapsulates data used in the process during execution of the process based on the received program.
- the communication device cannot acquire the data itself encapsulated in the object during execution of the processing based on the received program, but the data in the object is obtained by using the method provided in the object. Can be operated.
- the present invention provides a receiving means for receiving a program, a specifying means for specifying, among data stored in the communication device, data used when the program received by the receiving means is executed, An object having data encapsulated and specified by the specifying means, a method for operating the encapsulated data from outside the object, and delivering the data to a program that operates the object.
- Determining means for determining which of the first generating means or the second generating means generates the resource, and limiting resources that can be accessed when the program received by the receiving means is being executed,
- a communication device having access control means for prohibiting access to the data specified by the specifying means among data stored in the communication apparatus, while permitting access to the object generated by the generation means; I will provide a.
- the present invention also provides a receiving step of causing the communication unit to receive a program, and a specifying step of specifying data used when the program received in the receiving step is executed, among data stored in the storage unit.
- the encapsulated data and the encapsulated data based on protection necessity information indicating the necessity of protection of the data specified in the specific step, which is set in advance. Or an object having a method for operating the data as the first object having a method for transferring the data to the operation source program, or an object having no method for transferring the data to the operation source program. And a first or second object determined in the determining step.
- An object generating step, and a resource that can be accessed when the program received in the receiving step is being executed, is limited to the specific step of the data stored in the communication device.
- a program may be provided for causing a computer to execute an access control unit that prohibits access to the data specified in the generation step and permits access to the object generated in the generation step.
- the communication device access an object that encapsulates data used in the process during execution of the process based on the received program. Further, the communication device determines the type of the object to be generated based on the protection necessity information set for the data to be encapsulated. Furthermore, it determines whether or not the data itself encapsulated in the object can be obtained during execution of processing based on the received program. You.
- the present invention provides a mode in which the above-mentioned programs are distributed to users via a telecommunication line, or these programs are stored in a computer-readable storage medium such as an FD, CD, or MO disk and distributed. But it can also be implemented.
- FIG. 1 is a block diagram illustrating a configuration of a communication system according to an embodiment of the present invention.
- FIG. 2 is a block diagram illustrating a hardware configuration of the mobile phone according to the embodiment.
- FIG. 3 is a diagram exemplifying a data configuration of a type designation table stored in a nonvolatile memory in the mobile phone according to the embodiment.
- FIG. 4 is a diagram for explaining an execution environment of JaVaAP in the mobile phone according to the embodiment.
- FIG. 5 is a schematic diagram for explaining an encapsulated object in the mobile phone according to the embodiment.
- FIG. 6 is a schematic diagram illustrating an example of an incompletely encapsulated object in the mobile phone according to the embodiment.
- FIG. 7 is a schematic diagram illustrating a completely encapsulated object in the mobile phone according to the embodiment.
- FIG. 8 is a flowchart illustrating an operation of an object generation process executed by the CPU in the mobile phone according to the embodiment.
- FIG. 9 is a flowchart illustrating an operation of an access management process executed by the CPU in the mobile phone according to the embodiment.
- FIG. 10 is a flowchart illustrating the operation of a Java AP termination process executed by the CPU in the mobile phone according to the embodiment.
- FIG. 11 is a diagram for describing a modification of the JaVa execution environment according to Modification 6 of the present invention.
- FIG. 12 is a block diagram illustrating a modification of the communication system according to modification 6 of the present invention.
- FIG. 1 is a block diagram illustrating a configuration of a communication system 1 according to an embodiment of the present invention.
- the communication system 1 includes a content server 10, the Internet 20, a mobile packet communication network 30, and a mobile phone 40.
- FIG. 1 shows only one mobile phone 40 in order to prevent the drawing from being complicated. .
- FIG. 1 shows only one content server 10, one gateway server 31 and one base station 32.
- the content server 10 has a function of performing bucket communication with the mobile phone 40 via the Internet 20 and the mobile packet communication network 30.
- the content server 10 stores various contents such as programs and image data to be provided to the mobile phone 40 and music data.
- a Java application program hereinafter abbreviated as Java API
- the Java application is an application program for the mobile phone 40 described in the Java programming language, such as the Java application @Java application.
- the mobile packet communication network 30 is a communication network that provides a packet communication service to the mobile phone 40 accommodated in the mobile packet communication network 30, and has a gateway server 31 and a base station 32. are doing.
- the communication system 1 has a mobile telephone network (not shown) in addition to the mobile packet communication network 30.
- This mobile telephone network provides a general mobile telephone call service to the mobile telephone 40.
- the gateway server 31 exchanges data having different communication protocols such as a communication protocol for the mobile bucket communication network 30 and a communication protocol for the Internet 20. It converts them to each other and relays the exchange of data 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 wireless communication with a mobile phone 40 located in a wireless cell covered by the own station 32. Do.
- the mobile phone 40 performs wireless communication with the base station 32 that covers the wireless cell in which the mobile phone 40 is located.
- the mobile phone 40 has a function of performing packet communication with the content server 10 via the mobile packet communication network 30 and the Internet 20. Content can be downloaded.
- FIG. 2 is a block diagram illustrating a hardware configuration of the mobile phone 40.
- the mobile phone 40 includes a wireless communication section 401, an operation input section 402, a call processing section 403, a communication interface 404, a CPU 405, and a liquid crystal display. It has a display unit 406 and a storage unit 407, and these units are connected by a bus 411.
- the wireless communication unit 401 includes an antenna 401 a and controls wireless communication performed with the base station 32. Under the control of the CPU 405, the wireless communication unit 401 generates a transmission signal by superimposing, for example, data relating to transmission voice or data for packet communication on a carrier wave. Transmit to base station 32. In addition, the wireless communication unit 401 receives a wireless signal transmitted from the base station 32 via the antenna 410a, demodulates this signal, and receives data related to the received voice addressed to the own device 40. Get data for bucket communication—evening.
- the operation input unit 402 has a plurality of keys for inputting numbers, characters, operation instructions, and the like, and outputs an operation signal corresponding to the operation of these keys to the CPU 405.
- the call processing unit 403 has, for example, a microphone, a speaker, a voice processing unit, and the like, and performs a call process including disconnection of a call Z under the control of the CPU 405.
- the communication interface 404 controls wired communication with an electronic device connected via a communication cable.
- this communication interface 404 uses infrared communication, It may control short-range wireless communication such as HomeRF (Home Radio Frequency) and Bluetooth (registered trademark).
- the CPU 405 executes various programs stored in the storage unit 407 to control each unit of the device connected via the bus 411.
- the liquid crystal display unit 406 has a liquid crystal display panel and a drive circuit that controls display 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 (Electrica 11 y Erasab 1 e Programm ab 1 e—ROM). And has.
- the ROM 408 stores, for example, an operating system (hereinafter abbreviated as ⁇ S) for the mobile phone 40, a Web (World Wide Web) browser, software for constructing a Java execution environment, and the like.
- ⁇ S an operating system
- the RAM 409 is used as a work area of the CPU 405, and temporarily stores various programs and data executed by the CPU 405.
- the non-volatile memory 410 stores application programs incorporated in the mobile phone 40 from the time of product shipment of the mobile phone 40 and contents such as Java AP downloaded from the content server 10. .
- the non-volatile memory 410 stores address book data in which information such as telephone numbers and mail addresses are stored, received or transmitted e-mail data, history data on incoming and outgoing calls, and electronic payment. Various data such as the user's bank account number and credit card number are stored.
- Native application in order to distinguish the application software already stored in the R ⁇ M 408 or the nonvolatile memory 410 at the time of product shipment of the mobile phone 40 from the downloaded JaVaAP.
- This native application is provided with identification information indicating that it is a native application.
- the non-volatile memory 410 has a type designation table 410a, a JAR storage 410b, an individual scratch pad 410c, and a common scratch pad 410d.
- the type specification table 41 0a will be described with reference to FIG. I do.
- the type designation table 410 a includes, among various data stored in the nonvolatile memory 410, address book data, e-mail data, incoming / outgoing call history data, user data, and the like. Of the data that may be used by the downloaded Java Va AP when the downloaded Java Va AP is executed, the data name and the type designation information are registered in association with each other. .
- the type specification information is information that specifies whether the type of the object that handles the data is “completely encapsulated” or “incompletely encapsulated”.
- the above-mentioned user data is personal information relating to the user of the mobile phone 40, such as the user's name, age, birthday, bank account number, and credit card number. As shown in FIG. 3, the type designation information is 1-bit data of “1” or “0”. If the value of type specification information is set to "1”, the type of the object is specified as "completely encapsulated” type, while if the value of type specification information is set to "0”, the object Is designated as a "non-perfectly encapsulated” type.
- an encapsulated object is an object having one or more encapsulated (information hiding) data and one or more methods for enabling operations on each of the encapsulated data from outside the object. is there.
- a completely encapsulated object is a program that operates the object encapsulated in the object among the above encapsulated objects (for example, a downloaded JavaVa). This is an object configured to have no method to be passed to AP).
- An incompletely encapsulated object is an object that has at least one method of transferring the data in the object itself to a program that operates the object among the encapsulated objects. The difference between a fully encapsulated object and a non-fully encapsulated object is whether or not it has a method for passing the encapsulated data itself in the object to the operating program.
- the type designation table 410a shown in FIG. 3 for each data, whether the data is treated as a completely encapsulated object or whether it is treated as an incompletely encapsulated object is registered.
- the book data, e-mail data, incoming / outgoing call history data, and user data are particularly important in security among data stored in the mobile phone 40.
- the Java AP downloaded to the mobile phone 40 is a program whose reliability cannot be completely guaranteed. Therefore, even if a malicious third party creates a data-stealing JaVa AP by downloading it to a mobile phone 40, it will be described above through such a Java AP. It is necessary to prevent as much as possible that data with high security importance leaks out of the mobile phone 40.
- the type specification table 410a the address book data, e-mail data, incoming / outgoing history data, and user data—in the evening, the value of the type specification information is “1” (complete capsule). Has been registered. Further, in the type designation table 410a shown in FIG. 3, contents A and contents B are contents such as image data and music data downloaded from the contents server 10. These contents are given a copyright protection flag by the content provider (hereinafter referred to as the content provider). Here, the copyright protection flag is 1-bit data of "1" or "0".
- the content data for which the value of the copyright protection flag is "0" does not need to be treated as a completely encapsulated object because the copyright has been abandoned.
- the content data itself is delivered to the downloaded JAVA AP, and the convenience of the JAVA AP becomes higher if the content data itself can be delivered. Therefore, “0” (incompletely encapsulated type) is registered as the value of the type specification information in the content B in the type specification table 410a.
- the type specification table 410a "1" is set in advance as the value of the type specification information in the address book data, e-mail data, incoming / outgoing history data, and user data.
- the CPU 405 determines the value of the type designation information corresponding to the value of the copyright protection flag attached to this content. It is determined. Then, the type designation information is registered in the type designation table 410a together with the content identification information (data name) for identifying the content.
- the non-volatile memory 410 stores JAR storage 410 b, individual scratch pads 410 c, It has a common scratch pad 410d.
- Jav aAP is a JAR (Java Archive) file that combines the Java AP's main program and image files and audio files used in accordance with the execution of the main program, and a JAR file. It has an ADF (Application Descriptor File 1 e) in which various control information for controlling installation, activation, network access, and the like of the server are described.
- ADF Application Descriptor File 1 e
- each storage area in the JAR storage 410b stores a JAR file of the JaVa AP.
- each storage area in the individual scratch pad 410c includes, for example, when the JaVaAP is a game program, according to the use of the JaVaAP, such as the scoring data and save data until now.
- the data generated for the Java AP is stored.
- the common scratch pad 410 d stores data commonly used by a plurality of JaVaAPs.
- the JaVa AP is executed on the mobile phone 40 after the download, the resources that the mobile phone 40 can access with the execution of the JaVaAP are determined by the JaVaAP.
- Content server 10 site
- FIG. 4 is a diagram for explaining the execution environment of the JaVaAP in the mobile phone 40.
- the mobile phone 40 includes KVM (KV irtual Machine) as software for constructing an execution environment of Java AP, and CLDC (Con on) as a configuration. nected L im ited D evice C onfigurati on).
- the mobile phone 40 has a profile that has been independently formulated by the carrier as a profile.
- J2ME Java 2 Micro Edition
- KVM is a JVM Uav aVirtua1M aChinee) that has been redesigned for small electronic devices.
- the KVM converts a byte code that is an executable file format of Java APP into an instruction code that can be interpreted / executed by the CPU 405 via OS.
- the CLDC class library is a class library for CLDC.
- the original Java extension library is a class library for providing mobile phone-specific functions based on CLDC.
- the original Java extension library includes, for example, a user interface API (Ap 1 IC on Program Interface), a networking API, a scratchpad HAP I, a fully encapsulated API, and an incompletely encapsulated API. And so on.
- the user interface API is an API that supports the user interface function of the mobile phone 40.
- the networking API is an API that supports access to a network resource specified by a URL (UniformResorecLoCator).
- the scratch pad API is an API that supports writing and reading of data to and from the individual scratchpad 410c and the common scratchpad 410d.
- the fully encapsulated API is an object for generating a completely encapsulated object
- the non-fully encapsulated API is an object for generating a noncompletely encapsulated object.
- these programs are installed on the mobile phone prior to factory shipment.
- these programs are downloaded to a mobile phone from a site in the network and installed.
- the program may be installed on a PC other than a mobile phone.
- the program is stored in a computer-readable storage medium such as an FD, CD, or MO disk, distributed to the user, and installed on the PC by the user.
- the mobile phone 40 has a manufacturer-specific extension library in addition to the CLDC class library and the original JaVa extension library.
- the manufacturer-specific extension library is a class library for each manufacturer that manufactures the mobile phone 40 to provide a unique function.
- JAM Java Application Manager
- JAM manages Java AP downloaded to the mobile phone 40, a completely encapsulated object, an incompletely encapsulated object, and the like under the control of the OS. It has a function.
- JAM has a function of installing, updating, and deleting a Java AP, a function of displaying a list of Java Va stored in a nonvolatile memory 410, a function of displaying a Java AP, A function to perform execution management (startup and forced termination, etc.), a function to restrict access to the mobile phone 40 due to the execution of Java AP, and a function to create, update, and delete non-fully encapsulated objects.
- native applications that provide a telephone directory function, a browser function, a network communication function, and the like operate directly under the control of the OS.
- FIG. 5 is a schematic diagram for explaining an encapsulation object.
- an encapsulated object is composed of one or more encapsulated data and one or more methods for enabling each encapsulated data to be operated from outside the object. It is an object to have.
- an encapsulated object having two data 1 and 2 and two methods 1 and 2 is illustrated. Since data 1 and 2 in this encapsulated object are both encapsulated, data 1 and 2 cannot be read and written directly from outside the object. So, for example, if the downloaded program accesses data 1 and 2 in the encapsulated object, the program uses methods 1 and 2 to force the operation on the desired data 1 or data 2 Must be commanded to the structured object.
- the method 1 shown in Fig. 5 is, for example, a method for passing the specified data itself to the operation source program, the operation source program uses the method 1 to execute any data in the encapsulated object. It is possible to obtain 1 and 2. If method 2 shown in FIG.
- the operation source program uses method 2 to arbitrarily set any data 1 and 2 in the encapsulated object. Can be displayed on the screen. It should be noted here that the program that displays arbitrary data 1 and 2 in the encapsulated object on the screen using Method 2 specifies the data to be displayed and the command to the encapsulated object. However, it does not acquire the data to be displayed.
- address book data, e-mail data, etc. are treated as a completely encapsulated object, the operation source program will not be able to guarantee the reliability completely, such as a downloaded Java AP. Even if it does, it will not pass the data itself to the program. Therefore, security in the mobile phone 40 can be ensured. At the same time, even if such a program is used, address book data, e-mail data, and other data that were previously not allowed to access at all from the viewpoint of ensuring security are completely encapsulated. Operations can be performed using the methods of the object.
- FIG. 6 is a schematic diagram illustrating an example of an incompletely encapsulated object relating to telephone directory data. Note that, in this embodiment, the phonebook data is always treated as a completely encapsulated object because of its high importance in security, but here, it is treated as a non-completely encapsulated object for the sake of comparison. The following describes the case where
- the fields stored in the pri Vate field are encapsulated by declaring the fields in the object in the pri Vate field using the access modifier "pri Vate". .
- the access modifier "pri Vate" the access modifier "pri Vate"
- the data stored in each priVate field cannot be read and written directly from outside the object.
- the object in order to access the data stored in each private field from outside the object, the object must be instructed to operate on the data using the method provided for this object. .
- the incomplete encapsulation object shown in Fig. 6 is provided with two private fields, each of which stores pri Vatecharvalue [1] and rivatecharvalue [2] phonebook string data.
- This incomplete encapsulated object has two methods: get By tes 0 and dr awS tring ().
- getBytes0 is a method that transfers the data in the object to the program of the operation source in the form of a byte array. Therefore, the downloaded Java AP uses this method called get By tes 0 to store the phonebook string data (priVatecharvalue [1], privatecharvalue [2]) in the non-fully encapsulated object. ) Can be obtained.
- Java AP will store the acquired phonebook string data into the Java It can be sent to the server from which the AP was downloaded (content server 10).
- drawstrink is a method for displaying data in the object on the liquid crystal screen of the mobile phone 40.
- J avAP uses this method called dr awS tring () to display the phonebook string data (privatecharvalue [l], privatecharvalue [2]) in the non-fully encapsulated object on the LCD screen.
- FIG. 7 is a schematic diagram illustrating an example of a completely encapsulated object relating to the telephone directory. The difference between the fully encapsulated object shown in Fig. 7 and the non-fully encapsulated object shown in Fig. 6 is that the fully encapsulated object operates on the data itself within the object, like get By tes 0 described above. The point is that there is no method to transfer to the original program.
- a fully encapsulated object is encapsulated and has no method for transferring the data in the smart object to the program that operated it. Therefore, the downloaded Java AP uses the method dr awS tring () to display the phonebook string data (privatecharvalue [1], privatecharva 1 ue [2]) in the object on the screen. Is possible, but it is not possible to obtain the string data itself in the phone book. In view of the above, even if a malicious third party's data stealing Java AP was downloaded to the mobile phone 40, such a Java AP would not Phonebook data is not delivered. Of course, the telephone directory data is not transmitted to the outside of the mobile phone 40 such as a server.
- the fully encapsulated object and the non-fully encapsulated object are stored as ROM 408 or non-volatile memory as a native application.
- the display control program stored in 410 display the character string of the telephone directory on the LCD screen. If Java AP can acquire the display data from this display control program, the complete encapsulation object will be displayed.
- the use of objects and incompletely encapsulated objects has no meaning.
- the resources that the mobile phone 40 can access during the execution of the Java Va AP are restricted by the access restriction function of JAM as described above. Is limited.
- the display control program is not included in the resources to which the mobile phone 40 is allowed to access during the execution of the Java AP, it is necessary that the Java AP obtains the display data from the display control program. None can happen.
- encapsulation can be considered at the programming language level and at the execution code (machine language or bytecode) level. Even if the encapsulation at the programming language level is complete, if the encapsulation at the executable code level is not complete, it cannot be said that the data has been completely encapsulated. For example, a program using the programming language C ++ can generate an encapsulated object having a priVate field. However, since C ++ is only a programming language, it can only achieve encapsulation at the programming language level.
- the mobile phone 40 performs packet communication with the content server 10 via the mobile packet communication network 30 and the Internet 20 assuming that the mobile phone 40 performs the operation described below. It is assumed that VaAP is downloaded and stored in the nonvolatile memory 410. In addition, the nonvolatile memory 410 stores address book data, e-mail data, user data, etc. in addition to the downloaded Java AP (content). The type specification table 410a stores It is assumed that type designation information is registered for each of these data.
- the type designation table 410a "1" is set as the value of the type designation information for the address book data, the e-mail data, the incoming / outgoing history data, and the user data.
- the CPU 405 For the downloaded content, when the content is downloaded to the mobile phone 40, the CPU 405 outputs the type designation information value corresponding to the value of the copyright protection flag attached to the content.
- the type designation information and the content name are determined and registered in the type designation table 410a. ⁇ 1. Object generation processing>
- This object generation processing is executed by the CPU 405 as a function of JAM.
- the object generation processing is executed when a program to be executed is specified by an operation input from a list of programs displayed on the screen. Is done.
- the form of instructing the execution of the program is not limited to the operation input. For example, when the execution of the program is instructed at predetermined time intervals, or when executed from another program that has already been executed. In some cases, the execution of the program may be instructed from outside the mobile phone 40 using e-mail or the like.
- the CPU 405 of the mobile phone 40 specifies a program specified by an operation input as a program to be executed (Step S101).
- the CPU 405 determines whether the specified program is a downloaded Java AP or a native application (step S102).
- identification information indicating that the native application is a native application is given to the native application. Accordingly, the CPU 405 determines whether the program is a downloaded Java AP or a native application by determining whether or not the program has the above identification information. be able to.
- step S102 when the CPU 405 determines that the program is a native application (step S102: No), the CPU 405 ends the object generation processing and activates the native application designated as the program to be executed. Then, the CPU 405 performs a process based on the activated native application.
- the program to be executed is a native application
- the reliability can be completely guaranteed, so the use of a completely encapsulated object or an incompletely encapsulated object, or with the execution of a native application
- the native application can access any resources in the mobile phone 40 and any resources on the network.
- the CPU 405 determines that the program is a downloaded Java AP (step S102: Yes)
- the CPU 405 reads various data stored in the nonvolatile memory 410.
- the data used when this JaVaAP is executed is identified, for example, by analyzing the program contents of this JaVaAP (step S103).
- the data stored in the JAR file of this JaVaAP in the JAR storage 410b is excluded from the specific target. . This is because the data stored in the JAR file is the data necessary for executing this Java AP, and is the data prepared by the content provider that provides the Java AP. It is.
- the CPU 405 refers to the type specification table 410a (FIG. 3) and sets the type of the object handling the data to "completely encapsulated” based on the value of the type specification information of the data specified above. Or “incomplete encapsulation”.
- Type (step S104). For example, if the data used by Java AP is address book data overnight, the CPU 405 refers to the type specification table 410a, and changes the type of the object handling the address book data to “completely encapsulated” type. decide. If the data used by the Java AP is the content B (copyright protection flag “0”), the CPU 405 determines the type of the object handling the content B to be the “incomplete encapsulation” type.
- the CPU 405 generates a complete force object or an incomplete encapsulated object based on the data specified in step S103 and the type of the object determined in step S104 (step S104).
- step S104 the type of the object determined in step S104.
- step S 105 For example, if the data specified in step S103 is address book data (type designation information "1"), the CPU 405 activates a complete encapsulation API in the original Java extension library. Fully encapsulated API is used to identify the data from the methods included in fully encapsulated API. Select the method specified at times. Then, the method and the method are encapsulated to generate a fully encapsulated object for the dress book data. If the data specified in step S103 is the content B, the CPU 405 invokes the non-complete encapsulation API in the original Java extension library to generate the non-complete encapsulation object for the content B. Generate.
- the CPU 405 stores the generated completely encapsulated object or the non-fully encapsulated object in the common scratch pad 410d (step S106), and ends the object generation processing.
- the completely encapsulated object and the non-fully encapsulated object generated in step S105 are stored in the individual scratchpad 410c instead of the common scratchpad 410d. Is also good.
- step S103 If a plurality of data used by the Ja AP is specified in step S103, a completely encapsulated object or a non-fully encapsulated object for the data is specified for each identified data. In order to generate and store the generated data in the common scratch pad 410d, the processing of steps S104 to S106 is repeated for each data. Then, after ending the object generation processing, the CPU 405 activates the Java AP specified as the program to be executed, and starts the processing based on this program.
- This access management process is executed by the CPU 405 as a function of the JAM, and is executed as an interrupt process when an access request occurs in the process of executing the downloaded JaVaAP. .
- the CPU 405 of the mobile phone 40 determines whether or not the access request destination is a resource within a previously permitted range for an access request generated during the execution of the Java AP. Then, it is determined whether or not the access request is permitted (step S201).
- the downloaded JAVAAP is executed
- the CPU 405 allocates a resource that can be accessed along with the execution of the Java AP to a down port of the Java AP specified by the URL described in the ADF of the Java AP.
- a content server 10 site
- the CPU 405 permits this access request when the access request destination is any of the above-mentioned resources, but does not permit this access request when the access request destination is other than the above-mentioned resources. .
- the CPU 405 notifies the requesting Java AP of the determination result indicating whether the access request is permitted (step S202), and ends the access management process. Further, upon receiving the judgment result by JAM, the executing Java AP executes a process based on the access request according to the judgment result when the access request is permitted, but does not permit the access request. If so, the process based on the access request is cancelled.
- the CPU 405 of the mobile phone 40 activates the Java AP after performing the object generation processing shown in FIG. Also, in the course of executing the downloaded Java AP, the CPU 405 performs an access management process shown in FIG. 9 when an access request occurs. Therefore, the mobile phone 40 is always subjected to the access restriction by the JAM during the execution of the downloaded JaVaAP.
- the Java AP cannot access data itself such as address book data, e-mail data, incoming / outgoing call history data, user data, and content stored in the nonvolatile memory 410.
- the CPU 405 of the mobile phone 40 specifies, in the object generation processing described above, the data to be used by the Java AP to be activated, and either a completely encapsulated object or an incompletely encapsulated object for the data. Is generated and stored in the common scratchpad 410d. As described above, this common scratch pad 410d is portable even when access is restricted by JAM. This is a resource to which the access of the mobile phone 40 is permitted.
- the J aV aAP downloaded to the mobile phone 40 accesses the fully encapsulated object stored in the common scratchpad 410d and the incompletely encapsulated object, and uses the method provided in the object to execute this object. It is designed to instruct the operation on the data inside.
- a completely encapsulated object for address book data is generated by the above-described object generation processing, and stored in the common scratchpad 410d.
- the Java AP instructs the operation of the data in the object using the method provided for the object with respect to the generated completely encapsulated object for address book data. Therefore, while it is possible to display a part of the address book data of the completely encapsulated object on the screen, the data of the completely encapsulated object itself is not delivered to the Java AP.
- the downloaded Java AP is a program whose reliability cannot be guaranteed completely, but data whose copyright has been abandoned or data of low security importance is regarded as a non-perfectly encapsulated object.
- the data itself can be delivered to the JaVaAP. It is clear, without explanation, that it would be more convenient to deliver the data itself to the Java AP. In this way, if the object to be completely encapsulated and the object to be incompletely encoded are selectively used according to the security importance of the data to be encapsulated and the necessity of copyright protection, only the fully encapsulated object can be used. The convenience can be further improved as compared with the case where.
- JaVaAP termination processing executed by CPU 405 in mobile phone 40 will be described with reference to FIG.
- This JaVaAP termination processing is executed by the CPU 405 as a function of the JAM, and is executed as an interruption processing when a JaVaAP execution termination request is generated.
- the CPU 405 of the mobile phone 40 upon receiving a request to terminate the execution of the Java AP, generates a full force object or an incomplete force object stored in the common scratchpad 410d.
- the key is deleted (step S301).
- the fully encapsulated object and the non-fully encapsulated object to be deleted in step S301 are generated in the above-described object generation process (see FIG. 8) when the Java AP is activated, and are generated by the common scratchpad. This is stored in 410 d.
- the CPU 405 deletes the object from the common scratch pad 410 d, the CPU 405 ends the JaVAP termination processing.
- a fully encapsulated object or an incompletely encapsulated object is generated and stored in the common scratch pad 410 d, while the Java AP
- the fully encapsulated object or the non-fully encapsulated object can be deleted from the common scratchpad 4 1 d. No need to always hold at 0 d . Therefore, the memory resources of the mobile phone 40 can be used efficiently.
- the mobile phone 40 executes the processing according to the present invention (object generation processing, access management processing, Java AP termination processing) in accordance with a program stored in the ROM 408 or the nonvolatile memory 410.
- the program for executing such processing may be provided to the mobile phone 40 through communication. Further, a program for executing such processing may be provided to the mobile phone 40 using a recording medium such as an optical recording medium, a magnetic recording medium, or a semiconductor memory. However, when the program is provided to the mobile phone 40 via a recording medium, the mobile phone 40 has a recording medium drive for reading the program from the recording medium.
- the configuration is such that the type specification table 410a is used. However, if the type specification information is added to the data itself such as address book data, e-mail data, and content, etc. It is not necessary to use the designation table 410a.
- a completely encapsulated object or an incompletely encapsulated object for each data is generated and a common scratch is generated. It may be stored in the pad 410d.
- the common scratch pad 4 10 It is necessary to update the data in the fully encapsulated and non-fully encapsulated objects stored in d.
- security level information indicating security importance from “1 (importance“ high ”)” to “5 (importance“ low ”)” is added to data, While this security level information treats data from “1” to “3” as fully encapsulated objects, it treats data with security level information "4" and "5" as non-fully encapsulated objects. Good
- the J aV a AP may be transmitted by a carrier that operates the mobile packet communication network 30 or a fair third party such as a CA (certificate authority).
- va APs whose contents have been reviewed and are found to meet certain operating standards, as well as native applications, are programs that can completely guarantee reliability. Can be considered. Therefore, if the Java AP is certified by a third party, the data to be used can be obtained directly from the non-volatile memory 410 even in the case of the downloaded Java AP, as in the case of the native application. You may do so.
- identification information indicating that the Java AP is a certification program of a third-party organization is given to the Java AP certified by a third-party organization. Therefore, in the mobile phone 40, when it is determined whether or not the downloaded Java AP is a certification program by a third party, the presence or absence of the identification information may be determined.
- the content super-user 10 is configured to be connected to the Internet 20.
- the configuration may be such that the content server 10 is directly connected to the gateway server 31 of the mobile packet communication network 30 via a dedicated line.
- the configuration may be such that the gateway server 31 has the function of the content server 10.
- a configuration in which the content server 10 is installed in the mobile packet communication network 30 may be employed.
- the case where the present invention is applied has been described.
- the Java execution environment is not limited to the combination of KVM and J2ME described above.
- the communication device to which the present invention can be applied is not limited to a mobile phone.
- a configuration having MIDP (Mobile Information Device Profile) instead of the original Java extended profile as the J2ME profile may be adopted.
- MIDP Mobile Information Device Profile
- J VM in place of KVM
- CDC Connected Device Device onfiguration
- CLD C as a configuration of J 2ME
- a profile of J 2 ME for example, Profiles for LCD phones, TV profiles, power navigation profiles, etc. May be provided.
- a configuration having a hot pot and a J 2 SE (Java 2 Standard Edition) or a J 2 EE (Java 2 Enterprise Edition) may be employed.
- the present invention provides, for example, a PHS (Personal Handyphone System: registered trademark) terminal and a PDA (Person on al Digital A
- the present invention is applicable to various electronic devices having a communication function, such as ssistan 1;), car navigation devices, and personal computers. Further, the present invention is not limited to a communication device accommodated in mobile packet communication network 30.
- the present invention can be applied to personal computers 70 A to 70 C provided in LAN 50.
- the JaVa AP described in the JaVa programming language has been described.
- the programming language is not limited to the Java language.
- the fully encapsulated object relating to the telephone directory data has been exemplified.
- the methods and data included in the fully encapsulated object are not limited to this.
- Data such as still images, 3D images, moving images, image data such as Macintosh dia Flash (registered trademark), or moving image data, and such method Z are displayed on the screen of the mobile phone 40 as moving image data.
- a method may be used.
- the data may be audio data or music data, and the method may be a method of reproducing such audio music data by the reproducing unit of the mobile phone 40.
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU2003235331A AU2003235331A1 (en) | 2002-05-17 | 2003-05-16 | Communication device |
US10/514,685 US7818815B2 (en) | 2002-05-17 | 2003-05-16 | Communication device |
EP03723394A EP1507211A4 (en) | 2002-05-17 | 2003-05-16 | COMMUNICATIONS DEVICE |
US12/392,705 US8087078B2 (en) | 2002-05-17 | 2009-02-25 | Communication device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2002143608A JP3950010B2 (ja) | 2002-05-17 | 2002-05-17 | データ処理装置、プログラムおよび記録媒体 |
JP2002-143608 | 2002-05-17 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10514685 A-371-Of-International | 2003-05-16 | ||
US12/392,705 Continuation US8087078B2 (en) | 2002-05-17 | 2009-02-25 | Communication device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2003098442A1 true WO2003098442A1 (en) | 2003-11-27 |
Family
ID=29545028
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2003/006099 WO2003098442A1 (en) | 2002-05-17 | 2003-05-16 | Communication device |
Country Status (7)
Country | Link |
---|---|
US (2) | US7818815B2 (ja) |
EP (1) | EP1507211A4 (ja) |
JP (1) | JP3950010B2 (ja) |
CN (1) | CN1308850C (ja) |
AU (1) | AU2003235331A1 (ja) |
TW (1) | TWI239745B (ja) |
WO (1) | WO2003098442A1 (ja) |
Families Citing this family (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3950010B2 (ja) * | 2002-05-17 | 2007-07-25 | 株式会社エヌ・ティ・ティ・ドコモ | データ処理装置、プログラムおよび記録媒体 |
TWI231900B (en) | 2002-08-19 | 2005-05-01 | Ntt Docomo Inc | Communication terminal providing function against connection with specific website and method thereof and memory media memorizing the program |
JP4629304B2 (ja) * | 2002-10-30 | 2011-02-09 | 株式会社エヌ・ティ・ティ・ドコモ | 通信装置、プログラムおよび記録媒体 |
FI120638B (fi) * | 2003-12-17 | 2009-12-31 | Nokia Corp | Java-sovellusten käyttämän datan suojausjärjestelmä |
FR2864398A1 (fr) * | 2003-12-23 | 2005-06-24 | France Telecom | Terminal de telecommunication a deux espaces d'execution |
US8214799B2 (en) * | 2004-07-08 | 2012-07-03 | Microsoft Corporation | Providing information to an isolated hosted object via system-created variable objects |
JP4718151B2 (ja) * | 2004-09-24 | 2011-07-06 | 三菱電機株式会社 | 情報処理装置、情報処理方法およびプログラム |
CN101238473B (zh) * | 2005-08-03 | 2011-10-26 | 意法爱立信有限公司 | 保护密钥的安全终端和方法 |
JP4651681B2 (ja) | 2006-01-10 | 2011-03-16 | 富士通株式会社 | 端末装置およびコンピュータプログラム |
KR100894055B1 (ko) * | 2007-07-06 | 2009-04-20 | 드리머 | 디스크 매체 재생 장치 및 이를 이용한 멀티미디어 컨텐츠제공 방법 |
JP4879117B2 (ja) * | 2007-08-14 | 2012-02-22 | パナソニック株式会社 | 無線通信基地局装置、無線通信システム及び無線通信方法 |
US9256695B1 (en) | 2009-09-30 | 2016-02-09 | Saba Software, Inc. | Method and system for sharing content |
US8677506B2 (en) * | 2009-12-03 | 2014-03-18 | Osocad Remote Limited Liability Company | System and method for loading application classes |
CN101977214B (zh) * | 2010-10-18 | 2011-08-31 | 苏州阔地网络科技有限公司 | 一种网页上实现文件下载锁定同步的方法 |
US9665861B2 (en) * | 2014-01-10 | 2017-05-30 | Elo Touch Solutions, Inc. | Multi-mode point-of-sale device |
EP3160136B1 (en) * | 2014-06-20 | 2020-03-18 | Panasonic Intellectual Property Management Co., Ltd. | Hdr-uhd bd disk blu-ray disk playback and uhdtv display restrictions and conversions. |
DE102016204684A1 (de) * | 2016-03-22 | 2017-09-28 | Siemens Aktiengesellschaft | Verfahren und Einrichtung zum Bereitstellen einer kryptographischen Sicherheitsfunktion für den Betrieb eines Geräts |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001043176A (ja) * | 1999-06-15 | 2001-02-16 | Sun Microsyst Inc | 小フットプリント・デバイス・アプリケーション用の高性能ブックマーク |
JP2001350664A (ja) * | 2000-06-07 | 2001-12-21 | Nippon Telegr & Teleph Corp <Ntt> | 情報カプセル管理方法及び情報カプセル管理プログラムを格納した記憶媒体 |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5420866A (en) * | 1994-03-29 | 1995-05-30 | Scientific-Atlanta, Inc. | Methods for providing conditional access information to decoders in a packet-based multiplexed communications system |
US5675782A (en) * | 1995-06-06 | 1997-10-07 | Microsoft Corporation | Controlling access to objects on multiple operating systems |
US5790423A (en) * | 1995-06-14 | 1998-08-04 | Audible, Inc. | Interactive audio transmission receiving and playback system |
FR2743235B1 (fr) * | 1995-12-27 | 1998-01-23 | Alsthom Cge Alcatel | Methode pour securiser les collaborations entre objets d'un programme oriente objet |
US6088708A (en) * | 1997-01-31 | 2000-07-11 | Microsoft Corporation | System and method for creating an online table from a layout of objects |
US6199046B1 (en) * | 1997-07-29 | 2001-03-06 | Adsura Pty Ltd. | Method system and article of manufacture for performing real time currency conversion |
US6219787B1 (en) * | 1997-12-22 | 2001-04-17 | Texas Instruments Incorporated | Method and apparatus for extending security model to native code |
US6173404B1 (en) * | 1998-02-24 | 2001-01-09 | Microsoft Corporation | Software object security mechanism |
JP3955378B2 (ja) * | 1998-03-20 | 2007-08-08 | 株式会社野村総合研究所 | データアクセス制御を行うデータ通信システム |
US6850893B2 (en) * | 2000-01-14 | 2005-02-01 | Saba Software, Inc. | Method and apparatus for an improved security system mechanism in a business applications management system platform |
AUPP660298A0 (en) * | 1998-10-20 | 1998-11-12 | Canon Kabushiki Kaisha | Apparatus and method for preventing disclosure of protected information |
KR20010034000A (ko) | 1998-11-10 | 2001-04-25 | 요트.게.아. 롤페즈 | 저작권 보호를 위해 소프트웨어 객체로서 제공된 콘텐트 |
US6704873B1 (en) * | 1999-07-30 | 2004-03-09 | Accenture Llp | Secure gateway interconnection in an e-commerce based environment |
US7200230B2 (en) * | 2000-04-06 | 2007-04-03 | Macrovision Corporation | System and method for controlling and enforcing access rights to encrypted media |
US20020103942A1 (en) * | 2000-06-02 | 2002-08-01 | Guillaume Comeau | Wireless java device |
US7093298B2 (en) * | 2001-08-30 | 2006-08-15 | International Business Machines Corporation | Apparatus and method for security object enhancement and management |
JP3950010B2 (ja) * | 2002-05-17 | 2007-07-25 | 株式会社エヌ・ティ・ティ・ドコモ | データ処理装置、プログラムおよび記録媒体 |
JP4629304B2 (ja) * | 2002-10-30 | 2011-02-09 | 株式会社エヌ・ティ・ティ・ドコモ | 通信装置、プログラムおよび記録媒体 |
-
2002
- 2002-05-17 JP JP2002143608A patent/JP3950010B2/ja not_active Expired - Fee Related
-
2003
- 2003-05-16 AU AU2003235331A patent/AU2003235331A1/en not_active Abandoned
- 2003-05-16 WO PCT/JP2003/006099 patent/WO2003098442A1/ja active Application Filing
- 2003-05-16 US US10/514,685 patent/US7818815B2/en not_active Expired - Fee Related
- 2003-05-16 EP EP03723394A patent/EP1507211A4/en not_active Ceased
- 2003-05-16 TW TW092113375A patent/TWI239745B/zh not_active IP Right Cessation
- 2003-05-16 CN CNB038097060A patent/CN1308850C/zh not_active Expired - Fee Related
-
2009
- 2009-02-25 US US12/392,705 patent/US8087078B2/en not_active Expired - Fee Related
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001043176A (ja) * | 1999-06-15 | 2001-02-16 | Sun Microsyst Inc | 小フットプリント・デバイス・アプリケーション用の高性能ブックマーク |
JP2001350664A (ja) * | 2000-06-07 | 2001-12-21 | Nippon Telegr & Teleph Corp <Ntt> | 情報カプセル管理方法及び情報カプセル管理プログラムを格納した記憶媒体 |
Non-Patent Citations (8)
Title |
---|
"i Appli contents kaihatsu guid for DoJa-3.0 shosai-hen", NTT DOCOMO, INC., 17 April 2003 (2003-04-17), XP002972303, Retrieved from the Internet <URL:http://www.nttdocomo.co.jp/p_s/imode/java/pdf/jguidefordoja3_0_030417.pdf> [retrieved on 20030806] * |
"The Cryptolope Live! Product", IBM CRYPTOLOPE LIVE. GENERAL INFORMATION GUIDE, 1997, pages 1 - 26 |
GONG L, JAVA SECURITY ARCHITECTURE (JDK 1.2), VERSION 1.0, 6 December 1998 (1998-12-06) |
MARC A KAPLAN, IBM CRYPTOLOPES, SUPERDISTRIBUTION AND DIGITAL RIGHTS MANAGEMENT, 30 December 1996 (1996-12-30) |
OAKS S: "Java Security, THE DEFAULT SANDBOX", JAVA SECURITY, May 2001 (2001-05-01) |
SCOTT OAKS, TRANSLATED UNDER THE SUPERVISION OF AKIO SHIMADA: "Java Security", 28 November 2001, KABUSHIKI KAISHA ORAIRI JAPAN, XP002972302 * |
TETSU YAMATO: "Ketai yogo no kiso chisiki dai 143 kai: i appli DX towa", IMPRESS CORP., 13 May 2003 (2003-05-13), XP002972304, Retrieved from the Internet <URL:http://k-tai.impressco.jp/cda/article/keyword/13956.html> [retrieved on 20030513] * |
TETSUYA KAKU, MASAHIRO YAMADA, HIROAKI ITO: "Hajimete no i mode Java programming", NIKKEI BUSINESS PUBLICATIONS, INC., 26 March 2001 (2001-03-26), pages 30 - 41, XP002972301 * |
Also Published As
Publication number | Publication date |
---|---|
CN1308850C (zh) | 2007-04-04 |
JP3950010B2 (ja) | 2007-07-25 |
JP2003332978A (ja) | 2003-11-21 |
US20050235291A1 (en) | 2005-10-20 |
US7818815B2 (en) | 2010-10-19 |
US20090193515A1 (en) | 2009-07-30 |
EP1507211A4 (en) | 2007-12-05 |
TW200400742A (en) | 2004-01-01 |
EP1507211A1 (en) | 2005-02-16 |
AU2003235331A1 (en) | 2003-12-02 |
US8087078B2 (en) | 2011-12-27 |
TWI239745B (en) | 2005-09-11 |
CN1650273A (zh) | 2005-08-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4629304B2 (ja) | 通信装置、プログラムおよび記録媒体 | |
US8087078B2 (en) | Communication device | |
EP1465039B1 (en) | Content delivery method and content delivery system | |
TWI236298B (en) | Application level access privilege to a storage area on a computer device | |
US20120304310A1 (en) | Secure execution of unsecured apps on a device | |
CN103455520A (zh) | 安卓数据库访问的方法及设备 | |
JP2002041170A (ja) | プログラム実行制御装置 | |
CN109687974B (zh) | Apk验证方法、装置、移动终端及可读存储介质 | |
KR20150026656A (ko) | 응용프로그램 관리 방법 및 그 전자 장치 | |
JP2003198718A (ja) | 通信端末、コンテンツの使用制限方法およびプログラムの実行制限方法 | |
JP2003337630A (ja) | 通信端末、プログラム、記録媒体、通信端末のアクセス制御方法およびコンテンツの提供方法 | |
JP2004302543A (ja) | 受信装置およびプログラム | |
JP4612010B2 (ja) | データ処理装置、プログラムおよび記録媒体 | |
TWI244615B (en) | Terminal device and computer readable medium | |
JP4358478B2 (ja) | 通信端末のアクセス制御方法、コンテンツの提供方法、通信システムおよび中継装置 | |
JP4680485B2 (ja) | 端末装置、プログラムおよび記録媒体 | |
JP4652660B2 (ja) | 端末装置、プログラムおよび記録媒体 | |
KR100611119B1 (ko) | Drm 기반의 wipi 컨텐츠 서비스 방법 및 장치 | |
JP2004126736A (ja) | 通信端末及び通信制御方法 | |
KR101260759B1 (ko) | 네이티브 라이브러리 접근 제어장치 및 방법 | |
CN112464222A (zh) | 安全设备、对应的系统、方法和计算机程序产品 | |
JP2005173939A (ja) | 電子機器、受信装置およびプログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AU BR CA CN ID IN KR NO NZ PH PL SG US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2003723394 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 20038097060 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2003723394 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10514685 Country of ref document: US |