CN113468106A - Storage and analysis method of VR application file irrelevant to platform - Google Patents

Storage and analysis method of VR application file irrelevant to platform Download PDF

Info

Publication number
CN113468106A
CN113468106A CN202110805123.2A CN202110805123A CN113468106A CN 113468106 A CN113468106 A CN 113468106A CN 202110805123 A CN202110805123 A CN 202110805123A CN 113468106 A CN113468106 A CN 113468106A
Authority
CN
China
Prior art keywords
file
data
module
data set
current
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.)
Pending
Application number
CN202110805123.2A
Other languages
Chinese (zh)
Inventor
梁侃
梁友
崔广伟
王龙华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Henan Sincerity Information Technology Co ltd
Original Assignee
Henan Sincerity Information Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Henan Sincerity Information Technology Co ltd filed Critical Henan Sincerity Information Technology Co ltd
Priority to CN202110805123.2A priority Critical patent/CN113468106A/en
Publication of CN113468106A publication Critical patent/CN113468106A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/11File system administration, e.g. details of archiving or snapshots
    • G06F16/113Details of archiving
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/16File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/602Providing cryptographic facilities or services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database

Abstract

The invention discloses a storage method of a VR application file irrelevant to a platform, which comprises the following operation steps: s1, storing all edited data in the same file directory to form a data set; s2, writing project global configuration data into the current data set, storing drawing board configuration data, rendering configuration data and the like to form a data set; s3, writing a start file into the current data set, storing the scene and logic loaded and executed firstly, and forming a data set; s4, symmetrically encrypting each data in the current data set, obtaining a key by performing hash operation on the data file name, and forming a data set after encryption; compared with the prior art, the storage and analysis method does not use a common executable program as an application file, so that the difficulty of VR application development is reduced, the period is shortened, and the compatibility and the convenience of running on different VR devices are realized.

Description

Storage and analysis method of VR application file irrelevant to platform
Technical Field
The invention belongs to the technical field of VR application content development in the virtual reality industry, and particularly relates to a method for storing and analyzing VR application files independent of a platform.
Background
Virtual reality is abbreviated as VR, and the VR technology is an important direction of virtual simulation technology. The VR technology has huge application fields and huge market prospects, at present, the VR technology is widely applied to various industries such as education, industry, medical treatment, tourism, electric power, fire protection, military and the like, and development of VR application is one of key links in the VR technology and is an important link for docking VR with various application fields; at present, VR application development is mainly an extension of the traditional game software development technology, the development process and the final product are the same as game software, and in the development mode, VR application files do not form a file storage and analysis method special for VR, but adopt an executable file form of general software.
The development process of the executable file of the general software needs professional software developers to participate, the technological process of the traditional software engineering is adopted, and a special tool chain for software development is used, so that the threshold is high, the difficulty is high, and the period is long. The finally formed VR application file is platform-dependent and can only run on a certain system platform or a certain VR hardware device. Relying entirely on the operating system and hardware environment. An application developed under one operating system cannot run when being placed under another operating system, and aiming at the application developed by one VR hardware device, the application cannot be used for other VR hardware devices, and multiple types of data including textures, materials, 3D models, scenes, scripts, interactive logic and the like need to be stored in one VR application file; at present, a resource packaging mode used in a traditional game is mostly adopted for VR application files, and a logic aspect is that a native executable file of an operating system is generated by programming and compiling source codes. Platform independence and device independence cannot be achieved.
Disclosure of Invention
Compared with the prior art, the storage and analysis method does not use a common executable program as the application file any more, so that the difficulty of VR application development is reduced, the period is shortened, and the compatibility and the convenience of running on different VR devices are realized.
The technical scheme adopted by the invention is as follows:
a method for storing a VR application file independent of a platform comprises the following operation steps:
s1, storing all edited data in the same file directory to form a data set { D0, D1, D2, … … };
s2, writing project global configuration data Setting into the current data set to establish a subset, wherein the Setting subset stores drawing board configuration data, rendering configuration data and the like to form a subset database { Setting, D0, D1, D2, … … };
s3, writing a Boot file Boot into the current data set, establishing a Boot database, wherein the database stores the scene and logic loaded and executed firstly, and forming a Boot data cluster { Boot, Setting, D0, D1, D2, … … };
s4, symmetrically encrypting each data in the current data set, obtaining the key through carrying out hash operation on the data file name, and forming an encrypted data set { EBoot, ESetting, E0, E1, E2, … … } after encryption;
s5, generating an encrypted VR application file, and continuing to execute S6;
s6, wherein the value of the data verType module is assigned to be 3;
s7, symmetrically encrypting the data in the current data set, replacing each version number ver of the key once, namely the known ver, determining the content of the key, and forming an EZ data set base { EZData } after encryption;
and S8, writing the data set of the current EZ data set library into a file, firstly writing a Header module, and then writing an EZData module to form a final VR application file of an encrypted version.
As a preferred technical solution, the storage format of the VR application file further includes: and VR application files of Debug version and Release version.
According to a further preferable technical scheme, a Debug version VR application file is generated, a verType module value is given as 1, and after the steps from S1 to S3 are completed in the operation, the following operation steps are executed:
compressing and packaging a current Boot data cluster data set by using a Zip algorithm to form a file, and recording the file as a ZD data set database { ZDdata };
and writing the current ZD data set database data set into a file, firstly writing a Header module, and then writing an EZDdata module to form a final Debug VR application file.
According to a further preferable technical scheme, a Release VR application file is generated, a verType module value is given as 2, and after the steps from S1 to S3 are completed in the operation, the following operation steps are executed:
constructing a file header, wherein data comprises 3 bytes of a file type identification module VPP, 4 bytes of a file version number module ver, 1 byte of a file version type module verType and 4 bytes of a data block length module dataLength, and forming a data block with the length of 12 bytes:
the method comprises the following steps of (1) finally forming a data set { Header, EZData }, wherein the Header { "VPP", ver, verType and dataLength };
and writing the data set in the current database into a file, firstly writing a Header module, and then writing an EZDdata module to form a final Release VR application file.
In a further preferred embodiment, the storage method of the VR application file is edited in a VR editor.
A method for analyzing a VR application file irrelevant to a platform is used for analyzing a format file stored by a VR application file storage method, and comprises the following steps:
a1, opening the file, if the length of the file is less than 12 bytes, the file format is wrong, and the process is finished;
a2, reading Header data Header module { tag, ver, verType, dataLength }, 4 variables are: the version type identification module is 3 bytes, the file version number module is 4 bytes, the file version type module is 1 byte, and the data length module is 4 bytes;
a3, if the tag module VPP value is the file type identification module and the data length module dataLength value is more than or equal to 0, continuing to execute A4, otherwise, the file format is wrong, and ending;
a4, reading the length data of the data length module to form a current data EZData database;
a5, judging the file version type, if the verType module value is 3, continuing to execute A6, otherwise, jumping to A7;
a6, inquiring the key dictionary according to the value of the ver module, decrypting the current data by using the key, and defining the new current data as a ZData database;
a7, decompressing the current data by using an Unzip algorithm to obtain a current algorithm data cluster;
a8, judging the file version type, if the verType module value is 3 or 2, continuing to execute A9, otherwise, jumping to A10;
a9, carrying out hash operation on the file name of each file in the data set of the current algorithm data cluster to obtain a key, and decrypting the data by using the key to obtain the current data set;
a10, judging the file version type, if the value of the verType module is 3, 2 or 1, continuing to execute A11, otherwise, the file format is wrong, and ending;
a11, reading the data of the subset database, and setting the state of the canvas and the rendering parameter data;
a12, reading Boot data cluster, and obtaining a starting scene and starting logic data;
and A13, loading the scene and the interactive logic parameters, and finally completing the analysis of the VR application file.
In a further preferred embodiment, the VR application file parsing method is performed by parsing the VR player.
In summary, due to the adoption of the technical scheme, the invention has the beneficial effects that:
1. compared with the prior art, the VR application file format special for VR is designed, common executable programs are not used as application files, the difficulty of VR application development is reduced, the period is shortened, the VR application files are irrelevant to a system platform and can be operated on various platforms such as Windows, Android and Web browsers, the VR application files are irrelevant to hardware equipment and can be operated on different VR equipment;
2. the invention also designs 3 file version types according to the type and the characteristics of VR data, which is convenient for different links of development, Release and the like, the data format of the file, the file type identifier at the head of the file uses VPP, the file version type identifier is stored at the head of the file, 1 represents a Debug version, 2 represents a Release version, 3 represents an encryption version, the file adopts a double-layer data encryption method, the encryption key of each subdata file is different and is obtained by carrying out Hash operation on the file name, and the whole encryption key of the data can be obtained by inquiring a key dictionary through the file version number. Before encryption, data files such as textures, materials, 3D models, scenes, interactive logic and the like are organized, configuration files are stored in a Setting subfile, and starting data are stored in a Boot subfile;
3. the VR application file storage method and the analysis method provided by the invention can integrate an algorithm into corresponding software through programming, for example, the storage method is added into a VR editor, and the analysis method is added into a VR player or a VR virtual machine, so that the software can support the VR application file format;
4. the file data of the invention is divided into 2 parts, file header and body data, read and analyze the file header first, analyze the body data according to the file header data, judge whether the file identifier is "VPP" first, read the type identifier of file version again, the encrypted version needs to decipher and decompress the data entirety first then decipher the single data file, Release version can decompress the data entirety directly, only need to decipher the single data file, Debug version decompresses the data entirety directly, does not need to decipher, the key acquisition method of the decipherment is an important key point; the file operation system platform is irrelevant to hardware equipment, the canvas and the rendering parameters are set according to Setting data during operation, and then the first scene and the interactive logic are loaded according to Boot data.
Drawings
FIG. 1 is a schematic flow chart of a VR application file storage method according to the present invention;
fig. 2 is a flowchart of a VR application file parsing method according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail with reference to the following embodiments.
As shown in conjunction with FIGS. 1-2;
the invention relates to a storage method of VR application files irrelevant to a platform, which designs a VR application file format special for VR, compared with the prior art, common executable programs are not used as application files any more, so that the difficulty of VR application development is reduced, the period is shortened, VR application files are irrelevant to a system platform and can run on various platforms such as Windows, Android and Web browsers, and VR application files are irrelevant to hardware equipment and can run on different VR equipment, and the storage method of VR application files comprises the following operation steps:
s1, storing all edited data in the same file directory to form a data set { D0, D1, D2, … … };
s2, writing project global configuration data Setting into the current data set to establish a subset, wherein the Setting subset stores drawing board configuration data, rendering configuration data and the like to form a subset database { Setting, D0, D1, D2, … … };
s3, writing a Boot file Boot into the current data set, establishing a Boot database, wherein the database stores the scene and logic loaded and executed firstly, and forming a Boot data cluster { Boot, Setting, D0, D1, D2, … … };
s4, symmetrically encrypting each data in the current data set, obtaining the key through carrying out hash operation on the data file name, and forming an encrypted data set { EBoot, ESetting, E0, E1, E2, … … } after encryption;
s5, generating an encrypted VR application file, and continuing to execute S6;
s6, wherein the value of the data verType module is assigned to be 3;
s7, symmetrically encrypting the data in the current data set, replacing each version number ver of the key once, namely the known ver, determining the content of the key, and forming an EZ data set base { EZData } after encryption;
and S8, writing the data set of the current EZ data set library into a file, firstly writing a Header module, and then writing an EZData module to form a final VR application file of an encrypted version.
The invention also designs 3 file version types according to the type and the characteristics of VR data, which is convenient for different links of development, Release and the like, the data format of the file, the file type identifier at the head of the file uses VPP, the file version type identifier is stored at the head of the file, 1 represents a Debug version, 2 represents a Release version, 3 represents an encryption version, the file adopts a double-layer data encryption method, the encryption key of each subdata file is different and is obtained by carrying out Hash operation on the file name, and the whole encryption key of the data can be obtained by inquiring a key dictionary through the file version number. Before encryption, data files such as textures, materials, 3D models, scenes, interactive logic and the like are organized, configuration files are stored in a Setting subfile, and starting data are stored in a Boot subfile.
As a preferred technical solution, the storage format of the VR application file further includes: and VR application files of Debug version and Release version.
According to a further preferable technical scheme, a Debug version VR application file is generated, a verType module value is given as 1, and after the steps from S1 to S3 are completed in the operation, the following operation steps are executed:
compressing and packaging a current Boot data cluster data set by using a Zip algorithm to form a file, and recording the file as a ZD data set database { ZDdata };
and writing the current ZD data set database data set into a file, firstly writing a Header module, and then writing an EZDdata module to form a final Debug VR application file.
According to a further preferable technical scheme, a Release VR application file is generated, a verType module value is given as 2, and after the steps from S1 to S3 are completed in the operation, the following operation steps are executed:
constructing a file header, wherein data comprises 3 bytes of a file type identification module VPP, 4 bytes of a file version number module ver, 1 byte of a file version type module verType and 4 bytes of a data block length module dataLength, and forming a data block with the length of 12 bytes:
the method comprises the following steps of (1) finally forming a data set { Header, EZData }, wherein the Header { "VPP", ver, verType and dataLength };
and writing the data set in the current database into a file, firstly writing a Header module, and then writing an EZDdata module to form a final Release VR application file.
In a further preferred embodiment, the VR application file storage method is implemented by processing and editing in a VR editor.
A method for analyzing a VR application file irrelevant to a platform is used for analyzing a format file stored by a VR application file storage method, and comprises the following steps:
a1, opening the file, if the length of the file is less than 12 bytes, the file format is wrong, and the process is finished;
a2, reading Header data Header module { tag, ver, verType, dataLength }, 4 variables are: the version type identification module is 3 bytes, the file version number module is 4 bytes, the file version type module is 1 byte, and the data length module is 4 bytes;
a3, if the tag module VPP value is the file type identification module and the data length module dataLength value is more than or equal to 0, continuing to execute A4, otherwise, the file format is wrong, and ending;
a4, reading the length data of the data length module to form a current data EZData database;
a5, judging the file version type, if the verType module value is 3, continuing to execute A6, otherwise, jumping to A7;
a6, inquiring the key dictionary according to the value of the ver module, decrypting the current data by using the key, and defining the new current data as a ZData database;
a7, decompressing the current data by using an Unzip algorithm to obtain a current algorithm data cluster;
a8, judging the file version type, if the verType module value is 3 or 2, continuing to execute A9, otherwise, jumping to A10;
a9, carrying out hash operation on the file name of each file in the data set of the current algorithm data cluster to obtain a key, and decrypting the data by using the key to obtain the current data set;
a10, judging the file version type, if the value of the verType module is 3, 2 or 1, continuing to execute A11, otherwise, the file format is wrong, and ending;
a11, reading the data of the subset database, and setting the state of the canvas and the rendering parameter data;
a12, reading Boot data cluster, and obtaining a starting scene and starting logic data;
and A13, loading the scene and the interactive logic parameters, and finally completing the analysis of the VR application file.
Furthermore, the analysis method of the VR application file is analyzed and processed by a VR player, and the storage method and the analysis method of the VR application file provided by the invention can integrate an algorithm into corresponding software through programming, for example, the storage method is added into a VR editor, and the analysis method is added into the VR player or a VR virtual machine, so that the software can support the VR application file format.
The file data of the invention is divided into 2 parts, file header and body data, read and analyze the file header first, analyze the body data according to the file header data, judge whether the file identifier is "VPP" first, read the type identifier of file version again, the encrypted version needs to decipher and decompress the data entirety first then decipher the single data file, Release version can decompress the data entirety directly, only need to decipher the single data file, Debug version decompresses the data entirety directly, does not need to decipher, the key acquisition method of the decipherment is an important key point; the file operation system platform is irrelevant to hardware equipment, the canvas and the rendering parameters are set according to Setting data during operation, and then the first scene and the interactive logic are loaded according to Boot data.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents and improvements made within the spirit and principle of the present invention are intended to be included within the scope of the present invention.

