File sharing method and device

Abstract

Embodiments of the present application disclose a file sharing method and apparatus, relating to the field of communication technologies. The file sharing method includes: in response to a request to share a file of a first user with a second user, obtaining the file of the first user; wherein the file includes propagation chain data, and the propagation chain data is data formed by each user through which the file passes during propagation; obtaining a propagation rule from the propagation chain data, wherein the propagation rule is a sharing rule set by each user when sharing a file; and using the propagation rule in the file to control the file sharing of the first user to the second user. Thus, by adopting the embodiments of the present application, the scope of file sharing can be controlled to avoid malicious or illegal propagation of the file.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies, and in particular, to a file sharing method and apparatus. Background Art

[0002] With the development of Internet technologies, file sharing has become a common business form. Users can spread and share files based on the relationship chains in social applications, such as photo sharing based on friend relationships and document sharing based on colleague relationships.

[0003] In practical applications, after a file is shared with other users, the recipient can download and view the content of the file. At the same time, the recipient can also share the file with other recipients in some ways, such as sharing after copying and sharing again after downloading and uploading. The above sharing behaviors may lead to the risk of the scope of file sharing being expanded. After the file is shared, the user cannot control the subsequent dissemination and forwarding of the file. Summary of the Invention

[0004] The embodiments of the present application provide a file sharing method and apparatus. The embodiments of the present application propose a technical solution that can be used to control the scope of file sharing and can avoid malicious or illegal dissemination of files.

[0005] In a first aspect, the embodiments of the present application provide a file sharing method. The file sharing method includes: in response to a request to share a file of a first user with a second user, obtaining the file of the first user; wherein the file includes propagation chain data, and the propagation chain data is data formed by each user through which the file passes during propagation; obtaining a propagation rule from the propagation chain data, where the propagation rule is a sharing rule set by each user when sharing a file; and using the propagation rule in the file to control the file sharing of the first user to the second user.

[0006] Based on such a design, the file sharing of the first user to the second user can be controlled correspondingly according to the propagation rules set by the user. Thus, the file sharing method of the embodiments of the present application can be used to control the scope of file sharing and can avoid malicious or illegal dissemination of files.

[0007] In a possible design, when the first user shares a file with the second user, the propagation rule is to prohibit the second user from tampering with the file. Based on such a design, malicious tampering of the file during sharing can be avoided.

[0008] In a possible design, when the first user shares a file with the second user, the propagation rule is to prohibit the second user from sharing the file with a third user. Based on such a design, the user can control the file sharing scope and avoid malicious or illegal propagation.

[0009] In a possible design, when the first user shares a file with the second user, the propagation rule is to limit the number of users who receive the file. Based on such a design, the user can control the file sharing scope and avoid malicious or illegal propagation.

[0010] In a possible design, the second user downloads the content and propagation chain data of the file through an application in the user device and saves the content and propagation chain data of the file in a secure sandbox. Based on such a design, the files saved in the secure sandbox are only accessible to the application to which they belong or other applications authorized by the application, thereby ensuring that files including propagation chain data are not stolen or tampered with by third-party applications.

[0011] In a possible design, when the second user copies the file into a new file, the application copies the file including the file content and the propagation chain data in the secure sandbox. Based on such a design, when the second user downloads a file containing propagation chain data and the file is copied, the propagation chain data is also copied.

[0012] In a possible design, when the second user uploads the new file to the server, the application uploads both the file content and the propagation chain data to the server. Based on such a design, when the second user uploads a file containing a propagation chain and the file is copied, the propagation chain data is also uploaded.

[0013] In a second aspect, an embodiment of the present application further provides a file sharing device. The file sharing device includes: an acquisition unit configured to acquire the file of the first user in response to a request to share the file of the first user with the second user; wherein the file includes propagation chain data, and the propagation chain data is data formed by each user through which the file passes during propagation; the acquisition unit is further configured to acquire a propagation rule from the propagation chain data, wherein the propagation rule is a sharing rule set by each user when sharing a file; a control unit configured to use the propagation rule in the file to control the file sharing of the first user to the second user.

[0014] Based on such a design, the file sharing of the first user to the second user can be correspondingly controlled according to the propagation rule set by the user. Thus, the file sharing method of the embodiment of the present application can be used to control the file sharing scope and avoid malicious or illegal propagation of the file.

[0015] In a possible design, the control unit is further configured to prohibit a second user from tampering with a file according to the propagation rule. Based on such a design, malicious tampering of the file during sharing can be avoided.

[0016] In a possible design, the control unit is further configured to prohibit the second user from sharing the file with a third user according to the propagation rule. Based on such a design, a user can control the scope of file sharing and avoid malicious or illegal propagation.

[0017] In a possible design, the control unit is further configured to limit the number of users receiving the file according to the propagation rule. Based on such a design, a user can control the scope of file sharing and avoid malicious or illegal propagation.

[0018] In an embodiment of the present application, when receiving a request in response to sharing a file of a first user with a second user, the file of the first user can be obtained, and the propagation rule can be obtained from the propagation chain data of the file, and then the propagation rule in the file can be used to control the file sharing of the first user with the second user. In this way, the scope of file sharing can be controlled, and malicious or illegal propagation of the file can be avoided. Description of the Drawings

[0019] Figure 1 It is a schematic diagram of a file sharing provided for an embodiment of the present application.

[0020] Figure 2 It is another schematic diagram of the file sharing provided for an embodiment of the present application.

[0021] Figure 3 It is another schematic diagram of the file sharing provided for an embodiment of the present application.

[0022] Figure 4 It is a schematic diagram of a file sharing process provided for an embodiment of the present application.

[0023] Figure 5 It is a schematic flow diagram of a file sharing method provided for an embodiment of the present application.

[0024] Figure 6 It is another schematic diagram of a file sharing process provided for an embodiment of the present application.

[0025] Figure 7 It is a schematic flow diagram of a file sharing method of another embodiment provided for an embodiment of the present application.

[0026] Figure 8 It is another schematic diagram of a file sharing process provided for an embodiment of the present application.

[0027] Figure 9Another schematic diagram of the file sharing process provided by the embodiment of the present application.

[0028] Figure 10 Another schematic diagram of the file sharing process provided by the embodiment of the present application.

[0029] Figure 11 Schematic structural diagram of a file sharing device provided by the embodiment of the present application.

[0030] Figure 12 Another schematic structural diagram of a file sharing device provided by the embodiment of the present application.

[0031] Description of main component symbols

[0032] First user 100

[0033] Second user 200

[0034] Server 300

[0035] File sharing devices 500, 600

[0036] Acquisition unit 501

[0037] Control unit 502

[0038] Processor 601

[0039] Memory 602

[0040] Communication interface 603

[0041] The following specific embodiments will further illustrate the present application in conjunction with the above-mentioned drawings. Specific embodiments

[0042] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are some, but not all, of the embodiments of the present application.

[0043] In the embodiments of the present application, terms such as "first" and "second" are only used to distinguish different objects, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order. For example, the first application, the second application, etc. are used to distinguish different applications, rather than to describe the specific order of the applications. Features limited by "first" and "second" may explicitly or implicitly include one or more of such features.

[0044] Each user can spread shared content based on the user's relationship chain. For example, when a user publishes his or her shared content in an application, other users with whom he or she has a follow-up relationship can view or obtain the shared content.

[0045] like Figure 1 As shown, in some possible scenarios, the sharer can initiate sharing of his own files.

[0046] It is understood that there are two ways for the sharer to share, namely, one is to share with everyone, and any user can access the file. The other is to share with a specific user, and the server will save the sharing relationship and authenticate the recipient's permissions.

[0047] Specifically, after receiving a sharing request, the server can review the content of the file and check the risk level of the file content, such as whether the file content involves pornographic content, terrorist content, violent content, or other illegal content, and then evaluate the file classification or risk level based on the file content.

[0048] Thus, the server can block or allow the sharer to share the file according to the rules set according to the risk level of the file. If the server allows the sharer to share the file, the recipient can download or read the file after receiving the share.

[0049] exist Figure 1 In the application scenario shown, since the file content needs to be read when reviewing the file content, the server needs to identify the file format in order to determine whether the file content contains illegal or unlawful content. If the file is the user's personal data, it may be illegally stolen by a third party when shared.

[0050] If the file is encrypted, the content of the file may not be readable because it cannot be decrypted. Therefore, the sharer can only control the scope of sharing to a limited extent, but cannot control the secondary dissemination by the recipient, especially when the file is tampered with by malicious users and then spread.

[0051] In another possible scenario, Figure 2 As shown in , when user 201 shares a file, the transmission chain of the file can be: user 1 → user 2 → user 3 → user 4 and user 1 → user 2 → user 5 → user 6. It can be understood that in the process of users sharing with other users, each user is rated. That is, files can be shared according to the control rules set by content classification and user classification.

[0052] For example, when a user shares a certain file, the content of the file is first subject to content review to obtain the content classification. Then, the content classification and user classification can be combined, and the risk level of the current share can be calculated according to the control rules to determine whether to allow this share.

[0053] If a user has shared more illegal content and the spread range is wider, then the risk score of the user is higher, and the sharing control of the user is more stringent.

[0054] In Figure 2 In the application scenario shown, when the sharer shares, it may be illegally stolen by a third party, and the content of the file may not be readable due to inability to decrypt. The sharer can also not effectively control the subsequent dissemination and forwarding of the file.

[0055] Therefore, the embodiments of the present application provide a file sharing method, which solves the problem that the sharer cannot control the subsequent dissemination and forwarding of the file, can control the sharing range of the file, and avoid malicious and illegal dissemination of the file.

[0056] The file sharing method provided by the embodiments of the present application can be applied to the scenario where the first user 100 and the second user 200 share based on the server 300 as shown in Figure 3 shown.

[0057] In Figure 3 In the scenario shown, the first user 100 and the second user 200 can use their respective user devices. It can be understood that the user device can include but is not limited to one or more of the following: desktop computer, portable computer, tablet computer, personal digital assistant (PDA), cellular phone, and smart phone, etc. It can be understood that the user's information and data can be stored on the user device.

[0058] The user requests the interaction interface of the server 300 for communication, and different users can share information. Therefore, different devices can communicate with each other. The communication media between devices can include but are not limited to: network connections, such as the Internet, wide area network, local area network; telecommunications, such as 2G, 3G, 4G, 5G and other generations of wireless telecommunications networks; near field communication, such as infrared, Bluetooth, etc.

[0059] In one embodiment, the server 300 can communicate with the user devices of each user to control the sharing of files between different users. According to the embodiments of the present application, the file sharing between different users can be completed under the control of the server 300.

[0060] As Figure 3As shown, the first user 100 can initiate file sharing on the user device, and the user device of the first user 100 can install an application that matches the file service. The server 300 can provide relevant interfaces for the file service, such as server-side interfaces for file upload, download, sharing, copying, etc., for the user device to call.

[0061] The server 300 can also perform control of sharing risks, such as file content review, user grading, sharing behavior review, etc.

[0062] In one embodiment, the first user 100 can be the sharer, and the second user 200 can be the recipient. For example, the user device of the first user 100 can send web links, text, images, documents, folders, videos, audio, or installed applications, etc. as the files to be shared to the user device of the second user 200 to implement the file sharing function between devices.

[0063] For example, as Figure 4 shown, the first user 100 (i.e., the sharer) can call the interface of the server 300 through the application (APP) of the user device to initiate file sharing, and can set the propagation rules of the file during file sharing, that is, the first user 100 uploads the file with the propagation rules attached to the server 300. The server 300 can manage the propagation chain data of the file, generate a propagation node for the file sharing, that is, generate a propagation behavior data once, where the propagation node can include information for sharing control such as propagation rules, file metadata, sharer, etc.

[0064] It can be understood that in this embodiment, the file metadata can be data different from the file content. In some possible scenarios, the file metadata can be used to describe the characteristics of the file, such as file size, sha256, file name, file type, etc.

[0065] It can be understood that the server 300 will review the file content and propagation rules, that is, the server 300 reviews the file content and sharing behavior.

