IP Library Granted Patent US 7,310,663
Granted Patent B2
US 7,310,663 · App. 10/384,268 · Granted Dec 18, 2007

Initiation module for initiating network-based services

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,310,663
App. No.
10/384,268
Granted
Dec 18, 2007
Kind
B2
Abstract

A system allows subscribers quickly to self-activate network-based services by automatically configuring network elements. A service provider preconfigures a state machine on a core server. At the time of self-activation, activations are sent to policy distribution points (PDPs) that translate the activations into device-specific instructions, which in turn configure network elements to provide services. The speed of self-activation is increased by generating activations faster in the core server, by translating activations into device-specific instructions faster in the PDPs, and by separating the configuration of the network elements from complex registration steps. Initiation steps that configure network elements are performed faster by an initiation module that reads from, but does not write to, databases. Subscribers perform dynamic service selection using the initiation module. Initiating services faster results in a more enjoyable user experience as subscribers quickly switch back and forth between network-based services.

Claims (32)

1. A method comprising:

(a) providing a first interface, wherein 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, wherein 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 computer-readable medium having computer-executable instructions for performing steps comprising:

(a) providing an interface, wherein 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, wherein 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.

17. The computer-readable medium of claim 16 , 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.

18. A system comprising:

(a) a first interface on which a network element and configuration information are identified, wherein the network element is used by a service provider to provide a service to a subscriber, and wherein the configuration information is sent to the network element in the event the subscriber elects to start the service; and

(b) a second interface used by the subscriber to register for the service and to initiate the service without action after (a) by the service provider, wherein the subscriber registers once for the service and thereafter is able to initiate the service multiple times, wherein starting the service involves generating a first activation from the 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 network element to start the service for the subscriber.

19. The method of claim 18 , wherein the configuration information indicates whether the subscriber is authorized to use the service, whether the network element is used to provide the service, and the IP address of the network element.

20. The method of claim 18 , wherein the 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.

21. The method of claim 18 , wherein the subscriber registers for the service by generating an object for a billing system, and wherein no object for the billing system is generated during subsequent initiation of the service.

22. The method of claim 18 , wherein the configuration information is sent to the network element as an XML document within an HTTP request.

23. The method of claim 18 , wherein the first interface is a graphical user interface between the service provider and a state machine.

24. The method of claim 18 , wherein the policy distribution point includes a single program that: (a) receives an HTTP request, the HTTP request containing the configuration information, (b) converts the configuration information into the first device-specific instructions, and (c) sends the first device-specific instructions to the network element.

Assignments (14)
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2024
From: CITIZENS BANK, N.A.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 067822/0433 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT AT R/F 044978/0801 Recorded Dec 6, 2021
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 058949/0497 →
SECURITY INTEREST Recorded Mar 3, 2020
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 052076/0905 →
CHANGE OF NAME Recorded Jan 16, 2019
From: SONUS NETWORKS, INC.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
Reel/Frame 048078/0036 →
SECURITY INTEREST Recorded Jan 2, 2018
From: GENBAND US LLC; SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 044978/0801 →
MERGER AND CHANGE OF NAME Recorded Dec 24, 2017
From: SOLSTICE SAPPHIRE, INC.; SONUS NETWORKS, INC.; SONUS NETWORKS, INC.
To: SONUS, INC.
Reel/Frame 044957/0243 →
CHANGE OF NAME Recorded Dec 24, 2017
From: SONUS, INC.
To: SONUS NETWORKS, INC.
Reel/Frame 044957/0213 →
RELEASE OF SECURITY INTEREST Recorded Oct 24, 2017
From: BANK OF AMERICA, N.A.
To: SONUS NETWORKS, INC.; SONUS FEDERAL, INC.; NETWORK EQUIPMENT TECHNOLOGIES, INC.; PERFORMANCE TECHNOLOGIES, INCORPORATED; SONUS INTERNATIONAL, INC.; TAQUA, INC.
Reel/Frame 044283/0361 →
SECURITY INTEREST Recorded Sep 12, 2014
From: SONUS NETWORKS, INC.; SONUS FEDERAL, INC.; NETWORK EQUIPMENT TECHNOLOGIES, INC.; PERFORMANCE TECHNOLOGIES, INCORPORATED; SONUS INTERNATIONAL, INC.
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 033728/0409 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 10, 2008
From: SONUS NETWORKS CORP.
To: SONUS NETWORKS, INC.
Reel/Frame 021658/0652 →
CHANGE OF NAME Recorded Oct 7, 2008
From: ATREUS SYSTEMS CORP.
To: SONUS NETWORKS CORP.
Reel/Frame 021640/0230 →
RELEASE OF SECURITY INTEREST Recorded Oct 3, 2008
From: MOBIUS TECHNOLOGY VENTURES VI L.P.; MOBIUS TECHNOLOGY VENTURES ADVISORS FUND VI L.P.; MOBIUS TECHNOLOGY VENTURES SIDE FUND VI L.P.; SOFTBANK U.S. VENTURES FUND VI L.P.; BLUEPRINT VENTURES EMERGING COMMUNICATIONS FUND, I-Q, L.P.; BLUEPRINT VENTURES STRATEGIC AFFILIATES FUND I, L.P.; BLUEPRINT VENTURES EMERGING COMMUNICATIONS FUND, I, L.P.; SKYPOINT TELECOM FUND; BDC CAPITAL INC.; SQUARE 1 BANK
To: ATREUS SYSTEMS CORP.
Reel/Frame 021630/0313 →
SECURITY AGREEMENT Recorded Jan 31, 2008
From: ATREUS SYSTEMS, INC.
To: SQUARE 1 BANK
Reel/Frame 020451/0274 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 7, 2003
From: BELLINGER, DOUGLAS; BURKE, RICHARD; PHILLIPS, THOMAS; ARGENTINA, ANTONIO SCAFFIDI; STEWART, GEOFF; RAOUX, WENDY; RHUDE, PATRICK
To: ATREUS SYSTEMS CORP.
Reel/Frame 013871/0025 →