Similarity engine for facilitating re-creation of an application collection of a source computing device on a destination computing device

• US 9,032,392 B2
• Filed: 09/25/2013
• Issued: 05/12/2015
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Quixey, Inc.
• Inventors: Glover, Eric J., Quander, Marshall J.
• Primary Examiner(s): COYER, RYAN D
• Application Number:
  US14/037,155
• Publication Number:
  US 20140280240A1
• Time in Patent Office: 594 Days
• Field of Search: 717174-178
• US Class Current: 717/176
• CPC Class Codes: G06F 16/24553 of query operations
• CPC Class Codes: G06F 16/2457 with adaptation to user needs
• CPC Class Codes: G06F 16/3334 Selection or weighting of terms from queries, including natural language queries
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation

Abstract

Techniques are disclosed for facilitating re-creation of an application collection of a source computing device at a destination computing device. The techniques include receiving a source application identifier indicative of a source application edition, the edition of the application being programmed for a source operating system. The techniques also include receiving an indicator of a destination operating system. The techniques further include determining a source canonical application corresponding to the source application edition based on the source application identifier, the source canonical application being a representative of one or more application editions including the source application edition. The techniques also include determining a set of destination application editions that are likely similar to the source application edition based on the source canonical application, the set of destination application editions indicating one or more destination application editions programmed for the destination operating system.

Claims

1. A method comprising:

receiving, at a processing device, a source application identifier indicative of a source application edition programmed for a source operating system;

receiving, at the processing device, an indicator of a destination operating system;

determining, at the processing device, a source canonical application corresponding to the source application edition based on the source application identifier, the source canonical application being a representative of one or more application editions including the source application edition;

determining, at the processing device, a set of destination application editions that are likely similar to the source application edition based on the source canonical application, the set of destination application editions indicating one or more destination application editions programmed for the destination operating system, wherein a destination application identifier of a specific application edition is included in the set of destination application editions when a gaminess value of the specific application edition is within a tolerance of a gaminess value of the source application edition, each gaminess value respectively indicative of a likelihood that its corresponding application edition is directed to a game; and

providing, from the processing device, a reply indicating the set of destination application editions to a remote device, the remote device displaying information corresponding to the one or more destination application editions.

2. The method of claim 1, further comprising:

determining, at the processing device, one or more destination application identifiers, each destination identifier respectively indicating one of the destination application editions in the set of destination applications,

wherein the reply includes the destination application identifiers.

3. The method of claim 1, wherein determining the source canonical application includes querying an application database with the source application identifier, the application database storing a plurality of records including a record of the source canonical application, each record storing a canonical application and references to one or more application editions represented by the canonical application, each application edition including a corresponding application identifier.

4. The method of claim 3, wherein determining the set of destination application editions includes:

determining, at the processing device, whether the record of the source canonical application references an application edition programmed for the destination operating system; and

when the record references the application edition programmed for the destination operating system, including a destination application identifier of the application edition in the set of destination application editions.

5. The method of claim 3, wherein determining the set of destination application editions includes:

determining, at the processing device, whether an application edition referenced in the application database has a title that exactly matches a source title of the source application edition and is programmed for the destination operating system; and

when a specific application edition having a title that exactly matches the source title is determined, including a destination application identifier of the specific application edition in the set of destination application editions.

6. The method of claim 5, wherein the destination application identifier of the specific application edition is included in the set of destination application editions if an importance value of the specific application edition is within a tolerance of an importance value of the source application edition, each importance value being a function of an overall popularity of its respective application edition and an overall rating score of its respective application edition.

7. The method of claim 5, wherein the destination application identifier of the specific application edition is included in the set of destination application editions if:

an importance value of the specific application edition is within an importance tolerance of an importance value of the source application edition, and

a gaminess value of the specific application edition is within a gaminess tolerance of a gaminess value of the source application edition.

8. The method of claim 3, wherein determining the set of destination application editions includes:

determining, at the processing device, whether an application edition referenced in the application database has a title that weakly matches a source title of the source application edition and is programmed for the destination operating system, wherein the title of the application edition and the source title weakly match when the title of the application edition and the source title include the same non-stop words in order and are not exact matches; and

when a specific application edition having a title that weakly matches the source title is determined, including, at the processing device, a destination application identifier of the specific application edition in the set of destination application editions.

9. The method of claim 3, wherein determining the set of destination application editions includes:

referencing, at the processing device, a similarity matrix storing a plurality of similarity scores corresponding to the source canonical application, each similarity score indicating a degree of similarity between the source canonical application and another canonical application referenced in the application database;

identifying, at the processing device, a specific application edition based on the similarity matrix, the specific application edition being programmed for the destination operating system and corresponding to a specific canonical application having a highest similarity score with respect to the source canonical application; and

including, at the processing device, a destination application identifier of the specific application edition in the set of destination application editions.

10. The method of claim 1, wherein the source operating system is different than the destination operating system.

11. A similarity engine comprising:

a memory device that stores an application database storing a plurality of records, each record storing a respective canonical application, references to one or more application editions represented by the canonical application, and application identifiers respectively corresponding to each of the referenced application editions; and

a processing device that executes a request handler, the request hander being configured to;

receive a source application identifier indicative of a source application edition programmed for a source operating system;

receive an indicator of a destination operating system;

determine a source canonical application corresponding to the source application edition based on the source application identifier and the application database, the source canonical application being representative of one or more application editions including the source application edition;

determine a set of destination application editions that are likely similar to the source application edition based on the source canonical application, the set of destination application editions indicating one or more destination application editions programmed for the destination operating system, wherein a destination application identifier of a specific application edition is included in the set of destination application editions when a gaminess value of the specific application edition is within a tolerance of a gaminess value of the source application edition, wherein each gaminess value is respectively indicative of a likelihood that its corresponding application edition is directed to a game; and

provide a reply indicating the set of destination application editions to a remote device, the remote device displaying information corresponding to the one or more destination application editions.

12. The similarity engine of claim 11, wherein the request handler is further configured to:

determine one or more destination application identifiers, each destination identifier respectively indicating one of the destination applications in the set of destination applications,

wherein the reply includes the destination application identifiers.

13. The similarity engine of claim 11, wherein the request handler is configured to determine the source canonical application by querying the application database with the source application identifier and receiving a record of the source canonical application.

14. The similarity engine of claim 13, wherein the processing device executes an ID matcher configured to:

determine whether the record of the source canonical application references a specific application edition programmed for the destination operating system; and

include a destination application identifier of the specific application edition in the set of destination application editions when the record references the specific application edition is programmed for the destination operating system.

15. The similarity engine of claim 13, wherein the processing device executes a title matcher configured to:

determine whether an application edition referenced in the application database has a title that exactly matches a source title of the source application edition and is programmed for the destination operating system; and

include a destination application identifier of a specific application edition in the set of destination application editions when the specific application edition has a title that exactly matches the source title.

16. The similarity engine of claim 15, wherein the title matcher includes the destination application identifier of the specific application edition in the set of destination application editions when an importance value of the specific application edition is within a tolerance of an importance value of the source application edition, wherein each importance value is a function of an overall popularity of its respective application edition and an overall rating score of its respective application edition.

17. The similarity engine of claim 15, wherein the title matcher includes the destination application identifier of the specific application edition in the set of destination application editions when:

an importance value of the specific application edition is within an importance tolerance of an importance value of the source application edition, and

a gaminess value of the specific application edition is within a gaminess tolerance of a gaminess value of the source application edition.

18. The similarity engine of claim 13, wherein the processing device executes a title matcher configured to:

determine whether an application edition referenced in the application database has a title that weakly matches a source title of the source canonical application and is programmed for the destination operating system, wherein the title of the application edition and the source title weakly match when the title of the application edition and the source title have the same non-stop words in the same order and are not exact matches; and

include a destination application identifier of a specific application edition in the set of destination application editions when the specific application edition has a title that weakly matches the source title.

19. The similarity engine of claim 13, further comprising:

a similarity matrix storing a plurality of similarity scores corresponding to the source canonical application, each similarity score indicating a degree of similarity between the source canonical application and another canonical application referenced in the application database,

wherein the processing device executes a similarity matcher configured to;

identify a specific application edition based on the similarity matrix, the specific application edition being programmed for the destination operating system and corresponding to a specific canonical application having a highest similarity score with respect to the source canonical application, and

include a destination application identifier of the specific application edition in the set of destination application editions.

20. The similarity engine of claim 11, wherein the source operating system is different than the destination operating system.