Methods of transmitting a message to a message server in a push-to-talk network

• US 20060046757A1
• Filed: 09/02/2004
• Published: 03/02/2006
• Est. Priority Date: 09/02/2004
• Status: Active Grant

• Current Assignee: Sonim Technologies, Inc.
• Original Assignee: Sonim Technologies, Inc.
• Inventors: Emami-Nouri, Mohsen, Hoover, Christopher
• Granted Patent: US 7,415,284 B2
• Time in Patent Office: Days
• US Class Current: 455/518
• 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: H04M 3/533 Voice mail systems
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04W 88/184 Messaging devices, e.g. message centre

Abstract

In a push-to-talk communications network, a method of transmitting a message from a sending device to a set of receiving devices is disclosed. The method includes selecting the set of receiving devices from a contact list on the sending device, such that each of the receiving devices has an address on the contact list. The method also includes transmitting the message to a message server, wherein the sending device is coupled to the message server; storing the message within the message server; and assigning the message an identifier. The method further includes notifying the set of receiving devices that the message can be retrieved, wherein each of the set of receiving devices is coupled to the message server. Advantages of the invention include a standards-based solution that combines the flexibility of mobile messaging with the ease-of-use of voice.

Claims

1. In a push-to-talk communications network, a method of transmitting a first message from a sending device to a set of receiving devices, comprising:

selecting said set of receiving devices from a contact list on said sending device, such that each of said receiving devices has an address on said contact list;

transmitting said first message to a message server, wherein said sending device is coupled to said message server;

storing said first message within said message server;

assigning said first message an identifier;

notifying said set of receiving devices that said first message can be retrieved, wherein each of said set of receiving devices is coupled to said message server.

2. The method of claim 1 further including the step of establishing a message session before the step of transmitting said first message to said message server.

3. The method of claim 1, wherein said notification is displayed in a contact list on each of said set of receiving devices.

4. The method of claim 1, wherein said notification is displayed as a member of a group contained within a contact list on each of said set of receiving devices.

5. The method of claim 1, wherein said notification is displayed within an inbox on each of said set of receiving devices.

6. The method of claim 5, wherein said notification can be added or deleted from said inbox using a group list management protocol.

7. The method of claim 5, wherein said inbox is an instant talk group on each of said set of receiving devices.

8. The method of claim 5, wherein said entry on said inbox comprises a pointer to said first message on said message server.

9. The method of claim 1, wherein said notification is an entry on the said contact list associated with a SIP URI.

10. The method of claim 1, wherein said identifier is a SIP URI.

11. The method of claim 10, wherein said SIP URI includes a transaction priority field.

12. The method of claim 11, wherein said SIP URI includes a display placement field.

13. The method of claim 12, wherein said SIP URI includes a user licensing field.

14. The method of claim 1, wherein said sending device and said set of receiving devices are asynchronously coupled to said message server.

15. The method of claim 1, wherein said push-to-talk communications network is half-duplex.

16. The method of claim 1, wherein said message server is a message store.

17. The method of claim 16, wherein said message store is integrated into said push-to-talk communications network.

18. The method of claim 16, wherein said message store is external to said push-to-talk communications network.

19. The method of claim 1, where said first message is an ad-hoc instant personal direct voice message.

20. The method of claim 1, where said first message is an ad-hoc instant group direct voice message.

21. The method of claim 1, where said first message is an instant group direct voice message.

22. The method of claim 1, wherein said message server is a content server.

23. The method of claim 22, wherein said first message is an infotainment message.

24. The infotainment message of claim 23, wherein said infotainment message can be pre-viewed before a purchase by selecting an associated SIP URI from a list.

25. The method of claim 24, wherein said infotainment is purchased by selecting an additional set of SIP URIs.

26. The method of claim 24, wherein said infotainment is delivered by selecting an additional set of SIP URIs

27. The infotainment message of claim 23, wherein said infotainment message is a ring tone.

28. The method of claim 1, wherein said notification displays a name of a user associated with said sending device.

29. The method of claim 1, wherein said notification displays a time said message was received at said message server.

30. The method of claim 1, wherein said notification displays a length of said message

31. The method of claim 1, wherein said first message includes a SIP TO header.

32. The method of claim 1, wherein said first message includes a SIP REPLY TO header.

33. The method of claim 1, wherein said notification includes an alert.

34. The method of claim 33, wherein said alert is visual.

35. The method of claim 33, wherein said alert is audible.

36. The method of claim 1, wherein said first message can be deleted based on said notification.

37. The method of claim 36, wherein said first message can be retrieved based on said notification.

38. The method of claim 37, wherein a floor is automatically granted to said message server when said first message is retrieved.

39. The method of claim 1, wherein said sending device further includes a message compose mode function.

40. The method of claim 39, wherein said compose mode function is separated from said contact list.

41. The method of claim 1, wherein a SIP URI of said first message may be associated with a display name of said sending device.

42. The method of claim 41, wherein said display name is stored on a group and list management server.

43. The method of claim 1, wherein a date and a time when said message was transmitted can be displayed on each of said set of receiving devices.

44. The method of claim 1, wherein a length of said message can be displayed on each of said set of receiving devices.

45. The method of claim 1, wherein a push-to-talk session can be established between said message server and said sending device.

46. The method of claim 45, wherein said push-to-talk session can be established using a SIP URI of said first message.

47. The method of claim 45, wherein said first message is associated with a named SIP URI of said sending device, and a second message may be transmitted to said message server for said sending device.

48. The method of claim 47, wherein said message session is terminated and a floor is released when said message has been transmitted to said message server.

52. The method of claim 1, wherein a PTT-specific AdhocGroupRequest parameter in a SIP TO header of said message is replaced with a DVM specific SIP URI.

53. The method of claim 52, wherein said DVM specific SIP URI is used as the value of said AdhocGroupRequest parameter by selecting a particular entry on a contact list by a sending device user.

54. The method of claim 53, wherein a DVM specific SIP URI is added to said contact list via a back-end function.

55. The method of claim 1, wherein said sending device can subscribe to a transmission status of said message by sending a SIP SUBSCRIBE request to said message server.

56. The method of claim 53, wherein said transmission status can be sent by said message server by sending back a SIP NOTIFY request.

57. The method of claim 1, wherein only said sending device can disconnect from a message session.

58. The method of claim 1, wherein there is a no-sending-device restriction for transmitting an instant ad-hoc personal message.

59. The method of claim 1, wherein there is a black list restriction for transmitting an instant ad-hoc personal message.

60. The method of claim 1, wherein there is a no-sending-device restriction for receiving an instant ad-hoc personal message.

61. The method of claim 1, wherein there is a black list restriction for receiving an instant ad-hoc personal message

62. The method of claim 1, wherein only a message server box can receive said message.

63. The method of claim 2, wherein a DVM session can be terminated by said message server after a voice inactivity timer expiry.

64. The method of claim 1, wherein said sending device registers with an IMS core with a DVMRequest feature tag in an accept-contact header.

65. The method of claim 64, wherein said DVMRequest feature tag comprises a +g.poc.talkdvmburst tag.

66. The method of claim 1, wherein said sending device adds a timer string to a SIP supported header in a SIP INVITE message.

67. The method of claim 1, wherein a content type application/vnd.poc.dvm.refer-to is deployed for supporting an instant group and an ad-hoc group message.

68. The method of claim 67, wherein said push-to-talk communications network can discover a DVM service identifier as part of a recipient list as distributed across a Refer-To header and a set of body attributes.

69. The method of claim 1, wherein a free text string of message group member, sender display name and a URI are carried by deploying a content-type application/vnd.poc.dvm.group-event+xml.

70. The method of claim 2, wherein said sending device requests said media connection by sending a SIP REFER using an existing SIP dialog of an established early session.

71. The method of claim 1, wherein after said sending device sends an INVITE request, said message server sends a SIP 100 Trying response to said sending device on behalf of any of said set of receiving devices.

72. The method of claim 1, wherein a request-URI in SIP INVITE request is populated with a configurable parameter that indicates to said message server to create and return a transient ad-hoc message group identity in a SIP 200 response.

73. The method of claim 72, wherein said configurable parameter is a comp-ad-hocGroupDvmRequest.

74. The method of claim 1, wherein a request-URI in SIP INVITE request is populated with a global group identity of each of said set of receiving devices.

75. The method of claim 1, wherein a request-URI in SIP INVITE request is populated with a configurable parameter retr-ad-hocGroupDvmRequest.

76. The method of claim 1, wherein a contact list can be used to select a receiving device from said set of receiving devices.

77. The method of claim 1, wherein a handset phone book can be used to select a receiving device from said set of receiving devices.

78. The method of claim 1, wherein a INVITE request can be sent with a message-adapted SIP URI to said message server acting for said set of receiving devices when pressing a PTT button.

79. The method of claim 1, wherein a REFER request can be sent with a message-adapted SIP URI to a said message server acting for said set of receiving devices when pressing a PTT button.

80. The method of claim 1, wherein said sending device is notified when said message server starts to receive said message.

81. The method of claim 2, wherein said message server automatically ends a DVM session after said message is transmitted.

82. The method of claim 2, wherein said message server automatically ends a DVM session after a defined interval of inactivity.

83. The method of claim 2, wherein said sending device transfers a push-to-talk session to said DVM session if said receiving device is unavailable or if the Do-Not-Disturb setting is set.

84. The method of claim 1, wherein said each of set of receiving devices is notified when said message server starts to receive said DVM.

85. The method of claim 1, wherein said message server has an interface to an external message store.

86. The method of claim 85, wherein said interface is a MMSC.

87. The method of claim 85, wherein said interface is a CS Voice Mail server.

88. The method of claim 85, wherein said DVM is transcoded when transmitted to said external message store.

89. The method of claim 1, wherein said message server screens a DVM session request to ensure if said DVM can be transmitted.

90. The method of claim 1, wherein each of said set of receiving devices can convert a DVM session into a said push-to-talk session.

91. The method of claim 1, wherein said first message is placed in said sending device sent folder for later playback along with a reply.

92. The method of claim 1, wherein said sending device can fallback to said DVM session in case of failure to establish a PTT session to said receiving devices.

93. The method of claim 1, said sending device is coupled to said message server in an internet protocol network.

94. The method of claim 1, wherein each of said set of receiving devices is coupled to said message server in an internet protocol network.

49. The method of 1, wherein a sending device user can control a maximum message length and a maximum message size of said message.

50. The method of 3, wherein said first receiving device comprises native PoC client application.

51. The method of 50, wherein said message is a contact in said contact list or a member of a group in said contact list.

95. In a push-to-talk communications network, a method of asynchronously transmitting a first message from a sending device to a set of receiving devices, comprising:

selecting said set of receiving devices from a contact list on said sending device, such that each of said receiving devices has an unique address on said contact list;

establishing a message session before the step of transmitting said first message to said message server;

transmitting said first message to a message server, wherein said sending device is coupled to said message server in an internet protocol network;

storing said first message within said message server;

assigning said message an unique identifier;

notifying said set of receiving devices that said first message can be retrieved, wherein each of said set of receiving devices is asynchronously coupled to said message server in an internet protocol network.

96. In a push-to-talk communications network, a method of asynchronously transmitting a first message from a sending device to a set of receiving devices, comprising:

selecting said set of receiving devices from a contact list on said sending device, such that each of said receiving devices has an unique address on said contact list;

establishing a message session before the step of transmitting said first message to said message server;

transmitting said first message to a message server, wherein said sending device is coupled to said message server in an GSM/GPRS network;

storing said first message within said message server;

assigning said message an unique identifier;

notifying said set of receiving devices that said first message can be retrieved, wherein each of said set of receiving devices is asynchronously coupled to said message server in a GSM/GPRS network.