A privacy-preserving data management method and computing gateway based on a serverless architecture

Abstract

This invention discloses a privacy data management method and computing gateway based on a serverless architecture, relating to the field of computer technology. One specific implementation of the method includes: receiving a service request sent by an upstream computing service application; determining a target lifecycle rule corresponding to the service request based on the identifier of the target computing service application in the service request; routing the service request with the target lifecycle rule added to it to the target computing service application, so that the target computing service application stores the target privacy data from the service request in memory; and controlling the visibility of the target privacy data to the computing logic of the target computing service application when the data in memory satisfies the target lifecycle rule. This implementation controls the visibility of privacy data based on the memory where the privacy data resides, which can reduce performance overhead, avoid key security issues, and has high management efficiency.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a privacy data management method and computing gateway based on a serverless architecture. Background Technology

[0002] In recent years, cloud computing technology has developed rapidly, enabling various applications to provide users with convenient online data services in the cloud. Serverless architecture, as a new paradigm of cloud computing, has significantly reduced development and maintenance costs for application developers while improving the utilization rate of cloud resources for cloud providers, gradually becoming an important technology choice for building online data services. However, while enjoying the convenience brought by these services, users' private data is at risk of leakage. Therefore, how to continuously ensure the security of private data under a serverless architecture has become a crucial issue.

[0003] Existing methods encrypt privacy data based on cryptography, manage the lifecycle of privacy data by managing the visibility of keys, and use secret sharing technology to perform distributed hash storage of keys.

[0004] However, this method requires dynamic encryption and decryption of private data based on cryptography, which incurs significant performance overhead, and key management faces security issues. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a privacy data management method and computing gateway based on a serverless architecture. By controlling the visibility of privacy data based on the memory where the privacy data is located, performance overhead can be reduced, key security issues can be avoided, and management efficiency can be improved.

[0006] In a first aspect, embodiments of the present invention provide a privacy data management method based on a serverless architecture, applied to a computing gateway, comprising:

[0007] Receive service requests sent by upstream computing service applications;

[0008] Based on the identifier of the target computing service application and the target data specification in the service request, the cache of the computing gateway is queried to see if there is a target lifecycle rule corresponding to the service request. If it exists, the service request with the target lifecycle rule is routed to the target computing service application, so that the target computing service application stores the target privacy data in the service request in memory. When the data in memory satisfies the target lifecycle rule, the target privacy data is kept invisible to the computing logic of the target computing service application. Otherwise, based on the identifier of the target computing service application and the target data specification, a query is performed in the metadata management module to obtain the target lifecycle rule corresponding to the service request. The target lifecycle rule, the identifier of the target computing service application, and the target data specification are stored in the cache accordingly, and the service request with the target lifecycle rule is routed to the target computing service application.

[0009] The metadata management module contains lifecycle rules corresponding to the identifiers and data specifications of storage and computing service applications.

[0010] Optionally,

[0011] The target computing service application and the upstream computing service application belong to different cloud service providers.

[0012] Optionally,

[0013] The target lifecycle rules include:

[0014] The data in the privacy data memory page is within a first threshold range, and the data in other memory pages is within a second threshold range; wherein, the privacy data memory page is used to store the target privacy data.

[0015] In a second aspect, embodiments of the present invention provide a computing gateway, comprising:

[0016] The receiving module is configured to receive service requests sent by upstream computing service applications.

[0017] The determination module is configured to query the cache of the computing gateway to see if there is a target lifecycle rule corresponding to the service request, based on the identifier of the target computing service application and the target data specification in the service request. If there is, the request routing module is triggered; otherwise, the metadata management module is queried based on the identifier of the target computing service application and the target data specification to obtain the target lifecycle rule corresponding to the service request. The target lifecycle rule, the identifier of the target computing service application, and the target data specification are stored in the cache accordingly, and the request routing module is triggered.

[0018] The request routing module is configured to route service requests with the target lifecycle rule to the target computing service application, so that the target computing service application stores the target privacy data in the service request in memory, and when the data in memory satisfies the target lifecycle rule, controls the target privacy data to be invisible to the computing logic of the target computing service application.

[0019] Optionally,

[0020] The target computing service application and the upstream computing service application belong to different cloud service providers.

[0021] Optionally,

[0022] The target lifecycle rules include:

[0023] The data in the privacy data memory page is within a first threshold range, and the data in other memory pages is within a second threshold range; wherein, the privacy data memory page is used to store the target privacy data.

[0024] Thirdly, embodiments of the present invention provide an electronic device, including:

[0025] One or more processors;

[0026] Storage device for storing one or more programs.

[0027] When the one or more programs are executed by the one or more processors, the one or more processors implement the serverless data management method as described in any of the above embodiments.

[0028] Fourthly, embodiments of the present invention provide a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the privacy data management method based on a serverless architecture as described in any of the above embodiments.

[0029] One embodiment of the above invention has the following advantages or beneficial effects: Based on the identifier of the target computing service application, a target lifecycle rule for managing privacy data in the target computing service application is determined. The target lifecycle rule controls the visibility of privacy data based on the memory where the privacy data is located, does not depend on the key, can reduce performance overhead, avoid key security issues, and has high management efficiency.

[0030] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0031] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0032] Figure 1 This is a flowchart illustrating a serverless architecture-based privacy data management method applied to a computing gateway, as provided in one embodiment of the present invention.

[0033] Figure 2 This is a schematic diagram illustrating the lifecycle of privacy data according to an embodiment of the present invention;

[0034] Figure 3 This is a flowchart of a privacy data management method based on a serverless architecture for a target computing service application, provided by an embodiment of the present invention.

[0035] Figure 4 This is a flowchart illustrating a serverless privacy data management method applied to a serverless privacy data management system, as provided in an embodiment of the present invention.

[0036] Figure 5 This is a schematic diagram of a computing gateway provided in one embodiment of the present invention;

[0037] Figure 6 This is a schematic diagram of a target computing service application provided in one embodiment of the present invention;

[0038] Figure 7 This is a schematic diagram of a serverless data management system based on an embodiment of the present invention;

[0039] Figure 8 This is a flowchart of a serverless privacy data management method applied to a serverless privacy data management system, provided by another embodiment of the present invention;

[0040] Figure 9 This is a schematic diagram of a serverless data management system according to another embodiment of the present invention;

[0041] Figure 10 This is a schematic diagram of a computing gateway provided in another embodiment of the present invention;

[0042] Figure 11 This is a schematic diagram of a target computing service application provided in another embodiment of the present invention;

[0043] Figure 12 This is a link diagram provided in one embodiment of the present invention;

[0044] Figure 13 This is a schematic diagram of the structure of a computer system suitable for implementing terminal devices or servers of the present invention. Detailed Implementation

[0045] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0046] Existing methods for managing privacy data include the following four:

[0047] Method 1: Based on dynamic taint tracking and rule enforcement

[0048] Design rules for taint propagation and control at the underlying hardware and software (such as processors and virtual machines) where applications run, thereby blocking potential privacy data leaks during computation and controlling the lifecycle of privacy data.

[0049] However, this method requires real-time tracking and judgment at the instruction level, which incurs significant performance overhead and is not suitable for application in real-world scenarios.

[0050] Method 2: Static taint tracking and control code implantation

[0051] By conducting source code analysis on applications, code paths that may lead to privacy leaks during computation are marked and hardened, thereby preventing the leakage of privacy data during actual execution and ultimately controlling the lifecycle of privacy data.

[0052] However, this method requires analysis of the static logic of the program source code, which has high preprocessing overhead, and treating the entire source program as a white box reduces the privacy of the source code assets.

[0053] Method 3: Data Cleaning Based on Hierarchical Software Interfaces

[0054] Data cleanup is performed at each layer of the software stack (virtual machine, container, or operating system, etc.) that hosts the application, targeting critical software layer calls (such as data cleanup and memory reclamation). This type of data cleanup does not assess data privacy, thereby achieving the goal of controlling the data lifecycle.

[0055] However, this method requires modification of the interfaces at each layer of the software stack that handle privacy data, resulting in redundancy. Furthermore, since the interfaces are unaware of the privacy of the data, the accuracy of management will be greatly affected.

[0056] Method 4: Based on cryptographic protocols and key management

[0057] Cryptography is used to encrypt private data, and the lifecycle of private data is managed by managing the visibility of keys. Secret sharing technology is used to store keys in a distributed hash format.

[0058] However, this method requires dynamic encryption and decryption of private data based on cryptography, which incurs significant performance overhead, and key management faces security issues.

[0059] In view of this, such as Figure 1 As shown, this embodiment of the invention provides a privacy data management method based on a serverless architecture, applied to a computing gateway, including:

[0060] Step 101: Receive service requests sent by upstream computing service applications.

[0061] When cloud applications provide services to users, multiple computing service applications typically work together. These applications form a call path, where upstream computing service applications send their computation results (i.e., private data) to downstream computing service applications for further computation. Therefore, downstream computing service applications need to manage the lifecycle of the private data passed in by upstream computing service applications.

[0062] Step 102: Determine the target lifecycle rule corresponding to the service request based on the identifier of the target computing service application in the service request.

[0063] Lifecycle rules corresponding to the identifiers of computing service applications are pre-stored. These lifecycle rules can be stored in the cache or in other storage areas.

[0064] This invention defines the lifecycle of privacy data based on spatial characteristics related to privacy data computation. For example... Figure 2 As shown, given privacy data D and a computing service application S that uses that privacy data, Figure 2 In the computational service S, the time axis t corresponds to the computation process of S. When privacy data D is computed to become D*, and subsequent computations of S do not depend on D, privacy data D is considered to have reached the end of its lifecycle. The program segment P in the program space corresponding to D→D* is called the strongly relevant path of privacy data D in the computational service application S. The strongly relevant path is determined by the computational service application provider.

[0065] Computing service application providers register their privacy-related data strongly associated paths with their respective cloud computing providers. Specifically, the computing service application providers submit the registration in the form of program bytecode. The cloud computing providers then profile the memory access behavior of these strongly associated paths, forming lifecycle rules corresponding to the computing service application.

[0066] Considering that a computing service application may correspond to multiple data specifications, the computing service application provider can also submit data specifications corresponding to strongly related paths to the cloud computing provider. The cloud computing provider performs memory access behavior profiling on strongly related paths, forming lifecycle rules corresponding to the computing service application and data specifications. Data specifications include data size, type, etc.

[0067] Step 103: Route the service request with the target lifecycle rule to the target computing service application.

[0068] The target computing service application stores the target privacy data from the service request in memory. When the data in memory meets the target lifecycle rules, the target privacy data is kept invisible to the computing logic of the target computing service application.

[0069] According to the identifier of the target computing service application, the present invention determines the target lifecycle rules for managing privacy data in the target computing service application. The target lifecycle rules control the visibility of privacy data based on the memory where the privacy data is located, do not rely on keys, can reduce performance overhead, avoid key security issues, and have high management efficiency.

[0070] Furthermore, the lifecycle management rules proposed in this embodiment only require calculating the underlying code (such as bytecode) of the service-provided segments related to privacy data, resulting in high overall efficiency and a small security exposure. The space-based lifecycle management rules have fewer judgment metrics during implementation, and coupled with the hardware-based privacy data visibility control method, the overall efficiency is also high.

[0071] In one embodiment of the present invention, the target lifecycle rule corresponding to the service request is determined based on the identifier of the target computing service application in the service request, including:

[0072] Based on the identifier of the target computing service application and the target data specifications in the service request, a query is performed in the metadata management module to obtain the target lifecycle rules corresponding to the service request;

[0073] The lifecycle rules corresponding to the identifiers and data specifications of storage and computing service applications in the metadata management module.

[0074] In this embodiment of the invention, the lifecycle rules are stored through the metadata management module, which provides more storage space and reduces the resource consumption of the computing gateway compared to the cache of the computing gateway.

[0075] In one embodiment of the present invention, before querying the metadata management module based on the identifier of the target computation service application and the target data specifications in the service request, the method further includes:

[0076] Based on the identifier of the target computing service application and the target data specifications, query whether there is a target lifecycle rule in the cache of the computing gateway. If it exists, the service request with the target lifecycle rule will be routed to the target computing service application. Otherwise, the metadata management module will be queried based on the identifier of the target computing service application and the target data specifications in the service request.

[0077] After obtaining the target lifecycle rule corresponding to the service request, the following further applies:

[0078] Store the target lifecycle rules, the identifier of the target computing service application, and the target data specifications in the cache.

[0079] Through the embodiments of the present invention, lifecycle rules used during the calculation process can be stored in the cache of the computing gateway, thereby improving the management efficiency of privacy data.

[0080] In one embodiment of the present invention, the method further includes:

[0081] If the service request includes target data specifications, then the metadata management module will perform a query based on the identifier of the target computation service application and the target data specifications in the service request; otherwise, the current process will be terminated.

[0082] This invention determines whether to initiate lifecycle management of privacy data in computing service applications based on data specifications. If the security requirements for privacy data are high, data specifications can be added to the service request to trigger lifecycle management; if the security requirements for privacy data are low, lifecycle management can be omitted. Therefore, embodiments of this invention can be applied to different business scenarios.

[0083] like Figure 3 As shown, this embodiment of the invention provides a privacy data management method based on a serverless architecture, applied to a target computing service application, including:

[0084] Step 301: Receive the service request sent by the computing gateway.

[0085] Step 302: Store the target privacy data from the service request in memory.

