CN112261624B

CN112261624B - Method, electronic equipment and system for transmitting file in application

Info

Publication number: CN112261624B
Application number: CN202011003508.9A
Authority: CN
Inventors: 毕岩
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-12-31
Filing date: 2019-12-31
Publication date: 2022-01-11
Anticipated expiration: 2039-12-31
Also published as: WO2021135734A1; CN112261624A; CN113068156A

Abstract

The embodiment of the application discloses a method, electronic equipment and a system for transmitting files in an application without flow. By using the method, the electronic equipment can rapidly share the file to other nearby equipment in the application program through the Wi-Fi direct communication connection established between the electronic equipment and other equipment. By implementing the technical scheme provided by the embodiment of the application, the electronic equipment can quickly transmit the file to other surrounding equipment in application, the use experience of a user is optimized, the cellular data flow consumed by the electronic equipment can be saved, the load of a server is reduced, and in addition, the size of the file shared by the electronic equipment is not limited.

Description

Method, electronic equipment and system for transmitting file in application

Technical Field

The present application relates to the field of near field communication and terminal technologies, and in particular, to a method, an electronic device, and a system for transmitting a file in an application.

Background

With the development of wireless communication technology, electronic devices such as smart phones and tablet computers start supporting users to share files such as pictures, videos, documents and music through instant messaging (APP), so that the use experience of the users is improved.

Currently, when a user shares a file through an instant messaging application, an electronic device first transmits the file to a server through a network (e.g., a cellular network, a Wireless Fidelity (Wi-Fi), etc.), and then the server forwards the file to an opposite device. Such a way of sharing files has the following disadvantages:

1. the mode depends on the communication connection between the electronic equipment and the server, and the efficiency of file transmission is influenced when the network condition is poor.

2. Because files need to be transmitted through a network, users can only share smaller files under normal conditions, more time is needed when larger files are shared, and user experience is poor.

3. When more users share files by using the instant messaging application, the load of the server is overlarge.

How to meet the requirements of users on quick transmission, large file transmission and the like when the users share files through instant messaging application is a current research direction, and better use experience is provided for the users.

Disclosure of Invention

The embodiment of the application provides a method, electronic equipment and a system for transmitting files without flow in application, so that the electronic equipment can quickly transmit the files to other surrounding equipment in the application, the use experience of a user is optimized, and the file transmission process can be carried out under the condition of no network.

In a first aspect, an embodiment of the present application provides a method for transmitting a file in an application, which is applied to a first device. The method comprises the following steps: the first device displays a first user interface, the first user interface including: communication records of a first user and a second user in a first application program and a first operation option; in response to a first operation received on the first operation option, the first device displays a second user interface, wherein the second user interface comprises a first identifier and a second identifier, the first identifier corresponds to a first file stored in the first device, and the second identifier corresponds to a second file stored in the first device; the first equipment receives a second operation on the first identifier and selects the first file; responding to a third operation of sharing the first file, and sending the first file to the second equipment by the first equipment through a Wi-Fi direct communication connection between the first equipment and the second equipment; the first user logs in the first application program on the first device, and the second user logs in the first application program on the second device.

Implementing the method of the first aspect, the electronic device may quickly share files to other devices nearby in the application program through a Wi-Fi direct communication connection with the other devices. The method does not depend on a server, and can support the user to share the file no matter whether the electronic equipment and the server have communication connection or not and whether the communication connection is good or not. The method can optimize the use experience of the user, save the cellular data flow consumed by the electronic equipment and reduce the load of the server. In addition, the size of the file which can be shared by the electronic equipment is not limited by connecting the file sharing mode through Wi-Fi direct communication, namely, the method can support the electronic equipment to share a larger file to other surrounding equipment. The process of sharing files using applications on the electronic device is thus intuitive, simple and fast for the user.

In conjunction with the first aspect, in some embodiments, the first application may be an instant messaging type application, a mailbox type application, or the like. The first user interface may be an interface displayed when the electronic device runs the first application.

In conjunction with the first aspect, in some embodiments, the first file or the second file may include, but is not limited to: pictures, audio, video, documents, links, and the like.

In conjunction with the first aspect, in some embodiments, the first device may discover and determine the second device via bluetooth. The Bluetooth is used, so that the first equipment can be ensured to quickly discover and determine the second equipment, and the file sharing efficiency is improved. In one embodiment, the first device may discover one or more devices via bluetooth after displaying the first user interface and determine the second device among the one or more discovered devices. In another embodiment, the first device may discover one or more devices through bluetooth in response to the first operation and determine the second device among the one or more discovered devices.

In some embodiments, a first device may receive a bluetooth broadcast packet sent by one or more devices, where the bluetooth broadcast packet includes a user identifier, and a user corresponding to the user identifier logs in the first application program on the device. The one or more devices are the one or more devices discovered by the first device. The first device may determine, as the second device, a device that transmits the first identifier from among the one or more devices; the first identity is a user identity of the second user. In this way, the first device may determine, among the one or more discovered devices, a device to be used by the second user when logging into the first application.

In some embodiments, the first device may perform a procedure of establishing a Wi-Fi direct communication connection with the second device after determining the second device and before transmitting the first file to the second device.

In some embodiments, the first device may perform a procedure of establishing a bluetooth communication connection with the second device before performing a procedure of establishing a Wi-Fi direct communication connection with the second device, and transmit a service set identification SSID and a password to the second device through the established bluetooth communication connection; the SSID and the password are used for the second device to perform a process of establishing the Wi-Fi direct communication connection with the first device. That is to say, first equipment can establish bluetooth communication connection with second equipment earlier, establish Wi-Fi directly communication connection based on this bluetooth communication connection and second equipment again, can establish this Wi-Fi directly communication connection rapidly like this to improve the efficiency of sharing file.

With reference to the first aspect, in some embodiments, the second user interface further includes a second operation option, and the third operation includes: and the operation received on the second operation option after the first file is selected. In an embodiment, the first device may display the second operation option on the second user interface after selecting the first file, so that the user may be prompted to share the first file, and a better use experience is provided for the user. In another embodiment, the first device may display the second operation option on the second user interface simultaneously with the display of the second user interface.

With reference to the first aspect, in some embodiments, after the first device sends the first file to the second device, a third user interface may be further displayed, where the third user interface includes a prompt message, and the prompt message is used to indicate a transmission status of the first file. The transmission status of the first file may include, but is not limited to: the first file is waiting to be received by the second device, the first file is being transferred to the second device, the first file is not successfully transferred to the second device, the first file is successfully transferred to the second device, and so on. Therefore, the user can intuitively know the transmission state of the first file, and better use experience is provided for the user. In some embodiments, the third user interface may further include a record of communications of the first user and the second user in the first application. With reference to the first aspect, in some embodiments, the first device may send a file sharing request to the second device before sending the first file to the second device over the Wi-Fi direct communication connection with the second device; and sending the first file to the second device through the Wi-Fi direct communication connection with the second device on the condition that a sharing request response sent by the second device in response to the file sharing request is received. Therefore, the first file can be sent to the second device under the condition of obtaining the consent of the second user, and the use experience of the user can be ensured.

In some embodiments, the file sharing request may be sent by a server. Specifically, the first device may send a file sharing request to the server, so that the server sends the file sharing request to the second device. The server provides a service for the first application. The server sends the file sharing request, so that the server can acquire and record the file transmission event between the first device and the second device.

With reference to the first aspect, in some embodiments, before the first device sends the first file to the second device, a fourth operation for starting the first communication service and the second communication service may also be detected; in response to the fourth operation, the first device turns on the first communication service and the second communication service. The first communication service is used for the first device to discover and determine the second device through Bluetooth, and the second communication service is used for the first device to send the first file to the second device through the Wi-Fi direct communication connection. In one embodiment, the first communication service is a bluetooth communication service and the second communication service is a WLAN communication service.

In a second aspect, an embodiment of the present application provides a method for transmitting a file in an application. The method of the second aspect differs from the method of the first aspect in that the user selects the application first and then selects the file, whereas the user selects the file first and then selects the application in the method of the second aspect.

The method of the second aspect is applied to a first device, and may include: the first device displays a fourth user interface, wherein the fourth user interface comprises a third identifier and a fourth identifier, the third identifier corresponds to a third file stored in the first device, and the fourth identifier corresponds to a fourth file stored in the first device; receiving a fifth operation on the third identifier, and selecting the third file; responding to a sixth operation of sharing the third file, and displaying options of one or more application programs; the options of the one or more applications include an option of a first application; in response to a seventh operation received on the option of the first application, displaying a fifth user interface, the fifth user interface including: an option for one or more contacts of the first user in the first application; the one or more contacts comprise a second user; in response to an eighth operation received on the option of the second user, the first device sends a third file to the second device through a Wi-Fi direct communication connection with the second device; the first user logs in the first application program on the first device, and the second user logs in the first application program on the second device.

Implementing the method of the second aspect, the electronic device may quickly share files to other devices nearby in the application program through a Wi-Fi direct communication connection with the other devices. The method does not depend on a server, and can support the user to share the file no matter whether the electronic equipment and the server have communication connection or not and whether the communication connection is good or not. The method can optimize the use experience of the user, save the cellular data flow consumed by the electronic equipment and reduce the load of the server. In addition, the size of the file which can be shared by the electronic equipment is not limited by connecting the file sharing mode through Wi-Fi direct communication, namely, the method can support the electronic equipment to share a larger file to other surrounding equipment. The process of sharing files using applications on the electronic device is thus intuitive, simple and fast for the user.

The first application mentioned in the second aspect may refer to the relevant description in the first aspect.

In conjunction with the second aspect, in some embodiments, the third file or the fourth file may include, but is not limited to: pictures, audio, video, documents, links, and the like.

In conjunction with the second aspect, in some embodiments, the first device may discover and determine the second device via bluetooth. The Bluetooth is used, so that the first equipment can be ensured to quickly discover and determine the second equipment, and the file sharing efficiency is improved. In one embodiment, the first device may discover one or more devices through bluetooth after receiving a sixth operation of sharing the third file, and determine the second device among the one or more discovered devices. In another embodiment, the first device may discover one or more devices through bluetooth in response to the eighth operation, and determine the second device among the one or more discovered devices.

In some embodiments, the first device may perform a procedure of establishing a Wi-Fi direct communication connection with the second device after determining the second device and before transmitting the third file to the second device.

With reference to the second aspect, in some embodiments, in response to the sixth operation of sharing the third file, the first device may display one or more application programs with any one of the following options:

1. and all the application programs which are installed on the sending end and can be used for sharing the file respectively correspond to options.

2. In the application programs which are installed on the sending terminal and can be used for sharing the files, the options corresponding to the application programs which can share the files through the 'hashare' are available at present.

In combination with the second aspect, in some embodiments, the first device may further display the sixth user interface in response to an eighth operation received on the option of the second user, the sixth user interface including: the communication records of the first user and the second user in the first application program and prompt information, wherein the prompt information is used for indicating the transmission state of the third file. The transmission status of the third file may include, but is not limited to: a third file is waiting to be received by the second device, the third file is being transferred to the second device, the third file is not successfully transferred to the second device, the third file is successfully transferred to the second device, and so on. Therefore, the user can intuitively know the transmission state of the third file, and better use experience is provided for the user.

In conjunction with the second aspect, in some embodiments, a third operational option may be included in the fourth user interface. The sixth operation may include an operation received by the first device on the third operation option. In some embodiments, the first device may display the third operation option after selecting the third file, so that the user may be prompted to share the third file, and a better use experience is provided for the user. In another embodiment, the first device may display the third operational option on the fourth user interface simultaneously with the display of the fourth user interface.

In combination with the second aspect, in some embodiments, the first device may send a file sharing request to the second device before sending the third file to the second device over the Wi-Fi direct communication connection with the second device; and sending the third file to the second device through the Wi-Fi direct communication connection with the second device on the condition that a sharing request response sent by the second device in response to the file sharing request is received. Therefore, the third file can be sent to the second equipment under the condition of obtaining the consent of the second user, and the use experience of the user can be ensured.

With reference to the second aspect, in some embodiments, before the first device sends the third file to the second device, a fourth operation for starting the first communication service and the second communication service may also be detected; in response to the fourth operation, the first device turns on the first communication service and the second communication service. The first communication service is used for the first device to discover and determine the second device through Bluetooth, and the second communication service is used for the first device to send the third file to the second device through the Wi-Fi direct communication connection. In one embodiment, the first communication service is a bluetooth communication service and the second communication service is a WLAN communication service.

In a third aspect, an embodiment of the present application provides an electronic device. The electronic device includes one or more processors, memory; the memory is coupled to the one or more processors and is configured to store computer program code, the computer program code comprising computer instructions that are invoked by the one or more processors to cause the electronic device to perform the first aspect or the method of any one of the implementation manners of the first aspect.

In a fourth aspect, an embodiment of the present application provides an electronic device. The electronic device includes one or more processors, memory; the memory is coupled to the one or more processors and is configured to store computer program code comprising computer instructions that are invoked by the one or more processors to cause the electronic device to perform the method of the second aspect or any one of the embodiments of the second aspect.

In a fifth aspect, embodiments of the present application provide a computer program product including instructions, which, when run on an electronic device, cause the electronic device to perform the method described in the first aspect and any possible implementation manner of the first aspect.

In a sixth aspect, the present application provides a computer program product containing instructions, which when run on an electronic device, causes the electronic device to perform the method described in the second aspect and any possible implementation manner of the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which includes instructions that, when executed on an electronic device, cause the electronic device to perform the method described in the first aspect and any possible implementation manner of the first aspect.

In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which includes instructions that, when executed on an electronic device, cause the electronic device to perform a method as described in the second aspect and any possible implementation manner of the second aspect.

In a ninth aspect, an embodiment of the present application provides a system for transferring a file in an application, where the system includes: a first device and a second device. Wherein the first device may be the electronic device described in the third aspect above. The second device is used for receiving the first file through a Wi-Fi direct communication connection with the first device.

In a tenth aspect, an embodiment of the present application provides a system for transferring a file in an application, where the system includes: a first device and a second device. Wherein the first device may be the electronic device described in the fourth aspect above. The second device is used for receiving a third file through a Wi-Fi direct communication connection with the first device.

With reference to the ninth aspect or the tenth aspect, in some embodiments, the second device is further configured to receive a file sharing request sent by the first device before receiving the first file or the third file; responding to the file sharing request, and displaying a notification window which is used for inquiring whether a user receives the first file or the third file; the notification window comprises a fourth operation option, and the second device receives the first file or the third file in response to a ninth operation received on the fourth operation option.

With reference to the ninth aspect or the tenth aspect, in some embodiments, the second device is further configured to, before receiving the first file or the third file, send a bluetooth broadcast packet, where the bluetooth broadcast packet includes a user identifier, and a user corresponding to the user identifier logs in the first application program on the second device. The bluetooth broadcast packet is used for the first device to discover and determine the second device.

With reference to the ninth or tenth aspect, in some embodiments, the second device is further configured to perform a procedure of establishing a Wi-Fi direct communication connection with the first device before receiving the first file or the third file.

With reference to the ninth or tenth aspect, in some embodiments, the second device is further configured to display a seventh user interface after receiving the first file or the third file, the seventh user interface including: and the communication records and prompt information of the second user and the first user in the first application program. The prompt message is used for indicating the transmission state of the first file or the third file. The transmission status of the first file or the third file may refer to the related description of the first aspect and the second aspect.

By implementing the technical scheme provided by the embodiment of the application, the electronic equipment can rapidly share the file to other nearby equipment through Wi-Fi direct communication connection between the electronic equipment and other equipment in the application program. The technical scheme has the following beneficial effects: the electronic equipment can quickly and quickly transmit the file to other surrounding equipment in application, so that the use experience of a user is optimized; no matter whether communication connection exists between the electronic equipment and the server or not and whether the communication connection is good or not, the electronic equipment can share files to other equipment, so that cellular data flow consumed by the electronic equipment can be saved, and the load of the server is reduced; the size of the file shared by the electronic device is not limited, that is, the electronic device can share a larger file to other surrounding devices.

Drawings

Fig. 1A is a schematic diagram of a structure of an electronic device provided in an embodiment of the present application;

fig. 1B is a schematic diagram of a software structure of an electronic device according to an embodiment of the present application;

FIG. 2A is a user interface for displaying an application installed on an electronic device according to an embodiment of the present disclosure;

fig. 2B is a schematic diagram of opening a "share" provided in an embodiment of the present application;

3A-3I are a series of user interfaces provided by an embodiment of the present application on a sender in scenario I;

4A-4F are another series of user interfaces provided by embodiments of the present application on the transmitting end in scenario I;

fig. 5A to fig. 5I are still another series of user interfaces provided by the embodiment of the present application on the transmitting end in scenario one;

fig. 6A to 6H are a series of user interfaces on the transmitting end in scenario two according to the embodiment of the present application;

fig. 7A to 7E are another series of user interfaces on the transmitting end in scenario two according to the embodiment of the present application;

fig. 8A to 8I are still another series of user interfaces on the transmitting end in scenario two according to the embodiment of the present application;

fig. 9A to 9D are a series of user interfaces on the transmitting end in scenario three according to the present embodiment;

fig. 10A is a schematic block diagram of a communication system according to an embodiment of the present application;

