CN113992650B

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

Info

Publication number: CN113992650B
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: 2023-11-28
Anticipated expiration: 2040-07-10
Also published as: CN113992650A

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 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; in response to a file sharing operation, sending the file to a first system server to enable the first system server to execute the following processing: and sending the file to a storage server for storage, acquiring a link of the storage server for storing the file, 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 file can be shared across systems.

Description

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

Technical Field

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

Background

With the continuous development of internet technology, especially mobile internet, file sharing function is widely used in online social, online office and other scenes. For example, a user may share files such as pictures, documents, audio, and video to 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 to an isomorphic system, for example, only clients accessing the same system can share files. For file sharing between heterogeneous systems (i.e., across systems), there is no effective solution for the related art due to the variability between different systems.

Disclosure of Invention

The embodiment of the invention provides a file processing method, a file processing 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 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;

In response to a file sharing operation, sending the file to a first system server to enable the first system server to execute the following processing:

the file is sent to a storage server for storage, the link of the storage server for storing the file is obtained, 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 above scheme, the determining, in response to the file selection operation, the selected file as the file to which the sharing account needs to be sent to the receiving account includes:

presenting a list of files in response to a file view operation received in a chat page of the communication group;

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

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

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

In the above scheme, the method further comprises:

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

the selected account number comprises at least one heterogeneous system account number which belongs to a different system from the sharing account number.

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

in the above scheme, the method further comprises:

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

the selected account number comprises at least one heterogeneous system account number which belongs to different systems with the sharing account number.

In the above solution, after the link is sent to the heterogeneous system account by calling a cross-system communication interface, the method further includes:

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

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 is used 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 number in the storage server.

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

the file selection module is used for responding to the file selection operation, and determining the selected file as the file of the shared account needing to be sent to the receiving account;

the file sharing module is used for responding to the file sharing operation and sending the file to the first system server so that the first system server can execute the following processing: and sending the file to a storage server for storage, acquiring a link of the storage server for storing the file, 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-described aspect, when the same history file as the file has been stored in the storage server, the link is a multiplexed link for storing the history file; when the storage server does not store the same history file as the file, the link is a link newly generated by the storage server for storing the file.

In the above scheme, when the file sharing operation is used for sharing a plurality of different files at a time, the link points to a plurality of different files stored in the storage server, so as to be a uniform download link or a uniform dump link of a 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; when the file stored by the storage server is updated by the sharing account after the link is sent, the file before updating is used for uniformly responding to a downloading request or a transfer request aiming at the link; the updated file is used for uniformly responding to a downloading request or a dump request aiming at the link; or the file before updating is used for uniformly responding to a downloading request or a restocking 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 restocking 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 respond to a file viewing operation received in a chat page of the communication group, and present a file list; the communication group comprises the sharing account, at least one heterogeneous system account belonging to different systems with the sharing account and at least one isomorphic system account belonging to the same system with the sharing account; responding to file selection operation received in the file list, and determining the selected file as the file which needs to be sent to the receiving account by the sharing account; the receiving account is at least one account except the sharing account in the communication group.

In the above solution, 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 received account; the selected account number comprises at least one heterogeneous system account number which belongs to a different system from the sharing account number.

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

In the above scheme, the file sharing module is further configured to generate a sharing identifier that characterizes the file to be stored in the storage server when the receiving account includes at least one heterogeneous system account belonging to a different system with the sharing account; the sharing identification and the file are sent to a first system server, so that the first system server sends the file to the storage server for storage according to the sharing identification; the first system server is a server in a system to which the shared 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 comprises at least one heterogeneous system account belonging to a different system from the sharing account and the capacity of the file 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 comprises 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 does not exceed the available storage space, generating the sharing identifier for representing that the file needs to be stored to the storage server.

In the above aspect, the file processing device further includes: the prompting module is used for presenting capacity prompting information when the receiving account comprises 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 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 invoke a communication interface of a first system server to send the file to the isomorphic system account when the number of the receiving accounts is multiple and the multiple receiving accounts include isomorphic system accounts belonging to the same system as the sharing account; the first system server is a server in a system to which the shared account belongs.

In the above solution, the cross-system communication interface includes: a first system access layer disposed in the first system server, a second system access layer disposed in the second system server, and a cross-system access layer disposed in a 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, the link and the heterogeneous system account to the cross-system communication server via the cross-system access layer, so that the cross-system communication server maps, according to a mapping relationship, the heterogeneous system account to an associated account that can be identified by the second system server, and send, through the cross-system access layer, the link and the associated account to the second system server via the second system access layer, so that the second system server sends the link to the associated account; the mapping relation comprises the heterogeneous system account number which can be identified by the first system server and the associated account number which can be identified by the second system server.

In the above scheme, the file sharing module is further configured to respond to the file sharing operation, and present a sharing message corresponding to the file in a chat page, where the sharing message includes the link; determining at least one selected message in response to a message selection operation in the chat page, wherein the selected message comprises at least one sharing message; combining the selected at least one message into a chat message; when the receiving account comprises an isomorphic system account belonging to the same system as the sharing account, sending the chat message to the isomorphic system account 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; when the receiving account comprises a heterogeneous system account belonging to a different system with the sharing account, the chat message is sent to the heterogeneous system account by calling the cross-system communication interface.

