Data processing method and system, fog node

Abstract

The present disclosure relates to a data processing method and system, and a fog node. The data processing method performed by the fog node comprises: detecting whether first data of a user collected by the fog node comprises sensitive data; in a case where the first data comprises sensitive data and a preset subscription condition is met, sending a subscription message about a clearing event of the sensitive data to a cloud node, the subscription message comprising a subscription event identifier, the subscription message corresponding to a subscription timestamp and an identifier of a user to which the sensitive data belongs; receiving a publishing message about the clearing event of the sensitive data from the cloud node, the publishing message comprising a publishing event identifier, an identifier of a user whose sensitive data needs to be cleared, and a publishing timestamp; and in a case where the publishing event identifier is the same as the subscription event identifier, the identifier of the user in the publishing message and the identifier of the user in the subscription message have an intersection, and the subscription timestamp is less than the publishing timestamp, clearing sensitive data collected before the subscription timestamp corresponding to the identifier.

Description

Technical Field

[0001] This disclosure relates to the field of data processing, and in particular to data processing methods and systems, fog nodes, and computer-storable media. Background Technology

[0002] Fog computing introduces a fog layer between the cloud and terminal devices, utilizing devices within this fog layer that are close to the user to provide computing, storage, and communication resources. It features low latency, location awareness, high mobility, and a large number of nodes. Fog computing can provide users with localized information and service applications; however, fog nodes adjacent to end users may collect sensitive data such as user identity, location, and application usage. Fog nodes are widely dispersed, have inconsistent security levels, and may frequently join or leave the fog layer dynamically. Furthermore, the connection between terminals and fog nodes is highly random and temporary. If sensitive data stored in fog nodes is not handled promptly, there is a significant risk of sensitive data leakage. Current research on data protection in fog computing focuses on encryption and access control, and has not yet addressed the issue of proactively cleaning up sensitive data within fog nodes. Summary of the Invention

[0003] To address the aforementioned technical issues, this disclosure proposes a solution that can enhance the security capabilities of fog services and improve user experience.

[0004] According to a first aspect of this disclosure, a data processing method is provided, executed by a fog node, comprising: detecting whether first data collected by the fog node from a user includes sensitive data; if the first data includes sensitive data and satisfies preset subscription conditions, sending a subscription message for a sensitive data clearing event to a cloud node, the subscription message including a subscription event identifier, the subscription message corresponding to a subscription timestamp and an identifier of the user to whom the sensitive data belongs; receiving a publication message for a sensitive data clearing event from the cloud node, the publication message including a publication event identifier, an identifier of the user whose sensitive data needs to be cleared, and a publication timestamp; if the publication event identifier is the same as the subscription event identifier, the identifier of the user in the publication message intersects with the identifier of the user in the subscription message, and the subscription timestamp is less than the publication timestamp, clearing the sensitive data collected before the subscription timestamp corresponding to the identifier.

[0005] In some embodiments, clearing sensitive data collected before the subscription timestamp corresponding to the identifier includes: querying the sensitive data of the user corresponding to the identifier from the fog node according to the identifier; obtaining sensitive data whose collection timestamp is less than the subscription timestamp according to the collection timestamp of the sensitive data, as target sensitive data, wherein the collection timestamp represents the time when the sensitive data was collected by the fog node; and clearing the target sensitive data.

[0006] In some embodiments, the first data is collected by the fog node at a first time, the subscription timestamp is the first time, and the data processing method further includes: after sending the subscription message to the cloud node and before receiving the publish message from the cloud node, in response to collecting the second data of the user at a second time, updating the subscription timestamp to a second time, the second time being later than the first time.

[0007] In some embodiments, the preset subscription conditions include at least one of time conditions and behavioral conditions.

[0008] In some embodiments, the time condition includes a subscription time point, a subscription time period, or a subscription time interval.

[0009] In some embodiments, the behavioral condition includes the fog node disconnecting from the user terminal.

[0010] In some embodiments, the data processing method further includes: receiving an identifier of the user to which the first data belongs from the user; or, if it is detected that the first data includes sensitive data, generating an identifier of the user to which the first data belongs and sending the identifier to the user.

[0011] In some embodiments, detecting whether the first data includes sensitive data includes: classifying the first data according to a preset classification strategy to obtain a sensitive dataset and a non-sensitive dataset; and determining that the first data includes sensitive data if the sensitive dataset is not empty.

