File forwarding method and device, computer device, storage medium and program product

Abstract

The application discloses a file forwarding method and device, computer equipment, storage medium and program product, and belongs to the technical field of UI interaction. The method comprises the following steps: displaying conversation messages in a first application; in response to a selection operation on at least one conversation message in the first application, setting the at least one conversation message to a selected state; the at least one conversation message contains a first leakage-preventing file; in response to a first forwarding operation of forwarding the at least one conversation message to a second application, and a first user account logged in the computer equipment having a forwarding permission for the first leakage-preventing file, adding the first leakage-preventing file to the second application; and sending the first leakage-preventing file to a second user account through the second application.

Description

Technical Field

[0001] This application relates to the field of user interface (UI) interaction technology, and in particular to a file forwarding method, apparatus, computer device, storage medium and program product. Background Technology

[0002] With the continuous development of Internet technology, many conversational applications now support file leakage prevention features.

[0003] In related technologies, in session-based applications that support file leak prevention, when a user sends a file, the file can be set as a leak-proof file. After the leak-proof file is sent to the session interface, when other users view or download the leak-proof file, the session-based application will authenticate the other user's account. After successful authentication, other users are allowed to view or download the leak-proof file.

[0004] However, the above-mentioned solutions offer a relatively simple way for users to operate on leak-proof files, resulting in low efficiency in this process. Summary of the Invention

[0005] This application provides a file forwarding method, apparatus, computer device, storage medium, and program product. The technical solution is as follows:

[0006] According to one aspect of this application, a file forwarding method is provided, the method being performed by a computer device, the method comprising:

[0007] At least one session message is displayed in the first session interface of the first application, and the at least one session message contains a first anti-leakage file;

[0008] In response to a selection operation on the at least one session message, the at least one session message is set to a selected state;

[0009] In response to a first forwarding operation that forwards the at least one session message to a second application, and a first user account logged in on the computer device having forwarding permission for the first anti-leakage file, the first anti-leakage file is added to the sending interface of the second application;

[0010] The first anti-leakage file is sent to the second user account through the second application.

[0011] According to another aspect of this application, a file forwarding apparatus is provided, the apparatus comprising:

[0012] A session message display module is used to display at least one session message in the first session interface of the first application, wherein the at least one session message contains a first anti-leakage file;

[0013] The message selection module is used to set the at least one session message to a selected state in response to a selection operation on the at least one session message.

[0014] The file adding module is used to respond to a first forwarding operation that forwards the at least one session message to the second application, and the first user account logged in on the computer device has forwarding permission for the first anti-leakage file, and add the first anti-leakage file to the sending interface of the second application.

[0015] The file sending module is used to send the first anti-leakage file to the second user account through the second application.

[0016] In one possible implementation, the file adding module is configured to, in response to the first forwarding operation, query the first user account's download permission for the first anti-leakage file; and, if the query finds that the first user account has download permission for the first anti-leakage file, add the first anti-leakage file to the second application.

[0017] In one possible implementation, a file adding module is used to query the downloaded first anti-leakage file locally; if the downloaded first anti-leakage file is found, the downloaded first anti-leakage file is added to the second application.

[0018] In one possible implementation, a file adding module is used to download the first anti-leakage file to the local machine if the first anti-leakage file is not found; and to add the downloaded first anti-leakage file to the second application.

[0019] In one possible implementation, the file addition module is used to obtain the file type of the first anti-leakage file; if the file type of the first anti-leakage file belongs to a file type other than the specified file type, it queries the download permissions of the first user account for the first anti-leakage file.

[0020] In one possible implementation, the device further includes:

[0021] The first reminder module is used to display a first reminder message when at least one session message meets the first reminder condition before the file addition module adds the first anti-leakage file to the second application; the first reminder message is used to indicate that there is a file that cannot be forwarded in the at least one session message;

[0022] The first reminder condition includes at least one of the following conditions:

[0023] At least one session message contains a file of a specified file type;

[0024] The first user account does not have permission to download the first anti-leakage file;

[0025] The first anti-leakage file that was downloaded was not found locally.

[0026] In one possible implementation, the device further includes:

[0027] A processing module is used to perform anti-leakage processing on the first anti-leakage file in the second application.

[0028] In one possible implementation, the leak prevention process includes at least one of the following processes:

[0029] Add a leak prevention alert element to the file icon of the first leak prevention file;

[0030] Add a watermark to the preview image of the first leak-proof file;

[0031] The first leak-proof file is encrypted.

[0032] In one possible implementation, the device further includes:

[0033] The file receiving module is used to receive a second leak-proof file sent by a third user account through the second application;

[0034] The first permission query module is used to query the first user account's download permission for the second anti-leakage file in response to receiving a download operation for the second anti-leakage file;

[0035] The first download module is used to download the second anti-leakage file when it is found that the first user account has download permissions for the second anti-leakage file.

[0036] In one possible implementation, the device further includes:

[0037] A message adding module is configured to add the at least one session message to a first online document in response to a second forwarding operation that forwards the at least one session message in the first application;

[0038] The document forwarding module is used to forward the first online document in the first application.

[0039] In one possible implementation, the device further includes:

[0040] The first reminder module is used to display a second reminder message when the at least one session message meets the second reminder condition before the message adding module adds the at least one session message to the first online document; the second reminder message is used to indicate that there is a file in the at least one session message that cannot be forwarded.

[0041] The second reminder condition includes: the existence of a file of a specified file type in at least one session message.

[0042] In one possible implementation, the device further includes:

[0043] The document display module is used to display a second online document sent by a fourth user account, which contains a third leak-proof file;

[0044] The second permission query module is used to query the first user account's download permission for the third anti-leakage file in response to the download operation of the third anti-leakage file;

[0045] The second download module is used to download the third anti-leakage file if it is found that the first user account has download permissions for the third anti-leakage file.

[0046] In one possible implementation, the device further includes:

[0047] The summary extraction module is used to input the at least one conversation message into the generative language model and obtain the summary information output by the generative language model, wherein the summary information is a summary of the content contained in the at least one conversation message;

[0048] The file sending module is used to send the first anti-leakage file and the summary information to the second user account through the second application.

[0049] In one possible implementation, the summary extraction module is used for,

[0050] Construct a prompt statement containing session records, the prompt statement being used to instruct the extraction of a summary of the content of the session records; the session records contain the at least one session message;

[0051] The prompt statement is input into the generative language model to obtain the summary information output by the generative language model.

[0052] In one possible implementation, the second application is an email application, and the file sending module is used to send the email to the second user account through the email application after adding the first anti-leakage file as an attachment to the email and adding the summary information as the subject of the email.

[0053] According to another aspect of this application, a computer device is provided, the computer device comprising: a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the file forwarding method as described above.

[0054] According to another aspect of this application, a computer-readable storage medium is provided, the computer-readable storage medium storing a computer program, the computer program being loaded and executed by a processor to implement the file forwarding method as described above.

[0055] According to another aspect of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium, wherein a processor retrieves the computer instructions from the computer-readable storage medium, causing the processor to load and execute them to implement the file forwarding method as described above.

[0056] The beneficial effects of the technical solutions provided in this application include at least the following:

[0057] When a conversational message in a conversational application contains a file protected against file leakage (PPL), users can forward the PPL to other users directly across applications through operations in the conversation interface. During this process, authentication is performed on the current user's permission to forward the PPL during the process of adding the PPL to the sending interface of other applications. This ensures the security of PPL forwarding, thus balancing the efficiency and security of file forwarding when forwarding files through conversational applications. Attached Figure Description

[0058] Figure 1 This is a structural block diagram of a computer system provided in an exemplary embodiment of this application;

[0059] Figure 2 This is a flowchart of a file forwarding method provided in an exemplary embodiment of this application;

[0060] Figure 3 This is a schematic diagram illustrating a cross-application file forwarding method according to an embodiment of this application;

[0061] Figure 4 This is a flowchart of a file forwarding method provided in an exemplary embodiment of this application;

[0062] Figure 5 This is a flowchart of a file forwarding method provided in an exemplary embodiment of this application;

[0063] Figure 6 This is a flowchart of a file forwarding method provided in an exemplary embodiment of this application;

[0064] Figure 7 This is a flowchart illustrating a method for forwarding session messages via email, as described in an embodiment of this application.

[0065] Figure 8 This is a flowchart illustrating an in-application forwarding of session records according to an embodiment of this application;

[0066] Figure 9 This is a schematic diagram illustrating the addition of session messages to emails according to an embodiment of this application;

[0067] Figure 10 This is a schematic diagram of the email receiving side involved in the embodiments of this application;

[0068] Figure 11 This is a schematic diagram of a pop-up prompt involved in an embodiment of this application;

[0069] Figure 12 This is a schematic diagram illustrating text replacement involved in an embodiment of this application;

[0070] Figure 13 This is a schematic diagram illustrating email forwarding as described in an embodiment of this application;

[0071] Figure 14 This is a schematic diagram illustrating session record forwarding in an embodiment of this application;

[0072] Figure 15 This is a schematic diagram of a pop-up prompt involved in an embodiment of this application;

[0073] Figure 16 This is a flowchart illustrating the workflow of an embodiment of this application;

[0074] Figure 17 This is a system architecture diagram related to the embodiments of this application;

[0075] Figure 18 This is a structural block diagram of a file forwarding device provided in one embodiment of this application;

[0076] Figure 19 This is a structural block diagram of a computer device provided in an exemplary embodiment of this application. Detailed Implementation

[0077] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0078] Figure 1 A structural block diagram of a computer system provided in an exemplary embodiment of this application is given. The computer system 100 includes: a terminal 110 and a server 120.

[0079] Terminal 110 has a client 111 installed and running with at least two applications. When terminal 110 runs client 111, the application interface of client 111 is displayed on the screen of terminal 110. The application interface of client 111 may include the interface of a first application and the interface of a second application; wherein, the interface of the first application may include a session interface, and the interface of the second application may include a sending interface; for example, the first application may be a session application, and the second application may be an email application; the first application and the second application may be two sub-applications under the same main application, or the first application and the second application may be two independent applications. Users can trigger the display of various contents in the applications through the above application interfaces, including session messages, sent emails / files, etc.

[0080] Those skilled in the art will understand that the number of terminals described above can be more or less. For example, there may be only one terminal, or there may be six, eight, or more terminals. This application does not limit the number of terminals or the type of device.

[0081] Figure 1 Only one terminal is shown, but in different embodiments, multiple other terminals may be available to access server 120. Optionally, one or more terminals 130 may also be terminals corresponding to developers, on which an application or a plugin development and editing platform is installed. Developers can edit and update the application client or plugin on terminal 130 and transmit the updated client or plugin installation package to server 120 via wired or wireless network. Terminal 110 can download the client installation package from server 120 to update the client or plugin.

[0082] Terminal 110 and terminal 130 can be connected to server 120 via wireless network or wired network.

[0083] Server 120 includes at least one of a single server, multiple servers, a cloud computing platform, and a virtualization center. Server 120 is used to provide background services for clients of applications or plugins that support schedule management functions. Optionally, server 120 undertakes the primary computing work, and the terminal undertakes the secondary computing work; or, server 120 undertakes the secondary computing work, and the terminal undertakes the primary computing work; or, server 120 and the terminal use a distributed computing architecture for collaborative computing.

[0084] In an illustrative example, server 120 includes processor 122, user account database 123, application service module 124, and user-facing input / output interface (I / O interface) 125. Processor 122 loads instructions stored in server 120 and processes data in user account database 123 and application service module 124. User account database 123 stores user account data used by terminal 110 and other terminals 130, such as user account avatars, nicknames, and account levels. Application service module 124 provides background management services for applications. User-facing I / O interface 125 establishes communication and exchanges data with terminal 110 via wireless or wired networks.

[0085] Please refer to Figure 2 It illustrates a flowchart of a file forwarding method provided in an exemplary embodiment of this application, the method being executed by a computer device, for example, by an application in the computer device, so that the method is applied to Figure 1 The terminal 110 shown is used as an example to illustrate that the method may include the following steps.

[0086] Step 210: Display the session message in the first application.

[0087] In this embodiment of the application, the first application in the computer device supports instant messaging and other conversational functions, or the first application is a conversational application.

[0088] The computer device can display a first session interface in a first application, in which session messages sent by each session participant in the session corresponding to the first session interface are displayed.

[0089] The aforementioned conversation messages can contain a variety of different message types, including but not limited to text, images, videos, voice messages, documents (text documents, spreadsheet documents, etc.), emoticons, links, virtual red envelopes, message cards, and so on.

[0090] Step 220: In response to a selection operation on at least one session message in the first application, set at least one session message to a selected state; the at least one session message contains a first anti-leakage file.

[0091] In this embodiment, the first application supports file leakage prevention. Users / organizations that enable leakage prevention can centrally manage file operation permissions within the application, tracing file (e.g., document / video / image) uploads, downloads, views, forwarding, and other actions, reducing the risk of information leakage. Administrators / users can configure the scope of leakage prevention, selecting which members' files will be protected against leakage. Users have a series of permission controls for protected files, including what operations they can perform on the files (e.g., forwarding externally, downloading, viewing, editing, saving, etc.).

[0092] The aforementioned leak prevention documents can also be referred to as leak prevention resources.

[0093] Alternatively, the first application can set / mark one or more user-specified files as leak-proof files and configure which user accounts have which permissions for the leak-proof files based on permission configuration operations.

[0094] Correspondingly, when a user uploads, downloads, views, or forwards a file, the first application can perform an authentication operation to determine whether the user's account has the permission to upload, download, view, or forward the leak-proof file. If the authentication is successful, the user is allowed to perform the corresponding operation on the leak-proof file.

[0095] In this embodiment of the application, the first application also supports user selection / multi-selection of conversation messages. Specifically, for example, when a user clicks / long-presses a message / control / blank area in the first conversation interface, a selection box can pop up, which contains a message selection / multi-selection control. When the user clicks the selection / multi-selection control, the first conversation interface enters the message selection state. For example, a selection control will be displayed before each conversation message. When the user triggers the selection control corresponding to the conversation message, the conversation message can be set to a selected / unselected state. The user can trigger multiple conversation messages to enter the selected state at the same time, or only trigger a single conversation message to enter the selected state.

[0096] In this embodiment of the application, the computer device (first application) allows the user to select a session message containing a leak-proof file.

[0097] Step 230: In response to a first forwarding operation that forwards at least one session message to a second application, and a first user account logged in on the computer device having forwarding permissions for the first leak protection file, add the first leak protection file to the second application.

[0098] For example, when at least one of the aforementioned conversation messages is selected, the first application can display a first forwarding control to forward at least one conversation message to the second application. The first forwarding operation can be an operation performed by the user clicking the first forwarding control.

[0099] In this embodiment of the application, after a user selects at least one session message containing the first anti-leakage file in the first application, the user can perform the operation of forwarding at least one session message across applications. At this time, the computer device (such as the first application in the computer device) can detect whether the first user account currently logged in in the computer device has the permission to forward the first anti-leakage file. If so, the first anti-leakage file is added to the second application. For example, at this time, the computer device can display the sending interface of the second application, which contains the aforementioned first anti-leakage file.

[0100] In some embodiments, the computer device may also add other files besides the anti-leakage file from at least one session message to the second application, for example, by adding them to the sending interface of the second application.

[0101] In some embodiments, the computer device may also add a message preview image of at least one session message to a second application, for example, to the sending interface of the second application.

[0102] In some embodiments, when different types of files are added to the second application, they can be added to different positions in the sending interface according to their file types. For example, video and document files can be added as attachments in the sending interface, and image files can be added to the body of the sending interface.

[0103] Step 240: Send the first leak protection file to the second user account via the second application.

[0104] In this embodiment of the application, after the computer device adds the first anti-leakage file to the second application, it can send the first anti-leakage file in the second application; wherein, the second user account can be a user account set by the user in the second application.

[0105] In some embodiments, the second application may be an email application, and sending the first anti-leakage file to the second user account through the second application may refer to sending the first anti-leakage file to the second user account via email.

[0106] In some embodiments, if the at least one session message contains other files besides the anti-leakage file, the computer device can send the first anti-leakage file and the other files together to a second user account in a second application.

[0107] In some embodiments, if the computer device adds a message preview image of at least one session message to a second application, the computer device can then display the first leak-proof file and message preview in the second application. Figure 1 It is then sent to the second user account.

[0108] In some embodiments, the computer device sends an online document to a second user account via a second application. The online document includes the first leak-proof file mentioned above, or the online document includes at least one session message mentioned above.

[0109] The aforementioned online documents can be documents opened and displayed through a browser interface, a web page interface, or other application interfaces, including but not limited to at least one of online session log documents, online spreadsheet documents, online text documents, and online presentation documents.

[0110] In some embodiments, the computer device sends the aforementioned online document and the first anti-leakage file together to the second user account via a second application.

[0111] In this context, the computer device sending the online document to the second user account via the second application may refer to sending the link of the online document to the second user account via the second application.

[0112] In summary, in the solution shown in the embodiments of this application, when a session message in a session application contains an anti-leakage file, the user is allowed to forward the anti-leakage file in the session message directly to other users across applications through operations in the session interface. During this process, when adding the anti-leakage file to the sending interface of other applications, the current user's permission to forward the anti-leakage file is authenticated, which can ensure the security of the anti-leakage file forwarding. Thus, when forwarding files through a session application, both the efficiency and security of file forwarding are taken into account.

[0113] Based on the above Figure 2 Please refer to the proposed solution. Figure 3 This illustration shows a schematic diagram of cross-application file forwarding according to an embodiment of this application. Figure 3As shown, a first application 310 (a conversational application) and a second application 320 (an email application) are running on a computer device. The first application 310 displays a first conversation interface 312 containing multiple conversation messages. Users can select multiple conversation messages in the first conversation interface 312 through message multi-selection. These multiple conversation messages contain a first anti-leakage file 312a. After the user clicks the forwarding control 314 at the bottom of the first conversation interface 312, the computer device can check the forwarding permissions of the currently logged-in first user account for the first anti-leakage file 312a. If there are forwarding permissions, the sending interface 322 of the second application 320 is displayed, and the first anti-leakage file 312a is added as an email attachment to the sending interface 322. The user can set a second user account (which can be an email address) in the sending interface 322 and click the sending control 324. At this time, the computer device can send an email containing the first anti-leakage file 312a to the second user account through the second application 320.

