WO2005009014A1 - System and method of software transfer between a mobile phone and a mobile phone accessory - Google Patents

System and method of software transfer between a mobile phone and a mobile phone accessory Download PDF

Info

Publication number
WO2005009014A1
WO2005009014A1 PCT/IB2004/001074 IB2004001074W WO2005009014A1 WO 2005009014 A1 WO2005009014 A1 WO 2005009014A1 IB 2004001074 W IB2004001074 W IB 2004001074W WO 2005009014 A1 WO2005009014 A1 WO 2005009014A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile phone
accessory
software
interaction handler
transfer
Prior art date
Application number
PCT/IB2004/001074
Other languages
French (fr)
Inventor
Nadi S. Findikli
Original Assignee
Sony Ericsson Mobile Communications Ab
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sony Ericsson Mobile Communications Ab filed Critical Sony Ericsson Mobile Communications Ab
Priority to JP2006520023A priority Critical patent/JP2007531339A/en
Priority to EP04723672A priority patent/EP1647129A1/en
Publication of WO2005009014A1 publication Critical patent/WO2005009014A1/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • 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/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/108—Source integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the present invention generally relates to mobile phone accessory management, and more specifically to management of the capabilities and resources of a mobile phone accessory through dynamic software loading.
  • a mobile phone accessory When a mobile phone accessory is connected to a mobile phone, the user interface of the mobile phone typically needs to change to allow the user to exploit the additional capabilities offered by the mobile phone accessory. For example, a digital camera accessory will require additional user interface features for taking, viewing, and storing pictures.
  • the mobile phone software may require modification to allow the user to manage the resources associated with the mobile phone accessory or to manage the mobile phone accessory itself.
  • New or updated mobile phone software could add the functionality a mobile phone needs to take full advantage of the accessory.
  • mobile phone software may not initially enable pictures to be attached to emails; however, connecting a digital camera accessory to a mobile phone would necessitate the addition of such a feature.
  • Mobile phone accessories are often developed subsequent to the production of a mobile phone. Interaction between a mobile phone and a mobile phone accessory, as well as management of the mobile phone accessory itself, is typically restricted to preexisting fixed menu structures and menu options already loaded into the mobile phone. Thus, support for the mobile phone accessory may be limited since the mobile phone was produced without knowledge of the subsequently developed mobile phone accessory.
  • the present invention provides a method of operating a mobile phone accessory communicable with a mobile phone.
  • the method dynamically loads software into a mobile phone from a mobile phone accessory such that the software can be independently executed on the mobile phone platform.
  • Dynamic software loading facilitates full resource realization by not limiting the operation and management of the mobile phone accessory to a pre-existing menu structure and mode of operation already residing in the mobile phone.
  • the mobile phone is essentially converted into a differently operable and more capable device through the dynamic software loading process.
  • both devices exchange identification and configuration data to determine the appropriate software to transfer. Data pertaining to the software residing in the mobile phone accessory and the ability of the mobile phone to execute the software is shared.
  • a verification process ensures that the mobile phone and mobile phone accessory are authorized to receive and transfer software, respectively.
  • a software program or module is transferred or downloaded from the mobile phone accessory to be stored in the mobile phone.
  • the mobile phone can then execute the downloaded program.
  • the mobile phone platform contains application program interfaces (APIs) and processor hardware capable of running a variety of different software programs or modules.
  • APIs application program interfaces
  • the above mentioned APIs allow the software to perform functions using the existing hardware and software in the mobile phone, such as the display, speakers, keypad, etc.
  • FIGURE 1 is a block diagram illustrating functional components of the present invention.
  • FIGURE 2 is a flowchart illustrating a process for downloading software from a mobile phone accessory to a mobile phone. Best Mode(s) for Carrying Out the Invention
  • FIGURE 1 illustrates a mobile phone 100 and a mobile phone accessory 105 according to one embodiment of the present invention.
  • Mobile phone 100 and mobile phone accessory 105 both include a physical communication layer 110.
  • the physical communication layers 110 are capable of establishing a communication link between mobile phone 100 and mobile phone accessory 105.
  • the communication link can be a wireless radio frequency (RF), cabled, or optical link among others.
  • the communication link facilitates communication between mobile phone 100 and mobile phone accessory 105 providing a means for effecting a software transfer.
  • Mobile phone 100 further includes an accessory interaction handler 115.
  • the accessory interaction handler 115 communicates data pertaining to mobile phone 100 to mobile phone accessory 105.
  • accessory' interaction handler 115 communicates data to mobile phone accessory 105 that is useful in determining the appropriate software to transfer from mobile phone accessory 105 to mobile phone 100.
  • data can include, for instance, the hardware and software capabilities and characteristics of mobile phone 100.
  • the accessory interaction handler 115 is responsible for verifying that mobile phone accessory 105 is authorized to transfer software to mobile phone 100. After a transfer of software from mobile phone accessory 105 to the mobile phone 100, the accessory interaction handler 115 can verify that the software is licensed by the mobile phone manufacturer or its authorized agent for use on mobile phone 100. This step may be performed by embedding data within the software to identify its origin and credentials or by attaching a certificate to the software containing similar data.
  • the accessory interaction handler 115 can verify that the software has not been modified or corrupted since its initial creation. This step may be performed using data, either embedded in the software or attached as a certificate to the software, that verifies the consistency of the program. Such data may include, but is not limited to, a checksum or size check.
  • Mobile phone accessory 105 includes a corresponding phone interaction handler 120.
  • the phone interaction handler 120 communicates data pertaining to mobile phone accessory 105 to mobile phone 100.
  • phone interaction handler 120 communicates data regarding the software that mobile phone accessory 105 is capable of transferring to mobile phone 100. Such information can include an accounting of the different types and versions of software available for transfer to mobile phone 100.
  • the phone interaction handler 120 is also capable of verifying that mobile phone 100 is authorized to receive software from mobile phone accessory 105. Specifically, phone interaction handler 120 can ensure that unlicensed software can not be transferred to mobile phone 100 or that otherwise protected software can not be transferred to an unauthorized mobile phone. If any of the previously mentioned verification or authorization steps fail, then a software transfer is aborted. An error message can be shown on the display of mobile phone 100 indicating why the software transfer was aborted.
  • Mobile phone accessory 105 further includes storage for software 122 related to the operation of mobile phone accessory 105.
  • the software 122 can be in many forms and may include, but is not limited to, Java scripts, HTML pages, XML scripts, BREW scripts, C++ scripts, or native applications specific to a particular mobile phone 100.
  • mobile phone accessory 105 may store multiple copies of software 122 written in different programming languages and in different versions to ensure compatibility with a variety of mobile phones from a variety of manufacturers.
  • phone interaction handler 120 can select the software 122 best suited for a particular mobile phone 100.
  • Features of mobile phone 100 which may affect the software selection process include, but are not limited to, the existence of a keyboard on mobile phone 100, the software currently loaded in mobile phone 100, or the display characteristics and type of mobile phone 100. Display characteristics include the size, resolution, whether or not the display is color or monochrome, and color depth.
  • Mobile phone 100 further includes sufficient storage 125 for receiving transferred software.
  • Mobile phone 100 is also equipped with a processor 130 for executing software and a variety of APIs 135 to ensure usability with a variety of mobile phone accessories.
  • FIGURE 2 illustrates the process of dynamic software loading from mobile phone accessory to mobile phone.
  • Device discovery begins with the establishment of any suitable communication link 205 between the two devices. This can be achieved using a wireless RF link such as BluetoothTM, and optical link such as infrared, or a cabled link.
  • Device discovery encompasses both devices identifying themselves 210, 215 to one another. Device discovery may include manual steps initiated by the user or may be automatic.
  • Identification of the mobile phone to the mobile phone accessory 210 entails communicating to the mobile phone accessory that the mobile phone is capable of receiving stored software from the mobile phone accessory. Further, the mobile phone shares information regarding its hardware and software capabilities and characteristics useful for determining the appropriate software for transfer. For example, the mobile phone communicates information concerning its functional capabilities (such as display feature information and what software it is capable of executing), identity (such as software version information), and type (such as manufacturer and model information). Likewise, identification of the mobile phone accessory to the mobile phone 215 entails communicating to the mobile phone that the mobile phone accessory is capable of transferring stored software to the mobile phone. Further, the mobile phone accessory shares information regarding its identity and type along with an accounting of the software it contains.
  • Device discovery is completed when the mobile phone and mobile phone accessory determine: (a) what software will be downloaded from the mobile phone accessory to the mobile phone; (b) which method of authentication, if any, will be used to verify that the mobile phone and mobile phone accessory are authorized to receive and transfer software, respectively; and (c) which method of encryption, if any, will be used to transfer the software.
  • the mobile phone ensures that the mobile phone accessory is authorized to transfer software to the mobile phone 220.
  • the mobile phone accessory must ensure that the mobile phone is authorized to receive software from the mobile phone accessory 225. This is termed device authentication.
  • Authentication may be performed using one of a number of publicly available methods such as, for instance, Public Key Infrastructure (PKI), using a proprietary method developed as part of the dynamic software loading feature, or using a proprietary method developed by a mobile phone (or mobile phone accessory) manufacturer and made available to a mobile phone accessory (or mobile phone) manufacturer.
  • PKI Public Key Infrastructure
  • the software may be encrypted prior to transfer to provide further security.
  • Encryption may be performed using one of a number of publicly available methods such as, for instance, Data Encryption Standard (DES), using a proprietary method developed as part of the dynamic software loading feature, or using a proprietary method developed by a mobile phone (or mobile phone accessory) manufacturer and made available to a mobile phone accessory (or mobile phone) manufacturer.
  • DES Data Encryption Standard
  • the mobile phone After receiving and storing the software from the mobile phone accessory, the mobile phone then verifies the authenticity of the software 235. Specifically, the mobile phone verifies that the mobile phone manufacturer has licensed the software to be used on the mobile phone. This step can be performed by examining data embedded within the software itself or contained within a certificate attached to the software. Such data can identify the origin and credentials of the software.
  • the mobile phone can then compare this data against acceptable values or certificates stored within the mobile phone itself or can perform additional steps to complete PKI verification.
  • the mobile phone can also implement a security check to ensure the software has not been modified or tampered with since its original creation. This step may be performed using data, either embedded in the software or attached as a certificate to the software, that verifies the consistency of the program. Such data may include, but is not limited to, a checksum or size check.
  • the mobile phone can re-create the verification data based on the software it has received. The re-created verification data can then be compared to the transferred verification data delivered via secure means to determine the authenticity and integrity of the transferred software. Specific embodiments of an invention are disclosed herein.

Abstract

A system and method of operating a mobile phone accessory communicable with a mobile phone. The present invention dynamically loads software into a mobile phone from a mobile phone accessory to enable better management of the accessory's resources and capabilities. After a communication link is established between the mobile phone and mobile phone accessory, both devices exchange information to determine the appropriate software to transfer. A verification process then ensures that the mobile phone and mobile phone accesory are authorized to receive and transfer software, respectively. Subsequently, software is transferred from the mobile phone accessory to be stored in the mobile phone. The mobile phone is capable of executing the downloaded software. Specifically, the mobile phone contains the necessary API(s) and processor hardware needed to run a variety of software.

Description

TITLE SYSTEM AND METHOD OF SOFTWARE TRANSFER BETWEEN A MOBILE PHONE AND A MOBILE PHONE ACCESSORY DESCRIPTION Background Art The present invention generally relates to mobile phone accessory management, and more specifically to management of the capabilities and resources of a mobile phone accessory through dynamic software loading. When a mobile phone accessory is connected to a mobile phone, the user interface of the mobile phone typically needs to change to allow the user to exploit the additional capabilities offered by the mobile phone accessory. For example, a digital camera accessory will require additional user interface features for taking, viewing, and storing pictures. Ultimately, the mobile phone software may require modification to allow the user to manage the resources associated with the mobile phone accessory or to manage the mobile phone accessory itself. New or updated mobile phone software could add the functionality a mobile phone needs to take full advantage of the accessory. For example, mobile phone software may not initially enable pictures to be attached to emails; however, connecting a digital camera accessory to a mobile phone would necessitate the addition of such a feature. Mobile phone accessories are often developed subsequent to the production of a mobile phone. Interaction between a mobile phone and a mobile phone accessory, as well as management of the mobile phone accessory itself, is typically restricted to preexisting fixed menu structures and menu options already loaded into the mobile phone. Thus, support for the mobile phone accessory may be limited since the mobile phone was produced without knowledge of the subsequently developed mobile phone accessory. With today's advanced mobile phone accessories, it is desirable to use a more flexible means of ensuring interaction between the mobile phone and a mobile phone accessory and to more fully realize the capabilities of the mobile phone accessory. Further, it is desirable to perform actions with the mobile phone accessory that are not conventionally associated with menu functions and to take advantage of the graphical user interface of a mobile phone. A higher level of security may also be exploited to effectively manage the extended capabilities.
Disclosure of Invention The present invention provides a method of operating a mobile phone accessory communicable with a mobile phone. The method dynamically loads software into a mobile phone from a mobile phone accessory such that the software can be independently executed on the mobile phone platform. Dynamic software loading facilitates full resource realization by not limiting the operation and management of the mobile phone accessory to a pre-existing menu structure and mode of operation already residing in the mobile phone. As a result, the mobile phone is essentially converted into a differently operable and more capable device through the dynamic software loading process. After a communication link is established between the mobile phone and mobile phone accessory, both devices exchange identification and configuration data to determine the appropriate software to transfer. Data pertaining to the software residing in the mobile phone accessory and the ability of the mobile phone to execute the software is shared. A verification process ensures that the mobile phone and mobile phone accessory are authorized to receive and transfer software, respectively. A software program or module is transferred or downloaded from the mobile phone accessory to be stored in the mobile phone. The mobile phone can then execute the downloaded program. Specifically, the mobile phone platform contains application program interfaces (APIs) and processor hardware capable of running a variety of different software programs or modules. The above mentioned APIs allow the software to perform functions using the existing hardware and software in the mobile phone, such as the display, speakers, keypad, etc.
Brief Description of Drawings FIGURE 1 is a block diagram illustrating functional components of the present invention. FIGURE 2 is a flowchart illustrating a process for downloading software from a mobile phone accessory to a mobile phone. Best Mode(s) for Carrying Out the Invention
FIGURE 1 illustrates a mobile phone 100 and a mobile phone accessory 105 according to one embodiment of the present invention. For ease of illustration, not all of the components of mobile phone 100 or mobile phone accessory 105 have been shown. Mobile phone 100 and mobile phone accessory 105 both include a physical communication layer 110. The physical communication layers 110 are capable of establishing a communication link between mobile phone 100 and mobile phone accessory 105. The communication link can be a wireless radio frequency (RF), cabled, or optical link among others. The communication link facilitates communication between mobile phone 100 and mobile phone accessory 105 providing a means for effecting a software transfer. Mobile phone 100 further includes an accessory interaction handler 115. The accessory interaction handler 115 communicates data pertaining to mobile phone 100 to mobile phone accessory 105. Specifically, accessory' interaction handler 115 communicates data to mobile phone accessory 105 that is useful in determining the appropriate software to transfer from mobile phone accessory 105 to mobile phone 100. Such data can include, for instance, the hardware and software capabilities and characteristics of mobile phone 100. The accessory interaction handler 115 is responsible for verifying that mobile phone accessory 105 is authorized to transfer software to mobile phone 100. After a transfer of software from mobile phone accessory 105 to the mobile phone 100, the accessory interaction handler 115 can verify that the software is licensed by the mobile phone manufacturer or its authorized agent for use on mobile phone 100. This step may be performed by embedding data within the software to identify its origin and credentials or by attaching a certificate to the software containing similar data. Further, the accessory interaction handler 115 can verify that the software has not been modified or corrupted since its initial creation. This step may be performed using data, either embedded in the software or attached as a certificate to the software, that verifies the consistency of the program. Such data may include, but is not limited to, a checksum or size check. Mobile phone accessory 105 includes a corresponding phone interaction handler 120. The phone interaction handler 120 communicates data pertaining to mobile phone accessory 105 to mobile phone 100. Specifically, phone interaction handler 120 communicates data regarding the software that mobile phone accessory 105 is capable of transferring to mobile phone 100. Such information can include an accounting of the different types and versions of software available for transfer to mobile phone 100. The phone interaction handler 120 is also capable of verifying that mobile phone 100 is authorized to receive software from mobile phone accessory 105. Specifically, phone interaction handler 120 can ensure that unlicensed software can not be transferred to mobile phone 100 or that otherwise protected software can not be transferred to an unauthorized mobile phone. If any of the previously mentioned verification or authorization steps fail, then a software transfer is aborted. An error message can be shown on the display of mobile phone 100 indicating why the software transfer was aborted. Mobile phone accessory 105 further includes storage for software 122 related to the operation of mobile phone accessory 105. The software 122 can be in many forms and may include, but is not limited to, Java scripts, HTML pages, XML scripts, BREW scripts, C++ scripts, or native applications specific to a particular mobile phone 100. Multiple forms can accommodate varying cellular platforms such as Code Division Multiple Access (CDMA) or Global System for Mobile Communications (GSM). Further, mobile phone accessory 105 may store multiple copies of software 122 written in different programming languages and in different versions to ensure compatibility with a variety of mobile phones from a variety of manufacturers. Based on the features and capabilities of the currently connected mobile phone 100, phone interaction handler 120 can select the software 122 best suited for a particular mobile phone 100. Features of mobile phone 100 which may affect the software selection process include, but are not limited to, the existence of a keyboard on mobile phone 100, the software currently loaded in mobile phone 100, or the display characteristics and type of mobile phone 100. Display characteristics include the size, resolution, whether or not the display is color or monochrome, and color depth. Mobile phone 100 further includes sufficient storage 125 for receiving transferred software. Mobile phone 100 is also equipped with a processor 130 for executing software and a variety of APIs 135 to ensure usability with a variety of mobile phone accessories. FIGURE 2 illustrates the process of dynamic software loading from mobile phone accessory to mobile phone. First, the mobile phone and mobile phone accessory enter into a stage of device discovery. Device discovery begins with the establishment of any suitable communication link 205 between the two devices. This can be achieved using a wireless RF link such as Bluetooth™, and optical link such as infrared, or a cabled link. Device discovery encompasses both devices identifying themselves 210, 215 to one another. Device discovery may include manual steps initiated by the user or may be automatic. Identification of the mobile phone to the mobile phone accessory 210 entails communicating to the mobile phone accessory that the mobile phone is capable of receiving stored software from the mobile phone accessory. Further, the mobile phone shares information regarding its hardware and software capabilities and characteristics useful for determining the appropriate software for transfer. For example, the mobile phone communicates information concerning its functional capabilities (such as display feature information and what software it is capable of executing), identity (such as software version information), and type (such as manufacturer and model information). Likewise, identification of the mobile phone accessory to the mobile phone 215 entails communicating to the mobile phone that the mobile phone accessory is capable of transferring stored software to the mobile phone. Further, the mobile phone accessory shares information regarding its identity and type along with an accounting of the software it contains. Device discovery is completed when the mobile phone and mobile phone accessory determine: (a) what software will be downloaded from the mobile phone accessory to the mobile phone; (b) which method of authentication, if any, will be used to verify that the mobile phone and mobile phone accessory are authorized to receive and transfer software, respectively; and (c) which method of encryption, if any, will be used to transfer the software. After device discovery, the mobile phone ensures that the mobile phone accessory is authorized to transfer software to the mobile phone 220. Likewise, the mobile phone accessory must ensure that the mobile phone is authorized to receive software from the mobile phone accessory 225. This is termed device authentication. Authentication may be performed using one of a number of publicly available methods such as, for instance, Public Key Infrastructure (PKI), using a proprietary method developed as part of the dynamic software loading feature, or using a proprietary method developed by a mobile phone (or mobile phone accessory) manufacturer and made available to a mobile phone accessory (or mobile phone) manufacturer. After mutual device authentication 220, 225 occurs, transfer of the software 230 from the mobile phone accessory to the mobile phone can take place. The software may be encrypted prior to transfer to provide further security. Encryption may be performed using one of a number of publicly available methods such as, for instance, Data Encryption Standard (DES), using a proprietary method developed as part of the dynamic software loading feature, or using a proprietary method developed by a mobile phone (or mobile phone accessory) manufacturer and made available to a mobile phone accessory (or mobile phone) manufacturer. After receiving and storing the software from the mobile phone accessory, the mobile phone then verifies the authenticity of the software 235. Specifically, the mobile phone verifies that the mobile phone manufacturer has licensed the software to be used on the mobile phone. This step can be performed by examining data embedded within the software itself or contained within a certificate attached to the software. Such data can identify the origin and credentials of the software. The mobile phone can then compare this data against acceptable values or certificates stored within the mobile phone itself or can perform additional steps to complete PKI verification. The mobile phone can also implement a security check to ensure the software has not been modified or tampered with since its original creation. This step may be performed using data, either embedded in the software or attached as a certificate to the software, that verifies the consistency of the program. Such data may include, but is not limited to, a checksum or size check. The mobile phone can re-create the verification data based on the software it has received. The re-created verification data can then be compared to the transferred verification data delivered via secure means to determine the authenticity and integrity of the transferred software. Specific embodiments of an invention are disclosed herein. One of ordinary skill in the art will readily recognize that the invention may have other applications in other environments. In fact, many embodiments and implementations are possible. The following claims are in no way intended to limit the scope of the present invention to the specific embodiments described above. In addition, any recitation of "means for" is intended to evoke a means-plus-function reading of an element and a claim, whereas, any elements that do not specifically use the recitation "means for", are not intended to be read as means-plus-function elements, even if the claim otherwise includes the word "means".

Claims

CLAIMS:
1. A method of operating a mobile phone accessory communicable with a mobile phone, the method comprising: (a) establishing a communication link between the mobile phone and the mobile phone accessory; (b) exchanging data between the mobile phone and the mobile phone accessory, the data pertaining to software resident on the mobile phone accessory and the ability of the mobile phone to download and execute the software, wherein the data is used to determine what software to transfer from the mobile phone accessory to the mobile phone; and (c) transferring the software from the mobile phone accessory to the mobile phone via the communication link.
2. The method of claim 1 wherein exchanging data between the mobile phone and the mobile phone accessory further comprises: ensuring that the mobile phone is capable of receiving software through the communication link; and ensuring that the mobile phone accessory is capable of transferring software through the communication link.
3. The method of claim 1 further comprising: verifying that the mobile phone accessory is authorized to transfer the software to the mobile phone; and verifying that the mobile phone is authorized to receive the software from the mobile phone accessory.
4. The method of claim 1 further comprising verifying that the transferred software is licensed for use by the mobile phone.
5. The method of claim 1 further comprising verifying that the transferred software is certified to be used on the mobile phone.
6. The method of claim 1 further comprising verifying that the transferred software has not been tampered with since its creation.
7. The method of claim 1 wherein the software is encrypted before the transferring step.
8. A system for operating a mobile phone accessory communicable with a mobile phone, the system comprising: a physical communication layer in the mobile phone and the mobile phone accessory for providing a communication link between the mobile phone and the mobile phone accessory; an accessory interaction handler within the mobile phone for: exchanging data with the mobile phone accessory, the data pertaining to software resident on the mobile phone accessory and the ability of the mobile phone to execute the software, wherein the data is used to determine what software to transfer from the mobile phone accessory to the mobile phone; and receiving the software from the mobile phone accessory via the physical communication layer; and a phone interaction handler within the mobile phone accessory for: exchanging the data with the mobile phone; and transferring the software to the mobile phone via the physical communication layer.
9. The system of claim 8 wherein the accessory interaction handler verifies that the mobile phone accessory is capable of transferring software to the mobile phone.
10. The system of claim 8 wherein the phone interaction handler verifies that the mobile phone is capable of receiving software from the mobile phone accessory.
11. The system of claim 8 wherein the accessory interaction handler further verifies that the mobile phone accessory is authorized to transfer the software to the mobile phone.
12. The system of claim 8 wherein the phone interaction handler further verifies the mobile phone is authorized to receive the software from the mobile phone accessory.
13. The system of claim 8 wherein the accessory interaction handler further verifies that the transferred software is licensed for use by the mobile phone.
14. The system of claim 8 wherein the accessory interaction handler further verifies that the transferred software is certified to be used on the mobile phone.
15. The system of claim 8 wherein the accessory interaction handler further verifies that the transferred software has not been tampered with since its creation.
16. The system of claim 8 wherein the mobile phone accessory chooses a software program to transfer to the mobile phone based on the characteristics and capabilities of the mobile phone.
17. A mobile phone operable with a mobile phone accessory, the mobile phone comprising: a physical communication layer for providing a communication link between the mobile phone and the mobile phone accessory; an accessory interaction handler for: exchanging data with the mobile phone accessory, the data pertaining to software resident on the mobile phone accessory and the ability of the mobile phone to execute the software, wherein the data is used to determine what software to transfer from the mobile phone accessory to the mobile phone; and receiving the software from the mobile phone accessory via the physical communication layer.
18. The mobile phone of claim 17 wherem the accessory interaction handler verifies that the mobile phone accessory is capable of transferring software to the mobile phone.
19. The mobile phone of claim 17 wherein the accessory interaction handler further verifies that the mobile phone accessory is authorized to transfer the software to the mobile phone.
20. The mobile phone of claim 17 wherein the accessory interaction handler further verifies that software transferred to the mobile phone is licensed for use by the mobile phone.
21. The mobile phone of claim 17 wherein the accessory interaction handler further verifies that the transferred software is certified to be used on the mobile phone.
22. The mobile phone of claim 17 wherein the accessory interaction handler further verifies that the transferred software has not been tampered with since its creation.
23. A mobile phone accessory operable with a mobile phone, the mobile phone accessory comprising: a physical communication layer for providing a communication link between the mobile phone and the mobile phone accessory; a phone interaction handler for: exchanging data with the mobile phone accessory, the data pertaining to software resident on the mobile phone accessory and the ability of the mobile phone to execute the software, wherein the data is used to determine what software to transfer from the mobile phone accessory to the mobile phone; and transferring the software to the mobile phone via the physical communication layer.
24. The mobile phone accessory of claim 23 wherein the phone interaction handler verifies that the mobile phone is capable of receiving software from the mobile phone accessory.
25. The mobile phone accessory of claim 23 wherein the phone interaction handler further verifies that the mobile phone is authorized to receive the software from the mobile phone accessory.
26. The mobile phone accessory of claim 23 wherein the mobile phone accessory chooses a software program to transfer to the mobile phone based on the characteristics and capabilities of the mobile phone.
PCT/IB2004/001074 2003-07-17 2004-03-26 System and method of software transfer between a mobile phone and a mobile phone accessory WO2005009014A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2006520023A JP2007531339A (en) 2003-07-17 2004-03-26 System and method for software transfer between a mobile phone and a mobile phone accessory
EP04723672A EP1647129A1 (en) 2003-07-17 2004-03-26 System and method of software transfer between a mobile phone and a mobile phone accessory

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/604,394 2003-07-17
US10/604,394 US7305254B2 (en) 2003-07-17 2003-07-17 System and method of software transfer between a mobile phone and a mobile phone accessory

Publications (1)

Publication Number Publication Date
WO2005009014A1 true WO2005009014A1 (en) 2005-01-27

Family

ID=34062252

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2004/001074 WO2005009014A1 (en) 2003-07-17 2004-03-26 System and method of software transfer between a mobile phone and a mobile phone accessory

Country Status (5)

Country Link
US (1) US7305254B2 (en)
EP (1) EP1647129A1 (en)
JP (1) JP2007531339A (en)
CN (1) CN1802840A (en)
WO (1) WO2005009014A1 (en)

Families Citing this family (99)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6859799B1 (en) 1998-11-30 2005-02-22 Gemstar Development Corporation Search engine for video and graphics
US7103906B1 (en) 2000-09-29 2006-09-05 International Business Machines Corporation User controlled multi-device media-on-demand system
EP1986435B1 (en) 2000-10-11 2020-01-22 Rovi Guides, Inc. Systems and methods for providing storage of data on servers in an on-demand media delivery system
US7493646B2 (en) 2003-01-30 2009-02-17 United Video Properties, Inc. Interactive television systems with digital video recording and adjustable reminders
US7062261B2 (en) * 2003-01-31 2006-06-13 Motorola, Inc. Method and apparatus for automatic detection and installation of Java-enabled accessories
JP4794122B2 (en) * 2003-08-28 2011-10-19 京セラ株式会社 Information equipment
JP4391781B2 (en) * 2003-08-29 2009-12-24 オリンパス株式会社 Data rewriting device and data rewriting method
US7424312B2 (en) * 2003-09-23 2008-09-09 Motorola, Inc. Interface system for an accessory and a communication device
US7155254B2 (en) * 2003-09-23 2006-12-26 Motorola, Inc. Method and apparatus to self-configure an accessory device
US20050071845A1 (en) * 2003-09-29 2005-03-31 Janne Kallio Terminal equipment, an accessory and a method of communication between terminal equipment and an accessory
JP2005123961A (en) * 2003-10-17 2005-05-12 Kyocera Corp Information apparatus
EP1678926B1 (en) * 2003-10-28 2016-03-30 Nokia Technologies Oy Audio block
US20050097248A1 (en) * 2003-10-29 2005-05-05 Kelley Brian H. System and method for establishing a communication between a peripheral device and a wireless device
US7783729B1 (en) * 2004-03-19 2010-08-24 Single Touch Interactive, Inc. Transmitting mobile device data
US7673083B2 (en) * 2004-04-27 2010-03-02 Apple Inc. Method and system for controlling video selection and playback in a portable media player
US7529870B1 (en) 2004-04-27 2009-05-05 Apple Inc. Communication between an accessory and a media player with multiple lingoes
US8117651B2 (en) 2004-04-27 2012-02-14 Apple Inc. Method and system for authenticating an accessory
US7441058B1 (en) 2006-09-11 2008-10-21 Apple Inc. Method and system for controlling an accessory having a tuner
US7797471B2 (en) 2004-04-27 2010-09-14 Apple Inc. Method and system for transferring album artwork between a media player and an accessory
US7526588B1 (en) 2004-04-27 2009-04-28 Apple Inc. Communication between an accessory and a media player using a protocol with multiple lingoes
US7895378B2 (en) 2004-04-27 2011-02-22 Apple Inc. Method and system for allowing a media player to transfer digital audio to an accessory
US7826318B2 (en) 2004-04-27 2010-11-02 Apple Inc. Method and system for allowing a media player to transfer digital audio to an accessory
US7441062B2 (en) * 2004-04-27 2008-10-21 Apple Inc. Connector interface system for enabling data communication with a multi-communication device
US7529872B1 (en) 2004-04-27 2009-05-05 Apple Inc. Communication between an accessory and a media player using a protocol with multiple lingoes
JP4921363B2 (en) * 2004-08-14 2012-04-25 テレフオンアクチーボラゲット エル エム エリクソン（パブル） Software program synchronization method
US20060046706A1 (en) * 2004-08-26 2006-03-02 Jiansong Lin Monitoring and remote control of wireless communication device accessories and functionality
DE102004047364A1 (en) * 2004-09-29 2006-03-30 Siemens Ag Method for the spontaneous distribution of data and corresponding data network
US7525216B2 (en) * 2005-01-07 2009-04-28 Apple Inc. Portable power source to provide power to an electronic device via an interface
US7823214B2 (en) * 2005-01-07 2010-10-26 Apple Inc. Accessory authentication for electronic devices
US8238971B2 (en) * 2005-01-07 2012-08-07 Apple Inc. Accessory detection to minimize interference with wireless communication
US7398105B2 (en) * 2005-09-06 2008-07-08 Sarandis Kalogeropoulos Mobile communication device and accessory therefor
US20070157240A1 (en) * 2005-12-29 2007-07-05 United Video Properties, Inc. Interactive media guidance system having multiple devices
US9681105B2 (en) * 2005-12-29 2017-06-13 Rovi Guides, Inc. Interactive media guidance system having multiple devices
US8086332B2 (en) * 2006-02-27 2011-12-27 Apple Inc. Media delivery system with improved interaction
US8073984B2 (en) * 2006-05-22 2011-12-06 Apple Inc. Communication protocol for use with portable electronic devices
US8006019B2 (en) 2006-05-22 2011-08-23 Apple, Inc. Method and system for transferring stored data between a media player and an accessory
US7775437B2 (en) * 2006-06-01 2010-08-17 Evryx Technologies, Inc. Methods and devices for detecting linkable objects
US8918905B2 (en) * 2006-06-06 2014-12-23 Future Dial, Inc. Method and system to provide secure exchange of data between mobile phone and computer system
US7415563B1 (en) 2006-06-27 2008-08-19 Apple Inc. Method and system for allowing a media player to determine if it supports the capabilities of an accessory
US7558894B1 (en) 2006-09-11 2009-07-07 Apple Inc. Method and system for controlling power provided to an accessory
PL2092275T3 (en) 2006-12-20 2013-03-29 Johnson Controls Tech Co System and method for providing route calculation and information to a vehicle
WO2008091727A1 (en) 2007-01-23 2008-07-31 Johnson Controls Technology Company Mobile device gateway systems and methods
US20080301732A1 (en) * 2007-05-31 2008-12-04 United Video Properties, Inc. Systems and methods for personalizing an interactive media guidance application
GB2453405B (en) * 2007-06-15 2012-08-08 Apple Inc Systems and methods for providing device-to-device handshaking through a power supply signal
US20080319732A1 (en) * 2007-06-22 2008-12-25 Farnsworth Jeffrey S Serial channel emulator
US20090019492A1 (en) 2007-07-11 2009-01-15 United Video Properties, Inc. Systems and methods for mirroring and transcoding media content
US8116726B2 (en) 2007-08-30 2012-02-14 Motorola Mobility, Inc. Parent and child mobile communication devices with feature control and call-back
AU2008296673B2 (en) 2007-09-04 2010-05-27 Apple Inc. Smart dock for chaining accessories
JP5623287B2 (en) * 2007-12-05 2014-11-12 ジョンソン コントロールズテクノロジーカンパニーＪｏｈｎｓｏｎ Ｃｏｎｔｒｏｌｓ Ｔｅｃｈｎｏｌｏｇｙ Ｃｏｍｐａｎｙ Vehicle user interface system and method
WO2009077801A1 (en) * 2007-12-17 2009-06-25 Nokia Corporation Accessory configuration and management
US8626149B2 (en) * 2007-12-18 2014-01-07 Qualcomm Incorporated Monitoring and troubleshooting a module associated with a portable communication device
US8047966B2 (en) * 2008-02-29 2011-11-01 Apple Inc. Interfacing portable media devices and sports equipment
US8970647B2 (en) 2008-05-13 2015-03-03 Apple Inc. Pushing a graphical user interface to a remote device with display rules provided by the remote device
US9870130B2 (en) * 2008-05-13 2018-01-16 Apple Inc. Pushing a user interface to a remote device
JP5789509B2 (en) * 2008-06-27 2015-10-07 ピレリ・タイヤ・ソチエタ・ペル・アツィオーニ Method and plant for building tires for vehicle wheels
US20100058317A1 (en) * 2008-09-02 2010-03-04 Vasco Data Security, Inc. Method for provisioning trusted software to an electronic device
US8238811B2 (en) 2008-09-08 2012-08-07 Apple Inc. Cross-transport authentication
US8208853B2 (en) 2008-09-08 2012-06-26 Apple Inc. Accessory device authentication
US8655340B2 (en) * 2008-10-14 2014-02-18 At&T Intellectual Property I, L.P. Method, apparatus, and computer program product for wireless customer services
US8228670B2 (en) * 2008-10-20 2012-07-24 James T Fahey Peripheral storage device
EP2180664A1 (en) * 2008-10-22 2010-04-28 Vivendi Mobile Entertainment System and method for accessing multi-media content via a mobile terminal
US8447977B2 (en) 2008-12-09 2013-05-21 Canon Kabushiki Kaisha Authenticating a device with a server over a network
US8452903B2 (en) * 2009-03-16 2013-05-28 Apple Inc. Mobile computing device capabilities for accessories
US8909803B2 (en) 2009-03-16 2014-12-09 Apple Inc. Accessory identification for mobile computing devices
US8719112B2 (en) * 2009-11-24 2014-05-06 Microsoft Corporation Invocation of accessory-specific user experience
US7865629B1 (en) * 2009-11-24 2011-01-04 Microsoft Corporation Configurable connector for system-level communication
TWI391824B (en) * 2009-12-18 2013-04-01 Feeling Technology Corp Drive the connection system
US8886849B2 (en) 2012-05-11 2014-11-11 Apple Inc. Multi-mode adapter
EP2559225B1 (en) * 2010-04-14 2017-02-15 Microsoft Technology Licensing, LLC Dynamic configuration of connectors for system level communications
US8347014B2 (en) 2010-06-04 2013-01-01 Apple Inc. Class-based compatibility testing and notification
US8509882B2 (en) 2010-06-08 2013-08-13 Alivecor, Inc. Heart monitoring system usable with a smartphone or computer
US8301232B2 (en) 2010-06-08 2012-10-30 Alivecor, Inc. Wireless, ultrasonic personal health monitoring system
US9351654B2 (en) 2010-06-08 2016-05-31 Alivecor, Inc. Two electrode apparatus and methods for twelve lead ECG
FR2968494B1 (en) * 2010-12-03 2012-12-28 Oberthur Technologies METHOD OF COMMUNICATING BETWEEN AN ONBOARD SERVER AND A REMOTE SERVER
US8478913B2 (en) * 2011-11-30 2013-07-02 Apple Inc. Adapter for electronic devices
US8762605B2 (en) 2011-11-30 2014-06-24 Apple Inc. Adapter for electronic devices
US8805418B2 (en) 2011-12-23 2014-08-12 United Video Properties, Inc. Methods and systems for performing actions based on location-based rules
US9306879B2 (en) 2012-06-08 2016-04-05 Apple Inc. Message-based identification of an electronic device
WO2014036436A1 (en) 2012-08-30 2014-03-06 Alivecor, Inc. Cardiac performance monitoring system for use with mobile communications devices
US9021159B2 (en) 2012-09-07 2015-04-28 Apple Inc. Connector adapter
US9459670B2 (en) 2012-09-07 2016-10-04 Apple Inc. Adapter for use with a portable electronic device
US9213806B2 (en) 2012-11-08 2015-12-15 Bank Of America Corporation Managing and providing access to applications in an application-store module
WO2014074913A1 (en) 2012-11-08 2014-05-15 Alivecor, Inc. Electrocardiogram signal detection
WO2014107700A1 (en) 2013-01-07 2014-07-10 Alivecor, Inc. Methods and systems for electrode placement
US9369823B2 (en) * 2013-09-24 2016-06-14 Google Technology Holdings LLC System and method for transferring software applications and data between two mobile devices with different operating systems
US9254092B2 (en) 2013-03-15 2016-02-09 Alivecor, Inc. Systems and methods for processing and analyzing medical data
KR102072144B1 (en) * 2013-03-26 2020-01-31 삼성전자주식회사 Method for identifying for accessory an electronic device thereof
US9955286B2 (en) * 2013-05-08 2018-04-24 Natalya Segal Smart wearable devices and system therefor
US20140379800A1 (en) * 2013-06-25 2014-12-25 Actiontec Electronics, Inc. Systems and methods for sharing digital information between mobile devices of friends and family by loading application components onto embedded devices
US8838836B1 (en) 2013-06-25 2014-09-16 Actiontec Electronics, Inc. Systems and methods for sharing digital information between mobile devices of friends and family using multiple LAN-based embedded devices
US9525991B2 (en) 2013-06-25 2016-12-20 Actiontec Electronics, Inc. Systems and methods for sharing digital information between mobile devices of friends and family using embedded devices
US9247911B2 (en) 2013-07-10 2016-02-02 Alivecor, Inc. Devices and methods for real-time denoising of electrocardiograms
US9378723B2 (en) 2013-08-22 2016-06-28 Qualcomm Incorporated Apparatus and method for acquiring configuration data
US9420956B2 (en) 2013-12-12 2016-08-23 Alivecor, Inc. Methods and systems for arrhythmia tracking and scoring
EP3282933B1 (en) 2015-05-13 2020-07-08 Alivecor, Inc. Discordance monitoring
TWI584542B (en) * 2015-07-03 2017-05-21 新唐科技股份有限公司 Connector and manufacturing method and updating method of the same
US10974139B2 (en) * 2017-11-09 2021-04-13 Disney Enterprises, Inc. Persistent progress over a connected device network and interactive and continuous storytelling via data input from connected devices
WO2021229730A1 (en) * 2020-05-13 2021-11-18 パナソニックＩｐマネジメント株式会社 Wireless communication system
US11750735B2 (en) * 2021-10-28 2023-09-05 International Business Machines Corporation Changing a user interface based on aggregated device capabilities

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5465401A (en) * 1992-12-15 1995-11-07 Texas Instruments Incorporated Communication system and methods for enhanced information transfer
WO1999053621A1 (en) * 1998-04-14 1999-10-21 Qualcomm Incorporated Method and system for interfacing a wireless communication device with an accessory
EP0992900A2 (en) * 1998-10-09 2000-04-12 Nokia Mobile Phones Ltd. Method for installing two or more operating systems/user interfaces into an electronic device, and an electronic device
WO2001043408A1 (en) * 1999-12-09 2001-06-14 Sony Electronics, Inc. Peripheral memory device for a wireless phone and methods of implementing and using same
US20020034971A1 (en) * 1999-02-08 2002-03-21 Chienchung Chang Data allocation for multiple applications on a microprocessor or dsp

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SE516189C2 (en) 1996-07-03 2001-11-26 Ericsson Telefon Ab L M Method and apparatus for activating a user menu in a presentation means
US5848064A (en) * 1996-08-07 1998-12-08 Telxon Corporation Wireless software upgrades with version control
US6496979B1 (en) * 1997-10-24 2002-12-17 Microsoft Corporation System and method for managing application installation for a mobile device
US6189146B1 (en) * 1998-03-18 2001-02-13 Microsoft Corporation System and method for software licensing
FR2785136B1 (en) * 1998-10-21 2000-11-24 Cit Alcatel METHOD FOR REMOTE UPDATING OF THE SOFTWARE OF A RADIOTELEPHONE TERMINAL
US6442754B1 (en) * 1999-03-29 2002-08-27 International Business Machines Corporation System, method, and program for checking dependencies of installed software components during installation or uninstallation of software
JP3669619B2 (en) * 1999-09-06 2005-07-13 富士通株式会社 Software updating method and apparatus for wireless terminal device
US6493871B1 (en) * 1999-09-16 2002-12-10 Microsoft Corporation Method and system for downloading updates for software installation
US20020107809A1 (en) * 2000-06-02 2002-08-08 Biddle John Denton System and method for licensing management
US7165173B1 (en) * 2000-09-01 2007-01-16 Samsung Electronics Co., Ltd. System and method for secure over-the-air administration of a wireless mobile station
US6996815B2 (en) * 2000-11-29 2006-02-07 Microsoft Corporation Method and software tools for intelligent service pack installation
US6976167B2 (en) * 2001-06-26 2005-12-13 Intel Corporation Cryptography-based tamper-resistant software design mechanism
EP1347623A1 (en) * 2002-03-22 2003-09-24 Nokia Corporation Downloading of application software for an accessory device to a mobile terminal
US6970698B2 (en) * 2002-07-23 2005-11-29 Sbc Technology Resources, Inc. System and method for updating data in remote devices
US7062260B2 (en) * 2003-03-27 2006-06-13 Nokia Corporation Fetching application and driver for extension device from network

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5465401A (en) * 1992-12-15 1995-11-07 Texas Instruments Incorporated Communication system and methods for enhanced information transfer
WO1999053621A1 (en) * 1998-04-14 1999-10-21 Qualcomm Incorporated Method and system for interfacing a wireless communication device with an accessory
EP0992900A2 (en) * 1998-10-09 2000-04-12 Nokia Mobile Phones Ltd. Method for installing two or more operating systems/user interfaces into an electronic device, and an electronic device
US20020034971A1 (en) * 1999-02-08 2002-03-21 Chienchung Chang Data allocation for multiple applications on a microprocessor or dsp
WO2001043408A1 (en) * 1999-12-09 2001-06-14 Sony Electronics, Inc. Peripheral memory device for a wireless phone and methods of implementing and using same

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1647129A1 *

Also Published As

Publication number Publication date
CN1802840A (en) 2006-07-12
US20050014531A1 (en) 2005-01-20
EP1647129A1 (en) 2006-04-19
US7305254B2 (en) 2007-12-04
JP2007531339A (en) 2007-11-01

Similar Documents

Publication Publication Date Title
US7305254B2 (en) System and method of software transfer between a mobile phone and a mobile phone accessory
US7900048B2 (en) Method for loading an application in a device, device and smart card therefor
US6591095B1 (en) Method and apparatus for designating administrative responsibilities in a mobile communications device
KR101435295B1 (en) Method and system for performing multi-stage virtual sim provisioning and setup on mobile devices
DE60329162C5 (en) Security element control method and mobile terminal
RU2391796C2 (en) Limited access to functional sets of mobile terminal
EP1361527A1 (en) Method for loading an application in a device, device and smart card therefor
US8126446B2 (en) System and method for provisioning a third party mobile device emulator
US20130045715A1 (en) Method for Transmitting Files and Receiving Files Based on Mobile Terminals, and Mobile Terminal
GB2378531A (en) Providing application / driver software for an accessory of a communications device
JP2006195728A (en) Electronic device mounted on terminal device, and communication system
EP1919247A2 (en) System and method of communication control management
US7817984B2 (en) Mobile communication terminal and computer program thereof, IC card and computer program thereof, and mobile communication terminal system
US9027160B2 (en) Access management system and access management method
KR20090053282A (en) Method and apparatus for indentifing equipments requesting javapush
EP2094036A2 (en) Storage system of mobile terminal and access control method
EP1582052A1 (en) System and method for distributed authorization and deployment of over the air provisioning for a communications device
CN112383663B (en) Display method and device
JP5492988B2 (en) How to manage applications embedded in secured electronic tokens
WO2006010371A2 (en) Method and system for providing communication between communication equipment and a sim-type module, related equipment and computer program product therefor
JP2012074975A (en) Subscriber identity module, portable terminal, information processing method and program
CN115146293A (en) File encryption and decryption method, equipment and medium
CN115344849A (en) Digital key configuration method, system, electronic device and storage medium
EP3648491A1 (en) Multi-configuration secure element and associated method
Chandrasiri First Steps to Software Defined Radio Standards: MExE, the Mobile Execution Environment

Legal Events

Date Code Title Description
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 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 IT 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
WWE Wipo information: entry into national phase

Ref document number: 2004723672

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 5286/DELNP/2005

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2006520023

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 20048160382

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 2004723672

Country of ref document: EP