SYSTEMS, METHODS, AND COMPUTER PROGRAM PRODUCTS FOR PROVIDING SERVICE INTERACTION AND MEDIATION IN A COMMUNICATIONS NETWORK

• US 20080260119A1
• Filed: 04/21/2008
• Published: 10/23/2008
• Est. Priority Date: 04/20/2007
• Status: Abandoned Application

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Marathe, Rohini, Ravishankar, Venkataramalah
• Application Number:
  US12/106,807
• Publication Number:
  US 20080260119A1
• Time in Patent Office: Days
• US Class Current: 379/93.01
• CPC Class Codes: H04M 3/42017 Customized ring-back tones
• CPC Class Codes: H04M 7/125 Details of gateway equipment

Abstract

Systems, methods, and computer program products for providing service interaction and mediation in a communications network are disclosed. According to one aspect, the subject matter described herein includes a system for providing service interaction and mediation in a communications network. The system includes a communications interface for receiving a client-to-SCIM message from a service client; and a service capability interaction manager (SCIM) module for providing service interaction between the service client and multiple application servers providing different types of services. Providing the service interaction includes receiving, from the communications interface, the client-to-SCIM service interaction message, and, in response to receiving the client-to-SCIM message, generating multiple SCIM-to-server messages and sending the SCIM-to-server messages to multiple application servers. Providing the service interaction also includes receiving multiple server-to-SCIM service interaction messages from at least some of the application servers that received the SCIM-to-server messages, and, in response to receiving the server-to-SCIM messages, generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages, and sending the SCIM-to-client message containing the aggregation to the service client via the communications interface.

Claims

1. A system for providing service interaction and mediation in a communications network, the system comprising:

a communications interface for receiving a client-to-SCIM message from a service client; and

a service capability interaction manager (SCIM) module for providing service interaction between the service client and a plurality of application servers providing different types of services, wherein providing the service interaction includes;

receiving, from the communications interface, the client-to-SCIM service interaction message, and, in response to receiving the client-to-SCIM message, generating a plurality of SCIM-to-server messages and sending the SCIM-to-server messages to at least some of the plurality of application servers; and

receiving a plurality of server-to-SCIM service interaction messages from at least some of the plurality of application servers that received the SCIM-to-server messages, and, in response to receiving the server-to-SCIM messages, generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages, and sending the SCIM-to-client message containing the aggregation to the service client via the communications interface.

2. The system of claim 1 wherein the service capability interaction manager module is configured to generate the SCIM-to-server messages based on an analysis of a component of the client-to-SCIM message.

3. The system of claim 1 wherein the communications interface and the service capability interaction manager module are co-located with a network signaling point.

4. The system of claim 1 wherein the SCIM module is configured to convert received client-to-SCIM messages between at least one of:

a SIP protocol and a non-SIP protocol;

a CAMEL protocol and an IMS protocol; and

one version of a protocol and another version of a protocol; and

an internal protocol used internally by the SCIM module and an external protocol, used by a network entity other than the SCIM module, that is different from the internal protocol.

5. The system of claim 1 wherein generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages includes suppressing duplicate SCIM-to-client messages to the service client.

6. The system of claim 1 wherein generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages includes consolidating information contained in a plurality of SCIM-to-client messages into a single SCIM-to-client message to the service client.

7. The system of claim 1 wherein the SCIM module is configured to generate at least one of call detail records (CDRs) for calls associated with messages processed by the SCIM module and transaction data records (TDRs) for transactions associated with messages processed by the SCIM module.

8. The system of claim 1 wherein the service capability interaction manager module is configured to manage message subscription and notification in a communications network, wherein managing message subscription and notification includes:

receiving, from at least some of the plurality of application servers, requests to be notified of specified events, and in response to receiving the requests, creating an aggregation of the notification requests and sending a message containing the aggregation to the service client;

maintaining mappings between the application servers and the specified events; and

receiving notification of an event, and, in response, identifying at least one application server subscribed to receive notification of the event using the mappings and notifying the at least one identified application server of the event.

9. The system of claim 8 wherein creating an aggregation of the notification requests and sending a message containing the aggregation to the service client includes forwarding to the service client a first request to be notified of a specific event and not forwarding to the service client subsequent requests to be notified of the specific event.

