Information Processing Method and Related Devices in Interface Call

Abstract

This application relates to the field of computer technology and provides an information processing method and related devices in interface calls. The method includes: obtaining trigger record information of a target user, where the trigger record information is generated based on trigger operations performed by the target user on a target control in a target page; obtaining first call information corresponding to time information and associated with a page identifier, where the first call information includes a tracking identifier and interface information of a target interface, and the tracking identifier is generated based on a call request for the target interface; obtaining second call information associated with the tracking identifier, where the second call information includes sub-interface information of a sub-interface that is nested and called during the process of calling the target interface; generating a trigger call record for the target control according to the control information of the target control, the interface information of the target interface, and the sub-interface information of the sub-interface. This method realizes the association of user operations with interface calls.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more particularly, to a method for processing information in interface calls and related devices. Background Art

[0002] In related technologies, in order to achieve component or service reuse, interface calls are increasingly widely used. In some complex systems, in order to test system performance, it is generally necessary to determine the call relationship between interfaces in the system. However, in related technologies, in system testing, it is impossible to associate the controls triggered on the page with the interface calls in the backend. Therefore, it is impossible to know which controls triggered on the page can cause backend interface calls. Summary of the Invention

[0003] Embodiments of this application provide a method for processing information in interface calls and related devices to solve the problem in the prior art that it is impossible to know which controls triggered on the page can cause backend interface calls.

[0004] Other features and advantages of this application will become apparent through the following detailed description, or be learned in part through the practice of this application.

[0005] According to one aspect of the embodiments of this application, a method for processing information in interface calls is provided. The method includes:

[0006] Obtain the trigger record information of the target user, where the trigger record information is generated according to the trigger operation of the target user on the target control in the target page, and the trigger record information includes the user identifier of the target user, the control information of the target control, the page identifier of the target page, and the time information when the target user triggers the target control;

[0007] Obtain the first call information corresponding to the time information and associated with the page identifier, where the first call information includes a tracking identifier and the interface information of the target interface, and the tracking identifier is generated according to the call request for the target interface, and the call request for the target interface is initiated after detecting the trigger operation on the target control;

[0008] Obtain the second call information associated with the tracking identifier, where the second call information includes the sub-interface information of the sub-interface nestedly called during the call of the target interface;

[0009] Generate a trigger call record for the target control according to the control information of the target control, the interface information of the target interface, and the sub-interface information of the sub-interface.

[0010] According to one aspect of the embodiments of the present application, there is provided an information processing device in interface invocation, including: a trigger record information acquisition module, configured to acquire trigger record information of a target user, where the trigger record information is generated according to a trigger operation performed by the target user on a target control in a target page, and the trigger record information includes the user identifier of the target user, the control information of the target control, the page identifier of the target page, and the time information when the target user triggers the target control. A first invocation information acquisition module, configured to acquire first invocation information corresponding to the time information and associated with the page identifier, where the first invocation information includes a tracking identifier and interface information of a target interface, and the tracking identifier is generated according to an invocation request for the target interface, and the invocation request for the target interface is initiated after detecting the trigger operation on the target control. A second invocation information acquisition module, configured to acquire second invocation information associated with the tracking identifier, where the second invocation information includes sub-interface information of a sub-interface nestedly invoked during the invocation of the target interface.

[0011] A trigger invocation record generation module, configured to generate a trigger invocation record for the target control according to the control information of the target control, the interface information of the target interface, and the sub-interface information of the sub-interface.

[0012] In some embodiments of the present application, based on the foregoing solution, the trigger invocation record generation module includes: an interface invocation sequence generation unit, configured to generate an interface invocation sequence of the target interface according to the interface information of the target interface and the sub-interface information of the sub-interface; a trigger invocation record generation unit, configured to associate the interface invocation sequence of the target interface with the control information of the target control to obtain a trigger invocation record for the target control.

[0013] In some embodiments of the present application, based on the foregoing solution, the interface invocation sequence generation unit includes: a called order determination unit, configured to determine the called order between the sub-interfaces corresponding to the plurality of second invocation information according to the called time information in the plurality of second invocation information; an association unit, configured to associate the interface information of the target interface and the sub-interface information in the plurality of second invocation information according to the called order to obtain the interface invocation sequence of the target interface.

[0014] In some embodiments of the present application, based on the foregoing solution, the trigger call record further includes the page identifier of the target page where the target control is located; the information processing device in the interface call further includes: a call sequence query request acquisition module, configured to acquire a call sequence query request; a trigger call record acquisition module, configured to acquire a trigger call record associated with a first page identifier, where the first page identifier is the page identifier of the page whose call sequence is requested to be queried in the call sequence query request; an interface call sequence acquisition module, configured to acquire an interface call sequence from the trigger call record associated with the first page identifier; and a first return module, configured to return the acquired interface call sequence to the initiator of the call sequence query request.

[0015] In some embodiments of the present application, based on the foregoing solution, the information processing device in the interface call further includes: a first trigger record information acquisition module, configured to acquire first trigger record information corresponding to the user identifier of the target user and the page identifier of the target page within a specified time period; a location information acquisition module, configured to acquire, from the control information included in the first trigger record information, the location information of the control corresponding to the first trigger record information in the target page; and a first display control information generation module, configured to generate first display control information according to the location information, where the first display control information is used to control the marked display of the controls triggered within the specified time period in the target page.

[0016] In some embodiments of the present application, based on the foregoing solution, the first trigger record information further includes trigger sequence information, where the trigger sequence information indicates the sequence in which the control corresponding to the first trigger record information is triggered within the specified time period; the information processing device in the interface call further includes: a second display control information generation module, configured to generate second display control information according to the trigger sequence information in the first trigger record information, where the second display control information is used to control the trigger sequence marking of the controls triggered within the specified time period in the target page.

[0017] According to one aspect of the embodiments of the present application, there is provided an electronic device, including: a processor; a memory, where computer-readable instructions are stored on the memory, and when the computer-readable instructions are executed by the processor, the information processing method in the interface call as described above is implemented.

[0018] According to one aspect of the embodiments of the present application, there is provided a computer-readable storage medium, on which computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor, the information processing method in the interface call as described above is implemented.

[0019] In the solution of this application, by using the time information and page identifier in the trigger record information, the first call information corresponding to the time information in the trigger record information and associated with the page identifier is obtained, and the second call information associated with the tracking identifier in the first call information is obtained. Then, based on the control information of the target control in the trigger record information, the interface information of the target interface in the obtained first call information, and the sub-interface information in the obtained second call information, the trigger call record of the target control is generated, realizing the association of the control information describing the user's operation behavior with the interface information corresponding to the call triggered by the control, that is, associating the user's operation behavior with the called interface. For users who are not clear about the backend call situation, they can directly know which control in the target page can be triggered to initiate the call of the target interface according to this trigger call record. Of course, they can also directly know which interface the trigger of the target control in the target page will initiate a call to and the sub-interface nested and called in this interface according to this trigger call record, realizing the tracking of the call situation of the target interface starting from the control reflecting the user's operation behavior, effectively solving the problem in the prior art that it is impossible to know which controls triggered in the page can cause the backend interface call.

[0020] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit this application. Brief Description of the Drawings

[0021] The drawings here are incorporated into the specification and form a part of this specification, showing embodiments consistent with this application, and are used together with the specification to explain the principles of this application. Obviously, the drawings in the following description are only some embodiments of this application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts. In the drawings:

[0022] Figure 1 A schematic diagram of an application scenario where the technical solution of the embodiment of this application can be applied is shown.

[0023] Figure 2 It is a flowchart of an information processing method in interface call shown according to an embodiment of this application.

[0024] Figure 3 It is a flowchart of step 240 shown according to an embodiment of this application.

[0025] Figure 4 It is a flowchart of an information processing method in interface call shown according to another embodiment of this application.

[0026] Figure 5 It is a schematic diagram of an interface for displaying the query result of the interface call sequence shown according to a specific embodiment.

[0027] Figure 6 It is a schematic diagram of an interface for displaying query results of a triggered control shown according to a specific embodiment.

[0028] Figure 7 It is a flowchart of an information processing method in interface call shown according to another embodiment of the present application.

[0029] Figure 8 It is a schematic diagram of displaying controls triggered by a user on a page within a specified time period shown according to a specific embodiment.

[0030] Figure 9 It is a block diagram of an information processing device in interface call shown according to an embodiment of the present application.

[0031] Figure 10 It shows a schematic diagram of the structure of a computer system of an electronic device suitable for implementing the embodiments of the present application. Detailed implementation manners

[0032] Now, example embodiments will be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more complete and comprehensive, and will fully convey the concept of the example embodiments to those skilled in the art.

[0033] In addition, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of the embodiments of this application. However, those skilled in the art will realize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of this application.

[0034] The block diagrams shown in the drawings are only functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0035] The flowcharts shown in the drawings are only illustrative and do not necessarily include all the contents and operations / steps, nor do they necessarily have to be executed in the described order. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to the actual situation.

[0036] It should be noted that: "multiple" mentioned in this article refers to two or more. " / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the front and back associated objects.

[0037] Figure 1 A schematic diagram of an application scenario to which the technical solution of the embodiments of the present application can be applied is shown.

[0038] As Figure 1 shown, the application scenario includes a terminal 110, a service end 120, a middle platform service end, and an information collection end 130. The terminal 110, the service end 120, and the middle platform service end ( Figure 1 only the middle platform service end I and the middle platform service end II are schematically shown in the figure) are respectively communicatively connected to the information collection end 130. The terminal 110 is communicatively connected to the service end 120, and the service end 120 is communicatively connected to each middle platform service end.

[0039] The service end 120 directly provides services to the terminal 110, and the middle platform service end can also be called a service middle platform, which can share a set of reusable services for providing underlying implementation services for the services. The implementation of some underlying services needs to be achieved through the middle platform service end. The service end 120 can provide various types of services to the terminal 110, such as payment, order, commodity, etc. Therefore, there can be multiple middle platform service ends, and one middle platform service end corresponds to one type of service. For example, services related to payment can be implemented by a payment middle platform service end, services related to orders can be implemented by an order middle platform service, and services related to commodities can be implemented by a commodity middle platform service end.

[0040] The user can perform a trigger operation on the controls that can be triggered on the page based on the page displayed on the terminal 110. The trigger operation can be, for example, clicking, swiping, etc. After the control on the page is triggered, the terminal 110 correspondingly generates trigger record information for the user. The trigger record information includes a user identifier, control information of the triggered control, a page identifier of the page where the control is located, and time information when the user triggers the control. Among them, the page identifier of the page where the control is located can be generated by the terminal 110. The terminal 110 further reports the generated trigger record information to the information collection end 130.

[0041] In some embodiments of the present application, the terminal 110 can generate different page identifiers for different logged-in users on the same page. Therefore, the page identifiers generated by the terminal 110 can not only distinguish different pages but also distinguish the logged-in users who enter the page.

[0042] If the triggering operation of the user on the control is a triggering call operation for an interface, in other words, the control corresponds to the call of an interface. As long as it is detected that the control is triggered, a call to the interface associated with the control is initiated accordingly. For the convenience of description, the interface corresponding to the control is called the target interface. In this case, the terminal 110 correspondingly sends a call request for the target interface to the service end 120.

[0043] In some embodiments of the present application, after receiving the call request for the target interface, the service end 120 generates a tracking identifier for tracking the call process of the target interface, and calculates according to the interface parameters in the call request to obtain the interface call result. After the service end 120 obtains the interface call result, it can send the interface call result and the generated tracking identifier to the terminal 110, so that the terminal 110 generates the first call information according to the page identifier of the page where the control is located, the tracking identifier, and the interface information of the target interface. In some embodiments of the present application, after obtaining the interface call result of the target interface, the service end 120 can also generate the third call information according to the tracking identifier and the interface information of the target interface by the service end 120. And report the third call information to the information collection system as well.

[0044] In some embodiments of the present application, for the convenience of distinction, the first call information uploaded by the terminal 110 for the target interface carries the page identifier, while the first call information uploaded by the service end 120 for the target interface may not carry the page identifier. Thus, in the call process of the target interface, only the tracking identifier is transmitted, and the page identifier does not need to be transmitted.

[0045] It can be understood that if the called target interface does not need to involve the participation of the middleware server, the service end 120 can directly calculate according to the interface input parameters in the call request to obtain the corresponding interface call result, and the interface call result may include the interface output parameters calculated by calling the corresponding interface function according to the interface input parameters.

[0046] If the called target interface needs to involve the participation of the middleware server, the service end 120 also needs to further call the sub-interfaces nested under the target interface provided by the middleware server, and then determine the interface call result of the target interface according to the results of each sub-interface. In this case, the service end 120 correspondingly sends call requests for each sub-interface to the middleware server, and the tracking identifier is carried in the call requests for the sub-interfaces.

[0047] After each middle - tier server receives a call request for a sub - interface, it calculates based on the interface input parameters in the call request for the sub - interface to obtain the interface call result corresponding to the sub - interface. Correspondingly, after the middle - tier server obtains the call result of the sub - interface, it generates a second call message based on the tracking identifier and the interface information of the sub - interface, and uploads the second call message to the information collection system.

[0048] Furthermore, the middle - tier server can also return the obtained interface call result of the sub - interface to the service end 120, so that the service end 120 can determine the interface call result of the target interface based on the interface call results of the sub - interfaces returned by each middle - tier server.

[0049] In Figure 1 In the application scenario shown, based on the trigger record information reported by the terminal 110, the first call information reported by the terminal 110, the first call information reported by the service end 120, and the second call information reported by the middle - tier server, the information collection system can perform correlation analysis.

[0050] Specifically, based on the time information and page identifier in the trigger record information, the first call information associated with the time information and page identifier is obtained. Since the first call information includes a tracking identifier, the second call information carrying the tracking identifier can be further obtained.

[0051] On this basis, according to the interface call times carried in the first call information and the second call information, the call relationship between the target interface and each sub - interface can be determined, thereby generating an interface call sequence. And the control information in the trigger record information is corresponding to the interface information of each interface in the interface call sequence for the target interface, so as to obtain a trigger call record that can reflect the trigger relationship between the control and the target interface.

[0052] In some embodiments of the present application, based on the trigger record information reported by each terminal 110, a terminal can also obtain the first trigger record information reported for the target user on the target page within a specified time period from the information collection end 130, and then use a plugin to mark and display the controls triggered by the target user during this period on the target page according to the first trigger record information. Among them, the position information of the triggered control on the target page can be reflected by the buried - point information set at the control. Therefore, marking and displaying the triggered control is equivalent to restoring the buried - point set at the control on the target page, so as to facilitate intuitively understanding the controls triggered within the specified time period.

[0053] In another application scenario of the present application, the server providing the service may also not divide the business end 120 and the middleware server, so that the invocation of the target interface and the invocation of the sub-interfaces nested in the target interface are both implemented by the server, and the reporting of the invocation information is correspondingly performed during the invocation of the target interface.

[0054] The following elaborates in detail on the implementation details of the technical solution of the embodiments of the present application:

[0055] Figure 2 The flowchart of the information processing method in interface invocation shown according to an embodiment of the present application is shown. This method can be executed by a computer device with processing capabilities, such as a server, etc. The server can be Figure 1 the server where the information collection end is located in, and no specific limitation is made here. Referring to Figure 2 shown, this method at least includes steps 210 to 240, which are introduced in detail as follows:

[0056] Step 210, obtain the trigger record information of the target user. The trigger record information is generated according to the trigger operation of the target user on the target control in the target page. The trigger record information includes the user identifier of the target user, the control information of the target control, the page identifier of the target page, and the time information when the target user triggers the target control.

[0057] The target control refers to the control triggered by the target user in the target page. Any control triggered by the user can be used as the target control in the solution of the present application.

[0058] The user identifier is used to identify the client user who enters the target page. The user identifier can be the user name of the target user in the client, or the user ID, etc., and no specific limitation is made here.

[0059] The time information in the trigger record information is used to indicate the time when the target control is triggered.

[0060] The control information may include the control name, the position information of the control in the target page, etc. In some embodiments of the present application, data points can be set on each control in the target page, and the triggered controls in the target page are monitored through the set data points.

[0061] In some embodiments of the present application, the attributes of a triggerable control on a page can also be customized. Specifically, on the DOM (Document Object Model) of the page, data attributes are customized for the node where the control is located. For example, the control name, control type, control location information, etc. are defined through the data-hottag field. Among them, the control location information is used to describe the position of the control on the page.

[0062] After the page of the client is initialized, the client generates a page identifier for the page where it is located and monitors the controls on the DOM of the page that are configured with data-hottag information. Thus, when it is monitored that a control configured with data-hottag information on the DOM is triggered, the control name, control type, and control location information of the control are obtained correspondingly from the configured data-hottag information. Among them, the control type is classified according to the triggering method of the control, and the control type can include a control type indicating sliding, a control type indicating clicking, etc.

[0063] In the solution of the present application, the trigger record information is generated and reported by the client where the user is located.

[0064] In some embodiments of the present application, before step 210, the method further includes: receiving the trigger record information reported by the client; where the client generates the trigger record information according to the user identifier of the user where the client is located, the page identifier of the target page, and the control information of the target control after detecting a trigger operation on the target control in the target page. Thus, the execution entity of the present application can collect trigger record information for multiple clients.

[0065] Step 220, obtaining first call information corresponding to the time information and associated with the page identifier, where the first call information includes a tracking identifier and interface information of a target interface, and the tracking identifier is generated according to a call request for the target interface, and the call request for the target interface is initiated after detecting a trigger operation on the target control.

[0066] As described above, after the service side receives a call request for a target interface, it correspondingly generates a tracking identifier for tracking the call process of the target interface.

[0067] Among them, the first call information can be generated by the client after receiving the call result for the target interface returned by the service side and the tracking identifier returned for the call process of the target interface.

[0068] The interface information of the target interface may include the interface name, interface input parameters, interface output parameters, and called time information. Among them, the interface input parameters are obtained from the call request of the target interface. The interface parameters refer to the parameters input for calling the target interface, and the interface parameters indicate the result calculated for calling the target interface based on the interface input parameters. Of course, when the target interface call fails, the interface output parameters may also be fields indicating the interface call failure. The called time information at least includes the time when the call request for the target interface is initiated. In some embodiments, the called time information may further include the time when the call result is obtained.

[0069] Since the trigger record information includes the time information for triggering the target control (which is used to indicate the time when the target control is triggered) and the page identifier, and the first call information also includes the called time information (which includes the time used to indicate the initiation of the call request for the target interface), and when the operation of triggering the target control is to trigger the operation of the target interface, a call request for the target interface is initiated when it is detected that the target control is triggered. Therefore, the time indicated by the time in the trigger record information for the target control is basically the same as the time indicated by the called time information in the first call information for the target interface.

[0070] In some embodiments of the present application, first, according to the page identifier in the trigger record information for the target control, the first call information associated with the page identifier (i.e., the first call information carrying the page identifier) may be obtained. For ease of description, the first call information obtained in this process may be aggregated into a first information set; then, according to the time indicated by the time information in the trigger record information and a subsequent set time period, a target time period is determined, and the first call information whose called time information indicates a time within the target time period is filtered out in the first information set. The first call information filtered out the second time is the first call information corresponding to the time information in the trigger record information and associated with the page identifier in the trigger record information in step 220.

[0071] In some embodiments of the present application, the first call information may be generated and reported by the client, and the method further includes: receiving the first call information reported by the client; after receiving the call result and the tracking identifier for the target interface returned by the service end, the client generates the first call information according to the tracking identifier, the page identifier, and the interface information of the target interface. The interface information includes the called time information of the target interface, where the tracking identifier is generated by the service end after receiving the call request initiated by the client for the target interface.

[0072] In this embodiment, after obtaining the call result of the target interface, the service end sends the call result of the target interface and the tracking identifier generated by the service end to the client. Thus, the client generates the first call information according to the page identifier of the page where the target control is located, the tracking identifier, and the interface information of the target interface. Since the interface information of the target interface includes the call time information of the target interface, it is possible to determine the first call information corresponding to the time information in the trigger record information according to the time information in the trigger record information and the call time information in the first call information. The interface indicated to be called in the determined first call information is the interface to be called after the control indicated by the trigger record information is triggered.

[0073] In some embodiments of the present application, the service end can also report call information. For the sake of distinction, the call information reported by the service end is referred to as the third call information. The service end can generate the third call information according to the tracking identifier and the interface information of the target interface.

[0074] Step 230, obtain second call information associated with the tracking identifier, where the second call information includes sub-interface information of a sub-interface nested during the call of the target interface.

[0075] In the scenario where the target interface is a composite interface, one or more sub-interfaces are nested in the target interface. Therefore, in order to obtain the interface call result of the target interface, it is also necessary to further call the sub-interfaces nested under the target interface.

[0076] In the application scenario where the target interface is a composite interface, the call request for the sub-interface includes a tracking identifier for tracking the call process of the target interface. Thus, the second call information for the sub-interface can be generated according to the tracking identifier and the sub-interface information of the sub-interface.

[0077] Similar to the interface information of the target interface, the sub-interface information of the sub-interface can include the interface name, interface input parameters, interface output parameters, and call time information of the sub-interface. Among them, the call time information can include the time when the sub-interface is called, and can also include the time when the call result of the sub-interface is obtained.

[0078] The sub-interfaces nested under the target interface can include one-level or multi-level sub-interfaces. The tracking identifier is carried in the call request of the upper-level sub-interface under the target interface for the lower-level sub-interface to ensure complete tracking of the call process of the target interface. In step 230, it is necessary to obtain the second call information of each sub-interface nested under the target interface.

[0079] The second call information obtained in step 230 and associated with the tracking identifier (the tracking identifier for tracking the call process of the target interface) can reflect all the sub-interfaces nested within the target interface.

[0080] Step 240, generate a trigger call record for the target control according to the control information of the target control, the interface information of the target interface, and the sub-interface information of the sub-interface.

[0081] Since the first call information obtained in step 220 is the first call information for the target interface triggered by the target control in step 210, and the second call information obtained in step 230 is associated with the tracking identifier of the target interface, the control information in the trigger record information in step 210, the interface information in the first call information obtained in step 220, and the sub-interface information in the second call information obtained in step 230 are associated, thereby realizing the association of the target control reflecting the user operation behavior, the target interface called corresponding to the triggering of the target control, and the sub-interfaces nested under the target interface.

[0082] Therefore, the trigger call record for the target control generated according to the control information of the target control, the interface information of the target interface, and the sub-interface information of the sub-interfaces nested within the target interface associates the user's operation behavior with the called interface. For users who are not clear about the backend call situation, they can directly know which control in the target page can be triggered to initiate the call of the target interface and the sub-interfaces nested within the target interface according to this trigger call record. Of course, they can also directly know which interface the trigger of the target control in the target page will initiate a call to according to this trigger call record, realizing the tracking of the call situation of the target interface starting from the control reflecting the user operation behavior, and effectively solving the problem in the prior art that it is impossible to know which controls in the page can trigger the backend interface call.

[0083] In some embodiments of the present application, as Figure 3 shown, step 240 further includes:

[0084] Step 310, generate an interface call sequence of the target interface according to the interface information of the target interface and the sub-interface information of the sub-interface.

[0085] Step 320, associate the interface call sequence of the target interface with the control information of the target control to obtain a trigger call record for the target control.

[0086] The interface call sequence of the target interface is obtained by arranging the target interface and multiple sub-interfaces nested under the target interface in sequence according to the order of being called between the target interface and the multiple sub-interfaces nested under the target interface. In the interface call sequence of the target interface, each interface (target interface, sub-interface) can be identified by the interface name.

[0087] Since the second call information includes the call time of the corresponding sub-interface, therefore, based on the call times in the second call information corresponding to the multiple sub-interfaces, the hierarchical call relationship between the multiple sub-interfaces can be determined. On this basis, the interface call sequence of the target interface can be correspondingly generated.

[0088] In some embodiments of the present application, step 310 further includes: determining the call order between the sub-interfaces corresponding to the multiple second call information according to the call time information in the multiple second call information; associating the interface information of the target interface and the sub-interface information in the multiple second call information according to the call order to obtain the interface call sequence of the target interface.

[0089] As described above, the call time information is used to indicate the call time. Therefore, according to the call time indicated by the call time in the second call information associated with the tracking identifier, the multiple sub-interfaces are sorted to correspondingly determine the call order between the multiple sub-interfaces.

[0090] In some embodiments of the present application, the middle platform server provides services corresponding to the sub-interfaces. The method further includes: receiving the second call information reported by the middle platform server. After receiving the call request for the sub-interface corresponding to the target interface, the middle platform server generates the second call information according to the interface information of the sub-interface and the tracking identifier, and the service end sends the call request for the sub-interface to the middle platform server according to the tracking identifier.

[0091] In this embodiment, the service end provides services to each client. Therefore, the client first sends the call request for the target interface to the service end. Then, the service end correspondingly generates a tracking identifier, and when the target interface is a composite interface, sends the call request for the sub-interface to the middle platform server corresponding to the sub-interface. The call request sent by the service end to the middle platform server includes the tracking identifier. Thus, the middle platform server can generate the second call information according to the tracking identifier and the interface information corresponding to the sub-interface, and report the second call information.

[0092] Based on obtaining the interface call sequence, through step 330, the interface call sequence of the target interface is associated with the control information of the target control, and the obtained trigger call record for the target control reflects the full-link situation of the complete target interface call from the trigger behavior of the target interface to obtaining the call result.

[0093] Of course, if the target interface is not a composite interface, that is, it does not have nested sub-interfaces, then the interface information of the target interface can be directly associated with the control information of the target control to obtain the trigger call record of the target interface.

[0094] In some embodiments of the present application, since the trigger call record is based on the interface call sequence of the target interface and the control information of the target control, thus, based on the trigger call record, not only can the user's operation behavior be understood, but also the operation behavior in the user page can be associated with the call situation of the target interface, which is convenient for better understanding the call situation of the target interface.

[0095] In some embodiments of the present application, the interface information of each interface in the interface call sequence includes the call result of the interface. When any interface call in the interface call sequence fails, the cause of the call failure can be located through the call result in the interface information of each interface in the interface call sequence or the trigger call record, and it can be correspondingly determined which interface call failure causes the call failure of the target interface.

[0096] In some embodiments of the present application, the trigger call record further includes the page identifier of the target page where the target control is located; in this embodiment, as Figure 4 shown, the method further includes:

[0097] Step 410, obtain a call sequence query request, where the call sequence query request includes a first page identifier.

[0098] Step 420, obtain the trigger call record associated with the first page identifier, where the first page identifier is the page identifier of the page requested to be queried by the call sequence query request.

[0099] Step 430, obtain the interface call sequence from the trigger call record associated with the first page identifier.

[0100] Step 440, return the obtained interface call sequence to the initiator of the call sequence query request.

[0101] In this embodiment, the trigger call record generated for the target interface further includes the page identifier of the target page where the target control is located, thus, it is convenient to locate the page where the target control is located according to the trigger call record, and it is also convenient to classify or query the trigger call record according to the page.

[0102] In some application scenarios, if users are more concerned about the interface call sequence involved in a page, they can follow the process of steps 410-440 above, use the page identifier as the search term, and search for the interface call sequence corresponding to the controls on the page indicated by the page identifier.

[0103] As described above, since the trigger call record is obtained by associating the control information of the target control with the interface call sequence of the target interface, and the trigger call record includes the page identifier, therefore, the trigger call record can be queried first according to the page identifier (i.e., the first page identifier) of the page requested by the call sequence query request to obtain the trigger call record including the first page identifier; then the interface call sequence can be correspondingly obtained from the queried trigger call record.

