CN104270257B - NE-level webmaster business configuration adaption system and method based on PB and XPATH - Google Patents
NE-level webmaster business configuration adaption system and method based on PB and XPATH Download PDFInfo
- Publication number
- CN104270257B CN104270257B CN201410457407.7A CN201410457407A CN104270257B CN 104270257 B CN104270257 B CN 104270257B CN 201410457407 A CN201410457407 A CN 201410457407A CN 104270257 B CN104270257 B CN 104270257B
- Authority
- CN
- China
- Prior art keywords
- protocol
- data
- node
- business configuration
- 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.)
- Active
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
Abstract
The invention discloses a kind of NE-level webmaster business configuration adaption system based on PB and XPATH and method, it is related to computer software programming field, the system includes service end, client, PB itself serializing interface, PB itself unserializing interface, PB application interfaces, EBI and network element device, service end includes PB protocol definition units, business configuration agreement script adaptation unit and the PB searching units based on XPATH, PB protocol definitions unit is by business configuration agreement based on PB protocol definitions into general tree structure, and configuration data corresponding with business configuration agreement is defined as to the PB data of corresponding tree structure；Business configuration agreement script is fitted to protocol node by business configuration agreement script adaptation unit.The present invention can be adapted to the extension that any puppy parc script carries out NE-level business configuration, reduce the workload of webmaster business configuration functional development, easy to maintenance, reduce maintenance cost, improve webmaster quality.
Description
Technical field
The present invention relates to computer software programming field, a kind of NE-level webmaster based on PB and XPATH is specifically related to
Business configuration adaption system and method.
Background technology
Business configuration is a basic function of webmaster.The process of business configuration is：Described according to the agreement of business configuration,
The binary data blocks that the business tine tissue forming apparatus that user is filled in needs, then this data block is handed down to equipment, with complete
The opening of configuration, equipment into IP, the switching of function, the additions and deletions of business tine change.The agreement of business configuration describes carrier can
It can be document, it is also possible to script.If the agreement of business configuration describes carrier only document, webmaster developer needs fixed
Adopted corresponding data structure is corresponding with protocol fields, and completes data structure to the serializing operation of binary data blocks, and
The unserializing of binary data blocks to data structure is operated.If it is script that the agreement of business configuration, which describes carrier, have
The more common serializing carried out according to script and unserializing operation, but the structure type of script is also varied
, the processing mode of various scripts is also different, and the workload of webmaster business configuration functional development is very big, and maintenance cost is very
It is high.
The content of the invention
The invention aims to overcome the shortcomings of above-mentioned background technology, there is provided a kind of network element based on PB and XPATH
Level webmaster business configuration adaption system and method, can be adapted to the extension that any puppy parc script carries out NE-level business configuration,
The workload of webmaster business configuration functional development is reduced, it is easy to maintenance, maintenance cost is reduced, webmaster quality is improved.
The present invention provides a kind of NE-level webmaster business configuration adaption system based on PB and XPATH, including service end, visitor
Family end, PB itself serializing interface, PB itself unserializing interface, PB application interfaces, EBI and network element device, institute
Stating service end includes PB protocol definitions unit, business configuration agreement script adaptation unit and the PB searching units based on XPATH, its
In：
The PB protocol definitions unit is used for：By business configuration agreement based on sub-protocol buffers PB protocol definitions into general
Tree structure, and configuration data corresponding with business configuration agreement is defined as to the PB data of corresponding tree structure；Use PB
To define the public attribute of the node type of tree structure, protocol fields；Protocol node, back end are defined using PB；PB
Agreement tree structure includes each attribute that protocol fields are preserved in PB protocol architectures and PB data structures, PB protocol architectures, PB
Data are only preserved in data structure；
The business configuration agreement script adaptation unit is used to business configuration agreement script being fitted to protocol node：Loading
Business configuration agreement script data, parses the field attribute and circulating level of business configuration agreement script, according to field attribute and
Circulating level generates protocol node：Field attribute in business configuration agreement script and protocol node are set up into corresponding relation, root
Agreement script is transformed into protocol node according to corresponding relation；PB itself serializing interface is called to cache PB agreements；
The PB searching units based on XPATH are used for：One or one is searched according to specified protocol path or other conditions
The value of field is criticized, realizes that the PB based on XPATH is searched：When searching beginning, protocol node hierarchical structure is decomposed, protocol node is set up
Node set membership；The node set membership of back end is set up according to protocol node；Set up the child node of protocol node with
Corresponding relation between the child node of back end；The attribute set up between protocol fields and the field of back end and the pass of value
System, finally sets up inquiry relation；After the completion of inquiry relation is set up, according to XPATH syntactic analysis query statements；According to query statement
In routing information, the level navigated to where node；In corresponding level, data section is found according to keyword or other conditions
Point, finds data.
On the basis of above-mentioned technical proposal, the PB itself serializing interface is used for back end serializing to two
System：Protocol node is corresponding with business configuration agreement, when serializing, according to level and order, according to protocol fields
Length and protocol node type, the field value in back end is written in binary block.
On the basis of above-mentioned technical proposal, the PB itself unserializing interface is used for PB binary system unserializings
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 are put into back end.
On the basis of above-mentioned technical proposal, the PB application interfaces are used for：
(1) PB data merge：When business configuration has multiple entries, when entry is increased, according to described in agreement
Keyword, the data in two back end are merged into a back end；
(2) PB data are deleted：When business configuration has multiple entries, when entry is reduced, according to described in agreement
Keyword, corresponding entry in back end is deleted；
(3) PB data modifications：The corresponding back end in position according to where field name and path searching to field value, is repaiied
Change data therein；
(4) PB data are filled：Configuration interface is presented to user by client according to PB agreements, after user fills in data,
It is filled into using by data according to protocol node in back end.
On the basis of above-mentioned technical proposal, the public attribute of the protocol fields includes field name, field value, field class
The display mode of type length, field contents on configuration interface.
On the basis of above-mentioned technical proposal, each node in the PB agreements tree structure includes the attribute of the node
List, node includes child list, and each child node includes the attribute list and child list of the child node.
On the basis of above-mentioned technical proposal, business configuration agreement script is fitted to protocol node and cached by the service end
Get up, client query PB agreements carry out interface presentation, user carries out business configuration, client on the configuration interface of client
By configuration data according to protocol node tissue into back end, PB itself serializing interface is recalled, by back end sequence
Row turn to PB binary data, then call EBI, PB binary data is handed down into service end.
On the basis of above-mentioned technical proposal, the service end is received after PB binary data, by PB binary data
Unserializing into back end, then by back end according to protocol node be organized into network element device needs binary data, under
Issue network element device.
On the basis of above-mentioned technical proposal, after the network element device returns to business configuration interface to service end, service end
The binary data that network element device needs is parsed according to protocol node, back end is organized into, recalls PB's itself
Interface is serialized, back end sequence is turned into PB binary data, then PB binary data is returned to by EBI
To client；Antitone sequence dissolves back end to client again, and data are presented on configuration interface according to protocol node.
The present invention also provides a kind of adaptation of the NE-level webmaster business configuration based on PB and XPATH suitable for said system
Method, comprises the following steps：
A, by business configuration agreement based on PB protocol definitions into general tree structure, and will be corresponding with business configuration agreement
Configuration data be defined as the PB data of corresponding tree structure；Node type, the agreement word of tree structure are defined using PB
The public attribute of section；Protocol node, back end are defined using PB；PB agreements tree structure includes PB protocol architectures and PB numbers
According to structure, preserved in PB protocol architectures in each attribute of protocol fields, PB data structures and only preserve data；Business configuration is assisted
View script is converted to PB protocol architectures and is cached；
The flow of adaptation service configuration protocol script is as follows：
Step 101, loading business configuration agreement script data；
Step 102, the field attribute and circulating level for parsing business configuration agreement script；
Step 103, protocol node generated according to field attribute and circulating level：By the field in business configuration agreement script
Attribute sets up corresponding relation with protocol node, and agreement script is transformed into protocol node according to corresponding relation；
Step 104, the serializing interface caching PB agreements for calling PB itself；
When B, progress business configuration, issued according to the binary data that PB agreements and PB data are organized into equipment needs
Equipment, when reading device configuration, is parsed into PB data, with XPATH grammatical manner, root according to PB agreements by binary data
PB data are searched according to PB agreements, realize that the PB based on XPATH is searched；
It is as follows that PB based on XPATH searches flow：
When step 201, lookup start, protocol node hierarchical structure is decomposed, the node set membership of protocol node is set up；
Step 202, the node set membership for setting up according to protocol node back end；
Corresponding relation between the child node of step 203, the child node for setting up protocol node and back end；
Step 204, the attribute set up between protocol fields and the field of back end and the relation of value, it is final to set up inquiry
Relation；
After the completion of step 205, inquiry relation are set up, according to XPATH syntactic analysis query statements；
Step 206, the routing information in query statement, the level navigated to where node；
Step 207, in corresponding level, find back end according to keyword or other conditions, find data；
C, business configuration to issue flow as follows：
Business configuration agreement script is fitted to protocol node and is cached by service end, and client query PB agreements carry out boundary
Face is presented, and user carries out business configuration on the configuration interface of client, and client is by configuration data according to protocol node tissue
Into back end, PB itself serializing interface is recalled, back end sequence is turned into PB binary data, then called
EBI, service end is handed down to by PB binary data；
Service end is received after PB binary data, by PB binary data unserializings into back end, then by data
Node is organized into the binary data of network element device needs according to protocol node, is handed down to network element device；
After network element device returns to business configuration interface to service end, service end needs network element device according to protocol node
Binary data is parsed, and is organized into back end, recalls PB itself serializing interface, back end sequence is turned to
PB binary data, then returns to client by EBI by PB binary data；
Antitone sequence dissolves back end to client again, and data are presented on configuration interface according to protocol node.
Compared with prior art, advantages of the present invention is as follows：
(1) existing various business configuration modes are united and located by the present invention using a kind of new mode
Reason, the application mode of client is unified, only need to be according to Proto_Node (protocol node) processes user datas to Data_Node
The filling of (back end), can be adapted to the extension that any puppy parc script carries out NE-level business configuration, reduce webmaster business
The workload of configuration feature exploitation.
(2) what client of the invention was interacted with service end is PB data, and PB itself serializing is have passed through again (has compression
Process), interactive data volume is reduced；The process of Data Serialization and unserializing is general a set of code, easy to maintenance,
Maintenance cost can be effectively reduced, webmaster quality is improved.
Brief description of the drawings
Fig. 1 is the tree structure schematic diagram of PB agreements in the embodiment of the present invention.
Fig. 2 is the PB structural representations without circulation agreement in the embodiment of the present invention.
Fig. 3 is the PB structural representations for recirculating agreement in the embodiment of the present invention.
Fig. 4 is the PB structural representations of circulation agreement arranged side by side in the embodiment of the present invention.
Fig. 5 is the two PB structural representations for 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 the flow chart of the PB lookups based on XPATH in the embodiment of the present invention.
The flow chart that Fig. 8 issues for business configuration in the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawings and specific embodiment 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, including clothes
Business end, client, PB itself serializing interface, PB itself unserializing interface, PB application interfaces, EBI and network element
Equipment, service end includes PB protocol definitions unit, business configuration agreement script adaptation unit and the PB based on XPATH searches list
Member.
PB protocol definition units are used for：Business configuration agreement is assisted based on PB (Protocol Buffer, sub-protocol buffers)
View is defined as general tree structure, and configuration data corresponding with business configuration agreement is defined as into corresponding tree structure
PB data.Node type, public attribute (such as field name, field value, the field of protocol fields of tree structure are defined using PB
The display mode of Type Length, field contents on configuration interface etc.)；Protocol node, back end are defined using PB.PB is
A kind of structural data storage DIF of Google portable and effective, it is independently of language, independently of platform, can be used for
Structural data is serialized, and is well suited for being data storage or RPC (Remote Procedure Call Protocol, long-range mistake
Journey invocation protocol) data interchange format.
Shown in Figure 1, PB agreements tree structure includes preserving in PB protocol architectures and PB data structures, PB protocol architectures
Data are only preserved in each attribute of protocol fields, PB data structures.Each node in PB agreement tree structures can be included
The attribute list of the node, node again can include child list, each child node comprising the child node attribute list and
Child list.Without circulation agreement PB structures it is shown in Figure 2, one recirculate agreement PB structures it is shown in Figure 3, side by side
The PB structures for circulating agreement are shown in Figure 4, two recirculate agreement PB structures it is shown in Figure 5, it is oval in Fig. 2~5 to represent
Node, rectangle represents field or field value.The agreement of Multiple Cycle is i.e. available according to the combination of above structure.
Business configuration needs to come into contacts with binary data, the corresponding multiple fields, multiple entries, many of binary data
Individual level (containing entry again in entry), each field, entry, level have the data attribute and display properties of oneself, number
Include length, type, value scope etc. according to attribute, display properties includes whether display, Show Styles, display order etc., different
The different field structure of business configuration correspondence.
Business configuration agreement is provided in the way of script, and the form of script is not fixed, only needs that agreement word can be described
Business configuration agreement script is converted to PB protocol architectures and cached by the essential information of section, business configuration agreement script adaptation unit
Come.
Business configuration agreement script adaptation unit is used for：Business configuration agreement script is fitted to protocol node.
Shown in Figure 6, the flow of adaptation service configuration protocol script is as follows：
Step 101, loading business configuration agreement script data；
Step 102, the field attribute and circulating level for parsing business configuration agreement script,
Step 103, protocol node generated according to field attribute and circulating level：By the field in business configuration agreement script
Attribute sets up corresponding relation with protocol node, and agreement script is transformed into protocol node according to corresponding relation；
Step 104, the serializing interface caching PB agreements for calling PB itself.
When carrying out business configuration, the binary data for being organized into equipment needs according to PB agreements and PB data, which is issued, to be set
It is standby, when reading device configuration, binary data is parsed into by PB data according to PB agreements, with XPATH grammatical manner, according to
PB agreements are searched PB data.
PB searching units based on XPATH are used for：One or a collection of word are searched according to specified protocol path or other conditions
The value of section, realizes that the PB based on XPATH is searched.
Shown in Figure 7, it is as follows that the PB based on XPATH searches flow：
When step 201, lookup start, protocol node hierarchical structure is decomposed, the node set membership of protocol node is set up；
Step 202, the node set membership for setting up according to protocol node back end；
Corresponding relation between the child node of step 203, the child node for setting up protocol node and back end；
Step 204, the attribute set up between protocol fields and the field of back end and the relation of value, it is final to set up inquiry
Relation；
After the completion of step 205, inquiry relation are set up, according to XPATH syntactic analysis query statements；
Step 206, the routing information in query statement, the level navigated to where protocol node；
Step 207, in corresponding level, find back end according to keyword or other conditions, find data.
Described with PB tree structures after business configuration agreement, the hierarchical sequence of protocol node/protocol fields/back end with
XML paths are similar, and node/attribute/value of PB structures is also similar with XML node/attribute/value.XPATH (XML Path Language)
It is that one kind is used for determining certain portion in XML (Extensible Markup Language, extensible markup language) document
Language.There is provided the ability that node is looked in data-structure tree for trees of the XPATH based on XML.
PB itself serializing interface is used to back end serializing arriving binary system：Protocol node and business configuration agreement
It is corresponding, when serializing, according to level and order, according to the length and the type of protocol node of protocol fields, by number
It is written to according to the field value in node in binary block.
PB itself unserializing interface is used for PB binary systems unserializing into back end：Protocol node is matched somebody with somebody with business
It is corresponding to put agreement, when unserializing, according to level and order, according to the length and the class of protocol node of protocol fields
Type, the data in binary block are taken out and are put into back end.
PB application interfaces, are used for：
(1) PB data merge：When business configuration has multiple entries, when entry is increased, according to described in agreement
Keyword, the data in two back end are merged into a back end.
(2) PB data are deleted：When business configuration has multiple entries, when entry is reduced, according to described in agreement
Keyword, corresponding entry in back end is deleted.
(3) PB data modifications：The corresponding back end in position according to where field name and path searching to field value, is repaiied
Change data therein.
(4) PB data are filled：Configuration interface is presented to user by client according to PB agreements, after user fills in data,
It is filled into using by data according to protocol node in back end.
It is shown in Figure 8, business configuration to issue flow as follows：
Business configuration agreement script is fitted to protocol node and is cached by service end, and client query PB agreements carry out boundary
Face is presented, and user carries out business configuration on the configuration interface of client, and client is by configuration data according to protocol node tissue
Into back end, PB itself serializing interface is recalled, back end sequence is turned into PB binary data, then called
EBI, service end is handed down to by PB binary data.Service end is received after PB binary data, by PB binary data
Unserializing into back end, then by back end according to protocol node be organized into network element device needs binary data, under
Issue network element device.After network element device returns to business configuration interface to service end, service end is according to protocol node by network element device
The binary data needed is parsed, and is organized into back end, recalls PB itself serializing interface, by back end sequence
Row turn to PB binary data, and PB binary data then is returned into client by EBI.Client antitone sequence again
Back end is dissolved, data are presented on configuration interface according to protocol node.
The embodiment of the present invention also provides a kind of NE-level webmaster business based on PB and XPATH suitable for said system and matched somebody with somebody
Adaptation method is put, is comprised the following steps：
A, by business configuration agreement based on PB protocol definitions into general tree structure, and will be corresponding with business configuration agreement
Configuration data be defined as the PB data of corresponding tree structure.Node type, the agreement word of tree structure are defined using PB
The public attribute (such as display mode of field name, field value, field type length, field contents on configuration interface) of section；
Protocol node, back end are defined using PB.
It is shown in Figure 1, preserved in PB protocol architectures and number is only preserved in each attribute of protocol fields, PB data structures
According to.Each node in PB agreement tree structures can include the attribute list of the node, and node can include child node row again
Table, child node can include the attribute list and child list of its own again.PB structures without circulation agreement are referring to Fig. 2 institutes
Show, one recirculate agreement PB structures it is shown in Figure 3, the PB structures of circulation agreement are shown in Figure 4 side by side, and two recirculate association
The PB structures of view are shown in Figure 5, and ellipse represents node in Fig. 2~5, and rectangle represents field or field value.The association of Multiple Cycle
View is i.e. available according to the combination of above structure.
Business configuration needs to come into contacts with binary data, the corresponding multiple fields, multiple entries, many of binary data
Individual level (containing entry again in entry), each field, entry, level have the data attribute and display properties of oneself, number
Include length, type, value scope etc. according to attribute, display properties includes whether display, Show Styles, display order etc., different
The different field structure of business configuration correspondence.
Business configuration agreement is provided in the way of script, and the form of script is not fixed, only needs that agreement word can be described
The essential information of section, is converted to PB protocol architectures by business configuration agreement script and is cached.
Shown in Figure 6, the flow of adaptation service configuration protocol script is as follows：
Step 101, loading business configuration agreement script data；
Step 102, the field attribute and circulating level for parsing business configuration agreement script,
Step 103, protocol node generated according to field attribute and circulating level：By the field in business configuration agreement script
Attribute sets up corresponding relation with protocol node, and agreement script is transformed into protocol node according to corresponding relation；
Step 104, the serializing interface caching PB agreements for calling PB itself.
When B, progress business configuration, issued according to the binary data that PB agreements and PB data are organized into equipment needs
Equipment, when reading device configuration, is parsed into PB data, with XPATH grammatical manner, root according to PB agreements by binary data
PB data are searched according to PB agreements, realize that the PB based on XPATH is searched.
Shown in Figure 7, it is as follows that the PB based on XPATH searches flow：
When step 201, lookup start, protocol node hierarchical structure is decomposed, the node set membership of protocol node is set up；
Step 202, the node set membership for setting up according to protocol node back end；
Corresponding relation between the child node of step 203, the child node for setting up protocol node and back end；
Step 204, the attribute set up between protocol fields and the field of back end and the relation of value, it is final to set up inquiry
Relation；
After the completion of step 205, inquiry relation are set up, according to XPATH syntactic analysis query statements；
Step 206, the routing information in query statement, the level navigated to where protocol node；
Step 207, in corresponding level, find back end according to keyword or other conditions, find data.
It is C, shown in Figure 8, business configuration to issue flow as follows：
Business configuration agreement script is fitted to protocol node and is cached by service end, and client query PB agreements carry out boundary
Face is presented, and user carries out business configuration on the configuration interface of client, and client is by configuration data according to protocol node tissue
Into back end, PB itself serializing interface is recalled, back end sequence is turned into PB binary data, then called
EBI, service end is handed down to by PB binary data.Service end is received after PB binary data, by PB binary data
Unserializing into back end, then by back end according to protocol node be organized into network element device needs binary data, under
Issue network element device.After network element device returns to business configuration interface to service end, service end is according to protocol node by network element device
The binary data needed is parsed, and is organized into back end, recalls PB itself serializing interface, by back end sequence
Row turn to PB binary data, and PB binary data then is returned into client by EBI.Client antitone sequence again
Back end is dissolved, data are 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 modifications and change
Type is within the scope of the claims in the present invention and its equivalent technologies, then these modifications and variations are also in protection scope of the present invention
Within.
The prior art that the content not being described in detail in specification is known to the skilled person.
Claims (10)
1. a kind of NE-level webmaster business configuration adaption system based on PB and XPATH, including service end, client, PB itself
Serializing interface, PB itself unserializing interface, PB application interfaces, EBI and network element device, it is characterised in that：Institute
Stating service end includes PB protocol definitions unit, business configuration agreement script adaptation unit and the PB searching units based on XPATH, its
In：
The PB protocol definitions unit is used for：By business configuration agreement based on sub-protocol buffers PB protocol definitions into general tree-like
Structure, and configuration data corresponding with business configuration agreement is defined as to the PB data of corresponding tree structure；Determined using PB
The node type of adopted tree structure, the public attribute of protocol fields；Protocol node, back end are defined using PB；PB agreements
Tree structure includes each attribute that protocol fields are preserved in PB protocol architectures and PB data structures, PB protocol architectures, PB data
Data are only preserved in structure；
The business configuration agreement script adaptation unit is used to business configuration agreement script being fitted to protocol node：Loading business
Configuration protocol script data, parses the field attribute and circulating level of business configuration agreement script, according to field attribute and circulation
Level generates protocol node：Field attribute in business configuration agreement script and protocol node are set up into corresponding relation, according to right
It should be related to and agreement script is transformed into protocol node；PB itself serializing interface is called to cache PB agreements；
The PB searching units based on XPATH are used for：One or a collection of word are searched according to specified protocol path or other conditions
The value of section, realizes that the PB based on XPATH is searched：When searching beginning, protocol node hierarchical structure is decomposed, the section of protocol node is set up
Point set membership；The node set membership of back end is set up according to protocol node；Set up the child node and data of protocol node
Corresponding relation between the child node of node；The attribute set up between protocol fields and the field of back end and the relation of value,
Finally set up inquiry relation；After the completion of inquiry relation is set up, according to XPATH syntactic analysis query statements；According in query statement
Routing information, the level navigated to where protocol node；In corresponding level, data are found according to keyword or other conditions
Node, finds data.
2. the NE-level webmaster business configuration adaption system as claimed in claim 1 based on PB and XPATH, it is characterised in that：
The PB itself serializing interface is used to back end serializing arriving binary system：Protocol node and business configuration agreement are pair
Answer, when serializing, according to level and order, according to the length and the type of protocol node of protocol fields, by data section
Field value in point is written in binary block.
3. the NE-level webmaster business configuration adaption system as claimed in claim 1 based on PB and XPATH, it is characterised in that：
The PB itself unserializing interface is used for PB binary systems unserializing into back end：Protocol node is assisted with business configuration
View is corresponding, when unserializing, according to level and order, according to the length and the type of protocol node of protocol fields,
Data in binary block are taken out and are put into back end.
4. the NE-level webmaster business configuration adaption system as claimed in claim 1 based on PB and XPATH, it is characterised in that：
The PB application interfaces are used for：
(1) PB data merge：When business configuration has multiple entries, when entry is increased, the key according to described in agreement
Word, the data in two back end are merged into a back end；
(2) PB data are deleted：When business configuration has multiple entries, when entry is reduced, the key according to described in agreement
Word, corresponding entry in back end is deleted；
(3) PB data modifications：The corresponding back end in position according to where field name and path searching to field value, changes it
In data；
(4) PB data are filled：Configuration interface is presented to user by client according to PB agreements, after user fills in data, application
Data are filled into back end according to protocol node.
5. the NE-level webmaster business configuration adaption system as claimed in claim 1 based on PB and XPATH, it is characterised in that：
It is aobvious on configuration interface that the public attribute of the protocol fields includes field name, field value, field type length, field contents
Show mode.
6. the NE-level webmaster business configuration adaption system as claimed in claim 1 based on PB and XPATH, it is characterised in that：
Each node in the PB agreements tree structure includes the attribute list of the node, and node includes child list, per height
Node includes the attribute list and child list of the child node.
7. the NE-level webmaster business configuration adaption system based on PB and XPATH as 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 the service end, client query PB associations
View carries out interface presentation, and user carries out business configuration on the configuration interface of client, and client is by configuration data according to agreement
Node organization recalls PB itself serializing interface, back end sequence is turned into PB binary data into back end,
Then EBI is called, PB binary data is handed down to service end.
8. the NE-level webmaster business configuration adaption system as claimed in claim 7 based on PB and XPATH, it is characterised in that：
The service end is received after PB binary data, by PB binary data unserializings into back end, then by back end
The binary data of network element device needs is organized into according to protocol node, network element device is handed down to.
9. the NE-level webmaster business configuration adaption system as claimed in claim 8 based on PB and XPATH, it is characterised in that：
After the network element device returns to business configuration interface to service end, service end two is entered according to protocol node by what network element device needed
Data processed are parsed, and are organized into back end, recall PB itself serializing interface, back end sequence is turned into PB bis-
Binary data, then returns to client by EBI by PB binary data；Antitone sequence dissolves data section to client again
Data, are presented on configuration interface by point according to protocol node.
10. suitable for the NE-level webmaster business configuration based on PB and XPATH of system any one of claim 1 to 9
Adaptation method, it is characterised in that comprise the following steps：
A, by business configuration agreement based on PB protocol definitions into general tree structure, and corresponding with business configuration agreement will match somebody with somebody
Data definition is put into the PB data of corresponding tree structure；The node type of tree structure, protocol fields are defined using PB
Public attribute；Protocol node, back end are defined using PB；PB agreements tree structure includes PB protocol architectures and PB data knots
Preserved in structure, PB protocol architectures in each attribute of protocol fields, PB data structures and only preserve data；By business configuration agreement pin
Originally PB protocol architectures are converted to be cached；
The flow of adaptation service configuration protocol script is as follows：
Step 101, loading business configuration agreement script data；
Step 102, the field attribute and circulating level for parsing business configuration agreement script；
Step 103, protocol node generated according to field attribute and circulating level：By the field attribute in business configuration agreement script
Corresponding relation is set up with protocol node, agreement script is transformed into by protocol node according to corresponding relation；
Step 104, the serializing interface caching PB agreements for calling PB itself；
When B, progress business configuration, the binary data for being organized into equipment needs according to PB agreements and PB data, which is issued, to be set
It is standby, when reading device configuration, binary data is parsed into by PB data according to PB agreements, with XPATH grammatical manner, according to
PB agreements are searched PB data, realize that the PB based on XPATH is searched；
It is as follows that PB based on XPATH searches flow：
When step 201, lookup start, protocol node hierarchical structure is decomposed, the node set membership of protocol node is set up；
Step 202, the node set membership for setting up according to protocol node back end；
Corresponding relation between the child node of step 203, the child node for setting up protocol node and back end；
Step 204, the attribute set up between protocol fields and the field of back end and the relation of value, it is final to set up inquiry pass
System；
After the completion of step 205, inquiry relation are set up, according to XPATH syntactic analysis query statements；
Step 206, the routing information in query statement, the level navigated to where protocol node；
Step 207, in corresponding level, find back end according to keyword or other conditions, find data；
C, business configuration to issue flow as follows：
Business configuration agreement script is fitted to protocol node and is cached by service end, and client query PB agreements carry out interface and are in
Existing, user carries out business configuration on the configuration interface of client, and client is by configuration data according to protocol node tissue to number
According to the serializing interface in node, recalling PB itself, back end sequence is turned into PB binary data, bus is then called
Interface, service end is handed down to by PB binary data；
Service end is received after PB binary data, by PB binary data unserializings into back end, then by back end
The binary data of network element device needs is organized into according to protocol node, network element device is handed down to；
After network element device returns to business configuration interface to service end, service end two is entered according to protocol node by what network element device needed
Data processed are parsed, and are organized into back end, recall PB itself serializing interface, back end sequence is turned into PB bis-
Binary data, then returns to client by EBI by PB binary data；
Antitone sequence dissolves back end to client again, and data are 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 CN104270257A (en) | 2015-01-07 |
| CN104270257B true 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) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104270257B (en) * | 2014-09-10 | 2017-11-07 | 烽火通信科技股份有限公司 | NE-level webmaster business configuration adaption system and method based on PB and XPATH |
| CN105573956B (en) * | 2015-12-10 | 2019-06-21 | 盛趣信息技术（上海）有限公司 | Sequencing method and network communication method based on serializing |
| CN107222461B (en) * | 2017-05-04 | 2020-03-13 | 中国联合网络通信集团有限公司 | Communication processing method and device |
| CN112052294B (en) * | 2019-06-05 | 2023-01-31 | 烽火通信科技股份有限公司 | General data configuration method and system for service call |
| CN112051990A (en) * | 2019-06-06 | 2020-12-08 | 烽火通信科技股份有限公司 | Network management northbound interface model adaptation method and system |
| CN113765872B (en) * | 2020-10-14 | 2023-10-24 | 天翼数字生活科技有限公司 | Method and system for converting and adapting self-adaptive data format |
| CN112769767B (en) * | 2020-12-23 | 2022-06-14 | 华人运通(上海)云计算科技有限公司 | Vehicle-mounted Ethernet SOME/IP protocol data analysis method, device, medium and system |
| CN112801295A (en) * | 2021-04-12 | 2021-05-14 | 远江盛邦（北京）网络安全科技股份有限公司 | Organization deduction method and system based on universal network space assets |
Citations (2)
| 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 |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE202011110863U1 (en) * | 2010-04-05 | 2017-01-13 | Google Inc. | Column Memory Representations of records |
| US20120131645A1 (en) * | 2010-11-18 | 2012-05-24 | Harm Michael W | User Scriptable Server Initiated User Interface Creation |
| 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 (2)
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016037540A1 (en) | 2016-03-17 |
| CN104270257A (en) | 2015-01-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104270257B (en) | NE-level webmaster business configuration adaption system and method based on PB and XPATH | |
| US10747505B1 (en) | API specification generation | |
| US8156429B2 (en) | Method and system for accelerating downloading of web pages | |
| CN103383687B (en) | A kind of page processing method and device | |
| CN104915413B (en) | A kind of health detecting method and system | |
| US8549497B2 (en) | High-level hypermedia synthesis for adaptive web | |
| US11294899B2 (en) | Defining subgraphs declaratively with vertex and edge filters | |
| US8762410B2 (en) | Document level indexes for efficient processing in multiple tiers of a computer system | |
| US8468145B2 (en) | Indexing of URLs with fragments | |
| CN109522018B (en) | Page processing method and device and storage medium | |
| RU2008109251A (en) | INITIAL PLAYBACK OF SERVER CONTENT FOR WEB PAGES OF THE CLINICAL SCENARIO | |
| CN105550206B (en) | The edition control method and device of structured query sentence | |
| US20130179467A1 (en) | Calculating Property Caching Exclusions In A Graph Evaluation Query Language | |
| CN102075570A (en) | Method for implementing HTTP (hyper text transport protocol) message caching mechanism based on keywords | |
| Pagán et al. | A repository for scalable model management | |
| US11922209B2 (en) | Invoking functions of agents via digital assistant applications using address templates | |
| Odnert et al. | Architecture and compiler enhancements for PA-RISC workstations | |
| US7953886B2 (en) | Method and system of receiving and translating CLI command data within a routing system | |
| CN104021177B (en) | With reference to semantic net and the information integration method of geography information feature | |
| CN110321510A (en) | Page rendering method and system | |
| CN105989010A (en) | Web page data generation method, WEBITOX server and Web application system | |
| CN104778232A (en) | Searching result optimizing method and device based on long query | |
| US10719424B1 (en) | Compositional string analysis | |
| CN110851678A (en) | Method and device for crawling data | |
| CN108932327A (en) | A kind of page info extraction system and extracting method |
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 |