CN110851140B - System and method for realizing dynamic library of single chip microcomputer - Google Patents
System and method for realizing dynamic library of single chip microcomputer Download PDFInfo
- Publication number
- CN110851140B CN110851140B CN201911095291.6A CN201911095291A CN110851140B CN 110851140 B CN110851140 B CN 110851140B CN 201911095291 A CN201911095291 A CN 201911095291A CN 110851140 B CN110851140 B CN 110851140B
- Authority
- CN
- China
- Prior art keywords
- module
- driving
- function
- interface
- drive
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07G—REGISTERING THE RECEIPT OF CASH, VALUABLES, OR TOKENS
- G07G1/00—Cash registers
- G07G1/12—Cash registers electronically operated
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a system and a method for realizing a dynamic library of a singlechip, wherein the system comprises an application module, a dynamic library database and a dynamic library database, wherein the application module is used for driving a provided instruction to complete the operation required by a client; the application interface module is used for transmitting the driving function and the parameter information which need to be called by the application module to the driving interface module; the driving interface module is used for explaining the driving function and the parameter information transmitted by the application interface module, calling the corresponding driving function and transmitting the parameter information which is released by the explanation to the driving function; a drive module; and the operation hardware provides a drive function of the operation hardware for the drive interface module to call. The advantages are that: the driving module is independent, so that the labor division is facilitated, the efficiency is improved, and the driving module are not interfered with each other; the standardization of a driving interface is facilitated, the reloaded driving function in the second static library in the application interface module and different projects can be normally executed without changing codes after the reloading according to the standard, and the development time of the application program is saved.
Description
Technical Field
The invention relates to the field of single-chip microcomputers of POS machines, in particular to a system and a method for realizing a dynamic library of a single-chip microcomputer.
Background
With the progress of semiconductor technology, the functions of the single chip microcomputer are more and more powerful. And a singlechip is used as a main controller, so that various complex functions of the POS can be realized. Because the singlechip integrated level is high, the stable performance, and the price is substantial, so some POS machines on the market adopt the singlechip to realize, if: a password keyboard, mPOS, etc.
In software development of the single chip microcomputer, the single chip microcomputer is layered according to the tightness degree of hardware and can be divided into an application module and a driving module, and some single chip microcomputers have abundant hardware resources and can be added with a system layer. The use of the singlechip shows that hardware resources are limited, and a dynamic library such as Linux and windows of a PC (personal computer) cannot be realized. It is therefore common practice to: the driver modules are compiled into a static library and then provided to the application module developer. This practice, in some products, is disadvantageous and sometimes unacceptable to the customer. The concrete disadvantages are as follows: 1. to modify the driver, the application must be recompiled using the new driver static library. 2. When a plurality of applications are used, each application has a drive code, which wastes the originally limited hardware resources and is not convenient for the state management of the drive. 3. The duplicate name function probability of the driving module and the application module is greatly increased, and the management is inconvenient.
Disclosure of Invention
The invention aims to provide a system and a method for realizing a dynamic library of a singlechip, thereby solving the problems in the prior art.
In order to achieve the purpose, the technical scheme adopted by the invention is as follows:
a system for realizing dynamic library of single chip microcomputer comprises
The application module is used for driving the provided instruction to complete the operation required by the client;
the application interface module is used for transmitting the driving function and the parameter information which need to be called by the application module to the driving interface module;
the driving interface module is used for explaining the driving function and the parameter information transmitted by the application interface module, calling the corresponding driving function and transmitting the parameter information which is released by the explanation to the driving function;
a drive module; and the operation hardware provides a drive function of the operation hardware for the drive interface module to call.
Preferably, the driving interface module includes a driving interface management unit and an interrupt vector table management unit; the driving interface management unit is used for completing the operation of connecting the driving module and the application module together with the application management module; and a secondary drive function call table is arranged in the interrupt vector table management unit and is respectively a primary call table and a secondary call table.
Preferably, the content stored in the first-level call table is an entry of a second-level call table, the content stored in the first-level call table is classified according to modules, and the serial numbers of the modules correspond to the serial numbers of the second-level call table one to one.
Preferably, the content stored in the second-level call table is a driver function interface provided by each module in the first-level call table to the application module, and each driver function interface is numbered.
Preferably, a driver interface program is provided in the driver interface module, and the driver interface program is used for calling and managing the driver interface management unit and the interrupt vector table management unit.
Preferably, the drive interface management unit is provided with a drive module entry function, which is used to call a corresponding drive function according to the module number and the drive function interface number in the interrupt vector table management unit.
The invention also aims to provide a method for realizing the dynamic library of the single chip microcomputer, which is realized by using any system; the method comprises the following steps of,
s1, dividing the dynamic library into a driver module program partition, an application program partition and a shared RAM partition according to project requirements and hardware resources;
s2, operating hardware through the driving module according to project requirements, and providing a driving function of the operating hardware for the driving interface module to call; compiling a first static library and an interface document in the driving module, and transmitting the first static library and the interface document to the driving interface module;
s3, compiling a driving interface program in the driving interface module, starting the driving interface program, and handing the control right of the CPU to an application module;
s4, compiling a second static library in the application interface module, reloading each driving function in the second static library, packaging each driving function into a parameter packet according to the module number, the driving function interface number and the parameters of the driving function of the secondary driving function call table, and transmitting the parameter packet to the driving module entry function;
and S5, compiling the application program, calling the overloaded driving function in the second static library, and operating hardware.
Preferably, the calling process of the driving function is specifically,
A. the machine is powered on, a preset bootstrap program is started, hardware used during the boot period is initialized, the bootstrap program can run a driving interface program, and the CPU control right is handed to the driving interface program;
B. after the drive interface program is started, further initializing a hardware and interrupt vector table management unit, initializing each drive module and starting an application program;
C. after an application program is started, if hardware needs to be operated, a heavy-load drive function in a first static library is called, the heavy-load drive function calls a drive module entry function, and then the drive module entry function calls a drive function corresponding to a function module number and a function interface number in an interrupt vector table management unit;
D. the called drive function operates the hardware, and after the operation is finished, the operation result is fed back to the application program.
The invention has the beneficial effects that: 1. the driving module is independent, which is beneficial to division of labor and improves the efficiency without mutual interference. The personnel responsible for the application do not need to consider the driver, the personnel responsible for the driver do not need to consider the application, and the application and the driver are separately compiled and can be independently developed. 2. The standardization of the driving interface is facilitated, the reloaded driving function in the second static library in the dynamic library application interface module and different projects are reloaded according to the standard, the application program does not need to change codes and can be normally executed, and the development time of the application program is saved. 3. Hardware resources are saved, the second static library in the application interface module is compiled into the application program, the whole driving code is not, the dynamic library application interface module needs less hardware resources, and when a plurality of applications are needed, resources of the RAM and the ROM can be saved.
Drawings
FIG. 1 is a schematic diagram of the architecture of a system in an embodiment of the invention;
FIG. 2 is a schematic diagram of a method in an embodiment of the invention;
FIG. 3 is a schematic diagram of the principle of the driver function call of the method in the embodiment of 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 below with reference to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are given by way of illustration only.
Example one
As shown in fig. 1, the embodiment provides a system for implementing a dynamic library of a single chip microcomputer, and the system includes
The application module is used for driving the provided instruction to complete the operation required by the client;
the application interface module is used for transmitting the driving function and the parameter information which need to be called by the application module to the driving interface module;
the driving interface module is used for explaining the driving function and the parameter information transmitted by the application interface module, calling the corresponding driving function and transmitting the parameter information which is released by the explanation to the driving function;
a drive module; and the operation hardware provides a drive function of the operation hardware for the drive interface module to call.
In this embodiment, the application module uses the provision function of the driver to complete the function required by the user. Such as: and (4) a card swiping transaction function.
In this embodiment, the driving interface module includes a driving interface management unit and an interrupt vector table management unit; the driving interface management unit is used for completing the operation of connecting the driving module and the application module together with the application management module; and a secondary drive function call table is arranged in the interrupt vector table management unit and is a primary call table and a secondary call table respectively.
In this embodiment, the content stored in the first-level call table is an entry of the second-level call table, the content stored in the first-level call table is classified according to modules, and the numbers of the modules correspond to the numbers of the second-level call table one to one.
In this embodiment, the content stored in the second-level call table is a driving function interface provided by each module in the first-level call table to the application module, and each driving function interface is numbered.
In this embodiment, a driver interface program is disposed in the driver interface module, and the driver interface program is configured to call and manage the driver interface management unit and the interrupt vector table management unit. The driver interface program is named as VOS (Vanstone Operating System).
In this embodiment, the driver interface management unit is provided with a driver module entry function, and is configured to call a corresponding driver function according to the module number and the driver function interface number in the interrupt vector table management unit.
In this embodiment, the driver interface module integrates two basic functions of driver interface management and interrupt vector table management, and may also integrate functions of download management, file system management, system parameter management, and the like according to actual project requirements.
In this embodiment, the driver interface program is used to complete the function of linking the driver module and the application module together with the application interface module. The driver interface program maintains a secondary driver function call table, i.e., two function call tables, the primary call table being categorized by module, e.g., lcd, keys, etc. The content stored in the first-level call table is an entry of the second-level call table, each module is numbered, and the module number is unique and corresponds to the number of the second-level call table; the second level call table is an entry of each operation hardware drive function in the module, that is, a drive function interface provided by each module to the application module is put into the second level call table and is numbered, and the drive function number is unique. After the module number and the function number are fixed, the module number and the function number cannot be modified or deleted, otherwise, the application interface module is not matched with the driving interface module, and the application program cannot correctly call the driving function of the driving module.
Example two
As shown in fig. 2 and fig. 3, the present embodiment provides a method for implementing a dynamic library of a single chip microcomputer, where the method is implemented by using the system; the method comprises the following steps of,
s1, dividing the dynamic library into a driver module program partition, an application program partition and a shared RAM partition according to project requirements and hardware resources;
s2, operating hardware through the driving module according to project requirements, and providing a driving function of the operating hardware for the driving interface module to call; compiling a first static library and an interface document in the driving module, and transmitting the first static library and the interface document to the driving interface module;
s3, compiling a driving interface program in the driving interface module, starting the driving interface program, and handing the control right of the CPU to an application module;
s4, compiling a second static library in the application interface module, reloading each driving function in the second static library, packaging each driving function into a parameter packet according to the module number, the driving function interface number and the parameters of the driving function of the secondary driving function call table, and transmitting the parameter packet to the driving module entry function;
and S5, compiling the application program, calling the overloaded driving function in the second static library, and operating hardware.
In this embodiment, in order to connect the application interface module and the driver interface module, a memory (RAM) accessible by both the application module and the driver module needs to be partitioned from the dynamic library, and is used for transferring the entry function and the related parameters of the driver interface module.
In this embodiment, the calling process of the driver function is specifically,
A. the machine is powered on, a preset bootstrap program is started, hardware used during the boot period is initialized, the bootstrap program can run a driving interface program, and the CPU control right is handed to the driving interface program;
B. after the drive interface program is started, further initializing a hardware and interrupt vector table management unit, initializing each drive module and starting an application program;
C. after the application program is started, if hardware needs to be operated, calling a heavy-load drive function in the first static library, calling the drive module entry function by the heavy-load drive function, and calling a drive function corresponding to a function module number and a function interface number in the interrupt vector table management unit by the drive module entry function;
D. the called drive function operates the hardware, and after the operation is finished, the operation result is fed back to the application program.
In this embodiment, the method is specifically implemented as follows:
1. partitioning by project requirements, and hardware resources
E.g., 4M SDRAM space allocation
0x0000-0x03FF interrupt vector table in SDRAM.
0x400-0x00FFF application partition and dynamic bank shared RAM partition in SDRAM
0x00001000-0x00100FFF (1M) VOS space in SDRAM
0x00101000-0x001FFFFF (1020K) word bank space in SDRAM
0x00200000-0x002FFFFF (1M) application 1 space in SDRAM
0x00300000-0x003FFFFF (1M) application 2 space in SDRAM
The application program partition and the dynamic library share the RAM partition, and the specific use conditions are as follows:
0x400-0x450: storing dynamic library driver interface module entry functions
0x450-0xFFF: storage drive function parameter table
The drive interface module entry function is currently of the form: void ProcFunc (void); this reduces the push and pop time.
2. To realize the function of driving
And realizing the functions of each module according to project requirements, and providing a driving interface function.
Such as: the open function of the file system, prototype is as follows: int open (chassis filed, unidentified chassis mode).
3. Implementation of VOS
The VOS controls the drive interface management unit, takes the file system as a module and numbers the module, and the open function of the file system also numbers the module. The following were used:
#define FILE_MODULE_ID 0x08
#define OPEN_FUNC_ID 0x01
storing the address of the open function in the position with the index number of 1 of the file operation call table (the second level call table), and then storing the initial address of the file operation call table in the position with the index number of 8 of the first level call table. The driving interface management realizes a dynamic library driving module entry function, and the prototype thereof is as follows: void ProcFunc (void). The function of the ProcFunc function is to call a drive function according to ModuleID and FuncID in a parameter table in the dynamic library sharing RAM partition, and parameters transmitted during calling are obtained from the parameter table.
4. Implementing a second static library in an application interface module
Firstly, the application interface module acquires the entry function of the driving interface module, and then the connection between the application interface module and the driving interface module is completed. The main functions of the application module interface are: reloading the function of the drive, such as reloading the function open of the file system.
5. Implementing application programs
The application is compiled with a second static library in the application interface module.
After the application program is started, firstly, an appdliinit () function is called, and then, each driving function in a second static library in the application interface module can be called, such as an open function of a file system: ret = open ("test. Txt", O _ CREATE); making it operable to a file system open function in the VOS.
By adopting the technical scheme disclosed by the invention, the following beneficial effects are obtained:
the foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements should also be considered within the scope of the present invention.
Claims (4)
1. A system for realizing a singlechip dynamic library is characterized in that: the system comprises
The application module is used for driving the provided instruction to complete the operation required by the client;
the application interface module is used for transmitting the driving function and the parameter information which need to be called by the application module to the driving interface module;
the driving interface module is used for explaining the driving function and the parameter information transmitted by the application interface module, calling the corresponding driving function and simultaneously transmitting the parameter information which is explained to the driving function;
a drive module; the operation hardware provides a drive function of the operation hardware for the drive interface module to call;
the driving interface module comprises a driving interface management unit and an interrupt vector table management unit; the driving interface management unit is used for completing the operation of connecting the driving module and the application module together with the application interface module; a secondary drive function call table is arranged in the interrupt vector table management unit and is respectively a primary call table and a secondary call table;
the content stored in the first-level call table is an entry of a second-level call table, the content stored in the first-level call table is classified according to modules, and the serial numbers of the modules correspond to the serial numbers of the second-level call table one by one;
the content stored in the second-level call table is a driving function interface provided by each module in the first-level call table to the application module, and each driving function interface is numbered;
the drive interface module is provided with a drive interface program, and the drive interface program is used for calling and managing the drive interface management unit and the interrupt vector table management unit.
2. The system for realizing the dynamic library of the single chip microcomputer according to claim 1, wherein: the drive interface management unit is provided with a drive module entry function for calling a corresponding drive function according to the module number and the drive function interface number in the interrupt vector table management unit.
3. A method for implementing a dynamic library of singlechips, the method being implemented using the system of claim 1 or 2; the method is characterized in that: the method comprises the following steps of,
s1, dividing the dynamic library into a driver module program partition, an application program partition and a shared RAM partition according to project requirements and hardware resources;
s2, operating hardware through the drive module according to project requirements, and providing a drive function of the operating hardware for the drive interface module to call; compiling a first static library and an interface document in the driving module, and transmitting the first static library and the interface document to the driving interface module;
s3, compiling a driving interface program in the driving interface module, starting the driving interface program, and handing the control right of the CPU to an application module;
s4, compiling a second static library in the application interface module, reloading each driving function in the second static library, packaging each driving function into a parameter packet according to the module number, the driving function interface number and the parameters of the driving function of the secondary driving function call table, and transmitting the parameter packet to the driving module entry function;
and S5, compiling the application program, calling the overloaded driving function in the second static library, and operating hardware.
4. The method for realizing the dynamic library of the single chip microcomputer according to claim 3, wherein the method comprises the following steps: the calling process of the driving function is specifically that,
A. the method comprises the following steps that a machine is powered on, a preset bootstrap program is started, hardware used in a bootstrap period is initialized, the bootstrap program can run a driving interface program, and the control right of a CPU is given to the driving interface program;
B. after the drive interface program is started, further initializing a hardware and interrupt vector table management unit, initializing each drive module and starting an application program;
C. after the application program is started, if hardware needs to be operated, calling a heavy-load drive function in the first static library, calling the drive module entry function by the heavy-load drive function, and calling a drive function corresponding to a function module number and a function interface number in the interrupt vector table management unit by the drive module entry function;
D. the called drive function operates the hardware, and after the operation is finished, the operation result is fed back to the application program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911095291.6A CN110851140B (en) | 2019-11-11 | 2019-11-11 | System and method for realizing dynamic library of single chip microcomputer |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911095291.6A CN110851140B (en) | 2019-11-11 | 2019-11-11 | System and method for realizing dynamic library of single chip microcomputer |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110851140A CN110851140A (en) | 2020-02-28 |
| CN110851140B true CN110851140B (en) | 2023-04-07 |
Family
ID=69601233
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911095291.6A Active CN110851140B (en) | 2019-11-11 | 2019-11-11 | System and method for realizing dynamic library of single chip microcomputer |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110851140B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111856989A (en) * | 2020-06-19 | 2020-10-30 | 中电科航空电子有限公司 | Dynamic linking method for single chip microcomputer |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102685134A (en) * | 2012-05-15 | 2012-09-19 | 深圳市中电电力技术股份有限公司 | Communication managing machine capable of being comprehensively realized based on extensible markup language and dynamic library |
| CN105718264A (en) * | 2016-01-20 | 2016-06-29 | 国网山东省电力公司电力科学研究院 | Laser head driver architecture and method |
| CN106066809A (en) * | 2016-06-20 | 2016-11-02 | 深圳市普中科技有限公司 | A kind of emulation debugging method based on ARM kernel 51 emulator and system |
| CN109508202A (en) * | 2018-09-27 | 2019-03-22 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Drive development system, method and medium for embedded operating system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7536683B2 (en) * | 1999-01-15 | 2009-05-19 | Adobe Systems Incorporated | Method of dynamically appending a library to an actively running program |
-
2019
- 2019-11-11 CN CN201911095291.6A patent/CN110851140B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102685134A (en) * | 2012-05-15 | 2012-09-19 | 深圳市中电电力技术股份有限公司 | Communication managing machine capable of being comprehensively realized based on extensible markup language and dynamic library |
| CN105718264A (en) * | 2016-01-20 | 2016-06-29 | 国网山东省电力公司电力科学研究院 | Laser head driver architecture and method |
| CN106066809A (en) * | 2016-06-20 | 2016-11-02 | 深圳市普中科技有限公司 | A kind of emulation debugging method based on ARM kernel 51 emulator and system |
| CN109508202A (en) * | 2018-09-27 | 2019-03-22 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Drive development system, method and medium for embedded operating system |
Non-Patent Citations (1)
| Title |
|---|
| 张鑫焱 ; 金平 ; 陈怀民 ; 段晓军 ; .RTX下的驱动及Simulink模块封装技术.测控技术.(第04期),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110851140A (en) | 2020-02-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5247678A (en) | Load time linker for software used with a multiprocessor system | |
| US7103881B2 (en) | Virtual machine to provide compiled code to processing elements embodied on a processor device | |
| US5428792A (en) | System for producing language neutral objects and generating an interface between the objects and multiple computer languages | |
| EP1011043A2 (en) | Method and apparatus for loading a java application program | |
| US9164735B2 (en) | Enabling polymorphic objects across devices in a heterogeneous platform | |
| CN100549957C (en) | One kind is loaded the method and a kind of isolating and is loaded the device of isolating | |
| CN105242962A (en) | Quick lightweight thread triggering method based on heterogeneous many-core | |
| CN105190550A (en) | Booting method for computer system with multiple central processing units | |
| CN109388473A (en) | Android compatible layer implementation method and system based on mobile operating system | |
| US6691118B1 (en) | Context management system for modular software architecture | |
| US20050071856A1 (en) | Dynamically loadable stub modules | |
| US20070288912A1 (en) | Methods and apparatus to provide a managed runtime environment in a sequestered partition | |
| CN113826076A (en) | Expandable and secure container | |
| CN110851140B (en) | System and method for realizing dynamic library of single chip microcomputer | |
| CN114168255A (en) | Operation method and device of heterogeneous instruction set container in container cloud platform | |
| JP5401561B2 (en) | Application of platform-dependent routines within a virtual mechanism by embedding native code in a class file | |
| CN106598647A (en) | Intelligent apparatus development platform | |
| CN114089975A (en) | Expansion method and device of computing software, nonvolatile storage medium and processor | |
| CN111651158A (en) | Form page generation method, device, terminal and storage medium | |
| CN117573338A (en) | Resource allocation method and device and electronic equipment | |
| WO2023208012A1 (en) | Program processing method and apparatus, program running method and apparatus, terminal, smart card and storage medium | |
| CN113031957A (en) | Application program installation method, client, terminal, server and storage medium | |
| CN109460280B (en) | Method and terminal for running program | |
| CN111176689B (en) | Information processing method and electronic device | |
| CN103631648A (en) | Task processing method 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |