Anti-theft method and device for internet medical scene user data

Abstract

The application discloses an anti-theft method and device for user data in an internet medical treatment scene, and the method comprises the following steps: obtaining a data file access request initiated by a request initiator based on an internet hospital platform; obtaining a private link address of a user corresponding to the data file access request according to the data file access request; if the private link address does not belong to the request initiator, rejecting the data file access request; if the private link address belongs to the request initiator, generating a common valid period link according to the private link, and returning the data file accessed by the request initiator according to the common valid period link. Since the mapping between the user and the private link of the data file owned by the user is stored, the service is rejected when the private link does not belong to the request initiator of the data file access request, so that it can be ensured that only the corresponding user can access the data file, the user file is prevented from being leaked or stolen, and the data access security is improved.

Description

Technical Field

[0001] This invention relates to the field of data security technology, and in particular to a method and device for preventing theft of user data in an internet healthcare scenario. Background Technology

[0002] Internet hospital platforms are systems that provide various medical services to patients, doctors, hospitals, pharmacies, and other participants. Due to the special nature of the medical industry, relevant departments have very strict review and supervision processes for the service quality and safety of internet hospitals. Therefore, all participants are required to provide relevant and legal documents on the platform, and the platform securely and properly stores user data.

[0003] Currently, the access technologies provided by different service providers vary, but all the interfaces provided by all providers have the same problem. For example, if user A obtains the identifier of user B's file, they can obtain the validity link for accessing user B's file through the interface, and thus obtain user B's file. At this time, user B's file may be leaked or stolen, resulting in insecure access to user data. Summary of the Invention

[0004] This invention provides a method and apparatus for preventing theft of user data in internet healthcare scenarios, thereby avoiding the leakage or theft of user files and improving the security of user data access.

[0005] In a first aspect, embodiments of the present invention provide a method for preventing theft of user data in an internet healthcare scenario, the method comprising:

[0006] Obtain the data file access request initiated by the requester based on the Internet hospital platform;

[0007] Based on the data file access request, obtain the private link address of the user corresponding to the data file access request;

[0008] If the private link address does not belong to the request initiator, then the request to access the data file is rejected;

[0009] If the private link address belongs to the request initiator, a shared validity link is generated based on the private link, and the data file accessed by the request initiator is returned based on the shared validity link.

[0010] Furthermore, the step of generating a shared validity link based on the private link includes:

[0011] Based on the private link, the generateUrl interface of the basic service is called to generate a shared validity link, which is a link that can be accessed within a specified validity period and conforms to CDN rules.

[0012] Furthermore, the step of returning the data file accessed by the request initiator based on the shared validity period link includes:

[0013] Access the corresponding CDN service based on the shared validity period link;

[0014] The shared validity period links are verified through the CDN service.

[0015] If the verification passes, the data file accessed by the request initiator will be returned;

[0016] If the verification fails, access will be denied.

[0017] Furthermore, the verification of the shared validity period link through the CDN service includes:

[0018] The CDN service is used to perform validity period verification and authentication verification on the shared validity period links;

[0019] If both the validity period verification and the authentication verification are successful, the verification passes.

[0020] If the validity period verification or the authentication verification fails, the verification will not pass.

[0021] Furthermore, the data files returned to the requesting party include:

[0022] If the data file requested by the requesting party is found to be stored locally, then the data file is returned.

[0023] If the data file is not found to be saved locally, the data file will be retrieved from the OSS origin server, saved locally, and then returned to the request initiator.

[0024] Furthermore, it also includes:

[0025] Obtain the data file upload request initiated by the request initiator based on the Internet hospital platform;

[0026] Based on the file upload request, call the business system interface to obtain the upload token corresponding to the file upload request;

[0027] Based on the upload token, the upload interface is called to upload the data file to the corresponding OSS, and the private link of the data file on OSS is obtained.

[0028] Record the mapping relationship between the request initiator and the private link.

[0029] Furthermore, the business system interface is the fetchToken interface, and the upload interface is the upload interface.

[0030] Secondly, embodiments of the present invention provide an anti-theft device for user data in an internet healthcare scenario, the device comprising:

[0031] The request retrieval module is used to retrieve data file access requests initiated by the request initiator based on the Internet hospital platform;

[0032] The private link acquisition module is used to acquire the private link address of the user corresponding to the data file access request based on the data file access request.

[0033] The anti-theft module is used to reject the data file access request if the private link address does not belong to the request initiator; if the private link address belongs to the request initiator, it generates a shared validity link based on the private link and returns the data file accessed by the request initiator based on the shared validity link.

[0034] Thirdly, embodiments of the present invention provide an electronic device, the electronic device including a processor and a memory, the memory being used to store program instructions, and the processor being used to execute the computer program stored in the memory to implement any of the steps of the above-described methods for preventing theft of user data in Internet medical scenarios.

[0035] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described method for preventing theft of user data in internet medical scenarios.

[0036] In this embodiment of the invention, the requester initiates a file access request based on an internet hospital platform. Based on the file access request, the private link address corresponding to the user is obtained. If the private link address does not belong to the requester, the file access request is rejected. If the private link address belongs to the requester, a shared validity link is generated based on the private link, and the file accessed by the requester is returned based on the shared validity link. This invention stores a mapping between users and their private links to their owned files. When the private link does not belong to the requester of the file access request, the service is refused, thus ensuring that only the corresponding user can access the file, preventing user files from being leaked or stolen, and improving user data access security. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 A schematic diagram illustrating a method for preventing theft of user data in an internet healthcare scenario, provided by an embodiment of the present invention;

[0039] Figure 2 A schematic diagram illustrating the validity period link principle of Alibaba CDN provided in this embodiment of the invention;

[0040] Figure 3 This is a schematic diagram illustrating the validity period link principle of Kingsoft CDN, provided as an embodiment of the present invention.

[0041] Figure 4 A schematic diagram of a device for preventing theft of user data in an internet healthcare scenario provided by an embodiment of the present invention;

[0042] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this invention, and not all of them. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this invention.

[0044] To prevent user files from being leaked or stolen and to improve the security of user data access, this invention provides a method and device for preventing theft of user data in an internet healthcare scenario.

[0045] Example 1:

[0046] Figure 1 This invention provides a schematic diagram of a method for preventing theft of user data in an internet healthcare scenario, which includes the following steps:

[0047] S101: Obtain the data file access request initiated by the request initiator based on the Internet Hospital platform.

[0048] S102: Based on the data file access request, obtain the private link address of the user corresponding to the data file access request.

[0049] S103: Determine whether the private link address belongs to the request initiator; if not, proceed to S104; if yes, proceed to S105.

[0050] S104: Access request to data file denied.

[0051] S105: Generate a shared validity link based on the private link, and return the data file accessed by the requester based on the shared validity link.

[0052] Because the embodiments of the present invention store a mapping between users and their private links to their data files, the requesting party that does not belong to the data file access request will refuse to provide services, thereby ensuring that only the corresponding user can access the data file, preventing user files from being leaked or stolen, and improving the security of user data access.

[0053] The method for preventing theft of user data in Internet medical scenarios provided in this embodiment of the invention is applied to the client, which can be an electronic device, specifically a smart terminal, PC, tablet computer, or other such device.

[0054] The data files can be user-uploaded ID documents, medical records, health information, medication information, etc. on the internet hospital platform. ID documents include doctors' ID information, practice certificates, and other documents, and / or patients' ID information, medical insurance accounts, and other documents.

[0055] For example, when a user wants to query and display their user profile file, they can initiate an access request for that file through the internet hospital platform.

[0056] Data files belong to a specific user. For example, user A's identification data belongs to user A. In other words, the user corresponding to the data file requested can be determined based on the data file access request. Thus, based on the mapping relationship between the user and the private link address, the private link address of the user corresponding to the data file access request can be determined.

[0057] For example, if a business service record contains a private link address, the client can obtain that private link address through the business service.

[0058] If the private link address does not belong to the requesting party, the file access request will be rejected, meaning the service will be refused to the requesting party. Alternatively, an error message can be displayed to indicate that the requesting party has accessed files that do not belong to them.

[0059] If the private link address belongs to the request initiator, in one implementation of S105 above, when generating a shared validity link based on the private link, the generateUrl interface of the basic service can be called based on the private link to generate a shared validity link. The shared validity link is a link that is accessed within the specified validity period and conforms to CDN rules.

[0060] In this implementation, when returning the data file to the requester based on the shared validity link, the corresponding CDN service can be accessed; the shared validity link is verified by the CDN service; if the verification passes, the data file to the requester is returned; if the verification fails, access is denied.

[0061] As can be seen in this implementation, during the process of the client obtaining a file link through the business service, the business service can call the generateUrl interface of the basic service through the saved private link to obtain a link that is accessible for a specified validity period and conforms to CDN rules. After obtaining the CDN link that is accessible for a specified validity period, the client directly accesses the corresponding CDN service. The CDN service will verify the validity period and authentication service of the link according to the configuration rules.

[0062] For example, when verifying shared validity links through CDN services, the CDN service can be used to perform validity verification and authentication verification on the shared validity links; if both validity verification and authentication verification are successful, the verification passes; if either validity verification or authentication verification fails, the verification fails.

[0063] Different CDNs have different designs regarding link validity and authentication. Basic services need to generate valid links according to the specific CDN used. The validity link principles of Alibaba CDN and Kingsoft CDN are as follows: Figure 2 and Figure 3 As shown.

[0064] exist Figure 2 In Alibaba CDN, CDN customers can send authentication keys, timestamps, validity periods, etc., to application servers and CDN nodes. When a user accesses a page through a client, the client sends a request to the application server to access the page, and the application server authenticates the URL. The client then sends the authentication URL to the CDN node to request the resource, and the CDN node verifies the URL authentication information.

[0065] exist Figure 3In the Kingsoft CDN process, the mobile phone (workstation) obtains the upload token, the business service in the private cloud service obtains the upload token, and the basic service caches the token information. The mobile phone (workstation) uploads the file to the basic service of the private cloud service and verifies the token. The basic service verifies the token information and then uploads the file to the OSS service of the public cloud service. The mobile phone (workstation) reports the private link, and the business service saves the private link in the database. The mobile phone (workstation) queries the validity period link, the business service requests the validity period link from the basic service, the basic service verifies the mapping relationship, and then generates the validity period link and sends it to the OSS service. The mobile phone (workstation) requests the file from the CDN service of the public cloud service through the validity period link. If the CDN service verifies that the file does not exist locally, it will retrieve the file from the origin server of the OSS service.

[0066] This CDN uses timestamps and shared keys to prevent hotlinking, aiming to give each requested URL a certain "timeliness." This ensures that user content resources are not maliciously accessed or downloaded by unauthorized users during CDN distribution, thereby ensuring service security and avoiding unnecessary CDN bandwidth waste, saving costs for users. When verifying a request, the CDN node first compares the timestamp value in the URL with the current time. If it is less than the current time, it is considered expired, authentication fails, and access is denied. If it is greater than the current time, the MD5 hash value (key + URI + timestamp) in the request is compared with the MD5 hash value in the request. If they match, access is allowed; otherwise, authentication fails, and access is denied. The timestamp + shared key hotlinking prevention is globally configured and supports two types: encrypted strings in URL parameters and encrypted strings in the URL path.

[0067] In this implementation, when returning the data file accessed by the requesting party, if the data file is found to be stored locally, the data file is returned; if the data file is not stored locally, the data file is retrieved from the OSS origin server, stored locally, and then returned to the requesting party.

[0068] Storage and access are based on OSS+CDN. After setting up CDN and OSS collaboration, users upload files to OSS and then read the files through CDN. If the file is not present in CDN, it will retrieve the file from the origin server from OSS according to the configured policy and store it locally in CDN. At this time, a CDN-based validity link needs to be generated. This solution can solve the network response efficiency problem and reduce costs. In this case, the basic service can be designed to include access and authentication for different OSS and CDN providers, avoiding multiple developments by business users and uniformly solving the authentication and adaptation problem of different providers.

[0069] Storage and access are based on OSS private buckets. Before each request for a file, a valid link needs to be obtained from OSS to access the specific file. Each request to this valid link directly sends traffic to the OSS service. If the traffic from simultaneous requests is too high, OSS will experience network response efficiency issues. At the same time, the traffic cost of OSS storage services is relatively high. Therefore, it is often necessary to use CDN to accelerate static resources. At the same time, you can choose a CDN provider with lower fees to reduce costs. In this case, OSS is combined with CDN and can be adapted to different CDN services. If OSS traffic is expensive, users can choose a CDN service provider with cheaper fees to reduce costs.

[0070] In this embodiment of the invention, a mapping relationship between users and private link addresses is pre-stored, for example including the following process:

[0071] Obtain the data file upload request initiated by the requester based on the Internet hospital platform;

[0072] Based on the file upload request, call the business system interface to obtain the upload token corresponding to the file upload request;

[0073] Based on the upload token, the upload interface is called to upload the data file to the corresponding OSS, and the private link of the data file on OSS is obtained.

[0074] Record the mapping relationship between the request initiator and the private link.

[0075] In this example, the business system interface is the `fetchToken` interface, and the upload interface is the `upload` interface. In this example, the client obtains a call permission token for the basic service's `upload` interface by calling the `fetchToken` interface through the business service. The client can then use this token to directly call the basic service's `upload` interface to upload files and obtain the corresponding private link for that file on OSS. During this process, the basic service verifies the validity of the token. If valid, it uploads the file and obtains the mapping relationship between the private link and the user corresponding to the token. The client submits information containing the private link to the corresponding business service system, and the business service records the private link.

[0076] The following describes the implementation of this invention using the design process for preventing the theft of user identification information in an internet healthcare scenario. This process can solve the aforementioned problems of user identification information access security and simplify the technical access of different service providers.

[0077] In this embodiment, a third-party OSS storage service can be relied upon to create a new private bucket storage space for storing user identification documents and other files. This OSS must be able to serve as the origin server for CDN services to retrieve uploaded files. A third-party CDN service can be relied upon to accelerate file access. This requires setting the OSS in the first step as the origin server and setting the CDN storage space as a private user space to improve file security. A highly available cache server can be built to store and verify the tokens required for the upload interface. A relational database can be built, and a table T storing the mapping relationship between users and files can be created. An independent, highly available service can be built to connect to OSS and CDN for file uploads, accelerated access, etc.

[0078] Specifically, the steps include the following:

[0079] 1. Establish Service A as a basic service to provide general interfaces. The main interfaces include: the `fetchToken` interface for obtaining the upload token, the `upload` interface for uploading files to OSS, and the `generateUrl` interface for generating a time-limited access link. Users can call these interfaces when they need to upload, modify, delete, or view corresponding files.

[0080] 2. The client obtains a token for calling the basic service's `fetchToken` interface through the business service. Using this token, the client can directly call the basic service's `upload` interface to upload files and obtain the corresponding private link for that file on OSS. During this process, the basic service verifies the token's validity. If valid, it uploads the file and obtains the mapping between the private link and the user associated with the token. In this step, obtaining the token tells us which user it belongs to, and then the private link obtained after uploading also tells us which user it belongs to, thus allowing us to obtain the mapping between the private link and the user.

[0081] 3. The client submits information containing a private link to the corresponding business service system, and the business service records the private link.

[0082] 4. During the process of the client obtaining a file link through the business service, the business service calls the generateUrl interface of the basic service through the saved private link to obtain a link that is accessible for a specified validity period and conforms to CDN rules.

[0083] 5. After obtaining a valid CDN link, the client directly accesses the corresponding CDN service. The CDN service will verify the validity and authentication of the link according to the configured rules. If the link is invalid or the authentication fails, access will be refused. If it passes, the client will check if the file exists locally. If not, the client will retrieve the file from the origin server from OSS, save it locally, and then return it to the client.

[0084] Taking the example of doctors needing to upload documents such as their ID card and medical license when registering on an internet hospital platform: When uploading documents, the client calls the respective business system interface. The business system requests a valid token from basic service A. Internally, the business service interface uses this token to call the upload interface of basic service A to upload the file to the corresponding OSS. After the basic service A uploads the file, it records the mapping between the user and the private link returned by OSS. Basic service A returns the private link information to the business service, which records the user's private file link. When the client needs to display the user's information file, the business service requests the generateUrl interface of basic service A through the private link address. Basic service A will determine whether it is the current user's link. If it is, it will return a valid public link normally; otherwise, it will report an error.

[0085] Example 2:

[0086] Based on the above embodiments, Figure 4 This is a schematic diagram of a device for detecting the light transmittance of adhesive tape according to an embodiment of the present invention. The device includes:

[0087] The request acquisition module 401 is used to acquire the data file access request initiated by the request initiator based on the Internet hospital platform;

[0088] The private link acquisition module 402 is used to obtain the private link address of the user corresponding to the data file access request based on the data file access request.

[0089] The anti-theft module 403 is used to reject the data file access request if the private link address does not belong to the request initiator; if the private link address belongs to the request initiator, it generates a common validity link based on the private link and returns the data file to be accessed by the request initiator based on the common validity link.

[0090] Furthermore, the anti-theft module 403 is specifically used to call the generateUrl interface of the basic service based on the private link to generate a common validity link. The common validity link is a link that can be accessed within the specified validity period and conforms to CDN rules.

[0091] Furthermore, the anti-theft module 403 is specifically used to access the corresponding CDN service based on the shared validity period link; to verify the shared validity period link through the CDN service; if the verification passes, the data file to be accessed by the requester is returned; if the verification fails, access is denied.

[0092] Furthermore, the anti-theft module 403 is specifically used to perform validity period verification and authentication verification on the shared validity period links through CDN services; if both validity period verification and authentication verification are successful, the verification passes; if either validity period verification or authentication verification fails, the verification fails.

[0093] Furthermore, the anti-theft module 403 is specifically used to return the data file if the requesting party finds that the data file is stored locally; if the requesting party finds that the data file is not stored locally, it retrieves the data file from the OSS origin server, saves it locally, and then returns it to the requesting party.

[0094] Furthermore, it also includes: a recording module, used to obtain the document upload request initiated by the request initiator based on the Internet hospital platform; based on the document upload request, call the business system interface to obtain the upload token corresponding to the document upload request; based on the upload token, call the upload interface to upload the document to the corresponding OSS, and obtain the private link corresponding to the document on OSS; and record the mapping relationship between the request initiator and the private link.

[0095] Furthermore, the business system interface is the fetchToken interface, and the upload interface is the upload interface.

[0096] Example 3:

[0097] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Based on the above embodiments, this embodiment of the present invention also provides an electronic device, including a processor 501, a communication interface 502, a memory 503 and a communication bus 504, wherein the processor 501, the communication interface 502 and the memory 503 communicate with each other through the communication bus 504.

[0098] The memory 503 stores a computer program. When the program is executed by the processor 501, the processor 501 performs the steps of implementing the method for preventing theft of user data in the Internet medical scenario as described in the above embodiment.

[0099] The specific implementation process is described in the above embodiments, and the similarities will not be repeated.

[0100] The communication bus mentioned in the above electronic devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not mean that there is only one bus or one type of bus.

[0101] Communication interface 502 is used for communication between the above-mentioned electronic device and other devices.

[0102] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0103] The processors mentioned above can be general-purpose processors, including central processing units, network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits, field-programmable gate arrays or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0104] Example 4:

[0105] Based on the above embodiments, this invention also provides a computer-readable storage medium storing a computer program, which is executed by a processor to implement the steps of the method for preventing theft of user data in the Internet medical scenario as described in the above embodiments.

[0106] The specific implementation process is described in the above embodiments, and the similarities will not be repeated.

[0107] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0108] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0109] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0110] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0111] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for preventing theft of user data in an internet healthcare scenario, characterized in that, The method includes: Obtain the data file access request initiated by the requester based on the Internet hospital platform; Based on the data file access request, obtain the private link address of the user corresponding to the data file access request; If the private link address does not belong to the request initiator, then the request to access the data file is rejected; If the private link address belongs to the request initiator, a shared validity link is generated based on the private link, and the data file accessed by the request initiator is returned based on the shared validity link. Also includes: Obtain the data file upload request initiated by the request initiator based on the Internet hospital platform; Based on the file upload request, call the business system interface to obtain the upload token corresponding to the file upload request; Based on the upload token, the upload interface is called to upload the data file to the corresponding OSS, and the private link address of the data file on OSS is obtained. Record the mapping relationship between the request initiator and the private link address.

2. The method as described in claim 1, characterized in that, The step of generating a shared validity link based on the private link includes: Based on the private link, the generateUrl interface of the basic service is called to generate a shared validity link, which is a link that can be accessed within a specified validity period and conforms to CDN rules.

3. The method as described in claim 2, characterized in that, The data file returned to the request initiator based on the shared validity period link includes: Access the corresponding CDN service based on the shared validity period link; The shared validity period links are verified through the CDN service. If the verification passes, the data file accessed by the request initiator will be returned; If the verification fails, access will be denied.

4. The method as described in claim 3, characterized in that, The step of verifying the shared validity period link through the CDN service includes: The CDN service is used to perform validity period verification and authentication verification on the shared validity period links; If both the validity period verification and the authentication verification are successful, the verification passes. If the validity period verification or the authentication verification fails, the verification will not pass.

5. The method as described in claim 3, characterized in that, The data files returned to the requesting party include: If the data file requested by the requesting party is found to be stored locally, then the data file is returned. If the data file is not found to be saved locally, the data file will be retrieved from the OSS origin server, saved locally, and then returned to the request initiator.

6. The method as described in claim 1, characterized in that, The business system interface is the fetchToken interface, and the upload interface is the upload interface.

7. A device for preventing theft of user data in an internet healthcare scenario, characterized in that, The device includes: The request retrieval module is used to retrieve data file access requests initiated by the request initiator based on the Internet hospital platform; The private link acquisition module is used to acquire the private link address of the user corresponding to the data file access request based on the data file access request. The anti-theft module is used to reject the data file access request if the private link address does not belong to the request initiator; if the private link address belongs to the request initiator, it generates a shared validity link based on the private link and returns the data file accessed by the request initiator based on the shared validity link. It also includes: a recording module, used to obtain the document upload request initiated by the request initiator based on the Internet hospital platform; based on the document upload request, call the business system interface to obtain the upload token corresponding to the document upload request; based on the upload token, call the upload interface to upload the document to the corresponding OSS, and obtain the private link corresponding to the document on OSS; and record the mapping relationship between the request initiator and the private link.

8. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory being used to store program instructions, and the processor being used to execute the computer program stored in the memory to implement the steps of the method for preventing theft of user data in the Internet medical scenario as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, It stores a computer program, which, when executed by a processor, implements the steps of the method for preventing theft of user data in an Internet medical scenario as described in any one of claims 1-6.

Images