[0012] In some embodiments, the data processing method further includes: collecting and storing the user's data when providing fog services to the user.

[0013] According to a second aspect of this disclosure, a fog node is provided, comprising: a detection module configured to detect whether first data collected by the fog node from a user includes sensitive data; a sending module configured to send a subscription message about a sensitive data clearing event to a cloud node when the first data includes sensitive data and a preset subscription condition is met, the subscription message including a subscription event identifier, the subscription message corresponding to a subscription timestamp and an identifier of the user to whom the sensitive data belongs; a receiving module configured to receive a publishing message about a sensitive data clearing event from the cloud node, the publishing message including a publishing event identifier, an identifier of the user whose sensitive data needs to be cleared, and a publishing timestamp; and a clearing module configured to clear sensitive data collected before the subscription timestamp corresponding to the identifier when the publishing event identifier is the same as the subscription event identifier, the identifier of the user in the publishing message intersects with the identifier of the user in the subscription message, and the subscription timestamp is less than the publishing timestamp.

[0014] According to a third aspect of this disclosure, a fog node is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute the data processing method described in any of the above embodiments based on instructions stored in the memory.

[0015] According to a fourth aspect of this disclosure, a data processing system is provided, comprising: one or more fog nodes, each fog node being configured to: detect whether first data collected by the fog node from a user includes sensitive data; if the first data includes sensitive data and a preset subscription condition is met, generate and send a subscription message for a sensitive data clearing event, the subscription message including a subscription event identifier, the subscription message corresponding to a subscription timestamp and an identifier of the user to whom the sensitive data belongs; and a cloud node being configured to: parse the subscription message from each fog node to obtain a subscription event identifier corresponding to each fog node; generate a publication message for a sensitive data clearing event, the publication message including a publication event identifier, an identifier of the user whose sensitive data needs to be cleared, and a publication timestamp; and send the publication message to the fog node corresponding to the subscription event identifier that is the same as the publication event identifier; each fog node is further configured to: receive the publication message from the cloud node; and if the publication event identifier is the same as the subscription event identifier, the identifier of the user in the publication message intersects with the identifier of the user in the subscription message, and the subscription timestamp is less than the publication timestamp, clear the sensitive data collected before the subscription timestamp corresponding to the identifier.

[0016] In some embodiments, the cloud node is further configured to: receive a clearing instruction from a user who needs to clear sensitive data, the clearing instruction including an identifier of the user who needs to clear sensitive data; and, in response to receiving the clearing instruction, generate the publishing message based on the identifier of the user who needs to clear sensitive data.

[0017] According to a fifth aspect of this disclosure, a computer-storeable medium is provided that stores computer program instructions thereon, which, when executed by a processor, implement the data processing method described in any of the above embodiments.

[0018] The above embodiments can enhance the security capabilities of fog services and improve user experience. Attached Figure Description

[0019] The accompanying drawings, which form part of this specification, illustrate embodiments of this disclosure and, together with the specification, serve to explain the principles of this disclosure.

[0020] This disclosure will become clearer with reference to the accompanying drawings and the following detailed description.

[0021] in:

[0022] Figure 1 This is a flowchart illustrating a data processing method according to some embodiments of the present disclosure;

[0023] Figure 2 This is a block diagram illustrating fog nodes according to some embodiments of the present disclosure;

[0024] Figure 3 This is a block diagram illustrating fog nodes according to other embodiments of the present disclosure;

[0025] Figure 4 This is a block diagram illustrating a data processing system according to some embodiments of the present disclosure;

[0026] Figure 5 This is a block diagram illustrating a data processing system according to other embodiments of the present disclosure;

[0027] Figure 6 This is a schematic diagram illustrating a data processing method according to some embodiments of the present disclosure.

[0028] Figure 7 This is a block diagram illustrating a computer system for implementing some embodiments of the present disclosure. Detailed Implementation

[0029] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0030] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0031] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0032] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0033] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0034] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0035] Figure 1 This is a flowchart illustrating a data processing method according to some embodiments of the present disclosure.

[0036] like Figure 1 As shown, the data processing method includes steps S1-S4. The data processing method is executed by the fog node.

[0037] In step S1, it is detected whether the first data of the user collected by the fog node includes sensitive data.

[0038] In some embodiments, the first data is classified according to a preset classification strategy to obtain a sensitive dataset and a non-sensitive dataset; if the sensitive dataset is not empty, it is determined that the first data includes sensitive data.

