SESSION INITIATION PROTOCOL (SIP) MESSAGE INCORPORATING A MULTI-PURPOSE INTERNET MAIL EXTENSION (MIME) MEDIA TYPE FOR DESCRIBING THE CONTENT AND FORMAT OF INFORMATION INCLUDED IN THE SIP MESSAGE

• US 20110216766A1
• Filed: 05/20/2011
• Published: 09/08/2011
• Est. Priority Date: 12/19/2002
• Status: Active Grant

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Peters, Robert Y. JR., Samarasinghe, Harish
• Granted Patent: US 8,363,648 B2
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/612 for unicast

Abstract

A system and method for processing a plurality of requests for multi-media services received at a call control element (CCE) defined on the system from a plurality of IP-communication devices. The system includes at least one Network Routing Element (NRE), a Service Broker (SB), a media sever, a plurality of application servers (ASs) and a plurality of border elements, all of which are coupled to the CCE. The CCE is adapted to receive requests for multi-media services and to generate subsequent requests for the multi-media services, which are communicated to the SB for processing. The subsequent requests can each include a Session Initiation Protocol (SIP) message including a message identifier portion having at least a first predetermined information field and a second predetermined information field. The message identifier portion of the SIP message declares the content and format of the SIP message to a recipient device defined on the system.

Claims

1. A method of processing a request, comprising:

receiving a first request message for a multi-media service at a call control element; and

processing the first request message at the call control element for generating a second request message for the multi-media service and including a content-type header portion having a media type field and a media subtype field, wherein the media type field describes a type of data, and wherein the media subtype field describes a format of the data.

2. The method of claim 1, further comprising:

processing the second request message at a service broker element for identifying a content of the second request message, wherein the identifying the content of the second request message includes identifying an advanced intelligent service requested by the second request message.

3. The method of claim 1, further comprising:

sending the second request message to a service broker element.

4. The method of claim 3, further comprising:

receiving a redirect message from the service broker element.

5. The method of claim 4, further comprising:

generating a third request message.

6. The method of claim 5, further comprising:

sending the third request message to at least one application server.

7. The method of claim 6, wherein the redirect message comprises information pertaining to the at least one application server.

8. The method of claim 7, wherein the information pertaining to the at least one application server comprises a primary application server and a secondary application server.

9. The method of claim 6, further comprising:

receiving the third request message for the multi-media service by the at least one application server; and

processing the third request message at the at least one application server to identify an advanced intelligent service.

10. A non-transitory computer-readable medium having stored thereon a plurality of instructions, the plurality of instructions including instructions which, when executed by a processor, cause the processor to perform a method for processing a request, comprising:

receiving a first request message for a multi-media service at a call control element; and

processing the first request message at the call control element for generating a second request message for the multi-media service and including a content-type header portion having a media type field and a media subtype field, wherein the media type field describes a type of data, and wherein the media subtype field describes a format of the data.

11. The non-transitory computer-readable medium of claim 10, further comprising:

processing the second request message at a service broker element for identifying a content of the second request message, wherein the identifying the content of the second request message includes identifying an advanced intelligent service requested by the second request message.

12. The non-transitory computer-readable medium of claim 10, further comprising:

sending the second request message to a service broker element.

13. The non-transitory computer-readable medium of claim 12, further comprising:

receiving a redirect message from the service broker element.

14. The non-transitory computer-readable medium of claim 13, further comprising:

generating a third request message.

15. The non-transitory computer-readable medium of claim 14, further comprising:

sending the third request message to at least one application server.

16. The non-transitory computer-readable medium of claim 15, wherein the redirect message comprises information pertaining to the at least one application server.

17. The non-transitory computer-readable medium of claim 16, wherein the information pertaining to the at least one application server comprises a primary application server and a secondary application server.

18. The non-transitory computer-readable medium of claim 15, further comprising:

receiving the third request message for the multi-media service by the at least one application server; and

processing the third request message at the at least one application server to identify an advanced intelligent service.

19. A call control element for processing a request, comprising:

a processor configured to;

receive a first request message for a multi-media service; and

process the first request message for generating a second request message for the multi-media service and including a content-type header portion having a media type field and a media subtype field, wherein the media type field describes a type of data, and wherein the media subtype field describes a format of the data.

20. The call control element of claim 19, wherein the processor is further configured to send the second request message to a service broker element.