Source: http://www.google.com/patents/US7848780?dq=6004266
Timestamp: 2014-12-25 02:03:44
Document Index: 473504379

Matched Legal Cases: ['Application No. 02028128', 'Application No. 2001', 'Application No. 2', 'Application No. 200207356', 'Application No. 20026210', 'Application No. 10', 'Application No. 1']

Patent US7848780 - Communication device for controlling the use of content - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsIn a communication terminal using UIM, when a message disabling use of a content is received not by a communication terminal containing the content to disabled, but by another communication terminal containing the same content, the content stored in a storage unit of the communication terminal which...http://www.google.com/patents/US7848780?utm_source=gb-gplus-sharePatent US7848780 - Communication device for controlling the use of contentAdvanced Patent SearchPublication numberUS7848780 B2Publication typeGrantApplication numberUS 10/583,622Publication dateDec 7, 2010Filing dateDec 15, 2004Priority dateDec 17, 2003Fee statusPaidAlso published asCN1894945A, CN1894945B, EP1703407A1, EP1703407A4, US20070197201, WO2005059759A1Publication number10583622, 583622, US 7848780 B2, US 7848780B2, US-B2-7848780, US7848780 B2, US7848780B2InventorsSatoshi Washio, Hiroshi Kawabata, Tomoo YamaguchiOriginal AssigneeNtt Docomo, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (58), Non-Patent Citations (18), Referenced by (3), Classifications (25), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetCommunication device for controlling the use of contentUS 7848780 B2Abstract In a communication terminal using UIM, when a message disabling use of a content is received not by a communication terminal containing the content to disabled, but by another communication terminal containing the same content, the content stored in a storage unit of the communication terminal which has received the message is not disabled. Mobile phone 100-1 using UIM stores a program in correlation with a telephone number stored in the UIM. When mobile phone 100-1 receives a management message to delete a program, mobile phone 100-1 interprets the content of the management message. Mobile phone 100-1 obtains a telephone number from the UIM, and deletes the content stored in correlation with the telephone number according to the management message interpreted.
based upon the content management table stored in the module, deleting the content. Description
Mobile phones in conformity with the IMT-2000 (International Mobile Telecommunication 2000) standard are configured in a way that an IC card, that is referred to as UIM (User Identity Module), is attachable to and removable from the mobile phone. UIM is issued to a subscriber to a communication carrier operating a mobile communication network. The UIM stores subscriber information of a subscriber, for example, a phone number assigned to the subscriber by the communication carrier. When the owner of UIM attaches the UIM to a mobile phone, the mobile phone is enabled to communicate using the subscriber information stored in the UIM. Mobile phones conforming to the IMT-2000 standard are also capable of performing data communications. Some of them are also capable of communicating with a WWW (World Wide Web) server apparatus connected to the Internet, obtaining various data and/or various application programs, or the like (in the following, the data and programs will be referred to simply as �content�), and storing the obtained content in a storage unit such as a non-volatile memory, and making use of the obtained content.
SUMMARY OF THE INVENTION To accomplish its object, the present invention provides a communication terminal having: attachment means for attaching a module, the module storing a user identification for use in a communication network; storage means that stores a content in correlation with the user identification; receiving means that receives a message to disable a use of the content stored in the storage means; interpreting means that interprets the message received by the receiving means; determining means that obtains a user identification from the module, and determines whether the user identification obtained is stored in the storage means in correlation with the content that is specified to be disabled by the message interpreted by the interpreting means; and first control means that controls the storage means according to the content of the message interpreted by the interpreting means to disable a use of the content that is specified to be disabled by the message interpreted by the interpreting means, only when the determining means has determined that the content that is specified to be disabled by the message interpreted by the interpreting means is stored in the storage means in correlation with the user identification obtained from the module.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 illustrates a whole configuration of a communication system according to an embodiment of the present invention.
DESCRIPTION OF THE PREFERRED EMBODIMENTS In the following description, embodiments of the present invention will be described with reference to drawings.
1. Configuration 1-1. General configuration
Server apparatus 500 has similar functions to those of a general WWW server apparatus, and is connected to Internet 400. Domain name �aaa.cojp� is assigned to server apparatus 500.
Server apparatus 500 stores two text files written in HTML (HyperText Markup Language). In the following, such text files will be referred to as HTML files. One is an HTML file which produces page P10 illustrated in FIG. 2 when interpreted by a WWW browser. In the following, this will be referred to as an AAA file. The filename of the AAA file is �aaa.html�. The URL indicating a storage location of the AAA file is �http://www.abc.cojp/aaa.html�. The other is an HTML file which produces page P11 illustrated in FIG. 2 when interpreted by a WWW browser. In the following, this will be referred to as a BBB file. The file name of the BBB file is �bbb.html�. The URL indicating a storage location of the BBB file is �http://www.abc.cojp/bbb.html�. Furthermore, server apparatus 500 stores an application program to be distributed to mobile phone 100. The filename of the application program is �abc�. The URL of the application program is �http://www.abc.co jp/abc�. Furthermore, server apparatus 500 stores client table TB1 and a CGI program. The filename of the CGI program is �input.cgi�. The URL of the program is �http://www.abc.cojp/input.cgi�.
Page P10 file is written so that CPU 108 generates an HTTP request message using a POST method including the telephone number input in text box BX1 shown in FIG. 2 and the URL of the CGI program �input.cgi� as parameters (In the following, this will be abbreviated as an HTTP request.), when a user clicks �NEXT� button in page P10. Furthermore, BBB file is written so that CPU 108 generates an HTTP request, using a GET method, of obtaining the application program �abc� when a user clicks �DOWNLOAD� button shown in FIG. 2.
When server apparatus 500 running the server software receives an HTTP request using a POST method and including the URL of the CGI program �input.cgi� as a parameter, server apparatus 500 executes the CGI program specified with the URL. Server apparatus 500 executes the CGI program �input.cgi�, and stores the telephone number included in the HTTP request in client table TB1 in correlation with management data. Next, server apparatus 500 generates an HTTP response message including the BBB file (In the following this will be referred to as an HTTP response), and transmits the response to the mobile phone 100, that has transmitted the HTTP request.
When an administrator of server apparatus 500 operates to change the management data in client table TB1 using a keyboard (not shown), a management message is generated that includes the filename �abc� of the application program that server apparatus 500 distributes, together with management data. When the management message is generated, a telephone number corresponding to the changed management data is read, and the management message is transmitted to mobile phone 100 attached with the UIM 109 storing the telephone number. As previously described, server apparatus 500 is configured in a similar manner to a general computer apparatus.
UIM 109 is configured similarly to a general computer apparatus, and includes a CPU, a ROM (Read Only Memory), a RAM (Random Access Memory), a communication interface for communicating with CPU 108, and a non-volatile memory. These components are not shown in the Figure. The non-volatile memory of UIM 109 stores the telephone number �0*0-XXXX-YYYY� assigned to a subscriber by the communication carrier operating mobile communication network 200. The non-volatile memory of UIM 109 also stores program list table TB2. FIG. 6 illustrates a format of program list table TB2. As shown in FIG. 6, program list table TB2 stores a filename of the application program that was downloaded from server apparatus 500 when UIM 109 was attached to mobile phone 100 in correlation with management data of the application program. ROM of UIM 109 stores OS (Operating System) software for controlling each component of UIM 109. When UIM 109 is attached to mobile phone 100 and power is supplied to UIM 109 from mobile phone 100, CPU of UIM 109 loads OS software from the ROM and executes the OS software. When the OS software is executed UIM 109 communicates with CPU 108 via the communication interface and bus 101, and controls the non-volatile memory of UIM 109 corresponding to instructions from CPU 108.
FIG. 9 is a flowchart illustrating an operational flow when access control is established. When access control is established, CPU 108 obtains a telephone number from UIM 109. When CPU 108 obtains the telephone number, CPU 108 reads a filename of the application program stored in program management table TB3 in correlation with the telephone number obtained, and attempts to obtain management data corresponding to the filename by transmitting a message to UIM 109 requesting the management data. When CPU 108 obtains the management data, CPU 108 controls non-volatile memory 105 and UIM 109 according to the management data obtained. For example, if the management data is �DELETE�, CPU 108 deletes the filename specified when the management data is read from program management table TB3, and deletes the application program specified with the filename from non-volatile memory 105. When CPU 108 finishes controlling non-volatile memory 105, CPU 108 generates a message to delete the filename specified when the management data is read and the management data stored in correlation with the filename, and transmits it to UIM 109. When UIM 109 receives the message, UIM 109 deletes the filename and management data that are specified to be deleted from program list table TB2.
When a user of mobile phone 100 presses down keys of operation unit 103 to use a WWW browser, a browser program is executed to establish a WWW browser. When the WWW browser is used to download an application program from a server apparatus connected to Internet 400, a filename of the downloaded program is stored in program management table TB3 in correlation with the telephone number stored in the attached UIM 109. Furthermore, the telephone number stored in UIM 109 attached is stored in non-volatile memory 105 in correlation with the downloaded application program. When the filename of the program is stored in program management table TB3, the program generates a message including the filename of the downloaded program and the management data �ENABLED�, and of requesting to store the filename included in correlation with the included management data, and transmits it to UIM 109. When UIM 109 receives the message, UIM 109 stores the filename in correlation with the management data in program list table TB2. As described, mobile phone 100 is configured in a similar manner to a general computer apparatus.
2. Working Examples Next, the first working example to the third working example of the present embodiment will be described.
2-1. First Working Example First, the first working example of the present embodiment will be described with reference to FIG. 10. In the first working example, a working example will be first described in which a user of mobile phone 100 downloads a program stored in server apparatus 500 using mobile phone 100-1. Then, a working example will be described in which a management message is transmitted from server apparatus 500 to mobile phone 100-1 storing the program.
When CPU 108 of mobile phone 100-1 receives the HTTP response, the AAA file included in the response is interpreted by the WWW browser as page P10 illustrated in FIG. 2 is displayed in display unit 104. When a user viewing page P10, inputs in text box BX1 a telephone number �0*0-XXXX-YYYY� assigned to an owner of the UIM 109 using keys of operation unit 103, and clicks �NEXT� button, CPU 108 generates an HTTP request including the URL (http://www.abc.cojp/input.cgi) described in the AAA file and the telephone number input in the text box BX1 as parameters of a POST method, and transmits the request to server apparatus 500 (Step S103).
When CPU 108 receives the HTTP response, page P11 illustrated in FIG. 2 is displayed. When a user viewing page P11 clicks �Download� button using keys of operation unit 103, CPU 108 generates an HTTP request including a URL (http://www.abc.cojp/abc) described in the BBB file as a parameter of a GET method, and transmits the request to server apparatus 500 (Step S105). Server apparatus 500 that has received the HTTP request generates an HTTP response including the program �abc� specified in the URL included as a parameter, and transmits the response to mobile phone 100-1 (Step S106).
When CPU 108 of mobile phone 100-1 receives the HTTP response, the �abc� included in the response is extracted by the WWW browser, and the extracted program is stored in non-volatile memory 105 in correlation with the telephone number stored in UIM 109. When CPU 108 stores the downloaded program in non-volatile memory 105, CPU 108 stores the filename �abc� of the stored program in program management table TB3 in correlation with the telephone number �0*0-XXXX-YYYY� stored in UIM 109. Next, CPU 108 stores the filename of the downloaded application program, and generates a message requesting change of the management data to �ENABLED�, and transmits it to UIM 109. Next, CPU 108 transmits a message including the filename of the downloaded program and the management data �ENABLED�, and requesting storing the filename in correlation with the management data to UIM 109. When CPU of UIM 109 receives the message, CPU stores the filename and the management data included in the message in program list table TB2 stored in non-volatile memory of UIM 109.
When an owner of UIM 109 does not pay a fee for use of the downloaded application program, the administrator of server apparatus 500 tries to delete the application program that has been downloaded and stored. When the administrator of server apparatus 500 sets the management data corresponding to the telephone number �0*0-XXXX-YYYY� in client table TB1 to �DELETE� by using the keyboard of server apparatus 500, so as to delete the program stored in mobile phone 100-1, a management message including the filename �abc� of the application program distributed by server apparatus 500 and the management data �DELETE� is generated (FIG. 4: Step SA1). When the management message is generated, the telephone number �0*0-XXXX-YYYY� corresponding to the changed management data is read (Step SA2). CPU 108 transmits the generated management message by addressing the mobile phone to which UIM 109 that stores the telephone number is attached (FIG. 4: Step SA3, FIG. 10: Step S107).
When mobile phone 100-1, to which UIM 109 is attached, receives the management message, the message is interpreted by the established access control. CPU 108, by which the access control is established, interprets that the content of the management message transmitted from server apparatus 500, instructs deletion of the application program with the filename �abc� (FIG. 8: Step SB1).
Next, CPU 108 seeks the telephone number �0*0-XXXX-YYYY�, that is stored in UIM 109, in program management table TB3 stored in non-volatile memory 105. When CPU 108 finds the corresponding telephone number, CPU 108 seeks the filename �abc� included in the management message from filenames stored in correlation with the telephone number. By the above-mentioned downloading operation of an application program, the filename �abc� is stored in program management table TB3 as shown in FIG. 7. Thus, CPU 108 deletes the filename �abc� from program management table TB3. Next, CPU 108 deletes the application program having the filename �abc� from non-volatile memory 105, wherein the filename is stored in correlation with the telephone number stored in UIM 109 (Step SB2).
Next, CPU 108 generates a message to delete the filename �abc� included in the management message and the management data stored in correlation with the management message (Step SB3), and transmits it to UIM 109 (Step SB4). When UIM 109 receives the message, UIM 109 deletes the filename �abc� stored in program list table TB2 and the management data stored in correlation with the filename.
2-2. Second Working Example Next, the second working example of the present embodiment will be described with reference to FIG. 11. In the second working example, UIM is moved from mobile phone 100-1 that has downloaded an application program from server apparatus 500, to mobile phone 100-2 that does not store the application program distributed by server apparatus 500; a management message is transmitted from server apparatus 500; and then, UIM 109 is moved again to be attached to mobile phone 100-1. Here, since the operation of mobile phone 100-1 of downloading an application program (FIG. 11: Steps S201-S206) is the same as that of the first working example, its description will be omitted.
After UIM 109 is moved from mobile phone 100-1 that has downloaded the application program to be attached to mobile phone 100-2 (Step S207), when the administrator of server apparatus 500 changes the management data corresponding to the telephone number �0*0-XXXX-YYYY� in client table TB1 to �DELETE� by using a keyboard of server apparatus 500, so as to delete the program stored in mobile phone 100-1, a message including the filename �abc� of the application program distributed by server apparatus 500 and the management data �DELETE� (FIG. 4: Step SA1). When the management message is generated, the telephone number �0*0-XXXX-YYYY� corresponding to the changed management data is read (Step SA2). CPU 108 transmits the generated management message by addressing the mobile phone attached with UIM 109 that stores the telephone number (FIG. 4: Step SA3, FIG. 11: Step S208).
When mobile phone 100-2 attached with UIM 109 receives the management message, the message is interpreted by the means of the established access control. When access control has been established, CPU 108 interprets that the content of the management message transmitted from server apparatus 500 is a deletion of the application program having the filename �abc� (FIG. 8: Step SB1).
First, CPU 108 searches a telephone number �0*0-XXXX-YYYY� in program management table TB3 stored in non-volatile memory 105 the telephone number �0*0-XXXX-YYYY� stored in UIM 109. When CPU 108 finds the corresponding telephone number, CPU 108 seeks the filename �abc� included in the management message from the filenames stored in correlation with the telephone number. As mentioned above, the filename �abc� and the application program having the filename �abc� are not stored in non-volatile memory 105 of mobile phone 100-2. Accordingly, no application programs are deleted (Step SB2).
Next, CPU 108 generates a message to change the management data corresponding to the filename �abc� included in the management message to �DELETE� (Step SB3), and transmits it to UIM 109 (Step SB4). When the CPU of UIM 109 receives the message, the CPU changes the management data corresponding to the filename �abc� to �DELETE�.
Next, the user attaches UIM 109 to mobile phone 100-1 (Step S209), and powers on the mobile phone, and access control is established after the OS software is executed. When access control is established on CPU 108 mobile phone 100-1, CPU 108 obtains a telephone number �0*0-XXXX-YYYY� from UIM 109(FIG. 9: Step SC1). Next, CPU 108 reads the filename �abc� of the application program stored in correlation with the telephone number obtained from program management table TB3, and transmits a message to request the management data corresponding to the obtained filename to UIM 109 (Step SC2). When UIM 109 receives the message, UIM 109 reads the management data �DELETE� stored in correlation with the filename �abc�, and transmits it to CPU 108.
When CPU 108 receives the management data (Step SC3), CPU 108 deletes the filename �abc� of the program stored in correlation with the telephone number obtained from program management table TB3, and deletes the application program stored in correlation with the telephone number �0*0-XXXX-YYYY� and having the filename �abc� from non-volatile memory 105 of mobile phone 100-1. Next, CPU 108 generates a message to delete the management data stored in correlation with the deleted filename �abc�, and transmits it to UIM 109. When UIM 109 receives the message, UIM 109 deletes the filename �abc� stored in program list table TB2 and the management data stored in correlation with the filename (Step SC4).
As described above, when a message to delete a program is transmitted from server apparatus 500 to mobile phone 100, in which the program is not stored in non-volatile memory 105, mobile phone 100 changes the management data stored in UIM 109 to �DELETE�. Then, when UIM 109 is attached to mobile phone 100 in which the program specified in the message is stored, the program stored in non-volatile memory 105 is deleted according to the management data stored in UIM 109.
2-3. Third Working Example Next, the third working example of the present embodiment will be described with reference to FIG. 12. In the third working example, mobile phone 100-1 attached with UIM 109 downloads an application program from server apparatus 500; the UIM 109 is moved to be attached to mobile phone 100-2 that stores the application program in correlation with a telephone number �0*0-AAAA-BBBB�; and then, a management message is transmitted from server apparatus 500. Here, since the operations of mobile phone 100-1 and mobile phone 100-2 of downloading an application program are the same as those of the first working example, their description will be omitted. Furthermore, since server apparatus 500 operates in a similar manner to that of the first working example, their description will be omitted.
After UIM 109 is attached to mobile phone 100-2 (Step S301), when a management message including the filename �abc� of the application program and the management data �DELETE� is received by mobile phone 100-2 (Step S302), the message is interpreted by means of the access control established on CPU 108. When CPU 108 interprets that the content of the management message is an instruction to delete the application program having the filename �abc� (FIG. 8: Step SB1), CPU 108 seeks the telephone number �0*0-XXXX-YYYY� stored in UIM 109 in program management table TB3 stored in non-volatile memory 105.
When CPU 108 finds a corresponding telephone number, CPU 108 seeks the management data corresponding to the filename �abc� included in the management message from the filenames stored in correlation with the telephone number. In non-volatile memory 105 of mobile phone 100-2, application program with the filename �abc� is stored. However, the filename �abc� is stored in program management table TB3 in correlation with the telephone number �0*0-AAAA-BBBB�, but the filename �abc� is not stored in correlation with the telephone number �0*0-XXXX-YYYY� that is stored in UIM 109. Accordingly, CPU 108 does not delete the application program (Step SB2). Next, CPU 108 generates a message to change the management message corresponding to the filename �abc� included in the management message to �DELETE� (Step SB3), and transmits it to UIM 109 (Step SB4). When the CPU of UIM 109 receives the message, the CPU changes the management data corresponding to the filename �abc� to �DELETE�.
3. Modifications The present invention is not limited to the above embodiment. In the following, modifications to the embodiment will be described.
The management messages transmitted from server apparatus 500 may include not only a message to delete an application program, but also a message to disable use of an application program. Server apparatus 500 is configured to transmit a management message including the management data to mobile phone 100, when the administrator of server apparatus 500 changes the management data to �DISABLED�. When the management message is received by mobile phone 100, the management data in program list table TB2 stored in UIM 109 is changed to �DISABLED�. When the OS established on CPU 108 receives an instruction to execute an application program, the OS checks program list table TB2 in UIM 109. When the management data corresponding to the application program for which execution is instructed is �DISABLED�, the OS is configured not to read and not to execute the application program from non-volatile memory 105. According to this aspect, use of an application program may be disabled not only by deletion of an application program, but also by keeping the application program stored in non-volatile memory 105.
The application program may be a program written using Java� byte code (In the following, it will be abbreviated as a Java program). It is noted that a Java executing platform is required to download a Java program from a server apparatus or to execute the Java program. When a Java program is downloaded to mobile phone 100, the Java program is configured to be managed by the Java executing platform, so that other application programs are not able to, for example, delete the Java program from non-volatile memory 105. In this aspect, when a Java program is deleted according to a management message, access control may be configured to interpret the management message, to generate a message, interpretable by the Java executing platform, of requesting a deletion of a Java program, and to pass the message to the Java executing platform. The Java executing platform that has received the message may be configured to delete the Java program. Even if there exist a plurality of software platforms such as a software platform established on the mobile phone 100 or a software platform established on UIM, the access control interprets a management message transmitted from server apparatus 500, and exercises appropriate control according to each software platform. Thus, server apparatus 500 does not need to transmit a management message by addressing each software platform, and the application program that has been distributed to mobile phone 100 may be managed with only an abstract message.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5282247Nov 12, 1992Jan 25, 1994Maxtor CorporationApparatus and method for providing data security in a computer system having removable memoryUS5933773May 12, 1997Aug 3, 1999Telefonaktiebolaget Lm EricssonMethod and a device for mobile telephone supervisionUS6047071Apr 15, 1997Apr 4, 2000Nokia Mobile PhonesNetwork-initiated change of mobile phone parametersUS6091946May 10, 1996Jul 18, 2000Nokia Telecommunications OyChecking the access right of a subscriber equipmentUS6141563 *Dec 16, 1997Oct 31, 2000Motorola, Inc.SIM card secured subscriber unitUS6173172Nov 26, 1997Jan 9, 2001Nippon Shinpan Co., Ltd.System and method for preventing the unauthorized use of a mobile communication deviceUS6212372Jan 9, 1997Apr 3, 2001Comvik Gsm AbMethod in mobile telephone systems in which a subscriber identity module (SIM) is allocated at least two identities which are selectively activated by the userUS6236859Oct 22, 1997May 22, 2001Siemens AktiengesellschaftMethod for the location registration of a mobile terminalUS6314409Oct 26, 1998Nov 6, 2001Veridian Information SolutionsSystem for controlling access and distribution of digital propertyUS6320947Sep 14, 1999Nov 20, 2001Satyam Enterprise Solutions LimitedTelephony platform and method for providing enhanced communication servicesUS6342010Nov 14, 1997Jan 29, 2002Russell Dale SliferPersonalized wireless video game systemUS6381316May 9, 2001Apr 30, 2002Unpaid Systems, Ltd.Enhanced communication platform and related communication method using the platformUS6445914Sep 8, 1999Sep 3, 2002Ericsson, Inc.Method to perform subsidy protection for TDMA mobile stationsUS6501962Jan 31, 1997Dec 31, 2002Orange Personal Communications Services LimitedMobile communications terminal smart cardUS6633764Feb 11, 2000Oct 14, 2003Telefonaktiebolaget L M Ericsson (Publ)Apparatus, method and system for short message service center storage controlUS6810479Jan 26, 2000Oct 26, 2004Microsoft CorporationSystem and method for configuring and managing resources on a multi-purpose integrated circuit card using a personal computerUS6836654 *Dec 18, 2000Dec 28, 2004Koninklijke Philips Electronics N.V.Anti-theft protection for a radiotelephony deviceUS6850777 *Mar 31, 2000Feb 1, 2005Motorola, Inc.Method for providing a personal identification number to a subscriber identity moduleUS6871063Jun 30, 2000Mar 22, 2005Intel CorporationMethod and apparatus for controlling access to a computer systemUS6975855Apr 26, 2000Dec 13, 2005Nokia Networks OyMethod for managing mobile station facilitiesUS6999948Aug 9, 2000Feb 14, 2006Fujitsu LimitedMemory cardUS7130648Oct 18, 2000Oct 31, 2006Cp8 TechnologiesMessage transmission system and method, and utilization of the transmission system to investigate services offeredUS7248886Feb 26, 1998Jul 24, 2007Detemobil Deutsche Telekom Mobilnet GmbhPublic mobile communication system compatible wireless communication systemUS7349697Jul 12, 2001Mar 25, 2008Ntt Docomo, Inc.Mobile communication system, mobile terminal, subscriber information management apparatus, mobile network system, location area information registration method and call control methodUS7450929 *Dec 17, 2004Nov 11, 2008Ntt Docomo, Inc.Communication system, communication terminal device, and information storage moduleUS7650630Dec 9, 2002Jan 19, 2010Ntt Docomo, Inc.Device and method for restricting content access and storageUS20020099665Oct 1, 2001Jul 25, 2002Burger Todd O.Portable electronic authorization system and methodUS20030135748 *Dec 9, 2002Jul 17, 2003Kazuhiro YamadaDevice and method for restricting content access and storageUS20040073580Nov 8, 2002Apr 15, 2004Hirobumi NakayamaInformation delivery apparatus, information processing terminal, external content storage method, external content output method, content data, output control program, and information delivery systemUS20040133794Jul 7, 2003Jul 8, 2004Kocher Paul C.Self-protecting digital contentUS20040248550 *Jun 4, 2002Dec 9, 2004Josef HausnerMobile station in a mobile communication system and method for accessing a service and/or data set in the stand-by- mode of the mobile stationUS20070197201 *Dec 15, 2004Aug 23, 2007Ntt Docomo, Inc.Communication TerminalUS20080300020 *May 8, 2008Dec 4, 2008Renesas Technology Corp.Wireless communication system, sim card, mobile communication terminal, and data guaranteeing methodUS20090029736 *Jul 11, 2008Jan 29, 2009Samsung Electronics Co., Ltd.Mobile terminal and sim indicative information display method thereofUS20100071037Nov 25, 2009Mar 18, 2010Ntt Docomo, Inc.System for restricting content access and storageEP0607767B1Oct 29, 1993Nov 26, 1997Ericsson Inc.Access controlled device for rendering servicesEP1047277A2Apr 18, 2000Oct 25, 2000Nec CorporationMobile communication terminal with a detachable IC card and method of accessing the networkEP1085395A2Sep 13, 2000Mar 21, 2001Phone.Com, Inc.Access control system for files on a memory cardEP1107627A1Dec 3, 1999Jun 13, 2001Siemens AktiengesellschaftA method for protecting user data stored in memory of a mobile communication device, particularly a mobile phoneEP1143688A1Mar 2, 2000Oct 10, 2001Client Electronics GmbHMobile services on the basis of a smart cardGB2369205A * Title not availableJP2000049687A Title not availableJP2000099187A Title not availableJP2002100116A Title not availableJP2002135407A Title not availableJP2003198718A Title not availableJP2005086253A Title not availableJPH0865740A Title not availableJPH0923268A Title not availableJPH09322239A Title not availableJPH11191804A Title not availableJPH11306118A Title not availableKR20010043378A Title not availableWO1997044762A1May 16, 1997Nov 27, 1997Gemplus Card IntCommunication system for managing safely and independently a plurality of applications by each user card and corresponding user card and management methodWO1999057843A1Apr 23, 1999Nov 11, 1999Charles W BrownA method and apparatus for preventing the fraudulent use of a cellular telephoneWO2000048416A1Feb 9, 2000Aug 17, 2000Matti HiltunenMethod for the utilisation of applications stored on a subscriber identity module (sim) and for the secure treatment of information associated with themWO2000059225A1Feb 22, 2000Oct 5, 2000Motorola IncSecure wireless electronic-commerce system with wireless network domainWO2003040930A1Nov 8, 2002May 15, 2003Ntt Docomo IncInformation delivery apparatus, information processing terminal, external content storage method, external content output method, content data, output control program, and information delivery system* Cited by examinerNon-Patent CitationsReference1European Search Report dated Jun. 9, 2005, issued in European Patent Application No. 02028128, 3 pages.2Issue Notification dated Dec. 30, 2009, issued in U.S. Appl. No. 10/314,520 (1 page).3Japanese Office Action dated Sep. 11, 2007, issued in Japanese Patent Application No. 2001-392068, with English translation, 5 pages.4Microsoft Outlook 98, http://support.microsoft.com/?kbid=181005, 2 pages of English version, 3 pages of Japanese version, Jul. 30, 2001.5Notice of Allowance dated Aug. 21, 2009, issued in U.S. Appl. No. 10/314,520 (9 pages).6Notice of Allowance mailed Apr. 30, 2009, Patent Publication No. 2003/0135748 A1, U.S. Appl. No. 10/314,520.7Office Action dated Apr. 15, 2005, issued in Canadian Patent Application No. 2,413,231, 3 pages.8Office Action dated Dec. 13, 2004, issued in Singapore Patent Application No. 200207356-7, 9 pages.9Office Action dated Jan. 14, 2008, issued in Norwegian Patent Application No. 20026210, with English translation, 6 pages.10Office Action dated Mar. 24, 2005, issued in Korean Patent Application No. 10-2002-0083605, 3 pages.11Office Action mailed Feb. 2, 2009, Patent Publication No. 2003/0135748 A1, U.S. Appl. No. 10/314,520.12Office Action mailed Feb. 27, 2007, in U.S. Patent Publication No. 2003/0135748 A1, U.S. Appl. No. 10/314,520.13Office Action mailed May 26, 2006, in U.S. Patent Publication No. 2003/0135748 A1, U.S. Appl. No. 10/314,520.14Office Action mailed May 28, 2008, Patent Publication No. 2003/0135748 A1, U.S. Appl. No. 10/314,520.15Office Action mailed Nov. 16, 2007, Patent Publication No. 2003/0135748 A1, U.S. Appl. No. 10/314,520.16Republic of the Philippines Intellectual Property Office Official Gazette, vol. VII, No. 5, Aug. 18, 2004, regarding Philippines Patent Application No. 1-2002-00861, 3 pages.17Tsutao Nishizaki, "Card v. Mobile Phone: Next-Generation Mobile Phone and SIM," CardWave, pp. 30-33, Mar. 2001.18U.S. Appl. No. 12/626,585, filed Nov. 25, 2009, Yamada.Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8135385 *Oct 13, 2006Mar 13, 2012Ntt Docomo, Inc.Mobile terminal, access control management device, and access control management methodUS8291482Nov 25, 2009Oct 16, 2012Ntt Docomo, Inc.System for restricting content access and storageUS20120259879 *Mar 27, 2012Oct 11, 2012Ricoh Company, Ltd.Content processing apparatus, method, and system* Cited by examinerClassifications U.S. Classification455/558, 455/410, 379/433.09, 455/418, 455/425, 379/357.01, 379/211.05, 455/411, 455/550.1International ClassificationH04M1/00, H04M1/725, H04M3/42, G06F12/14, G06F1/00, H04M1/675, H04M11/08, H04W8/24, H04W92/08, H04W28/00Cooperative ClassificationH04M1/72525, G06F21/10, H04M1/72552European ClassificationH04M1/725F1M4, H04M1/725F1A, G06F21/10Legal EventsDateCodeEventDescriptionMay 7, 2014FPAYFee paymentYear of fee payment: 4Mar 15, 2011CCCertificate of correctionSep 9, 2010ASAssignmentOwner name: NTT DOCOMO, INC., JAPANEffective date: 20070326Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WASHIO, SATOSHI;KAWABATA, HIROSHI;YAMAGUCHI, TOMOO;REEL/FRAME:024965/0279RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google