[0039] In some embodiments, when a fog node provides fog services to a user, the user's data is collected and stored. For example, a user uses localized information and service applications provided by fog computing on a fog node adjacent to their terminal device, and that fog node collects and processes the user's data.

[0040] In step S2, if the first data includes sensitive data and preset subscription conditions are met, a subscription message for a sensitive data cleanup event is sent to the cloud node. The subscription message includes a subscription event identifier, which corresponds to a subscription timestamp and the identifier of the user to whom the sensitive data belongs. In some embodiments, the subscription event identifier is the topic of the event.

[0041] In some embodiments, taking the example of the first data being collected by the fog node at a first time and the subscription timestamp being the first time, after sending the subscription message to the cloud node and before receiving the publication message from the cloud node, in response to the collection of the user's second data at a second time, the subscription timestamp is updated to the second time, which is later than the first time.

[0042] In some embodiments, the preset subscription conditions include at least one of time conditions and behavioral conditions. For example, time conditions include a subscription time point, a subscription period, or a subscription interval. Behavioral conditions include the fog node disconnecting from the user terminal.

[0043] In some embodiments, before sending the subscription message to the cloud node, the identifier of the user to which the first data belongs is received from the user to which the first data belongs, or if it is detected that the first data includes sensitive data, the identifier of the user to which the first data belongs is generated and sent to the user.

[0044] In step S3, a publication message regarding the removal of sensitive data is received from the cloud node. The publication message includes a publication event identifier, the identifier of the user whose sensitive data needs to be removed, and a publication timestamp.

[0045] In step S4, if the published event identifier is the same as the subscribed event identifier, the user identifier in the published message overlaps with the user identifier in the subscribed message, and the subscription timestamp is less than the published timestamp, sensitive data collected before the subscription timestamp corresponding to the identifier is cleared. For example, the user identifier in the published message and the user identifier in the subscribed message can be exactly the same or partially the same.

[0046] In the above embodiments, taking into account the non-permanent connection characteristic of cloud nodes and fog nodes in cloud and fog scenarios, a publish-subscribe approach is adopted to achieve sensitive data clearing in cloud and fog scenarios. This effectively reduces the risk of leakage of user sensitive data, further strengthens the security capabilities of fog services, and improves user experience. Furthermore, the cloud nodes publish clearing events, and the fog nodes perform the clearing of sensitive data. A cloud-fog collaboration mechanism is employed. Addressing the heterogeneous and widely distributed nature of fog nodes, user requests are handled by readily accessible cloud components. An attribute-based publish-subscribe model is used to replace the traditional tightly coupled client-server model for transmitting clearing commands, ensuring the lightweight nature of the cloud and offering advantages such as strong adaptability, high efficiency, and scalability.

[0047] In some embodiments, step S4 can be implemented in the following manner.

[0048] First, based on the identifier, query the sensitive data of the user corresponding to the identifier from the fog node.

[0049] Then, based on the collection timestamp of the sensitive data, sensitive data with collection timestamps less than the subscription timestamp are selected as target sensitive data. The collection timestamp represents the time when the sensitive data was collected by the fog node.

[0050] Finally, the target sensitive data is cleared.

[0051] Figure 2 This is a block diagram illustrating a fog node according to some embodiments of the present disclosure.

[0052] like Figure 2 As shown, fog node 21 includes a detection module 211, a sending module 212, a receiving module 213, and a clearing module 214.

[0053] The detection module 211 is configured to detect whether the first data of the user collected by the fog node includes sensitive data, for example, by performing actions such as... Figure 1 Step S1 is shown.

[0054] The sending module 212 is configured to send a subscription message about a sensitive data cleanup event to the cloud node when the first data includes sensitive data and preset subscription conditions are met, for example, by performing the following: Figure 1 Step S2 is shown. The subscription message includes a subscription event identifier. The subscription message corresponds to a subscription timestamp and an identifier of the user to whom the sensitive data belongs.

[0055] The receiving module 213 is configured to receive a publishing message from the cloud node regarding a sensitive data cleanup event, for example, by performing... Figure 1 Step S3 is shown. The published message includes a publication event identifier, the identifier of the user whose sensitive data needs to be cleared, and a publication timestamp.

