CN103761095B - Method for generating universal upgrade file head data information - Google Patents
Method for generating universal upgrade file head data information Download PDFInfo
- Publication number
- CN103761095B CN103761095B CN201410029717.9A CN201410029717A CN103761095B CN 103761095 B CN103761095 B CN 103761095B CN 201410029717 A CN201410029717 A CN 201410029717A CN 103761095 B CN103761095 B CN 103761095B
- Authority
- CN
- China
- Prior art keywords
- data
- type
- data information
- header
- file
- 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
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000010606 normalization Methods 0.000 claims description 7
- 210000001072 colon Anatomy 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 description 3
- 238000004422 calculation algorithm Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000002910 structure generation Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000007429 general method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000000547 structure data Methods 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A method for generating universal head data information structure of upgrade file includes defining head configuration file script language format, designing head generation parser of upgrade file to extract script language configuration file once, reading script file line by line and index recording, checking script language standard, distributing address to needed data in script language, writing head buffer to head of output file generated by upgrade file by head generation parser, writing original upgrade file in address defined by offset address of end statement. The invention improves the utilization efficiency of the generation of the head data structure of the upgrade file.
Description
Technical Field
The invention relates to a method for generating a universal upgrade file header data information structure.
Background
In an embedded system in the communication industry, in order to facilitate management of software upgrade related to a communication device, header data information for identification and management needs to be generated at the header of an upgraded file, and the type of the file, an original MD5 (message digest 5) check code of the file, and other information that needs to be determined are determined by identifying the header information data of the file during the upgrade process, so as to ensure the correctness and integrity of the upgraded file.
The existing method for generating the header data of the upgrade file is respectively realized by each project engineering, and a general realization method of the prior art is briefly described here: a software tool for generating the header data structure information is compiled according to the header data structure information of the upgrade file in the project engineering, such as the type of the file, the original MD5 check code of the file and other information needing to be determined. For example, the tool is provided with data information required for the header of the file, such as file format type, date of creation, file size, MD5 checksum, etc., and the tool organizes the data information in a format and location predetermined by the project and adds the data information to the header of the specified file.
The implementation method is a very private and different method, can only be used in the header structures of the same type of project engineering, and cannot be a header data structure generation project of general project engineering upgrade file management (therefore, at present, there is no patent for an implementation method for public upgrade file header generation), and there is no unified and general implementation tool.
Obviously, the existing technology does not have a unified header data structure generation tool for managing the upgrade files, so that an industry-required unified specification and a tool thereof cannot be formed, and even different project projects in the same company may need different and respectively-realized non-universal tools, thereby reducing the utilization efficiency of the upgrade file management requirements. The method in the prior art is to fix each data address, and to meet the requirement of the same header structure, fill the corresponding data into a corresponding address in a fixed manner, because the implementation method is most direct and simple, it is determined that the corresponding header generation tool can only be applied to the corresponding header structure requirement of the same class in a fixed manner.
In order to adapt to management of header information of the upgrade file required by various project projects in a large enterprise and form a universal header generation tool in the industry, a set of universal header generation parser tool of the upgrade file needs to be designed to provide the universal header generation tool of the upgrade file for various projects.
Disclosure of Invention
The invention provides a method for generating a universal head data information structure of an upgrade file, which improves the utilization efficiency of the generation of the head data structure of the upgrade file.
In order to achieve the above object, the present invention provides a method for generating a generic upgrade file header data information structure, the method comprising the steps of:
for each script statement, a sequence number is given to the head generation parser of the upgrade file, the sequence number is correspondingly used as an index of the statement record;
step 3, performing script language normalization check;
the header generation parser of the upgrade file detects the normalization of the script language in turn according to the index sequence number, and gives a warning or an error prompt for the non-compliant script language defined in the step 1, once the header generation parser of the upgrade file finds an error, the header generation parser of the upgrade file immediately exits the process, and provides error warning information containing the line number and the error description of the line number in the file where the script error statement is located for the user;
step 4, distributing addresses to the required data in the script language by an upgrade file header generation parser;
and 5, after all the records are written into the head cache buffer one by one according to the rule of the step 4, the head generation parser of the upgrade file writes the head cache buffer into the head of the output file generated by the upgraded file at one time, and then writes the input original upgraded file from the address defined by the offset address offset of the end statement.
The script statement format is as follows: offset, type, param, offset, type, parameter;
wherein:
type indicates the data information type of the header addition unit;
offset represents an offset address of the header addition unit;
param denotes parameters of the head addition unit.
The data information type is divided into three types:
data information type string;
end flag type end;
other specific header addition unit data information types.
The data information types of the other specific head adding units comprise:
data information type md 5;
data information type time;
data information type size;
other data information types like param parameter information that may not require the user to input themselves.
The generation parser of the upgrading file head of the script language is also specified as follows:
1. data in the unspecified header data structure is automatically filled with zeros;
2. the offset of each data information type must be linearly increased, that is, the offset of the data information type of the previous statement must be smaller than the offset of the data information type of the next statement, and the offset of the data information type of the previous statement plus the data size of the type should not be larger than the offset of the data information type of the next statement, otherwise, data overlap occurs;
3. the data size of the string data information type is determined by the actual byte size of the param parameter, the data sizes of other data information types are determined by the type, and the data sizes needing to be specified by the parameter are determined by the actual specified size;
4. each script file must have at least one unique end-type script statement to define the total size of the generated header, the end type should only appear after all other script statements, and all other script statements after the end type can be automatically ignored or a certain warning or error information is prompted to the user;
5. the data information type of param parameter is not needed, if the user inputs the parameter, the parameter is automatically ignored, and certain alarm information is given.
The index record contains the following information: the actual line number line in the file in which the statement is located corresponds to the offset address offset at the beginning of the header, the data type, the data parameter length deslen, the data parameter string desstrng, and a hidden data parameter description.
The step 4 comprises the following steps:
step 4.1, establishing a head cache buffer, wherein the total head size of the head cache buffer is defined by the offset of the end statement, and the default values of the head cache are all 0;
step 4.2, operating the index records item by item according to the index sequence numbers, and storing the parameter data in the index records to the specified address in the head cache;
if the data information type is string type, directly filling string type character string parameters into the specified address in the head cache;
if the data information type is other types, according to specifications of different types, corresponding data is extracted, the corresponding data is stored in the hidden data parameter description in the type statement record, and the hidden data parameter is filled in the offset address offset in the head cache.
If the data information is data information of MD5 type, then the MD5 check code needs to be extracted from the input upgraded file and saved into the hidden data parameter description in the record.
The invention improves the utilization efficiency of the generation of the head data structure of the upgrade file.
Drawings
FIG. 1 is a schematic diagram of an index record.
Fig. 2 is a data structure of a header cache.
Detailed Description
The preferred embodiment of the present invention is described in detail below with reference to fig. 1 and 2.
The invention provides a method for generating a universal upgrade file header data information structure, which comprises the following steps:
the script statement format adopts a sectional statement structure, which is determined by a general method for generating an upgrade file head data structure;
defining a line as a statement, wherein the line feed indicates the end of the statement, empty lines can exist among the script statements, and each statement needs to start at the top line;
the script statement format is as follows: type: param (offset: type: parameter), i.e., a statement consists of three segments, each with a separator between them, such as ": "colon separate, a statement is used to describe a header addition unit, where:
type indicates the data information type of the header addition unit, such as management information required by the upgrade file, such as header identification, file type, item type, generation date, file size, MD5 check code, version number of the upgrade file, etc.;
offset represents an offset address of the header addition unit, that is, byte position information of a data information element in the data structure with respect to the beginning of the header of the upgrade file;
param represents parameters of the head addition unit, and the parameters are not necessary according to different types, namely, some types do not need the parameters;
the data information type is divided into three types:
1. data information type string;
the unit data information is completely specified by a parameter in the statement, namely a universal string type, and can be used for realizing the addition of any header structure data information and attribute definition thereof, the unit data information is a data information type facing all header addition units defined in a character form, and a user can use the type to describe data in all data information types, such as header identification marks, file types, item types, generation dates, file sizes, MD5 check codes, version numbers of upgrade files and other management information required by the upgrade files, and the information such as the file sizes can be automatically acquired from the upgraded files without manually acquiring the sizes of the upgrade files and then serving as a parameter for providing the data information types;
if a character string "TAG _ BEGIN" of the upgrade file header identification mark is added from the header, then offset is 0, type is string, and param is "TAG _ BEGIN", that is, the corresponding script statement of the header addition unit is:
0:string:TAG_BEGIN
for the parameter description content which cannot be represented by using the character form, a "\\" escape symbol can be used for representation, for example, data with a byte of "0 x 01" needs to be added from an offset of 16 bytes, and the following script statement can be used for implementation:
16:string:\01
in addition, string type supports the parameters of the two mixed description modes, such as:
18:string:\02a\03bcd\90
2. end flag type end;
for defining the end position of the header data structure, rather than for describing a particular data information type element; the offset address offset value of the end type should be the total size of the number of bytes occupied by the entire header data structure, and the statement is always completed in the last statement of the script statement; in fact, all other statements that appear after the end statement are automatically ignored;
3. the data information type of other specific header addition units;
parameters required by some data information types which do not need to be input explicitly describe contents, such as MD5 check codes for checking the upgrade file, information for recording the generation time of the upgrade file, and information for recording the file size of the upgrade file, and the like:
3.1, data information type md 5: the MD5 code of the upgraded file needs to be added at a specified position, so that a keyword of the type MD5 (MD 5 is a technology for encrypting character strings and is also used for extracting a unique check code of the file, and the unique check code plays a role of a file fingerprint, when the file is changed or damaged, the MD5 check of the file changes, so that the integrity of the file can be judged through the MD5 check code) can be used, and the type does not need a param parameter;
the script statement can automatically extract standard MD5 code from the input upgraded original file and fill the standard MD5 code to the position where the offset of the header is offset byte, because the MD5 code is 16 bytes, the MD5 type needs to occupy 16 bytes, therefore, the next unit of the script statement header addition unit must start from the offset of offset +16 bytes at least, otherwise, the upgrade file header generation parser reports error, thus avoiding the situation of data overlapping;
3.2, data information type time: the method is used for automatically acquiring the current absolute time (the number of seconds starting from 1/1970) of the system and filling the absolute time to a specified offset address offset position, the key word also does not need parameter content, and the type needs to occupy 4 bytes; therefore, the data unit offset of the next statement should at least start from offset +4, otherwise the update file header generation parser will report an error, and the situation of data overlapping is avoided;
3.3, data information type size, wherein the keyword type is used for acquiring the byte size of the upgraded file and filling the byte size into a header file with specified offset, the keyword has parameters, namely the content needs to be described, the parameters are used for specifying the size of a large header space occupied by the size of the file, 1 ~ 4 four parameters are supported, the parameters respectively represent that the size of the file occupies 1 to 4 byte spaces, and if the parameters are not included, the default size is 4 bytes;
3.4, other similar data information types which do not need param parameter information input by the user can be created and expanded to be similar to the keywords, so that the corresponding information can be automatically acquired through the analyzer and automatically generated to the specified position, and the user can conveniently use the data information of the types;
the script statement also comprises a comment symbol which can be defined by using a #, i.e. all contents after the comment symbol is used at the beginning of the script file are comment contents and do not participate in the parsing processing of the script language;
the generation parser of the upgrading file head of the script language is also specified as follows:
1. data in the unspecified header data structure is automatically filled with zeros;
2. the offset of each data information type must be linearly increased, that is, the offset of the data information type of the previous statement must be smaller than the offset of the data information type of the next statement, and the offset of the data information type of the previous statement plus the data size of the type should not be larger than the offset of the data information type of the next statement, otherwise, data overlap occurs;
3. the data size of the string data information type is determined by the actual byte size of the param parameter, the data sizes of other data information types are determined by the type, and the data sizes needing to be specified by the parameter are determined by the actual specified size;
4. each script file must have at least one unique end-type script statement to define the total size of the generated header, the end type should only appear after all other script statements, and all other script statements after the end type can be automatically ignored or a certain warning or error information is prompted to the user;
5. the data information type of param parameters is not needed, if the parameters are input by a user, the parameters are automatically ignored, and certain alarm information is given;
for a blank line or a line with a comment symbol "#", it is ignored, that is, only the true script statement is recorded;
for each script statement, a sequence number is given to the head generation parser of the upgrade file, the sequence number is correspondingly used as an index of the statement record;
as shown in fig. 1, the following information is included in the record based on the index: the actual line number line in the file in which the statement is located, the offset address offset corresponding to the beginning of the header, the data type, the data parameter length deslen, the data parameter string desstrng, and a hidden data parameter description;
step 3, performing script language normalization check;
sequentially detecting the normalization of the scripting language by the generation parser of the head of the upgrade file according to the index sequence number (starting from 0 to the last index), and giving a warning or an error prompt to the script language which does not conform to the normalization defined in the step 1; the method comprises the steps that once an analyzer generated by upgrading a file head finds an error, the process is immediately exited, and error warning information containing line rows (which is convenient for a user to locate the error position in a script file) of a script error statement and error description of the line rows is provided for the user;
the offset is used for comparing the size of the address space between the upper statement and the lower statement, and when the size of the offset cannot meet the minimum space size required by the data type, an error prompt is given;
if the end-type script statement is found, the header generation parser of the upgrade file can consider that the end-type script statement is the last configuration statement of the script file, and the end-type script statement can be ignored even if other script statements exist, and the offset of the end-type script statement is used for defining the total size of the header;
step 4, distributing addresses to the required data in the script language by an upgrade file header generation parser;
step 4.1, establishing a head cache buffer, wherein the total head size of the head cache buffer is defined by the offset of the end statement, and the default values of the head cache are all 0;
step 4.2, operating the index records item by item according to the index sequence number (starting from 0 to the last index), and storing the parameter data in the index records to the specified address in the head cache;
if the data information type is string type, directly filling string type character string parameters into the specified address in the head cache;
if the data information type is other types, extracting corresponding data according to specifications of different types, storing the corresponding data into hidden data parameter description in the type statement record, and filling the hidden data parameters into an offset address offset in a head cache;
if the data information is of the MD5 type, the MD5 check code needs to be extracted from the input upgraded file and is saved in the hidden data parameter description in the record;
regarding the extraction of the MD5 check code, there is an existing algorithm, which is not described herein as a public technology, and with the support of the existing algorithm, the MD5 check code can be more conveniently extracted from the original file of the updated file, and on the basis of this function, the MD5 check code can be obtained independently without using an external MD5 tool;
the data in fig. 2 corresponds to the information in fig. 1, in fig. 2, the 9 bytes of data in the first row are TAG _ BEGIN of string type, the first byte of the second row represents string type \ 01, the second byte represents string type \ 01, the 16 bytes of data in the third row is MD5 check code, the 7 bytes of data in the fourth row is TAG _ END of string type, the start addresses of the above 5 data types are all defined by their corresponding offsets, and the END type represents that the total size of the header data is 64 bytes, which correspond to the 6 records shown in fig. 1 respectively.
The method provided by the invention is a very flexible generation mode and basically adapts to all head generation requirements.
While the present invention has been described in detail with reference to the preferred embodiments, it should be understood that the above description should not be taken as limiting the invention. Various modifications and alterations to this invention will become apparent to those skilled in the art upon reading the foregoing description. Accordingly, the scope of the invention should be determined from the following claims.
Claims (8)
1. A method for generating a generic upgrade file header data information structure, the method comprising the steps of:
step 1, defining the format of a scripting language of a header configuration file, and designing an upgrade file header meeting the format to generate an analyzer;
step 2, generating a parser at the head of the upgrade file to extract the script language configuration file at one time, reading the script language configuration file line by line and indexing and recording;
for each script statement, a sequence number is given to the head generation parser of the upgrade file, the sequence number is correspondingly used as an index of the statement record;
step 3, performing script language normalization check;
the header generation parser of the upgrade file detects the normalization of the script language in turn according to the index sequence number, and gives a warning or error prompt for the definition which is not in accordance with the step 1, and the header generation parser of the upgrade file immediately exits the process once an error is found, and provides error warning information containing the line number and error description of the line number in the file where the script error statement is located for the user;
step 4, distributing addresses to the required data in the script language by an upgrade file header generation parser;
and 5, after all the records are written into the head cache buffer one by one according to the step 4, the head cache buffer is written into the head of the output file generated by the upgraded file by the head generation resolver of the upgraded file at one time, and then the input original upgraded file is written from the address defined by the offset address offset of the end type script statement.
2. The method for generating a generic upgrade file header data information structure as claimed in claim 1, wherein said script statement format is: type to param, offset type to parameter, i.e. the statement is composed of three segments, with a separator between each segment, in ": "colon separate, a statement is used to describe a header addition unit, where:
type represents a data information type of the header addition unit;
offset represents an offset address of the header addition unit;
param denotes parameters of the head addition unit.
3. The method for generating a generic upgrade file header data information structure as claimed in claim 2, wherein said data information type is divided into three types:
data information type string;
end flag type end;
other specific header addition unit data information types.
4. The method for generating a generic upgrade file header data information structure as claimed in claim 3, wherein said other specific header addition unit data information types comprise:
data information type md 5;
data information type time;
data information type size;
and other data information types without the param parameter information input by the user.
5. The method for generating generic upgrade file header data information structure according to claim 4, wherein said upgrade file header generation parser of scripting language further has the following specifications:
(1) data in the unspecified header data structure is automatically filled with zeros;
(2) the offset of each data information type must be linearly increased, that is, the offset of the data information type of the previous statement must be smaller than the offset of the data information type of the next statement, and the offset of the data information type of the previous statement plus the data size of the type should not be larger than the offset of the data information type of the next statement, otherwise, data overlap occurs;
(3) the data size of the string data information type is determined by the actual byte size of the param parameter, the data sizes of other data information types are determined by the type, and the data sizes needing to be specified by the parameter are determined by the actual specified size;
(4) each script language configuration file must have at least one unique end type script statement to define the total size of the generated header, the end type should only appear after all other script statements, all other script statements after the end type can be automatically ignored, or a certain warning or error information is prompted to the user;
(5) the data information type of param parameter information input by the user is not needed, if the parameter is input by the user, the parameter is automatically ignored, and certain alarm information is given.
6. The method for generating a generic upgrade file header data information structure as claimed in claim 1, wherein said index record comprises the following information: the actual line number line in the file in which the statement is located corresponds to the offset address offset at the beginning of the header, the data type, the data parameter length despllen, the data parameter string desstroking, and a hidden data parameter description.
7. The method for generating a generic upgrade file header data information structure as claimed in claim 6, wherein said step 4 comprises the steps of:
step 4.1, establishing a head cache buffer, wherein the total head size of the head cache buffer is defined by the offset of the end statement, and the default values of the head cache are all 0;
step 4.2, operating the index records item by item according to the index sequence numbers, and storing the parameter data in the index records to the specified address in the head cache;
if the data type is string type, directly filling string type character string parameters into the specified address in the head cache;
if the data type is other types, according to specifications of different types, corresponding data is extracted, the corresponding data is stored in the hidden data parameter description in the index record, and the hidden data parameter description is filled in the offset address offset in the head cache.
8. The method for generating generic upgrade file header data information structure as claimed in claim 7, wherein if it is data information of MD5 type, then MD5 check code needs to be extracted from the input upgraded file and saved into the hidden data parameter description in the record.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410029717.9A CN103761095B (en) | 2014-01-23 | 2014-01-23 | Method for generating universal upgrade file head data information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410029717.9A CN103761095B (en) | 2014-01-23 | 2014-01-23 | Method for generating universal upgrade file head data information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103761095A CN103761095A (en) | 2014-04-30 |
| CN103761095B true CN103761095B (en) | 2020-01-07 |
Family
ID=50528339
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410029717.9A Active CN103761095B (en) | 2014-01-23 | 2014-01-23 | Method for generating universal upgrade file head data information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103761095B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106610861B (en) * | 2016-11-14 | 2019-09-03 | 广州视源电子科技股份有限公司 | Compilation Method and device |
| CN108132780B (en) * | 2017-12-13 | 2021-05-07 | 苏州长风航空电子有限公司 | Aviation display control method based on custom script |
| CN109558113B (en) * | 2018-11-28 | 2021-07-30 | 偶忆科技（深圳）有限公司 | Data field representation method and device and electronic equipment |
| CN111459496B (en) * | 2020-04-07 | 2021-06-08 | 珠海格力电器股份有限公司 | Method for generating tamper-proof program file and method for upgrading equipment |
| CN111597155B (en) * | 2020-05-20 | 2023-07-14 | 北京数科网维技术有限责任公司 | File linearization method suitable for ZIP file |
| CN112084757A (en) * | 2020-09-11 | 2020-12-15 | 北京中油瑞飞信息技术有限责任公司 | List construction method and device based on industrial application platform |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5752039A (en) * | 1993-03-22 | 1998-05-12 | Ntt Data Communications Systems Corp. | Executable file difference extraction/update system and executable file difference extraction method |
| CN101370078A (en) * | 2008-09-05 | 2009-02-18 | 深圳创维数字技术股份有限公司 | Digital television set-top box and its document upgrading apparatus and method |
| CN101924607A (en) * | 2010-08-27 | 2010-12-22 | 华为终端有限公司 | Firmware processing method based on firmware air transmission technology, device and system thereof |
| CN102932691A (en) * | 2012-10-23 | 2013-02-13 | 深圳市同洲电子股份有限公司 | Method and device for upgrading wireless fidelity (Wi-Fi) software of digital television terminal |
| CN103092634A (en) * | 2011-10-31 | 2013-05-08 | 四川长虹电器股份有限公司 | Set-top box software upgrading method for multiple flash devices |
| CN103218244A (en) * | 2013-05-17 | 2013-07-24 | 烽火通信科技股份有限公司 | Software updating and upgrading method of communication equipment |
-
2014
- 2014-01-23 CN CN201410029717.9A patent/CN103761095B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5752039A (en) * | 1993-03-22 | 1998-05-12 | Ntt Data Communications Systems Corp. | Executable file difference extraction/update system and executable file difference extraction method |
| CN101370078A (en) * | 2008-09-05 | 2009-02-18 | 深圳创维数字技术股份有限公司 | Digital television set-top box and its document upgrading apparatus and method |
| CN101924607A (en) * | 2010-08-27 | 2010-12-22 | 华为终端有限公司 | Firmware processing method based on firmware air transmission technology, device and system thereof |
| CN103092634A (en) * | 2011-10-31 | 2013-05-08 | 四川长虹电器股份有限公司 | Set-top box software upgrading method for multiple flash devices |
| CN102932691A (en) * | 2012-10-23 | 2013-02-13 | 深圳市同洲电子股份有限公司 | Method and device for upgrading wireless fidelity (Wi-Fi) software of digital television terminal |
| CN103218244A (en) * | 2013-05-17 | 2013-07-24 | 烽火通信科技股份有限公司 | Software updating and upgrading method of communication equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103761095A (en) | 2014-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103761095B (en) | Method for generating universal upgrade file head data information | |
| US20090007065A1 (en) | Logging system and method for computer software | |
| CN109240661B (en) | Code generation method and device | |
| CN105095168A (en) | Automatic generation method and device for contract files | |
| CN113704706B (en) | Code reinforcement method and device | |
| US20150278231A1 (en) | System and method for customizing archive of a device driver generator tool for a user | |
| CN106547782A (en) | The acquisition methods and device of log information | |
| CN112230892B (en) | Fault management method based on extensible markup language | |
| KR101882759B1 (en) | Method and apparatus for stabilized binary differencing | |
| CN110688315A (en) | Interface code detection report generation method, electronic device, and storage medium | |
| CN108037941A (en) | Application program update method, electronic equipment based on public plug-in unit, storage medium | |
| CN110659210A (en) | Information acquisition method and device, electronic equipment and storage medium | |
| CN111367890A (en) | Data migration method and device, computer equipment and readable storage medium | |
| CN109462661B (en) | Data synchronization method and device, computer equipment and storage medium | |
| CN113591422B (en) | System for generating test case flow information in chip verification and application | |
| CN100527131C (en) | Interdynamic access method and tool of IMS data base | |
| CN105389180B (en) | A kind of USB port configurableization method based on Android platform | |
| JP4477531B2 (en) | Data import method and data import apparatus | |
| CN106407288A (en) | Method and system for synchronously updating information | |
| CN107992311A (en) | A kind of method of rapid batch packing generation APK file | |
| CN104320454A (en) | Method and system for realizing user-defined output in HTTP protocol recovery | |
| CN114328552A (en) | Database management method, system and computer readable medium | |
| CN113948164A (en) | Clinical medicine management method, device, equipment and computer readable storage medium | |
| CN114282268A (en) | Database integrity checking method and device based on SM3 algorithm | |
| CN109840080B (en) | Character attribute comparison method and device, storage medium and electronic equipment |
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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201113 Address after: Room 10242, No. 260, Jiangshu Road, Xixing street, Binjiang District, Hangzhou City, Zhejiang Province Patentee after: Hangzhou Jiji Intellectual Property Operation Co.,Ltd. Address before: 201620 Shanghai city Songjiang District Guangfulin road 4855 Lane 20, No. 90 Patentee before: Phicomm (Shanghai) Co.,Ltd. |
|
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20140430 Assignee: Hangzhou xiaobuzhixue Information Technology Co.,Ltd. Assignor: Hangzhou Jiji Intellectual Property Operation Co.,Ltd. Contract record no.: X2021330000454 Denomination of invention: A method for generating general header data information of upgrade file Granted publication date: 20200107 License type: Common License Record date: 20211019 |
|
| EE01 | Entry into force of recordation of patent licensing contract | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20140430 Assignee: Hangzhou national software industry base Co.,Ltd. Assignor: Hangzhou Jiji Intellectual Property Operation Co.,Ltd. Contract record no.: X2021330000669 Denomination of invention: A method for generating general header data information of upgrade file Granted publication date: 20200107 License type: Common License Record date: 20211103 |
|
| EE01 | Entry into force of recordation of patent licensing contract | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20240226 Address after: 710075 Building 5-130, Jinghe Zhigu, Chongwen Town, Jinghe New City, Xixian New District, Xi'an City, Shaanxi Province, China Patentee after: Xi'an Mingzhou Jinyu Network Technology Co.,Ltd. Country or region after: China Address before: Room 10242, No. 260, Jiangshu Road, Xixing street, Binjiang District, Hangzhou City, Zhejiang Province Patentee before: Hangzhou Jiji Intellectual Property Operation Co.,Ltd. Country or region before: China |
|
| TR01 | Transfer of patent right |