Sensitive data anonymization processing method and device, electronic equipment and medium

Abstract

The invention provides a sensitive data anonymization processing method and device, electronic equipment and a medium, and the method comprises the steps: creating a private cloud account in a private cloud server, creating a public cloud account in a public cloud platform, and associating the private cloud account with the public cloud account in the private cloud server; when a user reserves a conference through the terminal equipment, the private cloud server creates the conference, stores conference information and instructs the public cloud platform to create the conference, the public cloud platform returns the conference information to the private cloud server, and the private cloud server stores the conference information and generates reserved conference information; a user participates in a conference through terminal equipment, the terminal equipment sends a conference joining request for joining a specified conference to a private cloud server, and the private cloud server finds out reserved conference information according to a conference number carried by the conference joining request and returns a public cloud account corresponding to the terminal equipment and the conference information to the terminal equipment; and the user participates in the conference based on the public cloud account and the conference information through the terminal equipment.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and more specifically, to a method, apparatus, electronic device, and medium for anonymizing sensitive data. Background Technology

[0002] The technology behind public cloud video SaaS services aims to make complex audio and video processing capabilities as readily available as water and electricity. At its core, it encapsulates massive infrastructure and complex technical details through a cloud computing architecture, providing you with a ready-to-use video application experience.

[0003] Currently, in the application of public cloud video SaaS services, data processing primarily involves directly uploading various types of data, such as user video data, audio data, and participant information, to the cloud for processing. During this process, the cloud server stores, analyzes, and forwards this data to ensure the smooth running of the meeting and related data analysis and statistical functions. Users' personal identification information (such as name, ID number, and contact information) is also uploaded to the public cloud along with other data for management and access.

[0004] However, the existing data processing method, which directly uploads all data, including users' personal identity information, to the cloud, poses serious security risks, including the risk of sensitive data leakage, and leads to issues with users' privacy and data security. Summary of the Invention

[0005] In view of this, the purpose of this application is to provide a method, apparatus, electronic device and medium for anonymizing sensitive data. By performing anonymization processing of sensitive data on a private server, the path of sensitive data flowing to the public cloud is completely cut off from the source, which greatly reduces the risk of sensitive data leakage, ensures the confidentiality of sensitive data, and effectively protects the privacy and data security of users.

[0006] In a first aspect, embodiments of this application provide a method for anonymizing sensitive data, the method comprising: In response to a user conducting a meeting via a terminal device, a private cloud account for the user is created on a private cloud server and a public cloud account for the user is created on a public cloud platform. The user's private cloud account and public cloud account are then associated on the private cloud server. The private cloud server stores the user's collected personal identification information. In response to the user scheduling a meeting through the terminal device, the private cloud server creates the meeting and saves the meeting information, and simultaneously instructs the public cloud platform to create the meeting. After the public cloud platform successfully creates the meeting, it returns the meeting information to the private cloud server. The private cloud server saves the meeting information and generates the scheduled meeting information. In response to the user joining the meeting via the terminal device, the terminal device sends a joining request to the private cloud server. The private cloud server finds the corresponding booked meeting information based on the meeting number carried in the joining request, and returns the public cloud account corresponding to the terminal device and the meeting information to the terminal device, so that the user can join the meeting via the terminal device based on the public cloud account and the meeting information.

[0007] In one possible implementation, the user's personally identifiable information is collected through the following steps: In response to the user registering an account for the first time through the terminal device, the terminal device sends a login request to the private cloud server; The private cloud server receives the login request and collects and saves the user's personal identification information.

[0008] In one possible implementation, the step of creating the user's private cloud account on a private cloud server and the user's public cloud account on a public cloud platform, and associating the user's private cloud account and public cloud account on the private cloud server, includes: The private cloud server generates a one-time session mapping token and sends an account creation request to the public cloud platform; The public cloud platform creates the public cloud account based on the account creation request, and associates the public cloud account with the user's private cloud account in the private cloud server.

[0009] In one possible implementation, the method further includes: The validity period of the meeting is controlled based on the one-time session mapping token; wherein, the validity period of the one-time session mapping token is determined by the duration of the meeting and the dynamically randomly allocated encryption duration; In response to the end of the meeting, the one-time session mapping token is automatically invalidated.

[0010] In one possible implementation, the private cloud server creates a meeting and saves meeting information, while simultaneously instructing the public cloud platform to create a meeting, including: In response to the user logging in through the terminal device, a login request is sent to the private cloud server, and after the login authentication is successful on the private cloud server, the corresponding login result is returned to the terminal device. When the user schedules a meeting through the terminal device, the terminal device sends a meeting creation request to the private cloud server, and the private cloud server creates a meeting and saves the meeting information based on the meeting creation request. The private cloud server simultaneously sends a meeting request to the public cloud platform to create a specified meeting number and meeting configuration, so that the public cloud platform can create a meeting in response to the meeting request.

[0011] In one possible implementation, the method further includes: In response to the requirement of the user's personal identification information for the target business, the corresponding personal identification information is matched in the private cloud server through the user's public cloud account, and the personal identification information is processed in multiple dimensions. Upon completion of the processing of the personal identification information, the processed personal identification information is directly returned to the terminal device.

[0012] In one possible implementation, the meeting corresponds to a list of attendees; the method further includes: When the private cloud server transmits the meeting information to the public cloud platform, the private cloud server generates virtual participants and mixes the virtual participants into the meeting's participant list; Once the meeting begins, the private cloud server sends a departure instruction from the virtual participant to the public cloud platform.

[0013] Secondly, embodiments of this application also provide a sensitive data anonymization processing apparatus, the apparatus comprising: A creation module is used to respond to a user conducting meeting business through a terminal device by creating the user's private cloud account on a private cloud server and the user's public cloud account on a public cloud platform, and associating the user's private cloud account and public cloud account on the private cloud server; wherein, the private cloud server stores the collected personal identification information of the user; The reservation module is used to respond to when the user makes a reservation for a meeting through the terminal device. The private cloud server creates a meeting and saves the meeting information, and at the same time instructs the public cloud platform to create a meeting. After the public cloud platform successfully creates the meeting, it returns the meeting information to the private cloud server. The private cloud server saves the meeting information and generates the reserved meeting information. The meeting entry module is used to respond to the user joining a meeting through the terminal device. The terminal device sends a meeting entry request to the private cloud server to join the specified meeting. The private cloud server finds the corresponding booked meeting information based on the meeting number carried in the meeting entry request, and returns the public cloud account corresponding to the terminal device and the meeting information to the terminal device, so that the user can join the meeting through the terminal device based on the public cloud account and the meeting information.

[0014] In one possible implementation, the user's personally identifiable information is collected through the following steps: In response to the user registering an account for the first time through the terminal device, the terminal device sends a login request to the private cloud server; The private cloud server receives the login request and collects and saves the user's personal identification information.

[0015] In one possible implementation, the creation module is specifically used for: The private cloud server generates a one-time session mapping token and sends an account creation request to the public cloud platform; The public cloud platform creates the public cloud account based on the account creation request, and associates the public cloud account with the user's private cloud account in the private cloud server.

[0016] In one possible implementation, the device further includes: A control module is used to control the timeliness of the meeting based on the one-time session mapping token; wherein the timeliness of the one-time session mapping token is determined by the duration of the meeting and the dynamically randomly allocated encryption duration; An invalidation module is used to automatically invalidate the one-time session mapping token in response to the end of the meeting.

[0017] In one possible implementation, the reservation module is specifically used for: In response to the user logging in through the terminal device, a login request is sent to the private cloud server, and after the login authentication is successful on the private cloud server, the corresponding login result is returned to the terminal device. When the user schedules a meeting through the terminal device, the terminal device sends a meeting creation request to the private cloud server, and the private cloud server creates a meeting and saves the meeting information based on the meeting creation request. The private cloud server simultaneously sends a meeting request to the public cloud platform to create a specified meeting number and meeting configuration, so that the public cloud platform can create a meeting in response to the meeting request.

[0018] In one possible implementation, the device further includes: The processing module is used to respond to the requirement of the user's personal identification information in the target business, and then match the corresponding personal identification information in the private cloud server through the user's public cloud account, and perform multi-dimensional processing on the personal identification information. The return module is used to directly return the processed personal identification information to the terminal device in response to the completion of the processing of the personal identification information.

[0019] In one possible implementation, the meeting corresponds to a list of attendees; the device further includes: The generation module is used to generate virtual participants when the private cloud server transmits the meeting information to the public cloud platform, and to mix the virtual participants into the meeting's participant list. The sending module is used to send the virtual participant's departure instruction to the public cloud platform after the meeting starts.

