WO2021135734A1

WO2021135734A1 - Method for transmitting file in application, and electronic device and system

Info

Publication number: WO2021135734A1
Application number: PCT/CN2020/131219
Authority: WO
Inventors: 毕岩
Original assignee: 华为技术有限公司
Priority date: 2019-12-31
Filing date: 2020-11-24
Publication date: 2021-07-08
Also published as: CN112261624B; CN113068156A; CN112261624A

Abstract

Disclosed are a method for transmitting a file in an application in a traffic-free manner, and an electronic device and a system. By using the method, an electronic device can quickly share, in an application program, a file with other nearby devices by means of a WiFi direct communication connection established between the electronic device and the other devices. By implementing the technical solutions provided in the embodiments of the present application, an electronic device can quickly and conveniently transmit, in an application, a file to other surrounding devices, optimizing the usage experience of a user, and can also save on cellular data traffic consumed by the electronic device, reducing the load of a server; in addition, there is no limit to the size of the file shared by the electronic device.

Description

Method, electronic equipment and system for transferring files in application

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on December 31, 2019, the application number is 201911419935.2, and the application name is "Methods, Electronic Equipment and Systems for File Transmission in Applications", the entire contents of which are incorporated by reference In this application.

Technical field

This application relates to the field of short-range communication and terminal technology, and in particular to methods, electronic devices and systems for transferring files in applications.

Background technique

With the development of wireless communication technology, electronic devices such as smart phones and tablet computers have begun to support users to share pictures, videos, documents, music and other files through instant messaging applications (applications, APP), which improves the user experience.

At present, when users share files through instant messaging applications, the electronic device first transmits the files to the server via the network (such as cellular network, Wireless Fidelity (Wi-Fi), etc.), and then the server forwards the file to the peer equipment. This way of sharing files has the following shortcomings:

1. This method relies on the communication connection between the electronic device and the server, and the efficiency of file transfer will be affected when the network condition is poor.

2. Due to the need to transfer files through the network, users can only share smaller files under normal circumstances, and sharing larger files will take more time and the user experience is not good.

3. When many users use this instant messaging application to share files, the server load will be too large.

How to meet the needs of users for fast transmission and large file transmission when users share files through instant messaging applications, and to provide users with a better user experience, is the direction of current research.

Summary of the invention

The embodiments of the application provide a method, electronic device, and system for transferring files without traffic in an application, which can enable the electronic device to quickly and quickly transfer files to other surrounding devices in the application, optimize the user experience, and the file transfer process can be Do it without a network.

In the first aspect, an embodiment of the present application provides a method for transferring files in an application, which is applied to a first device. The method includes: a first device displays a first user interface, the first user interface includes: a first user and a second user's communication records in a first application, a first operation option; in response to the first operation For the first operation received on the option, the first device displays a second user interface. The second user interface includes a first identifier and a second identifier, and the first identifier corresponds to the first identifier stored in the first device. File, the second identifier corresponds to a second file stored in the first device; the first device receives a second operation on the first identifier, selects the first file; responds to sharing the first file In the third operation, the first device sends the first file to the second device through the Wi-Fi direct communication connection with the second device; wherein, the first user logs in to the second device on the first device The first application, the second user logs in the first application on the second device.

By implementing the method of the first aspect, the electronic device can quickly share files with other nearby devices in the application through Wi-Fi direct communication connections with other devices. The method does not rely on the server, and can support users to share files regardless of whether there is a communication connection between the electronic device and the server, and whether the communication connection is good. This method can optimize user experience, save cellular data traffic consumed by electronic devices, and reduce server load. In addition, the way of sharing files through Wi-Fi direct communication connection makes the size of the files that the electronic device can share is not limited, that is to say, the method can support the electronic device to share larger files to other surrounding devices. In this way, the process of using the application on the electronic device to share the file is intuitive, simple and fast for the user.

With reference to the first aspect, in some embodiments, the first application may be an instant messaging application, a mailbox application, and so on. The first user interface may be an interface displayed when the electronic device runs the first application program.

With reference to the first aspect, in some embodiments, the first file or the second file may include, but is not limited to: pictures, audios, videos, documents, links, and so on.

With reference to the first aspect, in some embodiments, the first device can discover and determine the second device via Bluetooth. Using Bluetooth can ensure that the first device quickly discovers and determines the second device, and improves the efficiency of sharing files. In an embodiment, the first device may discover one or more devices through Bluetooth after displaying the first user interface, and determine the second device among the discovered one or more devices. In another implementation manner, the first device may, in response to the first operation, discover one or more devices via Bluetooth, and determine the second device among the discovered one or more devices.

In some embodiments, the first device may receive a Bluetooth broadcast packet sent by one or more devices, and the Bluetooth broadcast packet includes a user identification, and a user corresponding to the user identification logs in the first application on the device. The one or more devices are one or more devices discovered by the first device. The first device may determine the device that sends the first identification among the one or more devices as the second device; the first identification is the user identification of the second user. In this way, the first device can determine the device used by the second user to log in to the first application among the discovered one or more devices.

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

In some embodiments, the first device may perform the process of establishing a Bluetooth communication connection with the second device before performing the process of establishing a Wi-Fi direct communication connection with the second device, and pass The established Bluetooth communication connection sends the service set identification SSID and password to the second device; the SSID and the password are used by the second device to perform the establishment of the Wi-Fi direct communication connection with the first device process. In other words, the first device can first establish a Bluetooth communication connection with the second device, and then establish a Wi-Fi direct communication connection with the second device based on the Bluetooth communication connection, so that the Wi-Fi direct communication connection can be quickly established. Thereby improving the efficiency of sharing files.

With reference to the first aspect, in some embodiments, the second user interface further includes a second operation option, and the third operation includes: an operation received on the second operation option after the first file is selected. In an implementation manner, 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 give the user a better user experience. In another implementation manner, the first device may simultaneously display the second operation option on the second user interface while displaying 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 also be displayed. The third user interface includes prompt information, and the prompt information is used to indicate the The 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, and the first file is being transferred to the second device. Successfully transmitted to the second device and so on. In this way, the user can intuitively learn the transmission status of the first file, and give the user a better experience. In some embodiments, the third user interface may further include a communication record 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 the first file to the second device through the Wi-Fi direct communication connection with the second device, and send the file to the second device. The device sends a file sharing request; and in the case of receiving a sharing request response sent by the second device in response to the file sharing request, the first device is connected through the Wi-Fi direct communication connection with the second device The file is sent to the second device. In this way, the first file can be sent to the second device with the consent of the second user, and the user experience can be guaranteed.

In some embodiments, the file sharing request may be sent by the 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 services for the first application. Sending the file sharing request through the server allows the server to learn and record the file transfer 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, it may also detect a fourth operation for starting the first communication service and the second communication service; Fourth operation, the first device starts the first communication service and the second communication service. The first communication service is used by the first device to discover and determine the second device via Bluetooth, and the second communication service is used by the first device to send the first file to the second device via the Wi-Fi direct communication connection. Two equipment. In one embodiment, the first communication service is a Bluetooth communication service, and the second communication service is a WLAN communication service.

In the second aspect, an embodiment of the present application provides a method for transferring files in an application. The difference between the method of the second aspect and the method of the first aspect is that in the method of the first aspect, the user first selects the application and then the file, while in the method of the second aspect, the user selects the file first and then the application.

The method of the second aspect is applied to a first device, and the method may include: the first device displays a fourth user interface, the fourth user interface includes a third identifier and a fourth identifier, the third identifier corresponds to the first device The third file stored in the third file, the fourth identifier corresponds to the fourth file stored in the first device; the fifth operation on the third identifier is received, and the third file is selected; in response to sharing the third file The sixth operation is to display the options of one or more applications; the options of the one or more applications include the options of the first application; in response to the seventh operation received on the options of the first application, display A fifth user interface. The fifth user interface includes: options for one or more contacts of the first user in the first application; the one or more contacts include the second user; The eighth operation received on the option of the second user, the first device sends the third file to the second device through the Wi-Fi direct communication connection with the second device; wherein, the first user is in the The first application is logged in on the first device, and the second user is logged in to the first application on the second device.

By implementing the method of the second aspect, the electronic device can quickly share files with other nearby devices in the application through Wi-Fi direct communication connections with other devices. The method does not rely on the server, and can support users to share files regardless of whether there is a communication connection between the electronic device and the server, and whether the communication connection is good. This method can optimize user experience, save cellular data traffic consumed by electronic devices, and reduce server load. In addition, the way of sharing files through Wi-Fi direct communication connection makes the size of the files that the electronic device can share is not limited, that is to say, the method can support the electronic device to share larger files to other surrounding devices. In this way, the process of using the application on the electronic device to share the file is intuitive, simple and fast for the user.

For the first application program mentioned in the second aspect, reference may be made to the related description in the first aspect.

With reference to the second aspect, in some embodiments, the third file or the fourth file may include, but is not limited to: pictures, audios, videos, documents, links, and so on.

With reference to the second aspect, in some embodiments, the first device can discover and determine the second device via Bluetooth. Using Bluetooth can ensure that the first device quickly discovers and determines the second device, and improves the efficiency of sharing files. In one embodiment, after receiving the sixth operation to share the third file, the first device may discover one or more devices via Bluetooth, and determine the second device among the discovered one or more devices equipment. In another implementation manner, the first device may, in response to the eighth operation, discover one or more devices via Bluetooth, and determine the second device among the discovered one or more devices.

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

With reference to the second aspect, in some embodiments, the first device responds to the sixth operation of sharing the third file, and the displayed one or more application options may be any of the following:

1. The corresponding options for all applications installed on the sender that can be used to share files.

2. Among the applications that can be used to share files installed on the sender, the options corresponding to the applications that can currently share files through "hishare".

With reference to the second aspect, in some embodiments, the first device may also display the sixth user interface in response to the eighth operation received on the option of the second user, and the sixth user interface includes: The communication record and prompt information of the user and the second user in the first application, the prompt information is used to indicate the transmission status of the third file. The transmission status of the third file may include but is not limited to: the 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, and the third file is being transferred to the second device. Successfully transmitted to the second device and so on. In this way, the user can intuitively learn the transmission status of the third file, and give the user a better experience.

With reference to the second aspect, in some embodiments, the fourth user interface may include a third operation option. The sixth operation may include the 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, giving the user a better user experience. In another implementation manner, the first device may simultaneously display the third operation option on the fourth user interface while displaying the fourth user interface.

With reference to the second aspect, in some embodiments, the first device may send the third file to the second device through the Wi-Fi direct communication connection with the second device, to the second device The device sends a file sharing request; and in the case of receiving a sharing request response sent by the second device in response to the file sharing request, the third device is connected through the Wi-Fi direct communication connection with the second device. The file is sent to the second device. In this way, the third file can be sent to the second device with the consent of the second user, and the user experience can be guaranteed.

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

In the third aspect, an embodiment of the present application provides an electronic device. The electronic device includes one or more processors and a memory; the memory is coupled with the one or more processors, and the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call The computer instructions cause the electronic device to execute the method in the first aspect or 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 and a memory; the memory is coupled with the one or more processors, and the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call The computer instructions cause the electronic device to execute the method in the second aspect or any one of the implementation manners of the second aspect.

In the fifth aspect, the embodiments of the present application provide a computer program product containing instructions. When the computer program product is run on an electronic device, the electronic device is caused to perform any possible implementation as in the first aspect and the first aspect. The method described by the method.

In a sixth aspect, the embodiments of the present application provide a computer program product containing instructions. When the computer program product is run on an electronic device, the electronic device is caused to perform any possible implementation as in the second aspect and the second aspect. The method described by the method.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions, which when the foregoing instructions run on an electronic device, cause the electronic device to execute the first aspect and any possible implementation manner in the first aspect Described method.

In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions, which when the foregoing instructions run on an electronic device, cause the foregoing electronic device to execute the second aspect and any possible implementation manner of the second aspect Described method.

In a ninth aspect, an embodiment of the present application provides a system for transferring files in an application. The system includes a first device and a second device. The first device may be the electronic device described in the third aspect. The second device is configured to receive the first file through the Wi-Fi direct communication connection with the first device.

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

With reference to the ninth or 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; in response to the file sharing request, display The notification window is used to ask the user whether to receive the first file or the third file; the notification window includes a fourth operation option, and in response to the ninth operation received on the fourth operation option, the second device receives The first file or the third file.

With reference to the ninth aspect or the tenth aspect, in some embodiments, the second device is further configured to send a Bluetooth broadcast packet before receiving the first file or the third file. The Bluetooth broadcast packet includes a user ID, and the user ID corresponds to The user logs in the first application on the second device. The Bluetooth broadcast packet is used by the first device to discover and determine the second device.

With reference to the ninth aspect or the tenth aspect, in some embodiments, the second device is further configured to perform a process 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 aspect or the 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, and the seventh user interface includes: the second user and the second user A user's communication record and prompt information in the first application program. The prompt information is used to indicate the transmission status of the first file or the third file. For the transmission status of the first file or the third file, refer to the related descriptions of the first aspect and the second aspect.

To implement the technical solutions provided by the embodiments of the present application, the electronic device can quickly share files with other nearby devices in the application through Wi-Fi direct communication connections with other devices. This technical solution has the following beneficial effects: the electronic device can quickly and quickly transfer files to other surrounding devices in the application, optimizing the user experience; regardless of whether there is a communication connection between the electronic device and the server, and whether the communication connection is Good, electronic devices can share files to other devices, which can save cellular data traffic consumed by electronic devices and reduce server load; the size of files shared by electronic devices is not limited, which means that electronic devices can share larger files To other equipment around.

Description of the drawings

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

FIG. 1B is a schematic diagram of the software structure of an electronic device provided by an embodiment of the present application;

FIG. 2A is a user interface for displaying an application program installed on an electronic device provided by an embodiment of the present application;

FIG. 2B is a schematic diagram of opening "hishare" provided by an embodiment of the present application;

Figures 3A-3I are a series of user interfaces on the sending end in scenario one provided by an embodiment of the application;

4A-4F are another series of user interfaces on the sending end in scenario one provided by an embodiment of this application;

5A-5I are another series of user interfaces on the sending end in scenario one provided by an embodiment of this application;

6A-6H are a series of user interfaces on the sending end in scenario 2 provided by an embodiment of this application;

7A-7E are another series of user interfaces on the sending end in scenario 2 provided by an embodiment of this application;

8A-8I are still another series of user interfaces on the sending end in scenario 2 provided by an embodiment of this application;

9A-9D are a series of user interfaces on the sending end in scenario 3 provided by an embodiment of this application;

FIG. 10A is a schematic structural diagram of a communication system provided by an embodiment of this application;

FIG. 10B is a schematic flowchart of a method for transferring files in an application in scenario 1 provided by an embodiment of the application; FIG.

FIG. 10C is a schematic flowchart of a method for transferring files in an application in scenario 2 provided by an embodiment of the application; FIG.

Figure 11 is the architecture of the ShareKit service provided by an embodiment of the application.

Detailed ways

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

Among them, in the description of the embodiments of the present application, unless otherwise specified, "/" means or, for example, A/B can mean A or B; "and/or" in this document is only a description of related objects The association relationship of indicates that there can be three kinds of relationships, for example, A and/or B, which can indicate: A alone exists, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" refers to two or more than two.

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

The following embodiments of the application provide a method, electronic device, and system for transferring files in an application, so that users can quickly share files with other users nearby through the application installed on the electronic device. The method does not rely on the server, and the file transfer process can be performed without a network. It can support users to share files regardless of whether there is a communication connection between the electronic device and the server and whether the communication connection is good. The method supports the electronic device to quickly transfer files to other surrounding devices in the application, optimizes the user experience, and can also save the cellular data traffic consumed by the electronic device and reduce the load of the server. Moreover, with this method, the size of the file that the electronic device can share is not limited, that is, the method can support the electronic device to share a larger file to other surrounding devices. In this way, the process of using the application on the electronic device to share the file is 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, connections based on 3G, LTE, 5G and other cellular mobile communication networks, wide area networks (WAN), local area networks (LAN), and so on.

