WO2010091312A1 - Apparatuses, methods and systems for an enhanced device feature cradle - Google Patents

Abstract

Aspects of apparatuses, methods and systems for an enhanced device feature cradle (hereinafter, "EDFC") are discussed The EDFC facilitates supplementing and enhancing the features of a user's primary device (e g, multi-media and/or mobile device) In one implementation (a heavy EDFC), the EDFC facilitates enhancing a user's primary multi-media device with full suite of enhanced features including cellular phone capabilities, camera/video features, wireless transmission features, GPS features, and a wide variety of other sensor data, hardware module, and/or communication features In another implementation (a light EDFC) the EDFC facilitates enhancing a user's primary smartphone device with one or a few specific enhanced features The EDFC Interface thus expands the possibilities for mobile device features, capabilities, applications, gameplay, functionality and/or the like by allowing the user to effectively and seamlessly expand and/or supplement the features of the user's primary device.

Description

APPARATUSES, METHODS AND SYSTEMS FOR AN ENHANCED

DEVICE FEATURE CRADLE

RELATED APPLICATIONS

[o o o i] Applicant hereby claims priority under 35 USC §119 for United States provisional patent application serial no. 61/150,718 filed February 6, 2009, entitled "APPARATUSES, METHODS AND SYSTEMS FOR AN ENHANCED DEVICE FEATURE CRADLE," attorney docket no. 19626-003PV.

[0002] The entire contents of the aforementioned applications are herein expressly incorporated by reference.

FIELD

[0003] The present invention is directed generally to an apparatuses, methods, and systems of multi-media mobile device connection interface and control, and more particularly, to APPARATUSES, METHODS AND SYSTEMS FOR AN ENHANCED DEVICE FEATURE CRADLE.

BACKGROUND

[0004] Multi-media mobile devices, such as a multi-media cell phone, a portable video player, and/or the like, are popular with consumers for a variety of utilities nowadays. For example, a multi-media mobile device may display a combination of media content, such as text, audio, still images, animation, video and other interactivity content forms on a user handset.

SUMMARY

[0005] The APPARATUSES, METHODS AND SYSTEMS FOR AN ENHANCED DEVICE FEATURE CRADLE (hereinafter "EDFC") provides an interface to expand features of a multi-media mobile device. The EDFC facilitates the implementation of a rich feature set that is customizable and dovetails with a broad number of user multi- media and/or mobile devices. For example, in one implementation, the EDFC may be configured to facilitate a significantly enhanced feature set to supplement a user's multi- media device (e.g., a portable music player). In another implementation, the EDFC may be configured to facilitate a significantly enhanced feature set to supplement a user's mobile device. In some implementations, the EDFC may be used to supplement a primary device's feature set transparently to a user, whereas in other implementations, the EDFC may be configured to drive enhanced functionality applications by actively controlling the primary device's display (e.g. implementing VPN application).

[0006] In one embodiment, a mobile device feature extension apparatus is disclosed, comprising: a sheath receptacle to interface with a primary mobile device; an electronic data communication port affixed to the sheath receptacle to establish a communication connection with the primary mobile device; and one or more elements providing extended features to the primary mobile device.

[0007] In one embodiment, a mobile device feature extension processor- implemented method is disclosed, comprising: receiving an indication of new component attached from the electronic data communication port; receiving hardware identifying data from the electronic data communication port; determining an extended feature of the new component based on the hardware identifying data; and obtaining an application component to engage the extended feature. [0008] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying appendices and/ or drawings illustrate various non- limiting, example, inventive aspects in accordance with the present disclosure: [0010] FIGURE 1 is of a block diagram illustrating an overview of an implementation of data flows between an enhanced device feature cradle (hereinafter "EDFC") system and affiliated entities in one embodiment of the EDFC operation; [0011] FIGURE 2 provides an implementation of EDFC system components in one embodiment of EDFC operation; [0012] FIGURE 3 A-D illustrate example overviews of an enhanced device feature cradle engaged with a user's primary multi-media and/or mobile device within implementations of the EDFC operation; [0013] FIGURES 4A-B illustrate aspects of the functionality associated with implementations of the EDFC operation; [0014] FIGURES 5A-C illustrate example logic flows in an embodiment of the EDFC operation;

[0015] FIGURES 6A-B illustrate example logic flows in alternative embodiments of the EDFC operation;

[0016] FIGURE 7 provides an example screen shots illustrating aspects of implementations of EDFC within one embodiment of the EDFC operation; and [0017] FIGURE 8 is of a block diagram illustrating embodiments of the EDFC controller; [0018] The leading number of each reference number within the drawings indicates the figure in which that reference number is introduced and/or detailed. As such, a detailed discussion of reference number 101 would be found and/or introduced in Figure 1. Reference number 201 is introduced in Figure 2, etc.

DETAILED DESCRIPTION

EDFC [0019] This disclosure details aspects of apparatuses, methods and systems for a enhanced device functionality cradle (hereinafter, "EDFC"). EDFC embodiments may facilitate transparently supplementing and/ or actively controlling a user's primary multi-media and/or mobile device (e.g., a user's portable music player and/or mobile phone device) to provide extended features.

[0020] For example, in one implementation, a user may engage a portable music player with an implementation of the EDFC configured with Bluetooth, WI-FI, camera, and/or cellular phone functionality to achieve a enhanced feature device for wireless communications. In this type of implementation, the additional features may be achieved by establishing a communication link between one or more hardware sensor modules situated in the cradle and the user's primary device. An application on situated on the primary device may be configured to receive and process data from the EDFC sensor modules for display to the user. In that case, the user may effectively upgrade his/her music player into a cellular phone music player.

[0021] For another example, the EDFC may be configured to take control of the primary device's display and facilitate remote display of application states for applications running on cradle and/or other devices. In one embodiment, the EDFC may enable a user to manipulate a mobile device, such as on a smart phone platform, e.g. Apple's iPhone OS, Google's Android OS, Blackberry's OS, and/or the engage and/or stimulate mobile device sensors, and/or the like, and have the resulting response in a mobile device application be transmitted in a real-time manner for display on one or more remote display devices (e.g., a television, a desktop, etc.). [0022] It is to be understood that, depending on the particular needs and/or characteristics of an EDFC user, mobile device, application, control configuration, display device, data payload, communication and/or network framework, hardware configuration, monetization model, and/ or the like, various embodiments of the EDFC may be implemented that enable a great deal of flexibility and customization. For purposes of illustration only, the instant disclosure discusses embodiments and/ or applications of the EDFC within the context of a cradle configured to interact with a user's primary device - i.e., a multi-media player and/or a mobile phone. However, it is to be understood that the system described herein may be readily configured and/or customized for a wide range of other applications and/or implementations. For example, aspects of the EDFC may be adapted for game and/or non-game related mobile device applications; applications, other types of integrated sensors (e.g., temperature, accelerometer, pressure, position, elevation, light intensity, wind speed, data rate, and/or the like); and/or the like applications and/or components. It is to be understood that the EDFC may be further adapted to other implementations or interface, control, and/or display applications. [0023] FIGURE 1 is of a block diagram illustrating an overview of an implementation of data flows between an EDFC system and affiliated entities in one embodiment of the EDFC operation. In Figure 1, a user (or users) 105 operating a primary device 110 connected to an EDFC device 100, an (optional) external device 120, an EDFC database 119, an EDFC server 130 and a system administrator 130 are shown to interact via a communication network 113.

[0024] In one embodiment, a user 105 may operate with a primary device 110 to connect to an EDFC 100 for extended features. In one implementation, the primary device may be directly housed in the EDFC device 100, which may take a form similar to a plug-in cradle, as shown in Figures 3A-D. In an alternative implementation, For another example, and the primary device may be directly housed into the EDFC device 100. For another example, the EDFC device 100 may be connected to the primary device 110 via a communications network, such as 3G wireless, Wi-Fi, Bluetooth, and/or the like, if the EDFC device and the primary device are network-enabled.

[0025] In one embodiment, the primary device 110 may include a wide variety of different devices and technologies such as, but not limited to mobile devices, dedicated game handsets, digital multi-media player, general computing devices, and/or the like. The EDFC device may include extended components and features such as gaming facilities, cellular communications modules, Wi-Fi interfaces, emulators, sensors, GPS applications, biometrics reader (e.g., fingerprint swiper, etc.), camera, human interface devices (e.g., mini keyboard, touchpad mouse, etc.), power supplies, and/or the like. For example, in one implementation, the primary device may be an Apple iTouch, which may be equipped with a GPS device by the extended EDFC device.

[0026] The EDFC facilitates connections through the communication network 113 based on a broad range of protocols that include WiFi, Bluetooth, 3G cellular, Ethernet, physical tethers (e.g., iPhone Video AV to Dock Connector Cable, which allows for connection to a monitor or TV), and/or the like. In one embodiment, the communication network 113 may be the Internet, a Wide Area Network (WAN), a telephony network, a Local Area Network (LAN), a Peer-to-Peer (P2P) connection, and/or the like. In one embodiment, the primary device 110 housed with an EDFC device 100 may detect, handshake and interact with an external system 120 to exchange control information and data payloads via the communication network 113. The external systems 120 may include facilities and technologies such as GPS satellite systems and services, cellular communications carriers, Internet service providers, and/or the like. For example, in one implementation, the EDFC device 100 may provide a network component such that the primary device 110, which may be a multi-media player, may project its source display onto the external device remote display 120. For another example, the EDFC device 100 may provide a GPS receiver to the primary device such that the primary device may have GPS reception and communicate with a GPS satellite system. [ 0027] In one embodiment, the EDFC entities such as the primary device 110 with the EDFC device 100, the external system 120 and/or the like, may also communicate with an EDFC database 119. In some embodiments, distributed EDFC databases may be integrated in-house with the external system 120, and/or the primary device 110. In other embodiments, the EDFC entities may access a remote EDFC database 119 via the communication network 113. In one embodiment, the EDFC entities may send data to the database 119 for storage, such as, but not limited to user account information, application data, protocol data, application history, and/or the like. [0028] In one embodiment, the EDFC database 119 may be one or more online database connected to a variety of vendors, such as hardware vendors (e.g. Apple Inc. , Intel, Sony, etc.), EDFC application vendors (e.g. Nintendo, Game Cube, Game Boy, etc.), service vendors (e.g. Verizon, AT&T, PlayStation Network, \V1iC0nnect24, etc.) and/or the like, and obtain updated hardware driver information, new application packages and services from such vendors. In one embodiment, the primary device 110 and/or the EDFC device 100 may constantly, intermittently, and/or periodically download updates, such as updated user profile, updated driver specifications, updated software programs, updated command instructions, and/or the like, from the EDFC database 119 via a variety of connection protocols, such as Telnet FTP, HTTP transfer, P2P transmission and/or the like. [o o 29] In a further embodiment, the EDFC device 100 and the primary device 110 may connect to an EDFC server 130 via the communication network 113. For example, in one implementation, the EDFC device 100 may connect to the EDFC server 130 for hardware registration, drivers validation, upgrade, and/or the like.

[0030] In one embodiment, a system administrator 140 may communicate with the EDFC entities for regular maintenance, service failure, system updates, database renewal, security surveillance and/or the like via the communication network 113. For example, in one implementation, the system administrator may be a user, who may directly operate with the primary device 110 to configure system settings, parental control, and/or the like. In another implementation, the system administrator may be a service vendor, e.g., Verizon, AT&T wireless, \V1iC0nnect24, etc., which may register and subscribe the primary device with extended EDFC component for services. [0031] FIGURE 2 illustrates an implementation of EDFC system components in one embodiment of EDFC operation. An EDFC interface device 201 may contain a number of functional modules and/or data stores. An EDFC controller 205 may serve a central role in some embodiments of EDFC operation, serving to orchestrate the reception, generation, and distribution of data and/or instructions to, from and between target device(s) and/ or client device(s) via EDFC modules and in some instances mediating communications with external entities and systems. [o o32] In one embodiment, the EDFC controller 205 may be housed separately from other modules and/or databases within the EDFC system, while in another embodiment, some or all of the other modules and/or databases may be housed within and/or configured as part of the EDFC controller. Further detail regarding implementations of EDFC controller operations, modules, and databases is provided below.

[0033] In one embodiment, the EDFC Controller 205 may be coupled to one or more interface components and/or modules. In one embodiment, the EDFC Controller may be coupled to a user interface (UI) 210, a maintenance interface 212, and a power interface 214. The user interface 210 may be configured to receive user inputs and display application states and/or other outputs. The UI may, for example, allow a user to adjust EDFC system settings, select communication methods and/or protocols, initiate a remote display mode, engage mobile device application features, identify driver information and/or the like. In one implementation, the user interface 210 may include, but not limited to devices such as, keyboard(s), mouse, stylus(es), touch screen(s), digital display(s), and/or the like. In one embodiment, the maintenance interface 212 may, for example, configure regular inspection and repairs, receive system upgrade data, report system behaviors, and/ or the like. In one embodiment, the power interface 214 may, for example, connect the EDFC controlled 205 to an embedded battery and/or an external power source. [0034] In one embodiment, the EDFC Controller may further be coupled to an drivers engine 260, configured to run device application software. In one implementation, the drivers engine 260 may receive sensory input information originating from one or more integrated sensors and interpret the information to update the configuration of an drivers specification. In one implementation, the updated drivers specification data may be transferred to a primary device and configured to run mobile device application software. For example, in one implementation, an application running on a primary device may comprise a video game, such as may be controlled via a motion-sensitive mobile device. The EDFC may be configure to transmit the video game data received from a co-playing device and/or sensory input data to the primary device for processing and/or display, more detail regarding which may be found herein and/or incorporated by reference. [0035] In one implementation, the EDFC Controller 205 may further be coupled to a sensor module 220, configured to interface with and/or process signals from sensor input/output (I/O) components 225. The sensor I/O components 225 may be stimulated by user manipulation, environmental conditions, and/or the like to generate electrical signals that may be received and/or processed by the sensor module 220 and/or other EDFC components, which in turn act to generate input controls which can be used by the application. A wide variety of different sensors may be compatible with EDFC operation and may be integrated with sensor I/O components 225, such as but not limited to transducers, accelerometers, thermometers, anemometers, barometers, microphones, and/or the like, configured to measure states of motion, sound level, volume, pitch, pressure, wind speed, temperature, data transfer rate, light intensity level, position, elevation, weather, moisture level, humidity, and/or the like. In one implementation, the sensor module 220 may configure signals received from the sensor I/O components 225 in a form suitable for an application being run by the applications engine 260. In another implementation, the applications engine 260 may receive signals directly from sensor I/O components 225 for processing to update an application state for one or more running applications. For example, in one implementation, a user may engage a EDFC remote control device housing in a golf club (as will be further illustrated in one implementation in Figure 8). The user may swing the remote control device as if swinging a real golf club in field, and the sensor I/O 225 may detect signals of the motion of the club and transfer the signals (e.g. electrical pulses from accelerometers indicating a velocity and a direction of a swing, etc.) suitable to the sensor module 220. The sensor module 220 may process and analyze the received signals and generate data describing characteristics of the movement, e.g. direction of the movement, speed of the movement, motion level, etc., and transmit the data to the EDFC controller 205. For example, in one embodiment, the iPhone SDK toolkit and/or runtime libraries may be installed and/or used to access and interpret such actions. [0036] In one embodiment, the EDFC Controller 205 may further be coupled to a communications module 230, configured to interface with and/or process signals from communications I/O components 235. The communications I/O components 235 may comprise components facilitating transmission of electronic communications via a variety of different communication protocols and/or formats as coordinated with and/or by the communications module 230. Communication I/O components 240 may, for example, contain ports, slots, antennas, amplifiers, and/or the like to facilitate transmission of display instructions, such as may instruct a remote display what and/or how to display aspects of a mobile device application state, via any of the aforementioned methods. Communication protocols and/or formats for which the communications module 230 and/or communications IO components 235 may be compatible may include, but are not limited to, GSM, GPRS, W-CDMA, CDMA, CDMA2000, HSDPA, Ethernet, WiFi, Bluetooth, USB, and/or the like. In various implementations, the communication I/O 235 may, for example, serve to configure data into application, transport, network, media access control, and/ or physical layer formats in accordance with a network transmission protocol, such as, but not limited to FTP, TCP/IP, SMTP, Short Message Peer-to-Peer (SMPP) and/or the like. The communications module 230 and communications I/O 235 may further be configurable to implement and/or translate Wireless Application Protocol (WAP), VoIP and/or the like data formats and/or protocols. The communications I/O 235 may further house one or more ports, jacks, antennas, and/or the like to facilitate wired and/or wireless communications with and/or within the EDFC system. For instance, in the above example, the EDFC controller 205 may transmit the received sensor data characteristics of the movement of the controller device to the communication module 230, and the data may then be transmitted to external entities (e.g. the target device, etc.) through the communications I/O 235.

[0037] Numerous data transfer protocols may also be employed as EDFC connections, for example, TCP/IP and/or higher protocols such as HTTP post, FTP put commands, and/or the like. In one implementation, the communications module 230 may comprise web server software equipped to configure application state data for publication on the World Wide Web. Published application state data may, in one implementation, be represented as an integrated video, animation, rich internet application, and/or the like configured in accordance with a multimedia plug-in such as Adobe Flash. In another implementation, the communications module 230 may comprise remote access software, such as Citrix, Virtual Network Computing (VNC), and/or the like equipped to configure application state data for viewing on a remote client (e.g., a remote display device). [0038] In one implementation, the EDFC controller 205 may further be coupled to a plurality of databases configured to store and maintain EDFC data. A drivers database 240 may contain drivers, hardware specification types, user IDs, hardware information, system settings, configurations, operating system requirements, application interface elements, and/or the like. A protocols database 245 may include data pertaining to communication protocols and/or data configurations suitable for publication on the World Wide Web, sharing between client and server devices in a remote-access software setup, and/or the like. A user database 250 may contain information pertaining to account information, contact information, profile information, identities of hardware devices, Customer Premise Equipments (CPEs), and/or the like associated with users, application history, system configurations, and/or the like. A hardware database 245 may contain information pertaining to hardware devices with which the EDFC system may communicate, such as but not limited to user devices, display devices, target devices, Email servers, user telephony devices, CPEs, gateways, routers, user terminals, and/or the like. The hardware database 228 may specify transmission protocols, data formats, and/or the like suitable for communicating with hardware devices employed by any of a variety of EDFC affiliated entities. [0039] In one embodiment, the EDFC databases may be implemented using various standard data-structures, such as an array, hash, (linked) list, struct, structured text file (e.g., XML), table, and/or the like. For example, in one implementation, the XML for the User Profile in the user database 250 may take a form similar to the following example: <User> <Quasi-static info> <User_ID>123-45-6789</User_ID> <Hardware ID> ΞDAΞFK45632_iPhone 3.0 </Hardware ID> <Census info> John Smith; 123 Maple Dr., Smalltown, CA 92676; (123)456-7890; j smithSemail . com; 55 years; male; white; married; 2 children; etc. </Census info>

</Quasi-static info> <Dγnamic info> <Application historγ> <Last login> <Ξerver ID> UΞ-CA-ADD00089 </Ξerver ID> <Time> 19:33:25 08-30-2009 </Time>

</Last login>

</Application historγ> </Dγnamic info> </User> [0040] Figures 3A-D illustrate an overview of example implementations of hardware components within one embodiment of the EDFC. As shown in Figures 3A-D, in one embodiment, an EDFC may take a form similar to a sheath receptacle in a shape such that a mobile device may be docked. Figure 3A illustrates a front view of an implementation of the EDFC. In this implementation the cradle 300 is configured to engage with a particular type of user primary device. It is to be understood that the 1 EDFC facilitates significant flexibility and as such primary device connector 310 as a

2 component on the EDFC may be substituted with a variety of connectors to facilitate

3 engagement with a broad array of user devices. For example, the connector 310 may

4 comprise a variety of dock connectors for different devices and technologies such as, but

5 not limited to, keyboard ports, serial ports, parallel ports, P/S2 connectors, USB ports,

6 eSATA ports, FireWire ports, Bluetooth receivers, Wi-Fi receivers, 3G receivers, and/or

7 the like. For another example, if the primary device is a third or higher generation

8 Apple iPod product, the EDFC connector 310 may be a 30-pin dock connector allowing

9 for FireWire and USB connectivity.

10 [0041] The EDFC in Figure iA also illustrates an EDFC connection point 320.

11 Depending on the implementation, the EDFC may be configured with a rechargeable

12 battery to power the various EDFC components, as well as supplement the power supply

13 of the primary device. In one implementation, the EDFC may be configured to be

14 recharged via its USB cable connectable at point 320 and/or via its own docking station.

15 [0042] Figure 3B illustrates a front view of an EDFC 300 engaged with a user's

16 primary device 330. As illustrated in Figures 3A-D, the EDFC unit may be contoured to

17 complement a variety of user primary devices, as well as facilitating robust engagement

18 between the EDFC and a user's primary device, as well as providing a non-intrusive,

19 seamless contour between devices.

20 [0043] The EDFC may be configured with a variety of sensors and/or hardware

21 modules that facilitate a broad array of features. For example, as in Figure 3C, the

22 EDFC may be configured with a keypad 340. Depending on the implementation, keypad

23 340 may be configured to replicate a QWERTY keyboard and/or may be configured to 1 facilitate a hybrid typing keypad, such as those implemented on certain mobile email

2 devices. As discussed above, EDFC may be configured to engage a variety of user

3 primary devices For example, the EDFC in Figure 3C illustrates a USB connector 315

4 that may be used to establish a data/power transfer between the EDFC and the primary

5 device. Alternately, the EDFC with keypad 340 may implement the device connector

6 310 or any number of other device connectors instead of, or in addition to connector

7 315. Similarly to the EDFC from Figure 3A, the EDFC in Figure 3D is configured with

8 connection point 320, to facilitate receiving a USB connector to transfer data and/ or

9 power from any number of other devices. 0 [0044] As briefly discussed above, the EDFC is configured to supplement and1 enhance a primary device's feature set. For example, in one implementation, the EDFC2 may incorporate a number of hardware modules and/or internal sensors, as well as3 facilitate connections with a broad range of external peripheral devices. For example, as4 illustrated in Figure 3D, the EDFC may be configured with a camera element 345 and5 related hardware to facilitate capturing still images, as well as video feeds and6 transferring the image/video data to the user's primary device. 7 [0045] It is to be understood that the EDFC may be customized based on the8 needs of the user and implementations may vary between 'light' feature supplemental9 solutions. For example, a 'light' EDFC may be configured with one or a few feature(s)0 such as the camera module from Figure 3D. This type of EDFC may be paired quite1 effectively with a user's primary device that already has a suite of functionality such as a2 high-end smartphone. Alternately, implementations of the EDFC may be customized3 with feature-rich functionality, including a variety of hardware modules (e.g., a camera 1 module, a keypad module and/ or the like); a variety of peripheral connection nodes, and

2 /or a series of internal sensors (e.g., as discussed above). These implementations of the

3 EDFC may appeal to a user who wants a full suite of technology features, but has a

4 relative stripped down primary device.

5 [0046] Figures 4A-B illustrate aspects of engaging EDFC with a user's primary

6 device configured to facilitate gameplay within embodiments of EDFC operation. In

7 Figure 4A, a user 401 manipulates an engaged EDFC primary device 405 to stimulate

8 sensors in the therein. A wide variety of mobile devices may be employed within

9 different embodiments of the EDFC. In one embodiment, the EDFC may be operated in

10 conjunction with primary devices containing integrated motion sensors, accelerometers,

11 and/or the like, such as the Apple iPhone. Manipulation of the EDFC engaged device

12 405 by the user 401 may facilitate an application running on the mobile device. This

13 data may then be transferred to EDFC communication modules for transfer to a

14 peripheral for display (such as monitor 420). In an alternate embodiment, the EDFC

15 may incorporate a dedicated web server and engages an Apple iPhone. The data from

16 the dedicated web server may be pushed via VCN to the iPhone for display via the

17 EDFCs and the iPhone's Wi-Fi communication modules. It is to be understood that in

18 some implementations, communications between the EDFC and the primary device may

19 occur via a variety of wireless communication protocols, such as, but not limited to 3G,

20 Wi-Fi, Bluetooth, and/or the like.

21 [0047] For example, in the illustrated implementation, the mobile device is

22 running a golfing game application, and the user 401 is stimulating motion sensors in

23 the mobile device 405 in order to simulate swinging of a golf club. The mobile device 1 405 may further contain integrated components providing communication capabilities

2 with the EDFC to facilitate sending signals via a communications network 410 to one or

3 more remote display devices 415. The communications network may, for example,

4 comprise a mobile data network, local area network, the internet, cable connection,

5 WiFi, Bluetooth, and/or the like. A wide variety of remote displays may be employed

6 within different embodiments of EDFC operation as well. For example, remote displays

7 compatible with EDFC operation may include, but are not limited to, computer

8 terminals, thin clients, television sets, communication network coupled monitors,

9 and/or the like. Based on the signal received via the communications network 410 from

10 the EDFC engaged mobile device 405, the remote display 415 may provide a display

11 screen 420 corresponding to the application state of the application running on the

12 mobile device.

13 [0048] In one implementation, the display screen 420 is the same as a display

14 screen that is or would be displayed on the mobile device itself as a representation of the

15 application state of the application running on the mobile device. Fig. 4B shows an

16 alternative implementation, in which the remote display comprises a computer terminal

17 425, and the EDFC engaged mobile device 405 is connected to the computer terminal by

18 ways of a cable connection 430. It is to be understood that various combinations of

19 mobile devices, remote displays, communications networks and/or connections, and/ or

20 the like are possible within various embodiments of EDFC operation. For example, a

21 computer terminal 425 may be communicatively coupled to the EDFC engaged mobile

22 device 405 by ways of a wireless internet connection rather than a direct cable

23 connection. [0049] Figure 5A provides a logic flow diagram illustrating aspects of docking a primary device into an EDFC cradle in one embodiment of EDFC operation. In Figure 5A, the EDFC may be initiated by a user physically attaching the primary device into an EDFC cradle 500. In one embodiment, the primary device may detect new hardware attached to the dock connector 505, and the EDFC may send hardware identifying data via the dock connector 507. [o θ5θ] In one embodiment, the EDFC may determine whether the adds-on cradle is compatible with the primary device 510. In one implementation, the EDFC may determine based on the received hardware identifier, dock connector protocol type, and/or the like of the EDFC cradle, whether the cradle satisfies hardware requirements of the primary device's hardwares and/or operating system. For example, in one implementation, if the cradle adopts a USB 3.0 connector, but the primary device, e.g., a first generation Apple iPod Shuffle, etc., does not support USB 3.0 standard, the EDFC may determine the cradle is not compatible with the primary device. If the cradle is determined incompatible, in one implementation, the EDFC may abort the connection attempt.

[0051] In some embodiments, the cradle may supplement for a feature-limited version of a primary device. For example, an iPod Touch is much like an iPhone that lacks a GPS location component, a compass, a cellular phone chipset, and a camera. As such, in one embodiment, the EDFC may use the exact chipsets and components available in the more full-featured devices (e.g., iPhone) as components in the cradle. Such an embodiment allows for little-to-no modification of the less-featured device. As such, each of the components missing that are supplied by the cradle, may be accessed by the less-featured device by modifying the drivers that already exist on the less- featured device (e.g., iPod Touch) to point to the memory addresses to the components on the supplementing cradle. [o o52] In one embodiment, if the cradle is determined to be compatible, the primary device may query a local memory stack for drivers based on the received hardware identifying data of the cradle 512. In one implementation, this may be achieved by providing an application specification to the device which in turn will query for device abilities. The application may determine the cradle's abilities by looking to a specific memory location, for driver and/or component lists. In one example, the cradle may provide such an application in a flash or Web DAV mountable drive, which may be used to copy and install the application. Once the application runs, a cradle type may be selected by the user, and it will modify driver addresses to map to the cradle components accordingly.

