Remote interface debugging method, device, storage medium, electronic equipment and system

Abstract

The present disclosure relates to a remote interface debugging method, device, storage medium, electronic device and system, the method comprising: generating a remote interface call request; performing data processing on the call parameters carried by the remote interface call request to obtain interface call protocol data, wherein the data processing is used to convert the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interactive protocol; sending the interface call protocol data to the second terminal device so that the second terminal device parses the interface call protocol data and calls the second target method according to the parsing result based on the reflection mechanism. There is no need to package the development environment information of the first terminal device into a specific file and install it to the second terminal device to be tested. The SDK interface of the second terminal device can identify and parse the interface call protocol data, so that the first terminal device can remotely call the SDK interface of the second terminal device.

Description

Technical Field

[0001] The present disclosure relates to the field of electronic information technology, and in particular, to a remote interface debugging method, device, storage medium, electronic device and system. Background Art

[0002] In game development technology, game development on the PC (personal computer) side uses the game engine as the development engine and adopts the C# programming language for engineering development. When testing the game terminal, the PC side needs to call the terminal's SDK (Software Development Kit) interface to implement it.

[0003] At present, the game engine needs to package the development environment information into a specific file and install it on the terminal to be tested before it can call the SDK interface on the terminal. For example, if the device is an Android system, the development environment needs to be packaged into an APK (Android application package) file and installed on the device to realize remote calling, which will reduce the efficiency of functional testing and occupy the terminal's memory. Summary of the invention

[0004] This summary is provided to introduce concepts in a brief form that will be described in detail in the detailed description below. This summary is not intended to identify key features or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0005] In a first aspect, the present disclosure provides a remote interface debugging method, applied to a first terminal device, comprising:

[0006] Generate remote interface call request;

[0007] Performing data processing on the call parameters carried in the remote interface call request to obtain interface call protocol data, wherein the data processing is used to convert the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interaction protocol;

[0008] The interface calling protocol data is sent to the second terminal device, so that the second terminal device parses the interface calling protocol data and calls the second target method according to the parsing result based on the reflection mechanism.

[0009] In a second aspect, the present disclosure provides a remote interface debugging device, comprising:

[0010] A generation module, used to generate a remote interface call request;

[0011] A processing module, used for performing data processing on the call parameters carried by the remote interface call request to obtain interface call protocol data, wherein the data processing is used to convert the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interaction protocol;

[0012] The sending module is used to send the interface calling protocol data to the second terminal device, so that the second terminal device parses the interface calling protocol data and calls the second target method according to the parsing result based on the reflection mechanism.

[0013] In a third aspect, the present disclosure provides a computer-readable medium having a computer program stored thereon, which implements the steps of the method described in the first aspect when the program is executed by a processing device.

[0014] In a fourth aspect, the present disclosure provides an electronic device, including:

[0015] a storage device having a computer program stored thereon;

[0016] A processing device is used to execute the computer program in the storage device to implement the steps of the method in the first aspect.

[0017] In a fifth aspect, the present disclosure provides a remote interface debugging system, including:

[0018] A first terminal device, used for generating a remote interface call request, performing digital processing on a call parameter carried in the remote interface call request to obtain interface call protocol data, and sending the interface call protocol data to a second terminal device connected to the first terminal device, wherein the digital processing is used for converting the call parameter into protocol data supported by the SDK interface of the second terminal device according to a preconfigured first interaction protocol;

[0019] The second terminal device is used to parse the interface call protocol data and call the second target method according to the parsing result based on the reflection mechanism.

[0020] Through the above technical solution, the call parameters carried in the interface call request are digitized to obtain interface call protocol data. Since the interface call protocol data converts the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interaction protocol, there is no need to package the development environment information of the first terminal device into a specific file and install it to the second terminal device to be tested. The SDK interface of the second terminal device can directly identify and parse the interface call protocol data to realize the remote call of the SDK interface of the second terminal device by the first terminal device, which reduces the memory occupancy of the second terminal device and improves the efficiency of terminal testing; and the second terminal device calls the second target method based on the reflection mechanism to realize dynamic acquisition of the second target method in the running state.

[0021] Other features and advantages of the present disclosure will be described in detail in the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the originals and elements are not necessarily drawn to scale. In the drawings:

[0023] Figure 1 The figure is a flowchart of a remote interface debugging method according to an exemplary embodiment of the present disclosure.

[0024] Figure 2 The present invention is a flowchart showing a second terminal device calling a second target method according to an exemplary embodiment of the present disclosure.

[0025] Figure 3 This is another flowchart of a second terminal device calling a second target method according to an exemplary embodiment of the present disclosure.

[0026] Figure 4 The diagram is an interactive diagram of a remote interface debugging method according to an exemplary embodiment of the present disclosure.

[0027] Figure 5 The figure is a block diagram of a remote interface debugging device according to an exemplary embodiment of the present disclosure.

[0028] Figure 6 It is a schematic structural diagram of an electronic device according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0029] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0030] It should be understood that the various steps described in the method embodiments of the present disclosure may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this respect.

[0031] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "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". The relevant definitions of other terms will be given in the following description.

[0032] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0033] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0034] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0035] As described in the background technology section, in the prior art, when performing game function testing, the development environment can only be packaged into a format file supported by the tested terminal to remotely perform the function test, which consumes a lot of time and memory. Based on this, the present disclosure provides the following technical solutions, which effectively reduce the memory usage of the tested terminal and improve the test efficiency of the program execution function test.

[0036] First, technical terms used in the present disclosure will be explained.

[0037] Interface: Interface refers to the application programming interface, which is the capability entry point exposed by the program to the outside world and shields the internal implementation details.

[0038] Method callback: The scenario is the call of an asynchronous method. The callback uses the interface handle to obtain and call the reference of the subclass that implements the interface. The callback is triggered and executed at a certain time.

[0039] Reflection mechanism: It means that in the running state, for any class, all the properties and methods of this class can be known, and for any object, any method and property of it can be called.

[0040] Dynamic proxy: A technique that creates a proxy object of a target object and performs functional enhancements on methods in the target object during program execution. In the process of generating a proxy object, the target object remains unchanged, and the methods in the proxy object are enhanced methods of the target object methods. It can be understood as dynamic interception of methods in an object during execution, and functional operations are performed before and after the interception method.

[0041] Figure 1 is a flowchart of a remote interface debugging method according to an exemplary embodiment of the present disclosure. The remote interface debugging method is applied to a first terminal device, referring to Figure 1 , the remote interface debugging method comprises the following steps:

[0042] In step 101, a remote interface call request is generated.

[0043] The remote interface call request carries call parameters, which may include class information, method information, parameter information, etc. of the called remote interface. In the present disclosure, the called remote interface refers to the SDK interface of the second terminal device.

[0044] In some embodiments, the first terminal device may be a game engine, and the second terminal device may be an Android phone.

[0045] In step 102, the call parameters carried in the remote interface call request are digitized to obtain interface call protocol data, wherein the digitization is used to convert the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interaction protocol.

[0046] It is worth noting that the first interactive protocol is used to represent the structured data agreed upon by the first terminal device and the second terminal device, and the data processing is used to encapsulate the call parameters into the structured data agreed upon by the first terminal device and the second terminal device according to the first interactive protocol.

[0047] For example, taking a piece of code as an example, the structure data can be:

[0048] {"ClassName:com.demo.TestLoginAgent",

[0049] "MethodName:login",

[0050] "IsOstatic:false",

[0051] "Params:["param"]",

[0052] "CallBack:[{

[0053] "CallBack className:com,demo.Login Listener",

[0054] "Call Backld:10",

[0055] "Paramlndex:1"

[0056] }]"}

[0057] In the above structure data, the information of the call parameters is recorded in the form of key-value pairs. For example, ClassName:com.demo.TestLoginAgent is a key-value pair of class field and class name.

[0058] For example, the interface call protocol data may be encapsulated in Json format.

[0059] For example, the first terminal device and the second terminal device may be connected via a long connection or a short connection, which is not limited in this embodiment.

[0060] In step 103, the interface call protocol data is sent to the second terminal device, so that the second terminal device parses the interface call protocol data and calls the second target method based on the parsing result of the reflection mechanism.

[0061] When parsing the interface calling protocol data, the second terminal device may parse it according to the first interactive protocol to obtain the calling parameters to call the second target method.

[0062] Through the above technical solution, the call parameters carried in the interface call request are digitized to obtain interface call protocol data. Since the interface call protocol data converts the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the pre-configured first interaction protocol, there is no need to package the development environment information of the first terminal device into a specific file and install it to the second terminal device to be tested. The SDK interface of the second terminal device can directly identify and parse the interface call protocol data to realize the remote call of the SDK interface of the second terminal device by the first terminal device, which reduces the memory occupancy of the terminal device and improves the efficiency of terminal testing; and the second terminal device calls the second target method based on the reflection mechanism to realize dynamic acquisition of the second target method in the running state.

[0063] In the following, the first terminal device may be a game engine, and the second terminal device may be an Android phone. Figure 2 The process of the second terminal device calling the second target method in the present disclosure is further explained. Figure 2 , the game engine generates an interface call protocol (i.e., interface protocol call data), the mobile SDK side parses the protocol data (i.e., parses the interface protocol call data) to obtain class, method, parameter information (i.e., class field, call method field, and basic type parameter field), dynamically obtains class instances (i.e., instance objects), obtains parameters (i.e., parameters corresponding to basic type parameter fields), combines parameters to obtain a parameter list, calibrates the parameters in the parameter list, dynamically obtains methods (i.e., the second target method of the instance object), and then dynamically executes the second target method. Among them, Figure 2 The process shown is explained in detail with reference to the following embodiments.

[0064] In a possible manner, the interface call protocol data includes a class field, a call method field, and a basic type parameter field, and the second terminal device calls the second target method according to the parsing result based on the reflection mechanism in the following manner: parse the interface call protocol data according to the first interaction protocol to obtain the class field, the call method field, and the basic type parameter field; obtain the instance object based on the reflection mechanism according to the class name corresponding to the class field; calibrate the type of the parameter corresponding to the basic type parameter field; and obtain the second target method corresponding to the instance object based on the reflection mechanism according to the call method field; and call the second target method based on the reflection mechanism according to the calibrated parameters.

[0065] It is worth noting that, based on the reflection mechanism, it can be understood that in the running state of the second terminal device, the instance object and the second target method corresponding to the instance object can be dynamically obtained, and the second target method can be dynamically executed.

[0066] It is worth noting that since the first interactive protocol is a structured data form agreed upon by the first terminal device and the second terminal device, the second terminal device can parse the interface call protocol data according to the first interactive protocol to obtain the class field, calling method field and basic type parameter field.

[0067] Wherein, in the case where the interface call protocol data includes a class field, a call method field, and a basic type parameter field, the interface call protocol data encapsulated by Json may be shown in the following table:

[0068] First level field Field Description ClassName SDK class name, including the full path, passed in by the first terminal device MethodName Calling method name Params Parameter List

[0069] The first-level field indicates the category of the calling parameter, ClassName indicates the class field, which is used to mark the subclass interface of the SDK and the path of the subclass interface. MethodName indicates the calling method field, and Params indicates the basic type parameter field. The parameter list is arranged in the order of parameter passing of all parameters involved in the calling method.

[0070] For example, the parameter type of the parameter includes but is not limited to Boolean type, Integer type, Double type, Long type, etc. Since the development environment, language, etc. of the first terminal device and the second terminal device are different, the parameter type requirements of the parameters corresponding to the basic type parameter field are different. For example, the game engine has an Integer type, but the Android system corresponds to the Long type. If the parameter type is not calibrated in the Android system, the Android system cannot correctly identify the Integer type, resulting in a call error. Therefore, in this application scenario, in order to execute the method call normally, the Integer type parameter needs to be calibrated to the Long type parameter.

[0071] Therefore, in order to shield the data type differences between different languages, through the above method, the second terminal device can calibrate the parameter type of the parameter corresponding to the basic type parameter field obtained by parsing, so as to avoid the second terminal device from making a call error when calling the second target method.

[0072] In a possible manner, the above-mentioned step of calibrating the type of the parameter corresponding to the basic type parameter field may include: generating a parameter array according to the parameter corresponding to the basic type parameter field; determining the calling function declared by the method calling field according to the calling method field; for each parameter in the parameter array, calibrating the type of the parameter according to the type of the parameter and the type of the function parameter at the same position as the parameter in the calling function.

[0073] For example, the parameters corresponding to the basic type parameter field may include multiple parameters, and the multiple parameters may be presented in the form of a list. The elements of the parameter array are the parameters arranged in the order of the parameters in the list.

[0074] It should be noted that the calling function declared in the method calling field and the second target method corresponding to the method calling field refer to the same piece of program code. The calling function is a function that can be normally called by the second terminal device, and the type of the parameter passed in the calling function is the type of the parameter that can be correctly recognized by the second terminal device.

[0075] Through the above method, the type of each parameter in the parameter array is calibrated according to the type of function parameters of the function that can be normally called by the second terminal device and corresponds to the method call field, so as to avoid method call errors caused by differences in data types on the second terminal device.

[0076] In a possible manner, the step of calibrating the type of each parameter in the parameter array according to the type of the parameter and the type of the function parameter at the same position as the parameter in the calling function may include: in the case where there are multiple calling functions, determining a calling function having the same number of function parameters as the number of parameters from the multiple calling functions according to the number of parameters of the parameters included in the parameter array, and obtaining a target calling function; and calibrating the type of each parameter in the parameter array according to the type of the parameter and the type of the function variable at the same position as the parameter in the target calling function.

[0077] It should be understood that the number of function parameters of the target call parameter is consistent with the number of parameters included in the parameter array.

[0078] It should be noted that the same position can be determined by the order of the parameter array and the order of the function parameters passed to the calling function. For example, the type of the second parameter in the parameter array should be calibrated according to the type of the second function parameter passed to the calling function.

[0079] Taking into account the multiple calling functions with the same name corresponding to the method calling field, therefore, when there are multiple calling functions, the target calling function corresponding to the method calling field can be determined according to the number of function parameters of the calling function based on the specific code of each calling function, thereby ensuring the accuracy of parameter type correction.

[0080] In a possible way, it is considered that the game engine and the Android system mobile phone have parameter types that can be supported at the same time, for example, Boolean type. For parameter types that can be supported at the same time, the terminal device does not need to calibrate such parameters. Therefore, the above step of calibrating the parameters corresponding to the basic type parameter field may also include: obtaining a type mapping table, the type mapping table includes multiple first-class parameter types and second-class parameter types corresponding to each first-class parameter type, calibrating the type of the parameters belonging to the first-class parameter type in the parameters corresponding to the basic type parameter field, and the parameter type of the parameters belonging to the first-class parameter type in the parameters corresponding to the basic type parameter field can be converted into the second-class parameter type corresponding to the first-class parameter type, so as to achieve the calibration of the parameter type.

[0081] It should be noted that one type of parameter type is a parameter type that cannot be supported by the first terminal device and the second terminal device at the same time, that is, a type that needs to be calibrated.

[0082] By calibrating only functions belonging to one parameter type, the time occupied by parameter calibration can be effectively reduced, and the efficiency of terminal device function testing can be further improved.

[0083] In a possible manner, the interface call protocol data also includes a callback type parameter field, and the method also includes: receiving interface callback protocol data returned by the second terminal device, wherein the interface callback protocol data is generated based on the call result of the second target method; parsing the interface callback protocol data, and calling the first target method according to the parsing result based on the reflection mechanism.

[0084] First of all, it should be noted that when the first terminal device performs a functional test on the second terminal device, in certain remote call situations, the first terminal device needs to respond to some specific call results of the second terminal device, that is, callback. For example, in the scenario of testing the login function of the second terminal device, the first terminal device calls the interface of the second terminal device to implement remote login. In the case of a login failure of the second terminal device, the first terminal device needs to analyze the cause of the failure. Since the first terminal device and the second terminal device are cross-device remote calls, there is no same runtime state and the execution state handle cannot be held. This requires the second terminal device to provide feedback on the failure state and failure cause information of the login method execution when the login method fails.

[0085] The following combination Figure 3 The example of the mobile phone SDK execution process is further explained in the present disclosure when the interface call protocol data also includes a callback type parameter field. Figure 3The mobile SDK side obtains the corresponding callback instance class and callback instance object by parsing the interface call protocol data. The callback instance class and callback instance object refer to the calling object that needs to send the callback result to the game engine side. The dynamic proxy instance object monitors the calling result of the callback method (i.e., the second target method), encapsulates the callback protocol according to the callback result, obtains the received callback protocol data, and sends it to the game engine side. The game engine side parses the callback protocol data and executes the call of the corresponding method (the first target method). Among them, refer to the following embodiments and the interaction process between the first terminal device and the second terminal device. Figure 3 Provide detailed explanation. Figure 4 FIG. 1 is a schematic diagram of the interaction process between the first terminal device and the second terminal device. Figure 4 As shown, after the second terminal device executes the call of the second target method, the second terminal device first generates interface callback protocol data according to the call result of calling the second target method and sends it to the first terminal device. Then, the first terminal device parses the interface callback protocol data and calls the first target method according to the parsing result based on the reflection mechanism.

[0086] For example, the second terminal device may monitor the instance object in the following manner: dynamically create a proxy object of the instance object, where the proxy object is used to monitor the call result of the second target method of the instance object.

[0087] For example, in the scenario where the second target method is a login method, when the login method execution failure is monitored, the callback method name and callback parameters are determined according to the call result information of the second terminal device calling the login method. For example, the method corresponding to the callback method name can be a method for executing when the second terminal device fails to log in. For example, in the code of the second target method, if the execution fails, method A (i.e., the callback method name) is called, and if the execution succeeds, the login interface of successful login is returned. The callback parameters are the parameters required by the method corresponding to the callback method name.

[0088] For example, the interface callback protocol data is obtained by the second terminal device encapsulating the callback method name, callback parameters and callback type parameter fields according to the preconfigured second interaction protocol. Similar to the first interaction protocol, the second interaction protocol also represents the structure data agreed upon by the first terminal device and the second terminal device.

[0089] The interface callback protocol data encapsulated by Json can be shown in the following table:

[0090] First level field Field Description CallBackID The identifier of the CallBack instance object of the first terminal device MethodName The method name of the interface callback result Params Callback method parameters

[0091] The first terminal device pre-caches a CallBack instance, obtains the CallBack instance object through the identifier of the CallBack instance object, and executes a call to the method name of the interface callback result corresponding to the CallBack instance object. It should be understood that the identifier of the CallBack instance object of the first terminal device is carried in the interface call protocol data.

[0092] The method name of the interface callback result is the callback method name, which is used to indicate the method that the first terminal device should execute, that is, the first target method.

[0093] The parameters of the callback method are the parameters that need to be passed into the method corresponding to the callback method name.

[0094] In a possible manner, the above-mentioned steps of parsing the interface callback protocol data line and calling the first target method according to the parsing result based on the reflection mechanism may include: parsing the interface callback protocol data according to the second interaction protocol to obtain the callback instance object identifier, the callback method name and the callback parameters; obtaining the cached callback instance object based on the reflection mechanism according to the callback instance object identifier; obtaining the first target method corresponding to the callback instance object based on the reflection mechanism according to the callback method name; and calling the first target method based on the reflection mechanism according to the callback parameters.

[0095] It should be noted that, similar to the second terminal device's understanding of the reflection mechanism, the second terminal device can also dynamically obtain the callback instance object and the first target method corresponding to the callback instance object in the running state based on the reflection mechanism, and can dynamically call the first target method.

[0096] Among them, the CallBack instance object is cached in advance, and there is no need to create the CallBack instance after receiving the interface call protocol data, thus improving the execution efficiency of the overall closed-loop test.

[0097] In a possible manner, when the interface call protocol data also includes a callback type parameter field, the above step of generating a parameter array based on the parameters corresponding to the basic type parameter field may include: generating a parameter array based on the parameters corresponding to the basic type parameter field and the callback parameters under the callback type parameter field, wherein each element in the parameter array is arranged in the arrangement order of the passed parameters of the second target method.

[0098] For example, when the interface call protocol data also includes a callback type parameter field, the interface call protocol data encapsulated by Json is shown in the following table:

[0099]

[0100] It should be noted that CallBackClassName corresponds to the class name of the interface called by the first terminal device, and path corresponds to the interface path of the interface. ParamsIndex represents the order of parameters that the callback function needs to pass in in the second target method.

[0101] It should be noted that a callback function is a function that is passed as a parameter. Therefore, when calibrating the parameters, the type of the callback function should also be calibrated to prevent the terminal device from causing method call errors due to differences in data types.

[0102] Based on the same inventive concept, the present disclosure provides a remote interface debugging device, such as Figure 5 As shown, the remote interface debugging device 500 includes:

[0103] A generating module 501 is used to generate a remote interface call request;

[0104] The processing module 502 is used to perform data processing on the call parameters carried by the remote interface call request to obtain interface call protocol data, wherein the data processing is used to convert the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interaction protocol;

[0105] The sending module 503 is used to send the interface calling protocol data to the second terminal device, so that the second terminal device parses the interface calling protocol data and calls the second target method according to the parsing result based on the reflection mechanism.

[0106] Optionally, the interface calling protocol data includes a class field, a calling method field and a basic type parameter field, and the second terminal device calls the second target method according to the parsing result based on the reflection mechanism in the following manner:

[0107] Parsing the interface call protocol data according to the first interaction protocol to obtain the class field, the call method field and the basic type parameter field;

[0108] According to the class name corresponding to the class field, obtaining the instance object based on the reflection mechanism;

[0109] calibrating the type of the parameter corresponding to the basic type parameter field; and,

[0110] According to the calling method field, acquiring a second target method corresponding to the instance object based on the reflection mechanism;

[0111] According to the calibrated parameters, the second target method is called based on the reflection mechanism.

[0112] Optionally, the type of the parameter corresponding to the basic type parameter field is calibrated in the following manner, including:

[0113] Generate a parameter array according to the parameters corresponding to the basic type parameter field;

[0114] Determine, according to the calling method field, the calling function declared by the method calling field;

[0115] For each of the parameters in the parameter array, the type of the parameter is calibrated according to the type of the parameter and the type of the function parameter at the same position as the parameter in the calling function.

[0116] Optionally, the parameter corresponding to the basic type parameter field is calibrated in the following manner, including:

[0117] In the case where the calling function includes multiple functions, according to the number of parameters of the parameters included in the parameter array, a calling function having the same number of function parameters as the number of parameters is determined from the multiple calling functions to obtain a target calling function;

[0118] For each parameter in the parameter array, the type of the parameter is calibrated according to the type of the parameter and the type of the function variable at the same position as the parameter in the target calling function.

[0119] Optionally, the interface calling protocol data further includes a callback type parameter field, and the apparatus 500 further includes:

[0120] A receiving module, configured to receive interface callback protocol data returned by the second terminal device, wherein the interface callback protocol data is generated based on a call result of the second target method;

[0121] The calling module is used to parse the interface callback protocol data line and call the first target method according to the parsing result based on the reflection mechanism.

[0122] Optionally, the second terminal device generates the interface callback protocol data based on the calling result of the second target method in the following manner:

[0123] Creating a proxy object of the instance object, wherein the proxy object is used to monitor the calling result of the second target method of the instance object;

[0124] Determine the callback method name and callback parameters according to the calling result of the second target;

[0125] According to the preconfigured second interaction protocol, the callback method name, the callback parameter, and the callback instance object identifier under the callback type parameter field are converted into interface callback protocol data supported by the first terminal device.

[0126] Optionally, the calling module includes:

[0127] A parsing submodule, which parses the interface callback protocol data according to the second interaction protocol to obtain the callback instance object identifier, the callback method name and the callback parameters;

[0128] An acquisition submodule, used for acquiring the cached callback instance object based on the reflection mechanism according to the callback instance object identifier;

[0129] According to the callback method name, based on the reflection mechanism, obtain a first target method corresponding to the callback instance object;

[0130] The calling submodule is used to call the first target method based on the reflection mechanism according to the callback parameter.

[0131] Optionally, the parameter array is generated in the following manner:

[0132] A parameter array is generated according to the parameters corresponding to the basic type parameter field and the callback parameters under the callback type parameter field, wherein each element in the parameter array is arranged in the order of the transmission parameters of the second target method.

[0133] Based on the same inventive concept, an embodiment of the present disclosure discloses a computer-readable medium on which a computer program is stored, characterized in that the program implements the steps of the method embodiment when executed by a processing device.

[0134] Based on the same inventive concept, the present disclosure embodiment discloses a remote interface debugging system, including:

[0135] A first terminal device, used for generating a remote interface call request, performing digital processing on a call parameter carried in the remote interface call request to obtain interface call protocol data, and sending the interface call protocol data to a second terminal device connected to the first terminal device, wherein the digital processing is used for converting the call parameter into protocol data supported by the SDK interface of the second terminal device according to a preconfigured first interaction protocol;

[0136] The second terminal device is used to parse the interface call protocol data and call the second target method according to the parsing result based on the reflection mechanism.

[0137] Based on the same inventive concept, the present disclosure discloses an electronic device, including:

[0138] a storage device having a computer program stored thereon;

[0139] A processing device is used to execute the computer program in the storage device to implement the steps in the method embodiment.

[0140] Reference below Figure 6 , which shows a schematic diagram of the structure of an electronic device 600 suitable for implementing the embodiment of the present disclosure. The terminal device in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 6 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0141] like Figure 6 As shown, the electronic device 600 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage device 608 into a random access memory (RAM) 603. In the RAM 603, various programs and data required for the operation of the electronic device 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 the bus 604.

[0142] Typically, the following devices may be connected to the I / O interface 605: an input device 606 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 607 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 608 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 609. The communication device 609 may allow the electronic device 600 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 6 The electronic device 600 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0143] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device 609, or installed from a storage device 608, or installed from a ROM 602. When the computer program is executed by the processing device 601, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0144] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0145] In some embodiments, the electronic device can communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and can be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0146] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0147] The above-mentioned computer-readable medium carries one or more programs. When the above-mentioned one or more programs are executed by the electronic device, the electronic device: generates a remote interface call request; performs data processing on the call parameters carried by the remote interface call request to obtain interface call protocol data, wherein the data processing is used to convert the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interaction protocol; sends the interface call protocol data to the second terminal device, so that the second terminal device parses the interface call protocol data, and calls the second target method according to the parsing result based on the reflection mechanism.

[0148] Alternatively, the computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device: receives the interface call protocol data sent by the first terminal device, parses the interface call protocol data, and calls the second target method according to the parsing result based on the reflection mechanism.

[0149] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving 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 may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0150] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0151] The modules involved in the embodiments described in the present disclosure may be implemented by software or hardware. The name of a module does not limit the module itself in some cases. For example, a generation module may also be described as a "module for generating remote interface call requests."

[0152] The functions described above herein 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 chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0153] In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A 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, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0154] According to one or more embodiments of the present disclosure, Example 1 provides a remote interface debugging method, which is applied to a first terminal device and includes:

[0155] Generate remote interface call request;

[0156] Performing data processing on the call parameters carried in the remote interface call request to obtain interface call protocol data, wherein the data processing is used to convert the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interaction protocol;

[0157] The interface calling protocol data is sent to the second terminal device, so that the second terminal device parses the interface calling protocol data and calls the second target method according to the parsing result based on the reflection mechanism.

[0158] According to one or more embodiments of the present disclosure, Example 2 provides a method of Example 1, wherein the interface call protocol data includes a class field, a call method field, and a basic type parameter field, and the second terminal device calls the second target method according to the parsing result based on the reflection mechanism in the following manner:

[0159] Parsing the interface call protocol data according to the first interaction protocol to obtain the class field, the call method field and the basic type parameter field;

[0160] According to the class name corresponding to the class field, an instance object is obtained based on a reflection mechanism;

[0161] calibrating the type of the parameter corresponding to the basic type parameter field; and,

[0162] According to the calling method field, acquiring a second target method corresponding to the instance object based on the reflection mechanism;

[0163] According to the calibrated parameters, the second target method is called based on the reflection mechanism.

[0164] According to one or more embodiments of the present disclosure, Example 3 provides a method of Example 2,

[0165] The calibrating the type of the parameter corresponding to the basic type parameter field includes:

[0166] Generate a parameter array according to the parameters corresponding to the basic type parameter field;

[0167] Determine, according to the calling method field, the calling function declared by the method calling field;

[0168] For each of the parameters in the parameter array, the type of the parameter is calibrated according to the type of the parameter and the type of the function parameter at the same position as the parameter in the calling function.

[0169] According to one or more embodiments of the present disclosure, Example 4 provides a method of Example 3, wherein for each parameter in the parameter array, the type of the parameter is calibrated according to the type of the parameter and the type of the function parameter at the same position as the parameter in the calling function, including:

[0170] In the case where the calling function includes multiple functions, according to the number of parameters of the parameters included in the parameter array, a calling function having the same number of function parameters as the number of parameters is determined from the multiple calling functions to obtain a target calling function;

[0171] For each parameter in the parameter array, the type of the parameter is calibrated according to the type of the parameter and the type of the function variable at the same position as the parameter in the target calling function.

[0172] According to one or more embodiments of the present disclosure, Example 5 provides a method of Example 2, wherein the interface call protocol data further includes a callback type parameter field, and the method further includes:

[0173] Receiving interface callback protocol data returned by the second terminal device, wherein the interface callback protocol data is generated based on the calling result of the second target method;

[0174] The interface callback protocol data line is parsed, and the first target method is called according to the parsing result based on the reflection mechanism.

[0175] According to one or more embodiments of the present disclosure, Example 6 provides a method of Example 5, wherein the second terminal device generates the interface callback protocol data based on the call result of the second target method in the following manner: creating a proxy object of the instance object, the proxy object being used to monitor the call result of the second target method of the instance object;

[0176] Determine the callback method name and callback parameters according to the calling result of the second target method;

[0177] According to the preconfigured second interaction protocol, the callback method name, the callback parameter, and the callback instance object identifier under the callback type parameter field are converted into interface callback protocol data supported by the first terminal device.

[0178] According to one or more embodiments of the present disclosure, Example 7 provides a method of Example 5, wherein parsing the interface callback protocol data line and calling the first target method according to the parsing result based on the reflection mechanism includes:

[0179] Parsing the interface callback protocol data according to the second interaction protocol to obtain the callback instance object identifier, the callback method name and the callback parameters;

[0180] According to the callback instance object identifier, obtaining the cached callback instance object based on the reflection mechanism;

[0181] According to the callback method name, based on the reflection mechanism, obtain a first target method corresponding to the callback instance object;

[0182] According to the callback parameter, the first target method is called based on the reflection mechanism.

[0183] According to one or more embodiments of the present disclosure, Example 8 provides a method of Example 5,

[0184] The generating a parameter array according to the parameters corresponding to the basic type parameter field comprises:

[0185] A parameter array is generated according to the parameters corresponding to the basic type parameter field and the callback parameters under the callback type parameter field, wherein each element in the parameter array is arranged in the order of the transmission parameters of the second target method.

[0186] According to one or more embodiments of the present disclosure, Example 9 provides a remote interface debugging device, including:

[0187] A generation module, used to generate a remote interface call request;

[0188] A processing module, used for performing data processing on the call parameters carried by the remote interface call request to obtain interface call protocol data, wherein the data processing is used to convert the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interaction protocol;

[0189] The sending module is used to send the interface calling protocol data to the second terminal device, so that the second terminal device parses the interface calling protocol data and calls the second target method according to the parsing result based on the reflection mechanism.

[0190] According to one or more embodiments of the present disclosure, Example 10 provides a computer-readable medium having a computer program stored thereon, which implements the steps of any of the methods described in Examples 1-8 when executed by a processing device.

[0191] According to one or more embodiments of the present disclosure, Example 11 provides an electronic device, including:

[0192] a storage device having a computer program stored thereon;

[0193] A processing device is used to execute the computer program in the storage device to implement the steps of any one of the methods described in Examples 1-8.

[0194] According to one or more embodiments of the present disclosure, Example 12 provides a remote interface debugging system, including:

[0195] A first terminal device, used for generating a remote interface call request, performing digital processing on a call parameter carried in the remote interface call request to obtain interface call protocol data, and sending the interface call protocol data to a second terminal device connected to the first terminal device, wherein the digital processing is used for converting the call parameter into protocol data supported by the SDK interface of the second terminal device according to a preconfigured first interaction protocol;

[0196] The second terminal device is used to parse the interface call protocol data and call the second target method according to the parsing result based on the reflection mechanism.

[0197] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in the present disclosure (but not limited to) by each other to form a technical solution.

[0198] In addition, although each operation is described in a specific order, this should not be understood as requiring these operations to be performed in the specific order shown or in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0199] Although the subject matter has been described in language specific to structural features and / or method logic actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims. Regarding the device in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Claims

1. A remote interface debugging method, characterized in that: Applied to the first terminal device, including: Generate remote interface call request; Performing data processing on the call parameters carried in the remote interface call request to obtain interface call protocol data, wherein the data processing is used to convert the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interaction protocol; Sending the interface call protocol data to the second terminal device, so that the second terminal device parses the interface call protocol data and calls the second target method according to the parsing result based on the reflection mechanism; The interface call protocol data includes a class field, a call method field and a basic type parameter field. The second terminal device calls the second target method according to the parsing result based on the reflection mechanism in the following manner: the interface call protocol data is parsed according to the first interaction protocol to obtain the class field, the call method field and the basic type parameter field; based on the class name corresponding to the class field, an instance object is obtained based on the reflection mechanism; the type of the parameter corresponding to the basic type parameter field is calibrated; and, based on the call method field, a second target method corresponding to the instance object is obtained based on the reflection mechanism; and based on the calibrated parameters, the second target method is called based on the reflection mechanism.

2. The method according to claim 1, characterized in that The calibrating the type of the parameter corresponding to the basic type parameter field includes: Generate a parameter array according to the parameters corresponding to the basic type parameter field; Determine the calling function declared by the calling method field according to the calling method field; For each of the parameters in the parameter array, the type of the parameter is calibrated according to the type of the parameter and the type of the function parameter at the same position as the parameter in the calling function.

3. The method according to claim 2, characterized in that The step of calibrating the type of each parameter in the parameter array according to the type of the parameter and the type of a function parameter at the same position as the parameter in the calling function comprises: In the case where the calling function includes multiple functions, according to the number of parameters of the parameters included in the parameter array, a calling function having the same number of function parameters as the number of parameters is determined from the multiple calling functions to obtain a target calling function; For each parameter in the parameter array, the type of the parameter is calibrated according to the type of the parameter and the type of the function variable at the same position as the parameter in the target calling function.

4. The method according to claim 1, characterized in that: The interface call protocol data also includes a callback type parameter field, and the method further includes: Receiving interface callback protocol data returned by the second terminal device, wherein the interface callback protocol data is generated based on the calling result of the second target method; The interface callback protocol data line is parsed, and the first target method is called according to the parsing result based on the reflection mechanism.

5. The method according to claim 4, characterized in that The second terminal device generates the interface callback protocol data based on the calling result of the second target method in the following manner: Creating a proxy object of the instance object, wherein the proxy object is used to monitor the calling result of the second target method of the instance object; Determine the callback method name and callback parameters according to the calling result of the second target method; According to the preconfigured second interaction protocol, the callback method name, the callback parameter, and the callback instance object identifier under the callback type parameter field are converted into interface callback protocol data supported by the first terminal device.

6. The method according to claim 4, characterized in that The parsing of the interface callback protocol data line, and calling the first target method according to the parsing result based on the reflection mechanism, includes: Parsing the interface callback protocol data according to the second interactive protocol to obtain a callback instance object identifier, a callback method name, and callback parameters; According to the callback instance object identifier, obtaining the cached callback instance object based on the reflection mechanism; According to the callback method name, based on the reflection mechanism, obtain a first target method corresponding to the callback instance object; According to the callback parameter, the first target method is called based on the reflection mechanism.

7. The method according to claim 4, characterized in that The generating a parameter array according to the parameters corresponding to the basic type parameter field comprises: A parameter array is generated according to the parameters corresponding to the basic type parameter field and the callback parameters under the callback type parameter field, wherein each element in the parameter array is arranged in the order of the transmission parameters of the second target method.

8. A remote interface debugging device, characterized in that: include: A generation module, used for generating a remote interface call request; A processing module, used for performing data processing on the call parameters carried by the remote interface call request to obtain interface call protocol data, wherein the data processing is used to convert the call parameters into protocol data supported by the SDK interface of the second terminal device connected to the first terminal device according to the preconfigured first interaction protocol; a sending module, configured to send the interface calling protocol data to the second terminal device, so that the second terminal device parses the interface calling protocol data and calls the second target method according to the parsing result based on a reflection mechanism; The interface call protocol data includes a class field, a call method field and a basic type parameter field. The second terminal device calls the second target method according to the parsing result based on the reflection mechanism in the following manner: the interface call protocol data is parsed according to the first interaction protocol to obtain the class field, the call method field and the basic type parameter field; based on the class name corresponding to the class field, an instance object is obtained based on the reflection mechanism; the type of the parameter corresponding to the basic type parameter field is calibrated; and, based on the call method field, a second target method corresponding to the instance object is obtained based on the reflection mechanism; and based on the calibrated parameters, the second target method is called based on the reflection mechanism.

9. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processing device, the steps of the method described in any one of claims 1 to 7 are implemented.

10. An electronic device, characterized in that: include: a storage device having a computer program stored thereon; A processing device, configured to execute the computer program in the storage device to implement the steps of the method according to any one of claims 1 to 7.

11. A remote interface debugging system, characterized in that: include: A first terminal device, used for generating a remote interface call request, performing digital processing on a call parameter carried in the remote interface call request to obtain interface call protocol data, and sending the interface call protocol data to a second terminal device connected to the first terminal device, wherein the digital processing is used for converting the call parameter into protocol data supported by the SDK interface of the second terminal device according to a preconfigured first interaction protocol; The second terminal device is used to parse the interface call protocol data and call the second target method according to the parsing result based on the reflection mechanism; The interface call protocol data includes a class field, a call method field and a basic type parameter field. The second terminal device calls the second target method according to the parsing result based on the reflection mechanism in the following manner: the interface call protocol data is parsed according to the first interaction protocol to obtain the class field, the call method field and the basic type parameter field; based on the class name corresponding to the class field, an instance object is obtained based on the reflection mechanism; the type of the parameter corresponding to the basic type parameter field is calibrated; and, based on the call method field, a second target method corresponding to the instance object is obtained based on the reflection mechanism; and based on the calibrated parameters, the second target method is called based on the reflection mechanism.

Images