[0114] Based on any one or more embodiments of the above-described embodiments of this application, in one possible implementation, please refer to... Figure 4 It illustrates a flowchart of a file forwarding method provided in an exemplary embodiment of this application, such as... Figure 4 As shown, step 230 may include steps 230a and 230b.

[0115] Step 230a: In response to the first forwarding operation, query the first user account's download permissions for the first anti-leakage file.

[0116] The aforementioned download permission refers to the permission to download the first anti-leakage file from the first application's session message to the local computer device.

[0117] In one possible implementation, after detecting the first forwarding operation, the computer device can obtain first authentication information of the first leak-proof file from the server. This first authentication information may include various user accounts with operation permissions to the first leak-proof file, and the operation types corresponding to the operation permissions of each user account for the first leak-proof file (e.g., viewing, downloading, saving, etc.). The computer device can determine whether the first user account is among the user accounts with operation permissions to the first leak-proof file by querying the first authentication information, and, if so, whether the operation type corresponding to the first user account's operation permissions for the first leak-proof file includes a download operation. If the first user account is among the user accounts with operation permissions to the first leak-proof file, and the operation type corresponding to the first user account's operation permissions for the first leak-proof file includes a download operation, then it is determined that the first user account has download permissions for the first leak-proof file.

[0118] In another possible implementation, after detecting the first forwarding operation, the computer device can obtain second authentication information for the first leak-proof file from the server. This second authentication information may include various user accounts that have download permissions for the first leak-proof file. For example, after detecting the first forwarding operation, the computer device can send a permission acquisition request. This request may include the file identifier of the first leak-proof file and the permission identifier for downloading the file. After receiving the permission acquisition request, the server returns the second authentication information containing the user accounts that have download permissions for the first leak-proof file to the computer device, which then receives this second authentication information. The computer device can then query the second authentication information to determine whether the first user account is among the user accounts with download permissions for the first leak-proof file. If so, it determines that the first user account has download permissions for the first leak-proof file. In this scheme, the computer device only needs to query the server for user accounts with download permissions for the first leak-proof file, without needing to query user accounts with other permissions for the first leak-proof file. This reduces information interaction with the server during the authentication process, improves authentication efficiency, and saves network resources.

[0119] In another possible implementation, after the computer device detects the first forwarding operation, it can obtain the permission information of the first user account. The permission information of the first user account includes the identifiers of each file that the first user account has operation permissions (such as viewing permissions, download permissions, collection permissions, etc.). The computer device can query the identifier of the first anti-leakage file among the identifiers of each file that the first user account has forwarding permissions. If the identifier of the first anti-leakage file is found, it is determined that the first user account has download permissions for the first anti-leakage file.

[0120] In one possible implementation, the computer device can pre-fetch first / second authentication information of the first anti-leakage file from the server, or pre-fetch permission information of the first user account, and cache the pre-fetched first / second authentication information or permission information in memory. The first application can provide a synchronous permission acquisition interface for reading the first / second authentication information or permission information from the cache. When the computer device queries the first user account's download permission for the first anti-leakage file, it can read the first / second authentication information or permission information from the cache through the synchronous interface, and query whether the first user account has download permission for the first anti-leakage file based on the first / second authentication information or permission information read from the cache. Each time the first application reads the first / second authentication information or permission information from the cache through the synchronous interface, the computer device can simultaneously fetch the first / second authentication information or permission information from the server to refresh the locally cached first / second authentication information or permission information. When the caching / refresh time of the locally cached first / second authentication information or permission information reaches a specified duration, the computer device can clear the locally cached first / second authentication information or permission information.

[0121] In this embodiment of the application, the computer device may pre-fetch the first / second authentication information of the first anti-leakage file from the server after at least one session message enters the selected state and after receiving the first forwarding operation, and before the first anti-leakage file is added to the second application.

[0122] In this process, the computer device can asynchronously retrieve / fetch the first / second authentication information of the first anti-leakage file from the server. In other words, the step of the computer device retrieving / fetching the first / second authentication information of the first anti-leakage file from the server can be executed in parallel with the process of the first application reading the first / second authentication information or permission information from the cache through a synchronous interface.

[0123] Step 230b: If it is found that the first user account has download permissions for the first anti-leakage file, add the first anti-leakage file to the second application.

[0124] In this embodiment of the application, when the computer device finds that the first user account has the permission to download the first anti-leakage file, it can call the interface of the second application to open the second application, for example, open the sending interface of the second application (e.g., the email editing interface), and add the first anti-leakage file to the sending interface of the second application.

[0125] In the scheme shown in the above embodiments of this application, during the authentication process, the computer device queries whether the first user account has download permission for the first anti-leakage file. If so, the first user account is allowed to forward the first anti-leakage file across applications, reusing the download permission of the anti-leakage file as the forwarding permission. There is no need to set additional permissions for the cross-application forwarding of the anti-leakage file, which simplifies the complexity of the authentication system and improves the efficiency of development and testing.

[0126] Based on any one or more embodiments of the above-described embodiments of this application, in one possible implementation, the process of adding the first leak-proof file to the second application may include:

[0127] The system queries the local machine for the first leak protection file that has been downloaded. If the first leak protection file is found, it is added to the second application.

[0128] In this embodiment of the application, if it is found that the first user account has the permission to download the first anti-leakage file, the computer device can query whether the first anti-leakage file has been downloaded to the local machine. If it has been downloaded to the local machine, the local first anti-leakage file is added to the second application.

[0129] When a computer device queries a downloaded first anti-leakage file locally, it can obtain the file address of the first anti-leakage file from at least one session message, and detect whether the file address is a local address or a network address. If the file address is a local address, it is determined that the downloaded first anti-leakage file has been found; otherwise, it is determined that the first anti-leakage file has not yet been downloaded locally.

[0130] When the aforementioned computer device adds the downloaded first anti-leakage file to the second application, it can open the file address of the first anti-leakage file through the file addition function of the second application and add the file corresponding to the file address to the sending interface of the second application.

[0131] For example, a computer device can call the interface of a second application through a first application to pass the file address of a first anti-leakage file to the second application. Then, the second application can open the file address of the first anti-leakage file through its attachment addition function and add the file corresponding to that file address as an attachment in the second application's sending interface.

[0132] In this embodiment of the application, when a computer device adds a first anti-leakage file to a second application, it can add the locally downloaded first anti-leakage file to the second application. This process can be implemented based on the second application's own file addition function, without requiring the first application to pass the first anti-leakage file to the second application. This simplifies the interface call relationship between the first application and the second application and can improve the efficiency of development and testing.

[0133] Based on any one or more embodiments of the above-described embodiments of this application, in one possible implementation, adding the first leak-proof file to the second application further includes:

[0134] If the first leak protection file is not found, download it to your local machine; add the downloaded first leak protection file to the second application.

[0135] In this embodiment of the application, when a computer device adds a first anti-leakage file to a second application, if it determines that the first anti-leakage file has not yet been downloaded locally, it can first download the first anti-leakage file locally, and then add the local first anti-leakage file to the second application.

[0136] For example, when the computer device determines that the first anti-leakage file has not yet been downloaded to the local machine, it automatically downloads the first anti-leakage file to the local machine through the first application, then passes the file address of the first anti-leakage file to the second application, and then opens the file address of the first anti-leakage file through the attachment addition function in the second application, and adds the file corresponding to the file address as an attachment in the sending interface of the second application.

[0137] In this embodiment, when the computer device does not find the downloaded first anti-leakage file locally, it can automatically download the first anti-leakage file to the local machine and add it to the second application. This eliminates the need for manual download by the user, simplifies the user operation steps in the file forwarding process, and improves the file forwarding efficiency.

[0138] Based on any one or more embodiments of the above-described embodiments of this application, in one possible implementation, after downloading the first anti-leakage file to the local machine and adding the first anti-leakage file to the second application, the computer device may also delete the local first anti-leakage file.

[0139] In this embodiment, since the first anti-leakage file is automatically downloaded to the local computer device rather than actively downloaded by the user, the user may not need to use the first anti-leakage file locally in the future. Therefore, after adding the first anti-leakage file to the second application, the computer device can delete the first anti-leakage file locally, thereby avoiding the first anti-leakage file from ineffectively occupying local storage space and saving storage space of the computer device.

[0140] Based on any one or more embodiments of the above embodiments of this application, in one possible implementation, the step of querying the download permission of the first user account for the first anti-leakage file may include:

[0141] Obtain the file type of the first leak protection file; if the file type of the first leak protection file is other than the specified file type, query the download permissions of the first user account for the first leak protection file.

[0142] The specified file type can be a file type pre-set by the developer.

[0143] In this embodiment, not all file types support cross-application forwarding. For example, the specified file types could be voice messages, virtual red envelopes, message cards, etc. Therefore, when querying the first user account's download permissions for the first leak-proof file, the computer device can first obtain the file type of the first leak-proof file. If the file type of the first leak-proof file does not belong to the specified file type, it indicates that the first application supports cross-application forwarding of the first leak-proof file. In this case, the computer device can further query the first user account's download permissions for the first leak-proof file. If the file type of the first leak-proof file belongs to the specified file type, it indicates that the first application does not support cross-application forwarding of the first leak-proof file. In this case, the computer device does not need to query the first user account's download permissions for the first leak-proof file, thereby avoiding a meaningless authentication process and improving authentication efficiency.

[0144] Based on any one or more embodiments of the above embodiments of this application, in one possible implementation, before adding the first anti-leakage file to the second application, the file forwarding method further includes: displaying a first reminder message when at least one session message meets the first reminder condition; the first reminder message is used to indicate that there is a file that cannot be forwarded in at least one session message;

[0145] The first reminder condition includes at least one of the following conditions:

[0146] At least one session message contains a file of the specified file type;

[0147] At least one session message contains a leak-proof file;

[0148] The first user account does not have permission to download the first leak protection file;

[0149] The first leak protection file that was downloaded was not found locally.

[0150] In one possible implementation, after the computer device sets at least one session message to a selected state, it detects whether the at least one session message contains a file of a specified file type and a file protected against file leakage. If the at least one session message contains a file of the specified file type, a reminder message can be displayed: "In the selected message, files of the specified file type do not support being added to the second application." If the at least one session message contains a file protected against file leakage, a reminder message can be displayed: "In the selected message, files without download permissions or not downloaded do not support being added to the second application." If at least one session message contains a file of the specified file type and a file protected against file leakage, a reminder message can be displayed: "In the selected message, files of the specified file type, files without download permissions, or not downloaded do not support being added to the second application."

[0151] In this embodiment, if at least one session message contains a file that does not support forwarding, a file that does not have download permissions, or a file that has not been downloaded, the computer device may also display a reminder message before adding the first anti-leakage file to the second application. For example, a pop-up window containing the reminder message may be displayed to remind the user to confirm whether to forward the currently selected at least one session message to the second application. This reduces the risk of users mistakenly forwarding session messages and causing subsequent forwarding operations, thereby improving the user's interaction efficiency in the process of forwarding files across applications.

[0152] Based on any one or more embodiments of the above embodiments of this application, in one possible implementation, when a preview image of at least one session message is added to the second application, in response to the fact that at least one session message contains a first type of filtered file, the information of the first type of filtered file in the preview image is replaced with first text, which is preset text used to indicate the file type of the first type of filtered file.

[0153] For example, when the first type of filtered file is a video, the first text is "[Video]", when the first type of filtered file is audio, the first text is "[Audio]", and when the first type of filtered file is an image, the first text is "[Image]".

[0154] The first type of filtered file mentioned above includes at least one of the following files: a file of a specified file type, an anti-leakage file that the first user account does not have download permission for, or a file that has not been downloaded.

[0155] Based on any one or more embodiments of the above-described embodiments of this application, in one possible implementation, please refer to... Figure 5 It illustrates a flowchart of a file forwarding method provided in an exemplary embodiment of this application, such as... Figure 5As shown, the above file forwarding method may also include step 250.

[0156] Step 250: Perform leak prevention processing on the first leak prevention file in the second application.

[0157] In this embodiment of the application, the second application can support the function of preventing file leakage.

[0158] For example, when a computer device adds a first leak-proof file to a second application, the first application can indicate to the second application that the first leak-proof file is a file that needs to undergo leak-proof processing. For example, when the computer device calls the interface of the second application through the first application to pass the file address of the first leak-proof file to the second application, an leak-proof tag can be added to the file address of the first leak-proof file. After receiving the file address passed by the first application, the second application can determine that the first leak-proof file corresponding to the file address is a file that needs to undergo leak-proof processing and perform leak-proof processing on the first leak-proof file.

[0159] In this embodiment of the application, after adding the first anti-leakage file from the first application to the second application, anti-leakage processing can be performed on the first anti-leakage file in the second application, thereby ensuring the security of the anti-leakage file after it is transferred across applications.

[0160] Based on any one or more embodiments of the above-described embodiments of this application, in one possible implementation, the above-described leakage prevention treatment includes at least one of the following treatments:

[0161] 1) Add a leak prevention alert element to the file icon of the first leak prevention file.

[0162] Among them, the aforementioned anti-leakage alert element can be the border of the file icon, such as specifying the color / brightness / thickness / style of the icon border; for example, adding a green highlighted border to the file icon of the first anti-leakage file.

[0163] 2) Add a watermark to the preview image of the first leak prevention document.

[0164] In this embodiment of the application, when the first leak-proof file is an image file or a video file, the second application can display a preview image of the first leak-proof file, and the second application can add a watermark to the preview image, for example, adding the first user account or the username corresponding to the first user account as a text watermark to the preview image.

[0165] In another possible implementation, the operation of adding a watermark to the preview image of the first leak-proof file can also be performed by the first application, and the first application can send the watermarked preview image to the second application through the interface of the second application.

[0166] 3) Encrypt the first leak protection file.

[0167] In this application embodiment, when the first anti-leakage file is a text file, spreadsheet, presentation, Portable Document Format (PDF), or other file that supports direct encryption, the computer device can also encrypt the first anti-leakage file in the second application.

[0168] The encrypted password can be set by the user corresponding to the first user account. Alternatively, the encrypted password can be automatically set by the computer device and displayed to both the user corresponding to the first user account and the user corresponding to the second user account.

[0169] In this embodiment of the application, the computer device can improve the security of the first leak-proof file after it is shared across applications by means of reminder elements, watermarks, or encryption in the second application.

[0170] Based on any one or more embodiments of the above embodiments of this application, in one possible implementation, the above file forwarding method further includes the following steps:

[0171] The application receives a second leak-proof file sent by a third user account; in response to receiving a download operation for the second leak-proof file, it queries the first user account's download permission for the second leak-proof file; if it finds that the first user account has download permission for the second leak-proof file, it downloads the second leak-proof file.

[0172] In this embodiment of the application, when a computer device receives a session message forwarded from a first application by another user account through a second application, and the session message contains a second anti-leakage file, if the user corresponding to the first user account needs to download the second anti-leakage file, the computer device can check whether the first user account has the permission to download the second anti-leakage file; if the check determines that the first user account has the permission to download the second anti-leakage file, the second anti-leakage file can be downloaded through the second application.

[0173] In the above embodiments of this application, when a user downloads an anti-leakage file forwarded by another user in the second application, the user can be authenticated, thereby ensuring the security of the anti-leakage file when it is downloaded in the second application and improving the security of the first anti-leakage file after it is shared across applications.

[0174] Based on any one or more embodiments of the above-described embodiments of this application, in one possible implementation, please refer to... Figure 6 It illustrates a flowchart of a file forwarding method provided in an exemplary embodiment of this application, such as... Figure 6As shown, the above file forwarding method may also include steps 260 and 270.

[0175] Step 260: In response to a second forwarding operation that forwards at least one session message in the first application, add at least one session message to the first online document.

[0176] The aforementioned first online document may be a session record document.

[0177] The aforementioned first online document may be an online document opened and displayed through a browser interface, a web page interface, or other application interface, including but not limited to at least one of online session log documents, online spreadsheet documents, online text documents, and online presentation documents.

[0178] In this application embodiment, the first application may also support in-application forwarding of session messages containing anti-leakage files, including individual in-application forwarding and batch in-application forwarding of session messages containing anti-leakage files.

[0179] For example, when a user selects one or more conversation messages in the first conversation interface of the first application and forwards them within the application, if the conversation message contains a leak protection file, the first application can also add the leak protection file along with other conversation messages to the online conversation log document.

[0180] Step 270: Forward the first online document in the first application.

[0181] Computer devices can forward a first online document to a second session interface of the first application through the first application. For example, they can forward a link to the first online document to the second session interface, thereby enabling in-application forwarding of session messages containing leak-proof files.

[0182] For session messages in session-based applications, when the session message contains anti-leakage files, users can directly forward the anti-leakage files in the session message to other users within the application through operations in the session interface, thereby improving the forwarding efficiency of anti-leakage files within the session.

[0183] Based on any one or more embodiments of the above embodiments of this application, in one possible implementation, before adding at least one session message to the first online document, the file forwarding method further includes:

[0184] If at least one session message meets the second reminder condition, a second reminder message is displayed; the second reminder message is used to indicate that at least one session message contains a file that cannot be forwarded; the second reminder condition includes: at least one session message contains a file of a specified file type.

[0185] In one possible implementation, during the in-application session forwarding process, after the computer device sets at least one session message to a selected state, it checks whether the at least one session message contains a file of a specified file type. If the at least one session message contains a file of the specified file type, a reminder message can be displayed: "In the selected message, the file of the specified file type does not support being added to the session record."

[0186] In this embodiment of the application, if at least one session message contains a file that does not support forwarding, the computer device may also display a reminder message before forwarding the first anti-leakage file within the application. For example, a pop-up window containing the reminder message may be displayed to remind the user to determine whether to forward the currently selected at least one session message within the application. This reduces the possibility of incomplete content in the session messages forwarded by the user and improves the user's interaction efficiency during the process of forwarding files within the application.

[0187] Based on any one or more embodiments of the above embodiments of this application, in one possible implementation, when at least one session message is added to the first online document, in response to the fact that at least one session message contains a second type of filtered file, the second type of filtered file is replaced with second text in the first online document, the second text being preset text used to indicate the file type of the second type of filtered file.

[0188] For example, when the second type of filtered file is a video, the second text is "[video]", when the second type of filtered file is audio, the second text is "[audio]", and when the second type of filtered file is an image, the second text is "[image]".

[0189] The second type of filtered file mentioned above includes files of a specified file type.

[0190] Based on any one or more embodiments of the above-described embodiments of this application, in one possible implementation, the file forwarding method further includes:

[0191] Display a second online document sent by a fourth user account, which contains a third leak protection file; in response to a download operation on the third leak protection file, query the first user account's download permissions for the third leak protection file; if the first user account is found to have download permissions for the third leak protection file, download the third leak protection file.

[0192] In this embodiment of the application, when a computer device receives an online document (such as an online session document) forwarded by another user account within the first application, and the online session document contains a third leak protection file, if the user corresponding to the first user account needs to download the third leak protection file, the computer device can check whether the first user account has the permission to download the third leak protection file; if the check determines that the first user account has the permission to download the third leak protection file, the third leak protection file can be downloaded through the first application.

[0193] In the above embodiments of this application, when a user downloads an anti-leakage file forwarded by another user within the first application, the user can be authenticated to ensure the security of the anti-leakage file when it is downloaded in the first application and improve the security of the first anti-leakage file after it is shared within the application.

[0194] Based on any one or more embodiments of the above embodiments of this application, in one possible implementation, the above file forwarding method may further include: inputting at least one session message into a generative language model to obtain summary information output by the generative language model, wherein the summary information is a summary of the content contained in at least one session message;

[0195] Accordingly, step 240 above can be implemented as follows: sending the first anti-leakage file and summary information to the second user account through the second application.

[0196] In this embodiment, the computer device can perform summary extraction processing on at least one session message using a generative language model to obtain summary information. This summary information can be a summary of the message content of at least one session message; for example, it can be text information summarizing the message content of at least one session message. Correspondingly, when forwarding the first anti-leakage file through the second application, the computer device can also send the aforementioned summary information along with the first anti-leakage file to the second user account.

[0197] With the above scheme, when forwarding leak-proof files across applications, the computer device can send the leak-proof file and a summary of the session messages extracted by calling the generative language model together to the second user account. This eliminates the need for the user to manually input descriptions of at least one of the session messages, allowing the recipient to understand the received content in a timely manner through the summary information, thereby significantly improving forwarding efficiency.

[0198] Based on any one or more embodiments of the above embodiments of this application, in one possible implementation, the process of inputting at least one session message into a generative language model and obtaining the summary information output by the generative language model may include:

[0199] Construct a prompt statement containing the session record, which is used to instruct the extraction of a summary of the session record's content; the session record contains at least one session message; input the prompt statement into the generative language model to obtain the summary information output by the generative language model.

[0200] In this embodiment of the application, the generative language model can be a pre-trained language model. The computer device can compose at least one conversation message into a conversation record, and construct a prompt statement that references the conversation record and instructs the generative language model to extract a summary of the conversation record according to a pre-set prompt statement format. For example, the prompt statement can be as follows:

[0201] Please extract a summary from the following conversation log according to the following requirements:

[0202] Requirements: {The input should be as brief as possible, within 20 characters; ...};

[0203] Session log: {Session message 1; Session message 2; ...}.

[0204] After the above prompt statement is constructed, the computer device can input the prompt statement into the generative language model, which will then perform natural language processing on the prompt statement and output summary information.

[0205] In the solution shown in the embodiments of this application, the computer device prompts the generative language model to extract summaries by constructing prompt statements containing session records, which can adapt to any language model and improve the flexibility of summary extraction.

[0206] Based on any one or more embodiments of the above embodiments of this application, in one possible implementation, the second application is an email application, and the step of sending the first anti-leakage file and summary information to the second user account through the second application can be implemented as follows: after adding the first anti-leakage file as an attachment to the email and adding the summary information as the subject of the email, the email is sent to the second user account through the email application.

[0207] When sending emails in an email application, it is usually necessary to set a summary. In this embodiment of the application, in the scenario where the second application is an email application, the computer device can automatically set the summary information as the subject of the email and add the first anti-leakage file as an attachment to the email, without requiring the user to manually set the email subject, thereby improving the efficiency of email editing and sending.

[0208] Based on any one or more embodiments of the above-described embodiments of this application, in one possible implementation, when the computer device forwards the first online document in the first application, it may forward the link of the first online document and the above-described summary information in the first application.

[0209] For example, a computer device can forward the aforementioned summary information and the link to the first online document to the second session interface of the first application through the first application.

[0210] With the above solution, when forwarding online documents containing anti-leakage files within an application, the computer device can forward the link to the online document along with a summary of the session messages extracted by the generative language model. This eliminates the need for users to manually input descriptions of the online document, allowing recipients to quickly understand its content through the summary information, thus significantly improving forwarding efficiency.

[0211] Based on any one or more embodiments of the above embodiments of this application, this application provides a solution for forwarding session messages containing leak-proof files in a session application to other users via email.

[0212] Taking the first application as a conversation sub-application within an office application and the second application as an email sub-application within an office application as examples, please refer to... Figure 7 This illustrates a flowchart of a method for forwarding session messages via email, as described in an embodiment of this application. Figure 7 As shown, the process may include the following steps:

[0213] S701 displays the session message in the first session interface of the session sub-application.

[0214] S702, in response to a selection operation on at least one session message in the first session interface, sets at least one session message to a selected state; the at least one session message contains a first anti-leakage file.

[0215] S703, in response to a first forwarding operation that forwards at least one session message to the email application, and a first user account logged in on the computer device having forwarding permission for the first leak protection file, the first leak protection file is added to the email editing interface of the email sub-application.

[0216] In this embodiment of the application, the computer device can add the first anti-leakage file as an attachment to the email being edited in the email sub-application's email editing interface.

[0217] S704 sends an email containing the first leak protection file to a second user account via the email sub-application.

[0218] In one possible implementation, step S703 includes: in response to the first forwarding operation, querying the first user account's download permission for the first anti-leakage file; if it is found that the first user account has download permission for the first anti-leakage file, adding the first anti-leakage file to the email editing interface of the email sub-application.

[0219] In one possible implementation, adding the first anti-leakage file to the email editing interface of the email sub-application includes: querying the locally downloaded first anti-leakage file; and if the downloaded first anti-leakage file is found, adding the downloaded first anti-leakage file to the email editing interface of the email sub-application.

[0220] In one possible implementation, adding the first leak-proof file to the second application includes:

[0221] If the first leak protection file is not found, download it to your local machine; add the downloaded first leak protection file to the email editing interface of the email sub-application.

[0222] In one possible implementation, the above scheme also includes:

[0223] Perform leak prevention processing on the first leak-proof file in the email sub-application.

[0224] In one possible implementation, the above scheme also includes:

[0225] Receive a second leak protection file sent by a third user account via the email sub-application; display the second leak protection file in the email viewing interface of the email sub-application; in response to receiving a download operation for the second leak protection file, query the first user account's download permission for the second leak protection file; if the query finds that the first user account has download permission for the second leak protection file, download the second leak protection file via the email sub-application.

[0226] Based on any one or more embodiments of the above embodiments of this application, this application also provides a scheme for forwarding a session message containing a leak-proof file in one session interface of a session application to the current session interface / another session interface in the session application.

[0227] Taking the first application as a conversation sub-application within an office application and the second application as an email sub-application within an office application as examples, please refer to... Figure 8 This illustrates a flowchart of an in-application session record forwarding method according to an embodiment of this application. Figure 8 As shown, the process may include the following steps:

[0228] S801, displays the session message in the first session interface of the session sub-application.

[0229] S802, in response to a selection operation on at least one session message in the first session interface, sets at least one session message to a selected state; the at least one session message contains a first anti-leakage file.

[0230] S803, in response to a second forwarding operation that forwards at least one session message in a session sub-application, adds at least one session message to the first session record.

[0231] The first session record corresponds to the first online document in the above embodiment.

[0232] S804, forwards the first session record in the session sub-application.

[0233] For example, forwarding the link to the first session record in a session sub-application.

[0234] The computer device may forward the first session record to the current first session interface, or to other session interfaces outside the first session interface.

[0235] In one possible implementation, the above scheme also includes:

[0236] Display the second session record sent by the fourth user account (corresponding to the second online document in the above embodiment), the second session record contains the third leak protection file; in response to the download operation of the third leak protection file, query the first user account's download permission for the third leak protection file; if it is found that the first user account has the download permission for the third leak protection file, download the third leak protection file in the second session record through the session sub-application.

[0237] The solution shown in the above embodiments of this application can support the forwarding of files to prevent leakage during the batch forwarding of cross-application or intra-application session messages through multi-select function integration, permission following mechanism and edge scene processing.

[0238] Multi-selection functionality integration: The core of the solution described in this application is to overcome the limitation that anti-leakage files (such as documents / videos / images) do not support multi-selection for adding to documents / other applications, and to unify the multi-selection logic. This improvement can greatly enhance the efficiency of user operations, especially in scenarios where batch processing of anti-leakage content to documents or emails is required.

[0239] In terms of technical implementation, the logic for multi-selection of files has been redesigned, which can accurately handle each selected content during multi-selection.

[0240] Permission follow-up mechanism:

[0241] When a protected-for-leak (CFLAP) file is added to an email or document, its permissions follow those of the CFLAP file sender. Whether it's inserted into a document as a session record or appears in an email as text (images) or attachments (files, videos), consistent permissions are ensured.

