Method and system for identity management across multiple planes

1. A method for identity management across multiple planes, the method comprising:

receiving, by a mission critical push to talk (MCPTT) server, a first request message to establish a call between a first MCPTT client and at least one second MCPTT client from a signaling plane entity, wherein the first request message comprises an application plane identity of the first MCPTT client and an application plane identity of the at least one second MCPTT client;

translating, at the MCPTT server, the application plane identity of the at least one second MCPTT client to a signaling plane identity of the at least one second MCPTT client; and

sending, by the MCPTT server, at least one second request message comprising the signaling plane identity of the at least one second MCPTT client to the at least one second MCPTT client to establish the call via the signaling plane entity.

2. The method of claim 1 , wherein translating the application plane identity of the at least one second MCPTT client to the signaling plane identity of the at least one second MCPTT client comprising:

retrieving a MCPTT client identity for each of the at least one second MCPTT client associated with the application plane identity;

identifying the signaling plane identity corresponding to each of the MCPTT identity from an identity management entity; and

translating the application plane identity to the signaling plane identity for each of the at least one second MCPTT client.

3. The method of claim 1 , wherein the signaling plane identity of the at least one second MCPTT client is predefined and is stored in an identity management entity during service registration,

wherein the identity management entity is stored at one of the MCPTT server, a group management server, and a signaling plane domain entity.

4. The method of claim 1 , wherein the application plane identity is one of a MCPTT client identity and a MCPTTT group identity, wherein the signaling plane identity is at least one of a public user identity, an IP multimedia public identity (IMPU), a tel uniform resource identifier (tel URI), and a mobile subscriber integrated services digital network (MSISDN) identity,

wherein the signaling plane entity is one of a session initiation protocol (SIP) core signaling plane entity, internet protocol (IP) multimedia subsystem (IMS) core signaling plane entity, and a home subscriber server (HSS) entity.

5. The method of claim 1 , wherein the application plane identity of the first MCPTT client and the application plane identity of the at least one second MCPTT client in the first request message is encrypted by the first MCPTT client,

wherein the application plane identity of the at least one second MCPTT client in the at least one second request message is encrypted by the MCPTT server, wherein the MCPTT server sends the encrypted application plane identities to the first MCPTT client.

6. The method of claim 1 , wherein the MCPTT server decrypts the application plane identity of the first MCPTT client and the application plane identity of the at least one second MCPTT client by:

fetching an security key associated with the first MCPTT client; and

decrypting the application plane identity of the first MCPTT client and the application plane identity of the at least one second MCPTT client in the first request message based on the security key.

7. A method for identity management across multiple planes, the method comprising:

receiving, by a signaling plane entity, a first request message from a first mission critical push to talk (MCPTT) client to establish a call with at least one second MCPTT client, wherein the first request message comprises an application plane identity of the first MCPTT client and an application plane identity of the at least one second MCPTT client;

sending, by the signaling plane entity, the first request message to an MCPTT server; and

receiving, by the signaling plane entity, at least one second request message from the MCPTT server to establish the call to the at least one second MCPTT client, wherein the at least one second request message comprises at least one signaling plane identity of the at least one second MCPTT client.

8. The method of claim 7 , wherein the signaling plane identity of the at least one second MCPTT client is predefined and is stored in an identity management entity during service registration,

wherein the identity management entity is stored at one of the MCPTT server, a group management server, and a signaling plane domain entity.

9. The method of claim 7 , wherein the application plane identity is one of a MCPTT client identity and a MCPTTT group identity, wherein the signaling plane identity is at least one of a public user identity, an IP multimedia public identity (IMPU), a tel uniform resource identifier (tel URI), and a mobile subscriber integrated services digital network (MSISDN) identity,

wherein the signaling plane entity is one of a session initiation protocol (SIP) core signaling plane entity, internet protocol (IP) multimedia subsystem (IMS) core signaling plane entity, and a home subscriber server (HSS) entity.

10. The method of claim 7 , wherein the application plane identity of the first MCPTT client and the application plane identity of the at least one second MCPTT client in the first request message is encrypted by the first MCPTT client,

wherein the application plane identity of the at least one second MCPTT client in the at least one second request message is encrypted by the MCPTT server, wherein the MCPTT server sends the encrypted application plane identities to the first MCPTT client.

11. A mission critical push to talk (MCPTT) server for identity management across multiple planes, comprising:

a memory unit; and

a processor unit coupled to the memory unit, where the processor unit is configured to:

receive a first request message to establish a call between a first MCPTT client and at least one second MCPTT client from a signaling plane entity, wherein the first request message comprises an application plane identity of the first MCPTT client and an application plane identity of the at least one second MCPTT client;

translate the application plane identity of the at least one second MCPTT client to a signaling plane identity of the at least one second MCPTT client; and

send at least one second request message comprising the signaling plane identity of the at least one second MCPTT client to the at least one second MCPTT client to establish the call via the signaling plane entity.

12. The MCPTT server of claim 11 , wherein translate the application plane identity of the at least one second MCPTT client to the signaling plane identity of the at least one second MCPTT client comprising:

retrieving a MCPTT client identity for each of the at least one second MCPTT client associated with the application plane identity;

identifying the signaling plane identity corresponding to each of the MCPTT identity from an identity management entity; and

translating the application plane identity to the signaling plane identity for each of the at least one second MCPTT client.

13. The MCPTT server of claim 11 , wherein the signaling plane identity of the at least one second MCPTT client is predefined and is stored in an identity management entity during service registration,

wherein the identity management entity is stored at one of the MCPTT server, a group management server, and a signaling plane domain entity.

14. The MCPTT server of claim 11 , wherein the application plane identity is one of a MCPTT client identity and a MCPTTT group identity, wherein the signaling plane identity is at least one of a public user identity, an IP multimedia public identity (IMPU), a tel uniform resource identifier (tel URI), and a mobile subscriber integrated services digital network (MSISDN) identity,

wherein the signaling plane entity is one of a session initiation protocol (SIP) core signaling plane entity, internet protocol (IP) multimedia subsystem (IMS) core signaling plane entity, and a home subscriber server (HSS) entity.

15. The MCPTT server of claim 11 , wherein the application plane identity of the first MCPTT client and the application plane identity of the at least one second MCPTT client in the first request message is encrypted by the first MCPTT client,

wherein the application plane identity of the at least one second MCPTT client in the at least one second request message is encrypted by the MCPTT server, wherein the MCPTT server sends the encrypted application plane identities to the first MCPTT client.

16. The MCPTT server of claim 11 , wherein the MCPTT server decrypts the application plane identity of the first MCPTT client and the application plane identity of the at least one second MCPTT client by:

fetching an security key associated with the first MCPTT client; and

decrypting the application plane identity of the first MCPTT client and the application plane identity of the at least one second MCPTT client in the first request message based on the security key.

17. The signaling plane entity of claim 11 , wherein the application plane identity of the first MCPTT client and the application plane identity of the at least one second MCPTT client in the first request message is encrypted by the first MCPTT client,

wherein the application plane identity of the at least one second MCPTT client in the at least one second request message is encrypted by the MCPTT server, wherein the MCPTT server sends the encrypted application plane identities to the first MCPTT client.

18. A signaling plane entity for identity management across multiple planes, comprising:

a memory unit; and

a processor unit coupled to the memory unit, where the processor unit is configured to:

receive a first request message from a first mission critical push to talk (MCPTT) client to establish a call with at least one second MCPTT client, wherein the first request message comprises an application plane identity of the first MCPTT client and an application plane identity of the at least one second MCPTT client;

send the first request message to an MCPTT server;

receive at least one second request message from the MCPTT server comprising at least one signaling plane identity of the at least one second MCPTT client; and

establish the call with the at least one second MCPTT client based on the signaling plane identity.

19. The signaling plane entity of claim 18 , wherein the signaling plane identity of the at least one second MCPTT client is predefined and is stored in an identity management entity during service registration,

wherein the identity management entity is stored at one of the MCPTT server, a group management server, and a signaling plane domain entity.

20. The signaling plane entity of claim 18 , wherein the application plane identity is one of a MCPTT client identity and a MCPTTT group identity, wherein the signaling plane identity is at least one of a public user identity, an IP multimedia public identity (IMPU), a tel uniform resource identifier (tel URI), and a mobile subscriber integrated services digital network (MSISDN) identity,

wherein the signaling plane entity is one of a session initiation protocol (SIP) core signaling plane entity, internet protocol (IP) multimedia subsystem (IMS) core signaling plane entity, and a home subscriber server (HSS) entity.