CN113992650A

CN113992650A - File processing method and device, electronic equipment and computer readable storage medium

Info

Publication number: CN113992650A
Application number: CN202010661489.2A
Authority: CN
Inventors: 黄铁鸣; 陈晓波; 康龙炀; 文琛; 李斌
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-07-10
Filing date: 2020-07-10
Publication date: 2022-01-28
Anticipated expiration: 2040-07-10
Also published as: CN113992650B

Abstract

The invention provides a file processing method, a file processing device, electronic equipment and a computer readable storage medium; the method comprises the following steps: responding to the file selection operation, and determining the selected file as a file which needs to be sent to a receiving account by the sharing account; the type of at least one receiving account is a heterogeneous system account, and the heterogeneous system account and the sharing account belong to different systems; responding to a file sharing operation, and sending the file to a first system server so as to enable the first system server to execute the following processing: and sending the file to a storage server for storage, acquiring a link for storing the file by the storage server, and sending the link to a receiving account with the type of the heterogeneous system account through a cross-system communication interface. By the method and the device, the cross-system file sharing can be realized.

Description

File processing method and device, electronic equipment and computer readable storage medium

Technical Field

The present invention relates to internet technologies, and in particular, to a file processing method and apparatus, an electronic device, and a computer-readable storage medium.

Background

With the continuous development of internet technology, especially mobile internet, the file sharing function is widely used in scenes such as online social contact, online office and the like. For example, a user may share files such as pictures, documents, audio, and video with other users in the same system through a file sharing function provided by the client.

Currently, the file sharing function provided by the related art is limited in a homogeneous system, for example, a file can be shared only between clients accessing the same system. For file sharing between heterogeneous systems (i.e. cross-system), there is no effective solution for related technologies due to differences between different systems.

Disclosure of Invention

The embodiment of the invention provides a file processing method and device, electronic equipment and a computer readable storage medium, which can realize cross-system file sharing.

The technical scheme of the embodiment of the invention is realized as follows:

the embodiment of the invention provides a file processing method, which comprises the following steps:

responding to the file selection operation, and determining the selected file as a file which needs to be sent to a receiving account by the sharing account;

the type of at least one receiving account is a heterogeneous system account, and the heterogeneous system account and the sharing account belong to different systems;

responding to a file sharing operation, and sending the file to a first system server so as to enable the first system server to execute the following processing:

sending the file to a storage server for storage, acquiring a link for storing the file by the storage server, and

and sending the link to a receiving account with the type of the heterogeneous system account through a cross-system communication interface.

In the foregoing solution, the determining, in response to the file selection operation, the selected file as a file that needs to be sent to the receiving account by the sharing account includes:

presenting a file list in response to a file viewing operation received in a chat page of a communication group;

the communication group comprises the sharing account and at least one heterogeneous system account belonging to a different system with the sharing account;

in response to a file selection operation received in the file list, determining the selected file as a file which needs to be sent to the receiving account by the sharing account;

the receiving account is at least one account in the communication group except the sharing account.

In the above aspect, the method further includes:

in response to an account selection operation received in a chat page of the communication group, determining the selected account as the receiving account;

the selected account includes at least one heterogeneous system account belonging to a different system from the sharing account.

in response to a file selection operation received in a file management page, determining a selected file as a file to be sent by the sharing account;

in the above aspect, the method further includes:

in response to an account selection operation received in an address book page, determining at least one selected account in the address book page and/or accounts in at least one contact group as the receiving account;

In the foregoing solution, after the sending the link to the heterogeneous system account by invoking the cross-system communication interface, the method further includes:

presenting prompt information and/or sending the prompt information to the heterogeneous system account;

wherein the prompt message is used for prompting that the file is stored in the storage server.

In the above scheme, the link is used for the heterogeneous system account to download the file from the storage server, or for the heterogeneous system account to transfer the file from the storage server to an available storage space;

the available storage space is the available storage space corresponding to the heterogeneous system account in the storage server.

An embodiment of the present invention provides a file processing apparatus, including:

the file selection module is used for responding to the file selection operation and determining the selected file as a file which needs to be sent to the receiving account by the sharing account;

the file sharing module is used for responding to a file sharing operation and sending the file to a first system server so that the first system server executes the following processing: and sending the file to a storage server for storage, acquiring a link for storing the file by the storage server, and sending the link to a receiving account with the type of the heterogeneous system account through a cross-system communication interface.

In the above scheme, when the same history file as the file is already stored in the storage server, the link is a multiplexed link for storing the history file; when the same history file as the file is not stored in the storage server, the link is a link newly generated by the storage server to store the file.

In the above scheme, when the file sharing operation is used to share a plurality of different files at one time, the link points to the plurality of different files stored in the storage server, so as to serve as a uniform download link or a uniform dump link of the plurality of different files.

In the above scheme, the file is stored in a storage space registered by the sharing account in the storage server; after the link is sent and the file stored by the storage server is updated by the sharing account, the file before updating is used for uniformly responding to a downloading request or a unloading request aiming at the link; the updated file is used for uniformly responding to a downloading request or a unloading request aiming at the link; or the file before updating is used for uniformly responding to a downloading request or a transferring request of a first heterogeneous system account aiming at the link, the first heterogeneous system account is a heterogeneous system account which does not need to be synchronized, the updated file is used for uniformly responding to a downloading request or a transferring request of a second heterogeneous system account aiming at the link, and the second heterogeneous system account is a heterogeneous system account which needs to be synchronized.

In the above scheme, the file selection module is further configured to present a file list in response to a file viewing operation received in a chat page of the communication group; the communication group comprises the sharing account, at least one heterogeneous system account belonging to a different system from the sharing account, and at least one homogeneous system account belonging to the same system as the sharing account; in response to a file selection operation received in the file list, determining the selected file as a file which needs to be sent to the receiving account by the sharing account; the receiving account is at least one account in the communication group except the sharing account.

In the above scheme, the file selection module is further configured to determine, in response to an account selection operation received in a chat page of the communication group, a selected account as the receiving account; the selected account includes at least one heterogeneous system account belonging to a different system from the sharing account.

In the above scheme, the file selection module is further configured to determine, in response to a file selection operation received in a file management page, a selected file as a file to be sent by the sharing account; in response to an account selection operation received in an address book page, determining at least one selected account in the address book page and/or accounts in at least one contact group as the receiving account; the selected account includes at least one heterogeneous system account belonging to a different system from the sharing account.

In the above scheme, the file sharing module is further configured to generate a sharing identifier representing that the file needs to be stored in the storage server when the receiving account includes at least one heterogeneous system account belonging to a different system from the sharing account; sending the sharing identifier and the file to a first system server so that the first system server sends the file to the storage server for storage according to the sharing identifier; the first system server is a server in a system to which the sharing account belongs.

In the above scheme, the file sharing module is further configured to determine a capacity of the file; and when the receiving account includes at least one heterogeneous system account belonging to a different system from the sharing account and the file capacity exceeds a file capacity threshold, generating the sharing identification representing that the file needs to be stored in the storage server.

In the above scheme, the file sharing module is further configured to determine an available storage space corresponding to the sharing account in the storage server; and when the receiving account number comprises at least one heterogeneous system account number belonging to a different system from the sharing account number, the capacity of the file exceeds a file capacity threshold value, and the capacity of the file does not exceed the available storage space, generating the sharing identification representing that the file needs to be stored in the storage server.

In the above solution, the file processing apparatus further includes: the prompting module is used for presenting capacity prompting information when the receiving account number comprises at least one heterogeneous system account number belonging to a different system from the sharing account number, the capacity of the file exceeds a file capacity threshold value, and the capacity of the file exceeds the available storage space; the capacity prompt information is used for prompting the sharing account to expand the available storage space and/or prompting the sharing account to clear the used storage space corresponding to the sharing account in the storage server.

In the above scheme, the file sharing module is further configured to, when the number of the receiving accounts is multiple and the multiple receiving accounts include homogeneous system accounts belonging to the same system as the sharing account, call a communication interface of a first system server, and send the file to the homogeneous system accounts; the first system server is a server in a system to which the sharing account belongs.

In the foregoing solution, the cross-system communication interface includes: a first system access layer arranged in the first system server, a second system access layer arranged in the second system server, and a cross-system access layer arranged in the cross-system communication server; the first system server is a server in a system to which the sharing account belongs, and the second system server is a server in a system to which the heterogeneous system account belongs; the first system server is further configured to send, through the first system access layer and via the cross-system access layer, the link and the heterogeneous system account to the cross-system communication server, so that the cross-system communication server maps the heterogeneous system account to an associated account that can be identified by the second system server according to a mapping relationship, and send, through the cross-system access layer and via the second system access layer, the link and the associated account to the second system server, so that the second system server sends the link to the associated account; the mapping relation comprises the heterogeneous system account which can be identified by the first system server and an associated account which can be identified by the second system server.

In the above scheme, the file sharing module is further configured to present, in response to the file sharing operation, a sharing message corresponding to the file in a chat page, where the sharing message includes the link; responding to a message selection operation in the chat page, and determining at least one selected message, wherein the selected message comprises at least one sharing message; merging the selected at least one message into a chat log message; when the receiving account number comprises a homogeneous system account number belonging to the same system as the sharing account number, sending the chat record message to the homogeneous system account number by calling a communication interface of a first system server; the first system server is a server in a system to which the sharing account belongs; and when the receiving account number comprises a heterogeneous system account number belonging to a different system with the sharing account number, sending the chat record message to the heterogeneous system account number by calling the cross-system communication interface.

In the foregoing solution, after sending the file to the first system server to enable the first system server to send the file to the storage server for storage, the file processing apparatus further includes: a link presenting module, configured to receive the link sent by the first system server, and present the link in a chat page of the sharing account sharing file (for example, a chat page of a communication group in which the sharing account participates); in response to a link sharing operation, sending the link to the first system server to cause the first system server to perform the following: and sending the link to a receiving account with the type of the heterogeneous system account through a cross-system communication interface.

In the above scheme, the prompt module is further configured to present prompt information, and/or send the prompt information to the heterogeneous system account; wherein the prompt message is used for prompting that the file is stored in the storage server.

In the above scheme, the link is used for the heterogeneous system account to download the file from the storage server, or for the heterogeneous system account to transfer the file from the storage server to an available storage space; the available storage space is the available storage space corresponding to the heterogeneous system account in the storage server.

receiving a link sent by a sharing account to a receiving account by calling a cross-system communication interface;

the receiving account is a heterogeneous system account which belongs to a different system from the sharing account;

and responding to the trigger operation aiming at the link, and acquiring the file from a storage server according to the link.

In the foregoing solution, the obtaining the file from the storage server according to the link in response to the trigger operation for the link includes:

downloading the file from the storage server in response to the downloading operation for the link; alternatively, the first and second electrodes may be,

and in response to the unloading operation aiming at the link, unloading the file into an available storage space corresponding to the receiving account in the storage server.

In the above aspect, the method further includes:

determining the capacity of the file corresponding to the link;

and automatically downloading the file from the storage server when the capacity of the file does not exceed a file capacity threshold.

the receiving module is used for receiving a link sent by the sharing account to the receiving account by calling the cross-system communication interface;

and the file acquisition module is used for responding to the trigger operation aiming at the link and acquiring the file from the storage server according to the link.

In the above scheme, the file obtaining module is further configured to respond to the downloading operation for the link, and download the file from the storage server; or, in response to a transfer operation for the link, transferring the file to an available storage space in the storage server corresponding to the receiving account.

In the above scheme, the file obtaining module is further configured to determine a capacity of the file corresponding to the link; and automatically downloading the file from the storage server when the capacity of the file does not exceed a file capacity threshold.

An embodiment of the present invention provides an electronic device, including:

a memory for storing computer executable instructions;

and the processor is used for realizing the file processing method provided by the embodiment of the invention when executing the computer executable instructions stored in the memory.

The embodiment of the invention provides a computer-readable storage medium, which stores computer-executable instructions and is used for causing a processor to execute the computer-readable storage medium to realize the file processing method provided by the embodiment of the invention.

The embodiment of the invention has the following beneficial effects:

by calling a cross-system communication interface, a sharer can send a file to a sharing object without the client through a file sharing function of the client; and in the cross-system communication process, the file to be shared is sent to the first system server, so that the first system server stores the file to the storage server, and sends the link of the file stored by the storage server to the sharing object, thereby saving background service resources used during file transmission and further ensuring that the transmission of other non-file messages cannot be delayed.

Drawings

FIG. 1 is a schematic diagram of a document processing system according to an embodiment of the present invention;

fig. 2A is a schematic structural diagram of a first terminal 400 according to an embodiment of the present invention;

fig. 2B is a schematic structural diagram of a second terminal 500 according to an embodiment of the present invention;

FIG. 3 is a flowchart illustrating a file processing method according to an embodiment of the present invention;

FIG. 4 is a flowchart illustrating a file processing method according to an embodiment of the present invention;

FIG. 5 is a flowchart illustrating a file processing method according to an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a document processing system according to an embodiment of the present invention;

FIG. 7 is a flowchart illustrating a file processing method according to an embodiment of the present invention;

fig. 8A and fig. 8B are schematic diagrams of application scenarios of a file processing method according to an embodiment of the present invention;

fig. 9A, 9B and 9C are schematic diagrams of application scenarios of the file processing method according to the embodiment of the present invention;

fig. 10 is a schematic application scenario diagram of a file processing method according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail with reference to the accompanying drawings, the described embodiments should not be construed as limiting the present invention, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used herein is for the purpose of describing embodiments of the invention only and is not intended to be limiting of the invention.

Before further detailed description of the embodiments of the present invention, terms and expressions mentioned in the embodiments of the present invention are explained, and the terms and expressions mentioned in the embodiments of the present invention are applied to the following explanations.

1) In response to the condition or state on which the performed operation depends, one or more of the performed operations may be in real-time or may have a set delay when the dependent condition or state is satisfied; there is no restriction on the order of execution of the operations performed unless otherwise specified.

2) The sharer is a sharing initiator, an account held by the sharer is called a sharing account, a sharing object (or called a sharee) is a target shared by the sharer, an account held by the sharing object is called a receiving account, and the sharing object may be a social network contact (for example, a friend associated with the social account, an information exchange platform associated with the social account, or an exchange group associated with the social account), an email contact, or a short message contact of the sharer.

3) The heterogeneous system account refers to an account belonging to a different system. For example, the account a belongs to the system a, the account B belongs to the system B, and the system a and the system B cannot communicate directly with each other, so that the account a and the account B are heterogeneous system accounts of each other.

4) The homogeneous system account refers to an account belonging to the same system. For example, the account a and the account B belong to the same system a, and the account a and the account B can directly communicate with each other through a server in the system a, so that the account a and the account B are isomorphic system accounts of each other.

5) The network disk, also called network hard disk and network U disk, is an online storage service provided by a storage server in a network. The network disk provides file management functions of storage, sharing, access, backup and the like of files for users. The user can manage or edit the files in the network disk through the network.

Referring to fig. 1, fig. 1 is a schematic structural diagram of a document processing system according to an embodiment of the present invention. Wherein, file processing system includes: the first system server 100 in the first system, the second system server 200 in the second system, the cross-system communication server 300, the first terminal 400, and the second terminal 500 will be described separately.

The first system and the second system are heterogeneous systems of each other and provide services for the accessed terminal respectively. For example, the first system server 100 is for providing a service to the first terminal 400 accessing the first system server 100. The second system server 200 is for providing a service to the second terminal 500 accessing the second system server 200.

Communication between the first system and the second system is cross-system communication, and is supported by the cross-system communication server 300, for example, communication services are provided to a client accessed in the first system and a client accessed in the second system.

In some embodiments, the first terminal 400 and the second terminal 500 implement the file processing method provided by the embodiments of the present invention by running a computer program, which may be a native program or a software module in an operating system; can be a local (Native) Application program (APP), i.e. a program that needs to be installed in an operating system to run; or may be an applet, i.e. a program that can be run only by downloading it to the browser environment; but also an instant messaging applet or file management applet that can be embedded in any APP. In general, the computer program may be any application, module or plug-in that may be in any form.

For example, the first terminal 400 runs the first client 410, the second terminal 500 runs the second client 510, and particularly, the first client 410 may be a computer program (e.g., enterprise WeChat) that provides an Internet social service for enterprise users, and the second client 510 may be a computer program (e.g., WeChat) that provides an Internet social service for individual users, or vice versa.

The embodiment of the invention can be realized by means of Cloud Technology (Cloud Technology), which is a hosting Technology for unifying series resources such as hardware, software, network and the like in a wide area network or a local area network to realize the calculation, storage, processing and sharing of data.

The cloud technology is a general term of network technology, information technology, integration technology, management platform technology, application technology and the like applied based on a cloud computing business model, can form a resource pool, is used as required, and is flexible and convenient. Cloud computing technology will become an important support. The file sharing function between the servers (e.g., the first system server 100, the second system server 200, and the cross-system communication server 300) may be implemented by a cloud technology.

For example, the first system server 100, the second system server 200, and the cross-system communication server 300 may be independent physical servers, may be a server cluster or a distributed system configured by a plurality of physical servers, and may be cloud servers providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a web service, cloud communication, a middleware service, a domain name service, a security service, a CDN, and a big data and artificial intelligence platform, but are not limited thereto.

Next, the structures of the first terminal 400 and the second terminal 500 provided by the embodiment of the present invention are explained. Referring to fig. 2A and fig. 2B, fig. 2A is a schematic structural diagram of a first terminal 400 according to an embodiment of the present invention, and fig. 2B is a schematic structural diagram of a second terminal 500 according to an embodiment of the present invention.

The first terminal 400 shown in fig. 2A includes: at least one processor 410, memory 450, at least one network interface 420, and a user interface 430. The various components in the first terminal 400 are coupled together by a bus system 440. It is understood that the bus system 440 is used to enable communications among the components. The bus system 440 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 440 in fig. 2A.

The Processor 410 may be an integrated circuit chip having Signal processing capabilities, such as a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like, wherein the general purpose Processor may be a microprocessor or any conventional Processor, or the like.

The user interface 430 includes one or more output devices 431, including one or more speakers and/or one or more visual displays, that enable the presentation of media content. The user interface 430 also includes one or more input devices 432, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

The memory 450 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard disk drives, optical disk drives, and the like. Memory 450 optionally includes one or more storage devices physically located remote from processor 410.

The memory 450 includes either volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory. The nonvolatile memory may be a Read Only Memory (ROM), and the volatile memory may be a Random Access Memory (RAM). The memory 450 described in embodiments of the invention is intended to comprise any suitable type of memory.

In some embodiments, memory 450 is capable of storing data, examples of which include programs, modules, and data structures, or a subset or superset thereof, to support various operations, as exemplified below.

An operating system 451, including system programs for handling various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and handling hardware-based tasks;

a network communication module 452 for communicating to other computing devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 including: bluetooth, wireless compatibility authentication (WiFi), and Universal Serial Bus (USB), etc.;

a presentation module 453 for enabling presentation of information (e.g., user interfaces for operating peripherals and displaying content and information) via one or more output devices 431 (e.g., display screens, speakers, etc.) associated with user interface 430;

an input processing module 454 for detecting one or more user inputs or interactions from one of the one or more input devices 432 and translating the detected inputs or interactions.

In some embodiments, the file processing apparatus provided by the embodiments of the present invention can be implemented by various forms of computer programs executed by the first terminal 400, such as the operating system 451, the first client 410, software modules, and scripts described above. Fig. 2A shows a file processing apparatus 455 stored in the memory 450, comprising the following software modules: a file selection module 4551 and a file sharing module 4552, which are logical and thus may be arbitrarily combined or further split depending on the functions implemented. The functions of the respective modules will be explained below.

The second terminal 500 shown in fig. 2B includes: at least one processor 510, memory 550, at least one network interface 520, and a user interface 530. The various components in the second terminal 500 are coupled together by a bus system 540. It is understood that the bus system 540 is used to enable communications among the components. The bus system 540 includes a power bus, a control bus, and a status signal bus in addition to a data bus. But for clarity of illustration the various buses are labeled as bus system 540 in figure 2B. The memory 550 includes an operating system 551, a network communication module 552, a presentation module 553, an input processing module 554, and a file processing device 555, and the user interface 530 includes an output device 531 and an input device 532.

It should be noted that the functions of the processor 510, the memory 550, the network interface 520, the user interface 530, the bus system 540, the processor 410, the memory 450, the network interface 420, the user interface 430, and the bus system 440 in the first terminal 400 are similar, and will not be described again.

In some embodiments, the file processing apparatus provided by the embodiments of the present invention may be implemented by various forms of computer programs run by the second terminal 500, such as the operating system 551, the second client 510, software modules and scripts described above. Fig. 2B shows a file handling device 555 stored in memory 550, which may be software in the form of programs and plug-ins, etc., including the following software modules: a receiving module 5551 and a file acquiring module 5552, which are logical and thus may be arbitrarily combined or further split according to the implemented functions. The functions of the respective modules will be explained below.

Next, a file processing method provided by the embodiment of the present invention cooperatively implemented by the first terminal 400 and the second terminal 500 in fig. 1 will be described as an example.

Hereinafter, the explanation is made based on the following scenarios: the first terminal 400 operates a first client, and the second terminal 500 operates a second client, where a login account in the first client is a sharing account that needs to share a file, and a login account in the second client is a target account (i.e., a receiving account) that shares the file with the sharing account.

It should be noted that the method shown in fig. 3 can be executed by various forms of computer programs executed by the first terminal 400 and the second terminal 500, and is not limited to the first client and the second client, such as the operating system 451, the software modules and the scripts described above, and therefore the first client and the second client should not be considered as limiting the embodiments of the present invention.

It should be noted that, because the above-mentioned "first" and "second" are relative, for other application scenarios, for example, the login account in the second client is a sharing account that needs to share a file, and the login account in the first client is a target account that shares the file with the sharing account, which can be implemented according to the following understanding.

In step S101, in response to a file selection operation, the first client determines the selected file as a file that the sharing account needs to send to the receiving account.

Here, the sharing account is an account belonging to the sharer, and thus the first client in step S101 specifically refers to the first client logged in with the sharing account. The receiving account is an account belonging to a sharing object, and the receiving account has two types, one is an isomorphic system account belonging to the same system as the sharing account, and the other is a heterogeneous system account belonging to a different system from the sharing account.

Here, the number of the accounts receiving the file in step S101 is one or more (i.e., at least two), and the accounts receiving the file include at least one heterogeneous system account belonging to a different system from the sharing account.

In some embodiments, the first client presents a list of files in response to a file viewing operation received in a chat page of the communication group; the communication group comprises a sharing account, at least one heterogeneous system account belonging to a different system with the sharing account, and at least one homogeneous system account belonging to the same system with the sharing account; responding to a file selection operation received in the file list, and determining the selected file as a file which needs to be sent to a receiving account by the sharing account; the receiving account is at least one account except for the sharing account in the communication group.

Here, the file list may be a list of files stored in the first client, or may be a list of files stored in the cloud corresponding to the sharing account, for example, a list of files stored in the storage server corresponding to the sharing account. Therefore, the sharer can share the locally stored file and can also share the file stored in the cloud.

For example, fig. 8B is a chat page of a communication group, and the member list 803 of the communication group includes two accounts of the first system and two accounts of the second system. When "bob testa" is a shared account, "bob testb", "bob teste", and "bob cycle" are receiving accounts, wherein "bob yttestb" is a homogeneous system account belonging to the same system as the shared account, and "bob teste" and "bob cycle" are heterogeneous system accounts belonging to different systems from the shared account. Therefore, when a sharer sends a file in a chat page of the communication group, the file or the link sent by the sharing account can be received no matter whether the receiving account in the communication group is a homogeneous system account belonging to the same system as the sharing account or a heterogeneous system account belonging to a different system from the sharing account.

As an example, a sharer may specify a sharing object to receive a file in a group chat, and as such, the method further comprises: the method comprises the steps that a first client responds to account selection operation received in a chat page of a communication group, and the selected account is determined to be a receiving account; the selected account includes at least one heterogeneous system account belonging to a different system from the sharing account.

For example, in fig. 8B, when "BobbyTestA" is a sharing account, "BobbyTestA" may select at least one heterogeneous system account belonging to a different system from the sharing account as a receiving account among "BobbyTestB", "BobbyTestE", and "bobbychen" in a chat page of the communication group. Therefore, the sharer can pertinently send the file in the communication group, and only the sharing object appointed by the sharer can receive the file, so that the privacy of file sending can be ensured.

In some embodiments, the first client presents a list of files in response to a file viewing operation received in the personal chat page; the account corresponding to the chat object in the personal chat page is a receiving account, and the receiving account is at least one heterogeneous system account belonging to a different system with the sharing account; and responding to the file selection operation received in the file list, and determining the selected file as a file which needs to be sent to the receiving account by the sharing account. Therefore, the sharer can send files to heterogeneous system accounts belonging to different systems with the sharing account through personal chat.

In still other embodiments, the first client determines, in response to a file selection operation received in the file management page, the selected file as a file to be sent by the sharing account; as such, the method further comprises: and in response to the account selection operation received in the address book page, determining the selected at least one account in the address book page and/or the account in the at least one contact group as a receiving account.

Here, the selected account includes at least one heterogeneous system account belonging to a different system from the sharing account.

By way of example, the account selection process may be located before or after the file selection process, and is not limited herein. The file management page and the address book page can be displayed simultaneously, for example, the file management page and the address book page are displayed in a split screen manner; the file management page is displayed above the address book page in a floating layer mode (the account number selection process is positioned before the file selection process), so that the file management page has transparency and cannot completely shield the address book page; the address book page is displayed above the file management page in a floating layer mode (the account number selection process is positioned after the file selection process), so that the address book page has transparency and cannot completely shield the file management page. Of course, the file management page and the address book page may not be displayed at the same time, for example, when the account number selection process is located before the file selection process and a file selection operation is received, the file management page is switched from the address book page to be presented; and when the account selecting process is positioned after the file selecting process and an account selecting operation is received, switching from the file management page to the address list presenting page.

Here, the file management page includes a file list, where the file list includes at least one file, and the file list may be a list of files stored in the first client, or may also be a list of files stored in the cloud corresponding to the sharing account, for example, a list of files stored in the storage server corresponding to the sharing account. Therefore, the sharer can share the locally stored file and can also share the file stored in the cloud.

In step S102, the first client sends the file to the first system server in response to the file sharing operation.

Here, the file sharing operation may be various forms of operations that are preset by the operating system and do not conflict with the registered operation; or may be various forms of operations that are user-defined and that do not conflict with registered operations. The file sharing operation comprises at least one of the following operations: click operations (e.g., single-finger click operations, multi-finger click operations, multiple continuous click operations, etc.); a sliding operation in a specific track or direction; performing voice operation; a motion sensing operation (e.g., an operation of moving up and down, a curved motion operation, or the like). Therefore, the sharing operation convenience of the user can be improved.

In some embodiments, the first client responds to a file sharing operation, and when the receiving account includes at least one heterogeneous system account belonging to a different system from the sharing account, the first client generates a sharing identifier representing that a file needs to be stored in the storage server; and sending the sharing identifier and the file to the first system server so that the first system server sends the file to the storage server for storage according to the sharing identifier. Therefore, as long as the receiving account comprises the heterogeneous system account belonging to different systems with the sharing account, the first system server is indicated to send the file to the storage server, so that background service resources used during file transmission can be saved, and further, the transmission of other non-file messages can be ensured not to be delayed.

Here, the first system server is a server in a system (or referred to as a first system) to which the sharing account belongs. The storage server may be a server independent from the first system server, or may be a storage module (e.g., a network disk) in the first system server.

In other embodiments, the first client determines a capacity of the file in response to the file sharing operation; when the receiving account includes at least one heterogeneous system account belonging to a different system from the sharing account and the file capacity exceeds a file capacity threshold (for example, 100M), generating a sharing identifier representing that the file needs to be stored in a storage server; and sending the sharing identifier and the file to the first system server so that the first system server sends the file to the storage server for storage according to the sharing identifier.

Here, the file size threshold may be a default value or a value set by the sharer.

In the embodiment of the invention, as long as the receiving account comprises the heterogeneous system account belonging to a different system from the sharing account and the file has an overlarge capacity, the first system server is instructed to send the file with the overlarge capacity to the storage server, so that the situation that the file with the overlarge capacity is directly shared with the sharing object to occupy the service resource of the background can be avoided, and further, the transmission of other non-file messages can be ensured not to have time delay. However, when the file capacity does not exceed the file capacity threshold, the file does not need to be transmitted to the storage server, and the transmission of the small-capacity file does not consume too many background service resources, so that the small-capacity file can be directly sent to the receiving account in the form of the file, and the file transmission rate can be improved.

In still other embodiments, the first client determines, in response to a file sharing operation, a capacity of a file and an available storage space of a corresponding sharing account in the storage server; when the receiving account number comprises at least one heterogeneous system account number belonging to a different system from the sharing account number, the capacity of the file exceeds a file capacity threshold value, and the capacity of the file does not exceed an available storage space, generating a sharing identification representing that the file needs to be stored in a storage server; and sending the sharing identifier and the file to the first system server so that the first system server sends the file to the storage server for storage according to the sharing identifier.

In the embodiment of the invention, because the first system server directly stores the file into the available storage space of the corresponding sharing account in the storage server, before uploading the file, the first client needs to judge whether the file stored in the storage server exceeds the limit, so that file transmission failure caused by insufficient capacity of the available space is avoided, and the reliability of file transmission can be ensured.

In some embodiments, when the receiving account includes at least one heterogeneous system account belonging to a different system from the sharing account, the capacity of the file exceeds a file capacity threshold, and the capacity of the file exceeds an available storage space, the first client presents capacity prompt information; the capacity prompt information is used for prompting the sharing account to expand the available storage space and/or prompting the sharing account to clear the used storage space of the corresponding sharing account in the storage server.

For example, in fig. 8A and 8B, a prompt message "the file is greater than 100M, the user of the second system cannot view the file, and the file can be sent to the user of the second system in a link form after the administrator is contacted to expand the microdisk", so that the sharer can be prompted that the capacity of the file to be shared exceeds the available storage space of the microdisk, thereby avoiding file transmission failure due to insufficient capacity of the available space, and ensuring the reliability of file transmission.

In step S103, the first system server sends the file to the storage server for storage, and obtains a link of the storage server to store the file.

Here, the concrete expression of the link includes at least one of: the text of the link; a graphical code (e.g., a bar code or two-dimensional code); an acoustic wave signal. The link is used for a receiving account (including a homogeneous system account and a heterogeneous system account) to download a file from a storage server, or used for the receiving account to transfer the file from the storage server to an available storage space; the available storage space is the available storage space corresponding to the received account in the storage server.

In some embodiments, the first system server determines a storage address of the file in the storage server, and generates a link corresponding to the storage address, wherein the link is used for the receiving account to acquire the file from the storage server according to the storage address.

In some embodiments, the first system server sends the file to the storage server to cause the storage server to: when the history file which is the same as the file is stored in the storage server, multiplexing a link which is used for storing the history file in the storage server to the link which is used for storing the history file, wherein the link which is obtained by the first system server is the multiplexed link which is used for storing the history file; when the history file with the same file is not stored in the storage server before responding to the file sharing operation, the file is stored, and a link pointing to the stored file is generated, wherein the link acquired by the first system server is a link newly generated by the storage server for storing the file.

Here, the history file is a file that is repeatedly uploaded by the sharing account and is the same as the file or a file that is uploaded by another account and is the same as the file.

As an example, the process of the storage server detecting whether the storage space contains the same history file as the file may be: the storage server compares the digital fingerprint (such as a data abstract) of the file with the digital fingerprint of the file already stored in the storage server; when the comparison is successful, determining that the historical file which is the same as the file is stored in the storage server; and when the comparison is not successful, determining that the history file which is the same as the file is not stored in the storage server.

Therefore, the storage space of the storage server can be prevented from being occupied by repeated files uploaded by the same or different users, and the redundancy of the files is avoided; and the time for uploading the file can be saved while the user uploads the repeated file.

In other embodiments, the first system server sends the file to the storage server to cause the storage server to: the storage server acquires a stored similar file which comprises part of the same content as the file in a storage space; determining the similar files and the content with the difference of the files, storing the content with the difference, fusing the content with the difference with the similar files to generate a fused file identical to the files, and generating a link pointing to the stored fused file, wherein the link acquired by the first system server is the link generated by the storage server for storing the fused file.

Taking the file as an example of a photo album, when the first system server sends a photo album containing photo 1, photo 2 and photo 3 to the storage server, the storage server detects in the storage space to obtain a similar photo album partially similar to the photo album, where the similar photo album contains photo 1 and photo 2. Thus, the storage server does not need to store photos 1 and 2 again, but only needs to store the part (i.e. photo 3) where the photo album and the similar photo album have differences. Therefore, the uploading speed of the file can be improved, and the storage space of the storage server can be saved.

In some embodiments, when the file sharing operation is used to share a plurality of different files at once, the first system server sends the plurality of different files to the storage server and obtains a unified link storing the plurality of different files from the storage server. Therefore, the sharing account can share the files by sending the links once, so that the situation that the background service resources are wasted by generating the links is avoided.

Here, the link (i.e., unified link) acquired by the first system server refers to a plurality of different files stored in the storage server as a unified download link or a unified dump link for the plurality of different files. The unified link is used for receiving the account number to acquire a plurality of different files at one time.

In some embodiments, the file is stored in a storage space registered by the sharing account in the storage server; after the link is sent to the receiving account, and when the file stored by the storage server is logged in the storage server by the shared account (for example, the shared account is logged in a network disk) and is updated, the storage server uses the file before updating to uniformly respond to a downloading request or a transferring request aiming at the link; or the storage server uses the updated file to uniformly respond to the downloading request or the unloading request aiming at the link; or the storage server uses the file before updating to uniformly respond to the downloading request or the unloading request of the first heterogeneous system account aiming at the link, and uses the file after updating to uniformly respond to the downloading request or the unloading request of the second heterogeneous system account aiming at the link.

Here, the first heterogeneous system account is a heterogeneous system account that does not need synchronization, and the second heterogeneous system account is a heterogeneous system account that needs synchronization.

For example, after the sharing account a sends a link corresponding to a file to the receiving account B, the sharing account a updates the file in the storage server, where the updated file occupies a new storage space of the storage server. When the receiving account B initiates a file acquisition request to the storage server for the link, the storage server may respond to the file acquisition request according to the file before update, or may respond to the file acquisition request according to the file after update. Here, the file version acquired by the receiving account B from the storage server according to the link may be a default of the system, or may be specified by the sharing account a, which is not limited herein. It should be noted that, when a plurality of receiving accounts are included, the sharing account can designate at least one receiving account for acquiring a file before updating or at least one receiving account for acquiring an updated file among the plurality of receiving accounts. Therefore, the safety of the data stored in the storage server can be ensured while the diversity of data acquisition is realized.

In some embodiments, after step S103, the method may further include: a first client receives a link sent by a first system server, and presents the link in a chat page of a sharing account sharing file (for example, a communication group in which the sharing account participates or a chat page of a personal chat); in response to the link sharing operation, sending a link to the first system server to cause the first system server to perform the following: and sending the link to the receiving account of which the type is the heterogeneous system account through a cross-system communication interface. Therefore, the sharer can acquire the file sending condition in time to avoid file sending omission, and the sharer can subsequently forward the shared object again according to the link presented in the interface to strongly prompt the shared object.

In step S104, the first system server sends a link to the second client through the cross-system communication interface.

Here, the second client specifically refers to a second client that logs in a receiving account of which the type is a heterogeneous system account.

That is to say, the second client receives the link sent by the sharing account to the heterogeneous system account by calling the cross-system communication interface.

In some embodiments, the above cross-system communication interface includes: the system comprises a first system access layer arranged in a first system server, a second system access layer arranged in a second system server and a cross-system access layer arranged in a cross-system communication server; the first system server sends a link to the second client through the cross-system communication interface: the link and the heterogeneous system account are sent to the cross-system communication server through the cross-system access layer through the first system access layer, so that the cross-system communication server maps the heterogeneous system account into a related account which can be identified by the second system server according to the mapping relation, and the link and the related account are sent to the second system server through the cross-system access layer through the second system access layer, so that the second system server sends the link to the related account.

Here, the mapping relationship includes a heterogeneous system account that can be recognized by the first system server and an associated account that can be recognized by the second system server, and the second system server is a server in a system (or referred to as a second system) to which the heterogeneous system account belongs.

In some embodiments, when the number of the receiving accounts is multiple and the multiple receiving accounts include homogeneous system accounts belonging to the same system as the sharing account, the first client invokes a communication interface of the first system server to send a file or a link to the homogeneous system accounts, so that the replacing step of step S104 is: and the first system server sends a file or a link to the first client logged in with the homogeneous system account.

Here, since the sharing account does not need to perform cross-system communication when sending a file to the homogeneous system account belonging to the same system as the sharing account, consumed background service resources are less, and therefore, the file can be directly sent to the homogeneous system account without sending a link, so that the homogeneous system account does not need to download the file from the storage server, and the rate of receiving the file by the homogeneous system account is improved.

As an example, when the capacity of the file exceeds a file capacity threshold (e.g., 100M), the first client calls a communication interface of the first system server to send the file to the homogeneous system account; and when the capacity of the file exceeds the file capacity threshold, calling a communication interface of the first system server, and sending a link to the isomorphic system account.

Here, since the sharing account sends a file with a large capacity to the isomorphic system account belonging to the same system as the sharing account, the embodiment of the present invention sends a link corresponding to the file to the isomorphic system account, so that it is possible to avoid directly sharing the file with the large capacity to the isomorphic system account and occupying too much service resources of the first system server, and it is further possible to ensure that no delay occurs in transmission of the remaining non-file messages sent to the isomorphic system account.

In the embodiment of the invention, different communication interfaces are called to send the file or the link to the receiving account numbers belonging to different systems, so that the file transmission efficiency can be improved.

In step S105, the second client acquires the file from the storage server according to the link in response to the trigger operation for the link.

Here, step S105 is an optional step.

In some embodiments, the second client determines a capacity of the corresponding linked file; and automatically downloading the file from the storage server when the capacity of the file does not exceed the file capacity threshold.

In other embodiments, the second client downloads the file from the storage server in response to a download operation for the link.

For example, in FIG. 9A, when the user triggers the share link 901 of "100M Large File. zip", a preview interface of the file "100M Large File. zip" is presented; when the user triggers the download button 902, the file "more than 100M big file. zip" can be downloaded locally.

As an example, the second client downloads the file from the storage server in response to a download operation for the link when the size of the file exceeds a file size threshold.

In some embodiments, the second client determines a capacity of the corresponding linked file; and when the capacity of the file does not exceed the file capacity threshold, automatically transferring the file to an available storage space corresponding to the receiving account in the storage server.

In other embodiments, the second client, in response to the dump operation for the link, dumps the file into the available storage space of the corresponding receiving account in the storage server.

As an example, when the capacity of the file exceeds the file capacity threshold, the second client, in response to a dump operation for the link, dumps the file into an available storage space of the storage server corresponding to the receiving account.

Taking the example that the link is a graphic code, the second client identifies the corresponding link from the graphic code in response to the scanning operation for the graphic code, and downloads the file from the storage server according to the link, or transfers the file to an available storage space of the corresponding receiving account in the storage server.

According to the embodiment of the invention, the sharing object is supported to download the file to the local or store the file to the cloud according to the link, so that the diversity of the file acquired by the user can be improved; and the files with smaller capacity are automatically downloaded or stored, so that the operation of the user can be reduced, and the efficiency of receiving the files by the user is improved.

Referring to fig. 4, fig. 4 is a schematic flowchart of a file processing method according to an embodiment of the present invention, and based on fig. 3, a step S106 may be further included after step S104.

In step S106, the first client presents the prompt information.

Here, the prompt information is used to prompt that the file has been stored to the storage server.

For example, in fig. 8A and 8B, a prompt message "the file is larger than 100M, and the file is uploaded to the microdisk and sent to the user of the second system in a link form in order to ensure that the user of the second system can view the file normally" is presented, so that the sharer can be prompted that the file has been transferred to the microdisk.

In some embodiments, the first client sends a prompt to the receiving account to cause the second client to present the prompt. Therefore, the sharing object can be prompted to transmit the file to the storage server, so that the sharing object can acquire the file from the storage server through the link.

Referring to fig. 5, fig. 5 is a schematic flowchart of a file processing method according to an embodiment of the present invention, and based on fig. 3, after step S104, step S107 to step S109 may further be included, where step S105 and step S107 to step S109 are not in sequence, and may be executed in parallel or in sequence.

In step S107, the first client presents the sharing message of the corresponding file in the chat page.

Here, the sharing message includes a link.

In some embodiments, the first client presents a sharing message corresponding to the file in the chat page in response to the file sharing operation.

For example, in fig. 8A, a plurality of shared messages (including shared message 804-1 and shared message 804-2) are presented in a chat page, wherein each shared message includes a link.

In step S108, the first client determines at least one selected message in response to a message selection operation in the chat page.

Here, the selected message includes at least one shared message. The user may select the sharing message that has been sent by the user, or may select the sharing messages that have been sent by the other users, which is not limited herein.

For example, in fig. 8A, the sharer may select at least one message among a plurality of shared messages (including shared message 804-1 and shared message 804-2).

In step S109, the first client merges the selected at least one message into a chat log message and transmits the chat log message.

For example, in fig. 8A, when the sharer selects the shared message 804-1 and the shared message 804-2, the shared message 804-1 and the shared message 804-2 are merged into the chat log message 805.

In some embodiments, when the receiving account includes a homogeneous system account belonging to the same system as the sharing account, sending a chat record message to the homogeneous system account by calling a communication interface of a first system server; when the receiving account includes a heterogeneous system account belonging to a different system from the sharing account, sending a chat record message to the heterogeneous system account by calling a cross-system communication interface.

Here, when the chat record message is triggered, a chat record preview interface is presented, where the chat record preview interface includes the selected shared message or a link corresponding to the shared message.

For example, in fig. 9C, when the user triggers the chat log sharing link 907 (i.e., the chat log message described above), a chat log preview interface is presented, wherein the chat log preview interface includes a file preview 908 of the file "more than 100M large file, zip" and the file "session file _1587893154.MP 4", wherein the file preview 908 may be a link of the corresponding file.

The embodiment of the invention supports the users to share the previously shared links, and can avoid information omission caused by the fact that other users do not see the previously shared links; and the user is supported to share a plurality of previously shared links, so that the complexity of operation caused by sharing one by the user can be avoided, and the sharing efficiency is improved.

The following describes a file processing method according to an embodiment of the present invention with an example.

In the related art, in the interworking group chat (or interworking group chat session) between different systems, it is not supported to transmit a file with an excessively large capacity. In order to solve the above technical problem, in an embodiment of the present invention, when a sharing account of a first system sends a large file with a capacity exceeding a file capacity threshold (for example, 100M) in an interworking group chat between different systems through a first client, the large file is first uploaded to a microdisk (i.e., the storage server) of a sharer (i.e., a corresponding sharing account) and a microdisk link card (or a sharing link, i.e., the link) is generated, and then the microdisk link card is pushed to an account (i.e., the heterogeneous system account) of a group chat member (i.e., the sharing object) of a second system in the form of the link card. After receiving the microdisk link card, the group chat members of the second system can trigger the microdisk link card and then can download the large file through the browser built in the second client, and the process of downloading the file does not depend on the logic of the second client, so that the technical problem is solved.

Here, the first client may be a computer program (e.g., corporate WeChat) that provides internet social services for enterprise users, the second client may be a computer program (e.g., WeChat) that provides internet social services for individual users, and vice versa.

Taking the file processing method provided by the embodiment of the invention applied to a conference scene, and taking the first client as an enterprise wechat and the second client as a wechat as an example, the enterprise wechat supports conference communication among different systems, wherein a conference communication group comprises at least one enterprise wechat account (equivalent to an isomorphic system account) and at least one wechat account (equivalent to a heterogeneous system account), and the enterprise wechat account can send a link of a corresponding file to the rest accounts (including the enterprise wechat account and the wechat account) in the conference communication group through the enterprise wechat client.

Next, a specific implementation of the file sharing function in the above example will be specifically described.

Referring to fig. 6, fig. 6 is a schematic structural diagram of a file processing system according to an embodiment of the present invention, which will be described with reference to fig. 6.

1) A first client: including microdisk logic and management of interworking group chat sessions.

Logic of micro disk: the sharer can access the microdisk through the first client.

2) A first system server: including the generation of microdisk link cards.

Storing Key Value pairs (KV, Key-Value): for data storage, where Key corresponds to the user's identity and Value corresponds to the user's message (including non-file messages, or files whose size does not exceed a file size threshold).

Link of relationships: including user data of friends of the user and user data of group members of the group in which the user is located.

Third, the micro-disk logic: for files having a storage capacity exceeding a file capacity threshold (e.g., 100M).

Fourthly, the first system access layer: for data (e.g., message) interaction, such as an enterprise wechat access layer.

3) A cross-system communication server: the method is used for transferring the messages of two heterogeneous systems, namely a first system and a second system.

Message logic: for synchronizing messages of the first system with messages of the second system.

Managing heterogeneous accounts (namely the heterogeneous system accounts): including a one-to-one mapping between the account of the first system and the account of the second system.

Event center: for real-time data (e.g., message) introduction.

KV storage: for data storage, Key corresponds to the user's identity and Value corresponds to the user's message (including non-file messages, or files whose size does not exceed a file size threshold).

A cross-system communication access layer (namely, the cross-system access layer): for data (e.g., message) interaction.

4) The second system server: for message interaction with the second client.

Storing KV: for data storage.

Third, the second system access layer: for data (e.g., message) interaction, such as the wechat access layer.

5) The second client: including interaction of session presentations and microdisk link cards.

Referring to fig. 7, fig. 7 is a schematic flowchart of a file processing method according to an embodiment of the present invention, and the following description will be given with reference to fig. 7 by taking an example in which the file capacity threshold is 100M.

First client (logged in with sharing account A) detects big files and marks whether to generate sharing link

In step S701, the first client (having logged in the sharing account a) sends the file F to the interworking chat session, and when the interworking chat session includes the account of the second system and the file F is greater than 100MB, it is marked that a sharing link needs to be generated.

In some embodiments, a first client (having a shared account a logged in) sends (or forwards) a file F with a file capacity exceeding 100MB to an interworking chat session, first determines whether the interworking chat session includes an account of a second system (i.e., a heterogeneous system account), and when the interworking chat session includes an account of the second system, continues to determine whether the shared account has a usage right of a microdisk and whether the capacity of the microdisk (i.e., an available storage space of the corresponding shared account in the storage server) exceeds a limit.

Here, whether the account of the second system is included in the interworking chat session may be determined by an Identification (ID) type of the account, because the ID type of the account of the first system is different from the ID type of the account of the second system.

As an example, when the sharing account a has the usage right of the microdisk, it is further required to determine whether the file F stored in the microdisk exceeds the usage right of the microdisk according to the current usage capacity (or referred to as storage space) of the microdisk.

For example, when the file F is not over-limited after being stored in the microdisk, a prompt message "the file is greater than 100M, and the uploaded microdisk is sent to the user of the second system in a link form to ensure that the user of the second system can normally view the file" is presented in the interworking group chat session ".

For example, when the file F is over-limited after being stored in the microdisk, a prompt message "the file is larger than 100M and cannot be viewed by the user of the second system, and the file F can be sent to the user of the second system in a link form after the microdisk is expanded by contacting with an administrator" is presented in the intercommunication group chat session.

In some embodiments, when a file larger than 100MB is sent, an account of a second system is included in an interworking group chat session, a sharing account a has a usage right of a microdisk, and the capacity of the microdisk does not exceed a limit, a first client (logged in the sharing account a) adds a mark for generating a microdisk link card to a message for sending the file F this time.

In step S702, the first client (logged in with the sharing account a) sends the file F to the first system server.

(II) realizing process of generating large file sharing link by first system server and interacting with second client

In step S703, after receiving the file F sent by the first client (having logged in the sharing account a), the first system server generates a file card message of the file F; detecting whether a message of the file F carries a mark needing to generate a sharing link or not; and when the message of the file F carries a mark needing to generate the sharing link, uploading the file F to the microdisk of the first system server to generate a corresponding microdisk link card message.

In step S704, the first system server transmits a file card message of the file F to the first client (registered with the reception account B).

In step S705, the first system server sends a file card message of the file F to the first client (the sharing account a is logged in).

Here, step S704 and step S705 are not in a sequential order, and may be performed in parallel.

In step S706, the first client (having the login receiving account B) opens the file card message of the file F in response to the user' S trigger operation, and starts downloading the file F.

