JP2009500877A - Method and system for device independent media transactions - Google Patents

Abstract

  Methods, systems, techniques, and computer readable media are provided for device independent media transactions, such as media transactions, acquisition, presentation, and publishing. An exemplary embodiment provides a device independent video transaction system (DIVTS) that allows a user to receive data streamed over a broadband connection and output video data to a display. Transactions for media such as streaming video can be performed on any device. In one embodiment, the DIVTS comprises a user interface (401), a transaction engine (402), a media subsystem (403), and optionally a media data repository (407). The subsystem further comprises an acquisition engine (404), a presentation engine (405), and a publishing engine (406). These components work together to allow the third party device (100) to perform media acquisition, transaction, presentation, and publishing. The abstract is prepared to comply with the rules that require the abstract and is submitted with the intention of not using it to interpret or limit the scope or meaning of the claims.

Description

  The present disclosure relates to methods and systems for device-independent media transactions, and more particularly to methods and systems for facilitating media transactions, acquisition, presentation, and publishing.

  Digital broadband network access has become widely used, and various technologies for distributing various media contents have emerged. Such techniques include dedicated set-top boxes for receiving and decoding digital and / or analog content for display on a television set, operating on a closed network, such as a network operated by a cable television company. Other technologies include portable media devices and software media players. A software media player typically operates on an open network such as the Internet, receives and decodes digital content, and attaches to a computing system such as a desktop computer, laptop computer, or mobile phone On the specified display device. The portable media device can store and display or play digital content obtained from the host computing system.

  The media distribution set-top box model has various disadvantages. First, set top boxes typically operate on closed networks. That is, consumers are limited to media choices offered by network owners, typically cable television companies. Thus, consumers are faced with monopolistic pricing because they are restricted from selecting media content. Furthermore, the set-top box model of content distribution is inherently unidirectional and consumption based. That is, consumers are passive with respect to their consumption, and their only two-way interaction is to select one of the various provided functions selected by the network operator. Consumers typically use a set-top box to share their content and / or provide reviews and / or ratings of the media they access, in a meaningful way, It is not possible to interact with other media content and / or other information resources.

  The software distribution media player model for media distribution also has some disadvantages. First, as with set-top boxes, the user plays a passive role in the consumption of media content. The user can choose from a number of media serving functions, but with little or no return of meaningful feedback or other interactive interactions related to the media consumed by the user . If the user wants to interact in this way, the user often has other software systems that may not be well integrated into the particular media player they are using (for example, , Web browser). In addition, the market for incompatible media players often collapsed as a result of standardization disputes between advocates of various media distribution standards. In some cases, a user must install multiple media players to access media content that conforms to various incompatible standards.

  In addition, the distributed portable media device model has various disadvantages. First, portable media devices typically do not have the ability to access streaming content directly over a broadband connection. Instead, they rely on a host computing system, such as a desktop personal computer, to download music and / or video from a content source and further transfer it to a portable media device. As such, when a portable media device is disconnected from the host system, the selection of content provided to the user is effectively static. In addition, with the host computing system intervening, users can add software systems added on the host computing system to build and manage media libraries that exist primarily for the purpose of providing content to portable media devices. Face the task of learning about usage.

  In addition, the issue of inconsistencies extends to various approaches to distributing media. There are numerous devices in the current home that can be used to consume various forms of media, including personal computers, laptop computers, personal digital assistants, cell phones, and televisions. However, in order to consume the media, the user must sometimes learn to utilize a dedicated interface for each device at the expense of considerable time, money, and / or frustration costs. There is no single unified interface that users can use to operate all these devices, consume media content in a way that has meaningful and true interactivity, and interact with each other. .

  In the embodiments described herein, methods and systems for performing device independent media transactions such as media transactions, acquisition, presentation, and issuance are presented. In an exemplary embodiment, a device independent video transaction system ("DIVTS") is provided that allows a user to receive data streamed over a broadband connection and display media data. Transactions can be performed on media such as video streamed on a device that can be output to. Media includes audio, text, video, still images, and other forms of information in various genres or formats, including movies, documentaries, books, magazines, news sources, reference materials, and the like. The term “media” as used herein further refers to one or more logical or physical groups and / or arrangements of information such as media items, media titles, content items, or media selections. including. Further, the one or more media items can be arranged in a media catalog or other collection or collection, or grouped in some other way. By installing DIVTS on a third party device, such a device becomes DIVTS compliant. The terms “DIVTS enabled”, “media enabled”, “video enabled”, etc., refer to devices configured to conduct transactions with media in various contexts. The DIVTS embodiments are device independent and can be provided for many different hardware operating environments (eg, personal computers, video game systems, personal digital assistants, cell phones, etc. running various operating systems). Thus, the user need only learn a single unified user interface to perform various interactive rich media functions.

  In some embodiments of DIVTS, to specify the media to be acquired, to instruct the destination of the presentation of the acquired media, and to provide a unified mechanism for initiating transactions related to the specified media Provides an interface based on a structured "quilt" metaphor. The interface uses a minimal set of input modalities and can be operated using various display devices, increasing the degree of platform and / or device independence. The quilt user interface provides a single unified interface for interacting with any instance of DIVTS running on any device, so users can run a single set to perform a rich set of media transactions. Just learn the interface.

  Using a DIVTS-enabled device, a user can perform a transaction on the media, which can be used to conduct financial transactions (eg, purchase, rental, subscription) to obtain the right to access the media title. Including. Performing a transaction further includes obtaining meta-information (eg, by searching, browsing, etc.) related to the media title, such as a review, synopsis, still image. Further, conducting the transaction includes performing a financial transaction to obtain goods and / or services drawn and / or suggested in the media title, and / or meta information related to the media title. Such goods and / or services include, for example, clothing or accessories worn by actors in a particular media title, articles drawn in advertisements associated with a particular media title, particular media This can include products that are guaranteed in the context of a title review. In addition, the user can use a DIVTS enabled device to obtain a media title for presentation (eg, display and / or playback) on the device. Further, in some embodiments, a user can use a DIVTS enabled device in media content stored at home or other network (eg, digital video stored on a home computer) or at home or other network. Media content (eg, web or internet camera) made available by some other method can be published (eg, shared).

  Multiple DIVTS interacting with other producers and consumers of the media over the network may form a media transaction network ("MTN") in some embodiments. A DIVTS that interacts bi-directionally over a network can be used to obtain media from various media sources. A media source can provide media data regardless of whether it is accessible over a network, such as a streaming media server, web server, FTP server, hard disk, or other computer readable media storage device, network camera, etc. Or including the system. Furthermore, DIVTS can be used to publish available media from a media source to various media sinks (media receiving devices) and make the media accessible. Media sinks include devices or systems that can consume media, such as software media players or other DIVTS. Using DIVTS as part of an MTN would otherwise be inaccessible from other devices on the MTN (including non-DIVTS enabled devices) or systems (eg, files whose media are generally not available from the network) Media that would have been resident on the system) can be made available.

  FIG. 1 is an exemplary block diagram of an exemplary embodiment of a device independent video transaction system that resides on a third party device. In the illustrated embodiment, third-party device 100 comprises media source 101 and device independent video transaction system (“DIVTS”) 102. Third-party device 100 can be a device that can stream media to a display or display media via a high-speed network connection (eg, a broadband Internet connection) or obtain the media. The DIVTS 102 interacts with the media source 101, media sink 103, media transaction network portal (“MTNP”) 104, display device 105, and audio device 106 in a bi-directional manner, and media and transactions related to the third-party device 100. To users of.

  In particular, the DIVTS 102 obtains media not only from the media source 101 but also from the MTNP 104. Acquiring media is digital and / or analog data along with information content that can be presented as images, audio, text, symbols, or other forms that can be perceived by human senses via a network, data bus, or other communication mechanism Can be included. In the illustrated embodiment, the DIVTS 102 obtains media from a media source 101 that is shown to reside on the third party device 100. As such, media source 101 can be a hard drive, optical drive, or other storage device or subsystem that can provide media to DIVTS 102. Further, the media source may be at a remote location, as illustrated by MTNP 104, which is the media to DIVTS 102 via a network (not shown) or other communication interconnect. Can be provided.

  DIVTS 102 also uses MTNP 104 to perform transactions on media and meta information and items related to such media (media related items). Media transaction execution includes purchasing, renting, subscribing, licensing, or obtaining any rights to the media, media-related meta-information, and / or media-related items. be able to. The media-related meta-information can include information related to acquirable media, such as media publication information (eg, title, publisher, director, producer, actor, etc.), review, synopsis, still photo, etc. Media-related items are recommended by media drawn goods and / or services (eg sunglasses worn by actors in a movie), goods and / or services suggested by drawn media (eg cooking programs) Cooking appliances), and media-related meta information (eg, advertisements provided with the acquired media, fan clubs of actors recommended in movie critique articles, etc.) and / or indicated by it Services can be included. A typical media transaction involves performing a search to obtain search results for the media to be obtained, obtaining media reviews and / or previews, purchasing, renting or subscribing media items, Operations such as purchasing a product that is depicted or related and providing a review of the media item may be included.

  In addition, DIVTS 102 presents the media to display device 105 and / or audio device 106. Media presentation prepares the media for output and other digitally and / or analog media data that can be detected by humans, including chemicals that can be perceived by signals or electromagnetic waves, sound waves, and taste or smell, or tactile impulses Initiating output of the media by an output device that can be changed to an impulse can be included. In the illustrated embodiment, the DIVTS 102 displays image data from the acquired video media item on a display device 105 (eg, a cathode ray tube (“CRT”) or a liquid crystal display (“LCD”)). The audio data from the acquired video media item is presented to the audio device 106 (eg, a speaker or a headphone) so that the viewer can audibly perceive it.

  In some embodiments, DIVTS 102 may also publish media to media sink 103. Media publishing includes providing the media so that it can be obtained or retrieved by a media sink or other consumer of the media, such as for presentation. Media publishing distributes such media items along with an indication of the location from which such media items can be obtained (eg, URL (“Uniform Resource Locator”), or URI (“Uniform Resource Indicator”)) or other It can include not only the media items themselves, but also metadata related to such media items, including mechanisms that communicate in some way. In the illustrated embodiment, the DIVTS 102 publishes media (eg, home-made video such as a home movie) to the media sink 103. For example, the media sink 103 can be a video player that acquires media issued over a network for the purpose of displaying on a remote display device.

  FIG. 2 is an exemplary block diagram illustrating an overview of an exemplary process that provides the functionality of a device independent video transaction system. A DIVTS, such as DIVTS 102, supports a number of functions as described with reference to FIG. Although these functions are illustrated as separate steps in FIG. 2, the functions can be performed in any order, and from one function typically depends on the desire of the user operating the device. It will be understood that the flow can proceed to other functions. In step 201, the DIVTS determines what media to present and displays a user interface for performing transactions related to such media. Then, in step 202, the DIVTS obtains media from the media source. The media can be obtained from any media source, including local and / or remote sources. Examples include media from local storage devices (eg, hard disk, optical drive, etc.) and media accessed via a broadband connection or computer network (eg, web server or streaming video server). In step 203, the DIVTS is suitable such as a device configured to present audio (eg, headphones, speakers, etc.) and / or a device configured to present video (eg, CRT or LCD display). Present the acquired media to a secure device. At step 204, the DIVTS initiates a media related transaction. Such transactions may be acquired, purchased, rented, subscribed, for example, by buying or buying any other goods and / or services that may be related to the entity or daily necessities, or the media being presented Can be related to In step 205, the DIVTS supports publishing media to other systems and / or users. After performing each of these steps, the DIVTS can return to any of the other previous steps to perform the functions described with reference to steps 201-205. After the DIVTS no longer performs such a function, such as when the user shuts down the device, the DIVTS process ends.

  In one embodiment where there are multiple media enabled devices, the media enabled devices can coexist in a network environment to facilitate media sharing and access. FIG. 3 is an exemplary network diagram illustrating a network of median transactions. A media transaction network (“MTN”) includes one or more devices, some of which are media-enabled and others are not media-enabled and are interconnected by one or more networks. For example, the illustrated MTN 300 includes a first local network 301, a second local network 302, a media sink resident on a mobile phone 305, DIVTS on a personal digital assistant (“PDA”) 306, server computing MTNP residing on system 308, media sources residing on server computing system 307, and connections to a plurality of other devices 309-313 via first local network 301. Mobile phone 305 and PDA 306 are connected to MTN 300 via wireless network access gateway 304. Wireless network access gateways can be used in addition to using fixed wires or cables by using network-enabled devices that use electromagnetic signals (eg, radio waves, microwaves, infrared, etc.) A device is provided that allows communication with a network enabled device. For example, the wireless network access gateway 304 may include a mobile phone installation device, a wireless router, a packet wireless system, an infrared transceiver, and the like. The various illustrated devices, computing systems, and networks are connected and communicatively coupled via an interconnect network 303 such as the Internet.

  In the illustrated embodiment, the first local network 301 resides on a DIVTS residing on the gaming system 309, a DIVTS residing on a desktop personal computer (“PC”) 310, and a non-DIVTS enabled video camera 311. Media sources and devices such as media sources and media sinks that reside on non-DIVTS capable laptop computers 313. The illustrated non-DIVTS enabled video camera 311 is a communication interface (eg, USB (“Universal Serial Bus”) interface, IP (“Internet Protocol”) accessible video data that can be accessed by other computing devices. Service). Furthermore, the laptop computer 313 is connected to the first local network 301 via the wireless network access gateway 312 in the figure. The local network 301 is connected to the MTN 300 via a network gateway 314 in the figure. The network gateway 314 may be, for example, a modem, cable modem, digital subscriber line (“DSL”) modem, router, or other device or subsystem that can connect the local network 301 to the interconnect network 303. it can.

  As such, the illustrated MTN is a “ecosystem” of devices and / or computing systems that can coordinately acquire media and execute, present, and publish their transactions. For example, the local network 301 can include a plurality of devices and / or computing systems that can be configured by a user to obtain media, execute, present, and display its transactions. The network is illustrated. The DIVTS that resides on the personal computer 310 can be used to publish media from non-DIVTS enabled devices such as the video camera 311 along with media that is local to the personal computer 310. In doing so, the user can make the media available from both DIVTS enabled and non-DIVTS enabled devices that are internal and external to the local network 301. For example, a user may obtain and / or present media issued by DIVTS residing on personal computer 310 utilizing a DIVTS residing on game system 409 or a media sink residing on laptop 313. be able to. In addition, devices 305 and 306 are external to local network 301 and typically reside on a hard drive that is local to personal computer 310 or cannot access media provided by, for example, video camera 311. As such, the user may issue a DIVTS residing on the personal computer 310 using a media sink on the mobile phone 305 (eg, an instance of a media player such as a RealPlayer ™ media player) or a DIVTS on the PDA 306. Media can be obtained and / or presented. Thus, one or more DIVTS-enabled devices operating on the network may have different sources due to various other media consuming devices on the network that may not otherwise be able to access media from such sources. It has a “gluing” function that facilitates sharing and presentation of media available from

  In some embodiments, a user can specify devices that can access the published media and / or access rights that can be used to limit the user. For example, a DIVTS user resident on a PC 310 can publish video provided by a media source in the video camera 311, but in addition, for example, devices operating on the local network 301, as well as on a PDA 306 By specifying an access right that allows access by DIVTS but does not allow access by other devices in the illustrated MTN 300, access to such media can also be restricted.

  The exemplary embodiments described herein include applications, tools, data structures, and DIVTS, quilt-based user interfaces, and / or transactions, acquisition, presentation of media, particularly video-based media titles, And other support for implementing MTNP to be used for publishing. Other embodiments of the described technology are used for other purposes, including distribution of other types of media, including audio books, podcasts, ebooks (eg, eBooks), educational materials, newspapers, current magazines, etc. can do. In addition, quilt metaphors provide a device-independent unified mechanism for invoking various feature sets, including web browsing, document creation, information organization and presentation (eg, encyclopedia), database front end, etc. can do.

  In addition, although some terms are used exclusively herein, one of ordinary skill in the art can use other terms interchangeably to obtain equivalent embodiments and examples. Will understand. For example, the terms “video”, “audiovisual”, “movie”, “movie”, and other similar terms are used to refer to media content that includes images and / or text and / or audio portions. can do. In addition, the terminology may use other spellings that may or may not be explicitly mentioned, and those skilled in the art are intended to include all such variations of terms. You will understand that. In the following description, numerous specific details are set forth, such as data formats and code sequences, in order to provide a thorough understanding of the described technology. However, the techniques of the present invention may also be practiced without or with some of the specific details described herein, such as code flow or changes in the order of different code flows or steps. You can also As such, the scope of the described techniques and / or functions is not limited by the particular order, selection, or decomposition of steps described with respect to a particular routine.

  FIG. 4 is an exemplary block diagram of components of an exemplary embodiment of a device independent video transaction system. The DIVTS 400 comprises one or more components that work together to allow the third party device to acquire media, execute and present its transactions as described with respect to FIGS. Can be issued. In an exemplary embodiment, the DIVTS 400 includes a user interface 401, a transaction engine 402, a media subsystem 403, and optionally a media data repository 407. In an exemplary embodiment, the media subsystem 403 further comprises an acquisition engine 404, a presentation engine 405, and a publishing engine 406. Depending on the particular embodiment, the media subsystem 403 may comprise only some of these sub-components or different components, or may distribute the functionality described in the plurality of components in different ways. it can.

  In the illustrated embodiment, the user interface 401 receives input from the user indicating which functions of the DIVTS 400 the user wants to perform. In addition, the user interface 401 is responsible for converting device dependent input events into device independent input events so that other components of the DIVTS can be implemented in a device independent manner. Transaction engine 402 initiates and executes transactions related to the media acquired and presented by media subsystem 403. Media subsystem 403 is responsible for media acquisition, media presentation, and media sharing via publishing mechanisms. Acquisition engine 404 acquires media from a variety of sources, including media sources and / or data repositories, such as media data repository 407. The presentation engine 405 initiates and / or facilitates the operation of displaying or presenting media on one or more output devices. The publishing engine 406 facilitates sharing of the local or remote media of the DIVTS 400 with other users, devices, and / or systems. The media data repository 407 is an optional component that may be present on a DIVTS-enabled device to store and / or access local media.

  In an exemplary embodiment of a device independent video transaction system, various types of user interfaces may be provided for exposing media related functions to users. FIG. 5 is an exemplary block diagram of a “quilt” user interface provided by an exemplary embodiment of a device independent video transaction system. Some embodiments of DIVTS are configured to specify a media to be acquired, determine a destination for presentation of the acquired media, and present a unified mechanism for initiating transactions related to the specified media. It has an interface based on the “quilt” metaphor. Other embodiments of DIVTS can incorporate other user interfaces to perform these functions.

  The illustrated quilt 500 comprises a plurality of “panels” that can each display information and / or comprise one or more actions that can be invoked by a user. The panels in the quilt user interface are similar in metaphor to the square “block” of the decorative quilt, except that the panels can be any shape, such as a rectangle, triangle, or any polygon. The illustrated quilt 500 includes a home panel 501, a first category panel 502, a second category panel 503, a results panel 504, a preview panel 505, a synopsis panel 506, a review panel 507, and a photo panel 508. Other quilts can include a different set of panels, or include the illustrated panel or a subset of additional panels. Each panel in the quilt is typically logically connected to at least one other panel, and the user can connect to and from one of the panels connected to that first panel from the first panel. Navigate through the quilt by moving to other connected panels, such as animations that give the user an illusion of motion. For example, in the representation of quilt 500, home panel 501 is connected to first category panel 502 and then to second category panel 503. A user navigates from one of these panels to another by generating appropriate input events, for example by using an input device such as a mouse, keypad, and / or joystick Can do. These panels and the movement between the panels will be further described with reference to FIGS.

  The user may display one or more panels of the quilt 500 using a viewport 510 (actually invisible to the user) used to create a frame that displays at least a portion of the quilt. it can. For example, in some embodiments, the viewport 510 can be implemented as a window that sets a clipping region using, for example, known graphic techniques. Using the clipping technique, the viewport 510 can set which panel is displayed to the user. Further, the placement of the viewport 510 with respect to the quilt panel sets a “reference” orientation point (eg, camera angle) for displaying the quilt. Different movement and / or animation effects can be achieved by moving the viewport 510 (ie, the orientation point) away from or closer to the surface of the quilt and by changing the orientation point (ie, the angle of orientation) relative to the quilt surface. can get.

  For example, when a user navigates a quilt from a first panel to a second panel, the viewport can be moved in various ways to display the second panel. In some embodiments, the movement of the viewport 510 is performed so that the user can see an animation of the transition from one panel to the next. For example, in the illustrated quilt, when the user navigates from the results panel 504 to the preview panel 505, the viewport 510 can be smoothly shifted from the illustrated position and instead surround the preview panel 505. . Additional or alternative navigation animation effects are possible, including immediate transition from one panel to the other, zooming in, zooming out, and changing the tilt of the viewport with respect to the quilt panel. Zooming in and / or zooming out can be performed by lowering and / or raising the viewport. Changing the viewport angle with respect to the quilt surface can give the user a perspective. Such effects can be implemented using, for example, known 2D and 3D graphics techniques. It should be noted that such animation effects can be conceptualized and executed in various ways equivalent to those described herein. For example, rather than shifting the viewport from one panel to the other, the quilt (ie, content) can be shifted by an equivalent amount while leaving the viewport in a fixed position. Other embodiments and improvements are possible.

  Navigation within the quilt can be performed by using a minimal set of user interface input events. In some embodiments, a set of five events including left, right, top, bottom, and selection is sufficient. Using the four direction events (left, right, top, and bottom), the user can navigate from one panel to the next. In the selection event, the user can invoke actions that can be used on the “currently active” panel. In some embodiments, the direction event may further cause a selection to be performed (eg, function as a selection event) and / or the selection event causes a direction movement (eg, functions as a direction event). be able to. Other embodiments may have more or fewer input events, and the events may be named differently (eg, “Left” is “West” and “Select” is “ Such as "action"). By configuring the quilt to navigate the quilt with a minimal set of input events, device independence can be enhanced and quilt-based user interfaces can be implemented on a variety of hardware devices.

  In addition, non-planar quilts are also possible. For example, a quilt can be mapped to one or more three-dimensional objects such as spheres, convex or concave polyhedra. Such embodiments “fly” or “move” over a three-dimensional landscape covered with a quilt panel capable of providing information and control to activate the functionality provided by DIVTS or other applications. Can give users the illusion of being.

  In a typical planar quilt with a rectangular panel, navigation proceeds in a horizontal or vertical orientation as described with respect to FIG. FIG. 6 is an exemplary state diagram illustrating navigation within an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. The illustrated state diagram is a hierarchical state diagram of the navigation transition shown in FIG. That is, the state diagram consists of “upper states” that can include one or more other states or higher states. A superior state typically includes characteristics that are common to all contained states or superior states.

  The illustrated quilt navigation upper state 600 includes a search upper state 601 and a media title navigation upper state 602. The upper search state 601 includes a category selection menu state 601a, a category selection / deselection state 601b, a title update and category list state 601c, and a title selection menu state 601d. The user can transition to any of states 601a-d by generating an input event as shown with respect to FIG. As the user transitions in states 601a-d, various panels, such as panels 502-504, are presented, providing the user with information about the media title categories that can be selected to search the set of media titles. . By selecting one or more categories, the user can narrow the set of media titles to only those titles included in each of the selected categories. After selecting at least one category, the user can enter a title selection menu state 601d.

  The user can select one title from the title selection menu state 601d and transition to the media title navigation upper state 602. The media title navigation upper level state 602 includes five media navigation states, a back state 602a, a preview state 602b, a synopsis state 602c, a review state 602d, and a photo state 602e. From each of the media navigation states 602a-e, the user initiates the generation of a “select” input event (eg, by pressing a button, moving the device, or moving a portion of the device, etc.). ), Transition to another state in which the instructed media navigation action can be performed on the user side. For example, the user can start generating a “select” input event from the preview state 602 b and transition to the preview upper state 603. In addition, the user initiates the generation of an appropriate direction (eg, “left”, “right”, etc.) input event from one of the media navigation states 602a-e to the media navigation state 602a-e. You can transition to other states. For example, the user can transition from preview state 602b to synopsis state 602c by initiating the generation of a “right” input event.

  The high preview state 603 includes a number of states 603a-d that allow the user to preview the selected media title. The upper preview state 603 includes a pause state 603a, a playback state 603b, a left seek state 603c, and a right seek state 603d. By transitioning to the appropriate of these states, the user may, for example, play a portion of the media title and / or seek (eg, fast forward or rewind) to a specific position in the media title. As a result, the selected media title can be previewed.

  The illustrated state diagram of FIG. 6 illustrates possible states and transitions that can be prepared to allow a user to acquire media, perform transactions on media, and / or present media. A set is shown. Other state diagrams with increasing and decreasing states and / or transitions are also conceivable.

  The exemplary quilt user interface may comprise a plurality of panels each with user selectable controls along with information for invoking one or more functions provided by the DIVTS as described above with respect to FIG. it can. 7A-7E are exemplary screen displays of various “panels” of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. 7A-7E show some detailed views of some of the quilt panels introduced with reference to FIG.

  FIG. 7A is an exemplary screen display 7A00 of a first category panel 7A01, a second category panel 7A02, and a result panel 7A03. This screen display corresponds to the viewport 510 arranged as shown in FIG. In the illustrated embodiment, the user is engaged in searching for media titles by selecting one or more categories shown in the first category panel 7A01 and the second category panel 7A02. In response, the DIVTS user interface displays a results panel 7A03 that includes a single media title, “Title 7” found in each of the selected categories. Performing a media search is described in further detail with respect to FIGS. 10 and 11A-11D.

  FIG. 7B is an exemplary screen display 7B00 of a preview panel that allows the user to preview the selected media title. The display 7B00 shows a media title navigation bar 7B01 including a back button 7B02, a rent now button 7B03, a preview button 7B04, a synopsis button 7B05, a reviews button 7B06, a photos button 7B07, and a video area 7B08. The user can perform different media acquisition and transaction functions by navigating the media title navigation bar 7B01 and selecting one or more of the illustrated buttons 7B02-7B07. In the illustrated embodiment, the user has selected the preview button 7B04, resulting in the display of data video in the video area 7B08 of the selected media title. After the user previews the selected media title, selecting the back button 7B02 returns to the previous panel (eg, results panel 7A03 described with respect to FIG. 7A), full by selecting the rent now button 7B03 Rent a media title, move to the synopsis panel described further with respect to FIG. 7C, move to the review panel described further with respect to FIG. 7D, or move to the photo panel further described with respect to FIG. Other or additional actions can be performed.

  FIG. 7C is an exemplary screen display 7C00 of a synopsis panel that allows the user to obtain a synopsis of the selected media title. The display 7C00 presents a media title navigation bar 7C01 similar to the media title navigation bar 7B01 described with respect to FIG. 7B. Further, the display 7C00 includes a synopsis area 7C02 that displays a summary of the selected media title. The user can generate input events that navigate (eg, page up / down) the entire summary of the selected media title.

  FIG. 7D is an exemplary screen display 7D00 of a review panel that allows a user to obtain a review of a selected media title. Display 7D00 presents a media title navigation bar 7D01 similar to media title navigation bar 7B01 described with respect to FIG. 7B. Further, the display 7D00 presents a plurality of reviews 7D02 that display reviews (eg, user-created reviews) of the selected media title. The user navigates the entire review (eg, page up / down when there are more reviews than can fit on a single screen) and / or gets more information about individual reviews (eg, single An input event can be generated (selecting a review so that the entire review can be accessed). In other embodiments, the user can also use such an interface to create and publish their own reviews or ratings that can be shared with other users on the MTN, for example.

  FIG. 7E is an exemplary screen display 7E00 of a photographic panel that allows a user to obtain a still image that has been retrieved from or within a selected media title. The display 7E00 presents a media title navigation bar 7E01 similar to the media title navigation bar 7B01 described with respect to FIG. 7B. Further, the display 7E00 presents a plurality of photographs 7E02 representing still images from the selected media title. The user can navigate in the various displayed photos 7E02 (eg, more than fits on a single screen) or get details of one or more displayed photos (E.g., high resolution and / or multiple images, prices, text descriptions, etc.). In some embodiments, such still images can also be purchased and / or licensed for use by the user (eg, for screen savers or other purposes).

  User-initiated input events, such as those described above with respect to FIGS. 5, 6, and 7A-7E, may be handled by a user interface routine provided by the DIVTS in some embodiments. FIG. 8 is an exemplary flowchart of an exemplary user interface routine provided by an exemplary embodiment of a device independent video transaction system. The illustrated user interface routine can be provided, for example, in the user interface 401 of FIG. That is, the user interface routine waits for a user-initiated action and executes the user-initiated action by invoking or executing one or more functions of the DIVTS, such as media acquisition or transaction execution.

  More specifically, at step 801, the routine determines or receives an indication of a user action to be performed, and then executes or initiates the indicated action at steps 802-808. Specifying inputs to this routine as well as other routines described herein are known in the art including, but not limited to, parameter passing, message passing, signals, sockets, pipes, streams, files. It can be implemented in various ways. In step 802, the routine determines whether the indicated user action is to perform a media and / or media related item transaction, if so, continues to step 803, otherwise, step 804. followed by. In step 803, the routine calls the MediaTransact routine to perform the media transaction. This routine is further described with reference to FIG. The routine then continues to step 809.

  At step 804, the routine determines whether the indicated user action is to access the media, if so, continue to step 805, otherwise continue to step 806. At step 805, the routine gets the media and possibly calls the MediaAcquire routine to present the media to the user. The MediaAcquire routine is further described with reference to FIG. The routine then continues to step 809.

  At step 806, the routine determines whether the indicated user action is to share media content, if so, continues to step 807, otherwise continues to step 808. In step 807, the media publish routine is called to publish the media by making it available to other users, and step 809 follows. The MediaPublish routine is further described with reference to FIG.

  In step 808, the routine performs other indicated actions as appropriate and continues to step 809. Other actions can include, for example, notifying the user of available software updates, performing such updates, adjusting system settings, and the like. In step 809, the routine determines if it is appropriate to exit or if there is other work to be performed, and if so, exits, otherwise, the beginning of the loop in step 801 Return to, wait for further user actions received and process.

  FIG. 9 is an exemplary flow diagram of an exemplary media transaction routine provided by an exemplary embodiment of a device independent video transaction system. The routine can be provided, for example, in the transaction engine 402 of FIG. The MediaTransact routine executes a loop that repeatedly invokes user-initiated actions by invoking or executing media transaction related functions supported by DIVTS, such as media search and / or licensing. In step 901, the routine determines or receives a user action or an indication of the media to be acquired. In steps 902-907, the routine processes the indicated action. Specifically, in step 902, the routine determines whether the indicated user action is a media search request. If so, the routine continues to step 903 and calls the MediaSearch routine described further with respect to FIG. 10, otherwise it continues to step 904. At step 904, the routine determines whether the indicated user action licenses or purchases the media and / or goods and services related to such media. If so, the routine continues to step 905, otherwise it continues to step 906. At step 905, the routine begins a transaction for the indicated media product and / or service. At step 906, the routine completes the transaction. Completing the transaction can, for example, give the user an indication of the success or failure of the transaction, or obtain additional information necessary to complete the transaction by further interacting with the user, and / or Or can include giving. In some embodiments, much or all of the information used to perform the transaction (eg, credit card number, contact information, etc.) can be stored locally or remotely, which allows the user to Transactions can be completed in a single step without providing additional information.

  At step 907, the routine performs other indicated actions as appropriate. Other actions include obtaining and providing user-generated reviews and / or ratings of media titles, adjusting or otherwise configuring user settings or preferences related to performing media transactions. (Eg, movie favorite categories, payment information, contact information, demographic information, etc.). In addition, embodiments with interfaces and functionality related to subscribing to media and / or media related content may be supported. For example, different levels of subscribers can be supported that define what type of media a user can access, the number of media titles per period, etc.

  After processing the user action in steps 903-907, the routine proceeds to step 908 to determine whether the transaction is complete. If the transaction is not complete (eg, because there are additional user actions to process), the routine proceeds to step 901 and continues to process more actions. Otherwise, the routine returns.

  FIG. 10 is an exemplary flowchart of an exemplary media retrieval routine provided by an exemplary embodiment of a device independent video transaction system. This routine may be provided in the transaction engine 402, for example, as further described with respect to FIG. The MediaSearch routine executes a loop that repeatedly narrows down a set of media titles according to one or more search conditions (eg, categories) selected by the user. Although described in terms of categories and subcategories, other criteria can be incorporated as well.

  Specifically, in step 1001, the routine initializes a variable WorkingSet for all available media titles. This collection of media titles may be stored locally, connected to a device hosting the DIVTS, or remotely on a network accessible media library or other information source. In step 1002, the routine receives an indication of the media title category. In the illustrated embodiment, a media title category is written by a specific author, commanded by a specific director, and related to a specific genre (eg, action, adventure, romance, etc.) Or it is a set of media titles that all have common characteristics such as having a language. Categories are further described with respect to FIG.

  In step 1003, the routine determines which of the media titles corresponds to the indicated category and initializes the other variable CurrentTitles with references to the media titles belonging to the category indicated in step 1002. In step 1004, the routine sets the WorkingSet variable to refer to a collection of titles that appear in both the current TitleSet as well as the current TitleSet. (This variable is updated to refer to the current title indicated by the current search condition in effect at each loop iteration.) At step 1005, the routine determines whether to continue processing additional search conditions. If so, continue to step 1002, otherwise continue to step 1006. The routine may continue, for example, upon receiving an instruction to add a media title category. At step 1006, the routine provides a set of titles indicated by a WorkingSet variable reflecting a set of media titles that match all indicated categories of media titles. The routine then returns.

  Note that in one embodiment, the search conditions are combined to form the intersection of the set of titles in each indicated category. The WorkingSet variable then reflects the set of media titles that are elements of the set intersection of this set. In other embodiments, other logical or set operators can be used to perform other types of searches, and the WorkingSet variable is adjusted accordingly. For example, in some embodiments, the user can select one or more set join operators to perform other types of searches (eg, all action movies in China or Europe).

  In some embodiments, one or more user interface screens are provided for obtaining input from a user and for providing results from the search process as described above with respect to FIG. be able to. 11A-11D are exemplary screen displays of an exemplary quilt user interface search panel provided by an exemplary embodiment of a device independent video transaction system. 11A-11D illustrate an example of four consecutive screens that can be displayed to the user during a search for a media title as provided by FIG.

  FIG. 11A shows the state of the search that the user selects from one of a number of genre categories. The screen displays three panels: a home panel 11A01, an upper category panel 11A02, and a category panel 11A03. The user has selected rental option 11A04 from home panel 11A01 indicating that the user wants to rent a media title for viewing. The user has selected a genre option 11A05 from the upper category panel 11A02 indicating that the user desires to specify a particular “Genre” category for the search. In the category panel 11A03, the cursor 11A06 is currently on the “Action” category. At this point, if the user begins to generate a “select” input event, the user interface will animate the transition and present a new panel view of the quilt on the display.

  FIG. 11B shows the resulting screen display after the user selects the “Action” category shown in FIG. 11A. This screen display shows an upper category panel 11B02, which is the upper category panel 11A02 shown in FIG. 11A, a category panel 11B02, which is the category panel 11A03 shown in FIG. 11A, and a result panel 11B03. Note that the home panel 11A01 of FIG. 11A is no longer displayed because the illustrated quilt user interface is configured to display at most three search panels in this example (viewports). Has been moved accordingly). Other embodiments may be configured to display more or fewer panels. In some embodiments, such configuration may be performed automatically in response to an indication of specific hardware requirements (eg, a small display device on the PDA). The result panel 11B03 shows all the six titles that are currently elements of the “Action” category.

  FIG. 11C shows the screen display that appears when the user next decides to further filter the search results of FIG. 11B by selecting additional categories. In this example, the user is back by initiating the occurrence of an input event suitable for selecting an additional higher category (“Studio”) 11C04 from the illustrated upper category panel 11C01. According to the illustrated embodiment, the search conditions are combined by using a logical “AND” (logical product) operation. As a result, a new category panel 11C02 that displays a number of studios in the selected upper category is displayed. Note that some of the studios (Studio 3, Studios 5-6, and Studios 8-10) are dimmed. The dimmed category indicates to the user that there are no media titles that fit within the dimmed category and other selected categories (in this case, the “Action” category of the genre upper category). In other embodiments, other mechanisms can be used to indicate that a media title does not exist in a particular category that can be selected with one or more already selected categories. Such mechanisms include, for example, displaying such categories in different colors, annotating such categories with icons and / or symbols, and hiding such categories. Furthermore, the result panel 11C03 from the initial search that is executed and displayed in FIG. 11B is still displayed. This panel is updated to reflect the results of the additional search criteria when the user selects one of the available categories in the category panel 11C02.

  FIG. 11D shows the screen display output when the user selects one of the studio categories of FIG. 11C. In this case, the user selects the category “Studio 4” 11D05, and as a result, the result panel 11D03 is updated, and the “Action” category of the “Genre” upper category 11D06 and the “Studio 4” of the “Studio” upper category 11D05 are updated. Reflects that there is only a single media title “Title 7” in both categories. Note that the upper category panel 11D01 indicates that the “Genre” upper category 11D06 is still selected by surrounding the appropriate text on the tab 11D08. Furthermore, a bridge 11D07 that appears from below the category panel 11D02 and is connected to the result panel 11D03 indicates that the search results are derived from the two selected categories. In this way, the user is informed of the current search structure and category.

  The category-based approach of media title search used by some embodiments and described above with respect to FIGS. 11A-11D can be conceptualized with respect to a categorization graph. FIG. 12 is a categorization graph representing the categorization of a number of exemplary media titles. A categorization graph is a directed aperiodic graph that can be used to represent one or more categories for one or more media titles. Arcs are directed (eg, using arrows) lines (straight lines, curves, or other lines) that are used to show relationships between nodes in a graph. A parent node (a node from which a circular arc comes out) is a category node. A leaf node (a node that does not have an arc from the node) is a media title node or an empty category node. A category node can be empty or indicate (by one or more arcs) one or more categories and / or media titles contained therein. The upper category node is a category node indicating at least one category node included in the upper category node. The two-level hierarchy including the top categories and categories used in the example described with respect to FIGS. 11A-11D can be generalized using a category classification graph. For example, the illustrated categorization graph has a single root node 1201 that includes all other categories, either directly or indirectly. In other embodiments, multiple root nodes can be represented.

  In the illustrated graph, the root node 1201 includes a genre category node 1202 and a country category node 1203. Genre category node 1202 and country category node 1203 include additional category nodes as illustrated. For example, the genre category node 1202 includes an action node 1204 and an adventure node 1205. Action category node 1204 includes media title node 1220, explosion category node 1206, and martial arts category node 1207. Note that the explosion category node 1206 is currently empty in that it does not reference other categories or media titles. Note also that the media title node 1220 is referenced by multiple category nodes. In general, there is no limit or restriction on the number of categories that can contain a given media title. In addition, the media titles of the examples illustrated in FIGS. 11A-11D can be represented in a category classification graph, even if organized in a two-level hierarchy of higher categories and categories, and represented in the search user interface. There is no limit to the number of categories and subcategory levels that can be.

  Furthermore, the country category node 1203 has an Asian category node 1208 that points to the China category node 1209, which further points to the media title node 1223. This graph shows an additional dashed arc 1211 indicating that, in some embodiments, a category node can include a direct arc that bypasses subcategories and points directly to media titles contained by such subcategories. ing. Even if the category is at or near the root of the categorization graph, such a direct arc can efficiently search all media titles in a given category when performing a search. Can be used as an optimization.

  The structure of the categorization graph can, in some embodiments, be automatically derived from structured or unstructured metadata related to a set of media titles. For example, keywords, tags, dates, and / or other structured (eg, XML (“Extensible Markup Language”)) and unstructured (eg, movie criticism) information can be examined and utilized to create a categorization graph. A categorization graph or equivalent that can be used to represent the correlation between media titles and categories, for example using various known techniques including automatic text classification Process unstructured data such as reviews, press releases, and advertisements in addition to text drawn on the media itself (as a text version of an audio book or movie script) with the goal of automatically generating data structures for Can do.

  In addition, by using categorization graphs or equivalent data structures, structural interrelationships and panel content of the search portion of the quilt user interface can also be automatically generated. For example, the children of a given category node can be assigned to a single category panel or placed within a single category panel. Then, selecting a category represented by a particular category node displays a category panel that includes the children of that category node and / or a results panel that includes the media title referenced by that category node.

  The process of filtering search criteria for the purpose of organizing in a panel for use with a quilt user interface can also be represented using Venn diagrams. 13A-13B are Venn diagrams representing categorization of a number of exemplary media titles. These figures provide alternative representations showing some of the collective relationships between the various categories shown in FIG. In FIG. 13A, MovieD 13A01 (shown at node 1223 in FIG. 12) is an element of the Chinese category 13A02, which is also a subset of the Asian category 13A03, which is also for all movies 13A04. A subset of the overall category. As another example, FIG. 13B shows that MovieB 13B01 (shown at 1222 in FIG. 12) is an element of both USA category 13B02 and martial arts category 13B03. Furthermore, the USA category 13B02 is a subset of the North American category 13B04. Martial art category 13B03 is a subset of both action category 13B05 and North America category 13B04. Both the North American category 13B04 and the action category 13B05 are a subset of the overall category 13B06. In some embodiments, it may also be beneficial to draw a Venn diagram and display the relationships shown by the user interface.

  Referring back to step 202 of FIG. 2, in an exemplary embodiment of the DIVTS user interface, in addition to searching for media, the user can also obtain media from various sources. FIG. 14 is an exemplary flowchart of an exemplary media acquisition routine provided by an exemplary embodiment of a device independent video transaction system. The routine can be provided, for example, in the media acquisition engine 404 of FIG. The MediaAcquire routine suitably starts a transaction (eg, licensing) to obtain a media title, and further executes a loop that receives media from the media source and starts its presentation as appropriate. An exemplary user interface for obtaining media is described with respect to FIG. Specifically, in step 1401, the routine determines an instruction for the media to be accessed. Such an instruction can be received, for example, as a result of selection by the user. In step 1402, the routine determines whether a financial transaction is required to obtain the indicated media. If so, the routine continues to step 1403, otherwise it continues to step 1404. In step 1403, the MediaTransact routine described with respect to FIG. 9 is called. Alternatively, if it is determined in step 1402 that no financial transaction is required, or after step 1403, then in step 1404, the routine begins media access. Initiating media access can include sending a message over the network, calling a function or procedure, or other mechanism for notifying the media source to begin providing media. At step 1405, the routine receives a portion of the indicated media or user action. At step 1406, the routine determines whether media has been received, if so, the routine continues to step 1407, otherwise it continues to step 1408. In step 1407, the routine begins displaying the received media portion. In some embodiments, this includes presenting a frame of video on a display device and / or playing a frame of audio data on a speaker or other audio output device. After step 1407, the routine continues to step 1410.

  Instead, if the routine determines in step 1406 that no media has been received, then in step 1408, the routine determines whether a user action has been received, and if so, continues to step 1409, and so on. Otherwise, continue to step 1410. Exemplary user actions include playing, pausing, fast forwarding, or stopping the display of video and / or other media. In step 1409, the routine processes the received user action as appropriate and then continues to step 1410. For example, if a pause action indication is received, the routine pauses the display of video and / or audio.

  At step 1410, the routine determines whether the acquisition of the indicated media has been completed, otherwise the routine returns to step 1405 to continue processing the media. The routine may end, for example, when there is no more media part available, or when the user indicates that he wants to end the acquisition process or some other way down. When finished, the routine returns.

  FIG. 15 is an exemplary screen display of a media acquisition panel of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. The MediaAcquire routine described with respect to FIG. 14 can receive instructions for user actions from this user interface and can direct media to this user interface. For example, the user can select the preview button 1501 so that the MediaAcquire routine begins to acquire the specified media title. When a portion of the specified media is received, the MediaAcquire routine can begin displaying image data (eg, video frames) on the video area 1502 and / or update the preview slider 1503. . The preview slider 1503 can also be manipulated by the user in some embodiments to seek or control the playback of a given media title.

  Referring again to step 205 of FIG. 2, in an exemplary embodiment of a DIVTS user interface, a user can also publish media to share media with other users. FIG. 16 is an exemplary flow diagram of an exemplary media publishing routine provided by an exemplary embodiment of a device independent video transaction system. The routine can be provided, for example, in the media publishing engine 406 of FIG. The MediaPublish routine collects information related to media sharing from the user so that the media sink can access such media.

  More specifically, in step 1601, the routine determines an indication of the location of the shared media. In some embodiments, such instructions can be represented, for example, by a URL passed to the user interface, eg, via user input. In step 1602, the routine determines or receives an indication of license conditions. License terms can include, for example, designation of assignment of legal rights included in the shared media. For example, the user may indicate that the user desires to place the indicated media in the public domain, or alternatively, may have some rights (eg, exclusive rights as defined by copyright law) It may be indicated that the user wants to retain one or more of the legal rights) in the indicated indicated media. In step 1603, the routine determines or receives an access right indication. Such access rights would allow the user to grant or deny access to the indicated media being shared, eg, a group of users, a group of devices, individual devices, and / or individual users Can be included. In step 1604, the routine determines or receives an indication of a distribution mechanism that shares the indicated media. Various distribution mechanisms are possible, including, for example, peer-to-peer distribution and / or centralized distribution through a media portal such as MTNP 308 described with respect to FIG. An exemplary MTNP is further described with respect to FIG.

  In step 1605, the routine determines whether the user has indicated that the media should be distributed via a portal or other centralized distribution mechanism. Otherwise, the routine continues to step 1606, otherwise it continues to step 1608. At step 1606, the routine accesses the indicated media via the indicated distribution mechanism. In some embodiments, this can include allowing media to be uploaded by one or more media sinks. Such functionality can be performed by a modified version of the MediaPublish routine, or alternatively by a turnkey media source such as a web server, media streaming service, etc. At step 1607, the routine provides media location indications to one or more portals or other distribution systems, as appropriate, and then returns. This step is a URL, IP (“Internet Protocol” so that it can be promoted, promoted, or communicated to other users in some other way via centralized or other distribution mechanisms. )) Providing an address or other indicator of available media.

  Instead, if it is determined at step 1605 that the user has indicated that the media should be distributed by a portal or other centralized distribution mechanism, the routine proceeds to step 1608. At step 1608, the routine provides the indicated media, license terms, and access rights to the portal or other centralized distribution mechanism. The centralized distribution mechanism then initiates the upload and storage of the directed media to a remote system (eg, media streaming service, FTP server, peer-to-peer network, and / or web server) for further distribution Can do. The routine then returns.

  FIG. 17 is an exemplary block diagram of a general purpose computer system for implementing an exemplary embodiment of a device independent video transaction system. A general purpose computer system 1700 may include one or more server and / or client computing systems and may span distributed locations. Further, each block shown in the figures may represent one or more such blocks as appropriate for a particular embodiment, or may be combined with other blocks. Further, the various blocks of DIVTS 1708 can physically reside on one or more machines, which use standard or dedicated interprocess communication mechanisms to communicate with each other.

  In the illustrated embodiment, computer system 1700 includes computer memory (“memory”) 1701, display 1702, central processing unit (“CPU”) 1703, network interface 1705, storage device 1706, pointing device 1707, and Other input / output (“IO”) devices 1704 are provided. The DIVTS 1708 is resident in the memory 1701 in the figure. The components of DIVTS 1708 are preferably executed on CPU 1703. As described with respect to FIG. 4, an exemplary DIVTS, such as DIVTS 1708, includes a user interface 1709, a transaction engine 1710, a media subsystem 1711, an optional media repository 1715, and an input engine 1716. The media subsystem 1711 includes an acquisition engine 1712, a presentation engine 1713, and an issue engine 1714. The input engine 1716 translates received physical input events into logical input events that can be consumed by other components, such as the user interface 1709, for example, physical received from the pointing device 1707 and / or other input devices 1704. Handle static user input events. Other programs 1720 can also reside in memory 1701 and are preferably executed on one or more CPUs 1703. Various implementation approaches and / or architectures are possible and are further described with respect to FIG.

  FIG. 18 is an exemplary block diagram of other details of an exemplary embodiment of a device independent video transaction system implemented on a third party entertainment device in a manner that is device independent. Third-party entertainment device 1801 includes DIVTS 1802, input control 1810, display control 1811, audio control 1812, hard drive 1813, network interface 1814, and optical media drive 1815. The DIVTS 1802 includes a user interface 1803, a media transaction engine 1804, a media publishing engine 1805, a media acquisition engine 1806, a media presentation engine 1807, and an input engine 1808. The user interface 1803 further includes a dispatcher 1830 and a plurality of listeners 1831.

  In typical operation, the input control 1810 of the third party device is connected to a pointing device 1820 such as a joystick or remote controller in this exemplary embodiment. Input control 1810 comprises a hardware / software / firmware interface that receives input events generated by pointing device 1820 and provides them to input engine 1808. Input engine 1808 further converts physical input events received from input control 1810 into logical device independent input events that are sent to dispatcher 1830. The dispatcher 1830 passes the logical input event to a listener 1831 that has expressed interest in that type of input event (eg, registers itself as available to handle a particular class or type of event). By). An exemplary dispatcher routine is further described with respect to FIG. Then, the listener interested in the input event starts or ends the presentation of media by the media presentation engine 1807, starts acquiring the media by the media acquisition engine 1806, and performs a media transaction by the media transaction engine 1804. Actions such as initiating or initiating sharing of media by the media publishing engine 1805 can be performed.

  For example, when media is received, presentation engine 1807 pushes the media to display control 1811 and / or audio control 1812 in the form of audio and / or video data. The display control can be, for example, a display driver (software) and / or hardware / firmware that transforms, renders, and / or controls the display 1821 to show image data. The audio control can be, for example, an audio driver and / or hardware / firmware that controls a speaker 1822 connected to output sound. Display 1821 and speaker 1822 can reside on device 1801 or be connected in some manner, such as by a communication mechanism. If one of the listeners 1831 initiates media acquisition, the media acquisition engine 1806 acquires the media as described, for example, with respect to FIGS. If one of the listeners 1831 initiates a media related transaction, the media transaction engine 1804 initiates or executes a media related transaction as described with respect to FIGS. Note that the media transaction engine 1804 may operate in conjunction with other internal and external systems and / or services, such as an independent vendor that provides financial authorization. If one of the listeners 1831 indicates that the user wants to share media, the media publishing engine 1805 is activated as described with respect to FIG.

  FIG. 19 is an exemplary flow diagram of an exemplary dispatcher routine provided by an exemplary embodiment of a device independent video transaction system. The routine can be provided, for example, in the dispatcher of FIG. The dispatcher routine executes a loop that repeatedly receives input events and passes them to the appropriate listeners. A listener is typically a software component that self-registers with dispatch to receive one or more specified events. Specifically, in step 1901, the routine receives an input event instruction. Such input events may comprise inputs generated and received from various hardware devices including but not limited to a keyboard, mouse, touchpad, touch screen, joystick, and / or remote controller. it can. In step 1902, the routine converts the physical input event received in step 1901 into a logical device independent input event. In step 1903, the routine determines a set of listeners who have expressed interest in receiving notification of the logical input event of step 1902.

  Next, in the loop defined by steps 1904-1906, the routine distributes logical input events to each listener in the set of listeners determined in step 1903. At step 1904, the routine determines whether there are any listeners in the set of listeners. If not, the routine continues to step 1907 and ends processing of the specified input event, and if so, continues to step 1905. In step 1905, the routine determines the next listener in the set of listeners. At step 1906, the routine delivers the logical input event to the listener determined at step 1905, returns to the top of the loop, and continues processing the specified input event in step 1904.

  In step 1907, the routine determines whether to continue processing the next input event, and if so, returns to step 1901. For example, if an additional event is waiting for processing, the routine can proceed to step 1901. Otherwise, the routine ends or enters a wait state until the next input event arrives. In one embodiment, the dispatch routine of FIG. 19 is implemented as or similar to an interrupt handler (eg, a device driver routine), which is invoked using a software or hardware interrupt triggered by the input device. Other programming techniques are also contemplated and operate to handle input events in a similar device independent manner.

  Referring again to FIG. 1, the DIVTS embodiment can interact with the media transaction network portal to perform media transactions as well as perform other functions. FIG. 20 is an exemplary block diagram of components of an exemplary embodiment of a media transaction network portal. The Media Transaction Network Portal (“MTNP”) provides the ability to perform media transactions, provide a device independent video transaction system to third party devices, and the context of a media transaction network in which one or more DIVTS enabled devices reside. A function for providing media is provided. In addition, the MTNP establishes an identification with the MTNP for the purpose of storing preferences (eg, favorite media categories) for MTNP users and information shared with other users (eg, media and / or ratings and Payment information (e.g., credits) for the purpose of providing and / or obtaining the right to obtain media and / or goods or services related to such media User account operations can be processed so that card information can be stored.

  The illustrated MTNP 2000 includes a media transaction management engine 2001, a user management engine 2002, a DIVTS distribution engine 2003, a media server 2004, a DIVTS repository 2005, a user data repository 2006, and a media data repository 2007. One or more of these components may be optional in a particular embodiment, and each block shown in the figure represents one or more blocks as appropriate for the particular embodiment. Can be represented or combined with other blocks. Further, the various blocks of MTNP 2000 can physically reside on one or more machines, which use standard or dedicated interprocess communication mechanisms to communicate with each other. The media transaction management engine 2001 processes media transactions as described with respect to FIG. 9 initiated by one or more DIVTS enabled devices 2008. In order to process a media transaction, it may be necessary to exchange interactively on the network 2011 with a payment processor system 2009 that can be operated by a third party. Examples of payment processors include credit card payment processors and / or electronic funds payment systems. The user management engine 2002 handles user registration and other user relationship functions and stores data related to such operations in the user data repository 2006. The DIVTS delivery engine 2003 provides an instance of DIVTS that is stored in the DIVTS repository 2005 or automatically generated to be installed on a third party device. A DIVTS instance can be represented by a machine or object code that is specific to a particular target computing system, or alternatively, a virtual machine or other that runs on the target computing system (ie, a third-party device) Can be represented in a high-level instruction format including virtual machine bytecode and / or source code that can be interpreted by any interpreter. Media server 2004 operates as a media source and provides media that can be stored in media data repository 2007 to one or more DIVTS enabled devices 2008. Media servers include, for example, streaming media servers, web servers, FTP (“file transfer protocol”) servers, and the like. Further, the MTNP 2000 can interact with the media source 2010 over the network 2011 and upload or obtain media or media instructions for the purpose of distribution, advertisement, and the like.

  FIG. 21 is an exemplary block diagram of a general purpose computer system for implementing an exemplary embodiment of a media transaction network portal. A general purpose computer system 2100 may include one or more server and / or client computing systems and may span distributed locations. Further, each block shown in the figures may represent one or more such blocks as appropriate for a particular embodiment, or may be combined with other blocks. Further, the various blocks of MTNP 2108 can physically reside on one or more machines, which use standard or dedicated interprocess communication mechanisms to communicate with each other.

  In the illustrated embodiment, computer system 2100 includes computer memory (“memory”) 2101, display 2102, central processing unit (“CPU”) 2103, network interface 2105, storage device 2106, pointing device 2107, and Other input / output (“IO”) devices 2104 are provided. The MTNP 2108 is resident in the memory 2101 in the figure. The components of MTNP 2108 are preferably executed on CPU 2103. As described with respect to FIG. 20, an exemplary MTNP includes media transaction management engine 2109, user management engine 2110, DIVTS delivery engine 2111, and media server 2112, DIVTS repository 2113, user data repository 2114, and media data repository. 2115. Other programs 2120 can also reside in memory 2101 and are preferably executed on one or more CPUs 2103.

  In the exemplary embodiment shown in FIGS. 17 and 21, the DIVTS and MTNP components can be implemented using standard programming techniques. Without limitation, an object-oriented type (for example, Java (registered trademark), C ++, C #, Smalltalk), a function type (for example, ML, Lisp, Scheme, etc.), a procedural type (for example, C, Pascal, Ada, Modular) ), Representative examples of various programming language paradigms, using various programming languages known in the art, including script types (eg, Perl, Ruby, Python, etc.) Specific embodiments can be implemented. Further, the various components of the illustrated embodiment are implemented by a single monolithic executable program that runs on a single CPU computer system, or alternatively, each comprises one or more CPUs. Decompose using various structuring techniques known in the art, including but not limited to multi-programming, multi-threading, client-server, or peer-to-peer, running on one or more computer systems be able to.

  Further, programming interfaces with data stored as part of the illustrated embodiment include C, C ++, C #, and Java APIs for accessing files, databases, or other data repositories. Or it can be made available by standard means, such as through a library, or through a web server, FTP server, or other type of server that allows access to stored data. For example, media data repository 1715 and DIVTS repository 2113 in FIG. 17, user data repository 2114, and media data repository 2015 in FIG. 21 may include one or more database systems, file systems, or such information, or a combination of the above Can be implemented using other methods known in the art for storing.

  Furthermore, the exemplary embodiments shown in FIGS. 17 and 21 can be implemented in a distributed environment consisting of multiple and even heterogeneous computer systems and networks. For example, in one embodiment, components 2109-2112 and repositories 2113-2115 of FIG. 21 are all located in physically different computer systems. In other embodiments, the various components 2109-2112 are hosted together on one machine, while the data repositories 2133-2115 are hosted on a host of another machine. Various distributed computing technologies include, but are not limited to, illustrative embodiments of distributed schemes including TCP / IP sockets, RPC, RMI, HTTP, Web services (XML-RPC, JAX-RPC, SOAP, etc.) Suitable for implementing the components. Other variations are possible.

  Different configurations and arrangements of codes and data are contemplated for use with the techniques of the present invention. In the exemplary embodiment, the components are shown in FIGS. 17 and 21 and can be executed asynchronously simultaneously, so that the components communicate using well-known dedicated message passing techniques. Can do. Equivalent synchronous embodiments are also supported by DIVTS and / or MTNP implementations.

  22-24 describe exemplary routines implemented by an exemplary media transaction network portal used by DIVTS enabled devices. FIG. 22 is an exemplary flow diagram of an exemplary user management routine provided by an exemplary embodiment of a media transaction network portal. The routine can be provided, for example, in the user management engine 2002 of the MTPN 2000 of FIG. The user management routine loops at steps 2201-2209, and user actions related to user identification intended to perform media transactions and other functions provided by MTPN, such as providing media for acquisition and / or presentation Receive and process instructions. Specifically, at step 2201, the routine determines or receives an indication of user account operation. In step 2202, the routine determines whether the indicated user account operation is to create a new user account. If so, the routine continues to step 2203 and creates a new account for the indicated user, otherwise it continues to step 2204. In step 2204, the routine determines whether the indicated user account operation is to edit an existing user account. If so, the routine continues to step 2205, otherwise it continues to step 2206. In step 2205, the routine edits the user's account settings as indicated. Such account settings may include payment options such as movie titles and / or movie categories, credit card information and / or bank account numbers, telephone numbers, addresses, and / or electronic Preferences related to contact information such as email addresses can be included.

  In step 2206, the routine determines whether the indicated user account operation is to delete an existing account. If so, the routine continues to step 2207 to delete the indicated user's account, otherwise proceeds to step 2208 to perform other indicated actions as appropriate. Other actions include, for example, performing periodic housekeeping operations (eg, log rotation), confirmations (eg, for account operations and / or transaction completion) and / or updates (eg, newly available) To the user).

  After steps 2203, 2205, 2207, and 2208, the routine continues to step 2209 and determines whether to continue processing other operations. If so, the routine returns to the beginning of the loop in step 2201. Otherwise, the routine terminates or otherwise enters a wait state waiting for the next operation.

  FIG. 23 is an exemplary flow diagram of an exemplary transaction management routine provided by an exemplary embodiment of a media transaction network portal. The routine can be provided, for example, in the media transaction management engine 2001 of MTNP 2000 of FIG. The transaction management routine executes a loop in steps 2301 to 2309 and executes or starts execution of the indicated transaction as appropriate.

  More specifically, at step 2301, the routine determines or receives an indication of a media transaction. In step 2302, the routine determines whether the indicated media transaction is a media title search request. If so, the routine proceeds to step 2303, executes a search, and outputs a media title instruction that matches the given search conditions. Otherwise, the routine continues to step 2304 to determine whether the indicated media transaction licenses or purchases the media and / or media-related goods and services. If so, the routine continues to step 2305, otherwise it continues to step 2306. At step 2305, the routine processes the indicated media and / or goods and / or service transactions as appropriate. This may include performing a licensing transaction to obtain the indicated media rights or to provide money or other valuable items in exchange for the indicated goods and services. The routine, in some embodiments, may be interoperable with a third party payment processor in processing financial transactions.

  At step 2306, the routine determines whether the indicated media transaction is to get media. If so, the routine continues to step 2307 and begins providing the indicated media, otherwise it continues to step 2308. Initiating provision of such media may include streaming the indicated media delivery to the requesting DIVTS, or otherwise initiating the delivery in some other way, such as media server 2004 of FIG. Commanding or otherwise informing the other components.

  At step 2308, the routine performs other indicated actions as appropriate. Other actions include, for example, performing periodic housekeeping operations (eg, log rotation), confirmations (eg, for transaction completion) and / or updates (eg, delivery or shipment of purchased items on MTNP) Notification) to the user. After steps 2303, 2305, 2307, and 2308, the routine continues to step 2309 and determines whether to continue processing. If so, the routine returns to the beginning of the loop at step 2301 to process the additional transaction. Otherwise, the routine ends.

  FIG. 24 is an exemplary flow diagram of an exemplary device independent video transaction system delivery routine provided by an exemplary embodiment of a media transaction network portal. Such a routine can be provided in, for example, the DIVTS distribution engine 2003 of FIG. At steps 2401-2407, the DIVTS delivery routine executes a (potentially continuous) loop to provide a DIVTS instance configured to execute on the requesting device.

  Specifically, in step 2401, the routine receives a request from the target system for DIVTS. At step 2402, the routine determines the target system configuration. In some embodiments, the request received at step 2401 can include a description of the target system. The description of the target system can include information related to the hardware and / or software configuration of the third party entertainment device on which the DIVTS is installed. In step 2403, the routine determines whether a compatible DIVTS is available, if so, continues to step 2405, otherwise continues to step 2404. The routine can make this determination by examining the target system configuration as determined in step 2402 and determining if a DIVTS that matches the determined target system configuration has already been generated. Alternatively, the routine can automatically determine the target system by executing some test instructions that respond from the device.

  If it is determined that a compatible DIVTS is not available, the routine continues to step 2404. At step 2404, the routine automatically generates a DIVTS based on the target system configuration. The automatically generated DIVTS can also be stored for later retrieval by the same type of target device. This step includes automatically compiling and / or linking pre-existing source and / or object modules to create a DIVTS instance that is running and / or compatible on the target system. be able to.

  Instead, if it is determined in step 2403 that a compatible DIVTS is already available, the routine proceeds to step 2405 and obtains a compatible DIVTS. Obtaining a compatible DIVTS can include accessing a DIVTS repository, such as the DIVTS repository 2005 described further with respect to FIG.

  After steps 2405 and 2404, the routine continues to step 2406 and sends the determined DIVTS instance to the requesting system. In step 2407, the routine determines whether to continue processing, and if so, returns to the beginning of the loop in step 2401. Otherwise, the routine ends.

  From the foregoing description, it will be understood that although specific embodiments have been described herein for purposes of illustration, various modifications may be made without departing from the spirit and scope of the disclosure. For example, the methods and systems for performing media-related transactions described herein are applicable for different uses than video-related transactions. Further, the methods and systems described herein include different protocols, communication media (optical, wireless, cable, etc.) and devices (wireless handsets, electronic organizers, personal digital assistants, portable email devices, game consoles, pagers) It can be applied to navigation devices such as GPS receivers.

FIG. 3 is an exemplary block diagram of an exemplary embodiment of a device independent video transaction system that resides on a third party device. FIG. 3 is an exemplary block diagram illustrating an overview of an exemplary process that provides the functionality of a device independent video transaction system. FIG. 3 is an exemplary network diagram illustrating a network of median transactions. FIG. 3 is an exemplary block diagram of components of an exemplary embodiment of a device independent video transaction system. FIG. 3 is an exemplary block diagram of a “quilt” user interface provided by an exemplary embodiment of a device independent video transaction system. FIG. 6 is an exemplary state diagram illustrating navigating in an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. 2 is an exemplary screen display of various “panels” of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. 2 is an exemplary screen display of various “panels” of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. 2 is an exemplary screen display of various “panels” of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. 2 is an exemplary screen display of various “panels” of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. 2 is an exemplary screen display of various “panels” of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. 3 is an example flow diagram of an example user interface routine provided by an example embodiment of a device independent video transaction system. 3 is an example flow diagram of an example media transaction routine provided by an example embodiment of a device independent video transaction system. 4 is an exemplary flow diagram of an exemplary media search routine provided by an exemplary embodiment of a device independent video transaction system. 3 is an exemplary screen display of a search panel of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. 3 is an exemplary screen display of a search panel of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. 3 is an exemplary screen display of a search panel of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. 3 is an exemplary screen display of a search panel of an exemplary quilt user interface provided by an exemplary embodiment of a device independent video transaction system. FIG. 6 is a categorization graph representing an exemplary categorization of a number of exemplary media titles. FIG. 6 is a Venn diagram representing an exemplary categorization of a number of exemplary media titles. FIG. 6 is a Venn diagram representing an exemplary categorization of a number of exemplary media titles. 3 is an example flow diagram of an example media acquisition routine provided by an example embodiment of a device independent video transaction system. 4 is an exemplary screen display of media obtained by an exemplary quilt user interface of an exemplary embodiment of a device independent video transaction system. 3 is an exemplary flow diagram of an exemplary media publishing routine provided by an exemplary embodiment of a device independent video transaction system. 1 is an exemplary block diagram of a general purpose computer system for implementing an exemplary embodiment of a device independent video transaction system. FIG. 1 is an exemplary block diagram of an exemplary embodiment of a device independent video transaction system implemented on a third party entertainment device. FIG. 3 is an exemplary flow diagram of an exemplary dispatcher routine provided by an exemplary embodiment of a device independent video transaction system. FIG. 3 is an exemplary block diagram of components of an exemplary embodiment of a media transaction network portal. FIG. 2 is an exemplary block diagram of a general purpose computer system for implementing an exemplary embodiment of a media transaction network portal. 3 is an exemplary flow diagram of an exemplary user management routine provided by an exemplary embodiment of a media transaction network portal. 3 is an exemplary flow diagram of an exemplary transaction management routine provided by an exemplary embodiment of a media transaction network portal. 3 is an exemplary flow diagram of an exemplary device independent video transaction system delivery routine provided by an exemplary embodiment of a media transaction network portal.

Claims (80)

A device independent media transaction system that resides on a single computing device,
A unified mechanism that runs on the single computing device, specifies the media to be acquired, determines the destination for presentation of the acquired media, and initiates a transaction related to the specified media. A user interface configured to present;
A media acquisition component configured to eject media specified via the user interface;
A media presentation component configured to present the retrieved media;
A device independent media transaction system comprising: a transaction component configured to execute a transaction related to the designated media.   The device independent media transaction system of claim 1, wherein the device independent media transaction system is a device independent video transaction system.   The single computing device is at least one of a desktop computing system, a laptop computing system, a set-top box, a gaming system, a palmtop computing system, or a mobile phone. Item 2. The device independent video transaction system according to Item 1.   The device-independent media transaction system according to any one of claims 1 to 3, wherein the designated media includes digital video data and / or digital audio data.   5. The device independent media transaction system of any one of claims 1 to 4, wherein the designated media resides on a computer readable media storage device of the computing device.   The media presentation component is further configured to display a digital video frame associated with the retrieved media on a display device coupled to the single computing device. 6. The device independent media transaction system according to any one of 1 to 5.   The transaction related to the designated media includes initiating payment of money in exchange for obtaining a right to present the designated media. A device independent media transaction system as described in the paragraph.   8. The transaction related to the designated media includes initiating payment of money in exchange for goods and / or services related to the designated media. A device independent media transaction system as described in the paragraph.   The transaction related to the specified media initiates a search for media titles that match one or more indicated categories and matches at least one of the one or more indicated categories Receiving at least one media title indication. 9. The device independent media transaction system of claim 1, further comprising:   The device-independent media transaction system according to any one of claims 1 to 9, wherein the transaction related to the designated media includes obtaining meta-information related to the designated media. .   The device independent media transaction system of claim 10, wherein the meta information includes at least one of a review, an image, a preview, a summary, or a synopsis.   A media publishing component configured to send the designated media to the media receiving device, wherein the user interface comprises a mechanism for designating the media to be published; 12. A device independent media transaction system according to any one of the preceding claims, wherein the device independent media transaction system communicates to a media issuing component.   The device-independent media transaction system of claim 12, wherein the transmission of the designated media includes providing an indication of a network location of the designated media.   14. The device independent media transaction system of at least one of claims 12 or 13, wherein the designated media resides on the single computing device.   15. The device independent media transaction system of at least one of claims 12 to 14, wherein the designated media resides on a computing device that is remote from the single computing device. A method on a single computing device for performing a media transaction comprising:
Executing on the single computing device, specifying the media to be acquired, initiating a transaction related to the specified media, acquiring the specified media, and presenting the acquired media Providing a user interface that presents the user with a unified mechanism for
Under control of the user interface,
Specify the media to be retrieved,
Initiating a transaction related to the specified media;
Obtaining the specified media from a media source;
Presenting the acquired media on a display device coupled to the single computing device.   The method of claim 16, wherein the designated media includes digital video data.   18. At least one of claims 16 or 17, wherein presenting the acquired media includes displaying a digital video associated with the acquired media on the display device. the method of.   19. At least one of claims 16-18, wherein the transaction related to the designated media includes initiating a payment of money in exchange for obtaining a right to present the designated media. The method described in 1.   20. At least one of claims 16-19, wherein the transaction related to the designated media includes initiating a settlement of money in exchange for goods and / or services related to the designated media. The method described in 1.   The transaction related to the specified media initiates a search for media titles that match one or more indicated categories and matches at least one of the one or more indicated categories 21. A method according to at least one of claims 16 to 20, comprising receiving an indication of at least one media title.   The transaction related to the specified media includes obtaining meta information related to the specified media, the meta information including at least one of a review, an image, a preview, a summary, and a synopsis. 22. A method according to at least one of claims 16-21.   The unifying mechanism further issues the designated media to a media receiving device, and communicates at least a portion of the designated media to the media receiving device under control of the user interface. 23. A method according to at least one of claims 16 to 22, characterized in that it is a mechanism for publishing recorded media to the media receiving device.   The user interface is a representation of a quilt with a plurality of panels, each panel invoking at least one of a plurality of functions of the media transaction system in response to a determined user input event 24. A method according to at least one of claims 16 to 23.   25. Content capable of operating a single computing device as a media transaction system in accordance with the steps of any one of claims 1 to 24, otherwise incapable of performing transactions on the media A computer-readable medium comprising: A method in a single computing device for interacting with a user operating a media transaction system installed on said single computing device, comprising:
Generating a representation of a quilt comprising a plurality of panels, each panel connected to at least one other panel of the plurality of panels and calling at least one of a plurality of functions of the media transaction system Having at least one associated action to start
Identifying one of the plurality of panels as a current panel;
Presenting the current panel;
In response to the received input event, initiate execution of the at least one action associated with the current panel, the action determining a selected media, and a transaction related to the selected media. Performing or relating to at least one of presenting a portion of the selected media.   The method of claim 26, wherein the received input event is at least one of an upper event, a lower event, a left event, a right event, or a selection event.   The received input event is a direction input event having an associated direction, the current panel is connected to one of the plurality of panels in the associated direction, and the one panel is the receiving 28. A method according to at least one of claims 26 or 27, wherein the method is presented as a response to an incoming event.   29. A method according to at least one of claims 26 to 28, wherein presenting the current panel comprises animating a transition from a previous current panel to the current panel.   Animating the transition from the previous current panel to the current panel includes shifting the previous current panel from a viewport and shifting the current panel into the viewport. 30. The method of claim 29, wherein:   Shifting the previous current panel from the viewport and shifting the current panel into the viewport results in a perception of a smooth transition from the previous panel to the current panel. 32. The method of claim 30, comprising.   32. A method according to at least one of claims 29 to 31, wherein the animating transition from the previous current panel to the current panel further comprises a scaling or panning operation.   The action associated with at least some of the plurality of panels is to select a category of media title, the received input event is a first selection event, and a first of the media title 33. The method of at least one of claims 26 to 32, wherein a category is selected as a response to receiving the first selection event.   The received input event is a second selection event, a second category of media title is selected as a response to the second selection event, and the selected first category and the selected The method of claim 33, comprising presenting a media title search result based at least in part on the second category.   The selected first category includes one or more media titles, the selected second category includes one or more media titles, and the media title search includes the selected 35. The method of claim 34, comprising performing a cross-set operation of a first category media title and the selected second category media title.   A first panel of the plurality of panels is associated with the first selection event, a second panel of the plurality of panels is associated with the second selection event, and the second panel Displaying the second panel by overlaying the first panel on top of the first panel and presenting instructions indicating that the first panel is below the second panel 36. A method according to claim 34 or 35, wherein:   37. A method according to at least one of claims 33 to 36, wherein at least some of the plurality of panels are automatically generated based at least in part on a data structure representing a category of media.   27. The presented current panel includes a plurality of instructions for media categories, at least one of the instructions being highlighted as a response to the received input event. 38. The method according to at least one of 37.   The plurality of panels of the quilt representation appear to be laid out on a single plane, further comprising presenting the current panel from an orientation perpendicular to the quilt representation, thereby orthogonal to the plane of the quilt representation 39. A method according to at least one of claims 26 to 38, comprising displaying the current panel with perspective.   40. The method of at least one of claims 26 to 39, further comprising using a viewport to present one or more of the plurality of panels.   41. The viewport supports an operation of zooming in and / or zooming out to display each of the plurality of panels reduced or increased in response to the received input event, respectively. the method of.   Presenting the selected piece of media includes initiating display of the selected piece of media on a display device coupled to the single computing device. 42. A method according to at least one of claims 26 to 41.   43. A method according to at least one of claims 26 to 42, wherein the media transaction system is a video transaction system.   44. At least presenting the current panel comprises initiating display of the current panel on a display device coupled to the single computing device. 2. The method according to item 1.   45. The method of at least one of claims 26 to 44, wherein the received input event is received from a user input device communicatively coupled to the single computing device.   46. A method according to at least one of claims 26 to 45, wherein the user input device is at least one of a joystick, a mouse, a pointing device, a remote controller, a button or a keyboard.   The single computing device is at least one of a desktop computing system, a laptop computing system, a set-top box, a gaming system, a palmtop computing system, or a mobile phone. 47. A method according to at least one of items 16 to 24 or 26 to 46.   48. A single computing device interacts with a user operating a media transaction system installed on the single computing device according to the steps of any one of claims 26 to 47. A computer-readable medium having contents that enable the above-described contents. A graphical user interface that allows a user operating a media transaction system installed on a single computing device to interact with the single computing device,
An array of panels that together present a quilt metaphor, each panel connected to at least one other panel of the plurality of panels, each panel having a plurality of functions of the media transaction system An array of panels having at least one associated action that invokes at least one of
Initiating execution of the action associated with the identified panel in response to a received input event associated with the identified panel, the action determining the selected media, the selected A dispatcher configured to relate to at least one of executing a transaction related to the selected media or presenting a portion of the selected media;
A display mechanism configured to present at least the identified panel in response to an instruction from the dispatcher by animating a smooth transition from the previously presented panel to the identified panel. A graphical user interface characterized by that. A method of operating a media transaction portal,
Providing a third party computing device with a device independent media transaction system executing on the third party computing device, wherein the media transaction system specifies the media to be acquired and directs the presentation of the acquired media; Being configured to have a user interface for initiating transactions involving specified media;
Receiving an indication of a transaction related to a specified media item from the device independent media transaction system executing on the third party device;
Initiating a designated transaction relating to the designated media item;
Providing a transaction result to the device independent media transaction system.   51. The method of claim 50, wherein the device independent media transaction system is a device independent video transaction system.   52. The method of at least one of claims 50 or 51, wherein the method is performed by one or more server computing systems.   53. A method according to at least one of claims 50 to 52, wherein providing the device independent media transaction system is performed by a device independent media transaction system distribution server.   54. At least one of claims 50-53, wherein receiving the indicated transaction, initiating the indicated transaction, and providing the transaction result is performed by a media transaction management server. The method described in 1.   The received and directed transaction is received from at least one of a desktop computing system, a laptop computing system, a set-top box, a gaming system, a palmtop computing system, or a mobile phone. 55. A method according to at least one of claims 50 to 54.   56. A method according to at least one of claims 50 to 55, wherein the indicated transaction is to initiate a settlement of money in exchange for the right to view the designated media item.   The indicated transaction is to perform a media catalog search based on one or more indicated conditions, and initiating the indicated transaction performs the media catalog search to execute the media catalog search. Obtaining a search result including at least one indication of a media item that matches one or more indicated conditions, and wherein the provided transaction result includes the search result. 57. A method according to at least one of 50 to 56.   58. At least one of claims 50 to 57, wherein the indicated transaction is to initiate a settlement of money in exchange for goods and / or services related to the specified media item. Method.   59. A method according to at least one of claims 50 to 58, wherein the indicated transaction is to obtain meta information relating to the specified media item.   The meta information includes at least one of a review of the designated media item, a summary of the designated media item, an evaluation of the designated media item, or an image from the designated media item. 60. The method of claim 59.   61. The method of at least one of claims 50-60, further comprising facilitating the publication of a media item specified by the device independent media transaction system.   Facilitating the issuance of the designated media item further includes determining a network location of the designated media and providing the network location to a second device independent media transaction system. 62. The method of claim 61, wherein:   Facilitating the issuance of the designated media item includes obtaining at least a portion of the designated media item from the device independent media transaction system and obtaining at least a portion of the designated media item. 64. The method of claim 61 or 62, further comprising providing to two device independent media transaction systems.   64. The method of at least one of claims 50 to 63, wherein providing the device independent media transaction system comprises receiving a request for a device independent media transaction system from the third party computing device. .   The method of at least one of claims 50 to 64, wherein the indicated transaction is to perform a user account operation for a specified user associated with the device independent media transaction system. .   The user account operation includes opening a new account for the specified user, closing the account for the specified user, updating the contact information for the specified user, payment for the specified user. 66. The method of claim 65, comprising at least one of updating information or updating the specified user's media preferences. Distributing video to a third-party device that is otherwise incapable of performing video-related transactions and facilitating the operation of the third-party device as part of a media transaction network,
Providing each of the third party devices with a device independent video transaction system executing on the third party computing device, thereby executing a transaction related to video;
Establishing a payment mechanism for multiple users associated with the third party device to perform electronic transactions involving multiple video titles;
The payment mechanism is used to facilitate a plurality of electronic transactions from the third-party device, each transaction being included in the plurality of users to obtain at least one of the plurality of video titles. Being started by one person,
After receiving notification that one of the facilitated transactions has been completed,
Initiating delivery of the at least one acquired video title to one of the corresponding devices;
Receiving compensation from the provider of the acquired video title.   Further comprising facilitating a plurality of product transactions using the payment mechanism, wherein each transaction is for the plurality of users to purchase products related to at least one of the plurality of video titles. 68. The method of claim 67, wherein the method is initiated by one of them. After receiving notification that one of the facilitated product transactions has been completed,
Initiating delivery of at least a portion of the purchased item;
69. The method of claim 68, further comprising receiving compensation for at least a portion of the purchased item from a provider.   70. The method of at least one of claims 67 to 69, wherein the established payment mechanism comprises a payment system that facilitates the money transfer.   The method of claim 70, wherein the payment system comprises an electronic funds payment system.   72. At least one of claims 67 to 71, wherein the payment mechanism includes a rental plan that facilitates the money transfer in exchange for the right to obtain one or more video titles for limited use. The method described.   The method of claim 72, wherein the limited use is at least one of a specified time or number of views.   74. A method according to claim 72 or 73, wherein the limited use is the number of devices that can be used to view the one or more video titles.   75. A method according to at least one of claims 67 to 74, wherein the method is performed by a computing system operating on behalf of a provider.   76. The method of at least one of claims 67 to 75, wherein the device independent video transaction system comprises a user interface with a trade dress brand associated with the provider.   77. A computer readable medium comprising content capable of operating a computing system as a media transaction network portal according to the steps of any one of claims 50 to 76 of the method.   78. The computer readable medium of claim 25, 48, or 77, wherein the computer readable medium is a memory of a computing system.   78. The computer readable medium of at least one of claims 25, 48, or 77, wherein the computer readable medium is a data transmission medium that transmits a generated data signal including the content.   78. The computer-readable medium of claim 25, 48, or 77, wherein the content is instructions that when executed cause the computing system to perform the method.

Images