In the above aspect, 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 file processing apparatus further includes: the presenting link module is 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 processing: 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 a prompt message, and/or send the prompt message to the heterogeneous system account; 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 is used 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 number in the storage server.

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

the receiving account is a heterogeneous system account belonging to different systems with the sharing account;

and responding to the triggering operation for the link, and acquiring the file from a storage server according to the link.

In the above scheme, the responding to the triggering operation for the link, acquiring the file from the storage server according to the link, includes:

Downloading the file from the storage server in response to a download operation for the link; or,

and responding to the transfer operation aiming at the link, and transferring the file to an available storage space corresponding to the receiving account number in the storage server.

In the above scheme, the method further comprises:

determining a capacity of a file corresponding to the link;

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

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

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

In the above aspect, the file obtaining module is further configured to download the file from the storage server in response to a download operation for the link; or, in response to the operation of transferring the file to the link, transferring the file to an available storage space corresponding to the received account number in the storage server.

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 the 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 for realizing the file processing method provided by the embodiment of the invention when being executed by a processor.

The embodiment of the invention has the following beneficial effects:

by calling the cross-system communication interface, a sharer can send a file to a sharing object not provided with the client through the 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 the link of the storage server storing the file is sent to the sharing object, thereby saving the background service resource used during file transmission, and further ensuring that the transmission of other non-file messages does not have time delay.

Drawings

FIG. 1 is a schematic diagram of a file 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 schematic flow chart of a file processing method according to an embodiment of the present invention;

FIG. 4 is a schematic flow chart of a file processing method according to an embodiment of the present invention;

FIG. 5 is a schematic flow chart of a file processing method according to an embodiment of the present invention;

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

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

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

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

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

Detailed Description

The present invention will be further described in detail with reference to the accompanying drawings, for the purpose of making the objects, technical solutions and advantages of the present invention more apparent, and the described embodiments should not be construed as limiting the present invention, and all other embodiments obtained by those skilled in the art without making any inventive effort are within the 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 to be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with one another 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 describing embodiments of the present invention in further detail, the terms and terminology involved in the embodiments of the present invention will be described, and the terms and terminology involved in the embodiments of the present invention will be used in the following explanation.

1) In response to a condition or state that is used to represent the condition or state upon which the performed operation depends, the performed operation or operations may be in real-time or with a set delay when the condition or state upon which it depends is satisfied; without being specifically described, there is no limitation in the execution sequence of the plurality of operations performed.

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

3) Heterogeneous system accounts refer to accounts belonging to different systems. For example, account a belongs to system a, account B belongs to system B, and direct communication between system a and system B is not possible, so account a and account B are heterogeneous system accounts of each other.

4) The isomorphic system account refers to accounts 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, network U disk, is an online storage service provided by a storage server in a network. The network disk provides the document management functions of storing, sharing, accessing, backing up and the like of the files for the user. The user can manage or edit files in the network disk through the network.

Referring to fig. 1, fig. 1 is a schematic diagram of a file processing system according to an embodiment of the present invention. Wherein the file processing system comprises: 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 each provides services for the accessed terminal. For example, the first system server 100 is for providing services 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, to provide communication services 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 in 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; a Native Application (APP), i.e. a program that needs to be installed in an operating system to run; the method can also be an applet, namely a program which can be run only by being downloaded into a browser environment; or an instant messaging applet or file management applet that can be embedded in any APP. In general, the computer programs described above 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, and the second terminal 500 runs the second client 510, and in particular, the first client 410 may be a computer program (e.g., an enterprise letter) providing an internet social service for an enterprise user, and the second client 510 may be a computer program (e.g., a letter) providing an internet social service for an individual user, or vice versa.

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

The cloud technology is a generic term of network technology, information technology, integration technology, management platform technology, application technology and the like based on cloud computing business model application, can form a resource pool, and is flexible and convenient as required. 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) described above may be implemented by cloud technology.

As an 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 formed by a plurality of physical servers, and may be a cloud server providing a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, a middleware service, a domain name service, a security service, a CDN, and a basic cloud computing service such as a big data and artificial intelligence platform, but not limited thereto.

Next, the structures of the first terminal 400 and the second terminal 500 provided in the embodiment of the present invention are described. Referring to fig. 2A and 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, a 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 connected communication between these components. The bus system 440 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration 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, such as a microprocessor or any conventional processor, or the like, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, 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 presentation of the 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.

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

Memory 450 includes volatile memory or nonvolatile memory, and may also include both volatile and nonvolatile memory. The non-volatile memory may be read only memory (ROM, read Only Me mory) and the volatile memory may be random access memory (RAM, random Access Memor y). The memory 450 described in embodiments of the present invention is intended to comprise any suitable type of memory.

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

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

network communication module 452 for reaching other computing devices via one or more (wired or wireless) network interfaces 420, exemplary network interfaces 420 include: bluetooth, wireless compatibility authentication (WiFi), and universal serial bus (USB, universal Serial Bus), etc.;

a presentation module 453 for enabling presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 431 (e.g., a display screen, speakers, etc.) associated with the 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 may be implemented by various forms of computer programs executed by the first terminal 400, for example, the operating system 451, the first client 410, the software modules, and the scripts described above. Fig. 2A shows a file processing device 455 stored in memory 450, comprising the following software modules: the file selection module 4551 and the file sharing module 4552 are logical, and thus may be arbitrarily combined or further split according to the implemented functions. The functions of the respective modules will be described hereinafter.

