Resource sharing method and system based on OSS

CN113568882BActive Publication Date: 2024-11-19CHONGQING MATHEMATICIAN TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110887518.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-08-03
Publication Date
2024-11-19
Estimated Expiration
2041-08-03

AI Technical Summary

Technical Problem

[0003]而目前分享者对网盘中的资源进行分享时,通常是将分享资源的访问链接发送给接收者,而接收者通过访问链接提取资源的方式却较繁杂,并且访问链接也不易保存

Benefits of technology

[0070] The shared resources are integrated through the integration module. When multiple sharers share resources with the same recipient, the more sharers there are, the more QR codes and access links the recipient receives. Each share can be accessed individually. Extracting resources from the space becomes cumbersome and error-prone. Therefore, the shared resources of each sharer are added to the integrated space, so that the recipient can obtain all shared resources when entering the integrated space.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113568882B_ABST
    Figure CN113568882B_ABST
Patent Text Reader

Abstract

The present invention relates to the field of file sharing technology, and specifically discloses a resource sharing method and system based on OSS. An exclusive personal space is generated for users with accounts on the OSS cloud server. The sharer uploads resources to the personal space, selects resources to be shared from the personal space, sets the sharing time and whether to encrypt, and randomly generates a sharing code after encryption is selected. A shared space is generated on the OSS cloud service, the resources selected by the sharer are added to the shared space, and a QR code and an access link are generated. The recipient can access the shared space through the QR code or the access link. When the sharer chooses encryption, the sharing code needs to be entered before access. Compared with the prior art, both the QR code and the access link are adopted at the same time. The shared space can be accessed through any of the two methods. The QR code is more convenient to use. The shared space can be entered by directly scanning the QR code, and it is also easy to save.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of file sharing, and in particular to an OSS-based resource sharing method and system. Background Art

[0002] With the development and popularization of the Internet, network disk technology has been more and more widely used. Network disk, also known as network USB disk or network hard disk, is an online storage service launched by Internet companies. It allocates a certain amount of disk space for users through the server, providing users with file management functions such as file storage, access, backup, and sharing.

[0003] Currently, when a sharer shares resources in a network disk, he usually sends an access link of the shared resource to the receiver. However, the way for the receiver to extract the resource through the access link is relatively complicated, and the access link is not easy to save. Summary of the invention

[0004] The technical problem solved by the present invention is to provide an OSS-based resource sharing method, which makes it more convenient for recipients to extract and share.

[0005] The basic solution provided by the present invention is an OSS-based resource sharing method, comprising the following steps:

[0006] Resource upload step: Generate a dedicated personal space on the OSS cloud server for users with accounts and receive resources uploaded by users;

[0007] Resource sharing step: record the user who provides the shared resources as the sharer, and obtain the shared resources selected by the sharer and the sharing rules set;

[0008] Time setting step: obtaining the sharing time of the shared resources set by the sharer. When the sharer selects multiple shared resources, obtaining the sharing time set by the sharer for each shared resource;

[0009] Verification setting steps: obtain whether the sharer encrypts the shared resources, and if so, generate a random sharing code;

[0010] Link generation steps: Generate a shared space on the OSS cloud server, add shared resources to the shared space, generate a QR code and access link, delete the shared resources from the shared space after the set sharing time is reached, and delete the shared space from the OSS cloud server when the last shared resource in the shared space is deleted;

[0011] Block sharing steps: upload the QR code, access link and sharing code to the blockchain node to generate a node access key;

[0012] Link acquisition step: According to the acquisition request issued by the user through the access key, the package file of the QR code, access link and sharing code is obtained from the blockchain node;

[0013] Resource acquisition steps: obtain the user's request to access the shared space through a QR code or access link, and allow the user who issued the request to enter the shared space. If the shared resource is encrypted, it is necessary to obtain the correct sharing code entered by the user who issued the request before allowing him to enter the shared space.

[0014] The principle and advantage of the present invention are: each user with an account has an exclusive personal space on the OSS cloud server. The user can upload resources to the personal space for storage. The sharer selects the files to be shared from the personal space, generates a shared space, adds the shared resources to the shared space, and generates a QR code and access link. The time of sharing and whether to encrypt can be selected, and when there are multiple shared resources, the sharing time can be set for each shared resource respectively. After the sharing time arrives, the shared resources will be deleted from the shared space. When there are no files in the shared space, the shared space will be deleted from the OSS cloud server. The QR code, access link and sharing code are packaged and uploaded to the blockchain node, and an access key is generated. The user can obtain the QR code, access link and sharing code from the blockchain node through the access key. The user can enter the shared space by scanning the QR code or clicking the sharing link. If the sharer chooses encryption, the correct sharing code must be entered before entering the shared space. Compared with the existing technology, both QR code and access link are adopted. The shared space can be accessed by any of the two methods. The QR code is more convenient to use. The shared space can be entered by directly scanning the QR code. It is also easy to save. The QR code, access link and sharing code are uploaded to the blockchain. The distributed storage of the blockchain is used to ensure the security of the QR code, access link and sharing code; and the tamper-proof nature of the blockchain is used to ensure the authenticity of the QR code, access link and sharing code, avoiding the occurrence of false QR codes, access links and sharing codes; and when the user shares, it only needs to send the access key to the shared object, rather than sending the QR code, access link and sharing code one by one, which is more convenient.

[0015] Further, the method further comprises the following steps:

[0016] Identity binding step: Each user account corresponds to a unique identity ID. The shared resource selected by the sharer is obtained while the identity ID of the target user of the sharer is obtained. The target of the sharer is recorded as the recipient, and a list of recipient identity IDs is generated;

[0017] Mirror generation step: Generate a mirror space on the OSS cloud server while generating the shared space, and generate a mirror resource with the same format and name as the shared resource in the mirror space, and the content of the mirror resource is empty;

[0018] Authentication steps: When a user requests to access a shared space through a QR code or access link, obtain the identity ID of the current access user, and check whether the identity ID of the current access user exists in the recipient identity ID list. If so, allow the current access user to enter the shared space; if not, allow the current access user to enter the mirror space.

[0019] Each user account corresponds to a unique identity ID. When sharing, the sharer enters the identity ID of the recipient and generates a mirror space. In the mirror space, a mirror resource with the same name and format as the shared resource but empty content is generated. When the user accesses the shared space through an access link or a QR code and enters the correct sharing code, it is determined whether the user's identity ID is the recipient's identity ID. If so, the user enters the shared space, and if not, the user enters the mirror space. As a result, the QR code, access link, and sharing code are leaked in time, and users who are not recipients cannot obtain the content of the shared resources. And for the phenomenon of web crawlers crawling resources, when the web crawler crawls the leaked access link and sharing code, it enters the mirror space, and crawls the mirror file with empty content. The role of the mirror file here is that when the web crawler crawls resources, if access is directly denied, the web crawler may continue to crawl, increasing the server load, and when it crawls an empty mirror file, it will leave directly. At the same time, if the user entering the space is a real user, he can judge whether it is the resource he needs by the file name format.

[0020] Furthermore, the identity verification step further includes the following steps:

[0021] Step 1: Set up an application channel in the mirror space, which is used to obtain the sharing application and identity ID of the user entering the mirror space;

[0022] Step 2: Send the sharing application and the ID of the user who issued the sharing application to the sharer;

[0023] Step 3: Obtain whether the sharer's sharing application is approved. If so, add the received identity ID to the recipient identity list and send an approval notification to the user who issued the sharing application. If not, send a rejection notification to the user who issued the sharing application and directly deny access the next time the user issues a request to access the shared space.

[0024] If a web crawler enters the mirror space, it will leave after crawling the mirror resources. If a real user enters the mirror space, it means that the user has certain needs for the resources in the shared space and has searched on the Internet to find the leaked QR code, access link and sharing code. An application channel is set up in the mirror space. Users with needs can send sharing applications and their identity IDs to the sharer through the application channel of the mirror space. The sharer can choose whether to add the user as a receiver. After adding, the user can enter the shared space. This gives users who have needs for shared resources but are not receivers the opportunity to apply for access rights to shared resources.

[0025] Furthermore, the identity verification step further includes the following steps:

[0026] Step 3: When the user enters the mirror space, a record is made;

[0027] Step 4: According to the preset number threshold, obtain the user ID whose number of times entering the mirror space exceeds the number threshold within a unit time, add an abnormal label to the identity ID, and deny access to any shared space for users with abnormal ID labels.

[0028] For users who normally obtain resources, they only obtain the resources they currently want to obtain, so the number of times they enter the mirror space will not exceed the threshold. Users who obtain resources abnormally will look for QR codes, access links and sharing codes of various resource sharing spaces when obtaining resources, and increase the base number of sharing applications by casting a wide net. There may be uninformed sharers who obtain resources through the applications of users who obtain resources abnormally. Therefore, an abnormal label is added to the identity ID that enters the mirror space more than the threshold number of times per unit time, so that it will be denied access when accessing any shared space, so that it can no longer send sharing applications to sharers, and even if a sharer approves his sharing application, he cannot enter the shared space.

[0029] Further, the method further comprises the following steps:

[0030] Permission setting steps: obtain the operation permissions for shared resources set by the sharer for different recipients, and bind the set operation permissions to the recipient's identity ID;

[0031] Permission implementation steps: When the recipient enters the shared space, he / she is provided with operation permissions for shared resources based on the operation permissions bound to his / her identity ID.

[0032] Set operation permissions for recipients and bind the operation permissions to the recipient's identity ID. You can set different operation permissions for different recipients. When the operation permissions of the shared resources provided by the sharer to multiple recipients overlap, there is no need to generate a separate shared space for each recipient. You only need to put all shared resources in one shared space and set the operation permissions for different recipients.

[0033] The permission setting step includes the following steps:

[0034] Step 1: Obtain the sharer's operating permissions for different recipients of a single shared resource;

[0035] Step 2: Obtain the sharer's operating permissions for one or more shared resources set for different recipients.

[0036] For different recipients, you can set operation permissions for parts of a single shared resource, and set operation permissions for one or more shared resources among multiple shared resources.

[0037] Furthermore, it also includes a resource integration step: according to a preset time period and source threshold, when the user's identity ID is added to the recipient identity ID lists of multiple sharers within the time period, and the number of added recipient identity ID lists is greater than the source threshold, an integrated space is generated, and all shared resources authorized by all sharers to the user are added to the integrated space. The user can enter the integrated space through any sharer's QR code or access link.

[0038] The time period is limited by the time period, and the source threshold is used to limit the number of sharers. When multiple sharers share with the same receiver within a time period, an integrated space is generated, and the resources authorized by all sharers to this receiver are added to the integrated space. Because when there are too many sharers, the receiver will receive more QR codes and access links. It will become troublesome and error-prone to visit each shared space individually to extract resources. Therefore, the shared resources of each sharer are added to the integrated space, so that the receiver can obtain all shared resources when entering the integrated space.

[0039] The present invention also provides an OSS-based resource sharing method and system, the system uses the above-mentioned OSS-based resource sharing method, and the system includes the following contents:

[0040] The resource sharing system based on OSS includes an OSS cloud server and a client, wherein the client includes a resource uploading module, a resource sharing module, and a resource acquiring module, and the OSS cloud server includes a space generating module, a time setting module, a resource deleting module, a verification and encryption module, a block uploading module, a link acquiring module, and a resource acquiring module;

[0041] Resource upload module: used to upload resources to personal space;

[0042] Resource sharing module: used to select shared resources from the personal space and set sharing rules;

[0043] Space generation module: used to generate a shared space when sharing resources, add shared resources to the shared space, and generate a QR code and access link;

[0044] Time setting module, used to set sharing time when sharing;

[0045] The resource deletion module is used to delete the shared resources from the shared space after the sharing time is reached;

[0046] Verification and encryption module: used to set whether to encrypt shared resources. If yes, a sharing code will be randomly generated. When accessing the shared space through a QR code or access link, you need to enter the correct sharing code to enter the shared space.

[0047] Block upload module: used to upload the QR code, access link and sharing code to the blockchain node and generate the node access key;

[0048] Link acquisition module: used to obtain the package file of QR code, access link and sharing code from the blockchain node through the acquisition request issued by the access key;

[0049] Resource acquisition module: used to access the shared space through a QR code or access link, and add shared resources in the shared space to the personal space or download them directly.

[0050] The sharer uploads resources to the personal space through the resource upload module, and selects shared resources from the personal space through the resource sharing module and sets sharing rules. The space generation module generates a shared space in the OSS cloud server, adds shared resources to the shared space, and generates a QR code and access link. The shared space can be entered through the QR code or access link. The sharing time is set through the time setting module. When there are multiple shared resources selected, different sharing times can be set for different resources. After the set sharing time is reached, the resource deletion module deletes the shared resources from the shared space. The shared resources are encrypted through the verification encryption module, and a sharing code is randomly generated. Users need to enter the correct sharing code to enter the shared space. Compared with the prior art, both QR codes and access links are used. The shared space can be accessed through any of the two methods, and the QR code is more convenient to use. The shared space can be entered by directly scanning the QR code, and it is also easy to save.

[0051] Furthermore, the OSS cloud server also includes an identity binding module, a mirror space management module, an identity authentication module, a login record module, and an abnormal marking module, and the client also includes an identity entry module and an application management module;

[0052] Identity binding module: used to generate a unique identity ID for the user account;

[0053] Identity entry module: used to input the recipient's identity ID when sharing and generate a recipient's identity ID list;

[0054] The space generation module is also used to generate a mirror space while generating the shared space;

[0055] Mirror space management module: used to generate a mirror resource in the mirror space with the same format and name as the shared resource, and the content of the mirror resource is empty;

[0056] Identity verification module: When a user accesses a shared space through a QR code or access link and enters the correct sharing code, the user's identity ID is obtained and compared to see if the user's identity ID exists in the recipient's identity ID list. If so, the user enters the shared space; if not, the user enters the mirror space.

[0057] The mirror space management module is also used to generate an application channel in the mirror space, and the application channel is used to send a sharing application and a user identity ID to the sharer;

[0058] Application management module: used to select whether to approve the application after receiving the sharing application;

[0059] Login record module: used to record the number of times a user enters the mirror space;

[0060] Abnormal marking module: A preset number threshold is used to bind the user ID that enters the mirror space more than the number threshold per unit time to an abnormal label.

[0061] The identity binding module generates a unique identity ID for each user. When sharing, the sharer enters the recipient's identity ID through the identity entry module and generates a list of recipient identity IDs. The space generation module generates a mirror space while generating a shared space, and generates empty mirror resources in the mirror space. After the user enters the correct sharing code, the identity ID of the current user is obtained, and it is determined whether its identity ID exists in the recipient's identity ID list. If it exists, it enters the shared space, and if it does not exist, it enters the mirror space. In addition, there is an application channel in the mirror space, through which the sharing application and its own identity ID can be sent to the sharer. The sharer receives the sharing application through the application management module and chooses whether to pass it. And every time a user enters the space, the login record module records it once, and the abnormal marking module is used to bind the user identity ID who enters the mirror space more than the number of times per unit time to an abnormal label according to the preset number of times threshold.

[0062] By setting up a mirror space, the QR code, access link and sharing code are leaked in time, and users who are not recipients cannot obtain the content of the shared resources. And when the web crawler crawls the leaked access link and sharing code, it enters the mirror space, and crawls the mirror file with empty content. And if it is a web crawler that enters the mirror space, it will leave after crawling the mirror resource. If it is a real user who enters the mirror space, it has a certain demand for the resources in the shared space, and has searched on the Internet to find the leaked QR code, access link and sharing code. By setting up an application channel, users who have a demand for shared resources but are not recipients have the opportunity to apply for access rights to shared resources.

[0063] For users who normally obtain resources, they only obtain the resources they currently want to obtain, so the number of times they enter the mirror space will not exceed the number threshold. Users who obtain resources abnormally will look for QR codes, access links and sharing codes of various resource sharing spaces when obtaining resources. Therefore, an abnormal tag is added to the identity ID that enters the mirror space more than the number threshold per unit time, so that it will be denied access to any shared space, so that it can no longer send sharing applications to sharers, and even if a sharer approves his sharing application, he cannot enter the shared space.

[0064] Furthermore, the client further includes a permission setting module, and the permission setting module includes a single permission setting module and multiple permission setting modules;

[0065] Permission setting module: used to set the operating permissions for the recipient to share resources and bind the operating permissions to the recipient's identity ID;

[0066] Single permission setting module: used to set operation permissions for a single resource, and set operation permissions for different recipients on different parts of the same shared resource;

[0067] Multiple permission setting modules: used to set operation permissions for multiple resources, and set operation permissions for one or more shared resources among multiple shared resources for different recipients;

[0068] The server also includes an integration module, which has a preset time period and a source threshold. When the user's identity ID is added to the recipient ID lists of multiple sharers within the time period, and the number of added recipient ID lists is greater than the source threshold, the shared resources authorized by all sharers to the user are integrated. The space generation module generates an integrated space when integrating the shared resources to store the integrated resources.

[0069] Through the permission setting module, different operating permissions are set for different recipients. And for different recipients, operating permissions can be set for parts of a single shared resource, and operating permissions can be set for one or more shared resources among multiple shared resources.

[0070] Shared resources are integrated through the integration module. When multiple sharers share resources to the same receiver, the more sharers there are, the more QR codes and access links the receiver will receive. It will become troublesome and error-prone to access each shared space individually to extract resources. Therefore, the shared resources of each sharer are added to the integrated space so that the receiver can obtain all shared resources when entering the integrated space. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] Figure 1 It is a flowchart of a resource sharing method based on OSS according to an embodiment of the present invention;

[0072] Figure 2 The figure is a flowchart of the mirror space of the resource sharing method based on OSS according to an embodiment of the present invention. DETAILED DESCRIPTION

[0073] The following is further described in detail through specific implementation methods:

[0074] The embodiment is basically as shown in the attached Figure 1 As shown:

[0075] In the OSS-based resource sharing method of this embodiment, an exclusive personal space is generated in the OSS cloud server for users with accounts. Users can upload resources to the personal space. When the sharer shares the resources in the personal space, he selects the resources to be shared in the personal space and sets the sharing rules. He can also select one or more resources to share at the same time. The sharing rule setting includes time setting and verification setting. The time setting is to set the sharing time of the shared resources. In this embodiment, the optional sharing time includes 7 days, 30 days and indefinite. When there are multiple shared resources selected by the sharer, the sharer can also set the sharing time for each shared resource. The verification setting is for the sharer to set whether encryption is required. If yes, a sharing code consisting of numbers and letters is randomly generated. After the sharing rule setting is completed, a shared space is generated on the OSS cloud server, the shared resources selected by the sharer are added to the shared space, and a QR code and access link are generated.

[0076] Then, the QR code, access link and sharing code are packaged and uploaded to the blockchain node, and an access key is generated. The sharer sends the access key to the recipient. When the recipient uses the access key to access, the package file of the QR code, access link and sharing code is obtained from the blockchain node. The recipient can access the shared space by scanning the QR code or clicking the access link, and download the shared resources in the shared space or add them to his personal space. When the set sharing time is reached, the shared resources will be deleted from the shared space. When the last shared resource is deleted from the shared space, the shared space will be deleted from the OSS cloud server.

[0077] In addition, in order to ensure that the resources shared by the sharer are not leaked, such as Figure 2 The present invention also proposes to correspond each user account to a unique identity ID. In this embodiment, the identity ID is a digital ID. When the sharer chooses encryption, he needs to enter the identity ID of the recipient and generate a list of the recipient's identity IDs. In addition, when generating a shared space, a mirror space is generated, and a mirror resource with the same format and name as the shared resource but empty content is generated in the mirror space, and the order and file structure of the mirror resource in the mirror space are the same as the order and file structure of the shared resource in the shared space.

[0078] When a user accesses the space through a QR code or access link and enters the correct sharing code, the identity ID of the currently accessing user is obtained and compared to see if the identity ID is in the recipient identity ID list. If it is, the user enters the shared space; if not, the user enters the shared space. This prevents the user from entering the mirror space when the QR code, access link, or sharing code is leaked. In addition, by setting up mirror resources with empty content in the mirror space, when a web crawler obtains the leaked access link and sharing code from the Internet and crawls the shared resources, it only crawls mirror resources with empty content from the mirror space.

[0079] In addition, there is an application channel in the mirror space. Users who enter the mirror space can send their identity ID and sharing application to the sharer through the application channel, explaining the reasons and reasons for wanting to obtain resources. If the person entering the mirror space is a real user and has a certain demand for the shared resources in the shared space, he will obtain the QR code or access link and sharing code of the shared space after searching on the Internet in a certain way, so the application channel is set up to allow him to apply for access rights from the sharer. If the person entering the mirror space is a web crawler, it will directly crawl the empty mirror file and leave directly. Therefore, a channel for obtaining resources is added for users with needs.

[0080] When the sharer receives the sharing application, he can choose whether to add the user who sent the sharing application to the recipient identity ID list. If he chooses yes, the user's identity ID will be added to the recipient identity ID list and a permission notification will be sent to the user. If he chooses no, a rejection notification will be sent to the user, and the user will be directly denied access when he tries to access the app again through the QR code or access link.

[0081] And every time a user enters the mirror space, a record is made, and according to the preset number threshold, the user ID whose number of times entering the mirror space exceeds the number threshold in the unit time is obtained, and an abnormal label is added to it. For users with abnormal ID labels, access will be directly denied when they access any shared space. In this embodiment, the unit time is one hour, and the number threshold is 6 times. For users who normally obtain resources, after entering the mirror space and sending a sharing application, they will first wait for the processing result of the sharer. If the application is passed, they will not search for the access link or QR code of other shared spaces. If the application is not passed, they will continue to search. There is also time to wait for the feedback of the sharer. Therefore, the number of times entering the mirror space within an hour will not exceed the number threshold. For users who obtain resources abnormally, they will constantly enter the mirror space through the QR code or access link, send sharing applications, and obtain more resources by increasing the base number of requests sent. Therefore, users who obtain resources abnormally will enter the mirror space within an hour. The number of times exceeds the threshold. An abnormal tag is added to the identity ID of a user who enters a space more than six times within an hour, so that he will be denied access to any shared space. Even if an uninformed sharer approves the sharing application of a user who obtains resources abnormally, the user who obtains resources abnormally will not be able to enter the shared space to obtain resources.

[0082] This embodiment also discloses an OSS-based resource sharing system using the above OSS-based resource sharing method, and the system includes the following contents:

[0083] It includes an OSS cloud server and a client, wherein the client includes a resource upload module, a resource sharing module, and a resource acquisition module, and the OSS cloud server includes a space generation module, a time setting module, a resource deletion module, a verification and encryption module, a block upload module, a link acquisition module, and a resource acquisition module;

[0084] Resource upload module: used to upload resources to personal space;

[0085] Resource sharing module: used to select shared resources from the personal space and set sharing rules;

[0086] Space generation module: used to generate a shared space when sharing resources, add shared resources to the shared space, and generate a QR code and access link;

[0087] Time setting module, used to set sharing time when sharing;

[0088] The resource deletion module is used to delete the shared resources from the shared space after the sharing time is reached;

[0089] Verification and encryption module: used to set whether to encrypt shared resources. If yes, a sharing code will be randomly generated. When accessing the shared space through a QR code or access link, you need to enter the correct sharing code to enter the shared space.

[0090] Block upload module: used to upload the QR code, access link and sharing code to the blockchain node and generate the node access key;

[0091] Link acquisition module: used to obtain the package file of QR code, access link and sharing code from the blockchain node through the acquisition request issued by the access key;

[0092] Resource acquisition module: used to access the shared space through a QR code or access link, and add shared resources in the shared space to the personal space or download them directly.

[0093] The OSS cloud server also includes an identity binding module, a mirror space management module, an identity authentication module, a login record module, and an abnormal marking module, and the client also includes an identity entry module and an application management module;

[0094] Identity binding module: used to generate a unique identity ID for the user account;

[0095] Identity entry module: used to input the recipient's identity ID when sharing and generate a recipient's identity ID list;

[0096] The space generation module is also used to generate a mirror space while generating the shared space;

[0097] Mirror space management module: used to generate a mirror resource in the mirror space with the same format and name as the shared resource, and the content of the mirror resource is empty;

[0098] Identity verification module: When a user accesses a shared space through a QR code or access link and enters the correct sharing code, the user's identity ID is obtained and compared to see if the user's identity ID is in the recipient ID list. If so, the user enters the shared space; if not, the user enters the mirror space.

[0099] The mirror space management module is also used to generate an application channel in the mirror space, and the application channel is used to send a sharing application and a user identity ID to the sharer;

[0100] Application management module: used to select whether to approve the application after receiving the sharing application;

[0101] Login record module: used to record the number of times a user enters the mirror space;

[0102] Abnormal marking module: A preset number threshold is used to bind the user ID that enters the mirror space more than the number threshold per unit time to an abnormal label.

[0103] Embodiment 2

[0104] The difference between this embodiment and embodiment 1 is that when setting sharing rules, the sharer can also set the receiver's operating permissions for the shared resources. In this embodiment, the operating permissions include save permissions and modify permissions. The save permissions allow the receiver to only download the shared resources from the shared space or add the shared resources to the personal space; the modify permissions allow the receiver to modify the shared resources in the shared space.

[0105] In addition, the sharer can set operation permissions for a single shared resource and set different operation permissions for different recipients on the same shared resource. For example, for a document resource with a total of 20 pages, the recipients include user A, user B and user C. The sharer sets the full-text save permission for user A, the modification permission for the first 10 pages for user B, and the modification permission for the last 10 pages for user C.

[0106] In addition, the sharer can also set operation permissions for multiple shared resources, and set operation permissions for one or more shared resources among multiple shared resources for different sharers. For example, the sharer shares three shared resources, including the first resource, the second resource, and the third resource. The save permission of the first resource and the second resource is set for user A, the modification permission of the second resource and the third resource is set for user B, and the save permission of the third resource is set for user C. Therefore, when the resources shared by the sharer for multiple recipients have intersections, only one QR code and access link are needed, instead of multiple QR codes and access links.

[0107] This embodiment also discloses an OSS-based resource sharing system using the above OSS-based resource sharing method, and the system includes the following contents:

[0108] The client further includes a permission setting module, and the permission setting module includes a single permission setting module and multiple permission setting modules;

[0109] Permission setting module: used to set the operating permissions for the recipient to share resources and bind the operating permissions to the recipient's identity ID;

[0110] Single permission setting module: used to set operation permissions for a single resource, and set operation permissions for different recipients on different parts of the same shared resource;

[0111] Multiple permission setting modules: used to set operation permissions for multiple resources, and to set operation permissions for one or more shared resources among multiple shared resources for different recipients.

[0112] Embodiment 3

[0113] The difference between this embodiment and the second embodiment is that a time period and a source threshold are set. During the time period, the user's identity ID is added to the recipient ID lists of multiple sharers, and when the number of added recipient ID lists is greater than the source threshold, an integrated space is generated, and all shared resources authorized by all sharers to the user are added to the integrated space. The user can enter the integrated space through any sharer's QR code or access link.

[0114] Specifically, in this embodiment, the time period is three days, and the source threshold is 10. If more than ten sharers share with the same receiver within three days, the receiver needs to enter 10 shared spaces to operate the shared resources, which is troublesome and prone to errors. Therefore, an integrated space is generated, and all the shared resources authorized by the sharers to the receiver are added to the integrated space. For example, a sharer's shared space has three shared resources, and the sharer is set to have the permission to save only the first resource, then only the first resource is added to the integrated space. After adding the resource to the integrated space, the receiver enters the integrated space when accessing the shared space through any sharer's QR code or access link. This reduces the intermediate process of the receiver entering multiple shared spaces to operate.

[0115] This embodiment also discloses an OSS-based resource sharing system using the above OSS-based resource sharing method, and the system includes the following contents:

[0116] The server also includes an integration module, which has a preset time period and a source threshold. When the user's identity ID is added to the recipient ID lists of multiple sharers within the time period, and the number of added recipient ID lists is greater than the source threshold, the shared resources authorized by all sharers to the user are integrated. The space generation module generates an integrated space when integrating the shared resources to store the integrated resources.

[0117] The above are only embodiments of the present invention. Common knowledge such as the known specific structures and characteristics in the scheme is not described in detail here. Ordinary technicians in the relevant field know all the common technical knowledge in the technical field to which the invention belongs before the application date or priority date, can obtain all the existing technologies in the field, and have the ability to apply conventional experimental means before that date. Ordinary technicians in the relevant field can improve and implement this scheme in combination with their own abilities under the enlightenment given by this application. Some typical known structures or known methods should not become obstacles for ordinary technicians in the relevant field to implement this application. It should be pointed out that for those skilled in the art, without departing from the structure of the present invention, several deformations and improvements can be made, which should also be regarded as the scope of protection of the present invention, and these will not affect the effect of the implementation of the present invention and the practicality of the patent. The scope of protection required by this application shall be based on the content of its claims, and the specific implementation methods and other records in the specification can be used to interpret the content of the claims.

Claims

1. The resource sharing method based on OSS is characterized by: The following steps are involved: Resource upload step: Generate a dedicated personal space on the OSS cloud server for users with accounts and receive resources uploaded by users; Resource sharing step: record the user who provides the shared resources as the sharer, and obtain the shared resources selected by the sharer and the sharing rules set; Time setting step: obtaining the sharing time of the shared resources set by the sharer. When the sharer selects multiple shared resources, obtaining the sharing time set by the sharer for each shared resource; Verification setting steps: obtain whether the sharer encrypts the shared resources, and if so, generate a random sharing code; Link generation steps: Generate a shared space on the OSS cloud server, add shared resources to the shared space, generate a QR code and access link, delete the shared resources from the shared space after the set sharing time is reached, and delete the shared space from the OSS cloud server when the last shared resource in the shared space is deleted; Block sharing steps: upload the QR code, access link and sharing code to the blockchain node to generate a node access key; Link acquisition step: According to the acquisition request issued by the user through the access key, the package file of the QR code, access link and sharing code is obtained from the blockchain node; Resource acquisition step: obtain the user's request to access the shared space through the QR code or access link, and allow the user who issued the request to enter the shared space. If the shared resource is encrypted, the user who issued the request needs to enter the correct sharing code before being allowed to enter the shared space; The following steps are also included: Identity binding step: Each user account corresponds to a unique identity ID. The shared resource selected by the sharer is obtained while the identity ID of the target user of the sharer is obtained. The target of the sharer is recorded as the recipient, and a list of recipient identity IDs is generated; Mirror generation step: Generate a mirror space on the OSS cloud server while generating the shared space, and generate a mirror resource with the same format and name as the shared resource in the mirror space, and the content of the mirror resource is empty; Identity verification step: when a user sends a request to access a shared space through a QR code or access link, obtain the identity ID of the current access user, and check whether the identity ID of the current access user exists in the recipient identity ID list. If so, allow the current access user to enter the shared space; if not, allow the current access user to enter the mirror space; The identity verification step further comprises the following steps: Step 1: Set up an application channel in the mirror space, which is used to obtain the sharing application and identity ID of the user entering the mirror space; Step 2: Send the sharing application and the ID of the user who issued the sharing application to the sharer; Step 3: Obtain whether the sharer's sharing application is approved. If so, add the received identity ID to the recipient identity list and send an approval notification to the user who issued the sharing application. If not, send a rejection notification to the user who issued the sharing application and directly deny access the next time the user issues a request to access the shared space.

2. The OSS-based resource sharing method according to claim 1, characterized in that: The identity verification step further comprises the following steps: Step 3: When the user enters the mirror space, a record is made; Step 4: According to the preset number threshold, obtain the user ID whose number of times entering the mirror space exceeds the number threshold within a unit time, add an abnormal label to the identity ID, and deny access to any shared space for users with abnormal ID labels.

3. The OSS-based resource sharing method according to claim 2, characterized in that: The following steps are also included: Permission setting steps: obtain the operation permissions for shared resources set by the sharer for different recipients, and bind the set operation permissions to the recipient's identity ID; Permission implementation steps: When the recipient enters the shared space, he / she is provided with operation permissions for shared resources based on the operation permissions bound to his / her identity ID.

4. The OSS-based resource sharing method according to claim 3 is characterized in that: The permission setting step includes the following steps: Step 1: Obtain the sharer's operating permissions for different recipients of a single shared resource; Step 2: Obtain the sharer's operating permissions for one or more shared resources set for different recipients.

5. The OSS-based resource sharing method according to claim 4 is characterized in that: It also includes a resource integration step: according to a preset time period and source threshold, when the user's identity ID is added to the recipient identity ID lists of multiple sharers within the time period, and the number of added recipient identity ID lists is greater than the source threshold, an integrated space is generated, and all shared resources authorized by all sharers to the user are added to the integrated space. The user can enter the integrated space through any sharer's QR code or access link.

6. An OSS-based resource sharing system, using the OSS-based resource sharing method according to claim 5, characterized in that: It includes an OSS cloud server and a client, wherein the client includes a resource upload module, a resource sharing module, and a resource acquisition module, and the OSS cloud server includes a space generation module, a time setting module, a resource deletion module, a verification and encryption module, a block upload module, a link acquisition module, and a resource acquisition module; Resource upload module: used to upload resources to personal space; Resource sharing module: used to select shared resources from the personal space and set sharing rules; Space generation module: used to generate a shared space when sharing resources, add shared resources to the shared space, and generate a QR code and access link; Time setting module, used to set sharing time when sharing; The resource deletion module is used to delete the shared resources from the shared space after the sharing time is reached; Verification and encryption module: used to set whether to encrypt shared resources. If yes, a sharing code will be randomly generated. When accessing the shared space through a QR code or access link, you need to enter the correct sharing code to enter the shared space. Block upload module: used to package and upload the QR code, access link and sharing code to the blockchain node, and generate the node access key; Link acquisition module: used to obtain the package file of QR code, access link and sharing code from the blockchain node through the acquisition request issued by the access key; Resource acquisition module: used to access the shared space through a QR code or access link, and add shared resources in the shared space to the personal space or download them directly.

7. The OSS-based resource sharing system according to claim 6, characterized in that: The OSS cloud server also includes an identity binding module, a mirror space management module, an identity authentication module, a login record module, and an abnormal marking module, and the client also includes an identity entry module and an application management module; Identity binding module: used to generate a unique identity ID for the user account; Identity entry module: used to input the recipient's identity ID when sharing and generate a recipient's identity ID list; The space generation module is also used to generate a mirror space while generating the shared space; Mirror space management module: used to generate a mirror resource in the mirror space with the same format and name as the shared resource, and the content of the mirror resource is empty; Identity verification module: When a user accesses a shared space through a QR code or access link and enters the correct sharing code, the user's identity ID is obtained and compared to see if the user's identity ID exists in the recipient's identity ID list. If so, the user enters the shared space; if not, the user enters the mirror space. The mirror space management module is also used to generate an application channel in the mirror space, and the application channel is used to send a sharing application and a user identity ID to the sharer; Application management module: used to select whether to approve the application after receiving the sharing application; Login record module: used to record the number of times a user enters the mirror space; Abnormal marking module: A preset number threshold is used to bind the user ID that enters the mirror space more than the number threshold in a unit time to an abnormal label.

8. The OSS-based resource sharing system according to claim 7, characterized in that: The client further includes a permission setting module, and the permission setting module includes a single permission setting module and multiple permission setting modules; Permission setting module: used to set the operating permissions for the recipient to share resources and bind the operating permissions to the recipient's identity ID; Single permission setting module: used to set operation permissions for a single resource, and set operation permissions for different recipients on different parts of the same shared resource; Multiple permission setting modules: used to set operation permissions for multiple resources, and set operation permissions for one or more shared resources among multiple shared resources for different recipients; The server also includes an integration module, which has a preset time period and a source threshold. When the user's identity ID is added to the recipient ID lists of multiple sharers within the time period, and the number of added recipient ID lists is greater than the source threshold, the shared resources authorized by all sharers to the user are integrated. The space generation module generates an integrated space when integrating the shared resources to store the integrated resources.