Information collection method and device, equipment, and storage medium

Abstract

The present disclosure relates to an information collection method and device, equipment and storage medium. The method applied to a collection device comprises: receiving identification information sent by a gateway device; wherein the identification information comprises interface identification of each application associated with the gateway device and gateway identification of the gateway device; generating a collection instruction for collecting running results of the application based on the interface identification of each application and the gateway identification of the gateway device, and sending the collection instruction to the gateway device; and receiving the running results of the application forwarded by the gateway device based on the collection instruction. Through the method, on the one hand, it is beneficial to reduce the performance consumption of the collection device or the gateway device when collecting large amounts of data; on the other hand, it is beneficial to improve the purpose and efficiency of information collection.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to an information acquisition method, apparatus, device, and storage medium. Background Technology

[0002] In recent years, with the rapid development of the internet, the number of Application Programming Interfaces (APIs) has been continuously increasing. APIs contain a wealth of valuable data, which is often used for big data analysis, risk analysis, and prevention. For example, user-related information can be collected from APIs for user behavior analysis; sensitive and risky data can also be collected to enhance application security. Therefore, how to efficiently collect application-related information has become a significant concern. Summary of the Invention

[0003] This disclosure provides an information collection method, apparatus, device, and storage medium.

[0004] According to a first aspect of the present disclosure, an information acquisition method is provided, applied in an acquisition device, comprising:

[0005] Receive identification information sent by the gateway device; wherein, the identification information includes: the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device;

[0006] Based on the interface identifiers of each application and the gateway identifier of the gateway device, a collection instruction is generated to collect the running results of the application, and the collection instruction is sent to the gateway device.

[0007] Receive the running results of the application forwarded by the gateway device based on the collection command.

[0008] In some embodiments, the step of generating a collection instruction for collecting the running results of applications based on the interface identifiers of each application and the gateway identifier of the gateway device includes:

[0009] Determine the historical number of times the gateway device collects the running results of the target application identified by the interface identifier within a preset time period;

[0010] Determine the frequency at which the gateway device indicated by the gateway identifier collects the operation results;

[0011] Based on the historical number of times the gateway device collects data from the target application and the collection frequency of the gateway device, a collection instruction is generated to collect the running results of the target application.

[0012] In some embodiments, generating a collection instruction for collecting the running results of the target application based on the historical collection quantity of the target application by the gateway device and the collection frequency of the gateway device includes:

[0013] In response to the fact that the collection frequency of the gateway device is less than or equal to a preset frequency threshold, and the number of historical collections of the target application by the gateway device is less than or equal to a preset number threshold, a collection instruction is generated to collect the running results of the target application.

[0014] In some embodiments, the method further includes:

[0015] In response to the gateway device's collection frequency being greater than the preset frequency threshold, or the gateway device collecting more historical data from the target application than the preset number threshold, an instruction is generated to not collect the running results of the target application.

[0016] The instruction to not collect the running results of the target application is sent to the gateway device.

[0017] In some embodiments, determining the frequency at which the gateway device indicated by the gateway identifier collects the operation results includes:

[0018] In response to the gateway device collecting historical data of the target application being less than or equal to the preset threshold, the frequency of data collection of the running results by the gateway device indicated by the gateway identifier is determined.

[0019] According to a second aspect of the present disclosure, an information collection method is provided, applied in a gateway device, comprising:

[0020] Send identification information to the acquisition device; wherein, the identification information includes: the interface identifier of each application associated with the gateway device and the gateway identifier of the gateway device;

[0021] The system receives a collection instruction from the collection device to collect the running results of the application; wherein the collection instruction is generated by the collection device based on the interface identifier of each application and the gateway identifier of the gateway device.

[0022] Based on the acquisition command, the application's execution results are forwarded to the acquisition device.

[0023] In some embodiments, the method further includes:

[0024] Receive the instruction sent by the acquisition device indicating that the running results of the application will not be collected;

[0025] According to the instruction, the application's execution results are not forwarded to the data acquisition device.

[0026] In some embodiments, forwarding the application's execution results to the collection device includes:

[0027] When the gateway device is in an idle state, the running results are forwarded to the acquisition device.

[0028] According to a third aspect of the present disclosure, an information acquisition device is provided, applied to an acquisition device, the device comprising:

[0029] The first receiving module is used to receive identification information sent by the gateway device; wherein, the identification information includes: the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device;

[0030] The first generation module is used to generate a collection instruction for collecting the running results of the applications based on the interface identifiers of each application and the gateway identifier of the gateway device, and send the collection instruction to the gateway device.

[0031] The second receiving module is used to receive the running results of the application forwarded by the gateway device based on the collection command.

[0032] In some embodiments, the first generation module is further configured to determine the historical number of times the gateway device collects the running results of the target application identified by the interface identifier within a preset time period; determine the collection frequency of the running results by the gateway device indicated by the gateway identifier; and generate a collection instruction for collecting the running results of the target application based on the historical number of times the gateway device collects the running results of the target application and the collection frequency of the gateway device.

[0033] In some embodiments, the first generation module is further configured to generate a collection instruction that indicates the collection of the running results of the target application in response to the fact that the collection frequency of the gateway device is less than or equal to a preset frequency threshold and the historical collection quantity of the target application by the gateway device is less than or equal to a preset quantity threshold.

[0034] In some embodiments, the first generation module is further configured to generate an instruction to not collect the running results of the target application in response to the fact that the collection frequency of the gateway device is greater than the preset frequency threshold, or the number of historical collections of the target application by the gateway device is greater than the preset number threshold.

[0035] The instruction to not collect the running results of the target application is sent to the gateway device.

[0036] In some embodiments, the first generation module is further configured to determine the collection frequency of the running results by the gateway device indicated by the gateway identifier in response to the gateway device collecting the historical data of the target application being less than or equal to the preset data threshold.

[0037] According to a fourth aspect of the present disclosure, an information collection device is provided, applied to a gateway device, the device comprising:

[0038] The first sending module is used to send identification information to the acquisition device; wherein, the identification information includes: the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device;

[0039] The third receiving module is used to receive a collection instruction sent by the collection device to collect the running results of the application; wherein the collection instruction is generated by the collection device based on the interface identifier of each application and the gateway identifier of the gateway device;

[0040] The first forwarding module is used to forward the running results of the application to the acquisition device based on the acquisition command.

[0041] In some embodiments, the apparatus is further configured to receive an instruction sent by the acquisition device indicating that the running results of the application are not collected;

[0042] According to the instruction, the application's execution results are not forwarded to the data acquisition device.

[0043] In some embodiments, the first forwarding module is further configured to forward the running results to the acquisition device when the gateway device is in an idle state.

[0044] According to a fifth aspect of the present disclosure, an electronic device is provided, the electronic device comprising:

[0045] processor;

[0046] Memory used to store processor-executable instructions;

[0047] The processor is configured to perform the information acquisition method as described in the first or second aspect above.

[0048] According to a sixth aspect of the present disclosure, a storage medium is provided, comprising:

[0049] When the instructions in the storage medium are executed by the first processor of the acquisition device, the acquisition device is able to perform the information acquisition method as described in the first aspect above; or, when the instructions in the storage medium are executed by the second processor of the access gateway, the gateway device is able to perform the information acquisition method as described in the second aspect above.

[0050] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0051] In the embodiments of this disclosure, the acquisition device and the gateway device are set up separately, and the calculation of the acquisition strategy and the implementation of the acquisition process are distributed to different devices to achieve decoupling. This allows the gateway device to focus only on the acquisition and forwarding of the results, while the acquisition device is responsible for determining the acquisition strategy (generating acquisition instructions). On the one hand, this helps to reduce the performance consumption of a single device (acquisition device or gateway device) when acquiring large amounts of data. On the other hand, the acquisition device also generates acquisition instructions (formulates acquisition strategies) based on the interface identifiers of each application and the gateway identifier of the gateway device to guide the gateway device to acquire and forward the results from other devices. This improves the purposefulness and efficiency of information acquisition and allows the acquisition device to acquire more information based on different gateway devices, thereby improving the accuracy of the system that uses the acquired information for related analysis (e.g., improving the accuracy of big data analysis and risk analysis).

[0052] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0053] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0054] Figure 1 This is a flowchart of an information collection method shown in an embodiment of the present disclosure. Figure 1 .

[0055] Figure 2 This is a flowchart of an information collection method shown in an embodiment of the present disclosure. Figure 2 .

[0056] Figure 3 This is a flowchart illustrating an information collection method according to an embodiment of this disclosure.

[0057] Figure 4 This is a framework diagram illustrating an information collection method according to an embodiment of this disclosure.

[0058] Figure 5 This is a flowchart of an information collection method according to an embodiment of this disclosure.

[0059] Figure 6 This is a diagram of an information acquisition device applied to an acquisition device in an embodiment of this disclosure.

[0060] Figure 7 This is a diagram of an information collection device applied to a gateway device in an embodiment of this disclosure.

[0061] Figure 8 This is a block diagram illustrating an electronic device 800 according to an exemplary embodiment. Detailed Implementation

[0062] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0063] Figure 1 This is a flowchart of an information collection method shown in an embodiment of the present disclosure. Figure 1 It is used in data acquisition devices, such as Figure 1 As shown, the information acquisition method applied in the acquisition device includes the following steps:

[0064] S11. Receive identification information sent by the gateway device; wherein, the identification information includes: the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device;

[0065] S12. Based on the interface identifier of each application and the gateway identifier of the gateway device, generate a collection instruction to collect the running results of the application, and send the collection instruction to the gateway device;

[0066] S13. Receive the running results of the application forwarded by the gateway device based on the collection command.

[0067] In this embodiment of the disclosure, the data acquisition device is an electronic device with computing and logic processing capabilities. It can be a terminal device such as a smartphone, tablet computer, laptop, personal digital assistant (PDA), handheld device, computing device, or vehicle-mounted device; or it can be other electronic devices such as a server. The gateway device can be a gateway-type electronic device, such as a single gateway or a gateway node device in a gateway cluster. For example, the gateway device can be an Nginx gateway.

[0068] In this embodiment, the data acquisition device and the gateway device establish a communication connection wirelessly or via a wired connection. The wireless communication connection methods include, for example, Bluetooth or mobile hotspot (Wireless Fidelity, WiFi). In this embodiment, the data acquisition device determines the running results of the application to be acquired and sends them to the gateway device as acquisition instructions, guiding the gateway device to forward the running results to the data acquisition device based on the acquisition instructions.

[0069] In step S11, the acquisition device receives identification information sent by the gateway device. This identification information includes the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device. In this embodiment, the interface identifiers of each application associated with the gateway device are identifiers that can uniquely identify the API; they can be the API name or the API path (e.g., a string consisting of the API's domain#path). In this embodiment, the gateway identifier of the gateway device is an identifier that can uniquely identify the gateway device; it can be the hostname of the gateway device or the IP address of the gateway device.

[0070] In this embodiment of the disclosure, the application is deployed on a third-party device (e.g., a server). The gateway device can connect to the third-party device via the network and communicate with it. The gateway device is associated with the calling interfaces of each application. Thus, the gateway device can access the application in the third-party device through the calling interfaces to obtain the running results of the application and forward them.

[0071] In this embodiment of the disclosure, the data acquisition device can connect to one or more gateway devices, and the application associated with the gateway device can be one or more. In step S12, the data acquisition device generates a data acquisition instruction for collecting the running results of the application based on the interface identifier of each application and the gateway identifier of the gateway device. For example, it generates a data acquisition instruction for collecting the running results of the target application identified by the interface identifier, which is forwarded by the target device identified by the gateway identifier, based on the gateway identifier of the gateway device and the interface identifier of the application. Alternatively, it can further combine at least one of the following to determine the data acquisition instruction for collecting the running results of the target application forwarded by the target device: the data acquisition frequency of the target device, the number of running results already collected, and the number of running results already collected of the target application. In this embodiment of the disclosure, the data acquisition instruction may also carry data acquisition parameters, such as the number of running results collected or the data acquisition interval.

[0072] In step S13, the acquisition device receives the running results of the application forwarded by the gateway device based on the acquisition command. The running results may include all or part of the data obtained by the application, such as business data, user privacy data, key data, etc.

[0073] It should be noted that the application's execution results typically contain a large amount of valuable information. In this embodiment of the disclosure, the application's execution results obtained by the acquisition device using the aforementioned information acquisition method can be directly sent to relevant systems (such as security analysis systems) for processing, or the execution results can be clustered, cleaned, and other processed before being provided to relevant systems for processing. For example, security analysis systems typically classify APIs by risk level and identify sensitive data based on API response information (application execution results), thereby achieving risk governance of APIs.

[0074] Typically, application execution results generate massive amounts of data. In related technologies, gateway devices directly collect these results based on predetermined policies. However, if the gateway device directly collects these massive amounts of data, it will consume a lot of power, which will affect its ability to handle other services (such as access control, load balancing, and routing management). On the other hand, if the gateway device collects only a small portion of the application's execution results randomly, the data collection will be insufficient or incomplete, which will affect the accuracy of subsequent systems that use the collected information for analysis.

[0075] In this embodiment, the acquisition device and gateway device are set up separately, and the calculation of the acquisition strategy and the implementation of the acquisition process are distributed to different devices to achieve decoupling. This allows the gateway device to focus only on the acquisition and forwarding of the results, while the acquisition device is responsible for determining the acquisition strategy (generating acquisition instructions). On the one hand, this helps reduce the performance consumption of a single device (acquisition device or gateway device) when acquiring large amounts of data. On the other hand, the acquisition device also generates acquisition instructions (formulates acquisition strategies) based on the interface identifiers of each application and the gateway identifier of the gateway device to guide the gateway device to acquire and forward the results from other devices. This improves the purposefulness and efficiency of information acquisition and allows the acquisition device to acquire more information based on different gateway devices, thereby improving the accuracy of the system that uses the acquired information for related analysis (e.g., improving the accuracy of big data analysis and risk analysis).

[0076] In some embodiments, the step of generating a collection instruction for collecting the running results of applications based on the interface identifiers of each application and the gateway identifier of the gateway device includes:

[0077] Determine the historical number of times the gateway device collects the running results of the target application identified by the interface identifier within a preset time period;

[0078] Determine the frequency at which the gateway device indicated by the gateway identifier collects the operation results;

[0079] Based on the historical number of times the gateway device collects data from the target application and the collection frequency of the gateway device, a collection instruction is generated to collect the running results of the target application.

[0080] In this embodiment of the disclosure, the data acquisition device can determine the historical data collection count of the target application within a preset time period by querying the historical running results of the application corresponding to the interface identifier in the cache, based on the interface identifier sent by the gateway device. Alternatively, the gateway device can calculate the historical data collection count of the target application's running results within the preset time period and send it to the data acquisition device. The preset time period can be a predetermined caching period for the application's running results, or a time period determined based on the application's business requirements.

[0081] In this embodiment of the disclosure, the data acquisition device can determine the frequency of data acquisition of one or more applications by the gateway device based on the gateway identifier sent by the gateway device.

[0082] In some embodiments, the data acquisition device may first determine whether to generate a data acquisition command based on the historical data acquisition quantity of the target application by the gateway device. If the historical data acquisition quantity is large, no data acquisition command will be generated; if the historical data acquisition quantity is small, the data acquisition frequency of the gateway device will be used to determine whether to generate a data acquisition command.

[0083] In other embodiments, the data acquisition device may first determine whether to generate a data acquisition command based on the data acquisition frequency of the gateway device. If the data acquisition frequency of the gateway device is too high, no data acquisition command will be generated. If the data acquisition frequency of the gateway device is low, the device may further determine whether to generate a data acquisition command based on the historical data acquisition quantity of the target application by the gateway device.

[0084] It should be noted that during application use, the same interface may be called repeatedly. This can result in two or more execution results for the same interface within a certain period. Repeatedly collecting the execution results of the same interface consumes significant device resources and is not particularly meaningful for security analysis. Furthermore, excessively high collection frequency from the gateway device can negatively impact its performance, while excessively low frequency may result in insufficient data collection.

[0085] In this embodiment, the acquisition device first determines the historical acquisition quantity and acquisition frequency of the target application by the gateway device within a preset time period. Based on this, it generates an acquisition instruction to acquire the running results of the target application. On the one hand, this reduces the repeated acquisition of the running results of the same application by the gateway device, which helps to improve the coverage of the acquisition of running results from different interfaces. On the other hand, it reduces the impact of the gateway device's excessively high acquisition frequency on the gateway device's performance, which helps to improve the stability of information acquisition.

[0086] In some embodiments, generating a collection instruction for collecting the running results of the target application based on the historical collection quantity of the target application by the gateway device and the collection frequency of the gateway device includes:

[0087] In response to the fact that the collection frequency of the gateway device is less than or equal to a preset frequency threshold, and the number of historical collections of the target application by the gateway device is less than or equal to a preset number threshold, a collection instruction is generated to collect the running results of the target application.

[0088] In this embodiment of the disclosure, the preset frequency threshold of the gateway device represents the collection frequency of the gateway device without affecting the operation of other services, and can be the maximum number of data collected by the gateway device per unit time.

[0089] In this embodiment of the disclosure, the preset quantity threshold represents the threshold number of times the running results of the target application are allowed to be collected. For example, when the preset quantity threshold is set to zero, it means that only applications that have never had their running results collected within a preset time period will be collected.

[0090] As mentioned earlier, the collection command can carry the number of execution results to be collected and / or the collection interval duration. For example, in this embodiment, the collection device can determine the number of execution results to be collected from the target application based on the difference between a preset quantity threshold and the historical collection quantity, and include this number in the collection command. Furthermore, the collection device can also determine the collection interval duration based on the number of execution results to be collected from the target application and the running frequency of the target application, and include this duration in the collection command. This method allows the gateway device to collect data more purposefully; for example, based on a determined number of results to be collected, a specified number of results can be collected; based on a determined collection interval duration, the execution results can cover different execution time points, thereby improving the quality of information collection.

[0091] In this embodiment of the disclosure, the collection instruction represents the sampling strategy for sampling the running results of the application. This strategy can be controlled by a preset duration, a preset quantity threshold, and a preset frequency threshold. The preset frequency threshold controls the maximum number of running results that a gateway device is allowed to collect or forward per second, thereby limiting the gateway's performance consumption. The preset duration (the duration for which running results are cached in the collection device) controls the gateway device to only collect or forward the running results of the application within the preset duration, based on the preset quantity threshold. This controls the number of running results of different APIs that a gateway device can send within the preset duration to be equal to the preset duration multiplied by the preset frequency threshold, thus achieving comprehensive and complete collection of the application's running results with minimal performance consumption on the gateway device.

[0092] In this embodiment of the disclosure, the collection frequency of the gateway device is limited by a preset frequency threshold, and the number of times the running results of the target application are collected is limited by a preset quantity threshold. This allows the collection device to guide the gateway device to collect the running results of as many target applications as possible without affecting the performance of the gateway device, thereby improving the stability and coverage of information collection.

[0093] In some embodiments, the method further includes:

[0094] In response to the gateway device's collection frequency being greater than the preset frequency threshold, or the gateway device collecting more historical data from the target application than the preset number threshold, an instruction is generated to not collect the running results of the target application.

[0095] The instruction to not collect the running results of the target application is sent to the gateway device.

[0096] As mentioned earlier, repeatedly collecting the results of the same interface within a certain period of time will consume a lot of device resources, and frequent collection by the gateway device can easily lead to a decrease in the performance of the gateway device. All of the above are situations where it is not suitable to collect the results of the operation.

[0097] In this embodiment of the present disclosure, when the collection frequency of the gateway device is greater than a preset frequency threshold, or when the number of historical collections of the target application by the gateway device is greater than a preset number threshold, the collection device directly generates an instruction to not collect the running results of the target application. This enables the gateway device to not collect the running results of the application based on the instruction, or to not forward the running results to the collection device after collection. This reduces the interaction of the working instructions of the gateway device, thereby reducing the performance consumption of the gateway device.

[0098] It should be noted that in this embodiment of the disclosure, the instruction sent by the acquisition device to the gateway device based on the identification information sent by the gateway device may carry identification information, wherein the identification information is used to characterize whether to collect the running results of the application. For example, when the identification information is "1", the instruction may be a collection instruction to collect the running results of the application, that is, the acquisition device constructs an API collection instruction; when the identification information is "0", the instruction may be an instruction to not collect the running results of the target application, that is, the acquisition device constructs an API ignore instruction.

[0099] In some embodiments, determining the frequency at which the gateway device indicated by the gateway identifier collects the operation results includes:

[0100] In response to the gateway device collecting historical data of the target application being less than or equal to the preset threshold, the frequency of data collection of the running results by the gateway device indicated by the gateway identifier is determined.

[0101] It should be noted that the collection instructions generated by the collection device are instructions used to guide the collection of the running results of the target application. If the historical collection count of the target application has exceeded the preset threshold, it usually indicates that the running results of the target application have met the collection requirements, and there is no need to collect data for the target application.

[0102] Therefore, in this embodiment of the disclosure, the collection frequency of the gateway device is further determined only when the number of historical collections of the target application is less than or equal to a preset number threshold. On the one hand, this can reduce the power consumption of the collection device caused by determining the collection frequency. On the other hand, it can also reduce the generation of meaningless collection instructions by the collection device and reduce the invalid data collection and forwarding of the gateway device, thereby reducing the performance consumption of the gateway device.

[0103] Figure 2 This is a flowchart of an information collection method shown in an embodiment of the present disclosure. Figure 2 It is used in gateway devices, such as Figure 2 As shown, the information collection method applied to gateway devices includes the following steps:

[0104] S21. Send identification information to the acquisition device; wherein, the identification information includes: the interface identifier of each application associated with the gateway device and the gateway identifier of the gateway device;

[0105] S22. Receive a collection instruction sent by the collection device to collect the running results of the application; wherein the collection instruction is generated by the collection device based on the interface identifier of each application and the gateway identifier of the gateway device;

[0106] S23. Based on the acquisition command, forward the application's running results to the acquisition device.

[0107] In this embodiment of the disclosure, the gateway device can be a gateway-type electronic device, such as a single gateway, a gateway node device in a gateway cluster, etc. In some embodiments, the gateway device is set as a single gateway, and one or more applications are associated on the single gateway. The gateway can interact with the collection device to collect information. In other embodiments, the gateway device can be set as a gateway node device in a gateway cluster. Each gateway node can be associated with one or more applications, and multiple gateway nodes can interact with the collection device to collect information.

[0108] In this embodiment of the disclosure, the gateway device and the acquisition device establish a communication connection wirelessly or via wired means. The gateway device obtains the identification information required for information acquisition and sends it to the acquisition device so that the acquisition device can generate acquisition instructions based on the identification information. Thus, the gateway device can collect the running results of the application based on the acquisition instructions and forward them to the acquisition device.

[0109] In step S21, the gateway device sends identification information to the data acquisition device. This identification information includes the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device itself. The identification information may be obtained by the gateway device from a third-party device where the applications are deployed. In step S22, the gateway device may receive data acquisition instructions from the data acquisition device in real time, or it may receive these instructions only when the gateway device detects that it is in a relatively idle state. The content of the data acquisition instructions generated by the data acquisition device is explained above.

[0110] In step S23, after receiving the collection instruction, the gateway device can acquire and forward the application's running results based on the collection instruction. There are several ways for the gateway device to acquire the application's running results: it can acquire the running results of the associated application from a third-party device running the application; or it can acquire the running results of the associated application from its own cached historical running results.

[0111] In this embodiment of the disclosure, when the gateway device acquires the running results, it can acquire the running results according to the acquisition parameters carried in the acquisition command. These acquisition parameters include the interface identifier of the application to be acquired, the number of results to be acquired, and the acquisition interval duration. For example, the gateway device can acquire a predetermined number of running results according to the number of results in the acquisition parameters; or it can acquire the running results according to the acquisition interval duration indicated in the acquisition parameters.

[0112] In this embodiment of the disclosure, the gateway device can forward the running results to the acquisition device in real time, or it can forward the running results to the acquisition device when the gateway device is idle.

[0113] In this embodiment, the acquisition device and the gateway device are set up separately, and the calculation of the acquisition strategy and the implementation of the acquisition process are distributed to different devices to achieve decoupling. This allows the gateway device to focus only on the acquisition and forwarding of the results, while the acquisition device is responsible for determining the acquisition strategy (generating acquisition instructions). On the one hand, this helps reduce the performance consumption of a single device (acquisition device or gateway device) when acquiring large amounts of data. On the other hand, the acquisition device also generates acquisition instructions (formulates acquisition strategies) based on the interface identifiers of each application and the gateway identifier of the gateway device to guide the gateway device to acquire and forward the results from other devices. This improves the purposefulness and efficiency of information acquisition and allows the acquisition device to acquire more information based on different gateway devices, thereby improving the accuracy of the system that uses the acquired information for related analysis (e.g., improving the accuracy of big data analysis and risk analysis).

[0114] In some embodiments, the device receives an instruction indicating that the running results of the application will not be collected.

[0115] According to the instruction, the application's execution results are not forwarded to the data acquisition device.

[0116] In this embodiment of the disclosure, the acquisition device can send an instruction not to collect the running results of the application when it is not suitable to collect the running results as described above. As a result, the gateway device does not need to collect or forward the running results, which helps to save the device resources of the gateway device.

[0117] In some embodiments, when the gateway device is in an idle state, the running results are forwarded to the acquisition device.

[0118] In this embodiment of the disclosure, the idle state of the gateway device can be a state where the utilization rate of the gateway device's central processing unit is low, or a state where the gateway device is not processing important or resource-intensive processes. For example, the gateway device can be considered to be in an idle state when it is generating logs.

[0119] In this embodiment, the gateway device forwards the running results to the acquisition device when idle, reducing the impact of forwarded data on the performance of the gateway device itself and improving the stability of the gateway device's operation.

[0120] Figure 3 This is a flowchart illustrating an information collection method according to an embodiment of this disclosure, such as... Figure 3As shown, the information acquisition method is applied to the acquisition device and the gateway device, and includes the following steps:

[0121] S31. The gateway device sends identification information to the acquisition device; wherein, the identification information includes: the interface identifier of each application associated with the gateway device and the device identifier of the gateway device;

[0122] S32. The data acquisition device receives the identification information sent by the gateway device;

[0123] S33. The data acquisition device generates a data acquisition command to collect the running results of the application based on the interface identifier of each application and the device identifier of the gateway device, and sends the data acquisition command to the gateway device.

[0124] S34. The gateway device receives a collection instruction sent by the collection device to collect the running results of the application.

[0125] S35. The gateway device forwards the application's execution results to the acquisition device based on the acquisition command;

[0126] S36. The acquisition device receives the running results of the application forwarded by the gateway device based on the acquisition command.

[0127] In step S31, the gateway device sends identification information to the acquisition device. The identification information may be obtained by the gateway device through a third-party device (the server of the application). The identification information includes the interface identifier of each application associated with the gateway device and the device identifier of the gateway device. The application associated with the gateway device may be one or more.

[0128] In step S32, the acquisition device receives identification information sent by the gateway device. The acquisition device can receive identification information from one or more gateway devices with which it has established network communication.

[0129] In step S33, the acquisition device generates an acquisition instruction to collect the running results of the application based on the interface identifier of each application and the device identifier of the gateway device, and sends the acquisition instruction to the gateway device. The acquisition instruction may also carry acquisition parameters, including the interface identifier of the application to be acquired, the number of running results to be acquired, or the acquisition interval of the running results.

[0130] In step S34, the gateway device can receive the acquisition command sent by the acquisition device in real time, or it can receive the acquisition command sent by the acquisition device when the gateway device detects that it is in a relatively idle state.

[0131] In step S35, the gateway device acquires and forwards the application's execution results based on the acquisition command. The gateway device can acquire the application's execution results from a third-party device running the application, or it can acquire them from its own cached historical execution results. Furthermore, the gateway device can send the application's execution results to the acquisition device in real time, or it can send the application's execution results to the acquisition device when the gateway device is idle.

[0132] In step S36, the acquisition device receives the running results of the application, which may include all or part of the data obtained from the application's execution.

[0133] In this embodiment, the acquisition device and the gateway device are set up separately, and the calculation of the acquisition strategy and the implementation of the acquisition process are distributed to different devices to achieve decoupling. This allows the gateway device to focus only on the acquisition and forwarding of the results, while the acquisition device is responsible for determining the acquisition strategy (generating acquisition instructions). On the one hand, this helps reduce the performance consumption of a single device (acquisition device or gateway device) when acquiring large amounts of data. On the other hand, the acquisition device also generates acquisition instructions (formulates acquisition strategies) based on the interface identifiers of each application and the gateway identifier of the gateway device to guide the gateway device to acquire and forward the results from other devices. This improves the purposefulness and efficiency of information acquisition and allows the acquisition device to acquire more information based on different gateway devices, thereby improving the accuracy of the system that uses the acquired information for related analysis (e.g., improving the accuracy of big data analysis and risk analysis).

[0134] Figure 4 This is a framework diagram illustrating an information collection method according to an embodiment of this disclosure, such as... Figure 4 As shown, the information collection method is applied to the repeaters (gateway devices) and collection devices of each gateway in the gateway cluster. The framework of the information collection method consists of the repeaters and collection devices of the gateways in the gateway cluster. The repeaters can be written in lightweight Lua scripts and embedded in each gateway in the gateway cluster (e.g., an Nginx gateway). The collection devices include deduplication devices (e.g., API deduplication devices) and rate limiters.

[0135] In this embodiment of the disclosure, the repeater and the acquisition device are deployed on different devices and communicate with each other via wired or wireless networks. The repeater is used to collect data on the Nginx gateway (e.g., API request data and response information), including identification information required for information collection (e.g., API identification information and gateway identification information of the gateway associated with the API), and API response information (running results) collected from the gateway device according to the sampling instructions. The repeater sends the above data to the acquisition device. In addition, the repeater can also receive acquisition instructions sent by the acquisition device.

[0136] In this embodiment of the disclosure, the data acquisition device is used to determine whether it is necessary to collect API response information based on the API identification information sent by the repeater and the gateway identification information corresponding to the gateway associated with the API. If it is necessary to collect API response information, the device sends a collection command to the repeater to guide the repeater to collect the API response information. In addition, the data acquisition device can also receive API response information sent by the repeater.

[0137] Figure 5 This is a flowchart of an information collection method according to an embodiment of this disclosure. For example... Figure 5 As shown, the information acquisition method is applied to the acquisition device and the gateway device, and includes the following steps:

[0138] S501. Obtain identification information, including the unique identifier of the application programming interface and the unique identifier of the gateway node;

[0139] In this embodiment, the forwarder obtains the unique identifier of the application interface (e.g., a string consisting of the API's domain#path) and the unique identifier of the gateway node (e.g., the hostname or network address of the Nginx node).

[0140] S502, Send identification information to the data acquisition device;

[0141] In this embodiment, the repeater sends identification information to the sampling device, that is, the gateway device sends identification information to the sampling device in this embodiment of the present disclosure.

[0142] S503, read the cache time of the application interface and the threshold for collecting gateway node responses;

[0143] In this embodiment, the collection device can obtain in advance the cache time of the application interface (e.g., the cache time length t1 of API response information in the collection device) and the gateway node response collection threshold (e.g., the maximum number of API response information that an Nginx node is allowed to send per second q1), where t1 and q1 are pre-configured according to the machine performance of the gateway.

[0144] S504. Obtain identification information;

[0145] In this embodiment, the acquisition device obtains the identification information sent by the repeater.

[0146] S505. During the cache period, has the response of the application interface been collected? If yes, proceed to step S508; if no, proceed to step S506.

[0147] In this embodiment, the acquisition device determines whether the application interface response (API response information) has been collected within the cache time (t1). If it has not been collected, it can further determine whether the performance of the gateway node supports the collection of the response.

[0148] S506. The number of times the gateway node response is collected is less than the response collection threshold; if yes, proceed to step S507; if no, proceed to step S508.

[0149] In this embodiment, the acquisition device determines whether the number of API response information collected by this gateway node within one second is less than the response collection threshold (q1). If it is, an API response acquisition instruction can be constructed; otherwise, an API response ignore instruction can be constructed.

[0150] S507, Construct the acquisition command for the application programming interface response;

[0151] In this embodiment, the acquisition device constructs an acquisition command in response to the application programming interface.

[0152] S508, Ignore instructions for constructing application interface responses;

[0153] In this embodiment, the acquisition device constructs an ignore instruction for the application programming interface response.

[0154] S509, Send acquisition command;

[0155] In this embodiment, the data acquisition device sends acquisition instructions, which include acquisition instructions indicating that the API response will be acquired, and ignore instructions indicating that the API response will not be acquired. The acquisition instructions and ignore instructions can be distinguished by acquisition identifier information. For example, acquisition identifier information can be set in the acquisition instructions; a acquisition identifier of "0" indicates an acquisition instruction to ignore the response, and a acquisition identifier of "1" indicates an acquisition instruction to acquire the response.

[0156] S510, Receive acquisition command;

[0157] In this embodiment, the repeater receives a collection command sent by the collection device. S511, The collection command represents a response from the collection application programming interface; if so, proceed to step S512;

[0158] In this embodiment, after receiving the collection instruction, the repeater determines whether the collection instruction is a collection instruction that represents the collection of response information.

[0159] S512, Collect response information from the application programming interface;

[0160] In this embodiment, when the acquisition instruction represents an acquisition instruction to acquire response information, the repeater collects the API response information and caches it.

[0161] S513, Asynchronously send the response information of the application programming interface to the acquisition device;

[0162] In this embodiment, the repeater asynchronously sends the cached API response information to the acquisition device.

[0163] S514, Receive response information.

[0164] In this embodiment, the data acquisition device receives response information from the API so that it can be provided to other devices or systems for various types of data analysis, such as risk analysis.

[0165] For example, if t1 is configured to 1800 seconds and q1 to 50, a gateway will only collect and send 50 API response messages per second, making the gateway performance consumption negligible. Furthermore, each API will only have its response message collected once within 1800 seconds. 1800 * 50 = 90,000, meaning each gateway can collect 90,000 different API response messages within 1800 seconds, completely covering all APIs on the gateway. Therefore, it can comprehensively and without omission collect all API response information, achieving comprehensive and complete API response information collection with extremely low gateway performance consumption, which is sufficient to meet subsequent security analysis, big data analysis, and other needs.

[0166] In this embodiment of the disclosure, the collection instruction represents the sampling strategy for sampling the running results of the application. The collection strategy can be formulated through the aforementioned t1 and q1 parameters. The q1 parameter is the maximum number of API response messages that a gateway node is allowed to send per second. This parameter limits the number of API response messages sent by the gateway, thereby limiting the gateway's performance consumption. The t1 parameter is the time for which a certain API is cached in the API deduplication device. It controls that the gateway only sends a certain API once within the t1 time. Therefore, the number of response messages of different APIs that a gateway can send is t1*q1.

[0167] In this embodiment, the repeater is embedded in the gateway device, and the acquisition device and the gateway device are set up separately. This decouples the calculation of the acquisition strategy and the implementation of the acquisition process by distributing them to different devices. The repeater on the gateway device only needs to focus on the acquisition and forwarding of the results, while the acquisition device is responsible for determining the acquisition strategy (generating acquisition instructions). On the one hand, this helps reduce the performance consumption of a single device (acquisition device or gateway device) when acquiring large amounts of data. On the other hand, the acquisition device also generates acquisition instructions (formulates acquisition strategies) based on the interface identifiers of each application and the gateway identifier of the gateway device to guide the repeater to acquire and forward the results from other devices through the gateway device. This improves the purposefulness and efficiency of information acquisition and allows the acquisition device to acquire more information based on different gateway devices, thereby improving the accuracy of the system using the acquired information for related analysis (e.g., improving the accuracy of big data analysis and risk analysis).

[0168] Figure 6 This is a diagram of an information acquisition device applied to an acquisition device according to an embodiment of this disclosure. (Refer to...) Figure 6 The information collection device 600 includes:

[0169] The first receiving module 601 is used to receive identification information sent by the gateway device; wherein, the identification information includes: the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device;

[0170] The first generation module 602 is used to generate a collection instruction for collecting the running results of the applications based on the interface identifiers of each application and the gateway identifier of the gateway device, and send the collection instruction to the gateway device.

[0171] The second receiving module 603 is used to receive the running results of the application forwarded by the gateway device based on the collection command.

[0172] In some embodiments, the first generation module 602 is further configured to determine the historical number of times the gateway device collects the running results of the target application identified by the interface identifier within a preset time period; determine the collection frequency of the running results by the gateway device indicated by the gateway identifier; and generate a collection instruction for collecting the running results of the target application based on the historical number of times the gateway device collects the running results of the target application and the collection frequency of the gateway device.

[0173] In some embodiments, the first generation module 602 is further configured to generate a collection instruction that indicates the collection of the running results of the target application in response to the fact that the collection frequency of the gateway device is less than or equal to a preset frequency threshold and the historical collection quantity of the target application by the gateway device is less than or equal to a preset quantity threshold.

[0174] In some embodiments, the first generation module 602 is further configured to generate an instruction to not collect the running results of the target application in response to the fact that the collection frequency of the gateway device is greater than the preset frequency threshold, or the number of historical collections of the target application by the gateway device is greater than the preset number threshold.

[0175] The instruction to not collect the running results of the target application is sent to the gateway device.

[0176] In some embodiments, the first generation module 602 is further configured to determine the collection frequency of the running results by the gateway device indicated by the gateway identifier in response to the gateway device collecting the historical data of the target application being less than or equal to the preset data threshold.

[0177] Figure 7 This is a diagram of an information collection device applied to a gateway device according to an embodiment of this disclosure. (Refer to...) Figure 7 The information collection device 700 includes:

[0178] The first sending module 701 is used to send identification information to the acquisition device; wherein, the identification information includes: the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device;

[0179] The third receiving module 702 is used to receive a collection instruction sent by the collection device to collect the running results of the application; wherein the collection instruction is generated by the collection device based on the interface identifier of each application and the gateway identifier of the gateway device;

[0180] The first forwarding module 703 is used to forward the running results of the application to the acquisition device based on the acquisition command.

[0181] In some embodiments, the apparatus is further configured to receive an instruction sent by the acquisition device indicating that the running results of the application are not collected;

[0182] According to the instruction, the application's execution results are not forwarded to the data acquisition device.

[0183] In some embodiments, the first forwarding module 703 is further configured to forward the running results to the acquisition device when the gateway device is in an idle state.

[0184] about Figure 6 and Figure 7 The specific manner in which each module performs its operation in the apparatus shown in the embodiments has been described in detail in the embodiments related to the method, and will not be elaborated here.

[0185] Figure 8 This is a block diagram illustrating an electronic device 800 according to an exemplary embodiment. For example, device 800 may be a mobile phone, a mobile computer, etc.

[0186] Reference Figure 8 The device 800 may include one or more of the following components: a processing component 802, a memory 804, a power supply component 806, a multimedia component 808, an audio component 810, an input / output (I / O) interface 812, a sensor component 814, and a communication component 816.

[0187] Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0188] Memory 804 is configured to store various types of data to support the operation of device 800. Examples of this data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0189] Power supply component 806 provides power to various components of device 800. Power supply component 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to device 800.

[0190] Multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0191] Audio component 810 is configured to output and / or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when device 800 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

[0192] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0193] Sensor assembly 814 includes one or more sensors for providing status assessments of various aspects of device 800. For example, sensor assembly 814 may detect the on / off state of device 800, the relative positioning of components such as the display and keypad of device 800, changes in the position of device 800 or a component of device 800, the presence or absence of user contact with device 800, the orientation or acceleration / deceleration of device 800, and temperature changes of device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0194] Communication component 816 is configured to facilitate wired or wireless communication between device 800 and other devices. Device 800 can access wireless networks based on communication standards, such as Wi-Fi, 4G, or 5G, or combinations thereof. In one exemplary embodiment, communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 816 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0195] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0196] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by a processor 820 of the device 800 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0197] A non-transitory computer-readable storage medium, wherein when instructions in the storage medium are executed by a processor of an acquisition device or a gateway device, the acquisition device or gateway device is enabled to perform the aforementioned information acquisition method.

[0198] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the foregoing claims.

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

Claims

1. An information collection method, characterized in that, When applied in a data acquisition device, the method includes: The system receives identification information sent by a gateway device; wherein the identification information includes: the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device; the applications are deployed on third-party devices; Based on the interface identifier of each application and the gateway identifier of the gateway device, a collection instruction is generated to collect the running results of the application, and the collection instruction is sent to the gateway device; wherein, the collection instruction is used to instruct the gateway device identified by the gateway identifier to forward the running results of the target application identified by the interface identifier; the collection instruction carries collection parameters, including the number of running results to be collected and / or the collection interval of running results; Receive the running results of the target application forwarded by the gateway device based on the collection command; Specifically, based on the interface identifiers of each application and the gateway identifier of the gateway device, a collection instruction for collecting the running results of the applications is generated, and the collection instruction is sent to the gateway device, including: Determine the historical number of times the gateway device collects the running results of the target application within a preset time period; Determine the frequency at which the gateway device indicated by the gateway identifier collects the operation results; Based on the historical data collection quantity of the target application by the gateway device and the collection frequency of the gateway device, a collection instruction is generated to collect the running results of the target application; wherein, the historical data collection quantity and the collection frequency are also used to determine whether to generate the collection instruction.

2. The method according to claim 1, characterized in that, The step of generating a collection instruction to collect the running results of the target application based on the historical collection quantity and collection frequency of the target application by the gateway device includes: In response to the fact that the collection frequency of the gateway device is less than or equal to a preset frequency threshold, and the number of historical collections of the target application by the gateway device is less than or equal to a preset number threshold, a collection instruction is generated to collect the running results of the target application.

3. The method according to claim 2, characterized in that, The method further includes: In response to the gateway device's collection frequency being greater than the preset frequency threshold, or the gateway device collecting more historical data from the target application than the preset number threshold, an instruction is generated to not collect the running results of the target application. The instruction to not collect the running results of the target application is sent to the gateway device.

4. The method according to claim 2, characterized in that, Determining the frequency at which the gateway device indicated by the gateway identifier collects operation results includes: In response to the gateway device collecting historical data of the target application being less than or equal to the preset threshold, the frequency of data collection of the running results by the gateway device indicated by the gateway identifier is determined.

5. An information collection method, characterized in that, When applied in a gateway device, the method includes: Send identification information to the data collection device; wherein, the identification information includes: the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device; the application is deployed on a third-party device; The system receives a collection instruction from the collection device to collect the running results of an application. The collection instruction is generated by the collection device based on the historical number of running results collected by the gateway device from the target application identified by the interface identifier within a preset time period, and the collection frequency of the running results by the gateway device indicated by the gateway identifier. The collection instruction is used to instruct the gateway device identified by the gateway identifier to forward the running results of the target application. The collection instruction carries collection parameters, including the number of running results collected and / or the collection interval duration. The historical number of collections and the collection frequency are also used by the collection device to determine whether to generate the collection instruction. Based on the acquisition command, the running results of the target application are forwarded to the acquisition device.

6. The method according to claim 5, characterized in that, The method further includes: Receive an instruction from the acquisition device indicating that the running results of the target application will not be collected; According to the instruction, the running results of the target application are not forwarded to the acquisition device.

7. The method according to claim 5, characterized in that, The forwarding of the target application's execution results to the acquisition device includes: When the gateway device is in an idle state, the running results are forwarded to the acquisition device.

8. An information acquisition device, characterized in that, Applied to a data acquisition device, the device includes: The first receiving module is used to receive identification information sent by the gateway device; wherein, the identification information includes: the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device; the application is deployed on a third-party device; The first generation module is used to generate a collection instruction for collecting the running results of the applications based on the interface identifiers of each application and the gateway identifier of the gateway device, and send the collection instruction to the gateway device; wherein, the collection instruction is used to instruct the gateway device identified by the gateway identifier to forward the running results of the target application identified by the interface identifier; the collection instruction carries collection parameters, including the number of running results to be collected and / or the collection interval of the running results; The second receiving module is used to receive the running results of the target application forwarded by the gateway device based on the collection command; The first generation module is further configured to: determine the historical number of times the gateway device collects the running results of the target application within a preset time period; determine the collection frequency of the running results by the gateway device indicated by the gateway identifier; and generate a collection instruction for collecting the running results of the target application based on the historical number of times the gateway device collects the running results of the target application and the collection frequency of the gateway device; the historical number of times the data is collected and the collection frequency are further configured to determine whether to generate the collection instruction.

9. An information acquisition device, characterized in that, Applied to a gateway device, the device includes: The first sending module is used to send identification information to the acquisition device; wherein, the identification information includes: the interface identifiers of each application associated with the gateway device and the gateway identifier of the gateway device; the application is deployed on a third-party device; The third receiving module is used to receive a collection instruction sent by the collection device to collect the running results of an application; wherein, the collection instruction is generated by the collection device based on the historical number of running results of the target application identified by the interface identifier collected by the gateway device within a preset time period and the collection frequency of running results by the gateway device indicated by the gateway identifier; the collection instruction is used to instruct the gateway device identified by the gateway identifier to forward the running results of the target application; the collection instruction carries collection parameters, including the number of running results collected and / or the collection interval duration of running results; the historical number of collections and the collection frequency are also used by the collection device to determine whether to generate the collection instruction; The first forwarding module is used to forward the running results of the target application to the acquisition device based on the acquisition command.

10. An electronic device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to perform the information acquisition method as described in any one of claims 1 to 4; or, configured to perform the information acquisition method as described in any one of claims 5 to 7.

11. A non-transitory computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the acquisition device, the acquisition device is able to perform the information acquisition method as described in any one of claims 1 to 4; or, when the instructions in the storage medium are executed by the processor of the access gateway, the gateway device is able to perform the information acquisition method as described in any one of claims 5 to 7.

Images