[0242] In the solutions shown in the above embodiments of this application, both document and email applications introduce the same anti-leakage permission control logic as chat, accurately controlling file permissions in various operation scenarios within documents and email.

[0243] Edge scene processing:

[0244] This application proposes different processing methods for inserting documents and inserting emails. For example, when inserting documents, the format and multiple selections are ensured to be added as session records, and special message types are judged; when inserting emails, different operations are performed based on whether download permissions are available and whether the email is actually downloaded, while also taking into account the situation of the email sender within the scope of the enterprise's document leakage prevention measures.

[0245] This application provides an improved product feature that allows users to select multiple leak-proof files at once and add them to a document or email in a unified manner. Specific features include:

[0246] I. Insert Email Address:

[0247] 1) Select the leak protection resources to be added in the chat (the leak protection resources correspond to the leak protection files mentioned above; for example, leak protection resources can have a green border), and click the Add to button to bring up the sheet menu.

[0248] 2) Select Add to Mail in the sheet menu.

[0249] 3) Choose to create a new email or send an email to group members (this affects the recipient information).

[0250] Please refer to Figure 9 This illustrates a schematic diagram of adding session messages to an email according to an embodiment of this application. Figure 9As shown, the user selects multiple conversation messages in the conversation interface using a multi-select method. The selected conversation messages are indicated by a checkmark 901. The user clicks the add button 902, a menu pops up, and then clicks the email control 903 in the menu. At this time, the conversation interface pops up email creation options, including the new email option 904 and the send to group chat members option 905. The user clicks the new email option 904 or the send to group chat members option 905, and the computer device opens the email editing interface. The email editing interface adds the files from the conversation messages, including but not limited to PDF document type leak-proof files 906 and image type leak-proof files 907.

[0251] 4) Fill in the recipient's name and send the email. The recipient will open the email and the files, pictures and videos will be protected against data leakage (the sender is within the scope of the data leakage protection).

[0252] Please refer to Figure 10 This illustrates a schematic diagram of the email receiving side involved in an embodiment of this application. For example... Figure 10 As shown, after the recipient receives the email, they open the email viewing interface 1001. The attachment bar displays the files from the conversation message, including but not limited to PDF document type protected files 1002 and image type protected files 1003. These protected files have undergone anti-leakage processing; for example, both PDF document type protected files 1002 and image type protected files 1003 have borders of a specified color added to indicate that the file is protected against leakage. When the user clicks on the image protected file 1003, an image preview interface 1004 is displayed, showing a preview image of the image protected file 1003. A watermark 1005 can be overlaid on this preview image.

[0253] The above is a branch of the main process for adding leak-proof chat files to the email. Other product features exist for edge computing scenarios:

[0254] 1) If the anti-leakage file has not been downloaded or you do not have permission to download it, a pop-up message will be displayed when you click "Add to Email".

[0255] Please refer to Figure 11 The diagram illustrates a pop-up notification as described in an embodiment of this application. Figure 11 As shown, the user-selected session messages contain leak-proof images and videos, some of which may not have been downloaded or for which the user does not have permission to download. In this case, the computer device can display a pop-up prompt 1101, prompting the user to check if there are any files in the selected session messages that the user does not have permission to download or that have not been downloaded.

[0256] 2) Files without download permissions and files that have not been downloaded were replaced with text when added to emails.

[0257] Please refer to Figure 12This illustrates a schematic diagram of text replacement involved in an embodiment of this application. For example... Figure 12 As shown, the user-selected conversation messages contain leak-proof images and videos. These leak-proof images and videos are files that have not been downloaded or for which the user does not have download permissions. When a conversation message is added to the email editing interface, the images and videos will not be added to the email editing interface; instead, the corresponding text "1201" will only be displayed in the preview image of the conversation message added to the email editing interface.

[0258] Users are prompted about unsupported message types, which are then filtered out during the email addition process.

[0259] Please refer to Figure 13 This illustrates a schematic diagram of email forwarding involved in an embodiment of this application. Figure 13 As shown, the user-selected conversation messages include leak-proof images, videos, and voice messages 1301. The leak-proof images and videos are files that have not been downloaded or for which there is no download permission. Voice messages 1301 are message types that do not support forwarding. When a conversation message is added to the email editing interface, the images, videos, and voice messages 1301 will not be added to the email editing interface. Instead, the corresponding text 1302 will only be displayed in the preview image of the conversation message added to the email editing interface.

[0260] II. Inserting a document:

[0261] Compared to inserting emails, inserting documents does not check download permissions. Inserting a document displays as a conversation record without converting it into text. Opening the conversation record in a document behaves almost identically to opening it in a chat conversation. The implementation process is as follows:

[0262] 1) After selecting the leak prevention file to be added, click Add to Document. You can choose to create a new document or select an existing document.

[0263] 2) Selecting a document will open the target document, which will be displayed as a session record.

[0264] 3) Clicking to open the conversation history behaves the same as opening the conversation history in the chat conversation, and the permissions follow the permissions of the original resource.

[0265] Please refer to Figure 14 This diagram illustrates the session record forwarding involved in an embodiment of this application. Please refer to... Figure 14 This illustrates a schematic diagram of session message forwarding to other sessions according to an embodiment of this application. Figure 14As shown, users can select multiple conversation messages in the conversation interface using a multi-select method. The selected conversation messages are indicated by a checkmark. Users can add the selected conversation messages to the conversation message record by clicking "New Document" 1401 or selecting an existing document 1402. After selecting the conversation to send the message record to, the user sends the message record to the conversation interface of another conversation. When the user clicks on the conversation message record 1403 in the conversation interface of another conversation, the conversation message record interface is opened, which displays multiple conversation messages 1404. When users view / download the anti-leakage file in the conversation message, they also need to verify their permissions for the anti-leakage file.

[0266] For edge cases, adding to a document does not offer download and permission options; it only checks the message type.

[0267] Please refer to Figure 15 The diagram illustrates a pop-up notification as described in an embodiment of this application. Figure 15 As shown, if the user selects multiple conversation messages, including voice messages 1501 that do not support forwarding, the computer device can display a pop-up prompt 1502, asking the user to confirm whether to forward the conversation message containing the voice message.

[0268] The logical flow of the technical implementation of this application is as follows:

[0269] 1) Under certain conditions, add an entry point for adding to email documents to the multi-select message menu.

[0270] Specific conditions include whether email document services are available, etc.

[0271] 2) Check and process the selected message type, check download permissions, and check and process whether the message has been downloaded to the local machine.

[0272] Adding to a document only requires checking the message type, while adding to an email requires checking the message type, download permissions, and whether the message has already been downloaded.

[0273] Adding messages to emails requires checking the message type: Email addition only supports text, files, images, and videos. Therefore, it's necessary to check if the selected message contains any other message types besides text, files, images, and videos, such as red envelopes and voice messages. If any special message types are found, a pop-up window should inform the user that these special message types are not supported for addition to emails, and the special message types should be filtered out.

[0274] Adding files to emails requires checking download permissions and whether they have been downloaded: Since adding files, images, and videos to emails requires adding them from local files, it is necessary to check the download permissions of the leak-proof resources. This requires initiating a network request to authenticate the download permissions of the files from the server (a function already implemented in the previous leak-proof process). If the server responds normally and the file has download permissions, then it is determined whether the file has been downloaded to the local machine based on the file path.

[0275] Adding to Document Message Type Check: Because adding to a document only displays as a session record, and opening the session record still uses the chat test capability, this part reuses the check logic for multi-select message forwarding to the session. More message types may be supported.

[0276] 3) Add leak-proof resources to email and documents. Resources in documents and email need to be leak-proofed.

[0277] For email, if the leak-protected resources in the message have been processed in the previous steps, the leak protection measures are determined based on whether the sender of the email is within the scope of the leak protection measures. The leak protection measures include displaying a green border on the outer layer, displaying a watermark on the resource preview page, and determining whether to download or save the resource based on whether the user has download permissions.

[0278] For documents, simply display the leak-protected session logs within the document; clicking to display the session logs will still invoke the chat application's capabilities. The chat application's leak-protected access control system can be directly reused.

[0279] Please refer to Figure 16 It illustrates a workflow diagram related to embodiments of this application; Figure 16 Taking the more complex example of adding to an email address, adding to a document involves fewer download permission checks, and message type checks and filtering differ between documents and emails, but the overall workflow is similar. Figure 16 As shown, the workflow may include the following steps:

[0280] In S1601, upon receiving a multi-select session message, the session application checks if the email document service is available. If yes, proceed to S1602; otherwise, end.

[0281] S1602, Add a function entry; the conversation application can add a function entry to forward to email or document in the pop-up menu.

[0282] S1603, Message Type Check; Session application checks the message type of multiple selected session messages.

[0283] S1604, the session application checks whether the selected session messages contain unsupported message types. If yes, proceed to S1605; otherwise, proceed to S1607.

[0284] S1605, Pop-up Warning: A pop-up message is displayed in the conversation to warn the user that there are messages that cannot be forwarded.

[0285] S1606, Message Filtering: After the user clicks OK, the session application filters out files that do not support forwarding during the file addition process.

[0286] S1607, Download permission check; The session application checks whether the current user has download permission for the leak-proof files in the multi-selected session messages. If yes, proceed to S1608; otherwise, proceed to S1610.

[0287] S1608, Download check: The session application checks whether the files (including but not limited to anti-leakage files) in the selected session messages have been downloaded to the local machine. If yes, proceed to S1609; otherwise, proceed to S1610.

[0288] S1609, Resources added to application; the email application adds resources downloaded locally to the email editing interface.

[0289] S1610, Replace with text added to the application; The email application adds preview images of selected conversation messages to the email editing interface, where files that cannot be forwarded, have no download permissions, or have not been downloaded are replaced with specified text by the email application or the conversation application.

[0290] S1611, Check if it is within the protection range; When an email application sends an email containing a protected file, it can check if the sender of the protected file is within the protection range of the protected file. If so, proceed to S1612; otherwise, end.

[0291] S1612, Resource Leakage Prevention: The email application performs leak prevention processing on leak-proof files in multiple selected conversation messages, such as adding borders of specified colors, adding watermarks, etc.

[0292] Please refer to Figure 17 It illustrates a system architecture diagram related to an embodiment of this application, showing the system architecture and the relationships between the modules as follows: Figure 17 As shown (using "added to email" as an example; "added to document" only includes partial content):

[0293] Message module 1701: This is the module for generating and preprocessing leak prevention resources. It provides the preprocessed leak prevention resources to the interface layer for further processing.

[0294] ①Message multi-selection provides the ability to select messages in batches, controls the entry and exit of the multi-selection state throughout the process, and is a source of preventing leaked resources.

[0295] ② Message type checking: Different message type checking rules have been set for email and documents, and pop-up prompts have been made for which types of messages.

[0296] ③ Message filtering: Based on the results of message type checks, different message types that should not be supported are filtered.

[0297] ④ Pop-up prompts: Based on the results of the message type check, pop-up prompts are given to users for different content combinations, so that users understand which types of messages are not supported for addition.

[0298] Interface layer 1702: This is the bridge between the message module and the email module. The leak-proof content contained in the message cannot be directly recognized and used by the email module and needs to be processed.

[0299] ① Message type determination: Determine whether each message is a file, image, or video, and process them differently accordingly.

[0300] ② For message processing with download permissions, mark videos, files and images, determine message download permissions from the anti-leakage module, obtain the local path of the resource, and attach message type tags for use by the email module.

[0301] ③ Replace text for files without download permissions: If you do not have download permissions for files, images, or videos, or if they have not been downloaded, you need to convert the resources into placeholder text [files][images][videos] according to their type.

[0302] Email module 1703: Receives data from the interface layer and ultimately converts the leak protection resources from the message into the leak-protected body or attachments of the email.

[0303] ① The email service is enabled to determine whether the "Add to Email" function entry is enabled, because the "Add to Email" function depends on the email service being enabled.

[0304] ② Add resources to emails. Data from the interface layer is used to add images to the body of the email and files and videos to the email attachments, based on type tags and local paths.

[0305] ③ Leakage prevention measures: Determine whether the email sender is within the scope of the company's leakage prevention measures and decide whether to implement leakage prevention measures for the resources. This includes drawing an outer green border, watermarking the file preview page, and handling the file download function based on whether download permissions are available.

[0306] The anti-leakage module 1704 is the module that carries the anti-leakage permissions. It implements the file permission management framework and provides numerous interfaces for the message module, interface layer and email module to call.

[0307] ① It carries the leakage prevention function, the specific implementation of leakage prevention resource management, and the module that carries the access control function.

[0308] ② Download permission judgment: retrieve information on whether the resource has download permission based on the resource's identifier (ID).

[0309] ③ File download judgment: Determine if the file exists locally based on the file path, and determine if the file has been downloaded completely.

[0310] ④ Determine the scope of use for leakage prevention: Determine whether a member is within the scope of use for leakage prevention to decide whether to implement leakage prevention measures for the resources issued by that member.

[0311] Furthermore, the process of adding anti-leakage resources to emails requires batch checking and processing of download permissions for these resources to determine whether to insert them as the original files or as replacement text. The original process required synchronous checks of file download permissions, but fetching anti-leakage download permissions from the server requires asynchronous network requests. Transforming the logic for adding anti-leakage resources to emails into an asynchronous process is challenging due to its complexity and legacy issues. A possible solution is to pre-fetch download permissions for selected anti-leakage resources at an appropriate time and cache them in memory. Provide a synchronous interface for obtaining permissions from the cache, ensuring seamless integration of anti-leakage download permission retrieval with the original synchronous email resource insertion process. Each time download permissions for anti-leakage files are synchronously obtained, data should also be fetched from the server to refresh the local cache. An expiration mechanism should be introduced for the local cache to meet the product's timeliness requirements. A suitable cache expiration time needs to be set considering the time interval of the entire operation.

[0312] The timing of pre-fetching is crucial: it should be done after the message is selected and the "Add Email" button is clicked. This is because only at this point can the resources to be processed be retrieved, and the user's action is to add the message to their email. It's also necessary to ensure that the email resource addition synchronous reading operation only occurs after the asynchronous network request callback. Pre-fetching the anti-leakage download permission should begin immediately after the email button is clicked, followed by synchronous execution of the permission reading and user pop-up selection. Since network requests typically operate on the order of tens to hundreds of milliseconds, this ensures that the synchronously retrieved permissions are the latest ones from the server.

[0313] The solutions shown in the above embodiments of this application can have the following effects:

[0314] Improved efficiency: Users can directly add chat leak prevention resources in batches to emails and documents, which is different from saving them individually to local storage and then manually adding them to documents and emails, greatly improving the efficiency of the operation.

[0315] Enhance data security: Anti-leakage resources are added to documents and emails, and the resources are protected from leakage based on whether the sender of the document is within the scope of anti-leakage protection.

[0316] Please refer to Figure 18 This diagram illustrates a structural block diagram of a file forwarding apparatus provided in an exemplary embodiment of this application. This file forwarding apparatus can be used to perform all or part of the steps in the file forwarding methods shown in the above embodiments of this application. The file forwarding apparatus includes:

[0317] The session message display module 1801 is used to display at least one session message in the first session interface of the first application, wherein the at least one session message contains a first anti-leakage file;

[0318] The message selection module 1802 is configured to set the at least one session message to a selected state in response to a selection operation on the at least one session message.

[0319] The file adding module 1803 is used to respond to a first forwarding operation that forwards the at least one session message to the second application, and the first user account logged in on the computer device has forwarding permission for the first anti-leakage file, by adding the first anti-leakage file to the sending interface of the second application.

[0320] The file sending module 1804 is used to send the first anti-leakage file to the second user account through the second application.

[0321] In one possible implementation, the file adding module 1803 is configured to, in response to the first forwarding operation, query the first user account's download permission for the first anti-leakage file; and, if it is found that the first user account has download permission for the first anti-leakage file, add the first anti-leakage file to the second application.

[0322] In one possible implementation, the file adding module 1803 is used to query the downloaded first anti-leakage file locally; if the downloaded first anti-leakage file is found, the downloaded first anti-leakage file is added to the second application.

[0323] In one possible implementation, the file adding module 1803 is used to download the first anti-leakage file to the local machine if the first anti-leakage file is not found; and to add the downloaded first anti-leakage file to the second application.

[0324] In one possible implementation, the file adding module 1803 is used to obtain the file type of the first anti-leakage file; if the file type of the first anti-leakage file belongs to a file type other than the specified file type, it queries the download permission of the first user account for the first anti-leakage file.

[0325] In one possible implementation, the device further includes:

[0326] The first reminder module is used to display a first reminder message when at least one session message meets the first reminder condition before the file addition module 1803 adds the first anti-leakage file to the second application; the first reminder message is used to indicate that there is a file that cannot be forwarded in the at least one session message;

[0327] The first reminder condition includes at least one of the following conditions:

[0328] At least one session message contains a file of a specified file type;

[0329] The first user account does not have permission to download the first anti-leakage file;

[0330] The first anti-leakage file that was downloaded was not found locally.

[0331] In one possible implementation, the device further includes:

[0332] A processing module is used to perform anti-leakage processing on the first anti-leakage file in the second application.

[0333] In one possible implementation, the leak prevention process includes at least one of the following processes:

[0334] Add a leak prevention alert element to the file icon of the first leak prevention file;

[0335] Add a watermark to the preview image of the first leak-proof file;

[0336] The first leak-proof file is encrypted.

[0337] In one possible implementation, the device further includes:

[0338] The file receiving module is used to receive a second leak-proof file sent by a third user account through the second application;

[0339] The first permission query module is used to query the first user account's download permission for the second anti-leakage file in response to receiving a download operation for the second anti-leakage file;

[0340] The first download module is used to download the second anti-leakage file when it is found that the first user account has download permissions for the second anti-leakage file.

[0341] In one possible implementation, the device further includes:

[0342] A message adding module is configured to add the at least one session message to a first online document in response to a second forwarding operation that forwards the at least one session message in the first application;

[0343] The document forwarding module is used to forward the first online document in the first application.

[0344] In one possible implementation, the device further includes:

[0345] The first reminder module is used to display a second reminder message when the at least one session message meets the second reminder condition before the message adding module adds the at least one session message to the first online document; the second reminder message is used to indicate that there is a file in the at least one session message that cannot be forwarded.

[0346] The second reminder condition includes: the existence of a file of a specified file type in at least one session message.

[0347] In one possible implementation, the device further includes:

[0348] The document display module is used to display a second online document sent by a fourth user account, which contains a third leak-proof file;

[0349] The second permission query module is used to query the first user account's download permission for the third anti-leakage file in response to the download operation of the third anti-leakage file;

[0350] The second download module is used to download the third anti-leakage file if it is found that the first user account has download permissions for the third anti-leakage file.

[0351] In one possible implementation, the device further includes:

[0352] The summary extraction module is used to input the at least one conversation message into the generative language model and obtain the summary information output by the generative language model, wherein the summary information is a summary of the content contained in the at least one conversation message;

[0353] The file sending module 1804 is used to send the first anti-leakage file and the summary information to the second user account through the second application.

[0354] In one possible implementation, the summary extraction module is used for,

[0355] Construct a prompt statement containing session records, the prompt statement being used to instruct the extraction of a summary of the content of the session records; the session records contain the at least one session message;

[0356] The prompt statement is input into the generative language model to obtain the summary information output by the generative language model.

[0357] In one possible implementation, the second application is an email application, and the file sending module 1804 is used to send the email to the second user account through the email application after adding the first anti-leakage file as an attachment to the email and adding the summary information as the subject of the email.

[0358] Please refer to Figure 19 , Figure 19 This is a structural block diagram of a computer device provided in an exemplary embodiment of this application. The computer device 1900 includes a Central Processing Unit (CPU) 1901, a system memory 1904 including Random Access Memory (RAM) 1902 and Read-Only Memory (ROM) 1903, and a system bus 1905 connecting the system memory 1904 and the CPU 1901. The computer device 1900 also includes a Basic Input / Output System (I / O System) 1906 that facilitates information transfer between various devices within the computer, and a mass storage device 1907 for storing the operating system 1913, application programs 1914, and other program modules 1915.

[0359] The basic input / output system 1906 includes a display 1908 for displaying information and an input device 1909 for user input, such as a mouse or keyboard. Both the display 1908 and the input device 1909 are connected to the central processing unit 1901 via an input / output controller 1910 connected to the system bus 1905. The basic input / output system 1906 may also include the input / output controller 1910 for receiving and processing input from multiple other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 1910 also provides output to a display screen, printer, or other types of output devices.

[0360] The mass storage device 1907 is connected to the central processing unit 1901 via a mass storage controller (not shown) connected to the system bus 1905. The mass storage device 1907 and its associated computer-readable media provide non-volatile storage for the computer device 1900. That is, the mass storage device 1907 may include computer-readable media (not shown) such as a hard disk or a CD-ROM (Compact Disc Read-Only Memory) drive.

[0361] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include RAM (Random Access Memory), ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technologies, CD-ROM, DVD (Digital Video Disc) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Of course, those skilled in the art will recognize that the computer storage media are not limited to the above-mentioned types. The system memory 1904 and mass storage device 1907 described above can be collectively referred to as memory.

[0362] Computer device 1900 can be connected to the Internet or other network devices via network interface unit 1911 connected to the system bus 1905.

[0363] The memory also includes one or more programs / instructions, which are stored in the memory. The central processing unit 1901 executes the one or more programs / instructions to implement all or part of the steps in the methods shown in the above embodiments of this application.

[0364] In an exemplary embodiment, this application provides a chip that includes programmable logic circuits and / or program instructions. When the chip is run on a computer device, it is used to implement the file forwarding method provided in the above method embodiments.

[0365] This application provides a computer-readable storage medium storing a computer program that is loaded and executed by a processor to implement the file forwarding method provided in the above method embodiments.

[0366] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, causing the processor to load and execute them to implement the file forwarding method provided in the above method embodiments.

[0367] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0368] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0369] It should be noted that the collection and processing of relevant data (such as user accounts, authentication information, and permission information) in this application should strictly comply with the requirements of relevant national laws and regulations, obtain the informed consent or separate consent of the personal information subject, and carry out subsequent data use and processing within the scope of laws and regulations and the authorization of the personal information subject.

[0370] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0371] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A file forwarding method, characterized in that, The method is performed by a computer device, and the method includes: Display session messages in the first application; In response to a selection operation on at least one session message in the first application, the at least one session message is set to a selected state; the at least one session message contains a first anti-leakage file; In response to a first forwarding operation that forwards the at least one session message to a second application, and a first user account logged in on the computer device having forwarding permission for the first anti-leakage file, the first anti-leakage file is added to the second application; The first anti-leakage file is sent to the second user account through the second application.

2. The method according to claim 1, characterized in that, The first forwarding operation, in response to forwarding the at least one session message to the second application, and the first user account logged in on the computer device having forwarding permissions for the first anti-leakage file, includes adding the first anti-leakage file to the second application, comprising: In response to the first forwarding operation, query the first user account's download permissions for the first anti-leakage file; If it is found that the first user account has download permissions for the first anti-leakage file, the first anti-leakage file is added to the second application.

3. The method according to claim 2, characterized in that, Adding the first anti-leakage file to the second application includes: Search locally for the first leak prevention file that has been downloaded; If the downloaded first anti-leakage file is found, add the downloaded first anti-leakage file to the second application.

4. The method according to claim 3, characterized in that, Adding the first anti-leakage file to the second application includes: If the first anti-leakage file is not found, download the first anti-leakage file to the local machine; Add the downloaded first anti-leakage file to the second application.

5. The method according to any one of claims 2 to 4, characterized in that, The querying of the first user account's download permissions for the first anti-leakage file includes: Obtain the file type of the first anti-leakage file; If the file type of the first anti-leakage file is other than the specified file type, query the download permissions of the first user account for the first anti-leakage file.

6. The method according to claim 5, characterized in that, Before adding the first leak-proof file to the second application, the method further includes: If at least one session message meets the first reminder condition, a first reminder message is displayed; the first reminder message is used to indicate that there is a file in the at least one session message that cannot be forwarded. The first reminder condition includes at least one of the following conditions: At least one session message contains a file of a specified file type; The first user account does not have permission to download the first anti-leakage file; The first anti-leakage file that was downloaded was not found locally.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: In the second application, the first leak-proof file is subjected to leak-proof processing.

8. The method according to claim 7, characterized in that, The leak prevention treatment includes at least one of the following: Add a leak prevention alert element to the file icon of the first leak prevention file; Add a watermark to the preview image of the first leak-proof file; The first leak-proof file is encrypted.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Receive a second leak-proof file sent by a third user account through the second application; In response to receiving a download operation for the second anti-leakage file, query the first user account's download permissions for the second anti-leakage file; If it is found that the first user account has download permission for the second anti-leakage file, then download the second anti-leakage file.

10. The method according to claim 1, characterized in that, The method further includes: In response to a second forwarding operation that forwards the at least one session message in the first application, the at least one session message is added to the first online document; Forward the first online document in the first application.

11. The method according to claim 10, characterized in that, Before adding the at least one session message to the first online document, the method further includes: If at least one session message meets the second reminder condition, a second reminder message is displayed; the second reminder message is used to indicate that there is a file in the at least one session message that cannot be forwarded. The second reminder condition includes: the existence of a file of a specified file type in at least one session message.

12. The method according to claim 10 or 11, characterized in that, The method further includes: Displays a second online document sent by a fourth user account, which contains a third leak-proof document; In response to the download operation of the third anti-leakage file, query the first user account's download permissions for the third anti-leakage file; If it is found that the first user account has download permission for the third leak protection file, then the third leak protection file is downloaded.

13. The method according to any one of claims 1 to 12, characterized in that, The method further includes: The at least one conversation message is input into a generative language model to obtain summary information output by the generative language model, wherein the summary information is a summary of the content contained in the at least one conversation message; Sending the first anti-leakage file to the second user account via the second application includes: The first anti-leakage file and the summary information are sent to the second user account through the second application.

14. The method according to claim 13, characterized in that, The step of inputting the at least one conversation message into the generative language model to obtain the summary information output by the generative language model includes: Construct a prompt statement containing session records, the prompt statement being used to instruct the extraction of a summary of the content of the session records; the session records contain the at least one session message; The prompt statement is input into the generative language model to obtain the summary information output by the generative language model.

15. The method according to claim 13 or 14, characterized in that, The second application is an email application, and the step of sending the first anti-leakage file and the digest information to the second user account through the second application includes: After adding the first leak-proof file as an attachment to the email and adding the summary information as the subject of the email, the email is sent to the second user account through the email application.

16. A file forwarding device, characterized in that, The device includes: A session message display module is used to display at least one session message in the first session interface of the first application, wherein the at least one session message contains a first anti-leakage file; The message selection module is used to set the at least one session message to a selected state in response to a selection operation on the at least one session message. The file adding module is used to respond to a first forwarding operation that forwards the at least one session message to the second application, and the first user account logged in on the computer device has forwarding permission for the first anti-leakage file, and add the first anti-leakage file to the sending interface of the second application. The file sending module is used to send the first anti-leakage file to the second user account through the second application.

17. A computer device, characterized in that, The computer device includes a processor and a memory, the memory storing at least one program, which is loaded and executed by the processor to implement the file forwarding method as described in any one of claims 1 to 15.

18. A computer-readable storage medium, characterized in that, The storage medium stores at least one program, which is loaded and executed by a processor to implement the file forwarding method as described in any one of claims 1 to 15.

19. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the file forwarding method as described in any one of claims 1 to 15.

Images