[0053] If a driver is available or already installed 515, the primary device may proceed to install the driver 520. In one implementation, the operating system (OS) running on the primary device may be configured to automatically search a drivers database in the local memory and instantiate or install the corresponding driver. For example, if a user operating a PDA docks the PDA into an EDFC cradle, the user may observe the PDA provides a pop-up message showing "Found New Hardware," followed by a message showing "The new hardware has been identified and ready for use," upon installation of the correct driver. In an alternative implementation, the OS may provide an option for a user to manually search for a driver in the local hard drive. For another example, if the primary device is an Apple iTouch, the iTouch may automatically instantiate a driver and corresponding application package to interface with the extended cradle. In one implementation, the instantiation may notify the OS and any reliant library and application of the availability of the extended feature. [O O54] If a search for the driver returns empty result, and the primary device is not network enabled 517, the primary device may abort the connection attempt. For example, in one implementation, if a PDA is not connected to the Internet, is docked into an EDFC with incompatible buses, the PDA may provide a pop-up window on the display showing "Found New Hardware," but then display a message showing "Hardware unusable." In one implementation, if the primary device is network- enabled, the primary device may download the driver from the Internet 518. For example, an application running on the primary device may automatically access an online drivers database (e.g., device drivers database, etc.) and obtain the demanded driver. For another example, a browser running on the primary device may be launched and a user may be directed to a website showing a list of relevant drivers for the cradle. The user may then select, download and install a driver. [0055] In one embodiment, a Linux Kernel may be employed to provide power management, driver stacking, automatic configuration, and dynamic loading of drivers. [0056] In an alternative embodiment, the EDFC may determine the extended feature of the cradle 522 in order to generate an application component. For example, in one implementation, the extended feature of the cradle may include one or more of GPS, camera, video, audio, power supply, biometrics reader, network, phone, human interface components/chipsets, and/or the like. In one implementation, the EDFC may generate an application component under the OS running on the primary device in order to access the extended cradle 525. For example, in one implementation, the primary device may provide an icon of the extended application on the desktop such that the user may instantiate the extended application of the cradle. [0057] In one implementation, upon instantiation of the driver, the OS of the primary device may re-map the memory address of the cradle feature to the driver 521, such that the extended application of the cradle may be included for use. [0058] Figure 5B provides a logic flow illustrating aspects of driver/ application instantiation on a primary device in an alternative embodiment of EDFC operation. In one embodiment, the primary device may receive hardware identification and parameters from the cradle 530, describing contents such as, but not limited to hardware type, interface protocol, and/or the like. The installed driver may then interface with the hardware layer of the primary device and translate the received cradle hardware identifying data to application data and submit to the OS 533. For example, in one implementation, if a GPS receiver is included in the cradle, the driver may report a GPS application requirement to the OS. [O O59] In one implementation, the OS may search its application library based on the received application identification 535. For example, in one implementation, a PDA running a Windows Mobile may search its Windows application library for GPS related applications if a GPS has been identified through attachment of cradle. In one implementation, if the application is available in the library 537, the primary device may retrieve the application package and interface with the installed cradle driver 538. In another implementation, if no application is found, the primary device may determine whether it is connected to the Internet 545. If so, the primary device may obtain and install an application package from the Internet 547. For example, in one implementation, an Apple iTouch may connect via Wi-Fi to an Apple Application Database online and download the required application package. In another implementation, if the primary device is not network enabled, the primary device may provide options for a user to provide an application package 550. For example, in one implementation, a user operating an Apple iTouch, may construct an application program 552 via the Xcode application developer. [0060] In one implementation, the OS running on the primary device may generate an application icon to the OS user interface 555. For example, the OS may generate a GPS button on the "Google map" application when a GPS cradle is attached and successfully installed, as shown in Figure 7.

[0061] Figure 5C shows a diagram illustrating aspects of data flows between layers of the primary device and the extended cradle within one embodiment of EDFC operation. In one embodiment, an extended cradle 565 is physically attached to a primary device 560. The extended cradle 565 may include elements such as a camera, a GPS receiver, a compass, sensors (e.g., temperature, accelerometer, pressure, position, elevation, light intensity, wind speed, data rate, and/or the like), batteries, network and phone facilities, human interfaces (e.g., keyboard, touchpad mouse, etc.), biometrics reader (e.g., fingerprint reader, etc.), extended memory card, and/or the like. Upon installation of the extended cradle, a user 564 operating the primary device 560 may initiate the cradle utility by launching an associated application 570, e.g., to launch a Google map application on an Apple iTouch extended with accurate GPS access. In one implementation, the application program may invoke a routine in 1 the driver 562b installed on the operating system 562 and interfacing the hardware 561.

2 The driver 562b may then issue commands to the hardware 561 to send control

3 instructions, or receive data from the extended cradle 565 via a dock connection. In

4 another implementation, once the primary device receives data from the cradle, the

5 hardware 561 may send the received data back to the driver 562b, and the driver may

6 invoke routines in the original calling program of the relevant application.

7 [0062] In one embodiment, the hardware 561 may exchange data with the

8 extended cradle 565 in a variety of communication standards and protocols, such as

9 USB, FireWire, eSATA, and or the like. For example, in one implementation, data

10 packets may be in formats such as USB, FireWires, eSATA, 30 Pin, Apple connector

11 and/or the like.

12 [0063] FIGURE 6A-B illustrate implementations of EDFC logic flow associated

13 with EDFC/ primary device configuration flow in alternative embodiments of EDFC

14 operation. In an alternative embodiment, a user may install an EDFC interface

15 application on the primary device 600, such as by, downloading the application and/or

16 the drivers to the primary device from the internet, uploading the device drivers from

17 the EDFC, and/or the like. The primary device engages EDFC 605 and the EDFC

18 attempts to establish communications with the primary device 610. The EDFC confirms

19 that communications with the primary device are established 615. If communications

20 are not established, the EDFC may be configured to retry establishing the data link 620.

21 The EDFC may also check whether there have been multiple communication failures

22 618. If there have not been multiple communication failures, the EDFC transitions to

23 re-attempting to establish communications. Otherwise, in some implementations, the EDFC may attempt to upload the EDFC interface application from local memory 619. Once a communication link between devices has been established, the feature set available for use by the primary device is determined 625. A user may select from a listing of available EDFC features displayed on the primary device 630 by an interface application. A user selects and configures the settings for a particular EDFC feature 635 and is presented with an option to configure additional EDFC features 640. If the user decides to configure additional EDFC features 640, such additional EDFC features are identified 645 and displayed 630 to user for configuration 635. If the user is done with feature configuration, the feature settings may be saved locally 650 and/ or saved on the EDFC as a back-up. The user may be provided with an option to modify/updated EDFC feature setting/defaults 665 at any time after the EDFC engaged primary device has been initialized. In one embodiment where cradle component are exposed to existing system preferences, the user may use those preference settings. [0064] FIGURE 6B illustrates an alternative implementation of logic flow associated with sensor data transfer from the EDFC to an engaged primary device associated with EDFC operation. In an alternative implementation, a user may engage a primary device application 651 that requests EDFC sensor data, such as by turning on the primary device, selecting an application icon, and/or the like. The sensor data request is processed 654, which in turn retrieves the requested data from the EDFC sensor(s) and attempts to transfer the data to the primary device 657. If the transfer was not successful (no primary device transfer receipt acknowledgment), the EDFC may check whether multiple communication faults exist 661. If multiple communication faults have not occurred, the EDFC may retry the data communication transfers 664. If 1 multiple communication faults have occurred, the EDFC may display a communications

2 failure message and initiate a system restart 667.

3 [ 0065 ] If the sensor data has been acknowledged by the primary device as having

4 been received 671, the EDFC may periodically continue to transfer/update sensor data

5 681, until an application completion message is received 674. In an implementation, the

6 EDFC (or a particular EDFC module) may transitions to a power conservation state 677

7 awaiting another sensor data request.

8 [0066] Figure 7 shows example screen shots illustrating an extended GPS

9 application within one embodiment of EDFC operation. As shown in Figure 7 in one0 implementation, 700 shows an example screen of an Apple iPod Touch without a GPS1 receiver. As such, when a Google map application is launched, the application may not2 be able to provide accurate location. Upon attaching to an EDFC with a GPS receiver,3 the iPod Touch may automatically instantiate GPS drivers for the extended GPS, and4 engage the GPS device ready for use. A GPS/compass icon 701 may be shown at the tool5 bar of the Google map application page 705, and the Google map application may then6 automatically provide a location and orientation iPod Touch with the enhanced cradle. 7 EDFC Controller 8 [0067] FIGURE 8 illustrates inventive aspects of a EDFC controller 801 in a block9 diagram. In this embodiment, the EDFC controller 801 may serve to aggregate, process,0 store, search, serve, identify, instruct, generate, match, and/or facilitate interactions1 with a computer through device connection technologies, and/or other related data. [o o68] Typically, users, which may be people and/or other systems, may engage information technology systems (e.g., computers) to facilitate information processing. In turn, computers employ processors to process information; such processors 803 may be referred to as central processing units (CPU). One form of processor is referred to as a microprocessor. CPUs use communicative circuits to pass binary encoded signals acting as instructions to enable various operations. These instructions may be operational and/or data instructions containing and/or referencing other instructions and data in various processor accessible and operable areas of memory 829 (e.g., registers, cache memory, random access memory, etc.). Such communicative instructions may be stored and/or transmitted in batches (e.g., batches of instructions) as programs and/or data components to facilitate desired operations. These stored instruction codes, e.g., programs, may engage the CPU circuit components and other motherboard and/or system components to perform desired operations. One type of program is a computer operating system, which, may be executed by CPU on a computer; the operating system enables and facilitates users to access and operate computer information technology and resources. Some resources that may be employed in information technology systems include: input and output mechanisms through which data may pass into and out of a computer; memory storage into which data may be saved; and processors by which information may be processed. These information technology systems may be used to collect data for later retrieval, analysis, and manipulation, which may be facilitated through a database program. These information technology systems provide interfaces that allow users to access and operate various system components. [o o 69] In one embodiment, the EDFC controller 801 may be connected to and/or communicate with entities such as, but not limited to: one or more users from user input devices 811; peripheral devices 812; an optional cryptographic processor device 828; and/or a communications network 813.

[0070] Networks are commonly thought to comprise the interconnection and interoperation of clients, servers, and intermediary nodes in a graph topology. It should be noted that the term "server" as used throughout this application refers generally to a computer, other device, program, or combination thereof that processes and responds to the requests of remote users across a communications network. Servers serve their information to requesting "clients." The term "client" as used herein refers generally to a computer, program, other device, user and/or combination thereof that is capable of processing and making requests and obtaining and processing any responses from servers across a communications network. A computer, other device, program, or combination thereof that facilitates, processes information and requests, and/or furthers the passage of information from a source user to a destination user is commonly referred to as a "node." Networks are generally thought to facilitate the transfer of information from source points to destinations. A node specifically tasked with furthering the passage of information from a source to a destination is commonly called a "router." There are many forms of networks such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc. For example, the Internet is generally accepted as being an interconnection of a multitude of networks whereby remote clients and servers may access and interoperate with one another. [0071] The EDFC controller 801 may be based on computer systems that may comprise, but are not limited to, components such as: a computer systemization 802 connected to memory 829.

