Method and Apparatus for Managing Proxy and Non-Proxy Requests In A Telecommunications Network

• US 20110314149A1
• Filed: 08/26/2011
• Published: 12/22/2011
• Est. Priority Date: 09/16/2004
• Status: Active Grant

• Current Assignee: Chen Yehezkel Burshan, Gregory John Wilkins, Michael Manning, Nathan John Sowatskey, Ritesh Kumar
• Original Assignee: Chen Yehezkel Burshan, Gregory John Wilkins, Michael Manning, Nathan John Sowatskey, Ritesh Kumar
• Inventors: Manning, Michael, Burshan, Chen Yehezkel, Sowatskey, Nathan John, Kumar, Ritesh, Wilkins, Gregory John
• Granted Patent: US 8,527,629 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method is disclosed for determining attributes of a client connection configured for use with a telecommunications network; comparing determined attributes with location definition information stored in a configuration file; determining at least one user-defined location in the location definition information associated with the client connection based on the comparison; wherein the method is performed by one or more computing devices.

Claims

1. A method comprising:

determining attributes of a client connection configured for use with a telecommunications network;

comparing determined attributes with location definition information stored in a configuration file;

determining at least one user-defined location in the location definition information associated with the client connection based on the comparison;

wherein the method is performed by one or more computing devices.

2. The method of claim 1, wherein comparing determined attributes with location definition information comprises comparing determined attributes with at least one Location object created from the location definition information stored in the configuration file.

3. The method of claim 2, wherein a Location object comprises a MBean.

4. The method of claim 1, wherein the location definition information comprises at least two hierarchically defined locations.

5. The method of claim 1, wherein the location definition information comprises at least one location group definition, said defined location group comprising at least two defined locations.

6. The method of claim 1, wherein a network management action selected from the group consisting of determining payment methods, determining rate information, setting quality of service parameters, determining whether access is allowed, and selecting a white list, is performed based at least in part on the at least one determined user-defined location.

7. The method of claim 1, further comprising determining a network management application for redirecting the client connection to based at least in part on the at least one determined user-defined location.

8. The method of claim 1, wherein determining attributes of the client connection comprises obtaining a Complete ID for the client session connection.

9. The method of claim 8, wherein the Complete ID includes at least one attribute selected from the group consisting of IP address, MAC address, VPI, VCI, Subnet address and MSISDN.

10. The method of claim 1, wherein the location definition information defines at least one location as a MAC address lookup, an IP address range, a VPI subnet range, or a combination of IP address range and VPI subnet range.

11. The method of claim 1, wherein the client connection is originated by a user at a wireless access point.

12. The method of claim 1, wherein the configuration file additionally includes white list definition information.

13. The method of claim 1, wherein the client connection is initiated by an unauthenticated user.

14. A non-transitory computer readable medium comprising one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform:

determining attributes of a client connection;

comparing determined attributes with location definition information stored in a configuration file;

determining at least one user-defined location in the location definition information associated with the client connection based on the comparison.

15. The non-transitory computer readable medium of claim 14, further comprising instructions which, when executed, cause the one or more processors to perform:

comparing determined attributes with at least one Location object created from the location definition information stored in the configuration file.

16. The non-transitory computer readable medium of claim 14, further comprising instructions which, when executed, cause the one or more processors to perform:

determining payment methods, determining rate information, setting quality of service parameters, determining whether access is allowed, and selecting a white list, is performed based at least in part on the at least one determined user-defined location.

17. A method comprising:

a proxy server receiving a secure request from the edge session;

the proxy server opening a connection to a web portal;

the proxy server making an out-of-band request to the web portal, the out-of-band request containing proxy meta-data;

the web portal using the proxy meta-data to determine a hostkey, the hostkey identifying the edge session;

wherein the method is performed by one or more computing devices.

18. The method of claim 17, wherein the proxy meta-data comprises remote address information, remote port information, address and port that the proxy server received the request on, and source address and port of the connection from the proxy server to the web portal;

and

wherein the web portal using the proxy meta-data to determine a hostkey comprises using remote address and port of the connection from the proxy server to the web portal in the proxy meta-data to look up the hostkey.

19. A non-transitory computer readable medium comprising one or more sequences of instructions which, when executed by one or more processors, cause the one or more processors to perform:

a proxy server receiving a secure request from the edge session;

the proxy server opening a connection to a web portal;

the proxy server making an out-of-band request to the web portal, the out-of-band request containing proxy meta-data;

the web portal using the proxy meta-data to determine a hostkey, the hostkey identifying the edge session.

20. The non-transitory computer readable medium of claim 19, wherein the proxy meta-data comprises remote address information, remote port information, address and port that the proxy server received the request on, and source address and port of the connection from the proxy server to the web portal;

and wherein the web portal uses a remote address and port of the connection from the proxy server to the web portal in the proxy meta-data to look up the hostkey.