RECEIVING BROADCAST SIGNALS USING INTELLIGENT COVERS FOR MOBILE DEVICES

Info

Publication number: 20090069052
Type: Application
Filed: Sep 12, 2008
Publication Date: Mar 12, 2009
Applicant: DEVICEFIDELITY, INC. (Richardson, TX)
Inventors: Deepak Jain (Garland, TX), Tuan Quoc Dao (Richardson, TX)
Application Number: 12/210,176

Abstract

The present disclosure is directed to a system and method for receiving broadcast signals using intelligent covers. In some implementations, a cover for a consumer device includes side surfaces, a rear surface, a physical interface, a circuit, and a broadcast service card. The side surfaces and a rear surface form an opening that receives at least a portion of a consumer device. A first portion of at least one of the surfaces includes a connector for connecting to a port of the consumer device. The circuit connects the physical interface to the connector. The broadcast service card connects to the physical interface and receives broadcasted content independent of the consumer device.

Description

Description

CLAIM OF PRIORITY

This application claims priority under 35 USC §119(e) to U.S. Patent Application Ser. No. 60/971,813, filed on Sep. 12, 2007, the entire contents of which are hereby incorporated by reference.

TECHNICAL FIELD

This invention relates to network communications and, more particularly, to receiving broadcast signals using covers for mobile devices.

BACKGROUND

Portable electronic devices and tokens have become an integrated part of the regular day to day user experience. There is a wide variety of common portable and handheld devices that users have in their possession including communication, business and entertaining devices such as cell phones, music players, digital cameras, smart cards, memory token and variety of possible combinations of the aforementioned devices and tokens. All of these devices share the commonality that consumer are accustomed to carrying them with them most of the time and to most places. This is true across the various demographics and age groups regardless of the level of the sophistication of the consumer, their age group, their technical level or background.

These common handheld devices offer options for expandable memory. Micro Secure Digital (microSD) is the popular interface across high-end cellphones while SD and MultiMediaCard (MMC) interfaces are also available in limited models. MicroSD is the least common denominator supported by the majority of these devices and tokens (in terms of size). In addition, adaptors are available to convert a MicroSD into MiniSD, SD, MMC and USB Although most popular MP3 player (iPOD) offer's a proprietary interface, competing designs do offer standard interfaces. Digital cameras offer mostly SD and MMC while extreme Digital (xD) is another option. Micro and Mini versions of these interfaces are also available in several models. Mini-USB is increasingly available across cellphones, digital cameras and MP3 players for synchronization with laptops.

Various content providers and service providers are developing digital broadcast networks that will be able to provide TV like viewing channels on mobile devices. Several new mobile handset models are also being developed that embed a miniature broadcast receiver that can receive these digital broadcast signals and use a media player software to offer channel viewing to the consumer. In order to secure access and provide access to premium content like movies, subscription based pay-TV content and music albums, the service provider uses a specially designed conditional access system (CAS) which is able to verify the user's subscription and unscramble premium content before rendering it for viewing.

Such capability can be added to the PC, by adding a hardware transceiver that can be added to the PC using peripheral interfaces such as USB, PCMCIA, PCIA or mini-PCI (and others). To control access, the conditional access system is implemented in the same hardware and comprises of a smart card that securely stores the user's identity and his subscription privileges. In addition, the service provider provides an Electronic Service Guide that the user can use to select the channels that he wishes to view. This software is typically installed on the PC together with the access driver for the hardware. In some options, the default channel guide provided by the operating system of the PC (such as Windows Vista/MacOS etc.) can be used.

There are other consumer devices such as smartphones, MP3 players, game players and portable video players that may make use of broadcast content connection for useful applications. Since the hardware for the broadcast receiver and the conditional access system is specialized and requires a dedicated processor to receive and unscramble content, many of these devices may not be upgraded with an embedded broadcast reception capability. In addition, these devices also lack PCMCIA or USB type expansion slots where broadcast receiver and CAS hardware could be inserted. These devices also typically lack the slot for a hardware security token such as a smart card in order to provide secure access to a fee based premium TV content. These devices also need memory for the users to record content captured through these devices. The need for such memory is growing at a rapid rate.

SUMMARY

The present disclosure is directed to a system and method for receiving broadcast signals using intelligent covers. In some implementations, a cover for a consumer device includes side surfaces, a rear surface, a physical interface, a circuit, and a broadcast service card. The side surfaces and a rear surface form an opening that receives at least a portion of a consumer device. A first portion of at least one of the surfaces includes a connector for connecting to a port of the consumer device. The circuit connects the physical interface to the connector. The broadcast service card connects to the physical interface and receives broadcasted content independent of the consumer device.

The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is an example updating system in accordance with some implementations of the present disclosure;

FIGS. 2A to 2C illustrate cross sectional views of some implementations of the cover of FIG. 1;

FIGS. 3A and 3B illustrate example slots in the cover of FIG. 1;

FIG. 4 illustrates an example converter module of the cover of FIG. 1;

FIG. 5 is an example service system that transmits transaction information;

FIG. 6 is an example service card of FIG. 5 in accordance with some implementations of the present disclosure;

FIG. 7 is an example Central Processing Unit (CPU) of the service card of FIG. 6;

FIG. 8 is a schematic diagram illustrating personalization processes of intelligent cards;

FIGS. 9A and 9B are flow charts illustrating an example method for initialize an intelligent card;

FIG. 10 is a flow chart illustrating an example method for activating a service card;

FIGS. 11A to 11C are examples of call flow illustrating call sessions with an intelligent card;

FIG. 12 is a flow chart illustrating an example method for synchronizing ESG data; and

FIG. 13 is a flow chart illustrating an method receiving selected broadcast content.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a block diagram illustrating an example system 100 for augmenting a mobile device, for example an iPhone, with additional external devices using a cover for the mobile device. For example, the system 100 may add an external microSecureDigital (microSD) slot to a mobile host device, for example an iPhone, using a flexible cover that encloses at least a portion of the mobile device and connects to a port of the mobile device. Aside from microSD, the system 100 may add an external memory device to a mobile device using other interfaces such as, for example, MultiMediaCard (MMC), SD, miniSD, Firewire, and/or others. By adding external devices (e.g., memory, transaction cards), the system 100 may upgrade a mobile device that does not include expansion slots with additional external devices while substantially maintaining the dimensions of the device. For example, the cover may increase the dimensions of the by 5 percent or less. In other words, the cover may add a device slots to a mobile device while substantially maintaining original attributes such as speaker outputs, network signal strength, headphone jacks, battery charging, docking ports, and others. In some implementations, the system 100 may update mobile devices with external memory devices, transaction cards, and/or other devices. For example, the intelligent card may wirelessly execute transactions with different enterprises using a single intelligent card and independent of a mobile host device. In other words, a single intelligent card included with the cover may execute a payment transaction with a financial institution, an access control transaction with a enterprise network, a ticket purchase transaction with a transit authority and/or an identity validation transaction with a government agency. In such implementations, each of the transactions can securely identify a user and user privileges with respect to the services being received from the different enterprises. In doing so, the cover including the intelligent card may operate as a logical wallet. In some of these implementations, the cover may include a circuit that converts signals between a form compatible with an external memory device (e.g., microSD) and a form compatible with the mobile device (e.g., USB). In addition, the system 100 may include an intelligent card integrated into an the cover such that removable may at least partially damage the cover.

At a high level, the system 100 includes a cover 102, an external device 104, a mobile device 106 and a network 108. The cover 102 including a slot 110 for connecting to the external device 104, a connector 112 for connecting to the mobile device 106, and a circuit 114 for communicably connecting the slot 110, an antenna 115 for boosting transmission and reception of RF signals, and the connector 112. The cover 102 may update the mobile device 106 with an external device 104. In addition, the cover 102 encloses at least a portion of the mobile device 106. In the case of enclosing a portion of the mobile device 106, the cover 102 may include other aspects that expose ports of the mobile device 106 for connecting with external peripherals such that the cover 102 does not substantially interfere with such connections. In other words, the cover 102 may either include ports substantially aligned with ports of the mobile device 106 or provide openings that allow substantially unrestricted access to the original ports of the device 106 (see FIG. 2C). The mobile device 106 may be communicable coupled to the network 108. The mobile device 106 includes a Graphical User Interface (GUI) 116 for presenting information to and/or receiving information from users.

The cover 102 can include any software, hardware, and/or firmware configured to update the mobile device 106 with one or more external devices slots. For example, the cover 102 may include a microSD slot and a physical interface for connecting to a port of the mobile device. In this example, the cover 102 may connect the microSD slot to the mobile device 106 using the physical interface. In some implementations, the cover 102 may include one or more of the following: one or more slots for external devices (e.g., memory, wireless transaction cards); one or more connectors that connect to the mobile device 106; one or more circuits for connecting the one or more slots to the one or more connectors; a conversion module that converts signals between different formats; a biometric reader that determines biometric information of a user of the mobile device 106; and/or other elements. In some implementations, the cover 102 may be formed of a flexible material such as, for example, silicone rubber, a soft neoprene, and/or other material. The opening formed by the cover 102 may be substantially be the same as or less than the dimensions of the mobile device 106. In the case of the opening dimensions being less, the cover 102 may be slightly flexible to stretch over the mobile device 106. The cover 102 may substantially maintain attributes of the mobile device 106, such as dimensions, accessibility to peripherals as provided by the device, charging, battery life, signal strength, access to display and all other input devices, connectivity to the wireless network if any, interface capability to a PC if any and any other features provided by the device. In maintaining the attributes, the added functionality may not degrade the device performance in any manner such that certification by regulatory authorities (e.g., FCC) and warranty by the issuer of the device 106 is compromised.

In the illustrated implementation, the cover 102 includes the slot 110, the connector 112 and the circuit 114. The slot 110 may comprise an MMC, miniMMC, microMMC, SD, miniSD, microSD, and/or other slots. The slot 110 may including an opening such that the external device 104 may be inserted after the mobile device 106 is inserted into the cover 102. In some implementations, the slot 110 may be formed in the rear surface such that cover 102 is removed or at least portion moved away from the surface of the mobile device 106 to insert the external device 104. In some implementations, the slot 110 and the external device 104 are integrated into the cover 102, and in this case, the external device 104 may not be removable without damaging the cover 102. The connector 112 includes at least a portion that connects to a port of the mobile device 106. The connector 112 may include a USB, iDock, microUSB, Firewire, Serial, and/or other connectors offered by the mobile device 106. In some implementations, the connector 112 may include a first interface for connecting to the mobile device 106 and a second interface for connecting with external devices. The second interface may be substantially similar in dimensions and interface capabilities as the original connector of the mobile device 106. In these instances, the connector 112 may pass one or more signals from external devices to the mobile device 106 without, for example, interfering with the connecting to the external device 104. For example, the connector 112 may include a second interface that connects with the power supply of the mobile device 106 and passes the signal to the mobile device 106 for charging. The circuit 114 can include any software, hardware, and firmware for communicably connecting the slot 110 with the connector 112. For example, the circuit 114 may include one or more wired connections between the slot 110 and the connector 112. In addition, the circuit 114 may also include a booster antenna that may enhance the signal reception capability of the mobile device 106 and/or the signal reception capability of any wireless transaction cards inserted into the slot 110 (see FIG. 2A). In some implementations, the circuit 114 may execute one or more of the following: pass signals between the slot 110 and the connector 112; translated or otherwise convert signals between forms compatible with the external device 104 and forms compatible with the mobile device 106; detect biometric information of a user of the mobile device 106; manage access to the external device 104 based, at least in part, on detected biometric information; enhance signal reception of the host device via an integrated booster antenna; enhance signal reception of a wireless transaction card inserted into the slot; provide access to software and system on the device inserted into the slot for an application residing on the mobile device; and/or other processes.

The external device 104 can include any software, hardware, and/or firmware configured to update the mobile device 106 with one or more features and/or functions. For example, the external device 104 may include solid-state memory (e.g., flash, EEPROM) for storing information received, for example, from the mobile device 106. The external device 104 may update the mobile device 106 with, for example, external memory, a wireless transaction card, a broadcast receiver, a broadband transceiver, and/or other elements. In regards to memory, the external device 104 may be a Flash or memory package, which is non-volatile memory that may be electrically erased and reprogrammed. The external device 104 may be a memory card, USB Flash drives, and/or other memory device. For example, the external device 104 may include Electrically Erasable Programmable Read-Only Memory (EEPROM) that is erased and programmed in blocks. In regards to memory cards, the external device 104 may be MMC, microMMC, miniMMC, SD, microSD, miniSD, Memory Stick, Memory Stick Duo, xD-Picture Card, Secure Digital High Capacity (SDHC), and/or other memory card. In some implementations, the external device 104 may include a memory capacity between 1 MB and 1 TB. Alternatively or in addition, the external device 104 may be a transaction card as discussed with respect to FIGS. 5 to 14. In these implementations, the external card 104 may wirelessly execute transactions with, for example, a point of sale device. In some implementations, the external card 104 is integrated/embedded into the cover 102. The external card 104 may store user credentials for a credit card, a debit card, a prepaid card, a gift card, a checking account, and/or other user accounts. In addition, the intelligent card may also store user credentials for other applications such as loyalty (points for purchase), airline (access to clubs, check-in), state (driving license), memberships (clubs) and/or others where user credentials are used to identify user so that goods and/or services can be provided. By storing multiple user credentials in a single external card 104, the system 100 may execute transactions with different institutions without requiring multiple instruments, as discussed in more detail with respect to FIGS. 5-14.

The mobile device 106 comprises an electronic device operable to interface with the cover 102 using one or more ports. For example, the mobile device 106 may have an iDock port that connects with the cover 102. As used in this disclosure, the mobile device 106 is intended to encompass cellular phones (e.g., iPhone), data phones, pagers, portable computers, SIP phones, smart phones, personal data assistants (PDAs), digital cameras, MP3 players, camcorders, one or more processors within these or other devices, or any other suitable processing devices capable of communicating information with the cover 102 through one or more ports and may not have otherwise have a slot for external card 104 could be directly plugged in. The one or more ports may include, for example, a USB port, an iDock port, a FireWire port, a serial port and/or any other interface port provided by the mobile device for connectivity with peripherals, and/or other ports. In some implementations, the mobile devices 106 may be based on broadcast radio technology. For example, the mobile device 106 may be a PDA operable to wirelessly connect with an external or unsecured network. In another example, the mobile device 106 may comprise a digital multimedia player that includes an input device, such as a keypad, a jog wheel, a jog dial, touch screen, or other device that can accept information or allows selection of user interface elements, and an output device that conveys information associated with the system 100, including digital data, visual information, or GUI 116.

The GUI 116 comprises a graphical user interface operable to allow the user of the mobile device 106 to interface with at least a portion of the system 100 for any suitable purpose, such as executing transactions and/or and presenting transaction history. Generally, the GUI 116 provides the particular user with an efficient and user-friendly presentation of data provided by or communicated within the system 100 and/or also an efficient and user-friendly means for the user to self-manage settings and access services offered by an institution. The GUI 116 may comprise a plurality of customizable frames or views having interactive fields, pull-down lists, and/or buttons operated by the user. The term graphical user interface may be used in the singular or in the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. The GUI 116 can include any graphical user interface, such as a generic web browser or touch screen, that processes information in the system 100 and presents the results to the user.

Network 108 facilitates wireless or wired communication between institutions and any other local or remote computer, such as the mobile device 106. Network 108 may be all or a portion of an enterprise or secured network. While illustrated as single network, network 108 may be a continuous network logically divided into various sub-nets or virtual networks without departing from the scope of this disclosure, so long as at least a portion of network 108 may facilitate communications with the mobile device 106. In some implementations, network 108 encompasses any internal or external network, networks, sub-network, or combination thereof operable to facilitate communications between various computing components in system 100. Network 108 may communicate, for example, Internet Protocol (IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice, video, data, and other suitable information between network addresses. Network 108 may include one or more local area networks (LANs), radio access networks (RANs), metropolitan area networks (MANs), wide area networks (WANs), all or a portion of the global computer network known as the Internet, and/or any other communication system or systems at one or more locations.

FIGS. 2A to 2C illustrate cross-sectional views of the cover 102 of FIG. 1. In particular, the views illustrate the components of the cover 102 that at least augment the mobile device 106 with the card 104. In FIG. 2A, the cover 102 includes a port-to-card converter module 202 (e.g., USB-to-microSD), a reader 204, and an antenna 206. The converter module 202 can include any software, hardware, and/or firmware that converts between card-processable signals and signals compatible with the mobile device 106. In the illustrated example, the converter module 202 converts between SD signals and USB signals. The reader 204 can include any software, hardware, and/or firmware that verifies or otherwise determines user information such as biometric information. In the illustrated example, the reader 204 determines fingerprints of a user and may verify whether the user has access to the card 104. In addition, the reader 204 may pass the biometric information to an application on the mobile device 106 (through the converter 202 and/or the connector) for, for example, to securely verify the identity of the device holder. The mobile host device 106 may include biometric identity verification for applications such as mobile banking. In some implementations, an application can use the biometric reader 204 to first register the user's biometric identity on first use and thereafter match the biometric identity of the device holder with the registered biometric identity. The secure storage of the biometric identity for the user may be provided by the removable secure card 104 or could be located on a special secure memory embedded in the cover. For example, when the user changes devices 106, the identity footprint may be erased from the initial device (if he removes the cover 102 and the card 104). In addition, another application running on the CPU of the cover 102 may also use the biometric data to secure access to certain features and/or services. The antenna 206 may wirelessly transmit and receive RF signals associated with the card 104. In the transaction-card implementations, the antenna 206 may extend the transaction range of the card 104 for wirelessly executing transactions. FIG. 2B is another illustration of a cross-sectional view of the cover 102. In this view, a connector 208 of the mobile device 106 is illustrated. For example, the connector 208 may be an iDock connector of an iPhone having 30 pins. FIG. 2C is yet another cross sectional view of the cover 102. In this view, the cover 102 includes the openings 214A and 214B for speakers included with the mobile device 106 and a cavity 212 for connecting a power supply to the connector 112 and the connector 208. In this case, the mobile device 106 may be charged using the connector 208 without removing the cover 102.

FIGS. 3A and 3B illustrate different implementations of the slot 110. In FIG. 3A, the slot 110 may be formed in the cover 102 such that a card 104 may be inserted and removed without lifting or otherwise removing at least a portion of the cover 102. In FIG. 3B, the slot 110 is formed on the inside of the cover 102 such that the cover is at least partially lifted or otherwise removed to insert and remove the card 104.

FIG. 4 illustrates some implementations of the convert module 202 that converts between USB and SD signals. As illustrated, the converter module 202 may receive a plurality of inputs associated with the card 104 and convert the signals to a form compatible with the connector 208 of the mobile device 106. In some implementations, the converter module 202 may convert, for example, between data formats. In some implementations, the converter module 202 may pass inputs to corresponding outputs such as for VDD and GND.

FIG. 5 is a block diagram illustrating an example service system 500 for receiving broadcast signals using an intelligent card. For example, the system 500 may include a SecureDigital (SD) card that receives broadcast signals (e.g., terrestial digital video broadcast) and presents content through a mobile host device based, at least in part, on the received broadcast signals. Broadcast signals may include terrestrial and/or satellite signals that encode images, audio, video, and/or other content. For example, the broadcast signals may be Digital Video Broadcasting—Handheld (DVB-H), DVB-H2, Digital Video Broadcasting—Satellite services to Handhelds (DVB-SH), Forward Link Only (FLO), Digital Multimedia Broadcasting (DMB), Multimedia Broadcast Multicast Service (MBMS), satellite radio, and/or others. Aside from SD, the system 500 may include other interfaces that connect an intelligent card to the host device such as, for example, MultiMediaCard (MMC), miniSD, microSD, Universal Serial Bus (USB), Apple iDock, Firewire, and/or others. An intelligent card may be a device configured to insert into or otherwise attach to a mobile host device and access or otherwise receiving broadcast signals (e.g., e.g., satellite radio) independent of the mobile host device. In some implementations, the intelligent card may be shaped as a microSD card, miniSD card, or microSD card including, for example, notches, raised portions and/or other features. In some implementations, the system 500 may modify, translate, or otherwise convert received broadcast signals to a form processable by or otherwise native to the mobile host device 106. In converting the signal protocols, the system 500 may present media content otherwise foreign to the mobile device 106. Foreign, as used herein, means any component, object, value, variable, content and/or data and/or data schema that is not directly processable, accessible, receivable or otherwise capable of communicating with the mobile devices 106. In some implementations, the conversion of the foreign content to compatible forms may be transparent to the user of the mobile device 106. By providing an intelligent card, the system 500 may access foreign content without either requiring additional hardware, software, and/or firmware in the mobile host device.

At a high level, the system 500 includes the mobile devices 106a and 102b and the content provider 504 coupled to the network 108. The mobile device 106 includes a GUI 116 for providing presenting content and a service card 104 for independently converting foreign content to forms compatible with the mobile device 106. In some implementations, the service card 104 may selectively switch antenna on and off in response to an event such as a selection of a graphical element using the GUI 116. The network 108 includes a content distribution stations 112a and 112b (e.g., broadcast tower, satellite, IP broadcast tower) for broadcasting content to the service cards 110.

Each mobile device 106 comprises an electronic device operable to interface with the service card 104. For example, the mobile device 106 may receive and transmit wireless and/or wireless communication with the system 500. As used in this disclosure, the mobile devices 106 are intended to encompass cellular phones, data phones, pagers, portable computers, SIP phones, smart phones, personal data assistants (PDAs), digital cameras, MP3 players, camcorders, video player, game player, one or more processors within these or other devices, or any other suitable processing devices capable of communicating information with the service card 104. In some implementations, the mobile devices 106 may be based on a cellular radio technology. For example, the mobile device 106 may be a PDA operable to wirelessly connect with an external or unsecured network. In another example, the mobile device 106 may comprise a smartphone that includes an input device, such as a keypad, touch screen, mouse, or other device that can accept information, and an output device that conveys information associated with a transaction with the provider 504, including digital data, visual information, or GUI 116.

The GUI 116 comprises a graphical user interface operable to allow the user of the mobile device 106 to interface with at least a portion of the system 500 for any suitable purpose, such as viewing content channels and/or displaying the Electronic Service Guide (ESG). Generally, the GUI 116 provides the particular user with an efficient and user-friendly presentation of data provided by or communicated within the system 500 and/or also an efficient and user-friendly means for the user to self-manage settings and access channels offered by the content provider 504. The GUI 116 may comprise a plurality of customizable frames or views having interactive fields, pull-down lists, and/or buttons operated by the user. The term graphical user interface may be used in the singular or in the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. The GUI 116 can include any graphical user interface, such as a generic media player or touch screen, that processes information in the system 500 and presents the results to the user.

The service card 104 can include any software, hardware, and/or firmware configured to receive broadcast signals from the distribution stations 112. For example, the service card 104 may receive content broadcasted by the content provider 504 and translate, map or otherwise convert the received content to forms viewable with the mobile device 106. In some implementations, the service card 104 can present received content through the GUI 116. In some implementations, the service card 104 may include one or more chipsets that execute an operating system and security processes to receive broadcast signals independent of the mobile host device 106. In doing so, the mobile device 106 may not require additional hardware, software, and/or firmware to present foreign content such as digital TV, IP-TV, satellite radio, satellite TV, and/or other broadcast services. In some implementations, the service card 104 may execute one or more of the following: wirelessly receive signals broadcasted by the distribution stations 112; determine subscription levels of the card 104 based, at least in part, on locally-stored user information; descramble content available to the user in accordance with the subscription levels; translate between broadcast protocols (e.g., DVB, FLO, MBMS, DMB) and protocols compatible with the service card 104; translate between service-card protocols and protocols compatible with mobile device 106; present broadcasted content for viewing through the GUI 116; execute applications locally stored in the service card 104; selectively switch the antenna on and off based, at least in part, on one or more events; authenticate user based, at least in part, on information locally stored in the service card 104; present the Electronic Service Guide application for the user through the GUI 116 for selection of available channels; present menu options for managing recordable content and configuring options for the personal video recorder application via GUI 116; present the personal video recorder application for viewing of recorded content via GUI 116; and/or others. In some implementations, the service card 104 may receive a broadcast signal in response to at least a user selecting a graphical element in the GUI 116. In some implementations, the service card 104 may selectively switch the antenna between an on and off state in response to one or more events (e.g., user request, completion of broadcast, change of host device, change of network connection of the host device, change of location). The service card 104 may include a communication module with a protocol translation module, antenna tuning circuit, power circuit and a miniature antenna tuned to receive broadcast signals.

In some implementations, the service card 104 may initiate receiving to a broadcast signal in response to at least a user selecting a graphical element in the GUI 116. In some implementations, the service card 104 may selectively switch the antenna between an on and off state in response to one or more events. The one or more events may include a user request, completion of broadcasted content, insertion of card 104 in a different mobile device, location change, timer events, detection of incorrect user ID and password entered by the user, message received from the content provider 504 using a broadcast/cellular signal, and/or others. For example, the service card 104 may receive one or more commands to switch the antenna off from the distribution station 512 or from the broadcast/cellular core network. In some implementations, the service card 104 may request user identification such as a PIN, a user ID and password combination, biometric signature, and/or others.

In regards to translating between protocols, the service card 104 may process information in, for example, ISO 7816, a stand security protocol, and/or others. In this case, the service card 104 may translate between a broadcast protocol and the service-card protocol. Broadcast protocols may include DVB, DMB, FLO and/or MBMS. In some implementations, ISO 7816 commands may be encapsulated within interface commands used to transmit data between the mobile host device 106 and the card 104. In addition, the service card 104 may interface the mobile device 106 through a physical interface such as MicroSD, Mini-SD SD, MMC, miniMMC, microMMC, USB, miniUSB, microUSB, firewire, Apple iDock, and/or others. In regard to security processes, the service card 104 may implement one or more Conditional Access Systems (VideoGuard, Irdeto Access, Nagravision, Conax, Viaccess and Mediaguard (a.k.a. SECA)). The CAS may use encryption algorithms to descramble or otherwise decrypt broadcast signals to determine encoded content. In some implementations, the service card 104 may execute private key (symmetric algorithms) such as Data Encryption Standard (DES), Triple DES (TDES) and/or others or public key (asymmetric algorithms) such as RSA, elliptic curves, and/or others to implement the chosen CAS system compliant with the service provider. For example, the service card 104 may include one or more encryption keys such as public-private keys. In addition, the service card 104 may include memory (e.g., Flash, EEPROM) including a secured token accessible by the content providers 504 to store access rights of the user. The service card 104 may also store user data, applications, offline Webpages, and/or other information. For example, the service card 104 may include a secure token that identifies content that the user subscribes to or can otherwise access. In addition, the service card 104 may execute or otherwise include digital rights management technology to substantially prevent illegal copying, storing or distributing or other violations of digital rights.

The service card 104 may present content (e.g., audio, video) to the user using the GUI 116. In response to initiating foreign-content access, the service card 104 may automatically present an offline Web page through the GUI 116. In some implementations, the offline Web page can be associated with a content provider 504. In some implementations, the service card 104 can be backward compatible and operate as a mass storage device. For example, if the wireless interface of the service card 104 is not available or deactivated, the service card 104 may operate as a mass storage device enabling users to access data stored in the memory component (e.g., Flash). In some implementations, the service card 104 can execute a set of initialization commands in response to at least insertion into the mobile device 106. These initialization commands may include determining device related information for the mobile device 106 (e.g., device ID, device capabilities), determining user relating information (e.g., user ID and password), incrementing counters, setting flags and activating/deactivating functions according to pre-existing rules and/or algorithms.

In some implementations, the service card 104 may automatically execute one or more fraud control processes. For example, the service card 104 may identify an operational change and automatically deactivate the card 104. The service card 104 may execute two fraud control processes: (1) determine a violation of one or more rules; and (2) automatically execute one or more actions in response to at least the violation. In regards to rules, the service card 104 may locally store rules associated with updates to operational aspects of the service card 104. For example, the service card 104 may store a rule indicating a change in mobile host device 106 is an operational violation. In some implementations, the service card 104 may store rules based, at least in part, on updates to one or more of the following: device ID; subscription period; registration information; CAS parameters; and/or other aspects. In response to one or more events matching or otherwise violating rules, the service card 104 may execute one or more processes to substantially prevent access to broadcasted content. In some implementations, the service card 104 may execute a command based, at least in part, on an event type. For example, the service card 104 may re-execute an activation process in response to at least a specified event type. In some implementations, the service card 104 may execute a command to disconnect the GUI 116 from the service card 104. The service card 104 may present a disconnection notification through the GUI 116 prior to executing the command. In some implementations, the service card 104 may provide options for the user to configure a rule table (PVR rule table) related to the personal video recorder application. This may allow the user to specify rules according to which content is automatically recorded by the service card.

In regards to accessing broadcasted services, the interface between the service card 104 and the station 512 may be DVB-H, DMB, MBMS, or FLO for Mobile-TV and Sirius/XM for Satellite Radio or other digital Mobile-TV and/or satellite broadcast interfaces. Based on the PVR Rule Table, the service card 104 may receive content from the broadcast content provider 504 and store the content in real-time to the memory. The content player of the mobile device 106 may then access the stored content using, for example, a media player and access to the GUI 116. The antenna mode of the service card 104 may be set to physical authentication only because the service card 104 may use the mobile device 106 to present video and/or audio. The secure element of the service card 104 may operate as set-top box (CAS token). In this implementation, the secure element my operate in two different roles as illustrated in Table 1 below.

TABLE 1 DVB-H/MediaFLO or other Mobile-TV XM/Sirius or other Satellite Radio Broadcast Broadcast Digital TV transmissions are generally scrambled to This is a simpler case where the satellite radio allow content providers and content providers to content providers may offer service to users who offer pay-per-use and tiered subscription services to have purchased a particular subscription plan. Only the end users. In order to perform this capability, protection applicable here-in is hence the service there are two types of protection that may be protection which would be implemented by the implemented: secure element. The secure element will store an a) Service Protection: In this case, subscription active subscription for the end-user which will related access rights are stored on a secure token enable the plug-in to securely receive transmission (such as the smart card in Cable or Satellite Set-top and produce output boxes). As and when a user purchases a premium channel/package or pay-per-use event, access right to the same is downloaded to this secure token. The algorithms and method of protection are generally provider dependent and in generally referred to as the CAS (Conditional Access System). The secure element in the plug-in, being a secure token, will host the CAS algorithm compliant with the content provider and the access keys management that are managed dynamically depending on the content subscribed to by the end-user b) Content Protection: In this case, the content download contains digital rights management technology wherein it cannot be illegally copied, stored or distributed. If required by the content provider, the secure element will implement the required DRM scheme of the content provider such that the content downloaded or viewed is used by the end-user according to the restrictions imposed by the content provider

