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 8,363,648 B2
• Filed: 05/20/2011
• Issued: 01/29/2013
• Est. Priority Date: 12/19/2002
• Status: Expired due to Fees

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property II LP (AT&T, Inc.)
• Inventors: Peters, Robert Y. Jr., Samarasinghe, Harish
• Primary Examiner(s): Sheikh, Ayaz
• Assistant Examiner(s): HALIYUR, VENKATESH N
• Application Number:
  US13/112,935
• Publication Number:
  US 20110216766A1
• Time in Patent Office: 620 Days
• Field of Search: 370228-503, 709205-248
• US Class Current: 370/356
• 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 comprising a processor; 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;

sending the second request message to a service broker element;

receiving a redirect message from the service broker element;

generating a third request message for the multi-media service; and

sending the third request message to at least one application server, wherein the third request message is for processing by the at least one application server to identify an advanced intelligent service.

2. The method of claim 1,

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

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

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

5. 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 of a call control element, cause the processor to perform operations for processing a request, the operations comprising:

receiving a first request message for a multi-media service at the 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;

sending the second request message to a service broker element;

receiving a redirect message from the service broker element;

generating a third request message for the multi-media service; and

sending the third request message to at least one application server, wherein the third request message is for processing by the at least one application server to identify an advanced intelligent service.

6. The non-transitory computer-readable medium of claim 5,

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

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

8. The non-transitory computer-readable medium 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. A call control element for processing a request, comprising:

a processor; and

a non-transitory computer-readable medium in communication with the processor, the non-transitory computer-readable medium having stored thereon a plurality of instructions, the plurality of instructions including instructions which, when executed by the processor, cause the processor to perform operations, the operations comprising;

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

processing 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;

sending the second request message to a service broker element;

receiving a redirect message from the service broker element;

generating a third request message for the multi-media service; and

sending the third request message to at least one application server, wherein the third request message is for processing by the at least on application server to identify an advanced intelligent service.