Patent Application
20080297481
The present invention generally relates to providing networked communications systems with handheld communications devices capable of providing access to sponsored content (e.g., Web pages and executable networked applications and services) over a wireless network using keyboard or other key-based access on a wireless device, such as, for example, a cellular phone.
To date, the primary access devices for the Internet have been PCs and laptops that are used at static locations, such as desks or coffee shops. These computing devices generally have large keyboards, large screens and some form of mouse/cursor control. Increasingly, however, small, handheld devices (such as cell phones) have incorporated Internet access capability, and the networks to which they connect increasingly offer broadband upload and download capacity. Since far more people globally own and use cell phones—as of 2006, approximately forty percent (40%) of the world's population owned a cell phone—than own or use PCs or laptops, and cell phones are becoming multi-mode devices connected to broadband wireless networks that provide Internet access, there is an urgent need to provide easy access on mobile devices for the content and media available on the traditional static-location Web access devices, such as PCs or laptops.
Currently, most standard mobile phones that are capable of accessing the Internet via cellular networks use a single access soft key—frequently the middle button on the phone's directional pad—that accesses the service provider's Web portal. To move from there to other parts of the Internet (such as other web pages, web applications and web content), the user must perform a series of frequently lengthy scrolls and clicks and text entry. For instance, by at least one communications industry measure, it currently takes on average of twenty clicks to download a ringtone.
The aforementioned shortcomings of mobile devices to provide easy access to a broad range of sources of content, media and applications on the Internet is addressed by a portable wireless device facilitating access to sponsored content over a wireless network and methods associated therewith. The wireless device includes a keypad user interface having a set of dedicated launch keys that have an assigned function to launch programs/modules providing access to sponsored content. The keypad user interface also includes a first set of programmable displays associated with, but separate from, each one of the set of dedicated launch keys. The programmable displays each present a representation of sponsored content invoked in response to a user pressing a corresponding one of the dedicated launch keys.
A launch key data structure is also included in the mobile device. The launch key data structure, by way of example a table in a database, includes a set of entries corresponding to individual ones of the dedicated launch keys. Each dedicated launch key entry in the data structure (e.g., table) includes at least an identification of a networked source of sponsored content accessible by selecting one of the dedicated launch keys on the keypad user interface. A first accounting function associates selection of one of the dedicated launch keys with a first compensation parameter.
Thus, in addition to providing an arrangement for automatically launching a Web page or application via a single key press on a mobile device, the disclosed system and methods provide a mechanism for charging content sponsors (e.g., a business associated with the Web URL or Web application to which a key is dedicated) on a monthly (or other time period) or click-through basis. The charge may be performed and received by the company providing telecommunications services to the device, thereby enabling that company to receive revenue independent of the charging the subscriber fees for voice or data services and, also potentially allowing subsidization of the device cost through revenue received from content sponsors over the duration of use of the device by a subscriber.
While the appended claims set forth the features of the present invention with particularity, the invention, together with its objects and advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings of which:
a, 6b, 6c and 6d summarize elements of an illustrative database table structure/schema for providing functionally related information defining the operation of a cellular phone or other wireless device incorporating the dedicated launch key functionality described herein;
Attention is directed to the set of figures. The figures illustratively depict a mobile device interface for Internet access according to a set of dedicated launch keys, associated accounting and billing systems and network access that provides a set of dedicated physical keys on a mobile device. The interface facilitates launching and accessing Web-based applications and URLs and performing associated accounting functions.
The diagrams and images generally show a user interface containing a set of hybrid display/physical keys dedicated to launching features and applications of a mobile device, including, importantly, Web-based applications and URLs. The dedicated launch keys have a scrolling ability such that there are as many in this list of individual keys as the database and memory in the device permit. One or more of each of the keys in this list is assigned a single, specific Web-based application or URL by the software running the device. This assignment is done permanently in advance of purchase by the network operator or the handset manufacturer, or, alternatively, is done on a download basis at any time by the network operator, and, alternatively, the software running the device may give the user the option of changing the assignment of some or all of the keys.
Further, in the system depicted in
The remote application's communication with the device OS can launch a URL or remote application, while leaving all the keys of the device keypad in standard telephone numeric mode or setting them to text entry mode (except the direct launch keys 16).
Alternatively, the application's communication can re-set all the keys (as stated with the exception of the direct launch keys 11) to a general set of application-specific modes, or, based on an identification of the owner information of the device 20 with a user identification in the remote application's database(s), to a user-specific set of application modes. For instance, if a mobile phone's owner identification information is passed to a remote application (either directly from the phone or from the phone's service provider's databases) consisting of a web-based social networking site, the networking site's server can match this data to its user database information, and, if it finds a match, the social networking site's server can download to the device a set of modes for the physical key/dynamic display keypad interface that are personalized to the specific individual based on the individual's preferences or on the individual's user patterns of the website, either on a standard basis or on a mobile usage basis, thereby personalizing the mobile device's keypad for the user to optimize the user's experience of the social website (and without the need for any user interface information such as menus appearing on the web page view displayed on the upper screen of the mobile phone, such as the user's personal page(s), and without the need for the user to log into the website via the website's home page, and without the necessity for cookies resident on the mobile device).
The same system generally applies to mobile gaming whereby a mobile game remote server places game graphics on an upper screen of the mobile device 20, and optimizes the keypad by re-setting the keys (except for the direct launch keys 16) on the keypad of the mobile device 20 with game commands. Similarly, web-based applications, such as word processing, photography editing, presentation development and spreadsheet programs, when launched by a direct access key and remotely accessed via the network, can re-set the mobile device's entire keypad (with the exception of the direct launch keys 16) based on parameters set by the user or by the remote application to make the user's experience easy and more compelling for the full set of features offered by the remote application.
A set of two keys 33 have an integral, uni-directional press-to-scroll functionality indicated by the grey up and down arrows. By pressing and holding these keys, the user scrolls through the list of all URLs, applications and features on or available through the device that have been assigned to direct launch keys 32, in order. The scrolling functionality can also be done using physically separate scroll keys, such as scroll wheels, toggle keys or directional pads. If the keypad technology is implemented using a touchscreen or control surface, the scrolling can be done using virtual keys or other touch control technology. The scrolling enables a virtually infinite list of direct launch keys, listed and scrolling in an order determined by the software and data structures for the keypad interface.
The keypad interface software can implement rules that are also, in whole or in part or expanded upon, distributed to developers as part of software developer kits that enable third party application developers to enhance or optimize their applications consistent with the underlying operational paradigm of the interface. For instance, a rule could be that the top right hand key and its associated display are locked by the software for most or all contexts to switch the device into its basic telephone mode. The scroll functionality would only apply to the dedicated launch keys below the top right key. This gives the user a “home base” and an easy way to put the phone back into its basic telephone mode that no software developer has the right (under the SDK) or the ability (under the core interface software) to override. Similar rules can be defined to build out a set of good programming practices for any third party developer of applications that will run on a device implemented with this system.
Of course, more or fewer than the number of physical keys shown in the figures for the keypad interface can be implemented. Four keys making up the left and right columns, with the right being the default column for the dedicated launch keys is a preferred implementation for a number of reasons, including, for instance, ease of ergonomic use, a sufficient number of scrolling keys (plus a top key locked to telephone mode, as described above), and optimal text entry mode. Keypad software can provide a user with the ability to change a left/right hand setting, automatically switching the keypad's dedicated launch key column from the right hand side to the left hand side. Twelve keys in the middle is also preferred because, for instance, of its familiarity to most people as the number of keys on standard telephone keypads and calculator keypads.
Further, the entire keypad can be implemented virtually on a touchscreen or control surface, with software creating “active” touch-sensitive areas and allocating virtual display areas for the displays above or on the keys. The implementation shown in certain of the figures is a hybrid of physical keys and integrated dynamic displays, which provides the benefit of tactile ease, familiarity, muscle memory of physical keys and ease of use for visually disabled people, combined with the benefits of displays that change according to the mode the user has selected.
As an alternative, a physical key in the dedicated launch key column can be allocated the role of an aggregator for a category or type of application or URL. When such an aggregator key is pressed, the middle twelve keys display a set of applications or URLs that fit that category. For instance, an aggregator key could be titled “WWW News” and the middle twelve keys when that aggregator key is selected could display one or more of www.cnn.com, www.nytimes.com, www.wsj.com, and www.bbb.org, etc. These can be pre-set, set by the user or set remotely. A click on one of these middle twelve keys performs a direct, one-click launch of that URL or application. The left hand column keys provide access to subsequent sets of launch keys within the same aggregation category. A click on one of the middle twelve keys configured as aggregated dedicated launch keys could result in a click through fee.
Aggregation keys can be determined according to a number of factors, including, for instance, subject matter of URL (e.g., news websites, video websites, search websites, social network websites, etc.), a company with multiple offerings by application or URL (e.g., Google with Google search, Google apps, etc; or Microsoft with Word, Excel, PowerPoint, Visio, etc.), subject matter of application (e.g., mobile gaming or ringtone websites), or user favorites (potentially analogous to play lists or “most-played” on MP3 players).
a, 6b, 6c, 6d and 6e summarize a set of fields generally defining an exemplary database schema for supporting dedicated launch keys that the device's OS, via the device's internal keypad software and remote applications, accesses to operate the keypad's features. A set of Structural Fields 600 depicted in
The Structural Fields 600 of
The core role of the Structural Fields 600 is to set high-level parameters of a set of direct access key definitions stored, on a per direct access key basis, in the form of Direct Access Key Definition fields 607 that are used by the keypad management software 920 (depicted herein below with reference to
The Definition fields 607 include a set of entries that hold the data and defining characteristics of each key in the dynamic array 31 (depicted herein above with reference to
The database fields also include a last updated information field 623 indicating when the particular dedicated launch key definition was last modified.
A set of payment information fields 624 including a paid lock/unlock flag 625, a payment type field 626, a billing provider server ID field 627 and a no payment required flag 628. The payment information fields are accessed by the payment software 800 (described herein below with reference to
The left hand column key fields and the middle twelve key fields, which are defined under a given right hand direct access key, are defined within tables in the database by sets of fields similar to those depicted in
A set of Navigation (Left Hand) Key definition fields 629 depicted in
Also depicted, in
The terminology “dedicated launch key” refers to keys in the right hand column 635 and/or keys in the middle twelve key group 633 that have the role allocated to them by fields in the database of directly launching sponsored content, together, as applicable according to the information in the applicable database fields, of displaying the sponsored content branding or other identifier information in the display associated with the applicable key and of activating the accounting/billing sequence when the key is selected.
The roles of the left hand and right hand key columns may be located differently or swapped (right and left, to accommodate left handed users), and may have fewer or more than the four keys depicted in these figures.
In the above described database (set of tables), the information to be displayed and the functionality associated with each key in the scrollable, dynamic keypad array 10 (described herein above with reference to
During step 704 the setup utility verifies the new setup against setup rules and/or current keypad database information (e.g., verify that a designated dedicated key is available to be reconfigured to contact a newly specified Web address). Thereafter, at step 705, if errors are detected, then control passes to step 706 wherein an error message is issued by the setup utility and control returns to step 702. Otherwise, if no setup errors are detected (or any detected errors have been corrected), then control passes from step 705 to step 707 wherein the setup utility commits the new launch key configuration to a launch key data structure (e.g., a table, a list, an array, etc.) such as the one depicted herein above with reference to
Thereafter, during step 810 a payment software module accesses payment processing information within the launch key information stored, for example, in a launch key data structure (see, e.g., field 624 and associated subfields described herein above with reference to
During step 820, if payments are current or otherwise flagged as not applicable, then control passes to step 830 wherein an “ok” message is registered. During step 820, if payments are determined to be necessary and are not current, then control passes to steps 840-890 wherein additional steps are performed to attempt to remedy a payment shortfall. During step 840 the payment software operates to read an address for a payment server associated with the dedicated launch key for which payments are not current. Thereafter, during step 850 the payment server (and associated billing system) corresponding to the address obtained during step 840 is accessed via a wireless connection.
Next, during step 860, a payment request is submitted to the payment server and logged on the payment server system. The payment request can be in a variety of forms including actual monetary value or registration of a click-through operation.
Control next passes to step 870. In the illustrative example, if during step 870 it is determined that the device received an “ok to launch message” from the payment server/billing system, then control passes to step 880 and the key payment software returns a payment “ok” message thereby indicating to the keypad management software 960 (described herein below with reference to
A number of alternatives are available to the above-described exemplary steps including: prompting a user for payment, sending an application or URL owner an error/payment due message, running a free application version or accessing a free alternative Web page/address, logging results in a dedicated key's data structure for later processing, retrying after an appropriate delay, etc.
Thereafter, during step 930 the device OS indexes into a table entry corresponding to the selected dedicated launch key within the launch key interface database (described herein above with reference to
Otherwise, if a payment error is identified during step 950, then control passes to step 970. During step 970 a payment error management process is invoked. The error management process, by way of example, reports the error to the user and other impacted parties (e.g., the sponsor/payer). Thereafter, control returns to step 900.
In further discussion of step 960, if the dedicated launch key is associated with a URL, then a browser is launched on the mobile device with an initial page address set to the IP address associated with the selected dedicated launch key, or, alternatively, if the browser is already open, then the browser is given the URL to open, in a new tab if tabbed browsing is enabled in the browser. If appropriate, the system supplies the device owner's associated logon credentials, as stored in the database fields, to identify the user to the website at the URL according to the user logon credentials previously specified for the launch key in the launch key data structure for use by the website to launch the user's personal pages, and, as appropriate, to download a customized or personalized set of key settings to the device keypad.
The structures, techniques, and benefits discussed above are merely exemplary embodiments of the invention carried out by software executed on computing machines and stored on computer-readable media in the form of computer executable instructions. In view of the many possible embodiments to which the principles of this invention may be applied, it should be recognized that the embodiments described herein with respect to the drawing figures are meant to be illustrative only and should not be taken as limiting the scope of invention. The illustrated embodiments can be modified in arrangement and detail without departing from the spirit of the invention. Moreover, those of skill in the art will recognize that the disclosed principles are not limited to any particular local area network protocols and/or topologies. Therefore, the invention as described herein contemplates all such embodiments as may come within the scope of the following claims and equivalents thereof.
This application claims priority of Higginson U.S. Provisional Application Ser. No. 60/940,954 filed on May 30, 2007, for “Direct Access Mobile Content System,” and Higginson U.S. Provisional Application Ser. No. 61/013,558 filed on Dec. 13, 2007, for “Direct Access Mobile Content System,” the contents of both provisional applications are incorporated herein by reference in their entirety, including any references contained therein. This application also incorporates by reference in its entirety the disclosure of Higginson U.S. Pat. No. 6,703,963 for a “Universal Keyboard.” The disclosure of which includes a description of a multi-function, multi-domain level keypad/keyboard within which the physical and functional features described herein are advantageously incorporated.
| Number | Date | Country | |
|---|---|---|---|
| 60940954 | May 2007 | US | |
| 61013558 | Dec 2007 | US |