10. The system of claim 8 wherein creating an aggregation of the notification requests and sending a message containing the aggregation to the service client includes consolidating information contained in the notification requests into a single notification request and sending the single notification request to the service client.

11. The system of claim 8 wherein notifying the at least one identified application server of the event includes notifying a plurality of application servers of the event.

12. The system of claim 8 wherein notifying the at least one identified application server of the event includes:

notifying one of the plurality of application servers of the event;

receiving, from the one application server, a response to the notification;

determining, based on the response to the notification, whether to notify another of the plurality of application servers of the event, and, based on that determination, notifying another of the plurality of application servers of the event.

18. The system of claim 1 wherein the SCIM module is configured to generate at least one of call detail records (CDRs) for calls associated with messages processed by the SCIM module and transaction data records (TDRs) for transactions associated with messages processed by the SCIM module.

13. A system for providing rules-based service interaction and mediation in a communications network, the system comprising:

a service interaction and mediation rules database for storing the service interaction and mediation rules for providing service interaction and mediation; and

a service capability interaction manager (SCIM) module for providing, using service interaction and mediation rules stored in the service interaction and mediation rules database, service interaction and mediation between a service client and a plurality of application servers providing different types of services, wherein the service capability interaction manager module is configured to receive at least one incoming service interaction message;

identify, using a component of one of the incoming messages, a service interaction and mediation rule;

generate, using the identified rule, at least one outgoing service interaction message; and

send the at least one outgoing message.

14. The system of claim 13 wherein receiving the at least one incoming message includes receiving a client-to-SCIM message from a service client, wherein generating the at least one outgoing message includes generating a plurality of SCIM-to-server messages, and wherein sending the at least one outgoing message includes sending the SCIM-to-server messages to at least some of the plurality of application servers.

15. The system of claim 13 wherein receiving the at least one incoming message includes receiving a plurality of server-to-SCIM messages from at least some of the plurality of application servers, wherein generating the at least one outgoing message includes generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages, and wherein sending the at least one outgoing message includes sending the SCIM-to-client message containing the aggregation to a service client.

16. The system of claim 15 wherein generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages includes suppressing duplicate SCIM-to-client messages.

17. The system of claim 15 wherein generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages includes consolidating information contained in a plurality of SCIM-to-client messages into a single SCIM-to-client message.

19. The system of claim 13 comprising an interface for remotely updating the service interaction and mediation rules database.

20. The system of claim 13 wherein the component of an incoming message includes a service key parameter.

21. The system of claim 13 wherein at least one of the service capability interaction manager module and the service interaction and mediation rules database is co-located with a network signaling point.

22. The system of claim 13 wherein the SCIM module is configured to manage message subscription and notification in a communications network, wherein managing message subscription and notification includes:

receiving, from at least some of the plurality of application servers, requests to be notified of specified events, and in response to receiving the requests, creating an aggregation of the notification requests and sending a message containing the aggregation to the service client;

maintaining mappings between the application servers and the specified events; and

receiving notification of an event, and, in response, identifying at least one application server subscribed to receive notification of the event using the mappings and notifying the at least one identified application server of the event.

23. The system of claim 22 wherein notifying the at least one identified application server of the event includes notifying a plurality of application servers of the event.

24. The system of claim 22 wherein notifying the at least one identified application server of the event includes:

notifying one of the plurality of application servers of the event;

receiving, from the one application server, a response to the notification;

determining, based on the response to the notification, whether to notify another of the plurality of application servers of the event, and, based on that determination, notifying another of the plurality of application servers of the event.

25. The system of claim 22 wherein the SCIM module is configured to, in response to receiving notification of an event, send a SCIM-to-server message to one of the plurality of applications servers, wherein the one application server is not identified as subscribed to receive notification of the event.

26. A system for providing service interaction and mediation in a communications network, the system comprising:

a communications interface for receiving a service interaction message including information identifying a subscriber; and

a service capability interaction manager (SCIM) module for providing service interaction and mediation between a service client and a plurality of network entities, wherein providing the service interaction includes;

identifying an event, occurring at the service client and associated with the identified subscriber, for which notification is desired;

identifying at least one of the plurality of network entities for receiving notification of the identified event;

maintaining mappings between the identified network entities and the identified event; and

sending, to the service client, a request to send notification of the identified event to the SCIM module.