[0066] Among them, the propagation rules include the propagation rules set by the user and the propagation rules configured by the system. Thus, the server 300 can perform file sharing control according to the propagation chain data. If it is determined that file sharing is allowed, the server 300 will supplement the propagation node of this sharing to the propagation chain.

[0067] It can be understood that the propagation rules are the sharing rules set by each user when sharing files.

[0068] In some possible implementations, the second user 200 can download the shared file through the APP in the user device. The downloaded content includes the propagation chain data of the file, and the downloaded file and the propagation chain data are saved to the secure sandbox of the system.

[0069] It can be understood that the secure sandbox is a security mechanism that provides an isolated environment for the executing program. The secure sandbox can ensure the security of the system by strictly controlling the resources accessed by the executing program. Other applications cannot directly access the data stored by the application in the secure sandbox (data in memory and on disk).

[0070] In the user device of the second user 200, if the second user 200 copies a file, the application needs to copy the propagation chain data of the file while copying the file content. If the second user 200 uploads a file to the server 300, the application also needs to upload it together with the propagation chain data.

[0071] In the following embodiments, taking the sharing between the first user 100 and the second user 200 based on the server 300 as an example, a file sharing method provided by the embodiments of the present application is elaborated in detail. As Figure 5 shown, the method includes:

[0072] Step S51, receive a request to share the file of the first user with the second user.

[0073] In one embodiment, the sharing of the file can be initiated by the first user 100, that is, the first user 100 can send a file sharing request to the server 300. For example, the first user 100 can operate their user device to share a specified file with the second user 200.

[0074] Specifically, the first user 100 can call the interface of the server 300 on the terminal side to share the file. When sharing, the recipient can be specified, for example, the first user 100, or it can be shared with all users. The first user 100 can set the propagation rule when sharing.

[0075] Step S52, obtain the propagation chain data of the file.

[0076] It can be understood that the propagation chain data in this embodiment can be the data formed by each user that the file passes through during propagation.

[0077] In one embodiment, after receiving the sharing request from the first user 100, the server 300 will obtain the propagation chain data of the file. It can be understood that the server 300 can obtain the necessary data for the propagation chain in the file, such as the metadata of the file, the sharer, the propagation rules, etc., and supplement these necessary data into the propagation chain data to form a propagation node.

[0078] It can be understood that in the embodiments of the present application, propagation information will be generated during the sharing process of the file and can be saved in the propagation chain.

[0079] For example, as Figure 6 shown, when a file is first shared by the owner of the file, the server will generate a propagation behavior data S0 and construct a propagation chain C0. That is, C0 contains a propagation behavior data S0. Among them, the propagation chain data can be saved in the metadata information of the file. If the recipient of the file shares the file with other users again, this sharing will also generate a propagation behavior data S1 and add S1 to the propagation chain C0. The new propagation chain is denoted as C1. And so on, when the file is shared by the nth recipient to the (n + 1)th recipient, the propagation chain C n+1 , that is, C n+1 = C n + S n+1 . The propagation chain C n+1 contains S0, S1,..., S n+1 these propagation behavior data.

[0080] Step S53, perform sharing control on the file.

[0081] In one embodiment, the server 300 can perform file sharing control according to the propagation chain data.

[0082] It can be understood that the file sharing control can be that the server 300 performs control to block or allow the sharing according to the file content, user characteristics, propagation characteristics, and in combination with the rules set by the system and the propagation rules on the propagation chain. Among them, the propagation rules can be specified by the sharer during sharing (and saved in the propagation behavior data of the propagation chain), or can be specified by the system configuration (saved in the server).

[0083] For example, the server 300 can allow the first user 100 to share the file with the second user 200 according to the propagation chain data, or the server 300 can block the first user 100 from sharing the file with the second user 200 according to the propagation chain data.

[0084] Please refer to Figure 7, which is a detailed flowchart of step S53. In one embodiment of the present application, the server 300's sharing control of a file may include:

[0085] Step S71, auditing the content of the file.

[0086] The server 300 may audit the content of the file uploaded by the first user 100 to obtain a content classification of the file.

[0087] Step S72, obtaining propagation chain data from the file.

[0088] For example, when the first user 100 uploads a file to the server 300, the server 300 may obtain propagation chain data from the file.

[0089] Step S73, obtaining propagation rules from the propagation chain data.

[0090] In one embodiment, the server 300 may obtain the propagation rules set by users in the propagation chain data. For example, the server 300 may obtain the propagation rules set by the first user 100 in the propagation chain data. It can be understood that each user can set the propagation rules for a particular file sharing.

[0091] Step S74, checking the propagation rules in sequence.

[0092] In one embodiment, the server 300 may check these propagation rules in sequence and perform sharing control according to the propagation rules.

[0093] It can be understood that in a possible application scenario, the propagation rules set by the user may be: prohibiting the recipient from tampering with the file (e.g., for copyright protection).

[0094] For example, as Figure 8 shown, when the first user 100 shares a file, it sets in the propagation rule (P0) that the recipient is prohibited from modifying the file, and this propagation rule (P0) is saved in the propagation chain. At this time, after the second user 200 downloads the file from the server 300 and modifies the file, and then shares the file with the third user.

[0095] At this time, the server 300 checks according to the propagation chain and checks that the hash value of the file in the current propagation behavior data S1 is inconsistent with the hash value of the file in the propagation behavior data S0. At this time, the server 300 can confirm that the file has been tampered with, and thus can prevent the second user from sharing the file with the third user.

[0096] With such a design, when a user shares something, the user can set the dissemination rules for the sharing, and the server controls according to the dissemination rules set by the user, thereby protecting its legitimate rights and interests such as privacy data and copyright.

[0097] It can be understood that in a possible application scenario, the dissemination rules set by the user can be: prohibiting secondary sharing.

[0098] For example, when the first user 100 shares a file, in the dissemination rules, it is set that only the users who receive the share can view the file, and the receiver is restricted from sharing the file again. It can be set to prohibit secondary sharing when sharing. Then, when the second user 200 shares the file again, the server 300 can block this sharing according to the dissemination rules on the dissemination chain (that is, prohibiting secondary sharing).

[0099] It can be understood that the embodiments of the present application can limit the operable permissions of the receiver for the shared file, and the above-mentioned operable permissions can include modification, copying, sharing, downloading, etc.

[0100] In a possible application scenario, the dissemination rules set by the user can be: limiting the total number of users who receive the file or the number of dissemination times.

[0101] For example Figure 9 As shown, the sharer can limit the number of receivers of the file in the dissemination rules. The server can obtain the source of the file from the dissemination chain, and obtain the receiver data of the file from this dissemination chain or other dissemination chains of the source file. Thus, the server can obtain the total number of file receivers. When the total number of file receivers exceeds the total number of users who receive the file in the dissemination rules, the sharing is blocked.

[0102] Thus, in the above scenario, the user can control the dissemination scope of the file sharing, specifically including the number of receivers, the number of dissemination times, and the user characteristics of the receivers, etc.

[0103] It can be understood that in a possible application scenario, the dissemination rules set by the system can be: limiting that the risk level of the sharing is lower than a preset index.

[0104] In an embodiment of the present application, the server 300 can comprehensively evaluate according to parameters such as the risk level of the file content, the number of receivers of the dissemination, the number of dissemination times, the risk level of the receivers, the number of complaints, etc., and then can obtain the risk level of the sharing.

[0105] It can be understood that the embodiments of the present application can evaluate the content classification or risk level of a file by checking the risk level of the file content, such as content that violates the law, such as pornographic content, terrorist content, violent content, etc. If the content of the file cannot be audited, the default value configured by the system is used. The embodiments of the present application can obtain the users on the dissemination path from the dissemination paths of the "violating" files that have occurred, and through the process of sharing these users with other users, perform a user risk assessment to obtain the recipient risk level.

[0106] For example, when the first user 100 is about to share a file, if the server 300 detects that the risk level of the file shared by the first user 100 is greater than a preset index, the server 300 will block this sharing.

[0107] With such a design, when the content of the file cannot be audited, the embodiments of the present application can use dissemination characteristics to control the sharing behavior according to the information in the process of file sharing and dissemination, such as the source of the file, the sharer, the recipient, the complaint information, etc.

[0108] Step S54, the second user downloads the shared file through the application in the user device and saves the file and the dissemination chain data in the secure sandbox.

[0109] It can be understood that the sharer can turn the original file into a new file by copying or first downloading and then re-uploading it as another file. At this time, the dissemination chain data is not in the new file. Therefore, if we want to prevent the user's file from being tampered with, stolen, and maliciously disseminated, it is necessary to protect the dissemination chain data.

[0110] When the server 300 confirms to allow the file sharing of the first user 100, the second user 200 can download the shared file from the server 300 through the application in his user device. Among them, the content downloaded by the second user 200 can include the dissemination chain data of the file. Thus, the second user 200 can save the file and the dissemination chain data to the secure sandbox of the operating system.

[0111] It can be understood that if the second user 200 copies the file, the application needs to control that while copying the file content, it also needs to copy the dissemination chain data of the file. If the second user 200 uploads the file to the server 300, the application also needs to upload the file carrying the dissemination chain data.

[0112] In this embodiment, when the second user 200 downloads the shared file, the protection mechanism of the secure sandbox of the operating system can be used to protect the dissemination chain data.

[0113] It can be understood that the files stored in the secure sandbox are only accessible to the application to which they belong or other applications authorized by that application, thereby ensuring that files including dissemination chain data are not stolen or tampered with by third-party applications.

[0114] For example, as Figure 10 shown, when the second user 200 downloads and views the file shared by the first user 100 on the user device, the second user 200 can operate the application to call the interface of the server 300 to download the file shared by the first user 100 from the server 300. The server 300 transmits the file content and dissemination chain data to the application, and the application saves the file downloaded from the server 300 to the secure sandbox of the system. It can be understood that this file includes file content and dissemination chain data.

[0115] When the second user 200 copies a file as a new file, the application also needs to copy the file in the secure sandbox, and the copied file includes file content and dissemination chain data to ensure that the dissemination chain data is maintained from the source file to the target file. When the second user 200 uploads the copied new file to the server 300, the application needs to upload both the file content and the dissemination chain data to the server 300, thereby ensuring that the dissemination chain data continues to be retained in the file in the case where the file is copied. It can be understood that if the server 300 copies the file as a new file, it will copy and retain the dissemination chain data in the source file.

[0116] Based on such a design, through the secure sandbox mechanism of the system, it is possible to protect the dissemination chain data of the file from being tampered with and lost during the processes of downloading, copying, modifying, and uploading the file.

[0117] Please refer to Figure 11 , Figure 11 which is a schematic structural diagram of a file sharing device disclosed in an embodiment of the present application. Among them, the file sharing device 500 can be used to execute Figures 3 to 10 some or all of the steps of the file sharing method described in Figures 3 to 10 . For specific details, please refer to the relevant description in

[0118] and will not be elaborated here.

[0119] For example, as Figure 11 shown, the file sharing device 500 provided in an embodiment of the present application may include: an acquisition unit 501 and a control unit 502.

[0120] The acquisition unit 501 is configured to obtain the file of the first user in response to a request to share the file of the first user with the second user.

[0121] It can be understood that the file includes propagation chain data, which is data formed by each user through which the file passes during propagation.

[0122] The obtaining unit 501 is also configured to obtain a propagation rule from the propagation chain data. Wherein, the propagation rule is a sharing rule set when the first user shares the file with the second user.

[0123] The control unit 502 is configured to use the propagation rule in the file to control the file sharing of the first user to the second user.

[0124] In a possible design, the control unit 502 is further configured to prohibit the second user from tampering with the file according to the propagation rule.

[0125] In a possible design, the control unit 502 is further configured to prohibit the second user from sharing the file with a third user according to the propagation rule.

[0126] In a possible design, the control unit 502 is further configured to limit the number of users receiving the file according to the propagation rule.

[0127] It can be understood that the division of each module in the above file sharing device is only for illustrative purposes. In other embodiments, the file sharing device can be divided into different modules as needed to complete all or part of the functions of the above file sharing device.

[0128] In the embodiments of the present application, the specific implementation of each unit can also be correspondingly referred to Figures 3 to 10 the corresponding description of the method embodiment shown. In Figure 11 the described file sharing device, the file sharing range can be controlled, and the malicious or illegal propagation of the file can be avoided. For specific content, reference can be made to the specific embodiments of the above file sharing method, which will not be elaborated here.

[0129] In this embodiment, the file sharing device 500 is presented in the form of a unit. Here, the "unit" may refer to an application-specific integrated circuit (ASIC), a processor and a memory that execute one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions. In addition, the obtaining unit 501 and the control unit 502 can be implemented by Figure 12 the processor 601 of the file sharing device shown.

[0130] As Figure 12 shown, the file sharing device 600 can be inFigure 12 The above structure is implemented. The file sharing device 600 includes at least one processor 601, at least one memory 602, and at least one communication interface 603.

[0131] The processor 601, the memory 602, and the communication interface 603 can be connected through a communication bus and complete communication with each other.

[0132] The processor 601 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the above program.

[0133] The communication interface 603 is used to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0134] The memory 602 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory can exist independently and be connected to the processor through a bus. The memory can also be integrated with the processor.

[0135] Among them, the memory 602 is used to store the application program code for executing the above solution, and is controlled by the processor 601 for execution. The processor 601 is used to execute the application program code stored in the memory 602. The code stored in the memory 602 can execute Figures 3 to 10 some or all of the steps of the file sharing method described above.

[0136] For those skilled in the art, it is obvious that the present application is not limited to the details of the above exemplary embodiments, and the present application can be implemented in other specific forms without departing from the spirit or basic characteristics of the present application. Therefore, as long as it is within the scope of the substantial spirit of the present application, appropriate changes and modifications made to the above embodiments should fall within the scope of protection required by the present application.

Claims

1. A file sharing method, characterized in that, The file sharing method includes: In response to a request to share a file of a first user with a second user, obtaining the file of the first user; wherein the file includes propagation chain data, and the propagation chain data is data formed by each user through which the file has passed during propagation; Obtaining a propagation rule from the propagation chain data, wherein the propagation rule is a sharing rule set by each user when sharing a file; Using the propagation rule in the file to control the file sharing of the first user with the second user.

2. The file sharing method according to claim 1, wherein: When the first user shares a file with the second user, the propagation rule is to prohibit the second user from tampering with the file.

3. The file sharing method according to claim 1 or 2, wherein: When the first user shares a file with the second user, the propagation rule is to prohibit the second user from sharing the file with a third user.

4. The file sharing method according to claim 1, wherein: When the first user shares a file with the second user, the propagation rule is to limit the number of users receiving the file.

5. The file sharing method according to claim 1, characterized in that, The method further includes: The second user downloads the content and propagation chain data of the file through an application in the user device, and saves the content and propagation chain data of the file into a secure sandbox.

6. The file sharing method according to claim 5, wherein: When the second user copies the file into a new file, the application copies the file including the file content and the propagation chain data in the secure sandbox.

7. The file sharing method according to claim 6, wherein: When the second user uploads the new file to the server, the application uploads both the file content and the propagation chain data to the server.

8. A file sharing device, characterized in that, The file sharing device includes: An obtaining unit, configured to obtain the file of the first user in response to a request to share a file of the first user with the second user; wherein the file includes propagation chain data, and the propagation chain data is data formed by each user through which the file has passed during propagation; The obtaining unit is further configured to obtain a propagation rule from the propagation chain data, wherein the propagation rule is a sharing rule set by each user when sharing a file; A control unit, configured to use the propagation rule in the file to control the file sharing of the first user with the second user.

9. The file sharing device according to claim 8, wherein: The control unit is further configured to prohibit the second user from tampering with the file according to the propagation rule.

10. The file sharing device according to claim 8 or 9, wherein: The control unit is further configured to prohibit the second user from sharing the file with a third user according to the propagation rule.

11. The file sharing device according to claim 8, wherein: The control unit is further configured to limit the number of users receiving the file according to the propagation rule.

Images