Apparatus and method for IM to PTT correlation of mobile phones as associated devices

• US 20060058012A1
• Filed: 09/14/2004
• Published: 03/16/2006
• Est. Priority Date: 09/14/2004
• Status: Active Grant

• Current Assignee: Unify Inc. (Atos SE)
• Original Assignee: Siemens Information And Communication Networks, Inc.
• Inventors: Beyda, William J., Caspi, Rami
• Granted Patent: US 7,450,934 B2
• Time in Patent Office: Days
• US Class Current: 455/415
• CPC Class Codes: H04L 12/1813 for computer conferences, e.g. chat rooms instant messaging H04L51/04; protocols for multimedia communication H04L65/1101; arrangements for multi-party communication H04L65/403; telephonic conference arrangements H04M3/56; television conference systems H04N7/15
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/4061 Push-to services, e.g. push-to-talk or push-to-video
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04M 7/0027 Collaboration services where a computer is used for data transfer and the telephone is used for telephonic communication
• CPC Class Codes: H04W 28/18 Negotiating wireless communication parameters
• CPC Class Codes: H04W 4/10 Push-to-Talk [PTT] or Push-On-Call services
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 76/45 for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support

Abstract

Some embodiments provide a system and method for enabling automatic call configuration to associated devices of parties involved in a data session. The call configuration involves a computing device utilized by an originating party. The originating party has an associated device other than the computing device which can be used for supplemental communication. The originating party picks or initiates a process which picks one or more destination parties to which supplemental communication is desired. Identifiers identifying a destination party or parties is forwarded to a mobile application server. The mobile application server can then perform an optional look-up to determine unique device identifiers for associated devices of the destination party or parties. The destination party identifier(s) and/or unique device identifiers is sent by the mobile application server to the associated device of the originating party. The associated device of the originating party is automatically configured to directly connect to the destination device with a single button press, like the PTT button found in some cell phone models.

Claims

1. A system for sending to an associated device utilized by a originating party a unique ID identifying an associated device utilized by a destination party, said originating party and destination party in a data session, said system comprising:

a computing device utilized by said originating party in said data session, said computing device sending an identifier for said destination party; and

a mobile application server capable of communicating with said computing device, said mobile application server utilizing said identifier for said destination party in order to send a unique ID to said associated device utilized by said originating party.

2. A system according to claim 1 wherein said associated device utilized by said originating party is a mobile communication device.

3. A system according to claim 2 wherein said mobile communication device at least one of a cellular telephone, a satellite telephone and a PDA.

4. A system according to claim 1 wherein said phone number is sent by said mobile application server in order to configure a push-to-talk capability of said associated device.

5. A system according to claim 4 further wherein said push-to-talk capability is activated by said originating party in order to place a call to said associated device utilized by said destination party.

6. A system according to claim 1 wherein said phone number is displayed on said associated device utilized by said originating party.

7. A system according to claim 1 wherein said data session is at least one of a instant messaging session, an instant messaging conference, a conference call, and a data collaboration session.

8. A system according to claim 1 wherein said unique ID is sent for each of a plurality other parties participating in said data session.

9. A system according to claim 1 wherein said mobile application server is the IP Multimedia Subsystem server.

10. A system according to claim 1 wherein said data session is an OpenScape configured session.

11. A system according to claim 1 wherein management of said data session is responsible for said associated devices.

12. A system according to claim 1 wherein said mobile application server includes a mechanism to look-up said unique ID based upon said identifier.

13. A system according to claim 8 wherein a list of said unique IDs corresponding to at least some of said other parties participating in said data session is sent to said associated device utilized by said originating party.

14. A system according to claim 5 wherein said call is a voice call.

15. A system according to claim 5 wherein said call is a data call.

16. A system according to claim 15 wherein said data call is short message service call.

17. A system according to claim 1 wherein said mobile application server and said computing device communicate via a data network.

36. A method according to claim 1 wherein said mobile application server is coupled to at least one wireless communication network, said at least one wireless communication network capable of communicating with said mobile communication device.

18. A method during a data session for automatic call configuration of an originating party'"'"'s associated device to a destination party'"'"'s associated device, said originating party and destination party participating in said data session, the method comprising:

sending from said originating party an identifier for said destination party;

determining a unique ID for said destination party'"'"'s associated device based on said identifier for said destination party; and

sending said unique ID to said originating party'"'"'s associated device such that a call or connection can be placed to said unique ID.

19. A method according to claim 18 further comprising:

said originating party selecting said destination party.

20. A method according to claim 18 further comprising:

receiving said identifier for said destination party.

21. A method according to claim 18 wherein determining said unique ID and sending said unique ID are performed by a mobile application server.

22. A method according to claim 19 wherein said sending from said originating party is performed by a computing device.

23. A method according to claim 18 wherein determining includes looking up said unique ID using said identifier for said destination party.

24. A method according to claim 18 wherein said unique ID is part of said identifier for said destination party.

25. A method according to claim 18 wherein said unique ID is a key to said identifier for said destination party.

26. A method according to claim 21 further comprising:

configuring a calling feature on said originating party'"'"'s associated device with said unique ID.

27. A method according to claim 26 wherein said calling feature is one or more of a last number dialed feature, a push-to-talk capability, and a call log selection feature.

28. A method according to claim 18 further comprising:

said originating party'"'"'s associated device displaying said unique ID.

29. A method according to claim 18 further comprising:

sending said identifier for said destination party to said originating party'"'"'s associated device in addition to said unique ID.

30. A method according to claim 26 wherein said calling feature is activated by said originating party in order to place said call to said destination party'"'"'s associated device.

31. A method according to claim 21 wherein said mobile application server is the IP Multimedia Subsystem server.

32. A method according to claim 18 wherein said data session includes at least one of a data collaboration session, an instant messaging session, a conferencing session and instant message conferencing session.

33. A method according to claim 18 wherein said data session is an OpenScape configured session.

34. A method according to claim 18 wherein said originating party'"'"'s associated device is a mobile communication device.

35. A method according to claim 34 wherein said mobile communication device at least one of a cellular telephone, a satellite telephone and a PDA.

37. A method according to claim 18 wherein said call is a voice call.

38. A method according to claim 18 wherein said call is a data call.

39. A method according to claim 38 wherein said data call is short message service call.

40. A method according to claim 18 wherein sending, determining and sending a unique ID are repeated for each of a plurality of destination parties.

41. A method according to claim 40 wherein said originating party'"'"'s associated device receives a list containing each said unique ID.

42. A method according to claim 40 wherein each said unique ID in said list is accompanied by a corresponding said identifier of said destination party.