27. The system of claim 26 wherein the SCIM module is configured to determine, prior to sending to the service client a request to send notifications of the identified event to the SCIM module, if the service client is configured to send to the SCIM module notification of the identified event, and, upon a determination that the service client is not configured to send to the SCIM module notification of the identified event, send to the service client the request to send notifications of the event to the SCIM module.

28. The system of claim 26 wherein the SCIM module is configured to receive, from the service client, notification of an event, and, in response to receiving the notification, identify, using the mappings, at least one network entity subscribed to receive notification of the event and notify the at least one identified network entity of the event.

29. The system of claim 26 wherein the received service interaction message includes at least one of:

identification of an event for which notification is desired;

profile information for the subscriber;

a service to which the subscriber is subscribed; and

a network entity to which notification is to be sent.

30. The system of claim 29 wherein the event for which notification is required comprises a service trigger.

31. The system of claim 26 wherein the SCIM module is configured to identify at least one of the event for which notification is desired and the at least one of the plurality of network entities for receiving notification of the identified event based on at least one of:

information contained in the service interaction message;

information included in the identified subscriber'"'"'s profile; and

information returned from a query for information associated with the identified subscriber.

32. The system of claim 31 wherein the information returned from a query for information associated with the identified subscriber includes information returned from a query to at least one of a home location register (HLR), a visitor location register (VLR), and a home subscriber server (HSS).

33. The system of claim 26 wherein the SCIM module is configured to maintain mappings between the identified network entities and the identified event using a database for associating subscribers, events, and network entities.

34. The system of claim 33 where the database is one of co-located with the SCIM module and not co-located with the SCIM module.

35. The system of claim 26 wherein the service interaction message is received from one of an application server (AS), a service control point (SCP), a home location register (HLR), a visitor location register (VLR), a home subscriber server (HSS), and a network entity for providing provisioning information.

36. The system of claim 26 wherein the service interaction message is received in response to a prior request, sent from the SCIM module, for information associated with the identified subscriber.

37. The system of claim 26 wherein the service interaction message is sent to the SCIM module from a message source in response to a provisioning operation occurring at the message source.

38. A service capability interaction manager (SCIM) having an extendable architecture, the SCIM comprising:

a database for storing system configuration information and element protocol configuration information;

a service interaction rules module for storing service interaction and mediation rules;

a service mediation and aggregation logic module for providing service mediation and aggregation in a communications network based on the service interaction and mediation rules stored by the service interaction rules module and the system configuration information stored in the database; and

a plurality of protocol handlers for performing protocol mediation and conversion between a protocol used by the service mediation and aggregation logic and protocols used by the plurality of network entities, based on the element protocol configuration information stored in the database.

39. A method for providing service interaction and mediation in a communications network, the method comprising:

at a service capability interaction manager (SCIM) module for performing service interaction and mediation between a service client and a plurality of application servers providing different services;

receiving, from the service client, a client-to-SCIM service interaction message, and, in response to receiving the client-to-SCIM message, generating a plurality of SCIM-to-server messages and sending the SCIM-to-server messages to at least some of the plurality of application servers; and

receiving a plurality of server-to-SCIM service interaction messages from at least some of the plurality of application servers that received the SCIM-to-server messages, and, in response to receiving the server-to-SCIM messages, generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages, and sending the SCIM-to-client message containing the aggregation to the service client.

40. The method of claim 39 wherein generating the SCIM-to-server messages includes generating the SCIM-to-server messages based on analysis of a component of the client-to-SCIM message.

41. The method of claim 39 wherein the SCIM module is co-located with a network signaling point.

42. The method of claim 39 wherein generating the SCIM-to-server messages in response to the client-to-SCIM message includes converting between one of:

a SIP protocol and a non-SIP protocol;

a CAMEL protocol and an IMS protocol; and

one version of a CAMEL protocol and another version of a CAMEL protocol.

43. The method of claim 39 wherein generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages includes suppressing duplicate SCIM-to-client messages.

44. The method of claim 39 wherein generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages includes consolidating information contained in a plurality of SCIM-to-client messages into a single SCIM-to-client message.

45. The method of claim 39 wherein the SCIM module is configured to generate at least one of call detail records (CDRs) for calls associated with messages processed by the SCIM module and transaction data records (TDRs) for transactions associated with messages processed by the SCIM module.

46. The method of claim 39 comprising managing, by the SCIM module, message subscription and notification in a communications network, wherein managing message subscription and notification includes:

