IP Library Granted Patent US 8,504,664
Granted Patent B2
US 8,504,664 · App. 12/506,234 · Granted Aug 6, 2013

Methods, systems, and computer readable media for a validation framework for validating commands for configuring entities in a telecommunications network

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 8,504,664
App. No.
12/506,234
Granted
Aug 6, 2013
Kind
B2
Abstract

Methods, systems, and computer program products for implementing a validation framework for validating commands for configuring entities in a telecommunications network are disclosed. According to one aspect, the subject matter described herein includes a method for implementing a validation framework for validating commands for configuring entities in a telecommunications network. The method includes providing, to a first computing system, a validation configuration file containing at least one rule for validating, based on domain knowledge of a network entity, commands for configuring the network entity, wherein the validation configuration file is provided from a developer of the network entity. The first computing system receives data associated with a command for configuring the network entity, validates the received data using the at least one rule, and, responsive to validating the data, performs at least one action.

Claims (119)

1. A method for implementing a validation framework for validating commands for configuring entities in a telecommunications network, the method comprising:

providing, to a first computing system, a validation configuration file containing at least one rule for validating, based on domain knowledge of a network entity, commands for configuring the network entity, wherein the validation configuration file is provided from a developer of the network entity, the validation configuration file being a human readable file convertible by the first computing system to a machine-readable format usable by the first computing system for performing data validation, wherein the first computing system includes a telecommunications network element; and

at the first computing system, receiving data associated with a command for configuring the network entity, validating the received data using the at least one rule, wherein said validating comprises at least one of validating the command and providing presentation intelligence, wherein providing presentation intelligence includes modifying an appearance of a graphical user interface for configuring the network entity, wherein modifying the appearance of the graphical user interface includes proactively controlling input by disabling or enabling graphical user interface elements based on the capabilities of the telecommunications network element, and, responsive to validating the data, performing at least one action.

2. The method of claim 1 comprising:

responsive to a change in the validation configuration file by the developer of the network entity, distributing an updated validation configuration file to the first computing system.

3. The method of claim 1 wherein the validation configuration file is at least one of:

stored locally at the network entity;

stored remotely from the network entity;

stored locally at the first computing system; and

stored remotely from the first computing system.

4. The method of claim 1 wherein the at least one rule includes:

at least one condition for triggering at least one action; and

the at least one action to be performed in response to the at least one condition being triggered.

5. The method of claim 1 wherein domain knowledge comprises information about at least one of:

a resource of the network entity;

a function performed by the network entity;

an operating characteristic of the network entity;

a configuration of the network entity;

a characteristic of an environment in which the network entity operates; and

information about a deployment of the network entity.

6. The method of claim 1 wherein validating, using the at least one rule, a command for configuring the network entity includes:

selecting the validation configuration file for processing;

accessing the validation configuration file; and

processing the validation configuration file for obtaining the at least one rule for validating commands for configuring the network entity.

7. The method of claim 6 wherein selecting the validation configuration file includes selecting the validation configuration file based on at least one of:

a type of the network entity;

a version of the network entity;

a configuration of the network entity;

a component of the network entity;

a type of a component of the network entity;

a version of a component of the network entity;

a configuration of a component of the network entity.

8. The method of claim 6 wherein at least one of selecting, accessing, and processing the validation configuration file occurs at runtime.

9. The method of claim 6 wherein processing the validation configuration file includes converting and storing the validation configuration file into a machine-readable format.

10. The method of claim 6 wherein at least one of selecting, accessing, and processing the validation configuration file occurs at least one of:

prior to a request for validation of input; and

in response to a request for validation of input.

11. The method of claim 1 wherein validating a received configuration command includes validating a configuration command received via at least one of:

a graphical user interface (GUI) module;

a command line interface (CLI) module; and

a network communication interface module.

12. The method of claim 1 wherein the user interface includes at least one of:

a graphical user interface (GUI) module;

a command line interface (CLI) module; and

a network communication interface module.

13. The method of claim 1 wherein modifying the appearance of the user interface includes at least one of:

initializing an interlace;

opening a GUI component;

changing a GUI component;

closing a GUI component;

selecting a GUI component;

entering data;

removing data;

replacing data; and

providing output to the user.

14. The method of claim 1 wherein performing at least one action in response to validating the received data includes at least one of:

transmitting the received data to the network entity;

generating a message to the source of the received data;

discarding the received data without transmitting it to the network entity;

providing output for an interface;

providing actions to be performed at the network entity;

providing actions to be performed at a second computing system;

indicating the data is valid;

indicating the data is invalid;

providing valid data;

modifying the data;

deleting the data;

creating new data;

triggering a condition;

validating new data; and

further processing the data.

15. The method of claim 1 wherein the first computing system is a component of the network entity.

16. The method of claim 1 wherein the network entity comprises a telecommunications network element and the first computing system comprises a telecommunications element management system for managing the telecommunications network element.

17. A system for validating commands for configuring entities in a telecommunications network, the system comprising:

an interface module for receiving data associated with a command for configuring a network entity; and

