Application service invocation

• US 8,644,460 B2
• Filed: 08/03/2010
• Issued: 02/04/2014
• Est. Priority Date: 07/29/2005
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Tai, Yung-Hwa, Welch, Gregory, Verlare, James L.
• Primary Examiner(s): Nguyen, Duc
• Assistant Examiner(s): Laekemariam, Yosef K
• Application Number:
  US12/849,622
• Publication Number:
  US 20100317334A1
• Time in Patent Office: 1,281 Days
• Field of Search: 370/467, 709/224, 379/221.03, 379/88.13, 379/88.17, 379/201.02, 379/265.09, 455/418
• US Class Current: 379/88.13
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1095 Inter-network session transfer or sharing
• CPC Class Codes: H04L 65/401 wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
• CPC Class Codes: H04M 3/42068 where the identifier is used to access a profile
• CPC Class Codes: H04M 3/4217 Managing service interactions
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04M 7/123 where the packet-switched network is an Internet Protocol Multimedia System-type network

Abstract

An Internet Protocol Multimedia Subsystem (IMS) includes a Serving-Call Session Control Function (S-CSCF). The S-CSCF includes a Service Capability Interaction Manager (SCIM) configured to invoke one or more application services in response to a message being received by the S-CSCF.

Claims

1. A method comprising:

identifying, using a Serving-Call Session Control Function (S-CSCF), a party of a message;

obtaining, using the S-CSCF and based on the identified party, a profile of the party,

the obtained profile including;

a first rule to invoke a macro application,

a second rule to invoke a micro application, and

information identifying an order for invoking the macro application and the micro application;

invoking, using the S-CSCF and based on the first rule, the macro application; and

invoking, using the S-CSCF and based on the second rule, the micro application,

the micro application and the macro application being invoked in an order that is based on the information identifying the order for invoking the macro application and the micro application.

2. The method of claim 1, further comprising:

detecting, based on the obtained profile, a trigger associated with the message; and

invoking, based on the obtained profile and the detected trigger, a second micro application.

3. The method of claim 1, where the message corresponds to a session initiation protocol (SIP) message,

the method further comprising:

parsing the SIP message to identify information in at least one of a header or a body of the SIP message,

where obtaining the profile comprises obtaining, based on the information in the at least one of the header or the body of the SIP message, the profile.

4. The method of claim 1, where invoking the macro application comprises:

transferring the message to a first device associated with the macro application, and

where invoking the micro application comprises;

transferring the message to a second device associated with the micro application.

5. The method of claim 1, further comprising:

detecting a trigger associated with the message;

identifying, based on the detected trigger, a second macro application and a second micro application; and

invoking the identified second macro application and the identified second micro application in an order that is based on the obtained profile.

6. The method of claim 1, further comprising:

obtaining, based on a second message, a second profile,

where the obtained second profile includes a third rule to invoke a second macro application; and

invoking, based on the third rule, the second macro application.

7. The method of claim 6, where obtaining the second profile comprises:

obtaining, based on identification information of a sender of the second message, the second profile.

8. A device comprising:

a memory to store instructions; and

a processor, to execute the instructions in the memory, to;

receive a call request,

obtain, based on the received call request, a user profile,

the obtained user profile including;

a Serving-Call Session Control Function (S-CSCF) rule to invoke a first application,

a Service Capability Interaction Manager (SCIM) rule to invoke a second application different than the first application, and

information identifying an order for invoking the first application and the second application,

invoke, using the S-CSCF rule included in the obtained user profile, the first application for the received call request, and

invoke, using the SCIM rule included in the obtained user profile, the second application for the received call request,

the first application and the second application being invoked based on the order identified in the obtained user profile.

9. The device of claim 8, where, when obtaining the user profile, the processor is to:

parse the received call request, and

obtain, based on parsing the received call request, the user profile.

10. The device of claim 8, where the received call request corresponds to a session initiation protocol (SIP) request, and

where the processor is to:

parse the SIP request to identify information in at least one of a header or a body of the SIP request,

where, when obtaining the user profile, the processor is to obtain, based on the information identified in at least one of a header or a body of the SIP request, the user profile.

11. The device of claim 8, where the obtained user profile further includes a second S-CSCF rule,

where the processor is further to:

identify, based on the second S-CSCF rule, a third application, and

invoke, using the second S-CSCF rule, the identified third application for the received call request.

12. The device of claim 8, where, when a call, associated with the received call request, is established, the processor is further to:

detect a trigger during the established call, and

invoke, based on detecting the trigger and based on the obtained user profile, a third application.

13. The device of claim 8, where the second application includes at least one of a voicemail function or a location function, and

where, when invoking the second application for the received call request, the processor is to:

invoke the at least one of the voicemail function or the location function for the received call request.

14. The device of claim 8, where, when invoking the first application for the received call request, the processor is to:

transfer the received call request to a device associated with the first application,

receive information from the device associated with the first application, and

forward, based on the received information, the received call request to a called party.

15. A non-transitory computer-readable medium for storing instructions, the instructions comprising:

a plurality of instructions which, when executed by a device, cause the device to;

receive a call request;

obtain, based on the received call request, a user profile,

the obtained user profile including;

a Serving-Call Session Control Function (S-CSCF) rule to invoke a first application,

a Service Capability Interaction Manager (SCIM) rule to invoke a second application different than the first application, and

information identifying an order for invoking the first application and the second application;

invoke, using the S-CSCF rule included in the obtained user profile, the first application for the received call request; and

invoke, using the SCIM rule included in the obtained user profile, the second application for the received call request,

the first application and the second application being invoked based on the order identified in the obtained user profile.

16. The non-transitory computer-readable medium of claim 15, where one or more instructions, of the plurality of instructions, to obtain the user profile, include:

one or more instructions to parse the received call request; and

one or more instructions to obtain, based on parsing the received call request, the user profile.

17. The non-transitory computer-readable medium of claim 15, where the received call request corresponds to a session initiation protocol (SIP) request, and

where the instructions further comprise:

one or more instructions to parse the SIP request to identify information in at least one of a header or a body of the SIP request,

where one or more instructions, of the plurality of instructions, to obtain the user profile, include one or more instructions to obtain, based on the information in the at least one of the header or the body of the SIP request, the user profile.

18. The non-transitory computer-readable medium of claim 15, where the obtained user profile further includes a second S-CSCF rule, and

where the instructions further comprise:

one or more instructions to identify, based on the second S-CSCF rule, a third application; and

one or more instructions to invoke, using the second S-CSCF rule, the third application for the received call request.

19. The non-transitory computer-readable medium of claim 15, the instructions further comprising:

one or more instructions to detect, when a call is established, a trigger during the call,

the call being associated with the received call request; and

one or more instructions to invoke, based on detecting the trigger and based on the obtained user profile, a third application.

20. The non-transitory computer-readable medium of claim 15, where the second application includes at least one of a voicemail function or a location function, and

where one or more instructions, of the plurality of instructions, to invoke the second application for the received call request include:

one or more instructions to invoke the at least one of the voicemail function or the location function for the received call request.