The present invention is related to the field of applications. More specifically, the present invention relates to an application broker.
An app store is an online application distribution system, which allows a user to search and download any desired application. Examples of an app store include, but are not limited to, the Amazon Appstore and the Mac App Store. Although numerous app stores exist today, a single app store, however, may not have an application that the user is specifically looking for. Feeling frustrated, the user may spend more time to look for it elsewhere or simply give up. Even if the app store does have the application that the user is specifically looking for, another app store may have the same application at a lower price or for free. The user may pay more for the application than what he could have gotten the application for had the user searched elsewhere. After the user finds the application to download, the user may have to download the application to a transitory device before transferring to an ultimate device that is capable of running the application. For example, the user may have to download an application on the user's personal computer from the iTunes Store before transferring the application to the user's iPhone. Completing such a process even by a user who is tech-savvy can be time consuming, tedious and frustrating at times.
The present invention addresses at least these limitations in the prior art.
Embodiments of the present invention are directed to an application broker, which can be a program on a client device, a service in a cloud accessible by the client device or both. The client device typically runs a guest environment in a host environment. A user is able to search for an application on the application broker configured to interface with one or more application sources. In some embodiments, the application broker is able to intelligently search, download and/or install the application in the guest operating system of the client device with minimal or no user intervention. The application is typically executed in an application player associated with the guest environment. In some embodiments, the application player is configured as the application broker. In some embodiments, the application broker can provide suggested applications to download when the client device is communicatively coupled with the one or more application sources.
In one aspect, a non-transitory computer-readable medium storing instructions that, when executed by a computing device supporting a first operating system and a second operating system, cause the computing device to perform a method. The method includes receiving a search text on a broker platform configured to interface with at least one application source, and searching, using the search text, in the at least one application source. The method also includes displaying at least one application that is specific to the second operating system and based on the search text. Information of the at least one application can be displayed. One or more sources of the at least one application are not displayed. Alternatively, the one or more sources of the at least one application are displayed.
In some embodiments, the method further includes displaying one or more suggested applications. Each of the suggested applications is specific to the second operating system. The one or more suggested applications can be displayed based on a ranking methodology. The ranking methodology can be based on relatedness, importance, popularity, and listing price.
In some embodiments, the method further includes downloading and installing one of the at least one application, and executing the at least one application on the computing device in an application player associated with the second operating system. In some embodiments, the application player includes the broker platform. In some embodiments, the one of the at least one application is downloaded and installed with minimal or no user intervention.
In some embodiments, the method further includes automatically selecting an application source to download from. The automatic selection can be based on at least one factor, such as cost. In some embodiments, the method further includes displaying in the application player the downloaded and installed application. In some embodiments, the method further includes invoking a payment workflow.
In another aspect, a non-transitory computer-readable medium storing instructions that, when executed by a computing device supporting a first operating system, cause the computing device to perform a method. The method includes communicatively coupling with a source device supporting a second operating system. The source device can be a personal computer, a tablet, a mobile device, or any suitable device capable of storing data, such as applications that are specific to the second operating system. The method also includes synching at least one application that is specific to the second operating system from the source device, and displaying the at least one application in an application player. The application player includes a broker platform configured to interface with at least one application source. In some embodiments, the at least one application source is automatically pre-selected, is selected by a user of the computing device, or both. In some embodiments, the application player is associated with the second operating system.
The broker platform is configured to search for applications from the at least one application source. In some embodiments, the broker platform is configured to intelligently select an application to be downloaded from one of the at least one application source. In some embodiments, the broker platform is configured minimize user intervention during a download and installation of an application from one of the at least one application source. In some embodiments, the broker platform is configured to invoke a payment workflow.
In some embodiments, the method further includes launching the second operating system specific application from the application player. In some embodiments, the method further includes executing the second operating system specific application in the application player.
In some embodiments, the method further includes using a feature on the source device. The feature on the source device can be G.P.S., an accelerometer, a camera, a microphone or any feature on the source device.
In yet another aspect, a non-transitory computer-readable medium storing instructions that, when executed by a computing device, cause the computing device to perform a method. The method includes presenting an application broker configured to interface with at least one application source to retrieve an application that is specific to a guest operating system. The application is typically configured to run in an application player associated with the guest operating system.
In some embodiments, the application player is configured as the application broker. In some embodiments, the application broker is a program launched from and executed on the computing device, which is a client device. Alternatively or in addition to, the application broker is a service in a cloud and is accessible by the client device.
In some embodiments, the application broker implements one or more monetization schemes utilized by the application broker.
In yet another aspect, a system includes at least one application source and an application broker. The application broker is typically communicatively coupled with the at least one application source and configured to interface with the at least one application source to retrieve applications therefrom. The system also includes a computing device configured to access, via the application broker, an application that is specific to an operating system that is a guest on the computing device. The application is configured to run in an application player associated with the guest operating system. The guest operating system can be the same as or different from a host operating system
In some embodiments, the application broker is a program executed on the computing device. Alternatively or in addition to, the application broker is a service in a cloud. In some embodiments, the application player is configured as the application broker.
In some embodiments, the application broker is configured to list any application residing on the computing device that is related to the guest operating system.
In some embodiments, the application broker utilizes one or more monetization schemes.
Reference will now be made in detail to implementations of the present invention as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.
In the following description, numerous details are set forth for purposes of explanation. However, one of ordinary skill in the art will realize that the invention may be practiced without the use of these specific details. Thus, the present invention is not intended to be limited to the embodiments shown but is to be accorded the widest scope consistent with the principles and features described herein.
Embodiments of the present invention are directed to an application broker, which can be a program on a client device, a service in a cloud accessible by the client device or both. The client device typically runs a guest environment in a host environment. A user is able to search for an application on the application broker configured to interface with one or more application sources. In some embodiments, the application broker is able to intelligently search, download and/or install the application in the guest operating system of the client device with minimal or no user intervention. The application is typically executed in an application player associated with the guest environment. In some embodiments, the application player is configured as the application broker. In some embodiments, the application broker can provide suggested applications to download when the client device is communicatively coupled with the one or more application sources.
In general, a hardware structure suitable for implementing the computing device 200 includes a network interface 202, a memory 204, processor(s) 206, I/O device(s) 208, a bus 210 and a storage device 212. The choice of processor is not critical as long as a suitable processor with sufficient speed is chosen. In some embodiments, the computer device 200 includes at least two processors 206. The memory 204 is able to be any conventional computer memory known in the art. The storage device 212 is able to include a hard drive, compact disc read only memory (CDROM), compact disc rewritable (CDRW), digital video disk (DVD), digital video disk rewritable (DVDRW), flash memory card, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM) or any other storage device. The computing device 200 is able to include one or more network interfaces 202. An example of a network interface includes a network card connected to an Ethernet or other type of LAN. The I/O device(s) 208 are able to include one or more of the following: keyboard, mouse, monitor, display, printer, modem, touchscreen, button interface and other devices. Application(s) 216 used by the application broker are likely to be stored in the storage device 212 and memory 204 and are processed by the processor 206. More or less components shown in
Application Player
In some embodiments, a client device supports a plurality of operating systems, including a host operating system and at least one guest operating system. The host operating system can be the same as or different from each guest operating system. In the foregoing discussion, assume that the host operating system on the client device is a WINDOWS 7 operating system and that a guest operating system on the client device is an ANDROID operating system.
In some embodiments, the client device is able to communicatively couple with another device (e.g., a smart phone) running an operating system that is the same as the guest operating system on the client device. In this example, the smart phone is running an ANDROID operating system. Once the client device and the smart phone are communicatively coupled, the client device and the smart phone can be synched and/or share features, as illustrated in
The application player on the client device can also utilize features of the smart phone. For example, if the client device does not have a location sensor, then the client device, when communicatively coupled with the smart phone, can use a location sensor of the smart phone. Other features of the smart phone include, but are not limited to, an accelerometer, a camera and a microphone.
Application Broker
The application player can also be configured as an application broker. The application broker typically interfaces with at least one application source. An application source is an online application distribution system. Amazon Appstore, Mac App Store, Handango, Freeware Lovers, Google Play and GetJar are such online application distribution systems. In some embodiments, the application broker is configured to interface with one or more pre-selected application sources. However, at any time, the user is able to configure more or less application sources that the application broker interfaces with. The application broker is configured to search for applications from the one or more application sources. Typically, the application broker receives a search text as input by, for example, the user, and searches based on the search text, the one or more application sources. The application broker is configured to minimize and eliminate user intervention as much as possible during a search, a download and/or installation of an application from an application source. The connection between the application broker and the one or more application sources can be configured on an application by application basis or for all applications.
The application broker 500 also includes a second area 510 which allows the user to search for an application from the one or more application sources. In
In some embodiments, the search is transparent to the user. The application broker 500 will search in all configured application sources. However, the results 510b are displayed without telling the user the one or more applications sources that offer each result 510b. In some embodiments, a description of each result 510b is shown. Descriptions can include publisher information, metatdata or other relevant data regarding the results that help the user decide which application to download and install.
The application broker 500 also includes a third area 515 which displays a set of one or more suggested applications, e.g., SA1, SA2 and SA3. The suggested applications can be determined based on the currently running application, existing installed applications, the search text, the search results, a monetization scheme or a combination thereof. In some embodiments, the third area 515 is periodically refreshed with another set of one or more suggested applications. In some embodiments, the suggested applications only include guest ANDROID operating specific applications. In some embodiments, the suggested applications are listed in a particular order, such as popularity, cost of application, relatedness, importance and listing prices. As shown in the bottom application broker 500 of
The application broker 500 also includes a back button 520, a menu button 525, a home button 530 and a settings button 535. The back button 520 allows the user to go back to a previous page or view. The menu button 525 displays a menu. The home button 520 allows the user to go back to a home screen of the application broker 500. The settings button 535 allows the user to configure application player settings, including connecting to another device, e.g., the smart phone in
Assume the user clicks on or otherwise activates the first result, Angry Birds Space, shown in the second area 510. In some embodiments, the application broker 500 will intelligently select an application source to download the application from and will download the application therefrom. If Amazon Appstore and GetJar are both configured application sources that offer Angry Birds Space, the application broker 500 will intelligently select one of them to download the application from based on one or more factors, e.g., cost of application. For example, the application broker 500 will automatically download and install the application from Amazon Appstore because Amazon Appstore's current promotion includes offering the application for free, whereas GetJar is offering the application for $1.99. Alternatively, the user is able to select which of the application sources, Amazon Appstore or GetJar, to download the application from. For example, the user selects GetJar to download the application from because the user has a GetJar gift certificate that the user wants to use. Once Angry Birds Space is downloaded and installed in the guest environment, Angry Birds Space is shown as an installed application in the first area 505 of the application broker 500. Typically, a corresponding icon is shown in the first area 505.
In some embodiments, the application broker 500 will invoke a payment workflow the very first time the user is required to purchase an application. User intervention is thus required. However, the payment workflow can thereafter be automated if the user saves payment information to be used in future purchases.
The method 600 begins at a step 605 where a search text is received in the application broker configured to interface with at least one application source. Typically, the search text is input by the user in search of an application specific to the guest ANDROID operating system.
At a step 615, at least one application that is specific to the guest ANDROID operating system and based on the search text is displayed as part of the results.
At a step 610, the application broker searches, using the search text, in the at least one application source. The application broker can be configured with one or more preselected application sources. In addition, the user is able to configure the application broker to include more or less application sources of his or her own choice.
At a step 615, at least one application that is specific to the guest Android operating system and based on the search text is displayed as part of the results.
When the user selects one of the results, at a step 620, the corresponding application downloads and installs in the guest operating system. In some embodiments, the installation require little or no user intervention. In some embodiments, a payment workflow is invoked during installation. Once downloaded and installed, the application will be indicated as such in the application broker.
When the user activates the installed application, at a step 625, the application is executed within the application player associated with the guest ANDROID operating system. In some embodiments, the application player is configured as the application broker. After the step 625, the method 600 ends.
Although
Monetization
The application broker can implement one or more monetization schemes. For example, referring back to
The first area 505 of the application broker 500 is also real estate that utilizes a monetization scheme. As discussed elsewhere, the first area 505 displays any installed guest ANDROID operating system specific applications, which can include those that come pre-installed with the application player. Similarly, a developer of an application can pay an agreed-to amount to have the application come pre-installed with the application player.
The application player can also implement one or more monetization schemes. For example, referring now to
In some embodiments, the application broker is able to perform the method 600 of
At a step 810, a set of one or more suggested applications is displayed in the application broker. In some embodiments, the set is displayed in the third area of the application broker. The one or more suggested applications are displayed based on at least one monetization scheme. The monetization scheme can be based on cost of a real estate property in the application broker. Alternatively, the monetization scheme is based on cross promotional agreements. In some embodiments, the set is periodically refreshed with other suggested application(s). After the step 810, the method 800 ends.
Embodiments of the present invention are directed toward an application broker, which is an interface to one or more application sources. The choice of application source can be transparent to an end user. Furthermore, the choice of application source can be different for different applications. The application broker allows the end user to search for an application that is a guest operating system specific application for downloading and installation, and to execute an application therefrom. In some embodiments, the application broker implements one or more monetization schemes.
While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. Thus, one of ordinary skill in the art will understand that the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the appended claims.
This application claims benefit of priority under 35 U.S.C. section 119(e) of the U.S. Provisional Patent Application Ser. No. 61/489,611, filed May 24, 2011, entitled “Switch Operating Systems,” and U.S. Provisional Patent Application Ser. No. 61/489,615, filed May 24, 2011, entitled “App Store Broker,” which are both hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
7647491 | Kawano et al. | Jan 2010 | B2 |
7987432 | Grechishkin et al. | Jul 2011 | B1 |
7987459 | Chow et al. | Jul 2011 | B2 |
8117554 | Grechishkin et al. | Feb 2012 | B1 |
8161275 | Woodward | Apr 2012 | B1 |
8332936 | Hackborn et al. | Dec 2012 | B1 |
8438375 | Woodward | May 2013 | B1 |
8448160 | Vincent et al. | May 2013 | B2 |
8594649 | Kwon et al. | Nov 2013 | B2 |
8726263 | Rangarajan et al. | May 2014 | B2 |
8732697 | Jonnala et al. | May 2014 | B2 |
20050114870 | Song et al. | May 2005 | A1 |
20060212865 | Vincent et al. | Sep 2006 | A1 |
20080133903 | Sun et al. | Jun 2008 | A1 |
20080141244 | Kelley | Jun 2008 | A1 |
20080216071 | Gidalov | Sep 2008 | A1 |
20090210702 | Welingkar et al. | Aug 2009 | A1 |
20090241104 | Amiga et al. | Sep 2009 | A1 |
20100162233 | Ku et al. | Jun 2010 | A1 |
20100199037 | Umbehocker et al. | Aug 2010 | A1 |
20110016299 | Galicia et al. | Jan 2011 | A1 |
20110035355 | Sagar et al. | Feb 2011 | A1 |
20110082900 | Nagpal et al. | Apr 2011 | A1 |
20110126216 | Galicia et al. | May 2011 | A1 |
20110173602 | Togami et al. | Jul 2011 | A1 |
20110276621 | Edery et al. | Nov 2011 | A1 |
20110302630 | Nair et al. | Dec 2011 | A1 |
20110307354 | Erman et al. | Dec 2011 | A1 |
20120011551 | Levy et al. | Jan 2012 | A1 |
20120023507 | Travis | Jan 2012 | A1 |
20120042159 | Liu | Feb 2012 | A1 |
20120066675 | Shelansky et al. | Mar 2012 | A1 |
20120079095 | Evans et al. | Mar 2012 | A1 |
20120086716 | Reeves et al. | Apr 2012 | A1 |
20120089906 | Reeves et al. | Apr 2012 | A1 |
20120089992 | Reeves et al. | Apr 2012 | A1 |
20120110315 | Lee | May 2012 | A1 |
20120110496 | Lee et al. | May 2012 | A1 |
20120116905 | Futty et al. | May 2012 | A1 |
20120143900 | Ainslie et al. | Jun 2012 | A1 |
20120191961 | Wu et al. | Jul 2012 | A1 |
20120216181 | Arcese et al. | Aug 2012 | A1 |
20120272233 | Lee | Oct 2012 | A1 |
20120303476 | Krzyzanowski et al. | Nov 2012 | A1 |
20130024778 | Reeves et al. | Jan 2013 | A1 |
20130047150 | Malasky et al. | Feb 2013 | A1 |
20130054952 | Shen | Feb 2013 | A1 |
20130074069 | Li | Mar 2013 | A1 |
20130081008 | Rangarajan et al. | Mar 2013 | A1 |
20130095785 | Sadana et al. | Apr 2013 | A1 |
20130139182 | Sethuraman et al. | May 2013 | A1 |
20130268397 | Mehta et al. | Oct 2013 | A1 |
20140007084 | Ding | Jan 2014 | A1 |
20140007222 | Qureshi et al. | Jan 2014 | A1 |
20140059536 | Hiratsuka et al. | Feb 2014 | A1 |
Entry |
---|
RapidValue, “How to Choose the Right Architecture for Your Mobile Application”, Nov. 2012, RapidValue Solutions, pp. 1-16; <http://www.rapidvaluesolutions.com/wp-content/uploads/2013/04/How-to-Choose-the-Right-Technology-Architecture-for-Your-Mobile-Application.pdf>. |
Ki et al., “Poster: Retro: An Automated, Application-Layer Record and Replay for Android”, 2014 ACM, MobiSys'14, Jun. 16-19, 2014, Bretton Woods, New Hampshire, USA, p. 373; <http://dl.acm.org/results.cfm?h=1&cfid=417717926&cftoken=68174932>. |
Wu et al., “Scaling Social Media Applications Into Geo-Distributed Clouds”, Mar. 12, 2014 IEEE, pp. 1-14; <http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6766261>. |
Number | Date | Country | |
---|---|---|---|
61489611 | May 2011 | US | |
61489615 | May 2011 | US |