TELECOM ADAPTER LAYER SYSTEM, AND METHOD AND APPARATUS FOR ACQUIRING NETWORK ELEMENT INFORMATION

Abstract

A Telecom Adapter Layer (TAL) system includes a management unit and an execution unit connected via a distributed bus. In order to acquire network element (NE) information, an external service module sends a Get Info request to the execution unit according to the reference of the execution unit, and the execution unit acquires information from an NE according to the request and returns the NE information acquired from the NE to the external service module. The execution unit can be deployed in a device other than the service module or the management unit. The TAL system may be expanded to include more than one management unit and/or execution unit. By acquiring NE information from the execution unit, the TAL system is capable to perform NE management across a firewall.

Description

FIELD OF THE INVENTION

The present invention relates to network technologies based on the Telecom Management Network (TMN) architecture, and in particular, to a Telecom Adapter Layer (TAL) system, a method and an apparatus for acquiring network element (NE) information.

BACKGROUND OF THE INVENTION

In a TMN where various hardware devices and software systems are deployed, the network management system (NMS) can manage hardware devices and software systems that serve as NEs on a centralized basis. To support certain services, the NMS may need to communicate with the NEs via the TAL to acquire specific information of the NEs. FIG. 1 shows the position of TAL in a TMN in the prior art. The service module in the figure may be a performance module, a fault service module or a topology service module, which acquires information of NEs via the TAL.

In the prior art, the NMS is generally deployed in a centralized way. The usual practice is to deploy the service module and the TAL on a same device. FIG. 2 shows a centralized deployment mode in the prior art. In the case that number of NEs accessed by a centralized network management (NM) server reaches the upper limit, the NM server needs to be expanded. Due to the expansion defects of centralized deployment, the only way to enable normal management is to adopt an NM server with more advanced configuration, and export the data from the original NM server. It is apparent that the workload is heavy and the original NM server cannot be reused.

Another defect of centralized deployment is: If the network segment in which a NM server is located is different from the network segment in which a NE managed by the NM server is located and a firewall is deployed in the network segment of the NEs, the NM server is unable to access the NEs managed by itself because the NM server cannot acquire the addresses of the NEs. As a result, the NM server cannot manage the NEs behind the firewall.

There is another form of centralized deployment in the prior art, that is, cluster deployment, as shown in FIG. 3. In this mode, although the TAL is separated physically, it serves as a centralized TAL device logically to manage NEs. However, the TAL is also unable to access NEs which are managed by the TAL and behind a firewall.

SUMMARY OF THE INVENTION

The embodiments of the present invention provide a TAL system, a method and an apparatus for acquiring NE information to solve the problems along with the centralized deployment of TAL in the prior art.

According to an embodiment of the present invention, a TAL system is provided which includes:

a management unit adapted to communicate with an external service module via a distributed bus, adapted to receive a Get Execution Unit request which contains a NE ID from the external service module, acquire a reference of an execution unit corresponding to a NE according to a mapping between NE IDs and execution unit IDs, and return the reference of the execution unit to the external service module; where

the execution unit adapted to communicate with the external service module and an NE via distributed buses, adapted to acquire NE information from the NE according to a Get Info request sent by the external service module according to the reference of the execution unit, and return the NE information acquired from the NE to the external service module.

A method for acquiring NE information provided in an embodiment of the present invention includes:

by the management unit, querying an execution unit corresponding to an NE according to a Get Execution Unit request sent by an external service module, and returning a reference of the execution unit to the external service module;

sending, by the external service module, the Get Info request to the execution unit according to the reference of the execution unit,

acquiring the NE information from the NE according to the Get Info request, and

returning the NE information acquired from the NE to the external service module.

A management apparatus provided in an embodiment of the present invention, which is adapted to communicate with an external service module via a distributed bus, includes:

a management module, adapted to receive a Get Execution Unit request that contains a NE ID from an external service module, acquire a reference of the execution unit corresponding to a NE according to a mapping between NE IDs and execution unit IDs, and return the reference of the execution unit to the external service module.

An execution apparatus provided in an embodiment of the present invention, which is adapted to communicate with an external service module and an NE via a distributed bus, includes:

an execution module, adapted to acquire NE information from an NE according to a Get Info request sent by the external service module according to a reference of an execution unit, and return the NE information acquired from the NE to the external service module.

Based on the preceding technical solution, embodiments of the present invention have the following advantages. A TAL system is partitioned into a management unit and an execution unit that operate relatively independently via a distributed bus The execution unit may be deployed in a device other than the service module or management unit, thus realizing distributed deployment. The execution unit can be expanded by deploying multiple execution units on one or more than one device to meet the requirements for expanding the element management system (EMS).

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will become more readily apparent from the Detailed Description of the Invention which proceeds with reference to the drawings, in which:

FIG. 1 shows the position of the TAL in a TMN in the prior art;

FIG. 2 shows a centralized deployment mode in the prior art;

FIG. 3 shows a cluster deployment mode in the prior art;

FIG. 4 shows the structure of a TAL system in an embodiment of the present invention;

FIG. 5 shows a distributed deployment mode of the TAL system in an embodiment of the present invention;

FIG. 6 shows another distributed deployment mode of the TAL system in an embodiment of the present invention;

FIG. 7 shows the deployment of a TAL system in one device in an embodiment of the present invention;

FIG. 8 shows the deployment of a TAL system across a firewall in an embodiment of the present invention;

FIG. 9 shows the structure of a TAL system in an embodiment of the present invention;

FIG. 10 shows a procedure for acquiring NE information in an embodiment of the present invention;

FIG. 11 shows a procedure for acquiring NE information in an embodiment of the present invention;

FIG. 12 shows a procedure for acquiring NE information in an embodiment of the present invention;

FIG. 13 shows a procedure for acquiring NE information in an embodiment of the present invention;

FIG. 14 shows a procedure for acquiring NE information in an embodiment of the present invention; and

FIG. 15 shows a signaling flow for a performance module to acquire the CPU usage of a SUN host in an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

In one embodiment of the present invention, the management function is separated from the execution function in the TAL system, and each is configured to communicate via a distributed bus. Physically, the management unit and the execution unit can be deployed in different devices. Execution units may be added or removed as required, and their positions may be chosen as required.

FIG. 4 shows the structure of a TAL system according to this embodiment of the present invention. The TAL system includes a management unit 4 and an execution unit 5. The management unit 4 is adapted to communicate with an external service module 2 via a distributed bus. For example, the management unit 4 may receive a Get Execution Unit request sent by the external service module 2 over the distributed bus.

The Get Execution Unit request includes the NE ID corresponding to an NE 3. The management unit 4 acquires a reference for an execution unit corresponding to the NE 3 by mapping the NE ID in the Get Execution Unit request to an execution unit ID, and returns the reference of the execution unit to the external service module 2. The external service module 2 is a functional module that provides management service, and includes, for example, a performance module, a fault module and a topology module. The execution unit 5 is adapted to communicate with the external service module 2 and the NE 3 via distributed buses. The external service module 2 may send a Get Info request to the execution unit 5 according to the reference of the execution unit, and the execution unit 5 acquires information from the NE 3 according to the Get Info request and returns the information acquired from the NE 3 to the external service module 2.

The management unit 4 and the execution unit 5 are relatively independent. The management unit 4 can provide the external service module 2 with a reference of the execution unit 5, so that the external service module 2 may call the execution unit 5 to acquire NE information according to the reference. With this inter-independency in real deployment, it is feasible to deploy a management unit in a device at the network and deploy execution units in a distributed way to facilitate the acquisition of NE information. FIG. 5 shows a distributed deployment mode of a TAL system in an embodiment of the present invention. In the figure, an execution unit 5 is deployed in a host 8 and an management unit 4 is deployed in a host 7. In the host 8, multiple execution units may be deployed, and each execution unit may manage more than one NE. This configuration can facilitate the expansion of the EMS.

Each distributed bus herein refers to a distributed component technology with the object-oriented technology as a main feature. It adopts an object-oriented multi-layer client/server computing model, which organizes all resources distributed on the network (the system layer or the application layer, the traditional application or data) as objects; each object has a clearly defined access interface. The application that creates and maintains an object entity is called a server, and the application that accesses an object over the object interface is called a client. An object in the server can not only be accessed, but also serve as a client of other objects. A large system built on this structure is in accordance with the development of Internet. The large system can be easily maintained, expanded and updated (for example, upgrade in the case of 7*24-hour system running), and features high availability, openness and scalability. The distributed buses provided in an embodiment of the present invention can adopt Common Object Request Broker Architecture (CORBA), Component Object Model/Distributed Component Object Model (COM/DCOM), JavaBeans/EJB and so on.

CORBA is released by the Object Management Group (OMG) of Needham, Mass. The distributed computer software environment developed in compliance with CORBA specifications can be used in various hardware and software environments. A product complying with CORBA is called an object request broker (ORB), which is middleware and is responsible for establishing a client and server relationship between objects. Via an ORB, a client can transparently access an interface inside an object on a server, no matter whether the server object is on a same computer or in a network.

The working principle of an ORB is to intercept an Interface Definition Language (IDL) request sent by a client object, find a server object that can respond to the IDL request, send parameters to the server object, activate the interface in the server object and finally return the result to the requesting client. Therefore, the client does not need to obtain the location of the requested object or other information unrelated to the object interface such as the programming language and operating system of the object. Therefore, an ORB provides interoperability between different applications in a heterogeneous distributed environment, thus realizing seamless connection between multiple target systems.

In addition to the CORBA bus, a COM/DCOM bus may also be adopted. The DCOM can enable components based on COM to collaborate between two processes in different computers so that the programmer need not compile network codes to process communication required in interaction between distributed components across a network. In the DCOM, ActiveX components are used as objects.

A distributed bus based on JavaBeans components may also be adopted. JavaBeans relates to a technology of reusing a code component. JavaBeans allows software developers to develop and reuse the code component Bean based on Java.

FIG. 6 shows a distributed deployment mode of a TAL system in another embodiment of the present invention. In this deployment mode, host 9 where a management unit resides communicates with several hosts 10 and 11 where multiple execution units are deployed. It is apparent that this deployment mode can reduce the load on a host as a management side and facilitate additional expansion comparing to the centralized deployment mode. To expand the TAL system according to the present invention, it only needs to register the execution unit deployed in hosts in devices that provide naming service so as to establish connections between the execution unit and the management unit. Similarly, it only needs to deregister the execution unit if an execution unit should be canceled. Although the management unit and execution unit may be applicable to distributed deployment mode in the present invention, they may also be deployed in a same device. FIG. 7 shows the deployment of a TAL system in a same device in an embodiment of the present invention.

The execution units in the present invention are independent and loosely coupled, relative to the management unit and external service module, so as to resolve the difficulty in managing NEs across a firewall. FIG. 8 shows the deployment of a TAL system across a firewall in an embodiment of the present invention. A firewall is often deployed in an edge device of a local area network (LAN). When a device outside the LAN needs to access NEs in the LAN through the firewall, the device should obtain the mapped addresses of the NEs, so as to implement the access and management. For security reasons and the large number of NEs, however, it is impossible for the NMS to acquire the mapped addresses of all NEs. In the present invention, execution unit 5 is deployed inside a firewall and is responsible for managing NEs and interacting with a management unit 4. Therefore, if the IP addresses mapped by the execution unit 5 through Network Address Translation (NAT) or other means are stored in the management unit 4, access across a firewall can be realized.

A management unit and an execution unit may be implemented in various modes. The following provides a specific implementation. It should be appreciated that other implementations able to realize the inter-independence of the management unit and the execution unit and realize functions of the management unit and the execution unit are all covered in the protection scope of the invention. FIG. 9 shows the structure of a specific implementation of a TAL system in an embodiment of the present invention. The management unit 4 includes: a management unit interface service module 41, an execution unit management module 42, and a mapping management module 43. The management unit interface service module 41 is adapted to communicate with the external service module 2. The management unit interface service module 41 may receive a Get Execution Unit request sent by the external service module 2, and query a mapping management module 43 for an execution unit ID of the execution unit 5 corresponding to an NE ID of the NE 3 contained in the Get Execution Unit request to acquire a reference of the execution unit 5. The mapping management module 43 is adapted to communicate with the management unit interface service module 41 and stores the mapping between NE IDs and execution unit IDs. The execution unit management module 42 is adapted to communicate with with the management unit interface service module 41 and the naming service module 6. The execution unit management module 42 acquires the reference (similar to a pointer or access address of an execution unit) of the execution unit 5 from the naming service module 6 according to the execution unit ID. In this way, the coupling between an execution unit 5 and a service module 2 is weakened.

The execution unit 5 includes: an execution unit interface service module 51, an NE engine module 52, a script package management module 54, a command interpretation module 53 and a protocol management module 55. The execution unit interface service module 51 is adapted to communicate with the external service module 2. The execution unit interface service module 51 receives and processes a Get Info request from the external service module 2 over an IDL interface. The NE engine module 52 is adapted to communicate with the execution unit interface service module 51. The NE engine module 52 acquires an NE engine entity according to the NE ID in the Get Info request. The command interpretation module 53 is adapted to communicate with the NE engine module 52 and the script package management module 54. The command interpretation module 53 establishes a command engine according to the Get Info request forwarded by the NE engine module 52, finds a script package corresponding to an execution command, queries a corresponding script command according to the mapping between script packages and script commands and executes the script command. The mapping between script packages and script commands is stored in the script package management module 54. The protocol management module 55 is adapted to communicate with the command interpretation module 53. The protocol management module 55 converts the format of a script command into a bottom-layer protocol format of the device and sends the script command corresponding to the bottom-layer protocol format to the NE 3. Upon acquiring the NE information, the protocol management module 55 returns the NE information to the external service module 2 via the command interpretation module 53, the NE engine module 52 and the execution unit interface service module 51.

Based on the preceding TAL system, the present invention provides a method for acquiring NE information. FIG. 10 shows a procedure for acquiring NE information in a first embodiment of the present invention, including the following.

Step 100: A management unit 4 queries an execution unit 5 corresponding to an NE 3 according to a Get Execution Unit request sent by an external service module 2 and returns a reference of the execution unit 5 to the external service module 2;

Step 200: The external service module 2 sends a Get Info request to the execution unit 5 according to the reference of the execution unit 5. The execution unit 5 execute the operation of getting NE information of the NE 3 according to the Get Info request and returns the NE information acquired from the NE 3 to the external service module 2.

As each execution unit corresponds to different NEs, before acquiring the NE information of an NE, the external service module needs to acquire the reference of the execution unit 5 corresponding to the NE 3 via the management unit 4 and acquire the NE information through the execution unit 5.

FIG. 11 shows a procedure for acquiring NE information in a second embodiment of the present invention. Compared with the preceding embodiment, this invention fractionalizes Step 100. Specifically, the management unit 4 receives the Get Execution Unit request containing an NE ID from an external service module 2 over the IDL interface; the management unit 4 acquires the execution unit ID according to a preset mapping between NE IDs and execution unit IDs; the management unit 4 acquires the reference of the execution unit 5 according to the execution unit ID and returns the reference to the external service module 2.

Applied to the preceding TAL system, Step 100 includes:

Step 110: The management unit interface service module 41 in the management unit 4 receives the Get Execution Unit request containing an NE ID from the external service module 2 over the IDL interface;

Step 120: The management unit interface service module 41 sends a Get Execution Unit ID request containing the NE ID to the mapping management module 43;

Step 130: The mapping management module 43 returns the execution unit ID corresponding to the NE 3 to the management unit interface service module 41 according to the preset mapping between NE IDs and execution unit IDs;

Step 140: The management unit interface service module 41 sends a Get Execution Unit Ref request containing the execution unit ID to the execution unit management module 42;

Step 150: The execution unit management module 42 returns the reference of the execution unit 5 to the management unit interface service module 41 according to the execution unit ID;

Step 160: The management unit interface service module 41 returns the reference of the execution unit 5 corresponding to the NE ID to the external service module 2.

Step 200 described in the second embodiment is fractionalized in a third embodiment of the invention shown in FIG. 12. Specifically, the execution unit 5 receives the Get Info request containing the NE ID and an execution command from the external service module 2 over the IDL interface; the execution unit 5 acquires an NE engine entity according to the NE ID in the Get Info request; the execution unit 5 converts the format of the execution command in the Get Info request into the bottom-layer protocol format of the device via the NE engine entity, sends the execution command corresponding to the bottom-layer protocol format to the NE, acquires the NE information and returns the NE information to the external service module 2.

Applied to the preceding TAL system, Step 200 includes:

Step 210: The execution unit 5 receives the Get Info request containing the NE ID and an execution command from the external service module 2 over the IDL interface;

Step 220: The execution unit 5 acquires the NE engine entity according to the NE ID in the Get Info request;

Step 230: The execution unit 5 sends the execution command in the Get Info request to the command interpretation module 53 via the NE engine entity;

Step 240: The command interpretation module 53 acquires and calls a script command corresponding to the execution command in the Get Info request;

Step 250: The command interpretation module 53 calls the protocol management module 55 to convert the format of the script command into the bottom-layer protocol format of the device and sends the script command corresponding to the bottom-layer protocol format to the NE 3. The protocol management module 55 acquires the NE information and returns the NE information to the external service module 2 via the command interpretation module 53, the NE engine module 52 and the execution unit interface service module 51.

FIG. 13 shows the process of the method for acquiring NE information in a fourth embodiment of the present invention. Compared with the preceding embodiment, this embodiment provides a command interpretation mode, including:

Step 241: The command interpretation module 53 establishes a command engine;

Step 242: The command interpretation module 53 queries the script package management module 54 for a script package corresponding to the execution command in the Get Info request and finds an associated script command according to the mapping between script packages and script commands;

Step 243: The command interpretation module 53 loads the script package according to the acquired script package name and executes the script command.

FIG. 14 shows a procedure for acquiring NE information in a fifth embodiment of the present invention. Compared with the preceding embodiments, this embodiment adds a Step before Step 100, By the added step, the execution unit 5 is registered with the naming service module 6 and an associated naming service module ID is generated in the naming service module 6. This step establishes the mapping between the reference of an execution unit 5 and the execution unit ID.

During registration, the protocol information of the NE 3 such as the IP address and port, as well as the execution unit ID, is entered through topology module. With the execution unit ID entered, the execution unit acquires the protocol information of the NE 3 and sends the protocol information of the NE to the NE 3, thus acquiring the topology information of the NE 3. After the execution unit 5 acquires the NE information, the topology module generates an ID and sends the ID to the mapping management module 43, thus establishing the mapping between the NE ID and the execution unit ID. In this way, the NE 3 completes registration.

The following describes the procedure with a specific example in which a performance module serving as an external service module 2 acquires the CPU usage information of a SUN host. FIG. 15 shows a signaling flow for the performance module to acquire the CPU usage of a SUN host in an embodiment of the present invention.

Step 301: The performance module sends a Get Execution Unit request with the NE ID “.0.123”, that is, the NE ID of the SUN host, to the management unit interface service module 41 via an IDL interface;

Step 302: The management unit interface service module 41 sends a request, to get an execution unit ID mapped with the NE ID “.0.123” to the mapping management module 43;

Step 303: The mapping management module 43 returns the execution ID “.1.189” to the management unit interface service module 41 according to the preset mapping between NE IDs and execution unit IDs;

Step 304: The management unit interface service module 41 sends a request, to get a reference of the execution unit 5 whose execution unit ID is “.1.189” to the execution unit management module 42;

Step 305: The execution unit management module 42 queries the reference of the execution unit whose execution unit ID is “.1.189” according to the pre-registered information of the execution unit 5 in the naming service module 6 and sends the reference to the management unit interface service module 41;

Step 306: The management unit interface service module 41 returns the reference of the execution unit 5 to the performance module;

Step 307: The performance module sends a request containing the NE ID “.0.123” and the execution command “GetSunCpu” to the execution unit interface service module 51 over the IDL interface provided by the execution unit 5 whose execution unit ID is “.1.189”. The execution command “GetSunCpu” stands for acquiring the CPU usage of the NE,

Step 308: The execution unit interface service module 51 queries an NE engine instance mapped with the NE ID “.0.123” in the NE engine module 52;

Step 309: The NE engine module 52 transparently transmits the request to the command interpretation module 53 via the found NE engine instance;

Step 310: The command interpretation module 53 creates a command engine and sends a request for querying a script package mapped with the command “GetSunCpu” to the script package management module 54.

Step 311: The script package management module 54 returns the script package “SunHostInfo” mapped with the command “GetSunCpu” to the command interpretation module 53;

Step 312: The command interpretation module 53 calls the command “Package require SunHostInfo” to load the script package “SunHostInfo”;

Step 313: The command interpretation module 53 executes the command “GetSunCpu” in the script package;

Step 314: The command interpretation module 53 calls the interface “snmp::GetExt” between the protocol management module 55 and the script package when calling the command “GetSunCpu”;

Step 315: The protocol management module 55 calls the corresponding bottom-layer command “TclSnmpGetExt”;

Step 316: The protocol management module 55 sends a Get CPU Usage request to the SUN host via the bottom-layer command, where the CPU usage of the SUN host is packed into a Protocol Data Unit (PDU) and sent to the SUN host;

Step 317: The SUN host returns the CPU usage, for example, 90%, to the protocol management module 55;

Steps 318-321: The protocol management module 55 returns the CPU usage to the performance module through other modules in the execution unit 5 (shown in FIG. 9).

Based on the preceding procedure, the performance module acquires the CPU usage of the SUN host so that the performance module can manage the host. The preceding example is used only to describe the idea of the invention. It is not used to limit the invention to a specific implementation.

An embodiment of the present invention provides a management apparatus (management unit), which can be applied in the preceding TAL system. The management apparatus is communicated with external service modules via distributed buses. The management apparatus includes a management module, the management module is adapted to receive a Get Execution Unit request containing an NE ID from an external service module, acquire a reference of the execution unit corresponding to an NE according to the mapping between NE IDs and execution unit IDs and return the reference of the execution unit to the external service module 2.

The management module includes a mapping management module, a management unit interface service module and an execution unit management module. The mapping management module is adapted to store the mapping between NE IDs and execution unit IDs. The management unit interface service module communicates with an external service module and the mapping management module. The management unit interface service module is adapted to receive the Get Execution Unit request from the external service module, query the execution unit ID according to the NE ID in the Get Execution Unit request in the mapping management module to acquire the reference of the execution unit, and send the reference of the execution unit returned by the execution unit management module to the external service module. The execution unit management module communicates with the management unit interface service module and the naming service module. The execution unit management module is adapted to acquire from the naming service module the reference of the execution unit according to the execution unit ID and return the reference of the execution unit to the management unit interface service module.

An embodiment of the present invention also provides an execution apparatus (execution unit), which can be applied in the preceding TAL system. The execution apparatus communicates with an external service module and an NE via distributed buses. The execution apparatus includes an execution module, adapted to acquire information from the NE according to the Get Info request sent by the external service module based on the reference of the execution unit and return the information acquired from the NE to the external service module.

The execution module includes an execution unit interface service module, an NE engine module, a script package management module, a command interpretation module and a protocol management module. The execution unit interface service module, in communication with the external service module, is adapted to receive and process the Get Info request from the external service module over the IDL interface. The NE engine module, in communication with the execution unit interface service module, is adapted to acquire a corresponding NE engine entity according to the NE ID in the Get Info request and forward the Get Info request to the command interpretation module via the NE engine entity. The script package management module is adapted to store the mapping between script packages and script commands. The command interpretation module, in communication with the NE engine module and the script package management module, is adapted to receive the Get Info request forwarded by the NE engine module, create a command engine according to the Get Info request, query the corresponding script package of the execution command in the Get Info request via the command engine, and find the corresponding script command according to the mapping between script packages and script commands. The protocol management module, in communication with the command interpretation module, is adapted to convert the format of a script command into the bottom-layer protocol format of the device, send the script command corresponding to the bottom-layer protocol format to the NE, acquire the NE information and return the NE information to the external service module via the command interpretation module, the network engine module and the execution unit interface service module.

In the present invention, a TAL system is divided into inter-independent management units and execution units via distributed buses. The execution unit can be deployed in a device other than the service module or management unit, thus realizing distributed deployment. In addition, the execution unit may be extended so as to deploy multiple execution units in one or more devices to satisfy the requirement of EMS expansion. As an execution unit is independent of the management unit, the execution unit can be deployed in a LAN behind a firewall, and the management unit can access the mapped-to execution unit through NAT, thus realizing NE management across a firewall.

It is apparent that those skilled in the art can make various modifications and variations to the present invention without departing from the scope of the present invention. The present invention is intended to cover these modifications and variations provided that they fall within the protected scope defined by the following claims. It is intended that this scope include all foreseeable equivalents to the structural elements and process steps described herein with reference to FIGS. 4-15.

Claims

1. A Telecom Adapter Layer (TAL) system, comprising: a management unit adapted to communicate with an external service module via a first distributed bus, and adapted to receive a Get Execution Unit request from the external service module and return a reference of an execution unit to the external service module response to the Get Execution Unit request;the execution unit adapted to communicate with the external service module and a network element (NE) via the first distributed bus and a second distributed bus, respectively, the execution unit being adapted to acquire NE information from the NE according to a Get Info request sent by the external service module based on the reference of the execution unit and return the NE information to the external service module.

2. The TAL system of claim 1, wherein the management unit comprises: a management unit interface service module adapted to communicate with the external service module, adapted to receive the Get Execution Unit request sent by the external service module, send the reference of the execution unit to the external service module; andan execution unit management module adapted to communicate with the management unit interface service module, adapted to acquire the reference of the execution unit and return the reference to the management unit interface service module.

3. The TAL system of claim 2, wherein the management unit interface service module is adapted to receive a Get Execution Unit request that contains a NE ID.

4. The TAL system of claim 3, wherein the management unit further comprises: a mapping management module, adapted to store a mapping between the NE ID and Execution Unit ID; wherein the execution unit management module adapted to communicate with a naming service module which is adapted to establish a mapping between the reference of the Execution Unit and the Execution Unit ID;the management unit interface service module is adapted to query the mapping management module for the execution unit ID mapped with the NE ID in the Get Execution Unit request; andthe execution unit management module is adapted to acquire the reference of the execution unit from the naming service module according to the execution unit ID.

5. The TAL system of claim 1, wherein the execution unit comprises: an execution unit interface service module adapted to communicate with the external service module, the execution interface service module being further adapted to receive the Get Info request sent by the external service module;a NE engine module adapted to communicate with the execution unit interface service module, and adapted to acquire an NE engine entity according to an NE ID in the Get Info request and forward the Get Info request to a command interpretation module via the NE engine entity;a script package management module, adapted to store mapping between script packages and script commands;the command interpretation module adapted to communicated with the NE engine module and the script package management module, and adapted to receive the Get Info request forwarded by the NE engine module, create a command engine according to the Get Info request, query a script package of an execution command in the Get Info request, query the script command based on the mapping between script packages and script commands and execute the script command; anda protocol management module adapted to communicate with the command interpretation module, and adapted to convert a format of the script command into a bottom-layer protocol format, send the script command corresponding to the bottom-layer protocol format to the NE, acquire the NE information and return the NE information to the external service module via the command interpretation module, the NE engine module and the execution unit interface service module.

6. The TAL system of claim 1, wherein the management unit and the execution unit are deployed in a single device.

7. The TAL system of claim 1, comprising a plurality of execution units which are deployed in a single device.

8. The TAL system of claim 1, wherein the distributed bus is a Common Object Request Broker Architecture bus.

9. A method for acquiring network element (NE) information, comprising the steps of: querying, by a management unit, an execution unit corresponding to a network element (NE) according to a Get Execution Unit request sent by an external service module;returning, by the management unit, a reference of the execution unit to the external service module;sending, by the external service module, a Get Info request to the execution unit according to the reference of the execution unit;acquiring, by the execution unit, NE information from the NE according to the Get Info request; andreturning, by the execution unit, the NE information acquired from the NE to the external service module.

10. The method of claim 9, further comprising the steps of: receiving, by the management unit, the Get Execution Unit request containing an NE ID from the external service module over an IDL interface;acquiring, by the management unit, an execution unit ID based on a preset mapping between the NE ID and an execution unit ID;acquiring, by the management unit, a reference of the execution unit according to the execution unit ID; andreturning, by the management unit, the reference to the external service module.

11. The method of claim 9, further comprising the steps of: receiving, by the execution unit, the Get Info request containing an NE ID and an execution command from the external service module over an IDL interface;acquiring, by the execution unit, a NE engine entity according to the NE ID in the Get Info request;converting, by the execution unit, a format of the execution command in the Get Info request into a bottom-layer protocol format;sending, by the execution unit, the execution command corresponding to the bottom-layer protocol format to the NE to acquire the NE information; andreturning, by the execution unit, the NE information to the external service module.

12. The method of claim 11, wherein the step of converting the format of the execution command into the bottom-layer protocol format, comprises the steps of: creating a command engine;querying a script package of the execution command in the Get Info request via the command engine;identifying a script command according to mapping between script packages and script commands;loading the script package according to an acquired script package name; andconverting a format of the script command into the bottom-layer protocol format.

13. The method of claim 10, further comprising the steps of: registering the execution unit with a naming service module; andgenerating a mapping between the reference of the execution unit and the execution unit ID;wherein the step of acquiring the reference of the execution unit according to the execution unit ID further, comprises the steps of:querying, by the management unit, the reference of the execution unit mapped with the execution unit ID based on the mapping between the reference of execution unit and the execution unit ID in the naming service module.

14. A management apparatus, adapted to communicate with an external service module via a distributed bus, comprising: a management unit, adapted to receive a Get Execution Unit request from the external service module to and return the reference of an execution unit to the external service module response to the Get Execution Unit request.

15. The management apparatus of claim 14, wherein the management unit comprises: a management unit interface service module, which adapted to communicate with the external service module, and is adapted to receive the Get Execution Unit request sent by the external service module and, send the reference of the execution unit to the external service module; andan execution unit management module, which adapted to communicate with the management unit interface service module, and is adapted to acquire the reference of the execution unit and return the reference to the management unit interface service module.

16. The management apparatus of claim 15, wherein the management unit interface service module is adapted to receive a Get Execution Unit request that contains a NE ID.

17. The management apparatus of claim 14, wherein the management unit further comprises: a mapping management module which is adapted to store mapping between the NE is ID and execution Unit ID; whereinthe execution unit management module is adapted to communicate with a naming service module which is adapted to establish a mapping between the reference of the Execution Unit and the Execution Unit ID;the management unit interface service module is adapted to query the mapping management module for the execution unit ID mapped with the NE ID in the Get Execution Unit request; andthe execution unit management module is adapted to acquire the reference of the execution unit from the naming service module according to the execution unit ID.

18. An execution apparatus, adapted to communicate with an external service module and a network element (NE) via distributed buses, comprising: an execution unit, adapted to acquire NE information from the NE according to a Get Info request sent by an external service module based on a reference of the execution unit, and return the NE information acquired from the NE to the external service module.

19. The apparatus of claim 18, wherein the execution unit comprises: an execution unit interface service module adapted to communicate with the external service module, and adapted to receive the Get Info request sent by the external service module over an IDL interface;an NE engine module adapted to communicate with the execution unit interface service module, and adapted to acquire an NE engine entity according to the NE ID in the Get Info request and forward the Get Info request to a command interpretation module via the NE engine entity;a script package management module, adapted to store mapping between script packages and script commands;the command interpretation module adapted to communicate with the NE engine module and the script package management module, and adapted to receive the Get Info request forwarded by the NE engine entity, create a command engine according to the Get Info request, query a script package of an execution command via the command engine, and identify a script command based on the mapping between script packages and script commands and execute the script command; anda protocol management module adapted to communicate with the command interpretation module, and adapted to convert a format of the script command into the bottom-layer protocol format, send the script command corresponding to a bottom-layer protocol format to the NE, and acquire the NE information and return the NE information to the external service module via the command interpretation module, the NE engine module and the execution unit interface service module.

20. The TAL system of claim 1, wherein the management unit and the execution unit are deployed in different devices.

21. The TAL system of claim 1, comprising a plurality of multiple execution units which are deployed in different devices.