HK1177273A - Persistent media playback - Google Patents

Description

Persistent media playback

Background

Online digital media stores are becoming more popular. The online digital media store may be configured as a website that allows consumer users to purchase various digital media such as music, videos, games, podcasts, audiobooks, applications, and so forth. Typically, a customer browses digital media available on various web pages within an online digital media store website. For example, a user may access descriptive material (e.g., title, artist information, album art, etc.) that describes content of digital media that may be purchased and/or downloaded by the user. In some cases, the user may further access previews of digital media. The user may then purchase and/or download files containing the selected digital media over a network, such as the internet, to a client device associated with the user, such as a digital media player, mobile phone, computer, or the like. The user may then play the digital media using the client device.

Disclosure of Invention

Persistent media playback techniques are described. In one implementation, a media player is served over a network for display by a browser of a device. One or more web pages may then be served over the network for display with the media player through the device's browser. The web page is configured to integrate with the media player so that the media player is persistently displayed by the browser. The media player may be configured to play media files that provide a variety of different media types. The media player may also be configured to provide context-related information during playback of the media.

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

Drawings

The detailed description describes embodiments with reference to the drawings. In the drawings, the left-most digit(s) of a reference number identifies the drawing in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items.

FIG. 1 is an illustration of an environment in an example implementation that is operable to provide persistent media playback across a Web browsing session without installation of client-side components.

FIG. 2 is a flow diagram depicting a procedure in an example implementation in which persistent media playback is provided across a Web browsing session.

FIG. 3 is a flow diagram depicting a procedure in an example implementation in which various media may be added to a queue of a persistent media player and played.

FIG. 4 is a flow diagram depicting a procedure in an example implementation in which contextually relevant information is provided during playback of media.

FIG. 5A is an illustration depicting an example persistent media player and web page.

FIG. 5B is an illustration depicting an example persistent media player and web page, wherein the persistent media player is configured to play video.

Detailed Description

Overview

Online digital media stores often allow users to play media while viewing web pages within the online digital media store website. However, users are typically limited to the media in the particular web page that the user is currently viewing. Thus, if the user navigates from a web page containing media to a different web page, the media is not available to the user and, as such, cannot be played. For example, a user may select to play a song selected from a web page in an online digital media store that provides music. The user may then navigate to a webpage within the store that provides the video, which causes playback of the selected song to stop. Previously developed techniques for addressing these problems involved installing client-side components such as browser plug-ins, which can diminish the user experience.

Techniques are described for providing persistent media playback across a Web browsing session without the need to install client-side components. In one implementation, a media player is served over a network for display by a browser of a client device. Web pages within the online digital media store website are served over the network for display by the device's browser. The web page is configured to integrate with the media player so that the browser persistently displays the media player during navigation between web pages of the website, during operations performed on the web page (e.g., scrolling), and so forth. For example, in one embodiment, the media player is configured as a web page in which subsequent web pages of the online digital media store website are presented.

In one or more implementations, a persistent media player is implemented to play media files, and the media files may be configured into a variety of different media types. Media may be selected from various web pages of the online media store website and added to and/or removed from a queue within the media player for eventual playback as the user navigates between the web pages of the website.

The persistent media player may also be configured to transmit targeted media, such as targeted marketing, content for a currently playing media item or user, and so forth. For example, the media player may be configured to provide context-based suggestions of other media. In an implementation, media may be suggested based on an analysis of the user's previous selections of media (e.g., media added to a queue of a media player), the user's profile, targeted promotions, and so forth. For example, media by the same artist or similar artists may be suggested, media of the same genre, or media selected by other users who also selected media added to the queue by the user, media that is part of a targeted promotion of media, and so forth.

In the discussion that follows, an example environment is first described that is operable to provide persistent media playback across a Web browsing session. Example procedures are then described which may be used in the example environment and in other environments without departing from the spirit and scope of the present invention.

Example Environment

FIG. 1 illustrates an environment 100 in an example implementation that is operable to provide persistent media playback across a Web browsing session without installation of client-side components. The illustrated environment 100 includes a server 102 operable by a service provider, and a client device 104 associated with a client of the service provider. As shown, the server 102 and the client device 104 may be configured to communicate over a network 106.

The server 102 may be configured in various ways. In one implementation, server 102 may be an Application Service Provider (ASP) that may be used to provide services to client device 104. For example, the service provider may operate an online media store, and the server 102 may be configured to provide an online media store website to clients of the service provider.

The client device 104 may also be configured in a variety of ways. For example, the client device 104 may be configured as a computer, such as a desktop or laptop computer, capable of communicating over a wired or wireless network. Client device 104 may also be configured as a mobile connected device such as a digital media player, personal digital assistant, smart phone, or cellular telephone capable of communicating over a wireless network; an entertainment device; a set top box communicatively coupled to a display device; game consoles, and the like. As such, the client device 104 may range from a full resource device with substantial memory and processor resources (e.g., a personal computer, a game console, etc.) to a relatively low-resource device with limited memory and/or processing resources (e.g., a mobile phone, a netbook, a set-top box, etc.).

The network 106 may assume a variety of configurations. For example, the network 106 may include the internet, a Wide Area Network (WAN), a Local Area Network (LAN), a wireless network (e.g., a WIFI (IEEE802.11) network), a cellular telephone network, a public telephone network, an extranet, an intranet, and so forth. Further, although only a single network 106 is shown, the network 106 may be configured to include multiple networks. For example, a desktop or laptop computer may be connected to the Internet through a local area network so that the computer's Web browser may access Web pages provided by Web sites within the World Wide Web (WWW). Similarly, a mobile browser in a smart phone may access a web page within a corporate intranet through a cellular telephone network. Various other scenarios are also contemplated.

In fig. 1, the server 102 and the client device 104 are shown to include respective processors 108, 110; respective memories 112, 114; and corresponding network interfaces 116, 118. In the following discussion, elements of server 102 are described with reference to FIG. 1. Corresponding elements and/or reference numbers associated with the client device 104 are shown in parenthesis. Where appropriate, elements of client device 104 are described separately.

The processor 108(110) provides processing functionality for the server 102 (client device 104) and may include any number of processors, microcontrollers, or other processing systems, as well as resident or external memory for storing data and other information accessed or generated by the server 102 (client device 104). Processor 108(110) may execute one or more software programs that implement the techniques described herein. The processor 108(110) is not limited by the materials used to fabricate it or the processing mechanisms used therein, and as such, may be implemented by semiconductors and/or transistors (e.g., electronic Integrated Circuits (ICs)), and so forth.

Memory 112(114) is an example of a computer-readable storage medium that may provide storage functionality to store various data associated with the operation of server 102 (client device 104), such as the software programs and code segments mentioned above, or other data that instruct processors 108(110) and other elements of server 102 (client device 104) to perform the steps described herein. Although only a single memory 112(114) is shown, various types and combinations of memories may be used. The memory 112(114) may be integrated with the processor 108(110), a separate memory, or a combination of both. The memory may include, for example, removable and non-removable memory elements such as RAM, ROM, flash memory (e.g., SD cards, micro SD cards), magnetic, optical, USB memory devices, and so forth. In embodiments of the client device 104, the memory 114 may comprise removable ICC (integrated circuit card) memory provided, for example, by a SIM (subscriber identity module) card, USIM (universal subscriber identity module) card, UICC (universal integrated circuit card), or the like.

Network interface 116(118) provides functionality to allow server 102 (client device 104) to communicate with one or more networks, such as network 106. In various implementations, network interfaces 116(118) may include various components, such as modems, routers, wireless access points, cellular telephone transceivers, and the like, as well as any associated software used by these components, such as drivers, configuration software, and the like. In fig. 1, network interface 116(118) is shown as an internal component of server 102 (client device 104). However, in some implementations, one or more components of the network interface 116(118) may be external components coupled to the server 102 (client device 104) through a wired or wireless connection.

The client device 104 may also include a browser 120 that may be implemented as a software application stored in the memory 114 and executed by the processor 110 of the client device 104. Browser 120 allows client device 104 to display and interact with web pages provided by server 102. Browser 120 may be configured in various ways. For example, the browser 120 may be configured to be suitable for use with full resource devices with substantial memory and processor resources, such as a Web browser for a personal computer, laptop computer, game console, and so forth. In other implementations, the browser 120 may be configured as a mobile browser suitable for low-resource devices (e.g., PDAs, smart phones, cellular phones, etc.) with limited memory and/or processor resources. Such a mobile browser may be configured to conserve memory and processor resources, for example, but may provide less browser functionality than a full-function Web browser.

As shown in fig. 1, the server 102 may include a media player module 122 that may be implemented as a software application stored in the memory 112 and executed by the processor 108 of the server 102. The media player module 122 represents functionality to provide persistent media playback across a Web browsing session without the need to install client-side components. In one implementation, the media player module 122 is configured as a media player 124 served by the server 102 over the network 106. Web pages 126 within a website, such as an online digital media store website 128, may be served over the network 106 for display by the browser 120 of the client device 104 in conjunction with the media player 124. The media player module 122 integrates the web pages 126 with the media player 124 such that the media player 124 is persistently displayed by the browser 120 during a browsing session, e.g., during navigation between the web pages 126 of the website 128. In embodiments, the media player 124 is configured as a web page in which subsequent web pages 126 of the online digital media store website 128 are presented. For example, the browser 120 may display each web page 126 with a media player 124, and the media player 124 may be displayed as a fixed toolbar. An example media player 124 is shown in fig. 5 and 6.

In implementations, the media player 124 is configured to play media files, and the media files may be configured to a variety of different media types. Example media types include audio (e.g., music, talk, soundtrack, audio podcasts, etc.), video (e.g., movies, video podcasts, etc.), games, software applications, and so forth. Media may be selected from one or more of the web pages 126 of the online media store website 128 and added to and/or removed from a queue within the media player 124 for eventual playback as the user navigates between the web pages 126 of the website 128.

The media player module 122 may further represent functionality to provide rich and context-specific discovery during playback that allows for the provision of targeted media, e.g., targeted marketing, content for a currently playing media item or user, and so forth. In an implementation, the media player module 122 generates relevant media suggestions based on the applicable context, such as through analysis of the user's selection of media to be added to the queue of the media player 124. For example, media may be suggested for performance by the same artist or similar artists, media of the same genre, or media selected by others who also selected media added to the queue by the user, and so on. Further discussion of persistent media playback may be found in the discussion that follows.

Generally, any of the functions or techniques described herein can be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations. The terms "module" and "functionality" as used herein generally represent software, firmware, hardware, or a combination thereof. For example, in the case of a software implementation, the modules represent executable instructions that perform specified tasks when executed on processors, such as the processors 108, 110 of the server 102 and client device 104 of FIG. 1, respectively. The program code can be stored in one or more tangible computer-readable media, examples of which include respective memories 112, 114 of the server 102 and client devices 104 of FIG. 1. The features of the techniques described below are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.

Example procedure

The following discussion describes processes that implement techniques for providing persistent media playback across a Web browsing session without the need to install client-side components. Aspects of the processes may be implemented using hardware, firmware, software, or a combination thereof. The procedures are shown as a set of blocks that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In some portions of the following discussion, reference will be made to environment 100 of FIG. 1.

FIG. 2 depicts a procedure 200 in an example implementation in which persistent media playback is provided across a Web browsing session. As shown, a request to navigate to a web page of a website is received (block 202). In an implementation, a request is received to navigate to a webpage 126 of an online media store website 128 to access media available from the website through the webpage 126. For example, a user may use the browser 120 of the user's client device 104 to access the website 128, e.g., by entering a Uniform Resource Locator (URL) for a web page 126 within the website 128, by selecting a link to a web page 126 within the website 128, and so forth.

The persistent media player is then served (block 204). For example, the media player 124 may be hosted by a server 102 associated with an online media store website 128. In one or more embodiments, the persistent media player is implemented as a web page that uses one or more hypertext markup language (HTML) documents configured to facilitate interaction with a user to provide playback of the media.

The requested web page is then served (block 206). As shown, a web page may be retrieved (block 208) and integrated with a persistent media player (block 210) such that the media player is persistently displayed with the web page. For example, the requested web page may be retrieved and inserted into a media player that is configured as another web page. In this way, operations that manipulate data within other web pages (e.g., media players) may be performed on the web page. In this manner, the media player remains accessible through the browser.

The process 200 may be repeated when the user requests to navigate to other web pages 126 of the website 128. Thus, during a browsing session, for example, during navigation between web pages 126 of web site 128. For example, the user may use browser 120 to navigate to a second web page 126 within website 128, e.g., by entering a URL of web page 126, selecting a link to web page 126, using navigation controls provided by browser 120, and so forth. The process 200 is then repeated so that the second web page 126 may be displayed with the media player 124, with the media player 124 remaining persistent within the browser display, e.g., the media player 124 remains at least substantially unchanged in appearance, size, and position within the display when the second web page is opened.

In one implementation, the web page 126 is inserted into an existing media player 124 when served. In this manner, the media player 124 may be served (block 204) less frequently than other web pages 126 of the website 128, e.g., once during a browsing session, each time a particular web page such as "home page" is accessed, at predetermined intervals, etc. In other implementations, the persistent media player is served each time a web page 126 within the website 128 is accessed (block 204). In this manner, the media player 124 is refreshed each time the web page 126 is accessed.

FIG. 3 depicts a procedure 300 in an example implementation in which various media may be added to a queue of a persistent media player. As shown, media may be added to a queue of a persistent media player (block 302) to cause the media to be played by the media player (block 304).

In an implementation, a media selection is received (block 306) identifying media to be added to a queue (block 306). For example, the user may select media to be added to the queue from the web pages 126 of the online media store 128. The selected media may be added to the queue (block 308).

The media added to the queue may be further reorganized within the queue (block 310). For example, media may be first queued within the queue in the order in which the media was initially added to the queue. Thereafter, the order of playback of the media may be changed so that the media is played in an order different from the order in which the media was added to the queue. For example, a user may wish to play a media item added to the queue before playing other media items within the queue when the media item was added. To do so, the user may reorganize the media items within the queue, for example, by dragging and dropping the media items in a desired order. In addition, media may be removed from the queue so that the media is not played. For example, the user may delete media items from the queue that the user no longer wishes to play, e.g., by dragging and dropping the media items out of the media player.

Additional media may be queued and organized as additional media selections are received, as illustrated by the loop shown for block 306-310 in fig. 3. The media is then played in the queued order (block 304) until the media player is turned off. In this way, the user may navigate among the web pages 126 of the website 128 without stopping playback of the media.

FIG. 4 illustrates a procedure 400 in an example implementation in which contextually relevant information is provided during playback of media by a persistent media player. The process 400 provides for integration of the media player 124 with related media discovery capabilities to provide contextual discovery during a playback experience. As shown, contextually relevant suggestions of information are made (block 402), such as additional media of interest to the user, and so forth. In an implementation, a relevant context that is used to select media to include in a suggestion is first determined (block 404). For example, the user may view a prompt displayed in the media player 124 to identify a context for selecting media. Media may then be selected according to the determined context (block 406) and included in the suggestion made to the user (block 408).

The media may be determined to be relevant in accordance with the determined context in a number of ways. For example, media relevance may be determined based on media currently being played by the media player 124, media in a queue of the media player 124, identified as relevant by the user (e.g., directly and/or indirectly based on a user profile), part of a targeted promotion, and so forth.

A response to the media suggestion may be received from the user (block 410). Various user responses are envisioned. For example, the user may decide to select suggested media for addition to the queue of the media player 124 for playback, ignore suggestions, delete suggestions, and so forth. When the user's response is to select suggested media for addition to the queue of the media player 124 for playback, the suggested media is added to the queue of the media player (block 412).

Example media Player

This section presents elements of a media player that can be generated to provide persistent media playback across a Web browsing session. Aspects of the media players may be generated by hardware, firmware, software, or a combination thereof. In some portions of the following discussion, reference will be made to the environment 100 of FIG. 1; refer to processes 200, 300, and 400 of fig. 2, 3, and 4, respectively; and/or other example environments and processes.

Fig. 5A and 5B illustrate a display 500 of the browser 120 including an example media player 124 and a web page 126. As shown, the media player 124 may be configured to persistently display a taskbar 502 (FIG. 1) in a display 500 of the browser 120. In fig. 5A and 5B, the taskbar 502 is illustrated as being positioned adjacent to the bottom of the browser display 500, e.g., below the displayed web page 126. However, it is contemplated that the taskbar 502 may be displayed in any portion of the browser display 500 (e.g., at the top of the display 500, on a side of the display 500, etc.), may be movable within a web page (e.g., as a persistent pop-up display), and so forth. Controls (e.g., tabs 504 and 506) may be provided to provide functionality such as moving the taskbar 502, hiding the taskbar 502, resizing the taskbar 502, and the like. Further, the taskbar 502 may be configured to appear integrated with the web page 126. For example, the web page 126 may include elements such as frames, colors, textures, combinations of these elements, and so forth, that are configured to be consistent with similar elements of the web page 126.

The taskbar 502 may include various sections that provide functionality to facilitate persistent media playback across a Web browsing session without the installation of client-side components. For example, in fig. 5A and 5B, the illustrated taskbar 502 includes a transfer control section 508, a queue section 510, and a context discovery section 512.

In various embodiments, the transport control segment 508 provides functionality for controlling playback of media by the media player 124. For example, the transport control segment 508 may include various transport controls 514, such as a play/pause button 516 (e.g., to start, pause, or stop playback of a media item 518), a next/fast forward button 520 (e.g., to skip or fast forward a media item 518), a previous/rewind button 522 (e.g., to replay or rewind a media item 518), sound/video quality controls 524 (e.g., equalizer display, sound mixing controls), and so forth.

The transfer control segment 508 may also include a media playback status bar 526, which media playback status bar 526 provides functionality for the status of the currently playing media item 518. The transfer control segment 508 may also be configured to allow the user to select playback to begin from a point within the media item 518 (e.g., by selecting a point within the playback status bar 526 for playback), and so forth. Various information 528 regarding the media items 518 may also be displayed. For example, information 528 may describe the title and name of the artist performing the content of media item 518, and may include indicia 530 such as album/video cover art, artist photos, and the like, associated with the media item currently being played. As shown, information 528 may be displayed with the media playback status bar 526 within the delivery control segment 508; although various other examples are also contemplated.

Fig. 5B illustrates the media player 124 as being configured for playback of a media item 518 having video content, such as a video, podcast, game, or the like. As shown, the transfer control segment 508 may be expanded to include a visual content display area 532. When the media item contains visual content (e.g., a video, a podcast, a game, etc.) to display the visual content, a visual content display area 532 may be included. In embodiments, the visual content display area 532 is dynamic so as to be hidden when visual content is not available (e.g., when the media item 518 contains audio content without video content), as shown in FIG. 5A.

The queue portion 510 provides functionality to display media queued for output by the media player 124. For example, the queue segment 510 includes a queue 534 of media items 518 to be played by the media player 124. In fig. 5A and 5B, the media items 518 within the queue 534 may be displayed as indicia 536 such as album/video cover art, title and artist, and so forth. However, it is contemplated that the media items 518 within the queue 534 may be represented in other manners, such as within a list, by animated icons, and so forth.

In implementations, the queue 534 may be configured to include media items 518 that may be configured into a variety of different media types. As such, the queue 534 may be configured to include media items 518 of a common media type (e.g., each media item 518 within the queue 534 is configured as a song), or media items 518 of various different media types, e.g., some media items 518 within the queue 534 may be configured as songs, while other media items 518 within the queue 534 may be configured as videos, podcasts, and so forth.

