SDK calling method, device, server and storage medium

Abstract

The present invention discloses an SDK calling method, device, server and storage medium, and belongs to the field of computer technology. The method comprises: obtaining a software development kit SDK, wherein the SDK comprises interface configuration information and function programs corresponding to multiple terminals; configuring a target interface based on the interface configuration information and function programs corresponding to the current terminal included in the SDK; and calling the function program of the SDK based on the target interface to execute the function corresponding to the SDK. The embodiment of the present invention realizes the same function on multiple terminals by adopting the method of calling SDK. During the calling process, the interface can be configured according to the function program and the interface configuration information corresponding to each terminal, so that the function program of the SDK can be directly called to realize the corresponding function. There is no need to develop a project file for each terminal, which greatly reduces the development time and labor cost. The SDK calling method has good versatility.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to an SDK calling method, device, server and storage medium. Background Art

[0002] With the development of computer technology, the application of multi-terminal isomorphism technology is becoming more and more widespread. In many scenarios, it is usually necessary to implement the same function on multiple terminals. For example, the same advertising function can be accessed on the web page, application, and mini program. In order to meet the needs of multi-terminal isomorphism, it is necessary to deploy engineering files that implement the same function on the corresponding servers of multiple terminals, and the engineering files may include functional programs.

[0003] At present, different terminals have different operating environments. If the same function needs to be implemented on multiple terminals, technicians need to develop a project file for each terminal. The development time required in this process is long, the labor cost is high, and the project files have poor versatility. Summary of the invention

[0004] The embodiment of the present invention provides a method, device, server and storage medium for calling a software development kit (SDK), which can solve the problems of long development time, high labor cost and poor versatility in related technologies. The technical solution is as follows:

[0005] In one aspect, a method for calling an SDK is provided, the method comprising:

[0006] Obtain a software development kit SDK, wherein the SDK includes a functional program and interface configuration information corresponding to multiple terminals;

[0007] Based on the function program included in the SDK and the interface configuration information corresponding to the current end, configure the target interface;

[0008] Based on the target interface, the function program of the SDK is called to execute the function corresponding to the SDK.

[0009] In one aspect, a SDK calling device is provided, the device comprising:

[0010] An acquisition module is used to acquire a software development kit SDK, wherein the SDK includes a functional program and interface configuration information corresponding to multiple terminals;

[0011] A configuration module, used to configure the target interface based on the functional program included in the SDK and the interface configuration information corresponding to the current end;

[0012] The calling module is used to call the function program of the SDK based on the target interface to execute the function corresponding to the SDK.

[0013] In a possible implementation, the plurality of functional programs include a style configuration program and a business logic program;

[0014] The configuration module is used to:

[0015] Based on the style configuration program included in the SDK and the interface configuration information corresponding to the current end, the display interface is configured;

[0016] The business processing interface is configured based on the business logic program included in the SDK and the interface configuration information corresponding to the current end.

[0017] In a possible implementation, the device further includes:

[0018] The update module is used to update the functional programs included in the SDK when receiving an update request of the SDK.

[0019] In a possible implementation, the functional program included in the SDK may be implemented based on a syntax abstract tree;

[0020] The update module is used to update the structure of the syntax abstract tree based on the content of the update request when receiving the update request of the SDK.

[0021] In a possible implementation, the device further includes:

[0022] The acquisition module, the configuration module or the calling module is further used to execute the steps of acquiring the software development kit SDK, configuring and calling when receiving a calling request for the SDK, wherein the calling request is triggered based on an interactive operation performed on a plug-in corresponding to any functional program of the SDK, and the calling request includes information of the plug-in;

[0023] The calling module is used to call any functional program corresponding to the plug-in of the SDK based on the target interface and the information of the plug-in, and execute the function corresponding to the any functional program.

[0024] On the one hand, a server is provided, which includes one or more processors and one or more memories, wherein at least one instruction is stored in the one or more memories, and the instruction is loaded and executed by the one or more processors to implement the operation performed by the SDK calling method.

[0025] On the one hand, a computer-readable storage medium is provided, wherein at least one instruction is stored in the computer-readable storage medium, and the instruction is loaded and executed by a processor to implement the operation performed by the SDK calling method.

[0026] The embodiment of the present invention realizes the same function on multiple terminals by calling SDK. During the calling process, the interface can be configured according to the function program and the interface configuration information corresponding to each terminal, so that the function program of SDK can be directly called to realize the corresponding function. There is no need to develop a project file for each terminal, which greatly reduces the development time and labor costs. The SDK calling method has good versatility. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0028] Figure 1 It is an implementation environment of an SDK calling method provided by an embodiment of the present invention;

[0029] Figure 2 is a flowchart of an SDK calling method provided by an embodiment of the present invention;

[0030] Figure 3 is a flowchart of an SDK calling method provided by an embodiment of the present invention;

[0031] Figure 4 is a flowchart of an SDK calling method provided by an embodiment of the present invention;

[0032] Figure 5 is a flowchart of an SDK calling method provided by an embodiment of the present invention;

[0033] Figure 6 It is a flowchart for building and deploying engineering files in related technologies;

[0034] Figure 7 It is a structural diagram of an SDK calling device provided by an embodiment of the present invention;

[0035] Figure 8 It is a structural diagram of a server provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0036] In order to make the objectives, technical solutions and advantages of the present invention more clear, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

[0037] Figure 1 This is an implementation environment of an SDK calling method provided by an embodiment of the present invention, see Figure 1 , the implementation environment may include multiple servers 101 and code repositories 102. The code repositories 102 may be stored in one or more servers. Each server 101 may be a terminal of the same network service. For example, the terminals may include a web page (WorldWide Web, referred to as Web) terminal, a mini program terminal, a light application terminal, and an application (Application, APP) terminal.

[0038] In an embodiment of the present invention, the code repository 102 is used to provide a software development kit (SDK). Each server 101 can obtain the SDK from the code repository 102 and call the SDK during operation to implement the same function on different terminals.

[0039] Figure 2 is a flowchart of an SDK calling method provided by an embodiment of the present invention, which can be applied to a server, and the server can be the above-mentioned Figure 1 Server 101 is shown. Figure 2 , the method may include the following steps:

[0040] 201. Each server obtains the SDK from the code repository.

[0041] The servers may refer to the terminals of the same network service. In the embodiment of the present invention, only the example of each terminal obtaining the SDK from the code repository and calling the SDK is used for explanation. The same steps may be performed for any terminal, and the embodiment of the present invention does not limit this.

[0042] The SDK may include a function program and interface configuration information corresponding to multiple terminals. The function program is a program corresponding to the function that the SDK can implement, and the corresponding function can be implemented by executing the function program. The SDK is applicable to multiple terminals, and through the interface configuration information corresponding to the multiple terminals, the SDK can be called and the function can be implemented on the server where the multiple terminals are located.

[0043] For example, in some scenarios, the SDK can create a collection of application software development tools for software packages, software frameworks, hardware platforms, operating systems, etc. provided by third-party developers. The SDK can be used as a plug-in and applied to existing products, such as an advertising plug-in, chart plug-in, voting plug-in, weather plug-in or other custom plug-in, etc., and applied to corresponding projects and products.

[0044] Since the operating environments of different terminals are different, the steps that each server needs to perform when calling the SDK may also be different. Therefore, each server can first obtain the information of each terminal, and adopt the corresponding processing method based on the information of each terminal. For a server, it can first obtain the information of the current terminal, and adopt the corresponding steps based on the information of the current terminal.

[0045] In one possible implementation, each server obtains the SDK from the code repository based on a call request to the SDK. For either end, the user can perform an operation, and the server detects the user's operation and calls the SDK based on the operation.

[0046] In a specific possible embodiment, the SDK may include one functional program or multiple functional programs, each of which may correspond to one function. Any functional program may be displayed as a corresponding plug-in in the display interface provided by the server, so that the user may interact with the plug-in, thereby triggering the above-mentioned call request to the SDK.

[0047] The call request may be triggered based on an interactive operation with a plug-in corresponding to any function program of the SDK, and the call request includes information about the plug-in. Therefore, in steps 201 to 203, each server may call any function program corresponding to the plug-in of the SDK based on the target interface and the information of the plug-in, and execute the function corresponding to the any function program.

[0048] 202. Each server configures the target interface based on the functional program included in the SDK and the interface configuration information corresponding to each end.

[0049] After each server obtains the SDK, the SDK's functional programs are encapsulated in the SDK. If you want to call the SDK's functional programs, you need to configure it.

[0050] In a possible implementation, before step 202, after each server obtains the SDK, before executing the functional program, the SDK may be initialized. For example, during the initialization process, the execution environment of the SDK may be initialized, the header files required for calling the SDK may be imported, the execution parameters may be initialized, and then the target interface may be configured after the SDK is initialized.

[0051] In a specific possible embodiment of the above step 201, the SDK may include multiple functional programs. Each functional program may correspond to a different target interface. The step 202 may be: each server configures each of the multiple target interfaces based on each functional program included in the SDK and the interface configuration information corresponding to each end, and each target interface corresponds to each functional program. For any end, the server where the end is located may configure each of the multiple target interfaces based on each functional program included in the SDK and the interface configuration information corresponding to the current end.

[0052] When configuring the target interface, the interface configuration information of the SDK can be written into the target interface. Through this writing step, the parameters of the target interface can be adjusted, and then the SDK can be called through the target interface with the adjusted parameters. Of course, if the SDK includes multiple functional programs, when configuring multiple target interfaces, the information of each functional program can be written into the corresponding target interface, and a corresponding relationship is established between the two, and the corresponding functional program can be called based on the target interface.

[0053] In a specific possible embodiment, the multiple functional programs include a style configuration program and a business logic program. The style configuration program can be used to indicate the display style. The business logic program is used to indicate the processing logic to be executed. For example, if the display style of a certain plug-in is determined, its display style can be determined based on the style configuration program. From a server perspective, after the user performs an interactive operation, the server can determine the interactive result required to be fed back for the interactive operation based on the business logic program.

[0054] In this embodiment, the server may perform different configuration processing for different functional programs as follows: the server may configure the display interface based on the style configuration program included in the SDK and the interface configuration information corresponding to the current end, and may configure the business processing interface based on the business logic program included in the SDK and the interface configuration information corresponding to the current end.

[0055] 203. Each server calls the function program of the SDK based on the target interface to execute the function corresponding to the SDK.

[0056] After each server configures the target interface, it can call the SDK's function program based on the target interface to implement the corresponding function.

[0057] In the implementation mode in which the SDK includes multiple functional programs, each server can call the functional program corresponding to any target interface based on any target interface according to the configuration parameters of the any target interface and execute the function corresponding to the functional program. For one end, the server where the end is located can call the functional program corresponding to any target interface based on any target interface according to the configuration parameters of the any target interface and execute the function corresponding to the functional program.

[0058] For example, in a specific example, Figure 3 As shown, taking the SDK called on the Web side as an example, after the SDK is initialized, the target interface can be configured. In this example, each functional program is taken as a functional module, and the SDK includes a user interface (UI) rendering module, an event binding module, a business logic module and a data reporting module. The SDK may also include a morphology configuration. For the multiple functional modules, the morphology configuration is the above-mentioned style configuration program, and based on the morphology configuration, the display style when the UI rendering is performed can be determined. For the plug-in displayed by UI rendering, if the user performs an interactive operation on the plug-in, the processing method of the event binding of the interactive operation can be determined according to the event configuration module, so as to call the business logic module to perform the corresponding business processing. After processing, the data can also be reported to the server, or the interactive results can be fed back to the user. The Web interface (target interface) may include a display interface (Render Application Programming Interface, Render API), an event binding interface (API), a business logic API and a data reporting API. In the process of configuring the target interface, the corresponding relationship between each functional module and the API can be configured, and each functional module can be called through each target interface to realize the corresponding function.

[0059] In the above specific example, if Figure 4 As shown, the specific process of the SDK call can be the following steps. In the following process, taking the Web end as an example, the various functional structures of the server are named according to the different functions performed by the server. The details are as follows:

[0060] Step 1: The user accesses the Web product and enables a specific plug-in, which is the functional plug-in corresponding to the SDK.

[0061] Step 2: The SDK initialization module initializes the SDK environment of the plug-in, that is, initializes the SDK. After the initialization is successful, it can return to the initialization success.

[0062] Step 3: The SDK initialization module uses the Web interface to initialize the framework.

[0063] Step 4: The SDK initialization module registers the multi-terminal isomorphic framework in the Web interface.

[0064] The process of step three and step four is also the process of configuring the target interface.

[0065] Step 5. After successful configuration, the multi-terminal isomorphic framework can read the style configuration for UI rendering and event binding.

[0066] Step 6: The UI is rendered successfully, that is, the plug-in is displayed to the user, and the user can interact with the plug-in.

[0067] Step 7: The functional modules in the multi-terminal isomorphic framework can determine to respond to the interactive operation event, process it according to the business logic, and report the data to the server.

[0068] Step 8: Return the interaction result to the user based on the Web interface.

[0069] Based on the above content, the calling process of the SDK can be as follows Figure 5 As shown, the SDK supports multi-terminal calls, for example, WEB terminals, mini-program terminals, mini-game terminals and other platforms. The SDK can be installed on various platforms as a plug-in as an implementation of a certain business. The SDK can be initialized, and the interface implementations of various platforms can be performed. During the call process on any platform, the SDK provides the interface implementation of the current platform according to the specifications of the multi-terminal isomorphic framework. For example, WEB interface implementation, mini-program interface implementation, mini-game interface implementation or other interface implementations. Through this interface implementation, the registration and call of the multi-terminal isomorphic framework can be completed, and then the call to the SDK can be realized. The multiple terminals share the same SDK, or the multiple terminals share the same multi-terminal isomorphic framework, and unified business logic can be realized.

[0070] In contrast, Figure 6As shown, in the related art, developers usually develop a set of frameworks, which can include front-end logic code, and use an abstract syntax tree to decompose code conversion into template files, business logic files, and style configuration files, so that the multiple files are built into a process through the project builder and deployed on different ends. During deployment, it is necessary to perform framework conversion according to the end to be deployed, build a framework applicable to the end, and then complete the deployment. The use scenario of the deployment process in the related art is limited, and the framework must be developed as a whole. It cannot be applied to plug-in product development like the SDK calling method provided in the embodiment of the present invention, nor can it be introduced in existing products. And the framework development in the related art is generally developed for one or some platforms, and some platforms do not support it, and developers need to redevelop a new framework. The access to new features in the related art is limited. For the new features that are newly supported by each platform, developers can either wait for the framework version to be updated, or can only manually modify the existing framework source code, and the complexity of the framework source code is extremely high, and it is difficult for developers to change it.

[0071] The method provided by the embodiment of the present invention manages the common business logic in a unified manner in the framework, which is conducive to reducing development time and labor costs, and is conducive to the maintenance of program code and the long-term development of products. For example, in an application scenario of an advertising plug-in, assuming that the advertising plug-in supports three different platforms, and it takes an average of 5 people / day to develop a new advertising style or a new function on each platform, then through the above-mentioned related technology, the total development workload of the three platforms is 15 people / day. However, since the style configuration and business logic of the method provided by the embodiment of the present invention are uniformly managed by the isomorphic framework, developers only need to implement new advertising styles or new functions within the framework, and the total development workload only requires 5 people / day.

[0072] In addition, in the method provided by the embodiment of the present invention, each platform provides the implementation of the interface, and the framework is only responsible for unified scheduling, which is conducive to the access of new platforms and new features and the rapid development of products.

[0073] 204. When receiving the SDK update request, each server updates the functional programs included in the SDK.

[0074] If the functional program in the SDK is updated, each server can directly update the functional program in the SDK without waiting for the platform version to be updated or redeveloped as in the related technology. The update is convenient and fast.

[0075] In a possible implementation, the functional program included in the SDK can also be implemented based on the syntax abstract tree, and step 204 can be: when receiving the update request of the SDK, each server updates the structure of the syntax abstract tree based on the content of the update request. The use of the abstract syntax tree is very helpful for developers who specialize in developing business logic programs to update the functional program. For either end, the above steps can also be performed in the same way, and no further details are given.

[0076] The embodiment of the present invention realizes the same function on multiple terminals by calling SDK. During the calling process, the interface can be configured according to the function program and the interface configuration information corresponding to each terminal, so that the function program of SDK can be directly called to realize the corresponding function. There is no need to develop a project file for each terminal, which greatly reduces the development time and labor costs. The SDK calling method has good versatility.

[0077] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present invention, which will not be described in detail here.

[0078] Figure 7 is a schematic diagram of the structure of an SDK calling device provided by an embodiment of the present invention, see Figure 7 , the device may include:

[0079] An acquisition module 701 is used to acquire a software development kit SDK, wherein the SDK includes a functional program and interface configuration information corresponding to multiple terminals;

[0080] Configuration module 702, configured to configure the target interface based on the function program included in the SDK and the interface configuration information corresponding to the current end;

[0081] The calling module 703 is used to call the function program of the SDK based on the target interface to execute the function corresponding to the SDK.

[0082] In a possible implementation, the SDK includes a plurality of functional programs;

[0083] The configuration module 702 is used to configure each target interface among multiple target interfaces based on each function program included in the SDK and the interface configuration information corresponding to the current end, and each target interface corresponds to each function program.

[0084] In a possible implementation, the plurality of functional programs include a style configuration program and a business logic program;

[0085] The configuration module 702 is used for:

[0086] Based on the style configuration program included in the SDK and the interface configuration information corresponding to the current end, the display interface is configured;

[0087] The business processing interface is configured based on the business logic program included in the SDK and the interface configuration information corresponding to the current end.

[0088] In a possible implementation, the device further includes:

[0089] The update module is used to update the functional programs included in the SDK when receiving an update request of the SDK.

[0090] In a possible implementation, the functional program included in the SDK may be implemented based on a syntax abstract tree;

[0091] The update module is used to update the structure of the syntax abstract tree based on the content of the update request when receiving the update request of the SDK.

[0092] In a possible implementation, the device further includes:

[0093] The acquisition module 701, the configuration module 702 or the calling module 703 are further used to execute the steps of acquiring the software development kit SDK, configuring and calling when a calling request for the SDK is received, wherein the calling request is triggered based on an interactive operation performed on a plug-in corresponding to any functional program of the SDK, and the calling request includes information of the plug-in;

[0094] The calling module 703 is used to call any functional program corresponding to the plug-in of the SDK based on the target interface and the information of the plug-in, and execute the function corresponding to the any functional program.

[0095] The device provided by the embodiment of the present invention realizes the same function on multiple terminals by adopting the method of calling SDK. During the calling process, the interface can be configured according to the function program and the interface configuration information corresponding to each terminal, so that the function program of the SDK can be directly called to realize the corresponding function. There is no need to develop a project file for each terminal, which greatly reduces the development time and labor costs. The SDK calling method has good versatility.

[0096] It should be noted that: the SDK calling device provided in the above embodiment only uses the division of the above functional modules as an example when calling the SDK. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the server is divided into different functional modules to complete all or part of the functions described above. In addition, the SDK calling device provided in the above embodiment and the SDK calling method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0097] Figure 8 It is a structural diagram of a server provided by an embodiment of the present invention. The server 800 may have relatively large differences due to different configurations or performances, and may include one or more processors (central processing units, CPU) 801 and one or more memories 802, wherein at least one instruction is stored in the one or more memories 802, and the at least one instruction is loaded and executed by the one or more processors 801 to implement the SDK calling method provided by the above-mentioned various method embodiments. Of course, the server 800 may also have components such as a wired or wireless network interface, a keyboard, and an input and output interface for input and output. The server 800 may also include other components for implementing device functions, which will not be described in detail here.

[0098] In an exemplary embodiment, a computer-readable storage medium is also provided, such as a memory including instructions, and the instructions can be executed by a processor to complete the SDK calling method in the above embodiment. For example, the computer-readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, and an optical data storage device.

[0099] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0100] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for calling a software development kit SDK, characterized in that: The method comprises: Obtain a software development kit SDK, wherein the SDK includes multiple functional programs and interface configuration information corresponding to multiple terminals; Based on each function program included in the SDK and the interface configuration information corresponding to the current end, each target interface among the multiple target interfaces is configured, and each target interface corresponds to each function program; Based on the target interface, the function program of the SDK is called to execute the function corresponding to the SDK.

2. The method according to claim 1, characterized in that: The multiple functional programs include a style configuration program and a business logic program; The configuring each target interface among the multiple target interfaces based on each functional program included in the SDK and the interface configuration information corresponding to the current end includes: Based on the style configuration program included in the SDK and the interface configuration information corresponding to the current end, the display interface is configured; The business processing interface is configured based on the business logic program included in the SDK and the interface configuration information corresponding to the current end.

3. The method according to claim 1, characterized in that The method further comprises: When an update request for the SDK is received, the functional programs included in the SDK are updated.

4. The method according to claim 3, characterized in that The functional programs included in the SDK are implemented based on the syntax abstract tree; When receiving the SDK update request, updating the functional program included in the SDK includes: When an update request of the SDK is received, the structure of the syntax abstract tree is updated based on the content of the update request.

5. The method according to claim 1, characterized in that The method further comprises: When a call request for the SDK is received, the steps of obtaining the software development kit SDK, configuring and calling are performed, wherein the call request is triggered based on an interactive operation performed on a plug-in corresponding to any functional program of the SDK, and the call request includes information of the plug-in; The calling of the function program of the SDK based on the target interface to execute the function corresponding to the SDK includes: Based on the target interface and the information of the plug-in, any function program corresponding to the plug-in of the SDK is called to execute the function corresponding to the any function program.

6. A software development kit SDK calling device, characterized in that: The device comprises: An acquisition module is used to acquire a software development kit SDK, wherein the SDK includes multiple functional programs and interface configuration information corresponding to multiple terminals; A configuration module, configured to configure each of the multiple target interfaces based on each functional program included in the SDK and the interface configuration information corresponding to the current end, each target interface corresponding to each functional program; The calling module is used to call the function program of the SDK based on the target interface to execute the function corresponding to the SDK.

7. The device according to claim 6, characterized in that The multiple functional programs include a style configuration program and a business logic program; the configuration module is used to: Based on the style configuration program included in the SDK and the interface configuration information corresponding to the current end, the display interface is configured; The business processing interface is configured based on the business logic program included in the SDK and the interface configuration information corresponding to the current end.

8. The device according to claim 6, characterized in that The device also includes: The update module is used to update the functional programs included in the SDK when receiving an update request of the SDK.

9. The device according to claim 8, characterized in that The functional programs included in the SDK are implemented based on the syntax abstract tree; The updating module is used to update the structure of the syntax abstract tree based on the content of the updating request when receiving the updating request of the SDK.

10. The device according to claim 6, characterized in that The device also includes: The acquisition module, the configuration module or the calling module is further used to execute the steps of acquiring the software development kit SDK, configuring and calling when receiving a calling request for the SDK, wherein the calling request is triggered based on an interactive operation performed on a plug-in corresponding to any functional program of the SDK, and the calling request includes information of the plug-in; The calling module is used to call any functional program corresponding to the plug-in of the SDK based on the target interface and the information of the plug-in, and execute the function corresponding to the any functional program.

11. A server, characterized in that: The server includes one or more processors and one or more memories, wherein at least one instruction is stored in the one or more memories, and the instruction is loaded and executed by the one or more processors to implement the operation performed by the software development kit SDK calling method as described in any one of claims 1 to claim 5.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one instruction, which is loaded and executed by a processor to implement the operations performed by the software development kit SDK calling method according to any one of claims 1 to 5.

Images