[0056] The clearing module 214 is configured to, when the published event identifier is the same as the subscribed event identifier, the user identifier in the published message and the user identifier in the subscribed message have an intersection, and the subscription timestamp is less than the published timestamp, clear sensitive data collected before the subscription timestamp corresponding to the identifier, for example, by performing the following: Figure 1 Step S4 is shown.

[0057] Figure 3 This is a block diagram illustrating a fog node according to other embodiments of the present disclosure.

[0058] like Figure 3As shown, fog node 31 includes a memory 311 and a processor 312 coupled to the memory 311. The memory 311 is used to store instructions for executing data processing methods corresponding to embodiments thereof. The processor 312 is configured to execute data processing methods in any of the embodiments of this disclosure based on the instructions stored in the memory 311. For example, fog node 31 and fog node 21 have the same or similar structure and function.

[0059] Figure 4 This is a block diagram illustrating a data processing system according to some embodiments of the present disclosure.

[0060] like Figure 4 As shown, the data processing system 4 includes one or more fog nodes 41 and cloud nodes 42.

[0061] Each fog node 41 is configured to: detect whether the first data collected by the fog node from the user includes sensitive data; if the first data includes sensitive data and a preset subscription condition is met, generate and send a subscription message regarding a sensitive data clearing event. The subscription message includes a subscription event identifier. The subscription message also corresponds to a subscription timestamp and the identifier of the user to whom the sensitive data belongs.

[0062] Cloud node 42 is configured to: parse subscription messages from each fog node to obtain a subscription event identifier corresponding to each fog node; generate a publication message about a sensitive data clearing event, the publication message including a publication event identifier, the identifier of the user whose sensitive data needs to be cleared, and a publication timestamp; and send the publication message to the fog node corresponding to the subscription event identifier that is the same as the publication event identifier.

[0063] Each fog node 41 is further configured to: receive the publication message from the cloud node; and, if the publication event identifier is the same as the subscription event identifier, the user identifier in the publication message intersects with the user identifier in the subscription message, and the subscription timestamp is less than the publication timestamp, clear sensitive data collected before the subscription timestamp corresponding to the identifier.

[0064] In some embodiments, cloud node 42 is further configured to: receive a clearing instruction from a user who needs to clear sensitive data, the clearing instruction including an identifier of the user who needs to clear sensitive data; and, in response to receiving the clearing instruction, generate the publishing message based on the identifier of the user who needs to clear sensitive data.

[0065] The following will combine Figure 5 and Figure 6 The data processing methods in some embodiments of this disclosure are described in detail.

[0066] Figure 5This is a block diagram illustrating a data processing system according to other embodiments of the present disclosure.

[0067] Figure 6 This is a schematic diagram illustrating a data processing method according to some embodiments of the present disclosure.

[0068] like Figure 5 As shown, the data processing system 5 includes a fog terminal component 51 and a cloud terminal component 52.

[0069] The fog terminal component 51 includes a data classification module 511, a message subscription module 512, an information retrieval module 513, and an information removal module 514. The fog terminal component 51 is deployed in the fog node.

[0070] The cloud component 52 includes an agent module 521, a request receiving module 522, and an information publishing module 523. The cloud component 52 is deployed in a cloud node.

[0071] A fog computing service architecture typically consists of a user terminal device layer, a fog layer, and a cloud layer. The fog layer, as the core of fog computing, is composed of various fog nodes. Fog nodes can be any device with computing, storage, and network connectivity capabilities, such as industrial controllers, switches, routers, wireless access points (APs), embedded servers, and video surveillance cameras. User terminal devices connect to the fog nodes and use localized information and service applications provided by fog computing. During this process, fog nodes collect various types of information, including sensitive user data, according to the application's needs.

[0072] like Figure 6 As shown, the fog computing service architecture includes user 1's terminal UE1 and user 2's terminal UE2. The fog computing service architecture also includes fog node F1, fog node F2, and cloud node C1. Fog nodes F1 and F2 both deploy the following... Figure 5 The fog terminal component 51 shown is deployed in cloud node C1 as follows. Figure 5 The cloud component 52 is shown. Both User 1's terminal UE1 and User 2's terminal UE are connected to fog node F1. User 1's terminal UE1 is also connected to fog node F2. For example, the fog computing service architecture may also include other users' terminals and other fog nodes, and User 1's terminal UE1 and User 2's terminal UE may also connect to other fog nodes; this disclosure does not impose any limitations.