fig. 10B is a schematic flowchart of a method for transmitting a file in an application in scenario one according to an embodiment of the present application;

fig. 10C is a schematic flowchart of a method for transmitting a file in an application in scenario two according to the embodiment of the present application;

fig. 11 is an architecture of a ShareKit service provided by an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

In the description of the embodiments herein, "/" means "or" unless otherwise specified, for example, a/B may mean a or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more than two.

In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the embodiments of the present application, "a plurality" means two or more unless otherwise specified.

The following embodiments of the application provide a method, an electronic device and a system for transmitting a file in an application, so that a user can quickly share the file to other nearby users through the application installed on the electronic device. The method does not depend on a server, the file transmission process can be carried out under the condition of no network, and the user can share the file no matter whether the communication connection exists between the electronic equipment and the server or not and whether the communication connection is good or not. The method supports the electronic equipment to quickly transmit the file to other surrounding equipment in application, optimizes the use experience of a user, and can also save cellular data traffic consumed by the electronic equipment and reduce the load of the server. Moreover, by using the method, the size of the file which can be shared by the electronic device is not limited, that is, the method can support the electronic device to share a larger file to other surrounding devices. The process of sharing files using applications on the electronic device is thus intuitive, simple and fast for the user.

Here, the communication connection between the electronic device and the server may include, but is not limited to, a connection based on a cellular mobile communication network such as 3G, LTE, 5G, etc., a Wide Area Network (WAN), a Local Area Network (LAN), and the like.

In the following embodiments of the present application, the electronic device may share files to other devices around in the following applications: instant messaging type applications, mailbox type applications, and the like.

In the following embodiments of the present application, the file shared by the electronic device to other surrounding devices may include, but is not limited to: pictures, audio, video, documents, links, and the like. The files may be acquired by the electronic device itself, such as pictures and/or videos captured by a camera, documents generated by capturing texts input by a user by using a display screen, and the like, or may be acquired by the electronic device from other devices such as a server through a network.

In the following embodiments of the present application, under a condition that a "hide" of an electronic device such as a smart phone is turned on, the electronic device may discover other devices such as a nearby mobile phone and a tablet computer. If the user wants to share the file in the application to other contacts in the application, the electronic device can send the file selected by the user to the other found devices, another user can log in the application on the other devices, and the other user is the contact of the current user. In the embodiment of the present application, an electronic device used when a certain user logs in to an application may be referred to as an associated device of the user. Specific implementation of how the electronic device discovers other devices nearby, determines a device associated with the contact in the other devices nearby, and sends a file will be described in detail in the following embodiments, and details are not repeated here.

In the following embodiments of the present application, a "share" is a service or function provided by an electronic device, and may support the electronic device to send a file to other devices nearby.

The process of the electronic device sending the file to other devices through the "share" does not completely pass through the server.

In some embodiments, a "hishare" may support the electronic device to transfer files to other devices nearby via one or more of Bluetooth (BT), Near Field Communication (NFC), wireless fidelity direct (Wi-Fi direct) (also known as wireless fidelity peer-to-peer (Wi-Fi p2p)), Wi-Fi software access point (software ap), and the like. In other embodiments, a "share" may support the electronic device transmitting data over a Local Area Network (LAN) to other devices within the same LAN as the electronic device. Devices that are within the same local area network as the electronic device may also be other devices in the vicinity of the electronic device. In still other embodiments, "hishare" may support the electronic device to transmit the file to the server through cellular mobile communication technology such as 3G, LTE, 5G, or Wide Area Network (WAN) technology, and the server forwards the file to other devices nearby.

It will be appreciated that some or all of the several embodiments described above may be implemented in combination. For example, "hashare" may support an electronic device to transmit files to other devices nearby using both Wi-Fi direct (e.g., Wi-Fi p2p) and cellular mobile communication technologies.

The nearby other devices refer to devices discovered by the electronic device through one or more technologies of NFC, Bluetooth, Wi-Fi direct (such as Wi-Fi p2p), Wi-Fi softAP and Wi-Fi LAN.

In the following embodiments of the present application, the turning on "share" may include: and starting one or more of a Bluetooth module, an NFC module and a WLAN module of the electronic equipment. In some embodiments, after the functional module is turned on, the electronic device may discover devices in the vicinity of the electronic device through one or more technologies of NFC, bluetooth, Wi-Fi direct (e.g., Wi-Fi p2p), Wi-Fi softAP, and Wi-Fi LAN.

In a specific embodiment, if the electronic device discovers other devices nearby the electronic device and transmits the file to the other devices nearby through one or more technologies of NFC, bluetooth, Wi-Fi direct (such as Wi-Fi p2p), Wi-Fi softAP, and Wi-Fi LAN after turning on the "hishare", the process of the electronic device transmitting the file to the other devices nearby in the application may not depend on the communication connection between the electronic device and the server since the technologies of bluetooth, Wi-Fi direct (such as Wi-Fi p2p), Wi-Fi softAP, and Wi-Fi LAN support that the electronic device does not need to communicate through the server. Therefore, the electronic equipment can quickly transmit the file to other surrounding equipment in application and can transmit a larger file to other surrounding equipment, so that the use experience of a user is optimized, the cellular data flow consumed by the electronic equipment can be saved, and the load of a server is reduced. For example, in one embodiment, the "hashare" supports the electronic device to first discover surrounding devices via bluetooth and determine devices associated with a contact among the devices, and then send a file selected by the user to the devices associated with the contact via Wi-Fi P2P. In this way, the electronic device may quickly and conveniently send files to the contact-associated device via Wi-Fi P2P by quickly discovering surrounding devices via BT.

It is to be understood that "share" is only a word used in this embodiment, and its representative meaning has been described in this embodiment, and its name does not set any limit to this embodiment. In addition, in some other embodiments of the present application, "Share" may also be referred to as other terms, such as "short-distance sharing", "fast sharing", "Moment Share", and the like.

In order to better describe the method for transmitting a file in an application provided by the embodiment of the present application, an exemplary electronic device provided by the embodiment of the present application is first described below.

In the embodiment of the present application, the electronic device may be a portable terminal device, such as a mobile phone, a tablet computer, a wearable device, and the like, which carries an iOS, Android, Microsoft, or other operating systems, and may also be a non-portable terminal device, such as a Laptop computer (Laptop) with a touch-sensitive surface or a touch panel, a desktop computer with a touch-sensitive surface or a touch panel, and the like.

Fig. 1A shows a schematic structural diagram of an electronic device 100.

The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identification Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present application does not specifically limit the electronic device 100.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

The controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

The charging management module 140 is configured to receive charging input from a charger. The charger may be a wireless charger or a wired charger.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140, and supplies power to the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The

antennas

1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including 2G/3G/4G/5G wireless communication applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide a solution for wireless communication applied to the electronic device 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), bluetooth (bluetooth, BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves. Illustratively, the wireless communication module 160 may include a bluetooth module, an NFC module, a WLAN module, and the like. The Bluetooth (BT) module may provide solutions including one or more of classic Bluetooth (Bluetooth 2.1) or Bluetooth Low Energy (BLE) Bluetooth communication. The WLAN module may provide solutions that include one or more of Wi-Fi direct, Wi-Fi LAN, or Wi-Fi softAP WLAN communications.

In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150 and antenna 2 is coupled to wireless communication module 160 so that electronic device 100 can communicate with networks and other devices through wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

In the embodiment of the present application, the Bluetooth (BT) module and the WLAN module included in the wireless communication module 160 of the electronic device 100 may transmit signals to detect or scan other devices nearby, and may also listen to signals transmitted by other devices, so as to discover the nearby devices by using wireless communication technologies such as bluetooth or WLAN, establish wireless communication connection with the nearby devices, and transmit files to the nearby devices through the connection.

The solution of wireless communication provided by the mobile communication module 150 of the electronic device 100 may enable the transmitting end to communicate with a device (e.g., a server) in the network, and the solution of WLAN wireless communication provided by the wireless communication module 160 may also enable the electronic device 100 to communicate with a device (e.g., a server) in the network. The electronic device 100 may communicate with other nearby devices (e.g., the receiving end 102) through a device (e.g., a server) in the network, for example, a sending end may first transmit a file to the device in the network, and then the device in the network transmits the file to the other nearby devices.

The processor 110 of the electronic device 100 may be configured to generate signals, such as a probe request, a bluetooth broadcast signal, a beacon signal, etc., transmitted by the wireless communication module 160 and the mobile communication module 150. The processor 110 of the electronic device 100 may also be configured to interpret signals received by the wireless communication module 160, the mobile communication module 150, such as probe responses, and the like.

The electronic device 100 implements display functions via the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, with N being a positive integer greater than 1.

The electronic device 100 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display 194, the application processor, and the like.

The ISP is used to process the data fed back by the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. Applications such as intelligent recognition of the electronic device 100 can be realized through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the memory capability of the electronic device 100.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The storage data area may store data (such as audio data, phone book, etc.) created during use of the electronic device 100, and the like.

The electronic device 100 may implement audio functions via the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals.

The headphone interface 170D is used to connect a wired headphone.

The pressure sensor 180A is used for sensing a pressure signal, and converting the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A can be of a wide variety, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a sensor comprising at least two parallel plates having an electrically conductive material. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic apparatus 100 may also calculate the touched position from the detection signal of the pressure sensor 180A.

The gyro sensor 180B may be used to determine the motion attitude of the electronic device 100.

The air pressure sensor 180C is used to measure air pressure.

The magnetic sensor 180D includes a hall sensor.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes).

A distance sensor 180F for measuring a distance.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode.

The ambient light sensor 180L is used to sense the ambient light level.

The fingerprint sensor 180H is used to collect a fingerprint.

The temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 implements a temperature processing strategy using the temperature detected by temperature sensor 180J.

The touch sensor 180K is also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is used to detect a touch operation applied thereto or nearby. The touch sensor can communicate the detected touch operation to the application processor to determine the touch event type. Visual output associated with the touch operation may be provided through the display screen 194. In other embodiments, the touch sensor 180K may be disposed on a surface of the electronic device 100, different from the position of the display screen 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, the bone conduction sensor 180M may acquire a vibration signal of the human vocal part vibrating the bone mass.

The keys 190 include a power-on key, a volume key, and the like.

The motor 191 may generate a vibration cue.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 195 is used to connect a SIM card.

The software system of the electronic device 100 may employ a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example, and exemplarily illustrates a software structure of the electronic device 100.

Fig. 1B is a block diagram of a software structure of the electronic device 100 according to the embodiment of the present application.

The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom.

The application layer may include a series of application packages.

As shown in fig. 1B, the application package may include applications such as camera, gallery, calendar, phone call, map, navigation, WLAN, bluetooth, music, video, short message, etc.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 1B, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100. Such as management of call status (including on, off, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The software system shown in fig. 1B is related to the presentation of various applications (e.g., an instant messaging application, a mailbox application, a file manager, etc.), and provides a "share" service in the embodiment of the present application. Wherein, the application framework layer provides WLAN service and Bluetooth service, and the kernel layer and the bottom layer provide WLAN capability, Bluetooth capability and basic communication protocol.

The method for transmitting the file in the application provided by the embodiment of the application relates to two ends, wherein one end is a sending end 101 for sending the file, and the other end is a receiving end 102 for receiving the file. Both the transmitting end 101 and the receiving end 102 are electronic devices, and the structures of both the transmitting end 101 and the receiving end 102 can refer to the related descriptions in the embodiments of fig. 1A and fig. 1B.

In this embodiment, the transmitting end may be referred to as a first device, and the receiving end may be referred to as a second device. The associated user at the transmitting end may be referred to as a first user and the associated user at the receiving end may be referred to as a second user.

In the method provided in this embodiment of the present application, the sending end 101 may discover other nearby devices, and determine, among the other nearby devices, a device associated with the contact selected by the user, where the device associated with the contact selected by the user is the receiving end 102. Then, the sender 101 may send the file selected by the user to the receiver 102 through "share" in the application.

The method for transmitting files in the application provided by the embodiment of the present application is described below with reference to the user interface provided by the embodiment of the present application.

The term "User Interface (UI)" in the embodiments of the present application is a media interface for performing interaction and information exchange between an application program or an operating system and a user, and implements conversion between an internal form of information and a form acceptable to the user. The user interface is source code written by java, extensible markup language (XML) and other specific computer languages, and the interface source code is analyzed and rendered on the electronic equipment and finally presented as content which can be identified by a user. A commonly used presentation form of the user interface is a Graphical User Interface (GUI), which refers to a user interface related to computer operations and displayed in a graphical manner. It may be a visual interface element such as text, an icon, a button, a menu, a tab, a text box, a dialog box, a status bar, a navigation bar, a Widget, etc. displayed in the display of the electronic device.

Fig. 2A-2B illustrate an operation of opening a "share" on the sender 101.

Fig. 2A illustrates an exemplary user interface 21 on the sender 101 for exposing installed applications. The user interface 21 displays: a status bar, a calendar indicator, a weather indicator, a tray with frequently used application icons, a navigation bar, other application icons (e.g., an icon of a gallery, an icon 201 of the instant messenger application "hi chat", etc.), etc. Wherein, the status bar can include: one or more signal strength indicators for mobile communication signals (which may also be referred to as cellular signals), an operator name (e.g., "china mobile"), one or more signal strength indicators for wireless fidelity (Wi-Fi) signals, a battery status indicator, a time indicator, and so forth. The navigation bar may include a return key, a home screen key, a multitasking key, etc. system navigation keys. In some embodiments, the user interface 21 illustratively shown in FIG. 2A may be a Home screen (Home Screen).

As shown in fig. 2A and 2B, when the sender 101 detects a downward sliding gesture on the display screen, in response to the gesture, the sender 101 may display a window 202 on the user interface 21. As shown in fig. 2B, a control 202A may be displayed in the window 202, and the control 202A may receive an operation (e.g., a touch operation, a click operation) to turn on/off a "share" function of the sender 101. The representation of control 202A may include an icon and/or text (e.g., the text "hashare," etc.). Other switch controls for functions such as Wi-Fi, bluetooth, flashlight, etc. may also be displayed in window 201. In some embodiments, after the sender 101 turns "share", the display form of the control 202A may be changed, for example, a shadow when the control 202A is displayed is increased.

Not limited to the manner in which the user opens the "share" in the window 202 shown in fig. 2A and fig. 2B, in this embodiment of the application, the sender 101 may also open the "share" in other manners. For example, the sender 101 may further display a setting interface provided by a settings (settings) application, and the setting interface may include a control provided for a user to turn on/off a "hashare" function of the sender 101, and the user may turn on the "hashare" of the sender 101 by inputting a user operation on the control. For another example, the user may select a contact for sharing a file in the application and then open a "share" of the sending end 101, which will be described in detail in the following embodiments, which will not be described herein again.

In one embodiment of the present application, the operation for opening the "share" may be referred to as a fourth operation for opening the first communication service and the second communication service. The first communication service is used for the sending end to find and determine the receiving end through Bluetooth, and the second communication service is used for the sending end to send the file to the receiving end through Wi-Fi direct communication connection.

The following describes the user interfaces implemented on the sending end 101 and the receiving end 102 in connection with several application scenarios related to the present application.

The method comprises the following steps: scene that user selects contact first and then selects file to share

Fig. 3A-3I exemplarily illustrate user interfaces displayed by the transmitting end 101 in scene one.

1. 3A-3B illustrate embodiments of a user selecting a contact in an application.

Fig. 3A exemplarily shows a user interface 31 of a first application (e.g. the instant messaging application "hi chat") displayed by the sender 101. The first application may be an application installed on the electronic device for social communication, and the first application may support communication between a plurality of users, such as sending text, voice, files, and the like to each other. The user may log into the first application on the sender 101 using his own user identification and password. After logging in the first application program, the user can communicate with the contact person added in the first application program by the user. In this embodiment, a user who logs in to the first application program on the sender 101 may be referred to as an associated user of the sender 101.

The user interface 31 shown in fig. 3A may be displayed by the sender 101 in response to a user operation (e.g., a click operation, a touch operation, etc.) received on the icon 201 in the user interface 21. The user interface 31 is used to present one or more contact options for the user in the first application.

As shown in fig. 3A, the user interface 31 has displayed therein: status bar 301, title bar 302, search box 303, one or more recent contacts options, menu bar 305.

The status bar 301 may refer to the status bar in FIG. 2A.

The title bar 302 may comprise a current page indicator for indicating the current page, e.g. the text information "hi chat" for indicating that the current page is providing a user interface for the first application "hi chat".

The search box 303 may be used to listen for touch operations, click operations, etc., in response to which the sender 101 may display a text entry box, such that the user enters a contact option, chat log (e.g., text information, pictures, links or other files, etc.) in the text entry box that the user desires to search.

The recent contact options may include contact options corresponding to one or more contacts that the user has recently communicated in the first application, and the contact options may include: a public number option, a user option, and a group option, among others. For example, the recent contacts option includes an option 304A of contact "Kate", and an option 304B of group "work group". Implementations of the contact options may include, but are not limited to: an icon or text. The icon or text may be used to indicate a user identification of the contact in the first application. The user identification may include, but is not limited to: an account number, avatar, nickname, name, etc. of the contact in the first application.

The menu bar 305 may include a plurality of controls, such as "hi chat", "address book", "find", and "me" shown in fig. 3A. The content displayed in the display area of the user interface other than menu bar 305 and status bar 301 is associated with the control currently selected by menu bar 305. The currently selected control in the menu bar 305 of fig. 3A is "hi chat".

The sending end 101 may display, on the display screen, a communication record of a contact corresponding to the contact option in response to the user operation detected on the contact option. In some embodiments, the sender 101 may also open a "share" in response to a user action detected on a contact option in the case that the "share" of the sender 101 has not been opened.

In this embodiment of the present application, the user operation detected by the sender 101 on the contact option may be referred to as a user operation for selecting a contact. The contact corresponding to the contact option is the selected contact.

Fig. 3B exemplarily shows the user interface 32 displayed by the sender 101 in response to an operation (e.g., a click operation, a touch operation, etc.) input by the user on the option 304A of the contact "Kate", where the selected contact is "Kate". The user interface 32 is used to present the communication record of the associated user of the sender 101 and the contact "Kate".

As shown in fig. 3B, displayed in the user interface 32 are: status bar 306, title bar, communication record 308 for the associated user of sender 101 and contact "Kate" (communication record shown in fig. 3B is empty), menu 309.

The status bar 306 may refer to the status bar in FIG. 2A.

The title bar may include a current page indicator 307B for indicating the current page, e.g., the text information "Kate" for indicating that the current page is one page where the user and contact "Kate" communicate. The title bar may further include a return key 307A, the return key 307A being used to listen to a user operation, and the sender 101 may display the user interface 31 illustrated in fig. 3A in response to the user operation on the return key 307A.

The menu 309 may include a control 309A, a text entry box 309B, and a control 309C. The control 309A may be used to listen to user operations, and the sender 101 may prompt the user to enter a voice to send to the contact "Kate" in response to a user operation acting on the control 309A. The text entry box 309B may be used to listen to user actions, and the sender 101 may display a virtual keyboard in response to a user action on the control 309B for the user to enter text sent to the contact "Kate". The control 309C may be used to listen to user operations, and the sender 101 may display more functional service options in response to user operations acting on the control 309C, such as an option to take a picture, an option to initiate a video call between devices associated with the contact "Kate", an option to transfer to the contact "Kate", and so on.

2. 3C-3E illustrate embodiments where a user selects a contact in an application, selects a file and shares to the selected contact.

Fig. 3C illustrates a plurality of functional service options displayed by the sender 101 in response to a user operation detected on the control 309C in the user interface 32 shown in fig. 3B. As shown in fig. 3C, the plurality of functional service options includes "share file transfer" 310.

The "share file transfer" option 310 is used to listen to user operations (e.g., clicking, touching, long-pressing, etc.), and the sender 101 may display a user interface for presenting one or more files stored by the sender 101 in response to the user operations detected on the "share file transfer" option 310.

In some embodiments, the sender 101 may also open a "share" in response to a user action detected on the "share file transfer" option 310 in the event that the "share" of the sender 101 has not been opened.

Fig. 3D illustrates a user interface 33 on the sender 101 for presenting one or more files stored by the sender 101. As shown, the user interface 33 may include: status bar 311, control 312A, control 312B, file area 313.

The status bar 311 may refer to the status bar in the user interface 21 shown in FIG. 2A.

The control 312A may be used to listen to user operations, and the sender 101 may display the user interface 32 shown in fig. 3C in response to a user operation detected on the control 312A.

The control 312B may be used to monitor user operations, and the sending end 101 may send a file selected by the user in the file area 313 to a device associated with the selected contact "Kate" in the first application program in response to the user operation detected on the control 312B. In some embodiments, control 312B may not receive a user operation until the user selects a file in file area 313. Alternatively, as shown in fig. 3D, when the user has not selected a file in the file area 313, the sender 101 may add a shadow on the control 312B to prompt the user that the control 312B has not been able to receive the user operation.

Thumbnail images or names of one or more files may be displayed in the file area 313, such as thumbnail images of pictures (e.g., picture thumbnail 313A, picture thumbnail 313B), thumbnail images of videos (e.g., video thumbnail 313C), names of documents (e.g., the name "novel 1" 313D of a Word-format document), and so forth. The thumbnail or name of the file may be stored in the transmitting end 101 in a file, for example, the original image corresponding to the picture thumbnail 313A, the original video corresponding to the video thumbnail 313C, or the like. When the sender 101 detects a slide operation up or down in the file area 313, the sender may update the content displayed in the file area 313 so that the user views thumbnails or names of more files. Not limited to a sliding operation up or down, the user may also slide left or right in the file area 313 to browse thumbnails or names of more files.

The user may enter a user action in the file area 313 to select a file to be shared with the contact "Kate". The user operation may be a click operation, a touch operation, or the like, which acts on the thumbnail or name of the file. For example, the user may click on the picture thumbnail 313A, the picture thumbnail 313B, and the name "novel 1" 313D in the file area 313, and select a corresponding file, for example, an original corresponding to the picture thumbnail 313A, an original corresponding to the picture thumbnail 313B, and a document corresponding to the name "novel 1" 313D, as a file to be shared with the contact "Kate". In some embodiments, as shown in fig. 3E, the sender may also display a mark 313E on a thumbnail or name that has been selected by the user in the file area 313, and the mark 313E may indicate that the file corresponding to the thumbnail or name has been selected by the user.

FIG. 3E illustrates an embodiment in which a user shares a selected file to a contact "Kate" in a first application. As shown in fig. 3E, the sender 101 may detect a user operation on the user interface 33, which may be an operation (e.g., a click operation, a touch operation) acting on the control 312B, and transmit the file selected by the user to a device associated with the contact "Kate" in the first application program, in response to the user operation, by the sender 101. Not limited to the operation of first selecting a file and then clicking the control 312B, the sender 101 may also transmit the file selected by the user to a device associated with the contact "Kate" in the first application program in response to other forms of operations, for example, may also shake the sender 101 after the user selects the file, and may also transmit the file in response to a voice control operation, for example.

The device associated with the contact is a device used when the contact currently logs in the first application program. In this embodiment, the device associated with the contact selected by the user is the receiving end 102. That is, the contact selected by the user in the first application is the associated user of the receiving end 102.

How the sending end 101 determines the device associated with the contact selected by the user (for example, the device associated with the contact "Kate" in the first application), that is, how to determine the receiving end 102, may refer to the detailed description of the subsequent embodiments, which is not repeated herein.

In this embodiment of the application, the sending end 101 transmits the file selected by the user to the receiving end 102 through a "share", and specific implementation of the transmission process may refer to detailed description of the subsequent embodiments, which is not repeated herein.

In some embodiments, after the sender 101 transmits the selected file to the receiver 102 in response to detecting the user operation for sharing the selected file to the contact, a prompt message 315 may be further displayed in the file transmission record 314 exemplarily shown in one or more of fig. 3F-3I. The prompt message 315 is used to prompt the user of the transmission state of the selected file, so that the user can very intuitively know the transmission state of the selected file, and the user experience is improved. In other embodiments, the prompt 315 may be an audio that is played through the speaker 170A rather than a visual interface element displayed on the display screen.

3. Fig. 3F-3I show a user interface on the sender 101 for feeding back the file transfer status.

After the sender 101 transmits the selected file to the recipient 102 in response to the operation of sharing the file to the contact, as shown in fig. 3F-3I, the sender 101 may display a file transmission record 314 in the communication record 308 of the user interface 32 exemplarily shown in fig. 3C. The user interface 32 is a user interface for displaying the communication record of the associated user of the sender 101 and the contact "Kate". So that the user can communicate with the contacts, such as sending text, voice, etc., in the user interface 32.

As shown in fig. 3F-3I, the file transfer record 314 may include: the head portrait of the associated user of the sender 101, the thumbnail images or names of one or more files that the user has selected, and a reminder 315. The prompt 315 is used to indicate the status of the transfer of the file that the user has selected.

As shown in FIG. 3F, the prompt 315 may be used to prompt the user that the transmission status of the selected file is the first transmission status. The first transmission state may refer to a file that the user has selected is waiting to be received by the receiving end 102. The reminder information 315 may include one or more of the following: the text message "wait for the other party to receive", overlays the shadow over all the file thumbnails or names. In some embodiments, when the sender 101 displays the prompt 315 as shown in fig. 3F, a control for canceling the file transmission may also be displayed in the file transmission record 314. The control may be implemented as the text "cancel transfer". Canceling the transmission of the file means that the sender 101 does not send the file to the receiver 102.

As shown in FIG. 3G, the prompt 315 may be used to prompt the user that the transmission status of the selected file is the second transmission status. The second transmission state may refer to a file that the user has selected being transmitted to the receiving end 102. The reminder information 315 may include one or more of the following: text information "send in", progress bar, overlaid portion of file thumbnail, or shadow on name.

As shown in fig. 3H, the prompt 315 may be used to prompt the user that the transmission status of the selected file is the third transmission status. The third transmission state may refer to the file that the user has selected being successfully transmitted to the receiving end 102. The reminder information 315 may include one or more of the following: the text message "sent successfully", progress bar.

As shown in FIG. 3I, the prompt 315 may be used to prompt the user that the transmission status of the selected file is the fourth transmission status. The fourth transmission state may refer to that the file selected by the user was not successfully transmitted to the receiving end 102. The reminder information 315 may include one or more of the following: the text message "failure to send", progress bar, shadow over all file thumbnails or names. In some embodiments, when the sender 101 displays the prompt 315 as shown in fig. 3I, a control for retransmitting the file may also be displayed in the file transfer record 314. The control may be implemented as the text "retransmit". Retransmitting the file means that the transmitting end 101 transmits the file selected by the user to the receiving end 102 again. Reasons why the user-selected file was not successfully transmitted to the receiving end 102 may include, but are not limited to: the device associated with the selected contact does not exist in the devices near the sending end 101, the communication connection between the sending end 101 and the receiving end 102 is interrupted, and the like, which is not limited in this embodiment of the application.

Without being limited to the several prompting messages shown in fig. 3F-3I, in other embodiments, the sending end 101 may also display some other prompting messages, such as a prompting message for prompting the user that a part of the selected file is successfully transmitted to the receiving end 102, a prompting message for prompting the user that the contact refuses to accept the file, and so on.

Through the UI embodiments exemplarily shown in fig. 3A-3I, after a user selects a contact in a first application, the sending end 101 may be triggered to send the selected file to the receiving end 102. Therefore, the sending end 101 can share the file in the first application program through the "share", the user experience is visual and simple, and the efficiency of sharing the file in the application program is greatly improved.

In the scenario of the first user selecting the contact first and then selecting the file for sharing, the sending end 101 may also display some other UI embodiments when executing the method provided by the embodiment of the present application, without being limited to the UI embodiments shown in fig. 3A to 3I. Several related extensions to the UI embodiments shown in fig. 3A-3I above will be described.

1. Extension 1: related extensions to the UI embodiment shown in FIG. 3C

As shown in fig. 3C, the sender 101 may display a plurality of feature service options including a "share file transfer" option 310 in response to a user operation detected on a control 308C in the user interface 32 shown in fig. 3B. Also, the "share file transfer" option 310 may receive a user operation, and the sender 101 may display the user interface 33 as shown in fig. 3D in response to the user operation.

Without being limited to the manner shown in fig. 3C, in the embodiment of the present application, the sender 101 may also display a "share file transfer" option in a manner described in (1) or (2) below.

(1) In some embodiments, the sender 101 may display the "share file transfer" option 310 after determining that the file can be transferred with the receiver 102 by "share".

Referring to fig. 4A-4C, one implementation of the sender 101 displaying the "share file transfer" option 310 is shown. In some embodiments of the present application, fig. 3B to 3C of the file sharing process shown in fig. 3A to 3I may be replaced with fig. 4A to 4C.

The user interface 32 shown in fig. 4A is the same as the user interface 32 shown in fig. 3B, and reference may be made to the related description.

A plurality of functional service options that the sender 101 displays in response to a user operation detected on the control 309C in the user interface 32 shown in fig. 4A may be included in the user interface 32 shown in fig. 4B. As shown in fig. 4B, before the sender 101 determines that the sender 101 can transmit the file with the receiver 102 via the "share" option, the sender 101 does not include the "share file transmission" option in the multiple functional service options displayed.

As shown in fig. 4C, after a while, if the sender 101 determines that the file can be transmitted with the receiver 102 by "share", the sender may newly display a "share file transmission" option 310 in the user interface 32. In some embodiments, in order to newly add and display the "share file transfer" option 310 in the user interface, the sender may adjust the arrangement manner of each functional service option, for example, reduce the distance between each functional service option, stop displaying a certain functional option, and the like, which is not limited in this embodiment of the application.

The "share file transfer" option shown in fig. 4C is the same as the "share file transfer" option in fig. 3C, and may be used to monitor user operations, and reference may be made to related descriptions, which are not described herein again.

Through the extension in the point (1), after determining that the file can be transmitted with the receiving end 102 through the "washre", the sending end 101 displays the "washre file transmission" option 310, so that when a user wants to transmit the file to a contact through the "washre", the probability that the file is successfully transmitted is improved, and better use experience is provided for the user.

(2) The sender 101 may display a "share file transfer" option 310 that may receive a user operation after determining that the file can be transferred with the receiver 102 via the "share".

Referring to fig. 4D-4F, another implementation is shown in which the sender 101 displays the "share file transfer" option 310. In some embodiments of the present application, the embodiments of fig. 3B-3C in the file sharing process shown in fig. 3A-3I may be replaced with the embodiments of fig. 4D-4F.

The user interface 32 shown in fig. 4D is the same as the user interface 32 shown in fig. 3B, and reference may be made to the related description.

A plurality of functional service options that the sender 101 displays in response to a user operation detected on the control 309C in the user interface 32 shown in fig. 4A may be included in the user interface 32 shown in fig. 4E. Before the sender 101 determines that the sender 101 can transmit the file with the receiver 102 by "share", the sender 101 cannot receive the user operation in the "share file transmission" option 310 in the plurality of functional service options displayed. The failure of the "share file transfer" option 310 to receive a user operation means that the sender 101 does not display a user interface for presenting files stored by the sender 101 in response to a user operation applied to the "share file transfer" option 310.

In some embodiments, before the sender 101 determines that the file can be transmitted with the receiver 102 by "share", a prompt message may be displayed on the user interface 32 to prompt that the file cannot be transmitted with the receiver 102 by "share". The reminder information may include, but is not limited to: the shading, text messaging, animation, etc. shown in fig. 4E overlaid on the "hashfile transfer" option 310.

As shown in fig. 4F, after a while, if the sender 101 determines that the file can be transmitted with the receiver 102 by "share", a "share file transmission" option 310 in the user interface 32 displayed by the sender 101 is available for receiving a user operation. The "share file transfer" option 310 may receive a user operation, that is, the sender 101 may display a user interface for presenting a file stored by the sender 101 in response to the user operation acting on the "share file transfer" option 310.

The case that the sender 101 and the receiver 102 can transmit the file through the "share" includes:

case 1. when a sender 101 sends a file to a receiver 102 via one or more of bluetooth, Wi-Fi direct (e.g., Wi-Fi p2p), and Wi-Fi softAP wireless communication technologies, a communication connection has been established between the sender 101 and the receiver 102. The communication connection is used for file transfer between the sender 101 and the receiver 102.

Case 2. when the transmitting end 101 transmits a file to the receiving end 102 through NFC, the distance between the transmitting end 101 and the receiving end 102 is within the effective communication distance of NFC. In other words, when the sender 101 sends a file to the receiver 102 through NFC, the sender 101 can discover the receiver 102 through NFC.

Case 3. when the transmitting end 101 transmits a file to the receiving end through a wireless communication technology such as Wi-Fi LAN, the transmitting end 101 and the receiving end 102 are in the same LAN.

Through the extension in the point (2), after determining that the file can be transmitted with the receiving end 102 through the "hashare", the sending end 101 displays a "hashare file transmission" option 310 capable of receiving a user operation, so that the user can accurately know whether the file can be transmitted to the contact through the "hashare", the probability that the file is successfully transmitted is improved, and better use experience is provided for the user.

2. Extension 2: related extensions to the UI embodiment shown in FIG. 3C

As shown in fig. 3C, the sender 101 may display a plurality of functional service options including a "hashare file transfer" option 310 in response to a user operation detected on a control 309C in the user interface 32 shown in fig. 3B. Also, the "hashare file transfer" option 310 may receive a user operation, and the sender 101 may display the user interface 33 for presenting the files stored by the sender 101 in response to the user operation. The sender 101 may send the file selected by the user in the user interface 33 to the receiver 102 through "share".

Without being limited to the manner shown in fig. 3C, in some other embodiments of the present application, the sender 101 may display a plurality of functional service options in response to the user operation detected on the control 309C in the user interface 32 shown in fig. 3B, where the "hishare file transfer" option 310 may not be included in the plurality of functional service options. When a user shares a file to a contact through these feature service options, the sender 101 may send the file to the receiver 102 through "share".

Fig. 5A-5I illustrate a user interface implemented on the sender 101 under extension 2. In some embodiments of the present application, the embodiments of fig. 3A to 3E in the file sharing process shown in fig. 3A to 3I may be replaced with fig. 5A to 5E, and fig. 3F to 3I may be replaced with fig. 5F to 5I.

First, FIGS. 5A-5B illustrate embodiments in which a user selects a contact in an application.

The user interface 51 shown in fig. 5A may refer to the user interface 31 shown in fig. 3A, and the user interface 52 shown in fig. 5B may refer to the user interface 32 shown in fig. 3B.

Next, fig. 5C-5E illustrate embodiments in which a user selects a contact in an application and then selects a file to share with the contact.

Fig. 5C illustrates a plurality of functional service options displayed by the sender 101 in response to a user operation detected on the control 309C in the user interface 52 illustrated in fig. 5B. Fig. 5C differs from fig. 3C in that the "hishare file transfer" option is not included in the user interface 52 shown in fig. 5C. As shown in fig. 5C, among the plurality of functional service options in user interface 52 is option 501 for sharing pictures and/or videos.

The option 501 is used to monitor a user operation (e.g., a click operation, a touch operation, a long press operation, etc.), and the sender 101 may display a user interface for displaying one or more pictures and videos stored by the sender 101 in response to the user operation detected on the option 501. In the case that the "share" of the sender 101 has not been opened, the sender 101 may also open the "share" in response to the user operation detected on the option 501.

Fig. 5D illustrates a user interface 53 on the sender 101 for presenting one or more pictures and videos stored by the sender 101. As shown, the user interface 53 may include: status bar 502, control 503A, control 503B, file area 504.

The status bar 502 may refer to the status bar in the user interface 21 shown in FIG. 2A.

The control 503A may be used to listen to user operations, and the sender 101 may display the user interface 52 shown in fig. 5C in response to a user operation detected on the control 503A.

Control 503B may be used to listen to user operations, and the sender 101 may send the file selected by the user in the file area 504 to a device associated with the contact "Kate" of the first application in response to the user operation detected on control 503B. In some embodiments, control 503B can receive a user action after the user selects a file in file area 504. Alternatively, as shown in fig. 5D, when the user has not selected a file in the file area 504, the sender 101 may add a shadow on the control 503B to prompt the user that the control 503B cannot receive the user operation.

The file area 504 may display one or more thumbnails of pictures and videos, such as thumbnails of pictures (e.g., picture thumbnail 504A), thumbnails of videos (e.g., video thumbnail 504B), and so forth. Original images, original videos, and the like corresponding to thumbnails of pictures and videos may be stored on the transmitting end 101. When the sender 101 detects a slide-up or slide-down operation in the file area 504, the sender may update the content displayed in the file area 504 so that the user views thumbnails of more pictures and/or videos. Without being limited to a swipe operation up or down, the user may also swipe left or right in the file area 504 to browse for more thumbnails or names of pictures and/or videos. In some embodiments, a control 504C may also be displayed in file region 504. The sender 101 may update the content displayed in the file area 504 in response to an operation (e.g., a click operation, a touch operation, etc.) entered by the user on the control 504C in order for the user to browse thumbnails of more pictures and/or videos.

The user may enter a user action in the file area 504 to select a picture and/or video to be shared with the contact "Kate". The user operation may be a click operation, a touch operation, or the like, which acts on a thumbnail of a picture and/or video. For example, the user may click on the picture thumbnail 504A and the video thumbnail 504B in the file area 504, and determine the corresponding file, for example, the original image corresponding to the picture thumbnail 504A and the original video corresponding to the video thumbnail 504B, as the file to be shared with the contact "Kate". In some embodiments, as shown in fig. 5E, the transmitting end may further display a mark 504D on the thumbnail selected by the user in the file area 504, where the mark 504D may indicate that the original picture or the original video corresponding to the thumbnail has been selected by the user.

FIG. 5E illustrates an embodiment in which the user shares the selected file to the contact "Kate" in the first application. As shown in fig. 5E, the sender 101 may detect a user operation for sharing the selected picture and/or video to the contact in the user interface 53, where the user operation may be an operation (e.g., a click operation, a touch operation) acting on the control 503B. The sender 101 may, in response to this operation, transmit the picture and/or video that the user has selected to a device associated with the contact "Kate" in the first application. Not limited to clicking on control 503B, the sender 101 may also transmit the picture and/or video selected by the user to a device associated with the contact "Kate" in the first application in response to other forms of operations, for example, may also transmit the picture and/or video selected by the user to the device associated with the contact "Kate" in response to a user shaking operation of the sender 101, for example, a voice control operation, and the like.

Here, when the sending end 101 sends the picture and/or video selected by the user to the receiving end 102 in response to the user operation for sharing the selected picture and/or video to the contact, the picture and/or video may be sent according to any one of the following policies:

strategy 1. after determining that a file can be transmitted with the receiving end 102 through the "share", the sending end 101 directly sends the file selected by the user to the receiving end 102 through the "share". If the sender 101 determines that the file cannot be transmitted with the receiver 102 through the "hashare", the file selected by the user is sent to the receiver 102 through cellular technology such as 3G, LTE or 5G or Wi-Fi technology. For the case that the sender 101 and the receiver 102 can transmit files through "share", reference is made to the above description of point 1, extension 1.

Strategy 2. the sending end 101 determines the total size of the file selected by the user, and if the total size exceeds a first threshold, the file selected by the user is sent to the receiving end 102 through a "share". If the total size does not exceed the first threshold, the sending end 101 sends the selected file to the receiving end 102 through cellular technology such as 3G, LTE, 5G, or Wi-Fi technology.

Strategy 3, the sending terminal 101 inquires whether the user sends the file selected by the user to the receiving terminal 102 through the "share", and when detecting that the user indicates a user operation of sending the selected file through the "share", the file selected by the user is sent to the receiving terminal 102 through the "share". The transmitting end 101 may output a visual interface element, voice, etc. displayed on the display screen to inquire whether the user transmits the file selected by the user to the receiving end 102 through "share". Such a policy may enable the sender 101 to send the selected file via "hashare" according to the user's needs.

For a specific implementation of the process of sending the file selected by the user to the receiving end 102 by the sending end 101 through the "hashare", reference may be made to the detailed description of the subsequent embodiments, which is not repeated herein.

Finally, fig. 5F-5I show a user interface on the sender 101 for feedback of the file transfer status.

After the sender 101 transmits the file selected by the user to the receiver 102 in response to the operation for sharing the file selected by the user to the contact, as shown in fig. 5F-5I, the sender 101 may display a file transmission record 505 in a communication record 308 of the user interface 32 exemplarily shown in fig. 5C.

Prompt information 506 is included in file transfer record 505. The file transfer 505 may be embodied with reference to the file transfer record 314 shown in fig. 3F-3I.

As shown in FIG. 5F, the prompt 506 may be used to prompt the transmission status of the selected file to be the first transmission status. The first transmission state may refer to the related description above. The reminder 506 may refer to the reminder 315 shown in FIG. 3F.

As shown in FIG. 5G, the prompt 506 may be used to prompt the transmission status of the selected file to be the second transmission status. The second transmission state may refer to the related description above. The hint 506 can refer to the hint 315 shown in FIG. 3G.

As shown in FIG. 5H, the prompt 506 may be used to prompt the transmission status of the selected file to be the third transmission status. The third transmission state may refer to the related description above. The hint 506 can refer to the hint 315 shown in FIG. 3H.

As shown in FIG. 5I, a prompt 506 may be used to prompt the transmission status of the selected file to be a fourth transmission status. The fourth transmission state may refer to the related description above. The hint 506 can refer to the hint 315 shown in FIG. 3I.

With the UI embodiments exemplarily shown in fig. 5A-5I, after an associated user of the sending end 101 selects a contact in a first application, the sending end 101 may be triggered to send the selected file to the receiving end 102 through a functional service option. Therefore, the sending end 101 can share the file in the first application program through the "share", the user experience is visual and simple, and the efficiency of sharing the file in the application program is greatly improved. With the UI embodiments exemplarily shown in fig. 5A to 5I, the sender 101 does not need to provide a special "hashare file transfer" option, and can send the file to the receiver 102 through "hashare" when the user triggers the sender 101 to send the selected file to the receiver 102.

(II) scenario II: the user selects the file first, and then selects a scene for the contact person to share.

Fig. 6A-6H exemplarily show user interfaces displayed by the transmitting end 101 in scene two.

1. 6A-6B illustrate embodiments of a user selecting a file.

Fig. 6A illustrates a user interface 61 of a second application (e.g., "gallery") displayed by the sender 101. The user interface 61 may be used to present one or more pictures and/or videos stored in the sender 101. The second application may support the user to perform various operations on the file stored on the sender 101, such as browsing, editing, deleting, selecting, and the like. The "gallery" is an application program for managing pictures installed on an electronic device such as a smart phone and a tablet computer, and may also be referred to as an "album", and the name of the application program is not limited in this embodiment. I.e., the "gallery" managed objects are pictures and/or videos.

As shown in fig. 6A, the user interface 61 may include: status column 601, title column 602, picture area 603. Wherein:

the status bar 601 may refer to the status bar in the user interface 21 shown in FIG. 2A.

The title bar 602 may include a current page indicator, such as the textual information "gallery". Not limited to text information, the current page indicator may also be an icon.

One or more thumbnails of pictures and videos may be displayed in the picture area 603, such as thumbnails of pictures (e.g., picture thumbnail 603A), thumbnails of videos (e.g., video thumbnail 603B), and so forth. Original images, original videos, and the like corresponding to thumbnails of pictures and videos may be stored on the transmitting end 101. When the transmitting end 101 detects a slide-up or slide-down operation in the picture area 603, the transmitting end may update the content displayed in the picture area 603 so that the user can browse thumbnails of more pictures and/or videos. Without being limited to a swipe operation up or down, the user may also swipe left or right in the picture area 603 to browse for more thumbnails or names of pictures and/or videos. In some embodiments, a control 603C may also be displayed in the picture region 603. The transmitting end 101 may update the content displayed in the picture area 603 in response to an operation (e.g., a click operation, a touch operation, etc.) input by the user on the control 603C, so that the user can browse thumbnails of more pictures and/or videos.

The user may enter a user action in picture area 603 to select a picture and/or video. The user operation may be a click operation, a touch operation, or the like, which acts on a thumbnail of a picture and/or video. For example, the user may click on the picture thumbnail 603A and the video thumbnail 603B in the picture area 603, and determine the corresponding file, for example, the original image corresponding to the picture thumbnail 603A and the original video corresponding to the video thumbnail 603B, as the file to be shared with the contact. In some embodiments, as shown in fig. 6B, the sending end may further display a mark 603D on the thumbnail selected by the user in the picture area 603, and the mark 603D may indicate that the original picture or the original video corresponding to the thumbnail has been selected by the user.

Fig. 6B illustrates an embodiment in which a user shares pictures and/or videos in a "gallery". As shown in fig. 6B, the sender 101 may detect an operation for sharing the selected file in the user interface 61 shown in fig. 6B. In response to this operation, the sender 101 may display one or more application icons. The sending end 101 may detect, on one or more application icons, an operation of the application selected by the user for sharing, and in response to the operation, the sending end 101 may send, in the application selected by the user, the file selected by the user to the device associated with the contact selected by the user.

The operations for sharing the selected file may be: the user selects a file and clicks on the "share file transfer" option 604A. In some embodiments, when the sender 101 detects an operation of selecting a file by a user in the user interface 61, the menu 604 in fig. 6B may be displayed in the user interface 61. In other embodiments, the sender 101 may also display the menu 604 in the user interface 61 initially, i.e. the menu 604 is not displayed until the user is detected to select a file. Menu 604 may include "share file transfer" option 604A, option 604B ("move"), option 604C ("select all"), option 604D "more. The "share file transfer" option 604A may be used to listen for sharing of the selected file by "share". In the case that the "share" of the sender 101 has not been opened, the sender 101 may also open the "share" in response to a user operation detected on the "share file transfer" option 604A.

Not limited to the operation of first selecting a file and then clicking the "share file transfer" option 604A, the operation for sharing the selected file may also be implemented in other forms, for example, an operation of selecting a file within a fixed time (e.g., 1 second) after shaking the sender 101, a voice control operation, and the like.

2. 6C-6D illustrate embodiments in which a user selects an application and a contact within the application and shares files to the contact.

As shown in fig. 6C, the sender 101 displays a window 605 in the user interface 61 in response to an operation for sharing the selected file (e.g., an operation entered on the "share file transfer" option 604A after the user selects the file). The window 605 may obscure a portion of the content originally displayed in the user interface 61.

Window 605 may include therein: one or more application options, e.g. "hi chat" option 605C, mailbox option 605D. The application options may be implemented in the form of text, icons, and the like. The application corresponding to the application option included in the window 605 may be any one of the following:

(1) all applications installed on the sender 101 that can be used to share files. For example, the sender 101 may display options of all instant messaging applications and mailbox applications in the window 605.

(2) Among the applications that are installed on the sender 101 and are available for sharing files, applications that can share files through "share" are currently available. After a user logs in an application installed on the sending end 101, if a device associated with a contact in the application can transmit a file with the sending end 101 through a "share", the application is an application capable of sharing the file through the "share". For example, if the user logs in the device 102 currently registered with the contact hit in the hi chat installed on the sender 101 and can transfer a file with the sender 101 by "hishere", and the user also logs in the mailbox installed on the sender 101, the device 102' currently registered with the contact William in the mailbox cannot transfer a file with the sender 101 by "hishere", and then the sender 101 displays only the option of the hi chat application in the window 605, but does not display the option of the mailbox application in the window 605. For the case that the sender 101 and other devices can transmit files through "share", reference is made to the related description in the extension 1 of the scenario one above. Therefore, the problem that the user selects an improper application program to cause file sharing failure can be avoided.

In some embodiments, prompt information 605B may also be included in window 605. Prompt 605B is used to prompt the user to select an application for sharing the selected file. For example, the prompt 605B may be a text message "through which application you want to share a file".

In some embodiments, prompt information 605A may also be included in window 605. The prompt 605A is used to prompt the user of the condition for sharing the file to other devices by "share". For example, the prompt 605A may be the text message "note: when sharing files through the hishare, the other party needs to start Bluetooth and WLAN ".

The application options in the window 605 may be used to listen to a user operation (e.g., a click operation, a touch operation, etc.), and the sender 101 may display a user interface for providing a user with a choice of a contact in a corresponding application to share a file in response to the user operation. In this embodiment, an application corresponding to an application option selected by a user may be referred to as a first application.

Referring to FIG. 6D, FIG. 6D illustrates one implementation of a user interface provided for a first application for a user to select a contact to share a selected file. The user interface 62 shown in fig. 6D may be displayed by the sender 101 in response to a user operation detected on control 605C.

As shown in fig. 6D, user interface 62 may include: status bar 606, title bar 607, reminder information 608, one or more contact options. Wherein:

the status bar 606 may refer to the status bar in the user interface 21 shown in FIG. 2A.

The title bar 607 may include a current page indicator, such as the textual information "hi chat". Not limited to text information, the current page indicator 607 may also be an icon.

The prompt 608 may be used to prompt the user to select a contact to share the file.

One or more contact options, such as contact "MAC" option 609A, contact "Kate" option 609B, may be used to listen for a selection of a contact to trigger an operation to share a file. The sending end 101 may send, in response to the operation detected on the contact option, the file selected by the user to a device associated with the contact corresponding to the contact option through "share". In some embodiments, the electronic device associated with the contact corresponding to the one or more contact options in the user interface 62 can transmit the file with the sender 101 through the "hashare". Therefore, the problem that the user selects an improper contact person to cause failure in file sharing can be solved.

In this embodiment, the device associated with the contact selected by the user may be referred to as the receiving end 102.

3. Fig. 6E to 6H show a user interface for feeding back the file transfer status on the sender 101.

In some embodiments, after the sender 101 sends the file selected by the user to the device associated with the contact corresponding to the contact option through "share" in response to the operation detected on the contact option, as shown in fig. 6E-6H, the sender 101 may display a file transmission record 610 in a user interface for displaying communication records of the user and the contact.

Fig. 6E-6H show a user interface 63 for presenting a communication record of the user and the contact "Kate".

As shown in fig. 6E-6H, the file transfer record 610 includes hint information 611. The file transfer 505 may be embodied with reference to the file transfer record 314 shown in fig. 3F-3I.

As shown in FIG. 6E, the prompt 611 may be used to prompt the transmission status of the selected file to be the first transmission status. The first transmission state may refer to the related description above. The hint 611 may refer to the hint 315 shown in FIG. 3F.

As shown in fig. 6F, the prompt 611 may be used to prompt the transmission status of the selected file to be the second transmission status. The second transmission state may refer to the related description above. The hint 611 may refer to the hint 315 shown in FIG. 3G.

As shown in fig. 6G, the prompt information 611 may be used to prompt the transmission status of the selected file to be the third transmission status. The third transmission state may refer to the related description above. The hint 611 may refer to the hint 315 shown in FIG. 3H.

As shown in fig. 6H, the prompt 611 may be used to prompt the transmission status of the selected file to be the fourth transmission status. The fourth transmission state may refer to the related description above. The hint 611 may refer to the hint 315 shown in FIG. 3I.

Not limited to the several prompt messages shown in fig. 6E-6H, in other embodiments, the sender 101 may also display some other prompt messages, for example, a prompt message for prompting that a part of the selected file is successfully transmitted to the receiver 102.

Through the UI embodiments shown in fig. 6A to 6H, after selecting a file to be shared, a user may trigger the sending end 101 to send the file to a contact in the first application. Therefore, the sending end 101 can share the file in the first application program through the "share", the user experience is visual and simple, and the efficiency of sharing the file in the application program is greatly improved.

The user can select files such as photos, videos and the like for sharing in other file management application programs, such as a file browser and a file manager, for sharing, without being limited to select the files such as the photos, the videos and the like for sharing.

In the second scenario where the user selects the file first and then selects the contact person for sharing, the sending end 101 may also display some other UI embodiments when executing the method provided by the embodiment of the present application, without being limited to the UI embodiments shown in fig. 6A to 6H. Several related extensions to the UI embodiments shown in fig. 6A-6H described above will be described below.

1. Extension 1: related extensions to the UI embodiments shown in FIGS. 6C-6D

As shown in fig. 6D, the sender 101 may display, in response to the operation detected on the first application option in the user interface 61 shown in fig. 6C, a plurality of contact options, where the devices associated with the contacts corresponding to the plurality of contact options are capable of transmitting files with the sender 101 through "hishare". That is, the user may first select the first application and then select a contact in a user interface provided by the first application to share the file.

Not limited to the manner shown in fig. 6D, in the embodiment of the present application, the user may also select the contact sharing file in the manner described in (1) or (2) below.

(1) In some embodiments, the sender 101 may display a user interface provided by the first application for presenting one or more recent contact options in response to an operation detected on the first application option in the user interface 61 shown in fig. 6C.

Fig. 7A-7B illustrate embodiments in which the sender 101 displays a user interface provided by a first application for exposing one or more recent contact options in response to an operation detected on the first application option. In some embodiments of the present application, fig. 6C-6D of the file transfer process shown in fig. 6A-6H described above may be replaced with fig. 7A-7B.

The user interface 61 shown in fig. 7A is the same as the user interface 61 shown in fig. 6C, and reference may be made to the related description.

FIG. 7B illustrates one implementation of a user interface provided by the first application for exposing one or more recent contact options. As shown in fig. 7B, the user interface 71 may include: status bar 701, title bar 702, search box 703, one or more recent contacts options, menu bar 705.

The status bar 301 may refer to the status bar in FIG. 2A. The title bar 702 may refer to the title bar 302 in FIG. 3A. The search box 703 may refer to the search box 303 in fig. 3A. Menu bar 705 may refer to menu bar 305 in FIG. 3A.

The recent contacts options may include options for one or more contacts that the user has recently communicated in the first application, and the contacts options may include: a public number option, a user option, and a group option, among others. For example, the recent contacts options include an option 704A for contact "MAC" and an option 704B for contact "Kate".

In some embodiments, the sender 101 may display a contact option corresponding to a contact for which the sender 101 can transmit a file via "hishare" in an upper area (e.g., as shown in fig. 7B). In other embodiments, the sending end 101 may further display an identifier on a contact option corresponding to a contact, where the associated device is capable of transmitting the file through the "share" by the sending end 101, where the identifier is used to prompt the user that the file can be currently shared to the corresponding contact through the "share". Therefore, the problem that the user selects an improper contact person to cause failure in file sharing can be solved.

(2) In some embodiments, the sender 101 may directly display a contact option in one or more applications for the user to directly select a contact in an application to share a file.

Fig. 7C illustrates one implementation where the sender 101 directly displays the contact options in one or more applications. In some embodiments of the present application, fig. 6C-6D of the file transfer process shown in fig. 6A-6H described above may be replaced with fig. 7C.

Fig. 7C differs from fig. 6C in that the content in the small window differs. As shown in FIG. 7C, a widget 706 is displayed in the user interface 72, the widget 706 including: prompt 706A, one or more application icons, and contact options corresponding to the application icons. Wherein:

the prompt 706A is used to prompt the user to select a contact sharing file in the application. The reminder 706A may be a text message "please select a contact to share your file".

The one or more application icons may be any of:

a. icons of all applications installed on the sender 101 that can be used to share files.

b. Among the applications installed on the sender 101 and available for sharing files, a device associated with a contact can transmit an icon of the application of the file with the sender 101 through a "hashare". In some embodiments, the sender 101 may first determine whether a device associated with a contact in an installed application is capable of transmitting a file with the sender 101 through a "share", and if so, display an option corresponding to the application in the window 706. For the case that the sender 101 and other devices can transmit files through "share", reference is made to the related description in point 1 extension 1 of scenario one above. Therefore, the problem that the user selects an improper contact person to cause failure in file sharing can be avoided.

As shown in fig. 7C, the one or more application icons may include, for example, an icon 706B of "hi chat", an icon 706E of a mailbox.

An application icon may correspond to one or more contact options. The contacts corresponding to the one or more contact options are all: and the user contacts in the application program corresponding to the application program icon. The contacts corresponding to the one or more contact options may be: the associated device can transmit the contact of the file with the sending end 101 through the "share". Therefore, the problem that the user selects an improper contact person to cause failure in file sharing can be solved.

As shown in fig. 7C, the icon 706B of "hi chat" corresponds to the option 706C of contact "MAC", the option 706D of contact "Kate", and the icon 706E of mailbox corresponds to the option 706F of contact "mark".

The contact option may be used to monitor a user operation (e.g., a click operation, a touch operation, etc.), and the sending end 101 may send, in response to the user operation detected on the contact option, a file selected by the user to a contact corresponding to the contact option through "hashare" in a corresponding application.

In some embodiments, the sender 101 may further display a user interface for presenting communication records of the user and the contact in response to the user operation detected on the contact option, and display a file transfer record in the user interface. The user interface for displaying the communication records of the user and the contact may refer to the user interface 63 shown in fig. 6E-6H, and the file transfer record may refer to the file transfer record 314 in fig. 6E-6H, which is not described herein again.

Through the extension in the point (2), the sending end 101 may directly display the contact options in one or more applications, so that the user directly shares the file with the corresponding contact by selecting the contact option. This way is intuitive and simple for the user, and user experience can be improved.

2. Extension 2: related extensions to the UI embodiments shown in FIGS. 6B-6C

As shown in fig. 6B-6C, the sender 101 may display a menu 604 in the user interface 61 after the user selects a file. A "hashare file transfer" option 604A is included in menu 604. And, the "share file transfer" option 604A may receive a user operation, and the sender 101 may display a window 605 in response to the user operation, so that the user may select an application program for sharing a file.

The file is not limited to being shared through the "share file transfer" option shown in fig. 6B-6C, but may be shared through other service options. In some embodiments, the sender 101 may display a menu in the user interface that does not include the "share file transfer" option after the user selects a file. When a user shares a file to a contact through a function service option in the menu, the sending end can send the file to a device associated with the contact through the "share".

Fig. 7D-7E show the user interface implemented on the transmitting end under extension 2. In some embodiments of the present application, fig. 6B to 6C of the file sharing process shown in fig. 6A to 6H may be replaced with fig. 7D to 7E.

Fig. 7D exemplarily shows the sender 101 displaying the menu 707 in the user interface 71 after the user selects a file. Fig. 7D differs from fig. 6B in that the menu 707 of the user interface shown in fig. 7D does not include a "share file transfer" option, but rather includes an option 707A for sharing pictures and/or video.

Option 707A is used to listen to user operations (e.g., a click operation, a touch operation, a long press operation, etc.), and the sender 101 may display a window 708 in the user interface shown in fig. 7E in response to a user operation detected on option 707A. In the case where the "share" of the sender 101 has not yet been opened, the sender 101 may also open the "share" in response to the user operation detected on the option 707A.

As shown in fig. 7E, window 708 may include therein: reminder information 708A, one or more service options such as icon 708B, icon 708C, icon 708D, icon 708E. The prompt 708A is used to prompt the user to select a way to share the file. The application or protocol corresponding to the service option may support sharing the file selected by the user to other devices. In some embodiments, in response to a detected operation (e.g., a touch operation, a click operation) on a service option, the sender 101 may trigger a process of sharing the selected file to another device through an application or protocol corresponding to the service option. For example, in response to the operation detected on the icon 708B, the sender 101 may launch the application "hi chat", display a user interface as shown in fig. 6D or fig. 7B, detect an operation on a contact option in the user interface, and send the selected file to a contact-associated device corresponding to the contact option in response to the operation. The following embodiments refer to the device with which the contact is associated as the receiving end 102

Here, when the sender 101 sends the selected file to the receiver 102 through the application, the file may be sent according to any one of the following policies:

(1) after determining that the file can be transmitted with the receiving end 102 through the "share", the sending end 101 directly sends the picture and/or video selected by the user to the receiving end 102. If the sender 101 determines that the file cannot be transmitted with the receiver 102 through the "hashare", the picture and/or video selected by the user is sent to the receiver 102 through cellular technology such as 3G, LTE, 5G, or Wi-Fi technology.

(2) The sending end 101 determines the total size of the file selected by the user, and if the total size exceeds a first threshold, the file selected by the user is sent to the receiving end 102 through a "share". If the total size does not exceed the first threshold, the sending end 101 sends the file selected by the user to the receiving end 102 through cellular technology such as 3G, LTE, 5G, or Wi-Fi technology.

(3) The sending end 101 inquires whether the user sends the file selected by the user to the receiving end 102 through the "share", and when detecting that the user indicates a user operation of sending the selected file through the "share", the sending end sends the file selected by the user to the receiving end 102 through the "share". The transmitting end 101 may output a visual interface element, voice, etc. displayed on the display screen to inquire whether the user transmits the selected file to the receiving end 102 through "share". Such a policy may enable the sender 101 to send pictures and/or videos through "hashes" according to user needs.

(III) scenario III: scene for user to select group to share file

A group refers to a group of one or more contacts in an application. A user may communicate in a group with one or more contacts in the group.

Fig. 8A-8I exemplarily illustrate the user interface displayed by the sender 101 in scene three.

1. Fig. 8A-8B illustrate embodiments of a user selecting a group in an application.

The user interface 81 shown in fig. 8A is the same as the user interface 31 shown in fig. 3A, and reference may be made to the related description.

The user interface 82 shown in FIG. 8B is similar to the user interface 32 shown in FIG. 3B, except that the user interface 82 is used to present a communication record 802 for the associated user of the sender 101 and the contacts in the group "workgroup". As shown in fig. 8B, the user interface 82 includes: a current page indicator 801, a communication record 802 (the communication record shown in fig. 8B is empty), a control 803, and some other controls. Wherein:

the current page indicator 801 is used to indicate the current page, for example, the text message "workgroup" is used to indicate that the current page is one page of the associated user of the sender 101 and the group "workgroup" communication.

The control 803 may be used to listen to user operations, and the sending end 101 may display more functional service options in response to user operations acting on the control 803, such as an option for taking a picture, an option for sending the location where the sending end 101 is currently located, and so on.

2. 8C-8E illustrate embodiments where a user selects a group in an application and then selects a file to share to contacts in the group.

Fig. 8C illustrates a plurality of functional service options displayed by the sender 101 in response to a user operation detected on a control 803 in the user interface 82 illustrated in fig. 8B. As shown in fig. 8C, the plurality of feature service options includes a "share file transfer" option 804. The "share file transfer" option 804 may refer to the "share file transfer" option 310 in fig. 3C.

Fig. 8D illustrates a user interface 83 on the sender 101 for presenting one or more files stored by the sender 101. The user interface 83 may refer to the user interface 33 shown in fig. 3D.

FIG. 8E illustrates an embodiment where a user shares a selected file to a contact in the group "workgroup" in the first application. The user interface shown in FIG. 8E can be found in reference to FIG. 3E and associated description.

As shown in fig. 8E, the sender 101 may detect, on the user interface 83, a user operation for sharing the selected file to a contact in the group "work group", where the user operation may be an operation (e.g., a click operation, a touch operation) acting on the control 805, and in response to the user operation, the sender 101 may share the file selected by the user to a device associated with the contact in the group "work group" in the first application. When the sending end 101 shares the file selected by the user to the device associated with the contact in the group "workgroup" in the first application program, there may be several ways:

(1) the sender 101 sends the file selected by the user to the devices associated with all the contacts in the group "workgroup". For example, assuming that the group "workgroup" includes the contact "Kate" and the contact "Mac," the sender 101 may send the file selected by the user to the device associated with the contact "Kate" and the device associated with the contact "Mac.

(2) The sending end 101 sends the file selected by the user to the equipment associated with part of the contacts in the group "work group", and then the sending end 101 and the equipment that has received the file send the file to the equipment associated with the contacts that have not received the file in the group "work group". Optionally, the sending end 101 sends the file selected by the user to a device associated with a part of contacts in the group "workgroup", and then the device that has received the file (i.e., the device associated with a part of contacts) forwards the file to a device associated with a contact that has not received the file in the group "workgroup". In some embodiments, the device associated with the part of the contact is a device capable of transmitting a file with the sender 101 through a "hashare".

For example, assuming that the group "workgroup" includes the contact "Kate" and the contact "Mac", the sender 101 may first send the file selected by the user to the device associated with the contact "Kate" through the "hashare", and then send the received file to the device associated with the contact "Mac" through the device associated with the contact "Kate". In a specific example, the sender 101 may transmit the file through the "washre" by the device associated with the contact "Kate", but may transmit the file through the "washre" by the device not associated with the contact "Mac", and the file may be transmitted through the "washre" by the device associated with the contact "Kate" and the device associated with the contact "Mac".

The mode (2) can improve the efficiency of file sharing and improve the user experience.

3. Fig. 8F to 8I show a user interface for feeding back a file transfer status on the transmitting end 101.

After the sender 101 shares the file selected by the user to the device associated with the group "workgroup" contact in the first application program in response to the user operation of sharing the selected file to the contact in the group "workgroup", as shown in fig. 8F to 8I, the sender 101 may display a file transmission record 806 in a communication record 802 shown in the user interface 82.

As shown in fig. 8F-8I, file transfer record 806 may include: the head portrait of the associated user of the sender 101, the thumbnail images or names of one or more files that the user has selected, and a prompt 807.

The prompt 807 indicates the status of the transmission of the file selected by the user to the various contacts in the group "workgroup". The transmission state in which the file selected by the user is transmitted to each device may be any one of: a first transmission state, a second transmission state, a third transmission state, and a fourth transmission state. The meaning of each transmission state and the implementation form of the prompt information 807 corresponding to each transmission state can refer to the related description about the file transmission state in the embodiments of fig. 3F to 3I, and are not described herein again.

Similar to the extension in scenario one, the UI embodiments shown in fig. 8A-8I described above have corresponding related extensions. For example, in the user interface shown in fig. 8C, after determining that a device that can be associated with a contact in the group "workgroup" transmits a file through "share", the sender 101 may display a "share file transmission" option 804. For another example, in the user interface shown in fig. 8C, after determining that the device that can be associated with the contact in the group "workgroup" transmits the file through "share", the sender 101 may display a "share file transmission" option 804 that can receive the user operation. The implementation of these relevant extensions may refer to the relevant description in scenario one, and is not described here again.

The user interface implemented on the receiving end 102 is described below.

The receiving end 102 is an end that receives a file. In this embodiment of the application, the receiving end 102 may be a device associated with a contact selected by an associated user of the sending end 101 in the first application, for example, a device associated with a contact "Kate" in the embodiments of fig. 3A to fig. 3I. In other embodiments, the receiving end 102 may include a device for associating the contacts in the group selected by the associated user of the sending end 101 in the first application, for example, a device for associating each contact in the group "work group" in the embodiments of fig. 8A to 8I.

Fig. 9A-9D illustrate an exemplary user interface displayed on the receiving end 102.

Fig. 9A shows a notification window 901 displayed in the user interface 91 by the receiving end 102 after the transmitting end 101 transmits the file selected by the user to the receiving end 102. The user interface 91 may be a main interface. The notification window 901 can be used to notify the user that the sender 101 wants to transmit the file to the receiver 102 by "hisshare" and ask the user whether to receive the file. As shown in fig. 9A, the notification window 901 may include: application identification 901A, hints information 901B, control 901C, and control 901D. Wherein:

the application identifier 901A is used to indicate an application used when the associated user of the receiving end 101 shares a file. An implementation form of the application identification 901A may include an icon, text (e.g., text information "hi chat"), and the like.

The prompt 901B is used to indicate a user who initiates file sharing (e.g., user "Lisa") and file information (e.g., number, size, type, etc. of files). The prompt 901B may be implemented in text.

Control 901C can be used to listen to user actions. In response to the user operation detected on the control 901C, the receiving end 102 rejects to receive the file sent by the sending end 101.

Control 901D can be used to listen to user actions. In response to the user operation detected on control 901D, the receiving end 102 starts receiving the file sent by the sending end 101, and jumps to display the user interface 92 for displaying the communication record between the associated user of the receiving end 102 (e.g., contact "Kate") and the associated user of the sending end 101 (e.g., user "Lisa").

Fig. 9B-9D illustrate a user interface 92 for presenting a record of communication between users. The user interface may be provided by a first application program, where the first application program initiates a file sharing application program for an associated user of the sending end 101, and the first application program is also an application program used by the receiving end 102 to receive a file.

As shown in fig. 9B-9D, the user interface 92 may include: page indicator 902, communication record 903. Wherein:

page indicator 902 is used to indicate that the current page is used to present a record of communication between the associated user of receiver 102 (e.g., contact "Kate") and the associated user of sender 101 (e.g., user "Lisa").

The communication record 903 may include a file transfer record 904. The file transfer record 904 may include: the head portrait of the associated user of the sender 101, the thumbnail images or names of one or more files that the user has selected on the sender 101, and the prompt information 905. The prompt information 905 is used to prompt the user of the transmission status of the received file.

As shown in fig. 9B, the prompt 905 may be used to prompt the user that the transmission status of the file is the second transmission status.

As shown in fig. 9C, the prompt 905 may be used to prompt the user that the transmission status of the file is the third transmission status.

As shown in fig. 9D, the prompt 905 may be used to prompt the user that the transmission status of the file is the fourth transmission status.

The specific meanings of the second transmission state, the third transmission state, and the fourth transmission state, and the implementation form of the prompt information 905 corresponding to each transmission state can refer to the related descriptions about the file transmission state in the embodiments of fig. 3F to 3I, and are not described herein again.

Through the UI embodiments exemplarily shown in fig. 9A-9D, the receiving end 102 may prompt the associated user of the receiving end 102 (i.e., the contact selected by the user in the above embodiment) when the user shares the file, so that the associated user can select whether to receive the file.

In some other embodiments of the present application, the notification window 901 exemplarily shown in fig. 9A may also be displayed on other user interfaces instead of the main interface, for example, the notification window 901 may also be displayed on a setting interface, a video interface, and the like displayed by the sending end 101, which is not limited in this embodiment of the present application.

It should be noted that the notification window 901 shown in fig. 9A is not necessary, and in some embodiments, the receiving end 102 may not display the notification window 901, and when a sender 101 sends a file to the receiving end 102 via a "hashare", the receiving end 102 directly receives the file from the sender 101. It can be understood that whether the receiving end 102 displays the notification window 901 or not can be set autonomously by the associated user of the receiving end 102, for example, the associated user of the receiving end 102 can set in a setting interface provided by the receiving end 102.

In this embodiment, the control 901D in the notification window 901 displayed by the receiving end 102 may be referred to as a fourth operation option. The operation received by the receiving end 102 on the control 901D may be referred to as a ninth operation.

In this embodiment, the user interface (e.g., the user interface 92 shown in fig. 9B-9D) displayed by the receiving end 102 for displaying the communication records between users may be referred to as a seventh user interface.

The following embodiments describe a system architecture and a method for transferring files in an application provided by the embodiments of the present application.

First, a communication system 1000 for transferring files in an application is presented.

As shown in fig. 10A, the communication system 1000 may include: a plurality of electronic devices such as electronic device 1001, electronic device 1002, electronic device 1003, electronic devices 1005, …, electronic device 100n, and the like, a server 1004. Illustratively, the device associated with the Lisa of the user may be the electronic device 1001, the device associated with the Kate of the user may be the electronic device 1002, and the device associated with the Mac of the user may be the electronic device 1003.

The plurality of electronic devices include a transmitting end and a receiving end. The sending end is the end for initiating file sharing, and the receiving end is the end for receiving files.

In the following embodiments of the present application, an electronic device 1001 associated with the user Lisa is taken as a sending end, and an electronic device 1002 associated with the user Kate is taken as a receiving end. In the following embodiments, the electronic device 1001 may also be referred to as a transmitting end 1001, and the electronic device 1002 may also be referred to as a receiving end 1002.

The transmitting terminal 1001 may be the transmitting terminal 101 mentioned in the foregoing embodiments. The transmitting end 1001 may be implemented as the electronic device 100 exemplarily shown in fig. 1A and 1B. Specifically, the transmitting end 1001 has one or more of a Bluetooth (BT) module, an NFC module, and a WLAN module. The sending end 1001 may detect or scan a device near the sending end 1001 by one or more transmission signals of a Bluetooth (BT) module, an NFC module, and a WLAN module, so that the sending end 1001 may discover the device near the sending end 1001 (e.g., a nearby mobile phone, a tablet computer, etc.) by using one or more wireless communication technologies of bluetooth, NFC, or WLAN, establish a wireless communication connection with a receiving end 1002 of the device near the sending end, and share a file to the receiving end 1002 by using one or more wireless communication technologies of bluetooth or WLAN. Among other things, a Bluetooth (BT) module may provide solutions that include one or more of classic bluetooth (bluetooth 2.1) or Bluetooth Low Energy (BLE) bluetooth communication. The WLAN module may provide solutions that include one or more of Wi-Fi direct, Wi-Fi LAN, or Wi-Fi softAP WLAN communications.

The receiving end 1002 may be the receiving end 102 mentioned in the foregoing embodiments. The receiving end 1002 may be implemented as the electronic device 100 exemplarily shown in fig. 1A and 1B. Specifically, the receiving end 1002 has one or more of a Bluetooth (BT) module, an NFC module, and a WLAN module. The receiving end 1002 may receive or transmit a wireless signal through one or more of a Bluetooth (BT) module, an NFC module, and a WLAN module. Among other things, a Bluetooth (BT) module may provide solutions that include one or more of classic bluetooth (bluetooth 2.1) or Bluetooth Low Energy (BLE) bluetooth communication. The WLAN module may provide solutions that include one or more of Wi-Fi direct, Wi-Fi LAN, or Wi-Fi softAP WLAN communications.

The same application or applications, e.g., a first application, may be installed in both the sender 1001 and the receiver 1002. The application may be, for example, an instant messaging type application, a mailbox type application, or the like.

The server 1004 is a server for providing a service to a certain application installed in the sender 1001 and the receiver 1002, and for example, the server 1004 may be a server for providing a service to a first application. The server 1004 provides various services, such as a communication record backup service, a computing service, a connection service, and the like, to the sender 1001 and the receiver 1002 through application communication.

The server 1004 may store in association a user identification of a user who registered the first application, and a device identification of an associated device of the user. After the user registers the first application program, the user can log in the first application program on the equipment by using the user identification and the password of the user. The associated device of the user refers to a device used when the user logs in the application at present.

The user identification may include, but is not limited to: account number, avatar, nickname, name, face image, Identity (ID), etc.

The device identification may include a Media Access Control (MAC) address, an Internet Protocol (IP) address, etc. that may indicate the identification of the unique device.

Referring to table 1, table 1 illustrates several user identities and device identities stored in association in server 1004.

User identification	Device identification
		Account number "Lisa"	Device identification of electronic device 1001
Account number "Kate"	Device identification of electronic device 1002
		Account number "Mac"	Device identification of electronic device 1003

TABLE 1

The associated user a.lisa of the sender 1001 may log in to the application on the sender 1001 using the user identity and password when registering the application. Obviously, after the associated user a.lisa of the sending end 1001 logs in the application, the sending end 1001 may know that the user identifier of the associated user a.lisa in the application is "Lisa". In addition, the sending end 1001 may also obtain the user identifier of the contact of its associated user in the application from previously pre-stored information or from the server 1004, for example, one contact of the associated user a.lisa of the sending end in the application is j.kate, and the user identifier of the contact j.kate is "Kate".

Kate, the associated user of the receiving end 1002, may also log into the application on the receiving end 1002 using the user id and password when registering the application. Obviously, after the associated user j.kate of the receiving end 1002 logs in the application, the receiving end 1002 can know that the user identifier of the associated user j.kate in the application is "Kate". In addition, the receiving end 1002 may also obtain the user identifier of the contact of its associated user in the application from the previously pre-stored information or from the server 1004, for example, one contact of the associated user j.kate of the receiving end in the application is a.lisa, and the user identifier of the contact a.lisa is "Lisa".

The connection between the sending end 1001 and the server 1004 may be through cellular mobile communication technology such as 3G, LTE, 5G, LAN or WAN communication technology, which may facilitate the server 1004 to forward the data sent by the sending end 1001 to the receiving end 1002.

The connection between the receiving end 1002 and the server 1004 may be through a LAN or WAN communication technology, which may facilitate the server 1004 to forward data sent by the receiving end 1002 to the sending end 1001.

In this embodiment, the sending end 1001 may discover nearby devices through one or more wireless communication technologies of bluetooth, NFC, and WLAN, and the nearby devices may include, for example, the electronic device 1002, the electronic device 1003, the electronic devices 1005 and …, the electronic device 100n, and the like. Then, the sending end 1001 may determine, in a nearby device, a device associated with the contact selected by the user in the application, that is, determine a receiving end. Here, if the contact selected by the user is "Kate", the electronic device 1002 associated with the contact "Kate" is the receiving end, and the other devices, such as the electronic device 1003, the electronic devices 1005, …, and the electronic device 100n, are not the receiving ends. Then, the sending end 1001 may send the file selected by the user to the receiving end 1002 through "share" in the first application, that is, the sending end 1001 may share the file selected by the user to a device associated with the contact, that is, the receiving end 1002, through one or more wireless communication technologies of bluetooth, NFC, and WLAN. In this way, the sending end 1001 and the receiving end 1002 can share the file to other nearby devices quickly during application, cellular data traffic of the receiving end and the sending end is not consumed, and the load of the server 1004 is reduced. Moreover, the size of the file shared by the sender 1001 to the receiver 1002 is not limited, that is, the sender 1001 may share a larger file to the receiver 1002.

It is to be understood that the configuration shown in the present embodiment does not constitute a specific limitation to the communication system 1000. In other embodiments of the present application, communication system 1000 may include more or fewer devices than those shown. For example, other cell phones, tablet computers, other server(s), etc. with one or more of a Bluetooth (BT) module, a WLAN module may also be included in the communication system 1000.

A method for transferring a file in an application implemented in the first point scenario one is described below based on the communication system 1000.

First, the general flow of the method for transferring a file in an application in scenario one is described. The deploying may comprise:

step 1: the sending end 1001 displays a first user interface, and a communication record of the associated user of the sending end 1001 and the selected contact in the first application can be displayed in the first user interface.

The first user interface may be a user interface provided by the first application. The first application program may be, for example, an instant messaging type application, a mailbox type application, or the like. The first user interface is used for displaying the communication records of the associated user of the sending terminal 1001 and the selected contact in the first application program. The first user interface may be seen as user interface 32 in fig. 3B.

Step 2: the sender 1001 may detect an operation for viewing a file stored in the sender 1001 in the first user interface, and display a second user interface for presenting one or more files stored by the sender 1001 in response to the operation for viewing the file stored in the sender 1001. The second user interface may be seen in the user interface 33 in fig. 3D.

In a scenario one provided in the embodiment of the present application, the "share" file sharing option 310 included in the first user interface may be referred to as a first operation option. An operation for viewing a file stored in the sender 1001, i.e., an operation received by the sender 1001 on the first operation option, may be referred to as a first operation.

And step 3: the sending end 1001 may detect a user operation of sharing the selected file to the contact in the second user interface, and in response to the user operation of sharing the selected file to the contact, the sending end 1001 sends the selected file to the associated device (i.e., the receiving end 1002) of the contact through "hishare". The process of sending the selected file to the receiving end 1002 by the sending end 1001 through "hishare" does not go entirely through the server 1004.

In scenario one provided by the embodiment of the present application, the selected file may be referred to as a first file. The second user interface may include a first identifier corresponding to the first file and a second identifier corresponding to a second file stored in the sender 1001.

In the first scenario provided in the embodiment of the present application, an operation of selecting a file by a user, that is, an operation received by the sending end 1001 on the first identifier, may be referred to as a second operation.

In a scenario one provided by the embodiment of the present application, a user operation of sharing a selected file to a contact may be referred to as a third operation. In some embodiments, the option 312B included in the second user interface may be referred to as a second operational option. The third operation may be an operation received by the transmitting end 1001 on the second operation option.

As can be seen, when detecting a scene in which a user shares a file in an application, the sending end 1001 may send the file to the receiving end 1002 through a "hashare". The process of transferring files to other devices nearby via the "hashare" may not rely on a communication connection between the sender 1001 and the server. Thus, the sending end 1001 can quickly transmit the file to other surrounding devices in application, the use experience of a user is optimized, when the sending end 1001 uses cellular data flow, the cellular data flow consumed by the sending end 1001 can be saved, and the load of a server is reduced. Moreover, the size of the file shared by the sender 1001 to the receiver 1002 is not limited, that is, the sender 1001 may share a larger file to the receiver 1002.

In the following, a method for transferring a file in an application in scenario one is described in detail.

Fig. 10B shows a flow of a method for transferring a file in an application in scenario one. As shown in fig. 10B, the method may include:

S1001-S1002: the "share" is turned on in advance.

S1001: the sender 1001 may detect an operation for turning "hishare".

S1002: in response to the detected operation for opening "share", the sender 1001 opens "share".

In some embodiments, as can be known in reference to the foregoing fig. 2A-2B embodiments, the operation for turning on the "share" may be a click operation, a touch operation, or the like of the switch control 202A, which is detected by the sender 1001 and acts on the "share" in the window 202.

Specifically, turning on "share" may refer to turning on one or more of a bluetooth module, an NFC module, and a WLAN module of the transmitting end 1001. After the "hishare" is turned on, the sender 1001 may discover devices near the sender 1001 by one or more technologies of NFC, bluetooth, Wi-Fi direct (e.g., Wi-Fi p2p), Wi-Fi softAP, and Wi-Fi LAN.

In some embodiments, S1001-S1002 may be optional steps, and the user may also trigger the sender 1001 to start "hishare" after selecting a contact for sharing a file in the application. That is, it may not be necessary to turn "hishare" on in advance.

S1003: the sender 1002 launches the first application and displays the first user interface. The first user interface may display a communication record of the associated user of the sender 1002 and the selected contact in the first application.

The first user interface may be a user interface provided by the first application. The first application program may be, for example, an instant messaging type application, a mailbox type application, or the like.

The first user interface is used for displaying the communication records of the associated user of the sending end 1002 and the selected contact in the first application program. Exemplary implementations of the first user interface may refer to the user interface 32 shown in fig. 3B or 3C, the user interface 32 shown in fig. 4B or 4C, the user interface 32 shown in fig. 4D or 4E or 4F, the user interface 52 shown in fig. 5B or 5C.

In some embodiments, the first user interface may be displayed by:

first, the sending end 1001 displays a user interface provided by a first application and displaying one or more contact options, and an exemplary implementation of the user interface may refer to the user interface 31 shown in fig. 3A or the user interface 51 shown in fig. 5A.

Then, the sending end 1001 detects a user operation for selecting a contact, and the operation for selecting the contact may be: a click operation, a touch operation and the like which are detected by a sending terminal 1001 and act on a certain contact option, wherein a contact corresponding to the contact option is a selected contact;

finally, the transmitting end 1001 displays a first user interface in response to the detected operation for selecting a contact. The first user interface displays the communication record of the associated user of the sending terminal 1001 and the selected contact in the first application.

S1004: the sender 1001 starts "share" while displaying the first user interface. S1004 is an optional step, and the user may also trigger the sending end 1001 to start "share" in advance, which may refer to S1001-S1002. The user may then trigger the sender 1001 to turn "share" again, as shown in S1006.

S1005: the sender 1001 may detect an operation for viewing a file stored in the sender 1001 in the first user interface.

The operation for viewing the file stored in the sender 1001 may be, for example: a user operation (for example, a click operation, a touch operation, and the like) acting on the "share file transfer" option 310 in the user interface 32 shown in fig. 3C, a user operation (for example, a click operation, a touch operation, and the like) acting on the "share file transfer" option 310 in the user interface 32 shown in fig. 4F, and a user operation (for example, a click operation, a touch operation, and the like) acting on the "photo" option 501 in the user interface 52 shown in fig. 5C.

S1006: in response to a detected operation to view a file stored in the sender 1001, the sender 1001 turns "hashare". S1006 is an optional step, and the user may also trigger the sending end 1001 to start "share" in advance, refer to S1001-S1002, or refer to S1004.

S1007: in response to an operation detected in the first user interface to view a file stored in the sender 1001, the sender 1001 displays a second user interface. The second user interface displays: the identity of one or more files stored by the sender 1001.

The second user interface is used to present one or more files stored by the sender 1001. The second user interface displays the identification of one or more files stored by the sender 1001. The files stored on the sender 1001 may include, but are not limited to: pictures, audio, video, documents, links, and the like. The identification of a file may be a thumbnail, name, etc. of the file.

The second user interface may be implemented in a form that is referenced to the user interface 33 shown in fig. 3D and the user interface 53 shown in fig. 5D. An implementable form of identification of the file may refer to a thumbnail or name of the file in the file area 313 shown in fig. 3D, a thumbnail of the file in the file area 504 shown in fig. 5D.

S1008: under the condition that "hishare" is turned on, the sender 1001 may discover nearby devices, such as the electronic device 1001, the electronic device 1002, the electronic device 1003, the electronic device 1005 …, and the electronic device 100 n. n is a positive integer. The following details will be described with respect to specific implementations of the sender 1001 to discover nearby devices, and will not be described herein again.

The embodiment of the present application does not limit the sequence of S1008 and S1007, and the sending end 1001 may execute S1007 and S1008 at the same time, or execute S1007 first, or execute S1008 first.

S1009: the transmitting end 1001 determines devices associated with the contact among the discovered nearby devices, i.e., determines the receiving end 1002. The transmitting end 1001 determines a specific implementation of the receiving end 1002 in a nearby device, and the following content will be described in detail, which is not described herein again.

S1010: the sender 1001 may detect a user operation of sharing the selected file to the contact in the second user interface.

Here, the selected file may include one or more of: selected pictures, selected documents, selected web pages, selected audio, selected links, and the like.

The user operation for sharing the selected file to the contact may be, for example, a user operation acting on control 312B in fig. 3E, a user operation acting on control 503B in fig. 5E, or the like.

The sending end 1001 determines the selected file manner and the user operation of sharing the selected file to the contact, which may refer to the related description in the UI embodiment and will not be described herein again.

S1011-S1016: in response to a user operation of sharing a selected file to a contact, the sending end 1001 sends the selected file to an associated device (i.e., the receiving end 1002) of the contact through "share". The process of sending the selected file to the receiving end 1002 by the sending end 1001 through "hishare" does not go entirely through the server 1004.

S1011: the transmitting end 1001 may establish a communication connection with the receiving end 1002.

The sender 1001 may establish a bluetooth communication connection, a Wi-Fi direct communication connection (e.g., a Wi-Fi p2p connection), a SoftAP connection, etc. with the receiver 1002. Specifically, the sending end 1001 may send a connection establishment request to the receiving end 1002 according to the device identifier of the receiving end 1002, and the receiving end 1002 may return a response that the connection establishment is successful to the sending end 1001.

The information required when the sending end 1001 and the receiving end 1002 establish a connection may be negotiated by the sending end and the receiving end after determining the devices associated with the contact in S1008-S1009. For example, when the sender and the receiver establish a Wi-Fi direct communication connection in S1011, the sender 1001 may discover nearby devices through bluetooth in S1008, determine the receiver 1002 in S1009, establish a bluetooth communication connection with the receiver 1002, and send a Service Set Identifier (SSID) and a password, which are required to establish the Wi-Fi direct communication connection, to the receiver 1002 through the bluetooth communication connection. The receiving end 1002 is connected to the transmitting end 1001 according to the SSID and the password, so that the receiving end 1001 and the transmitting end 1002 can successfully establish the Wi-Fi direct communication connection.

In some embodiments, S1011 is an optional step. If the transmitting end 1001 and the receiving end 1002 are in the same LAN, the transmitting end 1001 may directly transmit the selected file to the receiving end 1002 according to the device identifier of the receiving end 1002, without establishing a communication connection.

That is, in the case that the transmitting end 1001 transmits the selected file through one or more wireless communication technologies of bluetooth, Wi-Fi direct (such as Wi-Fi p2p), and Wi-Fi softAP, the transmitting end 1001 needs to establish a communication connection with the receiving end 1002 after determining the receiving end 1002. In the case where the transmitting end 1001 transmits the selected file through the Wi-Fi LAN wireless communication technology, the transmitting end 1001 and the receiving end 1002 may directly perform the file transmission because they are already in the same LAN.

S1012: the sender 1001 may send a file sharing request to the recipient 1002. The file sharing request is used to request the receiving end 1002 to receive the file shared by the sending end 1001.

In some embodiments, the sending end 1001 may send the file sharing request to the receiving end 1002 through an established communication connection (such as a bluetooth communication connection and/or a Wi-Fi direct communication connection), or send the file sharing request to the receiving end 1002 through a LAN or NFC.

In some embodiments, the sender 1001 may send the file sharing request to the server 1004 through a communication connection with the server 1004, and the server 1004 sends the file sharing request to the receiver 1002. In an embodiment, the file sharing request may carry a user identifier of a selected contact, and the server 1004 may determine, according to the user identifier of the selected contact, a device identifier stored in association with the user identifier of the contact, that is, a device identifier of the receiving terminal 1002, in data stored in association with the server 1004, so as to send the file sharing request to the receiving terminal 1002. In another embodiment, the file sharing request may carry a device identifier of the receiving end 1002, and the server 1004 may directly send the file sharing request to the receiving end 1002 according to the device identifier of the receiving end 1002.

The server sends the file sharing request, so that the server 1004 can acquire and record the file transmission event between the sending end 1001 and the receiving end 1002. When the sending end 1001 sends a file sharing request through the server 1004, the file sharing request may also carry indication information. The indication information may be used to indicate the size, type, etc. of the shared file.

S1013: the transmitting end 1001 displays the prompt information.

Specifically, the prompt message may prompt the transmitting end 1001 of the transmission status of the current file of the associated user. At this time, the prompt message is used to prompt the transmitting end 1001 that the transmission status of the current file of the associated user is the first transmission status. The first transmission state may refer to the selected file waiting to be received by the receiving end 1002.

An exemplary implementation of the hint information may refer to hint information 315 in FIG. 3F, and hint information 506 in FIG. 5F.

S1014: after receiving the file sharing request sent by the sender 1001, the receiver 1002 may display a notification window. The notification window is used to inquire whether an associated user of the receiving terminal 1002 accepts the file sharing request of the sending terminal 1001, that is, whether the user receives the selected file. An exemplary implementation of the notification window may refer to the notification window 901 in fig. 9A.

S1015: the receiving end 1002 returns a share request response to the transmitting end 1001 after detecting a user operation for accepting a file share request of the transmitting end 1001 in the notification window.

The user operation for receiving the file sharing request of the sender 1001 may be an operation acting on a control 901D in the window 901 of fig. 9A.

In some embodiments, the receiving end 1002 may send a share request reply to the sending end 1001 through an established communication connection (such as a bluetooth communication connection and/or a Wi-Fi direct communication connection), or send the share request reply to the sending end 1001 through a LAN or NFC. In some embodiments, the receiving end 1002 may send the sharing request reply to the server 1004 through a communication connection with the server 1004, and the server 1004 sends the sharing request reply to the sending end 1001.

In some embodiments, S1015 may not be necessary. That is to say, when a sending end 1001 sends a file sharing request to a receiving end 1002, the receiving end 1002 may directly return a sharing request response, and may receive a file from the sending end 1001 without user intervention.

S1016: after receiving the response of the sharing request from the receiving end 1002, the sending end 1001 sends the selected file to the receiving end 1002 through "share". The process of the sender 1001 sending the selected file to the receiver 1002 through the "hashare" does not go all the way through the server.

Specifically, the sending end 1001 may send the file selected by the user to the receiving end 1002 through an established communication connection (such as a bluetooth communication connection and/or a Wi-Fi direct communication connection), or through a LAN. In this way, the process of transmitting the file to other nearby devices, namely, the receiving end 1002, by the transmitting end 1001 in the application may not depend on the communication connection between the transmitting end 1001 and the server 1004, and the file may be quickly transmitted to the receiving end 1002 in the application, so as to optimize the user experience, save the cellular data traffic consumed by the transmitting end 1001, and reduce the load of the server. Moreover, since the process of the sending end 1001 transmitting the file to another device nearby, i.e. the receiving end 1002, in the application does not depend on the communication connection between the sending end 1001 and the server 1004, the size of the file shared by the sending end 1001 to the receiving end 1002 is not limited, that is, the sending end 1001 can share a larger file to the receiving end 1002.

In some embodiments, the sending end 1001 may also simultaneously send the file selected by the user to the receiving end 1002 in conjunction with an established communication connection (e.g., a bluetooth communication connection and/or a Wi-Fi direct communication connection)/LAN, and a communication connection between the sending end 1001 and the server. Therefore, the file can be transmitted in various modes, and the file transmission efficiency is improved. In a specific embodiment, the sending end 1001 may simultaneously combine the established communication connection (such as bluetooth communication connection and/or Wi-Fi direct communication connection)/LAN when the file selected by the user is greater than the second threshold, and the communication connection between the sending end 1001 and the server sends the file selected by the user to the receiving end 1002. Further, the sending end 1001 may divide the file selected by the user into two parts, send one part of the file through an established communication connection (such as a bluetooth communication connection and/or a Wi-Fi direct communication connection)/LAN, and send the other part of the file through a communication connection with the server. The embodiment of the present application does not limit the manner in which the transmitting end 1001 divides the file into two parts.

In this embodiment, the sending end 1001 may Send the selected file to the receiving end 1002 through an aid id call function (e.g., PreSend Send).

S1012-S1015 may not be necessary. That is, the sending end 1001 may directly send the selected file to the device associated with the contact after detecting the user operation of sharing the selected file to the contact.

S1017-S1019: and feeding back the file transmission state.

Referring to S1017, the receiving end 1002 may display the prompt information during the file transmission process, or may display the prompt information after the file transmission is finished. The prompting message may be used to prompt the receiving end 1002 for the transmission status of the file for the associated user (i.e., the selected contact).

Referring to S1018, the receiving end 1002 may feed back the transmission state of the file to the transmitting end 1001 during the file transmission, or may feed back the transmission state of the file to the transmitting end 1001 after the file transmission is finished.

Referring to S1019, after receiving the transmission status fed back by the receiving end 1002, the sending end 1001 may also display a prompt message to prompt the sending end 1001 of the transmission status of the associated user file.

In this embodiment of the application, the sending end 1001 may obtain the transmission state of the file by calling a function (e.g., onTransStateChange) through the aid id. The receiving end 1002 may obtain the transmission state of the file by using an aid l call function (e.g., oncorgress).

In some embodiments, the transmission status of a file may include, but is not limited to:

the second transmission state may refer to the selected file being transmitted to the receiving end 1002.

The third transmission status may refer to the selected file being successfully transmitted to the receiving end 1002.

The fourth transmission status may refer to that the selected file was not successfully transmitted to the receiving end 1002.

In some embodiments, the prompt displayed by the receiving end 1002 may refer to: hint information 905 in the file transfer record 903 as exemplarily shown in one or more of fig. 9B-9D. For the prompt information 905, reference may be made to related contents and extensions in the embodiments of fig. 9B to 9C, which are not described herein again.

In some embodiments, the prompt information displayed by the sending end 1001 may refer to: a hint 315 in a file transfer record 314 as exemplarily shown in one or more of fig. 3G-3I, or a hint 506 in a file transfer record 505 as exemplarily shown in one or more of fig. 5G-5I. For the prompt information 315, reference may be made to related contents and extensions in the embodiments of fig. 3G to fig. 3I, which are not described herein again. For the prompt information 506, reference may be made to the related contents and extensions in the embodiments of fig. 5G to 5I, which are not described herein again.

In the first scenario provided in the embodiment of the present application, the prompt information displayed by the sending end 1001 may be displayed in a third user interface. An exemplary implementation of this third user interface may refer to the user interface shown in any of fig. 3F-3I, 5F-5I.

The transmission state of the file is not limited to be prompted by displaying the prompt information on the display screen, the sending end 1001 and the receiving end 1002 may also stop other manners to prompt the transmission state of the file, for example, the sending end may also play voice to prompt, and the like.

S1017-S1019 may not be necessary. That is, both the receiving end and the transmitting end may not have to feed back the transmission status of the file.

In S1008, the transmitting end 1001 finds several implementations of nearby devices:

mode 1. discovery of nearby devices using bluetooth wireless communication technology

Specifically, devices (e.g., the electronic device 1002, the electronic device 1003, etc.) near the transmitting end 1001 may perform bluetooth broadcast, that is, transmit a bluetooth broadcast packet; the sender 1001 may perform bluetooth scanning to scan for broadcast packets broadcast by nearby devices.

In some embodiments, the broadcast packet may carry a device identification of the device. For example, the bluetooth broadcast packet sent by the electronic device 1002 carries the device identifier of the electronic device 1002, and the bluetooth broadcast packet sent by the electronic device 1003 carries the device identifier of the electronic device 1003. The transmitting end 1001 may discover nearby devices, for example, a nearby electronic device 1002 and an electronic device 1003, according to the device identifiers in the scanned broadcast packet.

In some embodiments, in addition to the device identifier, the broadcast packet may also carry a user identifier of an associated user of the device in an application installed in the device. For example, when the first application is installed on the electronic device 1002, the broadcast packet sent by the electronic device 1002 carries the user identifier of the user "Kate" in the first application. When the electronic device 1003 is installed with a first application program and a second application program (e.g., mailbox application program), a broadcast packet sent by the electronic device 1003 carries a user identifier of the user "Mac" in the first application program, for example, an account "Mac", and a user identifier of the user "Mac" in the second application program, for example, the account "Mac". The user id in the broadcast packet may be used by the transmitting end 1001 to determine a device associated with the selected contact, i.e., a receiving end, among nearby devices, which will be described in detail in the following embodiments.

Mode 2. discovery of nearby devices using Wi-Fi direct wireless communication technology

In some embodiments, the sender 1001 may broadcast a probe request (probe request) outward. After listening to the probe request, a device (e.g., a printer) in the vicinity may respond to a probe response (probe response) to notify its existence. The probe response (probe response) may carry an apparatus identifier of the apparatus, and may also carry a user identifier of an associated user of the apparatus in an application installed on the apparatus. Here, the device id may refer to a device id in the bluetooth broadcast packet in the manner 1, and the user id may refer to a user id in the bluetooth broadcast packet in the manner 1.

In other embodiments, nearby devices (e.g., cell phones, tablets, etc.) may periodically send out Beacon (Beacon) frames. The transmitting end 1001 may discover nearby devices by listening to Beacon frames transmitted by the nearby devices. The Beacon frame may carry an equipment identifier of the equipment, and may also carry a user identifier of an associated user of the equipment in an application installed in the equipment. Here, the device id may refer to a device id in the bluetooth broadcast packet in the manner 1, and the user id may refer to a user id in the bluetooth broadcast packet in the manner 1.

That is, the transmitting end 1001 may actively discover nearby devices or passively discover nearby devices using Wi-Fi direct wireless communication technology.

Mode 3. discover devices in the same Wi-Fi LAN

In some embodiments, the sending end 1001 may determine the IP address range of the LAN according to the IP address and the subnet mask of the LAN itself, and then may discover the devices in the LAN by means of unicast polling. Without being limited thereto, the transmitting end 1001 may also discover devices in the LAN by broadcasting messages or multicasting messages in the LAN. After receiving the broadcast message, the multicast message, or the polling message, the devices in the LAN may reply their own information to the transmitting end 1001. The information may carry an equipment identifier of the equipment, and may also carry a user identifier of an associated user of the equipment in an application installed in the equipment. Here, the device id may refer to a device id in the bluetooth broadcast packet in the manner 1, and the user id may refer to a user id in the bluetooth broadcast packet in the manner 1.

The method for discovering the nearby devices by the sending end 1001 is not limited to the above-mentioned several ways, and in practical application, the sending end 1001 may also discover the nearby devices based on wireless communication technologies such as bluetooth, Wi-Fi direct, Wi-Fi LAN, or NFC, and the like, which is not limited in this embodiment of the present application.

In this embodiment, after discovering a nearby device in any one of the above manners, the sender 1001 may call a function (e.g., an online device focus) through an Android Interface Definition Language (AIDL), so as to determine a device associated with a contact in the nearby device.

In S1009, the sending end 1001 determines the devices associated with the contact in the discovered nearby devices, that is, determines several implementations of the receiving end 1002:

mode 1. the transmitting end 1001 determines the receiving end according to the user identification transmitted by the nearby device

In some embodiments, a nearby device may send a user identification of the device's associated user in an application installed by the device to the sender 1001. The manner of sending may refer to the related description of the foregoing embodiment with respect to S1008. The sending end 1001 may find the same user id as the user id of the selected contact in the received user ids. And if the user identification which is the same as the user identification of the selected contact is found, determining the equipment which sends the user identification as a receiving end.

For example, assuming that the user identifier of the selected contact is the account "Kate", the sending terminal 1001 may determine that the electronic device 1002 sending the user account "Kate" is the receiving terminal.

Mode 2, the sending end 1001 determines the receiving end through the server 1004 corresponding to the first application program

In some embodiments, the sender 1001 may send a request to the server 1004, where the request carries the user identifier of the selected contact, and the request is used to query the device identifier of the device used by the contact when currently logging in the first application. Since the user identifier of the user registered with the first application and the device identifier of the device associated with the user are stored in association with the server 1004, the server 1004 may find the device identifier stored in association with the user identifier according to the user identifier carried in the request. The server 1004 may then send the found device identification to the sender 1001. After receiving the device identifier sent by the server, the sending end 1001 determines the device represented by the device identifier as a receiving end.

For example, assuming that the user identifier of the selected contact is the account "Kate", the sending end 1001 may send a request carrying the account "Kate" to the server. After receiving the request, the server 1004 may find the device identifier corresponding to the account "Kate" according to the data stored in table 1, and send the device identifier to the sending end 1001. The transmitting end 1001 may determine the electronic device 1002 characterized by the device identifier as a receiving end.

In one specific example, the user identification may be Huawei ID. In any of the above determination manners, the Huaqi ID may not be directly transmitted between devices, but may be transmitted between devices through a hash value (hash values) of the Huaqi ID. The hash value of the Huawei ID is obtained by calculating the Huawei ID by using a hash function (hash function) by the equipment.

A method for transferring a file in an application implemented in the second point scenario (second) is described below based on the communication system 1000.

First, the general flow of the method for transmitting a file in an application in scenario two is described. The deploying may comprise:

step 1: the sender 1001 displays a fourth user interface, and the fourth user interface is used for displaying one or more files stored by the sender 1001.

The fourth user interface may be a user interface provided by the second application. The second application may be, for example, a gallery, a file manager, a document manager, or the like. The fourth user interface may be seen in the user interface 61 shown in fig. 6A or 6B.

Step 2: the sender 1001 may detect a user operation for sharing the selected file in the fourth user interface, and display one or more application options in response to the user operation for sharing the selected file.

In scenario two provided in the embodiment of the present application, the selected file may be referred to as a third file. The fourth user interface includes a third identifier and a fourth identifier, where the third identifier corresponds to a third file, and the fourth identifier corresponds to a fourth file stored in the sending terminal 1001.

In the second scenario provided in this embodiment of the application, an operation of selecting the third file by the user, that is, an operation received by the sending end 1001 on the third identifier, may be referred to as a fifth operation.

In a scenario two provided in the embodiment of the present application, a user operation for sharing a selected file may be referred to as a sixth operation.

In a second scenario provided in this embodiment of the application, the "share file transfer" option 604A in the fourth user interface may be referred to as a third operation option, and the sixth operation may be an operation received by the sender 1001 on the third operation option.

And step 3: the sending end 1001 may detect a user operation acting on an application option, and in response to the user operation acting on the application option, display a fifth user interface, where the fifth user interface includes one or more contact options.

In the second scenario provided in the embodiment of the present application, the user operation acting on the application option may be referred to as a seventh operation. The application option corresponds to a first application.

The fifth user interface may be a user interface provided by the first application. The first application program may be, for example, an instant messaging type application, a mailbox type application, or the like. The fifth user interface may be seen in the user interface 62 shown in FIG. 6D or the user interface 71 shown in FIG. 7B.

And 4, step 4: the sender 1001 may detect a user operation acting on a contact option in the fifth user interface, and in response to the user operation acting on the contact option, the sender 1001 sends the selected file to the associated device (i.e., the receiver 1002) of the contact corresponding to the contact option through "hishare". The process of sending the selected file to the receiving end 1002 by the sending end 1001 through "hishare" does not go entirely through the server 1004.

In the second scenario provided in the embodiment of the present application, the user operation acting on the contact option may be referred to as an eighth operation.

In some embodiments, the sender 1001 may also display a sixth user interface in response to the user action on the contacts option. The sixth user interface includes: the communication records of the first user and the second user in the first application program and prompt information, wherein the prompt information is used for indicating the transmission state of the third file.

As can be seen, when detecting a scene in which a user shares a file in an application, the sending end 1001 may send the file to the receiving end 1002 through a "hashare". The process of transferring files to other devices nearby via the "hashare" may not rely on a communication connection between the sender 1001 and the server. Therefore, the sending end 1001 can quickly transmit the file to other surrounding devices in application, the use experience of a user is optimized, the cellular data flow consumed by the sending end 1001 can be saved, and the load of the server is reduced. Moreover, since the process of the sending end 1001 transmitting the file to another device nearby, i.e. the receiving end 1002, in the application does not depend on the communication connection between the sending end 1001 and the server 1004, the size of the file shared by the sending end 1001 to the receiving end 1002 is not limited, that is, the sending end 1001 can share a larger file to the receiving end 1002.

Next, a method for transmitting a file in an application in scenario two is described in detail.

Fig. 10C shows a flow of a method for transferring a file in an application in scenario two. As shown in fig. 10C, the method may include:

S1101-S1102: the "share" is turned on in advance. Reference may be made specifically to S1001-S1002 in the method embodiment of fig. 10B.

S1103: the electronic equipment displays a fourth user interface, wherein: the identity of one or more files stored by the sender 1001.

The fourth user interface may be provided by the second application. The fourth user interface is used to present one or more files stored by the sender 1001. The fourth user interface displays the identification of one or more files stored by the sender 1001. The files stored on the sender 1001 may include, but are not limited to: pictures, audio, video, documents, links, and the like. The identification of a file may be a thumbnail, name, etc. of the file.

The fourth user interface may be implemented in a form that is referenced to the user interface 61 shown in fig. 6A or 6B, and the user interface 73 shown in fig. 7D. An implementable form of identification of a file may refer to a thumbnail or name of the file in the file area 603 shown in fig. 6A.

S1104: the sender 1001 may detect an operation for sharing the selected file in the fourth user interface.

The selected files may include one or more of: selected pictures, selected documents, selected web pages, selected audio, selected links, and the like.

An exemplary implementation of an operation for sharing a selected file may include: a user operation acting on a control 604A in the user interface 61 shown in fig. 6B, and a user operation acting on a control 707A in the user interface 73 shown in fig. 7D.

The manner in which the sending end 1001 determines the selected file and the operation for sharing the selected file may refer to the related description in the foregoing UI embodiment, and details are not described here again.

S1105: in response to the detected operation for sharing the selected file, the sender 1001 turns "share". S1105 is an optional step, and the user may also trigger the sender 1001 to turn on "share" in advance, refer to S1101-S1102.

S1106: in response to the detected operation for sharing the selected file, the sender 1001 displays one or more application options in a fourth user interface.

The application corresponding to the one or more application options displayed in the fourth user interface may be all applications installed on the sending end 1001 and available for sharing a file, or an application that a device associated with a contact in the applications installed on the sending end 1001 and available for sharing a file can transmit a file with the sending end 1001 through a "hishare".

An exemplary implementation of displaying one or more application options in the fourth user interface may refer to the application options in window 605 shown in FIG. 6C or FIG. 7A.

S1107: the sender 1001 may detect an operation acting on an application option,

s1108: the transmitting end 1001 displays a fifth user interface in response to the operation acting on the application options, the fifth user interface displaying one or more contact options.

The fifth user interface may be a user interface provided by an application corresponding to the application option, such as the first application. An exemplary implementation of the fifth user interface may refer to the user interface 62 shown in fig. 6D or the user interface 71 shown in fig. 7B.

The one or more contact options in the fifth user interface may include contact options that, among contacts of the first application program, associated users of the sending end 1001 and the associated devices may respectively correspond to contacts of the sending end 101 transmitting files through "hishare", may also include contact options that, in the first application program, all contacts of the associated users of the sending end 1001 respectively correspond to contacts, and may also be options of one or more contacts that, in the first application program, the associated users of the sending end 1001 have recently communicated.

S1109: the sender 1001 may detect an operation acting on a contact option in the fifth user interface.

For example, the sender 1001 may detect a click operation, a touch operation, or the like, on the contact "Kate" option 609B in the user interface 62 shown in fig. 6D.

S1110: under the condition that "hishare" is turned on, the sender 1001 may discover nearby devices, such as the electronic device 1001, the electronic device 1002, the electronic device 1003, the electronic device 1005 …, and the electronic device 100 n. n is a positive integer. Reference may be made specifically to S1008 in the method embodiment of fig. 10B.

The sequence of S1110 and S1107 is not limited in this embodiment, and the sending end 1001 may execute S1107 and S1110 at the same time, may execute S1107 first, and may execute S1110 first.

S1111: the sending end 1001 determines, among the discovered nearby devices, a device associated with the contact corresponding to the contact option detected by the user operation, that is, determines the receiving end 1002. Reference may be made specifically to S1009 in the method embodiment of fig. 10B.

S1112-S1116: in response to the detected operation acting on the contact option in the fifth user interface, the sending end 1001 sends the selected file to the associated device (i.e., the receiving end 1002) of the contact corresponding to the contact option through "hishare". The process of sending the selected file to the receiving end 1002 by the sending end 1001 through "hishare" does not go entirely through the server 1004.

S1112: the transmitting end 1001 may establish a communication connection with the receiving end 1002. Specifically, refer to S1011 in the embodiment of the method in fig. 10B.

S1113: the sender 1001 may send a file sharing request to the recipient 1002. The file sharing request is used to request the receiving end 1002 to receive the file shared by the sending end 1001. Reference may be made specifically to S1012 in the method embodiment of fig. 10B.

S1114: the transmitting end 1001 displays the prompt information.

An exemplary implementation of the hint information may refer to hint information 611 in FIG. 6F.

S1115: after receiving the file sharing request sent by the sender 1001, the receiver 1002 may display a notification window. Reference may be made specifically to S1014 in the method embodiment of fig. 10B.

S1116: the receiving end 1002 returns a share request response to the transmitting end 1001 after detecting a user operation for accepting a file share request of the transmitting end 1001 in the notification window. Reference may be made specifically to S1015 in the method embodiment of fig. 10B.

S1117: after receiving the response of the sharing request from the receiving end 1002, the sending end 1001 sends the selected file to the receiving end 1002 through "share". The process of the sender 1001 sending the selected file to the receiver 1002 through the "hashare" does not go all the way through the server. Reference may be made specifically to S1016 in the method embodiment of fig. 10B.

S1118-S1120: and feeding back the file transmission state. Reference may be made specifically to S1017-S1019 in the method embodiment of fig. 10B.

In the second scenario provided in the embodiment of the present application, the prompt information displayed by the sending end 1001 may be displayed in the sixth user interface. An exemplary implementation of this sixth user interface may refer to the user interface shown in any of fig. 6E-6H.

In the method for transmitting a file in an application provided in the embodiment of the present application, both the sending end 1001 and the receiving end 1002 pre-bind a third party interface ShareKit service. The ShareKit service is used for supporting a device to run a method for transferring a file without traffic in an application, for example, the ShareKit service supports that a sending end 1001 sends a selected file to a receiving end 1002 through an aid l call function (e.g., PreSend Send), obtains a transfer state of the file through the aid l call function (e.g., ontranstatechange), and determines the receiving end 1002 through the aid l call function (e.g., ondevice found); the receiving end 1002 can also be supported to acquire the transmission state of the file through an AIDL call function (e.g., OnProgress).

That is, the ShareKit service may be a system function preset in the transmitting end 1001 and the receiving end 1002. The ShareKit service may be open in the form of an Android archive (aar) and an Android installation package (APK). The first application program on the sending end or the receiving end can call the aar interface to acquire ShareKit service.

Referring to fig. 11, fig. 11 illustrates an architecture for providing ShareKit services on a transmitting end 1001 and a receiving end 1002.

As shown in FIG. 11, a kit interface carrier, interaction mechanism and kit implementation carrier may be included in the architecture. Wherein:

the kit interface carrier may include aar and Java Archive (JAR) files of an application installed on the device, such as the first application.

The interaction mechanism may include an aid dl mechanism, a shared library (shared) mechanism, a Software Development Kit (SDK) mechanism, and a shared feature (shared) mechanism.

The kit implementation carrier may be stored in ROM. kit implementing vectors may include: presetting APK, presetting a program library, various system services and common services, shared features and the like.

Generally speaking, the method, the electronic device and the system for transmitting the file in the application provided by the embodiment of the application enable a user to quickly share the file to other nearby users through the application installed on the electronic device. The process of sharing files is independent of the server. The implementation of the technical scheme provided by the embodiment of the application has the following beneficial effects: the electronic equipment can quickly and quickly transmit the file to other surrounding equipment in application, so that the use experience of a user is optimized; no matter whether communication connection exists between the electronic equipment and the server or not and whether the communication connection is good or not, the electronic equipment can share files to other equipment, so that cellular data flow consumed by the electronic equipment can be saved, and the load of the server is reduced; the size of the file shared by the electronic device is not limited, that is, the electronic device can share a larger file to other surrounding devices.

The embodiments of the present application can be combined arbitrarily to achieve different technical effects.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions described in accordance with the present application are generated, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk), among others.

