Claims
- 1. A method comprising:
(a) providing a first interface whereby a service provider identifies a first network element used to provide a first service to a subscriber, and wherein the service provider defines first configuration information that is sent to the first network element in the event the subscriber elects to start the first service; and (b) providing a second interface whereby the subscriber registers for the first service and initiates the first service without action after (a) by the service provider, wherein the subscriber registers once for the first service and thereafter is able to initiate the first service multiple times, wherein starting the first service involves generating a first activation from the first configuration information and sending the first activation to a policy distribution point such that the policy distribution point converts the first activation into first device-specific instructions that provision the first network element to start the first service for the subscriber.
- 2. The method of claim 1, wherein step (a) includes writing items of information to a database regarding: whether the subscriber is authorized to use the first service, whether the first network element is used to provide the first service, and the IP address of the first network element.
- 3. The method of claim 2, wherein the items of information are preconfigured by the service provider using the first interface before the subscriber initiates the first service.
- 4. The method of claim 2, wherein registration of the first service in (b) involves writing one of the items of information to a database such that the item of information is not written to the database during subsequent initiation of the first service.
- 5. The method of claim 1, wherein registration of the first service in (b) involves generating an object for a billing system, and wherein no object for the billing system is generated during subsequent initiation of the first service.
- 6. The method of claim 1, wherein the first configuration information is sent to the policy distribution point as an XML document within an HTTP request.
- 7. The method of claim 1, wherein the first interface is a graphical user interface between the service provider and a state machine.
- 8. The method of claim 1, wherein the policy distribution point includes a single program that: (x) receives an HTTP request, the HTTP request containing the first configuration information, (y) converts the first configuration information into the first device-specific instructions, and (z) sends the first device-specific instructions to the first network element.
- 9. The method of claim 8, wherein a first part of the single program performs (x), a second part of the single program performs (y), and a third part of the single program performs (z), and wherein the first part, the second part and the third part are compiled together.
- 10. The method of claim 9, wherein the policy distribution point comprises web server software, wherein the web server software comprises the single program, and wherein the second part is a module, the module being compiled as part of the web server software.
- 11. The method of claim 1, wherein the first configuration information includes instructions taken from the group consisting of: open a port on a firewall, complete a network cross-connection on a gateway, and route an HTTP request from one IP address to another IP address.
- 12. The method of claim 1, wherein the first network element is taken from the group consisting of: a gateway, a firewall, a DSL modem, an application server, a CRM system and a billing system.
- 13. The method of claim 1, wherein step (a) further includes identifying a second network element used to provide a second service to the subscriber, and wherein the service provider defines second configuration information that is sent to the second network element in the event the subscriber elects to start the second service; and
wherein step (b) further includes registering for the second service and initiating the second service without action after (a) by the service provider, wherein the subscriber registers once for the second service and thereafter can initiate the second service multiple times, wherein starting the second service involves generating a second activation from the second configuration information and sending the second activation to the policy distribution point such that the policy distribution point converts the second activation into second device-specific instructions that provision the second network element to start the second service for the subscriber.
- 14. The method of claim 13, wherein the first network element is a networking device and the second network element is a computing device.
- 15. The method of claim 1, wherein the service provider defines third configuration information that is sent to the first network element in the event the subscriber elects to stop the first service; and
wherein the subscriber stops the first service without action after (a) by the service provider, wherein stopping the first service involves sending the third configuration information to the policy distribution point such that the policy distribution point converts the third configuration information into third device-specific instructions that provision the first network element so that the first service is stopped.
- 16. A system for self-activating network-based services, comprising:
(a) a billing system; (b) a network element used to provide a first service to a subscriber; (c) a core server, the core server comprising a first part, a second part and a user database, the first part generating a first activation and the second part generating a second activation; (d) a first policy distribution point (PDP), the first PDP receiving the first activation, translating the first activation into first device-specific instructions, sending the first device-specific instructions to the billing system, the first device-specific instructions configuring the billing system to provide the first service to the subscriber; and (e) a second PDP, the second PDP receiving the second activation, translating the second activation into second device-specific instructions, sending the second device-specific instructions to the network element, the second device-specific instructions configuring the network element to provide the first service to the subscriber wherein the first part sends the first activation during registration of the first service, and the second part sends the second activation during subsequent initiation of the first service.
- 17. The system of claim 16, wherein the first part writes to the user database during registration of the first service, and wherein the second part reads from but does not write to the user database during subsequent initiation of the first service.
- 18. The system of claim 16, wherein the second part is an initiation module.
- 19. The system of claim 16, wherein the network element is used to provide a second service to the subscriber, wherein the second part generates a third activation, and wherein the second PDP receives the third activation, translates the third activation into third device-specific instructions, and sends the third device-specific instructions to the network element, the third device-specific instructions configuring the network element to initiate the second service for the subscriber.
- 20. The system of claim 16, wherein the network element is taken from the group consisting of: a networking device, and a computing device.
- 21. The system of claim 16, wherein the core server further comprises a single sign-on engine, and wherein the second part instantiates the single sign-on engine.
- 22. The system of claim 16, wherein the core server comprises web server software, wherein the web server software comprises the second part, wherein the second part is compiled as part of the web server software.
- 23. A computer-readable medium having computer-executable instructions for performing steps comprising:
(a) providing an interface whereby a service provider identifies a first network element used to provide a first service to a subscriber, and wherein the service provider defines first configuration information that is sent to the first network element in the event the subscriber elects to initiate the first service; and (b) providing an interface whereby the subscriber starts and stops the first service without action after (a) by the service provider, wherein initiation of the first service involves sending the first configuration information to a policy distribution point such that the policy distribution point converts the first configuration information into first device-specific instructions that provision the first network element to start and to stop the first service for the subscriber.
- 24. The computer-readable medium of claim 23, wherein the policy distribution point comprises web server software, wherein the web server software comprises a single program that (x) sends and receives HTTP requests, (y) converts instructions contained in the HTTP requests into device-specific instructions, and (z) sends the device-specific instructions to the first network element, wherein a first part of the single program performs (x), a second part of the single program performs (y), and a third part of the single program performs (z), and wherein the first part, the second part and the third part are compiled together.
CROSS REFERENCE TO RELATED APPLICATION
[0001] This application claims the benefit under 35 U.S.C. §120 of patent application Ser. No. 10/213,043, entitled “System And Method For Setting Up User Self-Activating Network-Based Services”, by Bellinger et al., filed Aug. 5, 2002 (the subject matter of which is incorporated herein by reference), which in turn claims the benefit under 35 U.S.C. §119 of the provisional application serial No. 60/354,268, entitled “Software Platform For Managing Network-Based Services', by Bellinger et al., filed Feb. 4, 2002 (the subject matter of which is incorporated herein by reference).
Provisional Applications (1)
|
Number |
Date |
Country |
|
60354268 |
Feb 2002 |
US |
Continuations (1)
|
Number |
Date |
Country |
Parent |
10213043 |
Aug 2002 |
US |
Child |
10384268 |
Mar 2003 |
US |