System and method for orchestration of customization for a user expereince

• US 20100083217A1
• Filed: 12/05/2008
• Published: 04/01/2010
• Est. Priority Date: 09/30/2008
• Status: Active Grant

• Current Assignee: eBay Inc.
• Original Assignee: eBay Inc.
• Inventors: Dalal, Vipul C., Belur, Rangaraj Keshavamurthy
• Granted Patent: US 8,904,345 B2
• Time in Patent Office: Days
• US Class Current: 717/106
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 3/048 Interaction techniques based on graphical user interfaces [GUI]
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 40/14 Tree-structured documents parsing G06F40/205; validation G06F40/226
• CPC Class Codes: H04W 4/025 using location based information parameters

Abstract

A system and method for orchestration of customization for a user experience is disclosed. The apparatus in an example embodiment includes identifying a plurality of modules included in a webpage; discovering dependencies between each of the modules of the plurality of modules; designating at least one module of the plurality of modules for retaining dependency state information, the dependency state information including information indicative of states of dependencies between modules of the plurality of modules; and executing the modules of the webpage in an order indicated by the dependency state information.

Claims

1. A method comprising:

identifying a plurality of modules included in a webpage;

discovering dependencies between each of the modules of the plurality of modules;

designating at least one module of the plurality of modules for retaining dependency state information, the dependency state information including information indicative of states of dependencies between modules of the plurality of modules; and

executing the modules of the webpage in an order indicated by the dependency state information.

2. The method as claimed in claim 1 wherein discovering dependencies between each of the modules of the plurality of modules includes extracting dependency information from an application programming interface (API) for each of the plurality of modules.

3. The method as claimed in claim 1 wherein at least one module of the plurality of modules being a logical unit of code that can be reused on a web page.

4. The method as claimed in claim 1 wherein the dependency state information for modules of a webpage being based in part on the metadata of the webpage.

5. The method as claimed in claim 1 including gathering context information and providing a user experience customizer to automatically produce user experience customization selections based on the context information.

6. The method as claimed in claim 5 including collecting user activity feedback from a community of users and using the user activity feedback to adjust the user experience customizer to automatically produce user experience customization selections likely favored by a user based on a correlation of the user activity feedback with the context information.

7. The method as claimed in claim 5 wherein the context information is selected from the group:

site identifier, buyer segmentation information, domain identifier, and keywords/queries.

8. The method as claimed in claim 5 wherein the context information is selected from dimensions in the group:

site identifier, buyer segmentation information, domain identifier, and keywords/queries, and the method further includes progressively falling back to other sufficient and accurate dimensions in the group if a particular dimension does not provide sufficient or accurate information.

9. The method as claimed in claim 5 wherein the user experience customization selections are selected from the group:

page type, modules, and configurations.

10. An orchestrator component comprising:

a plurality of modules included in a webpage;

a dependency information generator to discover dependencies between each of the modules of the plurality of modules, to designate at least one module of the plurality of modules for retaining dependency state information, the dependency state information including information indicative of states of dependencies between modules of the plurality of modules; and

an execution engine to execute the modules of the webpage in an order indicated by the dependency state information.

11. The orchestrator component as claimed in claim 10 wherein the dependency information generator being further configured to extract dependency information from an application programming interface (API) for each of the plurality of modules.

12. The orchestrator component as claimed in claim 10 wherein at least one module of the plurality of modules being a logical unit of code that can be reused on a web page.

13. The orchestrator component as claimed in claim 10 wherein the dependency state information for modules of a webpage being based in part on the metadata of the webpage.

14. The orchestrator component as claimed in claim 10 including:

an input unit to gather context information; and

a predictive data unit to form correlations between the context data and a likely desirable structure and content provided in a corresponding user experience, the predictive data unit further to collect user activity feedback from a community of users and to adjust the user experience customizer based on the user activity feedback.

15. The orchestrator component as claimed in claim 14 including a decision unit to automatically produce user experience customization selections based on a correlation of the user activity feedback with the context information.

16. The orchestrator component as claimed in claim 14 wherein the context information is selected from the group:

site identifier, buyer segmentation information, domain identifier, and keywords/queries.

17. The orchestrator component as claimed in claim 14 wherein the context information is selected from dimensions in the group:

site identifier, buyer segmentation information, domain identifier, and keywords/queries, and the method further includes progressively falling back to other sufficient and accurate dimensions in the group if a particular dimension does not provide sufficient or accurate information.

18. The orchestrator component as claimed in claim 14 wherein the user experience customization selections are selected from the group:

page type, modules, and configurations.

19. An article of manufacture comprising a machine-readable storage medium having machine executable instructions embedded thereon, which when executed by a machine, cause the machine to:

identify a plurality of modules included in a webpage;

discover dependencies between each of the modules of the plurality of modules;

designate at least one module of the plurality of modules for retaining dependency state information, the dependency state information including information indicative of states of dependencies between modules of the plurality of modules; and

execute the modules of the webpage in an order indicated by the dependency state information.

20. The article of manufacture as claimed in claim 19 wherein discovering dependencies between each of the modules of the plurality of modules includes extracting dependency information from an application programming interface (API) for each of the plurality of modules.