Computer Systemization [o θ72] A computer systemization 802 may comprise a clock 830, central processing unit ("CPU(s)" and/or "processor(s)" (these terms are used interchangeable throughout the disclosure unless noted to the contrary)) 803, a memory 829 (e.g., a read only memory (ROM) 806, a random access memory (RAM) 805, etc.), and/or an interface bus 807, and most frequently, although not necessarily, are all interconnected and/or communicating through a system bus 804 on one or more (mother )board(s) 802 having conductive and/or otherwise transportive circuit pathways through which instructions (e.g., binary encoded signals) may travel to effect communications, operations, storage, etc. Optionally, the computer systemization may be connected to an internal power source 886. Optionally, a cryptographic processor 826 may be connected to the system bus. The system clock typically has a crystal oscillator and generates a base signal through the computer systemization's circuit pathways. The clock is typically coupled to the system bus and various clock multipliers that will increase or decrease the base operating frequency for other components interconnected in the computer systemization. The clock and various components in a computer systemization drive signals embodying information throughout the system. Such transmission and reception of instructions embodying information throughout a computer systemization may be commonly referred to as communications. These communicative instructions may further be transmitted, received, and the cause of return and/or reply communications beyond the instant computer systemization to: communications networks, input devices, other computer systemizations, peripheral devices, and/or the like. Of course, any of the above components may be connected directly to one another, connected to the CPU, and/or organized in numerous variations employed as exemplified by various computer systems.

[0073] The CPU comprises at least one high-speed data processor adequate to execute program components for executing user and/or system-generated requests. Often, the processors themselves will incorporate various specialized processing units, such as, but not limited to: integrated system (bus) controllers, memory management control units, floating point units, and even specialized processing sub-units like graphics processing units, digital signal processing units, and/or the like. Additionally, processors may include internal fast access addressable memory, and be capable of mapping and addressing memory 529 beyond the processor itself; internal memory may include, but is not limited to: fast registers, various levels of cache memory (e.g., level 1, 2, 3, etc.), RAM, etc. The processor may access this memory through the use of a memory address space that is accessible via instruction address, which the processor can construct and decode allowing it to access a circuit path to a specific memory address space having a memory state. The CPU may be a microprocessor such as: AMD's Athlon, Duron and/or Opteron; ARM's application, embedded and secure processors; IBM and/or Motorola's DragonBall and PowerPC; IBM's and Sony's Cell processor; Intel's Celeron, Core (2) Duo, Itanium, Pentium, Xeon, and/or XScale; and/or the like processor(s). The CPU interacts with memory through instruction passing through conductive and/or transportive conduits (e.g., (printed) electronic and/or optic circuits) to execute stored instructions (i.e., program code) according to conventional data processing techniques. Such instruction passing facilitates communication within the EDFC controller and beyond through various interfaces. Should processing requirements dictate a greater amount speed and/or capacity, distributed processors (e.g., Distributed EDFC), mainframe, multi-core, parallel, and/ or super-computer architectures may similarly be employed.Alternatively, should deployment requirements dictate greater portability, smaller Personal Digital Assistants (PDAs) may be employed. [0074] Depending on the particular implementation, features of the EDFC may be achieved by implementing a microcontroller such as CAST'S R8051XC2 microcontroller; Intel's MCS 51 (i.e., 8051 microcontroller); and/or the like. Also, to implement certain features of the EDFC, some feature implementations may rely on embedded components, such as: Application-Specific Integrated Circuit ("ASIC"), Digital Signal Processing ("DSP"), Field Programmable Gate Array ("FPGA"), and/or the like embedded technology. For example, any of the EDFC component collection (distributed or otherwise) and/or features may be implemented via the microprocessor and/or via embedded components; e.g., via ASIC, coprocessor, DSP, FPGA, and/or the like. Alternately, some implementations of the EDFC may be implemented with embedded components that are configured and used to achieve a variety of features or signal processing.

[0075] Depending on the particular implementation, the embedded components may include software solutions, hardware solutions, and/or some combination of both hardware/software solutions. For example, EDFC features discussed herein may be achieved through implementing FPGAs, which are a semiconductor devices containing programmable logic components called "logic blocks", and programmable interconnects, such as the high performance FPGA Virtex series and/ or the low cost Spartan series manufactured by Xilinx. Logic blocks and interconnects can be programmed by the customer or designer, after the FPGA is manufactured, to implement any of the EDFC features. A hierarchy of programmable interconnects allow logic blocks to be interconnected as needed by the EDFC system designer/administrator, somewhat like a one-chip programmable breadboard. An FPGAs logic blocks can be programmed to perform the function of basic logic gates such as AND, and XOR, or more complex combinational functions such as decoders or simple mathematical functions. In most FPGAs, the logic blocks also include memory elements, which may be simple flip-flops or more complete blocks of memory. In some circumstances, the EDFC may be developed on regular FPGAs and then migrated into a fixed version that more resembles ASIC implementations. Alternate or coordinating implementations may migrate EDFC controller features to a final ASIC instead of or in addition to FPGAs. Depending on the implementation all of the aforementioned embedded components and microprocessors may be considered the "CPU" and/or "processor" for the EDFC.

Power Source [0076] The power source 886 may be of any standard form for powering small electronic circuit board devices such as the following power cells: alkaline, lithium hydride, lithium ion, lithium polymer, nickel cadmium, solar cells, and/or the like. Other types of AC or DC power sources may be used as well. In the case of solar cells, in one embodiment, the case provides an aperture through which the solar cell may capture photonic energy. The power cell 886 is connected to at least one of the interconnected subsequent components of the EDFC thereby providing an electric current to all subsequent components. In one example, the power source 886 is connected to the system bus component 804. In an alternative embodiment, an outside power source 886 is provided through a connection across the I/O 808 interface. For example, a USB and/or IEEE 1394 connection carries both data and power across the connection and is therefore a suitable source of power.

Interface Adapters [0077] Interface bus(ses) 807 may accept, connect, and/or communicate to a number of interface adapters, conventionally although not necessarily in the form of adapter cards, such as but not limited to: input output interfaces (I/O) 808, storage interfaces 809, network interfaces 810, and/or the like. Optionally, cryptographic processor interfaces 827 similarly may be connected to the interface bus. The interface bus provides for the communications of interface adapters with one another as well as with other components of the computer systemization. Interface adapters are adapted for a compatible interface bus. Interface adapters conventionally connect to the interface bus via a slot architecture. Conventional slot architectures may be employed, such as, but not limited to: Accelerated Graphics Port (AGP), Card Bus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and/or the like.

[0078] Storage interfaces 809 may accept, communicate, and/or connect to a number of storage devices such as, but not limited to: storage devices 814, removable disc devices, and/or the like. Storage interfaces may employ connection protocols such as, but not limited to: (Ultra) (Serial) Advanced Technology Attachment (Packet Interface) ((Ultra) (Serial) ATA(PI)), (Enhanced) Integrated Drive Electronics ((E)IDE), Institute of Electrical and Electronics Engineers (IEEE) 1394, fiber channel, Small Computer Systems Interface (SCSI), Universal Serial Bus (USB), and/or the like. [0079] Network interfaces 810 may accept, communicate, and/or connect to a communications network 813. Through a communications network 813, the EDFC controller is accessible through remote clients 833b (e.g., computers with web browsers) by users 833a. Network interfaces may employ connection protocols such as, but not limited to: direct connect, Ethernet (thick, thin, twisted pair 10/100/1000 Base T, and/or the like), Token Ring, wireless connection such as IEEE 8θ2.na-x, and/or the like. Should processing requirements dictate a greater amount speed and/or capacity, distributed network controllers (e.g., Distributed EDFC), architectures may similarly be employed to pool, load balance, and/or otherwise increase the communicative bandwidth required by the EDFC controller. A communications network may be any one and/or the combination of the following: a direct interconnection; the Internet; a Local Area Network (LAN); a Metropolitan Area Network (MAN); an Operating Missions as Nodes on the Internet (OMNI); a secured custom connection; a Wide Area Network (WAN); a wireless network (e.g., employing protocols such as, but not limited to a Wireless Application Protocol (WAP), I-mode, and/or the like); and/or the like. A network interface may be regarded as a specialized form of an input output interface. Further, multiple network interfaces 810 may be used to engage with various communications network types 813. For example, multiple network interfaces may be employed to allow for the communication over broadcast, multicast, and/ or unicast networks. [0080] Input Output interfaces (I/O) 808 may accept, communicate, and/or connect to user input devices 8n, peripheral devices 812, cryptographic processor devices 828, and/or the like. I/O may employ connection protocols such as, but not limited to: audio: analog, digital, monaural, RCA, stereo, and/or the like; data: Apple Desktop Bus (ADB), IEEE I394a-b, serial, universal serial bus (USB); infrared; joystick; keyboard; midi; optical; PC AT; PS/2; parallel; radio; video interface: Apple Desktop Connector (ADC), BNC, coaxial, component, composite, digital, Digital Visual Interface (DVI), high-definition multimedia interface (HDMI), RCA, RF antennae, S-Video, VGA, and/or the like; wireless: 802.na/b/g/n/x, Bluetooth, code division multiple access (CDMA), global system for mobile communications (GSM), WiMax, etc.; and/or the like. One typical output device may include a video display, which typically comprises a Cathode Ray Tube (CRT) or Liquid Crystal Display (LCD) based monitor with an interface (e.g., DVI circuitry and cable) that accepts signals from a video interface, may be used. The video interface composites information generated by a computer systemization and generates video signals based on the composited information in a video memory frame. Another output device is a television set, which accepts signals from a video interface. Typically, the video interface provides the composited video information through a video connection interface that accepts a video display interface (e.g., an RCA composite video connector accepting an RCA composite video cable; a DVI connector accepting a DVI display cable, etc.). [o o 8 i] User input devices 811 may be card readers, dongles, finger print readers, gloves, graphics tablets, joysticks, keyboards, mouse (mice), remote controls, retina readers, trackballs, trackpads, and/or the like.

[0082] Peripheral devices 812 may be connected and/or communicate to I/O and/or other facilities of the like such as network interfaces, storage interfaces, and/ or the like. Peripheral devices may be audio devices, cameras, dongles (e.g., for copy protection, ensuring secure transactions with a digital signature, and/or the like), external processors (for added functionality), goggles, microphones, monitors, network interfaces, printers, scanners, storage devices, video devices, video sources, visors, and/or the like. [ 0083 ] It should be noted that although user input devices and peripheral devices may be employed, the EDFC controller may be embodied as an embedded, dedicated, and/or monitor-less (i.e., headless) device, wherein access would be provided over a network interface connection.

[0084] Cryptographic units such as, but not limited to, microcontrollers, processors 826, interfaces 827, and/or devices 828 may be attached, and/or communicate with the EDFC controller. A MC68HC16 microcontroller, manufactured by Motorola Inc., may be used for and/or within cryptographic units. The MC68HC16 microcontroller utilizes a 16-bit multiply-and-accumulate instruction in the 16 MHz configuration and requires less than one second to perform a 512-bit RSA private key operation. Cryptographic units support the authentication of communications from interacting agents, as well as allowing for anonymous transactions. Cryptographic units may also be configured as part of CPU. Equivalent microcontrollers and/or processors may also be used. Other commercially available specialized cryptographic processors include: the Broadcom's CryptoNetX and other Security Processors; nCipher's nShield, SafeNet's Luna PCI (e.g., 7100) series; Semaphore Communications' 40 MHz Roadrunner 184; Sun's Cryptographic Accelerators (e.g., Accelerator 6000 PCIe Board, Accelerator 500 Daughtercard); Via Nano Processor (e.g., L2100, L2200, U2400) line, which is capable of performing 500+ MB/s of cryptographic instructions; VLSI Technology's 33 MHz 6868; and/or the like.

Memory [0085] Generally, any mechanization and/or embodiment allowing a processor to affect the storage and/or retrieval of information is regarded as memory 829. However, memory is a fungible technology and resource, thus, any number of memory embodiments may be employed in lieu of or in concert with one another. It is to be understood that the EDFC controller and/or a computer systemization may employ various forms of memory 829. For example, a computer systemization may be configured wherein the functionality of on-chip CPU memory (e.g., registers), RAM, ROM, and any other storage devices are provided by a paper punch tape or paper punch card mechanism; of course such an embodiment would result in an extremely slow rate of operation. In a typical configuration, memory 829 will include ROM 806, RAM 805, and a storage device 814. A storage device 814 may be any conventional computer system storage. Storage devices may include a drum; a (fixed and/or removable) magnetic disk drive; a magneto-optical drive; an optical drive (i.e., Blueray, CD ROM/RAM/Recordable (R)/ReWritable (RW), DVD R/RW, HD DVD R/RW etc.); an array of devices (e.g., Redundant Array of Independent Disks (RAID)); solid state 1 memory devices (USB memory, solid state drives (SSD), etc.); other processor-readable

2 storage mediums; and/or other devices of the like. Thus, a computer systemization

3 generally requires and makes use of memory.

4 Component Collection

5 [0086] The memory 829 may contain a collection of program and/or database

6 components and/or data such as, but not limited to: operating system component(s) 815

7 (operating system); information server component(s) 816 (information server); user

8 interface component(s) 817 (user interface); Web browser component(s) 818 (Web

9 browser); database(s) 819; mail server component(s) 821; mail client component(s)

10 822; cryptographic server component(s) 820 (cryptographic server); the EDFC

11 component(s) 835; and/or the like (i.e., collectively a component collection). These

12 components may be stored and accessed from the storage devices and/or from storage

13 devices accessible through an interface bus. Although non-conventional program

14 components such as those in the component collection, typically, are stored in a local

15 storage device 814, they may also be loaded and/or stored in memory such as:

16 peripheral devices, RAM, remote storage facilities through a communications network,

17 ROM, various forms of memory, and/or the like.

is Operating System

19 [0087] The operating system component 815 is an executable program

20 component facilitating the operation of the EDFC controller. Typically, the operating

21 system facilitates access of I/O, network interfaces, peripheral devices, storage devices,

22 and/or the like. The operating system may be a highly fault tolerant, scalable, and

23 secure system such as: Apple Macintosh OS X (Server); AT&T Plan 9; Be OS; Unix and Unix-like system distributions (such as AT&T's UNIX; Berkley Software Distribution (BSD) variations such as FreeBSD, NetBSD, OpenBSD, and/or the like; Linux distributions such as Red Hat, Ubuntu, and/ or the like); and/or the like operating systems. However, more limited and/or less secure operating systems also may be employed such as Apple Macintosh OS, IBM OS/2, Microsoft DOS, Microsoft Windows 2OOO/2OO3/3.i/95/98/CE/Millenium/NT/Vista/XP (Server), Palm OS, and/or the like. An operating system may communicate to and/or with other components in a component collection, including itself, and/or the like. Most frequently, the operating system communicates with other program components, user interfaces, and/or the like. For example, the operating system may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. The operating system, once executed by the CPU, may enable the interaction with communications networks, data, I/O, peripheral devices, program components, memory, user input devices, and/or the like. The operating system may provide communications protocols that allow the EDFC controller to communicate with other entities through a communications network 813. Various communication protocols may be used by the EDFC controller as a subcarrier transport mechanism for interaction, such as, but not limited to: multicast, TCP/IP, UDP, unicast, and/or the like.

Information Server [0088] An information server component 816 is a stored program component that is executed by a CPU. The information server may be a conventional Internet information server such as, but not limited to Apache Software Foundation's Apache, Microsoft's Internet Information Server, and/or the like. The information server may allow for the execution of program components through facilities such as Active Server Page (ASP), ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, Common Gateway Interface (CGI) scripts, dynamic (D) hypertext markup language (HTML), FLASH, Java, JavaScript, Practical Extraction Report Language (PERL), Hypertext Pre-Processor (PHP), pipes, Python, wireless application protocol (WAP), WebObjects, and/or the like. The information server may support secure communications protocols such as, but not limited to, File Transfer Protocol (FTP); HyperText Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Socket Layer (SSL), messaging protocols (e.g., America Online (AOL) Instant Messenger (AIM), Application Exchange (APEX), ICQ, Internet Relay Chat (IRC), Microsoft Network (MSN) Messenger Service, Presence and Instant Messaging Protocol (PRIM), Internet Engineering Task Force's (IETF's) Session Initiation Protocol (SIP), SIP for Instant Messaging and Presence Leveraging Extensions (SIMPLE), open XML-based Extensible Messaging and Presence Protocol (XMPP) (i.e., Jabber or Open Mobile Alliance's (OMA's) Instant Messaging and Presence Service (IMPS)), Yahoo! Instant Messenger Service, and/or the like. The information server provides results in the form of Web pages to Web browsers, and allows for the manipulated generation of the Web pages through interaction with other program components. After a Domain Name System (DNS) resolution portion of an HTTP request is resolved to a particular information server, the information server resolves requests for information at specified locations on the EDFC controller based on the remainder of the HTTP request. For example, a request such as http://123.124.125.126/mylnformation.html might have the IP portion of the request "123.124.125.126" resolved by a DNS server to an information server at that IP address; that information server might in turn further parse the http request for the "/mylnformation.html" portion of the request and resolve it to a location in memory containing the information "mylnformation.html." Additionally, other information serving protocols may be employed across various ports, e.g., FTP communications across port 21, and/or the like. An information server may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the information server communicates with the EDFC database 819, operating systems, other program components, user interfaces, Web browsers, and/or the like.

[0089] Access to the EDFC database may be achieved through a number of database bridge mechanisms such as through scripting languages as enumerated below (e.g., CGI) and through inter-application communication channels as enumerated below (e.g., CORBA, WebObjects, etc.). Any data requests through a Web browser are parsed through the bridge mechanism into appropriate grammars as required by the EDFC. In one embodiment, the information server would provide a Web form accessible by a Web browser. Entries made into supplied fields in the Web form are tagged as having been entered into the particular fields, and parsed as such. The entered terms are then passed along with the field tags, which act to instruct the parser to generate queries directed to appropriate tables and/or fields. In one embodiment, the parser may generate queries in standard SQL by instantiating a search string with the proper join/select commands based on the tagged text entries, wherein the resulting command is provided over the bridge mechanism to the EDFC as a query. Upon generating query results from the query, the results are passed over the bridge mechanism, and may be parsed for formatting and generation of a new results Web page by the bridge mechanism. Such a 1 new results Web page is then provided to the information server, which may supply it to

2 the requesting Web browser.

3 [0090] Also, an information server may contain, communicate, generate, obtain,

4 and/or provide program component, system, user, and/or data communications,

5 requests, and/or responses.

6 User Interface

7 [0091] The function of computer interfaces in some respects is similar to

8 automobile operation interfaces. Automobile operation interface elements such as

9 steering wheels, gearshifts, and speedometers facilitate the access, operation, and

10 display of automobile resources, functionality, and status. Computer interaction

11 interface elements such as check boxes, cursors, menus, scrollers, and windows

12 (collectively and commonly referred to as widgets) similarly facilitate the access,

13 operation, and display of data and computer hardware and operating system resources,

14 functionality, and status. Operation interfaces are commonly called user interfaces.

15 Graphical user interfaces (GUIs) such as the Apple Macintosh Operating System's Aqua,

16 IBM's OS/2, Microsoft's Windows

17 2000/2003/3. i/95/98/CE/Millenium/NT/XP/Vista/7 (i.e., Aero), Unix's X-Windows

18 (e.g., which may include additional Unix graphic interface libraries and layers such as K

19 Desktop Environment (KDE), mythTV and GNU Network Object Model Environment

20 (GNOME)), web interface libraries (e.g., ActiveX, AJAX, (D)HTML, FLASH, Java,

21 JavaScript, etc. interface libraries such as, but not limited to, Dojo, jQuery(UI),

22 MooTools, Prototype, script.aculo.us, SWFObject, Yahoo! User Interface, any of which may be used and) provide a baseline and means of accessing and displaying information graphically to users. [0092] A user interface component 817 is a stored program component that is executed by a CPU. The user interface may be a conventional graphic user interface as provided by, with, and/or atop operating systems and/or operating environments such as already discussed. The user interface may allow for the display, execution, interaction, manipulation, and/or operation of program components and/ or system facilities through textual and/or graphical facilities. The user interface provides a facility through which users may affect, interact, and/or operate a computer system. A user interface may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the user interface communicates with operating systems, other program components, and/or the like. The user interface may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/ or responses.