One of ordinary skill in the art will appreciate that all or part of the processes in the methods of the above embodiments may be implemented by hardware related to instructions of a computer program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the above method embodiments. And the aforementioned storage medium includes: various media capable of storing program codes, such as ROM or RAM, magnetic or optical disks, etc.

In short, the above description is only an example of the technical solution of the present invention, and is not intended to limit the scope of the present invention. Any modifications, equivalents, improvements and the like made in accordance with the disclosure of the present invention are intended to be included within the scope of the present invention.

Claims

1. A method for transferring files in an application, the method comprising:

the method comprises the steps that a first device displays a first user interface of a first application program, wherein the first user interface comprises: communication records of a first user and a second user in a first application program and a first operation option, wherein the first user logs in the first application program on the first device, the second user logs in the first application program on the second device, and the first device and the second device communicate through the first application program;

in response to a first operation received on the first operation option, the first device displays a second user interface of the first application program, wherein the second user interface comprises a first identifier, and the first identifier corresponds to a first file stored in the first device;

the first equipment receives a second operation on the first identifier, and selects the first file;

responding to a third operation of sharing the first file, the first device sends the first file to the second device through a Wi-Fi direct communication connection between the first device and the second device, wherein the first device discovers the second device through Bluetooth and establishes the Wi-Fi direct communication connection through a Bluetooth communication connection established between the first device and the second device.

