Policy service system and methodology

• US 7,103,351 B2
• Filed: 06/23/2003
• Issued: 09/05/2006
• Est. Priority Date: 06/23/2003
• Status: Expired due to Fees

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: July Systems, Inc. (Cisco Systems, Inc.)
• Inventors: Smotra, Sachin, Chaudhari, Ambarish, Varma, Ramesh, Gopalan, Padma Priya, Kashikar, Amod, Reddy, Rajesh T S, Chakravorthy, Jyothirmoy
• Primary Examiner(s): Eng, George
• Assistant Examiner(s): KIM, WESLEY LEO
• Application Number:
  US10/601,397
• Publication Number:
  US 20040259534A1
• Time in Patent Office: 1,170 Days
• Field of Search: 455/414.1, 455/419, 455/414.3, 455/406, 455/411, 705/26, 705/34, 705/40, 705/44
• US Class Current: 455/414.1
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 30/0621 Item configuration or customization
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/62 based on trigger specification
• CPC Class Codes: H04M 15/68 Payment of value-added services
• CPC Class Codes: H04M 2215/0196 Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking

Abstract

The present invention provides for creation, relevance based discovery and delivery of services to mobile users over telecommunications networks. The services are provided on a Mobile Service Provider'"'"'s (MSP'"'"'s) network infrastructure and created in collaboration with third parties by means of service objects. Each service object is a three dimensional collection of service capabilities derived from the network infrastructure, service elements and assets like user billing relations, user profiles, device capability and location. The service capabilities address and factor in network facing, subscriber facing and third party requirements of service delivery. Service objects can be configured for different service and business priorities of the operator such as DRM and location services. A service object extends all MSP assets to third parties in a regulated manner. The user can discover relevant services, subscribe to, and personalize the services. The users receive a consolidated bill for the services they have used periodically.

Claims

1. A method for providing at least one service to a plurality of mobile users, the service being provided via a network infrastructure owned by a mobile service provider, the service being provided by at least one third party partnering the mobile service provider, the method comprising the steps of:

a. creating policy based service objects using core network information, service capability features, and the business relationship with the third party, the policy based service objects being created by the mobile service provider, the service objects once created being made available to the third party for service creation;

b. the mobile service provider providing a list of created service objects to the third party.

c. creating services using at least one of the created service objects, the services being created by the third party, and the service being added to a list of services, wherein the third party customizes the services as per subscriber profiles by specifying values to variables in the service object, the subscriber profiles including information about the plurality of mobile users;

d. providing the list of services to the mobile user via the network infrastructure upon intercepting a request for the service from the mobile user, wherein the list of services is relevant to the mobile user, the list of services being provided by the mobile service provider;

e. the mobile user subscribing to a service from the list of services being provided by the mobile service provider; and

f. the mobile user customizing the subscribed service by overwriting at least one variable, the variables defining the subscribed service.

2. The method as recited in claim 1, wherein the step of creating services using at least one of the created service objects includes selecting a charging model for a service from a number of charging models associated with the service object.

3. The method as recited in claim 1, wherein the step of creating a service by a third party comprises the step of:

a. entering authentication information for access to service objects available with the mobile service provider, the authentication enabling the third party to gain pre-defined access to service objects;

b. selecting at least one service object;

c. configuring service parameters on the selected service objects on the basis of predefined business relationships existing between the third party and the mobile service provider; and

d. providing relevance criteria for the created service on the basis of the shared core network information.

4. The method as recited in claim 3, wherein the step of configuring service parameters on the basis of predefined business relationships existing between the third party and the mobile service provider comprises the steps of:

a. using the core network information that is being shared between the mobile service provider and the third party, the shared core network information being defined on the basis of the pre-defined business relationships; and

b. providing value added services in accordance with the predefined business relationship.

5. The method as recited in claim 1, wherein the step of creating services using at least one of the predefined service objects is carried out by the mobile service provider.

6. The method as recited in claim 1, wherein the step of enabling the provision of the created service to the mobile user comprises the steps of:

a. applying network level controls on the service created in accordance with business relationships;

b. applying application level controls on the service created in accordance with business relationships; and

c. applying system level controls on the system elements participating in service creation and delivery.

7. The method as recited in claim 1, wherein the step of a user subscribing to a service comprises the steps of:

a. the mobile service provider matching user context information with relevance criteria of services offered;

b. the mobile service provider providing to the user, a list of available services whose relevance criteria matches with the user information;

c. the user selecting from the list, at least one service; and

d. the user subscribing to the selected service.

8. The method as recited in claim 1, further including the step of the mobile user customizing the service as per preference by means of the steps of:

a. the user identifying the service parameters to be customized; and

b. the user overwriting the identified service parameters.

9. The method as recited in claim 1, wherein the step of creating policy based service objects comprises the steps of:

a. assigning variables relevant to a service capability based on subscriber profiles, a network element capability database, and business rules relationships between the mobile service provider and the third party;

b. combining service capabilities to create a service object;

c. assigning values to variable in the service capabilities of the created service object;

d. selecting relevant policies and rules for the created service object based on the business relationships with the third parties; and

e. storing the created service object, wherein the stored service object is available for creating services by the third parties.

10. The method as recited in claim 9, wherein the step of assigning variables relevant to a service capability based on a network element capability database for creating service objects comprises the steps of:

a. defining network elements information including information relating to the capability of network elements; and

b. defining the gateway services information including information relating to the capability of gateway services.

11. The method as recited in claim 1, wherein the step of creating policy based service objects comprises providing conditions and actions for the service object that can be implemented with a service.

12. The method as recited in claim 1, wherein the step of providing the list of service objects to the third party by the mobile service provider comprises providing only authorized features to the third party for service creation.

13. The method as recited in claim 1, wherein the service objects are available through graphical user interface to the third party for service creation.

14. A system suitable for providing at least one service to a plurality of mobile users, the service being provided via a network infrastructure owned by a mobile service provider, the service being provided by at least one third party partnering the mobile service provider, the system comprising:

a. a business gateway for enabling the provision and modification of core network information by the mobile service provider and the third party;

b. a context server for maintaining information about the system, wherein the context server comprises;

i. means for collecting status information about the user;

ii. means for collecting status information about user devices;

iii. means for collecting status information about network elements; and

iv. means for collecting status information about applications enabling services;

c. a meta directory for storing the core network information, the core network information being needed for creation and delivery of services;

d. a service catalog for storing a list of available services, and the relevance criteria corresponding to each service;

e. an intermediation gateway for enabling the delivery of services; and

f. a meta controller for providing a policy based control of the business gateway, the context server, the meta directory, the service catalog and the intermediation gateway.

15. The system as recited in claim 14, wherein the business gateway authenticates third party for access to information available with the mobile service provider, and wherein the business gateway comprises:

a. a read module for reading the core network information stored in the meta directory, the information being read by the mobile service provider and the third party; and

b. a write module for providing core network information that is to be stored in the meta directory, the information being provided by the mobile service provider and the third party.

16. The system as recited in claim 14, wherein the meta directory comprises:

a. a service directory for storing service objects created by the mobile service provider;

b. a policy repository for storing policy rules created by the mobile service provider;

c. a business rules repository for storing rules decided on the basis of business relationships between the mobile service provider and third party;

d. a device profile database for storing details of user devices;

e. an application profile for storing details of the different applications that implement services; and

f. a subscriber profile for storing information about users subscribed for various services.

17. The system as recited in claim 14, wherein the intermediation gateway comprises:

a. a context engine receiving context information from the context server;

b. a policy component extracting policies relevant to a service from the meta controller;

c. an application handler deciding the appropriate application corresponding to a service requested by the user; and

d. a policy enforcement engine implementing policies extracted by the policy component on the application.

18. The system as recited in claim 17, wherein the system further comprises a metering record generator for storing usage information, the usage information being used to obtain consolidated billing for the users.

19. The system as recited in claim 14, wherein the meta controller comprises:

a. a policy decision engine for identifying policies corresponding to a requested service;

b. a network resource control module for policy based control of network infrastructure;

c. an application control module for policy based control of application implementing a requested service; and

d. a system resource control module for policy based control of system elements.

20. The system as recited in claim 19, wherein the policy decision engine authenticates the user requesting for a service.

21. The system as recited in claim 14, wherein the service catalog comprises:

a. means for extracting user information from the context server;

b. means for extracting relevance criteria for all the services stored in the service catalog; and

c. means for matching user context with relevance criteria for each service.

22. A system suitable for providing at least one service to a plurality of mobile users, the service being provided via a network infrastructure owned by a mobile service provider, the service being provided by at least one third party partnering the mobile service provider, the system comprising:

a. a business gateway for enabling the provision and modification of core network information by the mobile service provider and the third party;

b. a context server for maintaining information about the system;

c. a meta directory for storing the core network information, the core network information being needed for creation and delivery of services, wherein the meta directory comprises;

i. a service directory for storing service objects created by the mobile service provider;

ii. a policy repository for storing policy rules created by the mobile service provider;

iii. a business rules repository for storing rules decided on the basis of business relationships between the mobile service provider and third party;

iv. a device profile database for storing details of user devices;

v. an application profile for storing details of the different applications that implement services; and

vi. a subscriber profile for storing information about users subscribed for various services;

d. a service catalog for storing a list of available services, and the relevance criteria corresponding to each service;

e. an intermediation gateway for enabling the delivery of services; and

f. a meta controller for providing a policy based control of the business gateway, the context server, the meta directory, the service catalog and the intermediation gateway.