Web Browser [0093] A Web browser component 818 is a stored program component that is executed by a CPU. The Web browser may be a conventional hypertext viewing application such as Microsoft Internet Explorer or Netscape Navigator. Secure Web browsing may be supplied with I28bit (or greater) encryption by way of HTTPS, SSL, and/or the like. Web browsers allowing for the execution of program components through facilities such as ActiveX, AJAX, (D)HTML, FLASH, Java, JavaScript, web browser plug-in APIs (e.g., FireFox, Safari Plug-in, and/or the like APIs), and/or the like. Web browsers and like information access tools may be integrated into PDAs, cellular telephones, and/or other mobile devices. A Web browser may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the Web browser communicates with information servers, operating systems, integrated program components (e.g., plug-ins), and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses. Of course, in place of a Web browser and information server, a combined application may be developed to perform similar functions of both. The combined application would similarly affect the obtaining and the provision of information to users, user agents, and/or the like from the EDFC enabled nodes. The combined application may be nugatory on systems employing standard Web browsers.

Mail Server [0094] A mail server component 821 is a stored program component that is executed by a CPU 803. The mail server may be a conventional Internet mail server such as, but not limited to sendmail, Microsoft Exchange, and/ or the like. The mail server may allow for the execution of program components through facilities such as ASP, ActiveX, (ANSI) (Objective-) C (++), C# and/or .NET, CGI scripts, Java, JavaScript, PERL, PHP, pipes, Python, WebObjects, and/or the like. The mail server may support communications protocols such as, but not limited to: Internet message access protocol (IMAP), Messaging Application Programming Interface (MAPI)/Microsoft Exchange, post office protocol (POP3), simple mail transfer protocol (SMTP), and/or the like. The mail server can route, forward, and process incoming and outgoing mail messages that have been sent, relayed and/or otherwise traversing through and/or to the EDFC.

[0095] Access to the EDFC mail may be achieved through a number of APIs offered by the individual Web server components and/or the operating system.

[0096] Also, a mail server may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses.

Mail Client [0097] A mail client component 822 is a stored program component that is executed by a CPU 803. The mail client may be a conventional mail viewing application such as Apple Mail, Microsoft Entourage, Microsoft Outlook, Microsoft Outlook Express, Mozilla, Thunderbird, and/or the like. Mail clients may support a number of transfer protocols, such as: IMAP, Microsoft Exchange, POP3, SMTP, and/or the like. A mail client may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the mail client communicates with mail servers, operating systems, other mail clients, and/or the like; e.g., it may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, information, and/or responses. Generally, the mail client provides a facility to compose and transmit electronic mail messages. Cryptographic Server [0098] A cryptographic server component 820 is a stored program component that is executed by a CPU 803, cryptographic processor 826, cryptographic processor interface 827, cryptographic processor device 828, and/or the like. Cryptographic processor interfaces will allow for expedition of encryption and/or decryption requests by the cryptographic component; however, the cryptographic component, alternatively, may run on a conventional CPU. The cryptographic component allows for the encryption and/or decryption of provided data. The cryptographic component allows for both symmetric and asymmetric (e.g., Pretty Good Protection (PGP)) encryption and/or decryption. The cryptographic component may employ cryptographic techniques such as, but not limited to: digital certificates (e.g., X.509 authentication framework), digital signatures, dual signatures, enveloping, password access protection, public key management, and/or the like. The cryptographic component will facilitate numerous (encryption and/or decryption) security protocols such as, but not limited to: checksum, Data Encryption Standard (DES), Elliptical Curve Encryption (ECC), International Data Encryption Algorithm (IDEA), Message Digest 5 (MD5, which is a one way hash function), passwords, Rivest Cipher (RC5), Rijndael, RSA (which is an Internet encryption and authentication system that uses an algorithm developed in 1977 by Ron Rivest, Adi Shamir, and Leonard Adleman), Secure Hash Algorithm (SHA), Secure Socket Layer (SSL), Secure Hypertext Transfer Protocol (HTTPS), and/or the like. Employing such encryption security protocols, the EDFC may encrypt all incoming and/or outgoing communications and may serve as node within a virtual private network (VPN) with a wider communications network. The cryptographic component facilitates the process of "security authorization" whereby access to a resource is inhibited by a security protocol wherein the cryptographic component effects authorized access to the secured resource. In addition, the cryptographic component may provide unique identifiers of content, e.g., employing and MD5 hash to obtain a unique signature for an digital audio file. A cryptographic component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. The cryptographic component supports encryption schemes allowing for the secure transmission of information across a communications network to enable the EDFC component to engage in secure transactions if so desired. The cryptographic component facilitates the secure accessing of resources on the EDFC and facilitates the access of secured resources on remote systems; i.e., it may act as a client and/or server of secured resources. Most frequently, the cryptographic component communicates with information servers, operating systems, other program components, and/or the like. The cryptographic component may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.

The EDFC Database [0099] The EDFC database component 819 may be embodied in a database and its stored data. The database is a stored program component, which is executed by the CPU; the stored program component portion configuring the CPU to process the stored data. The database may be a conventional, fault tolerant, relational, scalable, secure database such as Oracle or Sybase. Relational databases are an extension of a flat file. Relational databases consist of a series of related tables. The tables are interconnected via a key field. Use of the key field allows the combination of the tables by indexing against the key field; i.e., the key fields act as dimensional pivot points for combining information from various tables. Relationships generally identify links maintained between tables by matching primary keys. Primary keys represent fields that uniquely identify the rows of a table in a relational database. More precisely, they uniquely identify rows of a table on the "one" side of a one-to-many relationship. [o o io o] Alternatively, the EDFC database may be implemented using various standard data-structures, such as an array, hash, (linked) list, struct, structured text file (e.g., XML), table, and/or the like. Such data-structures may be stored in memory and/or in (structured) files. In another alternative, an object-oriented database may be used, such as Frontier, ObjectStore, Poet, Zope, and/or the like. Object databases can include a number of object collections that are grouped and/or linked together by common attributes; they may be related to other object collections by some common attributes. Object-oriented databases perform similarly to relational databases with the exception that objects are not just pieces of data but may have other types of functionality encapsulated within a given object. If the EDFC database is implemented as a data-structure, the use of the EDFC database 819 may be integrated into another component such as the EDFC component 835. Also, the database may be implemented as a mix of data structures, objects, and relational structures. Databases may be consolidated and/or distributed in countless variations through standard data processing techniques. Portions of databases, e.g., tables, may be exported and/or imported and thus decentralized and/or integrated. [00101] In one embodiment, the database component 819 includes several tables 8i9a-e. In one embodiment, the database component 819 includes several tables 8i9a-d. A Users table 819a may include fields such as, but not limited to: user_ID, user_name, user_password, contact_info, hardware_ID, payload_history, user_evaluation and/or the like. A Hardware table 819b may include fields such as, but not limited to: hardware_ID, Driver_ID, hardware_type, hardware_name, data_formatting_requirements, protocols, addressing_info, usage_history, hardware_requirements, user_ID, and/or the like. A protocol table 819c may include fields such as, but not limited to protocol_ID, Driver_ID, user_ID, protocol_version, protocol_request, protocol_compatability, and/or the like. An Drivers table 8i9d may include fileds such as, but not limited to: Driver_ID, Hardware_ID, protocol_ID, OS_type, protocol_ID, user_type, Driver_type, Driver_version, policy_ID, Driver_setting, Driver_interface, Driver_authenti cation, Driver_signature, and/or the like. An Application table 8i9e may include fileds such as, but not limited to: app_ID, protocol_ID, Driver_ID, user_type, app_type, app_version, policy_ID, app_setting, app_interface, app_authentication, and/ or the like.

[00102] In one embodiment, the EDFC database may interact with other database systems. For example, employing a distributed database system, queries and data access by search EDFC component may treat the combination of the EDFC database, an integrated data security layer database as a single database entity. [00103] In one embodiment, user programs may contain various user interface primitives, which may serve to update the EDFC. Also, various accounts may require custom database tables depending upon the environments and the types of clients the EDFC may need to serve. It should be noted that any unique fields may be designated as a key field throughout. In an alternative embodiment, these tables have been decentralized into their own databases and their respective database controllers (i.e., individual database controllers for each of the above tables). Employing standard data processing techniques, one may further distribute the databases over several computer systemizations and/or storage devices. Similarly, configurations of the decentralized database controllers may be varied by consolidating and/or distributing the various database components 8i9a-e. The EDFC may be configured to keep track of various settings, inputs, and parameters via database controllers. [00104] The EDFC database may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the EDFC database communicates with the EDFC component, other program components, and/or the like. The database may contain, retain, and provide information regarding other nodes and data.

The EDFCs [00105] The EDFC component 835 is a stored program component that is executed by a CPU. In one embodiment, the EDFC component incorporates any and/or all combinations of the aspects of the EDFC that was discussed in the previous figures. As such, the EDFC affects accessing, obtaining and the provision of information, services, transactions, and/or the like across various communications networks.

[00106] The EDFC component enables the installation, engagement, and/or the like and use of the EDFC.

