WO2008052389A1 - Procédé et système de réalisation d'interfaces universelles dans le système de gestion de réseau - Google Patents

Procédé et système de réalisation d'interfaces universelles dans le système de gestion de réseau Download PDF

Info

Publication number
WO2008052389A1
WO2008052389A1 PCT/CN2006/002935 CN2006002935W WO2008052389A1 WO 2008052389 A1 WO2008052389 A1 WO 2008052389A1 CN 2006002935 W CN2006002935 W CN 2006002935W WO 2008052389 A1 WO2008052389 A1 WO 2008052389A1
Authority
WO
WIPO (PCT)
Prior art keywords
parameter
interface
information
type
message
Prior art date
Application number
PCT/CN2006/002935
Other languages
English (en)
Chinese (zh)
Inventor
Qingfei Nian
Original Assignee
Zte Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Priority to PCT/CN2006/002935 priority Critical patent/WO2008052389A1/fr
Priority to CN2006800562002A priority patent/CN101529807B/zh
Publication of WO2008052389A1 publication Critical patent/WO2008052389A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks

Definitions

  • the present invention relates to an interface of a network management system, and more particularly to an interface implementation method and system for a network management system in the field of telecommunications. Background technique
  • Telecom operators and equipment manufacturers monitor and manage telecommunication equipment through centralized telecommunication network management.
  • the telecommunications network management is divided into a workstation management function (MF), an operating system function (OSF), a network element function (NEF), and a Q interface adaptation function (QAF), each of which functions. It is composed of a plurality of sub-function modules, which are connected between the workstation function (WFS) and the operating system function (OSF) defined by the Telecommunication Management Network (TMN), between different telecommunication management networks or non-telecom management.
  • MF workstation management function
  • OSF operating system function
  • NEF network element function
  • Q interface adaptation function Q interface adaptation function
  • the interface (Qx) between QAFs interacts.
  • Each sub-function module must define and organize the interface in order to interact with other functions.
  • the implementation of the interface between systems or within the system is pre-defined or agreed within the application.
  • the parameter types and parameters of the interface are fixed.
  • the interface needs to be recompiled (internal convention) The way it is not needed) and the upgrade of the application, this change may introduce new problems and increase the complexity of system maintenance.
  • the implementation principle is to replace the original interface with a new derived interface.
  • the technical problem to be solved by the present invention is to provide a general interface implementation method and system for the network management system, which can enhance the interface expansion capability of the network management system, and can save development and maintenance costs of the network management system.
  • the present invention provides a method for implementing a common interface of a network management system, including the following steps:
  • the packet transmitted by the interface operation is defined as a general operation interface structure, and the operation information to be filled in the structure includes an operation identifier and an operation parameter, and the operation parameter is embodied in the form of a list, including a parameter name and a parameter value item.
  • Parameter values can be of any data type;
  • the operation information is configured and saved in the system, and the operation identifier used by the operation interface and the parameter name of the operation parameter are defined in the operation information;
  • the sending side function interface fills in the operation information according to the defined common operation interface structure, and generates a message to be sent to the receiving side function interface;
  • the receiving side function interface determines whether the function module is the processing module of the operation, and if yes, performs step (d), otherwise sends to the function interface of the function module that processes the operation, and then performs the step (d);
  • the function interface that receives the packet parses the packet, and determines whether the operation identifier and the name of some or all of the operation parameters have matching items in the configured operation information. If yes, execute the next step, otherwise , returning an error message to the sending side function interface, and ending;
  • the function interface parses the parameter value of the parameter that matches the success, and performs subsequent processing.
  • the foregoing interface implementation method may further have the following features:
  • the function function of the transmitting side in the step (b) is to send a message to another function interface inside the system, or to a function interface sent to another system.
  • the foregoing interface implementation method may further have the following features:
  • the operation parameter list of the general operation interface structure defined in the step (a) further includes a parameter The number type item; the parameter type of the operation parameter is defined in the operation information configured in the system; in the step (d), the function interface determines whether the operation parameter has a matching item in the configured operation information, and is also filled in. Whether the parameter type of the operation parameter is consistent with the configured parameter type. If the parameter name and the parameter type are the same, the two match. Otherwise, they do not match.
  • the foregoing interface implementation method may further have the following features:
  • the defined operation parameter list includes an entry parameter list, an exit parameter list, and a return value parameter list; the operation information configured in the system is also divided into an entry parameter, an exit parameter, and Return value parameters, and define the parameter names and parameter types of each operation parameter included in the three types of parameters.
  • the foregoing interface implementation method may further have the following features:
  • the operation processing information is further configured in the system, including the module name and the operation identifier, and each module may correspond to multiple operations;
  • the receiving side function interface finds the corresponding processing module according to the operation identifier parsed from the message to the configured operation processing information, and then sends the message or performs local processing.
  • the foregoing interface implementation method may further have the following features:
  • the operation operation information is further included in the general operation interface structure defined in the step (a); accordingly, the operation version information is also defined in the operation information configured in the system;
  • step (d) After the function interface of the step (d) parses the operation version information from the message, it also finds whether there is a matching item in the configured operation version information, and if yes, performs step (e), otherwise, an error message is returned. End.
  • the foregoing interface implementation method may further have the following features:
  • the step (a) further configures version compatibility information in the system, and defines a compatibility relationship between the versions;
  • the step (d) is considered to match if the operation version in the message is the same as or compatible with the configured operation version.
  • the foregoing interface implementation method may further have the following features:
  • the step (a) further configures type information in the system, and defines a custom parameter type name supported by the interface language and a corresponding system internal type or internal structure;
  • the step (e) function interface analyzes the custom parameter according to the type information of the configuration.
  • the foregoing interface implementation method may further have the following features:
  • the operation parameter defined by the general operation interface structure defined in the step (a) further includes the type version information; at the same time, the type version information corresponding to the custom parameter type is also defined in the type information also configured in the system;
  • the function interface of the step (d) parses the type version information of the operation parameter from the message, and finds whether the version information of the operation parameter is the same or compatible in the configured type information. If yes, the operation parameter is considered to be Matches the item, otherwise, the action parameter is considered to have no matching item.
  • the foregoing interface implementation method may further have the following features:
  • the system has a functional interface with one or more functional modules responsible for processing, and a functional interface of a functional module responsible for distributing operations, and the function of distributing the first to the receiving system when the system issues an operation between the systems.
  • the functional interface of the module which then determines the processing module of the operation for distribution.
  • the network management system with a universal operation interface includes a storage module and a plurality of functional modules, wherein the functional modules have functional interfaces that can communicate with each other, and the storage module stores the configured operation information.
  • the operation identifier used in the operation interface and the parameter name and parameter type of the operation parameter are defined in the operation information;
  • the message transmitted by the function interface is defined as a general operation interface structure, and the operation information to be filled in the structure includes an operation identifier and an operation parameter, and the parameter is represented in the form of a list, including a parameter name, a parameter type, and a parameter value.
  • the parameter value can adopt any data type;
  • the sending unit is configured to fill in the operation according to the general operation interface structure when transmitting Information, the generated message is sent to the function interface on the receiving side;
  • the receiving unit the processing module for determining the operation, distributing or forwarding the operations processed by the other function modules, parsing the message processed by the function module, determining the operation identifier and the name and type of the at least one operation parameter are configured Whether there is a matching item in the operation information, and if yes, parsing the parameter value of the parameter that matches the success, otherwise returning the error message.
  • the above network management system can also have the following features:
  • the storage module further stores operation processing information, including a module name and an operation identifier, and each module may correspond to multiple operations;
  • the above network management system can also have the following features:
  • the operation parameter adopts a structure of an entry parameter list, an exit parameter list, and a return value parameter list, and at least three fields of a parameter name, a parameter type, and a parameter value are defined in each list;
  • the operation information saved by the storage module is also divided into an entry parameter, an exit parameter, and a return value parameter, and respectively defines a parameter name and a parameter type of each operation parameter included in the three types of parameters.
  • the above network management system can also have the following features:
  • the operation version information is also saved in the storage module
  • the operation interface information is also included in the general operation interface structure defined by the function interface, and the receiving unit of the function interface further parses out the operation version information from the message, and finds whether there is a matching item in the configured operation version information. If so, continue to parse other information, otherwise an error message is returned.
  • the above network management system can also have the following features:
  • the receiving unit of the function interface determines that the operation version in the message is the same as or compatible with the configured operation version, it is considered that the two match.
  • the above network management system can also have the following features:
  • the storage module further stores type information, where the name of the custom parameter type supported by the interface language and the corresponding internal type or internal structure of the system are defined;
  • the receiving unit of the function interface parses the custom parameter in the packet according to the type information of the configuration.
  • the interface is flexible. You can add, modify, or delete interfaces through configuration files. You can increase or decrease the number of parameters on the interface and change the type of parameters through the configuration file.
  • the interface processing is more flexible.
  • the module that processes the interface can be configured to make the application and the interface loosely coupled, which facilitates the upgrade and debugging of the network management system. Drawing fan
  • Figure 1 is a schematic view showing the implementation of the method of the first embodiment of the present invention.
  • the implementation method of the present invention will be further described below with reference to the accompanying drawings and specific embodiments.
  • the implementation of the interface between the internal modules and the interface between the external modules implements two embodiments.
  • the telecommunication management network (TMN) specifies the workstation function (WFS).
  • WFS workstation function
  • the interface between the foreground and operating system functions (OSF), the interface (F), the different telecommunication management networks, or the interface (X) between the non-telecom management network and the operating system function (OSF) can be used.
  • FIG. 1 is a schematic diagram of an implementation of an interface between internal modules of a background system in this embodiment, and related functional modules are also shown.
  • the system includes a plurality of background function modules and a storage module.
  • the background function module only the operation interface portion, that is, the background function interface 1 to the background function interface n are shown.
  • the background system described above may be a back-end system of the telecommunications network management, but is not limited thereto.
  • the background function interface 1 is mainly used for the distribution of operation data, and other background function interfaces can also realize the operation data forwarding between internal modules.
  • the storage module stores the necessary configuration information, including type information, operation information, operation processing information, and version compatibility information.
  • the back-end function module can read the required configuration information from the storage module to complete the analysis of the data.
  • the background function module may also be replaced with a foreground function module, which is applicable to the internal function modules.
  • the method of this embodiment first defines a general interface operation structure to transmit messages and required configuration information, including the following contents:
  • the message transmitted by the function interface is defined as a general operation interface structure according to the specific interface language used, so that it can transmit various operation information.
  • the message between the internal module and the external module is the message with the above-mentioned general operation interface structure, but the same or different interface definition language can be used.
  • the ASN.1 definition can be used between the internal modules, and the external module can use the IDL.
  • the interface definition language can also be in the same language.
  • the operation interface structure definition in this embodiment includes an operation name, an operation version, an entry parameter list, an exit parameter list, and a return value parameter list; each list has the same format, and includes a parameter name, a parameter type, a type version, and a parameter.
  • the value is 4 fields, and the parameter value field can be represented by any type.
  • the configuration information includes operation processing information, operation information, version compatibility information, and type information, and can be saved in a file manner. among them:
  • the configured operational processing information is used to define the operations that the internal modules of the system can handle, including the module name and operation name. Each module can correspond to multiple operations.
  • the configured operation information defines the operation name, operation version, and operation parameters used by the operation interface of the interaction information between the internal modules of the system.
  • the operation parameters are divided into an entry parameter, an exit parameter, and a return value parameter, and parameters of each parameter are defined. Name and parameter type.
  • the compatibility between the operational version and the type version is defined in the configured version compatibility information.
  • the configured type information defines the custom parameter type name supported by the interface language, the corresponding system internal type or internal structure, and the type version.
  • the function interface can further parse the custom parameters according to this configuration. This definition is mainly to avoid parsing errors caused by changes in internal types or internal structure definitions. There is no version incompatibility or type change problem for the types provided by the interface language itself, so no definition is needed.
  • the operation name is used as an operation identifier.
  • the operation identifier can also be replaced with a command code or other flag.
  • the functional interface can be further divided into:
  • a sending unit configured to fill in the operation information according to the general operation interface and the structure, and generate a function interface that is sent to the receiving side;
  • the receiving unit is configured to find a corresponding processing module according to the operation identifier parsed from the message to the configured operation processing information, and then process the packet locally, or distribute or forward the message to the corresponding processing module.
  • parse the message and determine whether the operation identifier, the operation version (optional), and at least one operation parameter have matching items in the configured operation information (the operation version matching refers to the same or compatible, operation)
  • Parameter matching means that the parameter name and parameter type are the same, the type version is the same or compatible. If yes, the parameter value of the matching operation parameter is parsed. Otherwise, the error information is returned to the sending side.
  • the type information can be reported according to the configuration.
  • the custom parameters in the text are parsed.
  • the flow of the operation of the background function interface 1 to the background function interface n is taken as an example, that is, the background function interface 1 is the operation sending side, and the background function interface n is the operation receiving side, to explain the interface dynamic analysis and scheduling in the specific operation process. And processing methods, but other background functions are connected
  • the following process can also be implemented between the ports, and the process includes the following steps:
  • Step 101 The background function interface 1 fills in operation information according to the defined common operation interface structure, including an operation name and an operation version, and an entry parameter list, an exit parameter list, and a return value list, and each list includes a parameter name, a type, a version, and Value 4 items;
  • Step 102 the background function interface 1 finds the corresponding processing module as the background function interface n according to the filled operation name to the configured operation processing information, and sends the data of the operation information to the background function interface n;
  • the transmission can be either a distribution or a forwarding.
  • Step 103 After obtaining the operation data, the background function interface n parses out the operation name and the operation version to find the operation information in the configuration, and if it matches the operation with the same operation name and the same version or compatibility, the next step is performed, otherwise the transmission is performed. The side returns the corresponding error message and ends;
  • the configured version compatibility information it can be determined whether the currently used operation version is compatible with the operation version in the operation information. The same is true for the judgment of the type version below. If the operation name is different or the version is incompatible and forced to resolve, it may cause the system to crash.
  • Step 104 The background function interface II parses the entry parameter, the exit parameter, and the return parameter in the operation information, and performs matching on each parameter obtained according to the configured operation information and type information to determine whether the match name is the same and the type version is the same. Or compatible parameters, if any, go to the next step, otherwise, return the corresponding error message to the sending side, and end;
  • the receiver can only parse the matched parameters and not process the other parameters. It is also possible to require all matches to proceed down, otherwise an error message is returned.
  • Step 105 The background function interface n parses the parameter values with the same name and the same version or compatibility, and performs subsequent processing.
  • the parameter name, the parameter type, the type version, the parameter value, and the like are filled in the packet (such as an ASN packet) according to the general operation interface structure defined by the operator.
  • the application layer analyzes the configuration information locally by the receiver. The message does not parse the incompatible or unrecognized message and returns the corresponding error message.
  • the packet structure of this processing method is flat, the interface changes do not need to be recompiled, the number of parameters can be increased or decreased, and the parameter type is variable. Since the parsing of the entire packet is controlled by the application layer, it does not occur due to The problem of system crash caused by different definitions of the message structure.
  • the parameter types are all types defined by the system, you can also configure the above type information without using the configured operation information to determine whether the operation parameters can be resolved.
  • the operation processing information does not have to be written in a file, and in another embodiment, it can be directly written in the program, and the program judges the branch judgment to determine the distributed module, which is also feasible.
  • the operation version information may also be configured in the operation processing information, so that the distributed function interface first determines whether the operation version in the operation is the same as or compatible with the current configuration. If yes, redistribute, otherwise, the operation error message can be directly returned.
  • the return value parameter is incorporated into the exit parameter, in which case the return value parameter can be omitted.
  • some of the entry parameters and the exit parameters are combined into one class.
  • it is not important to classify the operation parameters as long as the operation parameter names and types used by the operation interface are defined, and correspondingly, in the general operation interface.
  • the structure also does not limit the number and type of parameter lists defined.
  • the above operation version and type version information may not be set.
  • only operations and parameters having the same name and the same version may be parsed, and 'the basic function of the present invention may be implemented.
  • the parameter type may not be added to the list of operating parameters.
  • FIG. 2 is an interface implementation of an external interface between a foreground system and a background system in this embodiment.
  • the structure of the foreground system and the configured information are the same as those of the first embodiment.
  • the back-end system and the foreground system have similar functional structures, including the front-end function interface 1 to the front-end function interface 1, and the front-end function interface is connected to the foreground device of the telecommunication network management system. , is responsible for information interaction with the background function interface, and has an external communication connection between the front function interface 1 and the background function interface 1.
  • the operation sending side and the operation receiving side are the foreground function interface or the background function interface
  • the dynamic analysis, scheduling, and processing methods of the foreground function interface are the same as the background function interface.
  • the following takes the foreground function interface 1 to send the operation to the background as an example, and the specific implementation steps of the method in this embodiment are described with reference to FIG. 2:
  • the front-end function interface 1 fills in the operation information according to the defined common operation interface structure, including the operation name, the operation version, the entry parameter list, the exit parameter list, and the return value list, and then generates a message according to the filled information to the background function interface 1
  • the operation data is sent.
  • the processing after the background function interface 1 receives the operation data is the same as the step 102 105 of the first embodiment, and belongs to the interface implementation between the internal modules, and is not repeated here.
  • the background function interface 1 in Figure 2 may also be the functional interface of the functional module to handle the operation, and thus it is not necessary to distribute it. However, if it is not the function interface of the function module that handles the operation, it needs to be forwarded to the corresponding function interface according to the configured processing module.
  • NE network element
  • GraphicString, GraphicString 5 GeneralizedTime and other types are ASN types. If you want to change the original structure during system upgrade, such as modifying CreateNE-T as follows:
  • operationName is the operation name
  • version is the version
  • inputParam, outputParam, and returnParam are the ingress parameter, the exit parameter, and the return value parameter, respectively.
  • the entry parameters, exit parameters, and return value parameters are all populated in the following list format:
  • ParamList-T SEQUENCE OF Param-T
  • N-T and Error-T are structures defined internally by the system, and the function modules can be parsed.
  • Type information profile definition :
  • the above NE refers to the network element
  • the EMS refers to the network management system, which is only an example.
  • the parameter name, parameter type, type version, parameter value, etc. are filled in the ASN message enemlOperationInterface-T according to the general operation interface structure defined by the operator.
  • the packet is parsed one by one, and the incompatible or unrecognized message is not parsed, and the corresponding error information is returned.
  • the present invention provides a network management system for data interaction in a network such as a Telecommunication Management Network (TMN) and a method for implementing the common interface thereof, including a general structure definition of a data packet and a specific packet information configuration.
  • TTN Telecommunication Management Network
  • the configuration of the function interface module of the system through the general conversion processing process of the message structure, completes the parsing of the message, and can achieve good compatibility, overcomes the lack of common, difficult to expand, interface and application of the existing interface processing technology
  • the shortcoming of coupling is too tight, the interface expansion capability of the network management system is enhanced, and the development and maintenance costs of the network management system can be saved.
  • the general interface processing method and system proposed by the present invention have universality, strong expansion capability, and no dependence on specific technologies, and can well solve the problem of interface expansion.
  • the method and system for implementing the universal interface according to the present invention when the interface needs to be upgraded for some reason, only the configuration information definition (type information, operation information, operation processing information) needs to be modified, and the corresponding foreground or The background function interface module has very good maintainability and can effectively reduce development and maintenance costs.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un système de gestion de réseau pour faire interagir des données dans le réseau de gestion de télécommunications (TMN) ou un autre réseau et le procédé pour réaliser ses interfaces universelles. L'invention comprend une définition de l'architecture universelle pour les messages de données, la configuration des informations de message de données spécifiques et la configuration du module d'interface de fonction du système. En transformant les messages de données en architecture universelle, l'invention pourrait accomplir l'analyse du message de données et réaliser une bonne compatibilité, et donc surmonter l'inconvénient de l'absence d'universalité, la difficulté d'extension et l'inconvénient naissant du fait que le couplage entre les interfaces et l'application est trop compact dans la technologie actuelle de traitement d'interfaces. L'invention pourrait également améliorer la capacité d'extension des interfaces du système de gestion de réseau et réduire les coûts de développement et de maintenance de la gestion de réseau.
PCT/CN2006/002935 2006-11-02 2006-11-02 Procédé et système de réalisation d'interfaces universelles dans le système de gestion de réseau WO2008052389A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2006/002935 WO2008052389A1 (fr) 2006-11-02 2006-11-02 Procédé et système de réalisation d'interfaces universelles dans le système de gestion de réseau
CN2006800562002A CN101529807B (zh) 2006-11-02 2006-11-02 一种网管系统通用的接口实现方法及其系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2006/002935 WO2008052389A1 (fr) 2006-11-02 2006-11-02 Procédé et système de réalisation d'interfaces universelles dans le système de gestion de réseau

Publications (1)

Publication Number Publication Date
WO2008052389A1 true WO2008052389A1 (fr) 2008-05-08

Family

ID=39343787

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/002935 WO2008052389A1 (fr) 2006-11-02 2006-11-02 Procédé et système de réalisation d'interfaces universelles dans le système de gestion de réseau

Country Status (2)

Country Link
CN (1) CN101529807B (fr)
WO (1) WO2008052389A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102651696A (zh) * 2011-02-28 2012-08-29 中兴通讯股份有限公司 一种对多版本共存的网管系统接口进行管理的方法及系统
WO2017000678A1 (fr) * 2015-07-01 2017-01-05 中兴通讯股份有限公司 Procédé et système de communication par paquets entre des systèmes de gestion de réseau
CN110865854A (zh) * 2019-11-11 2020-03-06 科大国创软件股份有限公司 一种支持热部署的接口调用编排方法
CN111078968A (zh) * 2019-12-26 2020-04-28 山东浪潮通软信息科技有限公司 一种可视化配置的跨系统数据交互方法及系统
CN112329415A (zh) * 2020-10-27 2021-02-05 江苏华邦网络科技有限公司 一种基于java web的出入参处理方法及系统
WO2022166718A1 (fr) * 2021-02-04 2022-08-11 大唐移动通信设备有限公司 Procédé et appareil de traitement d'informations, et support de stockage lisible par processeur

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6330574B1 (en) * 1997-08-05 2001-12-11 Fujitsu Limited Compression/decompression of tags in markup documents by creating a tag code/decode table based on the encoding of tags in a DTD included in the documents
CN1549510A (zh) * 2003-05-16 2004-11-24 中国移动通信集团公司 被管系统注册接口代理访问信息的方法
CN1751442A (zh) * 2003-02-14 2006-03-22 捷讯研究有限公司 用于压缩以结构化定义语言表达的无线应用程序的系统和方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6330574B1 (en) * 1997-08-05 2001-12-11 Fujitsu Limited Compression/decompression of tags in markup documents by creating a tag code/decode table based on the encoding of tags in a DTD included in the documents
CN1751442A (zh) * 2003-02-14 2006-03-22 捷讯研究有限公司 用于压缩以结构化定义语言表达的无线应用程序的系统和方法
CN1549510A (zh) * 2003-05-16 2004-11-24 中国移动通信集团公司 被管系统注册接口代理访问信息的方法

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102651696B (zh) * 2011-02-28 2017-03-29 中兴通讯股份有限公司 一种对多版本共存的网管系统接口进行管理的方法及系统
CN102651696A (zh) * 2011-02-28 2012-08-29 中兴通讯股份有限公司 一种对多版本共存的网管系统接口进行管理的方法及系统
WO2017000678A1 (fr) * 2015-07-01 2017-01-05 中兴通讯股份有限公司 Procédé et système de communication par paquets entre des systèmes de gestion de réseau
CN106330519A (zh) * 2015-07-01 2017-01-11 中兴通讯股份有限公司 一种网管系统间报文的通信方法及系统
CN106330519B (zh) * 2015-07-01 2019-12-17 中兴通讯股份有限公司 一种网管系统间报文的通信方法及系统
CN110865854B (zh) * 2019-11-11 2023-03-31 科大国创软件股份有限公司 一种支持热部署的接口调用编排方法
CN110865854A (zh) * 2019-11-11 2020-03-06 科大国创软件股份有限公司 一种支持热部署的接口调用编排方法
CN111078968A (zh) * 2019-12-26 2020-04-28 山东浪潮通软信息科技有限公司 一种可视化配置的跨系统数据交互方法及系统
CN111078968B (zh) * 2019-12-26 2024-03-08 浪潮通用软件有限公司 一种可视化配置的跨系统数据交互方法及系统
CN112329415A (zh) * 2020-10-27 2021-02-05 江苏华邦网络科技有限公司 一种基于java web的出入参处理方法及系统
WO2022166718A1 (fr) * 2021-02-04 2022-08-11 大唐移动通信设备有限公司 Procédé et appareil de traitement d'informations, et support de stockage lisible par processeur
CN114938496A (zh) * 2021-02-04 2022-08-23 大唐移动通信设备有限公司 信息处理的方法、装置及处理器可读存储介质
CN114938496B (zh) * 2021-02-04 2023-03-31 大唐移动通信设备有限公司 信息处理的方法、装置及处理器可读存储介质
US11910206B1 (en) 2021-02-04 2024-02-20 Datang Mobile Communications Equipment Co., Ltd. Information processing method, device and processor-readable storage medium

Also Published As

Publication number Publication date
CN101529807A (zh) 2009-09-09
CN101529807B (zh) 2011-02-02

Similar Documents

Publication Publication Date Title
US20190268225A1 (en) Service distribution method, device and system
CN100499510C (zh) 定位故障的方法以及业务维护平台
US10003405B2 (en) Data over cable service interface specification (DOCSIS) over passive optical network (PON)
CN1968134B (zh) 基于中间件实现多媒体融合业务的方法及系统
US9083648B2 (en) Method and system for performing remote network management on a voice home gateway terminal
CN109840155B (zh) 一种实现远程过程调用的方法及装置
WO2008052389A1 (fr) Procédé et système de réalisation d'interfaces universelles dans le système de gestion de réseau
WO2017162089A1 (fr) Procédé et dispositif de configuration de service pour service de réseau
WO2007059665A1 (fr) Systeme et procede de configuration d'un dispositif de reseau
WO2010127531A1 (fr) Appareil, composant de service web et procédé basé sur un service web
CN100499473C (zh) 实现业务请求的方法以及联机指令系统
CN106487538B (zh) 业务提速方法、策略控制平台以及系统
WO2013170818A2 (fr) Procédé et système de conversion de code d'erreur, serveur pppoe et terminal mobile
JP5717504B2 (ja) ＸＰａｔｈ表現を含むＸＭＬ表現された管理トランザクションを生成するための方法およびデバイス
CN111954100A (zh) 一种接口升级方法、装置以及光网络单元管理方法、装置
CN113285816B (zh) 一种基于键值配置的控制请求发送方法、装置和系统
CN117176633A (zh) 一种总线跨设备通信方法、装置、设备及存储介质
CN101212346A (zh) 一种网元管理系统的软件版本管理方法及装置
WO2012119340A1 (fr) Procédé et appareil permettant d'implémenter une interface nord
CN100452793C (zh) 一种基于软交换网络的业务发放方法
KR20180058458A (ko) Tosca 기반의 정보 모델을 이용하는 가상화 네트워크 기능 관리 방법, 가상 네트워크 기능 관리자, 및 이를 이용한 네트워크 기능 가상화 시스템
CN101753330B (zh) 一种基于vrf接口对设备管理的方法
CN101621528B (zh) 基于以太交换机集群管理的会话系统及会话通道实现方法
CN106789266A (zh) 一种网管设备、网元设备和网管系统
WO2014083561A1 (fr) Nœud de réseau de télécommunication prenant en charge une gestion hybride

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680056200.2

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 06805136

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06805136

Country of ref document: EP

Kind code of ref document: A1