BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of a mobile handset service system;
FIGS. 2A illustrates a mobile handset displaying a typical user interface for a streaming music application;
FIG. 2B shows the same mobile handset of FIG. 2A with a button to purchase a ringtone;
FIG. 2C shows the same mobile handset of FIGS. 2A and 2B with a button to purchase a music CD; and
FIG. 3 is a block diagram of a mobile handset system that allows the user to engage in e-commerce without terminating the original application that is running on the mobile handset.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
FIG. 1 depicts a typical mobile handset service system 20. The mobile handset service system 20 provide one or more services, such as movies, videos, sports information, music, etc. to a mobile handset 22 that includes a client application, such as a JAVA piece of code, that processes the incoming service data and displays the service data to the user of the mobile device. The mobile handset 22 may be any processing unit based device that is hand-sized with sufficient processing power, memory, display and connectivity capabilities to execute the client application, receive the service data and display that service data. For example, the mobile device may be a PDA, mobile phone, wireless email device (such as the Blackberry), or other handheld device. In the example shown in FIG. 1, the mobile device 22 couples to a communications link 24, such as the Internet, over a wireless network 26 and a firewall 28. The mobile handset service system 20 also has a service unit 30 that performs various function and operations for the mobile handset service system.
The service unit 30 may include a user information storage unit 32 that stores information about each user of the mobile handset service system including user billing information and user service personalization information. The service unit 30 may also have a billing server 34 that performs a billing operation for the services provided to the user. In the example shown in FIG. 1, the billing for the services are communicated over a secure link 36, such as a secure socket layer (SSL) connection, to a mobile handset carrier billing system 38 so that the mobile handset carrier can provide the bill for the services on the monthly invoice of the user of the mobile handset. Alternatively, the service unit 30 can directly bill the user. The service unit 30 may also include a live content ingester 40, a clip digester 42 and a content/asset storage unit 44 that handle the service content (such as music, movies, etc.) from a third party 46 that will be delivered by the mobile handset service system. The live content ingester receives any live content and processes it and then stores the live content in the content/asset storage unit 44 in various output encoding and file formats. The clip digester 42 receives non-live content and data, processes it and then stores the clips in the storage unit 44 in various output encoding and file formats.
The service unit 30 may further include a menu/personalization unit 48, a reporting unit 50, a streaming unit 52, a log database 54 and a data mining unit 56. The menu/personalization unit 48, the reporting unit 50, the streaming unit 52 and the data mining unit 56 may preferably each be server computers. The menu/personalization unit 48 generates and delivers the mobile handset service user interfaces to the user that may also be customized by the user based on the customization information stored in the user information storage unit 32. The streaming unit 52 may preferably support the real-time streaming protocol (RTSP) and the hypertext transfer protocol (HTTP) and may deliver/stream the service content to the mobile handset 22 over the link 24. The streaming unit 52 may request the service content from the content store 44 and may store service content information in the log store 54. The reporting unit 50 may generate a report about various aspects of the service unit and its operations. The data mining unit 56 collects user behavior information which is then mined to determine any recommendations and personalizations for users of the system.
Mobile handset 22 may include circuitry for running an operating system and applications, circuitry for processing data and metadata, and circuitry for rendering audio content and video content. All of the circuitry can be contained in a single integrated chip, in multiple integrated chips, or in a combination of some number of integrated chips and other electronic components.
FIG. 1 also shows an exemplary computing device 58 that hosts a website and/or offers products for sale. Computing device 58 connects to the Internet 24. It is to be understood that there could be an unlimited number of computing devices 58 connected to the Internet 24 in this fashion.
A user of mobile handset 22 can run various applications on the handset, such as an application that enables the user to listen to music or to watch video content streamed from streaming unit 52. In one embodiment of the invention, streaming unit 52 will send the digital content to the mobile handset 22 and will also send metadata to the mobile handset 22. The metadata can include information such as the title of the song or video, the duration of the song or video, etc. The metadata also can include information that will enable the user of mobile handset 22 to engage in e-commerce. For example, the metadata could include a URL for a website that may preferably be hosted on one or more computing devices 58 and that offers products for sale that are relevant to the content being streamed to mobile handset 22. In the alternative, the metadata could include information to be used to create a user-selectable option on the user interface of mobile handset 22 that will allow the user to purchase relevant products through a means other than a link. Examples of such products might include ringtones that contain the same music being streamed to mobile handset 22, CDs containing the same music, DVDs containing the video being streamed to mobile handset 22, etc. Mobile handset 22 receives the metadata and generates a button, menu item, link, etc. that is visible on the video display 60 of mobile handset 22 to enable the purchase of products related to the streamed content.
Referring now to FIGS. 2A, 2B, and 2C, mobile handset 22 is shown in greater detail. It is to be understood that FIGS. 2A, 2B, and 2C are exemplary and that the invention is not limited to the particular aesthetic or functional features displayed in the figures. Mobile handset 22 includes a video display 60. Mobile handset 22 includes a speaker (not shown) that generates audio content. Thus, a user of mobile handset 22 can watch video content of video display 60 and listen to audio content through a speaker.
In FIG. 2A, video display 60 shows an exemplary user interface for one embodiment of the invention. The video display 60 shows cover art for the music being streamed to mobile handset 22 by streaming unit 52. This cover art was streamed as part of the metadata associated with the music.
FIG. 2B shows a different screen within the same user interface shown in FIG. 2A. This screen might be accessed by pressing a certain button or sequence of button on the mobile handset 22, or by selecting an option on a menu. In FIG. 2B, video display 60 shows a button titled “Buy Ringtone.” If the user selects this button, mobile handset 22 will initiate an action to enable the user to buy a ringtone. For example, if the button constitutes a link, mobile handset 22 may launch an Internet browser and the browser will be directed to the URL associated with the link, such as a website hosted by computing device 58 at that URL. This URL was sent to mobile handset 22 by streaming unit 52 as part of the metadata associated with the music. Providing a URL as part of the metadata allows the user of a mobile handset to engage in e-commerce to purchase products that are related to the audio or video content that the user is listening to or watching. This transaction will not be transparent to the user, because the underlying application will need to be terminated when the browser is launched.
In the alternative, if the button shown in FIG. 2B does not constitute a link, when selected it could communicate with service unit 30 that the user wishes to purchase the relevant ringtone. Service unit 30, upon receipt of such a communication, could initiate a purchase transaction through any number of means, as discussed in greater detail below with reference to FIG. 3.
FIG. 2C shows a different screen within the same user interface shown in FIGS. 2A and 2B. This screen might be accessed by pressing a certain button or sequence of button on the mobile handset 22, or by selecting an option on a menu. In FIG. 2C, video display 60 shows a button titled “Buy CD.” When the user selects this button, the same activities will occur as discussed previously for FIG. 2B, except that instead of purchasing a ringtone, the user will purchase a CD associated with the underlying music content.
It is to be understood that a button could be replaced by another selection means, such as a soft key on mobile handset 22.
Computing device 58 and service unit 30 typically are operated by different persons or entities and their billing systems typically are not coordinated. When the user of a PC accesses a website that contains a link to a third-party commercial website, the user will be able to select a link that opens a new window in the Internet browser to access that third-party commercial website without terminating the window displaying the website that contains the link. Thus, the user of a PC can interact with multiple websites simultaneously. By contrast, the user of a mobile handset such as mobile handset 22 only will be able to access one website or run one application at a time. Thus, when the user of mobile handset 22 is listening to music being streamed by streaming server 52 and then selects a link to a URL for a website hosted by third-party server 58, the original music application will be terminated and an Internet browser will be launched to the website.
FIG. 3 shows an example of a system in which the original application on the mobile handset is not terminated when the e-commerce application is being executed. FIG. 3 depicts a coupling 62 between service unit 30 and third-party server 58. This coupling 62 can be a connection over the Internet or other network, a physical connection, or even an integration of service unit 30 and third-party server 58 into a single server or collection of servers. In this system, mobile handset 22 will display a button on the mobile handset display. The information displayed in and associated with the button were transmitted in the metadata from streaming unit 52 to mobile handset 22. When a user selects the button, instead of terminating the original application and launching a web browser, mobile handset 22 will instead communicate with service unit 30 and will indicate that the user selected the button (for example, a button titled “Buy Ringtone”). Service unit 30 then will understand that the user wishes to purchase the product associated with that button and will communicate with computing device 58 (which is the seller of such product) in a manner transparent to the user of mobile handset 22 to provide the requested product to the user and to handle billing for that transaction (for example, by directly billing the user's account with the operator of service unit 30 or the account with the mobile handset carrier, or by sending the transaction information to the operator of computing device 58 so that such operator can bill the user for the purchase) without terminating the music application. Thus, the user will be able to engage in commercial activity (e.g., the purchase of a ringtone) without disrupting the music or video application being run on mobile handset 22 at the time of the transaction. Thus, instead of directing consumers to purchase directly from a website hosted on computing device 58 (as would be the case if the selected button constitutes a link), service unit 30 instead receives the request from the user, and will coordinate with computing device 58 or other systems to fulfill the purchase request in a manner transparent to the user such that the user can continue the application.
In the alternative, if the relevant product is sold by the operator of service unit 30, then service unit 30, upon receiving the purchase request after the user selects the button, could service the request directly if configured to handle e-commerce purchases, or it could directly communicate with a computing device operated by the same operator of service unit 30 which would be no different in operation than communicating with computing device 58.
While the foregoing has been with reference to particular embodiments of the invention, it will be appreciated by those skilled in the art that changes in these embodiments may be made without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims.
Patent Application
20080033832
