CN101876901A - Method for realizing single disk block state of webmaster by using extensible markup language (XML) - Google Patents
Method for realizing single disk block state of webmaster by using extensible markup language (XML) Download PDFInfo
- Publication number
- CN101876901A CN101876901A CN2009102500256A CN200910250025A CN101876901A CN 101876901 A CN101876901 A CN 101876901A CN 2009102500256 A CN2009102500256 A CN 2009102500256A CN 200910250025 A CN200910250025 A CN 200910250025A CN 101876901 A CN101876901 A CN 101876901A
- Authority
- CN
- China
- Prior art keywords
- xml
- xsd
- status
- bulk state
- deck
- 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
Images
Abstract
The invention discloses a method for realizing the single disk block state of a webmaster by using extensible markup language (XML), and relates to application of the XML in single disk management. The method is characterized by comprising the following steps of: 1, generating a block state resolution and definition file; 2, generating an XML block state display file; and 3, displaying the single disk block state. The method for realizing the single disk block state of the webmaster by using the XML has the advantages of displaying the single disk block state by a block display method, quickly modifying the display mode as required, along with unified display mode and easy maintenance.
Description
Technical field
The present invention relates to the application of XML in the single-deck management, a kind of specifically method of dividing bulk state with XML realization webmaster single-deck.Said single-deck is the hardware device in the communication network.
Background technology
XML (eXtensible Markup Language, be called for short XML) be extend markup language, it is the same with HTML, all is according to SGML (Standard Generalized MarkupLanguage, be called for short SGML) made fixing, so XML can be considered as the subclass of SGML.XML is cross-platform in the Internet environment, depends on the technology of content, is the strong instrument of current Processing Structure document information.Expandable mark language XML is a kind of simple data storing language, use a series of simple mark data of description, and these marks can be set up with mode easily, though the XML occupation space will take more space than binary data, XML extremely simply is easy to grasp and use.XML simply makes it be easy to read and write data in Any Application, and this makes XML become unique common language of exchanges data very soon.Because the appearance of XML grammer, make SGML be able to standardization, and being applied to various fields, the message that makes its file content pass on can more easily be transmitted between each platform, the interchange and the data processing that help information, in addition, XML is easy to learn, therefore, XML has very important influence for the development of future network information.
XSD is meant XML organization definition (XML Schemas Definition), and XML Schema language is XSD just.XML Schema has described the structure of XML document, can verify certain XML document with the XML Schema of an appointment, whether meets its requirement to check this XML document.File design person can specify a structure that XML document allowed and a content by XML Schema, and can check in view of the above whether an XML document is effective.XML Schema itself is an XML document, and it meets the XML syntactic structure, can with general XML resolver resolves it.An XML Schema can define: whether the quantity of the attribute that occurs in the element that occurs in the document, the document, daughter element, daughter element, the order of daughter element, element are the acquiescence and the fixed value of data type, element or the attribute of sky, element and attribute.
XSD is that DTD (Document Type Definition, DTD (Document Type Definition)) replacer's reason has following 5 points, the one, can expand according to condition in the future, the 2nd, abundanter and useful than DTD, the 3rd, write with XML, the 4th, support data type, the 5th, support NameSpace.
The advantage of XML Schema is as follows:
1) XML Schema does not have special grammer based on XML;
2) XML can resolve and handle as other XML files;
3) XML Schema supports a series of data type (int, float, Boolean, date etc.);
4) XML Schema provides open-ended data model;
5) XML Schema supports comprehensive NameSpace;
6) XML Schema supports set of properties.
Since 21 century, because the fast development of communications industry, market competition is fierce day by day, and each big communications equipment manufacturer adopts the whole bag of tricks to reduce cost invariably.(said single-deck software is the software that operates on the single-deck in webmastering software exploitation and single-deck software development, said webmastering software is the software that moves on computers, it is in charge of all single-decks), the state of single-deck shows the general HTML (HyperText Mark-up Language) of the employing page, the developer need make the page of html format according to protocol contents, and often need in html page, use control to realize required display effect, yet there is following shortcoming in html page, makes it can't satisfy the demand of single-deck software development:
1) data and demonstration mix.Because used many controls in the html page, the skew and the length of control and data are closely connected, if html page will change display effect, just must make html page again, maintenance cost is very big.
2) need make different html pages to the different same data of single-deck demonstration, promptly html page and single-deck are man-to-man relation.
3) when the state of single-deck very for a long time, just must make a very big html page, can't realize that piecemeal shows.
Summary of the invention
At the defective that exists in the prior art, the object of the present invention is to provide a kind of method of dividing bulk state with XML realization webmaster single-deck, the mode that shows with piecemeal realizes that single-deck divides the demonstration of bulk state, and display mode is unified, can revise display mode as required fast, be easy to safeguard.
For reaching above purpose, the technical scheme that the present invention takes is:
A kind of method of dividing bulk state with XML realization webmaster single-deck is characterized in that may further comprise the steps:
Step 1, writing the branch bulk state resolves and defined file: dividing bulk state parsing and defined file and single-deck is the relation of one-to-many, divide in bulk state parsing and the defined file and comprised all status blocks, and each status block has unique state ID corresponding with it, each single-deck selection wherein several status blocks shows that the status block that needs to show obtains in minute bulk state parsing and defined file according to state ID;
Step 2, writing XML, to divide bulk state display file: XML to divide bulk state display file and single-deck be man-to-man relation, XML divides the quantity of the status block that bulk state display file shows as required, with the display format of each status block of formal definition of form, there are several status blocks that need to show just to have several forms corresponding with it;
Step 3, single-deck divide bulk state to show: webmastering software reads the branch block status data that single-deck reports, and obtains status block quantity and state ID thereof that this single-deck need show; Parse the status block that each needs show according to state ID and branch block status data in minute bulk state parsing and defined file, each status block that need show divides bulk state display file to generate final display page according to XML.
On the basis of technique scheme, XML divides bulk state display file to comprise form template and display type, and form template is used to control table format, and display type is used to represent basic data type.
Of the present inventionly realize that with XML the webmaster single-deck divides the method for bulk state to have the following advantages:
1) data are separated with demonstration.Dividing bulk state parsing and defined file is the status data definition, be responsible for the parsing of status block, and XML divides bulk state display file just to be responsible for the demonstration of status block, and write the skew that does not need computational data when parsing of branch bulk state and defined file and XML divide bulk state display file file, the page will change display effect just easily, need not make parsing of branch bulk state and defined file and XML again and divide bulk state display file, maintenance cost is low.
2) different single-decks is shown that same status block data do not need to make different XML and divide bulk state display file and divide bulk state to resolve and defined file, as long as status block ID unanimity.
3) when the state of single-deck very for a long time, do not need to make a very big display page, can realize easily that piecemeal shows.
Description of drawings
The present invention has following accompanying drawing:
Fig. 1 divides the structural representation of boardstatus_new element in bulk state parsing and the defined file
Embodiment
Below in conjunction with accompanying drawing the present invention is described in further detail.
The invention discloses a kind of method of dividing bulk state, may further comprise the steps with XML realization webmaster single-deck:
Step 1, writing the branch bulk state resolves and defined file: dividing bulk state parsing and defined file and single-deck is the relation of one-to-many, divide in bulk state parsing and the defined file and comprised all status blocks, and each status block has unique state ID corresponding with it, each single-deck selection wherein several status blocks shows that the status block that needs to show obtains in minute bulk state parsing and defined file according to state ID;
Step 2, writing XML, to divide bulk state display file: XML to divide bulk state display file and single-deck be man-to-man relation, XML divides the quantity of the status block that bulk state display file shows as required, with the display format of each status block of formal definition of form, there are several status blocks that need to show just to have several forms corresponding with it;
Step 3, single-deck divide bulk state to show: webmastering software reads the branch block status data that single-deck reports, and obtains status block quantity and state ID thereof that this single-deck need show; Parse the status block that each needs show according to state ID and branch block status data in minute bulk state parsing and defined file, each status block that need show divides bulk state display file to generate final display page according to XML.
On the basis of technique scheme, XML divides bulk state display file to comprise form template and display type, and form template is used to control table format, and display type is used to represent basic data type.
Below further specify concrete grammar of the present invention by a preferred embodiments, if some single-decks need show baseInfo, RecJ0 and three status blocks of SOE, then concrete implementing procedure is as follows:
Step 1, writing the branch bulk state resolves and defined file: dividing bulk state parsing and defined file and single-deck is the relation of one-to-many, divide in bulk state parsing and the defined file and comprised all status blocks, and each status block has unique state ID corresponding with it, each single-deck selection wherein several status blocks shows that the status block that needs to show obtains in minute bulk state parsing and defined file according to state ID; In this preferred embodiments, the branch bulk state is resolved and the expansion of defined file XSD by name, so following bulk state parsing and the defined file of will dividing abbreviates the XSD file as, is equivalent to the information analysis storehouse of all status blocks.What the XSD file carried out status page demonstration utilization is piecemeal thought, single-deck for minute bulk state, the XSD file just is equivalent to a total storehouse of status block, the branch bulk state of all single-decks all is stored in this file, and the needed several status blocks of certain single-deck can directly find in the XSD file according to state ID (IDentity).
Fig. 1 has shown the data structure of these three status blocks.Because baseInfo is the default configuration piece, does not need ID number.And the state ID of RecJ0 and two status block correspondences of SOE is 00030000,0003000B.The corresponding w:if=of difference in defined file " ../blockHead/statusID=' 0003000B ' " and w:if=" ../blockHead/statusID=' 00030000 ' ".These data structures adopt relevant XSD cannonical format such as element (xsd:element), complicated type (xsd:complexType), simple types (xsd:simpleType) to describe in the XSD file, below provide corresponding XSD definition format.
<xsd:complexType?name＝″BoardStatus_new″>
<xsd:sequence>
<xsd:element?name＝″baseInfo″type＝″baseType″
w:if＝″str(86，5)＝’4D42535F56’or?str(114，5)＝’4D42535F56’″>
＜!--for the essential information piece in minute bulk state, show the fundamental block letter
Breath--〉
</xsd:element>
<xsd:element?name＝″type″type＝″BYTE″/>
<xsd:element?name＝″blockNum″type＝″BYTE″/>
<xsd:element?name＝″record″type＝″blockRecord″
w:while＝″../blockNum″/>
</xsd:sequence>
</xsd:complexType>
＜!--single-deck essential information--〉
<xsd:complexType?name＝″baseType″>
<xsd:sequence>
<xsd:element name＝″cardno″ type＝″BYTE15″
W:event=" baseInfo " w:cn=" reel number " w:en=" Card Name "
w:show＝″ASCII″/>
<xsd:element?name＝″boardno″type＝″BYTE15″w:cn＝″
Plate number " w:en=" Board Name " w:show=" ASCII "/
<xsd:element?name＝″expandflag″type＝″BYTE7″/>
<xsd:element?name＝″expandtype″type＝″WORD″/>
<xsd:element?name＝″statusoffset″type＝″BYTE3″
w:size＝″″/>
＜xsd:element name=" time " type=" BYTE11 " w:cn=" system
Dish time " w:en=" Card Make Time " w:show=" ASCII "/
<xsd:element?name＝″BMUversion″type＝″BYTE13″
W:cn=" software version number " w:en=" Software Version " w:show=" ASCII "/〉
<xsd:element?name＝″BMUptime″type＝″BYTE11″
W:cn=" programming time " w:en=" Programme Time " w:show=" ASCII "/〉
＜xsd:element name=" active " type=" BYTE " w:cn=" dish
State of activation " w:en=" Card actived Status " w:show=" Actived "/
</xsd:sequence>
</xsd:complexType>
＜!--4.2.2 divides block state information--〉
<xsd:complexType?name＝″blockRecord″>
<xsd:sequence>
<xsd:element?name＝″FH″type＝″WORD″/>
<xsd:element?name＝″blocklable″type＝″BYTE″
w:show＝″Block″/>
<xsd:element?name＝″blocklength″type＝″DWORD″/>
<xsd:element?name＝″blockoffset″type＝″DWORD″/>
<xsd:element?name＝″ziptype″type＝″BYTE″/>
<xsd:element?name＝″backup″type＝″BYTE″/>
<xsd:element?name＝″blockid″type＝″DWORD″/>
<xsd:element?name＝″blockname″type＝″BYTE8″/>
<xsd:element?name＝″blockdata″type＝″BlockData″
w:if＝″../blocklength?！＝’00000000’″/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType?name＝″BlockData″>
<xsd:sequence>
<xsd:element?name＝″blockHead″type＝″Blockhead″/>
<xsd:element name＝″SOE″ type＝″SOE″
w:if＝″../blockHead/statusID＝’0003000B’″/>
<xsd:element name＝″RecJ0″ type＝″CRC15″
w:if＝″../blockHead/statusID＝’00030000’″/>
</xsd:sequence>
</xsd:complexType>
＜!--state divides build--〉
<xsd:complexType?name＝″Blockhead″>
<xsd:sequence>
<xsd:element?name＝″statusID″type＝″DWORD″/>
<xsd:element?name＝″datalength″type＝″DWORD″/>
<xsd:element?name＝″blockname″type＝″BYTE8″/>
<xsd:element?name＝″datatype″type＝″DWORD″/>
<xsd:element?name＝″bak″type＝″DWORD″/>
</xsd:sequence>
</xsd:complexType>
<！--CRC15-->
<xsd:complexType?name＝″CRC15″>
<xsd:sequence>
<xsd:element name＝″record″type＝″CRC15Rec″
w:while＝″datalength()div?16″/>
</xsd:sequence>
</xsd:complexType>
＜!--CRC15 record--〉
<xsd:complexType?name＝″CRC15Rec″>
<xsd:sequence>
<xsd:element?name＝″crc″type＝″BYTE″w:cn＝″CRC″
w:en＝″CRC″w:show＝″HEX″/>
＜xsd:element name=" data " type=" BYTE15 " w:cn=" number
Value " w:en=" value " w:show=" ASCII "/
</xsd:sequence>
</xsd:complexType>
＜!--section overhead state--〉
<xsd:complexType?name＝″SOE″>
<xsd:sequence>
＜xsd:element name=" SOEset " type=" BYTE " w:cn=" opens
Pin is provided with " w:en=" SOE Set " w:show=" SOEset "/
<xsd:element name＝″record780B″
type＝″addselect-780B″ w:while＝″datalength()！＝0″
w:if＝../../blockHead/datatype＝’80000000’″/>
<xsd:element name＝″record780A″
type＝″addselect-780A″ w:while＝″datalength()！＝0″
w:if＝../../blockHead/datatype＝’80000001’″/>
</xsd:sequence>
</xsd:compl?exType>
＜!--go up words and select record (780B)--〉
<xsd:complexType?name＝″addselect-780B″>
<xsd:sequence>
<xsd:element?name＝″received″type＝″BYTE″w:cn＝″
Last words are selected " w:en=" Add Select " w:show=" addselect_780B "/
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType?name＝″ASCII″>
<xsd:restriction?base＝″xsd:string″/>
</xsd:simpleType>
<xsd:simpleType?name＝″HEX″>
<xsd:restriction?base＝″xsd:hexBinary″/>
</xsd:simpleType>
<xsd:simpleType?name＝″SOEset″>
<xsd:restriction?base＝″xsd:hexBinary″>
＜xsd:enumeration value=" 00 " w:cn=" local termination "
w:en＝″Local?End″/>
＜xsd:enumeration value=" 01 " w:cn=" transparent transmission "
w:en＝″Transparency?Transmit″/>
</xsd:restriction>
</xsd:simpleType>
Boardstatus_new is the element (element is meant xsd:element) that closely links to each other with minute bulk state in the XSD file, and wherein: blockNum is the status block number; Baseinfo is the data parsing of single-deck essential information, comprising: reel number, version number, system dish time, BMU (BoardManagement Unit) software version number, BMU programming time, dish state of activation or the like. Type is a type, does not use at present; Record is for dividing the block state information recording section, the FH (beginning character of each status block of status block table of articles all is FH) of beginning is the status block table of articles to Blockname, writes down sign (blocklable), block length (blocklength), skew (blockoffset), compression type (ziptype), standby (backup), piece ID (blockid), piece name (blockname), the blocks of data (blockdata) of each status block.Blockhead in the blocks of data (blockdata) is a state piecemeal information header, mainly comprises: state ID (StatusID), block length (datalength), piece name (blockname), data type (datatype), standby (bak).And the remainder of blockdata is exactly status block data content: RecJ0 (J0 accepting state piece), SOE (section overhead status block).
Xsd represents the NameSpace of schema, and the literal behind the colon all is the definitional language of XSD.Can be with reference to the schema standard.Wherein, w:if:, be used to judge whether to be thereafter the xpath expression formula with this element resolution data for the schema expansion.Because the status block type is determined by " status data ID " in " dividing the block state information head ", so the judgement of w:if will be arranged.The corresponding state ID of each piece so just can know which piece the piece of back is according to the state ID of build, uses the relevant block definition that data are resolved then.
W:show: be the schema expansion.Be used to control display type, example is as follows:
A) letter
<xsd:simpleType?name＝″ASCII″>
<xsd:restriction?base＝″xsd:string″/>
</xsd:simpleType>
B) 16 systems
<xsd:simpleType?name＝″HEX″>
<xsd:restriction?base＝″xsd:hexBinary″/>
</xsd:simpleType>
C) enumeration type
<xsd:simpleType?name＝″SOEset″>
<xsd:restriction?base＝″xsd:hexBinary″>
＜xsd:enumeration value=" 00 " w:cn=" local termination "
w:en＝″Local?End″/>
＜xsd:enumeration value=" 01 " w:cn=" transparent transmission "
w:en＝″Transparency?Transmit″/>
</xsd:restriction>
</xsd:simpleType>
The using method of above-mentioned display type is as follows:
＜xsd:element name=" SOEset " type=" BYTE " w:cn=" expense setting " w:en=" SOE Set " w:show=" SOEset "/〉
When the SOEset value was 0, Chinese showed local termination, English display Local End, and when the SOEset value was 1, Chinese showed transparent transmission, English display TransparencyTransmit.
Step 2, writing XML, to divide bulk state display file: XML to divide bulk state display file and single-deck be man-to-man relation, XML divides the quantity of the status block that bulk state display file shows as required, with the display format of each status block of formal definition of form, there are several status blocks that need to show just to have several forms corresponding with it; XML divides bulk state display file to comprise form template and display type, and form template is used to control table format, and display type is used to represent basic data type.
Below provided the specific embodiment of three kinds of form templates and the specific embodiment of four kinds of display types, its quantity, content all can expand according to actual needs, and finish the function of writing template with script.
Three kinds of templates are as follows:
A) template 1
<template?name＝″table1″data＝″//baseInfo/*″col＝″4″>
＜title cn=" single-deck hardware information " en=" board base info "/〉
</template>
Wherein:
Name: template name, table1 are represented first kind of template, and data show according to mode from left to right.
Col: form columns.
Tilte: form topic head.
Cn: Chinese name.
En: English name.
Data: the list data source, use the xpath expression formula, in the XSD file, define.
Template 1 shows below form, and the StatusData in the following table represents concrete status data:
B) template 2
<template?name＝″table3″data＝″//RecJ0/record/*″col＝″3″flip＝″″>
＜title cn=" reception J0 " en=" receive J0 "/〉
＜sn cn=" branch road " en=" serial "/〉
<col?cn＝″CRC″en＝″CRC″/>
<col?cn＝″DATA″/>
</template>
Wherein:
Name: template name, table3 are represented second kind of template, are used to show a group record.
Sn: first row of form.
Col element: the header that refers to every hurdle.
Flip: perpendicular row is resolved, when not adding flip for walking crosswise parsing.
Template 2 shows below form, and the StatusData in the following table represents concrete status data:
C) template 3
<template?name＝″table4″data＝″//SOE″col＝″2″>
＜title cn=" section overhead state " en=" Setting Of SOH "/〉
<template?name＝″table1″data＝″SOEset″>
<template?name＝″table3″data＝″../record780B/*″>
＜sn cn=" sequence number " en=" serial "/〉
＜col cn=" going up words selects "/〉
</template>
</template>
</template>
Wherein:
Name: template name, table4 are represented the third template, situation that can indicator gauge rule form.
The problem of noting: the current reference position of data is the node of higher level data.
Template 3 shows below form, and the StatusData in the following table represents concrete status data:
Step 3, single-deck divide bulk state to show: webmastering software reads the branch block status data that single-deck reports, and obtains status block quantity and state ID thereof that this single-deck need show; Parse the status block that each needs show according to state ID and branch block status data in minute bulk state parsing and defined file, each status block that need show divides bulk state display file to generate final display page according to XML.Webmastering software reads the branch block status data that single-deck reports, and in conjunction with the XSD file, parses each minute block status data according to the state ID in minute block status data, comes out according to the form Pagination Display of XML file (XML divides bulk state display file) definition then.Step 3 can also further be subdivided into following step:
1) webmastering software reads the branch block status data that single-deck reports, and the block status data form was as follows in described minute:
The status block table of articles
Status data block 1 data 1 ..., status data block 1 data M 1,
Status data block 2 data 1 ..., status data block 2 data M 2,
……，……，
Status data block N data 1 ..., status data block N data M n
Said status block table of articles writes down sign, title, block length, skew of each status block etc.
Status block table of articles form is as follows:
2) read XSD file (dividing bulk state to resolve and defined file), according to definition in the file and state ID above-mentioned minute block status data is resolved in certain data structure, the predetermined data form should be consistent with above-mentioned minute block status data form in the XSD file.
3) read the display file of XML state at last,, minute bulk state is come out with the form Pagination Display of a plurality of forms in conjunction with data structure after resolving and the form definition among the XML.
The above only is a preferred embodiments of the present invention, and the interest field that the present invention advocated is not limited thereto.The present invention also can have other various embodiments; under the situation that does not deviate from spirit of the present invention and essence thereof; those skilled in the art work as can make various corresponding changes and distortion according to the present invention, but these changes and distortion all should belong to the protection domain of the appended claim of the present invention.
Claims (2)
1. realize the method that the webmaster single-deck divides bulk state with XML for one kind, it is characterized in that may further comprise the steps:
Step 1, writing the branch bulk state resolves and defined file: dividing bulk state parsing and defined file and single-deck is the relation of one-to-many, divide in bulk state parsing and the defined file and comprised all status blocks, and each status block has unique state ID corresponding with it, each single-deck selection wherein several status blocks shows that the status block that needs to show obtains in minute bulk state parsing and defined file according to state ID;
Step 2, writing XML, to divide bulk state display file: XML to divide bulk state display file and single-deck be man-to-man relation, XML divides the quantity of the status block that bulk state display file shows as required, with the display format of each status block of formal definition of form, there are several status blocks that need to show just to have several forms corresponding with it;
Step 3, single-deck divide bulk state to show: webmastering software reads the branch block status data that single-deck reports, and obtains status block quantity and state ID thereof that this single-deck need show; Parse the status block that each needs show according to state ID and branch block status data in minute bulk state parsing and defined file, each status block that need show divides bulk state display file to generate final display page according to XML.
2. method of dividing bulk state as claimed in claim 1 with XML realization webmaster single-deck, it is characterized in that: XML divides bulk state display file to comprise form template and display type, form template is used to control table format, and display type is used to represent basic data type.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200910250025 CN101876901B (en) | 2009-12-02 | 2009-12-02 | Method for realizing single disk block state of webmaster by using extensible markup language (XML) |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200910250025 CN101876901B (en) | 2009-12-02 | 2009-12-02 | Method for realizing single disk block state of webmaster by using extensible markup language (XML) |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101876901A true CN101876901A (en) | 2010-11-03 |
| CN101876901B CN101876901B (en) | 2013-04-10 |
Family
ID=43019463
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200910250025 Expired - Fee Related CN101876901B (en) | 2009-12-02 | 2009-12-02 | Method for realizing single disk block state of webmaster by using extensible markup language (XML) |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101876901B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105549936A (en) * | 2015-12-21 | 2016-05-04 | 腾讯科技（深圳）有限公司 | Data table display method and apparatus |
| CN115051904A (en) * | 2022-03-23 | 2022-09-13 | 武汉烽火技术服务有限公司 | Method and device for managing single disk state based on markup language |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030069960A1 (en) * | 2001-10-04 | 2003-04-10 | Symons Julie A. | Method for describing and comparing data center physical and logical topologies and device configurations |
| CN1640055A (en) * | 2002-07-01 | 2005-07-13 | 西门子公司 | Network management method for the configuration and the interface description of network elements by means of XML |
| US7159125B2 (en) * | 2001-08-14 | 2007-01-02 | Endforce, Inc. | Policy engine for modular generation of policy for a flat, per-device database |
| CN1917441A (en) * | 2005-08-20 | 2007-02-21 | 华为技术有限公司 | Method of realizing notification service, and distribution type network management system |
| CN101026486A (en) * | 2006-02-22 | 2007-08-29 | 华为技术有限公司 | Network management system and its method for realizing network management |
| CN101145130A (en) * | 2007-08-02 | 2008-03-19 | 中兴通讯股份有限公司 | Simple network management protocol software test device and test method |
| CN101394312A (en) * | 2008-11-12 | 2009-03-25 | 烽火通信科技股份有限公司 | Method and system for managing and parsing XML format uni-disk protocol |
-
2009
- 2009-12-02 CN CN 200910250025 patent/CN101876901B/en not_active Expired - Fee Related
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7159125B2 (en) * | 2001-08-14 | 2007-01-02 | Endforce, Inc. | Policy engine for modular generation of policy for a flat, per-device database |
| US20030069960A1 (en) * | 2001-10-04 | 2003-04-10 | Symons Julie A. | Method for describing and comparing data center physical and logical topologies and device configurations |
| CN1640055A (en) * | 2002-07-01 | 2005-07-13 | 西门子公司 | Network management method for the configuration and the interface description of network elements by means of XML |
| CN1917441A (en) * | 2005-08-20 | 2007-02-21 | 华为技术有限公司 | Method of realizing notification service, and distribution type network management system |
| CN101026486A (en) * | 2006-02-22 | 2007-08-29 | 华为技术有限公司 | Network management system and its method for realizing network management |
| CN101145130A (en) * | 2007-08-02 | 2008-03-19 | 中兴通讯股份有限公司 | Simple network management protocol software test device and test method |
| CN101394312A (en) * | 2008-11-12 | 2009-03-25 | 烽火通信科技股份有限公司 | Method and system for managing and parsing XML format uni-disk protocol |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105549936A (en) * | 2015-12-21 | 2016-05-04 | 腾讯科技（深圳）有限公司 | Data table display method and apparatus |
| CN105549936B (en) * | 2015-12-21 | 2020-05-19 | 腾讯科技（深圳）有限公司 | Data table display method and device |
| CN115051904A (en) * | 2022-03-23 | 2022-09-13 | 武汉烽火技术服务有限公司 | Method and device for managing single disk state based on markup language |
| CN115051904B (en) * | 2022-03-23 | 2023-09-12 | 武汉烽火技术服务有限公司 | Method and device for managing single disk state based on markup language |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101876901B (en) | 2013-04-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1794231B (en) | Context-free document portions with alternate formats | |
| Shklar | lang=" en"> Web Applications Architecture</title | |
| US7269788B2 (en) | Extensibility and usability of document and data representation languages | |
| Skonnard et al. | Essential XML quick reference | |
| US7739589B2 (en) | Extending markup of a browser using a plug-in framework | |
| CN101763423B (en) | Method for realizing presentation of tree-structure data in World Wide Web page as well as system and device therefor | |
| US7962919B2 (en) | Apparatus and method for modifying an initial event queue for extending an XML processor's feature set | |
| US20090006471A1 (en) | Exposing Specific Metadata in Digital Images | |
| CN100489862C (en) | Marked language archive analytical method, analytical module and user terminal | |
| GB2382174A (en) | Data formatting in a platform independent manner | |
| US9990344B1 (en) | Method and apparatus for extensibility of user interface binding definitions | |
| CN100492360C (en) | Method and system for webpage generation | |
| CN101876901B (en) | Method for realizing single disk block state of webmaster by using extensible markup language (XML) | |
| US20020174099A1 (en) | Minimal identification | |
| US20070168264A1 (en) | Automatic Package Conformance Validation | |
| CN105335205A (en) | Virtual instrument scripting language parser and method thereof | |
| CN102375889A (en) | Method for constructing webpage through webpage construction database | |
| CN102663107A (en) | Method and system for managing embedded data | |
| CN105808628A (en) | Webpage transcoding method, apparatus and system | |
| Holzner | SAMS Teach yourself XML in 21 days | |
| GB2458692A (en) | A process for generating database-backed, web-based documents | |
| CN106815303A (en) | A kind of crumbs navigation implementation method and system based on XML configurations and label | |
| Chase | XML primer plus | |
| KR20020069795A (en) | The method for recognize markup language to utilize universal document type definition and its readable form | |
| CN101446968A (en) | Method for parsing extend markup language |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130410 Termination date: 20201202 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |