Apparatus and generic method for interfacing with managed objects in a communication network
View Patent ↗A method of interfacing with managed objects in a communication network, including: receiving an application independent request for service using generically represented data; mapping the request to a registry to determine the particular service application that can process the requested service; and executing the service application that can process the requested service. A network element in a communications network, includes: a managed object manager configured to map an application independent request for service and to forward the request to a service application that can process the requested service; and a registry coupled to the managed object manager and configured to provide mapped results that indicate the service application that can process the requested service.
1. A method of interfacing with managed objects in a communication network, the method comprising:
receiving, at a network element, an application-independent request for service, wherein the request includes generic operations and data in a generic format, wherein the generic data format is an open-ended name-value pair format, such that the generically represented data includes a subset of the name-value pairs supported by different service applications in the communications network so that the request may be used across the different services in the network;
mapping the request to a registry to identify, from a plurality of service applications at the network element, a service application that can process the request;
executing the identified service application based upon the request,
wherein a plurality of client applications use the generic data format to transmit application-independent requests for service in the communication network,
wherein the request is mapped to the registry by a managed object manager, and
wherein the managed object manager and the registry together manage a generic interface.
2. The method of claim 1 wherein the request includes a protocol.
3. The method of claim 2 , wherein the protocol includes Common Object Request Broker Architecture (CORBA).
4. The method of claim 1 , wherein the mapping is performed by a managed object manager and wherein upon identifying the service application that can process the received request, the managed object manager forwards the received request to the identified service application for processing.
5. The method of claim 1 , wherein the request is based upon a generic interface definition language (IDL).
6. The method of claim 1 , wherein the request for service is transmitted from a client application.
7. The method of claim 6 , wherein the client application transmitting the request includes an element management system.
8. The method of claim 1 , wherein the network element includes a switch.
9. The method of claim 1 , wherein the request permits the client application transmitting the request to control the network element.
10. The method of claim 1 , wherein the request permits the client application transmitting the request to manage the network element.
11. The method of claim 1 , wherein the request permits the client application transmitting the request to monitor the network element.
12. The method of claim 1 , further comprising:
adding a new application independent request for service to the registry to enable the mapping of the new request to one of the plurality of service applications.
13. The method of claim 1 , wherein
the mapping the request includes determining which of the plurality of service applications at the network element supports the subset of name-value pairs in the received request.
14. A method of interfacing with managed objects in a communication network, the method comprising:
generating, at a client application, an application-independent request for service, wherein the request includes generic operations and data in a generic format, wherein the generic data format is an open-ended name-value pair format, such that the generically represented data includes a subset of the name-value pairs supported by different service applications in the communications network so that the request may be used across the different services in the network; and
transmitting the request to a network element,
wherein a plurality of client applications use the generic data format to transmit application-independent requests for service in the communication network;
wherein the request is mapped to a registry by a managed object manager, and
wherein the managed object manager and the registry together manage a generic interface.
15. The method of claim 14 , wherein the request is based upon an interface definition language (IDL).
16. The method of claim 14 , the method further comprising:
determining, at the network element, which of the plurality of service applications at the network element supports the subset of name-value pairs in the received request in order to identify a service application that can process the request.
17. A network element in a communications network, comprising:
a registry configured to provide a mapping between one of a plurality of service applications and an application-independent request for service, wherein the request includes generic operations and data in a generic data format wherein the generic data format is an open-ended name-value pair format, such that the generically represented data includes a subset of the name-value pairs supported by different service applications in the communications network so that the request may be used across the different services in the network; and
a managed object manager, coupled to the registry, configured to receive the request and to forward the request to the one of the plurality of service applications for processing the request,
wherein a plurality of client applications use the generic data format to transmit application-independent requests for service in the communications network,
wherein the request is mapped to the registry by the managed object manager, and
wherein the managed object manager and the registry together manage a generic interface.
18. The network element of claim 17 , wherein the request includes Common Request Broker Architecture (CORBA).
19. The network element of claim 17 , wherein the request is based upon a generic interface definition language (IDL).
20. The network element of claim 17 , wherein
the request is forwarded to the one of the plurality of service applications, which is determined by the managed object manager to support the subset of name-value pairs in the received request based on the mapping.
21. An apparatus for interfacing with managed objects in a communication network, the apparatus comprising:
means for receiving, at a network element, an application-independent request for service, wherein the request includes generic operations and data in a generic data format, wherein the generic data format is an open-ended name-value pair format, such that the generically represented data includes a subset of the name-value pairs supported by different service applications in the communications network so that the request may be used across the different services in the network;
means for mapping the request to a registry to determine from a plurality of service applications, a service application that can process the request; and
means for executing the identified service application based upon the request,
wherein a plurality of client applications use the generic data format to transmit application-independent requests for service in the communication network,
wherein the request is mapped to the registry by a managed object manager, and
wherein the managed object manager and the registry together manage a generic interface.
22. The apparatus of claim 21 , wherein
the means for mapping includes means for determining which of the plurality of service applications at the network element supports the subset of name-value pairs in the received request.