The second terminal 500 shown in fig. 2B includes: at least one processor 510, a 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 appreciated that the bus system 540 is used to enable connected communications between these components. The bus system 540 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration, the various buses are labeled as bus system 540 in fig. 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, and the bus system 540 in the first terminal 400 are similar to those of the processor 410, the memory 450, the network interface 420, the user interface 430, and the bus system 440 in the first terminal 400 described above, 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 running on the second terminal 500, for example, the operating system 551, the second client 510, the software modules, and the scripts described above. Fig. 2B shows a file processing device 555 stored in a memory 550, which may be software in the form of programs and plug-ins, etc., comprising the following software modules: the receiving module 5551 and the file obtaining module 5552 are logical, and thus may be arbitrarily combined or further split according to the implemented functions. The functions of the respective modules will be described hereinafter.

In the following, a document processing method provided by the first terminal 400 and the second terminal 500 in fig. 1 in cooperation with each other is taken as an example for explanation.

Hereinafter, description is made based on the following scenario: the first terminal 400 runs a first client, and the second terminal 500 runs a second client, wherein the login account in the first client is a sharing account for sharing the file, and the login account in the second client is a target account (i.e. receiving account) for sharing the file with the sharing account.

It should be noted that the method shown in fig. 3 may 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 described above, 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 further noted that, since the "first" and the "second" described above are opposite, for other application scenarios, for example, the login account in the second client is a sharing account for sharing a file, and the login account in the first client is a target account for sharing a file with the sharing account, which may be implemented according to the following understanding.

In step S101, the first client determines, in response to the file selection operation, the selected file as a file to which the sharing account needs to be sent 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 the 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, in step S101, the number of accounts for receiving the file is one or more (i.e., at least two), and the accounts for receiving the file include at least one heterogeneous system account that belongs to a different system from the sharing account.

In some embodiments, the first client presents a list of files in response to a file view 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 different systems with the sharing account, and at least one isomorphic system account belonging to the same system with the sharing account; responding to file selection operation received in a file list, and determining the selected file as a file of which the sharing account number needs to be sent to the receiving account number; the receiving account is at least one account except 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. Thus, the sharer can share the file stored locally and also can share the file stored in the cloud.

For example, fig. 8B is a chat page of a communication group, where the member list 803 of the communication group includes two accounts of the first system and two accounts of the second system. When "BobbyTestA" is a shared account, "BobbyTestB", "BobbyTestE" and "bobbyche" are receiving accounts, where "BobbyTestB" is a isomorphic system account belonging to the same system as the shared account, and "BobbyTestE" and "bobbyche" are heterogeneous system accounts belonging to different systems than the shared account. Therefore, when a sharer sends a file in a chat page of a communication group, the file or link sent by the sharing account can be received no matter whether the receiving account in the communication group belongs to an isomorphic system account of the same system as the sharing account or belongs to a heterogeneous system account of a different system from the sharing account.

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

For example, in fig. 8B, when "BobbyTestA" is a sharing account, the "BobbyTestA" may select at least one heterogeneous system account belonging to a different system from the sharing account among "BobbyTestB", "BobbyTestE", and "bobbyche" in a chat page of the communication group as the receiving account. Therefore, the sharer can send the file in the communication group in a targeted manner, and only the sharing object designated 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 view 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 different systems with the sharing account; and responding to the file selection operation received in the file list, and determining the selected file as the file of which the sharing account number needs to be sent to the receiving account number. Thus, the sharer can send the file 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 which the sharing account needs to be sent; as such, the method further comprises: and responding to the account selection operation received in the address book page, and determining at least one account selected in the address book page and/or the account in 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 shared account.

As an 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 may be displayed simultaneously, e.g., the file management page and the address book page are displayed on separate screens; displaying the file management page above the address book page in a floating layer mode (the account selection process is positioned before the file selection process), so that the file management page has transparency and does not completely shield the address book page; the address book page is displayed above the file management page in a floating layer mode (the account selection process is located after the file selection process), so that the address book page has transparency and can not 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 selection process is located before the file selection process and the file selection operation is received, the address book page is switched to the presentation file management page; and when the account selection process is positioned after the file selection process and the account selection operation is received, switching from the file management page to the address book 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 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. Thus, the sharer can share the file stored locally and also can share the file stored in the cloud.

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

Here, the file sharing operation may be various forms of operations preset by the operating system and having no conflict with the registered operations; or may be a user-defined operation of various forms that is non-conflicting with the registered operation. The file sharing operation includes at least one of: click operations (e.g., single click operations, multiple click operations, or multiple click operations, etc.); a sliding operation according to a specific trajectory or direction; voice operation; motion sensing operation (e.g., up-and-down shaking operation or curve motion operation). Thus, the convenience of sharing operation of the user can be improved.

In some embodiments, the first client responds to the 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 characterizing that the file needs to be stored in the storage server; and sending the sharing identification 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 identification. Therefore, when the receiving account includes heterogeneous system accounts which belong to different systems with the sharing account, the first system server is instructed to send the file to the storage server, and in this way, background service resources used in file transmission can be saved, and further, the transmission of other non-file messages can be guaranteed not to be delayed.

Here, the first system server is a server in a system (or first system) to which the shared account belongs. The storage server may be a server independent of 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 a file sharing operation; when the receiving account comprises at least one heterogeneous system account belonging to a different system from the sharing account and the capacity of the file exceeds a file capacity threshold (for example, 100M), generating a sharing identifier for representing that the file needs to be stored in a storage server; and sending the sharing identification 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 identification.

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 heterogeneous system accounts belonging to different systems with the sharing account and the capacity of the file is overlarge, 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 resources 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 is not required to be transmitted to the storage server, and the transmission of the small-capacity file does not cost excessive background service resources, so that the small-capacity file can be directly transmitted to the receiving account in the form of the file, and the transmission rate of the file 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 shared account in the storage server; when the receiving account comprises at least one heterogeneous system account belonging to different systems with the sharing account, the capacity of the file exceeds a file capacity threshold, and the capacity of the file does not exceed an available storage space, generating a sharing identifier for representing that the file needs to be stored in a storage server; and sending the sharing identification 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 identification.

In the embodiment of the invention, since the first system server directly stores the file into the available storage space of the corresponding shared account in the storage server, before uploading the file, the first client needs to judge whether the file is stored into the storage server and is out of limit, so that file transmission failure caused by insufficient available space capacity 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 than the sharing account, the capacity of the file exceeds a file capacity threshold, and the capacity of the file exceeds the available storage space, the first client presents a capacity prompt message; 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 prompt message may contact the administrator to expand the micro disk and then send the file to the user of the second system in a linked manner", so that the sharer may be prompted to have the capacity of the file to be shared exceeding the available storage space of the micro disk, so as to avoid failure in file transmission due to insufficient available space capacity, and thus ensure 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 form of the link includes at least one of: a linked text; a graphic code (e.g., a bar code or a two-dimensional code); an acoustic signal. The link is used for a receiving account (comprising an isomorphic system account and a heterogeneous system account) to download files from a storage server, or is used for the receiving account to transfer the files from the storage server to an available storage space; the available storage space is the available storage space corresponding to the received account number 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 obtain 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 storage server has stored the same history file as the file, multiplexing the link for storing the history file in the storage server with the link for storing the history file, wherein the link acquired by the first system server is the multiplexed link for storing the history file; when the same history file as the 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, and at this time, 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 the same as the file uploaded by the sharing account repeatedly or a file that is the same as the file uploaded by another account.

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 (e.g., a data digest) of the file with the digital fingerprint of the file already stored in the storage server; when the comparison is successful, determining that the history file which is the same as the file is already stored in the storage server; when the comparison is unsuccessful, it is determined that the storage server does not store the same history file as the file.

Therefore, the repeated uploading of the files by the same or different users can be prevented from occupying the storage space of the storage server, and file redundancy 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 similar file which is stored and contains part of the same content as the file in a storage space; determining the content with the difference between the similar 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 file, and generating a link pointing to the stored fused file, wherein the link acquired by the first system server is a link generated by the storage server for storing the fused file.

Taking the example that the file is a photo album, when the first system server sends the photo album including the photo 1, the photo 2, and the photo 3 to the storage server, the storage server detects in the storage space to obtain a similar photo album having a portion similar to the photo album, wherein the similar photo album includes the photo 1 and the photo 2. Thus, the storage server does not need to restore the photos 1 and 2, but only stores the part (i.e. photo 3) of the photo album where the difference exists between the photo album and the similar photo album. 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 a time, the first system server sends the plurality of different files to the storage server and obtains a unified link from the storage server that stores the plurality of different files. Therefore, the sharing account can share a plurality of files by sending the links once, so that the generation of a plurality of links is avoided, and the waste of background service resources 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 of the plurality of different files. The unified link is used for the receiving account 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; when a link is sent to a receiving account, and a file stored by a storage server is logged in the storage server by a sharing account (for example, the sharing account is logged in a network disk) and updated, the storage server uses the updated file for uniformly responding to a downloading request or a dump request aiming at the link; or the storage server uses the updated file for uniformly responding to the downloading request or the dump request aiming at the link; or the storage server uses the file before updating to uniformly respond to the downloading request or the transferring request of the first heterogeneous system account for the link, and uses the updated file to uniformly respond to the downloading request or the transferring request of the second heterogeneous system account for 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 has sent the link of the corresponding 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 aiming at the link, the storage server can respond to the file acquisition request according to the file before updating or respond to the file acquisition request according to the file after updating. Here, the file version of the receiving account B obtained from the storage server according to the link may be a default system, or may be specified by the sharing account a, which is not limited herein. It should be noted that, when the plurality of receiving accounts are included, the sharing account can specify at least one receiving account for acquiring the file before update or at least one receiving account for acquiring the file after update in the plurality of receiving accounts. Therefore, the safety of the stored data in the storage server can be ensured while the diversity of data acquisition is realized.

In some embodiments, after step S103, it may further include: the method comprises the steps that a first client receives a link sent by a first system server, and the link is presented in a chat page of a sharing account sharing file (such as a chat page of a communication group or personal chat in which the sharing account participates); 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 processing: and sending the link to a receiving account with the type of heterogeneous system account through a cross-system communication interface. Therefore, the sharer can acquire the sending condition of the file in time so as to avoid file sending omission, and the sharer can forward the file to the sharing object again according to the link presented in the interface later so as to strongly prompt the sharing object.

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

Here, the second client specifically refers to a second client logged in with a receiving account of a heterogeneous system account.

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

In some embodiments, the above-described cross-system communication interface comprises: a first system access layer disposed in the first system server, a second system access layer disposed in the second system server, and a cross-system access layer disposed in the cross-system communication server; the first system server sends a link to the second client through the cross-system communication interface: and sending the link and the associated account number to the second system server through the cross-system access layer by the cross-system access layer so that the second system server can send the link to the associated account number.

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

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

Because the sharing account sends the file to the isomorphic system account belonging to the same system as the sharing account without cross-system communication and consumes less background service resources, the file can be directly sent to the isomorphic system account without sending a link, and the file is not required to be downloaded from a storage server by the isomorphic system account, so that the file receiving rate of the isomorphic system account is improved.

As an example, when the capacity of the file exceeds a file capacity threshold (e.g., 100M), the first client invokes a communication interface of the first system server to send the file to the isomorphic 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, the background service resources consumed by sending the files with larger capacity to the isomorphic system accounts belonging to the same system as the sharing accounts by the sharing accounts are more, so that the embodiment of the invention sends the links of the corresponding files to the isomorphic system accounts, and thus, the situation that excessive service resources of the first system server are occupied due to directly sharing the files with excessive capacity to the isomorphic system accounts can be avoided, and further, the transmission of other non-file messages sent to the isomorphic system accounts can be ensured not to be delayed.

In the embodiment of the invention, the file or the link is sent to the receiving account belonging to different systems by calling different communication interfaces, so that the efficiency of file transmission can be improved.

In step S105, the second client acquires a 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 a user triggers a sharing link 901 of "over 100M big File. Zip", a preview interface of the file "over 100M big File. Zip" is presented; when the user triggers the download button 902, the file "over 100M large file. Zip" can be downloaded locally.

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

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 forwards the file to the available storage space of the corresponding receiving account in the storage server in response to a forwarding operation for the link.

As an example, when the capacity of the file exceeds the file capacity threshold, the second client side responds to the transfer operation for the link to transfer the file into the available storage space of the corresponding receiving account in the storage server.

Taking the link as a graphic code as an example, the second client responds to the scanning operation for the graphic code, identifies the corresponding link from the graphic code, downloads the file from the storage server according to the link, or transfers the file to the available storage space corresponding to the 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 automatically downloading or transferring files with smaller capacity can reduce the operation of users, thereby improving the efficiency of receiving files by the users.

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

In step S106, the first client presents a prompt message.

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

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

In some embodiments, the first client sends a prompt to the receiving account to cause the second client to present the prompt. In this way, 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 flow chart of a file processing method according to an embodiment of the present invention, based on fig. 3, step S107 to step S109 may be further included after step S104, where no sequence exists between step S105 and step S107 to step S109, and the steps may be executed in parallel or may be executed sequentially.

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

Here, the link is included in the sharing message.

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

For example, in FIG. 8A, multiple sharing messages (including sharing message 804-1 and sharing message 804-2) are presented in a chat page, where each sharing message includes a link.

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

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

For example, in FIG. 8A, a sharer may select at least one message from a plurality of sharing messages (including sharing message 804-1 and sharing message 804-2).

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

For example, in FIG. 8A, when the sharer selects the sharing message 804-1 and the sharing message 804-2, the sharing message 804-1 and the sharing message 804-2 are combined into the chat message 805.

In some embodiments, when the receiving account includes an isomorphic system account belonging to the same system as the sharing account, sending a chat message to the isomorphic system account by calling a communication interface of the first system server; when the receiving account comprises heterogeneous system accounts which belong to different systems with the sharing account, a cross-system communication interface is called to send chat messages to the heterogeneous system accounts.

Here, when the chat message is triggered, a chat message preview interface is presented, wherein the chat message preview interface includes the selected sharing message or a link corresponding to the sharing message.

For example, in FIG. 9C, when the user triggers chat message sharing link 907 (i.e., the chat message described above), a chat message preview interface is presented, wherein the chat message preview interface includes file previews 908 of file "over 100M large file zip" and file "Session File_1587893154.MP4", wherein file previews 908 may be links to corresponding files.

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 links which are shared before, so that the complexity of operation caused by the fact that the user shares the links one by one can be avoided, and the sharing efficiency is improved.

Next, a file processing method provided by an embodiment of the present invention is described as an example.

In the related art, in an interworking group chat (or interworking group chat session) between different systems, a file with an excessive transmission capacity is not supported. In order to solve the above technical problems, in the embodiment of the present invention, when a large file with a capacity exceeding a file capacity threshold (for example, 100M) is sent by a sharing account of a first system through an intercommunication group chat among different systems by a first client, the large file is uploaded to a micro disk (i.e., the storage server) of a sharer (i.e., the corresponding sharing account) and a micro disk link card (or called a sharing link, i.e., the link) is generated, and then pushed to an account of a group chat member (i.e., the sharing object) of a second system (i.e., the heterogeneous system account) in the form of the link card. After receiving the micro disk link card, the group chat member of the second system can download the large file through the built-in browser of the second client after triggering the micro disk link card, and the process of downloading the file is independent of the logic of the second client, so that the technical problem is solved.

