WO2023202721A1 - 文件传输方法、装置、电子设备和存储介质 - Google Patents

文件传输方法、装置、电子设备和存储介质 Download PDF

Info

Publication number
WO2023202721A1
WO2023202721A1 PCT/CN2023/094128 CN2023094128W WO2023202721A1 WO 2023202721 A1 WO2023202721 A1 WO 2023202721A1 CN 2023094128 W CN2023094128 W CN 2023094128W WO 2023202721 A1 WO2023202721 A1 WO 2023202721A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
upload
download
server
interface
Prior art date
Application number
PCT/CN2023/094128
Other languages
English (en)
French (fr)
Inventor
谭利霞
Original Assignee
广州视臻信息科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 广州视臻信息科技有限公司 filed Critical 广州视臻信息科技有限公司
Publication of WO2023202721A1 publication Critical patent/WO2023202721A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/04817—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance using icons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K17/00—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K17/00—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations
    • G06K17/0022—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisions for transferring data to distant stations, e.g. from a sensing device
    • G06K17/0025—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisions for transferring data to distant stations, e.g. from a sensing device the arrangement consisting of a wireless interrogation device in combination with a device for optically marking the record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/401—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]

Definitions

  • the embodiments of the present application relate to the field of data transmission technology, and in particular to file transmission methods, devices, electronic devices and storage media.
  • the source of the focus information may include files uploaded by the terminal equipment equipped by each participant, as well as various files generated by the conference equipment. If there are remote access participants, there may also be files generated by the remote conference equipment. document.
  • file data stored in personal terminal equipment can usually only be opened locally and then the file content can be sent to the conference terminal in a screencasting manner.
  • the file data itself cannot be quickly sent to the conference equipment; for files presented by the conference equipment, the file information can only be received visually or audibly by the individual terminal users themselves, and the file data itself cannot be quickly saved to the personal terminal for subsequent use.
  • users at both ends need to communicate in advance, and both parties must operate independently through mobile storage devices, communication software or emails to complete the transmission of file data.
  • File data transmission in conference scenarios The operation process is more complicated.
  • This application provides a file transmission method, device, electronic equipment and storage medium to solve the existing technical problems of relatively complex file data transmission operations in conference scenarios.
  • embodiments of the present application provide a file transmission method for a first device, including:
  • the file transfer interface includes a file download area and a file upload area
  • a file download interface is displayed, and the file download interface displays a first icon corresponding to the file directory obtained from the server according to the access request;
  • the file upload interface In response to the upload triggering operation, the file upload interface is displayed, and the file upload interface displays a second icon corresponding to the alternative upload file;
  • file data corresponding to at least one second icon is sent to the server.
  • embodiments of the present application also provide a file transmission method for the second device, including:
  • the file directory of the locally stored file is sent to the server, and the file management window is opened.
  • the file management window displays a QR code, and the QR code carries the access address information of the file directory on the server;
  • embodiments of the present application also provide a file transmission method for a server, including:
  • embodiments of the present application also provide a file transmission device for the first device, including:
  • the interface entry unit is used to obtain the access address information through the collaborative application recognition QR code, initiate an access request to the server, and enter the file transfer interface.
  • the file transfer interface includes a file download area and a file upload area;
  • the download operation receiving unit is used to receive the download trigger operation generated in the file download area
  • a download interface display unit configured to display a file download interface in response to a download triggering operation.
  • the file download interface displays a first icon corresponding to the file directory obtained from the server according to the access request;
  • a download target receiving unit configured to receive a file download operation for at least one first icon in the file download interface
  • a download request sending unit configured to send a file download request corresponding to at least one first icon to the server in response to the file download operation
  • the download file acquisition unit is used to obtain the file corresponding to the file download request from the server;
  • the upload operation receiving unit is used to receive the upload trigger operation generated in the file upload area
  • the upload interface display unit is used to display the file upload interface in response to the upload trigger operation, and the file upload interface displays a second icon corresponding to the alternative upload file;
  • the upload target receiving unit is used to receive a file upload operation for at least one second icon in the file upload interface
  • the upload data sending unit is configured to send file data corresponding to at least one second icon to the server in response to the file upload operation.
  • embodiments of the present application also provide a file transmission device for a second device, including:
  • Open command receiving unit used to receive file window opening commands
  • the open command response unit is used to respond to the file window opening command, send the file directory of the locally stored files to the server, and open the file management window.
  • the file management window displays a QR code, and the QR code carries the access of the file directory on the server. Address information;
  • the file request instruction receiving unit is used to receive the file request instruction sent by the server according to the file directory;
  • the file upload unit is used to upload the local storage file corresponding to the file request instruction to the server;
  • the file download unit is used to receive download files sent by the server and save the download files locally.
  • embodiments of the present application also provide a file transmission device for a server, including:
  • the file directory receiving unit is used to receive and save the file directory sent by the second device, and send access address information to the second device;
  • the file directory sending unit is configured to receive an access request initiated by the first device based on the access address information, and send the file directory to the first device;
  • a download request receiving unit configured to receive a file download request sent by the first device according to the file directory
  • a request instruction sending unit is used to send a file request instruction to the second device to obtain the file corresponding to the file download request in the file directory;
  • the download request response unit is used to save the file uploaded by the second device corresponding to the first device;
  • the upload data acquisition unit is used to acquire the file data provided by the first device, and send the corresponding file to the second device for storage according to the file data.
  • embodiments of the present application also provide an electronic device, including:
  • processors one or more processors
  • Memory for storing one or more computer programs
  • the electronic device When one or more computer programs are executed by one or more processors, the electronic device is caused to implement any of the file transfer methods of the first aspect, the second aspect, and the third aspect.
  • embodiments of the present application also provide a computer-readable storage medium on which a computer program is stored.
  • the computer program is executed by a processor, the file transmission in any one of the first aspect, the second aspect, and the third aspect is implemented. method.
  • the first device identifies the QR code through the collaborative application to obtain the access address information, initiates an access request to the server, and enters the file transfer interface.
  • the file transfer interface includes a file download area.
  • the user can independently upload files to and download from the second device by operating the first device in a meeting scenario using a conference device. files, which simplifies the operation process of file data transmission in conference scenarios and improves the data transmission efficiency between the first device and the second device.
  • Figure 1 is a flow chart of interface changes and data flow of a file transmission method provided by an embodiment of the present application.
  • Figure 2 is a schematic diagram of the interface of the interactive tablet.
  • Figure 3 is a schematic diagram of the architecture of an interactive tablet and a terminal device during collaborative interaction according to an embodiment of the present application.
  • Figure 4 is a schematic diagram of a file window opening instruction provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of a file management window provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram of the main page of the collaboration application provided by the embodiment of the present application.
  • FIG. 7 is a schematic diagram of an upload triggering operation on a file transfer interface provided by an embodiment of the present application.
  • Figure 8 is a schematic diagram of the file upload operation on the file upload interface provided by the embodiment of the present application.
  • Figure 9 is a schematic diagram of a file upload result prompt provided by an embodiment of the present application.
  • Figure 10 is a schematic diagram of the file management window after file upload provided by the embodiment of the present application.
  • Figure 11 is a schematic diagram of a download triggering operation on a file transfer interface provided by an embodiment of the present application.
  • Figure 12 is a schematic diagram of the file download operation on the file download interface provided by the embodiment of the present application.
  • Figure 13 is a schematic diagram of the main page of the collaborative application after file downloading provided by the embodiment of the present application.
  • Figure 14 is a method flow chart of a file transmission method for a first device provided by an embodiment of the present application.
  • Figure 15 is a method flow chart of a file transmission method for a second device provided by an embodiment of the present application.
  • Figure 16 is a method flow chart of a file transmission method for a server provided by an embodiment of the present application.
  • Figure 17 is a method flow chart of a file transmission device for a first device provided by an embodiment of the present application.
  • Figure 18 is a method flow chart of a file transmission device for a second device provided by an embodiment of the present application.
  • Figure 19 is a method flow chart of a file transmission device for a server provided by an embodiment of the present application.
  • Figure 20 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • the conference equipment can be a hardware product specially developed based on the conference scenario (such as an interactive tablet), or it can use existing equipment (large-size smart TV) for content display.
  • file transfer between participants and between participants and conference participants usually requires mobile
  • the storage device or both parties operate file transfer tools to complete the file data transfer operation.
  • the file data transfer operation is more complicated and the transfer efficiency is low. Especially when multiple people are involved and files need to be saved among multiple people, file transfer may need to be queued.
  • the conference equipment that specifically implements the file transmission method in this solution has the characteristics of large size, independent operating system, and network access, so that collaborative information can be displayed to multiple people, necessary data transmission with terminal equipment, and remote communication. Design requirements such as network connection of the device.
  • the interactive tablet is used as the main form of the conference equipment to illustrate the solution.
  • the interactive tablet mentioned in this solution can be an integrated device that uses touch technology to control the content displayed on the display tablet and realize human-computer interaction. It integrates a projector, electronic whiteboard, screen, audio, and TV One or more functions such as machine and video conferencing terminal.
  • the interactive tablet 11 includes at least one display screen 12 .
  • the interactive tablet 11 is configured with a display screen 12 with a touch function, and the display screen 12 can be a capacitive screen, a resistive screen, or an electromagnetic screen.
  • the user can realize the touch operation by touching the display screen 12 with a finger or a stylus.
  • the interactive tablet 12 detects the touch position and responds according to the touch position to realize the touch operation. control function.
  • the interactive tablet 11 is installed with at least one operating system, where the operating system includes but is not limited to Android system, Linux system and Windows system.
  • the interactive tablet is an interactive device mainly used to support multi-person communication scenarios, and the software in it is mainly used to realize the functional requirements in multi-person communication scenarios.
  • the interactive tablet may be installed with at least one application program having a document presentation function, where the application program may be a built-in application program of the operating system; at the same time, an application program downloaded from a third-party device or server may also be installed.
  • programs with document presentation functions also have other editing functions during the presentation, such as inserting tables, inserting pictures, inserting graphics, drawing tables, drawing graphics, etc.
  • the interactive tablet can be installed with at least one application with a whiteboard function, and the user can use the application to realize real-time writing, recording, modification and saving in multi-person collaborative communication scenarios.
  • the interactive tablet 11 can install an application to receive and display the screen projection, thereby using the architecture shown in Figure 3 to support multi-person communication scenarios.
  • Data transmission means that one or more participants in multi-person communication connect the personal terminal device to the interactive tablet 11 through the local area network or wide area network.
  • the personal terminal device and the interactive tablet 11 are also connected to the server 30 through the network.
  • the terminal device can be a personal computer 21 or a mobile terminal 22.
  • a single participant can only connect to the personal computer 21 or the mobile terminal 22, or can connect to the personal computer 21 and the mobile terminal 22 at the same time. .
  • multi-person communication is no longer just communication focused on the interactive tablet 11, but a collaborative interaction process of all participants on their respective terminal devices.
  • the terminal device used personally by conference participants is defined as the first device
  • the device used to display conference focus information to all participants is defined as the second device.
  • Participants copy the files that need to be displayed on the interactive tablet 11 to the interactive tablet 11 through a mobile storage device or send them to the interactive tablet 11 through a file transfer tool, and then open the file on the interactive tablet 11 for display; or directly display and cast it on a personal terminal device. screen to the interactive tablet 11 for display. If a participant wants to obtain files displayed by others, they also need to copy them through a mobile storage device or receive them from the other party through a file transfer tool. No matter which method is used for sending and receiving, the participants need to operate separately on two terminal devices, and the file transfer efficiency is low.
  • this solution implements a file transfer method that is simple to operate and efficient in conference scenarios.
  • the interactive tablet 11 and the terminal device serves as the actual focus device for presenting the conference content, and which one serves as the actual personal device used by the participants. That is, the interactive tablet 11 can be used by someone.
  • Each participant participates in the conference scene.
  • a certain personal computer 22 may also be used as a focus device for presenting conference content, and other personal computers 22 are used by participants to participate in the conference scene.
  • the hardware architecture of this solution does not even require the existence of the interactive tablet 11, that is, multiple terminal devices are connected to the server 30.
  • One of the terminal devices is used as the focus device for presenting conference content, assuming the role of the interactive tablet 11 in Figure 3, and the other terminals Devices are used by participants as terminals for individual collaborative interactions.
  • both the first device and the second device are installed with corresponding software for implementing this solution.
  • file management software is mainly installed, which is different from the existing file management tools that come with a personal computer system.
  • the file management software can have an account registered in the server and can be used on the first device. This account logs into the file management software.
  • the specific file management method of the file management software can be managed by storage path or by file type. There is no specific limit.
  • a collaboration application is mainly installed for realizing collaborative interaction with the first device and other second devices.
  • Normal use of collaborative applications also requires corresponding account registration and login. Participants in all conference scenarios can log in to their accounts on their personal terminal devices and conduct rich data interactions through the server. For example, during a meeting, you can control the first device, upload local files to your personal data space, initiate an audio and video conference, communicate with participants corresponding to another second device and then perform data transmission, etc.
  • the first device may also display the identification of the currently accessed second device, etc.
  • File management software and collaboration applications can be regarded as client software that provides corresponding functions for different device roles under the same data service system.
  • File management software and collaboration applications can realize data interaction based on the same data service system.
  • This solution is based on The system architecture, data service system and two client modes mentioned above are implemented.
  • the collaboration application and the file management software can be logged in through the same account.
  • the functions of the collaboration application and the file management software can be integrated into the same client software, that is, the first device and the second device.
  • the devices actually use the same or different versions of the same client software.
  • the collaboration application and the file management software will be used as the client software corresponding to the first device and the second device respectively.
  • File management software and collaboration applications are only limited to having corresponding functions and capable of data interaction within the software and hardware framework mentioned above, and do not imply restrictions on specific software names.
  • file management software can be named file presentation and file browsing; collaboration applications It can be named collaboration platform, collaboration meeting, etc.
  • first device and the second device are only used to define their device roles when using a specific function in a conference scenario.
  • collaboration application and file management software may be installed at the same time. It uses the collaboration application as the first device in a certain meeting scenario and uses the file management software as the second device in another meeting scenario.
  • a common hardware device role allocation method is that the interactive tablet 11 shown in Figure 3 is used as the second device, and the mobile terminal 22 or personal computer 21 of the conference participant is used as the first device.
  • the embodiment of the present application is based on this role allocation method. Give a detailed description.
  • FIG. 1 is a schematic diagram of interface changes and data flow of a file transfer method provided by an embodiment of the present application. Based on the interface changes and data flow shown in Figure 1, a comprehensive description of the file transfer method is given.
  • the file transfer method can be described as Including step S101-step S121:
  • Step S101 The second device receives a file window opening instruction.
  • the second device 10 only exists as an isolated hardware entity, it mainly realizes the display of conference focus information, and other terminal devices can basically only display the conference focus information through a screen projector or screen projection software. .
  • the second device 10 establishes a communication association with other devices in the architecture shown in Figure 3 through the received file window opening instruction.
  • Figure 4 shows a schematic diagram of an exemplary file window opening instruction.
  • the display screen 12 displays the display interface 13 of the interactive tablet 11 and displays the system desktop.
  • the system desktop includes at least one software icon 131, such as an icon 131 of a file management software.
  • the name of the file management software is "File Presentation", that is, the icon 131 of the file management software is the icon 131 corresponding to "File Presentation”.
  • An exemplary implementation of the file window opening instruction is to receive the opening instruction for the icon 131 of the file management software as the file window opening instruction.
  • the triggering operation of the icon 131 is to confirm receipt of the file window opening instruction when receiving the opening instruction for the "file presentation” icon 131.
  • receiving the operation instruction to insert a file in the whiteboard application window can also be used as a file window opening instruction.
  • the whiteboard application is the application with the whiteboard function mentioned above.
  • the whiteboard application window it can support the insertion of third-party files corresponding to various other file editing programs for display, such as inserting documents in the whiteboard application, Tables, pictures, etc.
  • the above operations can be realized by a single-finger touch of the corresponding icon detected by the touch screen, or by the operation of the corresponding icon detected by the mouse. Subsequent operations can also be realized by various interactive devices, and the specific interactive device realizes the corresponding The operation has been implemented in the existing technology, and will not be emphasized in subsequent operations.
  • Step S102 The second device responds to the file window opening instruction, sends the file directory of the locally stored file to the server, and opens the file management window.
  • the file management window displays a QR code, and the QR code carries the access address of the file directory on the server. information.
  • the file management window 132 shown in Figure 5 is opened.
  • the file management window 132 serves as an interactive interface for the user to operate files locally stored in the second device 10, in which the files stored in the second device 10 are displayed.
  • the file icon 133 corresponding to the file.
  • the locally stored files here mainly refer to user files saved by the second device 10. If necessary, system files can also be displayed according to default settings or user operations. In the file management window 132 shown in Figure 5, five locally stored files are displayed, namely "Pre-Research Chapter" and so on. In the file management window 132, you can also search for locally stored files to achieve rapid location of target files.
  • the second device 10 When opening the file management software, the second device 10 sends the file directory of the locally stored files to the server 30 and obtains the corresponding access address information returned by the server 30 as soon as possible.
  • the file management window 132 displays the file directory of the locally stored files. icon, the QR code 134 generated based on the access address information is also displayed.
  • Step S103 The server receives and saves the file directory sent by the second device, and sends the access address information to the second device.
  • the server 30 After receiving the file directory sent by the second device 10, the server 30 saves it, and sends the access address information corresponding to the save address to the second device 10, so that the second device 10 displays the file icon 133 in the file management window 132 at the same time.
  • the QR code 134 corresponding to the access address information 134 is displayed.
  • steps S103 and S102 are not strictly executed sequentially.
  • the file management window 132 is displayed in step S102, the access address information has actually been obtained and the QR code 134 has been generated. That is, some details in step S102 are implemented in step S103.
  • the relevant equipment that performs the steps is used as a reference, and the step with a high specific execution correlation is described as a step.
  • the above step numbers do not strictly indicate the order of the steps, but mainly indicate the role of a device in the process of implementing this solution. the overall implementation process.
  • Step S104 The first device obtains the access address information through the collaborative application recognition QR code, initiates an access request to the server, and enters the file transfer interface.
  • the file transfer interface includes a file download area and a file upload area.
  • the display page 23 of the first device 20 is as shown in Figure 6.
  • What is displayed at this time is the main page of the collaboration application, in which information used to implement the collaborative interaction process and various information can be displayed.
  • This kind of operation control, the interactive implementation of specific collaborative applications is not the focus of this solution, and will not be explained in detail here.
  • the code scanning control 231 as shown in Figure 6.
  • the camera is called to obtain information.
  • the access address information provided by the server 30 is identified and the generated QR code corresponds to the generated QR code, the camera is called based on the access address.
  • the information accesses the server 30 to obtain the file directory, and the display page 23 is switched to display the file transfer interface.
  • the file transfer interface is shown in Figure 7, corresponding to the upload operation and download operation of the file transfer.
  • the file transfer interface includes a file download area and a file upload area. , respectively corresponding to triggering file download operations and file upload operations.
  • the file directory may not be directly displayed on the file transfer interface after being obtained from the server 30 .
  • the second device 10 may not maintain the display state of the file management window 132, but open the file in the file management window 132, or open the whiteboard application to focus The central role of information display.
  • Step S105 The server receives the access request initiated by the first device based on the access address information, and sends the file directory to the first device.
  • step S105 the step of the server 30 sending the file directory to the first device 20 is as follows: After step S105, the actual execution is before displaying the file download area.
  • Step S106 The first device receives the download trigger operation generated in the file download area.
  • the file download area displays a file download control 234.
  • a trigger operation acting on the file download control 234 is detected, it is confirmed that the download trigger operation generated in the file download area is received.
  • Step S107 In response to the download triggering operation, the first device displays a file download interface.
  • the file download interface displays a first icon corresponding to the file directory obtained from the server according to the access request.
  • file information that can be downloaded from the second device 10 is correspondingly provided.
  • the first icon corresponding to the file directory of the second device 10 is displayed in the file download interface, and the file directory corresponds to
  • the icon in the file directory is defined as the first icon obtained from the server 30 according to the access request.
  • the first icon can be a thumbnail or a file name, as long as clear file information can be provided in the first icon.
  • Step S108 The first device receives a file download operation for at least one first icon in the file download interface.
  • the number of currently selected files may be displayed at the same time. For example, the number of selected files in Figure 12 is 2.
  • Step S109 In response to the file download operation, the first device sends a file download request corresponding to at least one first icon to the server.
  • Step S110 The server receives the file download request sent by the first device according to the file directory.
  • the first device 20 After receiving the confirmed file download operation, the first device 20 sends the corresponding file download request to the server 30 , that is, sends the file information to be downloaded to the server 30 .
  • Step S111 The server sends a file request instruction to the second device to obtain the file corresponding to the file download request in the file directory.
  • Step S112 The second device receives the file request instruction sent by the server according to the file directory.
  • Step S113 The second device uploads the locally stored file corresponding to the file request instruction to the server.
  • the files in the second device 10 are not saved synchronously. Considering the uncertainty of the first device 20 downloading files from the first device 10, there is no need to synchronize the files in the second device 10. Therefore, the server 30 sends a message to the second device 10 according to the received file download request.
  • the file request instruction is used to instruct the second device 10 to provide the file specified in the file directory in the file download request. After receiving the file request instruction, the second device 10 uploads the corresponding locally stored file to the server 30 .
  • Step S114 The server saves the file uploaded by the second device corresponding to the first device.
  • Step S115 The first device obtains the file corresponding to the file download request from the server.
  • the server 30 saves the file uploaded by the second device 10 corresponding to the first device 20. Specifically, it can be saved directly to the first device 20, or it can be saved to the first device that sends the file download request corresponding to the account currently logged in. Cloud space. Specifically, each collaboration application account has a corresponding storage space on the server, which is used to save the historical collaboration information corresponding to the account.
  • the historical collaboration information includes generated meeting reservation information, files generated by existing meetings, etc.
  • each information block is used to display historical collaboration information corresponding to a conference topic.
  • the main page displays two information blocks, which respectively display the reservation information of an upcoming meeting topic and the two files generated by historical collaboration information.
  • the first device 20 can obtain the file directly by obtaining the corresponding storage space, that is, the server 30 directly saves the file obtained from the second device 10 to the first device 10 corresponding to the file download request in the server 30 of storage space.
  • an information block is added to the main page of the collaboration application to display the latest downloaded file information, and the downloaded file can be opened, displayed and viewed from the information block.
  • Step S116 The first device receives the upload trigger operation generated in the file upload area.
  • in-application files refer to files generated in collaborative applications and are usually saved on the server
  • chat files refer to files recorded during file transfer in various social tools and are usually saved in specific folders
  • local photo albums and local files are mainly downloaded
  • picture files and non-picture files directly generated by the first device 20 may also overlap.
  • a picture file may be a file in a local photo album or a file in a chat file.
  • Step S117 In response to the upload triggering operation, the first device displays a file upload interface, and the file upload interface displays a second icon corresponding to the alternative upload file.
  • Step S118 The first device receives a file upload operation for at least one second icon in the file upload interface.
  • Step S119 In response to the file upload operation, the first device sends file data corresponding to at least one second icon to the server.
  • the interaction process of the file upload operation and the file download operation is generally similar.
  • the main difference lies in the different transmission directions of the files.
  • the files stored by the first device 20 in the corresponding storage space of the server 30 are completed.
  • the file upload operation can further accurately and quickly transmit various types of data.
  • Step S120 The server obtains the file data provided by the first device, and sends the corresponding file to the second device for storage according to the file data.
  • the server 30 obtains the file identification data provided by the first device 20; extracts the file from the storage space corresponding to the first device 20 according to the file identification data; and sends the extracted file to the second device 10 for storage. That is, when uploading an in-application file, the first upload trigger operation acting on the collaboration file control 233 is received; in response to the first upload trigger operation, a file upload interface is displayed, and the file upload interface displays the file corresponding to the file in the historical collaboration information. Two icons; in response to the file upload operation, send file identification data corresponding to at least one second icon to the server 30 . This completes the uploading operation of the "Meeting Observation List" in Figure 8.
  • Step S121 The second device receives the download file sent by the server and saves the download file locally.
  • the server 30 Based on the directly received file or the file obtained based on the file identification data, the server 30 displays the new identification on the icon corresponding to the downloaded file saved locally until the currently opened file management window is closed.
  • the new identification (new) of the file is set until the file management window that is opened is closed, that is, next time When the file management window is opened, the "new" on the icon of the "Meeting Watch List” in Figure 10 is no longer displayed.
  • the server 30 or the first device 20 After the server 30 or the first device 20 confirms that the file is successfully sent to the first device 20, it can return to the file transfer interface, and display the file upload result prompt as shown in Figure 9 on the file transfer interface.
  • the user can independently upload files to and download from the second device by operating the first device in a meeting scenario using a conference device. files, which simplifies the operation process of file data transmission in conference scenarios and improves the data transmission efficiency between the first device and the second device.
  • the above is an overall description of file transmission based on the architecture of the first device, server and second device. For one end, they can all exist as independent product forms. The following is the corresponding implementation files for the first device, server and second device. The procedures of the transmission methods are described separately.
  • Figure 14 is a method flow chart of a file transmission method for the first device.
  • the file transmission method includes:
  • Step S200 Obtain the access address information by identifying the QR code through the collaborative application, initiate an access request to the server, and enter the file transfer interface.
  • the file transfer interface includes a file download area and a file upload area.
  • Step S201 Receive the download trigger operation generated in the file download area.
  • Step S202 In response to the download triggering operation, a file download interface is displayed.
  • the file download interface displays a first icon corresponding to the file directory obtained from the server according to the access request.
  • Step S203 Receive a file download operation for at least one first icon in the file download interface.
  • Step S204 In response to the file download operation, send a file download request corresponding to at least one first icon to the server.
  • Step S205 Obtain the file corresponding to the file download request from the server.
  • Step S206 Receive the upload trigger operation generated in the file upload area
  • Step S207 In response to the upload triggering operation, the file upload interface is displayed, and the file upload interface displays a second icon corresponding to the candidate upload file.
  • Step S208 Receive a file upload operation for at least one second icon in the file upload interface
  • Step S209 In response to the file upload operation, send file data corresponding to at least one second icon to the server.
  • the main page of the collaboration application displays an information block, and the file upload area displays a collaboration file control.
  • the information block is used to display historical collaboration information saved on the server;
  • step S206 includes step S2061:
  • Step S2061 Receive the first upload trigger operation acting on the collaborative file control
  • step S207 includes step S2071:
  • Step S2071 In response to the first upload triggering operation, display the file upload interface, and the file upload interface displays the second icon corresponding to the file in the historical collaboration information;
  • step S209 includes step S20191:
  • file identification data corresponding to at least one second icon is sent to the server.
  • step S2051 is also included:
  • Step S2051 Add an information block for displaying the obtained file on the main page of the collaboration application.
  • step S209 it also includes:
  • Step S2091 Return to the file transfer interface, and display the file upload result prompt on the file transfer interface.
  • Figure 15 is a method flow chart of a file transfer method for a second device.
  • the file transfer method includes:
  • Step S301 Receive a file window opening instruction.
  • Step S302 In response to the file window opening instruction, send the file directory of the locally stored files to the server, open the file management window, the file management window displays a QR code, and the QR code carries the file directory. Access address information on the server.
  • Step S303 Receive a file request instruction sent by the server according to the file directory.
  • Step S304 Upload the locally stored file corresponding to the file request instruction to the server.
  • Step S305 Receive the download file sent by the server, and save the download file locally.
  • step S301 is specifically step S3011 or step S3012:
  • Step S3011 Receive an instruction to open an icon of the file management software as a file window opening instruction.
  • Step S3012 Receive an operation instruction to insert a file in the whiteboard application window as a file window opening instruction.
  • the file transmission method also includes:
  • Step S306 Display a new logo on the icon corresponding to the downloaded file saved locally until the currently opened file management window is closed.
  • Figure 16 is a method flow chart of the file transfer method for the server. As shown in Figure 16, the file transfer method includes:
  • Step S401 Receive and save the file directory sent by the second device, and send access address information to the second device.
  • Step S402 Receive an access request initiated by the first device based on the access address information, and send a file directory to the first device.
  • Step S403 Receive a file download request sent by the first device according to the file directory.
  • Step S404 Send a file request instruction to the second device to obtain the file corresponding to the file download request in the file directory.
  • Step S405 Save the file uploaded by the second device corresponding to the first device.
  • Step S406 Obtain the file data provided by the first device, and send the corresponding file to the second device for storage according to the file data.
  • the server is provided with a storage space for saving historical collaboration information corresponding to the first device
  • step S406 includes step S4061-step S4063:
  • Step S4061 Obtain the file identification data provided by the first device
  • Step S4062 Extract files from the storage space corresponding to the first device according to the file identification data
  • Step S4063 Send the extracted file to the second device for saving.
  • step S405 includes step S4051:
  • Step S4051 Save the file uploaded by the second device to the storage space corresponding to the first device.
  • FIG 17 is a schematic structural diagram of a file transmission device provided by an embodiment of the present application.
  • the file transfer device is used in the first device.
  • the file transfer device includes an interface entry unit 500, a download operation receiving unit 510, a download interface display unit 520, a download target receiving unit 530, a download request sending unit 540, and a download file.
  • the interface entry unit 500 is used to obtain the access address information through the collaborative application recognition QR code, initiate an access request to the server, and enter the file transfer interface.
  • the file transfer interface includes a file download area and a file upload area; the download operation receiving unit 510, Used to receive the download trigger operation generated in the file download area; the download interface display unit 520 is used to display the file download interface in response to the download trigger operation.
  • the file download interface displays the first file directory corresponding to the file directory obtained from the server according to the access request.
  • the download target receiving unit 530 is used to receive a file download operation for at least one first icon in the file download interface; the download request sending unit 540 is used to download the file corresponding to the at least one first icon in response to the file download operation
  • the request is sent to the server;
  • the download file acquisition unit 550 is used to obtain the file corresponding to the file download request from the server;
  • the upload operation receiving unit 560 is used to receive the upload trigger operation generated in the file upload area;
  • the upload interface display unit 570 is used to In response to the upload trigger operation, the file upload interface is displayed, and the file upload interface displays a second icon corresponding to the alternative upload file;
  • the upload target receiving unit 580 is used to receive a file upload operation for at least one second icon in the file upload interface;
  • the upload data sending unit 590 is configured to send file data corresponding to at least one second icon to the server in response to the file upload operation.
  • the main page of the collaboration application displays an information block
  • the file upload area displays a collaboration file control
  • the information block is used to display historical collaboration information saved on the server;
  • the upload operation receiving unit 560 includes:
  • the first upload operation receiving module is used to receive the first upload trigger operation acting on the collaborative file control
  • the upload interface display unit 570 includes:
  • the first upload interface display module is configured to display a file upload interface in response to the first upload trigger operation, and the file upload interface displays a second icon corresponding to the file in the historical collaboration information;
  • the upload data sending unit 590 includes:
  • the file identification data sending module is configured to send the file identification data corresponding to at least one second icon to the server in response to the file upload operation.
  • the file transmission device further includes:
  • the information block adds a display unit, which is used to add an information block for displaying the obtained files on the main page of the collaboration application.
  • the file transmission device further includes:
  • the upload result display unit is used to return to the file transfer interface and display the file upload result prompt on the file transfer interface.
  • Figure 18 is a schematic structural diagram of a file transmission device provided by an embodiment of the present application.
  • the file transfer device is used for the second device.
  • the file transfer device includes an opening instruction receiving unit 610, an opening instruction response unit 620, a file request instruction receiving unit 630, a file uploading unit 640 and a file downloading unit 650.
  • the opening instruction receiving unit 610 is used to receive the file window opening instruction; the opening instruction response unit 620 is used to respond to the file window opening instruction, send the file directory of the locally stored file to the server, and open the file management window.
  • a QR code is displayed, and the QR code carries the access address information of the file directory on the server;
  • the file request instruction receiving unit 630 is used to receive the file request instruction sent by the server according to the file directory;
  • the file upload unit 640 is used to transfer the file request The local storage file corresponding to the instruction is uploaded to the server; the file download unit 650 is used to receive the download file sent by the server and save the download file locally.
  • the opening instruction receiving unit 610 is specifically used to:
  • the file transmission device further includes:
  • the logo display unit is used to display the new logo on the icon corresponding to the downloaded file saved locally until the currently opened file management window is closed.
  • Figure 19 is a schematic structural diagram of a file transmission device provided by an embodiment of the present application.
  • the file transfer device is used in a server.
  • the file transfer device includes a file directory receiving unit 710, a file directory sending unit 720, a download request receiving unit 730, a request instruction sending unit 740, a download request response unit 750 and an upload data acquisition unit.
  • Unit 760 the file transfer device includes a file directory receiving unit 710, a file directory sending unit 720, a download request receiving unit 730, a request instruction sending unit 740, a download request response unit 750 and an upload data acquisition unit.
  • Unit 760 is a schematic structural diagram of a file transmission device provided by an embodiment of the present application.
  • the file transfer device includes a file directory receiving unit 710, a file directory sending unit 720, a download request receiving unit 730, a request instruction sending unit 740, a download request response unit 750 and an upload data acquisition unit.
  • Unit 760 the file transfer device includes a file directory receiving
  • the file directory receiving unit 710 is used to receive and save the file directory sent by the second device, and send access address information to the second device;
  • the file directory sending unit 720 is used to receive an access request initiated by the first device based on the access address information. , sending a file directory to the first device;
  • the download request receiving unit 730 is used to receive a file download request sent by the first device according to the file directory;
  • the request instruction sending unit 740 is used to send a file request instruction to the second device to obtain the file Download the file corresponding to the file directory in the request;
  • the download request response unit 750 is used to save the file uploaded by the second device corresponding to the first device;
  • the upload data acquisition unit 760 is used to obtain the file data provided by the first device, Send the corresponding file to the second device for storage according to the file data.
  • the server is provided with a storage space for saving historical collaboration information corresponding to the first device
  • the upload data acquisition unit 760 includes:
  • An identification acquisition module used to obtain the file identification data provided by the first device
  • a file extraction module configured to extract files from the storage space corresponding to the first device according to the file identification data
  • the file sending module is used to send the extracted files to the second device for saving.
  • the download request response unit 750 includes:
  • the cloud saving module is used to save the files uploaded by the second device to the storage space corresponding to the first device.
  • the file transmission device provided by the embodiments of the present application is included in an electronic device and can be used to execute the corresponding file transmission method provided in the above embodiments, and has corresponding functions and beneficial effects.
  • Figure 20 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • the electronic device includes a processor 810 and a memory 820, and may also include an input device 830, an output device 840, and a communication device 850; the number of processors 410 in the electronic device may be one or more,
  • a processor 810 is taken as an example; the processor 810, memory 820, input device 830, output device 840 and communication device 850 in the electronic device can be connected through a bus or other means. In Figure 20, connection through a bus is taken as an example.
  • the memory 820 can be used to store software programs, computer executable programs and modules, such as program instructions/modules corresponding to the file transmission method in the embodiment of the present application.
  • the processor 810 executes software programs, instructions and modules stored in the memory 820 to execute various functional applications and data processing of the electronic device, that is, to implement the above file transfer method.
  • the memory 820 may mainly include a stored program area and a stored data area, where the stored program area may store an operating system and at least one application program required for a function; the stored data area may store data created according to the use of the electronic device, etc.
  • the memory 820 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device.
  • the memory 820 may further include memory located remotely relative to the processor 810, and these remote memories may be connected to the electronic device through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, local area networks, mobile communication networks and combinations thereof.
  • the input device 830 may be used to receive input numeric or character information and generate key signal input related to user settings and function control of the electronic device.
  • the output device 840 may include a display device such as a display screen.
  • the above-mentioned electronic equipment includes a file transfer device, which can be used to perform any file transfer method and has corresponding functions and beneficial effects.
  • Embodiments of the present application also provide a computer-readable storage medium on which a computer program is stored.
  • the computer program when executed by a processor, is used to perform relevant operations in the file transmission method provided in any embodiment of the present application, and Have corresponding functions and beneficial effects.
  • the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects.
  • the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
  • the present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions.
  • These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.
  • These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions
  • the device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device.
  • Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • Memory may include non-volatile memory in computer-readable media, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM).
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information.
  • Information may be computer-readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • read-only memory read-only memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory or other memory technology
  • compact disc read-only memory CD-ROM
  • DVD digital versatile disc
  • Magnetic tape cassettes tape magnetic disk storage or other magnetic storage devices or any other non-transmission medium can be used to store information that can be accessed by a computing device.
  • computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Human Computer Interaction (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请实施例公开了文件传输方法、装置、电子设备和存储介质。为第一设备和第二设备设置服务器，由服务器接收并保存第二设备发送的文件目录，返回访问地址信息；接收第一设备根据访问地址信息发起的访问请求，返回文件目录；接收第一设备根据文件目录发送的文件下载请求，并从第二设备获取请求的文件提供给第一文件；获取第一设备提供的文件数据并将对应的文件保存到第二设备。通过服务器在第一设备和第二设备之间的数据存储和转发，基于协作应用，用户在使用会议设备的会议场景下，操作第一设备可以独立向第二设备上传文件和从第二设备下载文件，简化了会议场景下文件数据传输的操作过程，提高了第一设备和第二设备间的数据传输效率。

Description

文件传输方法、装置、电子设备和存储介质
本申请要求于2022年04月21日提交中国专利局、申请号为202210423879.5、发明名称为“文件传输方法、装置、电子设备和存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及数据传输技术领域，尤其涉及文件传输方法、装置、电子设备和存储介质。
背景技术
在信息技术背景下的会议场景中，经常出现多人围绕会议设备呈现的焦点信息进行讨论。在这一讨论过程中，焦点信息的来源可能有各个与会者配备的终端设备上传的文件，也有会议设备产生的各种文件，如果有远程接入的与会者，还可能会有远程会议设备产生的文件。
发明人使用现有的会议设备进行焦点信息相关的文件数据交互时发现，存储于个人的终端设备的文件数据，通常只能在本地打开文件之后，以投屏的方式将文件内容发送到会议终端进行显示，文件数据本身不能快捷发送到会议设备；对于会议设备呈现的文件，只能由个人终端用户自己以视觉或听觉方式接收文件信息，文件数据本身不能快捷保存到个人终端进行后续使用。实现会议终端和个人终端设备间的数据传输，需要两端用户预先沟通后，双方均通过移动存储设备、通讯软件或电子邮件各自进行操作，才能完成文件数据的传输，在会议场景下文件数据传输的操作过程较为复杂。
申请内容
本申请提供了一种文件传输方法、装置、电子设备和存储介质，以解决现有在会议场景下文件数据传输的操作过程较为复杂的技术问题。
第一方面，本申请实施例提供了一种文件传输方法，用于第一设备，包括：
通过协作应用识别二维码获取访问地址信息向服务器发起访问请求，并进入文件传输界面，文件传输界面包括文件下载区和文件上传区；
接收在文件下载区生成的下载触发操作；
响应于下载触发操作，显示文件下载界面，文件下载界面显示有根据访问请求从所述服务器获取的文件目录对应的第一图标；
接收对文件下载界面中至少一个第一图标的文件下载操作；
响应于所述文件下载操作，将至少一个第一图标对应的文件下载请求发送到服务器；
从服务器获取文件下载请求对应的文件；
接收在文件上传区生成的上传触发操作；
响应于上传触发操作，显示文件上传界面，文件上传界面显示有备选上传文件对应的第二图标；
接收对文件上传界面中至少一个第二图标的文件上传操作；
响应于文件上传操作，将至少一个第二图标对应的文件数据发送到服务器。
第二方面，本申请实施例还提供了一种文件传输方法，用于第二设备，包括：
接收文件窗口开启指令；
响应于文件窗口开启指令，将本地存储文件的文件目录发送到服务器，打开文件管理窗口，文件管理窗口显示有二维码，二维码携带有文件目录在服务器的访问地址信息；
接收服务器根据文件目录发送的文件请求指令；
将文件请求指令对应的本地存储文件上传到服务器；
接收服务器发送的下载文件，将下载文件保存到本地。
第三方面，本申请实施例还提供了一种文件传输方法，用于服务器，包括：
接收并保存第二设备发送的文件目录，向第二设备发送访问地址信息；
接收第一设备根据访问地址信息发起的访问请求，向第一设备发送文件目录；
接收第一设备根据文件目录发送的文件下载请求；
向第二设备发送文件请求指令，以获取文件下载请求在文件目录中对应的文件；
将第二设备上传的文件对应于第一设备进行保存；
获取第一设备提供的文件数据，根据文件数据将对应的文件发送到第二设备进行保存。
第四方面，本申请实施例还提供了一种文件传输装置，用于第一设备，包括：
界面进入单元，用于通过协作应用识别二维码获取访问地址信息向服务器发起访问请求，并进入文件传输界面，文件传输界面包括文件下载区和文件上传区；
下载操作接收单元，用于接收在文件下载区生成的下载触发操作；
下载界面显示单元，用于响应于下载触发操作，显示文件下载界面，文件下载界面显示有根据访问请求从所述服务器获取的文件目录对应的第一图标；
下载目标接收单元，用于接收对文件下载界面中至少一个第一图标的文件下载操作；
下载请求发送单元，用于响应于文件下载操作，将至少一个第一图标对应的文件下载请求发送到服务器；
下载文件获取单元，用于从服务器获取文件下载请求对应的文件；
上传操作接收单元，用于接收在文件上传区生成的上传触发操作；
上传界面显示单元，用于响应于上传触发操作，显示文件上传界面，文件上传界面显示有备选上传文件对应的第二图标；
上传目标接收单元，用于接收对文件上传界面中至少一个第二图标的文件上传操作；
上传数据发送单元，用于响应于文件上传操作，将至少一个第二图标对应的文件数据发送到服务器。
第五方面，本申请实施例还提供了一种文件传输装置，用于第二设备，包括：
开启指令接收单元，用于接收文件窗口开启指令；
开启指令响应单元，用于响应于文件窗口开启指令，将本地存储文件的文件目录发送到服务器，打开文件管理窗口，文件管理窗口显示有二维码，二维码携带有文件目录在服务器的访问地址信息；
文件请求指令接收单元，用于接收服务器根据文件目录发送的文件请求指令；
文件上传单元，用于将文件请求指令对应的本地存储文件上传到服务器；
文件下载单元，用于接收服务器发送的下载文件，将下载文件保存到本地。
第六方面，本申请实施例还提供了一种文件传输装置，用于服务器，包括：
文件目录接收单元，用于接收并保存第二设备发送的文件目录，向第二设备发送访问地址信息；
文件目录发送单元，用于接收第一设备根据访问地址信息发起的访问请求，向第一设备发送文件目录；
下载请求接收单元，用于接收第一设备根据文件目录发送的文件下载请求；
请求指令发送单元，用于向第二设备发送文件请求指令，以获取文件下载请求在文件目录中对应的文件；
下载请求响应单元，用于将第二设备上传的文件对应于第一设备进行保存；
上传数据获取单元，用于获取第一设备提供的文件数据，根据文件数据将对应的文件发送到第二设备进行保存。
第七方面，本申请实施例还提供了一种电子设备，包括：
一个或多个处理器；
存储器，用于存储一个或多个计算机程序；
当一个或多个计算机程序被一个或多个处理器执行，使得电子设备实现如第一方面、第二方面和第三方面任一的文件传输方法。
第八方面，本申请实施例还提供了计算机可读存储介质，其上存储有计算机程序，该计算机程序被处理器执行时实现如第一方面、第二方面和第三方面任一的文件传输方法。
上述文件传输方法、装置、电子设备和存储介质，该方法中，第一设备通过协作应用识别二维码获取访问地址信息向服务器发起访问请求，并进入文件传输界面，文件传输界面包括文件下载区和文件上传区；接收在文件下载区生成的下载触发操作；响应于下载触发操作，显示文件下载界面，文件下载界面显示有根据访问请求从所述服务器获取的文件目录对应的第一图标；接收对文件下载界面中至少一个第一图标的文件下载操作；响应于文件下载操作，将至少一个第一图标对应的文件下载请求发送到服务器；从服务器获取文件下载请求对应的文件；接收在文件上传区生成的上传触发操作；响应于上传触发操作，显示文件上传界面，文件上传界面显示有备选上传文件对应的第二图标；接收对文件上传界面中至少一个第二图标的文件上传操作；响应于文件上传操作，将至少一个第二图标对应的文件数据发送到服务器。通过服务器在第一设备和第二设备之间的数据存储和转发，基于协作应用，用户在使用会议设备的会议场景下，操作第一设备可以独立向第二设备上传文件和从第二设备下载文件，简化了会议场景下文件数据传输的操作过程，提高了第一设备和第二设备间的数据传输效率。
附图说明
图1为本申请实施例提供的一种文件传输方法的界面变化及数据流动流程图。
图2为交互平板的界面示意图。
图3为本申请实施例协作交互时交互平板与终端设备的架构示意图。
图4为本申请实施例提供的一种文件窗口开启指令的示意图。
图5为本申请实施例提供的文件管理窗口的示意图。
图6为本申请实施例提供的协作应用的主页面的示意图。
图7为本申请实施例提供的在文件传输界面的上传触发操作的示意图。
图8为本申请实施例提供的在文件上传界面的文件上传操作的示意图。
图9为本申请实施例提供的文件上传结果提示的示意图。
图10为本申请实施例提供的文件上传后文件管理窗口的示意图。
图11为本申请实施例提供的在文件传输界面的下载触发操作的示意图。
图12为本申请实施例提供的在文件下载界面的文件下载操作的示意图。
图13为本申请实施例提供的文件下载后协作应用的主页面的示意图。
图14为本申请实施例提供的用于第一设备的文件传输方法的方法流程图。
图15为本申请实施例提供的用于第二设备的文件传输方法的方法流程图。
图16为本申请实施例提供的用于服务器的文件传输方法的方法流程图。
图17为本申请实施例提供的用于第一设备的文件传输装置的方法流程图。
图18为本申请实施例提供的用于第二设备的文件传输装置的方法流程图。
图19为本申请实施例提供的用于服务器的文件传输装置的方法流程图。
图20为本申请实施例提供的一种电子设备的结构示意图。
具体实施方式
下面结合附图和实施例对本申请作进一步的详细说明。可以理解的是，此处所描述的具体实施例用于解释本申请，而非对本申请的限定。另外还需要说明的是，为了便于描述，附图中仅示出了与本申请相关的部分而非全部结构。
需要注意的是，由于篇幅所限，本申请说明书没有穷举所有可选的实施方式，本领域技术人员在阅读本申请说明书后，应该能够想到，只要技术特征不互相矛盾，那么技术特征的任意组合均可以构成可选的实施方式。
下面对本申请各实施例进行详细说明。
会议、教学、讨论、头脑风暴等多人交互场景下，多个参与者之间的信息传递在很长一段历史时期都通过说话、视觉和听觉实现，这种信息传递能给参与者很好的沟通体验，但是对沟通过程中的信息记录依赖于参与者按个人习惯和能力进行记录，实际传递的信息可能会丢失。
随着信息技术的发展，多人交互场景下的信息展示和信息记录有了更丰富的手段，尤其是基于会议设备的多人交互，每个参与者可以将需要展示的内容集中到会议设备进行展示，也可以在个人终端打开文件后投屏到会议设备进行展示。会议设备可以是基于会议场景专门开发的硬件产品(例如交互平板)，也可以是使用已有的设备(大尺寸的智能电视)进行内容展示。
在基于会议设备的进行多人交互的应用场景下，文件的实际内容可以通过会议设备向所有参与者进行展示，但是参与者之间以及参与者与会议者之间的文件传输，通常需要通过移动存储设备或者双方操作文件传输工具完成，文件数据的传输操作较为复杂，传输效率较低。尤其是有多人参与和多人间文件保存需要时，文件传输可能需要排队处理。
具体实现本方案中文件传输方法的会议设备具有尺寸较大、具备独立运行的操作系统、可接入网络的特点，从而可以实现协作信息向多人展示，与终端设备的必要数据传输，与远程设备的网络连接等设计需求。
在具体实施方式中以交互平板作为会议设备的主要形态进行方案说明。本方案中所说的交互平板，可以是通过触控技术对显示在显示平板上的内容进行操控和实现人机交互操作的一体化设备，其集成了投影机、电子白板、幕布、音响、电视机以及视频会议终端等一种或多种功能。
一般而言，如图2所示，交互平板11包括至少一块显示屏12。例如，交互平板11配置有一块具有触摸功能的显示屏12，且该显示屏12可以是电容屏、电阻屏或者电磁屏。在本实施例中，进一步的，用户可以通过手指或触控笔触控显示屏12的方式实现触控操作，相应的，交互平板12检测触控位置，并根据触控位置进行响应，以实现触控功能。典型的，交互平板11安装有至少一种操作系统，其中，操作系统包括但不限定于安卓系统、Linux系统及Windows系统。
交互平板作为主要用于支持多人沟通场景的交互设备，其中的软件主要用于实现多人沟通场景下的功能需求。例如，交互平板可以安装至少一个具有文稿演示功能的应用程序，其中，该应用程序可以为操作系统自带的应用程序；同时，也安装有从第三方设备或者服务器中下载的应用程序。可选的，具有文稿演示功能的程序除了显示已经编辑好的内容这一基础功能，还具有其他演示过程中的编辑功能，如插入表格、插入图片、插入图形、绘制表格、绘制图形等功能，以实现信息展示过程中的用户信息输入和输入内容的实时展示，进而提高文稿演示过程中的信息展示和交互效果。例如，交互平板可以安装至少一个具有白板功能的应用程序，用户可以基于该应用程序实现多人协作沟通场景下的实时书写记录、修改和保存。
为进一步提高多人沟通场景下文件传递方面的便利性，交互平板11可以安装一应用程序，实现对投屏画面的接收和显示，由此使用图3所示的架构支持多人沟通场景下的数据传输，即多人沟通的参与者中的一个或多个，将个人的终端设备通过局域网或广域网连接到交互平板11，个人的终端设备和交互平板11同时还通过网络与服务器30连接。在图3所示的具体场景中，终端设备可以是个人计算机21，也可以是移动终端22，单个参与者可以只连接个人计算机21或移动终端22，也可以同时连接个人计算机21和移动终端22。基于图3所示的架构，多人沟通不再仅仅是聚焦于交互平板11的沟通，而是所有参与者在各自终端设备的协作交互过程。在本方案中，将会议参与者个人使用的终端设备定义为第一设备，用于向所有参与者展示会议焦点信息的设备定义为第二设备。
参与者将需要在交互平板11进行显示的文件通过移动存储设备复制到或通过文件传输工具发送到交互平板11，然后在交互平板11打开文件进行显示；或者直接在个人的终端设备进行显示并投屏到交互平板11进行显示。如果参与者要获取他人展示的文件，同样需要通过移动存储设备进行复制或通过文件传输工具从对方接收。不管是哪种方式进行收发，均需要对应参与者在两个终端设备的分别操作，文件传输效率较低。
基于图3所示的架构，本方案实现了在会议场景下操作简洁，传输高效的文件传输方法。在具体实现本方案的过程中，并不限定交互平板11和终端设备中的哪一方作为呈现会议内容的实际焦点设备，哪一方作为参与者个人使用的实际个人设备，即交互平板11可以由某个参与者使用参加到会议场景中，某一个人计算机22也可能作为呈现会议内容的焦点设备，其它个人计算机22由参与者使用参加到会议场景。本方案的硬件架构，甚至可以没有交互平板11的存在，即多个终端设备连接到服务器30，其中一个终端设备用作呈现会议内容的焦点设备，承担图3中交互平板11的角色，其余终端设备由参与者使用作为个人协作交互的终端。
在本方案中，第一设备和第二设备均安装有用于实现本方案的对应软件。对于第一设备，主要是安装有文件管理软件，与现有例如个人计算机系统自带的文件管理工具有所不同，该文件管理软件可以有在服务器中的账号注册，并可以在第一设备使用该账号登录文件管理软件，文件管理软件具体的文件管理方式可以是按存储路径进行管理，也可以是按文件类型进行管理，具体不做限定。
对于第二设备，主要是安装有协作应用，用于实现与第一设备以及其它第二设备的协作交互。协作应用的正常使用也需要对应的账号注册和登录，所有会议场景下的参与者可以在个人的终端设备登录账号，通过服务器进行数据的丰富交互。例如会议过程中对第一设备的控制，将本地文件上传到个人的数据空间，发起音视频会议，与另一第二设备对应的参与者沟通后进行数据传输等。在具体使用过程中，第一设备还可以显示当前接入的第二设备的标识等。
文件管理软件和协作应用可以视为同一数据服务体系下，针对不用的设备角色提供相应功能实现的客户端软件，文件管理软件和协作应用可以基于同一数据服务体系实现数据交互，本方案即为基于前文所说的系统架构、数据服务体系和两种客户端模式实现。在具体实现本方案的过程中，协作应用和文件管理软件可以通过同一账号进行登录，如果有必要，可以将协作应用和文件管理软件的功能集成到同一客户端软件，即第一设备和第二设备实际使用同一客户端软件的相同或不同版本，在具体实现本方案时，第一设备和第二设备本身使用的客户端软件可能没有区别，但是二者根据会议场景下的角色不同使用客户端软件中的不同功能。为表述方便，后续以协作应用和文件管理软件分别作为第一设备和第二设备对应的客户端软件。
文件管理软件和协作应用仅限定具有相应功能并能在前文所说的软硬件框架下进行数据交互，不表示对具体软件名称的限定，例如文件管理软件可以命名为文件演示、文件浏览；协作应用可以命名为协作平台、协作会议等。
需要说明的是，第一设备和第二设备仅用于限定其在会议场景下使用某一具体功能时的设备角色。对于某个电子设备而言，可能同时安装协作应用和文件管理软件，其在某个会议场景下使用协作应用作为第一设备，在另一会议场景下使用文件管理软件作为第二设备。一种常见的硬件设备角色分配方式是图3所示的交互平板11作为第二设备，会议参与者的移动终端22或个人计算机21作为第一设备，本申请实施例即基于这种角色分配方式进行具体描述。
图1为本申请实施例提供的一种文件传输方法的界面变化及数据流动示意图，基于图1所示的界面变化及数据流动，对文件传输方法进行综合描述，该文件传输方法，可以描述为包括步骤S101-步骤S121：
步骤S101：第二设备接收文件窗口开启指令。
请参考图1，如果第二设备10仅作为孤立的硬件个体存在，主要实现对会议焦点信息的展示，与其它终端设备基本只能通过投屏器或投屏软件进行会议焦点信息的投屏展示。在本方案中，第二设备10通过接收到的文件窗口开启指令，建立与图3所示架构内的其它设备的通信关联。
图4所示是一种示例性的文件窗口开启指令的示意图。交互平板11开机后，显示屏12显示交互平板11的显示界面13显示系统桌面，系统桌面包括至少一个软件的图标131，例如文件管理软件的图标131，图4所示的显示界面13中，文 件管理软件的名称为“文件演示”，即文件管理软件的图标131为“文件演示”对应的图标131。文件窗口开启指令的一种示例性实现方式，是接收对文件管理软件的图标131的开启指令作为文件窗口开启指令，具体到图4所示的显示界面13中，当检测到对“文件演示”的图标131的触发操作，即为接收到对“文件演示”的图标131的开启指令时，确认接收到文件窗口开启指令。
在本方案的具体实现过程，接收在白板应用窗口插入文件的操作指令也可以作为文件窗口开启指令。在交互平板11中，白板应用即前文所说具有白板功能的应用程序，在白板应用窗口中，可以支持插入各种其它文件编辑程序对应的第三方文件进行显示，例如在白板应用中插入文档、表格、图片等。在白板应用窗口中检测到插入文件的操作指令时，也可以确认接收到文件窗口开启指令。
需要说明的是，在一次文件窗口开启指令的接收过程中，只能是以上一种具体的实现方式，但是在最终的产品的实现上，具备文件窗口开启指令的两种实现方式，即第一设备中检测到前文任何一种开启操作，均可以确认接收到文件窗口开启指令。而且以上操作可以是通过触摸屏检测到对应图标的单指触控实现，也可以是通过鼠标检测到对应图标的操作实现，后续的操作同样可以由各种的交互设备实现，具体的交互设备实现对应的操作在现有技术中已有实现，后续操作中不再另行强调。
步骤S102：第二设备响应于文件窗口开启指令，将本地存储文件的文件目录发送到服务器，打开文件管理窗口，文件管理窗口显示有二维码，二维码携带有文件目录在服务器的访问地址信息。
响应于文件窗口开启指令，打开如图5所示的文件管理窗口132，文件管理窗口132作为用户对第二设备10中本地存储的文件进行操作的交互界面，其中显示有第二设备10存储的文件对应的文件图标133，这里的本地存储文件主要是指第二设备10保存的用户文件，必要时，也可以根据默认设置或者用户的操作显示系统文件。在图5所示的文件管理窗口132中，显示有5个本地存储文件，即《预研篇》等。在文件管理窗口132中，也可以进行本地存储文件的搜索，实现目标文件的快速定位。
第二设备10在开启文件管理软件时，将本地存储文件的文件目录发送到服务器30，尽快获得服务器30对应返回的访问地址信息，如图5所示，在文件管理窗口132显示本地存储文件的图标时，同时显示根据访问地址信息生成的二维码134。
步骤S103：服务器接收并保存第二设备发送的文件目录，向第二设备发送访问地址信息。
服务器30接收到第二设备10发送的文件目录之后进行保存，并将保存地址对应的访问地址信息发送到第二设备10，以使第二设备10在文件管理窗口132显示文件图标133的同时，显示访问地址信息134对应的二维码134。
可以发现，步骤S103和步骤S102并不是严格的先后执行，步骤S102中的显示文件管理窗口132时，已经实际获得访问地址信息并生成二维码134，即步骤S102中的部分细节实现于步骤S103之后，在此，是以执行步骤的相关设备为参考，将具体执行关联度较高的步骤描述为一个步骤，以上步骤编号不严格表示步骤的先后顺序，主要表示一个设备在实现本方案过程中的整体实施过程。
步骤S104：第一设备通过协作应用识别二维码获取访问地址信息向服务器发起访问请求，并进入文件传输界面，文件传输界面包括文件下载区和文件上传区。
第一设备20中开启并登录协作应用之后，第一设备20的显示页面23如图6所示，此时显示的是协作应用的主页面，其中可以显示有用于实现协作交互过程的信息和各种操作控件，具体协作应用的交互实现不是本方案的实现重点，在此不做过多展开说明。在协作应用的主页面中，跟本方案的实施相关的是如图6所示的扫码控件231。具体的会议参与者在使用个人的终端设备(即第一设备20)参与到会议场景下进行协作交互时，如果有与第二设备10之间的文件传输需求，则通过访问保存于服务器30的文件目录进行文件的发送和接收。在协作中，当检测到对扫码控件231的触发操作时，调用摄像头进行信息获取，具体到本方案中，当识别到服务器30提供的访问地址信息对应生成的二维码时，基于访问地址信息访问服务器30以获取文件目录，显示页面23切换为显示文件传输界面，文件传输界面如图7所示，对应于文件传输的上传操作和下载操作，文件传输界面包括文件下载区域和文件上传区，分别对应触发文件下载操作和文件上传操作。其中文件目录在从服务器30获取之后可以不在文件传输界面直接显示。
如图7所示，“从设备下载”及下方的部分区域对应为文件下载区域，“上传至设备”及下方的部分区域对应为文件上传区域。
在具体实现过程中，第一设备20通过访问地址信息进入文件传输界面之后，因为第一设备20并没有与第二设备10的直接交互，第二设备10的文件目录也已经在服务器30进行保存，因此，第一设备20在文件传输界面进行文件传输相关操作时，第二设备10可以不保持文件管理窗口132的显示状态，而是在文件管理窗口132打开文件，或者打开白板应用起到焦点信息展示的核心作用。
步骤S105：服务器接收第一设备根据访问地址信息发起的访问请求，向第一设备发送文件目录。
如前文所述，步骤S105中服务器30根据访问地址信息发起的访问请求实际在显示文件传输界面之前，本方案中为适应描述的设备维度，服务器30箱第一设备20发送文件目录的步骤在编号上在步骤S105之后，实际执行是在显示文件下载区之前。
步骤S106：第一设备接收在文件下载区生成的下载触发操作。
如图11所示，文件下载区显示有文件下载控件234，当检测到作用于文件下载控件234的触发操作，确认接收到在文件下载区生成的下载触发操作。
步骤S107：第一设备响应于下载触发操作，显示文件下载界面，文件下载界面显示有根据访问请求从服务器获取的文件目录对应的第一图标。
接收到下载触发操作，即对应提供从第二设备10中可以下载的文件信息，具体如图12所示，在文件下载界面中显示第二设备10的文件目录对应的第一图标，文件目录对应于步骤S105，根据访问请求从服务器30获取到，文件目录的中的图标定义为第一图标。在文件下载界面的显示中，第一图标可以缩略图，也可以是文件名，在第一图标中能提供明确的文件信息即可。
步骤S108：第一设备接收对文件下载界面中至少一个第一图标的文件下载操作。
如图12所示，通过对至少一个第一图标或第一图标对应的选择框的操作，确认对应的文件进入选择状态，在接收到对确认控件的操作时，确认接收到完整的文件下载操作。在接收对第一图标的选择操作时，可以同时显示当前已选中的文件数量，例如图12中已选择的文件数量是2。
步骤S109：第一设备响应于文件下载操作，将至少一个第一图标对应的文件下载请求发送到服务器。
步骤S110：服务器接收第一设备根据文件目录发送的文件下载请求。
第一设备20接收到确认的文件下载操作之后，将对应的文件下载请求发送到服务器30，即将待下载的文件信息发送到服务器30。
步骤S111：服务器向第二设备发送文件请求指令，以获取文件下载请求在文件目录中对应的文件。
步骤S112：第二设备接收服务器根据文件目录发送的文件请求指令。
步骤S113：第二设备将文件请求指令对应的本地存储文件上传到服务器。
对于服务器30而言，并没有同步保存第二设备10中的文件。考虑到第一设备20从第一设备10中下载文件的不确定性，也没有必要同步保存第二设备10中的文件，因此，服务器30根据接收到的文件下载请求，向第二设备10发送文件请求指令，以指示第二设备10提供文件下载请求在文件目录中指定的文件，第二设备10接收到文件请求指令后，将对应的本地存储文件上传到服务器30。
步骤S114：服务器将第二设备上传的文件对应于第一设备进行保存。
步骤S115：第一设备从服务器获取文件下载请求对应的文件。
服务器30将第二设备10上传的文件对应于第一设备20进行保存，具体可以是直接保存到第一设备20，也可以是保存到发送文件下载请求的第一设备中当前登录的账号对应的云端空间。具体来说，每个协作应用的账号在服务器都有对应的存储空间，用于保存该账号对应的历史协作信息，历史协作信息包括已经生成的会议预约信息，已有会议生成的文件等。
在协作应用的主页面，显示有信息块，每个信息块分别用于显示一个会议主题对应的历史协作信息。如图6所示的主页面中，显示有两个信息块，分别显示有一个即将进行的会议主题的预约信息和一个历史协作信息生成的两个文件。本方案中的第一设备20获取文件可以是直接获取到对应的存储空间，即服务器30直接将从第二设备10获取到的文件，保存到文件下载请求对应的第一设备10在服务器30中的存储空间。对应在协作应用的主页面添加信息块呈现最新下载的文件信息，并可以从信息块对下载的文件进行打开显示查看。
步骤S116：第一设备接收在文件上传区生成的上传触发操作。
在文件上传区，可以有多个上传控件，分别用于触发不同来源的文件上传。在图7所示的文件传输界面中，文件上传区显示有“应用内文件”、“聊天文件”、“本地相册”和“本地文件”，分别是四个控件对应四种来源的文件。其中，应用内文件指协作应用中产生的文件，通常保存于服务器；聊天文件指各种社交工具中进行文件传输时记录的文件，通常保存于特定的文件夹；本地相册和本地文件主要是下载或第一设备20直接生成的图片文件和非图片文件。以上文件也可能存在交叉，例如某个图片文件既是本地相册中的文件，也可能是聊天文件中的文件。如果接收到在文件上传区中某个控件的触发操作，则确认接收到上传触发操作，并是针对某一类具体来源的文件的上传触发操作。
步骤S117：第一设备响应于上传触发操作，显示文件上传界面，文件上传界面显示有备选上传文件对应的第二图标。
步骤S118：第一设备接收对文件上传界面中至少一个第二图标的文件上传操作。
步骤S119：第一设备响应于文件上传操作，将至少一个第二图标对应的文件数据发送到服务器。
文件上传操作与文件下载操作的交互过程整体相似，区别主要在于文件的传输方向不同，具体可以参考图7-图10，最终完成第一设备20存储于服务器30中对应的存储空间中的文件，另外就是文件上传操作可以有针对各种类型数据的传输进一步准确快速传输。
步骤S120：服务器获取第一设备提供的文件数据，根据文件数据将对应的文件发送到第二设备进行保存。
基于前文服务器30中对应于第一设备20的存储空间，如果第一设备20本身上传的就是历史协作信息中的文件，那么第一设备20不需要上传文件的实质数据，只需要提供文件标识数据，服务器30获取第一设备20提供的文件标识数据；根据文件标识数据从第一设备20对应的存储空间提取文件；将提取到的文件发送到第二设备10进行保存。即在进行应用内文件上传时，接收作用于协作文件控件233的第一上传触发操作；响应于第一上传触发操作，显示文件上传界面，文件上传界面显示有历史协作信息中的文件对应的第二图标；响应于文件上传操作，将至少一个第二图标对应的文件标识数据发送到服务器30。即完成图8中《会议观察清单》的上传操作。
步骤S121：第二设备接收服务器发送的下载文件，将下载文件保存到本地。
服务器30根据直接接收到的文件或者根据文件标识数据获取到的文件，在保存到本地的下载文件对应的图标显示新增标识，直至当次打开的文件管理窗口关闭。具体如图10所示，在图5的基础上，有通过图8中操作新增的文件，并设置有文件的新增标识(new)，直至当次打开的文件管理窗口关闭，即下次打开文件管理窗口时，图10中《会议观察清单》的图标上的“new”不再显示。
服务器30或第一设备20确认文件向第一设备20发送成功后，可以返回文件传输界面，并在文件传输界面显示如图9所示的文件上传结果提示。
通过服务器在第一设备和第二设备之间的数据存储和转发，基于协作应用，用户在使用会议设备的会议场景下，操作第一设备可以独立向第二设备上传文件和从第二设备下载文件，简化了会议场景下文件数据传输的操作过程，提高了第一设备和第二设备间的数据传输效率。
以上是基于第一设备、服务器和第二设备的架构进行文件传输的整体描述，对于其中一端而言，均可以作为独立的产品形态存在，以下对第一设备、服务器和第二设备对应实施文件传输方法的过程分别进行描述。
请参考图14，其是用于第一设备的文件传输方法的方法流程图，如图14所示，该文件传输方法，包括：
步骤S200：通过协作应用识别二维码获取访问地址信息向服务器发起访问请求，并进入文件传输界面，文件传输界面包括文件下载区和文件上传区。
步骤S201：接收在文件下载区生成的下载触发操作。
步骤S202：响应于下载触发操作，显示文件下载界面，文件下载界面显示有根据访问请求从服务器获取的文件目录对应的第一图标。
步骤S203：接收对文件下载界面中至少一个第一图标的文件下载操作。
步骤S204：响应于文件下载操作，将至少一个第一图标对应的文件下载请求发送到服务器。
步骤S205：从服务器获取文件下载请求对应的文件。
步骤S206：接收在文件上传区生成的上传触发操作；
步骤S207：响应于上传触发操作，显示文件上传界面，文件上传界面显示有备选上传文件对应的第二图标。
步骤S208：接收对文件上传界面中至少一个第二图标的文件上传操作；
步骤S209：响应于文件上传操作，将至少一个第二图标对应的文件数据发送到服务器。
在具体实现本方案的过程中，协作应用的主页面显示有信息块，文件上传区显示有协作文件控件，信息块用于显示保存于服务器的历史协作信息；
对应的，步骤S206包括步骤S2061：
步骤S2061：接收作用于协作文件控件的第一上传触发操作；
对应的，步骤S207包括步骤S2071：
步骤S2071：响应于第一上传触发操作，显示文件上传界面，文件上传界面显示有历史协作信息中的文件对应的第二图标；
对应的，步骤S209包括步骤S20191：
响应于文件上传操作，将至少一个第二图标对应的文件标识数据发送到服务器。
在上述实施例的基础上，步骤S205之后，还包括步骤S2051：
步骤S2051：在协作应用的主页面添加用于显示获取到的文件的信息块。
在上述实施例的基础上，步骤S209之后，还包括：
步骤S2091：返回文件传输界面，并在文件传输界面显示文件上传结果提示。
本实施例中各个步骤的具体实现在前文已有详细描述，在此不做重复说明。
请参考图15，其是用于第二设备的文件传输方法的方法流程图，如图15所示，该文件传输方法，包括：
步骤S301：接收文件窗口开启指令。
步骤S302：响应于所述文件窗口开启指令，将本地存储文件的文件目录发送到服务器，打开文件管理窗口，所述文件管理窗口显示有二维码，所述二维码携带有所述文件目录在所述服务器的访问地址信息。
步骤S303：接收所述服务器根据所述文件目录发送的文件请求指令。
步骤S304：将所述文件请求指令对应的本地存储文件上传到所述服务器。
步骤S305：接收所述服务器发送的下载文件，将所述下载文件保存到本地。
在上述实施例的基础上，步骤S301具体为步骤S3011或步骤S3012：
步骤S3011：接收对文件管理软件的图标的开启指令作为文件窗口开启指令。
步骤S3012：接收在白板应用窗口插入文件的操作指令作为文件窗口开启指令。
在上述实施例的基础上，该文件传输方法，还包括：
步骤S306：在保存到本地的下载文件对应的图标显示新增标识，直至当次打开的文件管理窗口关闭。
本实施例中各个步骤的具体实现在前文已有详细描述，在此不做重复说明。
请参考图16，其是用于服务器的文件传输方法的方法流程图，如图16所示，该文件传输方法，包括：
步骤S401：接收并保存第二设备发送的文件目录，向所述第二设备发送访问地址信息。
步骤S402：接收第一设备根据所述访问地址信息发起的访问请求，向所述第一设备发送文件目录。
步骤S403：接收所述第一设备根据所述文件目录发送的文件下载请求。
步骤S404：向所述第二设备发送文件请求指令，以获取所述文件下载请求在所述文件目录中对应的文件。
步骤S405：将所述第二设备上传的文件对应于所述第一设备进行保存。
步骤S406：获取所述第一设备提供的文件数据，根据所述文件数据将对应的文件发送到所述第二设备进行保存。
在上述实施例的基础上，所述服务器设置有用于保存所述第一设备对应的历史协作信息的存储空间；
对应的，步骤S406包括步骤S4061-步骤S4063：
步骤S4061：获取所述第一设备提供的文件标识数据；
步骤S4062：根据所述文件标识数据从所述第一设备对应的存储空间提取文件；
步骤S4063：将提取到的文件发送到所述第二设备进行保存。
在上述实施例的基础上，所述步骤S405包括步骤S4051：
步骤S4051：将所述第二设备上传的文件保存到所述第一设备对应的存储空间。
本实施例中各个步骤的具体实现在前文已有详细描述，在此不做重复说明。
图17为本申请实施例提供的一种文件传输装置的结构示意图。该文件传输装置用于第一设备，参考图17，该文件传输装置包括界面进入单元500、下载操作接收单元510、下载界面显示单元520、下载目标接收单元530、下载请求发送单元540、下载文件获取单元550、上传操作接收单元560、上传界面显示单元570、上传目标接收单元580和上传数据发送单元590。
其中，界面进入单元500，用于通过协作应用识别二维码获取访问地址信息向服务器发起访问请求，并进入文件传输界面，文件传输界面包括文件下载区和文件上传区；下载操作接收单元510，用于接收在文件下载区生成的下载触发操作；下载界面显示单元520，用于响应于下载触发操作，显示文件下载界面，文件下载界面显示有根据访问请求从服务器获取的文件目录对应的第一图标；下载目标接收单元530，用于接收对文件下载界面中至少一个第一图标的文件下载操作；下载请求发送单元540，用于响应于文件下载操作，将至少一个第一图标对应的文件下载请求发送到服务器；下载文件获取单元550，用于从服务器获取文件下载请求对应的文件；上传操作接收单元560，用于接收在文件上传区生成的上传触发操作；上传界面显示单元570，用于响应于上传触发操作，显示文件上传界面，文件上传界面显示有备选上传文件对应的第二图标；上传目标接收单元580，用于接收对文件上传界面中至少一个第二图标的文件上传操作；上传数据发送单元590，用于响应于文件上传操作，将至少一个第二图标对应的文件数据发送到服务器。
在上述实施例的基础上，协作应用的主页面显示有信息块，文件上传区显示有协作文件控件，信息块用于显示保存于服务器的历史协作信息；
对应的，上传操作接收单元560包括：
第一上传操作接收模块，用于接收作用于协作文件控件的第一上传触发操作；
对应的，上传界面显示单元570包括：
第一上传界面显示模块，用于响应于第一上传触发操作，显示文件上传界面，文件上传界面显示有历史协作信息中的文件对应的第二图标；
对应的，上传数据发送单元590包括：
文件标识数据发送模块，用于响应于文件上传操作，将至少一个第二图标对应的文件标识数据发送到服务器。
在上述实施例的基础上，文件传输装置还包括：
信息块添加显示单元，用于在协作应用的主页面添加用于显示获取到的文件的信息块。
在上述实施例的基础山个，文件传输装置还包括：
上传结果显示单元，用于返回文件传输界面，并在文件传输界面显示文件上传结果提示。
图18为本申请实施例提供的一种文件传输装置的结构示意图。该文件传输装置用于第二设备，参考图18，该文件传输装置包括开启指令接收单元610、开启指令响应单元620、文件请求指令接收单元630、文件上传单元640和文件下载单元650。
其中，开启指令接收单元610，用于接收文件窗口开启指令；开启指令响应单元620，用于响应于文件窗口开启指令，将本地存储文件的文件目录发送到服务器，打开文件管理窗口，文件管理窗口显示有二维码，二维码携带有文件目录在服务器的访问地址信息；文件请求指令接收单元630，用于接收服务器根据文件目录发送的文件请求指令；文件上传单元640，用于将文件请求指令对应的本地存储文件上传到服务器；文件下载单元650，用于接收服务器发送的下载文件，将下载文件保存到本地。
在上述实施例的基础上，开启指令接收单元610具体用于：
接收对文件管理软件的图标的开启指令作为文件窗口开启指令；或
接收在白板应用窗口插入文件的操作指令作为文件窗口开启指令。
在上述实施例的基础上，文件传输装置还包括：
标识显示单元，用于在保存到本地的下载文件对应的图标显示新增标识，直至当次打开的文件管理窗口关闭。
图19为本申请实施例提供的一种文件传输装置的结构示意图。该文件传输装置用于服务器，参考图19，该文件传输装置包括文件目录接收单元710、文件目录发送单元720、下载请求接收单元730、请求指令发送单元740、下载请求响应单元750和上传数据获取单元760。
其中，文件目录接收单元710，用于接收并保存第二设备发送的文件目录，向第二设备发送访问地址信息；文件目录发送单元720，用于接收第一设备根据访问地址信息发起的访问请求，向第一设备发送文件目录；下载请求接收单元730，用于接收第一设备根据文件目录发送的文件下载请求；请求指令发送单元740，用于向第二设备发送文件请求指令，以获取文件下载请求在文件目录中对应的文件；下载请求响应单元750，用于将第二设备上传的文件对应于第一设备进行保存；上传数据获取单元760，用于获取第一设备提供的文件数据，根据文件数据将对应的文件发送到第二设备进行保存。
在上述实施例的基础上，服务器设置有用于保存第一设备对应的历史协作信息的存储空间；
对应的，上传数据获取单元760，包括：
标识获取模块，用于获取第一设备提供的文件标识数据；
文件提取模块，用于根据文件标识数据从第一设备对应的存储空间提取文件；
文件发送模块，用于将提取到的文件发送到第二设备进行保存。
在上述实施例的基础上，下载请求响应单元750，包括：
云端保存模块，用于将第二设备上传的文件保存到第一设备对应的存储空间。
本申请实施例提供的文件传输装置包含在电子设备中，且可用于执行上述实施例中提供的对应的文件传输方法，具备相应的功能和有益效果。
值得注意的是，上述文件传输装置的实施例中，所包括的各个单元和模块只是按照功能逻辑进行划分的，但并不局限于上述的划分，只要能够实现相应的功能即可；另外，各功能单元的具体名称也只是为了便于相互区分，并不用于限制本申请的保护范围。
图20为本申请实施例提供的一种电子设备的结构示意图。如图20所示，该电子设备包括处理器810和存储器820，并可以还包括输入装置830、输出装置840以及通信装置850；电子设备中处理器410的数量可以是一个或多个，图20中以一个处理器810为例；电子设备中的处理器810、存储器820、输入装置830、输出装置840以及通信装置850可以通过总线或其他方式连接，图20中以通过总线连接为例。
存储器820作为一种计算机可读存储介质，可用于存储软件程序、计算机可执行程序以及模块，如本申请实施例中的文件传输方法对应的程序指令/模块。处理器810通过运行存储在存储器820中的软件程序、指令以及模块，从而执行电子设备的各种功能应用以及数据处理，即实现上述的文件传输方法。
存储器820可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据电子设备的使用所创建的数据等。此外，存储器820可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器820可进一步包括相对于处理器810远程设置的存储器，这些远程存储器可以通过网络连接至电子设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
输入装置830可用于接收输入的数字或字符信息，以及产生与电子设备的用户设置以及功能控制有关的键信号输入。输出装置840可包括显示屏等显示设备。
上述电子设备包含文件传输装置，可以用于执行任意文件传输方法，具备相应的功能和有益效果。
本申请实施例还提供一种计算机可读存储介质，其上存储有计算机程序，该计算机程序在被处理器执行时用于执行本申请任意实施例中提供的文件传输方法中的相关操作，且具备相应的功能和有益效果。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。
因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。存储器可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。存储器是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括要素的过程、方法、商品或者设备中还存在另外的相同要素。
注意，上述仅为本申请的较佳实施例及所运用技术原理。本领域技术人员会理解，本申请不限于这里的特定实施例，对本领域技术人员来说能够进行各种明显的变化、重新调整和替代而不会脱离本申请的保护范围。因此，虽然通过以上实施例对本申请进行了较为详细的说明，但是本申请不仅仅限于以上实施例，在不脱离本申请构思的情况下，还可以包括更多其他等效实施例，而本申请的范围由所附的权利要求范围决定。

Claims (15)

  1. 文件传输方法，用于第一设备，其中，包括：
    通过协作应用识别二维码获取访问地址信息向服务器发起访问请求，并进入文件传输界面，所述文件传输界面包括文件下载区和文件上传区；
    接收在所述文件下载区生成的下载触发操作；
    响应于所述下载触发操作，显示文件下载界面，所述文件下载界面显示有根据所述访问请求从所述服务器获取的文件目录对应的第一图标；
    接收对所述文件下载界面中至少一个第一图标的文件下载操作；
    响应于所述文件下载操作，将所述至少一个第一图标对应的文件下载请求发送到所述服务器；
    从所述服务器获取所述文件下载请求对应的文件；
    接收在所述文件上传区生成的上传触发操作；
    响应于所述上传触发操作，显示文件上传界面，所述文件上传界面显示有备选上传文件对应的第二图标；
    接收对所述文件上传界面中至少一个第二图标的文件上传操作；
    响应于所述文件上传操作，将所述至少一个第二图标对应的文件数据发送到所述服务器。
  2. 根据权利要求1所述的文件传输方法，其中，所述协作应用的主页面显示有信息块，所述文件上传区显示有协作文件控件，所述信息块用于显示保存于所述服务器的历史协作信息；
    对应的，所述接收在所述文件上传区生成的上传触发操作，包括：
    接收作用于所述协作文件控件的第一上传触发操作；
    所述响应于所述上传触发操作，显示文件上传界面，所述文件上传界面显示有备选上传文件对应的第二图标，包括：
    响应于所述第一上传触发操作，显示文件上传界面，所述文件上传界面显示有所述历史协作信息中的文件对应的第二图标；
    所述响应于所述文件上传操作，将所述至少一个第二图标对应的文件数据发送到所述服务器，包括：
    响应于所述文件上传操作，将所述至少一个第二图标对应的文件标识数据发送到所述服务器。
  3. 根据权利要求2所述的文件传输方法，其中，所述从所述服务器获取所述文件下载请求对应的文件之后，还包括：
    在所述协作应用的主页面添加用于显示获取到的文件的信息块。
  4. 根据权利要求1-3任一项所述的文件传输方法，其中，所述响应于所述文件上传操作，将所述至少一个第二图标对应的文件数据发送到所述服务器之后，还包括：
    返回所述文件传输界面，并在所述文件传输界面显示文件上传结果提示。
  5. 文件传输方法，用于第二设备，其中，包括：
    接收文件窗口开启指令；
    响应于所述文件窗口开启指令，将本地存储文件的文件目录发送到服务器，打开文件管理窗口，所述文件管理窗口显示有二维码，所述二维码携带有所述文件目录在所述服务器的访问地址信息；
    接收所述服务器根据所述文件目录发送的文件请求指令；
    将所述文件请求指令对应的本地存储文件上传到所述服务器；
    接收所述服务器发送的下载文件，将所述下载文件保存到本地。
  6. 根据权利要求5所述的文件传输方法，其中，所述接收文件窗口开启指令为：
    接收对文件管理软件的图标的开启指令作为文件窗口开启指令；或
    接收在白板应用窗口插入文件的操作指令作为文件窗口开启指令。
  7. 根据权利要求5所述的文件传输方法，其中，还包括：
    在保存到本地的下载文件对应的图标显示新增标识，直至当次打开的文件管理窗口关闭。
  8. 文件传输方法，用于服务器，其中，包括：
    接收并保存第二设备发送的文件目录，向所述第二设备发送访问地址信息；
    接收第一设备根据所述访问地址信息发起的访问请求，向所述第一设备发送文件目录；
    接收所述第一设备根据所述文件目录发送的文件下载请求；
    向所述第二设备发送文件请求指令，以获取所述文件下载请求在所述文件目录中对应的文件；
    将所述第二设备上传的文件对应于所述第一设备进行保存；
    获取所述第一设备提供的文件数据，根据所述文件数据将对应的文件发送到所述第二设备进行保存。
  9. 根据权利要求8所述的文件传输方法，其中，所述服务器设置有用于保存所述第一设备对应的历史协作信息的存储空间；
    对应的，所述获取所述第一设备提供的文件数据，根据所述文件数据将对应的文件发送到所述第二设备进行保存，包括：
    获取所述第一设备提供的文件标识数据；
    根据所述文件标识数据从所述第一设备对应的存储空间提取文件；
    将提取到的文件发送到所述第二设备进行保存。
  10. 根据权利要求9所述的文件传输方法，其中，所述将所述第二设备上传的文件对应于所述第一设备进行保存，包括：
    将所述第二设备上传的文件保存到所述第一设备对应的存储空间。
  11. 文件传输装置，用于第一设备，其中，包括：
    界面进入单元，用于通过协作应用识别二维码获取访问地址信息向服务器发起访问请求，并进入文件传输界面，所述文件传输界面包括文件下载区和文件上传区；
    下载操作接收单元，用于接收在所述文件下载区生成的下载触发操作；
    下载界面显示单元，用于响应于所述下载触发操作，显示文件下载界面，所述文件下载界面显示有根据所述访问请求从所述服务器获取的文件目录对应的第一图标；
    下载目标接收单元，用于接收对所述文件下载界面中至少一个第一图标的文件下载操作；
    下载请求发送单元，用于响应于所述文件下载操作，将所述至少一个第一图标对应的文件下载请求发送到所述服务器；
    下载文件获取单元，用于从所述服务器获取所述文件下载请求对应的文件；
    上传操作接收单元，用于接收在所述文件上传区生成的上传触发操作；
    上传界面显示单元，用于响应于所述上传触发操作，显示文件上传界面，所述文件上传界面显示有备选上传文件对应的第二图标；
    上传目标接收单元，用于接收对所述文件上传界面中至少一个第二图标的文件上传操作；
    上传数据发送单元，用于响应于所述文件上传操作，将所述至少一个第二图标对应的文件数据发送到所述服务器。
  12. 文件传输装置，用于第二设备，其中，包括：
    开启指令接收单元，用于接收文件窗口开启指令；
    开启指令响应单元，用于响应于所述文件窗口开启指令，将本地存储文件的文件目录发送到服务器，打开文件管理窗口，所述文件管理窗口显示有二维码，所述二维码携带有所述文件目录在所述服务器的访问地址信息；
    文件请求指令接收单元，用于接收所述服务器根据所述文件目录发送的文件请求指令；
    文件上传单元，用于将所述文件请求指令对应的本地存储文件上传到所述服务器；
    文件下载单元，用于接收所述服务器发送的下载文件，将所述下载文件保存到本地。
  13. 文件传输装置，用于服务器，其中，包括：
    文件目录接收单元，用于接收并保存第二设备发送的文件目录，向所述第二设备发送访问地址信息；
    文件目录发送单元，用于接收第一设备根据所述访问地址信息发起的访问请求，向所述第一设备发送文件目录；
    下载请求接收单元，用于接收所述第一设备根据所述文件目录发送的文件下载请求；
    请求指令发送单元，用于向所述第二设备发送文件请求指令，以获取所述文件下载请求在所述文件目录中对应的文件；
    下载请求响应单元，用于将所述第二设备上传的文件对应于所述第一设备进行保存；
    上传数据获取单元，用于获取所述第一设备提供的文件数据，根据所述文件数据将对应的文件发送到所述第二设备进行保存。
  14. 一种电子设备，其中，包括：
    一个或多个处理器；
    存储器，用于存储一个或多个计算机程序；
    当所述一个或多个计算机程序被所述一个或多个处理器执行，使得所述电子设备实现如权利要求1-10任一所述的文件传输方法。
  15. 一种计算机可读存储介质，其上存储有计算机程序，其中，该计算机程序被处理器执行时实现如权利要求1-10任一所述的文件传输方法。
PCT/CN2023/094128 2022-04-21 2023-05-15 文件传输方法、装置、电子设备和存储介质 WO2023202721A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210423879.5 2022-04-21
CN202210423879.5A CN116980391A (zh) 2022-04-21 2022-04-21 文件传输方法、装置、电子设备和存储介质

Publications (1)

Publication Number Publication Date
WO2023202721A1 true WO2023202721A1 (zh) 2023-10-26

Family

ID=88419307

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/094128 WO2023202721A1 (zh) 2022-04-21 2023-05-15 文件传输方法、装置、电子设备和存储介质

Country Status (2)

Country Link
CN (1) CN116980391A (zh)
WO (1) WO2023202721A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116016496A (zh) * 2023-01-30 2023-04-25 中国联合网络通信集团有限公司 实时文件同步方法、装置、设备和介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104023021A (zh) * 2014-06-13 2014-09-03 珠海市君天电子科技有限公司 一种文件传输方法及装置
CN106254553A (zh) * 2016-09-30 2016-12-21 北京奇虎科技有限公司 一种文件传输处理方法和装置
CN111368173A (zh) * 2020-03-05 2020-07-03 五八有限公司 文件传输方法、装置、电子设备及可读存储介质
CN112399212A (zh) * 2019-08-18 2021-02-23 海信视像科技股份有限公司 显示设备、分享文件的方法和服务器

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104023021A (zh) * 2014-06-13 2014-09-03 珠海市君天电子科技有限公司 一种文件传输方法及装置
CN106254553A (zh) * 2016-09-30 2016-12-21 北京奇虎科技有限公司 一种文件传输处理方法和装置
CN112399212A (zh) * 2019-08-18 2021-02-23 海信视像科技股份有限公司 显示设备、分享文件的方法和服务器
CN111368173A (zh) * 2020-03-05 2020-07-03 五八有限公司 文件传输方法、装置、电子设备及可读存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116016496A (zh) * 2023-01-30 2023-04-25 中国联合网络通信集团有限公司 实时文件同步方法、装置、设备和介质

Also Published As

Publication number Publication date
CN116980391A (zh) 2023-10-31

Similar Documents

Publication Publication Date Title
CN107659416B (zh) 一种会议记录分享的方法、装置、会议终端和存储介质
US10326715B2 (en) System and method for updating information in an instant messaging application
CN107750466B (zh) 使用经同步的提示信号配对附近设备
EP2891296B1 (en) Systems and methods for sharing data among multiple end user devices
EP2901661B1 (en) Terminal and method for transmitting and receiving data
WO2019024867A1 (zh) 在视频页面中交互消息的方法、计算设备及存储介质
US9584566B2 (en) Method and system for synchronizing duplicated contents in multiple terminals
US20160127282A1 (en) System and method of adding an anonymous participant to a chat session
US10496354B2 (en) Terminal device, screen sharing method, and screen sharing system
US10225215B2 (en) Method and system for caching input content
US11960788B2 (en) Systems and methods for changing language during live presentation
CN107864358B (zh) 一种视频通话中的共享对象操作方法
WO2019019535A1 (zh) 数据发送、转发和传输的方法及装置
MX2013001676A (es) Protocolo de enlace multimedia/voz e interfaces de usuario relacionadas.
US20150326620A1 (en) Media presentation in a virtual shared space
WO2019085184A1 (zh) 会议板书文件的管理方法、装置、显示装置及存储介质
CN110019058B (zh) 文件操作的共享方法和装置
CN111695070A (zh) 一种在线内容显示控制方法、装置、电子设备和存储介质
WO2023202721A1 (zh) 文件传输方法、装置、电子设备和存储介质
US20230017859A1 (en) Meeting control method and apparatus, device, and medium
WO2014176896A1 (en) System and method for updating information in an instant messaging application
WO2023131290A1 (zh) 信息交互方法、装置、电子设备及介质
CN114422460A (zh) 一种在即时通信应用中建立同屏交流分享的方法、系统
CN112347401A (zh) 房屋同屏带看方法、系统、装置及计算机可读存储介质
KR20200020656A (ko) 대화방 기반의 업무관리 장치, 방법 및 이를 저장하는 기록매체

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23791373

Country of ref document: EP

Kind code of ref document: A1