CN111258683A

CN111258683A - Detection method, detection device, computer equipment and storage medium

Info

Publication number: CN111258683A
Application number: CN202010057497.6A
Authority: CN
Inventors: 纪伟; 李一山; 张岩
Original assignee: Beijing Sankuai Online Technology Co Ltd
Current assignee: Beijing Sankuai Online Technology Co Ltd
Priority date: 2020-01-19
Filing date: 2020-01-19
Publication date: 2020-06-09

Abstract

The application discloses a detection method, a detection device, computer equipment and a storage medium, and belongs to the technical field of computers. The method comprises the following steps: receiving a calling instruction through a target application, wherein the calling instruction comprises an object identifier of a target object; according to the calling instruction, a detection task is registered in Native code Native of the target application, wherein the detection task comprises an object identifier; after the detection task is established, calling a target object according to a calling instruction; and monitoring the process of calling the target object based on the detection task to obtain a calling result, wherein the calling result is calling success or calling failure. According to the method and the device, the detection task is registered in Native code Native, so that any process of calling a target object can be monitored through Native, and the detection method is more universal.

Description

Detection method, detection device, computer equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a detection method, an apparatus, a computer device, and a storage medium.

Background

With the continuous development of computer technology, applications can provide more and more functions for people, a target object can be called in the applications, the target object can be a web page, can also be a function of a native application, and can also be other objects, for example, an application jumps from a current web page to another web page, or objects such as bluetooth and a camera are called in the applications, but when the target object is called, a call failure may occur.

Disclosure of Invention

The embodiment of the application provides a detection method, a detection device, computer equipment and a storage medium, and the universality of the detection method can be improved. The technical scheme is as follows:

in one aspect, a detection method is provided, and the method includes:

receiving a calling instruction through a target application, wherein the calling instruction comprises an object identifier of a target object;

according to the calling instruction, a detection task is registered in Native code Native of the target application, and the detection task comprises the object identification;

after the detection task is established, calling the target object according to the calling instruction;

and monitoring the process of calling the target object based on the detection task to obtain a calling result, wherein the calling result is calling success or calling failure.

In a possible implementation manner, the monitoring, by the detection task, a procedure of invoking the target object to obtain an invocation result includes:

monitoring the process of calling the target object based on the detection task to obtain calling record data;

obtaining the calling result according to whether the calling record data meets the detection requirement or not,

the detection requirement is obtained based on at least one of:

a redirection follow-up number;

calling time length;

a response code white list;

and calling the target object and then successfully rendering the skipped page.

In a possible implementation manner, after obtaining the call result according to whether the call record data meets the at least one detection requirement, the method further includes:

and in response to the calling result being calling failure, re-calling the target object or degrading the target object according to the detection requirement that the calling record data does not meet.

In a possible implementation manner, the, in response to the call result being a call failure, recalling the target object or performing a demotion process according to the detection requirement that the call record data does not satisfy, includes:

responding to the calling result as calling failure, and determining a re-calling mode corresponding to the detection requirement that the calling record data does not satisfy;

and according to the recall mode, recalling the target object or degrading the target object.

In a possible implementation manner, the monitoring, based on the detection task, a procedure for calling the target object, and after obtaining a calling result, the method further includes:

outputting a recall prompt page, wherein the recall prompt page comprises at least one option, and each option corresponds to a calling mode;

and in response to the triggering operation of any option, recalling the target object or degrading the target object according to the calling mode corresponding to the option.

In a possible implementation manner, the recall hint page further includes reason hint information of failure to invoke the target object, where the reason hint information includes detection requirements that are not satisfied by a process of invoking the target object.

In a possible implementation manner, in response to that the call result is a call failure, the target object is called again in the webpage by jumping to the webpage corresponding to the callback identifier according to the callback identifier, where the callback identifier is obtained by analyzing the call instruction received by the target application.

In one aspect, a detection apparatus is provided, the apparatus comprising:

the receiving module is used for receiving a calling instruction through the target application, wherein the calling instruction comprises an object identifier of a target object;

the registration module is used for registering a detection task in Native code Native of the target application according to the calling instruction, wherein the detection task comprises the object identifier;

the calling module is used for calling the target object according to the calling instruction after the detection task is established;

and the monitoring module is used for monitoring the process of calling the target object based on the detection task to obtain a calling result, wherein the calling result is calling success or calling failure.

In one possible implementation, the listening module includes:

the monitoring unit is used for monitoring the process of calling the target object based on the detection task to obtain calling record data;

an obtaining unit, configured to obtain the call result according to whether the call record data meets a detection requirement, where the detection requirement is obtained based on at least one of:

a redirection follow-up number;

calling time length;

a response code white list;

and calling the target object and then successfully rendering the skipped page.

In a possible implementation manner, the invoking module is further configured to, in response to that the invoking result is an invoking failure, re-invoke the target object or perform degradation processing according to a detection requirement that the invoking record data does not satisfy.

In one possible implementation, the invoking module includes:

a determining unit, configured to determine, in response to the call result being a call failure, a recall manner corresponding to a detection requirement that the call record data does not satisfy;

and the calling unit is used for calling the target object again or performing degradation processing again according to the re-calling mode.

In one possible implementation, the apparatus further includes:

the display module is used for outputting a recall prompt page, the recall prompt page comprises at least one option, and each option corresponds to a calling mode;

and the calling module is also used for responding to the triggering operation of any option and recalling the target object or degrading the target object according to the calling mode corresponding to the option.

In one possible implementation, the apparatus further includes:

and the display module is used for responding to the calling result that the calling fails, jumping to a webpage corresponding to the callback identifier according to the callback identifier, and re-calling the target object in the webpage, wherein the callback identifier is obtained by analyzing the calling instruction received by the target application.

In one aspect, a computer device is provided and includes one or more processors and one or more memories, where at least one instruction is stored in the one or more memories, and the at least one instruction is loaded and executed by the one or more processors to implement the operations performed by the detection method according to any one of the possible implementations described above.

In one aspect, a computer-readable storage medium is provided, in which at least one instruction is stored, and the at least one instruction is loaded and executed by a processor to implement the operations performed by the detection method according to any one of the above possible implementations.

The beneficial effects brought by the technical scheme provided by the embodiment of the application at least comprise:

according to the detection method, the detection device, the computer equipment and the storage medium, the Native code Native registers the detection task, so that monitoring can be performed through Native in the process of calling the target object, and the process of calling the target object can be monitored no matter whether the target object is a webpage or a Native function, so that the detection method has universality.

In addition, when the target object is not called successfully, the method and the device can select to re-call the target object and can also select to perform degradation processing, and the service can be continued no matter the target object is re-called or the degradation processing is selected to call other objects, so that the continuity of the service is ensured.

In addition, after the calling result is obtained, if the calling result is that the calling of the target object fails, the calling failure reason can be displayed to the user, and multiple calling modes are provided for the user, so that the user can select one calling mode according to the calling failure reason to re-call the target object or perform degradation processing, and the problem that the user can only terminate the service when the calling of the target object fails is avoided.

In addition, after the calling result is obtained, if the calling result is that the calling of the target object fails, a calling mode can be automatically selected according to the reason of the calling failure, the target object is called again or the target object is degraded, manual operation of a user is not needed, and service continuity is guaranteed as much as possible. And the calling system can automatically process according to the reason of the calling failure, and can deal with the emergency of the calling failure, thereby improving the robustness of the calling system.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic illustration of an implementation environment provided by an embodiment of the present application;

FIG. 2 is a flow chart of a detection method provided by an embodiment of the present application;

FIG. 3 is a flow chart of a detection method provided by an embodiment of the present application;

FIG. 4 is a flow chart of a detection method provided by an embodiment of the present application;

FIG. 5 is a schematic structural diagram of a detection apparatus provided in an embodiment of the present application;

FIG. 6 is a schematic structural diagram of a detection apparatus provided in an embodiment of the present application;

fig. 7 is a schematic structural diagram of a terminal provided in an embodiment of the present application;

fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

The detection method provided by the embodiment of the application can be applied to computer equipment, and the computer equipment can be any terminal with an application installation function, such as a mobile phone, a tablet computer, a desktop computer and the like. The method comprises the steps that a target application is installed on a terminal, a calling instruction is received through the target application, a detection task is registered in Native code Native of the target application according to the calling instruction, the detection task comprises an object identifier of a target object, and the target object is called according to the calling instruction after the detection task is established; and monitoring the process of calling the target object based on the detection task to obtain a calling result, wherein the calling result is calling success or calling failure.

When the target object is a webpage, the terminal calls the target object, namely, the terminal jumps to another webpage from the current webpage, and the other webpage can be acquired in the server by the terminal. Fig. 1 is a schematic diagram of an implementation environment provided by an embodiment of the present application. Referring to fig. 1, the implementation environment includes: a terminal 101 and a server 102.

The terminal 101 may be any electronic device such as a mobile phone, a tablet computer, and a desktop computer, which is equipped with a target application function, and the server 102 may be a server, a server cluster formed by a plurality of servers, or a cloud computing server center, which is not limited in this embodiment of the present application.

In one possible implementation manner, the target object is a web page, and the process of the terminal invoking the target object may include: the terminal sends the object identification of the target object to the server, the server issues the target object to the terminal according to the object identification, and the terminal receives the target object and displays the target object in the display screen.

The detection method provided by the embodiment of the application can be applied to any terminal installed application:

for example, in Hybrid (mixed mode) mobile applications:

the detection method provided by the embodiment of the application can monitor the process of calling the webpage and the process of calling the Native function, so that the process of calling any object can be monitored, the method is more universal, in addition, the calling result of the calling object can be obtained, and the Hybrid application can be improved based on the calling result subsequently.

As another example, in native applications:

the detection method provided by the embodiment of the application can monitor the process of calling the native functions of other applications, so that a calling result is obtained, and the native applications can be improved subsequently according to the calling result.

Fig. 2 is a flowchart of a detection method according to an embodiment of the present application. Applied to a terminal, referring to fig. 2, the embodiment includes:

201. receiving, by the target application, a call instruction including an object identification of the target object.

202. According to the calling instruction, a detection task is registered in Native code Native of the target application, and the detection task comprises the object identification.

203. After the detection task is established, the target object is called according to the calling instruction.

204. And monitoring the process of calling the target object based on the detection task to obtain a calling result, wherein the calling result is calling success or calling failure.

According to the detection method, the detection task is registered in Native code Native, so that monitoring can be performed through Native in the process of calling the target object, the process of calling the target object can be monitored no matter whether the target object is a webpage or a Native function, and the detection method is enabled to be more universal.

In a possible implementation manner, the monitoring, by the detection task, a process of calling the target object to obtain a calling result includes:

obtaining the calling result according to whether the calling record data meets the detection requirement, wherein the detection requirement is obtained based on at least one of the following items:

a redirection follow-up number;

calling time length;

a response code white list;

and the page which is jumped after the target object is called is rendered successfully.

In a possible implementation manner, after obtaining the call result according to whether the call record data meets the detection requirement, the method further includes:

and in response to the calling result being calling failure, according to the detection requirement that the calling record data does not meet, re-calling the target object or degrading the target object.

In a possible implementation manner, the, in response to the call result being a call failure, recalling the target object according to a detection requirement that the call record data does not satisfy, includes:

and according to the recall mode, recalling the target object.

and in response to the triggering operation of any option, the target object or the degradation processing is recalled according to the calling mode corresponding to the option.

In one possible implementation manner, the recall hint page further includes reason hint information of failure to invoke the target object, and the reason hint information includes detection requirements that are not satisfied by a process invoking the target object.

All the above optional technical solutions may be combined arbitrarily to form the optional embodiments of the present disclosure, and are not described herein again.

Fig. 3 is a flowchart of a detection method according to an embodiment of the present application. Applied to a terminal, referring to fig. 3, the embodiment includes:

301. and receiving a calling instruction through the target application, wherein the calling instruction comprises the object identification of the target object.

The target application is any application installed on the terminal, and may be any type of application such as an electronic payment application, an instant messaging application, a sports application, and the like. The target application has a function of calling other objects to provide services for the user, for example, the target application can call other webpages, and the target application calls the other webpages to make the target application jump from the current webpage to the other webpages; the target application can also call a certain function of the native application, and the target application calls the certain function of the native application, such as calling a camera, calling Bluetooth and the like.

The target object may be any object providing a service for a user, may be a web page, and may also be a certain function of a native application, and the target object is not limited in the embodiment of the present application. The object identifier of the target object is an identifier for determining a unique target object, and may be an object ID (Identity, Identity number) or an object URL (Uniform resource Locator), and the object identifier is not limited in the embodiment of the present application.

The calling instruction is used for indicating a target object called by the target application, the calling instruction comprises an object identification of the target object, and the calling instruction can be triggered in the target application by a user. In one possible implementation manner, a display interface of the target application includes a calling option, and a calling instruction is received through the target application in response to a triggering operation on the calling option.

For example, a display interface of the target application includes a "face recognition" option, and in response to a trigger operation on the "face recognition" option, a call instruction is received by the target application, where the call instruction is used to call a shooting function of the native application, and the call instruction carries a camera identifier.

For another example, the display interface of the target application includes a "first application payment" option, and in response to a trigger operation on the "first application payment" option, a call instruction is received by the target application, where the call instruction is used to call a payment page of the first application, and the call instruction carries a page identifier of the payment page.

302. And according to the calling instruction, registering a detection task in Native code Native of the target application, wherein the detection task comprises object identification and detection requirements.

The target application can provide services for the user by calling the target object, and if the target object is not called, the services provided by the target application are interrupted. For example, the target application is an e-commerce application, the target application may provide various goods (physical goods or virtual goods) for the user to select and purchase, and if the user pays for a good that the user wants to purchase, the target application may call a payment page of the corresponding e-payment application, so that the user may pay on the payment page, and after the payment is completed, the current page may jump to a payment completion page of the target application. However, if the payment page of the corresponding electronic payment application fails to be called, conditions such as screen blank, loading error and the like may occur, which may cause service interruption provided by the target application for the user, and may also cause customer churn or customer complaint.

In the process, when the payment page of the electronic payment application is called, the payment page is equivalent to being separated from the target application, so that the target application cannot sense the problem of failure in calling the electronic payment application. At present, in the related art, an iFrame (a kind of tag) is added in a container where a webview (a web page view) is located, and timeout detection can be performed on a loading process of a web page through the iFrame, but the iFrame can only detect web page jump applied by the iFrame, but cannot perform detection if a web page applied by another application is called.

In order to solve the technical problem, an embodiment of the present application provides a universal detection method, where after a call instruction is received, a detection task is registered in Native of a target application, and then a process of calling a target object is monitored through Native, and if the called object is a certain function of a Native application, the calling needs to be implemented through Native, so that Native can monitor a calling process of the certain function of the Native application; in the Hybird application, the called webpage is displayed through the webview component, and Native can monitor the webview component, so that the process of monitoring and calling other webpages is realized. Therefore, the detection task is registered in Native, and the monitoring by Native has universality.

Whether the target object is successfully called by the target application is detected by monitoring the process of calling the target object by the target application to obtain calling record data, and whether the calling target object is successfully called is determined according to the calling record data. Therefore, a detection requirement corresponding to the call record data may be set, and whether the call target object is successfully called is monitored based on the detection requirement and the call record data, and in one possible implementation, registering a detection task in a Native of the target application may include: and registering a detection queue in Native, wherein the detection queue at least comprises the object identification and the detection requirement of the target object. The object identifier is used for indicating the called target object, and the detection requirement is used for indicating the requirement that Native judges whether the calling target object succeeds or fails.

In one possible implementation, the detection requirement is obtained based on at least one of redirection following number, calling duration, response code white list, page rendering success of jump after calling the target object.

It should be noted that, in the embodiment of the present application, only the redirection following number, the call duration, the response code white list, and the page rendering success of the jump after the target object is called are used, and the detection requirement is exemplarily explained, and may further include other parameters, which is not limited in the embodiment of the present application.

303. And determining the identifier of the first webpage as a callback identifier, wherein the first webpage is a webpage used for triggering a call instruction.

In response to failure of the target application to call the target object, a situation of a blank screen and no response may occur, so that service interruption provided by the target application is caused, and after the service interruption, the target application cannot jump to a previous node before the service interruption, that is, the target application cannot jump to a page triggering a call instruction. For example, a user triggers a call instruction in a payment method selection interface of a target application, and a terminal calls a payment page of a first application, but if the call of the payment page of the first application fails, the target application cannot jump to the payment method selection interface, and thus cannot call a target object again.

Therefore, the identifier of the first webpage can be determined as a callback identifier, and the callback identifier is saved in the target application, so that the target application program can jump to the page triggering the call instruction based on the callback identifier.

In one possible implementation, determining the identifier of the first web page as the callback identifier may include: and registering a callback queue in Native, wherein the callback queue at least comprises a callback identifier. If the page triggering the call instruction cannot be restored based on the callback identifier, the callback queue may further include other parameters, and the target application displays the page triggering the call instruction through the other parameters and the call webpage identifier. The embodiment of the present application does not limit other parameters included therein.

For example, the first web page is a payment method selection interface of the target application, the payment method selection interface includes at least one payment method option and also includes the quantity of resources to be paid, and if only the web page identifier of the payment method selection interface is stored in the callback queue, and the payment method selection interface is displayed again, the quantity of the resources to be paid may not be acquired, so that the quantity of the resources to be paid and the web page identifier may be stored in the callback queue together, so that the target application generates a corresponding payment method selection interface according to the quantity of the resources to be paid and the web page identifier.

It should be noted that the step 303 is an optional step in the embodiment of the present application, and may be selectively executed or not executed according to a requirement, if the step 303 is executed, after the calling of the target object fails, the call may jump to a page that triggers a call instruction based on the callback identifier, that is, the previous node that is to be served with the interrupt is returned, so that the call may be continued; if step 303 is not executed, after the target object is failed to be called, the target application may interrupt the service flow, and the user may jump to another page by operation to restart a service.

It should be noted that, when the step 303 is executed, the step 302 and the step 303 may be executed at the same time, as shown in fig. 4; or step 302 may be performed first, and then step 303 may be performed; step 303 may be executed first, and then step 302 is executed, which is not limited in this embodiment of the application.

304. And after the detection task is established, calling the target object according to the calling instruction.

Since the detection task is used for monitoring the calling process of the calling target object, the target object needs to be called after the detection task is created.

In one possible implementation, the target object is a web page, and the object identifier is a web page identifier, and according to the call instruction, calling the target object may include: if the target object is a webpage, the object identifier can be a webpage identifier, and the terminal can render the webpage corresponding to the webpage identifier in the webpage view container; the web page view container may be an existing web page view container, or a newly generated web page view container according to a call instruction.

In another possible implementation manner, the target object is a certain function of the native application, the object identifier may be the function identifier, the function identifier may be a character string corresponding to the function, and invoking the target object according to the invocation instruction may include: sending a calling message to Native, wherein the calling message carries the function identifier, and the Native calls a code corresponding to the function according to the function identifier; or, sending a call message to the operating system, where the call message carries the function identifier, and the operating system calls the corresponding native code according to the function identifier.

It should be noted that, according to the call instruction, the manner of calling the target object includes multiple manners, and the manner of calling the target object in the embodiment of the present application is not limited and may be any manner provided by the related art, which is not described herein any more.

305. And monitoring the process of calling the target object based on the detection task to obtain calling record data.

Wherein the call log data is data generated in a process of calling the target object, and the call log data generated in a process of successfully calling the target object is different from the call log data generated in a process of unsuccessfully calling the target object, and therefore, whether the target object is successfully called or not can be determined based on the call log data.

306. And acquiring a calling result according to whether the calling record data meets the detection requirement.

Wherein, according to whether the call record data meets the detection requirement, at least one item of the following items can be included, but not limited to:

(1) and if the detection requirement is obtained based on the number of the redirection following pages, determining whether the calling record data meets the detection requirement according to the calling results of the redirection following pages in the number.

In response to the target application invoking the target object, the terminal may enter one page and may continue to enter the next page in that page. For example, when the e-commerce application calls the payment function of the e-payment application, the e-commerce application sequentially enters an order confirmation page, a password input page, a payment confirmation page and a payment result page. At this time, the password input page, the payment confirmation page and the payment result page can be regarded as redirection following pages of the order confirmation page, if the redirection following pages are failed to be called, the service provided by the target application is also failed, and therefore the calling results of a preset number of redirection following pages can be synthesized to determine the calling result of the target object. The preset number may be the maximum number of redirection-following pages, or any number. For example, the number of redirection followers may be any integer not less than 1, such as 3, 4, 5, and so on.

In one possible implementation, if the preset number of redirection following pages of the target object are all successfully called, the detection requirement is met; if any page calling failure exists in the preset number of redirection following pages of the target object, the detection requirement is not met.

For example, when the preset number is 3, the target object has 5 redirection following pages, and if the terminal fails to call the 5 th redirection following page, the call record data meets the detection requirement; if the preset number is 3, the target object has 5 redirection following pages, and the terminal fails to call the 2 nd redirection following page, so that the call record data does not meet the detection requirement.

(2) And if the detection requirement is obtained based on the calling time length, determining whether the calling record data meets the detection requirement according to the time length of calling the target object.

The target application calls the target object, and if the target object is not successfully called within a period of time, the calling of the target object can be considered to be failed, so that the calling duration can be used as a detection requirement. The terminal may call the target object once or multiple times within the duration, which is not limited in the embodiments of the present application.

In one possible implementation, if the duration of calling the target object is longer than the calling duration, the calling data does not meet the detection requirement; and if the duration of calling the target object is not greater than the calling duration, calling the data to meet the detection requirement.

(3) And if the detection requirement is obtained based on the response code white list, determining whether the call record meets the detection requirement according to whether the received response code belongs to the response code white list.

When the webpage is called, the server transmits the content of the webpage to the target application and also sends a response code to the target application, wherein the response code can indicate success or failure of calling the webpage, and the response code white list is a response code set indicating success of calling the webpage, and can comprise a plurality of response codes or a threshold range of the response codes.

In one possible implementation, if the received response code belongs to a response code white list, determining that the call record meets the detection requirement; and if the received response code does not belong to the response code white list, determining that the call record does not meet the detection requirement.

The received response code belonging to the response code white list may refer to: the received response code is a code of a response code white list, or the value of the received response code belongs to a threshold range of the response code white list.

(4) And if the detection requirement is based on the display content of the terminal, determining whether the call record meets the detection requirement.

After the target object is called, the page of the target application changes, for example, after the target application calls the camera, a display frame is rendered on the page of the target application, and the display frame is used for displaying the image shot by the camera; for another example, after the target application calls another web page, the target application renders the page of the other web page, and therefore, the page skipped after the target object is called can be rendered successfully as the detection requirement. Moreover, if the calling of the target object fails, a failed keyword or a corresponding picture may be displayed on the display page, and whether the rendering of the page is successful or not may be determined according to success or failure of the keyword or picture indication displayed in the terminal page.

In a possible implementation manner, if display content is not detected in a page displayed by a terminal, determining that the call record does not meet the detection requirement; if the fact that the display content in the page displayed by the terminal comprises the failed keywords or the corresponding pictures is detected, determining that the calling record does not meet the detection requirement; and if the display content in the page displayed by the terminal is detected to comprise successful keywords or corresponding pictures, determining that the calling record meets the detection requirement.

If the calling record data meets the detection requirement, determining that the target object is successfully called; and if the calling record data does not meet any one of the detection requirements, determining that the target object is failed to be called.

It should be noted that, in the present application, only step 302, step 305, and step 306 are taken as examples to describe a process of registering a detection task and monitoring a process of calling a target object based on the detection task to obtain a calling result, and in another embodiment, a terminal registers the detection task in Native of a target application according to a calling instruction and monitors the process of calling the target object based on the detection task to obtain a calling result, where the calling result is a call success or a call failure.

307. And responding to the calling result that the calling fails, and jumping to a webpage corresponding to the callback identifier according to the callback identifier.

The callback identifier may be an identifier stored in the callback queue, or an identifier obtained by analyzing a call instruction received by the target application. The calling instruction may be generated when a user triggers to call the target object, or may be another calling instruction generated after the terminal fails to call the target object, and the calling instruction is used for calling a webpage corresponding to the callback identifier.

And responding to the calling result that the calling fails, acquiring the stored callback identifier, and jumping to a webpage corresponding to the callback identifier according to the callback identifier, namely jumping to the last node with interrupted service.

In the embodiment of the application, after the calling result is determined to be calling failure, the reason prompt information of the calling target object failure can be generated according to the detection requirement that the calling record data does not meet, and the reason prompt information is displayed in the webpage corresponding to the callback identifier. For example, the reason prompt message may be "the current network state is not good, the web page is failed to be called, and the network is requested to be re-detected and then retried", or "the target object is failed to be called for a plurality of times, and the second object capable of realizing the function that the target object can realize is requested to be called".

308. The target object or demotion process is recalled in the web page.

In a possible implementation manner, a plurality of objects on the terminal can implement a certain function, that is, calling any one of the plurality of objects can implement the function, but parameters of each object are different and effects of implementing the function are also different, and a priority of each object can be determined according to the effect of implementing the function by each object, where the better the effect of calling the object to implement the function is, the higher the priority of the object is. The effect of the target object for realizing the function is optimal, and the degradation processing refers to: if the calling of the target object fails, a second object with the priority next to the target object can be called, if the calling of the second object fails, a third object with the priority next to the second object is called, and calling is performed in sequence according to the priorities of the objects until the calling of the objects succeeds.

In another possible implementation manner, a plurality of objects on the terminal can implement a certain function, and the target object is any object in the plurality of objects. The degradation treatment is that: the calling instruction includes the object identification of the target object, and if the calling of the target object fails, any other object in the plurality of objects except the target object can be called. When the calling of the target object according to the calling instruction fails, any one of the objects other than the target object can be selected, and since the calling instruction includes the object identifier of the target object, the other object is finally called, and the calling processing mode can be regarded as the degradation processing.

When the target object or the demotion process is called again in the web page, the calling can be triggered by a user or a terminal. In a possible implementation manner, a page of the webpage comprises at least one option, and each option corresponds to a calling manner; and responding to the triggering operation of any option, and recalling the target object or degrading the target object according to the calling mode corresponding to the option. The trigger operation may be any one of a click operation, a slide operation, a long press operation, and the like, and the specific form of the trigger operation according to the embodiment of the present application is not limited.

The reason prompt information can be displayed on the webpage, and a user can determine to perform triggering operation on any option according to the reason prompt information. For example, the reason prompt message indicates that the current network state is not good and the calling of the payment webpage of the first application fails, and at this time, the user can confirm the connection state of the network and re-initiate the process of calling the payment webpage of the first application, that is, select an option corresponding to the payment webpage of the first application, so as to re-call the target object; for another example, the reason prompt message is that "the first application crashes and the payment webpage invoking the first application fails", and the user can select an option corresponding to the payment webpage invoking the second application according to the reason prompt message, thereby implementing the degradation processing.

In another possible implementation manner, in response to that the calling result is a calling failure, a recall manner corresponding to the detection requirement that the calling record data does not satisfy is determined, and the target object or the destaging process is recalled according to the recall manner.

The target object may be a living body detection service, for example, the target object is a face recognition service, and when the face recognition service of the target application fails to be invoked, a corresponding recall manner may be determined according to a detection requirement that the invocation recording data does not satisfy, and the target object may be recalled according to the recall manner. According to the recall mode, recalling the target object may include: if the target object is not found, the last calling mode can be replaced according to the plurality of calling modes provided in step 304, and the target object can be called again. If the target object is found, but the target object is failed to be called, the target object can be called again by adopting the last calling mode.

When the face recognition service of the calling target application fails, a corresponding re-calling mode can be determined according to the detection requirement that the calling record data is not satisfied, and degradation processing is carried out according to the re-calling mode. In one possible implementation manner, in response to the failure of the face recognition service of the calling target application, the face recognition service of the second application is determined to be called again according to the detection requirement that the calling record data does not meet. Wherein the target application and the second application are different applications. The detection requirement that the call record data is not satisfied may be a call duration, a call failure number, and the like, which is not limited in the embodiment of the present application.

The embodiment of the application is only exemplified by a face recognition service, and the method provided by the application can also be applied to other scenes if the target object is not a living body detection service.

It should be noted that, in the embodiment of the present application, only the call back is performed to the original web page on the basis of the web page, and in another embodiment, any one of the pages may be displayed, or a new page may be generated, and the page is used as a recall prompt page. In one possible implementation manner, a recall prompt page is displayed, the recall prompt page comprises at least one option, and each option corresponds to one calling manner; and when the user responds to the triggering operation of any option, the target object is recalled or the degradation processing is performed according to the calling mode corresponding to the option. In one possible implementation, the recall hint page further includes reason hint information for failure to invoke the target object, where the reason hint information includes detection requirements that are not satisfied by the process invoking the target object.

In the calling prompt page, the user can reselect a calling mode to call the target object according to the reason prompt information, or the terminal can call the target object again or perform degradation processing according to the calling mode corresponding to the detection requirement that the calling record data is not satisfied.

It should be noted that, in a possible implementation manner, in the embodiment of the present application, after a target object is successfully called, a detection task of the target object may be deleted, so that resources are saved, and after the target object is unsuccessfully called, the target object may be called again.

It should be noted that, after the call result is obtained, the call result may also be uploaded to the log server, where the call result may include at least one of an object identifier of the called target object, an application identifier of the target application, a terminal identifier, a call duration, call record data, a call failure reason, and the like. And the follow-up developer can improve the target application program according to the calling result. In addition, in a possible implementation manner, the calling result and the re-calling manner selected by the user can be uploaded to the log server together, and a subsequent developer can improve the manner of automatically re-calling the target object or degrading the processing of the terminal according to the calling result and the re-calling manner selected by the user.

According to the detection method provided by the embodiment of the application, the detection task is registered in the Native code Native, so that monitoring can be performed through Native in the process of calling the target object, and the process of calling the target object can be monitored no matter whether the target object is a webpage or a Native function, so that the detection method is more universal.

In addition, after the calling result is obtained, the calling result can be uploaded to a log server, so that a subsequent developer can improve the target application or calling mode; and the calling result and the re-calling mode selected by the user can be uploaded to a log server, so that a developer can automatically re-call the target object by the terminal according to the re-calling mode selected by the user, or the mode of automatically re-calling the target object by the terminal is improved.

In addition, when the target object is not called successfully, the method and the device can select to re-call the target object and select the degradation processing, and the service can be continued no matter the target object is re-called or the degradation processing is selected to call other objects, so that the continuity of the service is ensured, and the continuity of the service is ensured.

In addition, after the calling result is obtained, if the calling result is that the calling of the target object fails, the calling failure reason can be displayed to the user, and multiple calling modes are provided for the user, so that the user can select one calling mode according to the calling failure reason to re-call the target object or perform degradation processing, and the problem that the user can only terminal the service when the user encounters the calling of the target object that fails is solved.

In addition, after the calling result is obtained, if the calling result is that the calling of the target object fails, the terminal can automatically select a calling mode according to the reason of the calling failure, and re-call the target object or perform degradation processing, so that manual operation of a user is not needed, and continuous service is guaranteed as much as possible. And the calling system can automatically process according to the reason of the calling failure, and can deal with the emergency of the calling failure, thereby improving the robustness of the calling system.

Fig. 5 is a schematic structural diagram of a detection apparatus provided in an embodiment of the present application, and referring to fig. 5, the apparatus includes:

a receiving module 501, configured to receive a call instruction through a target application, where the call instruction includes an object identifier of a target object;

a registering module 502, configured to register a detection task in Native code Native of the target application according to the call instruction, where the detection task includes the object identifier;

a calling module 503, configured to call the target object according to the calling instruction after the detection task is created;

the monitoring module 504 is configured to monitor a process of calling the target object based on the detection task to obtain a calling result, where the calling result is a call success or a call failure.

As shown in fig. 6, in one possible implementation, the listening module 504 includes:

a monitoring unit 5041, configured to monitor a process of calling the target object based on the detection task, and obtain call record data;

an obtaining unit 5042, configured to obtain the invocation result according to whether the invocation recording data meets a detection requirement, where the detection requirement is obtained based on at least one of:

a redirection follow-up number;

calling time length;

a response code white list;

In a possible implementation manner, the calling module 503 is further configured to, in response to that the calling result is a call failure, re-call the target object or demote the target object according to a detection requirement that the call record data does not satisfy.

In one possible implementation, the calling module 503 includes:

a determining unit 5031, configured to determine, in response to the call result being a call failure, a recall manner corresponding to the detection requirement that the call record data is not satisfied;

a calling unit 5032, configured to recall the target object or demote processing according to the recall manner.

In one possible implementation, the apparatus further includes:

a display module 505, configured to output a recall prompt page, where the recall prompt page includes at least one option, and each option corresponds to a recall manner;

the calling module 503 is further configured to, in response to a trigger operation on any option, re-call the target object or demote the target object according to a calling manner corresponding to the option.

In one possible implementation, the apparatus further includes:

and the display module 505 is configured to jump to a webpage corresponding to the callback identifier according to the callback identifier in response to the call result being that the call fails, and recall the target object in the webpage, where the callback identifier is obtained by analyzing a call instruction received by the target application.

It should be noted that: in the detection device provided in the above embodiment, only the division of the functional modules is illustrated, and in practical applications, the function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the detection apparatus and the detection method provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.

Fig. 7 shows a block diagram of a terminal 700 according to an exemplary embodiment of the present application. The terminal 700 may be: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer iv, motion video Experts compression standard Audio Layer 4), a notebook computer, or a desktop computer. Terminal 700 may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, and so on.

In general, terminal 700 includes: a processor 701 and a memory 702.

The processor 701 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so on. The processor 701 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 701 may also include a main processor and a coprocessor, where the main processor is a processor for processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 701 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed on the display screen. In some embodiments, the processor 701 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.

Memory 702 may include one or more computer-readable storage media, which may be non-transitory. Memory 702 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in memory 702 is used to store at least one instruction for execution by processor 701 to implement the detection methods provided by the method embodiments herein.

In some embodiments, the terminal 700 may further optionally include: a peripheral interface 703 and at least one peripheral. The processor 701, the memory 702, and the peripheral interface 703 may be connected by buses or signal lines. Various peripheral devices may be connected to peripheral interface 703 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of radio frequency circuitry 704, touch screen display 705, camera 706, audio circuitry 707, positioning components 708, and power source 709.

The peripheral interface 703 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 701 and the memory 702. In some embodiments, processor 701, memory 702, and peripheral interface 703 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 701, the memory 702, and the peripheral interface 703 may be implemented on a separate chip or circuit board, which is not limited in this embodiment.

The Radio Frequency circuit 704 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 704 communicates with communication networks and other communication devices via electromagnetic signals. The rf circuit 704 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 704 includes: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuitry 704 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generation mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 704 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.

The display screen 705 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 705 is a touch display screen, the display screen 705 also has the ability to capture touch signals on or over the surface of the display screen 705. The touch signal may be input to the processor 701 as a control signal for processing. At this point, the display 705 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 705 may be one, providing the front panel of the terminal 700; in other embodiments, the display 705 can be at least two, respectively disposed on different surfaces of the terminal 700 or in a folded design; in still other embodiments, the display 705 may be a flexible display disposed on a curved surface or on a folded surface of the terminal 700. Even more, the display 705 may be arranged in a non-rectangular irregular pattern, i.e. a shaped screen. The Display 705 may be made of LCD (liquid crystal Display), OLED (Organic Light-Emitting Diode), or the like.

The camera assembly 706 is used to capture images or video. Optionally, camera assembly 706 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 706 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.

The audio circuitry 707 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 701 for processing or inputting the electric signals to the radio frequency circuit 704 to realize voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones may be provided at different portions of the terminal 700. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 701 or the radio frequency circuit 704 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, the audio circuitry 707 may also include a headphone jack.

The positioning component 708 is used to locate the current geographic position of the terminal 700 to implement navigation or LBS (location based Service). The positioning component 708 may be a positioning component based on the GPS (global positioning System) in the united states, the beidou System in china, the graves System in russia, or the galileo System in the european union.

Power supply 709 is provided to supply power to various components of terminal 700. The power source 709 may be alternating current, direct current, disposable batteries, or rechargeable batteries. When power source 709 includes a rechargeable battery, the rechargeable battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.

In some embodiments, terminal 700 also includes one or more sensors 710. The one or more sensors 710 include, but are not limited to: acceleration sensor 711, gyro sensor 712, pressure sensor 713, fingerprint sensor 714, optical sensor 715, and proximity sensor 716.

The acceleration sensor 711 can detect the magnitude of acceleration in three coordinate axes of a coordinate system established with the terminal 700. For example, the acceleration sensor 711 may be used to detect components of the gravitational acceleration in three coordinate axes. The processor 701 may control the touch screen 705 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 711. The acceleration sensor 711 may also be used for acquisition of motion data of a game or a user.

The gyro sensor 712 may detect a body direction and a rotation angle of the terminal 700, and the gyro sensor 712 may cooperate with the acceleration sensor 711 to acquire a 3D motion of the terminal 700 by the user. From the data collected by the gyro sensor 712, the processor 701 may implement the following functions: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.

Pressure sensors 713 may be disposed on a side bezel of terminal 700 and/or an underlying layer of touch display 705. When the pressure sensor 713 is disposed on a side frame of the terminal 700, a user's grip signal on the terminal 700 may be detected, and the processor 701 performs right-left hand recognition or shortcut operation according to the grip signal collected by the pressure sensor 713. When the pressure sensor 713 is disposed at a lower layer of the touch display 705, the processor 701 controls the operability control on the UI interface according to the pressure operation of the user on the touch display 705. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.

The fingerprint sensor 714 is used for collecting a fingerprint of a user, and the processor 701 identifies the identity of the user according to the fingerprint collected by the fingerprint sensor 714, or the fingerprint sensor 714 identifies the identity of the user according to the collected fingerprint. When the user identity is identified as a trusted identity, the processor 701 authorizes the user to perform relevant sensitive operations, including unlocking a screen, viewing encrypted information, downloading software, paying, changing settings, and the like. The fingerprint sensor 714 may be disposed on the front, back, or side of the terminal 700. When a physical button or a vendor Logo is provided on the terminal 700, the fingerprint sensor 714 may be integrated with the physical button or the vendor Logo.

The optical sensor 715 is used to collect the ambient light intensity. In one embodiment, the processor 701 may control the display brightness of the touch display 705 based on the ambient light intensity collected by the optical sensor 715. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 705 is increased; when the ambient light intensity is low, the display brightness of the touch display 705 is turned down. In another embodiment, processor 701 may also dynamically adjust the shooting parameters of camera assembly 706 based on the ambient light intensity collected by optical sensor 715.

A proximity sensor 716, also referred to as a distance sensor, is typically disposed on a front panel of the terminal 700. The proximity sensor 716 is used to collect the distance between the user and the front surface of the terminal 700. In one embodiment, when the proximity sensor 716 detects that the distance between the user and the front surface of the terminal 700 gradually decreases, the processor 701 controls the touch display 705 to switch from the bright screen state to the dark screen state; when the proximity sensor 716 detects that the distance between the user and the front surface of the terminal 700 gradually becomes larger, the processor 701 controls the touch display 705 to switch from the breath screen state to the bright screen state.

Those skilled in the art will appreciate that the configuration shown in fig. 7 is not intended to be limiting of terminal 700 and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.

Fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application, where the server 800 may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 801 and one or more memories 802, where the memory 1002 stores at least one instruction, and the at least one instruction is loaded and executed by the processors 801 to implement the methods provided by the foregoing method embodiments. Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input/output, and the server may also include other components for implementing the functions of the device, which are not described herein again.

In an exemplary embodiment, a computer-readable storage medium, such as a memory, is also provided that includes instructions executable by a processor in a terminal to perform the detection method in the above-described embodiments. For example, the computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

In an exemplary embodiment, there is also provided a computer program comprising at least one instruction which is loaded and executed by a processor to implement the detection method as in the above embodiments.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

The above description is only exemplary of the present application and should not be taken as limiting, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method of detection, the method comprising:

2. The method according to claim 1, wherein the monitoring, by the detection task, a procedure for calling the target object to obtain a calling result comprises:

a redirection follow-up number;

calling time length;

a response code white list;

and calling the target object and then successfully rendering the skipped page.

3. The method according to claim 2, wherein after obtaining the call result according to whether the call record data meets the detection requirement, the method further comprises:

4. The method according to claim 3, wherein the, in response to the call result being a call failure, recalling the target object or performing destaging processing according to the detection requirement that the call log data does not satisfy, comprises:

5. The method of claim 3, wherein the monitoring, based on the detection task, of the process of calling the target object, and after obtaining a calling result, the method further comprises:

6. The method of claim 5, wherein the recall hint page further comprises reason hint information for failure to invoke the target object, the reason hint information comprising detection requirements that are not met by a process invoking the target object.

7. The method of claim 1,

and in response to the calling result being that the calling fails, jumping to a webpage corresponding to the callback identifier according to the callback identifier, and re-calling the target object in the webpage, wherein the callback identifier is obtained by analyzing a calling instruction received by the target application.

8. A detection device, the device comprising:

9. A computer device comprising one or more processors and one or more memories having stored therein at least one instruction that is loaded and executed by the one or more processors to perform operations performed by the detection method of any one of claims 1 to 7.

10. A computer-readable storage medium having stored therein at least one instruction, which is loaded and executed by a processor to perform operations performed by a detection method according to any one of claims 1 to 7.