[0086] Step 303: Obtain the data from memory.

[0087] The data in memory can be read / write data, capacity data, etc. For example, the number of times the computing logic reads private data from memory.

[0088] Step 304: Determine whether the data in memory meets the target lifecycle rules in the service request. If it does, proceed to step 305; otherwise, proceed to step 303 after a certain period of time.

[0089] The target computing service application can retrieve data from memory at preset intervals to determine whether lifecycle management of privacy data is required.

[0090] Step 305: Control the target privacy data to be invisible to the computing logic of the target computing service application.

[0091] The target lifecycle rule is determined by the computing gateway based on the identifier of the target computing service application in the service request sent by the upstream computing service application. Once the computing logic becomes invisible, it can no longer access private data, thus preventing the misuse of private data.

[0092] The embodiments of the present invention control the visibility of privacy data based on the memory where the privacy data is located, without relying on keys, which can reduce performance overhead, avoid key security issues, and have high management efficiency.

[0093] In this embodiment of the invention, storing the target privacy data from the service request in memory includes:

[0094] Store the target privacy data in the service request into a privacy data memory page;

[0095] Retrieve data from memory, including:

[0096] Obtain data from private memory pages and other memory pages;

[0097] Target lifecycle rules, including:

[0098] The data in the privacy data memory page is within the first threshold range, and the data in other memory pages is within the second threshold range.

[0099] This invention stores privacy data separately from other data. Privacy data is stored in editable privacy data memory pages, while other data generated by computing service applications can be stored in other memory pages. The privacy data memory pages can be implemented based on the memory page isolation function provided by the chip. Compared to storing data in the same memory, the memory isolation method used in this invention improves management efficiency and accuracy. Furthermore, this invention considers not only the data in the privacy data memory pages but also the data in other memory pages, thus improving management precision.

[0100] In one embodiment of the present invention, the data in memory includes any one or more of the following:

[0101] The calculation logic counts the number of reads and / or read capacity of the privacy data memory page, the number of writes and / or write capacity of other memory pages, and the number of writes and / or write capacity of other memory pages after each access to the privacy data memory page.

[0102] For example, the data in memory is the number of times the computing logic reads the privacy data memory page, and the lifecycle rule is that the number of times the computing logic reads the privacy data memory page is greater than 10.

[0103] In one embodiment of the present invention, the method further includes:

[0104] The calculation results are obtained based on the target privacy data;

[0105] The computing gateway sends a target service request to the downstream computing service application; the target service request includes the computing result and the identifier of the downstream computing service application.

[0106] In this embodiment of the invention, downstream computing service applications can automatically enable lifecycle management of privacy data, or they can enable it through other identifiers such as data specifications carried in the target service request. For example, the target computing service application can add target data specifications to the target service request. This embodiment of the invention can determine whether to initiate lifecycle management of privacy data based on business needs.

[0107] In one embodiment of the present invention, the service request further includes: an identifier of the target privacy data;

[0108] The method also includes:

[0109] Based on the identifier of the target privacy data, the identifiers of multiple computing service applications corresponding to the identifier of the target privacy data, the lifecycle rules corresponding to the identifiers of the computing service applications, and the determination results obtained from the lifecycle rules, a call path link diagram is generated.

[0110] Among them, multiple computing service applications are on the call path.

[0111] Given that the call path may involve multiple computing service applications, this embodiment of the invention displays information such as the identifier of privacy data in the link diagram. Through the link diagram, users can more directly view the lifecycle management results of the computing service applications in each call path. The lifecycle management result, as described above, indicates whether the data in memory meets the lifecycle rules. Users can use the link diagram to check whether each computing service application is illegally using privacy data, further improving the security of privacy data.

[0112] In this embodiment of the invention, the target computing service application and the upstream computing service application belong to different cloud service providers.

[0113] This invention applies to privacy data protection in cross-domain scenarios. It should be noted that the computing service applications in the call path can correspond to the same cloud computing provider, meaning the computing service applications run in the same cloud, or they can correspond to different cloud computing providers, meaning the computing service applications run in different clouds, allowing for cross-domain interaction.

[0114] like Figure 4 As shown, this embodiment of the invention provides a privacy data management method based on a serverless architecture, applied to a privacy data management system based on a serverless architecture, including:

[0115] Step 401: The computing gateway receives a service request sent by the upstream computing service application.

[0116] Step 402: Determine the target lifecycle rule corresponding to the service request based on the identifier of the target computing service application in the service request.

[0117] Step 403: Route the service request with the added target lifecycle rule to the target computing service application.

[0118] Step 404: The target computing service application stores the target privacy data from the service request into memory.

[0119] Step 405: Obtain the data from memory.

[0120] Step 406: Determine whether the data in memory satisfies the target lifecycle rules in the service request. If it does, control the target privacy data to be invisible to the computing logic of the target computing service application. Otherwise, proceed to step 405.

[0121] The descriptions of the computing gateway and the target computing service application are given in the above embodiments, and will not be repeated in the following embodiments. In this embodiment of the invention, the computing gateway determines the rules adopted by the target computing service application for managing privacy data based on the identifier of the target computing service application, thereby enabling the target computing service application to control the visibility of privacy data based on the memory where the privacy data resides, thus improving the efficiency of privacy data management.

[0122] like Figure 5 As shown, an embodiment of the present invention provides a computing gateway, including:

[0123] The receiving module 501 is configured to receive service requests sent by upstream computing service applications.

[0124] The determination module 502 is configured to determine the target lifecycle rule corresponding to the service request based on the identifier of the target computing service application in the service request;

[0125] The request routing module 503 is configured to route service requests with added target lifecycle rules to the target computing service application, so that the target computing service application stores the target privacy data in the service request in memory. When the data in memory meets the target lifecycle rules, the target privacy data is controlled to be invisible to the computing logic of the target computing service application.

[0126] In one embodiment of the present invention, the determining module 502 is configured to query the metadata management module according to the identifier of the target computing service application and the target data specifications in the service request to obtain the target lifecycle rules corresponding to the service request; the metadata management module stores the lifecycle rules corresponding to the identifier and data specifications of the computing service application.

[0127] In one embodiment of the present invention, the determining module 502 is configured to query whether a target lifecycle rule exists in the cache of the computing gateway based on the identifier of the target computing service application and the target data specification. If it exists, the request routing module 503 is triggered to route the service request with the added target lifecycle rule to the target computing service application. Otherwise, the module performs a query in the metadata management module based on the identifier of the target computing service application and the target data specification in the service request; and stores the target lifecycle rule, the identifier of the target computing service application, and the target data specification in the cache accordingly.

[0128] In one embodiment of the present invention, the determining module 502 is configured to perform a query in the metadata management module based on the identifier of the target computing service application and the target data specification in the service request if the service request includes the target data specification; otherwise, the current process is terminated.

[0129] like Figure 6 As shown, this embodiment of the invention provides a target computing service application, including: a request processor 601, a service instance 602, and a policy executor 603; the service instance includes: computing logic 6021 and a language interpreter 6022;

[0130] Request processor 601 is configured to receive service requests sent by the computing gateway and store the target privacy data in the service request in memory;

[0131] The language interpreter 6022 is configured to acquire memory data based on its built-in read / write monitoring module;

[0132] The policy executor 603 is configured to determine whether the data in memory satisfies the target lifecycle rule in the service request. If it does, it controls the target privacy data to be invisible to the computation logic 6021.

[0133] Among them, the target lifecycle rule is determined by the computing gateway based on the identifier of the target computing service application in the service request sent by the upstream computing service application.

[0134] In one embodiment of the present invention, a request processor 601 is configured to store target privacy data in a service request into a privacy data memory page;

[0135] The language interpreter 6022 is configured to acquire data from privacy data memory pages and other memory pages based on the built-in read / write monitoring module;

[0136] Target lifecycle rules, including:

[0137] The data in the privacy data memory page is within the first threshold range, and the data in other memory pages is within the second threshold range.

[0138] In one embodiment of the present invention, the data in memory includes any one or more of the following:

[0139] The calculation logic counts the number of reads and / or read capacity of the privacy data memory page, the number of writes and / or write capacity of other memory pages, and the number of writes and / or write capacity of other memory pages after each access to the privacy data memory page.

[0140] In one embodiment of the present invention, computing logic 6021 is configured to obtain computing results based on target privacy data; request processor 601 is configured to send a target service request to a downstream computing service application through a computing gateway; the target service request includes: the computing result and the identifier of the downstream computing service application.

[0141] In one embodiment of the present invention, the service request further includes: an identifier of the target privacy data;

[0142] The target computing service application also includes: an audit module;

[0143] The auditing module is configured to generate a call path chain diagram based on the identifier of the target privacy data, the identifiers of multiple computing service applications corresponding to the identifier of the target privacy data, the lifecycle rules corresponding to the identifiers of the computing service applications, and the determination results obtained from the lifecycle rules.

[0144] Among them, multiple computing service applications are on the call path.

[0145] In practical applications, the audit module can be located in each computing service application, and multiple computing service applications can share a single audit module.

[0146] In one embodiment of the present invention, the target computing service application and the upstream computing service application belong to different cloud service providers.

[0147] like Figure 7 This invention provides a privacy data management system based on a serverless architecture, including: a computing gateway 701 and a target computing service application 702;

[0148] Computing gateway 701 is used to receive service requests sent by upstream computing service applications; determine the target lifecycle rule corresponding to the service request based on the identifier of the target computing service application in the service request; and route the service request with the target lifecycle rule to the target computing service application 702.

[0149] The target computing service application 702 is used to store the target privacy data in the service request into memory; retrieve the data in memory; determine whether the data in memory satisfies the target lifecycle rules in the service request; if so, control the target privacy data to be invisible to the computing logic of the target computing service application.

[0150] It should be noted that a privacy data management system may include multiple computing gateways and computing service applications.

[0151] like Figure 8 As shown, this embodiment of the invention provides a privacy data management method based on a serverless architecture, including:

[0152] Step 801: The computing gateway receives a service request sent by the upstream computing service application.

[0153] The service request includes: target privacy data, the identifier of the target privacy data, the identifier of the target computing service, and the target data specifications.

[0154] The embodiments of the present invention are based on Figure 9 The following example illustrates a serverless privacy data management system, which includes a metadata management module, two computing gateways, and four computing service applications. Figure 9 The computing service (hereinafter referred to as the computing service) and the audit module (i.e. Figure 9 The system includes end-to-end lifecycle auditing, where the computing gateway and computing service applications are part of the underlying infrastructure. It should be noted that the metadata management module can be an external module; that is, the system only includes the computing gateway, computing service applications, and the audit module. The audit module can be an embedded module within the computing service applications or a standalone module.

[0155] In this embodiment of the invention, the computing service is completed collaboratively by four computing service applications. Computing service applications 1 and 2 are located on the cloud provided by cloud service provider 1, and computing service applications 3 and 4 are located on the cloud provided by cloud service provider 2. Computing service application 1 is the entry computing service application (referred to as the entry service), and the computing service application is deployed in a runtime environment. It should be noted that the runtime environment is a virtual machine, and the computing service application can also run in other virtual machines or containers.

[0156] The metadata management module contains lifecycle rules corresponding to the identifiers and data rules of storage and computing service applications. For example... Figure 9 As shown, computing service application 1 has three data specifications: spec1, spec2, and spec3. Each of these three data specifications corresponds to a lifecycle rule, namely rule1, rule2, and rule3.

[0157] For example, a computing service application for image processing allows data specifications including: Specification 1: JPEG, 20kB-50kB; Specification 2: PNG, 50kB-80kB. The metadata management module stores the lifecycle rules corresponding to Specification 1 and Specification 2, respectively.

[0158] The computing service application in this embodiment of the invention is an in-memory online computing application. Based on the quantification of memory access behavior in strongly correlated paths, lifecycle rules for privacy data are formulated. The lifecycle rules support several semantic categories as shown in Table 1. That is, the data in memory includes: the number of reads and read capacity of the privacy data memory page by the computing logic, the number of writes and write capacity of the computing logic to other memory pages, and the number of writes and write capacity of the computing logic to other memory pages after each access to the privacy data memory page.

[0159] Table 1. Forms and Explanations of Lifecycle Management Rules

[0160]

[0161]

[0162] Step 802: When the service request contains a target data specification, the computing gateway queries the cache of the computing gateway to see if there is a target lifecycle rule based on the identifier of the target computing service application and the target data specification. If there is a target lifecycle rule in the cache, proceed to step 804; otherwise, proceed to step 803.

[0163] Step 803: The computing gateway queries the metadata management module based on the identifier of the target computing service application and the target data specifications in the service request to obtain the target lifecycle rule corresponding to the service request, and stores the target lifecycle rule, the identifier of the target computing service application, and the target data specifications in the cache.

[0164] like Figure 10 As shown, srv m Used to characterize upstream computing service applications ( Figure 10 Upstream computing services (abbreviated as srv) n Used to characterize downstream computing service applications ( Figure 10 Downstream computing services (abbreviated as downstream computing services), computing gateway (i.e. Figure 10 The cache of the computing gateway (without a service) stores hot rules, i.e., used lifecycle management rules. The privacy data lifecycle rule base is located in the metadata management module, and the rule base stores non-hot rules. The lifecycle rules stored in the rule base can also correspond to the privacy data identifier and data specification, and are not limited to the storage methods mentioned above. Similarly, the lifecycle rules in the cache can also correspond to the privacy data identifier and the identifier of the computing service application.

[0165] The identifier for privacy data is generated by the entry service, such as... Figure 9 As shown, Computing Service Application 1 acts as the entry service, generating corresponding identifiers for privacy data. Computing Service Application 1 then sends the obtained computation results to Computing Service Application 2 via the computing gateway. These results then serve as the privacy data that Computing Service Application 2 needs to manage. The identifiers for privacy data flow with service requests; that is, computing service applications within the same call path have the same identifiers for their privacy data.

[0166] Step 804: The compute gateway routes service requests with added target lifecycle rules to the target compute service application.

[0167] Step 805: The request processor receives the service request sent by the computing gateway and stores the target privacy data in the service request into the privacy data memory page.

[0168] Step 806: The language interpreter obtains data from the privacy data memory page and other memory pages based on the built-in read / write monitoring module.

[0169] Step 807: The policy executor determines whether the data in memory meets the target lifecycle rules in the service request. If it does, proceed to step 808; otherwise, proceed to step 806 after a preset time interval.

[0170] Step 808: Control the target privacy data to be invisible to the computing logic of the target computing service application.

[0171] like Figure 11 As shown, the request processor receives a computing service request (i.e., a service request), stores the target privacy data from the service request into a privacy data memory page, and loads the target lifecycle management rules into the policy executor. Memory pages with editable access permissions are called privacy memory pages, while ordinary memory pages are called other memory pages. The read / write monitoring module can monitor the data in the privacy memory page and other memory pages. The policy executor can obtain memory data from the read / write monitoring module and compare the memory data with the corresponding thresholds in the target lifecycle rules to determine whether the privacy data's lifecycle has terminated. If terminated, access to the privacy data is disabled, i.e., the privacy data is made invisible to the computing logic. The computing service application runs in a runtime environment.

[0172] Specifically, it can be done through Figure 11 The switch between the computational logic and the privacy memory page is controlled. If explicit data request is enabled, the privacy data is visible to the computational logic; otherwise, it is not visible to the computational logic. Figure 11 The privacy data storage abstraction in the module provides the entry point for computational logic to access privacy data. Computational logic can access privacy data through the interfaces shown in Table 2. The read / write monitoring module can obtain data in memory by monitoring read / write commands. Table 3 shows the relevant commands in the Python language interpreter. The read / write monitoring module can also record computation failures or situations where lifecycle management rules are not met, facilitating subsequent auditing and analysis of the computing service by users.

[0173] The policy executor and service instances reside in different process spaces, which can prevent malicious computing service intrusion.

[0174] Table 2. Interface Calls and Their Functions

[0175] Calling the interface Function Authorize(private_data) Data usage request QuotaQuery(private_data) Remaining quota inquiry

[0176] Table 3 Memory Read / Write Instructions

[0177]

[0178] Step 809: The calculation logic obtains the calculation result based on the target privacy data.

[0179] In the process of obtaining calculation results, the computation logic may access privacy data multiple times. This embodiment of the invention prevents privacy data from being misused in this process through lifecycle management rules.

[0180] Step 810: The request processor sends a target service request to the downstream computing service application through the computing gateway; the target service request includes: the computing result and the identifier of the downstream computing service application.

[0181] Step 811: The audit module generates a call path link diagram based on the identifier of the target privacy data, the identifiers of multiple computing service applications corresponding to the identifier of the target privacy data, the lifecycle rules corresponding to the identifiers of the computing service applications, and the determination results obtained from the lifecycle rules. The display module then displays the link diagram.

[0182] The auditing module can generate a link diagram after a call path is completed, or it can generate a link diagram during the execution of a computing service. Through the link diagram, users can visually view whether any computing service applications are experiencing situations that violate lifecycle management rules. For example... Figure 12 The diagram shown is a link diagram, illustrating two call paths, each corresponding to an identifier for privacy data, namely 0x3ec5 and 0x3ec6. The upper call path includes four computing service applications, and the lower call path includes three. Each computing service application stage displays the lifecycle management rules for managing privacy data. The link diagram also illustrates lifecycle management anomalies.

[0183] This invention combines spatial characteristics to determine the lifecycle rules of privacy data, explicitly decoupling privacy data lifecycle management from computing service applications, and integrating it into the underlying general capabilities provided by cloud computing infrastructure through system design. Through chain-like privacy data lifecycle management, end-to-end security protection is provided for privacy data services, and users can obtain the lifecycle management status of privacy data based on its identifier, greatly improving the interpretability and verifiability of the management process. Computing service applications utilize the memory page isolation features provided by the chip to quickly switch access permissions of computing logic to privacy data, minimizing the impact of the lifecycle management feature on the operation of computing services.

[0184] This invention provides an electronic device, comprising:

[0185] One or more processors;

[0186] Storage device for storing one or more programs.

[0187] When one or more programs are executed by one or more processors, the one or more processors implement the serverless architecture-based privacy data management method as described in any of the above embodiments.

[0188] This invention provides a computer-readable medium storing a computer program that, when executed by a processor, implements a serverless data management method as described in any of the above embodiments.

[0189] The following is for reference. Figure 13It shows a schematic diagram of the structure of a computer system 1300 suitable for implementing a terminal device of the present invention. Figure 13 The terminal device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.

[0190] like Figure 13 As shown, the computer system 1300 includes a central processing unit (CPU) 1301, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 1302 or programs loaded from storage section 1308 into random access memory (RAM) 1303. The RAM 1303 also stores various programs and data required for the operation of the system 1300. The CPU 1301, ROM 1302, and RAM 1303 are interconnected via a bus 1304. An input / output (I / O) interface 1305 is also connected to the bus 1304.

[0191] The following components are connected to I / O interface 1305: an input section 1306 including a keyboard, mouse, etc.; an output section 1307 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card such as a LAN card, modem, etc. The communication section 1309 performs communication processing via a network such as the Internet. A drive 1310 is also connected to I / O interface 1305 as needed. Removable media 1311, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 1310 as needed so that computer programs read from them can be installed into storage section 1308 as needed.

[0192] In particular, according to embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 1309, and / or installed from removable medium 1311. When the computer program is executed by central processing unit (CPU) 1301, it performs the functions defined above in the system of this invention.

[0193] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0194] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0195] The modules described in the embodiments of the present invention can be implemented in software or hardware. The described modules can also be housed in a processor; for example, a processor can be described as including a sending module, an acquisition module, a determining module, and a first processing module. The names of these modules do not necessarily limit the module itself; for example, the sending module can also be described as "a module that sends an image acquisition request to a connected server."

[0196] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A privacy data management method based on a serverless architecture, characterized in that, Applied to computing gateways, including: Receive service requests sent by upstream computing service applications; Based on the identifier of the target computing service application and the target data specification in the service request, the cache of the computing gateway is queried to see if there is a target lifecycle rule corresponding to the service request. If it exists, the service request with the target lifecycle rule is routed to the target computing service application, so that the target computing service application stores the target privacy data in the service request in memory. When the data in memory satisfies the target lifecycle rule, the target privacy data is kept invisible to the computing logic of the target computing service application. Otherwise, based on the identifier of the target computing service application and the target data specification, a query is performed in the metadata management module to obtain the target lifecycle rule corresponding to the service request. The target lifecycle rule, the identifier of the target computing service application, and the target data specification are stored in the cache accordingly, and the service request with the target lifecycle rule is routed to the target computing service application. The metadata management module contains lifecycle rules corresponding to the identifiers and data specifications of storage and computing service applications.

2. The method as described in claim 1, characterized in that, The target computing service application and the upstream computing service application belong to different cloud service providers.

3. The method as described in claim 1, characterized in that, The target lifecycle rules include: The data in the privacy data memory page is within a first threshold range, and the data in other memory pages is within a second threshold range; wherein, the privacy data memory page is used to store the target privacy data.

4. A computing gateway, characterized in that, include: The receiving module is configured to receive service requests sent by upstream computing service applications. The determination module is configured to query the cache of the computing gateway to see if there is a target lifecycle rule corresponding to the service request, based on the identifier of the target computing service application and the target data specification in the service request. If there is, the request routing module is triggered. Otherwise, based on the identifier of the target computing service application and the target data specification, a query is performed in the metadata management module to obtain the target lifecycle rule corresponding to the service request. The target lifecycle rule, the identifier of the target computing service application, and the target data specification are stored in the cache accordingly, triggering the request routing module. The request routing module is configured to route service requests with the target lifecycle rule to the target computing service application, so that the target computing service application stores the target privacy data in the service request in memory, and when the data in memory satisfies the target lifecycle rule, controls the target privacy data to be invisible to the computing logic of the target computing service application.

5. The computing gateway as described in claim 4, characterized in that, The target computing service application and the upstream computing service application belong to different cloud service providers.

6. The computing gateway as described in claim 4, characterized in that, The target lifecycle rules include: The data in the privacy data memory page is within a first threshold range, and the data in other memory pages is within a second threshold range; wherein, the privacy data memory page is used to store the target privacy data.

7. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-3.

8. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-3.

Images