The present invention relates, generally, to user interfaces and methods associated therewith and, more specifically, to navigation between user interface icons organized in a hierarchical manner.
User interfaces are ubiquitous in today's society. Computers, cell phones, fax machines and televisions, to name a few products, all employ user interfaces. User interfaces are intended to provide a mechanism for users to easily access and manipulate the, sometimes complex, functionality of the devices that they support. An example of a user interface is found in U.S. patent application Ser. No. 10/768,432, filed on Jan. 30, 2004, entitled “A Control Framework with a Zoomable Graphical User Interface for Organizing, Selecting and Launching Media Items”, the disclosure of which is incorporated here by reference. Typically, such user interfaces employ remote, handheld devices to provide inputs to their respective applications.
User interfaces facilitate navigation within an increasingly complex array of choices in a home entertainment system for example. Objects or icons within a user interface may be organized logically in a hierarchical manner. A user may select an icon on a home entertainment system user interface to indicate his or her desire to watch TV, play computer games, access the internet, etc. via a monitor/display for example. Once the choice for watching TV is indicated, the user may be presented with icons (for selection) that represent broadcast channels, premium channels, sports channels, etc. Each of these icons may be actuated to provide additional levels of choices. For example, under broadcast channels, the network channels may be presented.
As the choices and levels of organization of the interface objects/icons increase, it would be desirable to transition between user choices in a rapid manner.
In one embodiment, a method of returning target scenes from a user link request is disclosed. The method comprises the steps of: receiving a user link request on a user interface; comparing the received user link request to a plurality of entries in a lookup table; for each entry in the plurality of entries in the lookup table that matches the received user link request, identifying a target scene that corresponds to the matched entry in the lookup table; determining a closest one of the target scenes if multiple entries in the lookup table match the user link request; and transitioning to the closest target scene.
The accompanying drawings illustrate exemplary embodiments of the present invention, wherein:
The following detailed description of the invention refers to the accompanying drawings. The same reference numbers in different drawings identify the same or similar elements. Also, the following detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims.
Exemplary embodiments of the present invention provide a method for navigating between, and returning targets for, user selections on a user interface. More specifically, a “closest” target (from potentially multiple targets) is returned as described in more detail herein below. User interfaces as they pertain to exemplary embodiments are described first and specific exemplary methods for returning targets are then described.
An exemplary user interface (UI) 100 is illustrated in
An exemplary input device (or free-space pointing device) may resemble a mouse such as a wireless mouse 600 depicted in
Another exemplary free-space pointing device 700 may resemble a loop-shaped device such as that illustrated in
Referring back to
If a user chooses to watch premium channels, then actuation of icon 210 may result in displaying UI 300 of
Actuation of icon 310 on UI 300 may result in displaying UI 400 of
While each of the icons are depicted as having an oval shape, they are not restricted to this shape. The icons may be rectangular, square, circle or any other shapes. The icons may also be arranged in multiple rows as illustrated in user interface 800 of
For each movie title (
The user interface illustrated may be referred to as a zoomable user interface (ZUI) since highlighting one of a plurality of icons magnifies the highlighted icon in exemplary embodiments as illustrated in user interface 800 of
An overall exemplary hierarchical structure for the icons of
The language definition for each scene is represented as a scalable vector graphic (SVG). SVGs are used as they describe shapes on a display page, movements on a display page and location of graphics as they appear on a display page within a graphical display.
Programming information for a particular channel/network may be received by the server from the respective network on a periodic basis. Such programming may be dynamic in nature. That is, a movie title under the action genre for HBO for one period (a week or a month) may differ from a movie title under the action genre for HBO for a second period.
Each of the nodes/scenes may have a unique description or definition that may be stored in a server. The scene definition therefore may rely on information received from the networks. The scene representing “The Terminator” in
The scene representing “The Matrix” may have the following two exemplary definitions since The Matrix occurs twice: home\SHOWTIME\movies\sci-fi\The Matrix and home\HBO\movies\action\The Matrix.
The definition in this exemplary embodiment may be in a folder/subfolder type of hierarchy. Other formats may also be used to define the scenes. The definition for a scene may be viewed as the path from the home location to the scene location. The server may store a description (or definition) for all scenes that are currently available.
In the example described above, a plurality of generic identifiers may be assigned under the genre. The generic identifiers may be termed as movie-0, movie-1, . . . movie-n. The generic identifiers may have different movies associated with them based on programming for a particular time period. For the month of November 2005 for example, movie-0 may correspond to “The Matrix” and movie-1 may correspond to “Mission: Impossible” In April 2006, movie-0 may correspond to “Spiderman” and movie-1 may correspond to “Mission: Impossible II”.
Each of the program titles (such as “Mission: Impossible” and “The Matrix”) may have unique identification associated therewith such as a numeric or an alphanumeric code for example. Such identification may be included in metadata corresponding to the movie and may be received or known by the server.
A user highlighting “The Matrix” under HBO\Movies\Action, for example, may also be presented with related titles. The related titles/movies may be those having similar story lines, genre or those having common actors, etc. The related titles/movies may also be included in the metadata received by the server.
A user wishing to obtain information (such as a preview clip or description) or to view/play a related movie may click on an icon representing the related movie (movie 21, movie 36, etc. of
For each movie title or program available on the server, an entry may be created in a lookup table based on an identification generated by the server representing a user link request. Separate entries may be created for each aspect of a particular title. The separate aspects may be movie information (such as preview) and movie play for example. For each of these entries, a location (i.e. path of a scene described above) where the desired information such as movie information or movie play (a “target scene”) may be found may be listed in the corresponding column.
Because a particular user link request may have multiple resulting scenes, the link request may be listed multiple times in the table—each having a different corresponding resulting scene or path.
During runtime (i.e. while the user is navigating the user interface), a link request received from a user may be searched for in the table. If the received link request matches an entry in the table, the corresponding location information is obtained. If multiple entries match the received link request, then the information for multiple corresponding locations (each corresponding to one of the multiple entries) is obtained and the closest one of these corresponding locations is selected using an algorithm described below.
During runtime, using the exemplary setup illustrated in
For “The Matrix Reloaded Preview”, there are two potential resulting scenes. The scenes in this example have the paths Home\The Matrix Reloaded Preview and Home\SHOWTIME\The Matrix Reloaded Preview. A scene representing “The Matrix—Behind Scenes” may be Home\HBO\Documentaries\The Matrix—Behind Scenes or Home\SHOWTIME\Movies\The Matrix—Behind Scenes.
If the user chooses “The Matrix Reloaded Preview” for example, the server computes the shortest distance to “The Matrix Reloaded Preview” from the current scene.
In determining the shortest distance, the server attempts to minimize the number of steps or levels that have to be traversed up (i.e. go up as little as possible). This may be accomplished by picking the target having the longest common prefix (as it relates to the scene definition or path) with the current scene.
Then, it attempts to minimize the number of steps or levels that have to be traversed down (i.e. go down as little as possible). For the “going down” part, the server examines paths to each possible target and selects the path having the fewest “\” in exemplary embodiments.
In the example above, if the chosen scene is “The Matrix Reloaded Preview”, the current location/scene is Home\HBO\Movies\Action\The Matrix. The two possible destination scenes may be Home\SHOWTIME\The Matrix Reloaded Preview and Home\The Matrix Reloaded Preview. The common prefix for the current scene and the first destination scene is Home. The common prefix for the current scene and the second destination scene is also Home.
Both destination scenes in this example have the same length common prefixes with respect to the current scene. This implies that the same number of levels have to be traversed up regardless of either destination scenes. However, the number of levels to traverse down from Home varies between the destination scenes. For the first destination scene, two levels have to be traversed. For the second destination scene, only one level has to be traversed down. In this case, the server chooses the second destination (i.e. Home\The Matrix Reloaded Preview).
If the user chooses “The Matrix—Behind Scenes”, then the two destination scenes may be Home\HBO\Documentaries\The Matrix—Behind Scenes or Home\SHOWTIME\Movies\The Matrix—Behind Scenes. In this scenario the current scene (i.e. Home\HBO\Movies\Action\The Matrix) has a longer common prefix with Home\HBO\Documentaries\The Matrix—Behind Scenes than with Home\SHOWTIME\Movies\The Matrix—Behind Scenes. The server then chooses the first destination scene.
If only one destination scene is available, then the shortest distance need not be determined and the one destination scene may be selected. As illustrated in
If the distance to multiple destinations is identical, then any one of the destinations may be selected. As illustrated in
The transition from the source scene to the destination scene may be visually presented on the user interface utilizing the zoomable aspect of the user interface. That is, for example, the transition from Home\HBO\Movies\Action\The Matrix to Home\HBO\Documentaries\The Matrix—Behind Scenes in
At each stage of the transitioning sequence, the scene of interest (1210, 1220, 1230, 1240, 1253 and 1260) or relevance may be displayed more prominently on the user interface 1200 than other scenes (1215, 1225, 1235, 1245, 1247 and 1255) at that hierarchical level (illustrated in
Navigational icons illustrated in each of
The methods described herein may be implemented using known Java techniques. The server may be remotely located and user interaction via a handheld device may be facilitated over a network connecting a receiver (receiving user actuation from the handheld device) to the server. An exemplary system 1300 is illustrated in
Exemplary methods described above may be illustrated with reference to
The above-described exemplary embodiments are intended to be illustrative in all respects, rather than restrictive, of the present invention. Thus the present invention is capable of many variations in detailed implementation that can be derived from the description contained herein by a person skilled in the art. For example, while the description focused on navigating between programs in multiple locations in a home entertainment system, exemplary embodiments may be equally applicable for determining a closest branch of a retail chain having multiple locations that is within a same jurisdiction for ensuring a particular sales tax rate.
All such variations and modifications are considered to be within the scope and spirit of the present invention as defined by the following claims. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly described as such.
This application claims the benefit of U.S. Provisional Patent Application No. 60/683,099 filed on May 20, 2005 and entitled “Dynamic Hyperlinking Approach”, which is herein incorporated by reference in its entirety. This application is a continuation of, and claims priority from, U.S. patent application Ser. No. 11/438,520, filed on May 22, 2006, entitled “Dynamic Hyperlinking Approach”. This application is also related to, and claims priority from, U.S. patent application Ser. No. 11/119,663 filed on May 2, 2005 entitled “Freespace Pointing Devices and Methods” (now U.S. Pat. No. 7,239,301 issued Jul. 3, 2007, referred to herein as the “663 application) and Ser. No. 10/768,432, filed on Jan. 30, 2004 entitled “A Control Framework with a Zoomable Graphical User Interface for Organizing, Selecting and Launching Media Items” (referred to herein as the '432 application). The subject matter of each of these applications is incorporated in its entirety herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5706510 | Burgoon | Jan 1998 | A |
5781772 | Wilkinson, III et al. | Jul 1998 | A |
5873077 | Kanoh et al. | Feb 1999 | A |
5909440 | Ferguson et al. | Jun 1999 | A |
6222532 | Ceccarelli | Apr 2001 | B1 |
6243091 | Berstis | Jun 2001 | B1 |
6489979 | Belknap et al. | Dec 2002 | B1 |
6704729 | Klein et al. | Mar 2004 | B1 |
6714936 | Nevin, III | Mar 2004 | B1 |
7062490 | Adya et al. | Jun 2006 | B2 |
7328214 | Yuan et al. | Feb 2008 | B2 |
20020059603 | Kelts | May 2002 | A1 |
20020159466 | Rhoades | Oct 2002 | A1 |
20030090506 | Moore et al. | May 2003 | A1 |
20030097357 | Ferrari et al. | May 2003 | A1 |
20040088678 | Litoiu et al. | May 2004 | A1 |
20040123320 | Daily et al. | Jun 2004 | A1 |
20040268393 | Hunleth et al. | Dec 2004 | A1 |
20050005241 | Hunleth et al. | Jan 2005 | A1 |
20050071784 | Klein et al. | Mar 2005 | A1 |
20050198574 | Lamkin et al. | Sep 2005 | A1 |
20050253806 | Liberty et al. | Nov 2005 | A1 |
20060010246 | Schulz et al. | Jan 2006 | A1 |
Entry |
---|
Iglesias et al., From Analog to Digital Television: Strategies to Promote Rapid Adaptation and Awareness, 2010, UCS,—jucs.org. |
International Search Report in related International Application No. PCT/US06/19731 mailed Dec. 26, 2006. |
Written Opinion in related International Application No. PCT/US06/19731 mailed Dec. 26, 2006. |
ARM architecture, http://en.wikipedia.org/wiki/ARM—architecture, Apr 4, 2012. |
Arm Architecture, http://web.archive.org/web/20050407050615/http://en.wikipedia.org/wiki/ARM—architecture, Apr. 7, 2005. |
Lanthier et al., “Approximating Shortest Paths on Weighted Polyhedral Surfaces”, 2001, Algorithmica (New York), pp. 527-562, vol. 30, Iss. 4. |
H. Tzeng et al., “On Fast Address-Lookup Algorithms”, IEEE, Jun. 1999, pp. 1067-1082, vol. 17, No. 6. |
Number | Date | Country | |
---|---|---|---|
20140020028 A1 | Jan 2014 | US |
Number | Date | Country | |
---|---|---|---|
60683099 | May 2005 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11438520 | May 2006 | US |
Child | 14029082 | US |