2. The method of claim 1, wherein after the first device displays the first user interface, the method further comprises:

the first device discovers one or more devices through Bluetooth;

the first device determines the second device among the one or more discovered devices.

3. The method of claim 1, further comprising:

in response to the first operation, the first device discovers one or more devices via bluetooth;

4. The method according to claim 2 or 3,

the first device discovers one or more devices through bluetooth, and specifically includes: the first device receives a Bluetooth broadcast packet sent by one or more devices, wherein the Bluetooth broadcast packet comprises a user identifier, and a user corresponding to the user identifier logs in the first application program on the device;

the determining, by the first device, the second device among the one or more discovered devices specifically includes: the first device determines a device which sends a first identifier in the one or more devices as the second device; the first identifier is a user identifier of the second user.

5. The method of claim 2 or 3, wherein after the first device determines the second device among the one or more discovered devices, before the first device sends the first file to the second device over a Wi-Fi direct communication connection with the second device, the method further comprises:

the first device performs a procedure between the first device and the second device to establish the Wi-Fi direct communication connection.

6. The method of claim 5, wherein prior to the first device performing the process of establishing the Wi-Fi direct communication connection with the second device, the method further comprises:

the first device executes a process of establishing a Bluetooth communication connection with the second device;

the first device sends a Service Set Identifier (SSID) and a password to the second device through the established Bluetooth communication connection; the SSID and the password are used for the second device to perform a process of establishing the Wi-Fi direct communication connection with the first device.

