CN116541024B - Static deployment method for software communication architecture - Google Patents
Static deployment method for software communication architecture Download PDFInfo
- Publication number
- CN116541024B CN116541024B CN202310826429.5A CN202310826429A CN116541024B CN 116541024 B CN116541024 B CN 116541024B CN 202310826429 A CN202310826429 A CN 202310826429A CN 116541024 B CN116541024 B CN 116541024B
- Authority
- CN
- China
- Prior art keywords
- deployment
- model
- platform
- created
- models
- 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
- 230000003068 static effect Effects 0.000 title claims abstract description 41
- 238000000034 method Methods 0.000 title claims abstract description 34
- 238000013507 mapping Methods 0.000 claims abstract description 7
- 230000008569 process Effects 0.000 claims description 12
- 238000004891 communication Methods 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 3
- 238000005457 optimization Methods 0.000 description 3
- 238000007781 pre-processing Methods 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 238000013468 resource allocation Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application relates to a static deployment method for a software communication architecture, comprising the steps of: creating a basic model: creating various element models in the basic model; creating a deployment model: creating a configuration interface and a deployment interface; generating a platform deployment description file: according to the mapping relation among the element models in the deployment model, the names of the deployment models and the deployment relation among the element models are described; creating an application component instance: after the platform deployment description file is analyzed, an application component instance is created on the target platform according to the names of the deployment models in the platform deployment description file and the deployment relation among the element models; deployment: and deploying the application component examples on the target platform according to the association relation among the element examples. The method and the device can create a deployment model according to the needs of the user and deploy the appointed application components on the appointed executable equipment so as to meet different needs of the user.
Description
Technical Field
The present application relates to a static deployment method for a software communication architecture, in particular for a software communication architecture and based on device sequence allocation.
Background
The Software Communication Architecture (SCA) is a communication system design framework based on Joint Tactical Radio System (JTRS) and aimed at implementing a software radio system platform, and is one of the most widely used communication system frameworks in several current software radio architectures.
In SCA, deployment refers to deploying application and service implementations onto a target platform and ensuring that they can communicate and cooperate with each other, and therefore deployment is an essential step of SCA architecture implementation. Meanwhile, SCA also provides consistency and portability in deployment to support cross-platform interaction and reuse of application programs and services, so SCA and deployment are closely related and are the basis for realizing reliable, efficient and extensible distributed application programs and services.
In the SCA, the current deployment mode adopts dynamic deployment, and the dynamic deployment means that a system automatically decides which device to deploy an application component on according to the priority of each device and the capacities of the application component and the device, so that the system has certain flexibility and can improve the resource utilization rate. However, this approach has the disadvantage that if the user wants to deploy the specified application program on the specified executable device, the priority setting in the device bottom source code needs to be changed, which is difficult for the user to use, and in addition, the dynamic loading and resource allocation of the application component are involved in the dynamic deployment process, which increases the replicability of the system implementation and has high requirements on the system performance. Dynamic deployment therefore has the limitations and drawbacks described above in practical applications.
Disclosure of Invention
The application provides a static deployment method for a software communication system structure, through static deployment, a user can create a deployment model according to the needs of the user, and a designated application component is deployed on designated executable equipment so as to meet different needs of the user.
The application relates to a static deployment method for a software communication system structure, which comprises the following steps:
creating a basic model: creating various element models required by static deployment in a basic model;
creating a deployment model: according to element models in the basic model, a configuration interface and a deployment interface are created, wherein the configuration interface is used for explaining element models required in a static deployment process, and the deployment interface is used for explaining mapping relations among element models after deployment;
generating a platform deployment description file: according to the mapping relation among the element models in the deployment model, the names of the deployment models and the deployment relation among the element models are described in a file form;
creating an application component instance: after the platform deployment description file is analyzed, an application component instance is created on the target platform through a function according to the names of the deployment models in the platform deployment description file and the deployment relation among the element models;
deployment: after the element examples are created, the application component examples are deployed on a target platform according to the association relation among the element examples.
Through testing, the static deployment method has good reliability, the deployment model is created in the modeling process, the deployment condition can be simulated, and some human errors in the actual deployment process, such as no executable equipment in a platform, failure in deployment, and the like, are avoided. System performance can be improved by static deployment, because optimization can be performed by compiling, preprocessing, linking code, and the like in the static deployment. At the same time, static deployment has good security, and the possibility of attacking the system is obviously reduced because it is clear at deployment time which application components should be run. Static deployment also facilitates debugging and maintenance, which can be more easily tested, debugged and maintained since the application component copies produced by static deployment are relatively few (typically used by only developers and testers). Static deployment may also ignore priority settings within the device, facilitating deployment of the specified application components on the specified device.
Preferably, before generating the platform deployment description file, the created base model and deployment model are validated to verify compliance with SCA (software communications architecture) standards and SRTF (software radio communications equipment architecture) specifications, and whether the port connections between the element models match. The method can be used for verification in the existing algorithm mode and the like so as to improve the safety and standardization of deployment and later operation.
Specifically, when the basic model is created, the created element model comprises a device model, a node model, a platform model, an application component model and an application waveform model, and when the device model and the application component model are created, the element model comprises the attribute, the interface, the port and the implementation of the device model and the application component model.
On the basis, in a configuration interface of the deployment model, the deployment model comprises a platform model and at least one application waveform model, wherein the platform model comprises at least one node model, and each node model comprises at least one equipment model; at least one application component model is included under the application waveform model. The dependencies between the various element models are defined through the configuration interface.
Preferably, in the step of generating the platform deployment description file, the names of the deployment models and the deployment relations among the element models are described by generating the XML format file. The XML format file is a text format which is common to various systems at present, and has the advantages of readability, universality and the like.
Specifically, in the step of generating a platform deployment description file, a calling function initializes a built deployment model name array, creates a storage object, adds an XML statement to the storage object, then circularly traverses the deployment model names in the deployment model name array to obtain an application program list associated with each deployment model name, and then traverses the application program list to obtain an application component list on which each application program depends, traverses each application component list, creates a device allocation element for each application component list, sets a relevant attribute value for the device allocation element, then adds all the device allocation elements to the device allocation array, finally adds the device allocation array to a final reconstruction element, and adds all contents in the reconstruction element to a pdd.xml file, wherein the pdd.xml file is the platform deployment description file.
Further, when the element instance is created in the deployment step, after the platform deployment description file is parsed, the element instance which is mutually related is created on the target platform through the equipment allocation sequence.
Specifically, when using the device allocation sequence, verifying the correctness of the device allocation sequence to the device allocation by a function and returning to the allocated effective device; if the device allocation is correct and valid, the corresponding information is saved and the corresponding element instance is associated. Thereby ensuring the correctness of the association between the element instances.
Further, in the deployment step, names of all deployment models corresponding to the created element examples are displayed for the user to select, and after the user selects the deployment model name to be deployed, the deployment step is performed on the target platform according to the association relationship between the element examples created based on the equipment allocation sequence. The user can select different deployment models to deploy according to the needs, so that the deployment has more flexibility.
The beneficial effects of the application include:
1. through static deployment, a user can create a deployment model according to the needs of the user, and a designated application component is deployed on designated equipment, so that different needs of the user are met.
2. By using static deployment, deployment is only carried out according to the deployment relation in the platform deployment description file in the deployment process, and dynamic resource allocation is not required to be invoked, so that the operation efficiency is improved.
3. The method has good reliability, the deployment model is created in the modeling process, the deployment condition can be simulated, and some human errors in the actual deployment process, such as no executable equipment in the platform, failure in deployment and the like, are avoided.
4. The system performance is improved, and optimization can be performed by means of compiling, preprocessing, linking codes and the like in static deployment. At the same time, static deployment has good security, and the possibility of attacking the system is obviously reduced because it is clear at deployment time which application components should be run.
5. The system is convenient for debugging and maintenance, and the application component copy generated by static deployment is relatively few (usually only used by developers and testers), so that the system can be tested, debugged and maintained more easily.
6. Ignoring the priority settings inside the device facilitates the deployment of the specified application components on the specified device.
Drawings
FIG. 1 is a flow chart of a static deployment method for a software communication architecture of the present application.
FIG. 2 is a block diagram of a deployment model of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the application, as presented in the figures, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by a person skilled in the art without making any inventive effort, are intended to be within the scope of the present application.
Example 1:
as shown in fig. 1, the static deployment method for the software communication architecture of the present application comprises the steps of:
creating a basic model: creating various element models required by static deployment in a basic model;
creating a deployment model: according to element models in the basic model, a configuration interface and a deployment interface are created, wherein the configuration interface is used for describing element models required in a static deployment process, and the deployment interface is used for describing mapping relations among element models after deployment, namely, the deployment interface is used for describing how the element models are deployed;
generating a platform deployment description file: according to the mapping relation among the element models in the deployment model, the names of the deployment models and the deployment relation among the element models are described in a file form;
creating an application component instance: after the platform deployment description file is analyzed, an application component instance is created on the target platform through a function according to the names of the deployment models in the platform deployment description file and the deployment relation among the element models;
deployment: after the element examples are created, the application component examples are deployed on a target platform according to the association relation among the element examples.
Through testing, the static deployment method has good reliability, the deployment model is created in the modeling process, the deployment condition can be simulated, and some human errors in the actual deployment process, such as no executable equipment in a platform, failure in deployment, and the like, are avoided. System performance can be improved by static deployment, because optimization can be performed by compiling, preprocessing, linking code, and the like in the static deployment. At the same time, static deployment has good security, and the possibility of attacking the system is obviously reduced because it is clear at deployment time which application components should be run. Static deployment also facilitates debugging and maintenance, which can be more easily tested, debugged and maintained since the application component copies produced by static deployment are relatively few (typically used by only developers and testers). Static deployment may also ignore priority settings within the device, facilitating deployment of the specified application components on the specified device.
Example 2:
on the basis of embodiment 1, before generating the platform deployment description file, the created base model and deployment model are also verified to verify whether they conform to the SCA (software communication architecture) standard and the SRTF (software radio communication equipment architecture) specification, and whether the port connections between the element models match. The method can be used for verification in the existing algorithm mode and the like so as to improve the safety and standardization of deployment and later operation.
Example 3:
on the basis of the above embodiment, when the basic model is created, the created element model includes a device model, a node model, a platform model, an application component model and an application waveform model, and when the device model and the application component model are created, the created element model includes attributes, interfaces, ports and implementations of the device model and the application component model.
As shown in fig. 2, in the configuration interface of the deployment model, a platform model and an application waveform model (may also be multiple application waveform models), where a node model 1 and a node model 2 (may also be one or more node models) are included under the platform model, an equipment model 11 and an equipment model 12 are included under the node model 1, an equipment model 21 and an equipment model 22 are included under the node model 2, and one or more equipment models are included under each node model; at least one application component model is included under the application waveform model, and an application component model 1 and an application component model 2 are shown in fig. 2. The dependencies between the various element models are defined through the configuration interface.
Then, in the deployment interface, the application waveform model in the configuration interface needs to be deployed onto the device model 12, so that the application component model 1 and the application component model 2 corresponding to the application waveform model are respectively associated with the device model 12.
The creation of the element models can be realized through the prior art, and the part is not the innovation of the application.
Example 4:
on the basis of the above embodiment, in the step of generating the platform deployment description file, the names of the deployment models are described by generating a file in XML format, for example, a. Pdd. XML file, and the deployment relationship between the element models are generated. The XML format file is a text format which is common to various systems at present, and has the advantages of readability, universality and the like. The following describes the generation process of the platform deployment description file through a specific embodiment:
(1) The function 'initDeployments ()' is called to initialize the constructed deployment model name array 'depoyments';
(2) A storage object is created and XML declarations are added to the storage object, and the storage object is also used for storing IDs and names of various element models. Then circularly traversing the deployment model names in the deployment model name array 'depth' to obtain an application program list associated with each deployment model name;
(3) Traversing the application program list to obtain an application component list on which each application program depends;
(4) Traversing each application component list, creating a device allocation element 'deviceAssignment' for each application component list, and setting a related attribute value for the device allocation element 'deviceAssignment';
(5) Adding all the device allocation elements 'deviceAssignment' into a device allocation array 'deviceAssignment';
(6) And finally, adding the device allocation array 'deviceAssignments' to a final reconstruction element 'softwasasssembly', and adding all contents in the reconstruction element 'softwasasssembly' to a devicevolxml file which is the platform deployment description file.
After the system analyzes the platform deployment description file, an element instance which is mutually related is created on a target board card (target platform) through a device distribution sequence. When using the device allocation sequence, the correctness of the device allocation sequence to the device allocation is verified through a function and the allocated valid devices are returned. The function accepts four input parameters: appFactory, resolver, devices and deviceAssignments. Wherein, appfactor represents an application factory instance; resolvers represent dependency resolvers for establishing relationships between application components and devices; devices represent all available devices; deviceassignment means that a given device allocation array. During verification, the function allocates an array for storing effectively allocated devices, application component instances and resource implementations, and then traverses each element in the deviceAssignments and verifies the validity of each allocated device and application component instance using the softwaseassembly reference in appfactor. If the allocation is correct and valid, storing the information of the object, the application component ID, the device ID and the like of the device into an allocated array, and finally associating the corresponding device with the application component instance through the function.
When in deployment, displaying the names of all deployment models corresponding to the created application component examples for users to select, if only one deployment model is created before, only one option of the deployment model name is displayed, and if a plurality of deployment models are created before, the options of the plurality of deployment model names can be selected. After a user selects a deployment model name to be deployed, the system creates an instance of each element model in the deployment model on the target board card according to the association relation between each element instance created based on the equipment allocation sequence, and deploys the instances. Thereby making deployment more flexible.
The above examples merely illustrate specific embodiments of the application, which are described in more detail and are not to be construed as limiting the scope of the application. It should be noted that, for those skilled in the art, it is possible to make related modifications and improvements without departing from the technical idea of the application, which fall within the protection scope of the application.
Claims (7)
1. A static deployment method for a software communication architecture, comprising the steps of:
creating a basic model: creating various element models required by static deployment in a basic model;
creating a deployment model: according to element models in the basic model, a configuration interface and a deployment interface are created, wherein the configuration interface is used for explaining element models required in a static deployment process, and the deployment interface is used for explaining mapping relations among element models after deployment;
generating a platform deployment description file: according to the mapping relation among element models in the deployment model, the names of the deployment models and the deployment relation among the element models are described by generating a file form in an XML format; comprising the following steps:
the method comprises the steps of initializing a built deployment model name array by a calling function, creating a storage object, adding an XML statement into the storage object, circularly traversing the deployment model names in the deployment model name array to obtain application program lists associated with each deployment model name, traversing the application program lists to obtain application component lists on which each application program depends, traversing each application component list, creating a device allocation element for each application component list, setting a relevant attribute value for the device allocation element, adding all the device allocation elements into the device allocation array, finally adding the device allocation array into a final reconstruction element, and adding all contents in the reconstruction element into a pdd.xml file, wherein the pdd.xml file is the platform deployment description file;
creating an application component instance: after the platform deployment description file is analyzed, an application component instance is created on the target platform through a function according to the names of the deployment models in the platform deployment description file and the deployment relation among the element models;
deployment: after the element examples are created, the application component examples are deployed on a target platform according to the association relation among the element examples.
2. The static deployment method for a software communication architecture of claim 1, wherein: before generating the platform deployment description file, verifying the created basic model and the deployment model to verify whether the created basic model and the deployment model accord with the SCA standard SRTF specification and whether port connection among the element models is matched.
3. The static deployment method for a software communication architecture of claim 1, wherein: the created element models comprise a device model, a node model, a platform model, an application component model and an application waveform model when the basic model is created, and the attributes, interfaces, ports and implementations of the device model and the application component model when the device model and the application component model are created.
4. A static deployment method for a software communication architecture according to claim 3, wherein: the configuration interface of the deployment model comprises a platform model and at least one application waveform model, wherein the platform model comprises at least one node model, and each node model comprises at least one equipment model; at least one application component model is included under the application waveform model.
5. The static deployment method for a software communication architecture of claim 1, wherein: when the element instance is created in the deployment step, after the platform deployment description file is analyzed, the element instance which is mutually related is created on the target platform through the equipment distribution sequence.
6. The static deployment method for a software communication architecture according to claim 5, wherein: when using the device allocation sequence, verifying the correctness of the device allocation sequence to the device allocation by a function and returning the allocated effective devices; if the device allocation is correct and valid, the corresponding information is saved and the corresponding element instance is associated.
7. The static deployment method for a software communication architecture according to claim 5, wherein: in the deployment step, names of all deployment models corresponding to the created element examples are displayed for a user to select, and after the user selects the deployment model name to be deployed, the deployment step is carried out on the target platform according to the association relation among the element examples created based on the equipment allocation sequence.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310826429.5A CN116541024B (en) | 2023-07-07 | 2023-07-07 | Static deployment method for software communication architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310826429.5A CN116541024B (en) | 2023-07-07 | 2023-07-07 | Static deployment method for software communication architecture |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116541024A CN116541024A (en) | 2023-08-04 |
| CN116541024B true CN116541024B (en) | 2023-09-22 |
Family
ID=87452866
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310826429.5A Active CN116541024B (en) | 2023-07-07 | 2023-07-07 | Static deployment method for software communication architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116541024B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103813463A (en) * | 2014-02-13 | 2014-05-21 | 中国航空无线电电子研究所 | Resource distribution method in software communication architecture |
| CN108600369A (en) * | 2018-04-25 | 2018-09-28 | 中国人民解放军国防科技大学 | Waveform management method based on SCA core framework |
| CN111262742A (en) * | 2020-01-20 | 2020-06-09 | 中国人民解放军国防科技大学 | SCA-based dynamic partially reconfigurable equipment resource virtualization and waveform deployment method |
| CN111399828A (en) * | 2020-03-13 | 2020-07-10 | 上海介方信息技术有限公司 | Model-driven logic device modeling method and terminal |
| CN111416631A (en) * | 2020-03-04 | 2020-07-14 | 上海介方信息技术有限公司 | Waveform deployment implementation method based on waveform multistage nesting |
| CN113064737A (en) * | 2021-03-26 | 2021-07-02 | 中国航空无线电电子研究所 | Method for enabling components of software communication architecture to run in parallel on multi-core processor |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8352912B2 (en) * | 2008-12-15 | 2013-01-08 | International Business Machines Corporation | Method and system for topology modeling |
| US8719813B2 (en) * | 2011-11-29 | 2014-05-06 | Raytheon Company | Optimized SCA CORBA descriptor for SCA CORBA descriptor files |
-
2023
- 2023-07-07 CN CN202310826429.5A patent/CN116541024B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103813463A (en) * | 2014-02-13 | 2014-05-21 | 中国航空无线电电子研究所 | Resource distribution method in software communication architecture |
| CN108600369A (en) * | 2018-04-25 | 2018-09-28 | 中国人民解放军国防科技大学 | Waveform management method based on SCA core framework |
| CN111262742A (en) * | 2020-01-20 | 2020-06-09 | 中国人民解放军国防科技大学 | SCA-based dynamic partially reconfigurable equipment resource virtualization and waveform deployment method |
| CN111416631A (en) * | 2020-03-04 | 2020-07-14 | 上海介方信息技术有限公司 | Waveform deployment implementation method based on waveform multistage nesting |
| CN111399828A (en) * | 2020-03-13 | 2020-07-10 | 上海介方信息技术有限公司 | Model-driven logic device modeling method and terminal |
| CN113064737A (en) * | 2021-03-26 | 2021-07-02 | 中国航空无线电电子研究所 | Method for enabling components of software communication architecture to run in parallel on multi-core processor |
Non-Patent Citations (6)
| Title |
|---|
| A comprehensive survey on aerial mobile edge computing: Challenges, state-of-the-art, and future directions;Zhengyu Song等;Computer Communications;第191卷;第233-256页 * |
| Dynamic reconfiguration of software defined radios using standard architectures;Andrew R. Cormier 等;Physical Communication;第3卷(第2期);第73-80页 * |
| SCA核心框架优化设计技术研究;谢彬 等;计算机应用与软件(第08期);第163-166页 * |
| SDRPHY - XML description for SDR physical layer;E. Grayver等;2010 - MILCOM 2010 MILITARY COMMUNICATIONS CONFERENCE;第1140-1146页 * |
| 基于SCA的波形应用可视化编辑器设计与实现;喻希;中国优秀硕士学位论文全文数据库 信息科技辑(第4期);I138-285，摘要，第4.2-4.6节，第7.2节 * |
| 面向手持小型终端的软件无线电体系结构研究与设计;刘铮;中国优秀硕士学位论文全文数据库 信息科技辑(第3期);I136-1775 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116541024A (en) | 2023-08-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Le Traon et al. | Efficient object-oriented integration and regression testing | |
| CN110096425B (en) | QT development mode-based automatic testing method and device and storage medium | |
| CN111522734B (en) | Software function testing method and device, electronic equipment and storage medium | |
| CN111859834B (en) | UVM-based verification platform development method, system, terminal and storage medium | |
| CN113687858B (en) | Configuration file checking method and device, electronic equipment and storage medium | |
| CN111078274A (en) | Code development method and device, electronic equipment and computer storage medium | |
| CN108897588B (en) | Routing method and routing device for communication between modules | |
| CN116541024B (en) | Static deployment method for software communication architecture | |
| CN113190238A (en) | Framework deployment method and device, computer equipment and storage medium | |
| CN116719729B (en) | Universal verification platform, universal verification method, medium and electronic equipment | |
| Porter et al. | Towards model-based integration of tools and techniques for embedded control system design, verification, and implementation | |
| CN105301480A (en) | Test method of SOC chip | |
| CN109739756A (en) | The method and apparatus of mobile terminal application test | |
| CN110727601B (en) | Multi-platform program testing method and related device | |
| CN115034165A (en) | Chip simulation verification method, system, equipment and storage medium | |
| CN107015837A (en) | A kind of software kit automation is installed and collocation method and device | |
| CN101251824B (en) | Method for testing public objects request proxy structure and tools | |
| CN110414097A (en) | IMA system resource configuration verification method and system, computer readable storage medium | |
| CN110471767A (en) | A kind of dispatching method of equipment | |
| CN113608996B (en) | Mirror image compiling test method, system, device and readable storage medium | |
| CN117873650A (en) | Real-time running environment generation system, method, computer device and storage medium | |
| CN110554959A (en) | apache Ant integration method, system, terminal and storage medium | |
| CN115270485A (en) | Agile development method and system for simulation product | |
| CN114416266A (en) | Component visualization method and device, computer equipment and storage medium | |
| CN114328066A (en) | Verification method and device and electronic equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |