Data calling method and apparatus

Abstract

The data calling method and device provided by the embodiments of the present specification, wherein the data calling method comprises: intercepting a data calling request sent by a source end, wherein the data calling request carries calling source information and destination information of a destination end; querying an authentication rule to match the calling source information and the destination information; and if the matching fails, prohibiting the source end from calling data of the destination end. By intercepting the data calling request sent by the source end, the development cost is reduced without designing an interface for the source end and the destination end to perform authentication judgment. By querying the authentication rule and matching the calling source information and the destination information according to the authentication rule, the authentication efficiency is improved, and the data security of the destination end is ensured.

Description

Technical Field

[0001] The embodiments in this specification relate to the field of data application technology, and in particular to a data retrieval method. Background Technology

[0002] With the development of internet technology, massive amounts of data are being widely used in various scenarios. As the amount of data grows, a single data processing terminal can no longer fulfill all applications in various scenarios using only its own data, leading to increasingly frequent data calls between multiple data processing terminals.

[0003] Currently, the main approach is for the source to send a data request to the destination to directly access the data on the destination.

[0004] However, this data retrieval method, because it does not verify the data retrieval permissions of the source end, makes it difficult to guarantee the data security on the destination end. Therefore, there is an urgent need for a data retrieval method that can ensure the data security on the destination end while performing data retrieval. Summary of the Invention

[0005] In view of this, embodiments of this specification provide a data retrieval method. One or more embodiments of this specification also relate to a data retrieval apparatus, a computing device, a computer-readable storage medium, and a computer program, to address the technical deficiencies existing in the prior art.

[0006] According to a first aspect of the embodiments of this specification, a data retrieval method is provided, comprising:

[0007] Intercept data call requests sent from the source end, where the data call request carries the call source information and the destination end information;

[0008] Query the rights confirmation rules and match the source and destination information according to the rights confirmation rules;

[0009] If the match fails, the source end is prohibited from making data calls to the destination end.

[0010] According to a second aspect of the embodiments of this specification, a data retrieval apparatus is provided, comprising:

[0011] The interception module is configured to intercept data call requests sent by the source end, wherein the data call request carries the call source information and the destination end information;

[0012] The matching module is configured to query the rights confirmation rules and match the source and destination information according to the rights confirmation rules.

[0013] The "Disable Calling Module" is configured to prevent the source from making data calls to the destination if a match fails.

[0014] According to a third aspect of the embodiments of this specification, a computing device is provided, comprising:

[0015] Memory and processor;

[0016] The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions. When the computer-executable instructions are executed by the processor, they implement the steps of the above-described data retrieval method.

[0017] According to a fourth aspect of the embodiments of this specification, a computer-readable storage medium is provided that stores computer-executable instructions, which, when executed by a processor, implement the steps of the data retrieval method described above.

[0018] According to a fifth aspect of the embodiments of this specification, a computer program is provided, wherein when the computer program is executed in a computer, it causes the computer to perform the steps of the above-described data retrieval method.

[0019] In one embodiment of this specification, by intercepting data call requests sent by the source end, there is no need to design separate interfaces for authorization judgment on both the source and destination ends, thus reducing development costs. By querying authorization rules and matching the source and destination information according to these rules, if the match fails, the source end is prohibited from calling data from the destination end. Matching the source and destination information only according to the authorization rules improves authorization efficiency while ensuring the data security of the destination end. Attached Figure Description

[0020] Figure 1 This is a flowchart illustrating a data retrieval method provided in one embodiment of this specification;

[0021] Figure 2 This is a flowchart illustrating the processing procedure of a data retrieval method provided in one embodiment of this specification;

[0022] Figure 3 This is a schematic diagram of a module for data retrieval between two applications in a data retrieval method provided in one embodiment of this specification;

[0023] Figure 4 This is a system architecture diagram of a data retrieval system provided in one embodiment of this specification;

[0024] Figure 5 This is a flowchart illustrating a data retrieval method provided in one embodiment of this specification;

[0025] Figure 6 This is a schematic diagram of the structure of a data retrieval device provided in one embodiment of this specification;

[0026] Figure 7 This is a structural block diagram of a computing device provided in one embodiment of this specification. Detailed Implementation

[0027] Many specific details are set forth in the following description to provide a full understanding of this specification. However, this specification can be implemented in many other ways than those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this specification. Therefore, this specification is not limited to the specific implementations disclosed below.

[0028] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of this specification. The singular forms “a,” “described,” and “the” as used in one or more embodiments of this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in one or more embodiments of this specification refers to and includes any or all possible combinations of one or more associated listed items.

[0029] It should be understood that although the terms first, second, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first may also be referred to as second without departing from the scope of one or more embodiments of this specification, and similarly, second may also be referred to as first. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0030] First, the terms and concepts used in one or more embodiments of this specification will be explained.

[0031] Host system: A system that runs on a physical computer and provides access management for computer resources.

[0032] Confirmation of rights: Determining whether the source of the data request has the right to use the data in accordance with regulations.

[0033] Generalized invocation: The data caller can directly invoke the data without going through the application interface.

[0034] Remote Procedure Call (RPC): A communication method between multiple tasks and applications.

[0035] Currently, the method for determining the ownership of data from the source end to the destination end involves detecting whether there are non-compliant fields in the data being called during the data call process. This calling method can lead to data leakage at the destination end and cause data security issues because the source end has already received part of the called data.

[0036] To address the data security risks associated with the aforementioned calling methods, this specification provides a data calling method. This specification also relates to a data calling device, a computing device, and a computer-readable storage medium, which will be described in detail in the following embodiments.

[0037] See Figure 1 , Figure 1 A flowchart of a data retrieval method according to an embodiment of this specification is shown, which specifically includes the following steps.

[0038] Step 102: Intercept the data call request sent by the source end, wherein the data call request carries the call source information and the destination end information.

[0039] The data retrieval method provided in the embodiments of this specification is applied to the authorization terminal of the host system.

[0040] The authorization verification end can be a plug-in module located at the source end, or an authorization verification system located between the source and destination ends. Currently, for data calls within the host system, authorization verification requires manually writing corresponding authorization verification code for each program to verify whether programs have permission to call each other's data. This involves a huge amount of code writing and cannot take into account the program code in detail, which can introduce new risks to the program. The embodiments in this specification do not modify the program code, but choose to use a plug-in module or authorization verification system. This avoids a large amount of code writing and program code modification, thereby avoiding the introduction of new risks, saving development costs, and improving the security of the program code.

[0041] The source refers to various programs running on the host system, including applications, plugins, web browsers, compilers, databases, etc. The destination refers to various programs running on the host system that are not source programs, including applications, plugins, web browsers, compilers, databases, etc.

[0042] A data retrieval request is a request instruction sent from the source end to the destination end, requesting to retrieve data on the destination end, carrying the retrieval source information and the destination end information.

[0043] The source information refers to information that can identify the source in the host system. This can be user information on the source, or the source's product code, product name, version number, etc., without any restrictions here. The destination information refers to information that can identify the destination in the host system. This can be the destination's product code, product name, version number, etc., without any restrictions here.

[0044] Generally, the data retrieval process involves the source sending a data retrieval request, and the destination receiving the request and returning the requested data to the source. This data retrieval process between the source and destination can be direct or indirect. For example, the data retrieval process between source A and destination C is indirect. Source A sends a data retrieval request to intermediate B, intermediate B forwards the request to destination C, and destination C, upon receiving the request, indirectly returns the requested data to source A through intermediate B.

[0045] For the indirect calling method described above, the destination information of the destination needs to be pre-configured in the data calling request. This uniquely identifies the destination. Data calling requests containing destination information can accurately identify the destination within the host system, ensuring the accuracy of the calling path and thus the accuracy of the called data.

[0046] Intercepting data call requests sent from the source end involves using aspect-oriented programming (AOP) to identify pre-configured call source information within the request. The main call parameter serves as the basis for determining the legitimacy of the call. By employing bytecode-enhanced AOP to identify and intercept data call requests, real-time monitoring of the data stream is possible, ensuring the security of the called data.

[0047] Specifically, by using aspect-oriented programming, the call source information in the data call request sent by the source end is identified, and the data call request is intercepted.

[0048] By intercepting data call requests sent from the source, a generalized calling environment is provided for subsequent calls. This ensures that there is no need to design separate interfaces for the source and destination to determine rights, thus reducing development costs. The data call request carries the source information and the destination information, providing an information basis for subsequent rights determination.

[0049] Step 104: Query the rights confirmation rules and match the source information and destination information according to the rights confirmation rules.

[0050] The rights confirmation rule is a pre-set rule for whether the source has data access rights. It is a data access rule agreement signed by the source and the destination, which records the source information and the destination information.

[0051] The rules for determining data ownership are based on the project scenario corresponding to the source information. For example, if program A and program B are developed by the same company, and program C is developed by another company, and program A initiates a data call to access data on program B, or program B initiates a data call to access data on program A, then in this project scenario, programs A and B consider each other to have high data security. Conversely, if program C initiates a data call to access data on program A or program B, then in this project scenario, program A or program B considers program C's data security to be relatively low. If such a call is necessary, a rules for determining data ownership must be pre-agreed upon.

[0052] The query for rights confirmation rules can involve calling one or more rights confirmation rules from the rule index center and pre-stored in a cached query table of one or more rights confirmation rules. The query matches the source and destination information with the source and destination information of one or more rights confirmation rules in the query table. Alternatively, the query can involve querying the rule index center in real time based on the source and destination information. If a pre-signed rights confirmation rule is found, the source and destination information are confirmed to have matched successfully. If no pre-signed rights confirmation rule is found, the match between the source and destination information is confirmed to have failed.

[0053] The rule index center is a storage center used to store the rights confirmation rules pre-signed between the destination and multiple source ends. It is an application that stores these records and is deployed on a remote server.

[0054] Specifically, based on the source information and destination information, the pre-signed rights confirmation rules are queried, and the source information and destination information are matched according to the rights confirmation rules.

[0055] By querying the rights confirmation rules and matching the source and destination information according to the rules, a basis is provided for whether the source can successfully call the data on the destination. In addition, the efficiency of rights confirmation is improved by only matching the source and destination information.

[0056] Step 106: If the match fails, the source end is prohibited from making data calls to the destination end.

[0057] Based on the source and destination information, query the rights confirmation rules. If no pre-signed rights confirmation rules are found, it is confirmed that the source and destination information do not match.

[0058] Prohibit the source from making data calls to the destination. That is, adjust the running status of the authentication terminal to the closed state. The authentication terminal will no longer intercept data call requests sent by the source. At the same time, based on the status of the authentication terminal, the destination will stop the data call process.

[0059] Specifically, if the matching fails, the running status of the rights confirmation terminal will be adjusted to the closed state, and the data call process will be stopped.

[0060] In one embodiment of this specification, if a match is found, the source may be allowed to continue making data calls to the destination.

[0061] This embodiment of the specification intercepts data call requests sent by the source end, eliminating the need to design separate interfaces for authorization judgment on both the source and destination ends, thus reducing development costs. By querying authorization rules and matching the source and destination information according to these rules, if the match fails, the source end is prohibited from calling data from the destination end. Matching the source and destination information only according to the authorization rules improves authorization efficiency while ensuring the data security of the destination end.

[0062] Optionally, in one or more embodiments of this specification, after intercepting the data access request sent by the source in step 102, the following specific steps are further included:

[0063] Obtain the interface information for the data call request;

[0064] Identify whether the interface information is the interface information of the preset interface to be monitored;

[0065] Correspondingly, step 104 involves querying the rights confirmation rules and matching the source and destination information based on these rules, including the following specific steps:

[0066] If the interface information is the interface information of the preset interface to be monitored, then query the rights confirmation rules and match the source information and destination information according to the rights confirmation rules.

[0067] The interface information for the data retrieval request is the interface information for sending the data retrieval request instruction from the source end, including the source retrieval information and the destination end information.

[0068] The interfaces to be monitored are pre-defined. Based on the security requirements of different source endpoints, interfaces from those with lower security are selected as the monitored interfaces. These monitored interfaces can be compiled into a table; by querying the list of monitored interfaces, it can be determined whether the data call interface corresponding to the current data call request is in the list.

[0069] If the interface information is the interface information of the preset interface to be monitored, it means that the security of this call is not high. It is necessary to perform a confirmation rule query on this call, match the call source information and the destination information, and determine whether the source has signed the confirmation rule.

[0070] Furthermore, because the host system has a large number of needs to access data from the destination, requiring authorization for every call would place a significant burden on the host system's operation. Selective authorization is necessary. For example, in mobile systems, many applications need to access network address and transmission protocol data from the network connection module. In such cases, monitored call interfaces can be pre-defined. Calls that do not pose security risks can be made directly without authorization, while authorization is required for the few calls that may cause security issues. This ensures data security while maintaining the normal operation of the host system.

[0071] If the security assessment at the source changes, the list of interfaces to be monitored will be updated, making the identification process more flexible.

[0072] Specifically, the interface information for the data call request is obtained, and the call source information in the interface information is checked against the preset monitoring interface list.

[0073] For example, if the interface information for obtaining a data call request is RPC, and the list of interface information for the interface to be monitored is {RPC, Message, Tair cache, database, REST interface, CSS}, and the interface information RPC is identified as the interface information of the preset interface to be monitored {RPC, Message, Tair cache, database, REST interface, CSS}, then the rights confirmation rules are queried to match the call source information and the destination information.

[0074] By obtaining the interface information of the data call request, it is identified whether the interface information is the interface information of the preset interface to be monitored. If the interface information is the interface information of the preset interface to be monitored, authorization is performed. This method not only ensures the normal operation of the host system, but also avoids non-compliant calls as much as possible, thereby improving data security.

[0075] Optionally, in one or more embodiments of this specification, the following specific steps are included before step 104:

[0076] Obtain the project information corresponding to the data retrieval request;

[0077] Based on the project information, determine the target ownership confirmation model.

[0078] Project information refers to the specific scenario of data retrieval, which may include application type, interface type, project type, etc. For example, if the source needs to confirm rights before calling data on the destination, the project information is synchronous; if the source needs to confirm rights synchronously and call data on the destination, the project information is asynchronous; if the source needs to call the data first and then confirm rights, and then audit the call in the future, the project information is audited.

[0079] Based on the project information, the target rights confirmation mode is determined. Specifically, the project information is matched with the project rules in the rights confirmation end to obtain the target project rules, and then the target rights confirmation mode is obtained accordingly.

[0080] The project rules are generated in the privacy platform of the target developer in advance. After the information for different projects is generated, it will be pushed to the rights confirmation end through digital rights management (DRM) technology. These rules include: synchronous project rules, asynchronous project rules, and audit project rules.

[0081] The privacy platform has functions such as project rule generation, application dependency topology, risk monitoring, privacy inspection, and protocol relationship maintenance.

[0082] The target rights confirmation mode is obtained by comparing the project information and project rules retrieved from the data, and then obtaining the corresponding project rules from multiple rights confirmation modes.

[0083] Specifically, based on the specific scenario corresponding to the data call request, the project information corresponding to the data call request is determined, and it is matched with the project rules in the rights confirmation terminal to determine the corresponding rights confirmation mode among the pre-set multiple rights confirmation modes, which is then used as the target rights confirmation mode.

[0084] For example, the specific scenario corresponding to the data retrieval request is "request first, then confirm rights," with subsequent auditing of this retrieval. Based on the audit scenario corresponding to this data retrieval request, the target rights confirmation mode for the data retrieval request is determined to be the audit mode.

[0085] By identifying the specific project for data retrieval and selecting the corresponding rights confirmation mode based on the project information, the rights confirmation process can be adapted to the actual situation of data retrieval, ensuring the flexibility and relevance of data retrieval and rights confirmation.

[0086] Optionally, in one or more embodiments of this specification, obtaining the project information corresponding to the data retrieval request includes the following specific steps:

[0087] Collect system configuration information from the host system;

[0088] Based on the system configuration information, determine the application technology stack corresponding to the system configuration information;

[0089] By leveraging the application technology stack, we can obtain the project information corresponding to the data call request.

[0090] The system configuration information of the host system contains the hardware and software configuration settings for functions such as system access to data, data storage, and system performance testing.

[0091] The application technology stack refers to a series of functional code stacks configured to achieve the purpose of data retrieval. The functional code is arranged in chronological order according to a preset specific scenario, and is executed in chronological order when the corresponding function is executed. Bytecode of project information is pre-injected into the application technology stack at different injection points.

[0092] The system configuration information of the host system can be collected by sending a host system collection command after receiving a data call request, or by sending a host system collection command in advance, obtaining the system configuration information, and then recording it in the rights confirmation terminal.

[0093] After performing injection point analysis on the application technology stack, the project information bytecode is parsed to obtain the project information corresponding to the data call request.

[0094] Specifically, the system configuration information of the host system is collected, the application technology stack corresponding to the system configuration information is determined based on the system configuration information, injection point analysis is performed on the application technology stack, and the bytecode of the project information is parsed to obtain the project information corresponding to the data call request.

[0095] For example, the system configuration information of the host system is collected as {cache address; cache space; CPU utilization ...}. Based on the system configuration information {cache address; cache space; CPU utilization ...}, the corresponding application technology stack {authorization code 1 - database query code 2 - bytecode injection - database call code 3 ...} is determined. After performing injection point analysis on the application technology stack, the bytecode of the project information is parsed to obtain the corresponding project information as synchronization.

[0096] Determining the corresponding application technology stack based on the host system's system configuration information, and then obtaining project information, ensures a better integration of project information and the execution status of the application technology stack. This guarantees that the subsequently selected rights confirmation mode can better adapt to the actual situation of data calls, improving the flexibility and targeting of data calls and rights confirmation.

[0097] Optionally, in one embodiment of this specification, the target rights confirmation mode includes a synchronous rights confirmation mode;

[0098] Correspondingly, step 104 involves querying the rights confirmation rules and matching the source information and destination information according to these rules, including the following specific steps:

[0099] Based on the source and destination information, query one or more authorization rules in the cache;

[0100] If one or more rights confirmation rules are matched, the source information and destination information are matched according to the matched rights confirmation rules.

[0101] The authorization confirmation end allocates a thread for data calls initiated by the source end, and allocates the same thread for querying one or more authorization rules in the cache. On the same thread, authorization rule queries and judgments need to be performed first, and then data calls are made. This same thread configuration protects the data on the destination end from being called before authorization is confirmed, thus ensuring the security of the data on the destination end.

[0102] Specifically, one or more rights confirmation rules are pre-called from the rule index center, and one or more record rights confirmation rule query tables are pre-stored in the cache. If the rights confirmation rule determined based on the source information and destination information is consistent with the rule in the query table, then the source information and destination information are matched.

[0103] For example, multiple rights confirmation rules R1, R2, and R3 are pre-called from the rule index center and stored in the cache to obtain the query table [R1, R2, R3]. The rights confirmation rule is determined to be R1. The rights confirmation rule is queried and matched, and the source information and destination information are matched.

[0104] By pre-storing one or more rights confirmation rules in the cache, instead of having to call and query the rule index center that stores the rules every time a rights confirmation rule is queried, this synchronous rights confirmation mode improves the efficiency of rights confirmation and also improves the overall efficiency of data retrieval.

[0105] Optionally, after checking one or more authorization rules stored in the cache based on the source and destination information, the following specific steps are further included:

[0106] If one or more rights confirmation rules are not matched, a query request is sent to the rule index center, which carries the source and destination information of the caller.

[0107] Receive query results returned by the rule index center, where the query results carry the rights confirmation rules;

[0108] According to the rights confirmation rules, the source information and the destination information are matched.

[0109] The query results returned by the rule index center include record information such as the time information and rule name information of the rights confirmation rules pre-signed at the source.

[0110] Specifically, if one or more rights confirmation rules in the cache are not matched, a query request is sent to the rule index center, the query results returned by the rule index center are received, one or more rights confirmation rules are stored in the query table of rights confirmation rules in the cache, and the source information and destination information are matched.

[0111] Continuing with the example above, the rule for determining the rights is identified as R4. Since multiple rules for determining rights, R1, R2, and R3, are not found in the cache, a query request is sent to the rule index center. The query result R4 returned by the index center is received and stored in the query table [R1, R2, R3, R4] of the rules for determining rights in the cache. The source information and destination information are then matched.

[0112] If one or more rights confirmation rules are not matched, a query request is sent to the rule index center. Based on the query results returned by the rule index center, one or more rights confirmation rules stored in the cache are updated, and then matching is performed again. This ensures that when no rights confirmation rule in the cache is matched, the rights confirmation rule in the rule index center can be queried. This not only improves the completeness of rights confirmation in the synchronous rights confirmation mode, but also improves the efficiency of rights confirmation and the overall efficiency of data retrieval.

[0113] Optionally, after sending the query request to the center, the following specific steps are also included:

[0114] If no query results are received from the rule index center, the source end is prohibited from calling data from the destination end.

[0115] Specifically, after sending a query request to the rule index center, if no query result is received from the rule index center, the running status of the rights confirmation terminal is adjusted to the closed state, and the data call process is stopped.

[0116] Continuing with the example above, after sending a query request to the rule index center for the confirmation of rights rule R4, and not receiving a query result from the rule index center, the running status of the confirmation of rights end is changed to the closed state, and the data call process is stopped.

[0117] If no query results are received, the source end is prohibited from calling data from the destination end. This ensures the data security of the destination end during the synchronous rights confirmation process, improves the integrity of rights confirmation under the synchronous rights confirmation mode, enhances the efficiency of rights confirmation, and also improves the overall efficiency of data calling.

[0118] Optionally, the target rights confirmation mode includes an asynchronous rights confirmation mode;

[0119] Correspondingly, the query and confirmation rules in step 104 match the source information and the destination information, including the following specific steps:

[0120] Allows the source end to access data from the destination end and synchronously query the rights confirmation rules;

[0121] According to the rights confirmation rules, the source information and the destination information are matched.

[0122] The rights confirmation end allocates one thread for data retrieval from the source end to the destination end, and allocates another thread for querying rights confirmation rules, thus performing concurrent processing with two threads.

[0123] In addition, after prohibiting the source from calling data from the destination, a confirmation result log will be printed. This will help developers identify any issues such as confirmation abnormalities or non-compliant data calls that occur during the entire confirmation process.

[0124] Specifically, for a data call request sent from the source end, a thread calls data on the destination end, while another thread synchronously sends a query request to the rule index center. Upon receiving the query results returned by the rule index center, the source information and the destination end information are matched.

[0125] For example, in response to a data call request sent from the source, a thread Thread_1 calls data on the destination, while another thread Thread_2 synchronously sends a query request to the rule index center. Upon receiving the query results returned by the rule index center, the source information and the destination information are matched.

[0126] By asynchronously processing data retrieval and authorization, the source end can quickly retrieve the required data from the destination end, and simultaneously query the authorization rules to make authorization judgments, thereby improving the efficiency of data retrieval. Furthermore, the subsequent authorization judgments can also ensure the security of the data on the destination end.

[0127] Optionally, the target ownership confirmation model includes the audit model;

[0128] Correspondingly, the method further includes the following specific steps:

[0129] Collect statistics on the parameters to be analyzed and record them in the target log.

[0130] Display the target log, which is used for offline rights confirmation.

[0131] The auditing mode is one of calling the data first and then confirming the rights. It allows the source end to call data from the destination end, records the parameters to be analyzed during the data call process, and logs these parameters to the target log. The target log can provide a data reference basis for subsequent offline rights confirmation by developers.

[0132] The parameters to be analyzed are those related to data access anomalies or non-compliant data access during the data access process. For example, 2022.2.28 19:42:38 Data “domain” warning; from B to A. This parameter to be analyzed records that the data “domain” accessed from B to A at 19:42:38 on February 28, 2022, was non-compliant and a warning was issued.

[0133] Displaying the target log refers to showing the target log on the monitoring interface. Specifically, it involves statistically analyzing the parameters to be analyzed during the data call process, recording these parameters in the target log, and then displaying the target log on the monitoring interface.

[0134] For example, the parameters to be analyzed during the statistical data retrieval process:

[0135] 2022.2.2819:42:38Data "domain" warning; from B to A;

[0136] 2022.2.2819:43:50Data "scale" warning; from B to A;

[0137] 2022.2.2819:45:06Data "list_1" warning; from B to A.

[0138] The parameters to be analyzed are recorded to the target log 2022.2.28-Log, and the target log 2022.2.28-Log is displayed on the monitoring interface.

[0139] By prioritizing data retrieval before authorization, data retrieval is given the highest priority. This allows the source end to obtain data from the destination end immediately, and further analysis and confirmation of the parameters to be analyzed in the target log can be performed offline later. This improves the efficiency of data retrieval and provides a parameter basis for subsequent analysis and confirmation of the parameters to be analyzed in the target log.

[0140] Optionally, before intercepting the data request sent by the source in step 102, the following specific steps are also included:

[0141] Monitor operational indicators;

[0142] If the operating indicators exceed the preset threshold, the operating status of the rights confirmation terminal itself will be set to the off state.

[0143] The performance metrics refer to the performance metrics of the host system, including hardware or software metrics on the host system, such as CPU utilization, memory read / write speed, total progress of multiple threads, and progress of a single thread.

[0144] Specifically, the system monitors the host system's operational metrics. If the host system's operational metrics exceed a preset threshold, the system sets the operation status of the verification terminal to a closed state and stops the data call process to the destination terminal.

[0145] For example, if the CPU utilization rate of the host system is 90% and the preset CPU threshold is 85%, and the operating indicators exceed the preset threshold, the operating status of the rights confirmation terminal itself is set to OFF, stopping the process of calling data from the destination terminal.

[0146] Optionally, operational indicators can be monitored periodically, and if the operational indicators exceed the preset threshold multiple times in a row, the operational status of the rights confirmation terminal itself can be set to the off state.

[0147] For example, if the CPU utilization of the host system is monitored every 3 seconds, and the CPU utilization is detected to be 91%, 93%, and 88% three times in a row, exceeding the preset threshold of 85%, the operation status of the rights confirmation terminal itself is set to OFF.

[0148] By monitoring operational metrics and determining whether they exceed preset thresholds, the operation status of the rights confirmation terminal is set to closed if the preset thresholds are exceeded. This avoids the situation where excessive data calls consume too many resources, causing the host system to crash, and ensures the normal operation of the host system.

[0149] The following is in conjunction with the appendix Figure 2 Taking the application of the data retrieval method provided in this specification in inter-application data retrieval within a communication terminal system as an example, the data retrieval method will be further explained. Among other things, Figure 2 The present specification illustrates a data retrieval method according to an embodiment, which includes the following steps.

[0150] Step 202: Collect system configuration information of the host system.

[0151] The host system is a communication terminal system of Ver.12.5. The system configuration information of the host system (Ver.12.5) is collected: {Cache address: 0x00006400; Cache space: 512MB; CPU utilization: 33%...}.

[0152] Step 204: Intercept the data call request sent by the source end, and determine the application technology stack corresponding to the system configuration information based on the system configuration information.

[0153] The source is application A, and the destination is application B. Using aspect-oriented programming, the UID (User Identification) of the call source information (0x101f345A) and the UID of the destination information (0x101f678A) in the data call request sent by application A are identified, and the data call request is intercepted.

[0154] Based on the system configuration information {cache address: 0x00006400; cache space 512MB; CPU utilization 33%...}, the corresponding application technology stack is determined as {authorization code 1 - database query code 2 - bytecode injection - database call code 3...}.

[0155] Step 206: Use the application technology stack to obtain the project information and interface information corresponding to the data call request.

[0156] Get the interface information for the data call request: Access_Data:7200.

[0157] Step 208: If the interface information is the interface information of the preset interface to be monitored, then determine the target rights confirmation mode according to the project information.

[0158] If the target rights confirmation mode is synchronous rights confirmation mode, then execute steps 210 to 216; if the target rights confirmation mode is asynchronous rights confirmation mode, then execute step 218; if the target rights confirmation mode is audit mode, then execute step 220.

[0159] The preset interface information for the interfaces to be monitored is: Access_Data:7000; Access_Data:7200; Access_Data:7600. The interface information Access_Data:7200 is identified as the preset interface to be monitored.

[0160] Step 210: Query one or more authorization rules in the cache based on the source and destination information.

[0161] Determine if one or more rights confirmation rules are matched. If yes, proceed to step 212; otherwise, proceed to step 214.

[0162] Based on the source information UID: 0x101f345A and the destination information UID: 0x101f678A, query the cache for multiple rights confirmation rules R1, R2, and R3.

[0163] Step 212: Match the source information and destination information based on one or more of the matched rights confirmation rules.

[0164] If the match fails, proceed to step 222.

[0165] If the authorization rule is determined to be R2, and an authorization rule is matched, the source information UID: 0x101f345A and the destination information UID: 0x101f678A are matched.

[0166] Step 214: Send a query request to the rule index center, wherein the query request carries the source information and the destination information.

[0167] If the rights confirmation rule is R4 and no rights confirmation rule is matched, then a query request I_1 is sent to the rule index center.

[0168] Step 216: Receive the query results returned by the rule index center, and match the source information and destination information according to the query results.

[0169] If the match fails, proceed to step 222.

[0170] The query results returned by the rule index center show that the signing and confirmation rule was completed on September 1, 2020. Based on the query results, the source information UID: 0x101f345A and the destination information UID: 0x101f678A are matched.

[0171] Step 218: Allow the source end to call data from the destination end, and synchronously query the rights confirmation rules, and match the calling source information and destination end information according to the rights confirmation rules.

[0172] If the match fails, proceed to step 222.

[0173] Based on the project information "asynchronous", the target rights confirmation mode is determined to be asynchronous rights confirmation mode. On one thread Thread_1, application A makes a data call to application B. On another thread Thread_2, a query request I_2 is sent to the rule index center. The query result returned by the rule index center is received: the signing time of the rights confirmation rule is 2020.9.1. Based on the query result, the call source information UID: 0x101f345A and the destination information UID: 0x101f678A are matched.

[0174] Step 220: Statistically analyze the parameters to be analyzed and record them in the target log. Display the target log, which is used for offline rights confirmation.

[0175] Based on the project information "Audit", the target ownership confirmation mode is determined to be the audit mode, and the parameters to be analyzed during the statistical data retrieval process are as follows:

[0176] 2022.2.2819:42:38Data "domain" warning; from B to A;

[0177] 2022.2.2819:43:50Data "scale" warning; from B to A;

[0178] 2022.2.2819:45:06Data "list_1" warning; from B to A.

[0179] The parameters to be analyzed are recorded to the target log 2022.2.28-Log. The target log 2022.2.28-Log is displayed on the monitoring interface.

[0180] Step 222: Prevent the source from making data requests to the destination.

[0181] If the source UID (0x101f345A) and destination UID (0x101f678A) do not match, application A is prohibited from making data calls to application B.

[0182] This embodiment of the specification intercepts data call requests sent by the source end, eliminating the need for specific design of authorization judgment interfaces for the source and destination ends, thus reducing development costs. Based on project information, the corresponding target authorization mode is determined, and then the source and destination information are matched, making the authorization process more flexible. It can be selected according to project information, better meeting the actual requirements of the source end for data call scenarios and improving user experience. If the match fails, the source end is prohibited from calling the destination end, ensuring that if the match fails, the source end is promptly prohibited from calling the destination end, protecting the data security of the destination end.

[0183] The following is in conjunction with the appendix Figure 3 , Figure 3 This diagram illustrates a module diagram of a data retrieval method provided in one embodiment of this specification, showing a data retrieval method for data retrieval between two applications.

[0184] In the diagram, both Application A and Application B are applications in the host system. Application A has a pre-configured authorization terminal. Application A initiates a data call to Application B. Both Application A and Application B contain a calling module and a receiving module. Application A's calling module sends a data call request, and the authorization terminal intercepts the data call request and performs authorization judgment on this data call. If the authorization judgment is passed, Application A is allowed to initiate a remote procedure call to Application B. Application B's receiving module receives the data call request.

[0185] The following is in conjunction with the appendix Figure 4 , Figure 4 A system architecture diagram for data retrieval provided in one embodiment of this specification is shown.

[0186] The privacy platform in the diagram has the following functions: project rule generation, application dependency topology, risk monitoring, privacy inspection, and protocol relationship maintenance. Its foundational dependencies include modules such as the Awatch management console and the DRM push center. The rights confirmation rule parsing includes: global traffic control switch, log sampling frequency configuration, rights confirmation mode, and system health check configuration. Rights confirmation interface types include RPC, message, Tair cache, database, REST (Representational State Transfer), and CSS (Cascading Style Sheets) interfaces. Rights confirmation modes include audit mode, asynchronous rights confirmation mode, and synchronous rights confirmation mode. Data processing methods include ODPS (Open Data Processing Service) and target logs.

[0187] After generating project rules, the privacy platform will push them through the DRM rules and then push them to the rights confirmation end via the DRM push center. The rights confirmation end will process the data call request accordingly, determine whether it is a monitored interface based on the interface type, and then obtain the corresponding rights confirmation mode based on the project rules and project information. When confirming rights synchronously or asynchronously, it first checks whether there are rights confirmation rules in the cache. If not, it queries the rule index center remotely and performs matching after obtaining the returned query results.

[0188] The following is in conjunction with the appendix Figure 5 , Figure 5 This diagram illustrates a data retrieval process in one embodiment of a data retrieval method provided in this specification.

[0189] The first step is to load the rights confirmation client. This involves loading the rights confirmation client into the host application system.

[0190] The second step is to determine whether the data call from the source to the destination is in the monitoring list. Specifically, this involves determining whether the data call request is listed in the monitored categories based on the interface type. If so, proceed to the third step; otherwise, continue the process.

[0191] The third step is to determine the rights confirmation mode. This involves identifying the target rights confirmation mode based on the project data. If it's an asynchronous rights confirmation mode, the call and rights confirmation process continue simultaneously. If it's a synchronous rights confirmation mode, then proceed to the fourth step.

[0192] The fourth step is to query the authorization rules. This involves determining if the authorization rules in the cache are matched. If not, proceed to the fifth step; otherwise, proceed to the sixth step.

[0193] The fifth step is to query remote data. This involves requesting a confirmation rule from the rule index center. Once the confirmation rule is received from the rule index center, it can be updated in the cache. If the index center does not return a confirmation rule, the call terminates, meaning data retrieval is prohibited.

[0194] Step 6: Rule matching. If a match is found, the process continues. If a match is not found, the process terminates and logs are printed.

[0195] Step 7: Prohibit the source from accessing data from the destination.

[0196] Corresponding to the above method embodiments, this specification also provides embodiments of a data retrieval device. Figure 6 A schematic diagram of a data retrieval device according to one embodiment of this specification is shown. Figure 6 As shown, the device includes:

[0197] The interception module 602 is configured to intercept data call requests sent by the source end, wherein the data call request carries call source information and destination end information of the destination end;

[0198] Matching module 604 is configured to query the rights confirmation rules and match the source information and destination information according to the rights confirmation rules;

[0199] The "Disable Calls to Module 606" option is configured to prevent the source from making data calls to the destination if a match fails.

[0200] Optionally, the device further includes:

[0201] The interface information acquisition module is configured to acquire interface information for data call requests;

[0202] The interface information identification module is configured to identify whether the interface information is the interface information of the preset interface to be monitored;

[0203] Correspondingly, the matching module 604 is further configured to query the rights confirmation rules and match the source information and destination information if the interface information is a preset interface information to be monitored.

[0204] Optionally, the device further includes:

[0205] The project information acquisition module is configured to acquire project information corresponding to data call requests;

[0206] The rights confirmation mode determination module is configured to determine the target rights confirmation mode based on project information.

[0207] Optionally, the project information acquisition module is further configured to collect system configuration information of the host system; determine the application technology stack corresponding to the system configuration information based on the system configuration information; and obtain the project information corresponding to the data call request using the application technology stack.

[0208] Optionally, the target rights confirmation mode includes a synchronous rights confirmation mode; the matching module 604 is further configured to query one or more rights confirmation rules in the cache based on the call source information and the destination information; if one or more rights confirmation rules are matched, the call source information and the destination information are matched based on the matched one or more rights confirmation rules.

[0209] Optionally, the matching module 604 is further configured to, if one or more rights confirmation rules are not matched, send a query request to the rule index center, wherein the query request carries the source information and the destination information; receive the query results returned by the rule index center, wherein the query results carry the rights confirmation rules; and match the source information and the destination information according to the rights confirmation rules.

[0210] Optionally, the matching module 604 is also configured to prohibit the source from making data calls to the destination if no query results are received from the rule index center.

[0211] Optionally, the target rights confirmation mode includes an asynchronous rights confirmation mode;

[0212] The matching module 604 is further configured to allow the source end to make data calls to the destination end and simultaneously query the rights confirmation rules; and to match the source information and the destination information according to the rights confirmation rules.

[0213] Optionally, the target ownership confirmation mode includes an audit mode; the device also includes:

[0214] The parameter recording module is configured to collect statistics on the parameters to be analyzed and record them to the target log.

[0215] The log display module is configured to display target logs, which are used for offline rights confirmation.

[0216] Optionally, the device further includes:

[0217] The monitoring module is configured to monitor operational indicators;

[0218] The module will shut down the operation status of the rights confirmation terminal if the operating indicators exceed the preset threshold.

[0219] In one embodiment of this specification, by intercepting data call requests sent by the source end, there is no need to design separate interfaces for authorization judgment on the source and destination ends, thus reducing development costs. By querying the authorization rules and matching the call source information and destination end information according to the authorization rules, if the match fails, the source end is prohibited from calling data from the destination end. Matching the call source information and destination end information only according to the authorization rules improves the efficiency of authorization while ensuring the data security of the destination end.

[0220] The above is an illustrative scheme of a data retrieval device according to this embodiment. It should be noted that the technical solution of this data retrieval device and the technical solution of the data retrieval method described above belong to the same concept. For details not described in detail in the technical solution of the data retrieval device, please refer to the description of the technical solution of the data retrieval method described above.

[0221] Figure 7 A structural block diagram of a computing device according to one embodiment of this specification is shown. The components of the computing device 700 include, but are not limited to, a memory 710 and a processor 720. The processor 720 is connected to the memory 710 via a bus 730, and a database 750 is used to store data.

[0222] The computing device 700 also includes an access device 740, which enables the computing device 700 to communicate via one or more networks 760. Examples of these networks include Public Switched Telephone Network (PSTN), Local Area Network (LAN), Wide Area Network (WAN), Personal Area Network (PAN), or combinations of communication networks such as the Internet. The access device 740 may include one or more of any type of wired or wireless network interface (e.g., Network Interface Controller (NIC)), such as an IEEE 802.11 Wireless Local Area Networks (WLAN) wireless interface, a Wi-MAX (World Interoperability for Microwave Access) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so on.

[0223] In one embodiment of this specification, the above-described components of the computing device 700 and Figure 7 Other components, not shown, can also be connected to each other, for example, via a bus. It should be understood that... Figure 7 The block diagram of the computing device shown is for illustrative purposes only and is not intended to limit the scope of this specification. Those skilled in the art can add or replace other components as needed.

[0224] The computing device 700 can be any type of stationary or mobile computing device, including mobile computers or mobile computing devices (e.g., tablet computers, personal digital assistants, laptop computers, notebook computers, netbooks, etc.), mobile phones (e.g., smartphones), wearable computing devices (e.g., smartwatches, smart glasses, etc.) or other types of mobile devices, or stationary computing devices such as desktop computers or PCs. The computing device 700 can also be a mobile or stationary server.

[0225] The processor 720 is configured to execute the following computer-executable instructions, which, when executed by the processor, implement the steps of the above-described data retrieval method.

[0226] In one embodiment of this specification, by intercepting data call requests sent by the source end, there is no need to design separate interfaces for authorization judgment on the source and destination ends, thus reducing development costs. By querying authorization rules, the source and destination information are matched, which improves the efficiency of authorization judgment. If the match fails, the source end is prohibited from calling data from the destination end, thus ensuring the data security of the destination end.

[0227] The above is an illustrative scheme of a computing device according to this embodiment. It should be noted that the technical solution of this computing device and the technical solution of the data retrieval method described above belong to the same concept. For details not described in detail in the technical solution of the computing device, please refer to the description of the technical solution of the data retrieval method described above.

[0228] An embodiment of this specification also provides a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the data retrieval method described above.

[0229] In one embodiment of this specification, by intercepting data call requests sent by the source end, there is no need to design separate interfaces for authorization judgment on the source and destination ends, thus reducing development costs. By querying authorization rules, the source and destination information are matched, which improves the efficiency of authorization judgment. If the match fails, the source end is prohibited from calling data from the destination end, thus ensuring the data security of the destination end.

[0230] The above is an illustrative scheme of a computer-readable storage medium according to this embodiment. It should be noted that the technical solution of this storage medium and the technical solution of the data retrieval method described above belong to the same concept. For details not described in detail in the technical solution of the storage medium, please refer to the description of the technical solution of the data retrieval method described above.

[0231] An embodiment of this specification also provides a computer program, wherein when the computer program is executed in a computer, it causes the computer to perform the steps of the above-described data retrieval method.

[0232] In one embodiment of this specification, by intercepting data call requests sent by the source end, there is no need to design separate interfaces for authorization judgment on the source and destination ends, thus reducing development costs. By querying authorization rules, the source and destination information are matched, which improves the efficiency of authorization judgment. If the match fails, the source end is prohibited from calling data from the destination end, thus ensuring the data security of the destination end.

[0233] The above is an illustrative scheme of a computer program according to this embodiment. It should be noted that the technical solution of this computer program and the technical solution of the data retrieval method described above belong to the same concept. For details not described in detail in the technical solution of the computer program, please refer to the description of the technical solution of the data retrieval method described above.

[0234] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0235] The computer instructions include computer program code, which may be in the form of source code, object code, executable file, or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium may be appropriately added to or subtracted according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media may not include electrical carrier signals and telecommunication signals.

[0236] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments in this specification are not limited to the described order of actions, because according to the embodiments in this specification, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the embodiments in this specification.

[0237] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0238] The preferred embodiments disclosed above are merely illustrative of this specification. The optional embodiments do not exhaustively describe all details, nor do they limit the invention to the specific implementations described. Clearly, many modifications and variations can be made based on the embodiments described herein. These embodiments are selected and specifically described in this specification to better explain the principles and practical applications of the embodiments, thereby enabling those skilled in the art to better understand and utilize this specification. This specification is limited only by the claims and their full scope and equivalents.

Claims

1. A data calling method applied to an authority end of a host system, comprising: intercepting a data calling request sent by a source end, wherein the data calling request carries calling source information and destination information of a destination end; acquiring project information according to the data calling request, and determining a target authority mode according to the project information, wherein the acquiring project information comprises: collecting system configuration information of the host system, determining an application technology stack corresponding to the system configuration information according to the system configuration information, and obtaining project information corresponding to the data calling request by using the application technology stack, the project information being obtained by performing injection point analysis on the application technology stack and then performing bytecode analysis on the project information, and the bytecode injection of the project information being performed in advance on different injection points in the application technology stack; querying an authority rule according to the target authority mode, and matching the calling source information and the destination information according to the authority rule; if the matching fails, prohibiting the source end from performing data calling on the destination end. 2.The method of claim 1, after the intercepting the data calling request sent by the source end, further comprising: obtaining interface information of the data calling request; identifying whether the interface information is interface information of a preset to-be-monitored interface; the querying the authority rule and the matching the calling source information and the destination information according to the authority rule, comprising: if the interface information is the interface information of the preset to-be-monitored interface, querying the authority rule and matching the calling source information and the destination information according to the authority rule. 3.The method of claim 1, wherein the target authority mode comprises a synchronous authority mode; the querying the authority rule and the matching the calling source information and the destination information according to the authority rule, comprising: querying one or more authority rules in a cache according to the calling source information and the destination information; if the one or more authority rules are hit, matching the calling source information and the destination information according to the one or more authority rules. 4.The method of claim 3, after the querying the one or more authority rules stored in the cache according to the calling source information and the destination information, further comprising: if the one or more authority rules are not hit, sending a query request to a rule index center, wherein the query request carries the calling source information and the destination information; receiving a query result returned by the rule index center, wherein the query result carries an authority rule; matching the calling source information and the destination information according to the authority rule. 5.The method of claim 4, after the sending the query request to the rule index center, further comprising: if the query result returned by the rule index center is not received, prohibiting the source end from performing data calling on the destination end. 6.The method of any one of claims 1, 3-5, wherein the target authority mode comprises an asynchronous authority mode. The query right rule, and matching the calling source information and the destination information according to the right rule, comprising: Allowing the source end to call data to the destination end, and synchronously querying the right rule; According to the right rule, the calling source information and the destination information are matched.

7. The method of claim 1, wherein the target right mode comprises an audit mode; the method further comprises: Statistics to be analyzed parameters, and record the target log to the target log; Display the target log, wherein the target log is used for offline right.

8. The method of claim 1, before the data call request sent by the intercepted source end, further comprising: Monitoring the operation index; In the case where the operation index exceeds the preset threshold, the running state of the right end itself is set to the closed state.

9. A data calling device, comprising: An intercepting module configured to intercept a data calling request sent by a source end, wherein the data calling request carries calling source information and destination information of a destination end; A right mode determining module configured to determine a target right mode according to project information obtained from the data calling request, wherein the project information is obtained by analyzing the injection points of an application technology stack and then parsing the project information bytecode, and the bytecode injection of the project information is performed in advance at different injection points in the application technology stack; A project information obtaining module configured to collect system configuration information of a host system, determine an application technology stack corresponding to the system configuration information according to the system configuration information, and obtain the project information corresponding to the data calling request by using the application technology stack; A matching module configured to query a right rule according to the target right mode, and match the calling source information and the destination information according to the right rule; A calling prohibiting module configured to prohibit the source end from calling data to the destination end if the matching fails.

10. A computing device, comprising: A memory and a processor; The memory is used to store computer executable instructions, and the processor is used to execute the computer executable instructions, which realize the steps of the data calling method of any one of claims 1 to 8 when executed by the processor.

11. A computer readable storage medium storing computer executable instructions, which realize the steps of the data calling method of any one of claims 1 to 8 when executed by the processor.

Images