Interface call signaling protocol

• US 20050286542A1
• Filed: 08/25/2005
• Published: 12/29/2005
• Est. Priority Date: 12/18/2003
• Status: Abandoned Application

• Current Assignee: Barbara M. Desutter, Edward J. Neyens, Robert J Thomas, Thomas G. Hallin, William N. Shores
• Original Assignee: Barbara M. Desutter, Edward J. Neyens, Robert J Thomas, Thomas G. Hallin, William N. Shores
• Inventors: Hallin, Thomas G., Shores, William N., Thomas, Robert J., DeSutter, Barbara M., Neyens, Edward J.
• Application Number:
  US11/211,866
• Publication Number:
  US 20050286542A1
• Time in Patent Office: Days
• US Class Current: 370/401
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04W 4/10 Push-to-Talk [PTT] or Push-On-Call services
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• 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
• CPC Class Codes: H04W 80/10 adapted for application session management, e.g. SIP [Session Initiation Protocol] connection management H04W76/00; arrangements for session management H04L67/14
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

A third generation (3G) gateway (30) provides the facilities for extending a number of internet protocols (40, 64, 74, 83, 100, 110, 120 and 130) between a second generation (2G) network and a 3G network. The various messages of a session initiation protocol (SIP) are extended to provide user identification and server identification subfields (42). The SIP message extensions facilitate the communication of 2G and 3G networks for the purposes of implementing push-to-talk and dispatch service features.

Claims

1. An interface call signaling protocol for a communication system, using an internet protocol (IP), the interface call signaling protocol comprising:

an INVITE request field;

the INVITE request field including;

a user identification extension having direct routing information;

a server identification extension having a network address; and

a subscriber data base flag for indicating a table access is performed.

2. The interface call signaling protocol as claimed in claim 1, wherein there is further included:

a from header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

3. The interface call signaling protocol as claimed in claim 1, wherein there is further included:

a to header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

4. The interface call signaling protocol as claimed in claim 1, wherein there is further included:

a contact header field including;

a user identification extension having direct routing information;

a server identification extension having a network address; and

a cache flag for saving the user identification.

5. The interface call signaling protocol as claimed in claim 1, wherein there is further included:

a user agent field including;

a product extension indicating a “

voice signaling gateway”

; and

a product version extension.

6. The interface call signaling protocol as claimed in claim 1, wherein there is further included a content type header field including a media type extension representing a 2G gateway.

7. The interface call signaling protocol as claimed in claim 1, wherein there is further included a message body field including a call processing type media type extension representing a 2G gateway.

8. The interface call signaling protocol as claimed in claim 1, wherein:

the internet protocol includes session initiation protocol (SIP); and

the INVITE request field is a SIP INVITE request.

9. The interface call signaling protocol as claimed in claim 1, wherein for the internet protocol of a session description protocol when a message body indicates a multi-part message, there is further included an attribute extension for a session description protocol.

10. The interface call signaling protocol as claimed in claim 1, wherein there is further included:

a via header field;

a maximum forwards header field;

a call identification header field;

a Cseq header; and

a content length header.

11. A interface call signaling protocol for a communication system using an internet protocol (IP), the interface call signaling protocol comprising:

a from header field;

the from header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

12. The interface call signaling protocol as claimed in claim 11, wherein there is further included a to header field including:

a user identification extension having direct routing information; and

a server identification extension having a network address.

13. The interface call signaling protocol as claimed in claim 11, wherein there is further included a contact header field including a range extension for routing information.

14. The interface call signaling protocol as claimed in claim 11, wherein:

the internet protocol includes session initiation protocol (SIP); and

the INVITE response field is a SIP 301 INVITE response.

15. The interface call signaling protocol as claimed in claim 11, wherein there is further included:

a via head field;

a call identification header field;

a Cseq header field; and

a content length header field.

16. An interface call signaling protocol for a communication system, using an internet protocol (IP), the interface call signaling protocol comprising:

an INVITE response field;

a from header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

17. The interface call signaling protocol as claimed in claim 16, wherein there is further included a to header field including:

a user identification extension having direct routing information; and

a server identification extension having a network address.

18. The interface call signaling protocol as claimed in claim 16, wherein there is further included a contact header field including:

a user identification extension having direct routing information;

a server identification extension having a network address; and

a subscriber data base flag for indicating a table access is performed.

19. The interface call signaling protocol as claimed in claim 16, wherein:

the internet protocol includes session initiation protocol (SIP); and

the INVITE response field includes a SIP 302 INVITE response.

20. The interface call signaling protocol as claimed in claim 16, wherein there is further included:

a via header field;

a call identification header field;

a Cseq header field; and

a content length header field.

21. An interface call signaling protocol for a communication system, using an internet protocol (IP), the interface call signaling protocol comprising:

an INVITE response field;

a from header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

22. The interface call signaling protocol as claimed in claim 21, wherein there is further included:

a to header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

23. The interface call signaling protocol as claimed in claim 21, wherein there is further included:

a contact header field including;

a user identification extension having direct routing information;

a server identification extension having a network address; and

a cache flag for saving the user identification.

24. The interface call signaling protocol as claimed in claim 21, wherein there is further included a server header field including a product extension and a product version extension for interfacing purposes.

25. The interface call signaling protocol as claimed in claim 21, wherein for the internet protocol of a session description protocol when a message body indicates a session description message, there is further included an attribute extension for a session description protocol.

26. The interface call signaling protocol as claimed in claim 21, wherein:

the internet protocol includes session initiation protocol (SIP); and

the INVITE response field is a SIP 200 INVITE response.

27. The interface call signaling protocol as claimed in claim 21, wherein there is further included:

a via header field;

a call identification header field;

a Cseq header field;

a content type header field; and

a content length header field.

28. An interface call signaling protocol for a communication system, using an internet protocol (IP), the interface call signaling protocol comprising:

an INVITE response field;

a from header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

29. The interface call signaling protocol as claimed in claim 28, wherein there is further included:

a from header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

30. The interface call signaling protocol as claimed in claim 28 wherein there is further included:

a reason header field including;

a protocol extension;

a cause extension; and

a text extension.

31. The interface call signaling protocol as claimed in claim 28, wherein:

the internet protocol includes session initiation protocol (SIP); and

the INVITE response field is a SIP 4XX-6XX INVITE response.

32. The interface call signaling protocol as claimed in claim 28, wherein there is further included:

a via header field;

a call identification header field;

a Cseq header field; and

a content length header field.

33. An interface call signaling protocol for a communication system, using an internet protocol (IP), the interface call signaling protocol comprising:

an ACK request field;

a from header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

34. The interface call signaling protocol as claimed in claim 33, wherein there is further included:

a to header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

35. The interface call signaling protocol as claimed in claim 33, wherein:

the internet protocol includes session initiation protocol (SIP); and

the ACK request field is a SIP ACK request.

36. The interface call signaling protocol as claimed in claim 33, wherein there is further included:

a via header field;

a maximum forwards header field;

a call identification header field;

a Cseq header field;

a content type header field; and

a content length header field.

37. The interface call signaling protocol as claimed in claim 33, wherein for the internet protocol of a session description protocol when a message body indicates a session description message, there is further included an attribute extension for a session description protocol.

38. An interface call signaling protocol for a communication system, using an internet protocol (IP), the interface call signaling protocol comprising:

a message body for identifying a 2G gateway; and

a talker arbitration extension representing a plurality of parameters.

39. The interface call signaling protocol as claimed in claim 38, wherein there is further included:

an information request extension; and

a content type header field including an arbitration type extension.

40. The interface call signaling protocol as claimed in claim 38, wherein there is further included:

a from header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

41. The interface call signaling protocol as claimed in claim 38, wherein there is further included:

a to header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

42. The interface call signaling protocol as claimed in claim 39, wherein:

the internet protocol includes session initiation protocol (SIP); and

the information request extension includes a SIP INFO request.

43. The interface call signaling protocol as claimed in claim 38, wherein there is further included:

a via header field;

a maximum forwards header field;

a call identification header field;

a Cseq header field; and

a content length header field.

44. An interface call signaling protocol for a communication system, using an internet protocol (IP), the interface call signaling protocol comprising:

a BYE request field; and

a gateway call processing message body field including a call duration extension.

45. The interface call signaling protocol as claimed in claim 44, wherein there is further included:

a from header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

46. The interface call signaling protocol as claimed in claim 44, wherein there is further included:

a to header field including;

a user identification extension having direct routing information; and

a server identification extension having a network address.

47. The interface call signaling protocol as claimed in claim 44, wherein there is further included:

a reason header field including;

a protocol extension;

a cause extension; and

a text extension.

48. The interface call signaling protocol as claimed in claim 44, wherein there is further included a content type header field including a media type extension.

49. The interface call signaling protocol as claimed in claim 44, wherein there is further included:

a via header field;

a maximum forwards header field;

a call identification header field;

a Cseq header field; and

a content length header field.

50. The interface call signaling protocol as claimed in claim 44, wherein:

the internet protocol includes session initiation protocol (SIP); and

the BYE request field is a SIP BYE request.