Method of defining a SIP message body for communications between core network elements

• US 20040028080A1
• Filed: 03/07/2003
• Published: 02/12/2004
• Est. Priority Date: 08/06/2002
• Status: Abandoned Application

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Peters, Robert Yeager Jr., Samarasinghe, Harish
• Application Number:
  US10/384,223
• Publication Number:
  US 20040028080A1
• Time in Patent Office: Days
• US Class Current: 370/486
• CPC Class Codes: H04L 12/1425 involving dedicated fields in the data packet for billing purposes
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related

Abstract

A Session Initiation Protocol (SIP) request message and a SIP response message which are each adapted for communication between a plurality of network elements located on a multi-media services provider system for processing requests for multi-media services. The SIP request message includes a header region and a body region. The body region of the SIP request message can include a number of information parameters, such as, a border element identifier, a charge number parameter, a local address and transport area, a carrier, a calling party number, a charge party station type and a collected address. The SIP response message also includes a header portion and a body portion. The body portion of the SIP response message includes a number of service specific information parameters, such as a collected address, primary and alternate routing addresses, an alternate routing condition, manipulated digits and recording instructions.

Claims

1. A method of forming a multi-media communication path between at least a calling communication device and at least a destination communication device, the method comprising:

receiving a request for a multi-media service at a multi-media provider system;

processing the call request at the multi-media provider system for generating a Session Initiation Protocol (SIP) INVITE message; and

sending the SIP INVITE message to at least one processor of the multi-media provider system for processing the request for the multi-media service, wherein the SIP INVITE message includes at least one body portion having at least one information element required for providing call processing and service processing for the request for the multi-media service.

2. The method of claim 1, wherein processing the call request at the multi-media provider system includes processing the call request at a border element located on the multi-media provider system.

3. The method of claim 1, wherein processing the call request at the multi-media provider system includes processing the call request at a call control element located on the multi-media provider system.

4. The method of claim 3, wherein generating the SIP INVITE message includes providing border element identifier information in the at least one body portion of the SIP INVITE message.

5. The method of claim 4, wherein generating the SIP INVITE message includes providing charge number related information in the at least one body portion of the SIP INVITE message.

6. The method of claim 5, wherein generating the SIP INVITE message includes providing local access and transport area related information in the at least one body portion of the SIP INVITE message.

7. The method of claim 6, wherein generating the SIP INVITE message includes providing carrier related information in the at least one body portion of the SIP INVITE message.

8. The method of claim 7, wherein generating the SIP INVITE message includes providing calling party number related information in the at least one body portion of the SIP INVITE message.

9. The method of claim 8, wherein generating the SIP INVITE message includes providing charge party station type related information in the at least one body portion of the SIP INVITE message.

10. The method of claim 9, wherein generating the SIP INVITE message includes providing Customer Identifier related information in the at least one body portion of the SIP INVITE message.

11. The method of claim 10, wherein generating the SIP INVITE message includes providing collected address related information in the at least one body portion of the SIP INVITE message.

12. The method of claim 11, further including:

processing the SIP INVITE message at the processor for generating a SIP Redirect message; and

sending the SIP Redirect message to the call control element, wherein the SIP Redirect message includes at least one body portion having at least one information element required for providing call processing and service processing of the multi-media service request.

13. The method of claim 12, wherein generating the SIP Redirect message includes providing a collected address parameter in the at least one body portion of the SIP Redirect message.

14. The method of claim 13, wherein generating the SIP Redirect message includes providing a primary routing address parameter in the at least one body portion of the SIP Redirect message.

15. The method of claim 14, wherein generating the SIP Redirect message includes providing an alternate routing address parameter in the at least one body portion of the SIP Redirect message.

16. The method of claim 15, wherein generating the SIP Redirect message includes providing an alternate routing condition parameter in the at least one body portion of the SIP Redirect message.

17. The method of claim 16, wherein generating the SIP Redirect message includes providing a manipulated digits parameter in the at least one body portion of the SIP Redirect message.

18. The method of claim 17, wherein generating the SIP Redirect message includes providing a Carrier Identification Code parameter in the at least one body portion of the SIP Redirect message.

19. The method of claim 18, wherein generating the SIP Redirect message includes providing a Carrier Usage parameter in the at least one body portion of the SIP Redirect message.

20. The method of claim 19, wherein generating the SIP Redirect message includes providing a recording instruction parameter in the at least one body portion of the SIP Redirect message.

21. The method of claim 20, wherein generating the SIP Redirect message includes providing a recording information parameter in the at least one body portion of the SIP Redirect message.

22. A Session Initiation Protocol (SIP) message adapted for communication between a plurality of network elements to form a multi-media communication path between at least a calling communication device and at least a destination communication device, the SIP message comprising:

a header portion; and

a body portion, wherein the body portion includes at least one information element required for providing call processing and service processing for at least one request for at least one multi-media service.

23. The SIP message of claim 22, wherein the body portion further includes border element identifier information.

24. The SIP message of claim 23, wherein the body portion further includes charge number related information.

25. The SIP message of claim 24, wherein the body portion further includes local access and transport area related information.

26. The SIP message of claim 25, wherein the body portion further includes carrier related information.

27. The SIP message of claim 26, wherein the body portion further includes calling party number related information.

28. The SIP message of claim 27, wherein the body portion further includes charge party station type related information.

29. The SIP message of claim 28, wherein the body portion further includes collected address related information.

30. The SIP message of claim 29, wherein the body portion further includes Customer Identifier parameter.

31. The SIP message of claim 30, wherein the body portion further includes a Test Query parameter.

32. The SIP message of claim 31, comprising a SIP INVITE message.

33. The SIP message of claim 22, wherein the body portion further includes a collected address parameter.

34. The SIP message of claim 33, wherein the body portion further includes a primary routing address parameter.

35. The SIP message of claim 34, wherein the body portion further includes an alternate routing address parameter.

36. The SIP message of claim 35, wherein the body portion further includes an alternate routing condition parameter.

37. The SIP message of claim 36, wherein the body portion further includes a manipulated digits parameter.

38. The SIP message of claim 37, wherein the body portion further includes a Carrier Identification Code parameter.

39. The SIP message of claim 38, wherein the body portion further includes a Carrier Usage parameter.

40. The SIP message of claim 39, wherein the body portion further includes a recording instruction parameter.

41. The SIP message of claim 40, wherein the body portion further includes a recording information parameter.

42. The SIP message of claim 41, wherein the body portion further includes a Session Gapping parameter.

43. The SIP message of claim 42, wherein the body portion further includes a Error Description parameter.

44. The SIP message of claim 43, comprising a SIP Redirect message.