The table is for illustration purposes only. The activation of the service card 104 may include some, all, or different aspects of the chart.

In some implementations, the user may acquire the service card 104 when subscribing to a content provider's broadcast content service. The activation process may depend on whether the mobile device 106 includes an interface such as a screen, a keyboard and internet access. In some implementations, the service card 104 may be activated online or offline. Online activation may occur when the device 106 includes an interface such as screen, keyboard and wireless internet access (Cellphone, laptop or Wireless PDA), offline activation may occur when a device 106 does not include internet capability or doesn't have a screen/keyboard (MP3/4 players). These two activation processes are illustrated below in Table 2.

TABLE 2 Online Activation Offline Activation When the device has internet access and has a In this case, the user may cradle his device to the PC screen/keyboard, it is assumed to have an internet that has an internet access and launch the included browser and capable of browsing to any URL. In activation software. This software will take the user this case, when the plug-in inserts, it performs the to the content provider's landing page to perform plug-in bootstrap and authentication process. Once the registration and activation process. successful, the device is able to take the user to a landing page on a browser where the user can perform the registration and activation process.

The table is for illustration purposes only. The activation of the service card 104 may include some, all, or different aspects of the chart.

In some implementations, the service card 104 may operate as a personal video recorded (PVR). For example, the service card 104 may include GBs of flash memory that may store multimedia content. The service card 104 may include a microcontroller sufficiently strong to operate a recording process while streaming the content to the content player on the mobile device 106 at the same time. The service card 104 may include an application residing on a protected area of the memory that would run a PVR and an Electronic Service Guide (ESG) application to enable a user to review the content program and select the programs recording. The DVR and ESG application may enable playing back the recorded content from the memory. In comparison, the service card 104 may include a stronger microcontroller that has an internal clock (e.g., an ARM series processor). The service card 104 may include a special form factor that allows the SD interface to connect to a SD to USB adaptor for laptop use. In some implementations, the service card 104 includes a secure element OS to enable the functionality described above. The service card 104 may implement a CAS algorithm based on content provider's specification. The secure element OS may structure data in the secure element to enable storage of subscription data for the end user. The microcontroller OS may be capable of personalizing the secure element by loading/updating user subscription parameters. In addition, the microcontroller OS may be capable of presenting the service card 104 as SD mass storage to the mobile device 106. In addition to operating the memory, secure element, the broadcast receiver chipset and the antenna availability, the microcontroller OS may implement a very fast content writing function on the memory in real-time, receive the ESG in real-time from the broadcast content provider 204, and interact with the host device's content player to display the content. The secure element may operate as the CAS and subscription storage token because of cryptographic capabilities. The device application section may be used to store provider specific applications that operate from this segment of the memory or are installed on the mobile device 106 from this segment of the memory.

In some implementations, the service card 104 may include broadcast applications and WAN connectivity. In this case, the user may perform payment to a third party by connecting over the internet and/or performing peer-to-peer payment by connecting to another user with the same functionality. In some implementations, the service card 104 may include broadcast applications and broadcast reception capabilities. In this case, the user may purchase content in real-time and pay for merchandise advertised over the broadcast content in real-time.

The content distribution network 108 facilitates wireless or wired communication between the content providers 504 and any other local or remote computer. The distribution network 108 may be all or a portion of an enterprise or secured network. While illustrated as single network, the distribution network 108 may be a continuous network logically divided into various sub-nets or virtual networks without departing from the scope of this disclosure, so long as at least a portion of distribution network 108 may facilitate communications of transaction information between the content providers 504. In some implementations, the distribution network 108 encompasses any internal or external network, networks, sub-network, or combination thereof operable to facilitate communications between various computing components in system 500. Network 108 may communicate, for example, Internet Protocol (IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice, video, data, and other suitable information between network addresses. Network 108 may include one or more local area networks (LANs), radio access networks (RANs), metropolitan area networks (MANs), wide area networks (WANs), all or a portion of the global computer network known as the Internet, and/or any other communication system or systems at one or more locations. In some implementations, the distribution network 108 include the content providers 504a-c.

Content providers 504a-c comprises an electronic device (e.g., computing device) operable to broadcast content. In some implementation, the content providers 504 can provide broadcast signals that encodes content displayable by the service card 104. The content providers 504 may transmit one or more of the following: serial programs (e.g., television series), movies, news, opinions, education content, training, sports events, Web pages; advanced blogging sites, travel-related content, food and/or cooking content; entertainment; topical movies and/or videos (e.g., surfing, sailing, racing, extreme sports, etc.); political content (e.g., campaigning); adult content; court and/or trail programming; local-government content (e.g., C-SPAN); local programming (e.g., Wayne's World); performing arts (e.g., theater, concerts, music videos, etc.); virtual shopping malls; satellite radio content (audio only channels); and/or other content. The provided content may be in any suitable format such as MPEG, streaming, MP3, realtime, WMV, and/or others. In the illustrated implementation, the content providers 504 includes a conditional access module 124 for authenticating a user and associated privileges prior to providing access to services. For example, the CAS module 124 may transmit a request for information associated with the user such as subscriber ID, receiver ID, PIN, username and password, and/or other information. Based, at least in part, on information associated with the user information, the CAS module 124 may determine available services, content, level of services, and/or other aspects of the requested foreign service.

In some implementations, the service card 104 may operate in accordance with one or more of the following modes: active receiver; self train; killed; memory; inactive; and/or other modes. The service card 104 may operate active-receiver mode to present the service card 104 as a broadcast receiver. In this mode, the service card 104 may execute applications access broadcast services through the broadcast network 108. After the antenna of the service card 104 is activated in this mode, the network 108 may detect the presence of the service card 104. In this implementation, the mobile device 106 may not require additional software to access the services.

In regards to the self-train mode, the service card 104 may receive personalization information from another receiver. In some implementations, the self-train mode can be activated by a special action (e.g., a needle point press to a small switch, entry of an administrative password via the GUI 116). In response to at least activating this mode, the service card 104 may be configured to receive personalization data over, for example, the short range wireless interface from another peer service card or a wired connection with the home broadcast receiver. Personalization data received in this mode may include encrypted information that is stored in secured memory of the service card 104. In some implementations, the service card 104 in this mode may receive the information through a wireless interface of a transmitter and/or others. The service card 104 may then synthesize the information that corresponds to the user account and personalize an internal security module that includes, for example, service applications for accessing services from the GUI 116 and associated user credentials. The self-train mode may be used to re-personalize the service card 104 in the field. In some implementations, all previous data can be deleted if the self-train mode is activated. The self-train mode may be a peer-to-peer personalization mode where the card 104 may receive personalization information from another service card 104. This mode may represent an additional personalization mode as compared with factory, store and/or Over-The-Air (OTA) personalization scenarios which may be server to client personalization scenarios. In some implementations, the self-train mode may be a peer-to-peer personalization mode where the service card 104 receives personalization information from another service card. Since two service cards 110 are used in this mode, this mode may be different from a server-to-client personalization scenario as with a factory, store, and OTA personalization.

In regards to the inactive mode, the service card 104 may temporarily deactivate the wireless interface. In some implementations, the inactive mode can be activated through the physical interface with the mobile device 106 such as a SD interface. In response to at least the activation of the inactive mode, the service card 104 may temporarily behave as only a mass-memory card. In some implementations, the card 104 may also enter this state when the reset needle point is pressed. In this mode, the service card 104 may preserve locally-stored information including user information. In this mode, the service card 104 may execute the activation process and if successful may return to the active mode. The content provider 504 may use this mode to temporarily prevent usage in response to at least identifying at least potentially fraudulent activity.

In regards to the killed mode, the service card 104 may permanently deactivate the wireless interface. In some implementations, the killed mode is activated through the physical interface with the mobile device 106 such as a SD interface. In response to at least the activation of the killed mode, the service card 104 may permanently behaves as a mass memory stick. In the event that the reset needle point is pressed, the service card 104 may, in some implementations, not be made to enter any other modes. In addition, the service card 104 may delete user information in memory in response to at least this mode being activated. In some implementations, the providers 504 may use this mode to delete data from a service card 104 that is physically lost but still connected to the broadcast network 108.

In regards to the memory mode, the service card 104 may operate as a mass memory stick such that the memory is accessible through conventional methods. In some implementations, the service card 104 may automatically activate this mode in response to at least being removed from the host device, inserted into a non-authorized host device, and/or other events. The service card 104 may be switched to active mode from the memory mode by, for example, inserting the card 104 into an authorized device or may be switched from this mode into the self-train mode to re-personalize the device for a new host device or a new user account. In some implementations, the memory mode may operate substantially same as the inactive mode.

In some implementations, the service card 104 may be re-personalized/updated such as using software device management process and/or a hardware reset. For example, the user may want to re-personalize the service card 104 to change host devices, to have multiple host devices, and/or other reasons. In regards to the software device management, the user may need to cradle the new host device with the service card 104 inserted to launch the software device management application. In some implementations, the software management application can be an application directly installed on a client, integrated as a plug-in to a normal synchronization application such as ActiveSync, available via a browser plug-in running on the plug-in provider's website, and/or other sources. The user may log into the application and verify their identity, and in response to verification, the application may allow access to a devices section in the device management application. The device management application may read the service card 104 and display the MAC addresses, signatures of the devices that he has inserted his plug-in to, and/or other device specific information. The mobile device 106 may be marked as active and the host device may be shown as disallowed or inactive. The application may enable the user to update the status of the new host device, and in response to at least the selection, the device management application may install the signature on the new host device and mark update the status as allowable in secure memory of the service card 104. The user may be able to also update the status of the mobile device 106 to disallowed. Otherwise, both devices may be active and the service card 104 may be switched between the two devices. In regards to the hardware reset process, the use may use the reset needle point press on the physical service card 104 to activate the self-train mode. In this mode, the user data may be deleted and have to be reloaded. When the service card 104 is inserted into the new host device, the provisioning process may begin as discussed above.

In some aspects of operation, the content provider 504 may transmit information to the mobile host device 106 using the service card 104 in response to at least an event. The information may include, for example, service information (e.g., access history), scripts, applications, Web pages, and/or other information associated with the content provider 504. The event may include completing access to a service, determining a service card 104 is outside the operating range of a broadcast network 108, receiving a request from a user of the mobile host device, and/or others. For example, the content provider 504 may identify a mobile host device 106 associated with a card 104 that accessed a service and transmit service information to the service card 104 using the broadcast or cellular core network 108. In addition or alternatively, the content provider 504 may request information from the mobile host device 106, the service card 104 and/or the user using the broadcast or cellular core network 108. For example, the content provider 504 may transmit a request to update the Electronic Service Guide to the card 104 through the broadcast or cellular core network 108.

FIG. 6 is a block diagram illustrating an example service card 104 in accordance with some implementations of the present disclosure. In general, the service card 104 may independently receive broadcast signals to present through the GUI 116 of the mobile host device 106. The service card 104 is for illustration purposes only and may include some, all, or different elements without departing from the scope of the disclosure.

As illustrated, the service card 104 includes an antenna 602, an Antenna Control Function (ACF) module 604, a broadcast receiver 606, a set-top module 608, a CPU 610 and memory 612. The antenna 602 receives wireless broadcast signals such as satellite radio and/or TV. In some implementations, the ACF module 604 can selectively switch the antenna 602 between an active state and an inactive state in response to at least an event. A switching event may include a user selection through the GUI 116. In some implementations, the switching event may be based, at least in part, on operational aspects of the mobile host device 106 such as completion of presentation of multimedia. In addition, the ACF module 604 may dynamically adjust the impedance of the antenna 602 to tune the receive frequency. The ACF module 604 may selectively switch the antenna 602 on and off in response to at least a command from the CPU 610. In some implementations, the antenna 602 can be connected through a logic gate to allow for code from the CPU 610 to turn the antenna 602 on and off through the ACF module 604.

The receiver 606 can include any software, hardware, and/or firmware configured to receive broadcast signals using the antenna 602. For example, the receiver 606 may convert broadcast signals to set top module processable signals. In some implementations, the receiver 606 may translate a broadcast protocol to a security protocol. For example, the receiver 606 may translate to ISO 7816, a stand security protocol, and/or others. Broadcast signals may include DVB, DMB, FLO and/or MBMS. In some implementations, ISO 7816 commands may be encapsulated within interface commands used to transmit data between the mobile host device 106 and the card 104.

The set-top module 608 can include any software, hardware, and/or firmware configured to unscramble broadcast signals to a form displayable through the GUI 110. For example, the set-top module 608 may launch the CAS application to unscramble the broadcast signal to determine encoded content and decrypt the encoded content to a presentable form (e.g., MPEG 4). In some implementations, the set-top module 608 may authenticate one or more aspects of the mobile host device, user, and/or card 104. In some implementations, the set-top module 608 may authenticate a user by verifying a physical connection with a user using user information such as user ID and password, biometric information (e.g., fingerprint), a PIN entered by the user, a x.509 type certificate that is unique to the user and stored on the host device 110, and/or other processes. For example, the set-top module 608 may compare user information provided through the GUI 116 with user information stored in the local memory 612. Alternatively or in addition, the set-top module 608 may authenticate the mobile host device 106 by comparing a device signature with a locally-stored certificate. In some implementations, the user can select a user-id and password or PIN or certificate at provisioning time. If this case, the CPU 610 may instantiate a software plug-in on the host device. For example, a software plug-in may request the user for his user-id and password or PIN in real time, read a user certificate installed on the device (e.g., x.509), and/or others. The operation of the software plug-in may be customized by the provider. Regardless, the returned user data may be compared with user data stored in the memory 612. In case of a successful match, the ACF module 604 may activate the antenna 602. In case of an unsuccessful match of a certificate and/or user information, the card 104 is deactivated. In case of unsuccessful user ID and password match, the user may be requested to repeat user-id and password attempts until a successful match or the number of attempts exceeds a threshold. The card provider may customize the attempt threshold.

In some implementations, the set-top module 608 may implement one or more Conditional Access Systems with accompanying encryption algorithms to decode broadcast signals. For example, the set-top module 608 may include or otherwise identify a one or more keys for decoding broadcast content. In some implementations, the service card 104 may execute private key (symmetric algorithms) such as Data Encryption Standard (DES), Triple DES (TDES) and/or others or public key (asymmetric algorithms) such as RSA, elliptic curves, and/or others. For example, the service card 104 may include one or more encryption keys such as public-private keys. In connection with decoding signals, the CAS in the set-top module 608 may identify a subscription profile identifying content available to the user. For example, the CAS in the set-top module 608 may determine one or more broadcast channels available to the user and decode one of the available broadcast channels for presenting through the GUI. The set top box 608 may present the Electronic Service Guide to the user through the GUI. The Electronic Service Guide may not only present the choice of channels available to the user but may also make available a detailed listing of programming content available on each channel. The Electronic Service Guide may also interface to the Personal Video Recorder application in the card and provide options to the user to set up timers to record certain programs. The Electronic Service Guide may also be periodically updated by the service provider through the set top box.

The CPU 610 can include any software, hardware, and/or firmware that manages operational aspects of the card 104 independent of the mobile host device 106. For example, the CPU 610 may include a runtime environment for executing broadcast applications for accessing foreign content encoded in broadcast signals. In some implementations, the CPU 610 may execute one or more of the following: interfacing the mobile host device 106 such as translating between protocols; determining operational aspects of the mobile host device 106; transmitting commands to the mobile host device 106 to substantially control one or more hardware components (e.g., GUI 116, memory); identifying events associated with activating and deactivating the antenna 602; executing broadcast applications that present foreign content from the GUI 116; executing media protocol conversion to adapt the content according to the capabilities of the media player accessible through the GUI, execute the PVR application to record content on the flash memory of the card, provide access to stored content on the flash memory, manage the set top box using ISO 7816 interface, mange the broadcast chipset using a high-speed IP interface, manage the memory using a standard memory controller interface; and/or others. In some implementations, the CPU 610 may transmit to the ACF module 604 switching commands in response to an event such as a user request, completion of a transaction, and/or others. In some implementations, the CPU 610 may switch the antenna 602 between active and inactivate mode using the ACF module 604 based, at least in part, on a personalization parameter defined by, for example, a user, distributor (e.g., content provider), and/or others. For example, the CPU 610 may activate the antenna 602 when the service card 104 is physically connected to a host device and when a handshake with the host device is successfully executed. In some implementations, the CPU 610 may automatically deactivate the antenna 602 when the service card 104 is removed from the host device. In regards to the handshaking process, the CPU 610 may execute one or more authentication processes prior to activating the service card 104 and/or antenna 602 as illustrated in FIG. 11. For example, the CPU 610 may execute a physical authentication, a device authentication, and/or a user authentication. For example, the CPU 610 may activate the antenna 602 in response to at least detecting a connection to the physical interface with the host device (e.g., SD interface) and successful installation of the device driver for mass memory access (e.g., SD device driver) on the host device. In some implementations, device authentication may include physical authentication in addition to a signature comparison of a device signature stored in memory 612 that was created during first-use (provisioning) to a run-time signature calculated using, for example, a unique parameter of the host device 106. In the event no host device signature exists in the memory 612, the CPU 610 may bind with the first compatible host device 106 that the card 104 is inserted into. A compatible host device 106 may be a device that can successfully accomplish physical authentication successfully. If a host-device signature is present in the memory 612, the CPU 610 may compare the stored signature with the real-time signature of the current host device 106. If the signatures match, the CPU 610 may proceed to complete the bootstrap operation. If the signatures do not match, host device 106 may be rejected, bootstrap is aborted and the card 104 may be returned to the mode it was before being inserted into the device.

The memory 612 may include a secure and non-secured section. In this implementation, the secure memory 612 may store one or more user credentials that are not accessible by the user. In addition, the memory 612 may store offline Web pages, applications, service history, and/or other data. In some implementations, the memory 612 may include Flash memory from 64 MB to 32 GB. In addition, the memory 612 may be partitioned into user memory and device application memory. The memory 612 may store signatures of allowed host devices and/or antenna modes. In some implementations, the memory 612 may include secure portions designed to be accessible only by the content provider.

FIG. 7 illustrates is a block diagram illustrating an example CPU 610 of FIG. 6 in accordance with some implementations of the present disclosure. In general, the CPU 610 includes personalized modules that receive foreign content independent of the mobile device 106. The illustrated CPU 610 is for example purposes only, and the CPU 610 may include some, all or different modules without departing from the scope of this disclosure.

In some implementations, the service card 104 can include a host controller 702, a real-time framework 704, a broadcast application 706, a real-time OS 708, a high speed IP interface 710, a memory controller 712, and a security module driver 714. In some implementations, the host controller 702 includes an interface layer, an API/UI layer, a Web server, and/or other elements associated with the mobile host device 106. The host controller 702 includes interfaces to the host device, i.e., physical connection. In regards to the physical interface, the host controller 702 may physically interface the mobile device 106 using an SD protocol such as MicroSD, Mini-SD or SD (full-size). In some implementations, the physical interface may include a converter/adapter to convert between two different protocols based, at least in part, on the mobile device 106. In some implementations, the mobile device 106 may communicate using protocols such as USB, MMC, Firewire, iPhone proprietary interface, and/or others. In addition, the host controller 702 may include any software, hardware, and/or firmware that operates as an API between the mobile device 106 and the service card 104. Prior to accessing services, the service card 104 may automatically install drivers in the mobile device 106 in response to at least insertion. For example, the service card 104 may automatically install a microSD device driver in the device 106 to enable the service card 104 to interface the mobile device 106. In some implementations, the service card 104 may install an enhanced device driver such as a Mass Memory with Radio (MMR) API. In this implementation, the interface can drive a class of plug-ins that contain mass memory as well as a radio interface. The MMR API may execute one or more of the following: connect/disconnect to/from the MMR controller (Microcontroller in the plug-in); transfer data using MM protocol (e.g., SD, MMC, XD, USB, Firewire); send encrypted data to the MMR controller; receive Acknowledgement of Success or Error; received status word indicating description of error; turn radio on/off; send instruction to the service card 104 to turn the antenna on with specifying the mode of operation (e.g., sending mode, listening mode); transmit data such as send instruction to controller to transmit data via the radio; listen for data such as send instruction to controller to listen for data; read data such as send instruction to controller to send the data received by the listening radio; and/or others. In some implementations, MMR can be compliant with TCP/IP. In some implementations, API encapsulated ISO 7816 commands may be processed by the security module in addition to other commands.

In some implementations, host controller 702 can operate in accordance with the two processes: (1) the service card 104 as the master and the mobile device 106 as the slave; and (2) the card UT as the master. In the first process, the host controller 702 may pass one or more commands to the mobile device 106 in response to, for example, insertion of the service card 104 into a slot in the mobile device 106, a request from the GUI 116, and/or other events. In some implementations, the host controller 702 can request the mobile device 106 to execute one or more of following functions: Get User Input; Get Signature; Display Data; Send Data; Receive Data; and/or others. The Get User Input command may present a request through the GUI 116 for data from the user. In some implementations, the Get User Input may present a request for multiple data inputs. The data inputs may be any suitable format such as numeric, alphanumeric, and/or other strings of characters. The Get Signature command may request the mobile device 106 to return identification data such as, for example, a phone number, a device ID like an IMEI code or a MAC address, a network code, a subscription ID like the SIM card number, a connection status, location information, Wi-Fi beacons, GPS data, and/or other device specific information. The Display Data command may present a dialog to the user through the GUI 116. In some implementations, the dialog can disappear after a period of time, a user selection, and/or other event. The Send Data command may request the mobile device 106 to transmit packet data using its own connection to the external world (e.g., SMS, cellular, Wi-Fi). The Receive Data command may request the mobile device 106 to open a connection channel with certain parameters and identify data received through the connection. In some implementations, the command can request the mobile device 106 to forward any data (e.g., SMS) satisfying certain criteria to be forwarded to the service card 104.

In regards to the UT as master, the host controller 702 may execute one or more of the following commands: security module Command/Response; Activate/Deactivate; Flash Memory Read/Write; Send Data with or without encryption; Receive Data with or without decryption; URL Get Data/URL Post Data; and/or others. The security module commands may relate to security functions provided by the card and are directed towards the security module within the service card 104 (e.g., standard ISO 7816 command, proprietary commands). In some implementations, the commands may include encryption, authentication, provisioning of data, creation of security domains, update of security domain, update of user credentials after verification of key, and/or others. In some implementations, the commands may include non security related smart card commands such as, for example, read service history commands. The read service guide command may perform a read of the Electronic Service Guide data stored in the memory 612 of the service card 104. In some implementations, certain flags or areas of the memory 612 may be written to after security verification. The Activate/Deactivate command may activate or deactivate certain functions of the service card 104. The Flash Memory Read/Write command may execute a read/write operation on a specified area of the memory 612. The Read command may be used by the Media Player to receive the streaming content selected by the user for viewing. The Send Data with or without encryption command may instruct the mobile device 106 to transmit data using a wireless connection. In addition, the data may be encrypted by the service card 104 prior to transmission using, for example, keys and encryption capability stored within the set-top module 608. The Receive Data with or without decryption command may instruct the service card 104 to switch to listening mode to receive data from its wireless connection with the broadcast network 108. In some implementations, data decryption can be requested by the security module using, for example, keys and decryption algorithms available on the security module, i.e., on-board decryption. The URL Get Data/URL Post Data command may instruct the host controller 702 to return pages as per offline get or post instructions using, for example, offline URLs.

In some implementations, the host controller 702 may assign or otherwise associate URL style addressing to certain files stored in the memory 612 (e.g., flash) of the service card 104. In some implementations, the host controller 702 can locate a file using the URL and returns the file to the GUI 116 using standard HTTP, HTTPS style transfer. In some implementations, the definition of the files can be formatted using standard HTML, XHTML, WML and/or XML style languages. The file may include links that point to additional offline storage locations in the memory 612 and/or Internet sites that the mobile device 106 may access. In some implementations, the host controller 702 may support security protocols such as SSL. The host controller 702 may transfer an application in memory 612 to the mobile device 106 for installation and execution. The host controller 702 may request the capabilities of the browser on the device 106 using, for example, the browser user agent profile, in order to customize the offline Web page according to the supported capabilities of the device and the browser, such as, for example, supported markup language, screen size, resolution, colors and such.

As part of the Real time OS, the real-time framework 704 may execute one or more functions based, at least in part, on one or more periods of time. For example, the real-time framework 704 may enable an internal clock available on the CPU 610 to provide timestamps in response to at least requested events. The real-time framework 704 may allow certain tasks to be pre-scheduled such that the tasks are executed in response to at least certain time and/or event based triggers. This aspect is used by the Real Time OS to generate triggers to launch the Personal Video Recorder application, Set top box and the broadcast chipset to begin reception and recording of the content if the user set timer for content recording has been met. In some implementations, the real-time framework 704 may allow the CPU 610 to insert delays in certain transactions. In some implementation, a part of WAP standards called WTAI (Wireless Telephoney Application Interface) can be implemented to allow offline browser pages on the card 104 to make use of functions offered by the mobile device 106.

The broadcast application 706 can include any software, hardware, and/or firmware that receive broadcast content. For example, the broadcast application 706 may receive a request for content through the GUI and receive the associated broadcast signal in response to at least the request. In some implementations, the broadcast application 706 may execute one or more of the following: transmit properties of the service card 104; to the broadcast Content Distribution System; download the Electronic Service Guide data from the Broadcast Content Distribution System; tune the antenna to the right frequency based, at least in part, on selection made by the user via the Electronic Service Guide viewed on the GUI; receive the broadcasted content based, at least in part, on the subscription information; transmit user profile and authentication data to the content distribution system, receive instructions and data to update the Electronic Service Guide, receive request from the CPU to begin or end the broadcast reception; and/or other processes. In these case, the broadcast application 710 may present media through the GUI 116 that is otherwise not accessible by the mobile host device 106, i.e., foreign content.

The real-time OS 708 may execute or otherwise include one or more of the following: real-time framework 704; a host process that implements the physical interface between the service-card CPU and the mobile device 106; an interface that implements the physical interface between the service-card CPU and the security module; a memory-management process that implements the ISO 7816 physical interface between the service-card CPU and the memory 612; an application-layer process that implements the API and UT capabilities; the ACF module 604; power management; and/or others. In some implementations, the real-time OS 708 may manage the physical interface between the service-card CPU and the memory 612 that includes memory segmentation to allow certain memory areas to be restricted access and/or data buffers/pipes. In some implementations, the CPU 610 may include a separate memory controller 712 for managing the local memory 612. In some implementations, the real-time OS 708 may include a microcontroller OS configured to personalizing the set-top module 608 such as by, for example, converting raw data (account number, subscription information, user profile, receiver ID, CAS parameters) into secure encrypted information. In addition, the microcontroller OS may present the card 104 as a microSD mass storage to the host device 106. The microcontroller OS may partition the memory 612 into a user section and a protected device application section. In this example, the device application section may be used to store provider specific applications that either operate from this segment of the memory or are installed on the host device 106 from this segment of the memory.

The high speed IP interface 318 may provide the hardware protocol implementation and/or drivers for digital streaming content corresponding to the broadcasting signals received by the broadcast receiver. For example, the through this high speed IP interface, the CPU may receive non-encrypted or non-scrambled digital streaming content associated with free or off-air or non-premium channels. In this case, this streaming content is directly made available to the media player of the host device after appropriate media protocol translation if required. For example, through this high speed IP interface, the CPU may receive encrypted or scrambled digital content associated with premium or subscription channels. In this case, the content is first sent to the set-top box for decoding and unscrambling and then forwarded to the media player after any appropriate media translation.

FIG. 8 is a schematic diagram 800 of personalization of a intelligent card (e.g., the service card 104). In particular, the intelligent card may be personalized prior to being issued to a user, i.e., pre-issuance, or after being issued to a user, i.e., post-issuance. In regards to pre-issuance, intelligent cards may be personalized in mass batches at, for example, a factory. In this example, each intelligent card may be loaded with user credentials, security framework, applications, offline Web pages, and/or other data. In some implementations, a intelligent card may be personalized individually at, for example, an electronics retailer branch. In this case, a intelligent card may be individually loaded with data associated with a user after, for example, purchasing the card. As for post issuance, the intelligent card may be personalized wirelessly. For example, the service card 104 may be personalized through a cellular connection established using the mobile device 106. In some implementations, an intelligent card may be personalized by synchronizing with a computer such as client. The service card 104 may receive from an enterprise at least associated with the service GUI 116 that personalization data prior to activation including user credentials, broadcast applications, personal video recorder applications and at least one of operational flags, rule table or user interface. The personalization data present in the card may be updated after activation using at least one of the following methods: wireless or over the air messages containing special and secure update instructions; internet or client application running on a PC connected to the service card 104 via the host device or a card reader; internet application wirelessly connecting to the service card 104 via the host mobile device or user interface application of the service card 104 itself, and/or other methods.

In some implementations, provisioning of the intelligent card can be based, at least in part, on the distribution entity (e.g., service provider, wireless operator, user). For example, the intelligent card may be distributed by a service provider such as a content provider (for example, DirecTV). In the service provider implementation, the intelligent card can be pre-provisioned with user accounts. In this case, the intelligent card may be activated in response to at least initial insertion into a host device. The antenna mode may be set to physical authentication only by default. In some examples, the user may self-select a user-id/password or PIN authentication to prevent unauthorized use or through a PC cradle and plug-in management software if the host device does not have a screen and keyboard. In the wireless-operator implementation, the intelligent card may require device authentication before activation. In some examples, the user may provision service data (e.g., subscriber profile) using one of several methods. In addition, the user may add user authentication. In the user-provided implementation, the user may acquire the intelligent card from, for example, a retail store or other channels like OEM host device manufacturers. In this case, the user may activate the card in a plurality of different devices with provider selected provisioning.

In regards to activation, the intelligent card may be configured in memory mode when user acquires the card from, for example a content provider, a wireless operator, a third-party provider, and/or others. Activation of the card may include the following two levels: 1) physically, specifying antenna availability under a specific set of circumstances desired by the provider; and b) logically, at the service provider signifying activation of the broadcast application carried on the card. In some implementations, activation may be based, at least in part on device distributor, antenna availability selection, and/or type of host device as illustrated in Table 2 below.

TABLE 3 Plug-In Initial State Plug-in Seller and and Antenna Device Has No Screen/ Device Has Screen & Mode of distribution Availability Choice Keyboard keyboard Content provider ships Plug-In is in Memory Manual: User has to If the device is capable of plug-in directly to the Mode, It is full call provider's number wireless access, upon subscriber or through personalized with user's to activate his account, insertion, the plug-in participating resellers/ account information and the Device can only spawns a web page and distributors etc. Antenna mode is set to work with a single takes the user to content Physical Authentication account. User can also provider's website. The access content user self activates his provider's site on the account by entering his internet using another account number and PC to activate his matching secret personal account information (home phone number for example). The user can also optionally select a user-id and password (change Antenna availability to user authentication) at the same time. If Internet connection is not available, the device can automatically dial a voice call to content provider's number for account activation. If wireless connection is not available as well (device is only a PDA), the user has to fallback to manual activation (see left) WNO: Wireless Plug-In is in Memory Not Applicable Assumption: Device has a Network Operator Mode, it is partially functional wireless Ships plug-in bundled personalized (device connection. Operator with host device, User signature of the host offers a bundled broadcast can select his preferred device loaded to prevent application and host device and plugin user from changing host subscription. When user is bundled with it if device) while other clicks the broadcast user would like to information is not application, the user is avail of this service loaded. Antenna invited to sign-up with Availability is set to operator's partner content Device Authentication provider for a new (plug-in can only used account and subscription. with host device it is Once sign-up is shipped with) successful, account data is downloaded Over the Air or Over the Internet to the plugin and it is activated for use Device can use multiple content providers in this scenario and store multiple channels. User can select to enter a user ID and password for a content provider in the broadcast application in order to convert Antenna availability to user and device authentication for that content provider Plug-in is bound to a device signature. When removed from the device, the Antenna turns off and the plug-in turns into a simple mass memory stick. When Plug-in is inserted into another host device, the signature doesn't match and Antenna remains off. WNO: Wireless Plug-In is in Memory Not Applicable Assumption: Device has Network Operator Mode, it is functional wireless Ships plug-in as an unpersonalized. Antenna connection. Plug-In will accessory with an Availability is set to spawn an internet advice for compatible Network authentication connection to the operator devices, User can is set to On. Plug-In will portal and the broadcast select his preferred bind to first device it is application will be host device and inserted in and where downloaded upon user attempt to operate his network authentication is confirmation. User can plug-in with, to avail successful reject download and of the service choose to manually provision content provider data by going to a third party content provider or directly to the content provider website. Plug-In is bound to the device and to the wireless provider's network. If the same device is unlocked and used on another network, the plug-in will cease to operate and will revert back to memory mode. When removed from the device, the plug-in will revert to the memory mode. OEM 1: Cellphone Device Authentication Not Applicable Option A: Device manufacturer (device comes bundled Manufacturer offers a with a cellphone) broadcast application, rest of the process remains as above Option B: Wireless Operator offers a broadcast application. User goes to the wireless operator portal and downloads this application Over the Air. The rest of the process then remains the same as above Option C: User navigates to a third party broadcast application (example MSN-TV, Mobi-TV). Sign up is offered to participating content provider and applications are personalized on the plug- in Over the Internet Option D: User navigates to content provider's website and activates a new account which is personalized over the Internet on the plug-in OEM 2: Other Device Authentication User has to cradle the If the device has wireless manufacturer device to the PC with connection (it is a wireless an internet connection PDA): Same as above If and sign-up on the PC the device has no wireless by going to an content connection (it is an provider's website unconnected PDA): Same directly. Account is as left downloaded over the internet via the cradle and then the device is activated. In this process, the plug-in is bound to the device signature. When removed from the host device, the antenna turns off When plugged into another device, the device signature fails and the device behaves like a mass memory device only

The illustrated chart is for example purposes only. The user may activate an intelligent card using the same, some, or different processes without departing from the scope of this disclosure.

FIG. 9 is a flow chart illustrating an example method 900 for automatically bootstrapping an intelligent card in response to at least insertion into a host device. In general, an intelligent card may execute one or more authentication procedures prior to activation. Many of the steps in this flowchart may take place simultaneously and/or in different orders as shown. System 100 may use methods with additional steps, fewer steps, and/or different steps, so long as the methods remain appropriate.

Method 900 begins at step 902 where insertion into a host device is detected. For example, the service card 104 may detect insertion into the mobile device 106. If authentication is not required for any aspect of the intelligent card at decisional step 904, then execution ends. If authentication is required for at least one aspect, then execution proceeds to decisional step 906. If communication with the host device includes one or more errors, then, at step 908, a failure is indicated to the user. In the example, the service card 104 may present an indication of a communication error to the user using the GUI 116. If a communication error is not detected at decisional step 906, then execution proceeds to decisional step 910. In some implementations, the intelligent card uploads an SD driver to the host device. If the intelligent card only requires physical authentication, then execution proceeds to decisional step 912. If the network authentication flag is not set to on, then, at step 914, the antenna is turned on and the intelligent card is updated with host-device signature. As for the example, the service card 104 may activate the antenna for wireless transactions and update local memory with the host-device signature. If the network authentication flag is turned on at decisional step 912, then, at step 916, the intelligent card transmits a request for the network ID to the host device. Next, at step 918, the intelligent card retrieves a locally-stored network ID. If the stored network ID and the request network ID match at decisional step 920, then the card is activated at step 914. If the two network ID's do not match, then the antenna is deactivated at step 922.

Returning to decisional step 910, if the authentication is not only physical authentication, then execution proceeds to decisional step 924. If the authentication process includes device authentication, then, at step 926, the intelligent card transmits a request for a network ID to the host device. At step 928, the intelligent card retrieves a locally stored device signatures. If the intelligent card does not include at least one device signature, then execution proceeds to decisional step 934. If the intelligent card includes one or more device signatures, then execution proceeds to decisional step 932. If one of the device signatures matches the request network ID, then execution proceeds to decisional step 934. If the signatures and the request network ID do not match, then execution proceeds to step 922 for deactivation. If user authentication is not included in the authentication process, then execution proceeds to decisional step 912 for physical authentication. If user authentication is included at decisional step 934, then execution proceeds to step 938.

Returning to decisional step 924, if the authentication process does not include device authentication, then execution proceeds to decisional step 936. If user authentication is not included in the process, then, at step 922, the intelligent card is turned off. If user authentication is included, then, at step 938, the intelligent card request a user id and password from the user using the host device. While the user authentication is described with respect to entering a user id and password through the mobile host device, the user may be authenticated using other information such as a simple PIN and/or biometric information (e.g., fingerprint). Again returning to the example, the service card 104 may present a request for the user to enter a user-id and password through the GUI 116. At step 940, the intelligent card sends the entered information to the service provider using the cellular network or the broadcast network. If at the account information is validated by the service provider at decisional step 942, then execution proceeds to decisional step 912 for physical authentication. If the account information is not validated at decisional step 942, then execution proceeds to decisional step 944. If the number of attempts have not exceeded a specified threshold, then execution returns to step 938. If the number of attempts has exceed to the threshold, then the antenna is deactivated at step 922. In the example, if the event that the service card 104 fails to authorize the device, network and/or user, the service card 104 may wirelessly transmit an indication to the associated service provider using the cellular radio technology of the mobile host device 106. In this case, the illustrated method 900 may be implemented as a fraud control process to substantially prevent unauthorized use of the service card 104.

FIG. 1000 is a flow chart illustrating an example method 1000 for activating a wireless transaction system including an intelligent card. In general, an intelligent card may execute one or more activation processes in response to, for example, a selection from a user. Many of the steps in this flowchart may take place simultaneously and/or in different orders as shown. System 500 may use methods with additional steps, fewer steps, and/or different steps, so long as the methods remain appropriate.

Method 1000 begins at step 1002 where a request to activate a service card is received. For example, the user may select a graphical element displayed through the GUI 116 of a mobile host device 106 in FIG. 1. If an account activation is included at decisional step 1004, then at step 1006, a request to activate the associated user account is wirelessly transmitted to service provider using broadcast radio technology of the host device. For example, the service card 104 may wireless transmit an activation request to the service GUI 116 using the cellular radio technology of the mobile host device 106. If an account activation is not included, then execution proceeds to decisional step 1008. If card activation is not included, then execution ends. If card activation is included, then execution proceeds to decisional step 1010. If an activation code is not included, then at step 1012, one or more preprogrammed questions are presented to the user using the GUI of the host device. Returning to the initial example, the service card 104 may identify locally stored questions and present the questions to the user using the GUI 116 of the mobile host device 106. At step 1014, locally-stored answers to the programmed questions are identified. Returning to decisional step 1010, if an activation code is included, then execution proceeds to decisional step 1016. If the activation code is manually entered by the user, then at step 1018, a request for the activation code is presented to the user through the GUI of the mobile host device. In the initial example, the service card 104 may present a request for an activation code such as a string of characters to the user through the GUI 116 of the mobile host device 106. If the activation code is not manually entered by the user, then at step 1020, the service card wirelessly transmits a request for the activation code using the cellular radio technology of the host device. In the broadcast example, the service card 104 may transmit a request to the service provider using the cellular core network 108. In either case, the locally-stored activation code is identified at step 1022. If the locally stored information matches the provided information at decisional step 1024, then at step 1026, the service card is activated. For example, the service card 104 may activate in response to at least a user entering a matching activation code through the GUI 116. If the provided information does not match the locally stored information, then execution ends.

FIGS. 11A-C is an example call flow 1100 in accordance with some implementations of the present disclosure. As illustrated, the flow 1100 includes a network 1102, a host device 1104, an intelligent card 1106, and a broadcast network 1108. The host device 1104 is configured to communicate with the network 1102 and includes a slot for insertion of the intelligent card 1106. The intelligent card 1106 is configured to transmit commands to and receive data from a user interface application 1110 executed by the host device 1110 and execute access foreign services independent of the host device 1110. The card 1106 includes a CPU 1112 for accessing services and a wireless chipset 1114 for communicating with the broadcast network 1108. The CPU 1112 executes a host controller/API interface 1116 configured to transmits commands in a form compatible with the host device 1104 and convert data from the host device 1104 to a form compatible with the CPU 1112.

As illustrated, the flow 1100 may include multiple sessions 1120 between the host device 1104 and the card 1106 and between the card 1106 and the broadcast network 1108. The session 1120a illustrates a session managed by the card 1106 using the network capabilities of the host device 1110. In this example, the card 1106 transmits data for transmission through a network connected to the host device 1104, and after receiving the data, the host device 1104 transmits the data to the network 802. In response to receiving data from the network 1102, the host device 1104 may automatically transmit the received data to the card 1106. In some implementations, the card 1106 may transmit a request for a device signature to the host device 1104 as illustrated in session 1120b. For example, the card 1106 may request the device signature during a bootstrapping process. The session 1120c illustrates that a user may submit commands to the card 1106 through the interface of the host device 1104. For example, the user may request that the card display the user's transaction history through the interface of the host device 1104.

In some implementations, the card 1106 may receive a command to activate or deactivate the antenna through the host device 1104 as illustrated in session 1120d. For example, a service provider may identify irregular transactions and transmit a command through the network 1102 to deactivate the card 1106. The card 1106 may authorize a user by requesting a user-id and password using the host device 1104. As illustrated in session 1120e, the user may submit a user-id and password to the card 1106 using the interface of the host device 1104, and in response to an evaluation of the submitted user-id and password, the card 1106 may present through the host device 1104 an indication that the user verification is successful or has failed. In some implementations, a user and/or service provider may request a transaction history of the card 1106 as illustrated in session 1120f. For example, a service provider may transmit a request for the transaction history through the network 1102 connected to the host device 1104, and in response to at last in the request, the card 1106 may transmit the transaction history to the service provider using the network 1102 connected to the host device 1104. In some implementations, the user may present offline Web pages stored in the card 1106 as illustrated in session 1120. For example, the card 1106 may receive a request to present an offline Web page from the user using the host device 1104 and present the offline page using the URL in the request. In some implementations, content data stored in the memory of the card 1106 or available via live reception of streaming content may be presented through, for example, the host device 1104 as illustrated in session 1120h. For example, the user may request specific information associated with the Electronic Service Guide and the card 1106 may retrieve the data and present the data to the user using the host device 1104. In addition, the user may write data to the memory in the card 1106 as illustrated in session 1120i. For example, the user may setup timers for the Personal Video Recorder application on the card 1106 and the card 1106 may indicate the success and failure of the timer setup

In regards to session between the card 1106 and the terminal, the flow 1100 illustrates the personalization session 1120k and the transaction session 1120l. In regards to personalization, a service provider may personalize a card 1106 with user credentials, user applications, Web pages, and/or other information as illustrated in session 1120k. For example, the broadcast network 1108 may transmit a provisioning request to the card 1106 including associated data. The protocol translation 1118 may translate the personalization request to a form compatible with the card 1106. In response to at least the request, the CPU 1112 transmit an indication whether the personalization was a success or not using the protocol translation 1118. Prior to the a broadcast session beginning live reception, the broadcast network 1108 may submit a subscription verification challenge to the card 1106 as illustrated in session 1120l. In this case, the card 1106 may identify a receiver signature of the receiver 1118, present associated data to the user through the host device 1104, and transmit the signature to the broadcast network 1108 using the protocol translation 1118.

FIG. 12 is a flow chart illustrating an example method 1200 for managing the Electronic Service Guide application. In general, an intelligent card may receive ESG data from the broadcast network and display it to the user in response to at least an event. Many of the steps in this flowchart may take place simultaneously and/or in different orders as shown.

Method 1200 begins at step 1202 where ESG data currently stored is identified. For example, the service card 104 may receive ESG data from the broadcast network or the cellular network such as channel lineup, program listing, program information and program ratings. At step 1204, previously downloaded ESG content is identified. In the example, the service card 104 may identify content previously downloaded from the content provider to the local memory in the card 104. In some implementations, the service card 104 may identify one or more aspects of memory such as file names, file sizes, dates, and/or other aspects. If the previously-downloaded content matches the current content at decisional step 1206, then execution ends. If the previously-downloaded content does not match the current content, then, at step 1208, at least a portion of the locally-stored content is automatically updated in the local memory. As for the example, the service card 104 may only download content identified as new content or content that was previously not downloaded. In downloading the content, the service card 104 may substantially updates local-stored ESG content according to the latest available ESG from the service provider

FIG. 13 is a flow chart illustrating an example method 1300 for managing the Personal Video Recorder application. In general, an intelligent card may automatically receive data from the broadcast network and record it to the memory (if space is available) in response to at least an event (timer). Many of the steps in this flowchart may take place simultaneously and/or in different orders as shown.

Method 1300 begins at step 1302 where a timer event triggers the beginning of broadcast reception. For example, the service card 104 may automatically tune the antenna to the channel corresponding to the program that the user has setup to record as associated with the timer. At step 1304, available memory space is identified. In the example, the service card 104 may identify free local memory in the card 104. If the available memory is below a certain threshold (configured by the service provider) at decisional step 1306, then execution ends. If available memory is above a certain threshold, then, at step 1308, broadcast reception is started and content is automatically recorded in the local memory in a newly created program data file. After a specified size of program data is recorded, available memory is checked again and the process is repeated by appending to the program data file until either the program ends or the available memory falls below the threshold. Once the program ends, the program data file is finalized and given a unique identifier so that it can be accessed for viewing.

A number of embodiments of the invention have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. Accordingly, other embodiments are within the scope of the following claims.

Claims

1. A cover for a consumer device, comprising:

side surfaces configured to be adjacent at least a portion one or more side surfaces of the consumer device;

a rear surface configured to be adjacent at least a portion of a rear surface of the consumer device and connected to the side surfaces, the side surfaces and the rear surface form an opening that receives at least a portion of the consumer device, a first portion of at least one of the surfaces includes a connector for connecting to a port of the consumer device;

the connector that includes a first interface that connects to the port of the consumer device and second interface that substantially duplicates an original port of the consumer device;

a physical interface included in at least one of the surfaces that receives memory devices external to the consumer device;

a circuit integrated within at least one of the surfaces and that connects the physical interface to the connector; and

a broadcast service card connected to the physical interface and that receives broadcast content independent of the consumer device.

2. The cover of claim 1, wherein the physical interface that receives an external memory device comprises a microSecureDigital (microSD) slot.

3. The cover of claim 1, the circuit further comprising a conversion module that converts signals between a form compatible with the broadband service card and a form compatible with the consumer device.

4. The cover of claim 3, wherein the conversion module converts between a SD signal and a Universal Serial Bus (USB) signal.

5. The cover of claim 1, the consumer device comprising an iPhone, the connector comprising an iDock connector.

6. The cover of claim 1, wherein one or more of the side surfaces are substantially arcuate to substantially maintain a shape and dimensions of the consumer device.

7. The cover of claim 1, wherein the broadband service card comprises:

a communication module that wirelessly receives broadcast signals encoding content;

memory that stores user information used to decrypt the encoded content independent of the mobile host device, the stored information associated with a content provider; and

a service module that decrypts the encoded content in response to at least an event and presents the content through the GUI of the mobile host device.

8. The service card of claim 1, the broadcast signals comprise at least one of satellite broadcast signals, terrestrial broadcast signals, or IP broadcast signals.

9. The service card of claim 1, wherein the service module comprises an operating system with a runtime environment that executes a locally-stored broadcast application for receiving the content independent of the mobile host device.

10. The service card of claim 1, wherein a user-interface module that presents information associated with receiving the content through the GUI of the mobile host device.

11. The service card of claim 6, wherein the user-interface module further presents a request for user identification including at least one of a Personal Identification Number (PIN), user ID and password, or biometric signature through the GUI of the mobile host device, the service module further verifies the submitted user identification with user identification locally stored in the secure memory prior to accessing foreign services.

12. The service card of claim 1, wherein the service module selectively switches a broadcast receiver between an activate state and an inactivate state in response to at least an event.

13. The service card of claim 8, wherein the switching event includes a selection through a GUI of the mobile host device.

14. The service card of claim 1, wherein the service module further comprises a protocol translation module that translates signals from broadcast content to content processable by the mobile host device.

15. The service card of claim 1, further comprising an authentication module that authenticates at least one of a network of the mobile host device, the mobile host device, or a user.

16. The service card of claim 1, wherein the service card is initialized in response to at least insertion in the port of the mobile host device.

17. The service card of claim 1, further comprising an activation module that activates the service card in response to at least a user request or an initial insertion into the mobile host device.

18. The service card of claim 15, wherein the service card is activated based, at least in part, on a user manually entering an activation code through the GUI of the mobile host device.

19. The service card of claim 1, wherein the service card presents the content through the GUI independent of loading a driver onto the mobile host device.

20. The service card of claim 1, wherein the service card emulates a set-top box when receiving broadcast signals.

21. The service card of claim 1, further comprising a power module that receives power from the mobile host device.

22. The service card of claim 1, wherein an enterprise at least associated with the content provider uploads personalization data prior to activation, wherein the personalization data includes the user information and a broadcast application.

23. The service card of claim 18, the service module further operable to update the personalization data after activation in response to at least one of a wireless signal including secure update instructions or a wired signal through a client connected to the service card.

24. A method, comprising:

enclosing at least a portion of a consumer host device using a cover;

physically interfacing a port of the consumer host device using the cover;

wirelessly receiving broadcast signals encoding content;

storing user information used to decrypt the encoded content independent of the mobile host device, the stored information associated with a content provider; and

decrypting the encoded content in response to at least an event; and

presenting the content through the GUI of the mobile host device.

25. The method of claim 24, the broadcast signals comprise at least one of satellite broadcast signals, terrestrial broadcast signals, or IP broadcast signals.

26. The method of claim 24, further comprising executing a locally-stored broadcast application for receiving the content independent of the mobile host device.

27. The method of claim 24, wherein a user-interface module that presents information associated with receiving the content through the GUI of the mobile host device.

28. A system, comprising:

a means for enclosing at least a portion of a consumer host device using a cover;

a means for physically interfacing a port of the consumer host device using the cover;

a means for wirelessly receiving broadcast signals encoding content;

a means for storing user information used to decrypt the encoded content independent of the mobile host device, the stored information associated with a content provider;

a means for decrypting the encoded content in response to at least an event; and

a means for presenting the content through the GUI of the mobile host device.