WO2016037540A1 - 基于pb和xpath的网元级网管业务配置适配系统及方法 - Google Patents

基于pb和xpath的网元级网管业务配置适配系统及方法 Download PDF

Info

Publication number
WO2016037540A1
WO2016037540A1 PCT/CN2015/088843 CN2015088843W WO2016037540A1 WO 2016037540 A1 WO2016037540 A1 WO 2016037540A1 CN 2015088843 W CN2015088843 W CN 2015088843W WO 2016037540 A1 WO2016037540 A1 WO 2016037540A1
Authority
WO
WIPO (PCT)
Prior art keywords
protocol
data
node
service configuration
interface
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2015/088843
Other languages
English (en)
French (fr)
Inventor
陈林峰
张利兵
张勇
季小庭
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Fiberhome Telecommunication Technologies Co Ltd
Original Assignee
Fiberhome Telecommunication Technologies Co Ltd
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 Fiberhome Telecommunication Technologies Co Ltd filed Critical Fiberhome Telecommunication Technologies Co Ltd
Publication of WO2016037540A1 publication Critical patent/WO2016037540A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

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 invention relates to the field of computer software programming, in particular to a network element level network management service configuration adaptation system and method based on PB and XPATH.
  • Service configuration is a basic function of network management.
  • the process of the service configuration is as follows: the service content of the user is organized into the binary data blocks required by the device according to the protocol description of the service configuration, and then the data block is sent to the device to complete the IP configuration, the device activation, and the function. Switching, additions and deletions of business content, etc.
  • the protocol description carrier for the business configuration may be a document or a script. If the protocol description carrier of the service configuration is only a document, the network management developer needs to define the corresponding data structure corresponding to the protocol field, and complete the serialization operation of the data structure to the binary data block, and the deserialization of the binary data block to the data structure. operating.
  • protocol description carrier of the service configuration is a script
  • the business configuration function development has a large workload and high maintenance costs.
  • the purpose of the present invention is to overcome the deficiencies of the foregoing background, and provide a network element level network management service configuration adaptation system and method based on PB and XPATH, which can adapt any common protocol script to perform network element level service configuration expansion and reduce
  • the network management service configuration function develops workload, maintains convenience, reduces maintenance costs, and improves network management quality.
  • the invention provides a network element level network management service configuration based on PB and XPATH.
  • the system includes a server, a client, a PB's own serialization interface, a PB's own deserialization interface, a PB application interface, a bus interface, and a network element device.
  • the server includes a PB protocol definition unit and a service configuration protocol script. Adaptation unit and XPATH-based PB lookup unit, where:
  • the PB protocol defining unit is configured to: define a service configuration protocol based on a protocol buffer PB protocol into a general tree structure, and define configuration data corresponding to the service configuration protocol into PB data of a corresponding tree structure; use PB To define the node type of the tree structure, the common attribute of the protocol field; use PB to define the protocol node and the data node; the PB protocol tree structure includes the PB protocol structure and the PB data structure, and the PB protocol structure saves various attributes of the protocol field , only the data is saved in the PB data structure;
  • the service configuration protocol script adaptation unit is configured to adapt the service configuration protocol script to the protocol node: load the service configuration protocol script data, parse the field attribute and the loop level of the service configuration protocol script, and generate the protocol node according to the field attribute and the loop level. : the field attribute in the service configuration protocol script is associated with the protocol node, and the protocol script is converted to the protocol node according to the corresponding relationship; the serialized interface of the PB itself is called to cache the PB protocol;
  • the XPATH-based PB search unit is configured to: find a value of one or a batch of fields according to a specified protocol path or other conditions, and implement a PPATH search based on XPATH: when the search starts, the protocol node hierarchy is decomposed, and the node father and son of the protocol node are established.
  • Relationship establishing a node parent-child relationship of the data node according to the protocol node; establishing a correspondence relationship between the child node of the protocol node and the child node of the data node; establishing a relationship between the attribute and the value between the protocol field and the field of the data node, and finally establishing Query relationship; after the query relationship is established, the query statement is analyzed according to the XPATH syntax; according to the path information in the query statement, the level at which the node is located is located; at the corresponding level, the data node is found according to keywords or other conditions, and the data is found.
  • the serialization interface of the PB itself is used to serialize the data node to the binary: the protocol node corresponds to the service configuration protocol, and when serialized, according to the hierarchy and the order, according to the protocol field The length and type of protocol node, write the field values in the data node to the binary block.
  • the PB's own deserialization interface is used to deserialize the PB binary into a data node: the protocol node corresponds to the service configuration protocol, and when deserializing, according to the hierarchy and the order, according to The length of the protocol field and the type of the protocol node, the data in the binary block is taken out and placed in the data node.
  • the PB application interface is used to:
  • PB data merging When the service configuration has multiple entries, when adding an entry, the data in the two data nodes is merged into one data node according to the keywords described in the protocol;
  • PB data filling The client presents the configuration interface to the user according to the PB protocol, and after the user fills in the data, the application fills the data into the data node according to the protocol node.
  • the common attributes of the protocol field include a field name, a field value, a field type length, and a display manner of the field content on the configuration interface.
  • each node in the PB protocol tree structure includes a list of attributes of the node, the node includes a list of child nodes, and each child node includes a list of attributes and a list of child nodes of the child node.
  • the server adapts the service configuration protocol script to the protocol node to be cached, and the client queries the PB protocol for interface presentation, and the user is in the guest.
  • the service configuration is performed on the configuration interface of the client.
  • the client organizes the configuration data into the data node according to the protocol node, then calls the serialization interface of the PB itself, serializes the data node into PB binary data, and then calls the bus interface to PB binary. The data is sent to the server.
  • the server de-serializes the PB binary data into a data node, and then organizes the data node into binary data required by the network element device according to the protocol node, and sends the data to the network. Meta device.
  • the server parses the binary data required by the network element device according to the protocol node, organizes it into a data node, and then calls the serialization of the PB itself.
  • the interface serializes the data node into PB binary data, and then returns the PB binary data to the client through the bus interface; the client then deserializes the data node, and presents the data to the configuration interface according to the protocol node.
  • the present invention further provides a PB and XPATH-based network element level network management service configuration adaptation method, which includes the following steps:
  • the service configuration protocol is defined as a general tree structure based on the PB protocol, and the configuration data corresponding to the service configuration protocol is defined as the PB data of the corresponding tree structure; the node type and protocol of the tree structure are defined by using the PB.
  • Common attributes of the field use PB to define protocol nodes and data nodes;
  • PB protocol tree structure includes PB protocol structure and PB data structure, PB protocol structure saves various attributes of protocol fields, and only data is saved in PB data structure;
  • the service configuration protocol script is converted into a PB protocol structure and cached;
  • Step 101 Load service configuration protocol script data.
  • Step 102 Parse a field attribute and a loop level of the service configuration protocol script.
  • Step 103 Generate a protocol node according to the field attribute and the loop hierarchy: configure the service
  • the field attribute in the protocol script is associated with the protocol node, and the protocol script is converted to the protocol node according to the corresponding relationship;
  • Step 104 Calling the serialized interface of the PB itself to cache the PB protocol;
  • the device When the service is configured, the device is configured to deliver the binary data required by the device according to the PB protocol and the PB data.
  • the binary data When the device is configured, the binary data is parsed into PB data according to the PB protocol, and the syntax of the XPATH is used according to the PB.
  • the protocol searches the PB data to implement a PB lookup based on XPATH;
  • the XPATH-based PB lookup process is as follows:
  • Step 201 When the search starts, the protocol node hierarchy is decomposed, and the node parent-child relationship of the protocol node is established;
  • Step 202 Establish a node parent-child relationship of the data node according to the protocol node.
  • Step 203 Establish a correspondence between a child node of the protocol node and a child node of the data node.
  • Step 204 Establish a relationship between an attribute and a value between a protocol field and a field of the data node, and finally establish a query relationship.
  • Step 205 After the query relationship is established, parse the query according to the XPATH syntax.
  • Step 206 According to the path information in the query statement, locate the level at which the node is located;
  • Step 207 At a corresponding level, find a data node according to a keyword or other condition, and find data;
  • the server adapts the service configuration protocol script to the protocol node for caching, and the client queries the PB protocol for interface presentation.
  • the user configures the service on the client's configuration interface, and the client organizes the configuration data into the data node according to the protocol node.
  • Call PB's own serialization interface serialize the data node into PB binary data, and then call the bus The interface sends the PB binary data to the server.
  • the server After receiving the PB binary data, the server de-serializes the PB binary data into a data node, and then distributes the data node to the network element device according to the binary data required by the network element device.
  • the server parses the binary data required by the network element device according to the protocol node, organizes it into a data node, and then calls the serialized interface of the PB itself to serialize the data node into a PB binary. Data, and then return the PB binary data to the client through the bus interface;
  • the client then deserializes the data node and presents the data to the configuration interface according to the protocol node.
  • the present invention uses a new way to unify the existing various service configuration methods for processing, and the application mode of the client is unified, and only the user data is processed according to the Proto_Node (protocol node) to the Data_Node (data node).
  • the padding can be adapted to any common protocol script to extend the network-level service configuration, reducing the workload of network management service configuration function development.
  • the client and the server of the present invention interact with the PB data, and after the serialization of the PB itself (the process of compression), the amount of interaction data is reduced; the process of data serialization and deserialization is universal.
  • a set of code, easy to maintain, can effectively reduce maintenance costs and improve the quality of network management.
  • FIG. 1 is a schematic diagram of a tree structure of a PB protocol in an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of a PB structure without a cyclic protocol in an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a PB structure of a re-circulation protocol according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a PB structure of a parallel loop protocol in an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a PB structure of a two-cycle protocol in an embodiment of the present invention.
  • FIG. 6 is a flowchart of an adaptation service configuration protocol script according to an embodiment of the present invention.
  • FIG. 7 is a flowchart of a PB search based on XPATH according to an embodiment of the present invention.
  • FIG. 8 is a flowchart of a service configuration delivery according to an embodiment of the present invention.
  • the embodiment of the invention provides a network element level network management service configuration adaptation system based on PB and XPATH, including a server end, a client end, a serialization interface of the PB itself, a reverse serialization interface of the PB itself, a PB application interface, and a bus interface.
  • the server includes a PB protocol definition unit, a service configuration protocol script adaptation unit, and an XPATH-based PB search unit.
  • the PB protocol definition unit is configured to: define a service configuration protocol based on a PB (Protocol Buffer) protocol into a general tree structure, and define configuration data corresponding to the service configuration protocol into a corresponding tree structure PB data. .
  • PB Protocol Buffer
  • PB is a lightweight and efficient structured data storage exchange format of Google. It is language-independent and platform-independent. It can be used for structured data serialization. It is suitable for data storage or RPC (Remote Procedure Call Protocol). Call protocol) data exchange format.
  • the PB protocol tree structure includes a PB protocol structure and a PB data structure.
  • the PB protocol structure stores various attributes of the protocol field, and only the data is saved in the PB data structure.
  • Each node in the PB protocol tree structure may contain a list of attributes of the node, and the node may further include a list of child nodes, each of which contains a list of attributes and a list of child nodes of the child node.
  • the PB structure without loop protocol is shown in Figure 2, a recirculating protocol See Figure 3 for the PB structure. See Figure 4 for the PB structure of the parallel loop protocol. See Figure 5 for the PB structure of the double-loop protocol.
  • the ellipse in Figure 2-5 represents the node, and the rectangle represents the field or field value. Multi-cycle protocols can be obtained by combining the above structures.
  • Binary data corresponds to multiple fields, multiple entries, multiple levels (the entries contain entries), and each field, entry, and hierarchy has its own data attributes and display attributes.
  • Data attributes include length, type, value range, etc.
  • Display attributes include whether to display, display style, display order, etc. Different service configurations correspond to different field structures.
  • the service configuration protocol is provided in the form of a script.
  • the format of the script is not fixed. It only needs to be able to describe the basic information of the protocol field.
  • the service configuration protocol script adaptation unit converts the service configuration protocol script into a PB protocol structure and caches it.
  • the service configuration protocol script adaptation unit is configured to: adapt the service configuration protocol script to the protocol node.
  • Step 101 Load service configuration protocol script data.
  • Step 102 Parse field attributes and loop levels of the service configuration protocol script.
  • Step 103 Generate a protocol node according to the field attribute and the loop hierarchy: associate a field attribute in the service configuration protocol script with the protocol node, and convert the protocol script to the protocol node according to the correspondence relationship;
  • Step 104 Call the PB's own serialization interface to cache the PB protocol.
  • the device When the service is configured, the device is configured to deliver the binary data required by the device according to the PB protocol and the PB data.
  • the binary data is parsed into PB data according to the PB protocol, and the syntax of the XPATH is used according to the PB protocol.
  • PB data is searched.
  • the XPATH-based PB lookup unit is used to: according to the specified protocol path or other Find the value of one or a batch of fields and implement a PB lookup based on XPATH.
  • Step 201 When the search starts, the protocol node hierarchy is decomposed, and the node parent-child relationship of the protocol node is established;
  • Step 202 Establish a node parent-child relationship of the data node according to the protocol node.
  • Step 203 Establish a correspondence between a child node of the protocol node and a child node of the data node.
  • Step 204 Establish a relationship between an attribute and a value between a protocol field and a field of the data node, and finally establish a query relationship.
  • Step 205 After the query relationship is established, parse the query according to the XPATH syntax.
  • Step 206 According to the path information in the query statement, locate the level at which the node is located;
  • Step 207 At a corresponding level, find a data node according to a keyword or other condition to find out the data.
  • XPATH XML Path Language
  • XML Extensible Markup Language
  • PB's own serialization interface is used to serialize the data node to binary: the protocol node corresponds to the service configuration protocol.
  • the protocol node corresponds to the service configuration protocol.
  • the data node The field values in are written to the binary block.
  • PB's own deserialization interface is used to deserialize PB binary into data nodes:
  • the protocol node corresponds to the service configuration protocol.
  • the data in the binary block is taken out into the data node.
  • PB application interface for:
  • PB data merging When a service configuration has multiple entries, when adding an entry, the data in the two data nodes is merged into one data node according to the keywords described in the protocol.
  • PB data filling The client presents the configuration interface to the user according to the PB protocol, and after the user fills in the data, the application fills the data into the data node according to the protocol node.
  • the service configuration is as follows:
  • the server adapts the service configuration protocol script to the protocol node for caching, and the client queries the PB protocol for interface presentation.
  • the user configures the service on the client's configuration interface, and the client organizes the configuration data into the data node according to the protocol node.
  • the PB's own serialization interface is called, the data node is serialized into PB binary data, and then the bus interface is called, and the PB binary data is sent to the server.
  • the server de-serializes the PB binary data into a data node, and then distributes the data node to the network element device according to the binary data required by the network element device.
  • the server parses the binary data required by the network element device according to the protocol node, organizes it into a data node, and then calls the serialized interface of the PB itself to serialize the data node into a PB binary.
  • the data is then returned to the client via the bus interface.
  • the client deserializes the data node, according to The protocol node presents the data to the configuration interface.
  • the embodiment of the present invention further provides a PB and XPATH-based network element level network management service configuration adaptation method, which includes the following steps:
  • the service configuration protocol is defined as a general tree structure based on the PB protocol, and the configuration data corresponding to the service configuration protocol is defined as the PB data of the corresponding tree structure.
  • Use PB to define the node type of the tree structure, the common attributes of the protocol field (such as the field name, field value, field type length, display of the field content on the configuration interface, etc.); use PB to define the protocol node and data node.
  • the PB protocol structure saves various attributes of the protocol field, and only the data is saved in the PB data structure.
  • Each node in the PB protocol tree structure may contain a list of attributes of the node, which in turn may contain a list of child nodes, which in turn may contain its own list of attributes and a list of child nodes.
  • See Figure 2 for the PB structure without loop protocol.
  • See Figure 3 for the PB structure of a re-circulating protocol.
  • See Figure 4 for the PB structure of the parallel loop protocol.
  • See Figure 5 for the PB structure of the double-loop protocol.
  • the ellipse represents a node, and the rectangle represents a field or a field value. Multi-cycle protocols can be obtained by combining the above structures.
  • Binary data corresponds to multiple fields, multiple entries, multiple levels (the entries contain entries), and each field, entry, and hierarchy has its own data attributes and display attributes.
  • Data attributes include length, type, value range, etc.
  • Display attributes include whether to display, display style, display order, etc. Different service configurations correspond to different field structures.
  • the service configuration protocol is provided in the form of a script.
  • the format of the script is not fixed. It only needs to be able to describe the basic information of the protocol field and convert the service configuration protocol script into a PB protocol structure.
  • Step 101 Load service configuration protocol script data.
  • Step 102 Parse field attributes and loop levels of the service configuration protocol script.
  • Step 103 Generate a protocol node according to the field attribute and the loop hierarchy: associate a field attribute in the service configuration protocol script with the protocol node, and convert the protocol script to the protocol node according to the correspondence relationship;
  • Step 104 Call the PB's own serialization interface to cache the PB protocol.
  • the device When the service is configured, the device is configured to deliver the binary data required by the device according to the PB protocol and the PB data.
  • the binary data When the device is configured, the binary data is parsed into PB data according to the PB protocol, and the syntax of the XPATH is used according to the PB.
  • the protocol searches for PB data and implements PB lookup based on XPATH.
  • Step 201 When the search starts, the protocol node hierarchy is decomposed, and the node parent-child relationship of the protocol node is established;
  • Step 202 Establish a node parent-child relationship of the data node according to the protocol node.
  • Step 203 Establish a correspondence between a child node of the protocol node and a child node of the data node.
  • Step 204 Establish a relationship between an attribute and a value between a protocol field and a field of the data node, and finally establish a query relationship.
  • Step 205 After the query relationship is established, parse the query according to the XPATH syntax.
  • Step 206 According to the path information in the query statement, locate the level at which the node is located;
  • Step 207 At a corresponding level, find a data node according to a keyword or other condition to find out the data.
  • the server adapts the service configuration protocol script to the protocol node cache, and the client checks The PB protocol is used to present the interface.
  • the user configures the service on the client's configuration interface.
  • the client organizes the configuration data into the data node according to the protocol node, and then calls the PB's own serialization interface to serialize the data node into PB binary data. Then, the bus interface is called, and the PB binary data is sent to the server.
  • the server de-serializes the PB binary data into a data node, and then distributes the data node to the network element device according to the binary data required by the network element device.
  • the server parses the binary data required by the network element device according to the protocol node, organizes it into a data node, and then calls the serialized interface of the PB itself to serialize the data node into a PB binary.
  • the data is then returned to the client via the bus interface.
  • the client deserializes the data node and presents the data to the configuration interface according to the protocol node.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

本发明公开了一种基于PB和XPATH的网元级网管业务配置适配系统及方法，涉及计算机软件编程领域，该系统包括服务端、客户端、PB自身的序列化接口、PB自身的反序列化接口、PB应用接口、总线接口和网元设备，服务端包括PB协议定义单元、业务配置协议脚本适配单元和基于XPATH的PB查找单元，PB协议定义单元将业务配置协议基于PB协议定义成通用的树形结构，并将与业务配置协议对应的配置数据定义成对应的树形结构的PB数据；业务配置协议脚本适配单元将业务配置协议脚本适配到协议节点。本发明能适配任何通用协议脚本进行网元级业务配置的扩展，减少网管业务配置功能开发的工作量，维护方便，降低维护成本，提高网管质量。

Description

基于PB和XPATH的网元级网管业务配置适配系统及方法 技术领域
本发明涉及计算机软件编程领域，具体是涉及一种基于PB和XPATH的网元级网管业务配置适配系统及方法。
背景技术
业务配置是网管的一项基本功能。业务配置的过程是：根据业务配置的协议描述，将用户填写的业务内容组织成设备需要的二进制数据块，再将此数据块下发给设备，以完成IP的配置、设备的开通、功能的切换、业务内容的增删改等。业务配置的协议描述载体可能是文档，也可能是脚本。如果业务配置的协议描述载体仅仅是文档，则网管开发者需要定义相应的数据结构与协议字段对应，并完成数据结构到二进制数据块的序列化操作，以及二进制数据块到数据结构的反序列化操作。如果业务配置的协议描述载体是脚本，则会有根据脚本进行的比较通用的序列化及反序列化操作，但是脚本的结构形式也是多种多样的，各种脚本的处理方式也是不同的，网管业务配置功能开发的工作量很大，维护成本很高。
发明内容
本发明的目的是为了克服上述背景技术的不足，提供一种基于PB和XPATH的网元级网管业务配置适配系统及方法，能适配任何通用协议脚本进行网元级业务配置的扩展，减少网管业务配置功能开发的工作量，维护方便，降低维护成本，提高网管质量。
本发明提供一种基于PB和XPATH的网元级网管业务配置适 配系统，包括服务端、客户端、PB自身的序列化接口、PB自身的反序列化接口、PB应用接口、总线接口和网元设备，所述服务端包括PB协议定义单元、业务配置协议脚本适配单元和基于XPATH的PB查找单元，其中：
所述PB协议定义单元用于：将业务配置协议基于协议缓冲器PB协议定义成通用的树形结构，并将与业务配置协议对应的配置数据定义成对应的树形结构的PB数据；使用PB来定义树形结构的节点类型、协议字段的公共属性；使用PB来定义协议节点、数据节点；PB协议树形结构包括PB协议结构和PB数据结构，PB协议结构中保存协议字段的各种属性，PB数据结构中只保存数据；
所述业务配置协议脚本适配单元用于将业务配置协议脚本适配到协议节点：加载业务配置协议脚本数据，解析业务配置协议脚本的字段属性和循环层次，根据字段属性和循环层次生成协议节点：将业务配置协议脚本中的字段属性与协议节点建立对应关系，根据对应关系将协议脚本转换到协议节点；调用PB自身的序列化接口缓存PB协议；
所述基于XPATH的PB查找单元用于：根据指定协议路径或其他条件查找一个或一批字段的值，实现基于XPATH的PB查找：查找开始时，分解协议节点层次结构，建立协议节点的节点父子关系；根据协议节点建立数据节点的节点父子关系；建立协议节点的子节点与数据节点的子节点之间的对应关系；建立协议字段与数据节点的字段之间的属性与值的关系，最终建立查询关系；查询关系建立完成后，根据XPATH语法分析查询语句；根据查询语句中的路径信息，定位到节点所在的层次；在相应的层次，根据关键字或其他条件找到数据节点，查出数据。
在上述技术方案的基础上，所述PB自身的序列化接口用于将数据节点序列化到二进制：协议节点与业务配置协议是对应的，序列化的时候，根据层次和顺序，按照协议字段的长度及协议节点的类型，将数据节点中的字段值写入到二进制块中。
在上述技术方案的基础上，所述PB自身的反序列化接口用于将PB二进制反序列化成数据节点：协议节点与业务配置协议是对应的，反序列化的时候，根据层次和顺序，按照协议字段的长度及协议节点的类型，将二进制块中的数据取出放到数据节点中。
在上述技术方案的基础上，所述PB应用接口用于：
(1)PB数据合并：当业务配置有多个条目，在增加条目的时候，根据协议中描述的关键字，将两个数据节点中的数据合并到一个数据节点中；
(2)PB数据删除：当业务配置有多个条目，在减少条目的时候，根据协议中描述的关键字，将数据节点中对应的条目删掉；
(3)PB数据修改：根据字段名及路径查找到字段值所在的位置对应的数据节点，修改其中的数据；
(4)PB数据填充：客户端根据PB协议将配置界面呈现给用户，用户将数据填好后，应用将数据根据协议节点填充到数据节点中。
在上述技术方案的基础上，所述协议字段的公共属性包括字段名、字段值、字段类型长度、字段内容在配置界面上的显示方式。
在上述技术方案的基础上，所述PB协议树形结构中的每个节点包含该节点的属性列表，节点包含子节点列表，每个子节点包含该子节点的属性列表和子节点列表。
在上述技术方案的基础上，所述服务端将业务配置协议脚本适配到协议节点缓存起来，客户端查询PB协议进行界面呈现，用户在客 户端的配置界面上进行业务配置，客户端将配置数据按照协议节点组织到数据节点中，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后调用总线接口，将PB二进制数据下发给服务端。
在上述技术方案的基础上，所述服务端接收到PB二进制数据后，将PB二进制数据反序列化成数据节点，再将数据节点按照协议节点组织成网元设备需要的二进制数据，下发给网元设备。
在上述技术方案的基础上，所述网元设备返回业务配置接口给服务端后，服务端按照协议节点将网元设备需要的二进制数据解析出来，组织成数据节点，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后通过总线接口将PB二进制数据返回给客户端；客户端再反序列化出数据节点，按照协议节点将数据呈现到配置界面上。
本发明还提供一种适用于上述系统的基于PB和XPATH的网元级网管业务配置适配方法，包括以下步骤：
A、将业务配置协议基于PB协议定义成通用的树形结构，并将与业务配置协议对应的配置数据定义成对应的树形结构的PB数据；使用PB来定义树形结构的节点类型、协议字段的公共属性；使用PB来定义协议节点、数据节点；PB协议树形结构包括PB协议结构和PB数据结构，PB协议结构中保存协议字段的各种属性，PB数据结构中只保存数据；将业务配置协议脚本转换为PB协议结构缓存起来；
适配业务配置协议脚本的流程如下：
步骤101、加载业务配置协议脚本数据；
步骤102、解析业务配置协议脚本的字段属性和循环层次；
步骤103、根据字段属性和循环层次生成协议节点：将业务配置 协议脚本中的字段属性与协议节点建立对应关系，根据对应关系将协议脚本转换到协议节点；
步骤104、调用PB自身的序列化接口缓存PB协议；
B、进行业务配置的时候，根据PB协议和PB数据组织成设备需要的二进制数据下发设备，读设备配置的时候，根据PB协议将二进制数据解析成PB数据，以XPATH的语法方式，根据PB协议对PB数据进行查找，实现基于XPATH的PB查找；
基于XPATH的PB查找流程如下：
步骤201、查找开始时，分解协议节点层次结构，建立协议节点的节点父子关系；
步骤202、根据协议节点建立数据节点的节点父子关系；
步骤203、建立协议节点的子节点与数据节点的子节点之间的对应关系；
步骤204、建立协议字段与数据节点的字段之间的属性与值的关系，最终建立查询关系；
步骤205、查询关系建立完成后，根据XPATH语法分析查询语句；
步骤206、根据查询语句中的路径信息，定位到节点所在的层次；
步骤207、在相应的层次，根据关键字或其他条件找到数据节点，查出数据；
C、业务配置的下发流程如下：
服务端将业务配置协议脚本适配到协议节点缓存起来，客户端查询PB协议进行界面呈现，用户在客户端的配置界面上进行业务配置，客户端将配置数据按照协议节点组织到数据节点中，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后调用总线 接口，将PB二进制数据下发给服务端；
服务端接收到PB二进制数据后，将PB二进制数据反序列化成数据节点，再将数据节点按照协议节点组织成网元设备需要的二进制数据，下发给网元设备；
网元设备返回业务配置接口给服务端后，服务端按照协议节点将网元设备需要的二进制数据解析出来，组织成数据节点，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后通过总线接口将PB二进制数据返回给客户端；
客户端再反序列化出数据节点，按照协议节点将数据呈现到配置界面上。
与现有技术相比，本发明的优点如下：
(1)本发明使用一种新的方式将现存的各种各样的业务配置方式统一起来进行处理，客户端的应用方式统一，只需根据Proto_Node(协议节点)处理用户数据到Data_Node(数据节点)的填充，能适配任何通用协议脚本进行网元级业务配置的扩展，减少网管业务配置功能开发的工作量。
(2)本发明的客户端与服务端交互的是PB数据，又经过了PB自身的序列化(有压缩的过程)，交互的数据量减少；数据序列化和反序列化的过程是通用的一套代码，维护方便，能够有效降低维护成本，提高网管质量。
附图说明
图1是本发明实施例中PB协议的树形结构示意图。
图2是本发明实施例中无循环协议的PB结构示意图。
图3是本发明实施例中一重循环协议的PB结构示意图。
图4是本发明实施例中并列循环协议的PB结构示意图。
图5是本发明实施例中两重循环协议的PB结构示意图。
图6为本发明实施例中适配业务配置协议脚本的流程图。
图7为本发明实施例中基于XPATH的PB查找的流程图。
图8为本发明实施例中业务配置下发的流程图。
具体实施方式
下面结合附图及具体实施例对本发明作进一步的详细描述。
本发明实施例提供一种基于PB和XPATH的网元级网管业务配置适配系统，包括服务端、客户端、PB自身的序列化接口、PB自身的反序列化接口、PB应用接口、总线接口和网元设备，服务端包括PB协议定义单元、业务配置协议脚本适配单元和基于XPATH的PB查找单元。
PB协议定义单元用于：将业务配置协议基于PB(Protocol Buffer，协议缓冲器)协议定义成通用的树形结构，并将与业务配置协议对应的配置数据定义成对应的树形结构的PB数据。使用PB来定义树形结构的节点类型、协议字段的公共属性(如字段名、字段值、字段类型长度、字段内容在配置界面上的显示方式等)；使用PB来定义协议节点、数据节点。PB是Google的一种轻便高效的结构化数据存储交换格式，它独立于语言，独立于平台，可以用于结构化数据串行化，很适合做数据存储或RPC(Remote Procedure Call Protocol，远程过程调用协议)数据交换格式。
参见图1所示，PB协议树形结构包括PB协议结构和PB数据结构，PB协议结构中保存协议字段的各种属性，PB数据结构中只保存数据。PB协议树形结构中的每个节点可以包含该节点的属性列表，节点又可以包含子节点列表，每个子节点包含该子节点的属性列表和子节点列表。无循环协议的PB结构参见图2所示，一重循环协议的 PB结构参见图3所示，并列循环协议的PB结构参见图4所示，两重循环协议的PB结构参见图5所示，图2～5中椭圆代表节点，矩形代表字段或字段值。多重循环的协议按照以上结构组合即可得到。
业务配置需要与二进制的数据打交道，二进制的数据对应多个字段、多个条目、多个层次(条目中又包含了条目)，每个字段、条目、层次都有自己的数据属性和显示属性，数据属性包括长度、类型、值范围等，显示属性包括是否显示、显示样式、显示顺序等，不同的业务配置对应不同的字段结构。
业务配置协议以脚本的方式提供，脚本的格式不是固定的，只需能够描述协议字段的基本信息，业务配置协议脚本适配单元将业务配置协议脚本转换为PB协议结构缓存起来。
业务配置协议脚本适配单元用于：将业务配置协议脚本适配到协议节点。
参见图6所示，适配业务配置协议脚本的流程如下：
步骤101、加载业务配置协议脚本数据；
步骤102、解析业务配置协议脚本的字段属性和循环层次，
步骤103、根据字段属性和循环层次生成协议节点：将业务配置协议脚本中的字段属性与协议节点建立对应关系，根据对应关系将协议脚本转换到协议节点；
步骤104、调用PB自身的序列化接口缓存PB协议。
进行业务配置的时候，根据PB协议和PB数据组织成设备需要的二进制数据下发设备，读设备配置的时候，根据PB协议将二进制数据解析成PB数据，以XPATH的语法方式，根据PB协议对PB数据进行查找。
基于XPATH的PB查找单元用于：根据指定协议路径或其他条 件查找一个或一批字段的值，实现基于XPATH的PB查找。
参见图7所示，基于XPATH的PB查找流程如下：
步骤201、查找开始时，分解协议节点层次结构，建立协议节点的节点父子关系；
步骤202、根据协议节点建立数据节点的节点父子关系；
步骤203、建立协议节点的子节点与数据节点的子节点之间的对应关系；
步骤204、建立协议字段与数据节点的字段之间的属性与值的关系，最终建立查询关系；
步骤205、查询关系建立完成后，根据XPATH语法分析查询语句；
步骤206、根据查询语句中的路径信息，定位到节点所在的层次；
步骤207、在相应的层次，根据关键字或其他条件找到数据节点，查出数据。
用PB树形结构描述业务配置协议后，协议节点/协议字段/数据节点的层次顺序与XML路径类似，PB结构的节点/属性/值与XML的节点/属性/值也类似。XPATH(XML路径语言)是一种用来确定XML(Extensible Markup Language，可扩展标记语言)文档中某部分位置的语言。XPATH基于XML的树状结构，提供在数据结构树中找寻节点的能力。
PB自身的序列化接口用于将数据节点序列化到二进制：协议节点与业务配置协议是对应的，序列化的时候，根据层次和顺序，按照协议字段的长度及协议节点的类型，将数据节点中的字段值写入到二进制块中。
PB自身的反序列化接口用于将PB二进制反序列化成数据节点： 协议节点与业务配置协议是对应的，反序列化的时候，根据层次和顺序，按照协议字段的长度及协议节点的类型，将二进制块中的数据取出放到数据节点中。
PB应用接口，用于：
(1)PB数据合并：当业务配置有多个条目，在增加条目的时候，根据协议中描述的关键字，将两个数据节点中的数据合并到一个数据节点中。
(2)PB数据删除：当业务配置有多个条目，在减少条目的时候，根据协议中描述的关键字，将数据节点中对应的条目删掉。
(3)PB数据修改：根据字段名及路径查找到字段值所在的位置对应的数据节点，修改其中的数据。
(4)PB数据填充：客户端根据PB协议将配置界面呈现给用户，用户将数据填好后，应用将数据根据协议节点填充到数据节点中。
参见图8所示，业务配置的下发流程如下：
服务端将业务配置协议脚本适配到协议节点缓存起来，客户端查询PB协议进行界面呈现，用户在客户端的配置界面上进行业务配置，客户端将配置数据按照协议节点组织到数据节点中，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后调用总线接口，将PB二进制数据下发给服务端。服务端接收到PB二进制数据后，将PB二进制数据反序列化成数据节点，再将数据节点按照协议节点组织成网元设备需要的二进制数据，下发给网元设备。网元设备返回业务配置接口给服务端后，服务端按照协议节点将网元设备需要的二进制数据解析出来，组织成数据节点，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后通过总线接口将PB二进制数据返回给客户端。客户端再反序列化出数据节点，按照 协议节点将数据呈现到配置界面上。
本发明实施例还提供一种适用于上述系统的基于PB和XPATH的网元级网管业务配置适配方法，包括以下步骤：
A、将业务配置协议基于PB协议定义成通用的树形结构，并将与业务配置协议对应的配置数据定义成对应的树形结构的PB数据。使用PB来定义树形结构的节点类型、协议字段的公共属性(如字段名、字段值、字段类型长度、字段内容在配置界面上的显示方式等)；使用PB来定义协议节点、数据节点。
参见图1所示，PB协议结构中保存协议字段的各种属性，PB数据结构中只保存数据。PB协议树形结构中的每个节点可以包含该节点的属性列表，节点又可以包含子节点列表，子节点又可以包含它自己的属性列表和子节点列表。无循环协议的PB结构参见图2所示，一重循环协议的PB结构参见图3所示，并列循环协议的PB结构参见图4所示，两重循环协议的PB结构参见图5所示，图2～5中椭圆代表节点，矩形代表字段或字段值。多重循环的协议按照以上结构组合即可得到。
业务配置需要与二进制的数据打交道，二进制的数据对应多个字段、多个条目、多个层次(条目中又包含了条目)，每个字段、条目、层次都有自己的数据属性和显示属性，数据属性包括长度、类型、值范围等，显示属性包括是否显示、显示样式、显示顺序等，不同的业务配置对应不同的字段结构。
业务配置协议以脚本的方式提供，脚本的格式不是固定的，只需能够描述协议字段的基本信息，将业务配置协议脚本转换为PB协议结构缓存起来。
参见图6所示，适配业务配置协议脚本的流程如下：
步骤101、加载业务配置协议脚本数据；
步骤102、解析业务配置协议脚本的字段属性和循环层次，
步骤103、根据字段属性和循环层次生成协议节点：将业务配置协议脚本中的字段属性与协议节点建立对应关系，根据对应关系将协议脚本转换到协议节点；
步骤104、调用PB自身的序列化接口缓存PB协议。
B、进行业务配置的时候，根据PB协议和PB数据组织成设备需要的二进制数据下发设备，读设备配置的时候，根据PB协议将二进制数据解析成PB数据，以XPATH的语法方式，根据PB协议对PB数据进行查找，实现基于XPATH的PB查找。
参见图7所示，基于XPATH的PB查找流程如下：
步骤201、查找开始时，分解协议节点层次结构，建立协议节点的节点父子关系；
步骤202、根据协议节点建立数据节点的节点父子关系；
步骤203、建立协议节点的子节点与数据节点的子节点之间的对应关系；
步骤204、建立协议字段与数据节点的字段之间的属性与值的关系，最终建立查询关系；
步骤205、查询关系建立完成后，根据XPATH语法分析查询语句；
步骤206、根据查询语句中的路径信息，定位到节点所在的层次；
步骤207、在相应的层次，根据关键字或其他条件找到数据节点，查出数据。
C、参见图8所示，业务配置的下发流程如下：
服务端将业务配置协议脚本适配到协议节点缓存起来，客户端查 询PB协议进行界面呈现，用户在客户端的配置界面上进行业务配置，客户端将配置数据按照协议节点组织到数据节点中，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后调用总线接口，将PB二进制数据下发给服务端。服务端接收到PB二进制数据后，将PB二进制数据反序列化成数据节点，再将数据节点按照协议节点组织成网元设备需要的二进制数据，下发给网元设备。网元设备返回业务配置接口给服务端后，服务端按照协议节点将网元设备需要的二进制数据解析出来，组织成数据节点，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后通过总线接口将PB二进制数据返回给客户端。客户端再反序列化出数据节点，按照协议节点将数据呈现到配置界面上。
本领域的技术人员可以对本发明实施例进行各种修改和变型，倘若这些修改和变型在本发明权利要求及其等同技术的范围之内，则这些修改和变型也在本发明的保护范围之内。
说明书中未详细描述的内容为本领域技术人员公知的现有技术。

Claims (10)

  1. 一种基于PB和XPATH的网元级网管业务配置适配系统，包括服务端、客户端、PB自身的序列化接口、PB自身的反序列化接口、PB应用接口、总线接口和网元设备，其特征在于：所述服务端包括PB协议定义单元、业务配置协议脚本适配单元和基于XPATH的PB查找单元，其中：
    所述PB协议定义单元用于：将业务配置协议基于协议缓冲器PB协议定义成通用的树形结构，并将与业务配置协议对应的配置数据定义成对应的树形结构的PB数据；使用PB来定义树形结构的节点类型、协议字段的公共属性；使用PB来定义协议节点、数据节点；PB协议树形结构包括PB协议结构和PB数据结构，PB协议结构中保存协议字段的各种属性，PB数据结构中只保存数据；
    所述业务配置协议脚本适配单元用于将业务配置协议脚本适配到协议节点：加载业务配置协议脚本数据，解析业务配置协议脚本的字段属性和循环层次，根据字段属性和循环层次生成协议节点：将业务配置协议脚本中的字段属性与协议节点建立对应关系，根据对应关系将协议脚本转换到协议节点；调用PB自身的序列化接口缓存PB协议；
    所述基于XPATH的PB查找单元用于：根据指定协议路径或其他条件查找一个或一批字段的值，实现基于XPATH的PB查找：查找开始时，分解协议节点层次结构，建立协议节点的节点父子关系；根据协议节点建立数据节点的节点父子关系；建立协议节点的子节点与数据节点的子节点之间的对应关系；建立协议字段与数据节点的字段之间的属性与值的关系，最终建立查询关系；查询关系建立完成后，根据XPATH语法分析查询语句；根据查询语句中的路径信息，定位 到节点所在的层次；在相应的层次，根据关键字或其他条件找到数据节点，查出数据。
  2. 如权利要求1所述的基于PB和XPATH的网元级网管业务配置适配系统，其特征在于：所述PB自身的序列化接口用于将数据节点序列化到二进制：协议节点与业务配置协议是对应的，序列化的时候，根据层次和顺序，按照协议字段的长度及协议节点的类型，将数据节点中的字段值写入到二进制块中。
  3. 如权利要求1所述的基于PB和XPATH的网元级网管业务配置适配系统，其特征在于：所述PB自身的反序列化接口用于将PB二进制反序列化成数据节点：协议节点与业务配置协议是对应的，反序列化的时候，根据层次和顺序，按照协议字段的长度及协议节点的类型，将二进制块中的数据取出放到数据节点中。
  4. 如权利要求1所述的基于PB和XPATH的网元级网管业务配置适配系统，其特征在于：所述PB应用接口用于：
    (1)PB数据合并：当业务配置有多个条目，在增加条目的时候，根据协议中描述的关键字，将两个数据节点中的数据合并到一个数据节点中；
    (2)PB数据删除：当业务配置有多个条目，在减少条目的时候，根据协议中描述的关键字，将数据节点中对应的条目删掉；
    (3)PB数据修改：根据字段名及路径查找到字段值所在的位置对应的数据节点，修改其中的数据；
    (4)PB数据填充：客户端根据PB协议将配置界面呈现给用户，用户将数据填好后，应用将数据根据协议节点填充到数据节点中。
  5. 如权利要求1所述的基于PB和XPATH的网元级网管业务配置适配系统，其特征在于：所述协议字段的公共属性包括字段名、字 段值、字段类型长度、字段内容在配置界面上的显示方式。
  6. 如权利要求1所述的基于PB和XPATH的网元级网管业务配置适配系统，其特征在于：所述PB协议树形结构中的每个节点包含该节点的属性列表，节点包含子节点列表，每个子节点包含该子节点的属性列表和子节点列表。
  7. 如权利要求1至6中任一项所述的基于PB和XPATH的网元级网管业务配置适配系统，其特征在于：所述服务端将业务配置协议脚本适配到协议节点缓存起来，客户端查询PB协议进行界面呈现，用户在客户端的配置界面上进行业务配置，客户端将配置数据按照协议节点组织到数据节点中，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后调用总线接口，将PB二进制数据下发给服务端。
  8. 如权利要求7所述的基于PB和XPATH的网元级网管业务配置适配系统，其特征在于：所述服务端接收到PB二进制数据后，将PB二进制数据反序列化成数据节点，再将数据节点按照协议节点组织成网元设备需要的二进制数据，下发给网元设备。
  9. 如权利要求8所述的基于PB和XPATH的网元级网管业务配置适配系统，其特征在于：所述网元设备返回业务配置接口给服务端后，服务端按照协议节点将网元设备需要的二进制数据解析出来，组织成数据节点，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后通过总线接口将PB二进制数据返回给客户端；客户端再反序列化出数据节点，按照协议节点将数据呈现到配置界面上。
  10. 适用于权利要求1至9中任一项所述系统的基于PB和XPATH的网元级网管业务配置适配方法，其特征在于，包括以下步 骤：
    A、将业务配置协议基于PB协议定义成通用的树形结构，并将与业务配置协议对应的配置数据定义成对应的树形结构的PB数据；使用PB来定义树形结构的节点类型、协议字段的公共属性；使用PB来定义协议节点、数据节点；PB协议树形结构包括PB协议结构和PB数据结构，PB协议结构中保存协议字段的各种属性，PB数据结构中只保存数据；将业务配置协议脚本转换为PB协议结构缓存起来；
    适配业务配置协议脚本的流程如下：
    步骤101、加载业务配置协议脚本数据；
    步骤102、解析业务配置协议脚本的字段属性和循环层次；
    步骤103、根据字段属性和循环层次生成协议节点：将业务配置协议脚本中的字段属性与协议节点建立对应关系，根据对应关系将协议脚本转换到协议节点；
    步骤104、调用PB自身的序列化接口缓存PB协议；
    B、进行业务配置的时候，根据PB协议和PB数据组织成设备需要的二进制数据下发设备，读设备配置的时候，根据PB协议将二进制数据解析成PB数据，以XPATH的语法方式，根据PB协议对PB数据进行查找，实现基于XPATH的PB查找；
    基于XPATH的PB查找流程如下：
    步骤201、查找开始时，分解协议节点层次结构，建立协议节点的节点父子关系；
    步骤202、根据协议节点建立数据节点的节点父子关系；
    步骤203、建立协议节点的子节点与数据节点的子节点之间的对应关系；
    步骤204、建立协议字段与数据节点的字段之间的属性与值的关 系，最终建立查询关系；
    步骤205、查询关系建立完成后，根据XPATH语法分析查询语句；
    步骤206、根据查询语句中的路径信息，定位到节点所在的层次；
    步骤207、在相应的层次，根据关键字或其他条件找到数据节点，查出数据；
    C、业务配置的下发流程如下：
    服务端将业务配置协议脚本适配到协议节点缓存起来，客户端查询PB协议进行界面呈现，用户在客户端的配置界面上进行业务配置，客户端将配置数据按照协议节点组织到数据节点中，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后调用总线接口，将PB二进制数据下发给服务端；
    服务端接收到PB二进制数据后，将PB二进制数据反序列化成数据节点，再将数据节点按照协议节点组织成网元设备需要的二进制数据，下发给网元设备；
    网元设备返回业务配置接口给服务端后，服务端按照协议节点将网元设备需要的二进制数据解析出来，组织成数据节点，再调用PB自身的序列化接口，将数据节点序列化为PB二进制数据，然后通过总线接口将PB二进制数据返回给客户端；
    客户端再反序列化出数据节点，按照协议节点将数据呈现到配置界面上。
PCT/CN2015/088843 2014-09-10 2015-09-02 基于pb和xpath的网元级网管业务配置适配系统及方法 Ceased WO2016037540A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410457407.7A CN104270257B (zh) 2014-09-10 2014-09-10 基于pb和xpath的网元级网管业务配置适配系统及方法
CN201410457407.7 2014-09-10

Publications (1)

Publication Number Publication Date
WO2016037540A1 true WO2016037540A1 (zh) 2016-03-17

Family

ID=52161751

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/088843 Ceased WO2016037540A1 (zh) 2014-09-10 2015-09-02 基于pb和xpath的网元级网管业务配置适配系统及方法

Country Status (2)

Country Link
CN (1) CN104270257B (zh)
WO (1) WO2016037540A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112769767A (zh) * 2020-12-23 2021-05-07 华人运通(上海)云计算科技有限公司 车载以太网some/ip协议数据的解析方法、装置、介质及系统

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104270257B (zh) * 2014-09-10 2017-11-07 烽火通信科技股份有限公司 基于pb和xpath的网元级网管业务配置适配系统及方法
CN105573956B (zh) * 2015-12-10 2019-06-21 盛趣信息技术（上海）有限公司 序列化方法以及基于序列化的网络通信方法
CN107222461B (zh) * 2017-05-04 2020-03-13 中国联合网络通信集团有限公司 通信处理方法和装置
CN112052294B (zh) * 2019-06-05 2023-01-31 烽火通信科技股份有限公司 用于业务调用的通用数据配置方法及系统
CN112051990A (zh) * 2019-06-06 2020-12-08 烽火通信科技股份有限公司 网管北向接口模型适配方法及系统
CN113765872B (zh) * 2020-10-14 2023-10-24 天翼数字生活科技有限公司 一种自适应数据格式转换适配的方法和系统
CN112801295A (zh) * 2021-04-12 2021-05-14 远江盛邦（北京）网络安全科技股份有限公司 基于通用网络空间资产的组织推演方法及系统
CN116260894A (zh) * 2023-02-27 2023-06-13 北京天融信网络安全技术有限公司 数据传输方法、装置、系统和电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102457378A (zh) * 2010-10-15 2012-05-16 洛克威尔自动控制技术股份有限公司 用于工业装置的安全模型
US20120131645A1 (en) * 2010-11-18 2012-05-24 Harm Michael W User Scriptable Server Initiated User Interface Creation
CN103003813A (zh) * 2010-04-05 2013-03-27 谷歌公司 记录的列状存储表示
CN103940441A (zh) * 2014-05-06 2014-07-23 百度在线网络技术（北京）有限公司 一种兴趣点搜索方法和装置
CN104270257A (zh) * 2014-09-10 2015-01-07 烽火通信科技股份有限公司 基于pb和xpath的网元级网管业务配置适配系统及方法

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101719902B (zh) * 2009-12-04 2014-07-30 深圳创维数字技术股份有限公司 一种远程过程调用方法和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103003813A (zh) * 2010-04-05 2013-03-27 谷歌公司 记录的列状存储表示
CN102457378A (zh) * 2010-10-15 2012-05-16 洛克威尔自动控制技术股份有限公司 用于工业装置的安全模型
US20120131645A1 (en) * 2010-11-18 2012-05-24 Harm Michael W User Scriptable Server Initiated User Interface Creation
CN103940441A (zh) * 2014-05-06 2014-07-23 百度在线网络技术（北京）有限公司 一种兴趣点搜索方法和装置
CN104270257A (zh) * 2014-09-10 2015-01-07 烽火通信科技股份有限公司 基于pb和xpath的网元级网管业务配置适配系统及方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112769767A (zh) * 2020-12-23 2021-05-07 华人运通(上海)云计算科技有限公司 车载以太网some/ip协议数据的解析方法、装置、介质及系统

Also Published As

Publication number Publication date
CN104270257B (zh) 2017-11-07
CN104270257A (zh) 2015-01-07

Similar Documents

Publication Publication Date Title
WO2016037540A1 (zh) 基于pb和xpath的网元级网管业务配置适配系统及方法
US9959310B2 (en) Accessing single entities in OData entity sets
WO2020238597A1 (zh) 基于Hadoop的数据更新方法、装置、系统及介质
KR100843828B1 (ko) 포탈 서버에서 포틀릿들의 집합을 관리하기 위한 방법 및장치
US6449620B1 (en) Method and apparatus for generating information pages using semi-structured data stored in a structured manner
US8387030B2 (en) Service adaptation definition language
US8726229B2 (en) Multi-language support for service adaptation
US20040220946A1 (en) Techniques for transferring a serialized image of XML data
US20020078094A1 (en) Method and apparatus for XML visualization of a relational database and universal resource identifiers to database data and metadata
CN102402507B (zh) 一种soa多消息机制的异构数据集成系统和方法
CN106294695A (zh) 一种面向实时大数据搜索引擎的实现方法
EP2975535A1 (en) Checking freshness of data for a data integration system, DIS
US8762410B2 (en) Document level indexes for efficient processing in multiple tiers of a computer system
CN1987850A (zh) 一种实现ajax网页的方法
WO2018035799A1 (zh) 数据查询方法、应用和数据库服务器、中间件及系统
US11093492B1 (en) System and method of fetching data from an external program
CN110019314A (zh) 基于数据项分析的动态数据封装方法、客户端和服务端
WO2022135410A1 (zh) 加载源文件的方法及装置
CN107122486A (zh) 一种支持blob的多元大数据融合方法和系统
Niu et al. A design of cross-terminal web system based on JSON and REST
CN111611011A (zh) 一种支持Blob数据类型的JSON语法扩展方法和解析方法及装置
CN102523309A (zh) 响应客户端的请求获取并返回实时数据的方法和设备
US20150067089A1 (en) Metadata driven declarative client-side session management and differential server side data submission
Rodriguez-Martinez et al. Automatic deployment of application-specific metadata and code in MOCHA
CN103823855B (zh) 面向语义网的中文百科知识组织与集成方法

Legal Events

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

Ref document number: 15840872

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: 15840872

Country of ref document: EP

Kind code of ref document: A1