7. The method of any of claims 1-3, wherein after the first device sends the first file to the second device over a Wi-Fi direct communication connection with the second device, the method further comprises:

and the first equipment displays a third user interface, wherein the third user interface comprises prompt information, and the prompt information is used for indicating the transmission state of the first file.

8. The method according to any one of claims 1 to 3,

before the first device sends the first file to the second device through a Wi-Fi direct communication connection with the second device, the method further includes: the first device sends a file sharing request to the second device;

the sending, by the first device, the first file to the second device through a Wi-Fi direct communication connection with the second device specifically includes: and the first equipment sends the first file to the second equipment through Wi-Fi direct communication connection between the first equipment and the second equipment under the condition of receiving a sharing request response sent by the second equipment in response to the file sharing request.

9. The method according to claim 8, wherein the sending, by the first device, the file sharing request to the second device specifically includes:

the first device sends a file sharing request to a server, so that the server sends the file sharing request to the second device; wherein the server provides a service for the first application.

10. The method of any of claims 1-3, wherein before the first device sends the first file to the second device over a Wi-Fi direct communication connection with the second device, the method further comprises:

the first device detects a fourth operation for starting the first communication service and the second communication service;

in response to the fourth operation, the first device turns on the first communication service and a second communication service; the first communication service is used for the first device to discover and determine the second device through Bluetooth, and the second communication service is used for the first device to send the first file to the second device through the Wi-Fi direct communication connection.

