Methods for managing entity profiles and application launching in software applications

• US 10,637,909 B2
• Filed: 03/15/2013
• Issued: 04/28/2020
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: Gordon E. Seay
• Original Assignee: Gordon E. Seay
• Inventors: Seay, Gordon E.
• Primary Examiner(s): Bates, Kevin T
• Assistant Examiner(s): Patel, Ronak
• Application Number:
  US13/841,726
• Publication Number:
  US 20140280487A1
• Time in Patent Office: 2,601 Days
• Field of Search: 709203
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/30 Profiles

Abstract

Methods for managing entity profiles and application launching in software applications, including providing a network connected application server, providing an application configured to be loaded on a client computer, receiving credentials associated with a user from the client computer with the application server, identifying subscribed entities associated with the user, displaying a visual representation of the subscribed entities associated with the user on the client computer, and transferring entity profile data to the application in response to the user selecting the visual representation of one of the subscribed entities. In some examples, the methods include loading a launching utility on a client computer, where the launching utility is configured to display a user interface displaying a user subset of software applications.

Claims

1. A method for managing entity profiles in software applications, comprising:

providing an application server storing a plurality of applications, a plurality of users, and a plurality of profiles, wherein;

each profile corresponds to one of a plurality of entities subscribed to the application server,

each of the profiles includes a list of one or more of the plurality of applications to which the subscribed entity has subscribed; and

each of the profiles includes entity data specific to its corresponding subscribed entity;

storing a list of the subscribed entities associated with each of the plurality of users;

receiving, by the application server, credentials associated with one of the plurality of users;

identifying, by the application server, the subscribed entities associated with the user;

providing an application from the plurality of applications to a client computer in response to the user selecting the application;

providing, within the application or within a framework accessible to the application, a selector for the user to select from the subscribed entities associated with the user who are also subscribed to the application, the selector provided by an entity selection framework;

transferring to the application, entity data from the profile of a first entity in response to the user selecting the first entity from the selector;

executing the application with the first entity data;

receiving a selection of a second entity from the selector from the user, and in response;

updating the first entity data into the profile of the first entity;

transferring entity data from the profile of a second entity to the application in response to the user selecting the second entity from within the application;

refreshing the application with the second entity data, so that the entity data from the first entity profile is replaced in the application with the entity data from the second entity profile; and

executing the application with the second entity data.

2. The method of claim 1, wherein the application server

includes a processor and further comprising executing, at least partially, the application with the processor of the application server.

3. The method of claim 1, further comprising receiving with the application server client data input by the user on the client computer;

wherein selecting the first entity includes associating the client data received by the application server with the first entity in the entity data.

4. The method of claim 1, further comprising modifying the profile corresponding to the first entity when the first entity subscribes to the second application.

5. The method of claim 1, further comprising displaying an entity selector user interface with consistent graphical features in each application in a set of software applications including the application by referencing with a given application the entity selection framework including computer executable instructions for displaying in the set of software applications the entity selector user interface with particular graphical features.

6. The method of claim 1, further comprising updating the first entity data in the entity profile corresponding to the first entity when or after the first entity is selected.

7. The method of claim 6, further comprising retrieving state data associated with the first entity in response to the first entity being selected.

8. The method of claim 7, wherein the state data includes a uniform resource locater storing a location in the application at which the client computer was pointed to immediately prior to the user navigating away from the first entity, further comprising automatically navigating to the location associated the uniform resource locater when the user again selects the first entity and the application.

9. The method of claim 7, wherein retrieving state data includes retrieving state data from a shared state data memory accessible to each of the subscribed entities, further comprising:

receiving instructions from the user to select the second entity; and

retrieving state data associated with the first entity from the shared state data memory.

10. The method of claim 1, further comprising:

storing, on the application server, a last selected entity value corresponding to the first entity in response to the user selecting the first entity; and

intercepting a client operation within an active application if an entity tag value associated with the active application is not consistent with the last selected entity value.

11. The method of claim 10, wherein:

the entity tag value defined by the active application is inconsistent with the last selected entity value;