[0020] Thirdly, embodiments of this application provide an electronic device, including: a processor, a storage medium, and a bus. The storage medium stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the storage medium via the bus, and the processor executes the machine-readable instructions to perform the steps of the sensitive data anonymization processing method as described in any of the first aspects.

[0021] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the sensitive data anonymization processing method described in any one of the first aspects.

[0022] This application provides a sensitive data anonymization processing method, apparatus, electronic device, and medium. In response to a user conducting a meeting via a terminal device, the system creates a private cloud account on a private cloud server and a public cloud account on a public cloud platform, and associates the user's private cloud account and public cloud account on the private cloud server. In response to a user scheduling a meeting via the terminal device, the private cloud server creates the meeting and saves the meeting information, while simultaneously instructing the public cloud platform to create the meeting. After successful meeting creation, the public cloud platform returns the meeting information to the private cloud server, which saves the meeting information and generates scheduled meeting information. In response to a user joining a meeting via the terminal device, the terminal device sends a joining request to the private cloud server. The private cloud server retrieves the corresponding scheduled meeting information based on the meeting number carried in the joining request and returns the public cloud account and meeting information corresponding to the terminal device to the terminal device, enabling the user to join the meeting via the terminal device based on the public cloud account and meeting information. This application, by anonymizing sensitive data on a private server, completely cuts off the path of sensitive data flowing to the public cloud at the source, greatly reducing the risk of sensitive data leakage, ensuring the confidentiality of sensitive data, and effectively protecting user privacy and data security.

[0023] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0024] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0025] Figure 1 This is a flowchart of a sensitive data anonymization processing method provided according to an embodiment of this application; Figure 2 This is a diagram illustrating the account creation and mapping process; Figure 3 A diagram illustrating the terminal login and meeting scheduling process; Figure 4 This is a diagram illustrating the membership application process; Figure 5 This is a schematic diagram of the sensitive data anonymization processing apparatus provided according to an embodiment of this application; Figure 6 This is a schematic diagram of the structure of an electronic device provided according to an embodiment of this application. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the accompanying drawings in this application are for illustrative and descriptive purposes only and are not intended to limit the scope of protection of this application. Furthermore, it should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this application illustrate operations implemented according to some embodiments of this application. It should be understood that the operations in the flowcharts may not be implemented in sequence, and steps without logical contextual relationships may be reversed or implemented simultaneously. In addition, those skilled in the art, guided by the content of this application, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts.

[0027] Furthermore, the described embodiments are merely some, not all, of the embodiments of this application. The components of the embodiments of this application described and illustrated herein can typically be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0028] It should be noted that the term "comprising" will be used in the embodiments of this application to indicate the presence of the features declared thereafter, but does not exclude the addition of other features.

[0029] Considering the underlying technology of public cloud video SaaS services, the aim is to make complex audio and video processing capabilities as readily available as water and electricity. At its core, it encapsulates the massive infrastructure and complex technical details through a cloud computing architecture, providing you with a ready-to-use video application experience.

[0030] Currently, in the application of public cloud video SaaS services, data processing primarily involves directly uploading various types of data, such as user video data, audio data, and participant information, to the cloud for processing. During this process, the cloud server stores, analyzes, and forwards this data to ensure the smooth running of the meeting and related data analysis and statistical functions. Users' personal identification information (such as name, ID number, and contact information) is also uploaded to the public cloud along with other data for management and access.

[0031] However, the existing data processing method, which directly uploads all data, including users' personal identity information, to the cloud, poses serious security risks, including the risk of sensitive data leakage, and leads to issues with users' privacy and data security.

[0032] To address this issue, this application provides a method, apparatus, electronic device, and medium for anonymizing sensitive data. By performing anonymization on a private server, the path of sensitive data flowing to the public cloud is completely cut off at the source, greatly reducing the risk of sensitive data leakage, ensuring the confidentiality of sensitive data, and effectively protecting user privacy and data security.

[0033] Figure 1 This is a flowchart of a sensitive data anonymization method provided according to an embodiment of this application. For example... Figure 1 As shown, the sensitive data anonymization method of this application embodiment may specifically include: S101. In response to a user conducting meeting services through a terminal device, create the user's private cloud account on a private cloud server and the user's public cloud account on a public cloud platform, and associate the user's private cloud account and public cloud account on the private cloud server.

[0034] S102. In response to a user scheduling a meeting via a terminal device, the private cloud server creates the meeting and saves the meeting information. At the same time, it instructs the public cloud platform to create the meeting. After the public cloud platform successfully creates the meeting, it returns the meeting information to the private cloud server. The private cloud server saves the meeting information and generates the scheduled meeting information.

[0035] S103. In response to a user joining a meeting via a terminal device, the terminal device sends a joining request to the private cloud server. The private cloud server finds the corresponding booked meeting information based on the meeting number carried in the joining request, and returns the public cloud account and meeting information corresponding to the terminal device to the terminal device, so that the user can join the meeting via the terminal device based on the public cloud account and meeting information.

[0036] The above-mentioned sensitive data anonymization method completely cuts off the path of sensitive data to the public cloud by performing sensitive data anonymization on a private server, greatly reducing the risk of sensitive data leakage, ensuring the confidentiality of sensitive data, and effectively protecting user privacy and data security.

[0037] The exemplary steps described above in the embodiments of this application are illustrated below with specific examples: S101, in response to a user conducting meeting business through a terminal device, creates the user's private cloud account on a private cloud server and the user's public cloud account on a public cloud platform, and associates the user's private cloud account and public cloud account in the private cloud server.

[0038] In this embodiment, the terminal device includes at least a computer, mobile phone, tablet computer, etc., and the public cloud platform is a public cloud video SaaS service platform. The private cloud server stores the collected personal identification information of the user, which includes at least name, citizen identification number, and contact information. The public cloud account is a public cloud video random account, which does not contain any actual data information that can identify the user. The public cloud account is a unique random identifier for the user on the public cloud platform. The association between the public cloud account and the personal identification information is logically isolated on the private cloud server side. This association is only visible and used within the authorized private server and system. When a user conducts conferencing business (e.g., video conferencing business) through the terminal device, a private cloud account is created on the private cloud server and a public cloud account is created on the public cloud platform. The user's private cloud account and public cloud account are then associated on the private cloud server for subsequent processing. For example, as... Figure 2 As shown.

[0039] It should be noted that the user's personally identifiable information is collected through the following steps: In response to a user's first login to register an account via a terminal device, the terminal device sends a login request to the private cloud server; the private cloud server receives the login request and collects and stores the user's personally identifiable information. Specifically, when the terminal logs in to register an account for the first time, it sends a login request to the private cloud; the private cloud service collects and stores the user information.

[0040] In some implementations, the private cloud server generates a one-time session mapping token and sends an account creation request to the public cloud platform. The public cloud platform creates a public cloud account based on the account creation request and associates the public cloud account with the user's private cloud account on the private cloud server. The one-time session mapping token is a time-slice-based one-time session mapping token.

[0041] Specifically, when the aforementioned terminal logs in to register an account for the first time, it sends a login request to the private cloud. After the private cloud service collects and saves the user information, the private cloud generates a one-time session mapping token and sends an account creation request to the public cloud to create a random public cloud account, which is then stored on the private cloud server. The public cloud account is then associated with the user's private cloud account.

[0042] In summary, in this application, when a user conducts video conferencing through a terminal device, the terminal device collects and independently stores the user's personally identifiable information on a private cloud server, without directly uploading it to the public cloud environment. Furthermore, a unique, randomly generated identifier account (i.e., a public cloud account) is generated for the user on the public cloud platform. This account does not contain any actual data information that can identify the user, and a dynamic, encrypted, two-way mapping mechanism based on time slices is established to associate the private cloud account and the public cloud account, thereby achieving the association and binding of the public cloud account with the corresponding real user information on the private cloud server.

[0043] Therefore, the association between public cloud and private cloud user information in this application is logically isolated on the private cloud side. This association is only visible and usable within the authorized private server and system, thus resolving the risk of historical data association that may be caused by static mapping.

[0044] S102, in response to a user scheduling a meeting via a terminal device, the private cloud server creates the meeting and saves the meeting information, while simultaneously instructing the public cloud platform to create the meeting. After successfully creating the meeting, the public cloud platform returns the meeting information to the private cloud server, which then saves the meeting information and generates the scheduled meeting information.

[0045] In this embodiment, the meeting information refers to basic meeting information, including confidential user data such as meeting participants. When a user schedules a meeting via a terminal device, the private cloud server creates the meeting and saves the meeting information. Simultaneously, it instructs the public cloud platform to create the meeting. After successfully creating the meeting, the public cloud platform returns the meeting information to the private cloud server. The private cloud server saves the meeting information and generates scheduled meeting information for subsequent processing. For example, as... Figure 3 As shown.

[0046] Optionally, when creating a meeting and saving meeting information on the private cloud server, and simultaneously instructing the public cloud platform to create a meeting, in response to a user logging in via a terminal device, a login request is sent to the private cloud server. After successful login authentication on the private cloud server, the corresponding login result is returned to the terminal device. In response to a user scheduling a meeting via a terminal device, the terminal device sends a meeting creation request to the private cloud server, which creates the meeting and saves the meeting information based on the meeting creation request. Simultaneously, the private cloud server sends a meeting request to the public cloud platform to create a meeting with a specified meeting number and meeting configuration, so that the public cloud platform can create the meeting upon receiving the meeting request.

[0047] Specifically, when a terminal device logs in, it sends a login request to the private cloud server. After successful login authentication on the private cloud, the terminal device receives a login result. When scheduling a meeting, the terminal device sends a meeting creation request to the private cloud server. The private cloud server creates the meeting and saves basic meeting information (including confidential user data such as participant information). At the same time, it sends a meeting request to the public cloud to create a specified meeting number and meeting configuration (excluding confidential user data). After the public cloud successfully creates the meeting, it returns the result to the private cloud server, which then saves the meeting information and configuration.

[0048] S103, in response to a user joining a meeting via a terminal device, the terminal device sends a joining request to the private cloud server to join the specified meeting. The private cloud server finds the corresponding booked meeting information based on the meeting number carried in the joining request, and returns the public cloud account and meeting information corresponding to the terminal device to the terminal device, so that the user can join the meeting via the terminal device based on the public cloud account and meeting information.

[0049] In this embodiment, the meeting request carries the meeting ID of the specified meeting. When a user joins the meeting via a terminal device, the terminal device sends a meeting request to the private cloud server. The private cloud server retrieves the corresponding booked meeting information based on the meeting ID carried in the meeting request and returns the public cloud account and meeting information corresponding to the terminal device to the terminal device. The user then joins the meeting via the terminal device based on the public cloud account and meeting information. For example, as... Figure 4 As shown.

[0050] The sensitive data anonymization method provided in this application, in response to a user conducting a meeting via a terminal device, creates a private cloud account for the user on a private cloud server and a public cloud account on a public cloud platform, and associates the user's private cloud account and public cloud account on the private cloud server; in response to a user scheduling a meeting via a terminal device, the private cloud server creates the meeting and saves the meeting information, and simultaneously instructs the public cloud platform to create the meeting. After successfully creating the meeting, the public cloud platform returns the meeting information to the private cloud server, which saves the meeting information and generates scheduled meeting information; in response to a user joining a meeting via a terminal device, the terminal device sends a joining request to the private cloud server to join the specified meeting. The private cloud server finds the corresponding scheduled meeting information based on the meeting number carried in the joining request, and returns the public cloud account and meeting information corresponding to the terminal device to the terminal device, so that the user can join the meeting via the terminal device based on the public cloud account and meeting information. The sensitive data anonymization method described in this application completes the anonymization process on a private server, completely cutting off the path of sensitive data flowing to the public cloud at the source. This greatly reduces the risk of sensitive data leakage, ensures the confidentiality of sensitive data, and effectively protects user privacy and data security.

[0051] Furthermore, the validity period of the meeting is controlled based on a one-time session mapping token; the one-time session mapping token automatically expires upon the end of the meeting. The validity period of the one-time session mapping token is determined by the duration of the meeting and the dynamically randomly allocated encryption duration.

[0052] Specifically, this application adds timeliness control to the mapping relationship between user information of public cloud accounts and private cloud accounts. At the start of each meeting, the private cloud generates a one-time session mapping token. The timeliness of the one-time session mapping token is equal to the meeting duration plus the dynamically randomly assigned encryption duration. The token automatically expires after the meeting ends.

[0053] Furthermore, in response to the requirement of user's personal identification information for the target business, the corresponding personal identification information is matched in the private cloud server through the user's public cloud account, and the personal identification information is processed in multiple dimensions; in response to the completion of personal identification information processing, the processed personal identification information is directly returned to the terminal device.

[0054] Specifically, throughout the entire lifecycle of a video conferencing session, real-time audio and video processing services are technically supported by a public cloud platform. However, when the business requires a user's personally identifiable information, the processing takes place in a private cloud. The private cloud server matches the corresponding personally identifiable information with the public cloud account and then performs the necessary processing within the private cloud. For example, it filters necessary information based on the meeting scenario and performs format conversion. After processing, the results are directly returned to the terminal device. The entire process does not go through the public cloud and no important data is stored on the public cloud.

[0055] Therefore, the entire process does not go through the public cloud and no important data is left on the public cloud, thus achieving anonymous data transmission and service calls.

[0056] Furthermore, the meeting corresponds to a list of attendees. When the private cloud server transmits meeting information to the public cloud platform, the private cloud server generates virtual attendees and adds them to the meeting's attendee list. Once the meeting begins, the private cloud server sends a departure command to the public cloud platform for the virtual attendees. Virtual attendees can be identified using virtual attendee IDs.

[0057] Specifically, when the private cloud server in this application transmits meeting information to the public cloud platform, it mixes virtual participant IDs into the list of participants. After the meeting starts, the private cloud sends a virtual participant departure instruction to the public cloud, which will not affect the actual participants. The public cloud can only perceive the final real participation scale, but it is difficult to deduce the real user list of the private cloud.

[0058] Therefore, by mixing virtual participant IDs into the list of participants, a topological disguise for obfuscating meeting data is added.

[0059] In summary, the technical effects of this application are as follows: 1. Ensuring the confidentiality of sensitive data: User's personal identity information is stored only on the private cloud server, while the public cloud only has random accounts. Furthermore, the acquisition and processing of user information are completed between the private cloud and the terminal device, bypassing the public cloud. This completely cuts off the path of sensitive data flowing to the public cloud at the source, greatly reducing the risk of sensitive data leakage and effectively protecting user privacy and data security. 2. Solving the risk of historical data association that may result from static mapping through a time-slice-based dynamic mapping separation mechanism. 3. Defending against attacks that infer sensitive information from data such as meeting scale and timing through topology camouflage based on virtual participant meeting data obfuscation. 4. Not affecting normal meeting functions: Video capabilities utilize public cloud services, while user information is processed through the private cloud and directly returned to the terminal device. The processed data and acquired information meet the needs of the public cloud video SaaS service and the terminal device for meeting convening, data analysis, and statistics, without affecting the normal conduct of the meeting. 5. Enhance User Trust: By isolating sensitive user information in a private cloud, maintaining only random accounts with no actual data in the public cloud, and ensuring that user information processing and transmission do not pass through the public cloud, multiple effective data security measures significantly enhance user trust in public cloud video SaaS services, increasing user willingness and satisfaction. 6. Achieve Data Isolation and Control: Complete isolation of sensitive user information from the public cloud provides users with stronger management and control over their sensitive information. Users can flexibly adjust access permissions and scope according to their needs, further improving data security and controllability. 7. Reduce Data Transfer Risks: User information is processed within the private cloud and directly returned to the terminal device, reducing the number of data transfer points and lowering the risk of data interception or tampering during transmission.

[0060] Figure 5 This is a schematic diagram of the sensitive data anonymization processing apparatus provided according to an embodiment of this application; as shown below. Figure 5 As shown, the sensitive data anonymization processing apparatus 500 of this application embodiment may specifically include: The creation module 501 is used to respond to a user conducting a meeting through a terminal device by creating the user's private cloud account on a private cloud server and the user's public cloud account on a public cloud platform, and associating the user's private cloud account and public cloud account in the private cloud server; wherein, the private cloud server stores the collected personal identification information of the user. The reservation module 502 is used to respond to when the user makes a reservation for a meeting through the terminal device. The private cloud server creates a meeting and saves the meeting information, and at the same time instructs the public cloud platform to create a meeting. After the public cloud platform successfully creates the meeting, it returns the meeting information to the private cloud server. The private cloud server saves the meeting information and generates the reserved meeting information. The meeting entry module 503 is used to respond to the user joining a meeting through the terminal device. The terminal device sends a meeting entry request to the private cloud server to join a specified meeting. The private cloud server finds the corresponding booked meeting information based on the meeting number carried in the meeting entry request, and returns the public cloud account corresponding to the terminal device and the meeting information to the terminal device, so that the user can join the meeting through the terminal device based on the public cloud account and the meeting information.

[0061] In one possible implementation, a user's personally identifiable information is collected through the following steps: In response to a user registering an account for the first time via a terminal device, the terminal device sends a login request to the private cloud server; The private cloud server receives the login request and collects and stores the user's personally identifiable information.

[0062] In one possible implementation, a module is created specifically for: The private cloud server generates a one-time session mapping token and sends an account creation request to the public cloud platform; The public cloud platform creates a public cloud account based on the account creation request and associates the public cloud account with the user's private cloud account on the private cloud server.

[0063] In one possible implementation, the apparatus further includes: The control module is used to control the timeliness of the meeting based on a one-time session mapping token; wherein, the timeliness of the one-time session mapping token is determined by the duration of the meeting and the dynamically randomly allocated encryption duration; The invalidation module is used to automatically invalidate one-time session mapping tokens in response to the end of the meeting.

[0064] In one possible implementation, the reservation module is specifically used for: When a user logs in via a terminal device, a login request is sent to the private cloud server. After the login authentication is successful on the private cloud server, the corresponding login result is returned to the terminal device. When a user schedules a meeting via a terminal device, the terminal device sends a meeting creation request to the private cloud server. The private cloud server then creates the meeting based on the meeting creation request and saves the meeting information. The private cloud server simultaneously sends a meeting request to the public cloud platform, specifying the meeting number and meeting configuration, so that the public cloud platform can create the meeting upon receiving the meeting request.

[0065] In one possible implementation, the apparatus further includes: The processing module is used to respond to the target business's need for the user's personal identification information. It then matches the corresponding personal identification information with the user's public cloud account in the private cloud server and performs multi-dimensional processing on the personal identification information. The return module is used to directly return the processed personal identification information to the terminal device in response to the completion of personal identification information processing.

[0066] In one possible implementation, the meeting corresponds to a list of attendees; the apparatus further includes: The generation module is used to generate virtual participants when the private cloud server transmits meeting information to the public cloud platform, and to mix the virtual participants into the meeting's participant list. The sending module is used to send virtual participant departure instructions from the private cloud server to the public cloud platform after the meeting starts.

[0067] The sensitive data anonymization processing apparatus provided in this application embodiment, in response to a user conducting a meeting via a terminal device, creates a private cloud account for the user on a private cloud server and a public cloud account for the user on a public cloud platform, and associates the user's private cloud account and public cloud account in the private cloud server; in response to a user scheduling a meeting via a terminal device, the private cloud server creates the meeting and saves the meeting information, and simultaneously instructs the public cloud platform to create the meeting. After the public cloud platform successfully creates the meeting, it returns the meeting information to the private cloud server, which saves the meeting information and generates scheduled meeting information; in response to a user joining a meeting via a terminal device, the terminal device sends a joining request to the private cloud server to join the specified meeting. The private cloud server finds the corresponding scheduled meeting information based on the meeting number carried in the joining request, and returns the public cloud account and meeting information corresponding to the terminal device to the terminal device, so that the user can join the meeting via the terminal device based on the public cloud account and meeting information. The sensitive data anonymization processing device of this application completes the anonymization processing of sensitive data on a private server, completely cutting off the path of sensitive data to the public cloud from the source, greatly reducing the risk of sensitive data leakage, ensuring the confidentiality of sensitive data, and effectively protecting the privacy and data security of users.

[0068] like Figure 6As shown in the embodiment of this application, an electronic device 600 includes a processor 601, a memory 602, and a bus. The memory 602 stores machine-readable instructions executable by the processor 601. When the electronic device is running, the processor 601 communicates with the memory 602 via the bus, and the processor 601 executes the machine-readable instructions to perform the steps of the sensitive data anonymization processing method described above.

[0069] Specifically, the memory 602 and processor 601 mentioned above can be general-purpose memory and processor, without any specific limitations. When the processor 601 runs the computer program stored in the memory 602, it can execute the above-mentioned sensitive data anonymization processing method.

[0070] Corresponding to the above-described sensitive data anonymization method, this application embodiment also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the above-described sensitive data anonymization method.

[0071] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems and devices described above can be referred to the corresponding processes in the method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some communication interfaces; the indirect coupling or communication connection of devices or modules can be electrical, mechanical, or other forms.

[0072] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0073] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0074] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the deployment methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0075] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for anonymizing sensitive data, characterized in that, The method includes: In response to a user conducting a meeting via a terminal device, a private cloud account for the user is created on a private cloud server and a public cloud account for the user is created on a public cloud platform. The user's private cloud account and public cloud account are then associated on the private cloud server. The private cloud server stores the user's collected personal identification information. In response to the user scheduling a meeting through the terminal device, the private cloud server creates the meeting and saves the meeting information, and simultaneously instructs the public cloud platform to create the meeting. After the public cloud platform successfully creates the meeting, it returns the meeting information to the private cloud server. The private cloud server saves the meeting information and generates the scheduled meeting information. In response to the user joining the meeting via the terminal device, the terminal device sends a joining request to the private cloud server. The private cloud server finds the corresponding booked meeting information based on the meeting number carried in the joining request, and returns the public cloud account corresponding to the terminal device and the meeting information to the terminal device, so that the user can join the meeting via the terminal device based on the public cloud account and the meeting information.

2. The method according to claim 1, characterized in that, The user's personally identifiable information is collected through the following steps: In response to the user registering an account for the first time through the terminal device, the terminal device sends a login request to the private cloud server; The private cloud server receives the login request and collects and saves the user's personal identification information.

3. The method according to claim 2, characterized in that, The step of creating the user's private cloud account on a private cloud server and the user's public cloud account on a public cloud platform, and associating the user's private cloud account and public cloud account on the private cloud server, includes: The private cloud server generates a one-time session mapping token and sends an account creation request to the public cloud platform; The public cloud platform creates the public cloud account based on the account creation request, and associates the public cloud account with the user's private cloud account in the private cloud server.

4. The method according to claim 1, characterized in that, The method further includes: The validity period of the meeting is controlled based on the one-time session mapping token; wherein, the validity period of the one-time session mapping token is determined by the duration of the meeting and the dynamically randomly allocated encryption duration; In response to the end of the meeting, the one-time session mapping token is automatically invalidated.

5. The method according to claim 1, characterized in that, The private cloud server creates a meeting and saves the meeting information, while simultaneously instructing the public cloud platform to create a meeting, including: In response to the user logging in through the terminal device, a login request is sent to the private cloud server, and after the login authentication is successful on the private cloud server, the corresponding login result is returned to the terminal device. When the user schedules a meeting through the terminal device, the terminal device sends a meeting creation request to the private cloud server, and the private cloud server creates a meeting and saves the meeting information based on the meeting creation request. The private cloud server simultaneously sends a meeting request to the public cloud platform to create a specified meeting number and meeting configuration, so that the public cloud platform can create a meeting in response to the meeting request.

6. The method according to claim 1, characterized in that, The method further includes: In response to the requirement of the user's personal identification information for the target business, the corresponding personal identification information is matched in the private cloud server through the user's public cloud account, and the personal identification information is processed in multiple dimensions. Upon completion of the processing of the personal identification information, the processed personal identification information is directly returned to the terminal device.

7. The method according to claim 1, characterized in that, The meeting participant list; the method also includes: When the private cloud server transmits the meeting information to the public cloud platform, the private cloud server generates virtual participants and mixes the virtual participants into the meeting's participant list; Once the meeting begins, the private cloud server sends a departure instruction from the virtual participant to the public cloud platform.

8. A sensitive data anonymization processing device, characterized in that, The device includes: A creation module is used to respond to a user conducting meeting business through a terminal device by creating the user's private cloud account on a private cloud server and the user's public cloud account on a public cloud platform, and associating the user's private cloud account and public cloud account on the private cloud server; wherein, the private cloud server stores the collected personal identification information of the user; The reservation module is used to respond to when the user reserves a meeting through the terminal device. The private cloud server creates the meeting and saves the meeting information, and at the same time instructs the public cloud platform to create the meeting. After the public cloud platform successfully creates the meeting, it returns the meeting information to the private cloud server. The private cloud server saves the meeting information and generates the reserved meeting information. The meeting entry module is used to respond to the user joining a meeting through the terminal device. The terminal device sends a meeting entry request to the private cloud server to join the specified meeting. The private cloud server finds the corresponding booked meeting information based on the meeting number carried in the meeting entry request, and returns the public cloud account corresponding to the terminal device and the meeting information to the terminal device, so that the user can join the meeting through the terminal device based on the public cloud account and the meeting information.

9. An electronic device, characterized in that, include: The device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, they perform the steps of the sensitive data anonymization processing method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the sensitive data anonymization processing method as described in any one of claims 1 to 7.

Images