Here, the first client may be a computer program (e.g., an enterprise letter) that provides an internet social service for an enterprise user, and the second client may be a computer program (e.g., a letter) that provides an internet social service for an individual user, or vice versa.

Taking the example that the file processing method provided by the embodiment of the invention is applied to a conference scene, the first client is an enterprise WeChat and the second client is a WeChat, and conference communication among different systems is supported in the enterprise WeChat, wherein the 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), the enterprise WeChat account can send links of corresponding files to other accounts (comprising the enterprise WeChat account and the WeChat account) in the conference communication group through the enterprise WeChat client, and thus, the WeChat client can obtain corresponding files based on the links without downloading the enterprise WeChat client after receiving the links.

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, and will be described with reference to fig. 6.

1) The first client: including management of micro-disk logic and interworking group chat sessions.

(1) Micro-disk logic: the sharer can access the micro disk through the first client.

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

(1) Key-Value pair (KV) store: for data storage, where Key corresponds to the identity of the user and Value corresponds to the user's message (including non-file messages, or files having a capacity that does not exceed a file capacity threshold).

(2) The relation chain: including user data for friends of the user, and user data for group members of the group in which the user is located.

(3) Micro-disk logic: for storing files having a capacity exceeding a file capacity threshold (e.g., 100M).

(4) First system access layer: for data (e.g., message) interactions, such as enterprise WeChat Access layer.

3) A cross-system communication server: for relaying messages of both heterogeneous systems of the first system and the second system.

(1) Message logic: for synchronizing messages of a first system with messages of a second system.

(2) Heterogeneous account number (i.e., heterogeneous system account number described above) management: including a one-to-one mapping between the account number of the first system and the account number of the second system.

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

(4) KV storage: for data storage, key corresponds to the identity of the user, value corresponds to the user's message (including non-file messages, or files whose capacity does not exceed a file capacity threshold).

(5) Cross-system communication access layer (i.e., the cross-system access layer described above): for data (e.g., message) interactions.

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

(1) KV storage: for data storage.

(3) The second system access layer: for data (e.g., message) interactions, such as a WeChat access layer.

5) And a second client: including session presentation and interaction of the microdisk link card.

Referring to fig. 7, fig. 7 is a flowchart of a file processing method according to an embodiment of the present invention, and will be described below with reference to fig. 7 by taking a file capacity threshold of 100M as an example.

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

In step S701, a first client (logged in with a sharing account a) sends a file F to an intercommunication chat session, and when the intercommunication chat session includes an account of a second system and the file F is greater than 100MB, the need for generating a sharing link is marked.

In some embodiments, the first client (logged in with the sharing account a) sends (or forwards) a file F with a file capacity exceeding 100MB to the intercommunication chat session, first determines whether the intercommunication chat session includes an account of the second system (i.e. heterogeneous system account), and when the intercommunication chat session includes the account of the second system, continues to determine whether the sharing account has the use permission of the micro disk and whether the capacity of the micro disk (i.e. the available storage space corresponding to the sharing account in the storage server) is out of limit.

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

As an example, when the sharing account a has the use permission of the micro disk, it is further required to determine whether the current file F will overrun after being stored in the micro disk according to the current situation of the used capacity (or called storage space) of the micro disk.

For example, when the file F is stored in the micro disk and is not out of limit, a prompt message "the file is greater than 100M" is presented in the intercommunication group chat session, so as to ensure that the user of the second system can view the file normally, and the file is uploaded to the micro disk and sent to the user of the second system in a link form.

For example, when the file F is stored in the micro disk and exceeds the limit, a prompt message "the file is greater than 100M" is presented in the intercommunication group chat session, and the user of the second system cannot view the file, and the file can be connected to the administrator to expand the micro disk and then be sent to the user of the second system in a link form.

In some embodiments, when the sending of files greater than 100MB is simultaneously satisfied, the intercommunication group chat session includes an account number of the second system, the sharing account number a has the use authority of the micro disk, and the capacity of the micro disk is not excessively limited at the time, the first client (logging in the sharing account number a) will add a mark that needs to generate the micro disk link card to the message of the sending file F.

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

(II) implementation flow of large file sharing link generation by first system server and second client interaction

In step S703, after receiving the file F sent by the first client (logged in with 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 for generating a sharing link or not; and uploading the file F to the micro disk of the first system server to generate a corresponding micro disk link card message when the message of the file F carries a mark for generating a sharing link.

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

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

Here, there is no sequence between step S704 and step S705, and may be performed in parallel.

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

In some embodiments, because the first system supports the transceiving of files greater than 100MB, the first client (logged in with the sharing account a) and the first client (logged in with the receiving account B) in the interworking group chat session receive file card messages of the file F; when 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 may be directly downloaded from the first system server.

In step S707, the first system server transmits a micro-disc 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 (registered with the receiving account number C) opens the micro-disc link card message of the file F in response to the trigger operation of the user.

In step S709, the second client (registered with the receiving account C) 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 may be opened after the downloading is completed.

In step S710, the second client (registered with the receiving account C) downloads the file F and opens the file F.

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

Fig. 8A is an interface presentation diagram of a first client (logged in with the sharing account a) of a mobile terminal version sending over 100MB of large files. 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 micro disk, and prompt that the capacity of the file to be shared exceeds the available storage space of the micro disk (i.e. the capacity prompt described above).

Fig. 8B is an interface display diagram of a first client (logged in with sharing account a) of a version of the computer (PC, personal Computer) sending over 100MB of large files. In fig. 8B, a prompt 802 is presented in the first client, which can prompt the sharer that the file has been transferred to the micro disk, and prompt that the capacity of the file to be shared exceeds the available storage space of the micro disk.

Fig. 9A, 9B, and 9C are interface display diagrams of a second client (registered with the receiving account C) receiving a large file of more than 100 MB.

In FIG. 9A, when a user triggers a sharing link 901 of "over 100M large file.zip", a preview interface of the file "over 100M large file.zip" is presented; when the user triggers the download button 902, the file "over 100M large file.zip" can be downloaded locally; when the user activates the dump button 903, the file "over 100M large file.zip" can be saved to the first client (registered with the receiving account number C).

In FIG. 9B, when the user triggers the share link 904 of "Session File_1587893154.MP4", a preview interface of the file "Session File_1587893154.MP4" is presented; when the user triggers the download button 905, the file "session file_1587893154.mp4" can be downloaded locally; when the user activates the dump button 906, the file "session file_1587893154.mp4" can be saved to the first client (registered with the receiving account C).

In FIG. 9C, when the user triggers the chat message sharing link 907 (i.e., the chat message described above) sent by the sharing account, a chat message preview interface is presented, where the chat message preview interface includes a file preview 908 of the file "over 100M large file.

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

An exemplary structure of the file processing device 455 implemented as a software module provided in accordance with an embodiment of the present invention is described below in conjunction with fig. 2A, and in some embodiments, as shown in fig. 2A, the software module stored in the file processing device 455 of the memory 450 may include:

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

The file sharing module 4552 is configured to send, in response to a file sharing operation, the file to a first system server, so that the first system server performs the following processing: and sending the file to a storage server for storage, acquiring a link of the storage server for storing the file, 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 selection 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 different systems with the sharing account and at least one isomorphic system account belonging to the same system with the sharing account; responding to file selection operation received in the file list, and determining the selected file as the file which needs to be sent to the receiving account by the sharing account; the receiving account is at least one account except the sharing account in the communication group.

In the above solution, 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, the selected account as the received account; the selected account number comprises at least one heterogeneous system account number which belongs to a different system from the sharing account number.

In the above solution, the file selection module 4551 is further configured to determine, in response to a file selection operation received in a file management page, a selected file as a file that needs to be sent by the sharing account; responding to an account selection operation received in an address book page, and determining at least one account selected in the address book page and/or accounts in at least one contact group as the received account; the selected account number comprises at least one heterogeneous system account number which belongs to different systems with the sharing account number.

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

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

In the above solution, the file sharing module 4552 is further configured to determine an available storage space corresponding to the sharing account in the storage server; and when the receiving account comprises 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 does not exceed the available storage space, generating the sharing identifier for representing that the file needs to be stored to the storage server.

In the above aspect, the file processing device 455 further includes: the prompting module is used for presenting capacity prompting information when the receiving account comprises 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 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 solution, the file sharing module 4552 is further configured to, when the number of the receiving accounts is multiple and the multiple receiving accounts include isomorphic 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 isomorphic system accounts; the first system server is a server in a system to which the shared account belongs.

In the above solution, the file sharing module 4552 is further configured to respond to the file sharing operation, and present a sharing message corresponding to the file in a chat page, where the sharing message includes the link; determining at least one selected message in response to a message selection operation in the chat page, wherein the selected message comprises at least one sharing message; combining the selected at least one message into a chat message; when the receiving account comprises an isomorphic system account belonging to the same system as the sharing account, sending the chat message to the isomorphic system account 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; when the receiving account comprises a heterogeneous system account belonging to a different system with the sharing account, the chat message is sent to the heterogeneous system account by calling the cross-system communication interface.

In the above aspect, 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 file processing apparatus 455 further includes: the presenting link module is 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 processing: and sending the link to a receiving account with the type of the heterogeneous system account through a cross-system communication interface.

Continuing with the description of an exemplary architecture of file processing device 555 implemented as a software module provided in accordance with an embodiment of the present invention in conjunction with FIG. 2B, in some embodiments, as shown in FIG. 2B, the software modules stored in file processing device 555 of memory 550 may comprise:

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

and the file acquisition module 5552 is configured to respond to a triggering operation for the link, and acquire the file from the storage server according to the link.

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

In the above solution, the file obtaining module 5552 is further configured to determine a capacity of a file corresponding to the link; and automatically downloading the file from the storage server when the capacity of the file does not exceed the 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 present invention.

Embodiments of the present invention provide a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, cause the processor to perform a file processing method provided by embodiments of the present invention, for example, the file processing methods shown in fig. 3, 4, 5, and 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 FRAM, ROM, PROM, EP ROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; but may be a variety of devices including one or any combination of the above memories.

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

As an example, computer-executable instructions may, but need not, correspond to files in a file system, may be stored in a portion of a file that holds other programs or data, such as 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).

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

In summary, the embodiment of the invention has the following beneficial effects:

(1) By calling the cross-system communication interface, a sharer can send a file to a sharing object not provided with the client through the 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 storage file to the sharing object, thereby saving the background service resources used during file transmission and further ensuring that the transmission of other non-file messages does not have time delay.

(2) Before uploading the file to the storage server, judging whether the file is stored in the storage server or not is overrun, so that file transmission failure caused by insufficient available space capacity can be avoided, and the reliability of file transmission can be ensured.

(3) And by calling different communication interfaces, the file or the link is sent to the receiving account belonging to different systems, so that the efficiency of file transmission 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 automatically downloading or transferring files with smaller capacity can reduce the operation of users, thereby improving the efficiency of receiving files by the users.

(5) The user is supported to share the previously shared links, so that 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 links which are shared before, so that the complexity of operation caused by the fact that the user shares the links which are shared before one by one can be avoided, and the sharing efficiency is improved.

The foregoing is merely exemplary embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and scope of the present invention are included in the protection scope of the present invention.

Claims

1. A document processing method, comprising:

in the intercommunication group chat of the heterogeneous system, responding to file selection operation, determining the selected file as a file of which the sharing account needs to be sent to the receiving account;

determining the capacity of the file in response to a file sharing operation;

When the receiving account comprises at least one heterogeneous system account belonging to different systems with the sharing account and the capacity of the file exceeds a file capacity threshold, generating a sharing identifier representing that the file needs to be stored in a storage server;

the sharing identification and the file are sent to a first system server, so that the first system server sends the file to the storage server for storage according to the sharing identification, wherein the first system server is a server in a system to which the sharing account belongs;

acquiring a link of the storage server for storing the file;

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

The cross-system communication server maps the heterogeneous system account numbers into associated account numbers which can be identified by a second system server according to the mapping relation, and the link and the associated account numbers are sent 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 associated account numbers;

Wherein the first system access layer is set in the first system server, the second system access layer is set in the second system server, and the cross-system access layer is set in the cross-system communication server; the second system server is a server in a heterogeneous system account system; the mapping relation comprises the heterogeneous system account number which can be identified by the first system server and the association account number which can be identified by the second system server.

2. The method of claim 1, wherein the step of determining the position of the substrate comprises,

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

when the storage server does not store the same history file as the file, the link is a link newly generated by the storage server for storing the file.

3. The method of claim 1, wherein the step of determining the position of the substrate comprises,

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

4. The method of claim 1, wherein the step of determining the position of the substrate comprises,

the files are stored in a storage space registered by the sharing account number in the storage server;

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

the file before updating is used for uniformly responding to a download request or a dump request for the link,

the updated file is used to uniformly respond to a download request or a dump request for the link, or,

the file before updating is used for uniformly responding to a downloading request or a transfer request of a first heterogeneous system account aiming at the link, wherein 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 transfer 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.

5. The method of claim 1, wherein generating the sharing identifier that characterizes the file as needed to be stored to the storage server when the receiving account includes at least one heterogeneous system account that is different from the sharing account and the capacity of the file exceeds a file capacity threshold, comprises:

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

and when the receiving account comprises 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 does not exceed the available storage space, generating the sharing identifier for representing that the file needs to be stored to the storage server.

6. The method of claim 5, wherein the method further comprises:

when the receiving account comprises 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 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.

7. The method of claim 1, wherein when the number of the receiving accounts is plural, and the plural receiving accounts include homogeneous system accounts 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;

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

8. The method according to claim 1, wherein the method further comprises:

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;

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

combining the selected at least one message into a chat message;

when the receiving account comprises an isomorphic system account belonging to the same system as the sharing account, sending the chat message to the isomorphic system account 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;

when the receiving account comprises a heterogeneous system account belonging to a different system with the sharing account, the chat message is sent to the heterogeneous system account by calling the cross-system communication interface.

9. The method of claim 1, wherein after the 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, 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 processing:

10. A document processing apparatus, comprising:

the file selection module is used for responding to file selection operation in the intercommunication group chat of the heterogeneous system, and determining the selected file as the file of the sharing account needing to be sent to the receiving account;

the file sharing module is used for responding to file sharing operation, determining the capacity of the file, and generating a sharing identification representing that the file needs to be stored in a storage server when the receiving account comprises at least one heterogeneous system account belonging to different systems with the sharing account and the capacity of the file exceeds a file capacity threshold;

The file sharing module is further configured to send 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, where the first system server is a server in a system to which the sharing account belongs;

the file sharing module is further used for obtaining a link of the storage server for storing the file; the link and the heterogeneous system account number are sent to a cross-system communication server through a cross-system access layer by a first system access layer, so that the cross-system communication server maps the heterogeneous system account number into an associated account number which can be identified by a second system server according to a mapping relation, and the link and the associated account number are sent to the second system server through the cross-system access layer by the second system access layer, so that the second system server sends the link to the associated account number;

11. An electronic device, comprising:

a memory for storing executable instructions;

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

12. A computer-readable storage medium, characterized in that computer-executable instructions are stored, which when executed are adapted to implement the file processing method of any of claims 1 to 9.