the client operation has been received on the active application; and

intercepting the client operation entered on the active application includes;

comparing the entity tag value associated with the active application with the last selected entity value; and

rejecting the client operation based on the inconsistency between the entity tag value and the last selected entity value.

12. The method of claim 10, further comprising adjusting the last selected entity value to identify, upon execution of the first entity, the first entity as the last selected entity selected amongst the subscribed entities;

wherein;

the entity tag value defined by the active application is consistent with the last selected entity value;

the client operation has been received on the active application; and

intercepting the client operation entered on the active application includes;

comparing the entity tag value associated with the active application with the last selected entity value; and

accepting the client operation based on the consistency between the entity tag value and the last selected entity value.

13. The method of claim 1, wherein the first entity defines a user-designated default entity configured to be selected automatically when the user initiates a session with the application server.

19. The method of claim 1, wherein the entity selection framework comprises a program module that is referenced by each of the plurality of applications.

14. A hosted entity management method, comprising:

providing a network connected application server including one or more storage units storing a plurality of software applications and a plurality of entity profiles, each corresponding to at least one subscribed entity, each entity profile including entity data and a list of approved users, and each subscribed entity subscribed to at least one of the plurality of software applications;

receiving by the application server credentials associated with a user via a client computer wherein;

receiving credentials associated with the user includes comparing the credentials with user authentication data for controlling access to a portion of the plurality of software applications, to which the user is subscribed; and

the user is provided access to the entity data of a given entity profile only if the credentials are consistent with the user authentication data and the user is in the list of approved users of the given entity profile;

loading a launching utility on the client computer that includes computer executable instructions for displaying a user interface on the client computer, where the user interface displays the software applications in the portion of the plurality of software applications;

loading a selector provided by an entity selection framework to provide a list of all subscribed entities that include the user in the list of approved users in each subscribed entity'"'"'s corresponding profile;

loading, on the client computer, either;

a selected application in the user subset of the plurality of software applications in response to a user selecting the selected application on the user interface, and updating the selector to provide a list of only those subscribed entities that are subscribed to the selected application;

or

a modified user interface, in response to the user selecting a subscribed entity from the selector, that displays a subset of software applications to which the subscribed entity is subscribed;

transferring user data from a first entity profile stored on the storage unit to the selected application;

receiving a selection of a second entity profile; and

transferring user data from the second entity profile storted on the storage unit to the selected application, so that the user data from the first entity profile is replaced in the selected application by the user data from the second entity profile.

15. The method of claim 14, wherein:

the launching utility defines an entity launching utility and includes computer executable instructions for identifying a user subset of entities associated with the user;

displaying the user interface on the client computer includes simultaneously displaying a graphical representation depicting each application in the subset of applications associated with the selected entity.

16. A hosted entity management method, comprising:

providing a network connected server including a storage unit storing entity profile data corresponding to subscribed entities, the subscribed entities including at least a first entity and a second entity associated with a user;

providing a plurality of applications, each application defining a software application including a selector within the application to select from entities associated with the application, the selector provided by an entity selection framework, and wherein the first entity and second entity are each associated with a plurality of applications that is at least a subset of the plurality of applications;

receiving a user selection of the first entity;

providing, to a client computer, a list of the subset of the plurality of applications associated with the first entity;

storing, on the server, a last selected entity value corresponding to the first entity in response to the user selecting the first entity;

storing an entity tag value associated with an instance of an active application that is part of the plurality of applications associated with the second entity, the entity tag value identifying the instance of the active application as associated with the second entity; and

intercepting a client operation within the instance of the active application if the entity tag value is inconsistent with the last selected entity value.

17. The method of claim 16, wherein intercepting the client operation includes comparing the last selected entity value with the entity tag value, which may be stored in a client-side session memory, depicted in computer executable code associated with the active application, or stored in a server-side session memory.

18. The method of claim 16, wherein each subscribed entity includes an approved user list, each approved user list including all users associated with the corresponding subscribed entity who are approved to access entity profile data associated with the subscribed entity.