Service information model for managing a telecommunications network
Systems, methods, and computer program embodiments are disclosed for providing network management services for a telecommunications network. In an embodiment, a request may be received for a service provided by an operations support system (OSS). Data may be retrieved from a network management database based on the received request. The network management database may store a plurality of network management data, and the stored data may be correlated to a service information model that defines a plurality of base network entities used to represent the architecture of the network. An information model template may then be read by the OSS that specifies one or more provider-specific network entities that extend the base network entities defined by the service information model. The retrieved data may then be operated on by the OSS, and the resulting output may be customized based on the provider-specific network entities of the information model template.
1. An operations support system for managing a telecommunications network, comprising:
one or more computing devices;
a network management database storing a plurality of network management data, wherein the stored data is correlated to a service information model that defines a plurality of base network entities used to represent an architecture of the network;
a query manager, implemented on the one or more computing devices, configured to:
receive a request for a service provided by the operations support system; and
retrieve data from the network management database based on the received request;
a parser, implemented on the one or more computing devices, configured to read an information model template, the information model template specifying one or more provider-specific network entities that extend the base network entities defined by the service information model, wherein each provider-specific network entity includes one or more custom attributes, and wherein the retrieved data contains data values associated with the custom attributes;
an execution manager, implemented on the one or more computing devices, configured to:
instantiate one or more of the base network entities based on the retrieved data, each base entity instance correlated to a provider-specific network entity specified by the information model template;
link the custom attributes of each provider-specific network entity and associated retrieved data values to the corresponding base entity instances; and
operate on the base entity instances to produce a data output, wherein the data output is customized based on the linked custom attributes and associated retrieved data values; and
a presenter, implemented on the one or more computing devices, configured to present the customized data output for display to a user.
2. The system of claim 1 , wherein the execution manager is further configured to, for each base network entity:
identify data entries of the retrieved data corresponding to the base network entity, wherein each data entry includes a custom entity identifier;
correlate the custom entity identifier to a provider-specific network entity specified by the information model template; and
instantiate the base network entity for each identified data entry.
3. The system of claim 1 , wherein the information model template is formatted as an ASCII-based structured data object.
4. The system of claim 1 , wherein the custom attributes and associated retrieved data values are linked to the corresponding base entity instances at runtime of the service.
5. The system of claim 1 , wherein each base entity instance includes a custom attribute data field, and wherein the execution manager is further configured to link the custom attributes by populating the custom attribute data field of each base entity instance with an array of key-value pairs representing the corresponding custom attributes and associated retrieved data values.
6. The system of claim 1 , wherein the base network entities of the service information model include a container entity that represents a physical or logical grouping of network objects within the network, and wherein an instance of the container entity can contain other container instances.
7. The system of claim 1 , wherein one or more of the custom attributes of each provider-specific network entity define presentation characteristics, and wherein the presenter is further configured to apply the presentation characteristics to the customized data output displayed to the user.
8. The system of claim 1 , wherein each provider-specific network entity includes relationship information between the provider-specific entity and other provider-specific entities specified in the information model template.
9. The system of claim 1 , wherein the information model template includes one or more data collection rules corresponding to the one or more custom attributes.
10. A method for providing network management services for a telecommunications network, comprising:
receiving a request for a service provided by an operations support system;
retrieving data from a network management database based on the received request, the network management database storing a plurality of network management data, wherein the stored data is correlated to a service information model that defines a plurality of base network entities used to represent an architecture of the network;
reading an information model template, the information model template specifying one or more provider-specific network entities that extend the base network entities defined by the service information model, wherein each provider-specific network entity includes one or more custom attributes, and wherein the retrieved data contains data values associated with the custom attributes;
instantiating one or more of the base network entities based on the retrieved data, each base entity instance correlated to a provider-specific network entity specified by the information model template;
linking the custom attributes of each provider-specific network entity and associated retrieved data values to the corresponding base entity instances;
operating on the base entity instances to produce a data output, wherein the data output is customized based on the linked custom attributes and associated retrieved data values; and
presenting the customized data output for display to a user.
11. The method of claim 10 , wherein the instantiating further comprises, for each base network entity:
identifying data entries of the retrieved data corresponding to the base network entity, wherein each data entry includes a custom entity identifier;
correlating the custom entity identifier to a provider-specific network entity specified by the information model template; and
instantiating the base network entity for each identified data entry.
12. The method of claim 10 , wherein the information model template is formatted as an ASCII-based structured data object.
13. The method of claim 10 , wherein the custom attributes and associated retrieved data values are linked to the corresponding base entity instances at runtime of the service.
14. The method of claim 10 , wherein each base entity instance includes a custom attribute data field, and wherein the linking further comprises populating the custom attribute data field of each base entity instance with an array of key-value pairs representing the corresponding custom attributes and associated retrieved data values.
15. The method of claim 10 , wherein the base network entities of the service information model include a container entity that represents a physical or logical grouping of network objects within the network, and wherein an instance of the container entity can contain other container instances.
16. The method of claim 10 , wherein one or more of the custom attributes of each provider-specific network entity define presentation characteristics, and wherein the presenting further comprises applying the presentation characteristics to the customized data output displayed to the user.
17. The method of claim 10 , wherein each provider-specific network entity includes relationship information between the provider-specific entity and other provider-specific entities specified in the information model template.
18. The method of claim 10 , wherein the information model template includes one or more data collection rules corresponding to the one or more custom attributes.
19. A non-transitory computer-readable storage device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising:
receiving a request for a service provided by an operations support system;
retrieving data from a network management database based on the received request, the network management database storing a plurality of network management data, wherein the stored data is correlated to a service information model that defines a plurality of base network entities used to represent an architecture of the network;
reading an information model template, the information model template specifying one or more provider-specific network entities that extend the base network entities defined by the service information model, wherein each provider-specific network entity includes one or more custom attributes, and wherein the retrieved data contains data values associated with the custom attributes;
instantiating one or more of the base network entities based on the retrieved data, each base entity instance correlated to a provider-specific network entity specified by the information model template;
linking the custom attributes of each provider-specific network entity and associated retrieved data values to the corresponding base entity instances;
operating on the base entity instances to produce a data output, wherein the data output is customized based on the linked custom attributes and associated retrieved data values; and
presenting the customized data output for display to a user.
20. The non-transitory computer-readable storage device of claim 19 , wherein the instantiating further comprises, for each base network entity:
identifying data entries of the retrieved data corresponding to the base network entity, wherein each data entry includes a custom entity identifier;
correlating the custom entity identifier to a provider-specific network entity specified by the information model template; and
instantiating the base network entity for each identified data entry.
21. The non-transitory computer-readable storage device of claim 19 , wherein the information model template is formatted as an ASCII-based structured data object.
22. The non-transitory computer-readable storage device of claim 19 , wherein the custom attributes and associated retrieved data values are linked to the corresponding base entity instances at runtime of the service.
23. The non-transitory computer-readable storage device of claim 19 , wherein each base entity instance includes a custom attribute data field, and wherein the linking further comprises populating the custom attribute data field of each base entity instance with an array of key-value pairs representing the corresponding custom attributes and associated retrieved data values.
24. The non-transitory computer-readable storage device of claim 19 , wherein the base network entities of the service information model include a container entity that represents a physical or logical grouping of network objects within the network, and wherein an instance of the container entity can contain other container instances.
25. The non-transitory computer-readable storage device of claim 19 , wherein one or more of the custom attributes of each provider-specific network entity define presentation characteristics, and wherein the presenting further comprises applying the presentation characteristics to the customized data output displayed to the user.
26. The non-transitory computer-readable storage device of claim 19 , wherein each provider-specific network entity includes relationship information between the provider-specific entity and other provider-specific entities specified in the information model template.
27. The non-transitory computer-readable storage device of claim 19 , wherein the information model template includes one or more data collection rules corresponding to the one or more custom attributes.