a validation engine comprising a processor, the validation engine for validating the received data using at least one rule from a validation configuration file and based on domain knowledge of the network entity, wherein validating the received data comprises at least one of validating a received configuration command and providing presentation intelligence, wherein providing presentation intelligence includes modifying an appearance of a graphical user interface for configuring the network entity, wherein modifying the appearance of the graphical user interface includes proactively controlling input by disabling or enabling graphical user interface elements based on the capabilities of the telecommunications network element, wherein the validation configuration file is provided from a developer of the network entity, the validation configuration file being a human readable file convertible by the validation engine to a machine-readable format usable by the validation engine for performing data validation, wherein the first computing system includes a telecommunications network element, and, responsive to validating the data, performing an action.

18. The system of claim 17 wherein, responsive to a change in the validation configuration file by the developer of the network entity, an updated validation configuration file is distributed for use by the validation engine.

19. The system of claim 17 wherein the interface module includes at least one of:

a graphical user interface (GUI) module;

a command line interface (CLI) module; and

a network communication interface module.

20. The system of claim 17 wherein the received data includes a request to perform at least one of:

initializing an interface;

opening a GUI component;

changing a GUI component;

closing a GUI component;

selecting a GUI component;

entering data;

removing data;

replacing data; and

interacting with an interface.

21. The system of claim 17 wherein the validation engine is configured for selecting, accessing, and processing the validation configuration file containing the at least one rule.

22. The system of claim 17 wherein the validation configuration file is at least one of:

stored locally with the validation engine; and

stored remotely from the validation engine.

23. The system of claim 21 wherein at least one of selecting, accessing, and processing the validation configuration file occurs at runtime.

24. The system of claim 21 wherein processing the validation configuration file includes converting and storing the validation configuration file into a machine-readable format.

25. The system of claim 17 wherein the at least one rule includes:

an at least one condition for triggering an at least one action; and

the at least one action to be performed in response to the at least one condition being triggered.

26. The system of claim 17 wherein performing at least one action in response to validating the received data includes at least one of:

transmitting the received data to the network entity;

generating a message to a source of the received data;

discarding the received data without transmitting it to the network entity providing output for an interface;

providing actions to be performed at the network entity;

providing actions to be performed at the source of the received data;

indicating the data is valid;

indicating the data is invalid;

providing valid data;

modifying the data;

deleting the data;

creating new data;

triggering a condition;

validating new data; and

further processing the data.

27. The system of claim 17 wherein the interface module and the validation engine reside in at least one of: a telecommunications network element, a telecommunications element management system for managing the telecommunications network element, and a network management system.

28. A non-transitory computer readable medium having stored thereon computer executable instructions that when executed by a processor of a computer control the computer to perform steps comprising:

providing, to a first computing system, a validation configuration file containing at least one rule for validating, based on domain knowledge of a second computing system, commands for configuring the second computing system, wherein the validation configuration file is provided from a developer of the second computing system, the validation configuration file being a human readable file convertible by the first computing system to a machine-readable format usable by the first computing system for performing data validation, wherein the first computing system includes a telecommunications network element; and

at the first computing system, receiving data associated with a command for configuring the second computing system, validating the received data using the at least one rule, wherein said validating comprises at least one of validating the command and providing presentation intelligence, wherein providing presentation intelligence includes modifying an appearance of a graphical user interface for configuring the network entity, wherein modifying the appearance of the graphical user interface includes proactively controlling input by disabling or enabling graphical user interface elements based on the capabilities of the telecommunications network element, and, responsive to validating the data, performing at least one action.

Assignments (14)
SHORT-FORM PATENTS SECURITY AGREEMENT Recorded Sep 5, 2024
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: HPS INVESTMENT PARTNERS, LLC, AS ADMINISTRATIVE AGENT
Reel/Frame 068857/0290 →
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 →
SECURITY INTEREST Recorded Jan 2, 2018
From: GENBAND US LLC; SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 044978/0801 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT Recorded Dec 29, 2017
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: GENBAND US LLC
Reel/Frame 044986/0303 →
CORRECTIVE ASSIGNMENT TO CORRECT PATENT NO. 6381239 PREVIOUSLY RECORDED AT REEL: 039269 FRAME: 0234. ASSIGNOR(S) HEREBY CONFIRMS THE PATENT SECURITY AGREEMENT. Recorded Jan 3, 2017
From: GENBAND US LLC
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 041422/0080 →
RELEASE AND REASSIGNMENT OF PATENTS Recorded Jul 7, 2016
From: COMERICA BANK, AS AGENT
To: GENBAND US LLC
Reel/Frame 039280/0467 →
PATENT SECURITY AGREEMENT Recorded Jul 6, 2016
From: GENBAND US LLC
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 039269/0234 →
RELEASE OF SECURITY INTEREST Recorded Jan 10, 2014
From: ONE EQUITY PARTNERS III, L.P., AS COLLATERAL AGENT
To: GENBAND US LLC
Reel/Frame 031968/0955 →
SECURITY AGREEMENT Recorded Nov 9, 2010
From: GENBAND US LLC
To: COMERICA BANK
Reel/Frame 025333/0054 →
PATENT SECURITY AGREEMENT Recorded Jun 18, 2010
From: GENBAND US LLC
To: ONE EQUITY PARTNERS III, L.P., AS COLLATERAL AGENT
Reel/Frame 024555/0809 →
CHANGE OF NAME Recorded Jun 2, 2010
From: GENBAND INC.
To: GENBAND US LLC
Reel/Frame 024468/0507 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 16, 2009
From: YE, NANCY; SHEN, JUN
To: GENBAND INC.
Reel/Frame 023387/0320 →