[0073] In some embodiments, after user 1's terminal UE1 accesses fog nodes 1 and 2, fog nodes F1 and F2 collect and store user 1's data. After user 2's terminal UE2 accesses fog node F1, fog node F1 collects and stores user 2's data. For example, fog node F1 collects user 1's license plate number, parking location, etc., as well as user 2's application usage information, device temperature, etc.

[0074] Figure 5 The data classification module 511 of the fog terminal component 51 classifies the user information collected by the fog nodes according to preset data classification rules. The data classification includes two main categories: sensitive data and non-sensitive data. In some embodiments, further subcategories can be made based on the information's content. For example, sensitive data includes, but is not limited to, sensitive personal data and data that is not suitable for publication by enterprises or social organizations, such as personal sensitive information like names, phone numbers, email addresses, delivery addresses, personal biometric information, bank account numbers, license plate numbers, communication records and content, property information, credit information, whereabouts, accommodation information, health and physiological information, transaction information, etc., as well as certain location privacy, sensor data, and application usage information.

[0075] For sensitive data, Figure 5 The data classification module 511 adds metadata information that uniquely identifies the user and sends this metadata information to the corresponding user's terminal device. For example, this metadata information can also be generated by the user's terminal device when it first uses the fog service and sent to the fog node during data communication. The metadata information is used to mark sensitive information collected, such as the user's unique identifier.

[0076] In some embodiments, with Figure 6 Taking fog node F1 as an example, fog node F1 uses the data classification module deployed in its fog-end component to classify data. License plate numbers (classified as vehicle information) and parking locations (classified as location information) are grouped into sensitive information, and a unique metadata UID1 is added to them. Fog node F1 also uses the same data classification module to group application usage information (classified as usage information) into sensitive information, adding a unique metadata UID2 to it. Fog node F1 then sends UID1 and UID2 to user 1 and user 2 respectively.

[0077] In some embodiments, the categorized sensitive data can be stored in the manner shown in Table 1.

[0078] Table 1

[0079] UID1 Vehicle Information license plate number UID1 Location information Parking location UID2 Usage Information Usage statistics UID2 Sensor information temperature … … …

[0080] The metadata information (i.e., the unique identifiers of users) for sensitive data in Table 1 above is used to uniquely identify users 1 and 2. The category column describes the classification of the corresponding sensitive data, and the content column describes the content of the corresponding sensitive data.

[0081] If the data classification module 511 detects that the data of users 1 and 2 includes sensitive data UID1, it notifies the message subscription module 512 that the data of users 1 and 2 contains sensitive data. The sensitive data of users 1 and 2 is identified by their unique identifiers UID1 and UID2, respectively. The message subscription module 512 uses the identifiers UID1 and UID2 of the sensitive data of users 1 and 2 and the subscription timestamp as event attributes, respectively, and initiates a clear event subscription to the proxy module 521 of the cloud component 52. The message subscription module 512 also stores information on subscribed events as shown in Table 2 in the fog node, for example.

[0082] Table 2

[0083]

[0084] As shown in Table 2, the fog node subscribes to an event with the topic DELETE, which has the following event attributes: UID1, UID2, and subscription timestamp.

[0085] In some embodiments, the message subscription module 512 of the fog terminal component 51 can subscribe to events based on preset time nodes (such as a fixed time or a specific time interval) or special events (such as the user terminal disconnecting from the fog node).

[0086] For example, with Figure 6 For example, fog node F1 uses the message subscription module deployed in the fog component to subscribe to an event named "DELETE" from the proxy module of the cloud component of cloud node C1, specifying UID1 and UID2 as content and using the subscription timestamp (S-timestamp) as a constraint. Assuming the subscription time is 18:30 on March 5, 2020, the subscription timestamp value corresponding to UID1 and UID2 can be set to 202003051830.

[0087] In some embodiments, if the message subscription module 512 does not receive an event with a unique identifier for a specific user during the subscription period, but collects sensitive data of the same user during that period, the subscription timestamp can be modified. Figure 6 Taking fog node F1 as an example, if the message subscription module in fog node F1 subscribes to an event at 18:30 on March 5, 2020, and then collects sensitive data from user 1, it can modify the subscription timestamp of UID1. Assume the S-timestamp value of UID1 is changed to 202003081920. At this time, the subscription timestamp of UID2 remains unchanged, still 202003051830.

[0088] In some embodiments, at a certain time, the request receiving module 522 of the cloud component 52 receives a request from the user to actively send a sensitive data removal request to the cloud component. When the user disables / unregisters the fog service, disconnects from the fog node, or otherwise subjectively believes that sensitive data needs to be removed, the user submits a sensitive data removal request to the request receiving module 522 of the cloud component 52. This request must contain the user's unique identifier (i.e., the identifier of the sensitive data).

[0089] by Figure 6 Taking fog node F1 as an example, users 1 and 2 send a sensitive data clearing request to the request receiving module in cloud node C1. This request includes the user's unique identifier UID1 and UID2.

[0090] Upon receiving a request to clear sensitive data, the request receiving module 522 sends a notification to the information publishing module 523, carrying the unique identifiers UID1 and UID2 of users 1 and 2, to publish a clearing event. For example, the information publishing module 523 publishes the clearing event using the unique identifiers UID1 and UID2 of users 1 and 2 and the publishing timestamp as the content of the publishing message.

[0091] As shown in Table 3, the event topic of the events published by the information publishing module 523 is a clearing event, and the event attributes are UID1 and its corresponding publishing timestamp, and UID2 and its corresponding publishing timestamp. For example, clearing requests initiated by different users at the same time or within the same time period may have the same or different publishing timestamps. The publishing timestamp can be predefined by the user or it can be the time when the user initiated the clearing request.

[0092] Table 3

[0093]

[0094] For example, Figure 6 The information publishing module of Zhongyun node C1 uses UID1 and the publishing timestamp (P-timestamp) as message content to publish an event with the subject "DELETE". Assuming the publishing time is 9:10 AM on March 10, 2020, the value of the publishing timestamp can be set to 202003100910.

[0095] In some embodiments, the information publishing module 523 can publish events through the proxy module 521, that is, send a publishing message about the clearing event to the proxy module 521, and the proxy module 521 will send the publishing message to the fog nodes that have subscribed to the clearing event. In practical applications, multiple information publishing modules of a cloud node can use the same proxy module or multiple proxy modules.

[0096] After receiving the publication message for the clearing event, the message subscription module 512 of the fog terminal component 51 extracts the event topic, user unique identifier, and publication timestamp from the publication message. If the publication event topic is the same as the subscription event topic, and the user identifier in the publication message overlaps with the user identifier in the subscription message, it further determines whether the subscription timestamp is less than the publication timestamp. If the subscription timestamp is less than the publication time, it sends the user unique identifiers UID1 and UID2 from the publication message to the information retrieval module 513.

[0097] by Figure 6 Taking fog node F1 as an example, the information publishing module of fog node F1 publishes an event with the topic "DELETE" through the proxy module. The message content is UID1, and the publishing timestamp (P-timestamp) value is 202003100910. UID1 is a unique user identifier specified by the message subscription module of fog node F1, and the subscription timestamp (S-timestamp) value is 202003051830. A comparison shows that the publishing timestamp value is greater than the subscription timestamp value. Therefore, the message subscription module of fog node F1 accepts the DELETE event, extracts the UID1 contained in the DELETE event, and sends it to the information retrieval module of fog node F1.

[0098] Because fog nodes are widely distributed and their online / offline status may be uncertain, and different fog nodes may collect the same or different sensitive information from the same user at different times, the subscription timestamps will be inconsistent. For example, fog node F1 uses UID1 and UID2 as specified content, with a subscription timestamp value of 202003051830; fog node F2 uses UID1 as specified content, with a subscription timestamp value of 202003061830. If the information publishing module publishes a message with UID1 and a publishing timestamp (P-timestamp) value of 202003100910, then both fog nodes F1 and F2's message subscription modules will receive an event with the topic "Clear". However, assuming fog node F2's subscription time is 10:15 AM on March 11, 2020, then its subscription timestamp value will be 202003111015. In this case, if the subscription timestamp is greater than the publication timestamp, it can be assumed that user 1 did not subscribe to the clearing event through fog node F2 before the publication timestamp, and therefore the clearing operation will not be performed.

[0099] The information retrieval module 513 receives the user's unique identifier transmitted by the message subscription module 512, searches for the sensitive data associated with the user in the corresponding database based on the metadata information, and records the relevant information, the data table where the data is stored, the disk and other specific storage locations.

[0100] The information retrieval module 513 sends information related to the sensitive data to be deleted to the information clearing module 514 to perform the clearing operation. The information clearing module 514 should use an unrecoverable method to clear or anonymize the sensitive data.

[0101] In some embodiments, the information retrieval module 513 receives the user's unique identifier UID1 transmitted by the message subscription module 512, retrieves sensitive information such as the license plate number (classified as vehicle information) and the parking location (classified as location information), and then the information clearing module 514 clears the collected information of user 1's license plate number and parking location.

[0102] For example, the information retrieval module 513 and the information clearing module 514 can be combined into an information retrieval and clearing module, which performs data clearing operations while performing sensitive data retrieval.

[0103] In some embodiments, after performing sensitive data clearing operations, the fog terminal component 51 can also notify the cloud component 52 through conventional methods. The cloud component 52 can provide feedback to the user on the progress of fog node clearing and which fog nodes have been cleared, further enhancing the user experience.

[0104] In some embodiments, when the cloud component 52 publishes an event, some fog nodes that have subscribed to the event may not be online. If a user subsequently submits a clearing request, the message publishing module 523 should publish the event in the form of appended information. After the fog node comes online, it should connect to the proxy module 521 to obtain the previously published event from the proxy module 521.

[0105] Figure 7 This is a block diagram illustrating a computer system for implementing some embodiments of the present disclosure.

[0106] like Figure 7 As shown, the computer system 70 can be represented in the form of a general computing device. The computer system 70 includes a memory 710, a processor 720, and a bus 700 connecting different system components.

[0107] The memory 710 may include, for example, system memory, non-volatile storage media, etc. The system memory may store, for example, an operating system, application programs, a boot loader, and other programs. The system memory may include volatile storage media, such as random access memory (RAM) and / or cache memory. The non-volatile storage media may store, for example, instructions for executing at least one embodiment of the data processing method. Non-volatile storage media include, but are not limited to, disk storage, optical storage, flash memory, etc.

[0108] The processor 720 can be implemented using a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete hardware components such as discrete gates or transistors. Accordingly, each module, such as the decision module and the determination module, can be implemented by the central processing unit (CPU) running instructions in memory to execute the corresponding steps, or by dedicated circuitry to execute the corresponding steps.

[0109] Bus 700 can use any of the various bus architectures. For example, bus architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, and Peripheral Component Interconnect (PCI) bus.

[0110] The computer system 70 may also include an input / output interface 730, a network interface 740, and a storage interface 750. These interfaces 730, 740, and 750, as well as the memory 710 and processor 720, can be connected via a bus 700. The input / output interface 730 provides a connection interface for input / output devices such as a monitor, mouse, and keyboard. The network interface 740 provides a connection interface for various networked devices. The storage interface 750 provides a connection interface for external storage devices such as floppy disks, USB flash drives, and SD cards.

[0111] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus, and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations thereof, can be implemented by computer-readable program instructions.

[0112] These computer-readable program instructions are provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable device to produce a machine, such that execution of the instructions by the processor produces means for implementing the functions specified in one or more boxes of the flowchart and / or block diagram.

[0113] These computer-readable program instructions may also be stored in a computer-readable storage medium. These instructions cause a computer to work in a particular manner to produce an article of manufacture, including instructions that implement the functions specified in one or more boxes in a flowchart and / or block diagram.

[0114] This disclosure may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects.

[0115] The data processing methods and systems, fog nodes, and computer-storable media described in the above embodiments can enhance the security of fog services and improve user experience.

[0116] The data processing methods and systems, fog nodes, and computer-readable storage media according to this disclosure have been described in detail above. To avoid obscuring the concept of this disclosure, some details known in the art have not been described. Those skilled in the art will fully understand how to implement the technical solutions disclosed herein based on the above description.

Claims

1. A data processing method, executed by a fog node, comprising: Detect whether the first data collected by the fog node from the user includes sensitive data; If the first data includes sensitive data and meets the preset subscription conditions, a subscription message for the clearing event of the sensitive data is sent to the cloud node. The subscription message includes a subscription event identifier and corresponds to a subscription timestamp and the identifier of the user to which the sensitive data belongs. Receive a publishing message from the cloud node regarding a sensitive data removal event. The publishing message includes a publishing event identifier, an identifier of the user whose sensitive data needs to be removed, and a publishing timestamp. If the published event identifier is the same as the subscribed event identifier, the user identifier in the published message and the user identifier in the subscribed message have an intersection, and the subscription timestamp is less than the published timestamp, then sensitive data collected before the subscription timestamp corresponding to the identifier will be cleared.

2. The data processing method according to claim 1, wherein, Deleting sensitive data corresponding to the identifier collected before the subscription timestamp includes: Based on the identifier, query the sensitive data of the user corresponding to the identifier from the fog nodes; Based on the collection timestamp of the sensitive data, sensitive data whose collection timestamp is less than the subscription timestamp is obtained as target sensitive data, where the collection timestamp represents the time when the sensitive data was collected by the fog node; Remove the target sensitive data.

3. The data processing method according to claim 1, wherein, The first data is collected by the fog node at a first time, the subscription timestamp is the first time, and the data processing method further includes: After sending the subscription message to the cloud node and before receiving the publish message from the cloud node, in response to collecting the user's second data at a second time, the subscription timestamp is updated to a second time, which is later than the first time.

4. The data processing method according to claim 1, wherein, The preset subscription conditions include at least one of time conditions and behavioral conditions.

5. The data processing method according to claim 4, wherein, The time conditions include the subscription time point, the subscription time period, or the subscription time interval.

6. The data processing method according to claim 4, wherein, The behavioral conditions include the fog node disconnecting from the user terminal.

7. The data processing method according to claim 1 further includes: Receive the identifier of the user to whom the first data belongs; or If the first data is detected to include sensitive data, an identifier for the user to whom the first data belongs is generated and the identifier is sent to that user.

8. The data processing method according to claim 1, wherein, Detecting whether the first data includes sensitive data includes: According to a preset classification strategy, the first data is classified to obtain sensitive datasets and non-sensitive datasets; If the sensitive dataset is not empty, it is determined that the first data includes sensitive data.

9. The data processing method according to claim 1, further comprising: When providing fog services to users, collect and store the user's data.

10. A fog node, comprising: The detection module is configured to detect whether the first data collected by the fog node from the user includes sensitive data; The sending module is configured to send a subscription message about the clearing event of sensitive data to the cloud node when the first data includes sensitive data and the preset subscription conditions are met. The subscription message includes a subscription event identifier and corresponds to a subscription timestamp and the identifier of the user to which the sensitive data belongs. The receiving module is configured to receive a publishing message from the cloud node regarding a sensitive data clearing event. The publishing message includes a publishing event identifier, an identifier of the user whose sensitive data needs to be cleared, and a publishing timestamp. The clearing module is configured to clear sensitive data collected before the subscription timestamp corresponding to the published event identifier when the published event identifier is the same as the subscription event identifier, the user identifier in the published message and the user identifier in the subscription message have an intersection, and the subscription timestamp is less than the published timestamp.

11. A fog node, comprising: Memory; as well as A processor coupled to the memory, the processor being configured to perform the data processing method as described in any one of claims 1 to 9 based on instructions stored in the memory.

12. A data processing system, comprising: One or more fog nodes, each fog node being configured as follows: Detect whether the first data collected by the fog node from the user includes sensitive data; If the first data includes sensitive data and the preset subscription conditions are met, a subscription message for a clearing event of the sensitive data is generated and sent. The subscription message includes a subscription event identifier and corresponds to a subscription timestamp and the identifier of the user to whom the sensitive data belongs. The cloud node is configured as follows: Parse the subscription messages from each fog node to obtain the subscription event identifier corresponding to each fog node; Generate a publication message about the removal of sensitive data, the publication message including a publication event identifier, an identifier of the user whose sensitive data needs to be removed, and a publication timestamp; Send the publish message to the fog node corresponding to the subscription event identifier that is the same as the publish event identifier; Each fog node is also configured to: Receive the publish message from the cloud node; If the published event identifier is the same as the subscribed event identifier, the user identifier in the published message and the user identifier in the subscribed message have an intersection, and the subscription timestamp is less than the published timestamp, then sensitive data collected before the subscription timestamp corresponding to the identifier will be cleared.

13. The data processing system according to claim 12, wherein, The cloud node is also configured as follows: Receive a clearing instruction from a user who needs to clear sensitive data, the clearing instruction including the identifier of the user who needs to clear the sensitive data; In response to receiving the clearing instruction, the system generates the publishing message by clearing the identifier of the user whose sensitive data needs to be cleared.

14. A computer-storeable medium having stored thereon computer program instructions that, when executed by a processor, implement the data processing method as described in any one of claims 1 to 9.

Images