【精品文档】04中英文双语计算机专业外文翻译成品：TMN网络管理平台的设计与实现

此文档是毕业设计外文翻译成品（ 含英文原文+中文翻译），无需调整复杂的格式！下载之后直接可用，方便快捷！本文价格不贵,也就几十块钱！一辈子也就一次的事！外文标题：The Design and Implementation of a Network Management Platform for TMN外文作者：Dongjin Han*, Wen-Zhe Cui，文献出处：International Conference on Computer Communications and Networks,2018,516(如觉得年份太老，可改为近2年，毕竟很多毕业生都这样做)英文2131单词， 14568字符(字符就是印刷符)，中文3577汉字。The Design and Implementation of a Network Management Platform for TMNDongjin Han*, Wen-Zhe Cui，Youngeun Park, Shinhyuk Kang and Sunshin An Computer Network Lab., Dept, of Electronic Eng., Korea UniversityAbstractNetwork management systems which administer actual network resources are developed based on a software system called network management platforms. Network management platforms provide major functions defined in TMN and interfaces to develop network management systems.Our research designs and implements a network management platform suitable to the TMN environment of today and tomorrow. This platform increases the efficiency in handling management information by completely separating Managed Object class information from instance information. In addition, the performance of the platform is significantly improved through a multistructured MIT and a multi-staged arrangement of the execution of CMIS services. Furthermore, our platform allows a new MIB to be added to the managed system in run-time, solving the problem of having to recompile and restart the network management system. In our research, we develop a new concept of Class Level Filtering, which yields relatively high performance as the MIT becomes larger.1. IntroductionThe deployment of communication networks and distributed computing systems requires the use of open standards-based management systems. Telecommunication Management Network (TMN) provides the worldwide accepted ultimate framework for the unified management of all types of telecommunication services and underlying services in the future. TMN systems use object-oriented information modeling techniques and manager/agent concepts that underlie the Open Systems Interconnection (OSI) system managementl. Network management applications which administer actual network resources are developed based on a software system called a network management platform. In general, network management platforms provide both run-time and development environments. The run-time environment is represented by common management services, which reflect the overall operability of a management platform. The development environment provides the portability for management applications and allows the integration of these applications into the platform services. The performance of network management applications relies upon the performance of a network management platform itself. During the process of performing management operations in a managed system, all executed codes are provided by a network management platform with the exception of user codes. The user codes can be added to satisfy a management system developers requirements, e.g. interactions with real resource.This paper deals with the design and implementation of a new network management platform for TMN. Our platform consists of two parts, namely, Management System Kernel(MSK) and Managed Object Generation Envi- ronment(MOGE). MSK provides management systems with run-time environment including not only generic platform services but also additional new features. MOGE provides a management applications development environment including Guidelines for the Definitions of Management Objects(GDMO) compiler, ASN.I compiler, user Applications Program Interfaces(APIs) for hooks and configuration specific files. Our platform supports overall functionality defined in OSI systems management and efficient development environment. In addition, it provides new features that enhance the performance and adaptability. The additional features are: Dedicated Agent: A managed system can be requested from multiple managing systems at the same time. Our platform serves each managing system with a respective Dedicated Agent, allowing requests from multiple managing systems to be performed in the managed system concurrently. Internal Data Structure(IDS) and External Meta MIB(EMM): Our platform completely separates class information from Managed Object(MO) implementation. The class information such as package and attribute group information is generated from GDMO scripts and stored in specific files. The set of these specific files are named as External Meta MIB. When a managed system starts or the Dynamic Class Loading is invoked, Internal Data Structure is generated or updated in the managed systems process by analyzing and gathering information of the EMM. dual structured Management Information Tree(MIT): In our implementation, MIT consists of the complex structures of balanced Binary Search Trees(BSTs) and doubly linked lists. The balanced BSTs are used in searching a base MO, and the doubly linked lists in scoping operation respectively. Class Level Filtering(CLF): In this paper, all instances in an MIT are classified by MO class information. Using this information, instances of improper classes may be excluded from being filtered though being selected by scoping. Dynamic Class Loading: In conventional network management platforms, if a new MO class is developed while a managed system process is running, the process has to be regenerated and restarted for the addition of newly-made MO class information to take effect, causing fatal emptiness. To overcome this defect, we provide the Dynamic Class Loading feature.2. Overall architecture ComponentsThe platform consists of two parts, the MSK and MOGE. Figure 1 depicts overall platform architecture and three kinds of operation flows: numeric, uppercase alphabet, and lowercase alphabet.As depicted in Figure 1, the MSK is comprised of seven components. Agent Core is a main component of the platform and runs in the form of a thread. It is responsible for initializing a managed system, establishing an association with managing systems and performing Dynamic Class Loading. Dedicated Agent is also a form of a thread and is created by the Agent Core following an association request from a managing system. Its role is to provide a specified managing system with management services. The full set of MO instances available across a management interface is organized in the MIT. When an operation is performed in a managed system, all MO instances are accessed through the MIT2. In our study, we design and implement the MIT as a complex structure consisting of balanced BSTs and doubly linked lists. IDS maintains the information on all MO classes. The Agent Core constructs the IDS based on the information of the EMM. Each class information, such as object identifiers, packages, name bindings, and allomorphs, is built in its respective balanced search tree known as an AA tree. Management Information Base(MIB) stores MO instances that are the subjects to all management operations except for M-Create operations. Scheduler provides timer service with MO instances. By using Scheduler APIs, corresponding functions in MO instances can be invoked in specific time or interval. Monitor enables MO instances to receive messages from real resource. The Communication Infra Structure(CIS) provides management applications with communication services. The CIS consists of Association Control Service Element(ACSE), ROSE(Remote Operation Service Element), CMIP(Common Management Information Protocol) stack and CMIS(Common Management Information Service) API.Even though MOGE consists of several components, we will focus only on selected components for the con* centration on the subject of this paper. The ASN.l compiler produces C+ class typed syntax from ASN.l definition of the syntax. The GDMO compiler produces MO codes and an EMM from GDMO scripts. The EMM is comprised of several files, which contain the information of MO classes. It is used to construct an IDS in initiating a managed system or performing the CLF. MO framework provides basic functions of an MO for management operations, and hooks which enable a managed system developer to insert user codes to satisfy his requirements. Three kinds of operation flowsIn the paper, operation flows in the platform can be separated into three kinds of major operation flows. One is concerned with initializing managed systems(l-6) in MSK, another with establishing an association and performing management operations including event notifica- tion(A-J) and the last with generating new MO classes in MOGE(a-g).Initializing a managed systemWhen a managed systems starts, Agent Core creates Scheduler and Monitor threads. Also, it constructs IDS from EMM(l). By invoking the creation functions of MO classes in the IDS, Agent Core creates initial MO instances(2). A user may want to specify the new MO instances or reload the saved data of MO instances from persistent devices as the initial MO instances. When an MO instance is created, user code in the MO may be invoked for satisfying the developers requirements. This code may be intended to interact with real resource(3). In addition, the user code may request a timer service to the Scheduler and register an input port to the Monitor to receive messages from specific real resource(4). The Monitor begins to detect the signal(5). Once all of the above mentioned tasks are completed, the MO instances are registered in an MIT(6).3. ImplementationAgent CoreThe Agent Core is the main module of the platform and runs in the form of a thread. It plays the following roles as shown in Figure 2: Constructs an IDS containing all information of MO classes from EMM. Initializes the Scheduler and Monitor, which respectively supports timer service and interaction with real resource Establishes associations with managing systems.Creates a Dedicated Agent to take charge of subsequent management operations from the managing system. Whenever an association request of another managing system arrives, the Agent Core repeats this step.Dedicated AgentThe Dedicated Agent takes charge of management operations requested by a single managing system. It also runs in the form of a thread and is created by the Agent Core. The Dedicated Agent plays the following roles(see Figure 3): Provides a specified managing system with a management service. Multiple Dedicated Agents mayManagement Information TreeIn a managed system, all MO instances are administered in an MIT based on containment relationship. The containment relationship allows one MO instance to contain one or more other MO instances, and a containing MO instance can be contained in another MO instance. Each MO instance can be identified with a unique name based on the containment relationship. A management operation can be requested on one or more MO instances by a managing system specifying the scope and filter parameters in the management operation primitives2.Managed Object frameworkThe MO framework provides the feature of the basic function of the management operations and the hooks where developer can insert the user code to satisfy his requirements. The hooks are implemented through the virtual function. All the virtual functions are defined in Top class, which is the general MO class defined in X.721. The contents of instances of an MO class using conditional packageis) should be decided dynamically in MO creation time. In other words, instances of same MO class may have different attributes and actions individually. Supporting this feature, the MO framework provides an MO class with the ultimate flexibility.External Meta MIBThe EMM is used to initialize and update the IDS when an MO class needs to be added into a management application. When a GDMO compiler compiles a GDMO script defined by a developer, the EMM files are generated with MO class codes. EMM includes two parts: one reflects the MO class definition described in a GDMO script, and the other identifies the location and the name of shared libraries of MO classes.GDMO compilerThe GDMO compiler is an essential component of management platform. The output of GDMO compiler includes MO class C+ codes and the EMM. The MO class codes are compiled into shared libraries by using C+ compiler, and the EMM is used to initialize and update the IDS when the MO classes are added into a network management system.management environments. Hence, Under the above test conditions, the response time of the GET operations in both of platforms is tested in the following three cases with variable filter: No filter is specified Filter is set with “testObjectlcT Filter is set with “panzeeAttr=10”4ConclusionIn this paper, we have designed and implemented a network management platform, which supports not only the features defined in OSI management model, but also some additional ones. The managed system based on our platform is able to concurrently handle the requests from multiple managing systems. In addition this platform increases the efficiency in handling management information by completely separating Managed Object class information from instance information. Introducing new concepts, namely Class Level Filtering and Dynamic Class Loading, the performance and the stability of the network management system could be improved. From the performance evaluation, it can be found that the overall performance of the network management system is significantly improved by using the advanced features of the platform. In the future, we plan to improve the dynamic loading mechanism to allow more flexible capability. Furthermore, a more detailed report on performance evaluation will follow.References1 CCITT, Systems Management Overview, CCITT X.700 series recommendations, CCITT, 19922 CCITT, Overview of TMN Recommendations, CCITT X.3000 series recommendations, CCITT, 19923 George Pavlou, “The OSIMIS Platform: Making OSI Management Simple” in Proc. INM IV, pp. 480-493, 1995.4 Uyless Black, “Network Management Standards, McGraw-Hill Series on Computer Communications, 19955 Morris Sloman, et al., Network and Distributed Systems Management, Addison-Wesley Publishing Company, 19946 Iosif G. Ghetie, “Network and System Management Platform analysis and Evaluation”，Kluwer Academic Publishers, 19977 Charles J. Northrup, “Programming with UNIX Threads”， John Wiley & Sons, Inc., 19968 Salah Aidarous, Thomas Plevyak, Telecommunications Network Management Technologies and Implementations”， IEEE Series on Network Management, 1997TMN网络管理平台的设计与实现Dongjin Han*, Wen-Zhe Cui，Youngeun Park, Shinhyuk Kang and Sunshin An Computer Network Lab., Dept, of Electronic Eng., Korea University摘要：管理着实际网络资源的网络管理系统的开发都是基于被称之为网络管理平台的软件系统。网络管理平台提供TMN中定义的主要功能以及连接着去开发网络管理系统。我们的研究设计并实现了既适合当今又适合未来TMN环境的网络管理平台。该平台通过将实例信息中的Managed Object类信息实现完全分离，提高了处理管理信息的效率。此外，通过多结构MIT和CMIS服务执行的多阶段布置，平台的性能得到显着改善。此外，我们的平台允许在运行时将新的MIB添加到受管系统，解决了重新编译和重新启动网络管理系统的问题。在我们的研究中，我们提出了一个新的级别过滤的概念，随着MIT功能的扩大，其性能也相对较高。1.引言通信网络和分布式计算系统的部署需要使用基于开放式标准的管理系统。通信管理网络（TMN）为将来统一管理各种通信业务和基础业务提供了全球公认的终极框架。 TMN系统使用面向对象的信息建模技术和基于开放系统互连（OSI）系统管理的管理人或代理人概念1。管理着实际网络资源的网络管理系统的开发都是基于被称之为网络管理平台的软件系统。通常，网络管理平台同时提供运行时间和开发环境。运行时环境由通用管理服务来表现，它反映了管理平台的整体可操作性。开发环境为管理应用程序提供了方便性，并允许将这些应用程序集成到平台服务中。网络管理应用程序的性能依赖于网络管理平台本身的性能。在管理系统中执行管理操作的过程中，所有执行的代码都由网络管理平台提供，用户代码除外。可以添加用户代码以满足管理系统开发者的要求，例如，嫁接到真实的资源。本文介绍了TMN新的网络管理平台的设计和实现。 我们的平台由两部分组成，即管理系统内核（MSK）和管理对象生成环境（MOGE）。 MSK为管理系统提供运行时环境，不仅包括通用平台服务，还包括其他新功能。 MOGE提供了一个管理应用程序开发环境，包括管理对象定义指南（GDMO）编译器，ASN.I编译器，针对挂钩和配置特定数据存储的用户应用程序接口（API）。 我们的平台支持OSI系统管理和高效开发环境中定义的全部功能。 此外，它还提供了可增强性能和适应性的新功能。 附加功能是： 专用代理：可以同时从多个管理系统请求受管系统。 我们的平台为每个管理系统提供相应的专用代理，允许来自多个管理系统的请求同时在管理系统中执行。 内部数据结构（IDS）和外部元管理信息库（EMM）：我们的平台将类信息与管理对象（MO）实现完全分开。 类信息（如安装包和属性组信息）由GDMO脚本生成并存储在特定文件中。 这些特定存储信息的集合被命名为外部元管理信息库。 当受管系统启动或调用动态类加载时，通过分析和收集管理信息库的信息，在受管系统的进程中生成或更新内部数据结构。双结构管理信息树（MIT）：在我们的实现中，MIT由平衡二叉搜索树（BST）和双向链表组成的复杂结构组成。 平衡BST分别用于搜索基本MO和双向链表。CLF（分层过滤）：在本文中，MIT中的所有实例都按MO类信息进行分类。 使用这些信息，不正确层级的实例可能被排除在筛选之外，尽管是通过范围选择来进行筛选。动态类加载：在传统的网络管理平台中，如果在管理系统进程运行时开发新的MO类，则必须重新生成并重新启动该进程以添加新生成的MO类信息才能生效，从而导致致命的空虚。 为了克服这个缺陷，我们提供了动态类加载功能。2整体架构组件该平台由两部分组成，即MSK和MOGE。 图1描述了整体平台架构和三种操作流程：数字，大写字母和小写字母。如图1所示，MSK由七个组件组成。 Agent Core是该平台的主要组件，并以线程的形式运行。它负责初始化受管系统，建立与管理系统的关联并执行动态类加载。专用代理也是线程的一种形式，由Agent Core根据来自管理系统的关联请求创建。它的作用是为管理系统提供管理服务。整个管理界面可用的全套MO实例在MIT中组织。当在管理系统中执行操作时，所有的MO都通过MIT访问2。在我们的研究中，我们设计和实施MIT是一个由平衡BST和双向链表组成的复杂结构。 IDS维护所有MO类别的信息。 Agent Core根据EMM的信息构建IDS。每个类信息（如对象标识符，安装包，名称绑定和异形）均建立在其各自的称为AA树的平衡搜索树中。管理信息库（MIB）存储作为除M-Create操作以外的所有管理操作的MO实例。调度程序为MO实例提供定时器服务。通过使用Scheduler API，可以在特定的时间或间隔内调用MO实例中的相应功能。监视器可以使MO信息从真实资源接收消息。通信基础设施结构（CIS）为管理应用程序提供通信服务。 CIS由关联控制服务元素（ACSE），ROSE（远程操作服务元素），CMIP（通用管理信息协议）堆栈和CMIS（通用管理信息服务）API组成。尽管MOGE由多个组件组成，但我们将只关注选定的组件以专注于本文的研究主题。 ASN.l编译器根据秩序排列的ASN.l定义生成C +类类型排列秩序。 GDMO编译器通过GDMO脚本生成MO代码和EMM。 EMM由几个文件存储组成，其中包含MO类的信息。 它用于在启动受管系统或执行CLF时构建IDS。 MO框架为管理操作提供了MO的基本功能，以及使托管系统在开发人员能够插入用户代码以满足其需求。三种运行流程本文将平台的运行流程分为三种主要运行流程。 一个涉及MSK中的管理系统（I-6）的初始化，另一个涉及建立关联并执行包括事件通知（A-J）在内的管理操作，另一个涉及在MOGE（a-g）中生成新的MO类。初始化管理系统当管理系统启动时，Agent Core将创建调度程序和监视器线程。 另外，它从EMM构建IDS（l）。 通过调用IDS中MO类的创建功能，Agent Core创建初始MO实例（2）。 用户可能想要指定新的MO实例或从永久设备重新加载保存的MO实例数据作为初始MO实例。 当MO实例被创建时，MO中的用户代码可以被调用以满足开发者的要求。 此代码可能旨在与真实资源进行交互（3）。 另外，用户代码可以向调度程序请求定时器服务，并将输入端口注册到监视器以接收来自特定实际资源的消息（4）。 监视器开始检测信号（5）。 一旦所有上述任务完成，MO实例就在MIT进行了注册（6）。3 实现以Agent为核心Agent Core是平台的主要模块，并以线程的形式运行。 它起到以下的作用，如图2所示：构建一个包含来自EMM的MO类的所有信息的IDS。初始化调度器和监视器，它们分别支持定时器服务和与实际资源的交互建立与管理系统的关联。创建专