Claims (7)

1. A storage method of a VR application file irrelevant to a platform is characterized in that:
the storage method of the VR application file comprises the following operation steps:
s1, storing all edited data in the same file directory to form a data set { D0, D1, D2, … … };
s2, writing project global configuration data into the current data set to establish a subset, storing drawing board configuration data and rendering configuration data in the subset, and forming a subset database;
s3, writing a Boot file Boot into the current data subset, establishing a Boot database, wherein the database stores the scene and logic loaded and executed firstly, and forming a Boot data cluster;
s4, symmetrically encrypting each data in the current Boot data cluster, obtaining a key by performing hash operation on a data file name, and forming an encrypted data set after encryption;
s5, generating an encrypted VR application file, and continuing to execute S6;
s6, wherein the value of the data verType module is assigned to be 3;
s7, symmetrically encrypting the data in the current data set, replacing each version number ver of the key once, namely the known ver, determining the content of the key, and forming an EZ data set library after encryption;
and S8, writing the data set of the current EZ data set library into a file, firstly writing a Header module, and then writing an EZData module to form a final VR application file of an encrypted version.
2. The method of claim 1, wherein the method for storing the VR application file is implemented by: the storage format of the VR application file further comprises: debug version and Release version.
3. The method of claim 2, wherein the method for storing the VR application file is implemented by: generating a Debug version VR application file, assigning the value of the data verType module as 1, and after the steps S1-S3 are completed in the operation, executing the following operation steps:
compressing and packaging a current Boot data cluster data set by using a Zip algorithm to form a file, and recording the file as a ZD data set library;
and writing the current ZD data set database data set into a file, firstly writing a Header module, and then writing an EZDdata module to form a final Debug VR application file.
4. The method of claim 2, wherein the method for storing the VR application file is implemented by: and generating a VR application file of a Release version, assigning a data verType module value as 2, and after the steps from S1 to S3 are completed in the operation, executing the following operation steps:
constructing a file header, wherein data comprises 3 bytes of a file type identification module, 4 bytes of a file version number module, 1 byte of a file version type module and 4 bytes of a data block length module to form a data block with the length of 12 bytes;
and writing the data set in the current database into a file, firstly writing a Header module, and then writing an EZDdata module to form a final Release VR application file.
5. The method for storing the platform-independent VR application file of claim 1, 2, 3 or 4, wherein the method further comprises: and the storage method of the VR application file processes editing in a VR editor.
6. A method for analyzing a VR application file independent of a platform is used for analyzing a format file stored by a VR application file storage method, and is characterized in that: the method comprises the following analysis steps:
a1, opening the file, if the length of the file is less than 12 bytes, the file format is wrong, and the process is finished;
a2, reading a Header data Header module, wherein 4 variables are respectively: the version type identification module is 3 bytes, the file version number module is 4 bytes, the file version type module is 1 byte, and the data length module is 4 bytes;
a3, if the tag module value is the file type identification module and the assignment of the data length module is more than or equal to 0, continuing to execute A4, otherwise, the file format is wrong, and ending;
a4, reading the length data of the data length module to form a current data EZData database;
a5, judging the file version type, if the verType module value is 3, continuing to execute A6, otherwise, jumping to A7;
a6, inquiring the key dictionary according to the value of the ver module, decrypting the current data by using the key, and defining the new current data as a ZData database;
a7, decompressing the current data by using an Unzip algorithm to obtain a current algorithm data cluster;
a8, judging the file version type, if the verType module value is 3 or 2, continuing to execute A9, otherwise, jumping to A10;
a9, carrying out hash operation on the file name of each file in the data set of the current algorithm data cluster to obtain a key, and decrypting the data by using the key to obtain the current data set;
a10, judging the file version type, if the value of the verType module is 3, 2 or 1, continuing to execute A11, otherwise, the file format is wrong, and ending;
a11, reading the data of the subset database, and setting the state of the canvas and the rendering parameter data;
a12, reading Boot data cluster, and obtaining a starting scene and starting logic data;
and A13, loading the scene and the interactive logic parameters, and finally completing the analysis of the VR application file.
7. The method of claim 6, wherein the method for parsing the VR application file is performed by: and the analysis method of the VR application file is analyzed and processed by a VR player.
CN202110805123.2A 2021-07-15 2021-07-15 Storage and analysis method of VR application file irrelevant to platform Pending CN113468106A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110805123.2A CN113468106A (en) 2021-07-15 2021-07-15 Storage and analysis method of VR application file irrelevant to platform

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110805123.2A CN113468106A (en) 2021-07-15 2021-07-15 Storage and analysis method of VR application file irrelevant to platform

Publications (1)

Publication Number Publication Date
CN113468106A true CN113468106A (en) 2021-10-01

Family

ID=77880573

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110805123.2A Pending CN113468106A (en) 2021-07-15 2021-07-15 Storage and analysis method of VR application file irrelevant to platform

Country Status (1)

Country Link
CN (1) CN113468106A (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120057707A1 (en) * 2010-09-03 2012-03-08 Fang Ko Cheng Method of abolishing unauthorized copying of digital data stored on an optical disc
CN103701829A (en) * 2014-01-03 2014-04-02 厦门市美亚柏科信息股份有限公司 Method of off-line analyzing DPAPI (Data Protection Application Programming Interface) enciphered data
WO2014187168A1 (en) * 2013-05-22 2014-11-27 福建联迪商用设备有限公司 Information storage and management method and apparatus based on webkit browser
CN110990084A (en) * 2019-12-20 2020-04-10 紫光展讯通信(惠州)有限公司 Chip secure starting method and device, storage medium and terminal
CN111262705A (en) * 2020-01-15 2020-06-09 西安理工大学 Method for checking block chain trusted boot
CN112612528A (en) * 2020-12-30 2021-04-06 卡斯柯信号有限公司 System software selective starting and remote updating method based on Bootloader

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120057707A1 (en) * 2010-09-03 2012-03-08 Fang Ko Cheng Method of abolishing unauthorized copying of digital data stored on an optical disc
WO2014187168A1 (en) * 2013-05-22 2014-11-27 福建联迪商用设备有限公司 Information storage and management method and apparatus based on webkit browser
CN103701829A (en) * 2014-01-03 2014-04-02 厦门市美亚柏科信息股份有限公司 Method of off-line analyzing DPAPI (Data Protection Application Programming Interface) enciphered data
CN110990084A (en) * 2019-12-20 2020-04-10 紫光展讯通信(惠州)有限公司 Chip secure starting method and device, storage medium and terminal
CN111262705A (en) * 2020-01-15 2020-06-09 西安理工大学 Method for checking block chain trusted boot
CN112612528A (en) * 2020-12-30 2021-04-06 卡斯柯信号有限公司 System software selective starting and remote updating method based on Bootloader

Similar Documents

Publication Publication Date Title
CN108469955B (en) Annotation-based Android injection framework implementation method
CN109032577B (en) Data simulation method
CN111985055B (en) Model packaging method and device and electronic equipment
CN107797805B (en) Code packaging method and device and computer readable storage medium
CN110442371A (en) A kind of method, apparatus of release code, medium and computer equipment
CN115544490A (en) Method and system for detecting password constant in binary file
CN112835587B (en) Compiling integration method and device
CN113468106A (en) Storage and analysis method of VR application file irrelevant to platform
CN112965720A (en) Component compiling method, device, equipment and computer readable storage medium
CN115904480B (en) Code reconstruction method, device, electronic equipment and storage medium
CN111414107A (en) Scalable vector graphics processing method and system
CN111930387B (en) Integration method and device of integration package, electronic equipment and storage medium
JPH0194431A (en) Software parts synthesizer
CN114661298A (en) Automatic public method generation method, system, device and medium
US8010572B1 (en) Kstore scenario simulator processor and XML file
US9274929B2 (en) Constraint derivation in context following for use with object code insertion
CN111143182B (en) Analysis method, device and storage medium for process behavior
CN114527984A (en) Shader generation method and device, player and storage medium
CN114816972A (en) Coloring language testing method and device, electronic equipment and storage medium
CN113448874A (en) Method and device for generating unit test script
JP2000066889A (en) Method and device for supplying difference between source code and design information
CN112312630A (en) Data processing method and device
CN108390850B (en) Data processing method and device, electronic equipment and server
Bangert et al. Nail: A practical interface generator for data formats
CN110968342B (en) Version comparison method, device and system

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination