CN104270257A - Network element level network management service configuration adaptive system and method based on PB and XPATH - Google Patents
Network element level network management service configuration adaptive system and method based on PB and XPATH Download PDFInfo
- Publication number
- CN104270257A CN104270257A CN201410457407.7A CN201410457407A CN104270257A CN 104270257 A CN104270257 A CN 104270257A CN 201410457407 A CN201410457407 A CN 201410457407A CN 104270257 A CN104270257 A CN 104270257A
- Authority
- CN
- China
- Prior art keywords
- protocol
- node
- data
- agreement
- back end
- 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.)
- Granted
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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Communication Control (AREA)
Abstract
The invention discloses a network element level network management service configuration adaptive system and method based on a PB and an XPATH, and relates to the field of computer software programming. The system comprises a server, a client, a serialization interface of the PB, a deserialization interface of the PB, a PB application interface, a bus interface and a network element device, wherein the server comprises a PB protocol defining unit, a service configuration protocol script adaptive unit and a PB searching unit based on the XPATH, a service configuration protocol is defined into a universal tree structure by the PB protocol defining unit based on a PB protocol, and configuration data corresponding to the service configuration protocol are defined into the PB data of the corresponding tree structure by the PB protocol defining unit; a service configuration protocol script is adapted to a protocol node by the service configuration protocol script adaptive unit. The network element level network management service configuration adaptive system and method based on the PB and the XPATH can be adaptive to any universal protocol script so that network element level service configuration can be extended, the development workload of network management service configuration functions is reduced, maintenance is convenient to perform, the maintaining cost is reduced, and the network management quality is improved.
Description
Technical field
The present invention relates to computer software programming field, specifically relate to a kind of NE-level webmaster business configuration adaption system based on PB and XPATH and method.
Background technology
Business configuration is a basic function of webmaster.The process of business configuration is: the agreement according to business configuration describes, the business tine of user being filled in is organized into the binary data blocks that equipment needs, again this data block is handed down to equipment, to complete the configuration of IP, the opening of equipment, the switching of function, the additions and deletions of business tine change.It may be document that the agreement of business configuration describes carrier, also may be script.If it is only document that the agreement of business configuration describes carrier, then webmaster developer to need to define corresponding data structure corresponding with protocol fields, and complete data structure and operate to the serializing of binary data blocks, and binary data blocks operates to the unserializing of data structure.If it is script that the agreement of business configuration describes carrier, then can the more common serializing carried out of with good grounds script and unserializing operation, but the version of script is also diversified, the processing mode of various script is also different, the workload of webmaster business configuration functional development is very large, and maintenance cost is very high.
Summary of the invention
The object of the invention is the deficiency in order to overcome above-mentioned background technology, a kind of NE-level webmaster business configuration adaption system based on PB and XPATH and method are provided, the adaptive any puppy parc script of energy carries out the expansion of NE-level business configuration, reduce the workload of webmaster business configuration functional development, easy to maintenance, reduce maintenance cost, improve webmaster quality.
The invention provides a kind of NE-level webmaster business configuration adaption system based on PB and XPATH, comprise service end, client, the serializing interface of PB self, the unserializing interface of PB self, PB application interface, bus interface and network element device, described service end comprises PB protocol definition unit, business configuration agreement script adaptation unit and searches unit based on the PB of XPATH, wherein:
Described PB protocol definition unit is used for: business configuration agreement is become general tree structure based on sub-protocol buffers PB protocol definition, and the configuration data corresponding with business configuration agreement is defined as the PB data of corresponding tree structure; PB is used to define the node type of tree structure, the public attribute of protocol fields; PB is used to define protocol node, back end; PB agreement tree structure comprises PB protocol architecture and PB data structure, preserves each attribute of protocol fields, only preserve data in PB data structure in PB protocol architecture;
Described business configuration agreement script adaptation unit is used for business configuration agreement script to be fitted to protocol node: loaded with traffic configuration protocol script data, resolve field attribute and the circulating level of business configuration agreement script, protocol node is generated: the field attribute in business configuration agreement script and protocol node are set up corresponding relation, according to corresponding relation, agreement script is transformed into protocol node according to field attribute and circulating level; Call the serializing interface buffer memory PB agreement of PB self;
The described PB based on XPATH search unit for: according to the value of specified protocol path or other conditional searches one or a collection of field, the PB realized based on XPATH searches: when searching beginning, decompose protocol node hierarchical structure, set up the node set membership of protocol node; The node set membership of back end is set up according to protocol node; Set up the corresponding relation between the child node of protocol node and the child node of back end; Set up the relation of attribute between protocol fields and the field of back end and value, finally set up query relation; After query relation has been set up, according to XPATH syntactic analysis query statement; According to the routing information in query statement, navigate to the level at node place; At corresponding level, find back end according to keyword or other conditions, find data.
On the basis of technique scheme, the serializing interface of described PB self to be used for back end serializing to binary system: protocol node is corresponding with business configuration agreement, when serializing, according to level and order, according to the length of protocol fields and the type of protocol node, the field value in back end is written in binary block.
On the basis of technique scheme, the unserializing interface of described PB self is used for PB binary system antitone sequence to change into back end: protocol node is corresponding with business configuration agreement, when unserializing, according to level and order, according to the length of protocol fields and the type of protocol node, the data in binary block are taken out and is put in back end.
On the basis of technique scheme, described PB application interface is used for:
(1) PB data merge: when business configuration has multiple entry, when increase entry, according to the keyword described in agreement, the data in two back end are merged in a back end;
(2) PB data are deleted: when business configuration has multiple entry, when minimizing entry, according to the keyword described in agreement, entry corresponding in back end are deleted;
(3) PB data modification: according to field name and the path searching back end corresponding to the position at field value place, amendment data wherein;
(4) PB data stuffing: configuration interface is presented to user according to PB agreement by client, user applies and data is filled in back end according to protocol node after data being filled in.
On the basis of technique scheme, the public attribute of described protocol fields comprises field name, field value, field type length, the display mode of field contents on configuration interface.
On the basis of technique scheme, each node in described PB agreement tree structure comprises the attribute list of this node, and node comprises child list, and each child node comprises attribute list and the child list of this child node.
On the basis of technique scheme, business configuration agreement script is fitted to protocol node and is cached by described service end, client query PB agreement is carried out interface and is presented, user carries out business configuration on the configuration interface of client, configuration data is organized in back end according to protocol node by client, then calls the serializing interface of PB self, and back end sequence is turned to PB binary data, then call bus interface, PB binary data is handed down to service end.
On the basis of technique scheme, after described service end receives PB binary data, PB binary data antitone sequence is changed into back end, then back end is organized into the binary data of network element device needs according to protocol node, be handed down to network element device.
On the basis of technique scheme, described network element device returns business configuration interface to after service end, the binary data that network element device needs parses according to protocol node by service end, be organized into back end, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then by bus interface, PB binary data is returned to client; Client again antitone sequence dissolves back end, data is presented on configuration interface according to protocol node.
The present invention also provides a kind of NE-level webmaster business configuration adaptation method based on PB and XPATH being applicable to said system, comprises the following steps:
A, business configuration agreement is become general tree structure based on PB protocol definition, and the configuration data corresponding with business configuration agreement is defined as the PB data of corresponding tree structure; PB is used to define the node type of tree structure, the public attribute of protocol fields; PB is used to define protocol node, back end; PB agreement tree structure comprises PB protocol architecture and PB data structure, preserves each attribute of protocol fields, only preserve data in PB data structure in PB protocol architecture; Business configuration agreement script is converted to PB protocol architecture be cached;
The flow process of adaptation service configuration protocol script is as follows:
Step 101, loaded with traffic configuration protocol script data;
Step 102, the field attribute of resolving business configuration agreement script and circulating level;
Step 103, generate protocol node according to field attribute and circulating level: the field attribute in business configuration agreement script and protocol node are set up corresponding relation, according to corresponding relation, agreement script is transformed into protocol node;
Step 104, call the serializing interface buffer memory PB agreement of PB self;
B, when carrying out business configuration, equipment is issued according to the binary data that PB agreement and PB Organization of Data forming apparatus need, when reading Equipments Setting, according to PB agreement, binary data is resolved to PB data, with the grammatical manner of XPATH, search PB data according to PB agreement, the PB realized based on XPATH searches;
It is as follows that PB based on XPATH searches flow process:
Step 201, when searching beginning, decompose protocol node hierarchical structure, set up the node set membership of protocol node;
Step 202, set up the node set membership of back end according to protocol node;
Step 203, set up corresponding relation between the child node of protocol node and the child node of back end;
Step 204, set up the relation of attribute between protocol fields and the field of back end and value, finally set up query relation;
After step 205, query relation have been set up, according to XPATH syntactic analysis query statement;
Step 206, according to the routing information in query statement, navigate to the level at node place;
Step 207, at corresponding level, find back end according to keyword or other conditions, find data;
C, business configuration to issue flow process as follows:
Business configuration agreement script is fitted to protocol node and is cached by service end, client query PB agreement is carried out interface and is presented, user carries out business configuration on the configuration interface of client, configuration data is organized in back end according to protocol node by client, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then calls bus interface, PB binary data is handed down to service end;
After service end receives PB binary data, PB binary data antitone sequence is changed into back end, then back end is organized into the binary data of network element device needs according to protocol node, be handed down to network element device;
Network element device returns business configuration interface to after service end, the binary data that network element device needs parses according to protocol node by service end, be organized into back end, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then by bus interface, PB binary data is returned to client;
Client again antitone sequence dissolves back end, data is presented on configuration interface according to protocol node.
Compared with prior art, advantage of the present invention is as follows:
(1) the present invention uses a kind of new mode existing various business configuration modes to be united to process, the application mode of client is unified, only need according to the filling of Proto_Node (protocol node) processes user data to Data_Node (back end), the adaptive any puppy parc script of energy carries out the expansion of NE-level business configuration, reduces the workload of webmaster business configuration functional development.
(2) client of the present invention and service end mutual be PB data, have passed through again the serializing (having the process of compression) of PB self, mutual data volume reduces; The process of Data Serialization and unserializing is general a set of code, easy to maintenance, effectively can reduce maintenance cost, improves webmaster quality.
Accompanying drawing explanation
Fig. 1 is the tree structure schematic diagram of PB agreement in the embodiment of the present invention.
Fig. 2 is the PB structural representation without circulation agreement in the embodiment of the present invention.
Fig. 3 is a PB structural representation recirculating agreement in the embodiment of the present invention.
Fig. 4 is the PB structural representation of circulation agreement arranged side by side in the embodiment of the present invention.
Fig. 5 is the two PB structural representations recirculating agreement in the embodiment of the present invention.
Fig. 6 is the flow chart of adaptation service configuration protocol script in the embodiment of the present invention.
Fig. 7 is based on the flow chart that the PB of XPATH searches in the embodiment of the present invention.
Fig. 8 is the flow chart that in the embodiment of the present invention, business configuration issues.
Embodiment
Below in conjunction with drawings and the specific embodiments, the present invention is described in further detail.
The embodiment of the present invention provides a kind of NE-level webmaster business configuration adaption system based on PB and XPATH, comprise service end, client, the serializing interface of PB self, the unserializing interface of PB self, PB application interface, bus interface and network element device, service end comprises PB protocol definition unit, business configuration agreement script adaptation unit and searches unit based on the PB of XPATH.
PB protocol definition unit is used for: by business configuration agreement based on PB (Protocol Buffer, sub-protocol buffers) protocol definition becomes general tree structure, and the configuration data corresponding with business configuration agreement is defined as the PB data of corresponding tree structure.PB is used to define the node type of tree structure, the public attribute (as field name, field value, field type length, the display mode etc. of field contents on configuration interface) of protocol fields; PB is used to define protocol node, back end.PB is the structural data memory transactions form of a kind of portable and effective of Google, it is independent of language, independent of platform, may be used for structural data serialization, be well suited for doing data to store or RPC (Remote Procedure Call Protocol, remote procedure call protocol) data interchange format.
Shown in Figure 1, PB agreement tree structure comprises PB protocol architecture and PB data structure, preserves each attribute of protocol fields, only preserve data in PB data structure in PB protocol architecture.Each node in PB agreement tree structure can comprise the attribute list of this node, and node can comprise child list again, and each child node comprises attribute list and the child list of this child node.PB structure without circulation agreement is shown in Figure 2, one the recirculate PB structure of agreement is shown in Figure 3, and the PB structure of circulation agreement arranged side by side is shown in Figure 4, and two the recirculate PB structures of agreement are shown in Figure 5, oval representation node in Fig. 2 ~ 5, rectangle represents field or field value.The agreement of Multiple Cycle can obtain according to above textural association.
Business configuration needs to come into contacts with binary data, binary data corresponding multiple field, multiple entry, many levels (containing entry again in entry), each field, entry, level have oneself data attribute and display properties, data attribute comprises length, type, value scope etc., display properties comprise whether show, Show Styles, DISPLAY ORDER etc., the field structure that different business configuration is corresponding different.
Business configuration agreement provides in the mode of script, and the form of script is not fixing, and only need the essential information that can describe protocol fields, business configuration agreement script is converted to PB protocol architecture and is cached by business configuration agreement script adaptation unit.
Business configuration agreement script adaptation unit is used for: business configuration agreement script is fitted to protocol node.
Shown in Figure 6, the flow process of adaptation service configuration protocol script is as follows:
Step 101, loaded with traffic configuration protocol script data;
Step 102, the field attribute of resolving business configuration agreement script and circulating level,
Step 103, generate protocol node according to field attribute and circulating level: the field attribute in business configuration agreement script and protocol node are set up corresponding relation, according to corresponding relation, agreement script is transformed into protocol node;
Step 104, call the serializing interface buffer memory PB agreement of PB self.
When carrying out business configuration, issue equipment according to the binary data that PB agreement and PB Organization of Data forming apparatus need, when reading Equipments Setting, according to PB agreement, binary data is resolved to PB data, with the grammatical manner of XPATH, according to PB agreement, PB data are searched.
PB based on XPATH search unit for: according to the value of specified protocol path or other conditional searches one or a collection of field, the PB realized based on XPATH searches.
Shown in Figure 7, it is as follows that the PB based on XPATH searches flow process:
Step 201, when searching beginning, decompose protocol node hierarchical structure, set up the node set membership of protocol node;
Step 202, set up the node set membership of back end according to protocol node;
Step 203, set up corresponding relation between the child node of protocol node and the child node of back end;
Step 204, set up the relation of attribute between protocol fields and the field of back end and value, finally set up query relation;
After step 205, query relation have been set up, according to XPATH syntactic analysis query statement;
Step 206, according to the routing information in query statement, navigate to the level at node place;
Step 207, at corresponding level, find back end according to keyword or other conditions, find data.
After describing business configuration agreement by PB tree structure, the hierarchical sequence of protocol node/protocol fields/back end and XML class of paths seemingly, the node/attribute/value of PB structure and the node/attribute/value of XML also similar.XPATH (XML path language) is the language that one is used for determining certain portion in XML (Extensible Markup Language, extend markup language) document.XPATH, based on the tree of XML, is provided in data-structure tree the ability of looking for node.
The serializing interface of PB self to be used for back end serializing to binary system: protocol node is corresponding with business configuration agreement, when serializing, according to level and order, according to the length of protocol fields and the type of protocol node, the field value in back end is written in binary block.
The unserializing interface of PB self is used for PB binary system antitone sequence to change into back end: protocol node is corresponding with business configuration agreement, when unserializing, according to level and order, according to the length of protocol fields and the type of protocol node, the data in binary block are taken out and is put in back end.
PB application interface, for:
(1) PB data merge: when business configuration has multiple entry, when increase entry, according to the keyword described in agreement, the data in two back end are merged in a back end.
(2) PB data are deleted: when business configuration has multiple entry, when minimizing entry, according to the keyword described in agreement, entry corresponding in back end are deleted.
(3) PB data modification: according to field name and the path searching back end corresponding to the position at field value place, amendment data wherein.
(4) PB data stuffing: configuration interface is presented to user according to PB agreement by client, user applies and data is filled in back end according to protocol node after data being filled in.
Shown in Figure 8, business configuration to issue flow process as follows:
Business configuration agreement script is fitted to protocol node and is cached by service end, client query PB agreement is carried out interface and is presented, user carries out business configuration on the configuration interface of client, configuration data is organized in back end according to protocol node by client, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then calls bus interface, PB binary data is handed down to service end.After service end receives PB binary data, PB binary data antitone sequence is changed into back end, then back end is organized into the binary data of network element device needs according to protocol node, be handed down to network element device.Network element device returns business configuration interface to after service end, the binary data that network element device needs parses according to protocol node by service end, be organized into back end, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then by bus interface, PB binary data is returned to client.Client again antitone sequence dissolves back end, data is presented on configuration interface according to protocol node.
The embodiment of the present invention also provides a kind of NE-level webmaster business configuration adaptation method based on PB and XPATH being applicable to said system, comprises the following steps:
A, business configuration agreement is become general tree structure based on PB protocol definition, and the configuration data corresponding with business configuration agreement is defined as the PB data of corresponding tree structure.PB is used to define the node type of tree structure, the public attribute (as field name, field value, field type length, the display mode etc. of field contents on configuration interface) of protocol fields; PB is used to define protocol node, back end.
Shown in Figure 1, preserve each attribute of protocol fields in PB protocol architecture, in PB data structure, only preserve data.Each node in PB agreement tree structure can comprise the attribute list of this node, and node can comprise child list again, and child node can comprise again its attribute list and child list.PB structure without circulation agreement is shown in Figure 2, one the recirculate PB structure of agreement is shown in Figure 3, and the PB structure of circulation agreement arranged side by side is shown in Figure 4, and two the recirculate PB structures of agreement are shown in Figure 5, oval representation node in Fig. 2 ~ 5, rectangle represents field or field value.The agreement of Multiple Cycle can obtain according to above textural association.
Business configuration needs to come into contacts with binary data, binary data corresponding multiple field, multiple entry, many levels (containing entry again in entry), each field, entry, level have oneself data attribute and display properties, data attribute comprises length, type, value scope etc., display properties comprise whether show, Show Styles, DISPLAY ORDER etc., the field structure that different business configuration is corresponding different.
Business configuration agreement provides in the mode of script, and the form of script is not fixing, only needs the essential information that can describe protocol fields, business configuration agreement script is converted to PB protocol architecture and is cached.
Shown in Figure 6, the flow process of adaptation service configuration protocol script is as follows:
Step 101, loaded with traffic configuration protocol script data;
Step 102, the field attribute of resolving business configuration agreement script and circulating level,
Step 103, generate protocol node according to field attribute and circulating level: the field attribute in business configuration agreement script and protocol node are set up corresponding relation, according to corresponding relation, agreement script is transformed into protocol node;
Step 104, call the serializing interface buffer memory PB agreement of PB self.
B, when carrying out business configuration, equipment is issued according to the binary data that PB agreement and PB Organization of Data forming apparatus need, when reading Equipments Setting, according to PB agreement, binary data is resolved to PB data, with the grammatical manner of XPATH, search PB data according to PB agreement, the PB realized based on XPATH searches.
Shown in Figure 7, it is as follows that the PB based on XPATH searches flow process:
Step 201, when searching beginning, decompose protocol node hierarchical structure, set up the node set membership of protocol node;
Step 202, set up the node set membership of back end according to protocol node;
Step 203, set up corresponding relation between the child node of protocol node and the child node of back end;
Step 204, set up the relation of attribute between protocol fields and the field of back end and value, finally set up query relation;
After step 205, query relation have been set up, according to XPATH syntactic analysis query statement;
Step 206, according to the routing information in query statement, navigate to the level at node place;
Step 207, at corresponding level, find back end according to keyword or other conditions, find data.
C, shown in Figure 8, business configuration to issue flow process as follows:
Business configuration agreement script is fitted to protocol node and is cached by service end, client query PB agreement is carried out interface and is presented, user carries out business configuration on the configuration interface of client, configuration data is organized in back end according to protocol node by client, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then calls bus interface, PB binary data is handed down to service end.After service end receives PB binary data, PB binary data antitone sequence is changed into back end, then back end is organized into the binary data of network element device needs according to protocol node, be handed down to network element device.Network element device returns business configuration interface to after service end, the binary data that network element device needs parses according to protocol node by service end, be organized into back end, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then by bus interface, PB binary data is returned to client.Client again antitone sequence dissolves back end, data is presented on configuration interface according to protocol node.
Those skilled in the art can carry out various modifications and variations to the embodiment of the present invention, if these amendments and modification are within the scope of the claims in the present invention and equivalent technologies thereof, then these revise and modification also within protection scope of the present invention.
The prior art that the content do not described in detail in specification is known to the skilled person.
Claims (10)
1. the NE-level webmaster business configuration adaption system based on PB and XPATH, comprise service end, client, the serializing interface of PB self, the unserializing interface of PB self, PB application interface, bus interface and network element device, it is characterized in that: described service end comprises PB protocol definition unit, business configuration agreement script adaptation unit and searches unit based on the PB of XPATH, wherein:
Described PB protocol definition unit is used for: business configuration agreement is become general tree structure based on sub-protocol buffers PB protocol definition, and the configuration data corresponding with business configuration agreement is defined as the PB data of corresponding tree structure; PB is used to define the node type of tree structure, the public attribute of protocol fields; PB is used to define protocol node, back end; PB agreement tree structure comprises PB protocol architecture and PB data structure, preserves each attribute of protocol fields, only preserve data in PB data structure in PB protocol architecture;
Described business configuration agreement script adaptation unit is used for business configuration agreement script to be fitted to protocol node: loaded with traffic configuration protocol script data, resolve field attribute and the circulating level of business configuration agreement script, protocol node is generated: the field attribute in business configuration agreement script and protocol node are set up corresponding relation, according to corresponding relation, agreement script is transformed into protocol node according to field attribute and circulating level; Call the serializing interface buffer memory PB agreement of PB self;
The described PB based on XPATH search unit for: according to the value of specified protocol path or other conditional searches one or a collection of field, the PB realized based on XPATH searches: when searching beginning, decompose protocol node hierarchical structure, set up the node set membership of protocol node; The node set membership of back end is set up according to protocol node; Set up the corresponding relation between the child node of protocol node and the child node of back end; Set up the relation of attribute between protocol fields and the field of back end and value, finally set up query relation; After query relation has been set up, according to XPATH syntactic analysis query statement; According to the routing information in query statement, navigate to the level at node place; At corresponding level, find back end according to keyword or other conditions, find data.
2. as claimed in claim 1 based on the NE-level webmaster business configuration adaption system of PB and XPATH, it is characterized in that: the serializing interface of described PB self to be used for back end serializing to binary system: protocol node is corresponding with business configuration agreement, when serializing, according to level and order, according to the length of protocol fields and the type of protocol node, the field value in back end is written in binary block.
3. as claimed in claim 1 based on the NE-level webmaster business configuration adaption system of PB and XPATH, it is characterized in that: the unserializing interface of described PB self is used for PB binary system antitone sequence to change into back end: protocol node is corresponding with business configuration agreement, when unserializing, according to level and order, according to the length of protocol fields and the type of protocol node, the data in binary block are taken out and is put in back end.
4., as claimed in claim 1 based on the NE-level webmaster business configuration adaption system of PB and XPATH, it is characterized in that: described PB application interface is used for:
(1) PB data merge: when business configuration has multiple entry, when increase entry, according to the keyword described in agreement, the data in two back end are merged in a back end;
(2) PB data are deleted: when business configuration has multiple entry, when minimizing entry, according to the keyword described in agreement, entry corresponding in back end are deleted;
(3) PB data modification: according to field name and the path searching back end corresponding to the position at field value place, amendment data wherein;
(4) PB data stuffing: configuration interface is presented to user according to PB agreement by client, user applies and data is filled in back end according to protocol node after data being filled in.
5., as claimed in claim 1 based on the NE-level webmaster business configuration adaption system of PB and XPATH, it is characterized in that: the public attribute of described protocol fields comprises field name, field value, field type length, the display mode of field contents on configuration interface.
6. as claimed in claim 1 based on the NE-level webmaster business configuration adaption system of PB and XPATH, it is characterized in that: each node in described PB agreement tree structure comprises the attribute list of this node, node comprises child list, and each child node comprises attribute list and the child list of this child node.
7. the NE-level webmaster business configuration adaption system based on PB and XPATH according to any one of claim 1 to 6, it is characterized in that: business configuration agreement script is fitted to protocol node and is cached by described service end, client query PB agreement is carried out interface and is presented, user carries out business configuration on the configuration interface of client, configuration data is organized in back end according to protocol node by client, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then bus interface is called, PB binary data is handed down to service end.
8. as claimed in claim 7 based on the NE-level webmaster business configuration adaption system of PB and XPATH, it is characterized in that: after described service end receives PB binary data, PB binary data antitone sequence is changed into back end, again back end is organized into the binary data of network element device needs according to protocol node, is handed down to network element device.
9. as claimed in claim 8 based on the NE-level webmaster business configuration adaption system of PB and XPATH, it is characterized in that: described network element device returns business configuration interface to after service end, the binary data that network element device needs parses according to protocol node by service end, be organized into back end, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then by bus interface, PB binary data is returned to client; Client again antitone sequence dissolves back end, data is presented on configuration interface according to protocol node.
10. be applicable to the NE-level webmaster business configuration adaptation method based on PB and XPATH of system according to any one of claim 1 to 9, it is characterized in that, comprise the following steps:
A, business configuration agreement is become general tree structure based on PB protocol definition, and the configuration data corresponding with business configuration agreement is defined as the PB data of corresponding tree structure; PB is used to define the node type of tree structure, the public attribute of protocol fields; PB is used to define protocol node, back end; PB agreement tree structure comprises PB protocol architecture and PB data structure, preserves each attribute of protocol fields, only preserve data in PB data structure in PB protocol architecture; Business configuration agreement script is converted to PB protocol architecture be cached;
The flow process of adaptation service configuration protocol script is as follows:
Step 101, loaded with traffic configuration protocol script data;
Step 102, the field attribute of resolving business configuration agreement script and circulating level;
Step 103, generate protocol node according to field attribute and circulating level: the field attribute in business configuration agreement script and protocol node are set up corresponding relation, according to corresponding relation, agreement script is transformed into protocol node;
Step 104, call the serializing interface buffer memory PB agreement of PB self;
B, when carrying out business configuration, equipment is issued according to the binary data that PB agreement and PB Organization of Data forming apparatus need, when reading Equipments Setting, according to PB agreement, binary data is resolved to PB data, with the grammatical manner of XPATH, search PB data according to PB agreement, the PB realized based on XPATH searches;
It is as follows that PB based on XPATH searches flow process:
Step 201, when searching beginning, decompose protocol node hierarchical structure, set up the node set membership of protocol node;
Step 202, set up the node set membership of back end according to protocol node;
Step 203, set up corresponding relation between the child node of protocol node and the child node of back end;
Step 204, set up the relation of attribute between protocol fields and the field of back end and value, finally set up query relation;
After step 205, query relation have been set up, according to XPATH syntactic analysis query statement;
Step 206, according to the routing information in query statement, navigate to the level at node place;
Step 207, at corresponding level, find back end according to keyword or other conditions, find data;
C, business configuration to issue flow process as follows:
Business configuration agreement script is fitted to protocol node and is cached by service end, client query PB agreement is carried out interface and is presented, user carries out business configuration on the configuration interface of client, configuration data is organized in back end according to protocol node by client, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then calls bus interface, PB binary data is handed down to service end;
After service end receives PB binary data, PB binary data antitone sequence is changed into back end, then back end is organized into the binary data of network element device needs according to protocol node, be handed down to network element device;
Network element device returns business configuration interface to after service end, the binary data that network element device needs parses according to protocol node by service end, be organized into back end, call the serializing interface of PB self again, back end sequence is turned to PB binary data, then by bus interface, PB binary data is returned to client;
Client again antitone sequence dissolves back end, data is presented on configuration interface according to protocol node.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410457407.7A CN104270257B (en) | 2014-09-10 | 2014-09-10 | NE-level webmaster business configuration adaption system and method based on PB and XPATH |
| PCT/CN2015/088843 WO2016037540A1 (en) | 2014-09-10 | 2015-09-02 | Network element network management service configuration adaptation system and method based on pb and xpath |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410457407.7A CN104270257B (en) | 2014-09-10 | 2014-09-10 | NE-level webmaster business configuration adaption system and method based on PB and XPATH |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104270257A true CN104270257A (en) | 2015-01-07 |
| CN104270257B CN104270257B (en) | 2017-11-07 |
Family
ID=52161751
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410457407.7A Active CN104270257B (en) | 2014-09-10 | 2014-09-10 | NE-level webmaster business configuration adaption system and method based on PB and XPATH |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN104270257B (en) |
| WO (1) | WO2016037540A1 (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016037540A1 (en) * | 2014-09-10 | 2016-03-17 | 烽火通信科技股份有限公司 | Network element network management service configuration adaptation system and method based on pb and xpath |
| CN105573956A (en) * | 2015-12-10 | 2016-05-11 | 盛趣信息技术（上海）有限公司 | Serialization method and serialization-based network communication method |
| CN107222461A (en) * | 2017-05-04 | 2017-09-29 | 中国联合网络通信集团有限公司 | Communication processing method and device |
| CN112051990A (en) * | 2019-06-06 | 2020-12-08 | 烽火通信科技股份有限公司 | Network management northbound interface model adaptation method and system |
| WO2020244033A1 (en) * | 2019-06-05 | 2020-12-10 | 烽火通信科技股份有限公司 | General data configuration method and system for service invocation |
| CN112801295A (en) * | 2021-04-12 | 2021-05-14 | 远江盛邦（北京）网络安全科技股份有限公司 | Organization deduction method and system based on universal network space assets |
| CN113765872A (en) * | 2020-10-14 | 2021-12-07 | 天翼智慧家庭科技有限公司 | Method and system for adaptive data format conversion adaptation |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112769767B (en) * | 2020-12-23 | 2022-06-14 | 华人运通(上海)云计算科技有限公司 | Vehicle-mounted Ethernet SOME/IP protocol data analysis method, device, medium and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101719902A (en) * | 2009-12-04 | 2010-06-02 | 深圳创维数字技术股份有限公司 | Remote procedure calling (PRC) method and system |
| CN102457378A (en) * | 2010-10-15 | 2012-05-16 | 洛克威尔自动控制技术股份有限公司 | Security model for industrial devices |
| US20120131645A1 (en) * | 2010-11-18 | 2012-05-24 | Harm Michael W | User Scriptable Server Initiated User Interface Creation |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101785959B1 (en) * | 2010-04-05 | 2017-10-17 | 구글 인코포레이티드 | Columnar storage representations of records |
| CN103940441B (en) * | 2014-05-06 | 2018-01-30 | 百度在线网络技术（北京）有限公司 | A kind of interest point search method and device |
| CN104270257B (en) * | 2014-09-10 | 2017-11-07 | 烽火通信科技股份有限公司 | NE-level webmaster business configuration adaption system and method based on PB and XPATH |
-
2014
- 2014-09-10 CN CN201410457407.7A patent/CN104270257B/en active Active
-
2015
- 2015-09-02 WO PCT/CN2015/088843 patent/WO2016037540A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101719902A (en) * | 2009-12-04 | 2010-06-02 | 深圳创维数字技术股份有限公司 | Remote procedure calling (PRC) method and system |
| CN102457378A (en) * | 2010-10-15 | 2012-05-16 | 洛克威尔自动控制技术股份有限公司 | Security model for industrial devices |
| US20120131645A1 (en) * | 2010-11-18 | 2012-05-24 | Harm Michael W | User Scriptable Server Initiated User Interface Creation |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016037540A1 (en) * | 2014-09-10 | 2016-03-17 | 烽火通信科技股份有限公司 | Network element network management service configuration adaptation system and method based on pb and xpath |
| CN105573956A (en) * | 2015-12-10 | 2016-05-11 | 盛趣信息技术（上海）有限公司 | Serialization method and serialization-based network communication method |
| CN107222461A (en) * | 2017-05-04 | 2017-09-29 | 中国联合网络通信集团有限公司 | Communication processing method and device |
| CN107222461B (en) * | 2017-05-04 | 2020-03-13 | 中国联合网络通信集团有限公司 | Communication processing method and device |
| WO2020244033A1 (en) * | 2019-06-05 | 2020-12-10 | 烽火通信科技股份有限公司 | General data configuration method and system for service invocation |
| CN112051990A (en) * | 2019-06-06 | 2020-12-08 | 烽火通信科技股份有限公司 | Network management northbound interface model adaptation method and system |
| CN113765872A (en) * | 2020-10-14 | 2021-12-07 | 天翼智慧家庭科技有限公司 | Method and system for adaptive data format conversion adaptation |
| CN113765872B (en) * | 2020-10-14 | 2023-10-24 | 天翼数字生活科技有限公司 | Method and system for converting and adapting self-adaptive data format |
| CN112801295A (en) * | 2021-04-12 | 2021-05-14 | 远江盛邦（北京）网络安全科技股份有限公司 | Organization deduction method and system based on universal network space assets |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016037540A1 (en) | 2016-03-17 |
| CN104270257B (en) | 2017-11-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104270257A (en) | Network element level network management service configuration adaptive system and method based on PB and XPATH | |
| CN109522018B (en) | Page processing method and device and storage medium | |
| US9832076B2 (en) | Resource change management in machine to machine network | |
| US8549497B2 (en) | High-level hypermedia synthesis for adaptive web | |
| US20180196643A1 (en) | Generating web api specification from online documentation | |
| CN102075570B (en) | Method for implementing HTTP (hyper text transport protocol) message caching mechanism based on keywords | |
| CN109445835A (en) | Method, terminal device and the computer readable storage medium of building project frame | |
| US20060031751A1 (en) | Method for creating editable web sites with increased performance & stability | |
| CN106790206B (en) | The message parsing method and device of operation system | |
| CN103645951A (en) | Cross-platform mobile data management system and method | |
| CN101997927A (en) | Method and system for caching data of WEB platform | |
| CN106294695A (en) | A kind of implementation method towards the biggest data search engine | |
| US20160072927A1 (en) | Odata enabled mobile software applications | |
| US20130179467A1 (en) | Calculating Property Caching Exclusions In A Graph Evaluation Query Language | |
| CN103699674A (en) | Webpage storing method, webpage opening method, webpage storing device, webpage opening device and webpage browsing system | |
| CN106909361A (en) | Web development approaches and device based on masterplate engine | |
| US20030158894A1 (en) | Multiterminal publishing system and corresponding method for using same | |
| Moradi et al. | Caasset: A framework for model-driven development of context as a service | |
| CN103744845A (en) | Method and system for WEB platform data caching | |
| Riva et al. | Designing web-based mobile services with REST | |
| KR20120122959A (en) | Method and Device for Collecting Web Contents and Computer-readable Recording Medium for the same | |
| CN109063059A (en) | User behaviors log processing method, device and electronic equipment | |
| CN110837359A (en) | MVC Web framework realized by GOLANG language | |
| CN112287266A (en) | Processing method and device for webpage configuration, equipment and storage medium | |
| CN106991144B (en) | Method and system for customizing data crawling workflow |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |