CN110300165B - Method, device and equipment for calling functional program and storage medium - Google Patents
Method, device and equipment for calling functional program and storage medium Download PDFInfo
- Publication number
- CN110300165B CN110300165B CN201910563498.5A CN201910563498A CN110300165B CN 110300165 B CN110300165 B CN 110300165B CN 201910563498 A CN201910563498 A CN 201910563498A CN 110300165 B CN110300165 B CN 110300165B
- Authority
- CN
- China
- Prior art keywords
- interface
- calling
- program
- preset
- identification parameter
- 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
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the disclosure discloses a method, a device, equipment and a storage medium for calling a functional program, wherein the method for calling the functional program comprises the following steps: receiving a call instruction of a functional program sent by a server, wherein the call instruction comprises an identification parameter; determining a currently called interface from at least one interface in a preset interface group according to the calling instruction; and calling the functional program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called. The calling method, the calling device, the calling terminal and the readable medium of the functional program are used for solving the problems of large program change amount, high error rate and poor maintainability of a service layer in the SDK deleting or adding process.
Description
Technical Field
The present disclosure relates to computer software technologies, and in particular, to a method, an apparatus, a device, and a storage medium for calling a function program.
Background
Various Applications (APPs) can be installed in the intelligent terminal to meet different requirements of users, for example, a live webcast Application can be installed to watch live multimedia data, and a shopping Application can be installed to perform online shopping.
The program structure of an application program can be generally divided into a presentation layer, a business layer and a persistence layer, wherein the presentation layer can be used for interface display, the business layer can be used for method calling, and the persistence layer is used for data persistence operation. Various service functions can be realized by calling various Software Development Kits (SDKs) accessed by the service layer, for example, live webcast application can realize live webcast by calling the SDK with the function of connecting to the service layer, and beauty in the live webcast process can be realized by calling the SDK with the function of beautifying accessed by the service layer. Aiming at a certain service function, a service layer usually accesses SDKs provided by a plurality of manufacturers, so that after an application program is on the market, when the SDK provided by a certain manufacturer is abnormally called, the SDKs provided by other manufacturers can be quickly called, and the risk coping capability is improved; in addition, the SDK provided by each manufacturer includes a function program for implementing the service function, and the function program includes a plurality of interfaces for the application program to call.
In the prior art, a call relationship between a service layer and each interface in a plurality of SDK function programs corresponding to each service function needs to be established to realize the call of the service layer to each SDK function program. The defects of the prior art comprise: when an SDK is deleted or added, the call logic of each interface in the functional programs of the service layer and the deleted or added SDK needs to be updated, which results in large program change amount of the service layer, high error rate, and poor maintainability.
Disclosure of Invention
In view of this, the embodiments of the present disclosure provide a method, an apparatus, a device, and a storage medium for calling a function program, which are used to solve the problems of large program change amount, high error rate, and poor maintainability of a service layer in an SDK deleting or adding process.
In a first aspect, an embodiment of the present disclosure provides a method for calling a function program, which is applied to a service layer of an application program, and includes:
receiving a call instruction of a functional program sent by a server, wherein the call instruction comprises an identification parameter;
determining a currently called interface from at least one interface in a preset interface group according to the calling instruction;
and calling the functional program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
In a second aspect, an embodiment of the present disclosure provides an apparatus for calling a function program, including:
the instruction receiving module is used for receiving a calling instruction of a functional program sent by a server, wherein the calling instruction comprises an identification parameter;
the interface determining module is used for determining a currently called interface from at least one interface in a preset interface group according to the calling instruction;
and the function program calling module is used for calling the function program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
In a third aspect, an embodiment of the present disclosure provides a terminal device, including:
one or more processors;
a memory for storing one or more programs;
when the one or more programs are executed by the one or more processors, the one or more processors implement the calling method of the functional program according to any embodiment of the present disclosure.
In a fourth aspect, the embodiments of the present disclosure provide a computer storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the method for calling the functional program according to any one of the embodiments of the present disclosure.
The method comprises the steps that the service layer receives a calling instruction sent by a server, and the calling instruction comprises an identification parameter of the functional program to be called; the service layer calls at least one interface in a preset interface group in sequence according to the calling instruction, and in the process that each interface in the interface group is called, each interface can determine a functional program interface corresponding to the identification parameter from at least one functional program according to the identification parameter and call the functional program interface; when at least one interface in the preset interface group is called, namely, the function program interface corresponding to the identification parameter in each interface is called, so that the calling of the function program corresponding to the identification parameter is realized. By presetting an interface group comprising at least one interface and calling a function program corresponding to the identification parameter according to at least one interface in the interface group, when the function program is deleted or added, the calling relationship between the service layer and the interface group does not need to be changed, and the calling relationship between each interface in the interface group and the deleted or added function program interface only needs to be modified, so that the problems of large program change amount, high error rate and poor maintainability of the service layer are solved.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, a brief description will be given below to the drawings required for the embodiments or the technical solutions in the prior art, and it is obvious that the drawings in the following description are some embodiments of the present disclosure, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flowchart illustrating a method for calling a functional program according to an embodiment of the present disclosure;
fig. 2 is a flowchart illustrating a method for calling a functional program according to a second embodiment of the present disclosure;
fig. 3 is a flowchart illustrating a method for calling a functional program according to a third embodiment of the present disclosure;
fig. 4 shows a flowchart of a method for calling a microphone connecting function program according to a fourth embodiment of the present disclosure;
fig. 5 shows a schematic structural diagram of a calling device of a functional program according to a fifth embodiment of the present disclosure;
fig. 6 shows a schematic diagram of a hardware structure of a terminal device according to a sixth embodiment of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Example one
Fig. 1 shows a flowchart of a method for calling a function program according to a first embodiment of the present disclosure, where the embodiment of the present disclosure is applicable to a case of calling the function program, and the method may be implemented by a terminal, and may be implemented by software and/or hardware in the terminal.
As shown in fig. 1, the method for calling a functional program provided in the embodiment of the present disclosure is applied to a service layer of an application program, and includes the following steps:
s110, receiving a call instruction of the functional program sent by the server, wherein the call instruction comprises an identification parameter.
The functional program may be a functional program for implementing a business function in a Software Development Kit (SDK). The service layer of the application program can realize the service function by calling the function program in the SDK, for example, the service layer of the network live broadcast application can realize the wheat connection by calling the function program in the wheat connection SDK, and the beauty in the live broadcast process can be realized by calling the function program in the beauty SDK. For a certain service function, the service layer usually accesses SDKs provided by multiple manufacturers to improve risk response capability, that is, the service layer may call any one of the functional programs provided by different manufacturers to implement a service function. The identification parameters of the functional programs provided by different manufacturers can be preset and used for uniquely identifying the functional programs. The identification parameter may be a character string composed of at least one element of letters, numbers, symbols, or the like.
When monitoring user operation acting on an application program interface, the terminal can trigger a service layer of the application program to call a functional program for realizing a service function corresponding to the user operation. And before calling the functional program, the service layer can send a request message to the server, wherein the request message can be used for requesting the identification parameter of the functional program to be called. And after receiving the request message, the server can issue a calling instruction of the functional program to the service layer, wherein the calling instruction comprises an identification parameter for uniquely identifying the functional program.
And S120, determining a currently called interface from at least one interface in the preset interface group according to the calling instruction.
Optionally, determining a currently called interface from at least one interface in the preset interface group according to the call instruction includes: and determining the currently called interface from at least one interface in the preset interface group according to the calling instruction and the preset calling sequence.
The presetting process of the interface group may include: combing the service function realization steps of the functional programs in each SDK to be accessed to obtain the number N of the main steps and the calling sequence of the main steps; dividing a plurality of interfaces provided by each SDK into N groups according to the number N of the main steps and the calling sequence of the main steps, wherein each group of interfaces can realize one step in the main steps when being called, and each group of interfaces can realize the service function after being called according to the calling sequence of the main steps; defining N interfaces, respectively mapping the N groups of interfaces of each SDK to the defined N interfaces, and adding identification parameters of the N groups of interfaces of each SDK in the mapping process, wherein the identification parameters of the N groups of interfaces of each SDK are the same as the identification parameters of the functional programs of each SDK, and the calling sequence of the main step corresponding to the N groups of interfaces is the calling sequence of the defined interfaces mapped by the N groups of interfaces. The N defined interfaces can form a preset interface group, and the calling sequence of the interfaces is defined as a preset calling sequence.
For example, both SDK1 and SDK2 may implement a certain service function, and the identification parameters of the function programs of SDK1 and SDK2 are "SDK 1" and "SDK 2", respectively, the presetting process of the interface group may include: combing the service functions of the functional programs in the SDK1 and the SDK2 to obtain main steps S1 and S2, and calling S1 and then calling S2; the interface provided by the SDK1 is divided into two groups of an interface 11 and an interface 12, the interface provided by the SDK2 is divided into two groups of an interface 21 and an interface 22, wherein the step 1 can be realized by calling the interface 11 and the interface 21, and the step 2 can be realized by calling the interface 12 and the interface 22, wherein the service function can be realized by calling the interface 11 and then calling the interface 12, and the service function can also be realized by calling the interface 21 and then calling the interface 22; two interfaces, namely interface 1 and interface 2, are defined, interface 11 of SDK1 is mapped to interface 1, interface 12 of SDK1 is mapped to interface 2, interface 21 of SDK2 is mapped to interface 1, interface 22 of SDK2 is mapped to interface 2, and the identification parameter added to interface 11 and interface 12 is "SDK 1" and the identification parameter added to interface 21 and interface 22 is "SDK 2" in the mapping process, wherein since the service function can be realized by calling interface 11 first and then calling interface 12, the service function can also be realized by calling interface 21 first and then calling interface 22 first, and therefore the calling sequence of mapped interface 1 and interface 2 is that interface 1 is called first and then interface 2 is called first. The interface 1 and the interface 2 can form a preset interface group, and the interface 1 is called first and then the interface 2 is called to serve as a preset calling sequence.
At least one interface in the preset interface group can be called in sequence according to the calling instruction, the calling sequence of at least one interface in the preset interface group can be determined according to the preset calling sequence, and the interface needing to be called currently is determined as the current calling interface in sequence according to the calling sequence.
And S130, calling the functional program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
The identification parameters of the same functional program interface in each interface of the interface group are the same, for example, the interface group includes interface 1 and interface 2, interface 11 of SDK1 can be called through interface 1, interface 12 of SDK1 can be called through interface 2, where the identification parameters of interface 11 and interface 12 are the same. The interfaces in the interface group are sequentially called according to a preset calling sequence, in the calling process of each interface in the interface group, the functional program interface corresponding to the identification parameter is called through the currently called interface, and when the calling of each interface in the preset interface group is finished, each group of interfaces of the functional application program corresponding to the identification parameter can also be called, so that the calling of the functional program corresponding to the identification parameter is finished.
Optionally, the invoking the functional program interface corresponding to the identifier parameter through the currently invoked interface includes:
assigning a preset variable in a program in a currently called interface according to the identification parameter; and determining a functional program interface corresponding to the identification parameter from at least one functional program interface contained in the program in the currently called interface according to the preset variable, and calling the functional program interface corresponding to the identification parameter.
When each interface is defined in the interface group presetting process, a variable can be predefined in the interface definition method process, and the variable can be assigned according to the identification parameter in the received calling instruction. In the process of defining the method for each interface, the corresponding relation between different variable assignments and the functional program interface can be defined, so that the functional program interface corresponding to the identification parameter can be determined from at least one functional program interface contained in the program in the currently called interface according to the preset variable, and the functional program interface corresponding to the identification parameter is called.
In addition, when the functional program of the SDK is newly added, a plurality of interfaces provided by the SDK to be newly added can be divided into N groups according to the number N of the main steps and the calling sequence of the main steps, wherein each group of interfaces can realize one step in the main steps when being called, and each group of interfaces can realize the service function after being called according to the calling sequence of the main steps; respectively mapping N groups of interfaces of the SDK to be newly added to N interfaces of a preset interface group, and adding identification parameters of the N groups of interfaces of the SDK to be newly added in the mapping process, wherein the identification parameters of the N groups of interfaces of the SDK to be newly added are the same as the identification parameters of the functional program of the newly added SDK, and the calling sequence of the main step corresponding to the N groups of interfaces is the calling sequence of the definition interfaces mapped by the N groups of interfaces. When the functional program of the SDK is removed, the mapping relation between the N groups of interfaces of the SDK to be removed and the N interfaces of the preset interface group is canceled from the N interfaces of the preset interface group. Therefore, when the functional program is deleted or added, the calling relationship between the service layer and the interface group does not need to be changed, and the calling relationship between each interface in the interface group and the deleted or added functional program interface only needs to be modified, so that the problems of large program modification amount, high error rate and poor maintainability of the service layer are solved.
In the method for calling the functional program provided by the embodiment of the disclosure, a service layer receives a calling instruction issued by a server, wherein the calling instruction comprises an identification parameter of the functional program to be called; the service layer calls at least one interface in the preset interface group in sequence according to the calling instruction and the preset calling sequence, and in the process that each interface in the interface group is called, each interface can determine a functional program interface corresponding to the identification parameter from at least one functional program according to the identification parameter and call the functional program interface; when at least one interface in the preset interface group is called, namely, the functional program interfaces corresponding to the identification parameters in each interface are called according to the preset calling sequence, so that the calling of the functional programs corresponding to the identification parameters is realized. By presetting an interface group comprising at least one interface and calling a function program corresponding to the identification parameter according to at least one interface in the interface group, when the function program is deleted or added, the calling relationship between the service layer and the interface group does not need to be changed, and the calling relationship between each interface in the interface group and the deleted or added function program interface only needs to be modified, so that the problems of large program change amount, high error rate and poor maintainability of the service layer are solved.
Example two
In the present embodiment, a call instruction is further described on the basis of the above embodiment, which belongs to the same inventive concept as the method for calling a function program proposed in the above embodiment, and the technical details that are not described in detail in the present embodiment may be referred to in the above embodiment.
Optionally, the call instruction further includes a type parameter; correspondingly, according to the call instruction and the preset call sequence, determining the currently called interface from at least one interface in the preset interface group, including: and determining a target interface group from at least one preset interface group according to the type parameters, and determining a currently called interface from at least one interface in the target interface group.
Fig. 2 shows a flowchart of a method for calling a functional program according to a second embodiment of the present disclosure, where the method for calling a functional program according to the second embodiment of the present disclosure includes the following steps:
s210, receiving a call instruction of a functional program issued by a server, wherein the call instruction comprises an identification parameter and a type parameter;
s220, determining a target interface group from at least one preset interface group according to the type parameters, and determining a currently called interface from at least one interface in the target interface group;
and S230, calling the functional program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
The application program can realize various service functions, for example, live webcast application can realize a microphone connecting service function, and can also realize a beauty service function in the live webcast process. Different interface groups can be preset aiming at different service functions, and type parameters can be set for the different interface groups, so that the type of the service function can be realized by the interface group is uniquely identified. After receiving a call instruction issued by a server, the service layer may determine a target interface group according to a type parameter in the call instruction, and sequentially call at least one interface in the target interface group according to a preset call sequence, thereby implementing the call of a plurality of interface groups.
For example, the interface group 1 may be preset for the microphone connecting service function, and the type parameter of the interface group 1 is "Connection", and the interface group 2 may be preset for the Beauty service function, and the type parameter of the interface group 2 is "Beauty". When the type parameter in the call instruction received by the service layer is "Beauty", it may be determined that the target interface group is the interface group 2, and then at least one interface in the interface group 2 is sequentially called.
In this embodiment, based on the above embodiment, a call instruction is further described, and a target interface group can be determined from at least one preset interface group through a type parameter included in the call instruction, so that the call of a function program is realized when a plurality of interface groups are provided. In addition, the method for calling a function program provided by the above embodiment belongs to the same inventive concept, and technical details that are not described in detail in this embodiment can be referred to the above embodiment, and the present embodiment has the same beneficial effects as the above embodiment.
EXAMPLE III
The present embodiment further describes a case where the function program interface fails to be called on the basis of the above embodiment, which is the same inventive concept as the method for calling the function program proposed in the above embodiment, and the technical details that are not described in detail in the present embodiment may be referred to in the above embodiment.
Optionally, if the interface of the function program corresponding to the currently called interface calling identification parameter fails, a calling exception message is generated and fed back to the server, so that the server issues a calling instruction of the function program including the updated identification parameter.
Fig. 3 shows a flowchart of a method for calling a functional program provided in the third embodiment of the present disclosure, where the method for calling a functional program provided in the third embodiment of the present disclosure includes the following steps:
s310, receiving a call instruction of a functional program sent by a server, wherein the call instruction comprises an identification parameter;
s320, determining a currently called interface from at least one interface in a preset interface group according to the calling instruction;
s330, calling a function program interface corresponding to the identification parameter through the currently called interface;
s340, judging whether the function program interface is successfully called;
s350, if the function program interface is successfully called, determining the currently called interface from at least one interface in the preset interface group again until the calling of at least one interface in the preset interface group is finished;
s360, if the calling of the functional program interface fails, generating a calling abnormal message and feeding the calling abnormal message back to the server so as to enable the server to issue a calling instruction of the functional program containing the updated identification parameters;
and S370, when receiving the calling instruction of the updated function program for identifying the parameters, repeatedly executing the steps S320-S360 until at least one interface in the preset interface group is called.
If the function program interface corresponding to any interface calling identification parameter in the preset interface group fails, the function program cannot be called, at this time, a calling exception message can be generated and fed back to the server, wherein the calling exception message can include exception interface information, so that the calling exception position of the function program interface can be quickly positioned, and the updating and maintenance of the application program are facilitated. When the server receives the calling abnormal message, the server can update the identification parameter, generate a calling instruction containing the updated identification parameter, and issue the calling instruction again so that the service layer calls other functional application programs to realize the service function. When the calling of the functional program interface fails, a calling abnormal message is generated and fed back to the server, so that the server issues a calling instruction of the functional program containing the updated identification parameters, and the functional program parameters are called according to the updated calling instruction, thereby improving the risk coping capability of the application program.
The step of updating the identification parameters may be that the server updates the identification parameters according to the error rate of each function program that completes the service function online. The server may select, as the updated identification parameter, an identification parameter of a functional program with a low error rate, in addition to the identification parameter before the update.
In this embodiment, on the basis of the above embodiment, a case of a call failure of the functional program interface is further described, and by generating a call exception message and feeding back the call exception message to the server when the call failure of the functional program interface occurs, the server issues a call instruction of the functional program including the updated identification parameter, and calls the functional program parameter according to the updated call instruction, thereby improving the risk response capability of the application program. In addition, the method for calling a function program provided by the above embodiment belongs to the same inventive concept, and technical details that are not described in detail in this embodiment can be referred to the above embodiment, and the present embodiment has the same beneficial effects as the above embodiment.
Example four
In this embodiment, based on the above embodiment, a function program is further described as a hayman function program, which belongs to the same inventive concept as the method for calling a function program proposed in the above embodiment, and the technical details that are not described in detail in this embodiment can be referred to in the above embodiment.
Fig. 4 shows a flowchart of a method for calling a microphone connecting function program according to a fourth embodiment of the present disclosure, where the method for calling a function program according to the fourth embodiment of the present disclosure includes the following steps:
s410, receiving a call instruction of the microphone connecting function program issued by the server, wherein the call instruction comprises an identification parameter of the microphone connecting function program;
s420, determining a currently called interface from at least one interface in a preset interface group according to the calling instruction;
and S430, calling the microphone connecting function program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
For example, the presetting process of the interface group corresponding to the microphone connecting function program may include:
the method comprises the steps of combing service functions of functional programs in the wheat-connecting SDK1 and the wheat-connecting SDK2 to obtain a main step S1, and carrying out signaling interaction between an anchor A and an anchor B, wherein for example, the anchor A can send a wheat-connecting application to the anchor B, and the anchor B can agree with the application; and S2, the two anchor broadcasters respectively pull the audio and video stream of the opposite party to realize the connection of the wheat. And calling S1 first and then S2 can implement two-cast connecting wheat.
The steps of the functional programs in the liam SDK1 and the liam SDK2 for realizing the service functions are substantially the same as those of the main step, and there may be differences in names of the steps and methods or in splitting the main step into sub-steps. According to the number and calling sequence of the main steps, a plurality of interfaces provided by the connecting SDK1 are divided into two groups of an interface 11 and an interface 12, and a plurality of interfaces provided by the connecting SDK2 are divided into two groups of an interface 21 and an interface 22, wherein the step S1 can be realized by calling the interface 11 and the step S1 can be realized by calling the interface 12 and the step S2 can be realized by calling the interface 11 and then calling the interface 12, and the connecting service function can be realized by calling the interface 21 and then calling the interface 22.
Defining two interfaces, namely an interface 1 and an interface 2, mapping an interface 11 of a connecting SDK1 to the interface 1, mapping an interface 12 of a connecting SDK1 to the interface 2, mapping an interface 21 of a connecting SDK2 to the interface 1, mapping an interface 22 of the connecting SDK2 to the interface 2, adding an identification parameter of the interface 11 and the interface 12 to be 'connecting SDK 1' in the mapping process, and adding an identification parameter of the interface 21 and the interface 22 to be 'connecting SDK 2', wherein because the service function can be realized by calling the interface 11 and then calling the interface 12 and the service function can also be realized by calling the interface 21 and then calling the interface 22, the calling sequence of the mapped interface 1 and interface 2 is that the interface 1 is called first and then calling the interface 2. The interface 1 and the interface 2 can form a preset interface group, and the interface 1 is called first and then the interface 2 is called to serve as a preset calling sequence.
Further, if the identification parameter of the microphone connecting function program in the call instruction of the microphone connecting function program received by the service layer is 'microphone connecting SDK 1', sequentially calling an interface 1 and an interface 2 in the preset interface group. And when the interface 1 is called, the interface 1 calls the interface 11 according to the identification parameter 'connecting to the wheat SDK 1'; when the interface 2 is called, the interface 2 calls the interface 12 according to the identification parameter 'Lianmai SDK 1', so that the calling of the function program in the Lianmai SDK1 is realized.
The present embodiment further describes that the function program is a linkman function program on the basis of the above embodiment, which belongs to the same inventive concept as the method for calling the function program proposed in the above embodiment, and the technical details that are not described in detail in the present embodiment may refer to the above embodiment, and the present embodiment has the same beneficial effects as the above embodiment.
EXAMPLE five
Fig. 5 is a schematic structural diagram illustrating a calling device of a functional program according to a fifth embodiment of the present disclosure, where the fifth embodiment of the present disclosure is applicable to a case of calling the functional program. The function program calling device provided by the present disclosure can implement the function program calling method provided by the above-described embodiment.
As shown in fig. 5, the apparatus for calling a function program in an embodiment of the present disclosure includes:
the instruction receiving module 510 is configured to receive a call instruction of a function sequence issued by a server, where the call instruction includes an identifier parameter;
an interface determining module 520, configured to determine, according to the call instruction, a currently called interface from at least one interface in the preset interface group;
the function program calling module 530 is configured to call, through the currently called interface, the function program interface corresponding to the identifier parameter until at least one interface in the preset interface group is called.
Optionally, the function program calling module includes:
the assignment submodule is used for assigning a preset variable in the program in the currently called interface according to the identification parameter;
and the function program calling submodule is used for determining a function program interface corresponding to the identification parameter from at least one function program interface contained in the program in the currently called interface according to the preset variable and calling the function program interface corresponding to the identification parameter.
Optionally, the call instruction further includes a type parameter; correspondingly, the interface determination module is specifically configured to: and determining a target interface group from at least one preset interface group according to the type parameters, and determining a currently called interface from at least one interface in the target interface group.
Optionally, the calling device of the function program further includes:
the calling abnormal message generating module is used for generating calling abnormal messages and feeding the calling abnormal messages back to the server if the function program interface corresponding to the currently called interface calling identification parameters fails, so that the server sends a calling instruction of the function program containing the updated identification parameters;
correspondingly, the instruction receiving module is used for receiving a call instruction of the functional program which is sent by the server and contains the updated identification parameters; the interface determining module is used for determining a currently called interface from at least one interface in the preset interface group according to the calling instruction of the updated functional program for identifying the parameters; and the function program calling module is used for calling the function program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
Optionally, the functional program includes a wheat connecting functional program; correspondingly, the instruction receiving module is used for receiving a call instruction of the microphone connecting function program issued by the server, wherein the call instruction comprises an identification parameter of the microphone connecting function program; the interface determining module is used for determining a currently called interface from at least one interface in the preset interface group according to the calling instruction; and the function program calling module is used for calling the microphone connecting function program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
The calling device of the functional program provided by the embodiment of the present disclosure and the calling method of the functional program provided by the embodiment belong to the same inventive concept, and technical details that are not described in detail in the embodiment of the present disclosure may refer to the embodiment, and the embodiment of the present disclosure have the same beneficial effects.
EXAMPLE six
Fig. 6 shows a schematic diagram of a hardware structure of a terminal device according to a sixth embodiment of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 6 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 6, the electronic device 600 may include a processing means (e.g., central processor, graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read-Only Memory (ROM) 602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 6 illustrates an electronic device 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of the embodiments of the present disclosure.
The terminal provided by the embodiment of the present disclosure and the method for calling the function program provided by the embodiment belong to the same inventive concept, and technical details that are not described in detail in the embodiment of the present disclosure may be referred to the embodiment, and the embodiment of the present disclosure have the same beneficial effects.
EXAMPLE seven
The disclosed embodiments provide a computer storage medium on which a computer program is stored, which when executed by a processor implements the calling method of the functional program provided by the above embodiments.
It should be noted that the computer storage media described above in this disclosure can be computer readable signal media or computer readable storage media or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM) or FLASH Memory (FLASH), an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer storage may be contained in the electronic device; or may exist separately without being assembled into the electronic device.
The computer stores one or more programs that, when executed by the electronic device, cause the electronic device to: receiving a calling instruction of a functional program sent by a server, wherein the calling instruction comprises an identification parameter; determining a currently called interface from at least one interface in a preset interface group according to the calling instruction and a preset calling sequence; and calling the functional program interface corresponding to the identification parameter through the currently called interface, and determining the currently called interface from at least one interface in the preset interface group again after the functional program interface is successfully called until the calling of at least one interface in the preset interface group is finished.
Alternatively, the computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a calling instruction of a functional program sent by a server, wherein the calling instruction comprises an identification parameter; determining a currently called interface from at least one interface in a preset interface group according to the calling instruction and a preset calling sequence; and calling the functional program interface corresponding to the identification parameter through the currently called interface, and determining the currently called interface from at least one interface in the preset interface group again after the functional program interface is successfully called until the calling of at least one interface in the preset interface group is finished.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of an element does not in some cases constitute a limitation on the element itself.
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
According to one or more embodiments of the present disclosure, [ example one ] there is provided a method for calling a function program, applied to a service layer of an application program, including:
receiving a call instruction of a functional program sent by a server, wherein the call instruction comprises an identification parameter;
determining a currently called interface from at least one interface in a preset interface group according to the calling instruction;
and calling the functional program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
According to one or more embodiments of the present disclosure, [ example two ] there is provided a method of calling a functional program, further comprising:
optionally, determining a currently called interface from at least one interface in a preset interface group according to the call instruction includes:
and determining a currently called interface from at least one interface in a preset interface group according to the calling instruction and a preset calling sequence.
According to one or more embodiments of the present disclosure, [ example three ] there is provided a method of calling a functional program, further comprising:
optionally, the invoking the functional program interface corresponding to the identifier parameter through the currently invoked interface includes:
assigning a preset variable in a program in a currently called interface according to the identification parameter;
and determining a functional program interface corresponding to the identification parameter from at least one functional program interface contained in the program in the currently called interface according to the preset variable, and calling the functional program interface corresponding to the identification parameter.
According to one or more embodiments of the present disclosure, [ example four ] there is provided a method of calling a functional program, further comprising:
optionally, the call instruction further includes a type parameter; correspondingly, according to the call instruction and the preset call sequence, determining the currently called interface from at least one interface in the preset interface group, including:
and determining a target interface group from at least one preset interface group according to the type parameters, and determining a currently called interface from at least one interface in the target interface group.
According to one or more embodiments of the present disclosure, [ example five ] there is provided a method of calling a functional program, further comprising:
optionally, the method for calling a functional program further includes:
if the interface of the function program corresponding to the currently called interface calling identification parameter fails, a calling abnormal message is generated and fed back to the server, so that the server issues a calling instruction of the function program containing the updated identification parameter.
According to one or more embodiments of the present disclosure, [ example six ] there is provided a method of calling a functional program, further comprising:
optionally, the functional program includes a wheat connecting functional program; correspondingly, the calling method comprises the following steps:
receiving a call instruction of a microphone connecting function program issued by a server, wherein the call instruction comprises an identification parameter of the microphone connecting function program;
determining a currently called interface from at least one interface in a preset interface group according to a calling instruction;
and calling the microphone connecting function program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
According to one or more embodiments of the present disclosure, [ example seven ] there is provided an invoking device of a function program, including:
the instruction receiving module is used for receiving a calling instruction of a functional program sent by a server, wherein the calling instruction comprises an identification parameter;
the interface determining module is used for determining a currently called interface from at least one interface in a preset interface group according to the calling instruction;
and the function program calling module is used for calling the function program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
According to one or more embodiments of the present disclosure, [ example eight ] there is provided an invoking apparatus of a functional program, further comprising:
optionally, the interface determining module is specifically configured to: and determining a currently called interface from at least one interface in a preset interface group according to the calling instruction and a preset calling sequence.
According to one or more embodiments of the present disclosure, [ example nine ] there is provided an invoking apparatus of a function program, further comprising:
optionally, the function program calling module includes:
the assignment submodule is used for assigning a preset variable in the program in the currently called interface according to the identification parameter;
and the function program calling submodule is used for determining a function program interface corresponding to the identification parameter from at least one function program interface contained in the program in the currently called interface according to the preset variable and calling the function program interface corresponding to the identification parameter.
According to one or more embodiments of the present disclosure, [ example ten ] there is provided an invoking apparatus of a functional program, further comprising:
optionally, the call instruction further includes a type parameter; correspondingly, the interface determination module is specifically configured to: and determining a target interface group from at least one preset interface group according to the type parameters, and determining a currently called interface from at least one interface in the target interface group according to a preset calling sequence.
The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (12)
1. A method for calling a function program, which is applied to a service layer of an application program, comprises the following steps:
receiving a call instruction of a functional program sent by a server, wherein the call instruction comprises an identification parameter;
determining a currently called interface from at least one interface in a preset interface group according to the calling instruction;
calling a functional program interface corresponding to the identification parameter through a currently called interface until at least one interface in the preset interface group is called;
the identification parameters can identify the functional program and also can identify a functional program interface, and the functional program interface is preset with the identification parameters.
2. The method according to claim 1, wherein the determining a currently called interface from at least one interface in a preset interface group according to the call instruction comprises:
and determining a currently called interface from at least one interface in a preset interface group according to the calling instruction and a preset calling sequence.
3. The method according to claim 1, wherein said calling the functional program interface corresponding to the identification parameter through the currently called interface comprises:
assigning a preset variable in a program in the currently called interface according to the identification parameter;
and determining a functional program interface corresponding to the identification parameter from at least one functional program interface contained in a program in the currently called interface according to the preset variable, and calling the functional program interface corresponding to the identification parameter.
4. The method of claim 1, wherein the call instruction further comprises a type parameter; correspondingly, according to the call instruction, determining a currently called interface from at least one interface in a preset interface group, including:
and determining a target interface group from at least one preset interface group according to the type parameter, and determining a currently called interface from at least one interface in the target interface group.
5. The method of any of claims 1-4, further comprising:
if the currently called interface fails to call the functional program interface corresponding to the identification parameter, generating a call exception message and feeding the call exception message back to the server so that the server issues a call instruction of the functional program containing the updated identification parameter.
6. The method for calling a functional program according to claim 1, wherein the functional program comprises a Lianmai functional program; correspondingly, the calling method comprises the following steps:
receiving a call instruction of a microphone connecting function program issued by a server, wherein the call instruction comprises an identification parameter of the microphone connecting function program;
determining a currently called interface from at least one interface in a preset interface group according to the calling instruction;
and calling the microphone connecting function program interface corresponding to the identification parameter through the currently called interface until at least one interface in the preset interface group is called.
7. An apparatus for calling a function program, comprising:
the instruction receiving module is used for receiving a calling instruction of a functional program sent by a server, wherein the calling instruction comprises an identification parameter;
the interface determining module is used for determining a currently called interface from at least one interface in a preset interface group according to the calling instruction;
the function program calling module is used for calling a function program interface corresponding to the identification parameter through a currently called interface until at least one interface in the preset interface group is called;
the identification parameters can identify the functional program and also can identify a functional program interface, and the functional program interface is preset with the identification parameters.
8. The apparatus of claim 7, wherein the interface determination module is specifically configured to:
and determining a currently called interface from at least one interface in a preset interface group according to the calling instruction and a preset calling sequence.
9. The apparatus of claim 7, wherein the function calling module comprises:
the assignment submodule is used for assigning a preset variable in a program in the currently called interface according to the identification parameter;
and the function program calling submodule is used for determining a function program interface corresponding to the identification parameter from at least one function program interface contained in a program in a currently called interface according to the preset variable and calling the function program interface corresponding to the identification parameter.
10. The apparatus of claim 7, wherein the call instruction further comprises a type parameter; correspondingly, the interface determination module is specifically configured to: and determining a target interface group from at least one preset interface group according to the type parameter, and determining a currently called interface from at least one interface in the target interface group.
11. A terminal device, characterized in that the terminal comprises:
one or more processors;
a memory for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement a calling method of a functional program as recited in any of claims 1-6.
12. A computer storage medium on which a computer program is stored, characterized in that the program, when executed by a processor, implements a method of calling a functional program as claimed in any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910563498.5A CN110300165B (en) | 2019-06-26 | 2019-06-26 | Method, device and equipment for calling functional program and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910563498.5A CN110300165B (en) | 2019-06-26 | 2019-06-26 | Method, device and equipment for calling functional program and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110300165A CN110300165A (en) | 2019-10-01 |
| CN110300165B true CN110300165B (en) | 2021-11-12 |
Family
ID=68029065
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910563498.5A Active CN110300165B (en) | 2019-06-26 | 2019-06-26 | Method, device and equipment for calling functional program and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110300165B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111190661B (en) * | 2019-12-31 | 2021-09-28 | 腾讯科技（深圳）有限公司 | Data processing method and equipment |
| CN111240927B (en) * | 2020-01-03 | 2024-01-30 | 北京小米移动软件有限公司 | Method, device and storage medium for detecting time consumption of method in program |
| CN111447395B (en) * | 2020-03-05 | 2023-11-28 | 视联动力信息技术股份有限公司 | Data communication method, device, terminal equipment and storage medium |
| CN113836497B (en) * | 2020-06-24 | 2024-09-20 | 武汉杰开科技有限公司 | Program running method, integrated circuit chip and related device |
| CN111796802B (en) * | 2020-06-30 | 2023-09-12 | 北京字节跳动网络技术有限公司 | Function package generation method and device and electronic equipment |
| CN112230982A (en) * | 2020-10-15 | 2021-01-15 | 北京达佳互联信息技术有限公司 | Material processing method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106411970A (en) * | 2015-07-28 | 2017-02-15 | 阿里巴巴集团控股有限公司 | Fault handling method, device and system based on service call |
| CN109240838A (en) * | 2018-09-20 | 2019-01-18 | 深圳市牛鼎丰科技有限公司 | Interface call method, device, computer equipment and storage medium |
| CN109408256A (en) * | 2018-10-17 | 2019-03-01 | 麒麟合盛网络技术股份有限公司 | Using call method and device |
| CN109640191A (en) * | 2017-10-09 | 2019-04-16 | 武汉斗鱼网络科技有限公司 | A kind of method and apparatus of even wheat live streaming |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9454410B2 (en) * | 2008-03-04 | 2016-09-27 | Microsoft Technology Licensing, Llc | Transparent integration of application components |
| US9420031B2 (en) * | 2013-01-15 | 2016-08-16 | Microsoft Technology Licensing, Llc | Systems and methods for building and using hybrid mobile applications |
| US9507609B2 (en) * | 2013-09-29 | 2016-11-29 | Taplytics Inc. | System and method for developing an application |
-
2019
- 2019-06-26 CN CN201910563498.5A patent/CN110300165B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106411970A (en) * | 2015-07-28 | 2017-02-15 | 阿里巴巴集团控股有限公司 | Fault handling method, device and system based on service call |
| CN109640191A (en) * | 2017-10-09 | 2019-04-16 | 武汉斗鱼网络科技有限公司 | A kind of method and apparatus of even wheat live streaming |
| CN109240838A (en) * | 2018-09-20 | 2019-01-18 | 深圳市牛鼎丰科技有限公司 | Interface call method, device, computer equipment and storage medium |
| CN109408256A (en) * | 2018-10-17 | 2019-03-01 | 麒麟合盛网络技术股份有限公司 | Using call method and device |
Non-Patent Citations (2)
| Title |
|---|
| "Design and Development of Embedded Multimedia Terminal";Jie Cao，Lei Yin，Hong Zhao;《2010 Ninth International Symposium on Distributed Computing and Applications to Business, Engineering and Science》;20100916;全文 * |
| "如何用即构sdk开发实现小程序直播";海水冷却;《CSDN博客》;20190517;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110300165A (en) | 2019-10-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110300165B (en) | Method, device and equipment for calling functional program and storage medium | |
| CN111679990B (en) | Test data generation method and device, readable medium and electronic equipment | |
| CN110390493B (en) | Task management method and device, storage medium and electronic equipment | |
| CN111163324B (en) | Information processing method and device and electronic equipment | |
| CN110781373A (en) | List updating method and device, readable medium and electronic equipment | |
| CN111432001A (en) | Method, apparatus, electronic device, and computer-readable medium for jumping scenes | |
| CN111309415A (en) | UI (user interface) information processing method and device of application program and electronic equipment | |
| CN114513552A (en) | Data processing method, device, equipment and storage medium | |
| CN112685075A (en) | Gray scale distribution method and device, electronic equipment and computer readable medium | |
| CN115470754A (en) | Data analysis method and device, computer readable medium and electronic equipment | |
| CN111212296B (en) | Live broadcast room gift list configuration method, device, medium and electronic equipment | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN113518183A (en) | Camera calling method and device and electronic equipment | |
| CN113127550A (en) | Information processing method, information processing device, electronic equipment and storage medium | |
| CN111538717A (en) | Data processing method and device, electronic equipment and computer readable medium | |
| CN112115154A (en) | Data processing and data query method, device, equipment and computer readable medium | |
| CN114764282A (en) | Information processing method, device, terminal and storage medium | |
| CN112162682A (en) | Content display method and device, electronic equipment and computer readable storage medium | |
| CN111399730A (en) | Image processing method, image processing device, electronic equipment and computer readable storage medium | |
| CN111291254A (en) | Information processing method and device | |
| CN118158082B (en) | Method, device, equipment and medium for updating communication resource message of intelligent household equipment | |
| CN111367590A (en) | Interrupt event processing method and device | |
| CN116319322B (en) | Power equipment node communication connection method, device, equipment and computer medium | |
| CN111294321B (en) | Information processing method and device | |
| CN111694679B (en) | Message processing method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |