Method for PoC server to handle PoC caller preferences

• US 20060270362A1
• Filed: 05/27/2005
• Published: 11/30/2006
• Est. Priority Date: 05/27/2005
• Status: Active Grant

• Current Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Original Assignee: Motorola Mobility, Inc. (Lenovo Group Ltd.)
• Inventors: Jagadesan, Balakumar, Emrich, John E.
• Granted Patent: US 7,801,494 B2
• Time in Patent Office: Days
• US Class Current: 455/90.200
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1094 Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• 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: H04L 67/306 User profiles
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04M 2215/2093 Push to talk
• CPC Class Codes: H04M 3/53308 Message originator indirectly connected to the message centre, e.g. after detection of busy or absent state of a called party
• CPC Class Codes: H04W 4/10 Push-to-Talk [PTT] or Push-On-Call services
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/16 Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 76/45 for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
• CPC Class Codes: H04W 84/08 Trunked mobile radio systems

Abstract

A Push-to-X over Cellular (PoC) server (351) receives a server registration message (301) for a first called device from a second server. The PoC server (351) receives a PoC invitation message (310) with PoC preferences and a message (313) from an originating device (311). The PoC preferences determine what device to call first (e.g., a mobile device 315, 317) and how many hops the call can be forwarded (e.g., to a voicemail server) if the first-attempted device is not available, before discontinuing the connection. If a trigger, such as time elapsed, occurs for the first-attempted device (350) and the PoC preferences permit, the PoC server (351) sends an invitation message (360) to the second server (391). If the second server (391) is a recording server, the invitation message (360) includes a message (363) from the originating device that is compatible with the capabilities of the recording server (391).

Claims

1. A method for a Push-to-X over Cellular (PoC) server comprising:

receiving a server registration for a first called device from a second server;

receiving a PoC invitation message with PoC preferences from an originating device; and

sending an invitation message to the second server, if a trigger occurs for the first called device and the PoC preferences permit.

2. A method according to claim 1 further comprising, before sending an invitation message to the second server:

receiving PoC addresses for one or more called parties from the originating device; and

sending invitation messages to the one or more called parties.

3. A method according to claim 1 further comprising:

sending a “

BYE”

message to the first called device, if the trigger occurs for the first called device.

4. A method according to claim 1 further comprising:

receiving at least one recorded message from the originating device.

5. A method according to claim 4 wherein the at least one recorded message is at least one of:

a text message, an audio message, a picture message, and a video message.

6. A method according to claim 4 further comprising:

forwarding the at least one recorded message to the second server, if the trigger occurs for the first called device and the PoC preferences permit.

7. A method according to claim 6 further comprising:

sending a “

BYE”

message to the second server.

8. A method according to claim 6 further comprising, before forwarding the at least one recorded message to the second server:

determining messaging capabilities of the second server; and

modifying the at least one recorded message based on the messaging capabilities of the second server.

9. A method according to claim 4 further comprising:

determining messaging capabilities of the second server;

selecting one message of the at least one recorded message based on the messaging capabilities of the second server; and

forwarding the one message to the second server, if the trigger occurs for the first called device and the PoC preferences permit.

10. A method according to claim 4 further comprising:

determining messaging capabilities of the second server;

selecting one message of the at least one recorded message based on the messaging capabilities of the second server and a message preference of the originating device; and

forwarding the one message to the second server, if the trigger occurs for the first called device and the PoC preferences permit.

11. A method according to claim 4 further comprising:

selecting one message of the at least one recorded message that is compatible with messaging capabilities of the second server; and

forwarding the one message to the second server, if the trigger occurs for the first called device and the PoC preferences permit.

12. A method according to claim 11 further comprising:

sending a “

BYE”

message to the second server.

13. A method according to claim 1 further comprising:

sending a Real Time Protocol media message from the originating device.

14. A method according to claim 13 further comprising:

sending the Real Time Protocol media message to a second called device.

15. A method according to claim 1 wherein the server registration includes a PoC address for the second server.

16. A method according to claim 1 wherein the second server is a voicemail server.

17. A method according to claim 1 wherein the second server is an electronic mail server.

18. A method according to claim 1 wherein the second server is a multimedia messaging server.

19. A method according to claim 1 wherein the trigger is an elapsed timer.

20. A method according to claim 1 wherein the PoC preferences include a hop count limit.