Media may be added to the queue 534 in a variety of ways. For example, media may be selected from the web page 126 within the browser display 500 and added to the queue 534 for playback by the media player 124. In the illustrated embodiment, the web pages 126 are provided by an online media store website 128. The web page 126 includes various media products available to the user for playback by the media player 124. To select one of the media products from the web page for inclusion in the queue 534, a "drag" icon ("+") 538 associated with the media item 518 may be selected. The media item 518 is then added to the queue 534 in response to the selection.

In one or more implementations, the media item 518 dragged from the web page is added to the left side of the queue 534 when the pluck icon 538 is selected. The media items 518 may then be moved to the right as playback of the media item 518 higher in the queue 534 is completed and/or as other media items 518 are added to the queue 534. When the media item 518 is played by the media player 124, the media item 518 is moved to the transfer control portion 508. Media queued for playback by the media player 124 may be reordered within the queue 534, for example, by dragging the reordered media items 518 to a desired position in the queue. The media item 518 may also be removed from the queue 534.

In implementations, the queue 534 remains persistent during navigation to other web pages. In this manner, a user may navigate among the various web pages 126 of the website 128 without interrupting playback of the media by the media player 124. For example, the user may select music from the first web page 126 to be included in the queue and then navigate to a second web page from which the user selects one or more videos to be included in the queue 534. Each of these selections may be made without interrupting playback of the selected media.

The context discovery section 512 provides functionality to suggest additional media that may be of interest to the user. The contextual discovery section 512 also allows for the provision of targeted media, such as targeted marketing, content targeted to the currently playing media item or user, and so forth. As shown, the context discovery section 512 includes one or more search contexts 540 (e.g., "similar artists," "friends," "queues," "popular downloads," "associated albums," etc.) upon which suggestions of information can be made. For example, the user may select the illustrated "similar artists" search context to receive suggestions of media similar to the media item 518 currently being played, the media item 518 added to the queue 534 for later playback, and so on. Suggestions can be made in a number of ways, such as displayed within the web page 126 (e.g., via a "pop-up" window), displayed within the taskbar 502, and so forth.

Conclusion

Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed invention.

Claims (14)

1. A computer-implemented method, comprising:

serving a media player over a network for display by a browser of a device, the media player configured to play media (204); and

integrating one or more web pages served over the network for display by the browser of the device with the media player such that the media player is persistently displayed by the browser during navigation between web pages (206).

2. The computer-implemented method of claim 1, wherein the media comprises at least two different types of media.

3. The computer-implemented method of claim 2, wherein the different types of media comprise audio, video, games, podcasts, or software applications.

4. The computer-implemented method of claim 1, wherein the media player includes a queue containing selected media to be played by the media player.

5. The computer-implemented method of claim 1, further comprising receiving a selection of the media from at least one of the web pages, and causing the media to be inserted into the queue.

6. The computer-implemented method of claim 1, further comprising providing context-based suggestions of additional media to be added to the queue.

7. The computer-implemented method of claim 1, wherein the media player includes integration with each of the web pages displayed by the browser.

8. A system comprising a media player module (122) configured to:

serving a media player over a network for display by a browser of a device, the media player configured to play media;

integrating one or more web pages served through the network for display by the browser of the device with the media player so that the media player is persistently displayed by the browser during navigation between web pages; and

providing context-based suggestions of additional media to be added to the queue of the media player.

9. The system of claim 14, wherein the context-based suggestion is based on media played by the media player.

10. The system of claim 14, wherein the additional media comprises at least two different types of media.

11. The system of claim 16, wherein the media type comprises audio, video, games, or software applications.

12. The system of claim 14, wherein the context-based suggested additional media is available for selection from the one or more web pages.

13. The system of claim 18, wherein the media player module is configured to receive a selection of the additional media from at least one of the web pages and cause the media to be inserted into the queue.

14. A system as defined in claim 14, wherein the media player comprises a taskbar.