[00107] The EDFC component enabling access of information between nodes may be developed by employing standard development tools and languages such as, but not limited to: Apache components, Assembly, ActiveX, binary executables, (ANSI) (Objective-) C (++), C# and/or .NET, database adapters, CGI scripts, Java, JavaScript, mapping tools, procedural and object oriented development tools, PERL, PHP, Python, shell scripts, SQL commands, web application server extensions, web development environments and libraries (e.g., Microsoft's ActiveX; Adobe AIR, FLEX & FLASH; AJAX; (D)HTML; Dojo, Java; JavaScript; jQuery(UI); MooTools; Prototype; script.aculo.us; Simple Object Access Protocol (SOAP); SWFObject; Yahoo! User Interface; and/or the like), WebObjects, and/or the like. In one embodiment, the EDFC server employs a cryptographic server to encrypt and decrypt communications. The EDFC component may communicate to and/or with other components in a component collection, including itself, and/or facilities of the like. Most frequently, the EDFC component communicates with the EDFC database, operating systems, other program components, and/or the like. The EDFC may contain, communicate, generate, obtain, and/or provide program component, system, user, and/or data communications, requests, and/or responses.

Distributed EDFCs [00108] The structure and/or operation of any of the EDFC node controller components may be combined, consolidated, and/or distributed in any number of ways to facilitate development and/or deployment. Similarly, the component collection may be combined in any number of ways to facilitate deployment and/or development. To accomplish this, one may integrate the components into a common code base or in a facility that can dynamically load the components on demand in an integrated fashion. [00109] The component collection may be consolidated and/or distributed in countless variations through standard data processing and/or development techniques. Multiple instances of any one of the program components in the program component collection may be instantiated on a single node, and/or across numerous nodes to improve performance through load-balancing and/or data-processing techniques. Furthermore, single instances may also be distributed across multiple controllers and/or storage devices; e.g., databases. All program component instances and controllers working in concert may do so through standard data processing communication techniques.

[00110] The configuration of the EDFC controller will depend on the context of system deployment. Factors such as, but not limited to, the budget, capacity, location, and/or use of the underlying hardware resources may affect deployment requirements and configuration. Regardless of if the configuration results in more consolidated and/or integrated program components, results in a more distributed series of program components, and/or results in some combination between a consolidated and distributed configuration, data may be communicated, obtained, and/or provided. Instances of components consolidated into a common code base from the program component collection may communicate, obtain, and/or provide data. This may be accomplished through intra-application data processing communication techniques such as, but not limited to: data referencing (e.g., pointers), internal messaging, object instance variable communication, shared memory space, variable passing, and/or the like. i [o o iii] If component collection components are discrete, separate, and/or

2 external to one another, then communicating, obtaining, and/or providing data with

3 and/or to other component components may be accomplished through inter-application

4 data processing communication techniques such as, but not limited to: Application

5 Program Interfaces (API) information passage; (distributed) Component Object Model

6 ((D)COM), (Distributed) Object Linking and Embedding ((D)OLE), and/or the like),

7 Common Object Request Broker Architecture (CORBA), local and remote application

8 program interfaces Jini, Remote Method Invocation (RMI), SOAP, process pipes, shared

9 files, and/or the like. Messages sent between discrete component components for inter-0 application communication or within memory spaces of a singular component for intra-1 application communication may be facilitated through the creation and parsing of a2 grammar. A grammar may be developed by using standard development tools such as3 lex, yacc, XML, and/or the like, which allow for grammar generation and parsing4 functionality, which in turn may form the basis of communication messages within ands between components. For example, a grammar may be arranged to recognize the tokens6 of an HTTP post command, e.g.: 7 w3c -post http : / / . . . Valuel 8 9 [00112] where Valuel is discerned as being a parameter because "http://" is part of0 the grammar syntax, and what follows is considered part of the post value. Similarly,1 with such a grammar, a variable "Valuel" may be inserted into an "http://" post2 command and then sent. The grammar syntax itself may be presented as structured data3 that is interpreted and/or other wise used to generate the parsing mechanism (e.g., a4 syntax description text file as processed by lex, yacc, etc.). Also, once the parsing mechanism is generated and/or instantiated, it itself may process and/or parse structured data such as, but not limited to: character (e.g., tab) delineated text, HTML, structured text streams, XML, and/or the like structured data. In another embodiment, inter-application data processing protocols themselves may have integrated and/or readily available parsers (e.g., the SOAP parser) that may be employed to parse communications data. Further, the parsing grammar may be used beyond message parsing, but may also be used to parse: databases, data collections, data stores, structured data, and/ or the like. Again, the desired configuration will depend upon the context, environment, and requirements of system deployment. [ 00113 ] [ 00114 ] [00115] The entirety of this application (including the Cover Page, Title, Headings, Field, Background, Summary, Brief Description of the Drawings, Detailed Description, Claims, Abstract, Figures, and otherwise) shows by way of illustration various embodiments in which the claimed inventions may be practiced. The advantages and features of the application are of a representative sample of embodiments only, and are not exhaustive and/or exclusive. They are presented only to assist in understanding and teach the claimed principles. It should be understood that they are not representative of all claimed inventions. As such, certain aspects of the disclosure have not been discussed herein. That alternate embodiments may not have been presented for a specific portion of the invention or that further undescribed alternate embodiments may be available for a portion is not to be considered a disclaimer of those alternate embodiments. It will be appreciated that many of those undescribed embodiments incorporate the same principles of the invention and others are equivalent. Thus, it is to be understood that other embodiments may be utilized and functional, logical, organizational, structural and/or topological modifications may be made without departing from the scope and/or spirit of the disclosure. As such, all examples and/or embodiments are deemed to be non-limiting throughout this disclosure. Also, no inference should be drawn regarding those embodiments discussed herein relative to those not discussed herein other than it is as such for purposes of reducing space and repetition. For instance, it is to be understood that the logical and/or topological structure of any combination of any program components (a component collection), other components and/or any present feature sets as described in the figures and/or throughout are not limited to a fixed operating order and/ or arrangement, but rather, any disclosed order is exemplary and all equivalents, regardless of order, are contemplated by the disclosure. Furthermore, it is to be understood that such features are not limited to serial execution, but rather, any number of threads, processes, services, servers, and/or the like that may execute asynchronously, concurrently, in parallel, simultaneously, synchronously, and/or the like are contemplated by the disclosure. As such, some of these features may be mutually contradictory, in that they cannot be simultaneously present in a single embodiment. Similarly, some features are applicable to one aspect of the invention, and inapplicable to others. In addition, the disclosure includes other inventions not presently claimed. Applicant reserves all rights in those presently unclaimed inventions including the right to claim such inventions, file additional applications, continuations, continuations in part, divisions, and/or the like thereof. As such, it should be understood that advantages, embodiments, examples, functional, features, logical, organizational, structural, topological, and/or other aspects of the disclosure are not to be considered limitations on the disclosure as defined by the claims or limitations on equivalents to the claims.

Claims

What is claimed is: l. A mobile device feature extension apparatus, comprising: a sheath receptacle to interface with a primary mobile device; an electronic data communication port affixed to the sheath receptacle to establish a communication connection with the primary mobile device; and one or more components providing extended features to the primary mobile device wherein the components are the same as the components missing from the primary device and available on a more full-featured version of the primary device; and an application accessible by the primary device to modify drivers on the primary device to address the components on the sheath receptacle, wherein the application re-maps addresses in the primary device for access of components on the more full -featured version of the primary device to addresses to the components on the sheath receptacle.

2. The apparatus of claim i, wherein the sheath receptacle is in a shape of a mobile device case.

3. The apparatus of claim 1, wherein the primary mobile device may be any of a portable media player, a cellular phone, a portable digital computer and a portable Apple product.

4- The apparatus of claim l, wherein the electronic data communication port may be any of a USB port, a Fire Wire port, Bluetooth, and WiFi.

5. The apparatus of claim 1, wherein the one or more elements may include any of a camera, a GPS receiver, a sensor, a battery, a compass, data network and phone facilities, human interfaces, a biometrics reader, and an extended memory card.

6. The apparatus of claim 5, wherein the sensor may be configured to sense any of temperature, accelerometer, pressure, position, elevation, light intensity, wind speed, and data rate.

7. The apparatus of claim 5, wherein the human interfaces may be any of a mini keyboard and a touchpad mouse.

8. The apparatus of claim 5, wherein the biometrics reader may be a fingerprint reader.

9. The apparatus of claim 1, wherein the primary device is configured to: receive an indication of new component attached from the electronic data communication port; receive hardware identifying data from the electronic data communication port; determine an extended feature of the new component based on the hardware identifying data; and obtain an application component to engage the extended feature.

10. The apparatus of claim 9, further comprising: querying a local memory stack for a driver to interface with the new component; and downloading a driver file from a network drivers database if query returns empty result.

li. The apparatus of claim g, wherein obtaining an application component to engage the extended feature comprises: querying an application library based at least in part on the determined extended feature.

12. The apparatus of claim g, wherein obtaining an application component to engage the extended feature comprises: downloading an application package from an online application library based at least in part on the determined extended feature.

13. The apparatus of claim 9, wherein obtaining an application component to engage the extended feature comprises: receiving user instructions to construct an application package for the extended feature.

14- The apparatus of claim 13, wherein the application package is constructed under Xcode.

15. The apparatus of claim 1, wherein the one or more elements are configured to: receive a request for an extended feature; collect sensing data indicative of the extended feature; and send the collected sensing data to the primary device via the electronic data communication port.

16. The apparatus of claim 15, wherein the electronic data communication port sends data indicative of the extended features in a format of USB packets to the primary device.

17. The apparatus of claim 15, wherein the one or more elements are further configured to periodically update sensing data with the primary device.

18. The apparatus of claim 1, wherein the one or more elements are in a power save mode if there is no request for an extended feature.

19. A mobile device feature extension processor-implemented method, comprising: receiving an indication of new component attached from the electronic data communication port; receiving hardware identifying data from the electronic data communication port; modifying drivers on a primary device to address the new component based on the hardware identifying data; and re-mapping an address in the primary device for access of a component on a more full-featured version of the primary device to an address to the new component.

20. A mobile device feature extension processor-readable medium storing processor-issuable instructions to: receive an indication of new component attached from the electronic data communication port; receive hardware identifying data from the electronic data communication port; modify drivers on a primary device to address the new component based on the hardware identifying data; and re-map an address in the primary device for access of a component on a more full-featured version of the primary device to an address to the new component.