11. The method of any of claims 1-3, wherein the first application is an instant messaging application or a mailbox application.

12. The method according to any one of claims 1-3, further comprising:

when the size of the first file exceeds a first threshold value, the first device sends the first file to a second device through a Wi-Fi direct communication connection between the first device and the second device;

when the size of the first file does not exceed the first threshold, the first device sends the first file to the second device through a cellular mobile communication network.

13. A method for transferring files in an application, the method comprising:

the first equipment displays a fourth user interface, wherein the fourth user interface comprises a third identifier, and the third identifier corresponds to a third file stored in the first equipment;

receiving a fifth operation on the third identifier, and selecting the third file;

in response to a sixth operation of sharing the third file, displaying one or more application program options, wherein the one or more application program options comprise the option of the first application program;

in response to a seventh operation received on the option of the first application, displaying a fifth user interface, the fifth user interface including: an option for one or more contacts of the first user in the first application; the one or more contacts comprise a second user;

in response to an eighth operation received on the option of the second user, the first device sends a third file to the second device through a Wi-Fi direct communication connection with the second device;

the first user logs in the first application program on the first device, the second user logs in the first application program on the second device, and the first application program is used for communication between the first device and the second device, wherein the first device discovers the second device through Bluetooth and establishes the Wi-Fi direct communication connection through Bluetooth communication connection established between the first device and the second device.

14. An electronic device, characterized in that the electronic device comprises: a display screen, a memory, one or more processors; the display screen, the memory coupled with the one or more processors, the memory for storing computer program code, the computer program code comprising computer instructions that the one or more processors invoke to cause the electronic device to perform the method of any of claims 1-13.

15. A computer-readable storage medium comprising instructions that, when executed on an electronic device, cause the electronic device to perform the method of any of claims 1-13.