[0104] Through the above process, the query of the interface call sequence according to the page identifier of the page is realized, which is convenient for users to quickly understand the interface call sequence related to a specific page.

[0105] Figure 5 It is a schematic diagram of an interface showing the query result of the interface call sequence according to a specific embodiment. As Figure 5 shown, it shows the interface call sequence related to the page with the page identifier (invoiceid) of c8cd1651-e9c7-fbc0-e179-cb1e8107a866. The displayed interface call sequence not only includes the call time of the target interface, but also the call order of each interface from top to bottom in the displayed interface call sequence is from first to last, and each line shows the relevant information of an interface. In Figure 5 it, the value of the field fstring43 is used to indicate the name of the interface, the value of the field fstring44 is used to indicate the interface input parameters of the interface; the value of the field fstring45 is used to indicate the interface output parameters of the interface; the value of the sub-field finvoiceid is used to indicate the page identifier.

[0106] In some embodiments of the present application, the triggered control can also be queried based on the trigger record information reported by each client. In a specific embodiment, according to the page identifier (for the convenience of description, this page identifier is called the second page identifier) in the received triggered control query request, the trigger record information including the second page identifier can be queried, and then the control information can be obtained from the queried trigger record information, and the obtained control information is the triggered control on the page indicated by the second page identifier.

[0107] Figure 6 It is a schematic diagram of an interface showing the query result of the triggered control according to a specific embodiment, as Figure 6As shown, in the display area for querying the results of the triggered control, the buried point name corresponding to the triggered control on the page with the page identifier (invoiceid) of c8cd1651 - e9c7 - fbc0 - e179 - cb1e8107a866 is displayed. The value of the sub - segment fstring33 is used to indicate the name of the buried point set at the control. Since the buried point and the control are in one - to - one correspondence, therefore, the control can be determined correspondingly through this buried point name, that is, the control for the triggered operation.

[0108] In some embodiments of the present application, as Figure 7 shown, the method further includes:

[0109] Step 710, obtain first trigger record information corresponding to the user identifier of the target user and the page identifier of the target page within a specified time period.

[0110] The first trigger record information refers to the trigger record information reported within a specified time period and generated according to the controls triggered by the target user on the target page. Among them, the specified time period can be set by the user according to actual needs.

[0111] Step 720, obtain the position information of the control corresponding to the first trigger record information in the target page from the control information included in the first trigger record information.

[0112] Step 730, generate first display control information according to the position information, and the first display control information is used to control the marked display of the controls triggered within the specified time period on the target page.

[0113] The generated first display control information indicates the position information of the controls triggered by the target user on the target page within a specified time period. (For the convenience of description, the triggered control is called the third control).

[0114] After step 730, the third control can be located on the target page according to the position information in the first display control information, and then, the located third control is marked and displayed. The marked display performed can be to set an additional color, or set a specified marker for the third control, which is not specifically limited here.

[0115] In some embodiments of the present application, the first trigger record information further includes trigger sequence information, and the trigger sequence information indicates the sequence in which the control corresponding to the first trigger record information is triggered within the specified time period; after step 710, the method further includes: generating second display control information according to the trigger sequence information in the first trigger record information, and the second display control information is used to control the trigger sequence marking of the controls triggered within the specified time period on the target page.

[0116] In this embodiment, the client needs to perform sequential statistics on the controls triggered in the page. In a specific embodiment, a statistical field for the user to perform sequential statistics on the triggered controls can be configured in the page logged in by the user. After detecting that a control in the page is triggered, the value of the statistical field is incremented by 1. During the process of generating trigger record information for the target control, the value of the statistical field at the corresponding moment is added to the trigger record information. Thus, the value of the statistical field in the trigger information record can be used as trigger sequence information to indicate the sequence in which the corresponding control is triggered within a specified time period.

[0117] In this embodiment, the second display control information indicates the trigger sequence of each control triggered by the target user in the target page within a specified time period. Thus, the trigger sequence of each control triggered by the target user in the target page within a specified time period can be determined according to the second display control information. Thus, it is convenient to intuitively understand the controls triggered in the target page within a specified time period.

[0118] Figure 8 is a schematic diagram showing the display of the controls triggered by the user in the page within a specified time period according to a specific embodiment, as Figure 8 shown, not only are the triggered controls marked and displayed in a display manner different from that of the untriggered controls. It can be seen that within this period of time, the controls triggered in this page include Figure 8 "New Orientation" (referred to as control A for convenience of description), "Select Orientation Package" (referred to as control B), "Female" in the gender column (control C), "Unlimited" in the behavioral interest intention column (control D) and "System Preferred" (control E), "Users with Installed Applications" in the application installation column (control F). And the triggered controls A - F are numerically marked, and the marked numbers are used to indicate the sequence in which the corresponding controls are triggered within a specified time period. As Figure 8 shown, the number marked on control A is 24, indicating that control A is the 24th control triggered by the user within the specified time period. The number marked on control B is 23, indicating that control B is the 23rd control triggered by the user within the specified time period.

[0119] In Figure 8 it also further shows the buried point information of the buried points configured for the triggered controls. In Figure 8 it shows the buried point names of the buried points corresponding to the controls with trigger sequences from 1 to 10. By configuring the buried points for the controls in the page, trigger record information can be generated and reported when the controls are triggered.

[0120] The following introduces the device embodiments of the present application, which can be used to execute the methods in the above embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the above method embodiments of the present application.

[0121] Figure 9 is a block diagram of an information processing device in interface call shown according to an embodiment, as Figure 9 shown. The information processing device in this interface call includes:

[0122] A trigger record information acquisition module 910, configured to acquire trigger record information of a target user, where the trigger record information is generated according to a trigger operation performed by the target user on a target control in a target page, and the trigger record information includes a user identifier of the target user, control information of the target control, a page identifier of the target page, and time information when the target user triggers the target control.

[0123] A first call information acquisition module 920, configured to acquire first call information corresponding to the time information and associated with the page identifier, where the first call information includes a tracking identifier and interface information of a target interface, and the tracking identifier is generated according to a call request for the target interface, and the call request for the target interface is initiated after detecting the trigger operation on the target control.

[0124] A second call information acquisition module 930, configured to acquire second call information associated with the tracking identifier, where the second call information includes sub-interface information of a sub-interface nestedly called during the process of calling the target interface.

[0125] A trigger call record generation module 940, configured to generate a trigger call record for the target control according to the control information of the target control, the interface information of the target interface, and the sub-interface information of the sub-interface.

[0126] In some embodiments of the present application, the trigger call record generation module 940 includes: an interface call sequence generation unit, configured to generate an interface call sequence of the target interface according to the interface information of the target interface and the sub-interface information of the sub-interface; a trigger call record generation unit, configured to associate the interface call sequence of the target interface with the control information of the target control to obtain a trigger call record for the target control.

[0127] In some embodiments of the present application, the interface call sequence generation unit includes: a called order determination unit, configured to determine the called order between sub-interfaces corresponding to multiple pieces of the second call information according to the called time information in the multiple pieces of the second call information; an association unit, configured to associate the interface information of the target interface and the sub-interface information in the multiple pieces of the second call information according to the called order, so as to obtain the interface call sequence of the target interface.

[0128] In some embodiments of the present application, the trigger call record further includes the page identifier of the target page where the target control is located; the information processing device in the interface call further includes: a call sequence query request acquisition module, configured to acquire a call sequence query request; a trigger call record acquisition module, configured to acquire a trigger call record associated with a first page identifier, where the first page identifier is the page identifier of the page requested to be queried by the call sequence query request; an interface call sequence acquisition module, configured to acquire an interface call sequence from the trigger call record associated with the first page identifier; a first return module, configured to return the acquired interface call sequence to the initiator of the call sequence query request.

[0129] In some embodiments of the present application, the information processing device in the interface call further includes: a first trigger record information acquisition module, configured to acquire first trigger record information corresponding to the user identifier of the target user and the page identifier of the target page within a specified time period; a position information acquisition module, configured to acquire the position information of the control corresponding to the first trigger record information in the target page from the control information included in the first trigger record information; a first display control information generation module, configured to generate first display control information according to the position information, where the first display control information is used to control the marked display of the control triggered within the specified time period in the target page.

[0130] In some embodiments of the present application, the first trigger record information further includes trigger order information, where the trigger order information indicates the order in which the control corresponding to the first trigger record information is triggered within the specified time period; the information processing device in the interface call further includes: a second display control information generation module, configured to generate second display control information according to the trigger order information in the first trigger record information, where the second display control information is used to control the trigger order marking of the control triggered within the specified time period in the target page.

[0131] In some embodiments of the present application, the information processing device in the interface call further includes: a trigger record information receiving module, configured to receive the trigger record information reported by the client; wherein, after detecting a trigger operation on a target control in a target page, the client generates the trigger record information according to the user identifier of the user where the client is located, the page identifier of the target page, and the control information of the target control.

[0132] In some embodiments of the present application, the information processing device in the interface call further includes: a first call information receiving module, configured to receive the first call information reported by the client; after receiving the call result and the tracking identifier for a target interface returned by the service end, the client generates the first call information according to the tracking identifier, the page identifier, and the interface information of the target interface, and the interface information includes the called time information of the target interface, wherein the tracking identifier is generated by the service end after receiving the call request initiated by the client for the target interface.

[0133] In some embodiments of the present application, the information processing device in the interface call further includes: a second call information receiving module, configured to receive the second call information reported by the middle platform service end, and after receiving the call request for the sub-interface corresponding to the target interface, the middle platform service end generates the second call information according to the interface information of the sub-interface and the tracking identifier, and the service end sends the call request for the sub-interface to the middle platform service end according to the tracking identifier.

[0134] Figure 10 FIG. shows a schematic structural diagram of a computer system of an electronic device suitable for implementing the embodiments of the present application.

[0135] It should be noted that Figure 10 The computer system 1000 of the electronic device shown is only an example, and should not impose any limitation on the functions and usage scope of the embodiments of the present application.

[0136] Such as Figure 10As shown, computer system 1000 includes a Central Processing Unit (CPU) 1001, which can perform various appropriate actions and processes according to programs stored in a Read-Only Memory (ROM) 1002 or programs loaded from a storage section 1008 into a Random Access Memory (RAM) 1003, such as executing the methods in the above embodiments. In the RAM 1003, various programs and data required for system operations are also stored. The CPU 1001, ROM 1002, and RAM 1003 are connected to each other via a bus 1004. An Input / Output (I / O) interface 1005 is also connected to the bus 1004.

[0137] The following components are connected to the I / O interface 1005: an input section 1006 including a keyboard, a mouse, etc.; an output section 1007 including, for example, a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), etc. and speakers, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the I / O interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed so that a computer program read from it can be installed into the storage section 1008 as needed.

[0138] Specifically, according to an embodiment of the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program codes for executing the methods shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 1009, and / or installed from the removable medium 1011. When the computer program is executed by a Central Processing Unit (CPU) 1001, various functions defined in the system of the present application are executed.

[0139] It should be noted that the computer-readable medium shown in the embodiments of the present application can be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of a computer-readable storage medium can 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), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device. In the present application, a computer-readable signal medium can include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, and this computer-readable medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on a computer-readable medium can be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0140] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. Among them, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, and the above module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, and the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0141] The units involved in the embodiments of the present application can be implemented in software or in hardware, and the described units can also be provided in a processor. In some cases, the names of these units do not constitute a limitation on the units themselves.

[0142] On the other hand, the present application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or may exist alone without being assembled into the electronic device. The above computer-readable storage medium carries computer-readable instructions, and when the computer-readable storage instructions are executed by a processor, the methods in any of the above embodiments are implemented.

[0143] According to one aspect of the present application, an electronic device is also provided, which includes: a processor; a memory, on which computer-readable instructions are stored, and when the computer-readable instructions are executed by the processor, the methods in any of the above embodiments are implemented.

[0144] According to one aspect of the embodiments of the present application, a computer program product or a computer program is provided, which includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods in any of the above embodiments.

[0145] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of the two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0146] Through the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described herein can be implemented in software or in a manner of software combined with necessary hardware. Therefore, the technical solutions according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (such as a personal computer, a server, a touch terminal, or a network device, etc.) to execute the methods according to the embodiments of the present application.

[0147] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include known common general knowledge or conventional technical means in the technical field not disclosed in the present application.

[0148] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. An information processing method in interface call, characterized in that, The method includes: Obtaining trigger record information of a target user, where the trigger record information is generated based on a trigger operation performed by the target user on a target control in a target page, and the trigger record information includes a user identifier of the target user, control information of the target control, a page identifier of the target page, and time information when the target user triggers the target control; Obtaining first call information corresponding to the time information and associated with the page identifier, where the first call information includes a tracking identifier and interface information of a target interface, and the tracking identifier is generated based on a call request for the target interface, and the call request for the target interface is initiated after detecting the trigger operation on the target control; Obtaining second call information associated with the tracking identifier, where the second call information includes sub-interface information of a sub-interface nestedly called during the call of the target interface; Generating a trigger call record for the target control according to the control information of the target control, the interface information of the target interface, and the sub-interface information of the sub-interface.

2. The method according to claim 1, wherein The generating a trigger call record for the target control according to the control information of the target control, the interface information of the target interface, and the sub-interface information of the sub-interface includes: Generating an interface call sequence of the target interface according to the interface information of the target interface and the sub-interface information of the sub-interface; Associating the interface call sequence of the target interface with the control information of the target control to obtain a trigger call record for the target control.

3. The method according to claim 2, wherein The generating an interface call sequence of the target interface according to the interface information of the target interface and the sub-interface information of the sub-interface includes: Determining the call order between sub-interfaces corresponding to multiple pieces of the second call information according to the called time information in the multiple pieces of the second call information; Associating the interface information of the target interface and the sub-interface information in the multiple pieces of the second call information in accordance with the call order to obtain the interface call sequence of the target interface.

4. The method according to any one of claims 2-3, characterized in that, The trigger call record further includes a page identifier of the target page where the target control is located; The method further includes: Obtaining a call sequence query request; Obtaining a trigger call record associated with a first page identifier, where the first page identifier is the page identifier of the page requested to be queried by the call sequence query request; Obtaining an interface call sequence from the trigger call record associated with the first page identifier; Returning the obtained interface call sequence to the initiator of the call sequence query request.

5. The method according to claim 1, wherein The method further includes: Obtaining first trigger record information corresponding to the user identifier of the target user and the page identifier of the target page within a specified time period; Obtaining, from the control information included in the first trigger record information, position information of the control corresponding to the first trigger record information in the target page; Generating first display control information according to the position information, where the first display control information is used to control the marked display of the controls triggered within the specified time period in the target page.

6. The method according to claim 5, characterized in that, The first trigger record information further includes trigger sequence information, and the trigger sequence information indicates the sequence in which the control corresponding to the first trigger record information is triggered within the specified time period; After obtaining the first trigger record information corresponding to the user identifier of the target user and the page identifier of the target page within the specified time period, the method further includes: Generating second display control information according to the trigger sequence information in the first trigger record information, where the second display control information is used to control the trigger sequence marking of the controls triggered within the specified time period on the target page.

7. An information processing device in interface calls, characterized in that, including: A trigger record information acquisition module, configured to acquire trigger record information of a target user, where the trigger record information is generated according to a trigger operation performed by the target user on a target control on a target page, and the trigger record information includes the user identifier of the target user, the control information of the target control, the page identifier of the target page, and the time information when the target user triggers the target control; A first call information acquisition module, configured to acquire first call information corresponding to the time information and associated with the page identifier, where the first call information includes a tracking identifier and interface information of a target interface, and the tracking identifier is generated according to a call request for the target interface, and the call request for the target interface is initiated after detecting a trigger operation on the target control; A second call information acquisition module, configured to acquire second call information associated with the tracking identifier, where the second call information includes sub-interface information of a sub-interface nested and called during the call of the target interface; A trigger call record generation module, configured to generate a trigger call record for the target control according to the control information of the target control, the interface information of the target interface, and the sub-interface information of the sub-interface; 8. The device according to claim 7, characterized in that, The trigger call record generation module includes: An interface call sequence generation unit, configured to generate an interface call sequence of the target interface according to the interface information of the target interface and the sub-interface information of the sub-interface; A trigger call record generation unit, configured to associate the interface call sequence of the target interface with the control information of the target control to obtain a trigger call record for the target control.

9. An electronic device, characterized in that, including: A processor; A memory, on which computer-readable instructions are stored, and when the computer-readable instructions are executed by the processor, the method described in any one of claims 1-6 is implemented.

10. A computer-readable storage medium, on which computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor, the method described in any one of claims 1-6 is implemented.

Images