Method for deploying, provisioning and storing initial filter criteria

• US 20060140385A1
• Filed: 12/27/2004
• Published: 06/29/2006
• Est. Priority Date: 12/27/2004
• Status: Active Grant

• Current Assignee: Alcatel-Lucent USA, Inc. (Nokia Corporation)
• Original Assignee: Lucent Technologies, Inc. (Nokia Corporation)
• Inventors: Murakami, Kazutaka, Haase, Oliver
• Granted Patent: US 7,643,626 B2
• Time in Patent Office: Days
• US Class Current: 379/221.90
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/4588 containing mobile subscriber information, e.g. home subscriber server [HSS]
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• 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: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

The inventors provide herein methods for the decomposition of initial Filter Criteria (iFCs) into user-independent, global data and user specific data. In various embodiments of the present invention, the approach is based on Trigger point templates that represent families of trigger points, which are able to be instantiated to real trigger points by adding missing user specific data. Trigger point templates are specified at service deployment time and are instantiated to real trigger points and complemented with the other iFC components to form complete iFCs at the time of service subscription. It is demonstrated that the trigger point methods of the present invention facilitate the storing, provisioning and downloading of initial filter criteria and are beneficial in terms of at least storage and run-time efficiency.

Claims

1. A method for efficient implementation of initial filter criteria (iFC) related to a respective user service in a provider network, comprising:

decomposing said iFC into user specific parameters and user independent parameters.

2. The method of claim 1, wherein respective user specific parameters are provided for use in said iFC for execution of said user service by a respective user at a time of subscription to said service.

3. The method of claim 1, wherein said user independent parameters comprise global service data.

4. The method of claim 1, wherein said user independent parameters are provided to said iFC at a time of deployment of said service.

5. The method of claim 1, wherein said iFC only needs to be recorded in a storage device once for all users of said provider network having access to said storage device and desiring the execution of said service.

6. The method of claim 5, wherein a placeholder is recorded for each user specific parameter in said iFC until respective user specific parameters are provided to said iFC for execution of said service.

7. The method of claim 5, wherein said iFC is recorded in said storage device using Extensible Markup Language.

8. The method of claim 5, wherein said storage device comprises a Home Subscriber Server (HSS).

9. The method of claim 5, wherein said iFC is downloaded from said storage device and recorded in a Call Session Control Function (CSCF) server which delegates execution user services.

10. The method of claim 9, wherein said CSCF comprises a Serving CSCF.

11. The method of claim 9, wherein said iFC is recorded in said Serving CSCF using Extensible Markup Language.

12. The method of claim 1, wherein said iFC is a global service identifier.

13. The method of claim 1, wherein said iFC comprises a Trigger Point (TP) template.

14. A method for efficient storage of initial filter criteria (iFCs) associated with respective user services in a provider network, comprising:

decomposing said iFCs into user specific service parameters and user independent service parameters related to the execution of said respective user services such that each of said iFCs related to a respective user service only needs to be recorded in a storage device once for all users having access to said storage device and desiring the execution of said services, wherein a placeholder is stored for each of said user specific parameters and said user specific parameters are respectively provided to said iFCs for execution of said respective user services by a respective user at a time of execution of said services.

15. The method of claim 14, wherein said iFCs are stored in said storage device using Extensible Markup Language.

16. The method of claim 14, wherein said storage device comprises a Home Subscriber Server (HSS).

17. The method of claim 14, wherein said iFC comprises a Trigger Point (TP) template.

18. A method for deploying a new service in a provider network, comprising:

upon receiving a request for a new service, deploying a respective service code to at least one application server and storing in a memory device an identifier of said at least one application server that hosts said service code;

defining a Trigger Point (TP) template for said new service and storing said TP template in said memory device, said TP template comprising global service data and user specific service parameters; and

assigning a default value and a description for each of said user specific service parameters in said TP template, said description indicating what user specific data is to be inserted into said TP template.

19. The method of claim 18, further comprising:

provisioning a Service Info field of said TP template.

20. The method of claim 19, wherein said provisioning comprises storing in said memory device a name for a Service Info character string.

21. The method of claim 19, wherein said provisioning comprises storing in said memory device a provisioning screen for said service.

22. The method of claim 18, further comprising determining and storing in said memory device a priority for said service.

23. The method of claim 18, further comprising determining a default handling for said service.

24. The method of claim 23, wherein said default handling comprises terminating a session if a critical service is not available.

25. The method of claim 23, wherein said default handling comprises continuing a session if a service is not available.

26. The method of claim 18, further comprising:

upon receiving a user'"'"'s subscription request for a service, assigning at least one application server hosting said service as a host server and storing in a memory device, an identifier for said at least one application server; and

provisioning said TP template with user specific actual parameters received in said subscription request.

27. An apparatus comprising a memory and a processor, said apparatus adapted to perform the steps of:

upon receiving a request for a new service, deploying a respective service code to at least one application server and storing in a memory device an identifier of said at least one application server that hosts said service code;

defining a Trigger Point (TP) template for said new service and storing said TP template in said memory device, said TP template comprising global service data and user specific service parameters; and

assigning a default value and a description for each of said user specific service parameters in said TP template, said description indicating what user specific data is to be inserted into said TP template.

28. The apparatus of claim 27, wherein said apparatus comprises a Serving Call Session Control Function (SCSCF) server.

29. The apparatus of claim 27, further adapted to perform the steps of:

upon receiving a user'"'"'s subscription request for a service, assigning at least one application server hosting said service as a host server and storing in a memory device, an identifier for said at least one application server; and

provisioning said TP template with user specific actual parameters received in said subscription request.