CN114416202B - Mobile terminal SDK calling method and system - Google Patents
Mobile terminal SDK calling method and system Download PDFInfo
- Publication number
- CN114416202B CN114416202B CN202210047274.0A CN202210047274A CN114416202B CN 114416202 B CN114416202 B CN 114416202B CN 202210047274 A CN202210047274 A CN 202210047274A CN 114416202 B CN114416202 B CN 114416202B
- Authority
- CN
- China
- Prior art keywords
- calling
- sdk
- native
- interface
- layer
- 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
Classifications
-
- 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/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- 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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
-
- 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 invention belongs to the technical field of operating systems and software development, and particularly relates to a mobile terminal SDK calling method and system. The method calls a language supporting a reflection mechanism in a request or interface mode, firstly, a native platform developer writes a configuration file, automatically analyzes the configuration file and generates a corresponding intermediate description template when an application project is constructed, finally, a calling method required by the calling language is generated according to a pre-configured calling template, and a mobile terminal developer decouples a third party SDK from the method in the mode. The method overcomes the defect of the existing mobile terminal third party SDK access method in performance, and provides a method and a channel for calling a specific SDK through analyzing the input parameters for supporting multiple manufacturer interfaces for providing low invasiveness and good compatibility for the front end under the scene of inconvenient direct calling of the third party SDK in the development process of the mobile terminal hybrid architecture.
Description
Technical Field
The invention belongs to the technical field of operating systems and software development, and particularly relates to a mobile terminal SDK calling method and system.
Background
Today, SDKs (software development kits) or methods provided by each platform (operating system) are developed by the developer of the platform using a specific platform development language, for example, the Android platform uses Java and the IOS platform uses Object C/Swift, which results in that users unfamiliar with the platform development language cannot conveniently use the method of the platform, especially for the SDKs to be accessed by the mobile terminal.
Currently, in the development of a mobile terminal hybrid architecture, when a third party SDK is required to be accessed, if the third party SDK cannot provide a jsSDK (a JavaScript-based development kit provided by a third party platform for a webpage developer) corresponding to the adaptation front-end call, a corresponding native platform developer is required to access the native SDK, and an SDK interface is exposed to be called by the front-end personnel. If the same SDK is needed to access multiple vendors (hardware device/push service/sharing/payment), the native platform developer is required to expose the SDK interface of each vendor or the interface unified by the front-end corresponding SDK method, and the vendors are distinguished according to the front-end input parameters.
For the first situation, the native platform developer directly exposes the SDK interface to the front-end personnel for calling, and when the actual business operation is performed, the front-end personnel is required to call and integrate the exposed SDK interface, and a large amount of repeated codes are required to be written to declare to call the native method object and method, so that the operation efficiency is low.
For the second situation, the native platform developer uniformly calls the interfaces by exposing methods of the SDKs of a plurality of manufacturers and distinguishes the manufacturers by front-end parameters, however, when the SDKs are updated and the methods are changed or the parameters of the parameters are changed, a large amount of native layer codes need to be modified, and the decoupling of the SDKs from the front-end call interfaces cannot be well achieved.
In summary, in the hybrid development of the mobile terminal (Android/IOS), under the scenario that the third party SDK is inconvenient to call directly, there is an urgent need to develop an SDK call method and channel that has low invasiveness and good compatibility and supports interfaces of multiple vendors.
Disclosure of Invention
In order to overcome the defect of the existing mobile terminal third party SDK access method in performance and meet the technical requirement of facilitating the mobile terminal to access the SDK, the invention provides a set of solution. The invention aims to provide a mobile terminal SDK calling method for calling any method in a tool package of a reflectable language based on any application request, and aims to provide a method and a channel for calling a specific SDK through analyzing an incoming parameter, which have low invasiveness and good compatibility, and support a plurality of manufacturer interfaces, for a front end under the scene of inconvenient direct calling of a third party SDK in the development process of a mobile terminal (Android/IOS) mixed architecture.
The implementation of the method solves the following technical problems: (1) SDK access must be made by the native platform developer; (2) coupling the native exposure interface to the SDK; (3) The front end needs to encapsulate the calling method according to the native exposed interface.
In addition, the method of the invention is essentially used for calling the language supporting the reflection mechanism in the form of a request or an interface, so that the method is applicable to other fields besides the mobile terminal, and can be applied to the calling flow in the method of the invention if the language supporting the reflection mechanism is simply adjusted.
Specifically, the invention provides a mobile terminal SDK calling method, which calls a language supporting a reflection mechanism in a request or interface mode, firstly, a native platform developer writes a configuration file, automatically analyzes the configuration file and generates a corresponding intermediate description template when an application project is constructed, and finally, the mobile terminal developer generates a calling method required by the calling language according to a pre-configured calling template, and the mobile terminal developer decouples a third party SDK calling and an integration method in the mode.
Further, the method of the present invention includes three functional layers, namely a calling layer, a description layer and a registration layer, each of which operates and executes corresponding functions according to the following modes, wherein:
calling layer: the call layer comprises a unified call interface which is an interface used when a native method or an SDK is actually called, and when a developer needs to call a corresponding description layer method, the developer only needs to call a deviceInvoke, wherein the deviceInvoke comprises a method name and an incoming parameter;
description layer: the description layer contains an intermediate description template, which declares a method or object to be used for calling a specific native method or SDK in an annotating way, when the peripheral equipment is accessed, the SDK of a plurality of manufacturers is accessed, and if the method names and the incoming parameters of the calling methods in the SDKs are consistent, the same description method is used;
registration layer: the registration layer contains APT registration preprocessing and a call object registration center, and stores the registration information of the native method and the SDK as the call objects.
Further, the implementation flow of the method comprises three stages, namely, the construction time, the pre-compiling time and the running time;
preparing a native platform end operation base when the mobile end hybrid architecture application is developed, constructing an application project on the operation base, and generating an intermediate description layer code according to a configuration file required to be called by a front-end developer when the application project is constructed at the construction stage; after the application project is constructed, generating a calling interface and a registration object of the front end by a front end developer at the pre-compiling stage according to the intermediate description layer code by using a pre-compiling script; when the user calls the unified call interface in the runtime, the native method or SDK to be called is acquired in the call object registry, and the reflection call is carried out through the intermediate description layer code.
Further, the method of the invention comprises the steps of:
(1) Native platform construction
Before application packaging, writing or configuring a corresponding interface description file by a front-end developer according to a native method or SDK used as required, constructing an application project, calling a native interface configuration file by the front-end, processing the configuration file, and generating an intermediate description layer code in a native platform; packaging after the application project is constructed, generating a corresponding registration code by a native method in the packaging process according to the intermediate description layer code, and injecting a call object pool when the application runs;
(2) Before compiling the native platform
Invoking an object registration interface;
firstly performing APT compiling pretreatment to generate a registration object, then performing APT compiling pretreatment to generate a target language calling interface, calling a native method or an SDK from a front-end page through the interface, and returning a calling result to the front-end page after the calling is completed;
(3) When the native platform operates
Accessing a call object registry through a call object registry interface to acquire a native method or SDK to be called;
and after the object pool is called, a call result is returned to the unified call interface, the method obtained from the object pool is applied to be reflected and called to a specific original method, a multi-SDK unified method is processed through an intermediate description layer, and finally a plurality of the same SDK objects which are called are automatically processed by entering a common method unified processing interface.
Further, in the method step (1), the application project construction executes a corresponding automatic construction flow in the construction process, and the automatic construction flow is completed according to a built-in construction mechanism in the Android or IOS system, so as to download the dependency and execute the preprocessing task.
In addition, the invention also relates to the application of the mobile terminal SDK calling method in the mobile terminal hybrid architecture development technology.
On the other hand, the invention also provides a mobile terminal SDK calling system, which comprises:
(1) And (3) calling a layer module: the calling layer module comprises a unified calling interface which is an interface used when the native method or the SDK is actually called;
(2) Description layer module: the description layer module contains an intermediate description template, and states that a method or object is used for calling a specific native method or SDK in an annotating mode;
(3) Registration layer module: the registration layer module comprises an APT registration preprocessing and calling object registration center, and stores the registration information of the native method and the SDK as the calling objects;
(4) And the automatic control module is used for: and organizing and controlling the operation of each module so as to realize the mobile terminal SDK calling method.
In summary, the invention provides a mobile terminal SDK calling method and a system, and the method has the following functional characteristics:
(1) The unified calling interface is utilized to realize that the corresponding native method or SDK can be called through calling the name of the method and the parameters.
(2) The native description interface and the front-end call interface are automatically generated in the form of a build script and a configuration file.
(3) The same method or SDK of multiple vendors can be uniformly called through the intermediate description layer.
(4) When the SDK is accessed to the hardware peripheral equipment, the modular decoupling can be realized, and the maintenance of a developer is facilitated.
(5) The description interface for the native method can be generated only in the form of a configuration file, so that independent development of a front-end developer is realized.
(6) The method and the system can be used for being universal in Android and IOS platforms, and provide convenience for users.
Drawings
In order to more clearly illustrate the technical scheme of the embodiment of the invention, the drawings which are needed to be used in the description of the embodiment are briefly introduced below. It is apparent that the drawings described in the following description are only some, but not all, embodiments of the invention, and that other drawings may be derived from these drawings by a person skilled in the art without inventive effort.
Fig. 1 is a functional hierarchical diagram of a mobile terminal SDK calling method according to the present invention.
Fig. 2 is a schematic diagram of a flow stage structure hierarchy of the mobile terminal SDK calling method of the present invention.
Fig. 3 is a schematic diagram of an operation flow of the SDK calling method of the mobile terminal of the present invention.
Fig. 4 is an exemplary diagram of a configuration file of the SDK calling method at the mobile terminal in a specific case of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the technical solutions of the present invention will be clearly and completely described below with reference to specific embodiments and corresponding drawings. It is apparent that the described embodiments are only some embodiments of the present invention, but not all embodiments, and the present invention may be implemented or applied by different specific embodiments, and that various modifications or changes may be made in the details of the present description based on different points of view and applications without departing from the spirit of the present invention.
Meanwhile, it should be understood that the scope of the present invention is not limited to the following specific embodiments; it is also to be understood that the terminology used in the examples of the invention is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the invention.
In addition, for convenience of description, the following embodiments are described by taking an Android system as an example, but the method and the system are equally applicable to an IOS system.
Example 1: mobile terminal SDK calling method (see FIGS. 1-4)
The method calls a language supporting a reflection mechanism in a request or interface mode, firstly, a native platform developer writes a configuration file, automatically analyzes the configuration file and generates a corresponding intermediate description template when an application project is constructed, finally, a calling method required by the calling language is generated according to a pre-configured calling template, and a mobile terminal developer decouples a third party SDK call and an integration method in the mode.
The method comprises three functional layers, namely a calling layer, a description layer and a registration layer (shown in figure 1), wherein each functional layer operates and executes corresponding functions in the following manner, and the method comprises the following steps:
calling layer: the call layer comprises a unified call interface which is an interface used when a native method or an SDK is actually called, and when a developer needs to call a corresponding description layer method, the developer only needs to call a deviceInvoke, wherein the deviceInvoke comprises a method name and an incoming parameter;
description layer: the description layer contains an intermediate description template, which declares a method or object to be used for calling a specific native method or SDK in an annotating way, when the peripheral equipment is accessed, the SDK of a plurality of manufacturers is accessed, and if the method names and the incoming parameters of the calling methods in the SDKs are consistent, the same description method is used;
registration layer: the registration layer comprises APT registration preprocessing and a call object registration center, and stores the registration information of a native method and an SDK as a call object;
typically, only the call layer and the description layer need be focused on by the developer.
In general, the implementation flow of the method comprises three stages, namely, the construction time, the compiling time and the running time (shown in fig. 2);
preparing a native platform end operation base when the mobile end hybrid architecture application is developed, constructing an application project on the operation base, and generating an intermediate description layer code according to a configuration file required to be called by a front-end developer when the application project is constructed at the construction stage; after the application project is constructed, generating a calling interface and a registration object of the front end by a front end developer at the pre-compiling stage according to the intermediate description layer code by using a pre-compiling script; when the user calls the unified call interface in the runtime, the native method or SDK to be called is acquired in the call object registry, and the reflection call is carried out through the intermediate description layer code.
Specifically, the method comprises the following steps (as shown in fig. 3):
(1) Native platform construction
Writing or configuring a corresponding interface description file by a front-end developer according to a native method or SDK used by the front-end developer before application packaging, constructing an application project (the application project is constructed and executed with a corresponding automatic construction flow in the construction process, and the automatic construction flow is completed according to a built-in construction mechanism in an Android or IOS system, and the aim is to download dependence and execute preprocessing tasks), calling a native interface configuration file by the front-end and processing the configuration file, and generating an intermediate description layer code in a native platform; packaging after the application project is constructed, generating a corresponding registration code by a native method in the packaging process according to the intermediate description layer code, and injecting a call object pool when the application runs;
for the front-end developer, the two steps are both noninductive, and for the calling in the front-end development process, the calling is only required to be carried out according to the method and the parameters in the configuration file, and the calling method is shown in fig. 4;
as shown in the example configuration file (see fig. 4), the toolkit name corresponding to the calling object is: the com.external.gwi.devicefkx.gwi deviceProtocol JRBJ, what needs to be called is a native object named IDCardReader, namely an identity card reading function, wherein an open method is provided, two parameters are needed to be transmitted, the two parameter types are int and String respectively, and at the moment, only an external.invoke ("open", the int type parameter, the String type parameter) needs to be called for the front end;
when a front-end developer calls an invoke method, the called method name is transferred into a native platform through a jsbridge bridge, an object which is automatically injected into a native call pool during construction and after packaging is searched, a corresponding method is searched in a registered SDK name after the object is found, an instance of the object is obtained through reflection and is called, a result is returned to the front end, and if no registered object is searched or is not found, abnormal information is submitted to the front-end for processing.
(2) Before compiling the native platform
Invoking an object registration interface;
the method comprises the steps of firstly performing APT compiling pretreatment to generate a registration object, then performing APT compiling pretreatment to generate a target language calling interface, calling a native method or an SDK from a front-end page through the interface, and returning a calling result to the front-end page after calling is completed.
(3) When the native platform operates
Accessing a call object registry through a call object registry interface to acquire a native method or SDK to be called;
and after the object pool is called, a call result is returned to the unified call interface, the method obtained from the object pool is applied to be reflected and called to a specific original method, a multi-SDK unified method is processed through an intermediate description layer, and finally a plurality of the same SDK objects which are called are automatically processed by entering a common method unified processing interface.
Example 2: mobile terminal SDK calling system
The system comprises:
(1) And (3) calling a layer module: the calling layer module comprises a unified calling interface which is an interface used when the native method or the SDK is actually called;
(2) Description layer module: the description layer module contains an intermediate description template, and states that a method or object is used for calling a specific native method or SDK in an annotating mode;
(3) Registration layer module: the registration layer module comprises an APT registration preprocessing and calling object registration center, and stores the registration information of the native method and the SDK as the calling objects;
(4) And the automatic control module is used for: the operations of the above modules are organized and controlled to implement the mobile terminal SDK calling method described in embodiment 1.
The embodiments of the present invention are described in a progressive manner, and the same or similar parts between the embodiments are referred to in the related description of the method embodiments.
The foregoing is merely exemplary of the present invention and is not intended to limit the present invention. Various modifications and variations of the present invention will be apparent to those skilled in the art. Any modification, replacement, etc. that comes within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.
Claims (3)
1. A mobile terminal SDK calling method is used for developing a mobile terminal hybrid architecture and is characterized in that the method calls a language supporting a reflection mechanism in a request or interface mode, a native platform developer writes a configuration file, the configuration file is automatically analyzed and a corresponding intermediate description template is generated when an application project is constructed, finally a calling method required by a calling language is generated according to a preset calling template, and the mobile terminal developer decouples a third party SDK calling and an integrated method in the mode;
the mobile terminal SDK calling method comprises three functional layers, namely a calling layer, a description layer and a registration layer, wherein each functional layer operates and executes corresponding functions according to the following mode, and the method comprises the following steps of:
calling layer: the call layer comprises a unified call interface which is an interface used when a native method or an SDK is actually called, and when a developer needs to call a corresponding description layer method, the developer only needs to call a deviceInvoke, wherein the deviceInvoke comprises a method name and an incoming parameter;
description layer: the description layer contains an intermediate description template, which declares a method or object to be used for calling a specific native method or SDK in an annotating way, when the peripheral equipment is accessed, the SDK of a plurality of manufacturers is accessed, and if the method names and the incoming parameters of the calling methods in the SDKs are consistent, the same description method is used;
registration layer: the registration layer comprises APT registration preprocessing and a call object registration center, and stores the registration information of a native method and an SDK as a call object;
the implementation flow of the mobile terminal SDK calling method comprises three stages, namely a construction time, a compiling time and a running time;
preparing a native platform end operation base when the mobile end hybrid architecture application is developed, constructing an application project on the operation base, and generating an intermediate description layer code according to a configuration file required to be called by a front-end developer when the application project is constructed at the construction stage; after the application project is constructed, generating a calling interface and a registration object of the front end by a front end developer at the pre-compiling stage according to the intermediate description layer code by using a pre-compiling script; when a user calls a unified call interface in a runtime stage, acquiring a native method or SDK (software description language) to be called from a call object registry, and carrying out reflection call through an intermediate description layer code;
the mobile terminal SDK calling method comprises the following steps:
(1) Native platform construction
Before application packaging, writing or configuring a corresponding interface description file by a front-end developer according to a native method or SDK used as required, constructing an application project, calling a native interface configuration file by the front-end, processing the configuration file, and generating an intermediate description layer code in a native platform; packaging after the application project is constructed, generating a corresponding registration code by a native method in the packaging process according to the intermediate description layer code, and injecting a call object pool when the application runs;
(2) Before compiling the native platform
Invoking an object registration interface;
firstly performing APT compiling pretreatment to generate a registration object, then performing APT compiling pretreatment to generate a target language calling interface, calling a native method or an SDK from a front-end page through the interface, and returning a calling result to the front-end page after the calling is completed;
(3) When the native platform operates
Accessing a call object registry through a call object registry interface to acquire a native method or SDK to be called;
and after the object pool is called, a call result is returned to the unified call interface, the method obtained from the object pool is applied to be reflected and called to a specific original method, a multi-SDK unified method is processed through an intermediate description layer, and finally a plurality of the same SDK objects which are called are automatically processed by entering a common method unified processing interface.
2. The mobile terminal SDK calling method according to claim 1, wherein in the step (1), the application project construction executes a corresponding automatic construction flow in the construction process, and the automatic construction flow is completed according to a construction mechanism built in an Android or IOS system, and the purpose of the method is to download dependencies and execute preprocessing tasks.
3. A mobile-side SDK invocation system, the system comprising:
(1) And (3) calling a layer module: the calling layer module comprises a unified calling interface which is an interface used when the native method or the SDK is actually called;
(2) Description layer module: the description layer module contains an intermediate description template, and states that a method or object is used for calling a specific native method or SDK in an annotating mode;
(3) Registration layer module: the registration layer module comprises an APT registration preprocessing and calling object registration center, and stores the registration information of the native method and the SDK as the calling objects;
(4) And the automatic control module is used for: the operations of the above modules are organized and controlled to implement the mobile terminal SDK calling method described in claim 1 or 2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210047274.0A CN114416202B (en) | 2022-01-17 | 2022-01-17 | Mobile terminal SDK calling method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210047274.0A CN114416202B (en) | 2022-01-17 | 2022-01-17 | Mobile terminal SDK calling method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114416202A CN114416202A (en) | 2022-04-29 |
| CN114416202B true CN114416202B (en) | 2023-08-04 |
Family
ID=81273592
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210047274.0A Active CN114416202B (en) | 2022-01-17 | 2022-01-17 | Mobile terminal SDK calling method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114416202B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115543853B (en) * | 2022-11-23 | 2023-03-17 | 北京蔚领时代科技有限公司 | Mobile terminal native SDK debugging method and system |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101957759A (en) * | 2010-10-21 | 2011-01-26 | 江苏科技大学 | SDK interface conversion system and implementation method thereof |
| CN103713896A (en) * | 2013-12-17 | 2014-04-09 | 北京京东尚科信息技术有限公司 | Software development kit generation method and device used for accessing server |
| CN106951233A (en) * | 2017-03-02 | 2017-07-14 | 广州天高软件科技有限公司 | Mixed mode smart mobile phone application development framework |
| CN107526584A (en) * | 2016-10-18 | 2017-12-29 | 腾讯科技（深圳）有限公司 | Data cut-in method and device |
| CN107589947A (en) * | 2017-08-02 | 2018-01-16 | 成都极娱网络科技有限公司 | A kind of SDK cut-in methods, client and system |
| CN109976831A (en) * | 2019-03-28 | 2019-07-05 | 山东浪潮通软信息科技有限公司 | Data interactive method between a kind of JavaScript and primary APP |
| CN110908704A (en) * | 2019-11-14 | 2020-03-24 | 亚信科技（中国）有限公司 | Method and device for calling cross-platform native function of mobile terminal |
| CN111913713A (en) * | 2020-06-10 | 2020-11-10 | 中国科学院软件研究所 | Heterogeneous service integration method based on service call tracking |
| CN113568661A (en) * | 2021-07-06 | 2021-10-29 | 浙江浙大中控信息技术有限公司 | Method for realizing app mixed development based on Android sdk |
| CN113886259A (en) * | 2021-10-19 | 2022-01-04 | 赞同科技股份有限公司 | Non-flow popup automatic processing method and system for bank counter system and electronic device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170102925A1 (en) * | 2014-03-26 | 2017-04-13 | Syed Adeel Ali | Automatch process and system for software development kit for application programming interface |
-
2022
- 2022-01-17 CN CN202210047274.0A patent/CN114416202B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101957759A (en) * | 2010-10-21 | 2011-01-26 | 江苏科技大学 | SDK interface conversion system and implementation method thereof |
| CN103713896A (en) * | 2013-12-17 | 2014-04-09 | 北京京东尚科信息技术有限公司 | Software development kit generation method and device used for accessing server |
| CN107526584A (en) * | 2016-10-18 | 2017-12-29 | 腾讯科技（深圳）有限公司 | Data cut-in method and device |
| CN106951233A (en) * | 2017-03-02 | 2017-07-14 | 广州天高软件科技有限公司 | Mixed mode smart mobile phone application development framework |
| CN107589947A (en) * | 2017-08-02 | 2018-01-16 | 成都极娱网络科技有限公司 | A kind of SDK cut-in methods, client and system |
| CN109976831A (en) * | 2019-03-28 | 2019-07-05 | 山东浪潮通软信息科技有限公司 | Data interactive method between a kind of JavaScript and primary APP |
| CN110908704A (en) * | 2019-11-14 | 2020-03-24 | 亚信科技（中国）有限公司 | Method and device for calling cross-platform native function of mobile terminal |
| CN111913713A (en) * | 2020-06-10 | 2020-11-10 | 中国科学院软件研究所 | Heterogeneous service integration method based on service call tracking |
| CN113568661A (en) * | 2021-07-06 | 2021-10-29 | 浙江浙大中控信息技术有限公司 | Method for realizing app mixed development based on Android sdk |
| CN113886259A (en) * | 2021-10-19 | 2022-01-04 | 赞同科技股份有限公司 | Non-flow popup automatic processing method and system for bank counter system and electronic device |
Non-Patent Citations (1)
| Title |
|---|
| 基于微信平台的移动银行应用架构研究;甘荣石;《中国优秀硕士学位论文全文数据库 (信息科技辑)》(第6期);I138-293 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114416202A (en) | 2022-04-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8291375B2 (en) | Attribute-based component programming system and methodology for object-oriented languages | |
| KR101795844B1 (en) | Runtime system | |
| US7010796B1 (en) | Methods and apparatus providing remote operation of an application programming interface | |
| US7739656B2 (en) | Generating asynchronous interfaces and methods from synchronous interfaces and methods | |
| US20030236657A1 (en) | Method of developing wireless device applications using an integrated emulator and an IDE | |
| US7950024B2 (en) | Mechanism for transparently interfacing with a third party version control system | |
| CN110912724A (en) | Parameter-driven automatic service arrangement method and device | |
| US20060230379A1 (en) | System and method for generating a user interface based on metadata exposed by object classes | |
| JP2004503866A (en) | Modular computer system and related methods | |
| US7594217B2 (en) | Matching client interfaces with service interfaces | |
| US7219341B2 (en) | Code analysis for selective runtime data processing | |
| CN112685020A (en) | Method and device for dynamically creating service interface, electronic equipment and storage medium | |
| CN114416202B (en) | Mobile terminal SDK calling method and system | |
| US6675227B1 (en) | Method for providing a service implementation for both EJB and non-EJB environments | |
| US20040128644A1 (en) | Software architecture for distributed enterprise business applications | |
| Schieferdecker et al. | A meta-model for TTCN-3 | |
| US11080102B2 (en) | System and method for developing modularized application | |
| CN115857898A (en) | Application system construction and operation method and device | |
| Yang et al. | Professional Microsoft Smartphone Programming | |
| CN113568603B (en) | Component object creating and interface method calling method, terminal and storage device | |
| Dantas et al. | Developing adaptive j2me applications using AspectJ. | |
| AU2019100212A4 (en) | System and method for developing modularized application | |
| US7308679B2 (en) | Method and computer program product for providing a meta-data programming language level interface | |
| Srinivasmurthy et al. | Web2exchange: A model-based service transformation and integration environment | |
| Wetherbee et al. | Beginning EJB 3: Java EE 7 Edition |
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 |