WO2014184611A1

WO2014184611A1 - Software updating in a mobile terminal

Info

Publication number: WO2014184611A1
Application number: PCT/IB2013/053879
Authority: WO
Inventors: Sami PIENIMÄKI; Antti SAARNIO; Martin Schuele
Original assignee: Jolla Mobile
Priority date: 2013-05-13
Filing date: 2013-05-13
Publication date: 2014-11-20

Abstract

A method for registering an accessory with a mobile terminal includes detecting a coupling of the accessory with the mobile terminal, detecting an identification code associated with the accessory, determining if a software download associated with the accessory is available, determining if the mobile terminal is authorized to receive the software download based on the detected identification code and downloading the software to the mobile terminal if the mobile terminal is authorized to receive the download.

Description

SOFTWARE UPDATING IN A MOBILE TERMINAL

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is related to Application No. , filed on , entitled "Magnetic Coupling of an Accessory Device to a Portable Electronic Device" (Attorney Docket No. JOLM.2255.WOU1; Jolla004), the disclosure of which is incorporated herein by reference in its entirety.

BACKGROUND Field

[0002] The aspects of the present disclosure relate generally to the management of software applications, software drivers and user interfaces of mobile terminals. In particular, the aspects of the present disclosure are related to the management of software when the hardware configuration of a mobile terminal is changed.

Description of Related Art

[0003] When a person connects a new printer in a personal computer (PC) via a

Universal Serial Bus (USB) the printer and the personal computer communicate. Based on the communications, the operating system of the personal computer typically initiates a printer driver setup process. If the drivers or data related to the drivers are already installed in the personal computer, the installation, meaning the adaptation of the software environment to hardware change, is made using the drivers or data in the PC. In the event that the drivers are not found in the personal computer, the personal computer can be configured to connect automatically over a network connection such as the Internet, to an operating system vendor or printer manufacturer web site. The needed drivers can then be downloaded to the personal computer. After downloading the drivers, the software environment of the personal computer is configured or updated to the hardware environment change (i.e. the combination of the personal computer and the printer).

[0004] Most current portable electronic devices, such as mobile terminals, mobile communication devices and smart phone, are based on a monolithic design concept. Generally, these devices have a single configuration without any hardware adaptations, apart from adding for example larger memory card.

[0005] From the consumer point of view, this leads to situation where the consumers have to accept the device configurations that are available. It would be advantageous to be able to provide a modular design for a mobile terminal or communication device, where accessories can be easily attached and de-attached. One aspect of such a modular design is application No. , filed on , entitled "Magnetic Coupling of an Accessory

Device to a Portable Electronic Device" (Attorney Docket No. JOLM.2255.WOU1; Jolla004), the disclosure of which is incorporated herein by reference in its entirety.

[0006] Some accessories might require certain software adaptation to function properly when used in a mobile terminal, as is otherwise described herein. The software adaptations might be needed in the user interface layer, middleware, kernel, drivers or there might be dedicated application related to the accessory. The management of such modifications and adaptations, also referred to as software updates, can be challenging.

[0007] Additionally, when accessories for mobile terminals are modular, one user may provide an accessory used on their device to another user for use on their device. In such cases, the drivers and software in the other device may also need to be installed, reconfigured or updated.

[0008] Accordingly, it would be desirable to provide a smart cover for a mobile terminal that resolves at least some of the problems identified above.

SUMMARY OF THE INVENTION

[0009] As described herein, the exemplary embodiments overcome one or more of the above or other disadvantages known in the art.

[0010] One aspect of the present disclosure relates to a method for registering an accessory with a mobile terminal. In one embodiment, the method includes detecting a coupling of the accessory with the mobile terminal, detecting an identification code associated with the accessory, determining if a software download associated with the accessory is available, determining if the mobile terminal is authorized to receive the software download based on the detected identification code and downloading the software to the mobile terminal if the mobile terminal is authorized to receive the download.

[0011] Another aspect of the present disclosure relates to a system for downloading software related to an accessory of a mobile terminal. In one embodiment, the system includes a magnetic field sensor in the mobile terminal configured to detect a magnetic coupling of the accessory to the mobile terminal; an identification sensor in the mobile terminal configured to detect a unique identifier of the accessory; and a verification system configured to determine if the mobile terminal is authorized to receive a requested download of software based on the unique identifier. [0012] These and other aspects and advantages of the exemplary embodiments will become apparent from the following detailed description considered in conjunction with the accompanying drawings. It is to be understood, however, that the drawings are designed solely for purposes of illustration and not as a definition of the limits of the invention, for which reference should be made to the appended claims. Additional aspects and advantages of the invention will be set forth in the description that follows, and in part will be obvious from the description, or may be learned by practice of the invention. Moreover, the aspects and advantages of the invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed out in the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In the drawings:

[0014] Figure 1 illustrates a perspective view of an exemplary system incorporating aspects of the disclosed embodiments.

[0015] Figure 2 illustrates a front view of a portable electronic device incorporating aspects of the present disclosure.

[0016] Figure 3 is a system flow diagram of a process incorporating aspects of the present disclosure.

[0017] Figure 4 is a system flow diagram of another process incorporating aspects of the present disclosure.

[0018] Figure 5 illustrates a side view of the exemplary system shown in Figure 1.

[0019] Figure 6 illustrates a top plan view of a portable electronic device incorporating aspects of the disclosed embodiments. [0020] Figure 7 illustrates a top plan view of an accessory device incorporating aspects of the disclosed embodiments.

[0021] Figures 8 and 9 illustrate perspective side views of one embodiment of the system illustrated in Figure 1.

[0022] Figure 10 illustrates one embodiment of an electromagnetic loop for use in a system incorporating aspects of the disclosed embodiments.

[0023] Figure 11 is a cross-sectional side view illustrating the use of an electromagnetic loop in an embodiment of a system incorporating aspects of the present disclosure.

[0024] Figure 12 is a cross-sectional side view of an electromagnetic coil an embodiment of a system incorporating aspects of the present disclosure.

[0025] Figure 13 is a side plan view of a portable electronic device with multiple accessory devices in an embodiment of a system incorporating aspects of the present disclosure.

[0026] Figure 14 is a block diagram of an exemplary architecture in which aspect of the present disclosure can be practiced.

DETAILED DESCRIPTION OF THE DISCLOSED EMBODIMENTS

[0027] Referring to Figure 1, one embodiment of a portable electronic device 100 including an attachable and detachable electrically powered accessory device 200 is generally indicated by reference 10. In one embodiment, the device 200 is both mechanically and electrically coupled to the portable electronic device 100 in a manner that allows the accessory device 200 to be removed and reattached in a repeatable manner. The aspects of the disclosed embodiments are generally directed to downloading and updating software in a portable electronic device 100 when an accessory 200 is attached to the portable electronic device 100.

[0028] In the example of Figure 1, the portable electronic device 100 generally comprises a mobile communication device or terminal, such as a smart phone. In alternate embodiments, the portable electronic device 100 can any suitable type of mobile or portable electronic device, including but not limited to a wireless terminal, mobile communication device, a smart telephone, a Mobile Internet Device (MID), a tablet computer, a phablet, an Ultra-Mobile Personal Computer (UMPC), a tablet, a Personal Digital Assistant (PDA), a web pad, a Personal Computer (PC), a Handheld PC, a laptop computer, and a cellular phone. In one embodiment, the portable electronic device 100 may, for example, be implemented using a smart telephone that includes computing hardware which is operable to execute one or more software or computer program products recorded on machine -readable data storage media. In one embodiment, the portable electronic device 100 can include a memory device that is configured to store data and information, such as for example application drivers and application software. For the purposes of the description herein, the portable electronic device 100 will be generally referred to as terminal 100.

[0029] The accessory device 200 illustrated in Figure 1 is configured to be coupled or connected to the terminal device 100 is a manner that allows the accessory device 200 to be easily removed and reattached. In one embodiment, the accessory device 200 is magnetically coupled to the terminal device 100. As shown in Figure 1, the terminal device includes magnetic devices or members 106-108, while the accessory device 200 can include corresponding magnetic devices or members 206-209, shown in Figures 5-7, for example. The magnetic members 106-109 and 206-209 are generally configured to provide a secure mechanical connection between the terminal device 100 and the accessory device 200, enable a flow of electrical power to and between terminal device 100 and the accessory device 200 as well as enable a transmission of data and information to and between the terminal device 100 and the accessory device 200.

[0030] The accessory device 200 is generally any suitable device that can provide functionality for the terminal device 100. Such devices can include, but are not limited to, an input device such as a keyboard or touch screen, a display, a battery, other auxiliary power source, a microphone, a game application, joystick, a game control device, SIM/dual SIM (enabling more than one or additional SIMs to be added to the terminal 100), additional radio modem (such LTE) and additional antennas, NFC cover, audio input & output (e.g. speakers), keyboard, hardware signpad, extra sensors cover (e.g. heart rate and smell), mobile payment cover, camera cover, security-mode cover, privacy/stealth-mode cover, asset tracking cover, gaming cover, brand cover, storage cover, clock cover, e-ink cover, dual boot cover, UI control/interaction cover. In alternate embodiments, the accessory device 200 can include any suitable device that can be releasably attached and reattached to the terminal device 100 in a repeatable manner and requires one or more of electrical power and a data connection. As an example, in one embodiment, the accessory device 200 can comprise an additional display for the terminal 100. In this embodiment, the related software adaptations that need to be downloaded to the terminal 100 can include transcoders for transcoding videos and images in the terminal 100 in a format that can be shown and communicated to the accessory 200. In one embodiment, the accessory device 200 can be configured to be used remotely when detached from the terminal 100. The accessory device 200 can also be configured to communicate with the terminal 100 via short range radio communication such as Bluetooth or wireless local area network connection.

[0031] Figure 2 illustrates a display portion one embodiment of a terminal 100. In this example, the terminal device 100 comprises a mobile communication device, such as a smart phone device or tablet. In one embodiment, the terminal device 100 can include a front side camera 142 that faces the user and a backside camera 144 on the opposite side of the terminal device 100. In alternate embodiments, the terminal device 100 does not have to include a camera.

[0032] In the embodiment shown in Figure 2, the terminal device 100 includes a display 146 on which graphical elements 148 can be presented. In one embodiment, the graphical elements 148 can comprise application elements or icons. In the example shown in Figure 2, six different application icons are presented on the display 146, generally referred to as A-F. In alternate embodiments, any suitable number of graphical elements 148 or application icons A-E can be presented, other than including six. The application icons A-E generally correspond to applications, or application software, that is stored in the terminal device 100. In one embodiment, the application software is stored in a memory of the terminal device 100. As will be generally understood, when a user selects an application icon A-E, such as icon C, the corresponding application starts or is opened.

[0033] One or more of the application icons A-E shown in Figure 2 can be related to an accessory 200 that is configured to be installed in, coupled or attached to the terminal device 100. For example, the application icon F could correspond to a word processing application that is installed in the terminal device 100 and is enabled when the accessory device 200 that is coupled to the terminal device 100 is a keyboard. In one embodiment, the application icon F corresponding to the word processing application will only be enabled or visible when the keyboard accessory device 200 is coupled to the terminal device 100. For example, in one embodiment, the application icon F, while visible on the display 146 may be grayed out when a keyboard accessory device is not attached to the smart phone device 140, to show that the word processing application is not available or active.

[0034] The installation of the word processing application corresponding to application icon F can initiate when the keyboard accessory device 200 is first detected to be coupled to the terminal device 100. Generally, the detection of the coupling or attachment of an accessory 200 to the terminal device 100 will trigger a software configuration change or update. The software configuration change triggered by the accessory 200 can take place at any layer of the software, including for example, drivers, middleware, applications and user interfaces. The software configuration changes are deep, behavioral and holistic configuration changes, not limited to the user interface and graphics. The configuration changes can enable new functionality that goes all the way through the full architecture of the software, and can even change the architecture, for example by enabling a new operating system.

[0035] Referring to Figure 3, when an accessory 200 is coupled to the terminal device 100 for the first time, an identification code that is unique to the accessory 200 can be detected S3.1. The identification code can be any identifier that can be used to identify the accessory device 200, and can include, but is not limited to, a quick response (QR) code. In one embodiment, the identifier can be provided by an identifier device or chip 400 that is disposed on or in the accessory device 200, such as for example a near field communication (NFC) device. In one embodiment, the terminal 100 can include a near field communication tag and the accessory device 200 can include a near field communication tag. As is generally understood, near field communication is a wireless technology which allows for the transfer of data such as text or numbers between two NFC enabled devices. NFC tags, which can include for example stickers, can contain small microchips with small aerial antenna. NFC tags can store small amounts of information for transfer to another NFC device, such as a mobile phone. NFC tags can be used to pair devices, such as the terminal 100 with the accessory device 200. However, in accordance with the aspects of the disclosed embodiments, in one exemplary embodiment as shown in Figure 1, the terminal 100 can include two NFC tags 12, 14, one in each corner of the terminal 100. One of the tags 12, 14 can be used for pairing, while the other one of the tags 12, 14 can be used for the communication of data and information, as is described herein.

[0036] The identifier is configured to be read or detected by the terminal device 100 when the accessory device 200 is coupled to the terminal device 100, as is generally described herein. In one embodiment, the identification of the accessory 200 is based on strong digital authentication.

[0037] The identifier can be read automatically by the terminal device 100, or the identifier can be manually entered using a touch pad or keyboard 402 that is part of the accessory device 200. Although a touch pad or keyboard 402 is described with respect to this example, it will be understood that the identifier can be manually entered using any suitable input device, other than including a touch pad or keypad. For example, in one embodiment, when a coupling of the accessory device 200 with the terminal device 100 is detected, a prompt can appear on the display of the terminal device 100 or the accessory device 200, which prompt can enable a selection of the identifier. As another example, if the identifier is a quick response code, and the terminal device 100 includes a camera or optical device 112, the quick response code can be read by the camera 112. [0038] An action resulting from reading the identifier is executed S3.2. In one embodiment, an action can include, but is not limited to, establishing a connection to a system that has the software required for the application associated with the accessory device 200. This can include for example, establishing a network connection, such as with the Internet, to connect to a server system 600 hosting a website that is associated with the accessory device 200 and from which the software or drivers for the accessory device 200, and the applications related thereto, can be obtained.

[0039] In one embodiment, the server system 600 is configured to check S3.3 from a software configuration management system/database 602 and determine whether the detected identifier is valid. It can also be determined whether the terminal device 100 has authorization to download and install the software related to the accessory 200. Although the server system 600 and software configuration management system/database 602 are shown as different entities in Figure 3, in alternate embodiments the same entity or system can run one or both. For example, in one embodiment software related to these backend components can be implemented as cloud service or can be installed in one or more servers. An exemplary environment can include for example Apache servers and a database environment can be for example MySQL servers.

[0040] In one embodiment, an accessory 200 can be verified by an authorization process carried out or executed by the server system 600 or software configuration management server 602. The authorization process can include testing the compliance and operation of the accessory 200 and verifying that the accessory 200 works with other devices and terminal. The International Mobile Equipment Identity number (IMEI) of the terminals 100, or International Mobile Subscriber Identity (IMSI) number of a users, which can use and be allowed access to the accessory 200 can be set in the databases during the authorization process. The accessories 200 can also be given a set of identifiers during the authorization process.

[0041] The software configuration management server 602 can maintain data and information of some or all of the software components of the terminal 100. This can include maintaining information on terminals 100 with no accessories 200 in addition to terminals with registered accessories 200. In one embodiment, the software configuration management server 602 can be used as backup server for the terminal 100 as well as used for configuring a new terminal purchased by a consumer.

[0042] As is illustrated in the flow diagram of Figure 3, in one embodiment, the software related to the accessory 200 is downloaded S2.4 to the terminal device 100. The software is then installed in the terminal device 100 and any needed software configuration adaptations are executed during the installation procedure. If the software management system 602 or server system 600 denies the download of the software, step S2.4 can include a suitable notification to the user.

[0043] In one embodiment, a notification can be provided S3.5 to the server system

600 upon a successful downloading and installation of the software. The database 602 can be updated S3.6 from the terminal device 100 or by the server system 600 to reflect the new software installation and hardware configuration of the terminal device 100. Examples of the information that can be provided to the database 602 for the update, can include, but is not limited to an IMEI code, memory usage of the terminal device 100, location updates, radio environment information, phone number, identifications (ID) of accessories 200 associated with the ID of the terminal device 100, usage history of accessories 200, software versions of applications in the terminal device 100 and software versions of other software modules in the terminal device 100.

[0044] In one embodiment, the software configuration changes are communicated from the accessory 200 to the terminal 100. In this example the software configuration changes are stored within and distributed from the accessory 200, and not the server system 600. In one embodiment, the software configuration changes can be stored in a memory storage device of the accessory 200 and downloaded from the memory storage device to the terminal device 100.

[0045] A number of possible scenarios exist where the installation of an accessory

200, including the registration and downloading of software related to the accessory 200 can be allowed or disallowed. For example, in one embodiment, the accessory device 200, when coupled to the terminal device 100, requires software for the proper operation of the accessory device 200 and any associated application program. However, in this example, the software can only be downloaded and installed to one terminal device 100, such as a mobile terminal, at a time. This means that once the software related to an application for an accessory 200 has been downloaded to a terminal device 100, the software cannot be downloaded to another terminal without the current or prior installation being uninstalled or otherwise disabled. In this situation, the database 602 is checked to see if the software related to the accessory 200 is installed in a terminal other than current terminal device 100. If the software is not installed in another terminal, the terminal device 100 is allowed to install the software from server system 600. However, if the software associated with the identifier of the accessory 200 already been downloaded and installed in another terminal, the user of the accessory 200 is notified and the requested software download and modifications are not authorized. [0046] In another embodiment, the user of the other terminal in which the software related to the accessory 200 is currently downloaded, can be notified that their accessory 200 is being installed in the terminal 100 or that a request to have software related to the accessory 200 downloaded to the terminal 100 has been received. The user of the other terminal might decide to release the software to the terminal 100. This might initiate an uninstallation and/or deactivation process of the software in other terminal. This particular aspect of the disclosed embodiments can be helpful in preventing unauthorized use of an accessory, since the owner of a terminal to which the accessory related software is downloaded must approve a subsequent download of the same accessory related software to another terminal.

[0047] As another example, the accessory device 200, when coupled to the terminal device 100, requires software for the proper operation of the accessory device 200 and any associated application program. In this embodiment, the software is capable of being downloaded to and installed in more than terminal device 100 at a time. This means that different instances of the software can be downloaded and installed in different terminals 100, without the need to uninstall or de-authorize a prior or earlier installation. In this situation, when the identifier is detected S3.1, the database 600 is checked S3.2 to determine if the identifier is valid. If the identifier corresponding to the accessory is valid, an identifier of the terminal 100 is stored in the database 600. In this manner, the database 600 can maintain a record of the terminals that have downloaded and installed the software related to the accessory 100. The download and installation process is then initiated S3.3, S3.4.

[0048] In another embodiment, a limit can be set on the number of times the software related to the accessory 200 can be downloaded and installed. In one embodiment, after the identifier for the accessory 200 is detected S3.1, the database 600 is checked to determine S3.2 if the identifier is valid. A counter associated with the specific software related to the accessory 200 is checked to determine whether a pre-determined download limit has been met or exceeded. If the identifier for the accessory 200 is valid and the counter has a count value that is less than or equal to a pre-determined download limit, the download process can be initiated S3.3, S3.4. In one embodiment, the counter can be updated or incremented to reflect the download.

[0049] In one embodiment, the accessory 200 is associated with a gaming application and the terminal device 100 is configured to run the gaming application. In this embodiment, a basic version of the game application can be downloaded to or stored in the terminal device 100. When coupling of the gaming accessory 200 is detected, the installation process of the accessory 200, generally referred to with respect to Figure 3, can initiate a search to determine if related software is needed or whether updates are available for the gaming application. Examples of such updates can include, but are not limited to, new levels, new tools, troops or other resources and features related to the game. In one embodiment, the installation of the accessory 200 can trigger a modification of the gaming application software to utilize different or modified controls. For example, the accessory 200 can comprise a joystick type device, or other such game controller, that can be used to control the game. As new controls are added, the software can be updated accordingly.

[0050] In one embodiment, a set of rules can be associated with the gaming accessory

200. For example, there can be a limit set as to the number of times the gaming accessory 200 can be registered, such as in the process described with respect to Figure 3. The accessory registration process can also be used to connect one or more users together, in a manner similar to a social network. Since information pertaining to each download is stored in the server system 600, this information, including the identifier of the accessory 200, can be used to connect the different users that have downloaded the software related to the accessory.

[0051] In one embodiment, the accessory device 200 comprises a gaming cover for the terminal 100. When the gaming cover is coupled to the terminal device 100, the game related identifier that is associated with the gaming cover is used to install as well as update the application software associated with the game application. If the gaming cover is transferred from a current terminal device to another terminal device, the registration process described with respect to Figure 3 is repeated. The various terminal devices, or users, can be defined to be within a social network based on the information obtained during the registration process.

[0052] In one embodiment, the accessory device 200 can comprise a branded cover for the terminal device 100. The branded cover can include a unique identifier and the registration process described in Figure 3 will initiate a software download or update process. In this example, the download can comprise a brand related theme, including ringtones and sounds, or background for the terminal device 100. In one embodiment, the background image for the terminal device 100 would automatically change to a brand related background that has been downloaded. This could also include periodic and automatic changes in themes and background as the owner of the brand provides such changes and updates. Other downloads and updates could include, but are not limited to, colors, ring tones, fonts and a brand image.

[0053] In one embodiment, where the accessory device 200 comprises a branded cover, the software downloads associated with a particular cover can be limited to one terminal device 100 at a time to reduce the possibility of duplicating and copying without authorization. In this embodiment, download authorization may need to come from the brand owner or current terminal user. For example, when coupling of the branded cover to the terminal device 100 is detected, as is generally described herein, in one embodiment, the verification and authorization process could include a registration process with the brand owner. For example, a user name and password may be required to initiate the software download to the terminal device 100. This can include the presentation of such login information on the display 142 of the terminal device 100 when coupling of the accessory 200 to the terminal device 100 is detected. Alternatively, a branded cover can be distributed without restriction on the number of downloads or the need to revoke a software configuration from another terminal device 100. In one embodiment, the data recorded in the server system 600 related to the sharing of the cover by different users, based on the registration process described with respect to Figure 3, can be used to create a network or social network for activities that can include, but are not limited to marketing, advertising and other such purposes.

[0054] Figure 4 illustrates one embodiment of a process for revoking rights associated with a software download. In this example, accessory 200 is initially associated with terminal device 100. The accessory related software can one be downloaded to, or installed in one terminal at a time. Thus, if the accessory 200 is transferred to a requesting terminal device 111 shown in Figure 4, the software related to accessory 200, currently downloaded to and registered with terminal device 100, must be un-registered before it can be downloaded and installed in requesting terminal device 111.

[0055] Accessory 200 includes a unique identification code or identifier 12. In one embodiment, the identification code 12 can be read S4.1 automatically by the terminal device 111 or entered manually when the accessory 200 is coupled to the terminal device 111. An action resulting from the reading S4.1 of the identification code 12 is executed S4.2. This can include for example, establishing a communication connection with a server system 600, over a network, such as the Internet or a mobile communication network. The server system 600 can be linked or communicatively coupled to a website or other data storage location that maintains the software that is related to the accessory.

[0056] In one embodiment, the server system 600 determines S4.3 from the software configuration management system/database 602 whether the identifier 12 associated with the accessory 200 is valid and authorized, as well as whether the requesting terminal device 111 is authorized to install the software related to the accessory. In this example, the accessory 200 is identified S4.4 in the database 602 as only be able to be associated with one terminal at a time, and that the accessory 200 is currently associated with terminal 100 in the database 602. In this situation, a notification is sent S4.4 to the server 600 indicating that the download request cannot be honored because the accessory 200 is associated with a terminal device 100, which is different from the requesting terminal device 111.

[0057] The terminal 100 is then notified, S4.5, either directly from the server 600 or the database 602, that a download of software related to the accessory 200 is being requested by another terminal, in this case requesting terminal device 111. The notification can be sent for example by using an Internet Protocol connection, a push notification message, multimedia message service (MMS) message or a short message service (SMS) message. The notification S4.5 will generally comprise an ownership change request.

[0058] In one embodiment, a reply S4.6 is sent from the terminal 100 back to the server system 600 or database 602, and will indicate whether the request to change the ownership of the accessory device 200 from terminal 100 to terminal 111 is declined or accepted. This owner verification feature can reduce the risk of the use of a stolen accessory device 200.

[0059] If the ownership change request is granted, a message S4.7 can be sent to the software configuration management system 602 via the server system 600 or directly from the terminal device 100 that informs the software configuration management system 602 that the request is granted. In this case, the software components related to the accessory 200 are removed from or disabled in the terminal device 100. The removal of the software components can be monitored by the software configuration management system 602. For example, in one embodiment, a check sum of software setup on the terminal device 100 can be sent to the system 602 to verify that all components are disabled or removed from the terminal device 100.

[0060] Once the software components are removed from the terminal device 100, the download to the requesting terminal 111 can commence S3.8. In this embodiment, the software components are downloaded and the configuration change is recorded in the server system 600. In one embodiment, the requesting terminal 111 can send S3.9 a notification to the server system 600 of the updated configuration. The configuration is stored S3.10 in the software configuration management system 602 to reflect the new ownership of the accessory 200. An identifier associated with the requesting terminal 111 can also be stored and associated with the accessory 200 in the server system 600.

[0061] Referring to Figures 5-7, one embodiment of a system 10 incorporating aspects of the disclosed embodiments is illustrated. In this example, the terminal device 100 includes a first or front side 102 and a second or back side 104. In one embodiment, the front side or first side 102 of terminal device 100 might include a keyboard and a display (not shown), in a fashion as is generally understood in the art. The back or second side 104 may include a battery, battery compartment or connection (not shown), as is generally understood in the art. It will be understood that although the terminal device 100 is generally described herein as having a front and a back side with respective functionality, the aspects of the disclosed embodiments are not so limited, and the functionalities described with respect to the front side 102 and back side 104 could be reversed.

[0062] The accessory device or cover part 200 is configured to be attached and reattached to the terminal device 100 in a manner that allows the accessory device 200 to be provided with one or more of electrical power from the terminal device 100 and a data communication connection to and between the terminal device 100. In the example shown in Figure 7, the accessory device 200 has a first side 202 and a second side 204, with the second side 203 of the accessory device 200 being configured to be communicatively and releasably coupled to the second side 104 of the terminal device 100. Although the second side 204 of the accessory device 200 is generally described herein as being coupled to the second side 104 of the terminal device 100, the aspects of the disclosed embodiments are not so limited, and a suitably configured side 202, 204 of the accessory device 200 can be coupled to a suitably configured side 102, 104 of the terminal device 100, as is further described herein.

[0063] In the example illustrated in Figures 5-7, the second side 104 of the terminal device 100 includes one or more magnetic devices or members 106, 108, which are suitably mounted in, or coupled to the second side 104. For example, in one embodiment, the magnetic members 106, 108 can be secured to the second side 104 by the use of an adhesive, cement, screw, pin, rivet, sonic welding, or other suitable fastener or fastening system. In one embodiment, the magnetic members 106, 108 are integrally formed in or embedded in the second side 104. [0064] The magnetic device 106, 108 will generally comprise magnets, or other suitable material or element that has magnetic properties, such as metal or steel. The polarity of the magnetic members 106, 108 will generally depend upon the particular connection application, as is further described herein.

[0065] Generally, the magnets 106, 108 will be configured to be substantially flush with a surface 110 of the second side 104, so as to present a substantially flat surface 110. In alternate embodiments, the magnets 106, 108 can be configured to extend or protrude above the surface 110. This can be advantageous where a space or gap is needed between the terminal device 100 and the accessory device 200, such as for cooling.

[0066] Although only four magnets 106-109 are shown in Figures 5-7 with respect to the terminal device 100, in alternate embodiments, any suitable number of magnets can be used, including more or less than four.

[0067] As is shown in Figure 6, the accessory device 200 includes magnetic members

206-209 on the second side 204 of the accessory device 200. The accessory device 200 is configured to be coupled to the terminal device 100 by coupling of the magnetic members 106-109 to magnetic members 206-209. While the magnetic members 206-209 will generally be described herein as magnets, the magnetic members 206-209 can comprises any suitable material or element that can be magnetized or is otherwise magnetically attracted. For example, in one embodiment, one or more of the magnetic members 206-209, or a combination thereof, comprise metal parts that are magnetically attracted to one or more of the magnetic members 106-109. Alternatively, one or more, or a combination thereof, of the magnetic members 106-109 can comprise metal parts. The locations and positions of the respective magnetic members 106-109 and 206-209 allow the terminal device 100 to be connected to the accessory device 200. The connection is configured to not only provide a secure mechanical connection, but to also provide an electrical and a data communication connection to and between the terminal device 100 and the accessory device 200. The aspects of the disclosed embodiments advantageously eliminate the need to have a mechanical type of fastener and connector to mechanically and electrically join the terminal device 100 and the accessory device 200. In accordance with the aspects of the disclosed embodiments, the magnetic interaction and coupling of the magnetic members 106-109 and 206-209 mechanically and electrically couple the terminal device 100 with the accessory device 200.

[0068] Figures 8-9 illustrate different examples of exemplary accessory devices 200 used in conjunction with the terminal device 100. In Figure 8, the terminal device 100 has a camera with a camera lens or optics 112. The accessory device 200 in this example includes a camera device 212 with an opening 208 in the accessory device 200 that is aligned with the camera lens 112 to allow the camera and camera optics 112 of the terminal device 100 to continue to function and be utilized in conjunction with the camera device 212 of the accessory 200. For example, the camera device 212 may provide additional functionality to the camera device 112 of the terminal device 100. In one embodiment where the terminal device 100 does not include a camera device, the accessory 200 can be used to provide the camera. The camera device 212 of the accessory device 200 can include a communication coupling through one or more of the magnetic members 206-209 that allows the camera view from the camera 212 to be presented on a display 146 of the terminal device 100.

[0069] In one embodiment, the connection of the accessory 200 to the portable electronic device 100 through the magnetic coupling of magnetic members 106-109 and 206- 209 allows the accessory to be electrically powered or charged. For example, referring to Figure 9, in one embodiment, the accessory 200 includes a power storage device 220, such as a battery power supply. In this example, the battery 220 is a chargeable or rechargeable battery or power supply and is electrically coupled to the magnetic members 206, 207. The magnetic members 106, 107 of the terminal device 100 are electrically coupled to a power source or power supply. When magnetic members 106, 107 are magnetically coupled to magnetic members 206, 207, an electrical circuit is formed, which allows electrical power to be delivered to the power storage device 220 and charge the battery in this case. In the embodiment of Figure 8, the electrical power from the terminal device 100 can be used to power the camera device 212.

[0070] In one embodiment, referring to Figure 9, the electrical circuit can also be formed by the use of electrically conductive pins 224 on the accessory device 200 that connect to receptacles on the terminal device 100. In one embodiment, accessory device 100 can include galvanic power contacts 226. Alternatively, the power storage device 220 can be electrically charged using an inductive device.

[0071] For example, referring to Figure 10, in one embodiment, one or more electrical loops 310 are disposed in the terminal device 100. The electrical or inductive loops 310 are configured to generate an electric or electromagnetic field 304 when power or current is applied to the loop 310. An electrical or inductive loop 320 in the accessory device 200 is electrically or magnetically coupled to the electromagnetic field 304, which generates electrical power in the accessory device 200. Although only one loop is shown in each of the terminal device 100 and accessory device 200 in the example of Figure 10, it will be understood that the terminal device 100 and accessory device 200 can include more than one inductive loop. [0072] One of the challenges with inductive loop/wireless charging is the efficiency of the coupling. Some of the energy is lost due to the open core structure of the inductive loop. In one embodiment, one or more of the magnetic members 106, 108 of the terminal device 100 and one or more of the magnetic members 206, 028 of the accessory device 200 or located within an area encompassed by the respective inductive loops 310, 320 shown in Figure 10. This forms a closed core structure for inductive coupling.

[0073] For example, referring to Figure 11, magnets 306, 308 are electrical coupled together with a metal strip or element 312. Metal parts or terminals 326, 328 are electrically connected together with metal strip or element 324.

[0074] The magnet 306 is positioned within an area encompassed by the magnetic loop 310 of the terminal device 100. The metal part 326 is positioned within an area encompassed by the receiving inductive loop 320 of the accessory device 200. This configuration of the respective inductive loops 310, 320 positioned around a magnetic device or metal part, enhances the efficiency of the inductive charging from the terminal device 100 to the accessory device 200.

[0075] In one embodiment, the polarity of the magnetic device 306 is selected so that some of the magnetic force can be eliminated by inducing sufficient electrical current, in the correct direction, to the inductive coil 310. This makes it easier to detach the accessory device 200 from the terminal device 100.

[0076] Figure 12 illustrates on embodiment for implementing conductivity between the portable electronic device 100 and the accessory device 200. The illustration in Figure 12 shows a cross sectional view of one embodiment of a terminal device 100 and an accessory device 200 incorporating aspects of the present disclosure. In this embodiment, the terminal device 100 includes magnetic members 106 and 108. The magnetic members 106 and 108 are conductively coupled to each other with a conductive member 130. The conductive member 130 generally comprises any material or element that is configured to conduct electrical signals and energy, such as a metal for example. An inductive or electrical coil 132 is turned around the conductive member 130. In one embodiment, the electrical coil 132 is a strand of conductive material, such as wire, that is turned or coiled around the conductive member 130. The coil 132 is used to form an electromagnetic field for energy transfer as well as data communication. For example, in one embodiment, electrical energy or communication signals are passed through the coil 132. The energy is transferred to the conductive member 130 in a manner that is generally understood. This energy can then be transferred to the accessory device 200 through the magnetic members 106, 108 to the corresponding magnetic members 206, 208, as is generally described herein.

[0077] As is shown in Figure 12, the accessory device 200 includes magnetic members 206, 208, which can also include or comprise electrically conductive members. The magnetic members 206, 206 are electrically coupled or connected together with a conductive member 230, similar to the conductive member 130. A coil 232 is turned around the conductive member 130, in a manner similar to the coil 132 described above. The coil 232 is used to form an electromagnetic field for energy transfer purposes as well as data communication. When the accessory device 200 is coupled to the terminal device 100 using the combination of magnet 106, 108 and 206, 206, the conductive members 130, 230 and coils 132, 232, allow electrical energy and data communication to be transferred to and between the terminal device 100 and the accessory device 200. In one embodiment, a particular type of accessory 200 can be defined and identified by the characteristics of the magnetic field that is associated with the accessory 200. Thus, the coil 232 can be specifically designed for a particular type of accessory device 200.

[0078] The aspects of the disclosed embodiments provide a number of practical applications. For example, in one embodiment, the portable electronic device 100 can include an inductive charging loop, such as that shown for example in Figure 12. The inductive charging loop can be used to charge the accessory device 200 or provide electrical power to the accessory device 200. The accessory device 200 and also be used a receiving part when the portable electronic device 100 is to be charged. For example, in this embodiment, the accessory device 200 can comprise an electrical or battery charger. The accessory device 200 is magnetically coupled to the portable electronic device 100 as is generally described herein. The magnetic coupling, which provides a physical and electrical connection, allows the accessory device 200 to provide electrical power to the portable electronic device 100. The electrical power can be provided inductively, using the loops 232 and 132 shown in Figure 12, or the magnetic members 106, 108 and 206, 208 can provide electrical contacts that are coupled to suitable electrical and electronic circuits, that provides for the flow of electrical power and data signals, to and between the accessory device 200 and the portable electronic device 100. The magnetic members 106 and 206, as well as 108 and 208, will align the portable electronic device 100 with the accessory device 200 to ensure that the coils 132, 232 are properly aligned to provide the inductive coupling for applications such as charging. Also, as noted with respect to the embodiment shown in Figure 11, the magnetic members, such as 106 and 206, can be positioned within an area encompassed by the loops 310 and 320.

[0079] In one embodiment, the terminal device 100 can also include a magnetic field sensor or magnetometer 140, generally shown in Figure 1. The magnetic field sensor 140, which is generally internal to the terminal device 100, can be used to detect when an accessory device 200 is attached or decoupled from the terminal device 100. Although the example shown in Figure 1 shows the magnetic field sensor 140 as being separate from the magnetic member 106, in one embodiment, the magnetic field sensor 140 can be integrated within one or more of the magnetic members 106-109. Also, although only one magnetic sensor 140 is shown in Figure 1, in alternate embodiments, any suitable number of magnetic sensors 140 can be used, including more or less than one. The location of the magnetic sensors 140 can also be at any suitable position on the terminal device 100 that can be used to detect the presence of the accessory device 200.

[0080] Figure 13 is a block diagram illustrating an exemplary operating environment for performing the disclosed methods. This exemplary operating environment is only an example of an operating environment and is not intended to suggest any limitation as to the scope of use or functionality of operating environment architecture. Neither should the operating environment be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment.

[0081] The present methods and systems can be operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that can be suitable for use with the systems and methods comprise, but are not limited to, personal computers, server computers, laptop devices, and multiprocessor systems. Additional examples comprise set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, and distributed computing environments that comprise any of the above systems or devices, and the like. [0082] The processing of the disclosed methods and systems can be performed by software components. The disclosed systems and methods can be described in the general context of computer-executable instructions, such as program modules, being executed by one or more computers or other devices. Generally, program modules comprise computer code, routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The disclosed methods can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including memory storage devices.

[0083] The systems and methods disclosed herein can be implemented via one or more portable electronic devices 100, such as that shown in Figure 1. As is illustrated in Figure 13, in one embodiment, the components of the portable electronic device 100 can include, but are not limited to, one or more processors or processing units 703, an operating system 705, a network adapter 708, a system data storage device or memory 712, an Input/Output Interface 710, a display adapter 709 and a system bus 713 that couples various system components including the processor 703 to the system memory 712. In the case of multiple processing units 703, the system can utilize parallel computing.

[0084] The one or more terminal device 100 typically include computer readable media. Exemplary readable media can be any available media that is non-transitory and accessible by the portable electronic device 100 and comprises, for example and not meant to be limiting, both volatile and non-volatile media, removable and non-removable media. The system memory 712 comprises computer readable media in the form of volatile memory, such as random access memory (RAM), and/or non-volatile memory, such as read only memory (ROM). The system memory 712 typically contains data such as demand control data 707 and/or program modules such as an operating system 705 that is immediately accessible to and/or are presently operated on by the processing unit 703. In one aspect, the system memory 712 contains computer executable codes sections for performing the processes and steps described herein.

[0085] In another aspect, the portable electronic device 100, as well as the accessory device 200, can also comprise other non-transitory, removable/non-removable, volatile/nonvolatile computer storage media. By way of example, the system memory 712 can in one embodiment include or comprises a mass storage device that can provide non-volatile storage of computer code, computer readable instructions, data structures, program modules, and other data for the portable electronic device 100. For example and not meant to be limiting, a mass storage device can be a hard disk, a removable magnetic disk, a removable optical disk, magnetic cassettes or other magnetic storage devices, flash memory cards, CD-ROM, digital versatile disks (DVD) or other optical storage, random access memories (RAM), read only memories (ROM), electrically erasable programmable read-only memory (EEPROM), and the like. In one embodiment, the accessory device 200 can optionally also include one or more processor(s) 714 as well as memory 716, as those terms are generally described herein.

[0086] Thus, while there have been shown, described and pointed out, fundamental novel features of the invention as applied to the exemplary embodiments thereof, it will be understood that various omissions and substitutions and changes in the form and details of devices and methods illustrated, and in their operation, may be made by those skilled in the art without departing from the spirit and scope of the invention. Moreover, it is expressly intended that all combinations of those elements and/or method steps, which perform substantially the same function in substantially the same way to achieve the same results, are within the scope of the invention. Moreover, it should be recognized that structures and/or elements and/or method steps shown and/or described in connection with any disclosed form or embodiment of the invention may be incorporated in any other disclosed or described or suggested form or embodiment as a general matter of design choice. It is the intention, therefore, to be limited only as indicated by the scope of the claims appended hereto.

Claims

CLAIMS What is claimed is:

1. A method for registering an accessory with a mobile terminal, the mobile terminal including a controller that is configured to:

detect a coupling of the accessory with the mobile terminal;

detect an identification code associated with the accessory;

determine if a software download associated with the accessory is available;

determine if the mobile terminal is authorized to receive the software download based on the identification code; and

download the software from a server if the mobile terminal is authorized to receive the download.

2. The method of claim 1, comprising:

determining in the server that the software is registered to another mobile terminal; initiating a transmission of a request message to the another mobile terminal to release the registered software; and

downloading the software to the mobile terminal from the server over a communication channel between the mobile terminal and the server when a release authorization message is received from the another mobile terminal.

3. The method of claim 2, comprising uninstalling the software from the another mobile terminal prior to downloading the software to the mobile terminal.

4. The method of claim 2, comprising revoking an authorization associated with the another mobile terminal prior to downloading the software to the mobile terminal.

5. The method of any preceding claim, comprising registering the mobile terminal in a database when the software is downloaded.

6. The method of any preceding claim, comprising detecting the coupling of the accessory with the mobile terminal using a magnetic field sensor to detect a presence of the accessory device, the identification code being provided to the mobile terminal through a magnetic coupling of the accessory to the mobile terminal.

7. The method of any preceding claim, wherein the accessory is coupled to the mobile terminal through a coupling of magnetic members on the mobile terminal and the accessory, the coupling of the magnetic members providing a mechanical and electrical connection between the mobile terminal and the accessory.

8. The method of claim 7, wherein electrical power and a data connection is provided to and between the mobile terminal and the accessory through the coupling of the magnetic members.

9. The method of any preceding claim, comprising initiating an application in the mobile terminal related to the accessory after detecting the coupling of the accessory with the mobile terminal.

10. The method of any preceding claim, wherein the identification code is a quick response code or a identifier stored in a near field communication chip.

11. The method of any preceding claim, wherein the mobile terminal establishes a communication connection with a software configuration management system to determine if the mobile terminal is authorized to receive the software download based on the identification code.

12. A system comprising computer readable code means recorded in a memory of a processing device, the computer readable code means including instructions, that when executed by the processor, are configured to implement the method according to claims 1-11.

13. A system for downloading software related to an accessory of a mobile terminal, comprising:

a magnetic field sensor in the mobile terminal configured to detect a magnetic coupling of the accessory to the mobile terminal;

an identification sensor in the mobile terminal configured to detect a unique identifier of the accessory; and

a verification system configured to determine if the mobile terminal is authorized to receive a requested download of software based on the unique identifier.

14. The system of claim 13, comprising a software configuration management system configured to access software downloads related to the accessory and maintain a registry of software downloads to mobile terminals.

15. The system of claim 14, wherein the software configuration management system is configured to:

determine that the accessory is registered with another mobile terminal;

transmit a request message to the another mobile terminal for a release of the accessory; and

enabling a release of the download to the mobile terminal when a reply message from the another mobile terminal includes a release code.

16. The system of any one of claims 13-15, comprising a magnetic member in the mobile terminal and a magnetic member in the accessory, a magnetic coupling of the magnetic member in the mobile terminal and the magnetic member in the accessory providing an electrical and data communication connection to and between the mobile terminal and the accessory.