Divitas protocol proxy and methods therefor

• US 7,480,500 B1
• Filed: 05/30/2007
• Issued: 01/20/2009
• Est. Priority Date: 06/14/2006
• Status: Expired due to Fees

• Current Assignee: Divitas Networks, Inc.
• Original Assignee: Divitas Networks, Inc.
• Inventors: Mittal, Ajay
• Primary Examiner(s): Nguyen; David Q
• Application Number:
  US11/755,704
• Time in Patent Office: 601 Days
• Field of Search: 455/414.1, 455/418, 455/426.1, 455/426.2, 455/432.2, 455/432.3
• US Class Current: 455/403
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/147 Signalling methods or messages providing extensions to protocols defined by standardisation
• CPC Class Codes: H04L 67/2876 Pairs of inter-processing entities at each side of the network, e.g. split proxies
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys
• CPC Class Codes: H04W 76/12 Setup of transport tunnels
• CPC Class Codes: H04W 88/182 Network node acting on behalf of an other network entity, e.g. proxy

Abstract

A mobility architectural arrangement for managing telecommunication mobility for a handset is provided. The arrangement includes a DiVitas protocol proxy (DPP), which is configured to manage connectivity between a mobility client of the handset and a mobility server within an enterprise. The DPP includes a client DPP being configured to manage the connectivity for the mobility client of the handset. The client DPP receives a plurality of client connectivity requests from a plurality of application clients. The server DPP is configured to manage the connectivity for the mobility server. The server DPP receives a plurality of server connectivity requests from a plurality of application servers. The client DPP and the server DPP are configured to interact with one another to establish a secure channel.

Claims

1. A mobility architectural arrangement for managing telecommunication mobility for a handset, comprising:

a DiVitas protocol proxy (DPP), said DPP being configured to manage connectivity between a mobility client of said handset and a mobility server within an enterprise, wherein said DPP including

a client DPP being configured to manage said connectivity for said mobility client of said handset, said client DPP receiving a plurality of client connectivity requests from a plurality of application clients, and

a server DPP being configured to manage said connectivity for said mobility server, said server DPP receiving a plurality of server connectivity requests from a plurality of application servers

wherein said client DPP and said server DPP are configured to interact with one another to establish a secure channel.

2. The mobility architectural arrangement of claim 1 wherein said client DPP is configured to include a plurality of sub-client DPPs, each of said plurality of sub-client DPPs being configured to handle a protocol of a plurality of protocols.

3. The mobility architectural arrangement of claim 1 wherein said server DPP is configured to include a plurality of sub-server DPPs, each of said plurality of sub-server DPPs being configured to handle a protocol of a plurality of protocols.

4. The mobility architectural arrangement of claim 1 wherein a first application client of said plurality of application clients send a set of data packets to said client DPP via an application protocol interface (API), said set of data packets is configured to include a local host address and a port number, said local host address being associated with said mobility client and said port number being associated with said first application client.

5. The mobility architectural arrangement of claim 4 wherein a DiVitas data exchange (DDX) tag is configured to be attached to said set of data packets, said DDX tag including a unique identification which is associated with said first application client.

6. The mobility architectural arrangement of claim 5 wherein said DDX tag is encrypted.

7. The mobility architectural arrangement of claim 6 wherein said client DPP format said set of data packets with said DDX tag into a format capable of being transmitted through said secure channel to said server DPP of said mobility server.

8. The mobility architectural arrangement of claim 7 wherein said server DPP is configured to decrypt said DDX tag and to employ said unique identification to send said set of data packets to said first application server.

9. The mobility architectural arrangement of claim 1 wherein said mobility client is configured to include a database, said database being employed to store authentication data for each of said plurality of application clients.

10. A method for managing telecommunication mobility for a handset, comprising:

employing a Divitas protocol proxy (DPP) to manage connectivity between a mobility client of said handset and a mobility server within an enterprise, said DPP including

a client DPP being configured to manage connectivity for said handset, said client DPP receiving a plurality of client connectivity requests from a plurality of application clients, and

a server DPP being configured to manage connectivity for said mobility server, said server DPP receiving a plurality of server connectivity requests from a plurality of application servers; and

employing said client DPP and said server DPP to establish a secure channel between said handset and said mobility server to enable said plurality of application clients to interact with said plurality of application servers.

11. The method of claim 10 further including

sending a set of data packets from a first application client of said plurality of application clients to said client DPP of said mobility client via an application protocol interface (API);

attaching a DiVitas data exchange (DDX) tag to said set of data packets, said DDX tag being configured to include data about said first application client,

sending said set of data packets with said DDX tag through said secure channel to said server DPP of said mobility server;

analyzing said DDX tag to identify a first application server of said plurality of application servers, said first application server being associated with said first application client; and

sending said set of data packets to said first application server.

12. The method of claim 10 wherein said client DPP is configured to include a plurality of sub-client DPPs, each of said plurality of sub-client DPPs, being configured to handle a protocol of a plurality of protocols.

13. The method of claim 10 wherein said server DPP is configured to include a plurality of sub-client DPPs, each of said plurality of sub-server DPPs being configured to handle a protocol of a plurality of protocols.

14. The method of claim 11 wherein said set of data packets is configured to include a local host address and a port number, said local host address being associated with said mobility client and said port number being associated with said first application client.

15. The method of claim 11 wherein said client DPP format said set of data packet enabling said set of data packet to be sent through said secure channel, said secure channel being established via a control protocol.

16. The method of claim 15 wherein said control protocol is a session initiation protocol (SIP).

17. The method of claim 11 wherein said DDX tag is configured to include a unique identification.

18. The method of claim 17 wherein said DDX tag is encrypted by said client DPP.

19. The method of claim 18 wherein said server DPP is configured to decrypt said DDX tag.

20. The method of claim 10 wherein said mobility client is configured to include a database, said database being employed to store authentication data for each of said plurality of application clients.

21. An article of manufacture comprising a program storage medium having computer readable code embodied therein, said computer readable code being configured to manage telecommunication mobility for a handset within a mobility architectural arrangement, comprising

code for establishing a secure channel between a mobility client of said handset and a mobility server that is located within an enterprise by employing a Divitas protocol proxy (DPP), said DPP including

a client DPP configured to manage connectivity for said handset, said client DPP receiving a plurality of client connectivity requests from a plurality of application clients, and

a server DPP configured to manage connectivity for said mobility server, said server DPP receiving a plurality of server connectivity requests from a plurality of application servers;

and

code for employing said client DPP and said server DPP to establish a secure channel between said handset and said mobility server to enable said plurality of application clients to interact with said plurality of application servers.

22. The article of manufacture of claim 21 further including

code for sending a set of data packets from a first application client of said plurality of application clients to said client DPP of said mobility client via an application protocol interface (API);

code for attaching a DiVitas data exchange (DDX) tag to said set of data packets, said DDX tag being configured to include data about said first application client,

code for sending said set of data packets with said DDX tag through said secure channel to said server DPP of said mobility server;

code for analyzing said DDX tag to identify a first application sever of said plurality of application servers, said first application server being associated with said first application client; and

code for sending said set of data packets to said first application server.

23. The article of manufacturing of claim 21 wherein said client DPP is configured to include a plurality of sub-client DPPs, each of said plurality of sub-client DPPs, being configured to handle a protocol of a plurality of protocols.

24. The article of manufacturing of claim 21 wherein said server DPP is configured to include a plurality of sub-client DPPs, each of said plurality of sub-server DPPs being configured to handle a protocol of a plurality of protocols.

25. The article of manufacturing of claim 22 wherein said set of data packets is configured to include a local host address and a port number, said local host address being associated with said mobility client and said port number being associated with said first application client.

26. The article of manufacturing of claim 22 wherein said client DPP format said set of data packets enabling said set of data packets to be sent through said secure channel, said secure channel being established via a control protocol.

27. The article of manufacturing of claim 22 wherein said DDX tag is configured to include a unique identification and said DDX tag is encrypted by said client DPP.

28. The article of manufacturing of claim 27 wherein said server DPP is configured to decrypt said DDX tag.

29. The article of manufacturing of claim 21 wherein said mobility architectural arrangement is configured to include a database, said database being employed to store authentication data for each of said plurality of application clients.