In the following embodiments of the present application, the electronic device can share files with other surrounding devices in the following applications: instant messaging applications, mailbox applications, and so on.

In the following embodiments of the present application, the files shared by the electronic device to other surrounding devices may include, but are not limited to: pictures, audios, videos, documents, links, and so on. These files can be obtained by the electronic device itself, such as pictures and/or videos captured by a camera, documents generated by using a display screen to collect text input by the user, etc., or the electronic device can be obtained from other devices such as a server through the network. Obtained.

In the following embodiments of the present application, under the condition that the "hishare" of the electronic device such as a smart phone is turned on, the electronic device can discover other devices such as nearby mobile phones and tablet computers. If a user wants to share a file in an application with other contacts in the application, the electronic device can send the file selected by the user to other discovered devices, and another user can log in to the application on other devices, and the other user is Is the contact of the current user. In the embodiments of the present application, the electronic device used by a certain user to log in to the application may be referred to as the user's associated device. The specific implementation of the steps of how the electronic device discovers other nearby devices, how to determine the devices associated with the contact among other nearby devices, and how to send files will be described in detail in subsequent embodiments, and will not be repeated here.

In the following embodiments of this application, "hishare" is a service or function provided by an electronic device, which can support the electronic device to send files to other nearby devices.

The process of electronic devices sending files to other devices through "hishare" does not completely go through the server.

In some embodiments, "hishare" can support the electronic device to pass Bluetooth (BT), near field communication (NFC), wireless fidelity direct (Wi-Fi direct) (also known as Wi-Fi direct) For wireless fidelity peer-to-peer (Wi-Fi p2p), Wi-Fi software access point (software access point, softAP) one or more of the technologies to transfer files to other nearby equipment. In other embodiments, "hishare" can support the electronic device to transmit data via a local area network (LAN) to other devices in the same local area network as the electronic device. The device in the same local area network as the electronic device may also be other devices near the electronic device. In still other embodiments, "hishare" can support the electronic device to transmit files to the server through 3G, LTE, 5G and other cellular mobile communication technologies or wide area network (WAN) technologies, and the server can forward the files to nearby other devices.

It can be understood that part or all of the above several embodiments can be implemented in combination. For example, "hishare" can support electronic devices to simultaneously use Wi-Fi direct connection (such as Wi-Fi p2p) and cellular mobile communication technology to transfer files to other nearby devices.

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

In the following embodiments of the present application, turning on "hishare" may include turning on one or more of the Bluetooth module, NFC module, and WLAN module of the electronic device. In some embodiments, after the above functional modules are turned on, the electronic device can be discovered through one or more of NFC, Bluetooth, Wi-Fi direct connection (such as Wi-Fi p2p), Wi-Fi softAP, and Wi-Fi LAN. Equipment near the electronic device.

In a specific embodiment, if the electronic device turns on "hishare", one or more of NFC, Bluetooth, Wi-Fi direct connection (such as Wi-Fi p2p), Wi-Fi softAP, Wi-Fi LAN Technology discovers other devices near the electronic device and transfers files to other nearby devices, then due to Bluetooth, Wi-Fi direct connection (such as Wi-Fi p2p), Wi-Fi softAP, Wi-Fi LAN and other technical support electronic devices There is no need to communicate with each other through the server, and the process of the electronic device transferring files to other nearby devices in the application does not rely on the communication connection between the electronic device and the server. In this way, the electronic device can quickly transfer files to other surrounding devices in the application, and can transfer larger files to other surrounding devices, so as to optimize the user experience and save the cellular data traffic consumed by the electronic device. Reduce the load on the server. For example, in one embodiment, “hishare” supports electronic devices to discover the surrounding devices through Bluetooth and determine the devices associated with the contact among these devices, and then send the files selected by the user to the device through Wi-Fi P2P. The device associated with the contact. In this way, electronic devices can quickly discover surrounding devices through BT, and quickly and conveniently send files to the devices associated with the contact through Wi-Fi P2P.

It is understandable that "hishare" is only a word used in this embodiment, and its representative meaning has been recorded in this embodiment, and its name does not constitute any limitation on this embodiment. In addition, in some other embodiments of the present application, "hishare" may also be referred to as other nouns such as "short-distance sharing", "quick sharing", "Moment Share" and so on.

In order to better introduce the file transfer method in the application provided in the embodiment of the present application, the following first introduces the exemplary electronic device provided in the embodiment of the present application.

In the embodiments of the present application, the electronic device may be a portable terminal device equipped with iOS, Android, Microsoft or other operating systems, such as a mobile phone, a tablet computer, a wearable device, etc., or a laptop with a touch-sensitive surface or a touch panel. Non-portable terminal devices such as laptops, desktop computers with touch-sensitive surfaces or touch panels.

FIG. 1A shows a schematic diagram of the structure 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, and an antenna 2. , Mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone jack 170D, sensor module 180, buttons 190, motor 191, indicator 192, camera 193, display screen 194, and Subscriber identification module (subscriber identification module, SIM) card interface 195, etc. 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, and ambient light Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100.

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU), etc. Among them, the different processing units may be independent devices or integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching instructions and executing instructions.

A memory may also be provided in the processor 110 to store instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can store instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. Repeated accesses are avoided, the waiting time of the processor 110 is reduced, and the efficiency of the system is improved.

In some embodiments, the processor 110 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, and a universal asynchronous transmitter/receiver (universal asynchronous) interface. receiver/transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and / Or Universal Serial Bus (USB) interface, etc.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can 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 screen 194, the camera 193, and the wireless communication module 160.

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

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

The mobile communication module 150 can provide a wireless communication solution including 2G/3G/4G/5G and the like 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 can receive electromagnetic waves by the antenna 1, and perform processing such as filtering, amplifying and transmitting the received electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor, and convert it into electromagnetic waves for radiation via the antenna 1. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the processor 110. In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low frequency baseband signal to be sent into a medium and high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed 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 an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be provided in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide applications on the electronic device 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), and global navigation satellites. System (global navigation satellite system, GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (infrared, IR) and other wireless communication solutions. 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, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be sent from the processor 110, perform frequency modulation, amplify, and convert it into electromagnetic waves to radiate through the antenna 2. Exemplarily, the wireless communication module 160 may include a Bluetooth module, an NFC module, a WLAN module, and so on. The Bluetooth (BT) module can provide one or more Bluetooth communication solutions including classic Bluetooth (Bluetooth 2.1) or Bluetooth low energy (Bluetooth low energy, BLE). The WLAN module can provide one or more WLAN communication solutions including Wi-Fi direct, Wi-Fi LAN, or Wi-Fi softAP.

In some embodiments, the antenna 1 of the electronic device 100 is coupled with the mobile communication module 150, and the antenna 2 is coupled with the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC , FM, and/or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (quasi -zenith satellite system, QZSS) and/or satellite-based augmentation systems (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 can transmit signals to detect or scan other nearby devices, and can also monitor signals emitted by other devices, thereby using Bluetooth Or wireless communication technologies such as WLAN discover nearby devices, establish wireless communication connections with nearby devices, and transfer files to nearby devices through the above-mentioned connections.

The wireless communication solution provided by the mobile communication module 150 of the electronic device 100 can enable the sender to communicate with a device (such as a server) in the network, and the WLAN wireless communication solution provided by the wireless communication module 160 can also enable the electronic device 100 to communicate with Communication with devices (such as servers) in the network. The electronic device 100 can communicate with other nearby devices (such as the receiving end 102) through a device in the network (such as a server). For example, the sending end can first transmit a file to a device in the network, and then the device in the network can transmit the file To other devices nearby.

The processor 110 of the electronic device 100 may be used to generate signals sent by the wireless communication module 160 and the mobile communication module 150, such as detection requests, Bluetooth broadcast signals, beacon signals, and so on. The processor 110 of the electronic device 100 may also be used to parse the signals received by the wireless communication module 160 and the mobile communication module 150, such as detection responses and the like.

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

The display screen 194 is used to display images, videos, and the like. The display screen 194 includes a display panel. The display panel can use liquid crystal display (LCD), organic light-emitting diode (OLED), active matrix organic light-emitting diode or active-matrix organic light-emitting diode (active-matrix organic light-emitting diode). AMOLED, flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 194, and N is a positive integer greater than one.

The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

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

The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and is projected to the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transfers the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other formats of image signals. In some embodiments, the electronic device 100 may include one or N cameras 193, and N is a positive integer greater than one.

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the electronic device 100 selects the frequency point, the digital signal processor is used to perform Fourier transform on the energy of the frequency point.

Video codecs are used to compress or decompress digital video.

NPU is a neural-network (NN) computing processor. By drawing on the structure of biological neural networks, for example, the transfer mode between human brain neurons, it can quickly process input information, and it can also continuously self-learn. Through the NPU, applications such as intelligent cognition of the electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, and so on.

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

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

The electronic device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. For example, music playback, recording, etc.

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

The speaker 170A, also called "speaker", is used to convert audio electrical signals into sound signals.

The receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals.

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

The earphone interface 170D is used to connect wired earphones.

The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be provided on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors and so on. The capacitive pressure sensor may include at least two parallel plates with conductive materials. When a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor 180A. The electronic device 100 may also calculate the touched position according to the detection signal of the pressure sensor 180A.

The gyro sensor 180B may be used to determine the movement posture 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 can detect the magnitude of the acceleration of the electronic device 100 in various directions (generally three axes).

Distance sensor 180F, used to measure 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 brightness of the ambient light.

The fingerprint sensor 180H is used to collect fingerprints.

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

Touch sensor 180K, also called "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch screen is composed of the touch sensor 180K and the display screen 194, which is also called a “touch screen”. The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. The visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100, which is different from the position of the display screen 194.

The bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can obtain the vibration signal of the vibrating bone mass of the human voice.

The button 190 includes a power-on button, a volume button, and so on.

The motor 191 can generate vibration prompts.

The indicator 192 may be an indicator light, which may be used to indicate the charging status, power change, or to indicate messages, missed calls, notifications, and so on.

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

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example to illustrate the software structure of the electronic device 100 by way of example.

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

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Communication between layers through software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.

The application layer can include a series of application packages.

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

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 1B, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and so on.

The window manager is used to manage window programs. The window manager can obtain the size of the display screen, determine whether there is a status bar, lock the screen, take a screenshot, etc.

The content provider is used to store and retrieve data and make these data accessible to applications. The data may include videos, images, audios, phone calls made and received, browsing history and bookmarks, phone book, etc.

The view system includes visual controls, such as controls that display text, controls that display pictures, and so on. The view system can be used to build applications. The display interface can be composed of one or more views. For example, a display interface that includes a short message notification icon may include a view that displays text and a view that displays pictures.

The phone manager is used to provide the communication function of the electronic device 100. For example, the management of the call status (including connecting, hanging up, etc.).

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

The notification manager enables the application to display notification information in the status bar, which can be used to convey notification-type messages, and it can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, and so on. The notification manager can also be a notification that appears in the status bar at the top of the system in the form of a chart or a scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, text messages are prompted in the status bar, prompt sounds, electronic devices vibrate, and indicator lights flash.

Android Runtime includes core libraries and virtual machines. Android runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one part is the function functions that the java language needs to call, and the other part is the core library of Android.

The application layer and application framework layer run in a virtual machine. The virtual machine executes the java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

The system library can include multiple functional modules. For example: surface manager (surface manager), media library (Media Libraries), three-dimensional graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL), etc.

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

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support multiple audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing.

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

The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

The software system shown in FIG. 1B involves the presentation of various applications (such as instant messaging applications, mailbox applications, file managers, etc.), and provides the "hishare" service in the embodiments of the present application. Among them, the application framework layer provides WLAN services and Bluetooth services, and the core and the bottom layer provide WLAN capabilities, Bluetooth capabilities, and basic communication protocols.

The method for transferring files in an application provided in the embodiments of the present application involves two ends, one end is the sending end 101 that sends the file, and the other end is the receiving end 102 that receives the file. The sending end 101 and the receiving end 102 are both electronic devices, and the structures of the sending end 101 and the receiving end 102 can refer to the related description in the embodiment of FIG. 1A and FIG. 1B.

In the embodiments of the present application, the sending end may be referred to as the first device, and the receiving end may be referred to as the second device. The associated user at the sending end may be referred to as the first user, and the associated user at the receiving end may be referred to as the second user.

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

The method for transferring files in the application provided by the embodiment of the present application will be described below in conjunction with the user interface provided by the embodiment of the present application.

The term "user interface (UI)" in the embodiments of this application is a medium interface for interaction and information exchange between an application or operating system and a user. It realizes the relationship between the internal form of information and the form acceptable to the user. Conversion. The user interface is a source code written in a specific computer language such as java and extensible markup language (XML). The interface source code is parsed and rendered on an electronic device, and finally presented as content that can be recognized by the user. The commonly used form of the user interface is a graphical user interface (GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It can be visual interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, Widgets, etc. displayed on the display screen of the electronic device.

2A-2B exemplarily show an operation of turning on "hishare" on the sending end 101.

FIG. 2A exemplarily shows an exemplary user interface 21 on the sending end 101 for displaying installed applications. The user interface 21 displays: a status bar, a calendar indicator, a weather indicator, a tray with commonly used application icons, a navigation bar, and other application icons (such as the icon of the gallery, the icon 201 of the instant messaging application "Hi Chat", etc. and many more. Among them, the status bar may include: one or more signal strength indicators of mobile communication signals (also known as cellular signals), the name of the operator (for example, "China Mobile"), and wireless fidelity (Wi-Fi) One or more signal strength indicators of the signal, battery status indicator, time indicator, etc. The navigation bar may include system navigation keys such as the return key, the home screen key, and the multitasking key. In some embodiments, the user interface 21 exemplarily shown in FIG. 2A may be a home screen.

As shown in FIGS. 2A and 2B, when the sending end 101 detects a downward sliding gesture on the display screen, the sending end 101 may display a window 202 on the user interface 21 in response to the gesture. As shown in FIG. 2B, a control 202A may be displayed in the window 202, and the control 202A may receive an operation (such as a touch operation, a click operation) to turn on/off the "hishare" function of the sending terminal 101. The manifestation of the control 202A may include an icon and/or text (for example, the text "hishare", etc.). The window 201 may also display switch controls for other functions such as Wi-Fi, Bluetooth, flashlight, and so on. In some embodiments, after the sending end 101 opens "hishare", the display form of the control 202A can be changed, for example, a shadow when the control 202A is displayed is added.

It is not limited to the manner in which the user opens "hishare" in the window 202 shown in FIGS. 2A and 2B. In the embodiment of the present application, the sending end 101 may also initiate "hishare" in other ways. For example, the sender 101 may also display a setting interface provided by the settings application. The settings interface may include a control provided to the user to enable/disable the "hishare" function of the sender 101. Enter a user operation on the above to open the "hishare" of the sender 101. For another example, the user can also select a contact to share the file in the application and then turn on the "hishare" of the sender 101, which will be described in detail in subsequent embodiments, and will not be repeated here.

In an embodiment of the present application, the operation for opening "hishare" may be referred to as the fourth operation for opening the first communication service and the second communication service. The first communication service is used by the sending end to discover 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 a Wi-Fi direct communication connection.

The user interface implemented on the sending end 101 and the receiving end 102 will be described below in conjunction with several application scenarios involved in this application.

(1) Scenario 1: The user selects the contact first, and then selects the file to share

3A to 3I exemplarily show the user interface displayed by the sending end 101 in scenario one.

1. Figures 3A-3B show an embodiment in which a user selects a contact in an application.

FIG. 3A exemplarily shows the user interface 31 of the first application program (for example, the instant messaging application "Hi Chat") displayed by the sending terminal 101. The first application program may be an application program for social communication installed on an electronic device, and the first application program may support communication between multiple users, such as sending texts, voices, files, etc. to each other. The user can log in to the first application on the sending terminal 101 using his user ID and password. After the user logs in to the first application, he can communicate with the contacts added by the user in the first application. In the embodiment of the present application, the user who logs in to the first application on the sending end 101 may be referred to as an associated user of the sending end 101.

The user interface 31 shown in FIG. 3A may be displayed by the sending terminal 101 in response to a user operation (such as a click operation, a touch operation, etc.) received on the icon 201 in the user interface 21. The user interface 31 is used to display one or more contact options of the user in the first application.

As shown in FIG. 3A, the user interface 31 displays: a status bar 301, a title bar 302, a search box 303, one or more recent contact options, and a menu bar 305.

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

The title bar 302 may include a current page indicator for indicating the current page, for example, the text information "Hi Chat" is used to indicate that the current page is a user interface provided by the first application "Hi Chat".

The search box 303 can be used to monitor touch operations, click operations, etc., in response to the operation, the sending end 101 can display a text input box so that the user can enter the contact options and chat records (such as text information) that the user wants to search in the text input box , Pictures, links or other files, etc.).

The recent contact options may include contact options corresponding to one or more contacts that the user has communicated recently in the first application program, and the contact options may include: official account options, user options, group options, and so on. For example, the recent contact options include an option 304A for the contact "Kate" and an option 304B for the group "workgroup". The realization form of the contact option may include, but is not limited to: icons or text. The icon or text can be used to indicate the user identification of the contact in the first application. The user identification may include, but is not limited to: the account number, avatar, nickname, name, etc. of the contact in the first application.

The menu bar 305 may include multiple controls, such as "Hi Chat", "Address Book", "Discover" and "Me" as shown in FIG. 3A. The content displayed in the display area other than the menu bar 305 and the status bar 301 in the user interface is related to the currently selected control in the menu bar 305. The currently selected control in the menu bar 305 in FIG. 3A is "Hi Chat".

The sending end 101 may respond to the user operation detected on the contact option and display the communication record of the contact corresponding to the contact option on the display screen. In some embodiments, when the "hishare" of the sender 101 has not been enabled, the sender 101 may also enable "hishare" in response to a user operation detected on the contact option.

In the embodiment of the present application, the user operation detected by the sending end 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 (such as a click operation, a touch operation, etc.) input by the user on the option 304A of the contact "Kate", and the selected contact is "Kate" . The user interface 32 is used to display the communication records of the associated user of the sending terminal 101 and the contact "Kate".

As shown in FIG. 3B, the user interface 32 displays: a status bar 306, a title bar, a communication record 308 of the associated user and contact "Kate" of the sending end 101 (the communication record shown in FIG. 3B is empty), and a menu 309 .

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

The title bar may include a current page indicator 307B for indicating the current page, for example, the text information "Kate" is used to indicate that the current page is a page for communication between the user and the contact "Kate". The title bar may also include a return key 307A, which is used to monitor user operations, and the sending end 101 may display the user interface 31 shown in FIG. 3A in response to the user operation on the return key 307A.

The menu 309 may include a control 309A, a text input box 309B, and a control 309C. The control 309A can be used to monitor user operations, and the sending terminal 101 can prompt the user to input the voice sent to the contact "Kate" in response to the user operation on the control 309A. The text input box 309B can be used to monitor user operations, and the sending end 101 can display a virtual keyboard in response to the user operations on the control 309B for the user to input the text sent to the contact "Kate". The control 309C can be used to monitor user operations, and the sender 101 can display more functional service options in response to user operations on the control 309C, such as options for taking pictures, and equipment for initiating association with the contact "Kate" Options for video calls between users, options for transferring money to the contact "Kate", etc.

2. Figures 3C-3E show an embodiment in which a user selects a file and shares it with the selected contact after selecting a contact in the application.

FIG. 3C exemplarily shows a plurality of function service options displayed by the sending end 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 multiple function service options include "hishare file transfer" 310.

The "hishare file transfer" option 310 is used to monitor user operations (such as click operations, touch operations, long-press operations, etc.). The sender 101 can respond to the user operations detected on the "hishare file transfer" option 310 and display A user interface for displaying one or more files stored on the sending end 101.

In some embodiments, when the "hishare" of the sender 101 has not been turned on, the sender 101 may also enable "hishare" in response to a user operation detected on the "hishare file transfer" option 310.

FIG. 3D exemplarily shows a user interface 33 on the sending end 101 for displaying one or more files stored by the sending end 101. As shown in the figure, the user interface 33 may include: a status bar 311, a control 312A, a control 312B, and a file area 313.

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

The control 312A can be used to monitor user operations, and the sending end 101 can display a user interface 32 as shown in FIG. 3C in response to the user operation detected on the control 312A.

The control 312B can be used to monitor user operations. The sender 101 can respond to the user operation detected on the control 312B, and send the file selected by the user in the file area 313 to the selected contact "Kate" in the first application. "Associated device. In some embodiments, the control 312B can only receive user operations after the user selects a file in the file area 313. Optionally, 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 remind the user that the control 312B cannot receive user operations.

The file area 313 may display thumbnails or names of one or more files, such as thumbnails of pictures (such as picture thumbnails 313A, picture thumbnails 313B), video thumbnails (such as video thumbnails 313C), Name (such as the name of the Word format document "Novel 1" 313D) and so on. The file corresponding to the thumbnail or name of the file, such as the original image corresponding to the picture thumbnail 313A, the original video corresponding to the video thumbnail 313C, etc., may be stored on the sending terminal 101. When the sending end 101 detects an upward or downward sliding operation in the file area 313, the sending end can update the content displayed in the file area 313 so that the user can browse more file thumbnails or names. Not limited to the upward or downward sliding operation, the user can also slide left or right in the file area 313 to browse the thumbnails or names of more files.

The user can input a user operation 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, etc., acting on the thumbnail or name of the file. For example, the user can click on the image thumbnail 313A, the image thumbnail 313B, and the name "Novel 1" 313D in the file area 313, and select the corresponding file such as the original image corresponding to the image thumbnail 313A, the original image corresponding to the image thumbnail 313B, The file corresponding to the name "Novel 1" 313D is selected as the 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 the thumbnail or name selected by the user in the file area 313. The mark 313E may indicate that the thumbnail or the file corresponding to the name has been User choice.

Fig. 3E exemplarily shows an embodiment in which the user shares the selected file with the contact "Kate" in the first application. As shown in FIG. 3E, the sending terminal 101 may detect a user operation for sharing the selected file to the contact on the user interface 33, and the user operation may be an operation acting on the control 312B (for example, a click operation, Touch operation), the sending end 101 can transmit the file selected by the user to the device associated with the contact "Kate" in the first application in response to the user operation. Not limited to the operation of first selecting a file and then clicking the control 312B, the sender 101 can also transmit the file selected by the user to the device associated with the contact "Kate" in the first application in response to other forms of operation, for example, it can also In response to the user's operation of shaking the sending terminal 101 after selecting a file, for example, the file can be transferred in response to a voice control operation or the like.

The device associated with the contact refers to the device used when the contact currently logs in to the first application. In this embodiment of the present application, the device associated with the contact selected by the user is the receiving end 102. In other words, the contact selected by the user in the first application is an associated user of the receiving terminal 102.

How the sender 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 receiver 102, can refer to the detailed description of the subsequent embodiments. Do not go into details.

In the embodiment of the present application, the sending end 101 transmits the file selected by the user to the receiving end 102 through "hishare". For the specific implementation of the transmission process, please refer to the detailed description of the subsequent embodiments, which will not be repeated here.

In some embodiments, the sending end 101 responds to the detected user operation for sharing the selected file to the contact, and after transmitting the selected file to the receiving end 102, it may be shown in FIG. 3F-figure. Prompt information 315 is displayed in one or more exemplary file transfer records 314 shown in 3I. The prompt information 315 is used to prompt the user of the transmission status of the selected file, which can make the user know the transmission status of the selected file very intuitively, and improve the user experience. In some other embodiments, the prompt information 315 may not be a visual interface element displayed on the display screen, but may be audio played through the speaker 170A.

3. FIG. 3F-FIG. 3I show the user interface on the sending end 101 for feedback of the file transmission status.

After the sending end 101 responds to the operation of sharing the selected file to the contact and transmits the file to the receiving end 102, as shown in FIG. 3F-FIG. 3I, the sending end 101 may exemplify the user as shown in FIG. 3C. The file transfer record 314 is displayed in the communication record 308 of the interface 32. Among them, the user interface 32 is a user interface for displaying the communication records of the associated user of the sending terminal 101 and the contact "Kate". In this way, the user can communicate with the contact in the user interface 32, for example, sending text, voice, and so on.

As shown in FIGS. 3F-3I, the file transfer record 314 may include: the avatar of the associated user of the sending end 101, the thumbnail or name of one or more files selected by the user, and prompt information 315. The prompt message 315 is used to indicate the transmission status of the file selected by the user.

As shown in FIG. 3F, the prompt message 315 may be used to prompt the user that the transmission state of the file selected by the user is the first transmission state. The first transmission state may mean that the file selected by the user is waiting to be received by the receiving terminal 102. The prompt message 315 may include one or more of the following: the text message "waiting to be received by the other party", and a shadow covering all the file thumbnails or names. In some embodiments, when the sending end 101 displays the prompt message 315 as shown in FIG. 3F, it may also display a control for canceling the file transfer in the file transfer record 314. The control can be implemented as the text "Cancel Transfer". Cancelling the file transmission means that the sending end 101 does not send the file to the receiving end 102.

As shown in FIG. 3G, the prompt message 315 can be used to prompt the user that the transmission state of the file selected by the user is the second transmission state. The second transmission state may mean that the file selected by the user is being transmitted to the receiving end 102. The prompt information 315 may include one or more of the following: text information "Sending", a progress bar, and a shadow on the thumbnail or name of the covered part of the file.

As shown in FIG. 3H, the prompt message 315 may be used to prompt the user that the transmission state of the file selected by the user is the third transmission state. The third transmission state may mean that the file selected by the user is successfully transmitted to the receiving end 102. The prompt information 315 may include one or more of the following: text information "send successfully" and a progress bar.

As shown in FIG. 3I, the prompt message 315 can be used to prompt the user that the transmission state of the file selected by the user is the fourth transmission state. The fourth transmission state may mean that the file selected by the user has not been successfully transmitted to the receiving end 102. The prompt information 315 may include one or more of the following: text information "sending failed", a progress bar, and shadows on thumbnails or names of all files. In some embodiments, when the sending end 101 displays the prompt message 315 as shown in FIG. 3I, it may also display a control for retransmitting the file in the file transfer record 314. The control can be implemented as the text "Retransmit". Retransmitting the file means that the sending end 101 sends the file selected by the user to the receiving end 102 again. The reason why the file selected by the user is not successfully transmitted to the receiving end 102 may include but is not limited to: there is no device associated with the selected contact among the devices near the sending end 101, and there is a problem between the sending end 101 and the receiving end 102. The communication connection is interrupted, etc., which is not limited in the embodiment of the present application.

It is not limited to the several prompt messages shown in FIGS. 3F-31. In some other embodiments, the sending end 101 may also display other prompt messages, for example, to remind the user that some of the files selected by the user have been successfully transmitted to The prompt information of the receiving terminal 102, the prompt information used to prompt the user contact to refuse to accept the file, and so on.

Through the UI embodiments exemplarily shown in FIGS. 3A to 3I, after the user selects a contact in the first application, the sending end 101 can be triggered to send the selected file to the receiving end 102. In this way, the sender 101 can share files through "hishare" in the first application, and the user experience is intuitive and simple, which greatly improves the efficiency of sharing files in the application.

In the above-mentioned (1) scenario where the user first selects a contact and then selects a file to share, it is not limited to the UI embodiment shown in FIGS. 3A-3I. The sending end 101 may also execute the method provided in the embodiment of this application. Some other UI examples are displayed at the same time. Several related extensions to the above-mentioned UI embodiments shown in FIGS. 3A to 3I will be introduced below.

1. Extension 1: Related extensions to the UI embodiment shown in Figure 3C

As shown in FIG. 3C, the sending end 101 may display a plurality of functional service options in response to a user operation detected on the control 308C in the user interface 32 shown in FIG. 3B, and the multiple functional service options include "hishare file transfer" Option 310. In addition, the "hishare file transfer" option 310 can receive a user operation, and the sending end 101 can display a user interface 33 as shown in FIG. 3D in response to the user operation.

It is not limited to the manner shown in FIG. 3C. In the embodiment of the present application, the sending end 101 may also display the "hishare file transfer" option in the manner described in (1) or (2) below.

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

Referring to FIGS. 4A-4C, it shows an implementation manner in which the sender 101 displays the "hishare file transfer" option 310. In some embodiments of the present application, FIGS. 3B-3C in the file sharing process shown in FIGS. 3A-3I can be replaced with FIGS. 4A-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 related descriptions.

The user interface 32 shown in FIG. 4B may include multiple functional service options displayed by the sending terminal 101 in response to a user operation detected on the control 309C in the user interface 32 shown in FIG. 4A. As shown in FIG. 4B, before the sending end 101 determines that it can transfer files with the receiving end 102 through "hishare", the multiple function service options displayed by the sending end 101 do not include the "hishare file transfer" option.

As shown in FIG. 4C, after a period of time, if the sending end 101 determines that it can transfer files with the receiving end 102 through "hishare", the sending end can newly display a "hishare file transfer" option 310 in the user interface 32. In some embodiments, in order to newly display the "hishare file transfer" option 310 in the user interface, the sender can adjust the arrangement of each function service option, for example, reduce the distance between each function service option, and stop displaying a certain function. There are no restrictions on this in the embodiment of the present application.

The "hishare file transfer" option shown in FIG. 4C is the same as the "hishare file transfer" option in FIG. 3C, which can be used to monitor user operations. You can refer to related descriptions, which will not be repeated here.

Through the expansion in point (1) above, the sender 101 will display the “hishare file transfer” option 310 after confirming that it can transfer files with the receiver 102 via “hishare”, so that it can be used when the user wants to transfer files via “hishare” When a file is given to a contact, the probability of the file being successfully transferred is increased, and the user has a better experience.

(2) The sending end 101 may display the “hishare file transfer” option 310 that can receive user operations after determining that it can transfer files with the receiving end 102 through “hishare”.

Referring to FIGS. 4D-4F, it shows another implementation manner in which the sender 101 displays the "hishare file transfer" option 310. In some embodiments of the present application, the embodiments of FIGS. 3B-3C in the file sharing process shown in FIGS. 3A-3I can be replaced with FIGS. 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 related descriptions.

The user interface 32 shown in FIG. 4E may include multiple functional service options displayed by the sending terminal 101 in response to a user operation detected on the control 309C in the user interface 32 shown in FIG. 4A. Before the sender 101 determines that the file can be transferred with the receiver 102 through "hishare", the "hishare file transfer" option 310 among the multiple functional service options displayed by the sender 101 cannot receive user operations. The "hishare file transfer" option 310 cannot receive user operations means that the sender 101 does not display a user interface for displaying the files stored by the sender 101 in response to the user operation on the "hishare file transfer" option 310.

In some embodiments, before the sending end 101 determines that the file can be transferred with the receiving end 102 via "hishare", a prompt message may be displayed on the user interface 32 to prompt that it is not currently possible to transfer the file with the receiving end 102 via "hishare". . The prompt information may include, but is not limited to: shadows, text information, animations, etc., overlaid on the "hishare file transfer" option 310 shown in FIG. 4E.

As shown in FIG. 4F, after a period of time, if the sending end 101 determines that it can transfer files with the receiving end 102 through "hishare", the "hishare file transfer" option 310 in the user interface 32 displayed by the sending end 101 can be used to receive user operations . The “hishare file transfer” option 310 that can receive user operations means that the sender 101 can display a user interface for displaying the files stored by the sender 101 in response to the user operation on the “hishare file transfer” option 310.

The situations in which the sending end 101 and the receiving end 102 can transfer files through "hishare" include:

Case 1. When the sending end 101 sends a file to the receiving end 102 through one or more of the wireless communication technologies of Bluetooth, Wi-Fi direct connection (such as Wi-Fi p2p), and Wi-Fi softAP, the sending end 101 and A communication connection has been established between the receiving ends 102. This communication connection is used for file transfer between the sending end 101 and the receiving end 102.

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

Case 3. When the sending end 101 sends a file to the receiving end through wireless communication technologies such as Wi-Fi LAN, the sending end 101 and the receiving end 102 are in the same LAN.

Through the expansion in point (2) above, after the sender 101 determines that it can transfer files with the receiver 102 through "hishare", it displays the "hishare file transfer" option 310 that can receive user operations, so that the user can accurately know the current Is it possible to transfer files to contacts through "hishare" to increase the probability of files being successfully transferred and give users a better user experience.

2. Extension 2: Regarding the relevant extension of the UI embodiment shown in Figure 3C

As shown in FIG. 3C, the sending end 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, and the multiple functional service options include "hishare file transfer" Option 310. In addition, the "hishare file transfer" option 310 can receive a user operation, and the sending end 101 can display a user interface 33 for displaying the file stored by the sending end 101 in response to the user operation. The sending end 101 may send the file selected by the user in the user interface 33 to the receiving end 102 through "hishare".

It is not limited to the manner shown in FIG. 3C. In some other embodiments of the present application, the sending end 101 may display multiple functional service options in response to a user operation detected on the control 309C in the user interface 32 shown in FIG. 3B. The "hishare file transfer" option 310 may not be included in the multiple function service options. When a user shares a file with a contact through these functional service options, the sending end 101 can send the file to the receiving end 102 through “hishare”.

5A-5I show the user interface implemented on the sending end 101 under extension 2. In some embodiments of the present application, the embodiment of FIGS. 3A-3E in the file sharing process shown in FIGS. 3A-3I can be replaced with FIGS. 5A-5E, and FIGS. 3F-3I can be replaced with FIG. 5F -Figure 5I.

First, Figures 5A-5B show an embodiment 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.

Secondly, Figures 5C-5E show an embodiment in which the user selects a contact in the application and then selects a file to share with the contact.

FIG. 5C exemplarily shows a plurality of function service options displayed by the sending end 101 in response to a user operation detected on the control 309C in the user interface 52 shown in FIG. 5B. The difference between Fig. 5C and Fig. 3C is that the user interface 52 shown in Fig. 5C does not include the "hishare file transfer" option. As shown in FIG. 5C, the multiple functional service options in the user interface 52 include an option 501 for sharing pictures and/or videos.

Option 501 is used to monitor user operations (for example, click operations, touch operations, long-press operations, etc.). The sender 101 can respond to the user operations detected on the option 501 to display one or more of the stored information of the sender 101. A picture and video user interface. In the case that the "hishare" of the sending end 101 has not been turned on, the sending end 101 may also enable the "hishare" in response to the user operation detected on the option 501.

FIG. 5D exemplarily shows a user interface 53 on the sending end 101 for displaying one or more pictures and videos stored by the sending end 101. As shown in the figure, the user interface 53 may include: a status bar 502, a control 503A, a control 503B, and a file area 504.

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

The control 503A can be used to monitor user operations, and the sending end 101 can display a user interface 52 as shown in FIG. 5C in response to the user operation detected on the control 503A.

The control 503B can be used to monitor user operations, and the sending end 101 can send the file selected by the user in the file area 504 to the device associated with the contact "Kate" of the first application in response to the user operation detected on the control 503B. . In some embodiments, the control 503B can only receive user operations after the user selects a file in the file area 504. Optionally, 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 remind the user that the control 503B cannot receive user operations.

One or more thumbnails of pictures and videos may be displayed in the file area 504, such as thumbnails of pictures (such as picture thumbnail 504A), thumbnails of video (such as video thumbnail 504B), and so on. The original images, original videos, etc. corresponding to the thumbnails of the pictures and videos can be stored on the sending terminal 101. When the sending end 101 detects an upward or downward sliding operation in the file area 504, the sending end may update the content displayed in the file area 504 so that the user can browse more thumbnails of pictures and/or videos. Not limited to the upward or downward sliding operations, the user can also slide left or right in the file area 504 to browse more thumbnails or names of pictures and/or videos. In some embodiments, a control 504C may also be displayed in the file area 504. The sending terminal 101 may update the content displayed in the file area 504 in response to an operation input by the user on the control 504C (for example, a click operation, a touch operation, etc.), so that the user can browse more thumbnails of pictures and/or videos.

The user can input a user operation 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, etc., acting on the thumbnail of the picture and/or video. For example, the user can click on the image thumbnail 504A and the video thumbnail 504B in the file area 504, and determine the corresponding file, such as the original image corresponding to the image thumbnail 504A, and the original video corresponding to the video thumbnail 504B, as to be shared with the contact. Kate’s file. In some embodiments, as shown in FIG. 5E, the sender may also display a mark 504D on the thumbnail selected by the user in the file area 504. The mark 504D may indicate that the original picture or original video corresponding to the thumbnail has been selected by the user. Selected.

Fig. 5E exemplarily shows an embodiment in which the user shares the selected file with the contact "Kate" in the first application. As shown in FIG. 5E, the sender 101 can detect a user operation for sharing the selected picture and/or video to the contact in the user interface 53, and the user operation can be an operation on the control 503B ( For example, click operation, touch operation). The sending end 101 may transmit the picture and/or video selected by the user to the device associated with the contact "Kate" in the first application in response to this operation. Not limited to the operation of clicking the control 503B, the sending terminal 101 can also transmit the pictures and/or videos selected by the user to the device associated with the contact "Kate" in the first application in response to other forms of operation, for example, it can also In response to the user's operation of shaking the sending terminal 101, for example, it may also respond to a voice control operation, etc., to send the picture and/or video selected by the user to the device associated with the contact "Kate" and so on.

Here, in response to the user operation for sharing the selected picture and/or video to the contact, the sending end 101 sends the picture and/or video selected by the user to the receiving end 102 according to any one of the following Kinds of strategies to send:

Strategy 1. After determining that the sending end 101 can transmit files with the receiving end 102 through "hishare", it directly sends the file selected by the user to the receiving end 102 through "hishare". If the sending end 101 determines that the file cannot be transferred with the receiving end 102 through "hishare", the file selected by the user is sent to the receiving end 102 through 3G, LTE, 5G or other cellular technologies or Wi-Fi technology. For the situation that the sending end 101 and the receiving end 102 can transfer files through "hishare", please refer to the related description in the first point extension 1 above.

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

Strategy 3. The sending end 101 asks the user whether to send the file selected by the user to the receiving end 102 through "hishare", and when it detects the user's operation instructing to send the selected file through "hishare", it passes "hishare" The file selected by the user is sent to the receiving terminal 102. The sending end 101 can output visual interface elements, voice, etc. displayed on the display screen to ask the user whether to send the file selected by the user to the receiving end 102 through "hishare". This strategy can enable the sending end 101 to send the selected file through "hishare" according to the user's needs.

For the specific implementation of the process in which the sending end 101 sends the file selected by the user to the receiving end 102 through "hishare", reference may be made to the detailed description of the subsequent embodiments, which will not be repeated here.

Finally, FIG. 5F-FIG. 5I show the user interface on the sending end 101 for feedback of the file transmission status.

After the sending end 101 transmits the file selected by the user to the receiving end 102 in response to the operation for sharing the file selected by the user to the contact, as shown in FIG. 5F-FIG. 5I, the sending end 101 can be shown in FIG. The file transfer record 505 is displayed in the communication record 308 of the user interface 32 exemplarily shown in 5C.

The file transfer record 505 includes prompt information 506. For the specific implementation of the file transmission 505, refer to the file transmission record 314 shown in FIGS. 3F-3I.

As shown in FIG. 5F, the prompt message 506 can be used to prompt that the transmission state of the selected file is the first transmission state. For the first transmission status, refer to the previous description. The prompt information 506 may refer to the prompt information 315 shown in FIG. 3F.

As shown in FIG. 5G, the prompt message 506 can be used to prompt that the transmission state of the selected file is the second transmission state. For the second transmission state, refer to the previous description. The prompt information 506 may refer to the prompt information 315 shown in FIG. 3G.

As shown in FIG. 5H, the prompt message 506 can be used to prompt that the transmission state of the selected file is the third transmission state. For the third transmission state, refer to the previous description. The prompt information 506 may refer to the prompt information 315 shown in FIG. 3H.

As shown in FIG. 5I, the prompt message 506 can be used to prompt that the transmission state of the selected file is the fourth transmission state. For the fourth transmission state, refer to the previous description. For the prompt information 506, refer to the prompt information 315 shown in FIG. 3I.

Through the UI embodiments exemplarily shown in FIGS. 5A-5I, after the associated user of the sending end 101 selects a contact in the first application, the sending end 101 can be triggered to send the selected file to the receiver through the function service option.端102. In this way, the sender 101 can share files through "hishare" in the first application, and the user experience is intuitive and simple, which greatly improves the efficiency of sharing files in the application. With the UI embodiments exemplarily shown in FIGS. 5A-5I, the sending end 101 does not need to provide a special "hishare file transfer" option, and when the user triggers the sending end 101 to send the selected file to the receiving end 102, through "Hishare" sends the file to the receiving end 102.

(2) Scenario 2: The user selects the file first, and then selects the contact to share.

6A-6H exemplarily show the user interface displayed by the sending end 101 in the second scenario.

1. Figures 6A-6B show an embodiment in which a user selects a file.

FIG. 6A exemplarily shows the user interface 61 of the second application (for example, "Gallery") displayed by the sending end 101. The user interface 61 may be used to display one or more pictures and/or videos stored in the sending terminal 101. The second application program can support the user to perform various operations on the files stored on the sending terminal 101, such as browsing, editing, deleting, and selecting operations. "Gallery" is a picture management application installed on smart phones, tablet computers and other electronic devices, and can also be called "album". This embodiment does not limit the name of the application. That is, the objects managed by the "Gallery" are pictures and/or videos.

As shown in FIG. 6A, the user interface 61 may include: a status bar 601, a title bar 602, and a picture area 603. among them:

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

The title bar 602 may include a current page indicator, for example, the text information "Gallery". Not limited to text information, the current page indicator can also be an icon.

One or more thumbnails of pictures and videos may be displayed in the picture area 603, such as picture thumbnails (such as picture thumbnail 603A), video thumbnails (such as video thumbnail 603B), and so on. The original images, original videos, etc. corresponding to the thumbnails of the pictures and videos can be stored on the sending terminal 101. When the sending end 101 detects an upward or downward sliding operation in the picture area 603, the sending end may update the content displayed in the picture area 603, so that the user can browse more thumbnails of pictures and/or videos. Not limited to the upward or downward sliding operation, the user can also swipe left or right in the picture area 603 to browse more thumbnails or names of pictures and/or videos. In some embodiments, a control 603C may also be displayed in the picture area 603. The sending terminal 101 may update the content displayed in the picture area 603 in response to an operation input by the user on the control 603C (for example, a click operation, a touch operation, etc.), so that the user can browse more thumbnails of pictures and/or videos.

The user can input a user operation in the picture area 603 to select a picture and/or video. The user operation may be a click operation, a touch operation, etc., acting on the thumbnail of the picture and/or video. For example, the user can click on the picture thumbnail 603A and the video thumbnail 603B in the picture area 603 to determine the corresponding files such as the original image corresponding to the picture thumbnail 603A and the original video corresponding to the video thumbnail 603B as the ones to be shared with the contact. file. In some embodiments, as shown in FIG. 6B, the sender may also display a mark 603D on the thumbnail selected by the user in the picture area 603. The mark 603D may indicate that the original picture or original video corresponding to the thumbnail has been selected by the user. select.

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

The operation for sharing the selected file may be: the user clicks the "hishare file transfer" option 604A after selecting the file. In some embodiments, when the sending terminal 101 detects the user's operation of selecting a file in the user interface 61, the menu 604 in FIG. 6B may be displayed in the user interface 61. In other embodiments, the sending end 101 may also initially display the menu 604 in the user interface 61, that is, the menu 604 does not need to be detected after the user selects a file. The menu 604 may include a "hishare file transfer" option 604A, an option 604B ("move"), an option 604C ("select all"), and an option 604D "more". The "hishare file transfer" option 604A can be used to monitor the operation of sharing the selected file through "hishare". In the case that the "hishare" of the sending end 101 has not been turned on, the sending end 101 may also enable the "hishare" in response to a user operation detected on the "hishare file transfer" option 604A.

It is not limited to the operation of first selecting the file and then clicking the "hishare file transfer" option 604A. The operation for sharing the selected file can also be implemented in other forms, for example, it can also be a fixed time (such as 1 second) after shaking the sending end 101 ) Select file operation, voice control operation, etc.

2. Figures 6C-6D show an embodiment in which a user selects an application and a contact in the application, and shares a file with the contact.

As shown in FIG. 6C, the sending end 101 responds to the operation for sharing the selected file (for example, the operation input on the “hishare file transfer” option 604A after the user selects the file), and displays a window 605 in the user interface 61. The window 605 can obscure part of the content originally displayed in the user interface 61.

The window 605 may include: one or more application options, for example, an option 605C of "Hi Chat" and an option 605D of an email address. The implementation form of the application options can be text, icons, and so on. The application corresponding to the application options included in the window 605 can be any of the following:

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

(2) Among the applications that can be used to share files installed on the sending end 101, the applications that can currently share files through "hishare". After the user logs in to the application installed on the sending terminal 101, if the device associated with the contact in the application can transfer files with the sending terminal 101 through "hishare", the application is an application that can share files through "hishare" program. For example, if a user logs in to the HiChat installed on the sending terminal 101, the device 102 on which the contact Kate in HiChat is currently logged in can transfer files with the sending terminal 101 through "hishare", and the user also logs in to the mailbox installed on the sending terminal 101 at the same time. The contact person in the mailbox that William is currently logged in to the device 102' cannot transfer files with the sender 101 via "hishare". At this time, the sender 101 only displays the options of the HiChat application in the window 605, and does not display in the window 605 Options for email application. For the situation that the sending end 101 can transfer files with other devices through "hishare", please refer to the related description in the extension 1 of the above scenario 1. This can avoid the problem that users choose inappropriate applications and cause file sharing failures.

In some embodiments, the window 605 may also include prompt information 605B. The prompt message 605B is used to prompt the user to select an application program for sharing the selected file. For example, the prompt message 605B may be the text message "Which application do you want to share the file through".

In some embodiments, the window 605 may also include prompt information 605A. The prompt message 605A is used to prompt the user to share the condition of the file to other devices through "hishare". For example, the prompt message 605A may be a text message "Note: When sharing files through hishare, the other party needs to turn on Bluetooth and WLAN".

The application options in the window 605 can be used to monitor user operations (such as click operations, touch operations, etc.), and the sender 101 can respond to the user operations to display for the user to select the contacts in the corresponding application to share the file. interface. In the embodiment of the present application, the application corresponding to the application option selected by the user may be referred to as the first application.

Referring to FIG. 6D, FIG. 6D is an implementation manner of a user interface provided by the first application program for the user to select a contact to share the selected file. The user interface 62 shown in FIG. 6D may be displayed by the sending end 101 in response to a user operation detected on the control 605C.

As shown in FIG. 6D, the user interface 62 may include: a status bar 606, a title bar 607, prompt information 608, and one or more contact options. among them:

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

The title bar 607 may include an indicator of the current page, for example, the text message "Hi Chat". Not limited to text information, the current page indicator 607 may also be an icon.

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

One or more contact options, such as the contact "MAC" option 609A and the contact "Kate" option 609B, can be used to monitor the operation of selecting a contact to trigger file sharing. The sender 101 may respond to the operation detected on the contact option, and send the file selected by the user to the device associated with the contact corresponding to the contact option through "hishare". In some embodiments, the electronic device associated with the contact corresponding to one or more contact options in the user interface 62 can transfer files with the sender 101 through "hishare". In this way, it is possible to avoid the problem that the user selects inappropriate contacts and causes the file sharing failure.

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

3. Figures 6E-6H show the user interface on the sending end 101 for feedback of the file transmission status.

In some embodiments, in response to the operation detected on the contact option, the sender 101 sends the file selected by the user to the device associated with the contact corresponding to the contact option via "hishare", as shown in Figure 6E -As shown in FIG. 6H, the sending end 101 may display the file transfer record 610 in the user interface for displaying the communication record of the user and the contact.

6E-6H show the user interface 63 for displaying the communication records of the user and the contact "Kate".

As shown in FIGS. 6E-6H, the file transfer record 610 includes prompt information 611. For the specific implementation of the file transmission 505, refer to the file transmission record 314 shown in FIGS. 3F-3I.

As shown in FIG. 6E, the prompt message 611 can be used to prompt that the transmission state of the selected file is the first transmission state. For the first transmission status, refer to the previous description. The prompt information 611 may refer to the prompt information 315 shown in FIG. 3F.

As shown in FIG. 6F, the prompt message 611 can be used to prompt that the transmission state of the selected file is the second transmission state. For the second transmission state, refer to the previous description. The prompt information 611 may refer to the prompt information 315 shown in FIG. 3G.

As shown in FIG. 6G, the prompt message 611 can be used to prompt that the transmission state of the selected file is the third transmission state. For the third transmission state, refer to the previous description. The prompt information 611 may refer to the prompt information 315 shown in FIG. 3H.

As shown in FIG. 6H, the prompt message 611 can be used to prompt that the transmission state of the selected file is the fourth transmission state. For the fourth transmission state, refer to the previous description. The prompt information 611 may refer to the prompt information 315 shown in FIG. 3I.

It is not limited to the several prompt messages shown in Figures 6E-6H. In some other embodiments, the sending end 101 may also display other prompt messages, for example, to prompt that part of the selected file is successfully transmitted to the receiver. The prompt information of the terminal 102 and so on.

Through the UI embodiments shown in FIGS. 6A to 6H, the user can trigger the sending terminal 101 to send the file to the contact in the first application after selecting the file to be shared. In this way, the sender 101 can share files through "hishare" in the first application, and the user experience is intuitive and simple, which greatly improves the efficiency of sharing files in the application.

Not limited to selecting photos, videos and other files in the "Gallery" to share, users can also select files to share in other file management applications, such as selecting documents in the file browser or document manager for sharing.

In the above-mentioned (2) scenario where the user first selects a file and then selects a contact for sharing, it is not limited to the UI embodiment shown in FIGS. 6A-6H. The sending end 101 may also execute the method provided in the embodiment of this application. Some other UI examples are displayed at the same time. The following will introduce several related extensions to the above-mentioned UI embodiments shown in FIGS. 6A to 6H.

1. Extension 1: Regarding the relevant extension of the UI embodiment shown in Figure 6C-Figure 6D

As shown in FIG. 6D, the sending end 101 may display a plurality of contact options in response to the operation detected on the first application option in the user interface 61 shown in FIG. 6C, and the contact information corresponding to the multiple contact options The associated device can transfer files with the sender 101 through "hishare". In other words, the user can first select the first application, and then select a contact in the user interface provided by the first application to share the file.

It is not limited to the manner shown in FIG. 6D. In the embodiment of the present application, the user can also select a contact to share a file in the manner described in (1) or (2) below.

(1) In some embodiments, the sending end 101 may respond to the operation detected on the first application option in the user interface 61 shown in FIG. 6C, and display one or more items provided by the first application program. User interface for recent contacts options.

7A-7B show an embodiment in which the sender 101 displays a user interface provided by the first application program for displaying one or more recent contact options in response to an operation detected on the first application program option . In some embodiments of the present application, FIGS. 6C-6D in the file transfer process shown in FIGS. 6A-6H can be replaced with FIGS. 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 related descriptions.

FIG. 7B shows an implementation form of a user interface provided by the first application program for displaying one or more recent contact options. As shown in FIG. 7B, the user interface 71 may include: a status bar 701, a title bar 702, a search box 703, one or more recent contact options, and a menu bar 705.

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

The recent contact options may include options for one or more contacts that the user has communicated with in the first application program recently, and the contact options may include: official account options, user options, group options, and so on. For example, the recent contact options include an option 704A for the contact "MAC" and an option 704B for the contact "Kate".

In some embodiments, the sender 101 may display the contact options corresponding to the contacts whose associated device and the sender 101 can transfer files through "hishare" in the upper area (for example, as shown in FIG. 7B). In other embodiments, the sender 101 may also display an identifier on the contact option corresponding to the contact whose associated device can transfer files with the sender 101 through "hishare". The identifier is used to remind the user that the user can currently use "hishare" "Share the file with the corresponding contact. In this way, it is possible to avoid the problem that the user selects inappropriate contacts and causes the file sharing failure.

(2) In some embodiments, the sender 101 may directly display contact options in one or more applications, so that the user can directly select contacts in the application to share files.

FIG. 7C shows an implementation manner in which the sender 101 directly displays contact options in one or more applications. In some embodiments of the present application, FIGS. 6C to 6D in the file transfer process shown in FIGS. 6A to 6H can be replaced with FIG. 7C.

The difference between FIG. 7C and FIG. 6C is that the content in the small window is different. As shown in FIG. 7C, a small window 706 is displayed in the user interface 72, and the small window 706 includes: prompt information 706A, one or more application icons, and contact options corresponding to the application icons. among them:

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

One or more application icons can be any of the following:

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

b. Among the applications installed on the sending end 101 that can be used to share files, the device associated with the contact can transfer files with the sending end 101 through "hishare". In some embodiments, the sending end 101 may first determine whether there is a contact-associated device in the installed application that can transfer files with the sending end 101 through "hishare", and if so, the option corresponding to the application is displayed in Window 706. For the situation that the sending end 101 can transfer files with other devices through "hishare", please refer to the related description in point 1 extension 1 of the above scenario 1. This can avoid the problem that users choose inappropriate contacts and cause file sharing failures.

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

One application icon can correspond to one or more contact options. The contacts corresponding to the one or more contact options are all: the user's contacts in the application corresponding to the application icon. The contact corresponding to the one or more contact options may be: a contact whose associated device can transfer files with the sender 101 through “hishare”. In this way, it is possible to avoid the problem that the user selects inappropriate contacts and causes the file sharing failure.

As shown in FIG. 7C, the icon 706B of "Hi Chat" corresponds to the option 706C of the contact "MAC", the option 706D of the contact "Kate", and the icon 706E of the mailbox corresponds to the option 706F of the contact "Mark".

Contact options can be used to monitor user operations (such as click operations, touch operations, etc.). The sender 101 can respond to the user operations detected on the contact options and pass the file selected by the user in the corresponding application. hishare" is sent to the contact corresponding to the contact option.

In some embodiments, the sender 101 may also display a user interface for displaying communication records between the user and the contact in response to a user operation detected on the contact option, and display the file transfer record in the user interface . For the user interface used to display the communication records between the user and the contact, please refer to the user interface 63 shown in FIGS. 6E-6H, and the file transfer record may refer to the file transfer record 314 in FIGS. 6E-6H, which will not be repeated here. .

Through the expansion in point (2) above, the sender 101 can directly display the contact options in one or more applications, so that the user can directly share the file to the corresponding contact by selecting the contact option. This method is intuitive and simple for users, and can improve user experience.

2. Extension 2: Regarding the relevant extension of the UI embodiment shown in Figure 6B-Figure 6C

As shown in FIGS. 6B-6C, the sending end 101 may display a menu 604 in the user interface 61 after the user selects a file. The menu 604 includes a "hishare file transfer" option 604A. In addition, the "hishare file transfer" option 604A can receive a user operation, and the sender 101 can display a window 605 in response to the user operation, so that the user can select an application to share the file.

It is not limited to sharing files through the "hishare file transfer" option shown in FIG. 6B-FIG. 6C, and files can also be shared through other service options. In some embodiments, the sender 101 may display a menu that does not include the "hishare file transfer" option in the user interface after the user selects a file. When the user shares a file with a contact through the function service option in the menu, the sender can send the file to the device associated with the contact through "hishare".

Figures 7D-7E show the user interface implemented on the sender under extension 2. In some embodiments of the present application, FIGS. 6B-6C in the file sharing process shown in FIGS. 6A-6H can be replaced with FIGS. 7D-7E.

FIG. 7D exemplarily shows the menu 707 displayed on the user interface 71 after the user selects a file by the sending terminal 101. The difference between FIG. 7D and FIG. 6B is that the menu 707 of the user interface shown in FIG. 7D does not include the "hishare file transfer" option, but includes an option 707A for sharing pictures and/or videos.

Option 707A is used to monitor user operations (such as click operations, touch operations, long-press operations, etc.), and the sending end 101 may display a window 708 in the user interface shown in FIG. 7E in response to the user operation detected on option 707A. In the case that the "hishare" of the sending end 101 has not been turned on, the sending end 101 may also enable the "hishare" in response to the user operation detected on the option 707A.

As shown in FIG. 7E, the window 708 may include: prompt information 708A, one or more service options such as icon 708B, icon 708C, icon 708D, icon 708E. The prompt message 708A is used to prompt the user to select a way to share the file. The application or protocol corresponding to the service option can support sharing the file selected by the user to other devices. In some embodiments, in response to an operation (such as a touch operation, a click operation) detected on a service option, the sender 101 may trigger to share the selected file to other devices through the application or protocol corresponding to the service option the process of. For example, in response to an operation detected on the icon 708B, the sender 101 may start the application "Hi Chat", and display the user interface shown in FIG. 6D or FIG. 7B, in which the user interface is detected to act on the contact option In response to the operation, the selected file is sent to the device associated with the contact corresponding to the contact option. The device associated with the contact is referred to as the receiving end 102 in the following embodiment.

Here, when the sending end 101 sends the selected file to the receiving end 102 through the application, it can be sent according to any one of the following strategies:

(1) After the sending end 101 determines that it can transfer files with the receiving end 102 through "hishare", it directly sends the picture and/or video selected by the user to the receiving end 102. If the sending end 101 determines that the file cannot be transferred with the receiving end 102 through “hishare”, it will send the pictures and/or videos selected by the user to the receiving end 102 through 3G, LTE, 5G and other cellular technologies 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 the first threshold, it sends the file selected by the user to the receiving end 102 through "hishare". 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 3G, LTE, 5G, or other cellular technology or Wi-Fi technology.

(3) The sending end 101 asks the user whether to send the file selected by the user to the receiving end 102 through "hishare", and when it detects the user's operation instructing to send the selected file through "hishare", it passes "hishare" The file selected by the user is sent to the receiving terminal 102. The sending end 101 may output visual interface elements, voices, etc. displayed on the display screen to ask the user whether to send the selected file to the receiving end 102 through “hishare”. This strategy can enable the sending end 101 to send pictures and/or videos through "hishare" according to user requirements.

(3) Scenario 3: The user chooses a group to share files

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

8A-8I exemplarily show the user interface displayed by the sending end 101 in the third scenario.

1. Figures 8A-8B show an embodiment in which a user selects 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 related descriptions.

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 display the communication records 802 of the associated users of the sending end 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. among them:

The current page indicator 801 is used to indicate the current page, for example, the text information "workgroup" is used to indicate that the current page is a page for communication between the associated user of the sending end 101 and the group "workgroup".

The control 803 can be used to monitor user operations, and the sender 101 can display more functional service options in response to user operations on the control 803, such as options for taking pictures, options for sending the current location of the sender 101, etc. Wait.

2. Figures 8C-8E show an embodiment in which the user selects a group in the application and then selects a file to share with the contacts in the group.

FIG. 8C exemplarily shows a plurality of function service options displayed by the sending end 101 in response to a user operation detected on the control 803 in the user interface 82 shown in FIG. 8B. As shown in FIG. 8C, the multiple function service options include a "hishare file transfer" option 804. The “hishare file transfer” option “hishare file transfer” option 804 can refer to the “hishare file transfer” option “hishare file transfer” option 310 in FIG. 3C.

FIG. 8D exemplarily shows a user interface 83 on the sending end 101 for displaying one or more files stored by the sending end 101. The user interface 83 may refer to the user interface 33 shown in FIG. 3D.

Fig. 8E exemplarily shows an embodiment in which the user shares the selected file with the contacts in the group "workgroup" in the first application. For the user interface shown in FIG. 8E, refer to FIG. 3E and related descriptions.

As shown in FIG. 8E, the sending end 101 can detect on the user interface 83 a user operation for sharing the selected file to the contacts in the group "workgroup", and the user operation can be applied to the control 805. The sender 101 can respond to the user operation and share the file selected by the user to the device associated with the contact in the group "workgroup" in the first application. . When the sender 101 shares the file selected by the user to the device associated with the contact in the group "workgroup" in the first application, there are several ways:

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

(2) The sender 101 first sends the file selected by the user to the devices associated with some contacts in the group "workgroup", and then the sender 101 and the device that has received the file jointly send the file to the group" The device associated with the contact in the “workgroup” that has not received the file. Optionally, the sender 101 first sends the file selected by the user to the device associated with some contacts in the group "workgroup", and then the device that has received the file (ie, the device associated with some contacts) sends the file again Forward to the device associated with the contact in the group "workgroup" who has not received the file. In some embodiments, the device associated with the part of the contact is a device that can transfer files with the sender 101 through “hishare”.

For example, assuming that the group "workgroup" contains the contact "Kate" and the contact "Mac", the sender 101 can first send the file selected by the user to the device associated with the contact "Kate" via "hishare" , And then the device associated with the contact "Kate" sends the received file to the device associated with the contact "Mac" via "hishare". In a specific example, the sender 101 can transfer files via "hishare" to the device associated with the contact "Kate", but cannot transfer files via "hishare" to the device associated with the contact "Mac", and the contact "Kate" The associated device and the device associated with the contact "Mac" can transfer files through "hishare".

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

3. Figures 8F-8I show a user interface on the sending end 101 for feedback of the file transmission status.

In response to the user operation of sharing the selected file to the contact in the group "workgroup", the sender 101 shares the file selected by the user to the group "workgroup" in the first application. After the person is associated with the device, as shown in FIGS. 8F-8I, the sending end 101 can display the file transfer record 806 in the communication record 802 shown in the user interface 82.

As shown in FIGS. 8F-8I, the file transfer record 806 may include: the avatar of the associated user of the sending end 101, the thumbnail or name of one or more files selected by the user, and prompt information 807.

The prompt message 807 is used to indicate the transmission status of the file selected by the user to each contact in the group "workgroup". The transmission state of the file that the user has selected to be transmitted to each device can be any one of the following: the first transmission state, the second transmission state, the third transmission state, and the fourth transmission state. For the meaning of each transmission state, and the implementation form of the prompt information 807 corresponding to each transmission state, please refer to the related description of the file transmission state in the embodiment of FIG. 3F-3I, which will not be repeated here.

Similar to the extension in scenario 1, the UI embodiment shown in FIGS. 8A to 8I also has corresponding related extensions. For example, in the user interface shown in FIG. 8C, the sender 101 may display the "hishare file transfer" option after determining that the device associated with the contact in the group "workgroup" transmits files through "hishare". "Option 804. For another example, in the user interface shown in Figure 8C, the sender 101 may determine that the device that can be associated with the contact in the group "workgroup" transmits files through "hishare", and then displays that it can receive user operations The "hishare file transfer" option "hishare file transfer" option 804. For the implementation of these related extensions, please refer to the related description in scenario 1, which will not be repeated here.

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

The receiving end 102 is the end that receives the file. In the embodiment of the present application, the receiving end 102 may be a device associated with the contact selected by the associated user of the sending end 101 in the first application, for example, the device associated with the contact "Kate" in the embodiment of FIG. 3A-3I . In other embodiments, the receiving end 102 may include a device associated with a contact in the group selected by the associated user of the sending end 101 in the first application, for example, the group "workgroup" in the embodiment of FIG. 8A-8I. Device associated with each contact in ".

9A-9D exemplarily show the user interface displayed on the receiving end 102.

FIG. 9A shows the notification window 901 displayed by the receiving end 102 in the user interface 91 after the sending end 101 sends the file selected by the user to the receiving end 102. The user interface 91 may be the main interface. The notification window 901 can be used to notify the user that the sending terminal 101 wants to transfer a file to the receiving terminal 102 through "hishare", and to ask the user whether to receive the file. As shown in FIG. 9A, the notification window 901 may include: an application program identification 901A, a prompt message 901B, a control 901C, and a control 901D. among them:

The application identifier 901A is used to indicate the application used when the associated user of the receiving end 101 shares a file. The implementation form of the application program identifier 901A may include an icon, text (for example, the text message "Hi Chat") and so on.

The prompt information 901B is used to indicate the user who initiated the file sharing (for example, the user "Lisa") and file information (for example, the number, size, type, etc. of the file). The prompt information 901B can be implemented in text.

The control 901C can be used to monitor user operations. In response to the user operation detected on the control 901C, the receiving end 102 refuses to receive the file sent by the sending end 101.

The control 901D can be used to monitor user operations. In response to the user operation detected on the control 901D, the receiving end 102 starts to receive the file sent by the sending end 101, and jumps to display the associated user (such as the contact "Kate") and the sending end 101 used to display the receiving end 102 The user interface 92 of the communication records between associated users (for example, the user "Lisa").

9B-9D show a user interface 92 for displaying communication records between users. The user interface may be provided by a first application. The first application is an application for an associated user of the sending end 101 to initiate file sharing, and the first application is also an application for the receiving end 102 to receive files.

As shown in FIGS. 9B-9D, the user interface 92 may include: a page indicator 902 and a communication record 903. among them:

The page indicator 902 is used to indicate that the current page is used to display the communication records between the associated user of the receiving end 102 (for example, the contact "Kate") and the associated user of the sending end 101 (for example, the user "Lisa").

The communication record 903 may include a file transfer record 904. The file transfer record 904 may include: the avatar of the associated user of the sending end 101, the thumbnails or names of one or more files selected by the user on the sending end 101, and prompt information 905. The prompt message 905 is used to prompt the user of the transmission status of the received file.

As shown in FIG. 9B, the prompt information 905 can be used to prompt the user that the file transmission state is the second transmission state.

As shown in FIG. 9C, the prompt information 905 can be used to prompt the user that the file transmission state is the third transmission state.

As shown in FIG. 9D, the prompt information 905 can be used to prompt the user that the file transmission state is the fourth transmission state.

For the specific meaning of the second transmission state, the third transmission state, and the fourth transmission state, as well as the realization form of the prompt information 905 corresponding to each transmission state, please refer to the file transmission state in the embodiment of FIG. 3F-FIG. 3I Relevant descriptions will not be repeated here.

Through the UI embodiments exemplarily shown in FIGS. 9A-9D, the receiving end 102 can prompt the associated user of the receiving end 102 (ie, the contact selected by the user in the above-mentioned embodiment) when a user shares a file for the The associated user chooses whether to receive the file.

In some other embodiments of the present application, the notification window 901 exemplarily shown in FIG. 9A may not be displayed on the main interface but displayed on other user interfaces. For example, the notification window 901 may also be displayed on the sending end 101. The setting interface, the video interface, etc., are not limited in the embodiment of the present application.

It should be noted that the notification window 901 shown in FIG. 9A is not necessary. In some embodiments, the receiving end 102 may not display the notification window 901. When the sending end 101 sends a file to the receiving end 102 via "hishare" At this time, the receiving end 102 directly receives the file from the sending end 101. It is understandable that whether the receiving end 102 displays the notification window 901 can be independently set by the associated user of the receiving end 102, for example, the associated user of the receiving end 102 can set it in the setting interface provided by the receiving end 102.

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

In the embodiment of the present application, the user interface displayed on the receiving end 102 for displaying communication records between users (for example, the user interface 92 shown in FIGS. 9B-9D) may be referred to as the seventh user interface.

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

First, a communication system 1000 for transferring files in applications is introduced.

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 device 1005,..., Electronic device 100n, etc., and server 1004. Exemplarily, the device associated with the user Lisa may be the electronic device 1001, the device associated with the user Kate may be the electronic device 1002, and the device associated with the user Mac may be the electronic device 1003.

Multiple electronic devices include a sending end and a receiving end. The sending end is the end that initiates file sharing, and the receiving end is the end that receives the file.

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

The sending end 1001 may be the sending end 101 mentioned in the foregoing embodiment. The sending end 1001 may be implemented as the electronic device 100 exemplarily shown in FIGS. 1A and 1B. Specifically, the sending end 1001 has one or more of a Bluetooth (BT) module, an NFC module, and a WLAN module. The sender 1001 can detect or scan devices near the sender 1001 through one or more of the Bluetooth (BT) module, NFC module, and WLAN module, so that the sender 1001 can use one of Bluetooth, NFC or WLAN Or multiple wireless communication technologies to discover nearby devices (such as nearby mobile phones, tablets, etc.), and establish a wireless communication connection with the receiving end 1002 in the nearby devices, through one or more wireless communication technologies in Bluetooth or WLAN Share the file to the receiving end 1002. Among them, the Bluetooth (BT) module can provide solutions including one or more of Bluetooth communication in classic Bluetooth (Bluetooth 2.1) or Bluetooth Low Energy (BLE). The WLAN module can provide one or more WLAN communication solutions including Wi-Fi direct, Wi-Fi LAN, or Wi-Fi softAP.

The receiving end 1002 may be the receiving end 102 mentioned in the foregoing embodiment. The receiving end 1002 may be implemented as the electronic device 100 exemplarily shown in FIGS. 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 wireless signals through one or more of a Bluetooth (BT) module, an NFC module, and a WLAN module. Among them, the Bluetooth (BT) module can provide solutions including one or more of Bluetooth communication in classic Bluetooth (Bluetooth 2.1) or Bluetooth Low Energy (BLE). The WLAN module can provide one or more WLAN communication solutions including Wi-Fi direct, Wi-Fi LAN, or Wi-Fi softAP.

The sending end 1001 and the receiving end 1002 are both installed with the same one or more applications, for example, a first application program may be installed. The application may be, for example, an instant messaging application, a mailbox application, and so on.

The server 1004 is a server used to provide services for a certain application installed in the sending end 1001 and the receiving end 1002. For example, the server 1004 may be a server providing services for the first application. The server 1004 provides various services for the sending end 1001 and the receiving end 1002 through application communication, such as communication record backup service, computing service, connection service, and so on.

The server 1004 may associate and store the identification of the user who has registered the first application program and the device identification of the associated device of the user. After the user registers the first application, he can use his user ID and password to log in to the first application on the device. The user's associated device refers to the device currently used when the user logs in to the application.

User identification may include, but is not limited to: account number, avatar, nickname, name, face image, Huawei logo (identity, ID), etc.

The device identifier may include a media access control (MAC) address, an internet protocol (Internet protocol, IP) address, etc., which may indicate a unique device identifier.

Referring to Table 1, Table 1 exemplarily shows several user IDs and device IDs that are associated and stored in the server 1004.

用户标识User ID	设备标识Equipment Identity
账号“Lisa”Account "Lisa"	电子设备1001的设备标识Device identification of electronic device 1001
账号“Kate”Account "Kate"	电子设备1002的设备标识Device identification of electronic device 1002
账号“Mac”Account "Mac"	电子设备1003的设备标识Device identification of electronic device 1003

Table 1

The associated user A. Lisa of the sending end 1001 can use the user ID and password when registering the application to log in to the application on the sending end 1001. Obviously, after the associated user A. Lisa of the sending end 1001 logs in to the application, the sending end 1001 can learn that the user identification of the associated user A. Lisa in the application is "Lisa". In addition, the sender 1001 can also obtain the user ID of the contact of the associated user in the application from the previously stored information or from the server 1004. For example, one of the contacts of the associated user A. Lisa of the sender in the application is J .Kate, the user ID of the contact J.Kate is "Kate".

The associated user J. Kate of the receiving end 1002 can also use the user ID and password when registering the application to log in to the application on the receiving end 1002. Obviously, after the associated user J.Kate of the receiving end 1002 logs in to the application, the receiving end 1002 can learn that the user identifier of the associated user J.Kate in the application is "Kate". In addition, the receiving end 1002 can also obtain the user ID of the contact of the associated user in the application from the previously stored information or from the server 1004. For example, one of the contacts of the associated user J.Kate of the receiving end in the application is A. .Lisa, the user ID of contact A.Lisa is "Lisa".

The sending end 1001 and the server 1004 can be connected by 3G, LTE, 5G and other cellular mobile communication technologies, LAN or WAN communication technologies, which can facilitate the server 1004 to forward the data sent by the sending end 1001 to the receiving end 1002.

The receiving end 1002 and the server 1004 can be connected by LAN or WAN communication technology, which can facilitate the server 1004 to forward the data sent by the receiving end 1002 to the sending end 1001.

In the embodiment of the present application, the sending end 1001 can discover nearby devices through one or more of Bluetooth, NFC, and WLAN wireless communication technologies. The nearby devices can include, for example, electronic devices 1002, electronic devices 1003, and electronic devices 1005. ,..., electronic equipment 100n and so on. Then, the sending end 1001 can determine the device associated with the contact selected by the user in the application among nearby devices, that is, determine the receiving end. Here, if the contact selected by the user is "Kate", the associated device of the contact "Kate", that is, the electronic device 1002 is the receiving end, and the other devices such as electronic device 1003, electronic device 1005,..., electronic device 100n, etc. are not the receiving end . After that, the sending end 1001 can send the file selected by the user to the receiving end 1002 through "hishare" in the first application. That is, the sending end 1001 can use one or more of Bluetooth, NFC, and WLAN to transfer the file to the receiving end 1002. The file selected by the user is shared to the device associated with the contact, that is, the receiving end 1002. In this way, the sending end 1001 and the receiving end 1002 can quickly share files to other nearby devices in the application, without consuming the cellular data traffic of the receiving end and the sending end, and reducing the load of the server 1004. In addition, 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.

It can be understood that the structure shown in this embodiment does not constitute a specific limitation on the communication system 1000. In other embodiments of the present application, the communication system 1000 may include more or less devices than shown. For example, the communication system 1000 may also include other mobile phones, tablet computers, and other one or more servers having one or more of a Bluetooth (BT) module and a WLAN module.

In the following, based on the communication system 1000, the method for transferring files in the application implemented in the first scenario 1 described above is introduced.

First, introduce the overall flow of the method of transferring files in the application in scenario 1. The expansion can include:

Step 1: The sending end 1001 displays a first user interface. The first user interface may display the communication records of the associated user of the sending end 1001 and the selected contact in the first application.

The first user interface may be a user interface provided by the first application program. The first application program may be, for example, an instant messaging application, a mailbox application, and the like. The first user interface is used to display the communication records of the associated user of the sending end 1001 and the selected contact in the first application. The first user interface may refer to the user interface 32 in FIG. 3B.

Step 2: The sending end 1001 may detect in the first user interface the operation for viewing the file stored in the sending end 1001, and in response to the operation for viewing the file stored in the sending end 1001, the second user interface is displayed. The second user interface is used to display one or more files stored by the sending end 1001. For the second user interface, refer to the user interface 33 in FIG. 3D.

In the first scenario provided by the embodiment of the present application, the "hishare" file sharing option 310 included in the first user interface may be referred to as the first operation option. The operation for viewing the file stored in the sending end 1001, that is, the operation received by the sending end 1001 on the first operation option, may be referred to as the first operation.

Step 3: The sending end 1001 can detect the user operation of sharing the selected file to the contact in the second user interface. In response to the user operation of sharing the selected file to the contact, the sending end 1001 passes "Hishare" sends the selected file to the associated device of the contact (ie, the receiving end 1002). The process of sending the selected file to the receiving end 1002 by the sending end 1001 through "hishare" does not completely pass through the server 1004.

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

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

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

It can be seen that when a scene in which a user shares a file in an application is detected, the sending end 1001 can send the file to the receiving end 1002 through “hishare”. The process of transferring files to other nearby devices through "hishare" can be independent of the communication connection between the sender 1001 and the server. In this way, the sender 1001 can quickly transfer files to other surrounding devices in the application, and optimize the user experience. When the sender 1001 uses cellular data traffic, it can also save the cellular data traffic consumed by the sender 1001 and reduce the server’s cost. load. In addition, 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, the method of transferring files in the application in scenario one is introduced in detail.

FIG. 10B shows the flow of the method for transferring files in the application in the first scenario. As shown in FIG. 10B, the method may include:

S1001-S1002: Turn on "hishare" in advance.

S1001: The sending end 1001 can detect the operation for opening "hishare".

S1002: In response to the detected operation for turning on "hishare", the sending end 1001 turns on "hishare".

In some embodiments, referring to the aforementioned embodiments in FIGS. 2A-2B, it can be seen that the operation for opening "hishare" may be a click operation or touch operation detected by the sending end 1001 that acts on the switch control 202A of "hishare" in the window 202. Operation and so on.

Specifically, turning on "hishare" may refer to turning on one or more of the Bluetooth module, NFC module, and WLAN module of the sending end 1001. After "hishare" is turned on, the sender 1001 can discover the vicinity of the sender 1001 through one or more of NFC, Bluetooth, Wi-Fi direct connection (such as Wi-Fi p2p), Wi-Fi softAP, and Wi-Fi LAN. device of.

In some embodiments, S1001-S1002 may be optional steps, and the user may also select a contact who shares the file in the application and trigger the sender 1001 to start "hishare". In other words, it is not necessary to turn on "hishare" in advance.

S1003: The sending end 1002 starts the first application and displays the first user interface. The first user interface may display the communication records of the associated user of the sending end 1002 and the selected contact in the first application.

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

The first user interface is used to display the communication records of the associated user of the sending end 1002 and the selected contact in the first application. The exemplary implementation of the first user interface may refer to the user interface 32 shown in FIG. 3B or FIG. 3C, the user interface 32 shown in FIG. 4B or FIG. 4C, the user interface 32 shown in FIG. 4D or FIG. 4E or FIG. 4F, The user interface 52 shown in FIG. 5B or FIG. 5C.

In some embodiments, the first user interface may be displayed in the following manner:

First, the sender 1001 displays a user interface provided by the first application program displaying one or more contact options. For an exemplary implementation of the user interface, refer to the user interface 31 shown in FIG. 3A or the user interface shown in FIG. 5A. Interface 51.

Then, the sender 1001 detects a user operation for selecting a contact. The operation for selecting a contact may be: a click operation, touch operation, etc., that acts on a contact option detected by the sender 1001. The contact option The corresponding contact is the selected contact;

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

S1004: While the sending end 1001 displays the first user interface, it turns on "hishare". S1004 is an optional step, and the user can also trigger the sending end 1001 to enable "hishare" in advance, please refer to S1001-S1002. The user can also trigger the sender 1001 to turn on "hishare" later, refer to S1006.

S1005: The sending end 1001 may detect an operation for viewing the file stored in the sending end 1001 in the first user interface.

The operation for viewing files stored in the sending end 1001 may be, for example, user operations (such as click operations, touch operations, etc.) acting on the "hishare file transfer" option 310 in the user interface 32 shown in FIG. 3C, and acting on User operations (such as click operations, touch operations, etc.) on the "hishare file transfer" option 310 in the user interface 32 shown in FIG. 4C, and actions on the "hishare file transfer" option 310 in the user interface 32 shown in FIG. 4F User operations (for example, click operations, touch operations, etc.), user operations (for example, click operations, touch operations, etc.) acting on the "photo" option 501 in the user interface 52 shown in FIG. 5C.

S1006: In response to the detected operation for viewing the file stored in the sending end 1001, the sending end 1001 turns on "hishare". S1006 is an optional step, and the user can also trigger the sending end 1001 to enable "hishare" in advance. You can refer to S1001-S1002, or refer to S1004.

S1007: In response to the operation for viewing the file stored in the sending end 1001 detected in the first user interface, the sending end 1001 displays the second user interface. The second user interface displays: the identification of one or more files stored by the sending end 1001.

The second user interface is used to display one or more files stored by the sending end 1001. The identification of one or more files stored by the sending end 1001 is displayed in the second user interface. The files stored in the sending end 1001 may include, but are not limited to: pictures, audios, videos, documents, links, and so on. The identification of the file can be the thumbnail, name, etc. of the file.

The achievable form of the second user interface can refer to the user interface 33 shown in FIG. 3D and the user interface 53 shown in FIG. 5D. The achievable form of the identification of the file can refer to the thumbnail or name of the file in the file area 313 shown in FIG. 3D, and the 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 can discover nearby devices, such as electronic device 1001, electronic device 1002, electronic device 1003, electronic device 1005..., electronic device 100n. n is a positive integer. Regarding the specific implementation of the sending end 1001 discovering nearby devices, the follow-up content will be described in detail, and will not be repeated here.

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

S1009: The sending end 1001 determines the device associated with the contact among the discovered nearby devices, that is, the receiving end 1002 is determined. The sending end 1001 determines the specific implementation of the receiving end 1002 in nearby devices, and the subsequent content will be described in detail, and will not be repeated here.

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

Here, the selected files may include one or more of the following: selected pictures, selected documents, selected web pages, selected audios, selected links, and so on.

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

The manner in which the sender 1001 determines the selected file and the user operation of sharing the selected file to the contact can refer to the relevant description in the aforementioned UI embodiment, which will not be repeated here.

S1011-S1016: 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 of the contact (ie, the receiving end 1002) through "hishare". The process of sending the selected file to the receiving end 1002 by the sending end 1001 through "hishare" does not completely pass through the server 1004.

S1011: The sending end 1001 can establish a communication connection with the receiving end 1002.

The sending end 1001 can establish a Bluetooth communication connection, a Wi-Fi direct communication connection (such as a Wi-Fip2p connection), a SoftAP connection, and the like with the receiving end 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 sender 1001 and the receiver 1002 establish a connection can be negotiated by the sender and receiver after the device associated with the contact is determined in S1008-S1009. For example, when the sending end and the receiving end establish a Wi-Fi direct communication connection in S1011, the sending end 1001 can discover nearby devices through Bluetooth in S1008, and after determining the receiving end 1002 in S1009, establish Bluetooth communication with the receiving end 1002 Connect, and send a service set identifier (SSID) and password required for establishing a Wi-Fi direct communication connection to the receiving end 1002 through the Bluetooth communication connection. The receiving end 1002 connects to the sending end 1001 according to the SSID and password, so that the receiving end 1001 and the sending end 1002 can successfully establish a Wi-Fi direct communication connection.

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

That is to say, when the sender 1001 transmits the selected file through one or more of the wireless communication technologies of Bluetooth, Wi-Fi direct connection (such as Wi-Fi p2p), and Wi-Fi softAP, the sender 1001 needs to establish a communication connection with the receiving end 1002 after determining the receiving end 1002. In the case where the sending end 1001 transmits the selected file through Wi-Fi LAN wireless communication technology, because the sending end 1001 and the receiving end 1002 are already in the same LAN, the file can be transferred directly.

S1012: The sending end 1001 may send a file sharing request to the receiving end 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 a 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 to the receiving end 1002 through a LAN or NFC. Send a file sharing request.

In some embodiments, the sending end 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 receiving end 1002. In one embodiment, the file sharing request may carry the user identification of the selected contact, and the server 1004 may determine the user identification of the selected contact in the data stored in its own association with the user identification of the selected contact. The user ID of is associated with the stored device ID, that is, the device ID of the receiving end 1002 is determined, and the file sharing request is sent to the receiving end 1002. In another embodiment, the file sharing request may carry the device identification 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 identification of the receiving end 1002.

Sending the file sharing request through the server allows the server 1004 to learn and record the current file transfer 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 instruction information. The instruction information can be used to indicate the size, type, etc. of the shared file.

S1013: The sending end 1001 displays a prompt message.

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

For an exemplary implementation of the prompt information, refer to the prompt information 315 in FIG. 3F and the prompt information 506 in FIG. 5F.

S1014: After receiving the file sharing request sent by the sending end 1001, the receiving end 1002 may display a notification window. The notification window is used to ask the associated user of the receiving end 1002 whether to accept the file sharing request from the sending end 1001, that is, to ask the user whether to receive the selected file. For an exemplary implementation of the notification window, refer to the notification window 901 in FIG. 9A.

S1015: After the receiving end 1002 detects a user operation for accepting the file sharing request of the sending end 1001 in the notification window, it returns a sharing request response to the sending end 1001.

The user operation for receiving the file sharing request from the sending end 1001 may be an operation acting on the control 901D in the window 901 of FIG. 9A.

In some embodiments, the receiving end 1002 may send a sharing request response 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 to the sending end 1001 through a LAN or NFC. Send response to sharing request. In some embodiments, the receiving end 1002 may send the sharing request response to the server 1004 through a communication connection with the server 1004, and the server 1004 sends the sharing request response to the sending end 1001.

In some embodiments, S1015 may not be necessary. In other words, when the sending end 1001 sends a file sharing request to the receiving end 1002, the receiving end 1002 can directly return the sharing request response, and the file from the sending end 1001 can be received without user intervention.

S1016: After receiving the share request response returned by the receiving end 1002, the sending end 1001 sends the selected file to the receiving end 1002 through "hishare". The sending end 1001 sends the selected file to the receiving end 1002 through "hishare" not completely 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 sending end 1001 transmits files in the application to other nearby devices, namely the receiving end 1002, without relying on the communication connection between the sending end 1001 and the server 1004, and the file can be quickly transferred to the receiving end 1002 in the application. By optimizing the user experience, the cellular data traffic consumed by the sender 1001 can also be saved, and the load on the server can be reduced. Moreover, since the sending end 1001 transmits files in the application to other nearby devices, namely the receiving end 1002, the process does not rely on the communication connection between the sending end 1001 and the server 1004, and the size of the file shared by the sending end 1001 to the receiving end 1002 is not affected. Restriction, that is, the sending end 1001 can share larger files to the receiving end 1002.

In some embodiments, the sending end 1001 can also combine an established communication connection (such as a Bluetooth communication connection and/or Wi-Fi direct communication connection)/LAN at the same time, and the communication connection between the sending end 1001 and the server will be The file selected by the user is sent to the receiving end 1002. In this way, files can be transferred in a variety of ways, which improves the efficiency of file transfer. In a specific implementation, the sending end 1001 may simultaneously combine an established communication connection (such as a Bluetooth communication connection and/or a 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 can divide the file selected by the user into two parts, and send a part of the file through the established communication connection (such as Bluetooth communication connection and/or Wi-Fi direct communication connection)/LAN, and pass it between the server and the server. The communication link sends another part of the file. The embodiment of the present application does not limit the manner in which the sending end 1001 divides the file into two parts.

In the embodiment of the present application, the sending end 1001 may send the selected file to the receiving end 1002 through an AIDL calling function (for example, 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: Feedback file transfer status.

With reference to S1017, the receiving end 1002 may display a prompt message during the file transfer process, or may display the prompt message after the file transfer ends. The prompt information can be used to prompt the file transmission status of the associated user (ie, the selected contact) of the receiving end 1002.

With reference to S1018, the receiving end 1002 may feed back the transmission status of the file to the sending end 1001 during the file transmission process, and may also feedback the transmission status of the file to the sending end 1001 after the file transmission is completed.

With reference 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 transmission status of the associated user file of the sending end 1001.

In the embodiment of the present application, the sending end 1001 may call a function (for example, onTransStateChange) through AIDL to obtain the transmission state of the file. The receiving end 1002 may call a function (for example, OnProgress) through AIDL to obtain the transmission status of the file.

In some embodiments, the file transfer status may include, but is not limited to:

The second transmission state may mean that the selected file is being transmitted to the receiving end 1002.

The third transmission state may mean that the selected file is successfully transmitted to the receiving end 1002.

The fourth transmission state may mean that the selected file has not been successfully transmitted to the receiving end 1002.

In some embodiments, the prompt information displayed by the receiving end 1002 may refer to: one or more of the prompt information 905 in the file transfer record 903 shown in FIGS. 9B to 9D exemplarily. Regarding the prompt information 905, reference may be made to the relevant content and extensions in the embodiments of FIGS. 9B to 9C, which will not be repeated here.

In some embodiments, the prompt information displayed by the sending end 1001 may refer to: one or more of the prompt information 315 in the file transfer record 314 shown in FIG. 3G-FIG. 3I, or the prompt information 315 in FIG. 5G-FIG. One or more of the prompt information 506 in the file transfer record 505 described as an example in 5I. Regarding the prompt information 315, reference may be made to the relevant content and extensions in the embodiments of FIGS. 3G-3I, which will not be repeated here. Regarding the prompt information 506, please refer to the related content and extensions in the embodiments of FIGS. 5G-5I, which will not be repeated here.

In the first scenario provided by the embodiment of the present application, the prompt information displayed by the sending end 1001 may be displayed in the third user interface. For an exemplary implementation of the third user interface, reference may be made to the user interface shown in any one of FIG. 3F-FIG. 3I and FIG. 5F-FIG. 5I.

It is not limited to the way of displaying prompt information on the screen to prompt the user of the file transmission status. The sending end 1001 and the receiving end 1002 can also stop other methods to prompt the file transmission status, for example, it can also be prompted by playing a voice, etc. The application embodiment does not limit this.

S1017-S1019 may not be necessary. In other words, both the receiving end and the sending end do not need to feed back the transmission status of the file.

The following is a detailed description of several implementation methods for the sender 1001 to discover nearby devices in S1008:

Method 1. Use Bluetooth wireless communication technology to discover nearby devices

Specifically, the devices near the sending end 1001 (such as the electronic device 1002, the electronic device 1003, etc.) can perform Bluetooth broadcasting, that is, send Bluetooth broadcast packets; the sending end 1001 can perform Bluetooth scanning to scan broadcast packets broadcast by nearby devices.

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

In some embodiments, in addition to the device identification, the broadcast packet may also carry the user identification of the associated user of the device in the application installed on 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 identification of the user "Kate" in the first application. When the first application and the second application (such as a mailbox application) are installed on the electronic device 1003, the broadcast packet sent by the electronic device 1003 carries the user identification of the user "Mac" in the first application, such as the account " Mac", and the user identification of the user "Mac" in the second application, such as the account "Mac". The user identification in the broadcast packet can be used by the sender 1001 to determine the device associated with the selected contact among nearby devices, that is, to determine the receiver. The subsequent embodiments will describe this process in detail.

Method 2. Use Wi-Fi direct wireless communication technology to discover nearby devices

In some embodiments, the sending end 1001 may broadcast a probe request to the outside. After listening to the detection request, nearby devices (such as printers) can respond with a probe response to notify their existence. Wherein, the probe response may carry the device identification of the device, and may also carry the user identification of the associated user of the device in the application installed on the device. Here, the device identification can refer to the device identification in the Bluetooth broadcast package in mode 1, and the user identification can refer to the user identification in the Bluetooth broadcast package in mode 1.

In other embodiments, nearby devices (such as mobile phones, tablet computers, etc.) can periodically send out beacon frames. The sender 1001 can discover nearby devices by monitoring the Beacon frames sent by nearby devices. Among them, the Beacon frame may carry the device identification of the device, and may also carry the user identification of the associated user of the device in the application installed on the device. Here, the device identification can refer to the device identification in the Bluetooth broadcast package in mode 1, and the user identification can refer to the user identification in the Bluetooth broadcast package in mode 1.

In other words, the sending end 1001 can adopt Wi-Fi direct wireless communication technology to actively discover nearby devices or passively discover nearby devices.

Method 3. Discover devices in the same Wi-Fi LAN

In some embodiments, the sender 1001 can determine the IP address range of the LAN according to its own IP address and subnet mask in the LAN, and then can discover the devices in the LAN by means of unicast polling. Not limited to this, the sender 1001 can also discover the devices in the LAN through broadcast messages or multicast messages in the LAN. After receiving a broadcast message, a multicast message, or a polling message, the device in the LAN can reply its own information to the sender 1001. The information may carry the device identification of the device, and may also carry the user identification of the associated user of the device in the application installed on the device. Here, the device identification can refer to the device identification in the Bluetooth broadcast package in mode 1, and the user identification can refer to the user identification in the Bluetooth broadcast package in mode 1.

It is not limited to the above several ways that the sender 1001 discovers nearby devices. In actual applications, the sender 1001 can also use other methods to discover nearby devices based on wireless communication technologies such as Bluetooth, Wi-Fi Direct, Wi-Fi LAN, or NFC. Equipment, this embodiment of the application does not limit this.

In the embodiment of the present application, the sending end 1001 can use any of the above methods to find nearby devices, and then call a function (for example, OnDeviceFound) through the Android interface definition language (AIDL), so that it can be used in nearby devices. Determine the device associated with the contact.

In S1009, the sending end 1001 determines the device associated with the contact among the discovered nearby devices in detail below, that is, several implementation manners for determining the receiving end 1002:

Method 1. The sender 1001 determines the receiver according to the user ID sent by nearby devices

In some embodiments, a nearby device may send the user identifier of the associated user of the device in an application installed on the device to the sending end 1001. For the sending mode, refer to the related description of S1008 in the previous embodiment. The sending end 1001 may search for a user ID that is the same as the user ID of the selected contact among the received user IDs. If the user ID that is the same as the user ID of the selected contact is found, the device that sends the user ID is determined as the receiving end.

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

Method 2. The sending end 1001 determines the receiving end through the server 1004 corresponding to the first application

In some embodiments, the sending end 1001 may send a request to the server 1004, the request carrying the user identification of the selected contact, and the request is used to inquire about the identification of the device that the contact currently uses to log in to the first application. Since the server 1004 stores the identification of the user who registered the first application in association with the device identification of the user's associated device, the server 1004 can find the user identification that is stored in association with the user identification according to the user identification carried in the request. Equipment Identity. After that, the server 1004 may send the found device identification to the sending end 1001. After receiving the device identification sent by the server, the sending end 1001 determines the device represented by the device identification as the receiving end.

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

In a specific example, the user identification may be a Huawei ID. In any of the foregoing determination methods, the Huawei ID may not be directly transmitted between devices, but may be transmitted between devices through the hash values of the Huawei ID. The hash value of the Huawei ID is calculated by the device using a hash function to calculate the Huawei ID.

In the following, based on the communication system 1000, the method for transferring files in the application implemented in the second scenario 2 described above is introduced.

First, introduce the overall flow of the method of transferring files in the application in scenario 2. The expansion can include:

Step 1: The sending end 1001 displays a fourth user interface, and the fourth user interface is used to display one or more files stored by the sending end 1001.

The fourth user interface may be a user interface provided by the second application program. The second application program may be, for example, a gallery, a file manager, a document manager, and so on. The fourth user interface may refer to the user interface 61 shown in FIG. 6A or FIG. 6B.

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

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

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

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

In the second scenario provided by the embodiment of the present application, the "hishare file transfer" option 604A in the fourth user interface may be referred to as the third operation option, and the sixth operation may be received by the sending end 1001 on the third operation option operating.

Step 3: The sender 1001 can detect a user operation acting on an application option, and in response to the user operation acting on an application option, a fifth user interface is displayed, and the fifth user interface includes one or more contact options .

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

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

Step 4: The sending end 1001 can detect the user operation acting on the contact option in the fifth user interface, and in response to the user operation acting on the contact option, the sending end 1001 sends the selected file through "hishare" Give the associated device of the contact corresponding to the contact option (that is, the receiving end 1002). The process of sending the selected file to the receiving end 1002 by the sending end 1001 through "hishare" does not completely pass through the server 1004.

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

In some embodiments, the sending end 1001 may also display the sixth user interface in response to the user operation acting on the contact option. The sixth user interface includes: the communication records and prompt information of the first user and the second user in the first application, and the prompt information is used to indicate the transmission status of the third file.

It can be seen that when a scene in which a user shares a file in an application is detected, the sending end 1001 can send the file to the receiving end 1002 through “hishare”. The process of transferring files to other nearby devices through "hishare" can be independent of the communication connection between the sender 1001 and the server. In this way, the sender 1001 can quickly transfer files to other surrounding devices in the application, optimize the user experience, and can also save the cellular data traffic consumed by the sender 1001 and reduce the load of the server. Moreover, since the sending end 1001 transmits files in the application to other nearby devices, namely the receiving end 1002, the process does not rely on the communication connection between the sending end 1001 and the server 1004, and the size of the file shared by the sending end 1001 to the receiving end 1002 is not affected. Restriction, that is, the sending end 1001 can share larger files to the receiving end 1002.

In the following, the method of transferring files in the application in scenario two is introduced in detail.

FIG. 10C shows the flow of the method for transferring files in the application in the second scenario. As shown in FIG. 10C, the method may include:

S1101-S1102: Turn on "hishare" in advance. For details, refer to S1001-S1002 in the method embodiment of FIG. 10B.

S1103: The electronic device displays a fourth user interface, and the fourth user interface displays: the identifier of one or more files stored by the sending end 1001.

The fourth user interface may be provided by the second application. The fourth user interface is used to display one or more files stored by the sending end 1001. The identification of one or more files stored by the sending end 1001 is displayed in the fourth user interface. The files stored in the sending terminal 1001 may include, but are not limited to: pictures, audios, videos, documents, links, and so on. The identification of the file can be the thumbnail, name, etc. of the file.

The achievable form of the fourth user interface can refer to the user interface 61 shown in FIG. 6A or 6B and the user interface 73 shown in FIG. 7D. The achievable form of the identification of the file can refer to the thumbnail or the name of the file in the file area 603 shown in FIG. 6A.

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

The selected files can include one or more of the following: selected pictures, selected documents, selected web pages, selected audios, selected links, and so on.

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

For the manner in which the sending end 1001 determines the selected file, and the operation for sharing the selected file, reference may be made to the relevant description in the aforementioned UI embodiment, which will not be repeated here.

S1105: In response to the detected operation for sharing the selected file, the sender 1001 turns on "hishare". S1105 is an optional step, and the user can also trigger the sending end 1001 to enable "hishare" in advance, please refer to S1101-S1102.

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

The application corresponding to one or more application options displayed in the fourth user interface can be all applications installed on the sending end 1001 that can be used to share files, or can be installed on the sending end 1001 that can be used to share files In the program, the device associated with the contact can transfer files with the sender 1001 through "hishare" application.

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

S1107: The sending end 1001 can detect the operation that acts on the application options,

S1108: In response to the operation on the application options, the sending end 1001 displays a fifth user interface, and the fifth user interface displays one or more contact options.

The fifth user interface may be an application program corresponding to the application option, for example, a user interface provided by the first application program. For an exemplary implementation form of the fifth user interface, 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 the contacts of the associated user of the sender 1001 in the first application, and the associated device can correspond to the contacts of the sender 101 who transfer files through "hishare". The contact options may also include the contact options corresponding to all the contacts of the associated user of the sending end 1001 in the first application, or the associated user of the sending end 1001 communicated in the first application recently Options for one or more contacts.

S1109: The sending end 1001 can detect an operation acting on the contact option in the fifth user interface.

For example, the sending end 1001 can detect a click operation, a touch operation, etc., 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 can discover nearby devices, such as electronic device 1001, electronic device 1002, electronic device 1003, electronic device 1005..., electronic device 100n. n is a positive integer. For details, refer to S1008 in the method embodiment of FIG. 10B.

The embodiment of this application does not limit the sequence of S1110 and S1107. The sending end 1001 can execute S1107 and S1110 at the same time, or execute S1107 first, or execute S1110 first.

S1111: The sending end 1001 determines the device associated with the contact corresponding to the contact option operated by the user in the discovered nearby devices, that is, the receiving end 1002 is determined. For details, refer 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 sender 1001 sends the selected file to the associated device of the contact corresponding to the contact option through "hishare" ( That is, the receiving end 1002). The process of sending the selected file to the receiving end 1002 by the sending end 1001 through "hishare" does not completely pass through the server 1004.

S1112: The sending end 1001 can establish a communication connection with the receiving end 1002. For details, refer to S1011 in the method embodiment of FIG. 10B.

S1113: The sending end 1001 may send a file sharing request to the receiving end 1002. The file sharing request is used to request the receiving end 1002 to receive the file shared by the sending end 1001. For details, refer to S1012 in the method embodiment of FIG. 10B.

S1114: The sending end 1001 displays a prompt message.

For an exemplary implementation of the prompt information, refer to the prompt information 611 in FIG. 6F.

S1115: After receiving the file sharing request sent by the sending end 1001, the receiving end 1002 may display a notification window. For details, refer to S1014 in the method embodiment in FIG. 10B.

S1116: After the receiving end 1002 detects a user operation for accepting the file sharing request of the sending end 1001 in the notification window, it returns a sharing request response to the sending end 1001. For details, refer to S1015 in the method embodiment of FIG. 10B.

S1117: After receiving the share request response returned by the receiving end 1002, the sending end 1001 sends the selected file to the receiving end 1002 through "hishare". The sending end 1001 sends the selected file to the receiving end 1002 through "hishare" not completely through the server. For details, refer to S1016 in the method embodiment of FIG. 10B.

S1118-S1120: feedback the file transfer status. For details, refer to S1017-S1019 in the method embodiment of FIG. 10B.

In the second scenario provided by the embodiment of the present application, the prompt information displayed by the sending end 1001 may be displayed in the sixth user interface. For an exemplary implementation of the sixth user interface, reference may be made to the user interface shown in any one of FIGS. 6E to 6H.

In the method for transferring files in an application provided in the embodiment of the present application, the sending end 1001 and the receiving end 1002 are both pre-bound to the third-party interface ShareKit service. The ShareKit service is used to support the method of transferring files without traffic in the running application of the device. For example, the ShareKit service supports the sender 1001 to call the function (such as PreSend Send) to send the selected file to the receiver 1002 through AIDL. A function (for example, onTransStateChange) obtains the transmission status of the file, and determines the receiving end 1002 by calling a function (for example, OnDeviceFound) through AIDL; it can also support the receiving end 1002 to obtain the transmission status of the file through AIDL calling a function (for example, OnProgress).

In other words, the ShareKit service may be a system function preset in the sending end 1001 and the receiving end 1002. The ShareKit service can be opened in the form of Android archive (aar) and Android installation package (Android packet, APK). The first application on the sending end or the receiving end can call the aar interface to obtain the ShareKit service.

Referring to FIG. 11, FIG. 11 shows the architecture of providing ShareKit services on the sending end 1001 and the receiving end 1002.

As shown in Figure 11, the architecture can include kit interface carriers, interaction mechanisms, and kit implementation carriers. among them:

The kit interface carrier may include an aar and a Java archive (Java archive, JAR) of an application (for example, the first application) installed on the device.

The interaction mechanism may include an AIDL mechanism, a shared library (shared library) mechanism, a software development kit (software development kit, SDK) mechanism, and a shared feature (share feature) mechanism.

The kit implementation carrier can be stored in ROM. The kit implementation carrier may include: preset APK, preset library, various system services and common services, shared feature, etc.

In general, the method, electronic device, and system for transferring files in applications provided by the embodiments of the present application can enable users to quickly share files with other users nearby through applications installed on the electronic device. The process of sharing files does not depend on the server. The implementation of the technical solutions provided by the embodiments of this application has the following beneficial effects: the electronic device can quickly and quickly transfer files to other surrounding devices in the application, optimizing the user experience; regardless of whether there is a connection between the electronic device and the server The communication connection, whether the communication connection is good, the electronic device can share files to other devices, which can save the cellular data traffic consumed by the electronic device and reduce the load of the server; the size of the file shared by the electronic device is not limited, which means that the electronic device The device can share larger files to other surrounding devices.

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

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, it can be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the procedures or functions described in this application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website site, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media. The usable medium may be a magnetic medium, (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk).

A person of ordinary skill in the art can understand that all or part of the process in the above-mentioned embodiment method can be realized. The process can be completed by a computer program instructing relevant hardware. The program can be stored in a computer readable storage medium. , May include the processes of the above-mentioned method embodiments. The aforementioned storage media include: ROM or random storage RAM, magnetic disks or optical disks and other media that can store program codes.

In short, the above descriptions are only examples of the technical solutions of the present invention, and are not used to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of the present invention shall be included in the protection scope of the present invention.

Claims

A method for transferring files in an application, characterized in that the method includes:

The first device displays a first user interface, and the first user interface includes: a communication record of the first user and the second user in the first application, and a first operation option;

In response to the first operation received on the first operation option, the first device displays a second user interface. The second user interface includes a first identifier and a second identifier, and the first identifier corresponds to For the first file stored in the first device, the second identifier corresponds to the second file stored in the first device;

The first device receives the second operation on the first identifier, and selects the first file;

In response to the 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 with the second device;

Wherein, 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.
The method according to claim 1, wherein after the first device displays the first user interface, the method further comprises:

The first device discovers one or more devices via Bluetooth;

The first device determines the second device among the one or more discovered devices.
The method according to claim 1, wherein the method further comprises:

In response to the first operation, the first device discovers one or more devices via Bluetooth;

The first device determines the second device among the one or more discovered devices.
The method according to claim 2 or 3, wherein:

The discovery of one or more devices by the first device via Bluetooth specifically includes: the first device receives a Bluetooth broadcast packet sent by one or more devices, the Bluetooth broadcast packet includes a user identification, and the user identification corresponds to The user of logs in the first application on the device;

The first device to determine the second device among the discovered one or more devices specifically includes: the first device determines, among the one or more devices, the device that sends the first identifier as the The second device; the first identifier is the user identifier of the second user.
The method according to any one of claims 2-4, wherein after the first device determines the second device among the one or more discovered devices, the first device passes and Before the Wi-Fi direct communication connection between the two devices sends the first file to the second device, the method further includes:

The first device executes the process of establishing the Wi-Fi direct communication connection with the second device.
The method according to claim 5, wherein before the first device executes 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 identification SSID and a password to the second device through the established Bluetooth communication connection; the SSID and the password are used by the second device to execute and communicate with the first device The process of establishing the Wi-Fi direct communication connection between the two.
The method according to any one of claims 1-6, wherein the first device sends the first file to the second device through a Wi-Fi direct communication connection with the second device. After the equipment, the method further includes:

The first device displays a third user interface, and the third user interface includes prompt information, and the prompt information is used to indicate the transmission status of the first file.
The method according to any one of claims 1-7, wherein:

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

The sending of the first file to the second device by the first device through the Wi-Fi direct communication connection with the second device specifically includes: when the first device receives the second device In the case of a response to the sharing request sent in response to the file sharing request, the first file is sent to the second device through a Wi-Fi direct communication connection with the second device.
The method according to claim 8, wherein the sending of a file sharing request by the first device to the second device specifically comprises:

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.
The method according to any one of claims 1-9, wherein the first device sends the first file to the second device through a Wi-Fi direct communication connection with the second device. Before the device, the method further includes:

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 enables the first communication service and the second communication service; the first communication service is used by the first device to discover and determine the second device via Bluetooth, The second communication service is used by the first device to send the first file to the second device through the Wi-Fi direct communication connection.
An electronic device, characterized in that the electronic device comprises: a display screen, a memory, one or more processors; the display screen, the memory and the one or more processors are coupled, and the memory is used for In storing computer program code, the computer program code includes computer instructions, and the one or more processors invoke the computer instructions to cause the electronic device to execute:

Displaying a first user interface on the display screen, the first user interface including: a communication record of the first user and the second user in the first application, and a first operation option;

In response to the first operation received on the first operation option, a second user interface is displayed on the display screen, the second user interface including a first identifier and a second identifier, the first identifier Corresponding to the first file stored in the electronic device, and the second identifier corresponds to the second file stored in the electronic device;

Receiving a second operation on the first identifier, and selecting the first file;

In response to the third operation of sharing the first file, sending the first file to the second device through a Wi-Fi direct communication connection with the second device;

Wherein, the first user logs in the first application on the electronic device, and the second user logs in the first application on the second device.
The electronic device according to claim 11, wherein the one or more processors are further configured to invoke the computer instruction to cause the electronic device to execute:

After displaying the first user interface on the display screen, discover one or more devices via Bluetooth;

The second device is determined among the one or more discovered devices.
The electronic device according to claim 11, wherein the one or more processors are further configured to invoke the computer instruction to cause the electronic device to execute:

In response to the first operation, discover one or more devices via Bluetooth;

The second device is determined among the one or more discovered devices.
The electronic device according to claim 12 or 13, wherein the one or more processors are specifically configured to invoke the computer instruction to cause the electronic device to execute:

Receiving a Bluetooth broadcast packet sent by one or more devices, the Bluetooth broadcast packet including a user identification, and a user corresponding to the user identification logs in the first application on the device;

Among the one or more devices, the device that sends the first identification is determined to be the second device; the first identification is the user identification of the second user.
The electronic device according to any one of claims 12-14, wherein the one or more processors are further configured to invoke the computer instructions to cause the electronic device to execute:

After the second device is determined among the one or more devices discovered, the first file is sent to the first file through the Wi-Fi direct communication connection with the second device Before the second device, perform the process of establishing the Wi-Fi direct communication connection with the second device.
The electronic device according to claim 15, wherein the one or more processors are further configured to invoke the computer instructions to cause the electronic device to execute:

Before performing the process of establishing the Wi-Fi direct communication connection with the second device, perform the process of establishing a Bluetooth communication connection with the second device;

The service set identification SSID and password are sent to the second device through the established Bluetooth communication connection; the SSID and the password are used by the second device to perform the establishment of the Wi -Fi direct communication connection process.
The electronic device according to any one of claims 11-16, wherein the one or more processors are further configured to invoke the computer instructions to cause the electronic device to execute:

After the first file is sent to the second device through the Wi-Fi direct communication connection with the second device, a third user interface is displayed on the display screen, and the third user interface is displayed on the display screen. The user interface includes prompt information, and the prompt information is used to indicate the transmission status of the first file.
The electronic device according to any one of claims 11-17, wherein:

The one or more processors are further configured to call the computer instructions to cause the electronic device to execute: send the first file through the Wi-Fi direct communication connection with the second device Send a file sharing request to the second device before sending it to the second device;

The one or more processors are specifically configured to invoke the computer instructions to cause the electronic device to execute: in the case of receiving a sharing request response sent by the second device in response to the file sharing request, pass and The Wi-Fi direct communication connection between the second devices sends the first file to the second device.
The electronic device according to claim 18, wherein the one or more processors are specifically configured to invoke the computer instruction to cause the electronic device to execute:

Send 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.
The electronic device according to any one of claims 11-19, wherein the one or more processors are further configured to call the computer instructions to cause the electronic device to execute:

Before sending the first file to the second device through the Wi-Fi direct communication connection with the second device, the first file used to start the first communication service and the second communication service is detected Four operations;

In response to the fourth operation, start the first communication service and the second communication service; the first communication service is used by the electronic device to discover and determine the second device via Bluetooth, the second communication service Used for the electronic device to send the first file to the second device through the Wi-Fi direct communication connection.
A computer program product containing instructions, characterized in that, when the computer program product runs on an electronic device, the electronic device is caused to execute the method according to any one of claims 1-10.
A computer-readable storage medium, comprising instructions, characterized in that, when the instructions are executed on an electronic device, the electronic device is caused to execute the method according to any one of claims 1-10.