receiving, from at least some of the plurality of application servers, requests to be notified of specified events, and in response to receiving the requests, creating an aggregation of the notification requests and sending a message containing the aggregation to the service client;

maintaining mappings between the application servers and the specified events; and

receiving notification of an event, and, in response to receiving the notification, identifying at least one application server subscribed to receive notification of the event using the mappings and notifying the at least one identified application server of the event.

47. The method of claim 46 wherein creating an aggregation of the notification requests and sending a message containing the aggregation to the service client includes forwarding to the service client a first request to be notified of a specific event and not forwarding to the service client subsequent requests to be notified of the specific event.

48. The method of claim 46 wherein creating an aggregation of the notification requests and sending a message containing the aggregation to the service client includes consolidating information contained in the notification requests into a single notification request and sending the single notification request.

49. The method of claim 46 wherein notifying the at least one identified application server of the event includes notifying a plurality of application servers of the event.

50. The method of claim 46 wherein notifying the at least one identified application server of the event includes:

notifying one of the plurality of application servers of the event;

receiving, from the one application server, a response to the notification;

determining, based on the response to the notification, whether to notify another of the plurality of application servers of the event, and, based on that determination, notifying another of the plurality of application servers of the event.

51. A method for providing rules-based service interaction and mediation in a communications network, the method comprising:

at a service capability interaction manager (SCIM) module for service interaction and mediation between a service client and a plurality of application servers providing different services;

receiving at least one incoming service interaction message;

identifying, using a component of one of the incoming messages, a service interaction and mediation rule in a service interaction and mediation rules database operatively associated with the service capability interaction manager module and for storing service interaction and mediation rules for performing service interaction and mediation;

generating, using the identified rule, at least one outgoing service interaction message; and

sending the at least one outgoing message.

52. The method of claim 51 wherein receiving the at least one incoming message includes receiving a client-to-SCIM message from the service client, wherein generating the at least one outgoing messages includes generating a plurality of SCIM-to-server messages, and wherein sending the at least one outgoing message includes sending the SCIM-to-server messages to at least some of the plurality of application servers.

53. The method of claim 51 wherein receiving the at least one incoming message includes receiving a plurality of server-to-SCIM messages from at least some of the plurality of application servers, wherein generating the at least one outgoing message includes generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages, and wherein sending the at least one outgoing message includes sending the SCIM-to-client message containing the aggregation to a service client.

54. The method of claim 53 wherein generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages includes suppressing duplicate SCIM-to-client messages.

55. The method of claim 53 wherein generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages includes consolidating information contained in a plurality of SCIM-to-client messages into a single SCIM-to-client message.

56. The method of claim 51 wherein the SCIM module is configured to generate at least one of call detail records (CDRs) for calls associated with messages processed by the SCIM module and transaction data records (TDRs) for transactions associated with messages processed by the SCIM module.

57. The method of claim 51 wherein the component of one of the incoming messages includes a service key parameter.

58. The method of claim 51 wherein the service capability interaction manager module is co-located with a network signaling point.

59. The method of claim 51 comprising managing, by the service capability interaction manager module, message subscription and notification in a communications network, wherein managing message subscription and notification includes:

receiving, from at least some of the plurality of application servers, requests to be notified of specified events, and in response to receiving the requests, creating an aggregation of the notification requests and sending a message containing the aggregation to the service client;

maintaining mappings between the application servers and the specified events; and

receiving notification of an event, and, in response, identifying at least one application server subscribed to receive notification of the event using the mappings and notifying the at least one identified application server of the event.

60. The method of claim 59 wherein notifying the at least one identified application server of the event includes notifying a plurality of application servers of the event.

61. The method of claim 59 wherein notifying the at least one identified application server of the event includes:

notifying one of the plurality of application servers of the event;

receiving, from the one application server, a response to the notification;

determining, based on the response to the notification, whether to notify another of the plurality of application servers of the event, and, based on that determination, notifying another of the plurality of application servers of the event.

62. The system of claim 59 wherein the SCIM module is configured to, in response to receiving notification of an event, send a SCIM-to-server message to one of the plurality of applications servers, wherein the one application server is not identified as subscribed to receive notification of the event.

63. A method for providing service interaction and mediation in a communications network, the method comprising:

at a service capability interaction manager (SCIM) module for performing service interaction and mediation between a service client and a plurality of network entities;

receiving a service interaction message including information identifying a subscriber;

identifying an event, that occurs at the service client and is associated with the identified subscriber, for which notification is desired;

identifying at least one of the plurality of network entities to receive notification of the identified event;

maintaining mappings between the identified network entities and the identified event; and

sending, to the service client, a request to send notifications of the identified event to the SCIM module.

64. The method of claim 63 wherein sending, to the service client, a request to send notifications of the identified event to the SCIM module includes determining if the service client is configured to send to the SCIM module notification of the identified event, and, upon a determination that the service client is not configured to send to the SCIM module notification of the identified event, sending to the service client the request to send notifications of the event to the SCIM module.

65. The method of claim 63 comprising receiving, from the service client, notification of an event, and, in response to receiving the notification, identifying, using the mappings, at least one network entity subscribed to receive notification of the event and notifying the at least one identified network entity of the event.

66. The method of claim 63 wherein receiving the service interaction message includes receiving a service interaction message including at least one of:

an event for which notification is desired;

profile information for the subscriber;

a service to which the subscriber is subscribed; and

a network entity to which notification is to be sent.

67. The method of claim 63 wherein identifying an event for which notification is required comprises identifying a service trigger.

68. The method of claim 63 wherein identifying an event for which notification is desired and identifying at least one of the plurality of network entities for receiving notification of the identified event is based on at least one of:

information contained in the service interaction message;

information included in the identified subscriber'"'"'s profile; and

information returned from a query for information associated with the identified subscriber.

69. The method of claim 67 wherein the information returned from a query for information associated with the identified subscriber includes information returned from a query to at least one of a home location register (HLR), a visitor location register (VLR), and a home subscriber server (HSS).

70. The method of claim 63 wherein maintaining mappings between the identified network entities and the identified event includes maintaining a database for associating subscribers, events, and network entities.

71. The method of claim 70 where maintaining a database includes at least one of maintaining a database that is co-located with the SCIM module and maintaining a database that is not co-located with the SCIM module.

72. The method of claim 63 wherein receiving the service interaction message comprises receiving the service interaction message from one of an application server (AS), a service control point (SCP), a home location register (HLR), a visitor location register (VLR), a home subscriber server (HSS), and a network entity for providing provisioning information.

73. The method of claim 63 wherein the service interaction message is received in response to a prior request, sent from the SCIM module, for information associated with the identified subscriber.

74. The method of claim 63 wherein the service interaction message is sent to the SCIM module from a message source in response to a provisioning operation occurring at the message source.

75. A computer readable medium having stored thereon computer-executable instructions that when executed by the processor of a computer perform steps comprising:

at a service capability interaction manager (SCIM) module for performing service interaction and mediation between a service client and a plurality of application servers providing different services;

receiving, from the service client, a client-to-SCIM service interaction message, and, in response to receiving the client-to-SCIM message, generating a plurality of SCIM-to-server messages and sending the SCIM-to-server messages to at least some of the plurality of application servers; and

receiving a plurality of server-to-SCIM service interaction messages from at least some of the plurality of application servers that received the SCIM-to-server messages, and, in response to receiving the server-to-SCIM messages, generating a SCIM-to-client message containing an aggregation of at least a portion of data from at least some of the server-to-SCIM messages, and sending the SCIM-to-client message containing the aggregation to the service client.

76. A computer readable medium having stored thereon computer-executable instructions that when executed by the processor of a computer perform steps comprising:

at a service capability interaction manager (SCIM) module for performing service interaction and mediation between a service client and a plurality of application servers providing different services;

receiving at least one incoming service interaction message;

identifying, using a component of one of the incoming messages, a service interaction and mediation rule in a service interaction and mediation rules database operatively associated with the service capability interaction manager module and for storing service interaction and mediation rules for performing service interaction and mediation;

generating, using the identified rule, at least one outgoing service interaction message; and

sending the at least one outgoing message.

77. A computer readable medium having stored thereon computer-executable instructions that when executed by the processor of a computer perform steps comprising:

receiving a service interaction message including information identifying a subscriber;

identifying an event, occurring at the service client and associated with the identified subscriber, for which notification is desired;

identifying at least one of the plurality of network entities for receiving notification of the identified event;

maintaining mappings between the identified network entities and the identified event; and

determining if the service client is configured to send notification of the identified event, and, if not, sending to the service client a request to be notified of the identified event.