IP Library › Granted Patent US 8,321,566

Granted Patent B2

US 8,321,566 · App. 13/276,220 · Granted Nov 27, 2012

System and method to control application to application communication over a network

Assignee: Jibe Mobile

View Patent ↗

Loading inventors, assignments & file history…

Monitor This Case

Get email alerts when status or documents change.

Order Certified Copies

Most orders are placed with the USPTO same day — all within 24 business hours.

Order via The Patent Place →

Pre-filled with this patent's details

Quick Facts

Patent No.: US 8,321,566
App. No.: 13/276,220
Granted: Nov 27, 2012
Kind: B2

External Links

USPTO Patent Center↗ Full Patent PDF↗

Abstract

A method is provided to control communication between applications that communicate over a network comprising: designating a different respective application identifier (AppID) for each of a multiplicity of A2A enabled applications suitable to run on endpoint devices coupled to a network suitable for delivery of multimedia information; providing in non-transitory media a registry that indicates authorized AppIDs; receiving over the network a request originating from a first endpoint device for authorization for a media connection; wherein the authorization request includes an AppID; in response to the authorization request, determining whether the AppID within the authorization request matches an authorized AppID indicated within the registry; rejecting the authorization request in response to a determination that the AppID does not match an authorized AppID indicated within the registry.

Claims (121)

1. A method to control communication between applications that communicate over a network comprising:

providing in non-transitory media a registry that indicates authorized AppIDs associated with a multiplicity of A2A Application to application enabled applications suitable to run on endpoint devices coupled to a network suitable for delivery of multimedia information and respective corresponding secret information for each respective AppID;

receiving over the network by an application management server a request for authorization for an A2A enabled application associated with a given AppID running on a first endpoint device to create a media connection;

wherein the authorization request includes the given AppID and a token that is generated as a function of at least the secret information corresponding to the given AppID;

in response to the authorization request, determining by the application management server whether the given AppID and the corresponding secret information used to generate the token within the authorization request match an authorized AppID and corresponding secret information indicated within the registry;

sending an authorization over the network by the application management server for the A2A enabled application associated with the given AppID to create the media connection in response to a determination that the given AppID and the corresponding secret information used to generate the token does match an authorized AppID and corresponding secret information indicated within the registry.

2. The method of claim 1 further including:

applying a transformation to the token information to produce transformation information;

determining whether secret information associated in the registry with an AppID that matches the given AppID within the authorization matches transformation information.

3. The method of claim 1 ,

wherein the registry indicates respective blacklist information associated with respective authorized AppIDs; and further including:

determining whether blacklist information associated in the registry with an AppID that matches the given AppID within the authorization request indicates that an application associated with the given AppID is blacklisted.

4. The method of claim 1 ,

wherein the registry indicates respective meta-data associated with respective authorized AppIDs; and further including:

wherein the authorization request includes user identifying information (userID);

providing access to user profile information associated with the userID within the authorization request;

determining whether meta-data associated in the registry with an AppID that matches the given AppID within the authorization request indicates that a user having the obtained profile is authorized to use the application associated with the given AppID.

5. The method of claim 1 further including:

applying a transformation to the token information to produce transformation information;

wherein the registry indicates respective blacklist information associated with respective authorized AppIDs;

and further including:

determining at least one of:

whether secret information associated in the registry with an AppID that matches the given AppID within the authorization matches transformation information; and

whether blacklist information associated in the registry with an AppID that matches the given AppID within the authorization request indicates that an application associated with the given AppID is blacklisted; and

rejecting the authorization request in response to a determination of at least one of:

that the secret information associated in the registry with an AppID that matches the given AppID within the authorization request does not match the transformation information; and

that blacklist information associated in the registry with an AppID that matches the given AppID within the authorization request indicates that the application is blacklisted.

6. A method to control communication between applications that communicate over a network comprising:

designating a different respective application identifier (AppID) for each of a multiplicity of A2A enabled applications suitable to run on endpoint devices coupled to a network suitable for delivery of multimedia information;

providing in non-transitory media a registry that indicates authorized AppIDs;

receiving over the network a request originating from a first endpoint device for authorization for a media connection;

wherein the authorization request includes an AppID;

in response to the authorization request, determining whether the AppID within the authorization request matches an authorized AppID indicated within the registry;

rejecting the authorization request in response to a determination that the AppID does not match an authorized AppID indicated within the registry;

designating respective different respective secret information for each different respective application identifier (AppID);

wherein the registry indicates respective secret information associated with respective authorized AppIDs;

wherein the registry indicates respective meta-data associated with respective authorized AppIDs; and further including:

wherein the authorization request includes a token information;

wherein the authorization request includes user identifying information (userID);

applying a transformation to the token information to produce transformation information;

providing access to user profile information associated with the userID within the authorization request;

determining at least one of:

whether secret information associated in the registry with an AppID that matches the AppID within the authorization matches transformation information; and

whether meta-data associated in the registry with an AppID that matches the AppID within the authorization request indicates that a user having the obtained profile is authorized to use the application associated with the AppID; and

rejecting the authorization request in response to a determination of at least one of:

that the secret information associated in the registry with an AppID that matches the AppID within the authorization request does not match the transformation information; and

that meta-data associated in the registry with an AppID that matches the AppID within the registration indicates that the user having the obtained profile is not authorized to use the application associated with the AppID.

7. The method of claim 1 ,

wherein receiving the authorization request includes receiving an authorization request sent by a proxy server that is part of the network.

8. The method of claim 1 ,

wherein sending includes sending a message to a proxy server that is part of the network.

9. A system to control communication between applications that communicate over a network comprising:

an application management server including:

a registry stored in non-transitory media that indicates a different respective application identifier (AppID) and respective corresponding secret information for each of a multiplicity of A2A enabled applications suitable to run on endpoint devices coupled to a network suitable for delivery of multimedia information;

wherein the management server is configured to receive over the network a request originating from an A2A enabled application associated with a given AppID running on a first endpoint device for authorization for a media connection with an A2A enabled application on a second endpoint device;

wherein the authorization request includes a given AppID and a token that is generated as a function of at least the secret information corresponding to the given AppID;

wherein the application management server is configured to determine in response to receiving an authorization request, whether the given AppID and the corresponding secret information used to generate the token within the authorization request match an authorized AppID and corresponding secret information indicated within the registry;

wherein the application management server is configured to send an authorization over the network for the A2A enabled application associated with the given AppID to create the media connection in response to a determination that the given AppID and the corresponding secret information used to generate the token does match an authorized AppID and corresponding secret information indicated within the registry.

10. The system of claim 9 ,

wherein the application management server is configured to apply a transformation to the token information to produce transformation information;

wherein the application management server is configured to determine whether secret information associated in the registry with an AppID that matches the given AppID within the authorization matches transformation information;

wherein the application management server is configured to send the authorization request in response to a determination that the secret information associated in the registry with an AppID that matches the given AppID within the authorization request does match the transformation information.

11. The system of claim 9 ,

wherein the registry indicates respective blacklist information associated with respective authorized AppIDs;

wherein the application management server is configured to determine whether blacklist information associated in the registry with an AppID that matches the given AppID within the authorization request indicates that an application associated with the given AppID is blacklisted; and

wherein the application management server is configured to send the authorization request only after determining that blacklist information associated in the registry with an AppID that matches the given AppID within the authorization request indicates that the application is not blacklisted.

12. The system of claim 9 ,

wherein the registry indicates respective meta-data associated with respective authorized AppIDs; and further including:

wherein the authorization request includes user identifying information (userID);

wherein the application management server is configured to provide access to user profile information associated with the userID within the authorization request;

wherein the application management server is configured to determine whether meta-data associated in the registry with an AppID that matches the given AppID within the authorization request indicates that a user having the obtained profile is authorized to use the application associated with the given AppID; and

wherein the application management server is configured to send the authorization request only after determining that meta-data associated in the registry with an AppID that matches the given AppID within the registration indicates that the user having the obtained profile is authorized to use the application associated with the given AppID.

13. The system of claim 9 ,

wherein the registry indicates respective blacklist information associated with respective authorized AppIDs;

and further including:

wherein the application management server is configured to apply a transformation to the token information to produce transformation information;

wherein the application management server is configured to determine:

whether secret information associated in the registry with an AppID that matches the given AppID within the authorization matches transformation information; and

wherein the application management server is configured to not send an authorization in response to a determination of at least one of:

that the secret information associated in the registry with an AppID that matches the given AppID within the authorization request does not match the transformation information; and

that blacklist information associated in the registry with an AppID that matches the given AppID within the authorization request indicates that the application is blacklisted.

14. A system to control communication between applications that communicate over a network comprising:

means for designating a different respective application identifier (AppID) for each of a multiplicity of A2A enabled applications suitable to run on endpoint devices coupled to a network suitable for delivery of multimedia information;

an application management server including:

non-transitory media a registry that indicates authorized AppIDs and corresponding secret information;

wherein the management server is configured to receive over the network a request originating from a first endpoint device for authorization for a media connection request;

wherein the authorization request includes an AppID;

wherein the application management server is configured to determine in response to receiving an authorization request, whether the AppID within the authorization request matches an authorized AppID indicated within the registry;

wherein the application management server is configured to reject the authorization request in response to a determination that the AppID does not match an authorized AppID indicated within the registry;

wherein the means for designating designates respective different respective secret information for each different respective application identifier (AppID);