Systems and methods of storing and managing configuration data in telecommunications systems and devices

A system for storing and managing data in a telecommunications system or device, comprising:

• at least one computerized data repository operative to store at least a first instance of a first data object for a first object type, wherein the first instance of the first data object has a primary key that identifies the first instance of the first data object, and one or more foreign keys that reference one or more primary keys of one or more instances of one or more other data objects for one or more other object types;
• and
• a data manager including at least one processor operative to execute at least one program out of at least one memory:
• to generate a list of at least the one or more other object types;
• in response to a first user request to access an instance of the first data object for the first object type, to generate a data file that contains (1) first data pertaining to the respective foreign keys of at least the first instance of the first data object, and, (2) for at least the one or more other object types in the list, second data pertaining to the one or more primary keys of the one or more instances of the one or more other data objects referenced by the respective foreign keys of at least the first instance of the first data object;
• using at least the first data and the second data contained in the data file, to perform a data object validation process to determine a validity of each foreign key of at least the first instance of the first data object;
• and
• in the event each foreign key of at least the first instance of the first data object is determined to be valid, to allow the first user request.

A method of storing and managing data in a telecommunications system or device, comprising:

• storing, in a data repository, at least an instance of a first data object for a first object type, the instance of the first data object having a primary key that identifies the instance of the first data object, and one or more foreign keys that reference a primary key of at least an instance of a second data object for a second object type;
• and
• in response to a user request to add or modify an instance of the first data object for the first object type:
• generating, by the data manager, an add file that contains (1) first data pertaining to the respective foreign keys of at least the instance of the first data object, and (2) second data pertaining to the primary key of at least the instance of the second data object referenced by the respective foreign keys of at least the instance of the first data object;
• using at least the first data and the second data contained in the add file, performing, by the data manager, a first data object validation process to determine a validity of each foreign key of at least the instance of the first data object;
• and
• in the event each foreign key of at least the instance of the first data object is determined to be valid, adding or modifying the instance of the first data object for the first object type.