In some embodiments, because transceiving of files greater than 100MB is supported in the first system, the first client (logged in with sharing account a) and the first client (logged in with receiving account B) in the interworking group chat session receive a file card message for file F; after the user triggers the file card message through the first client (logged in with the sharing account a) or the first client (logged in with the receiving account B), the file F can be directly downloaded from the first system server.

In step S707, the first system server sends the microdisk link card message of the file F to the second client (registered with the receiving account C) through the second system server.

In step S708, the second client (having the login receiving account C) opens the microdisk link card message of the file F in response to the user' S trigger operation.

In step S709, the second client (having the reception account C logged in) downloads the file F through the first system server.

In some embodiments, the second client (logged in with the receiving account C) downloads the file F from the first system server through a built-in browser, and the file F can be opened after the downloading is completed.

In step S710, the second client (having the receiving account C logged in) downloads the file F and then opens the file F.

Referring to fig. 8A, 8B, 9A, 9B, 9C, and 10, fig. 8A, 8B, 9A, 9B, 9C, and 10 are schematic diagrams of application scenarios of a file processing method according to an embodiment of the present invention.

Fig. 8A is an interface display diagram of a first client (logged in with sharing account a) of a mobile terminal version sending a large file of more than 100 MB. In fig. 8A, a prompt 801 is presented in the first client, which can prompt the sharer that the file has been transferred to the microdisk and prompt that the size of the file to be shared exceeds the available storage space of the microdisk (i.e., the above-mentioned capacity prompt).

Fig. 8B is an interface display diagram of a first client (registered with the sharing account a) of a Computer (PC) version sending a large file of more than 100 MB. In fig. 8B, the first client displays a prompt message 802, which can prompt the sharer that the file has been transferred to the microdisk and prompt that the capacity of the file to be shared exceeds the available storage space of the microdisk.

Fig. 9A, 9B, and 9C are interface display diagrams of a second client (logged in with the receiving account number C) receiving a file over 100 MB.

In FIG. 9A, when the user triggers the share link 901 for "100M over File. zip", a preview interface for the file "100M over File. zip" is presented; when the user triggers the download button 902, the file "more than 100M big file. zip" can be downloaded locally; when the user triggers the dump button 903, the file "more than 100M big file. zip" can be saved to the first client (logged in with the receiving account C).

In FIG. 9B, when the user triggers the share link 904 of "Session File _1587893154.MP 4", a preview interface of the file "Session File _1587893154.MP 4" is presented; when the user triggers the download button 905, the file "session file _1587893154.MP 4" can be downloaded locally; when the user triggers the dump button 906, the file "session file _1587893154.MP 4" can be saved to the first client (logged in with the receiving account C).

In fig. 9C, when the user triggers a chat record sharing link 907 (i.e., the chat record message) sent by the sharing account, a chat record preview interface is presented, where the chat record preview interface includes a file preview 908 of the file "file over 100M large, zip" and the file "session file _1587893154.MP 4".

FIG. 10 is an interface display diagram of a first client (logged in with receiving account B) receiving a file over 100 MB. When a user triggers a chat record sharing link 101 sent by a sharing account, presenting a chat record preview interface, wherein the chat record preview interface comprises a file preview 102 of files 'over 100M big file, zip' and file 'video'; when a user triggers the file preview 102 of the file '100M big file, zip', presenting a preview interface of the file '100M big file, zip'; when the user triggers the download button 103, the file "more than 100M big file. zip" can be downloaded locally.

An exemplary structure of the file processing apparatus 455 provided by the embodiment of the present invention implemented as software modules is described below with reference to fig. 2A, and in some embodiments, as shown in fig. 2A, the software modules stored in the file processing apparatus 455 of the memory 450 may include:

the file selection module 4551 is configured to, in response to a file selection operation, determine a selected file as a file that needs to be sent to a receiving account by a sharing account;

a file sharing module 4552, configured to send the file to a first system server in response to a file sharing operation, so that the first system server performs the following processing: and sending the file to a storage server for storage, acquiring a link for storing the file by the storage server, and sending the link to a receiving account with the type of the heterogeneous system account through a cross-system communication interface.

In the above solution, the file selecting module 4551 is further configured to present a file list in response to a file viewing operation received in a chat page of a communication group; the communication group comprises the sharing account, at least one heterogeneous system account belonging to a different system from the sharing account, and at least one homogeneous system account belonging to the same system as the sharing account; in response to a file selection operation received in the file list, determining the selected file as a file which needs to be sent to the receiving account by the sharing account; the receiving account is at least one account in the communication group except the sharing account.

In the above scheme, the file selection module 4551 is further configured to determine, in response to an account selection operation received in a chat page of the communication group, a selected account as the receiving account; the selected account includes at least one heterogeneous system account belonging to a different system from the sharing account.

In the above scheme, the file selection module 4551 is further configured to determine, in response to a file selection operation received in a file management page, that the selected file is a file that needs to be sent by the sharing account; in response to an account selection operation received in an address book page, determining at least one selected account in the address book page and/or accounts in at least one contact group as the receiving account; the selected account includes at least one heterogeneous system account belonging to a different system from the sharing account.

In the above scheme, the file sharing module 4552 is further configured to generate a sharing identifier representing that the file needs to be stored in the storage server when the receiving account includes at least one heterogeneous system account belonging to a different system from the sharing account; sending the sharing identifier and the file to a first system server so that the first system server sends the file to the storage server for storage according to the sharing identifier; the first system server is a server in a system to which the sharing account belongs.

In the above scheme, the file sharing module 4552 is further configured to determine a capacity of the file; and when the receiving account includes at least one heterogeneous system account belonging to a different system from the sharing account and the file capacity exceeds a file capacity threshold, generating the sharing identification representing that the file needs to be stored in the storage server.

In the above scheme, the file sharing module 4552 is further configured to determine an available storage space in the storage server corresponding to the shared account; and when the receiving account number comprises at least one heterogeneous system account number belonging to a different system from the sharing account number, the capacity of the file exceeds a file capacity threshold value, and the capacity of the file does not exceed the available storage space, generating the sharing identification representing that the file needs to be stored in the storage server.

In the above solution, the file processing apparatus 455 further includes: the prompting module is used for presenting capacity prompting information when the receiving account number comprises at least one heterogeneous system account number belonging to a different system from the sharing account number, the capacity of the file exceeds a file capacity threshold value, and the capacity of the file exceeds the available storage space; the capacity prompt information is used for prompting the sharing account to expand the available storage space and/or prompting the sharing account to clear the used storage space corresponding to the sharing account in the storage server.

In the above scheme, the file sharing module 4552 is further configured to, when the number of the receiving accounts is multiple and the multiple receiving accounts include an isomorphic system account belonging to the same system as the sharing account, call a communication interface of a first system server to send the file to the isomorphic system account; the first system server is a server in a system to which the sharing account belongs.

In the foregoing solution, the file sharing module 4552 is further configured to present, in response to the file sharing operation, a sharing message corresponding to the file in a chat page, where the sharing message includes the link; responding to a message selection operation in the chat page, and determining at least one selected message, wherein the selected message comprises at least one sharing message; merging the selected at least one message into a chat log message; when the receiving account number comprises a homogeneous system account number belonging to the same system as the sharing account number, sending the chat record message to the homogeneous system account number by calling a communication interface of a first system server; the first system server is a server in a system to which the sharing account belongs; and when the receiving account number comprises a heterogeneous system account number belonging to a different system with the sharing account number, sending the chat record message to the heterogeneous system account number by calling the cross-system communication interface.

In the above solution, after sending the file to the first system server to make the first system server send the file to the storage server for storage, the file processing apparatus 455 further includes: a link presenting module, configured to receive the link sent by the first system server, and present the link in a chat page of the sharing account sharing file (for example, a chat page of a communication group in which the sharing account participates); in response to a link sharing operation, sending the link to the first system server to cause the first system server to perform the following: and sending the link to a receiving account with the type of the heterogeneous system account through a cross-system communication interface.

Continuing with FIG. 2B, an exemplary structure implemented as software modules of the file processing device 555 provided by the embodiment of the invention is described below, and in some embodiments, as shown in FIG. 2B, the software modules stored in the file processing device 555 in the memory 550 may include:

the receiving module 5551 is configured to receive a link from the sharing account to the receiving account by calling a cross-system communication interface;

a file obtaining module 5552, configured to, in response to a trigger operation for the link, obtain the file from the storage server according to the link.

In the above solution, the file obtaining module 5552 is further configured to respond to a downloading operation for the link, and download the file from the storage server; or, in response to a transfer operation for the link, transferring the file to an available storage space in the storage server corresponding to the receiving account.

In the above solution, the file obtaining module 5552 is further configured to determine a capacity of the file corresponding to the link; and automatically downloading the file from the storage server when the capacity of the file does not exceed a file capacity threshold.

Embodiments of the present invention provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the file processing method according to the embodiment of the invention.

Embodiments of the present invention provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, cause the processor to execute a file processing method provided by an embodiment of the present invention, for example, the file processing methods shown in fig. 3, fig. 4, fig. 5 and fig. 7, where the computer includes various computing devices including an intelligent terminal and a server.

In some embodiments, the computer-readable storage medium may be memory such as FRAM, ROM, PROM, EP ROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or may be various devices including one or any combination of the above memories.

In some embodiments, the computer-executable instructions may be in the form of programs, software modules, scripts or code written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and they may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

By way of example, computer-executable instructions may correspond, but do not necessarily have to correspond, to files in a file system, and may be stored in a portion of a file that holds other programs or data, e.g., in one or more scripts in a hypertext markup language document, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).

By way of example, computer-executable instructions may be deployed to be executed on one computing device or on multiple computing devices at one site or distributed across multiple sites and interconnected by a communication network.

In summary, the embodiments of the present invention have the following beneficial effects:

(1) by calling a cross-system communication interface, a sharer can send a file to a sharing object without the client through a file sharing function of the client; and in the cross-system communication process, the file to be shared is sent to the storage server so as to send the link of the storage server for storing the file to the sharing object, so that background service resources used in file transmission can be saved, and the transmission of other non-file messages can be ensured not to have time delay.

(2) Before uploading the file to the storage server, whether the file stored in the storage server exceeds the limit or not is judged, file transmission failure caused by insufficient capacity of available space can be avoided, and therefore reliability of file transmission can be guaranteed.

(3) By calling different communication interfaces, the file or the link is sent to the receiving account numbers belonging to different systems, and the file transmission efficiency is improved.

(4) The sharing object is supported to download the file to the local or store the file to the cloud according to the link, so that the diversity of the file acquired by the user can be improved; and the files with smaller capacity are automatically downloaded or stored, so that the operation of the user can be reduced, and the efficiency of receiving the files by the user is improved.

(5) The users are supported to share the previously shared links, and information omission caused by the fact that other users do not see the previously shared links can be avoided; and the user is supported to share a plurality of previously shared links, so that the complexity of operation caused by the user sharing the previously shared links one by one can be avoided, and the sharing efficiency is improved.

The above description is only an example of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, and improvement made within the spirit and scope of the present invention are included in the protection scope of the present invention.

Claims

1. A file processing method, comprising:

2. The method of claim 1,

when the same history file as the file is stored in the storage server, the link is a multiplexed link for storing the history file;

when the same history file as the file is not stored in the storage server, the link is a link newly generated by the storage server to store the file.

3. The method of claim 1,

when the file sharing operation is used for sharing a plurality of different files at one time, the link points to the plurality of different files stored in the storage server to serve as a uniform download link or a uniform dump link of the plurality of different files.

4. The method of claim 1,

the file is stored in a storage space registered by the sharing account in the storage server;

when the link is sent and the file stored in the storage server is updated by the sharing account,

the file before updating is used for uniformly responding to the downloading request or the unloading request aiming at the link,

the updated file is used for uniformly responding to the downloading request or the unloading request aiming at the link, or,

the file before updating is used for uniformly responding to a downloading request or a transferring request of a first heterogeneous system account aiming at the link, the first heterogeneous system account is a heterogeneous system account which does not need to be synchronized, and

the updated file is used for uniformly responding to a downloading request or a transferring request of a second heterogeneous system account aiming at the link, wherein the second heterogeneous system account is a heterogeneous system account needing synchronization.

5. The method of claim 1, wherein sending the file to the first system server comprises:

when the receiving account number comprises at least one heterogeneous system account number belonging to a different system from the sharing account number, generating a sharing identification representing that the file needs to be stored in the storage server;

sending the sharing identification and the file to the first system server so as to enable the first system server to share the sharing identification and the file

The first system server sends the file to the storage server for storage according to the sharing identifier;

the first system server is a server in a system to which the sharing account belongs.

6. The method according to claim 5, wherein when the receiving account includes at least one heterogeneous system account that belongs to a different system from the sharing account, generating a sharing identifier that indicates that the file needs to be stored in the storage server includes:

determining a size of the file;

and when the receiving account includes at least one heterogeneous system account belonging to a different system from the sharing account and the file capacity exceeds a file capacity threshold, generating the sharing identification representing that the file needs to be stored in the storage server.

7. The method according to claim 6, wherein when the receiving account includes at least one heterogeneous system account belonging to a different system from the sharing account and the file capacity exceeds a file capacity threshold, generating the sharing identifier indicating that the file needs to be stored in the storage server includes:

determining an available storage space corresponding to the sharing account in the storage server;

and when the receiving account number comprises at least one heterogeneous system account number belonging to a different system from the sharing account number, the capacity of the file exceeds a file capacity threshold value, and the capacity of the file does not exceed the available storage space, generating the sharing identification representing that the file needs to be stored in the storage server.

8. The method of claim 7, further comprising:

when the receiving account number comprises at least one heterogeneous system account number belonging to a different system from the sharing account number, the capacity of the file exceeds a file capacity threshold value, and the capacity of the file exceeds the available storage space, presenting capacity prompt information;

the capacity prompt information is used for prompting the sharing account to expand the available storage space and/or prompting the sharing account to clear the used storage space corresponding to the sharing account in the storage server.

9. The method according to claim 1, wherein when the number of the receiving accounts is multiple and a plurality of receiving accounts include a homogeneous system account belonging to the same system as the sharing account, the method further comprises:

calling a communication interface of a first system server, and sending the file to the isomorphic system account;

10. The method of claim 1,

the cross-system communication interface comprises:

a first system access layer arranged in the first system server, a second system access layer arranged in the second system server, and a cross-system access layer arranged in the cross-system communication server; the first system server is a server in a system to which the sharing account belongs, and the second system server is a server in a system to which the heterogeneous system account belongs;

the sending the link to the receiving account with the type of the heterogeneous system account through the cross-system communication interface includes:

transmitting, by the first system access layer, the link and the heterogeneous system account to the cross-system communication server via the cross-system access layer, such that

The cross-system communication server maps the heterogeneous system account into a related account which can be identified by the second system server according to a mapping relation, and sends the link and the related account to the second system server through the cross-system access layer and the second system access layer so that the second system server sends the link to the related account;

the mapping relation comprises the heterogeneous system account which can be identified by the first system server and an associated account which can be identified by the second system server.

11. The method of claim 1, further comprising:

responding to the file sharing operation, and presenting a sharing message corresponding to the file in a chat page, wherein the sharing message comprises the link;

responding to a message selection operation in the chat page, and determining at least one selected message, wherein the selected message comprises at least one sharing message;

merging the selected at least one message into a chat log message;

when the receiving account number comprises a homogeneous system account number belonging to the same system as the sharing account number, sending the chat record message to the homogeneous system account number by calling a communication interface of a first system server;

the first system server is a server in a system to which the sharing account belongs;

and when the receiving account number comprises a heterogeneous system account number belonging to a different system with the sharing account number, sending the chat record message to the heterogeneous system account number by calling the cross-system communication interface.

12. The method of claim 1, wherein after sending the file to the first system server to cause the first system server to send the file to the storage server for storage, the method further comprises:

receiving the link sent by the first system server, and presenting the link in a chat page of the sharing account sharing file;

in response to a link sharing operation, sending the link to the first system server to cause the first system server to perform the following:

13. A document processing apparatus, characterized by comprising:

14. An electronic device, comprising:

a memory for storing executable instructions;

a processor for implementing the file processing method of any one of claims 1 to 12 when executing computer executable instructions stored in the memory.

15. A computer-readable storage medium having stored thereon computer-executable instructions for implementing the file processing method of any one of claims 1 to 12 when executed.