Information acquisition method and device, equipment and storage medium

Abstract

The invention relates to an information acquisition method and device, equipment and a storage medium. The method applied to the acquisition equipment comprises the following steps: receiving identification information sent by gateway equipment; wherein the identification information comprises an interface identification of each application program associated with the gateway equipment and a gateway identification of the gateway equipment; based on the interface identifier of each application program and the gateway identifier of the gateway equipment, generating an acquisition instruction for acquiring the running result of the application program, and sending the acquisition instruction to the gateway equipment; and receiving a running result of the application program forwarded by the gateway device based on the acquisition instruction. Through the method, on one hand, the performance consumption of the acquisition equipment or the gateway equipment during large data volume acquisition is reduced; and on the other hand, the purposiveness and efficiency of information acquisition can be improved.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to an information collection method and apparatus, device, and storage medium. Background Art

[0002] With the rapid development of the Internet in recent years, the number of application program interfaces (APIs) has been growing continuously. API-related information contains a lot of valuable data, which is usually used for big data analysis, risk analysis, and prevention and control. For example, user-related information in the API can be collected to analyze user behavior; for another example, sensitive data, risk data, and other information in the API can be collected to protect the application. Therefore, how to efficiently collect application-related information has become a highly concerned issue. Summary of the invention

[0003] The present invention provides an information collection method, device, equipment, and storage medium.

[0004] According to a first aspect of an embodiment of the present disclosure, there is provided an information collection method, which is applied to a collection device and includes:

[0005] Receiving identification information sent by a gateway device; wherein the identification information includes: interface identifications of each application associated with the gateway device and a gateway identification of the gateway device;

[0006] Based on the interface identifier of each application and the gateway identifier of the gateway device, generating a collection instruction for collecting the running results of the application, and sending the collection instruction to the gateway device;

[0007] Receive the running result of the application program forwarded by the gateway device based on the collection instruction.

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

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

[0010] Determine the frequency of collecting operation results by the gateway device indicated by the gateway identifier;

[0011] A collection instruction for collecting the running result of the target application is generated according to the historical collection quantity of the target application by the gateway device and the collection frequency of the gateway device.

[0012] In some embodiments, generating a collection instruction for collecting the running result of the target application according to 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 collection frequency of the gateway device being less than or equal to a preset frequency threshold, and the historical collection quantity of the target application by the gateway device being less than or equal to a preset quantity threshold, a collection instruction is generated to instruct collection of the running result of the target application.

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

[0015] In response to the collection frequency of the gateway device being greater than the preset frequency threshold, or the number of historical collections of the target application by the gateway device being greater than the preset number threshold, generating an instruction to instruct not to collect the running result of the target application;

[0016] An instruction indicating not to collect the running result of the target application is sent to the gateway device.

[0017] In some embodiments, determining the frequency of collecting the operation results by the gateway device indicated by the gateway identifier includes:

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

[0019] According to a second aspect of an embodiment of the present disclosure, there is provided an information collection method, which is applied to a gateway device, and includes:

[0020] Sending identification information to the collection device; wherein the identification information includes: the interface identification of each application associated with the gateway device and the gateway identification of the gateway device;

[0021] Receiving a collection instruction for collecting the running results of the application program sent by the collection device; wherein the collection instruction is generated by the collection device based on the interface identifier of each application program and the gateway identifier of the gateway device;

[0022] Based on the collection instruction, the running result of the application is forwarded to the collection device.

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

[0024] receiving an instruction sent by the collection device indicating that the running result of the application program is not to be collected;

[0025] According to the instruction, the running result of the application is not forwarded to the collection device.

[0026] In some embodiments, forwarding the running result of the application to the collection device includes:

[0027] When the gateway device is in an idle state, the operation result is forwarded to the collection device.

[0028] According to a third aspect of an embodiment of the present disclosure, there is provided an information collection device, which is applied to a collection device, and the device includes:

[0029] A first receiving module, configured to receive identification information sent by a gateway device; wherein the identification information includes: interface identifications of each application associated with the gateway device and a gateway identification of the gateway device;

[0030] A first generating module, configured to generate a collection instruction for collecting the running results of the application programs based on the interface identifiers of the application programs 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 result of the application program forwarded by the gateway device based on the collection instruction.

[0032] In some embodiments, the first generation module is also used to determine the number of historical collections of running results of the target application identified by the interface identifier by the gateway device 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 number of historical collections of the target application by the gateway device and the collection frequency of the gateway device.

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

[0034] In some embodiments, the first generating module is further configured to generate an instruction indicating not to collect the running result of the target application in response to the collection frequency of the gateway device being greater than the preset frequency threshold, or the historical collection quantity of the target application by the gateway device being greater than the preset quantity threshold;

[0035] An instruction indicating not to collect the running result of the target application is sent to the gateway device.

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

[0037] According to a fourth aspect of an embodiment of the present disclosure, there is provided an information collection device, which is applied to a gateway device, and the device includes:

[0038] A first sending module, used to send identification information to a collection device; wherein the identification information includes: interface identifications of each application associated with the gateway device and a gateway identification of the gateway device;

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

[0040] The first forwarding module is used to forward the running result of the application program to the collection device based on the collection instruction.

[0041] In some embodiments, the apparatus is further configured to receive an instruction sent by the collection device indicating that the running result of the application program is not to be collected;

[0042] According to the instruction, the running result of the application is not forwarded to the collection device.

[0043] In some embodiments, the first forwarding module is further used to forward the operation result to the collection device when the gateway device is in an idle state.

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

[0045] processor;

[0046] a memory for storing processor-executable instructions;

[0047] Wherein, the processor is configured to execute the information collection method as described in the first aspect or the second aspect above.

[0048] According to a sixth aspect of an embodiment of the present disclosure, there is provided a storage medium, including:

[0049] When the instructions in the storage medium are executed by the first processor of the collection device, the collection device is enabled to execute the information collection 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 enabled to execute the information collection method as described in the second aspect above.

[0050] The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

[0051] In the embodiments of the present disclosure, the collection device and the gateway device are separately provided, and the calculation of the collection strategy and the implementation of the collection process are assigned to different device operations to achieve decoupling, so that the gateway device only focuses on the collection and forwarding of the operation results, while the collection device is responsible for determining the collection strategy (generating collection instructions). On the one hand, it is beneficial to reduce the performance consumption of a single device (collection device or gateway device) when collecting large amounts of data; on the other hand, the collection device also generates collection instructions (formulates collection strategies) based on the interface identifiers of each application and the gateway identifier of the gateway device to guide the gateway device to collect and forward the operation results from other devices, thereby improving the purposefulness and efficiency of information collection, and is beneficial for the collection device to collect more information based on different gateway devices, thereby improving the accuracy of the system that subsequently uses the collected information for related analysis (for example, it can improve the accuracy of big data analysis and risk analysis).

[0052] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

[0056] Figure 3 It is a flow interaction diagram of an information collection method shown in an embodiment of the present disclosure.

[0057] Figure 4 It is a framework diagram of an information collection method shown in an embodiment of the present disclosure.

[0058] Figure 5 It is a flow chart of an information collection method in an embodiment of the present disclosure.

[0059] Figure 6 It is a diagram of an information collection device applied to a collection device in an embodiment of the present disclosure.

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

[0061] Figure 8 is a block diagram of an electronic device 800 according to an exemplary embodiment. DETAILED DESCRIPTION

[0062] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

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

[0064] S11, receiving identification information sent by a gateway device; wherein the identification information includes: interface identifications of each application associated with the gateway device and a gateway identification of the gateway device;

[0065] S12, based on the interface identifier of each application and the gateway identifier of the gateway device, generating a collection instruction for collecting the running results of the application, and sending the collection instruction to the gateway device;

[0066] S13: Receive the running result of the application forwarded by the gateway device based on the collection instruction.

[0067] In the disclosed embodiments, the acquisition device is an electronic device with computing and logic processing capabilities, and may be a terminal device such as a smart phone, a tablet computer, a notebook, a personal digital assistant (PDA), a handheld device, a computing device, a vehicle-mounted device, or other electronic devices, such as a server. The gateway device may be a gateway-type electronic device, such as a single gateway, a gateway node device in a gateway cluster, etc. For example, the gateway device may be an Nginx gateway.

[0068] In the embodiment of the present disclosure, a communication connection is established between the collection device and the gateway device in a wireless or wired manner, and the wireless communication connection method involved includes, for example, Bluetooth or a mobile hotspot (Wireless Fidelity, WiFi), etc. In the embodiment of the present disclosure, the collection device is used to determine the running results of the application to be collected and send them to the gateway device in the form of a collection instruction, so as to instruct the gateway device to forward the running results to the collection device based on the collection instruction.

[0069] In step S11, the acquisition device receives the identification information sent by the gateway device, and the identification information includes the interface identification of each application associated with the gateway device and the gateway identification of the gateway device. In the embodiment of the present disclosure, the interface identification of each application associated with the gateway device is an identification that can be used to uniquely identify the API, which can be the name of the API or the path of the API (for example, a string consisting of domain#path of the API). In the embodiment of the present disclosure, the gateway identification of the gateway device is an identification that can be used to uniquely identify the gateway device, which can be the host name of the gateway device or the IP address of the gateway device.

[0070] In the disclosed embodiment, the application is deployed on a third-party device (such as a server), and the gateway device and the third-party device can establish a network connection and communicate. The gateway device is associated with a calling interface for each application, and the gateway device can access the application in the third-party device through the calling interface to obtain the running results of the application and forward it.

[0071] In the embodiment of the present disclosure, the collection device can be connected to one or more gateway devices, and the application associated with the gateway device can be one or more. In step S12, the collection device generates a collection 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, based on the gateway identifier of the gateway device and the interface identifier of the application, a collection instruction for the running results of the target application identified by the interface identifier is generated to be forwarded by the target device identified by the gateway identifier; it can also be based on this and further combined with at least one of the collection frequency of the target device, the number of running results collected, and the number of running results of the target application that have been collected to determine the collection instruction for the running results of the target application forwarded by the target device. In the embodiment of the present disclosure, the collection instruction can also carry collection parameters, such as the number of running results collected or the collection interval of the running results.

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

[0073] It should be noted that the running results of the application usually contain a lot of valuable information. In the embodiment of the present disclosure, the running results of the application obtained by the acquisition device executing the above-mentioned information acquisition method can be directly sent to various related systems (such as security analysis systems) for processing, or the running results can be clustered, cleaned, etc. and then provided to various related systems for processing. For example, the security analysis system usually classifies the API risk level, identifies sensitive data, etc. according to the API response information (the running results of the application), thereby realizing risk management of the API.

[0074] Normally, the amount of data from the running results of an application is huge. In related technologies, the running results of the application are collected directly through a gateway device based on a predetermined strategy. If the gateway device directly collects massive running results, the large amount of collected data will cause large device consumption of the gateway device, which will in turn affect the gateway device's processing of other services (for example, access control, load balancing, routing management, etc.); if the gateway device randomly collects a small amount of running results of some applications, the amount of data collected will be small or incomplete, which will affect the accuracy of related systems that subsequently use the collected information for analysis.

[0075] In this regard, in an embodiment of the present disclosure, the collection device and the gateway device are separately provided, and the calculation of the collection strategy and the implementation of the collection process are assigned to different device operations to achieve decoupling, so that the gateway device only focuses on the collection and forwarding of the operation results, while the collection device is responsible for determining the collection strategy (generating collection instructions). On the one hand, it is beneficial to reduce the performance consumption of a single device (collection device or gateway device) when collecting large amounts of data; on the other hand, the collection device also generates collection instructions (formulates collection strategies) based on the interface identifiers of each application and the gateway identifier of the gateway device to guide the gateway device to collect and forward the operation results from other devices, thereby improving the purposefulness and efficiency of information collection, and is beneficial for the collection device to collect more information based on different gateway devices, thereby improving the accuracy of the system that subsequently uses the collected information for related analysis (for example, it can improve the accuracy of big data analysis and risk analysis).

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

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

[0078] Determine the frequency of collecting operation results by the gateway device indicated by the gateway identifier;

[0079] A collection instruction for collecting the running result of the target application is generated according to the historical collection quantity of the target application by the gateway device and the collection frequency of the gateway device.

[0080] In the disclosed embodiment, the collection device can determine the number of historical collections 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 according to the interface identifier sent by the gateway device; in addition, the gateway device can also calculate the number of historical collections of the running results of the target application within the preset time period and send it to the collection device. The preset time period can be a predetermined cache time period of the running results of the application, or a time period determined based on the business needs of the application.

[0081] In the disclosed embodiment, the collection device may count the historical number of running results of one or more applications collected by the gateway device per unit time according to the gateway identifier sent by the gateway device to determine the frequency with which the gateway device collects the running results.

[0082] In some embodiments, the collection device can first determine whether to generate a collection instruction based on the historical collection quantity of the target application by the gateway device. When the historical collection quantity is large, no collection instruction is generated; when the historical collection quantity is small, it is further determined whether to generate a collection instruction based on the collection frequency of the gateway device.

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

[0084] It should be noted that during the use of an application, the same interface may be called repeatedly. In this way, within a certain period of time, the same interface of the application may have two or more running results. Repeated collection of the running results of the same interface will occupy a lot of device resources and is not very meaningful for security analysis. In addition, if the collection frequency of the gateway device is too high, it will affect its own performance. If it is too low, the collection device may collect too few running results.

[0085] In this regard, in the embodiment of the present disclosure, the collection device first determines the historical collection quantity of the target application by the gateway device within a preset time period and the collection frequency of the gateway device, and generates a collection instruction for collecting the running results of the target application based on this. On the one hand, it can reduce the situation where the gateway device repeatedly collects the running results of the same application, which is beneficial to improve the coverage of the collection of running results of different interfaces; on the other hand, it can reduce the impact of the excessively high collection frequency of the gateway device on the performance of the gateway device, which is beneficial to improve the stability of information collection.

[0086] In some embodiments, generating a collection instruction for collecting the running result of the target application according to 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 collection frequency of the gateway device being less than or equal to a preset frequency threshold, and the historical collection quantity of the target application by the gateway device being less than or equal to a preset quantity threshold, a collection instruction is generated to instruct collection of the running result of the target application.

[0088] In the embodiment of the present 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 may be the maximum collection quantity of the gateway device in a unit time.

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

[0090] As mentioned above, the collection instruction may carry the number of run results collected and / or the length of the collection interval. For example, in this embodiment, the collection device may determine the number of run results to be collected of the target application based on the difference between the preset number threshold and the historical collection number and carry it in the collection instruction; in addition, the collection device may also determine the length of the collection interval based on the number of run results to be collected of the target application and the running frequency of the target application and carry it in the collection instruction. In this way, it is convenient for the gateway device to collect more purposefully, for example, based on the determined number to be collected, a specified number of collections can be achieved; based on the determined collection interval, the run results can cover different run time points, and in this way, the quality of information collection can be improved.

[0091] In the disclosed embodiment, the collection instruction represents a sampling strategy for sampling the running results of an application, which can be implemented by controlling a preset duration, a preset number 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, so as to limit gateway performance consumption; the preset duration (the duration for caching the running results in the collection device) is used to control that within the preset duration, the gateway device only collects or forwards the running results of applications with a preset number threshold, thereby controlling the number of running results of different APIs that a gateway device can send within the preset duration to be the preset duration multiplied by the preset frequency threshold, thereby achieving comprehensive and complete collection of the running results of the application with extremely low performance consumption of the gateway device.

[0092] In the disclosed embodiments, 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, so that the collection device can 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 of information collection and the collection coverage.

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

[0094] In response to the collection frequency of the gateway device being greater than the preset frequency threshold, or the number of historical collections of the target application by the gateway device being greater than the preset number threshold, generating an instruction to instruct not to collect the running result of the target application;

[0095] An instruction indicating not to collect the running result of the target application is sent to the gateway device.

[0096] As mentioned above, repeatedly collecting the operation results of the same interface within a certain period of time will occupy a lot of device resources, and the frequent collection of gateway devices will easily lead to reduced performance of the gateway device. The above are all situations that are not suitable for operation result collection.

[0097] In this regard, in an embodiment of the present disclosure, when the collection frequency of the gateway device is greater than a preset frequency threshold, or the historical collection quantity of the target application by the gateway device is greater than a preset quantity threshold, the collection device directly generates an instruction indicating not to collect the running results of the target application, so that the gateway device can not collect the running results of the application based on the instruction or not forward the running results to the collection device after collection, which can reduce the interaction of the work instructions of the gateway device, thereby reducing the performance consumption of the gateway device.

[0098] It should be noted that, in the embodiments of the present disclosure, the collection device may carry identification information in the instruction sent to the gateway device based on the identification information sent by the gateway device, wherein the identification information is used to indicate whether to collect the running results of the application. Exemplarily, when the identification information is "1", the instruction may be a collection instruction for collecting the running results of the application, that is, the collection device constructs an API collection instruction; when the identification information is "0", the instruction may be an instruction indicating not to collect the running results of the target application, that is, the collection device constructs an API ignore instruction.

[0099] In some embodiments, determining the frequency of collecting the operation results by the gateway device indicated by the gateway identifier includes:

[0100] In response to the historical collection quantity of the target application by the gateway device being less than or equal to the preset quantity threshold, the collection frequency of the operation result 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 for guiding the collection of the running results of the target application. If the historical collection times of the target application have 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 the target application at this time.

[0102] Therefore, in the embodiment of the present 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 due to determining the collection frequency. On the other hand, it can also reduce the generation of meaningless collection instructions by the collection device, and can also reduce invalid data collection and forwarding by the gateway device, thereby reducing the performance consumption of the gateway device.

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

[0104] S21, sending identification information to a collection device; wherein the identification information includes: interface identifications of each application associated with the gateway device and a gateway identification of the gateway device;

[0105] S22, receiving a collection instruction for collecting the running results of the application program sent by the collection device; wherein the collection instruction is generated by the collection device based on the interface identifier of each application program and the gateway identifier of the gateway device;

[0106] S23. Based on the collection instruction, forward the running result of the application to the collection device.

[0107] In the embodiments of the present disclosure, the gateway device may 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 configured as a single gateway, and one or more applications are associated with the single gateway. The gateway can interact with the collection device to collect information; in other embodiments, the gateway device can be configured as a gateway node device in a gateway cluster, and one or more applications can be associated with each gateway node, and multiple gateway nodes can interact with the collection device to collect information.

[0108] In the disclosed embodiment, a communication connection is established between the gateway device and the collection device in a wireless or wired manner. The gateway device obtains identification information required for information collection and sends it to the collection device, so that the collection device generates a collection instruction based on the identification information. The gateway device can then collect the running results of the application based on the collection instruction and forward it to the collection device.

[0109] In step S21, the gateway device sends identification information to the collection device, the identification information includes the interface identification of each application associated with the gateway device and the gateway identification of the gateway device, wherein the identification information may be obtained by the gateway device from a third-party device that deploys the application. In step S22, the gateway device may receive the collection instruction sent by the collection device in real time, or may receive the collection instruction sent by the collection device when the gateway device detects that it is in a relatively idle state, wherein the content of the collection instruction generated by the collection device please refer to the above description.

[0110] In step S23, after receiving the collection instruction, the gateway device can obtain and forward the running result of the application based on the collection instruction. There are many ways for the gateway device to obtain the running result of the application. The gateway device can obtain the running result of the associated application from a third-party device running the application; or the gateway device can obtain the running result of the associated application from the historical running results cached by itself.

[0111] In the embodiment of the present disclosure, when the gateway device acquires the operation results, the operation results may be collected according to the collection parameters carried in the collection instruction, wherein the collection parameters include the interface identifier of the application to be collected, the collection quantity, the collection interval duration, etc. For example, the gateway device may collect a predetermined number of operation results according to the collection quantity in the collection parameter; or the operation results may be collected according to the collection interval duration indicated in the collection parameter.

[0112] In the disclosed embodiment, the gateway device may forward the operation result to the collection device in real time, or may forward the operation result to the collection device when the gateway device is in an idle state.

[0113] In the disclosed embodiment, the collection device and the gateway device are separately provided, and the calculation of the collection strategy and the implementation of the collection process are assigned to different device operations to achieve decoupling, so that the gateway device only focuses on the collection and forwarding of the operation results, while the collection device is responsible for determining the collection strategy (generating collection instructions). On the one hand, it is beneficial to reduce the performance consumption of a single device (collection device or gateway device) when collecting large amounts of data; on the other hand, the collection device also generates collection instructions (formulates collection strategies) based on the interface identifiers of each application and the gateway identifier of the gateway device to guide the gateway device to collect and forward the operation results from other devices, thereby improving the purposefulness and efficiency of information collection, and is beneficial for the collection device to collect more information based on different gateway devices, thereby improving the accuracy of the system that subsequently uses the collected information for related analysis (for example, it can improve the accuracy of big data analysis and risk analysis).

[0114] In some embodiments, receiving an instruction sent by the collection device indicating that the running result of the application program is not to be collected;

[0115] According to the instruction, the running result of the application is not forwarded to the collection device.

[0116] In the disclosed embodiment, the collection device may send an instruction not to collect the running results of the application when it is not suitable to collect the running results as mentioned above, so that the gateway device does not need to collect or forward the running results, which is beneficial to saving the device resources of the gateway device.

[0117] In some embodiments, when the gateway device is in an idle state, the operation result is forwarded to the collection device.

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

[0119] In the disclosed embodiment, the gateway device forwards the operation result to the collection device in an idle state, thereby reducing the impact of the forwarded data on the performance of the gateway device itself, and is conducive to improving the stability of the operation of the gateway device.

[0120] Figure 3 is a flow chart of an information collection method shown in an embodiment of the present disclosure, such as Figure 3As shown, the information collection method is applied to the collection device and the gateway device, and includes the following steps:

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

[0122] S32, the collection device receives the identification information sent by the gateway device;

[0123] S33, the collection device generates a collection instruction for collecting 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 collection instruction 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 program;

[0125] S35, the gateway device forwards the running result of the application to the collection device based on the collection instruction;

[0126] S36. The collection device receives the running result of the application program forwarded by the gateway device based on the collection instruction.

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

[0128] In step S32, the collection device receives the identification information sent by the gateway device. The collection device may receive the identification information from one or more gateway devices with which the collection device establishes network communication.

[0129] In step S33, the collection device generates a collection instruction for collecting 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 collection instruction to the gateway device; wherein, the collection instruction may also carry collection parameters, including the interface identifier of the application to be collected, the number of running results to be collected, or the collection interval duration of the running results.

[0130] In step S34, the gateway device may receive the collection instruction sent by the collection device in real time, or may receive the collection instruction sent by the collection 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 running result of the application based on the collection finger, wherein the gateway device may acquire the running result of the associated application from a third-party device running the application; or the gateway device may acquire the running result of the associated application from the historical running result cached by itself. In addition, the gateway device may send the running result of the application to the collection device in real time; or it may send the running result of the application to the collection device when the gateway device is idle.

[0132] In step S36, the collection device receives the running result of the application, and the running result may include all or part of the data obtained by running the application.

[0133] In the disclosed embodiment, the collection device and the gateway device are separately provided, and the calculation of the collection strategy and the implementation of the collection process are assigned to different device operations to achieve decoupling, so that the gateway device only focuses on the collection and forwarding of the operation results, while the collection device is responsible for determining the collection strategy (generating collection instructions). On the one hand, it is beneficial to reduce the performance consumption of a single device (collection device or gateway device) when collecting large amounts of data; on the other hand, the collection device also generates collection instructions (formulates collection strategies) based on the interface identifiers of each application and the gateway identifier of the gateway device to guide the gateway device to collect and forward the operation results from other devices, thereby improving the purposefulness and efficiency of information collection, and is beneficial for the collection device to collect more information based on different gateway devices, thereby improving the accuracy of the system that subsequently uses the collected information for related analysis (for example, it can improve the accuracy of big data analysis and risk analysis).

[0134] Figure 4 is a framework diagram of an information collection method shown in an embodiment of the present disclosure, such as Figure 4 As shown, the information collection method is applied to the forwarder (gateway device) and collection device of each gateway in the gateway cluster, and the framework of the information collection method is composed of the forwarder and collection device of the gateway in the gateway cluster. Among them, the forwarder can be written by a lightweight Lua script and embedded in each gateway of the gateway cluster (for example, Nginx gateway), and the collection device includes a deduplication device (for example, an API deduplication device) and a flow limiter.

[0135] In the disclosed embodiment, the forwarder and the collection device are respectively deployed on different devices, and the two parties communicate through a wired or wireless network. The forwarder is used to collect data on the Nginx gateway (for example, API request data and response information), including identification information required for information collection (for example, API identification information and gateway identification information of the gateway associated with the API), and API response information (operation results) collected from the gateway device according to the sampling instruction, and sends the above data to the collection device. In addition, the forwarder can also receive collection instructions sent by the collection device.

[0136] In the disclosed embodiment, the collection device is used to determine whether it is necessary to collect response information for the API based on the identification information of the API sent by the forwarder and the gateway identification information corresponding to the gateway associated with the API, and if it is necessary to collect the API, send a collection instruction to the forwarder to instruct the forwarder to collect the API response information. In addition, the collection device can also receive the API response information sent by the forwarder.

[0137] Figure 5 FIG. 1 is a flow chart of an information collection method according to an embodiment of the present disclosure. Figure 5 As shown, the information collection method is applied to the collection device and the gateway device, and includes the following steps:

[0138] S501, obtaining identification information, including a unique identification of an application program interface and a unique identification of a gateway node;

[0139] In this embodiment, the forwarder obtains the unique identifier of the application program interface (eg, a string consisting of domain#path of the API) and the unique identifier of the gateway node (eg, the host name or network address of the Nginx node).

[0140] S502, sending identification information to a collection device;

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

[0142] S503, reading the cache time of the application program interface and the gateway node response collection threshold;

[0143] In this embodiment, the collection device can obtain in advance the cache time of the application program interface (for example, the cache time length t1 of the API response information in the collection device) and the gateway node response collection threshold (for example, the maximum number of API response information q1 allowed to be sent by the Nginx node in one second), where t1 and q1 are configured in advance based on the machine performance of the gateway.

[0144] S504, obtaining identification information;

[0145] In this embodiment, the collection device obtains the identification information sent by the transponder.

[0146] S505: Has the response of the application program interface been collected within the cache time? If so, execute step S508; if not, execute step S506;

[0147] In this embodiment, the collection device determines whether the response of the application program interface (API corresponding 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 gateway node response collections is less than the response collection threshold; if so, execute step S507; if not, execute step S508;

[0149] In this embodiment, the collection 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 so, an API response collection instruction can be constructed; if not, an API response ignore instruction can be constructed.

[0150] S507, constructing a collection instruction for an application program interface response;

[0151] In this embodiment, the collection device constructs a collection instruction in response to an application program interface.

[0152] S508, constructing an ignore instruction of the application program interface response;

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

[0154] S509, sending a collection instruction;

[0155] In this embodiment, the collection device sends a collection instruction, which includes a collection instruction indicating that the API response is to be collected, and an ignore instruction indicating that the API response is not to be collected. The collection instruction and the ignore instruction can be distinguished by the collection identification information. For example, the collection identification information can be set in the collection instruction. When the collection identification information is "0", it indicates a collection instruction to ignore the response, and when it is "1", it indicates a collection instruction to collect the response.

[0156] S510, receiving a collection instruction;

[0157] In this embodiment, the forwarder receives the collection instruction sent by the collection device. S511, the collection instruction represents the response of the collection application program interface; if so, execute step S512;

[0158] In this embodiment, after receiving the collection instruction, the forwarder determines whether the collection instruction is a collection instruction for collecting response information.

[0159] S512, collecting response information of the application program interface;

[0160] In this embodiment, the forwarder collects and caches the response information of the API when the collection instruction represents a collection instruction for collecting response information.

[0161] S513, asynchronously sending the response information of the application program interface to the acquisition device;

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

[0163] S514: Receive response information.

[0164] In this embodiment, the collection device receives the response information of the API so as to provide it to other devices or systems for various types of data analysis, such as risk analysis.

[0165] For example, if the current t1 is configured to 1800 seconds and q1 is configured to 50, a gateway will only collect and send 50 API response information per second, and the consumption of gateway performance is almost negligible. In addition, each API will only be collected once within 1800 seconds, 1800*50=90000, that is, each gateway can collect 90,000 different API response information within 1800 seconds, which can completely cover all APIs on the gateway. Therefore, the response information of all APIs can be collected comprehensively and without omissions, and the performance consumption of the gateway is extremely low. The response information of the API is collected comprehensively and without omissions, which is sufficient to meet the needs of subsequent security analysis, big data analysis, etc.

[0166] In the disclosed embodiment, the collection instruction represents a sampling strategy for sampling the running results of the application program. The collection strategy can be formulated through the aforementioned t1 parameter and q1 parameter, wherein the q1 parameter is the maximum number of API response messages allowed to be sent by a gateway node per second. This parameter limits the number of API response messages sent by the gateway, and is used to limit gateway performance consumption; the t1 parameter is the time for caching a certain API in the API deduplication device, which controls the gateway to send a certain API only once within the t1 time, and thus the number of response messages of different APIs that a gateway can send is t1*q1.

[0167] In the disclosed embodiment, a repeater is embedded in a gateway device, and the collection device and the gateway device are separately provided, so that the calculation of the collection strategy and the implementation of the collection process can be assigned to different device operations to achieve decoupling, so that the repeater of the gateway device only needs to focus on the collection and forwarding of the operation results, while the collection device is responsible for determining the collection strategy (generating collection instructions). On the one hand, it is beneficial to reduce the performance consumption of a single device (collection device or gateway device) when collecting large amounts of data; on the other hand, the collection device also generates collection instructions (formulates collection strategies) based on the interface identifiers of each application and the gateway identifier of the gateway device to guide the repeater to collect and forward the operation results from other devices through the gateway device, thereby improving the purposefulness and efficiency of information collection, and facilitating the collection device to collect more information based on different gateway devices, thereby improving the accuracy of the system that subsequently uses the collected information for related analysis (for example, it can improve the accuracy of big data analysis and risk analysis).

[0168] Figure 6 is a diagram of an information collection device applied to a collection device in an embodiment of the present disclosure. Figure 6 , the information collection device 600 includes:

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

[0170] A first generating module 602 is used to generate a collection instruction for collecting the running results of the application programs based on the interface identifiers of the application programs 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 result of the application program forwarded by the gateway device based on the collection instruction.

[0172] In some embodiments, the first generation module 602 is also used to determine the number of historical collections of running results of the target application identified by the interface identifier by the gateway device 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 number of historical collections of the target application by the gateway device and the collection frequency of the gateway device.

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

[0174] In some embodiments, the first generating module 602 is further configured to generate an instruction indicating not to collect the running result of the target application in response to the collection frequency of the gateway device being greater than the preset frequency threshold, or the historical collection quantity of the target application by the gateway device being greater than the preset quantity threshold;

[0175] An instruction indicating not to collect the running result of the target application is sent to the gateway device.

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

[0177] Figure 7 is a diagram of an information collection device applied to a gateway device in an embodiment of the present disclosure. Figure 7 , the information collection device 700 includes:

[0178] The first sending module 701 is used to send identification information to the collection device; wherein the identification information includes: the interface identification of each application associated with the gateway device and the gateway identification 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 program; wherein the collection instruction is generated by the collection device based on the interface identifier of each application program and the gateway identifier of the gateway device;

[0180] The first forwarding module 703 is used to forward the running result of the application program to the collection device based on the collection instruction.

[0181] In some embodiments, the apparatus is further configured to receive an instruction sent by the collection device indicating that the running result of the application program is not to be collected;

[0182] According to the instruction, the running result of the application is not forwarded to the collection device.

[0183] In some embodiments, the first forwarding module 703 is further configured to forward the operation result to the collection 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 operations in the device in the illustrated embodiment has been described in detail in the embodiment of the method, and will not be elaborated on here.

[0185] Figure 8 8 is a block diagram of an electronic device 800 according to an exemplary embodiment. For example, the 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 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] The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0188] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc. The 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 memory, flash memory, magnetic disk or optical disk.

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

[0190] The 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 touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0191] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the 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 button, volume button, start button, and lock button.

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

[0194] The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as Wi-Fi, 4G or 5G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can 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 above method.

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

[0197] A non-temporary computer-readable storage medium, when the instructions in the storage medium are executed by a processor of a collection device or a gateway device, enables the collection device or the gateway device to execute the aforementioned information collection method.

[0198] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the claims above.

[0199] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. An information collection method, characterized in that: Applied to a collection device, the method comprises: Receiving identification information sent by a gateway device; wherein the identification information includes: interface identifications of each application associated with the gateway device and a gateway identification of the gateway device; Based on the interface identifier of each application and the gateway identifier of the gateway device, generating a collection instruction for collecting the running results of the application, and sending the collection instruction to the gateway device; Receive the running result of the application program forwarded by the gateway device based on the collection instruction.

2. The method according to claim 1, characterized in that The generating of a collection instruction for collecting the running results of the application programs based on the interface identifiers of the application programs and the gateway identifier of the gateway device includes: Determine the number of historical collections of the running results of the target application identified by the interface identifier by the gateway device within a preset time period; Determine the frequency of collecting operation results by the gateway device indicated by the gateway identifier; A collection instruction for collecting the running result of the target application is generated according to the historical collection quantity of the target application by the gateway device and the collection frequency of the gateway device.

3. The method according to claim 2, characterized in that The generating, according to the historical number of collections of the target application by the gateway device and the collection frequency of the gateway device, a collection instruction for collecting the running result of the target application, comprises: In response to the collection frequency of the gateway device being less than or equal to a preset frequency threshold, and the historical collection quantity of the target application by the gateway device being less than or equal to a preset quantity threshold, a collection instruction is generated to instruct collection of the running result of the target application.

4. The method according to claim 3, characterized in that The method further comprises: In response to the collection frequency of the gateway device being greater than the preset frequency threshold, or the number of historical collections of the target application by the gateway device being greater than the preset number threshold, generating an instruction to instruct not to collect the running result of the target application; An instruction indicating not to collect the running result of the target application is sent to the gateway device.

5. The method according to claim 3, characterized in that: The determining the frequency of collecting the operation results by the gateway device indicated by the gateway identifier includes: In response to the historical collection quantity of the target application by the gateway device being less than or equal to the preset quantity threshold, the collection frequency of the operation result by the gateway device indicated by the gateway identifier is determined.

6. An information collection method, characterized in that: Applied in a gateway device, the method comprises: Sending identification information to the collection device; wherein the identification information includes: the interface identification of each application associated with the gateway device and the gateway identification of the gateway device; Receiving a collection instruction for collecting the running results of the application program sent by the collection device; wherein the collection instruction is generated by the collection device based on the interface identifier of each application program and the gateway identifier of the gateway device; Based on the collection instruction, the running result of the application is forwarded to the collection device.

7. The method according to claim 6, characterized in that The method further comprises: receiving an instruction sent by the collection device indicating that the running result of the application program is not to be collected; According to the instruction, the running result of the application is not forwarded to the collection device.

8. The method according to claim 6, characterized in that The forwarding of the running result of the application to the collection device includes: When the gateway device is in an idle state, the operation result is forwarded to the collection device.

9. An information collection device, characterized in that: Applied to a collection device, the device comprises: A first receiving module, configured to receive identification information sent by a gateway device; wherein the identification information includes: interface identifications of each application associated with the gateway device and a gateway identification of the gateway device; A first generating module, configured to generate a collection instruction for collecting the running results of the application programs based on the interface identifiers of the application programs and the gateway identifier of the gateway device, and send the collection instruction to the gateway device; The second receiving module is used to receive the running result of the application program forwarded by the gateway device based on the collection instruction.

10. An information collection device, characterized in that: Applied to a gateway device, the device comprises: A first sending module, used to send identification information to a collection device; wherein the identification information includes: interface identifications of each application associated with the gateway device and a gateway identification of the gateway device; A third receiving module is used to receive a collection instruction sent by the collection device to collect the running results of the application program; wherein the collection instruction is generated by the collection device based on the interface identifier of each application program and the gateway identifier of the gateway device; The first forwarding module is used to forward the running result of the application program to the collection device based on the collection instruction.

11. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to execute the information collection method as described in any one of claims 1 to 5; or, is configured to execute the information collection method as described in any one of claims 6 to 8.

12. A non-transitory computer-readable storage medium, characterized in that: When the instructions in the storage medium are executed by the processor of the collection device, the collection device is enabled to execute the information collection method as described in any one of claims 1 to 5; or, when the instructions in the storage medium are executed by the processor of the access gateway, the gateway device is enabled to execute the information collection method as described in any one of claims 6 to 8.

Images