The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Dec. 11, 2012
Filed:
Aug. 24, 2007
Can Paul Boyacigiller, Annapolis, MD (US);
Christopher Charles Dacombe, Ellicott City, MD (US);
Praveen Babu Dharmavaram, Laurel, MD (US);
Raghu Nandan, Rockville, MD (US);
Sreenivasa R. Pamidala, Crofton, MD (US);
Zhijian Pan, Clarksville, MD (US);
Bouna Sall, Bowie, MD (US);
Can Paul Boyacigiller, Annapolis, MD (US);
Christopher Charles Dacombe, Ellicott City, MD (US);
Praveen Babu Dharmavaram, Laurel, MD (US);
Raghu Nandan, Rockville, MD (US);
Sreenivasa R. Pamidala, Crofton, MD (US);
Zhijian Pan, Clarksville, MD (US);
Bouna Sall, Bowie, MD (US);
International Business Machines Corporation, Armonk, NY (US);
Abstract
The present invention discloses use of resource lists to invoke multiple services in an IMS environment. More specifically, SIP clients can exchange XML content with each other and/or with SIP servers that includes an XCAP resource list. A list entry can exist for each service that is to be included within a communication session. Each service specifying entry can include sub-attributes for the service, which comprise attribute-value pairs able to be read using standard conventions. Use of the resource lists alleviates a need to define a schema and write custom code each time a new service is developed. In one embodiment, additional nested XCAP resource lists can be used to define content that is to be shared among multiple services. For example, a resource list can be used to define a participant list, which is shared as common input data across the multiple services.