WO2005059759A1 - 通信端末 - Google Patents
通信端末 Download PDFInfo
- Publication number
- WO2005059759A1 WO2005059759A1 PCT/JP2004/019152 JP2004019152W WO2005059759A1 WO 2005059759 A1 WO2005059759 A1 WO 2005059759A1 JP 2004019152 W JP2004019152 W JP 2004019152W WO 2005059759 A1 WO2005059759 A1 WO 2005059759A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- stored
- message
- mobile phone
- content
- program
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 52
- 230000002596 correlated effect Effects 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 15
- 238000000034 method Methods 0.000 description 14
- 238000010295 mobile communication Methods 0.000 description 14
- 230000004044 response Effects 0.000 description 13
- 238000012545 processing Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 238000012217 deletion Methods 0.000 description 3
- 230000037430 deletion Effects 0.000 description 3
- 239000004973 liquid crystal related substance Substances 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003213 activating effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
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]
-
- 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
-
- 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/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
- H04M1/72436—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for text messaging, e.g. SMS or e-mail
Definitions
- the present invention relates to a technology for managing content stored in a communication terminal.
- a mobile phone compliant with IMT-2000 International Mobile Telecommunication 2000
- IMT-2000 International Mobile Telecommunication 2000
- IMT-2000 International Mobile Telecommunication 2000
- UIM User Identity Module
- This UIM is issued by a telecommunications carrier operating a mobile communication network to subscribers who have signed up for a subscription. (Assigned telephone number).
- the UIM owner attaches the UIM to the mobile phone, the mobile phone can communicate using the contractor information in the UIM.
- a mobile phone that complies with IMT-200000 can also perform data communication.
- Some of these telephones communicate with a WWW (World Wide Web) server device connected to the Internet, and various data and application programs (such programs and data are simply referred to as " Some contents can be acquired and stored in a storage unit such as a nonvolatile memory, and the acquired contents can be used. Content managers sometimes update the content to be distributed. If the WWW server device updates the content to be distributed, it may be necessary to update the content before distribution already distributed to the mobile phone.
- a server device that distributes the content stores a telephone number of the mobile phone to which the content is provided, and transmits the content to the mobile phone using the telephone number.
- a technique of updating a content stored in a mobile phone by transmitting a message instructing an update for example, see Japanese Patent Application Laid-Open No. 11-25017).
- the www server device obtains the telephone number of the corresponding mobile phone, sends a message to the mobile phone specified by the phone number, and attempts to delete the content from the mobile phone.
- the user of the mobile phone obtains the content from the WWW server device using his own mobile phone (for example, A), stores the content in the mobile phone A, and stores the same content.
- his own mobile phone for example, A
- you have borrowed another person's mobile phone for example, B
- the message transmitted from the WWW server device is transmitted to another person's mobile phone B equipped with the UIM, and the content downloaded to the other person's mobile phone B is deleted.
- the content that should be deleted and stored in the mobile phone A to which the content has been downloaded is not deleted, which is contrary to the intention of the operator of the WWW server device.
- the person who lent the mobile phone B would be disadvantaged.
- the present invention has been made in view of the above-described circumstances, and in a communication terminal using UIM, a message indicating that the content cannot be used is not a communication terminal that stores the content that should be unusable.
- a communication terminal or program that, when received by another communication terminal that stores the same content, does not disable the content stored in the storage unit of the communication terminal that received the message. And a recording medium. Disclosure of the invention
- the present invention provides mounting means for mounting a module that stores a user identifier that is an identifier used for communication on a communication network and uniquely identifies a user; Receiving means for receiving a message indicating that the content stored by the means is unusable; interpreting means for interpreting the content of the message received by the receiving means; acquiring the user identifier from the module; Determining means for determining whether or not the obtained user identifier is stored in the storage means in association with the content which is made unusable by the message interpreted by the interpreting means; The content which is made unusable by the message is stored in association with the user identifier obtained from the module. Only when it is determined by the determining means that the message is interpreted, the content which is disabled by the message interpreted by the interpreting means based on the content of the message interpreted by the interpreting means is disabled. And a first control means for controlling the storage means.
- the communication terminal when receiving a message indicating that the content is unusable, interprets the content of the received message.
- the communication terminal acquires a user identifier from a module storing a user identifier that uniquely identifies the user on the communication network, and the acquired user identifier is interpreted by the interpreting means. It is determined whether or not the content is stored in the storage unit in association with the content which is made unusable by the message.
- the communication terminal is only required when the determining means determines that the content which is disabled by the message interpreted by the interpreting means is stored in association with the user identifier acquired from the module. Based on the content of the message interpreted by the interpreting means, the content made unusable by the message interpreted by the interpreting means is disabled.
- a message stating that the content is unusable is issued. , Not to the communication terminal that stores the content to be disabled, but to other communication terminals that store the same content Even if the content is received, the content stored in the storage unit of the communication terminal that has received the message can not be disabled.
- FIG. 1 is a diagram illustrating an overall configuration of a communication system according to an embodiment of the present invention.
- FIG. 2 is a diagram exemplifying a page provided by the server 500 according to the embodiment.
- FIG. 3 is a diagram exemplifying a format of a customer table T B1 stored in the server device 500 according to the embodiment.
- FIG. 4 is a flowchart illustrating a processing flow when the server 500 according to the embodiment transmits a management message.
- FIG. 5 is a diagram illustrating a hardware configuration of the mobile phone 100 according to the embodiment.
- FIG. 6 is a diagram exemplifying a format of a program list table TB2 stored in the UIM 109 mounted on the mobile phone 100 according to the embodiment.
- FIG. 7 is a diagram exemplifying a format of a program management table TB3 stored in the nonvolatile memory 105 of the mobile phone 100 according to the embodiment.
- FIG. 8 is a flowchart illustrating an example of a flow of a process performed when the CPU 108 of the mobile phone 100 according to the embodiment receives the management message.
- FIG. 9 is a flowchart illustrating a flow of processing performed when the access controller is implemented in the mobile phone 100 according to the embodiment.
- FIG. 10 is a diagram for describing a first operation example of the embodiment.
- FIG. 11 is a diagram for explaining a second operation example of the embodiment.
- FIG. 12 is a diagram for explaining a third operation example of the embodiment.
- FIG. 13 is a diagram illustrating a format of a customer table used in a modification of the embodiment.
- FIG. 1 is a diagram illustrating an overall configuration of a communication system 10 according to an embodiment of the present invention.
- the mobile phones 100-1 and 100-2 and the server device 500 are required. (Because the configuration of the mobile phone 100-1 and the mobile phone 100-2 is the same, hereafter, especially when there is no need to distinguish individual mobile phones, the mobile phone 10 0).
- the mobile communication network 2000 is, for example, a communication network conforming to IMT-2000.
- the mobile communication network 200 provides a telephone service and a data communication service to a user who has made a subscription contract with a communication carrier operating the mobile communication network 200.
- the mobile communication network 200 is composed of a radio base station that performs radio communication with a mobile phone, an exchange connected to the radio base station, and a gateway exchange connected to the exchange and the gateway server device 300 (all of them). (Not shown).
- the gateway server device 300 interconnects the mobile communication network 200 and the Internet network 400.
- the gateway server device 300 is a protocol used in the mobile communication network 200 when performing packet communication between the internetwork 400 and the mobile communication network 200. It performs mutual conversion between the Internet 400 and TCPZIP (Transmission Control Protocol / Internet Protocol), which is a protocol used as a standard in the Internet 400.
- TCPZIP Transmission Control Protocol / Internet Protocol
- the mobile phone 100 is a mobile phone conforming to IMT-2000.
- the mobile phone 100 is capable of performing packet communication, and is connected to the Internet 4 via a mobile communication network 2000, a gateway server apparatus 300, and an Internet network 400. Communication can be performed with the server 500 connected to 00.
- the mobile phone 100 is owned by a person who has made a subscription contract with the carrier operating the mobile communication network 200.
- the server 500 has the same function as a general WWW server, Connected to the Internet 400.
- the server device 500 has a domain name “aaa.co.jp”.
- the server device 500 stores server software for causing the server device 500 to function as a general WWW server device.
- the server device 500 starts the server software, the server device 500 is given a function as a general WWW server device, and can perform communication based on, for example, HTTP (HyperText Transfer Protocol).
- HTTP HyperText Transfer Protocol
- the server device 500 stores two text files (hereinafter abbreviated as HTML files) described in accordance with HTML (HyperText Markup Language).
- HTML files One is an HTML file (hereinafter abbreviated as an AAA file) for providing the page P10 illustrated in FIG. 2 when interpreted by a WWW browser.
- the file name of the AAA file is “aaa.html”, and the URL indicating the storage location of the AAA file is “http: ⁇ ⁇ .abc.co.jp / aaa.html”.
- the other is an HTML file (hereinafter abbreviated as BBB file) for providing the page P11 illustrated in FIG. 2 when interpreted by a WWW browser.
- the file name of the BBB file is “bbb.html”, and the URL indicating the storage location of the BBB file is “http: @ www.abc.co.jp / bbb.htmlj.
- the file name of this application program is “abc” and the URL is “http: @ www.abc.co.jp / abc”.
- the server device 500 has a customer table TB1, a CG whose file name is “input, cgi” and whose URL is “http: @ www.abc.co.jp / input.cgi”. I remember the program.
- the page 10 file contains the telephone number entered in the text box BX 1 shown in Figure 2 and the CGI program ⁇ input.input '' when the operation of clicking the ⁇ Next '' button on page 10 is performed.
- HTTP request message using the POST method with the cgij URL as a parameter (hereinafter abbreviated as HTTP request) Is generated by the CPU 108.
- the CPU 108 sends an HTTP request using the GET method for obtaining the abbreviated program “abc” to the BBB file. It is written to generate.
- FIG. 3 is a diagram illustrating a format of the customer table TB1.
- the customer table TBI includes, in the past, a telephone number of a party to whom content has been distributed in the past and a data indicating the management status of the application program at the partner (hereinafter, abbreviated as management data). ) Are stored in association with each other.
- server device 500 executes the CGI program specified by the URL. Execute.
- the server device 500 stores the telephone number included in the HTTP request and stores it in the customer table TB1 in association with the management data.
- server device 500 generates an HTTP response message (hereinafter abbreviated as HTTP response) containing the BBB file, and transmits this response to mobile phone 100 that has transmitted the HTTP request.
- HTTP response an HTTP response message
- FIG. 4 is a flowchart illustrating the flow of processing when the server device 500 transmits the management message to the mobile phone 100.
- the configuration of the server device 500 is a general computer device. It is the same as the device. [1-3. Mobile phone configuration]
- FIG. 5 is a block diagram illustrating a hardware configuration of the mobile phone 100. As shown in FIG. 5, each unit of the mobile phone 100 is connected to a bus 101, and data is exchanged between the units via the bus 101.
- the communication unit 102 has a function as a communication interface, and forms a mobile communication network 200 via an antenna (not shown) under the control of a CPU (Central Processing Unit) 108. Wireless communication is performed with a wireless base station. Communication section 102 transmits a signal output from CPU 108 to the radio base station, and outputs a signal transmitted from the radio base station to CPU 108.
- the operation unit 103 has a plurality of keys, such as a numeric keypad, not shown. When the user of mobile phone 100 presses a key on operation unit 103, a signal indicating the pressed key is output from operation unit 103 to CPU 108.
- the display unit 104 has, for example, a control circuit for controlling the display of a liquid crystal display and a liquid crystal display (not shown). The display unit 104 operates a character or graphic screen and the mobile phone 100 under the control of the CPU 108. The menu screen etc. of is displayed on the liquid crystal display.
- the configuration of the UI Ml 09 is the same as that of a general computer device, and includes a CPU, a ROM (Read Only Memory), a RAM (Random Access Memory), and a communication interface for communicating with the CPU 108. And a non-volatile memory (both not shown).
- the non-volatile memory of the UI Ml 09 stores a telephone number “0 * 0-XXXX-YYYY” given to a subscriber by a communication operator operating the mobile communication network 200.
- the nonvolatile memory of the UI Ml 09 stores a program list table TB2.
- FIG. 6 is a diagram illustrating a format of the program list table TB2. As shown in FIG.
- the program list table TB2 contains the file name of the application program downloaded from the server device 500 when the UI Ml 09 was attached to the mobile phone 100, and the corresponding file name. Stored in association with application program management data It is.
- OS Operating System
- OS Operating System
- the CPU of the UIM 109 reads the OS software from the ROM and starts up.
- the UI Ml 09 communicates with the CPU 108 via the communication interface and the bus 101, and controls the non-volatile memory of the UIM 109 in accordance with an instruction from the CPU 108.
- the non-volatile memory 105 stores data for controlling the mobile phone 100 and application programs downloaded from the server device 500.
- the nonvolatile memory 105 stores a program management table TB3.
- FIG. 7 is a diagram illustrating a format of the program management table TB3. As shown in FIG. 7, the program management table TB3 stores the file name of the application program downloaded from the server device 500 and the UIM109 attached to the mobile phone 100 when the application program was downloaded. The stored telephone numbers are stored in association with each other.
- the ROM 106 stores, for example, OS software for controlling each unit of the mobile phone 100, a browser program for realizing a WWW browser capable of interpreting HTML, and the like. Also, the ROM 106 interprets a management message transmitted from the server device 500 and controls the nonvolatile memory 105 and the UI Ml 09 to implement an access controller, which is an application that controls the CPU 108, on the CPU 108 (hereinafter, referred to as a program). Control program). Details of this access controller will be described later.
- the CPU 108 uses the RAMI 07 as a work area, reads OS software from the ROM 106, and starts up.
- the CPU 108 executing the OS software performs a process according to a signal input to the CPU 108. For example, when the user of the mobile phone 100 presses a key included in the operation unit 103, the CPU 108 instructs the user based on a signal output from the operation unit 103 and a screen displayed on the display unit 104. And perform processing according to the user's instructions.
- the CPU 108 reads out the control program from the ROM 106 and activates it.
- FIG. 8 and FIG. 9 are flowcharts illustrating the flow of processing performed by the CPU 108 implementing the access controller.
- FIG. 8 is a flowchart illustrating a flow when the CPU 108 that realizes the access controller processes the management message.
- the CPU 108 interprets the management message, controls the UIM 109 and the nonvolatile memory 105 based on the content of the management message, deletes the application program stored in the nonvolatile memory 105, and executes the program management table TB. Delete the data stored in 3 and add / change / delete the data to / from the program list table TB2 stored in UIM109.
- FIG. 9 is a flowchart illustrating an example of the flow of processing performed when the access controller is implemented.
- the CPU 108 obtains a telephone number from the UIM 109.
- the CPU 108 reads out the file name of the application program stored in association with the telephone number acquired in the program management table TB3, and requests management data of this file name. Is sent to UI Ml 09 to obtain management data.
- the CPU 108 controls the nonvolatile memory 105 and the UIM 109 based on the acquired management data.
- the management data is “delete”
- the file name specified when the management data was read is deleted from the program management table TB3, and the application program specified by this file name is stored in the nonvolatile memory 105.
- Remove When the control of the non-volatile memory 105 is completed, the CPU 108 instructs to delete the file name specified when the management data is read out and the management data stored in association with the file name. Generate a message and send it to UI Ml 09. When UI Ml 09 receives this message, the program list table TB 2 Then, the file name and the management data instructed to be deleted are deleted.
- the file name of the program When the file name of the program is stored in the program management table TB3, the file name of the downloaded application program and the management data “usable” are included, and the included file name and the management file are included. It generates a message requesting that it be associated and stored, and sends it to UIM109. Upon receiving this message, the UIM 109 stores the file name and management data in the program list table TB2 in association with each other. As described above, the configuration of the mobile phone 100 is the same as that of a general computer device.
- first operation example of the present embodiment will be described with reference to FIG.
- an operation example when a user of the mobile phone 100 downloads a program stored in the server device 500 using the mobile phone 100-1 will be described.
- An operation example when a management message is transmitted from server device 500 to mobile phone 100-1 in which a program is stored will be described.
- the control program is started after the OS software is started, and the access controller is realized.
- use mobile phone 100-1 When the user performs an operation for realizing the WWW browser using the key of the operation unit 103 of the mobile phone 100-1, the WWW browser is realized.
- the GET method using the URL of the AAA file as a parameter is used.
- the HTTP request is transmitted to the server 500 (FIG. 10: step S101).
- server device 500 Upon receiving this HTTP request, server device 500 generates an HTTP response including the AAA file, and transmits it to mobile phone 100-1 (step S102).
- the CPU 108 of the mobile phone 100-1 receives the HTTP response, the AAA file included in the response is interpreted by the WWW browser, and the page P10 shown in FIG. You.
- the user who saw this page P 10 inputs the telephone number “0 * 0—XXXX—YYYYJ” assigned to the owner of the UI Ml 09 in the text box BX1 using the key of the operation unit 103,
- the CPU 108 stores the URL (http://www.abc.co.jp/input.cgi) written in the AAA file and the text box BXl
- An HTTP request is generated with the input telephone number and the parameters of the POST method as parameters, and the request is transmitted to server device 500 (step S103).
- server device 500 Upon receiving this HTTP request, server device 500 starts the CGI program specified by the URL included as a parameter, and stores the telephone number also included as a parameter in customer table TB1. Store. Next, server apparatus 500 generates an HTTP response including the BBB file, and transmits the response to mobile phone 100-1 (step S104).
- the WWW browser extracts “abc” included in the response, and extracts the extracted program with the telephone number stored in the UI Ml 09.
- the information is stored in the nonvolatile memory 105 in association with it.
- the CPU 108 associates the stored program file name “abc” with the telephone number “0 * O—XXXX—YYYYJ” stored in the UIM 109,
- the program is stored in the program management table TB 3.
- the CPU 108 stores the file name of the downloaded application program, generates a message requesting that the management data be set to “enabled”, and generates a UI Ml 09 Send to.
- the CPU 108 includes a file name of the downloaded program and the management data “usable”, and sends a message to the UI Ml 09 requesting that the file name and the management data be stored in association with each other. .
- the UI Ml 09 CPU stores the file name and the management data included in the message in the program list table TB 2 stored in the non-volatile memory of the UI Ml 09 .
- the mobile phone 100-1 downloads the application program from the server device 500
- the telephone number assigned to the person who downloaded the application program is stored in the server device 500.
- the mobile phone 100-1 also contains the downloaded application program, the file name of the downloaded application program, the telephone number stored in the UI Ml 09 installed when the application program was downloaded, and Is stored. Also, the file name of the downloaded application program is stored in the UIM 09 attached to the mobile phone 100-1 when the application program was downloaded.
- Application program downloaded by the owner of UI Ml 09 If the user does not pay the usage fee, the administrator of the server device 500 tries to delete the downloaded and stored application program. In order to delete the program stored in the mobile phone 100-1, the administrator of the server device 500 operates the keyboard of the server device 500 to delete the telephone number “0 * 0—XXXX” of the customer table TB1. — If the management data associated with “YYYY” is set to “delete”, a management message containing the file name “abc” of the application program distributed by the server device 500 and the management data “delete” is generated. Generated ( Figure 4: Step SA1).
- the telephone number “0 * 0—XXXX—YYYY” corresponding to the changed management data is read (step SA 2).
- the CPU 108 transmits the generated management message to the mobile phone equipped with the UIM 109 in which the telephone number is stored (see FIG.
- Step S A3 Step S A3
- Figure 10 Step S 107).
- the CPU 108 that implements the access controller is a server
- the CPU 108 searches the program management template TB3 stored in the nonvolatile memory 105 for the telephone number “0 * 0_XXXX—YYYY” stored in the UIMl09.
- the CPU 108 searches the file name stored in association with this telephone number for the file name "abc" included in the management message. Since the file name “abc” is stored in the program management table TB3 as shown in FIG. 7 by the above-described application program download operation, the CPU 108 obtains the file name “abc” from the program management table TB3. "Is deleted.
- the CPU 108 deletes the application program with the file name “abc” stored in association with the telephone number stored in the UI Ml 09 from the nonvolatile memory 105 (Step SB2).
- the CPU 108 generates a message indicating that the file name “abc” included in the management message and the management data stored in association with the management message are to be deleted (step SB 3), and sends the message to the UIM 109. Send it (step SB 4).
- the UI Ml 09 deletes the file name "abc" stored in the program list table TB2 and the management data stored in association with this file name.
- the mobile phone 100 interprets the abstract message transmitted from the server device using the access controller realized by the mobile phone 100, and stores the message in the nonvolatile memory 105 program and the UI Ml 09. And delete the day and night.
- Step S207 After the UIM109 has been replaced with the mobile phone 100-1 by downloading the application program from the mobile phone 100-1 (step S207), the administrator of the server device 500 deletes the program stored in the mobile phone 100-1.
- a management message including the file name “abc” of the application program distributed by the server device 500 and the management data “delete” is generated (FIG. 4: Step SA1). Changes when an administrative message is generated
- the phone number “0 * 0-XXXX-YYYYJ” associated with the management data is read out (step SA 2).
- the CPU 108 determines the mobile phone equipped with the UIM 109 storing the phone number.
- the generated management message is sent as the destination ( Figure 4: Step S A3, Figure 11: Step S 208).
- Step SB l When the mobile phone 100-2 equipped with UIML09 receives this management message, the message is interpreted by the implemented access controller.
- the CPU 108 in which the access controller is implemented interprets that the content of the management message sent from the server device 500 indicates that the application program whose file name is “abc” is to be deleted (FIG. 8). : Step SB l).
- the CPU 108 searches the program management table TB3 stored in the nonvolatile memory 105 for the telephone number “0 * 0—XXXX_YYYY” stored in the UIMl09.
- the CPU 108 searches the file name stored in association with this telephone number for the file name “abc” included in the management message.
- the application program is deleted. No (step SB 2).
- the CPU 108 generates a message requesting that the management data corresponding to the file name “abc” included in the management message be changed to “delete” (step SB3), and transmits the message to the UIM 109. (Step SB4).
- the 1111 ⁇ 109 PU changes the management data corresponding to the file name “abc” to “delete”.
- the access controller is realized after the OS software is started.
- the CPU 108 acquires the telephone number “0 * 0—XX XX—YYYY” from the UIM 109 (FIG. 9: step SC1).
- the CPU 108 stores the application program file stored in association with the obtained telephone number.
- the file name “abc” is read from the program management table TB3, and a message requesting the management data of the read file name is transmitted to the UI Ml 09 (step SC2).
- the UIM 109 reads out the management data “delete” stored in association with the file name “abc” and sends it to the CPU 108.
- the CPU 108 Upon receiving this management data (step SC3), the CPU 108 deletes the program file name “abc” stored in association with the obtained telephone number from the program management table TB3, and the mobile phone 100— The application program whose file name is “abc” stored in association with the telephone number “0 * 0—XXXX—YYYY” is deleted from the nonvolatile memory 105 of 1. Next, the CPU 108 generates a message to delete the deleted file name “a” and the management data stored in association with this file name, and transmits the message to the UIM 109. Upon receiving this message, UIM109 deletes the file name “abc” stored in the program list table TB2 and the management data stored in association with this file name (step SC4). ).
- the mobile phone 100 Rewrite the management data stored in 109 to “Delete”. Thereafter, when the UIM 109 is replaced with the mobile phone 100 in which the program specified in the message is stored, the UIM 109 is stored in the non-volatile memory 105 based on the management data stored in the UIM 109. Program is deleted.
- the mobile phone 100-1 equipped with the UI Ml 09 downloads the application program from the server device 500
- the mobile phone 100-1 stores the application program in association with the telephone number “0 * 0—AAA A—BBBB”.
- UI Ml 09 has been replaced with a mobile phone 100-2
- An operation example when a management message is transmitted will be described. Note that the operation of downloading the application program by the mobile phone 100-1 and the mobile phone 100-2 is the same as that of the first operation example, and thus the description thereof is omitted. In addition, the operation performed by the server device 500 is the same as that of the first operation example, and the description thereof is omitted.
- the mobile phone 100-2 receives a management message including the application program file name "a” and management data "delete”. (Step S302), this message is interpreted by the access controller realized by the CPU.
- the CPU 108 interprets that the content of the management message is an instruction to delete the application program whose file name is “abc” (FIG. 8: step SB1), the content is stored in the nonvolatile memory 105. Search the telephone number “0 * 0—XXXX—YYYY” stored in the UI Ml 09 in the program management table TB 3 that is stored.
- the CPU 108 searches the file name stored in association with this telephone number for the file name “abc” included in the management message.
- the nonvolatile memory 105 of the mobile phone 100-2 stores an application program whose file name is “abc”. However, in the program management table TB3, the file name “abc” is stored in association with the telephone number “0 * 0—AAA—BBBB”, but the telephone number “abc” stored in the UIM 109 is stored. The file name “abc” is not stored in association with “0 * 0—XXXX—YYYYY”. Therefore, the CPU 108 does not delete the application program (step SB2).
- the CPU 108 generates a message requesting that the management data corresponding to the file name “abc” included in the management message be changed to “delete” (step SB 3), Send it to UI Ml 09 (Step SB 4).
- the UI Ml09 CPU changes the management data corresponding to the file name “abc” to “delete”.
- the mobile phone 100 stores the application program having the same file name as the file name included in the management message, If the application program specified by the file name included in the message is not stored in association with the telephone number stored in the stored UIM l09, it is stored in the nonvolatile memory 105. Application programs that have been installed are not deleted. Even if a management message is sent while the user of the mobile phone 100-1 is borrowing and using another mobile phone 100-2 that stores the same application program, the mobile phone of the other mobile phone may not be used. It is possible not to delete the application program stored in the telephone 100-2.
- the management message transmitted from the server 500 may be not only a message for instructing deletion of the application program but also a message for stopping use of the application program.
- the server device 500 sends a management message including the management data to the mobile phone 100. .
- the management data of the program list table TB2 stored in the UIM 109 is changed to “suspended”.
- the OS realized by the CPU 108 receives an instruction to execute the application program, it checks the program list table TB2 of the UIM 109 and manages the management data of the application program instructed to be executed.
- the application program should not be executed without being read from the nonvolatile memory 105. According to such an embodiment, it is possible not only to delete the application program but also to stop using it while the application program is stored in the nonvolatile memory 105.
- the distribution from the server 500 is not limited to the application program. It may be image data for displaying an image, or music data for generating a musical sound.
- the UIM 109 has the same configuration as a general computer device. However, it may have only a storage unit. If the UIM 109 has only a storage unit, the CPU 108 may directly control the storage unit of the UIM.
- the server 500 transmits both the application program and the management message.
- the server that transmits the management message and the server that distributes the application program may be provided separately.
- the server 500 may distribute a plurality of application programs.
- the customer table TBI is modified so that the telephone number, the file name of the distributed program and the management data are associated with each other. It may be stored and managed.
- the application program may be a program described using Java (registered trademark) bytecode (hereinafter abbreviated as a Java program).
- a JaVa execution environment is required.
- the Java program is downloaded to the mobile phone 100, it is managed by the Java execution environment, and another application program deletes the Java program from the nonvolatile memory 105. I am not able to do it.
- the access controller interprets the management message and the Java execution environment can interpret the Java program.
- a message requesting deletion may be generated and passed to the Java runtime environment, and the Java runtime environment receiving this message may delete the Java program.
- the access controller transmits the management message transmitted from the server 500 Interpretation and control according to each software environment are performed, so the server device 500 does not need to send management messages to each software environment as a destination. It is possible to manage the distributed application program.
- Various software stored in the ROM 106 of the mobile phone 100 may be rewritable. As an example of a method of rewriting various software, the following method can be cited. For example, a rewritable flash ROM is used instead of the ROM 106.
- a recording medium such as a CD—ROM (Co Immediately Activated Disc Read Only Memory) containing various software
- the personal computer reads various software recorded on the CD-ROM, and transmits the read software to the mobile phone 100 connected by a cable.
- the mobile phone 100 that has received the software writes the received software into the flash ROM, thereby versioning various software stored in the mobile phone 100.
- various kinds of software stored in the mobile phone 100 can be rewritten such as version upgrade.
- various software may be rewritten by downloading via the Internet 400.
- the data when the application program is downloaded, the data is stored in the program management table TB3 and the message is transmitted to the UIM109 by the WWW browser.
- the download of the application program may be monitored, and the OS or the access controller may store the data in the program management table TB3.
- the mobile phone 100 downloads and stores the application program from the server device 500.
- the application program is installed in the mobile phone 100 in advance when the mobile phone 100 is manufactured, and the customer table TBI and Alternatively, the program list table TB2 and the program management table TB3 may be created before the mobile phone 100 is sold.
- the telephone number stored in the UIMl 09 is used as information for specifying the mobile phone 100 to which the management message is to be transmitted.
- the present invention is not limited to this. Identify the mobile phone 100 that sends the management message If the mobile communication network 200 can send a message to the mobile phone 100 based on this information, other information such as an e-mail address can be uniquely identified. May be.
- the user of the mobile phone 100 inputs the telephone number stored in the UIM l09 into the text box BX1 of the page P10, thereby storing the telephone number in the customer table TB1.
- the manner in which the server device 500 stores the telephone number in the customer table TB1 is not limited to this manner.
- the WWW browser realized by the mobile phone 100 describes the phone number stored in the UIM 109 in the header of the HT TP request, and the server device 500 requests the HT TP request. May be stored in the customer table TB1.
- the file name of the application program and the management data are stored in the UIM 109.
- the application program when the application program is downloaded, only the file name is stored. If the management data is not stored in association with the file name, the CPU 108 may determine that the application program can be used.
- Downloading of the application program from the server 500 and transmission of the management message are not limited to mobile phones. It may be a communication terminal that can use a mobile communication network, such as a PDA (Personal Digital Assistance) or a portable personal computer.
- a mobile communication network such as a PDA (Personal Digital Assistance) or a portable personal computer.
- the application program and the program management table TB3 are stored in the nonvolatile memory 105, but may be stored in a recording medium that is removable from the mobile phone 100. .
- the management message transmitted by the server 500 is not limited to the mode including the file name and the management data as described in the above-described embodiment. Other modes may be used as long as the instruction to delete the application program can be given and the application program to be deleted can be specified. For example, if only the file name of the application program is included in the management message May indicate that the application program is to be deleted, and in the case where other data is included in addition to the file name, the usage of the application program may be stopped.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2004800376705A CN1894945B (zh) | 2003-12-17 | 2004-12-15 | 一种通信终端的通信方法 |
EP04807509A EP1703407A4 (en) | 2003-12-17 | 2004-12-15 | COMMUNICATION TERMINAL |
US10/583,622 US7848780B2 (en) | 2003-12-17 | 2004-12-15 | Communication device for controlling the use of content |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2003-420188 | 2003-12-17 | ||
JP2003420188A JP4348173B2 (ja) | 2003-12-17 | 2003-12-17 | 通信端末 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2005059759A1 true WO2005059759A1 (ja) | 2005-06-30 |
Family
ID=34697239
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2004/019152 WO2005059759A1 (ja) | 2003-12-17 | 2004-12-15 | 通信端末 |
Country Status (6)
Country | Link |
---|---|
US (1) | US7848780B2 (ja) |
EP (1) | EP1703407A4 (ja) |
JP (1) | JP4348173B2 (ja) |
CN (1) | CN1894945B (ja) |
TW (1) | TWI283814B (ja) |
WO (1) | WO2005059759A1 (ja) |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
NZ533176A (en) * | 2001-12-25 | 2005-10-28 | Ntt Docomo Inc | Device and method for restricting content access and storage |
JP4348173B2 (ja) * | 2003-12-17 | 2009-10-21 | 株式会社エヌ・ティ・ティ・ドコモ | 通信端末 |
TWI238643B (en) * | 2004-06-01 | 2005-08-21 | Benq Corp | Method and mobile communication device capable of resuming operating function of temporarily disable SIM card |
JP4347255B2 (ja) * | 2005-04-13 | 2009-10-21 | アルパイン株式会社 | 端末装置、コンテンツの消去/転送制御システム及びコンテンツ消去制御方法 |
JP4778970B2 (ja) * | 2005-10-13 | 2011-09-21 | 株式会社エヌ・ティ・ティ・ドコモ | 携帯端末、アクセス制御管理装置及びアクセス制御管理方法 |
JP2007323568A (ja) * | 2006-06-05 | 2007-12-13 | Sharp Corp | 電子機器、認証装置、そのプログラムおよびコンピュータ読取り可能な記録媒体、認証システム、ならびに認証方法。 |
JP2009200845A (ja) * | 2008-02-21 | 2009-09-03 | Ntt Docomo Inc | 移動端末の記憶システム及びアクセス制御方法 |
US8280369B1 (en) * | 2009-01-13 | 2012-10-02 | Sprint Communications Company L.P. | Controlling application modes on a mobile device |
US8725122B2 (en) * | 2009-05-13 | 2014-05-13 | First Data Corporation | Systems and methods for providing trusted service management services |
JP5768451B2 (ja) * | 2011-04-07 | 2015-08-26 | 株式会社リコー | コンテンツ処理装置、コンテンツ処理方法及びコンテンツ処理装置の制御プログラム |
US8812603B2 (en) | 2012-05-11 | 2014-08-19 | Blackberry Limited | Method, system and apparatus for processing calendar events |
EP2662811A1 (en) * | 2012-05-11 | 2013-11-13 | BlackBerry Limited | Method, system and apparatus for processing calendar events |
JP5962211B2 (ja) * | 2012-05-25 | 2016-08-03 | 株式会社リコー | 位置情報管理システム、位置情報管理方法及び管理サーバ |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003040930A1 (fr) * | 2001-11-08 | 2003-05-15 | Ntt Docomo, Inc. | Dispositif de distribution d'informations, terminal de traitement d'informations, procede de stockage de contenu externe, procede de sortie de contenu externe, donnees de contenu, programme de controle de sortie, et systeme de distribution d'informations |
JP2003198718A (ja) * | 2001-12-25 | 2003-07-11 | Ntt Docomo Inc | 通信端末、コンテンツの使用制限方法およびプログラムの実行制限方法 |
JP2005086253A (ja) * | 2003-09-04 | 2005-03-31 | Vodafone Kk | 移動体通信端末 |
Family Cites Families (53)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
SE467559B (sv) * | 1991-04-12 | 1992-08-03 | Comvik Gsm Ab | Foerfarande vid telefonsystem |
SE470519B (sv) | 1992-11-09 | 1994-06-27 | Ericsson Telefon Ab L M | Anordning för tillhandahållande av tjänster såsom telefonkommunikation datakommunikation, etc omfattande en terminalenhet och en accessenhet |
US5282247A (en) * | 1992-11-12 | 1994-01-25 | Maxtor Corporation | Apparatus and method for providing data security in a computer system having removable memory |
JPH0865740A (ja) | 1994-08-18 | 1996-03-08 | Casio Comput Co Ltd | 携帯通信装置 |
FI101031B (fi) * | 1995-05-12 | 1998-03-31 | Nokia Telecommunications Oy | Tilaajalaitteen käyttöoikeuden tarkistus |
JP3513990B2 (ja) | 1995-07-07 | 2004-03-31 | カシオ計算機株式会社 | 通信端末 |
JP2000503154A (ja) * | 1996-01-11 | 2000-03-14 | エムアールジェイ インコーポレイテッド | デジタル所有権のアクセスと分配を制御するためのシステム |
US6038551A (en) * | 1996-03-11 | 2000-03-14 | Microsoft Corporation | System and method for configuring and managing resources on a multi-purpose integrated circuit card using a personal computer |
SE506584C2 (sv) * | 1996-05-13 | 1998-01-19 | Ericsson Telefon Ab L M | Förfarande och anordning vid övervakning av mobilkommunikationsenhet |
FR2748834B1 (fr) | 1996-05-17 | 1999-02-12 | Gemplus Card Int | Systeme de communication permettant une gestion securisee et independante d'une pluralite d'applications par chaque carte utilisateur, carte utilisateur et procede de gestion correspondants |
JPH09322239A (ja) | 1996-05-31 | 1997-12-12 | Nippon Shinpan Kk | 携帯電話等の移動体通信機の不正使用防止方法および該方法を実現する不正使用防止システム |
GB2317246B (en) * | 1996-09-13 | 2001-08-08 | Orange Personal Comm Serv Ltd | Data store |
WO1998018274A2 (de) * | 1996-10-23 | 1998-04-30 | Siemens Aktiengesellschaft | Verfahren zum ortsabhängigen anmelden eines mobilen endgerätes |
DE19708189C2 (de) * | 1997-02-28 | 2000-02-17 | Deutsche Telekom Mobil | Zu einem öffentlichen Mobilkommunikationssystem kompatibles nicht öffentliches Schnurlos-Kommunikationssystem |
US6047071A (en) * | 1997-04-15 | 2000-04-04 | Nokia Mobile Phones | Network-initiated change of mobile phone parameters |
JPH1125017A (ja) * | 1997-07-01 | 1999-01-29 | Sony Corp | 情報通信システム |
US6342010B1 (en) * | 1997-11-14 | 2002-01-29 | Russell Dale Slifer | Personalized wireless video game system |
US6141563A (en) * | 1997-12-16 | 2000-10-31 | Motorola, Inc. | SIM card secured subscriber unit |
JP3223870B2 (ja) | 1997-12-25 | 2001-10-29 | 株式会社デンソー | 電話装置 |
JPH11306118A (ja) | 1998-04-21 | 1999-11-05 | Yazaki Corp | インターネット端末装置及び画像表示制御方法 |
US6223290B1 (en) | 1998-05-07 | 2001-04-24 | Intel Corporation | Method and apparatus for preventing the fraudulent use of a cellular telephone |
JP3663058B2 (ja) | 1998-07-29 | 2005-06-22 | シャープ株式会社 | 移動体通信用端末装置 |
EA003432B1 (ru) * | 1998-09-15 | 2003-04-24 | Ин Тач Текнолоджиз Лимитед | Платформа расширенной связи и способ связи, использующий платформу |
JP2000099187A (ja) | 1998-09-24 | 2000-04-07 | Sanyo Electric Co Ltd | 無線通信システム、無線通信方法および記録媒体 |
FI107860B (fi) | 1999-02-09 | 2001-10-15 | Sonera Smarttrust Oy | Menetelmä ja järjestelmä tietoliikennejärjestelmässä ja tilaajaidentiteettimoduuli |
US6463534B1 (en) | 1999-03-26 | 2002-10-08 | Motorola, Inc. | Secure wireless electronic-commerce system with wireless network domain |
JP3283848B2 (ja) | 1999-04-20 | 2002-05-20 | エヌイーシーモバイリング株式会社 | 移動無線通信装置および通信許可方法 |
FI108604B (fi) * | 1999-04-28 | 2002-02-15 | Nokia Corp | Menetelmä matkaviestimen toiminteiden hallitsemiseksi |
CN1248143C (zh) * | 1999-08-10 | 2006-03-29 | 富士通株式会社 | 存储插件 |
US6445914B1 (en) * | 1999-09-08 | 2002-09-03 | Ericsson, Inc. | Method to perform subsidy protection for TDMA mobile stations |
KR20010050212A (ko) | 1999-09-13 | 2001-06-15 | 스테븐 디.피터스 | 메모리 카드에 기록된 파일에 대한 접근 제어 시스템 |
US7080037B2 (en) * | 1999-09-28 | 2006-07-18 | Chameleon Network Inc. | Portable electronic authorization system and method |
FR2799918B1 (fr) * | 1999-10-18 | 2002-04-05 | Bull Cp8 | Systeme et procede et de transmission de messages, et utilisation du systeme de transmission pour l'investigation de services fournis |
EP1107627A1 (en) | 1999-12-03 | 2001-06-13 | Siemens Aktiengesellschaft | A method for protecting user data stored in memory of a mobile communication device, particularly a mobile phone |
EP1113683A1 (fr) * | 1999-12-21 | 2001-07-04 | Koninklijke Philips Electronics N.V. | Protection d'un appareil radiotéléphonique contre le vol |
US6832230B1 (en) * | 1999-12-22 | 2004-12-14 | Nokia Corporation | Apparatus and associated method for downloading an application with a variable lifetime to a mobile terminal |
ES2288841T3 (es) * | 2000-02-11 | 2008-02-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Aparato, metodo y sistema para control de almacenamiento de un centro de servicios de mensajes cortos. |
EP1143688A1 (en) | 2000-03-02 | 2001-10-10 | Client Electronics GmbH | Mobile services on the basis of a smart card |
US6850777B1 (en) * | 2000-03-31 | 2005-02-01 | Motorola, Inc. | Method for providing a personal identification number to a subscriber identity module |
US6871063B1 (en) * | 2000-06-30 | 2005-03-22 | Intel Corporation | Method and apparatus for controlling access to a computer system |
DE60118122T2 (de) * | 2000-07-14 | 2006-08-24 | Ntt Docomo, Inc. | Standortsregistrationsverfahren mit Unterstützung für mehrere SIM Karten mit unterschiedlichen Funktionen |
JP4305593B2 (ja) | 2000-07-17 | 2009-07-29 | ソニー株式会社 | データ記録再生方法および装置、データ記録装置および方法 |
US6900320B2 (en) * | 2000-07-24 | 2005-05-31 | Matsushita Electric Industrial Co., Ltd. | Personal information control system |
JP2002135407A (ja) | 2000-10-30 | 2002-05-10 | Toshiba Corp | 通信端末装置および同通信端末装置における認証方法 |
GB2369205B (en) * | 2000-11-17 | 2005-02-02 | Personal Data Prot System Ltd | Personal data device and protection system and method for storing and protecting personal data |
US7987510B2 (en) * | 2001-03-28 | 2011-07-26 | Rovi Solutions Corporation | Self-protecting digital content |
DE10135527A1 (de) * | 2001-07-20 | 2003-02-13 | Infineon Technologies Ag | Mobilstation eines Mobilkommunikationssystems und Verfahren zum Zugreifen auf einen Dienst und/oder einen Datensatz im Bereitschaftsmodus der Mobilstation |
NZ533176A (en) * | 2001-12-25 | 2005-10-28 | Ntt Docomo Inc | Device and method for restricting content access and storage |
US7175078B2 (en) * | 2002-03-13 | 2007-02-13 | Msystems Ltd. | Personal portable storage medium |
JP4348173B2 (ja) * | 2003-12-17 | 2009-10-21 | 株式会社エヌ・ティ・ティ・ドコモ | 通信端末 |
JP4091908B2 (ja) * | 2003-12-18 | 2008-05-28 | 株式会社エヌ・ティ・ティ・ドコモ | 通信システム、通信端末装置および情報記憶モジュール |
JP2008301329A (ja) * | 2007-06-01 | 2008-12-11 | Renesas Technology Corp | 無線通信システム、simカード、移動通信端末およびデータの保証方法 |
KR20090011314A (ko) * | 2007-07-25 | 2009-02-02 | 삼성전자주식회사 | 이동 단말기와 그의 심 카드 표시 방법 |
-
2003
- 2003-12-17 JP JP2003420188A patent/JP4348173B2/ja not_active Expired - Fee Related
-
2004
- 2004-12-15 US US10/583,622 patent/US7848780B2/en not_active Expired - Fee Related
- 2004-12-15 TW TW093138978A patent/TWI283814B/zh not_active IP Right Cessation
- 2004-12-15 CN CN2004800376705A patent/CN1894945B/zh not_active Expired - Fee Related
- 2004-12-15 EP EP04807509A patent/EP1703407A4/en not_active Withdrawn
- 2004-12-15 WO PCT/JP2004/019152 patent/WO2005059759A1/ja active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003040930A1 (fr) * | 2001-11-08 | 2003-05-15 | Ntt Docomo, Inc. | Dispositif de distribution d'informations, terminal de traitement d'informations, procede de stockage de contenu externe, procede de sortie de contenu externe, donnees de contenu, programme de controle de sortie, et systeme de distribution d'informations |
JP2003198718A (ja) * | 2001-12-25 | 2003-07-11 | Ntt Docomo Inc | 通信端末、コンテンツの使用制限方法およびプログラムの実行制限方法 |
JP2005086253A (ja) * | 2003-09-04 | 2005-03-31 | Vodafone Kk | 移動体通信端末 |
Non-Patent Citations (1)
Title |
---|
NISHIZAKI T.ET AL: "Card vs keitai denwa jisedai ketai to sim.", CARDWAVE., vol. 14, no. 3, 10 February 2001 (2001-02-10), pages 30 - 33, XP008142220 * |
Also Published As
Publication number | Publication date |
---|---|
JP4348173B2 (ja) | 2009-10-21 |
JP2005184277A (ja) | 2005-07-07 |
US20070197201A1 (en) | 2007-08-23 |
CN1894945A (zh) | 2007-01-10 |
US7848780B2 (en) | 2010-12-07 |
TWI283814B (en) | 2007-07-11 |
TW200521685A (en) | 2005-07-01 |
EP1703407A4 (en) | 2012-08-01 |
EP1703407A1 (en) | 2006-09-20 |
CN1894945B (zh) | 2011-11-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR100440704B1 (ko) | 콘텐츠를 분배하기 위한 장치 및 방법 | |
KR100718068B1 (ko) | 어플리케이션에 의한 기억영역의 사용 관리 방법 | |
JP4141301B2 (ja) | 通信端末 | |
JP4598741B2 (ja) | 機能更新システム及び機能更新方法 | |
WO2003098432A1 (en) | Portable terminal, method, program, and storage medium for managing application start | |
WO2005059759A1 (ja) | 通信端末 | |
JP2004080245A (ja) | データ保管システム | |
JP4303101B2 (ja) | 通信端末およびプログラム | |
JP5029098B2 (ja) | ネットワークシステム、端末カスタマイズ方法およびカスタマイズサービス方法 | |
KR20020005127A (ko) | 이동통신 단말기의 응용 프로그램 갱신 방법 | |
KR100608150B1 (ko) | 무선인터넷 서비스 시스템을 위한 무선컨텐츠 다운로드시스템 및 그 방법 | |
JP4007936B2 (ja) | 制御サーバ装置 | |
JP4377317B2 (ja) | コンテンツ提供方法、サーバ及び移動体通信端末 | |
JP4323304B2 (ja) | アプリケーション識別方法および通信端末 | |
KR100583736B1 (ko) | 이동통신 단말기에 탑재된 자바 어플리케이션의 제어장치및 방법 | |
JP2006259849A (ja) | 携帯端末装置 | |
JP4138591B2 (ja) | 端末装置 | |
EP2446349B1 (en) | Method and program for initiating a second service in dependency of a first service | |
KR20100128948A (ko) | 애플리케이션 다운로드 서비스 시스템 및 그 방법 | |
JP2004126736A (ja) | 通信端末及び通信制御方法 | |
KR100838210B1 (ko) | 모바일 응용 프로그램 이용에 대한 정액 요금 서비스 제공방법 및 장치 | |
JP2004234345A (ja) | アプリケーションプログラム実行装置およびプログラム | |
KR20010099066A (ko) | 이동 전화기의 전화 번호 관리를 위한 네트웍 서비스 | |
JP2004118603A (ja) | データ編集装置、データ編集システム及びデータ編集プログラム | |
JP2002351667A (ja) | サービス提供システム及びそのアプリケーション管理方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200480037670.5 Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2004807509 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 2004807509 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10583622 Country of ref document: US Ref document number: 2007197201 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 10583622 Country of ref document: US |