WO2024046347A1

WO2024046347A1 - Data sharing method and system, and related apparatus

Info

Publication number: WO2024046347A1
Application number: PCT/CN2023/115722
Authority: WO
Inventors: 贾银元; 王志峰; 许浩维
Original assignee: 华为技术有限公司
Priority date: 2022-09-01
Filing date: 2023-08-30
Publication date: 2024-03-07
Also published as: CN117676480A

Abstract

The present application provides a data sharing method and system, and a related apparatus. An electronic device displays an option of a current interactive contact (for example, a current call contact) and/or an option of a most recent interactive contact (for example, a most recent call contact or a most recent private contact) in a system sharing interface for data or in an application sharing interface during or after interaction with the contact, etc. The electronic device shares specified data selected by a sharing user with a specified contact selected by the user after the electronic device receives the input made by the user on the option of the current interactive contact and/or the option of the most recent interactive contact. In this way, it can be convenient for the user to quickly share data with a contact who is currently interacting with the user or has interacted with the user most recently, thereby enhancing data sharing experience.

Description

A data sharing method, system and related devices

This application claims the priority of the Chinese patent application submitted to the China Patent Office on September 1, 2022, with the application number 202211067060.6 and the application title "A data sharing method, system and related devices", the entire content of which is incorporated by reference. in this application.

Technical field

The present application relates to the field of communication technology, and in particular, to a data sharing method, system and related devices.

Background technique

With the development of wireless communication technology, terminals such as smartphones and tablets have begun to support users in sharing pictures, documents and other data to other devices, improving users' office efficiency and experience. For example, users can share pictures, files and other data on smartphones and other terminals to other devices without using data cables. Currently, when users want to share data on portable terminal devices such as smartphones to other devices, the operation process is complicated.

Contents of the invention

This application provides a data sharing method, system and related devices, which enables the electronic device to display the currently interacting contacts (for example, current call contacts) in the data sharing interface during or after the interaction with the contacts. options and/or options for recently interacted contacts (for example, recent call contacts, recent private message contacts, etc.), so that users can quickly share data with contacts they are currently interacting with or have recently interacted with, improving Improve the user experience of sharing data.

In a first aspect, this application provides a data sharing method, including: a first electronic device displays a call interface, the call interface includes contact information of the second electronic device, and the call interface is used to represent the relationship between the first electronic device and The second electronic device is making an operator call; the first electronic device receives a first input to share the first designated data during the operator call with the second electronic device; in response to the first input , the first electronic device displays a first sharing interface, and displays a first option corresponding to the second electronic device in the first sharing interface; the first electronic device receives a second input to the first option; responds Upon the second input, the first electronic device sends the first specified data to the second electronic device.

Through a data sharing method provided by this application, the first electronic device can display the options of the second electronic device in the specified data sharing interface during the operator call with the second electronic device. After the first electronic device receives the user's input on the option of the second electronic device, the first electronic device may share the specified data with the second electronic device. In this way, it is convenient for users to quickly share data with contacts who are on the phone, improving the user experience of sharing data.

In a possible implementation, a call mark is displayed around the first option, and the call mark is used to indicate that the first option is an option corresponding to the second electronic device that is talking to the first electronic device.

In this way, it is convenient for the user to quickly find the option of the second electronic device on the sharing interface.

In a possible implementation, the contact information corresponding to the second electronic device is also displayed around the first option, and the contact information corresponding to the second electronic device includes one or more of the following: the second The phone number of the electronic device, the contact name that the first electronic device has noted for the phone number of the second electronic device, the contact avatar that the first electronic device has noted for the phone number of the second electronic device, and the call application Mark; wherein, the calling application mark is used to represent the calling application to which the calling interface belongs.

In this way, it is convenient for the user to find the option of the second electronic device on the sharing interface.

In a possible implementation, in response to the second input, the first electronic device sends the first specified data to the second electronic device, specifically including: in response to the second input, the first electronic device The device sends a data transmission request to the second electronic device, where the data transmission request is used to request the transmission of the first specified data to the second electronic device; the first electronic device receives the confirmation information sent by the second electronic device, and the confirmation The information is used to indicate that the second electronic device allows the first electronic device to send the first designated data to the second electronic device; in response to the confirmation information, the first electronic device sends the first designated data to the second electronic device. Electronic equipment.

In this way, before sharing data to the second electronic device, a data transmission request can be sent to the second electronic device, and only after receiving confirmation from the second electronic device, the data can be shared to the second electronic device to prevent the second electronic device from receiving the requested data. Force data to be received.

In a possible implementation, the method further includes: in response to the second input, the first electronic device displays a first prompt, the first prompt being used to prompt the user that the first electronic device is requesting a request to the third electronic device. The two electronic devices send the first specified data.

In this way, users can perceive the data sharing process.

In a possible implementation, the method further includes: during the process of sending the first designated data to the second electronic device, the first electronic device displays a second prompt and a sending progress bar. The second prompt The sending progress bar is used to remind the user that the first electronic device is sending the first specified data to the second electronic device. The sending progress bar is used to remind the user of the progress of the first electronic device sending the first specified data to the second electronic device. .

In this way, users can perceive the data sharing process.

In a possible implementation, the method further includes: during the process of sending the first specified data to the second electronic device, the first electronic device displays a sending cancellation control, the canceling control being used to trigger the first The electronic device suspends sending the first designated data to the second electronic device.

In this way, the user can stop sharing data to the second electronic device midway.

In a possible implementation, the method further includes: after the first electronic device sends the first specified data to the second electronic device, displaying a third prompt and a withdrawal control, the third prompt being used to prompt The first electronic device of the user has finished sending the first specified data to the second electronic device. The withdrawal control is used to trigger the first electronic device to send a withdrawal instruction to the second electronic device. The withdrawal instruction is used to request the The second electronic device deletes the first designated data that has been received by the first electronic device.

In this way, after sharing data to the second electronic device, the user can actively withdraw the data shared to the second electronic device from the second electronic device, which can prevent privacy leakage caused by the user mistakenly sending data to the second electronic device. .

In a possible implementation, the first sharing interface is a system sharing interface, and the first sharing interface also includes options for one or more nearby devices discovered by the first electronic device through near field communication technology, one or more A service option. The option of the nearby device is used to trigger the first electronic device to share the first specified data to the nearby device. The service option can be used to trigger the first electronic device to use the application or protocol corresponding to the service option. Share the first specified data.

In this way, the option of the current call contact (i.e., the second electronic device) can be displayed in the sharing interface of the operating system of the first electronic device, so as to facilitate the user to realize the communication with the current call contact when activating the sharing function of the operating system. Data sharing for call contacts.

In a possible implementation, the first sharing interface is an in-application sharing interface of the first application, and the first sharing interface also includes one or more functional options in the first application;

The first electronic device receives the first input of sharing the first specified data during the operator call with the second electronic device. Specifically, the first electronic device receives the first input of sharing the first specified data with the second electronic device. During the call, the operator displays the first interface of the first application. The first interface includes the first specified data and a first control. The first control is used to share the first specified data, wherein the sharing of the first specified data The first designated data includes a retrieval link for sharing the first designated data; the first electronic device receives the first input to the first control.

In this way, the options of the current call contact (i.e., the second electronic device) can be displayed in the sharing interface within the application of the first electronic device, making it convenient for the user to communicate with the current call contact when calling up the sharing function of the application. data sharing.

In a possible implementation, the first specified data includes one or more of the following: pictures, audios, videos, document files, location information, links, contact information, calendars, application packages, and memos.

In a possible implementation, the method further includes: after the first electronic device sends the first specified data to the second electronic device, the first electronic device and the second electronic device end the operator call; the first electronic device receives a third input to share the second specified data; in response to the third input, the first electronic device displays a second sharing interface, the second sharing interface includes one or more recent interactive contacts People's options; wherein, the most recently interacted contact is a contact who has interacted with the first electronic device within a recent period of time when the first electronic device received the third input, and the one or more recently interacted contacts The options include a third electronic device corresponding to the second option; the first electronic device receives a second input of the second option; in response to the second input, the first electronic device sends the second specified data to the third electronic device.

In this way, the option of the most recently interacted contacts that have interacted with the second electronic device in the recent period can be displayed in the data sharing interface. When the first electronic device receives the user's input of the option of the recently interacted contact, the first electronic device The electronic device can share specified data with recently interacted contacts. In this way, users can quickly share data with contacts they have interacted with recently, improving the user experience of sharing data.

In a possible implementation, the contact information of the recently interacted contact is displayed around the option of the recently interacted contact, and the contact information of the recently interacted contact includes one or more of the following: the recently interacted contact The contact information of the interactive contact includes one or more of the following: the phone number of the recently interacted contact, the contact name of the recently interacted contact, the contact avatar of the recently interacted contact, and the contact application tag; among which, The contact application mark is used to represent the application used by the first electronic device to interact with the recently interacted contact.

In this way, users can quickly find options for recently interacting contacts on the sharing interface.

In a possible implementation, the interaction includes any of the following: making phone calls on an operator, receiving text messages, sending text messages, over-the-top calls, receiving or sending private messages within social applications.

In a possible implementation, before the first electronic device sends the first specified data to the second electronic device, the method further includes: the first electronic device establishes the first data with the second electronic device. Transmission link; in response to the second input, the first electronic device sends the first specified data to the second electronic device, specifically including: in response to the second input, the first electronic device The first specified data is sent to the second electronic device on the data transmission link.

In a possible implementation, the method further includes: during the operator call with the second electronic device and before receiving the first input, the first electronic device establishes a connection with the second electronic device. Complete the first data transmission link; in response to the first input, the first electronic device displays a first sharing interface, and displays a first option corresponding to the second electronic device in the first sharing interface, specifically including: : In response to the first input, the first electronic device displays the first sharing interface, and the first sharing interface includes the first option corresponding to the second electronic device.

In this way, the establishment of the data transmission link between the first electronic device and the second electronic device can be completed before the sharing interface is displayed, which facilitates the user to quickly share data on the first electronic device to the second electronic device.

In a possible implementation, in response to the first input, the first electronic device displays a first sharing interface, and displays a first option corresponding to the second electronic device in the first sharing interface, specifically including: : In response to the first input, the first electronic device displays the first sharing interface; after the first electronic device and the second electronic device establish the first data transmission link, the first electronic device The first option corresponding to the second electronic device is displayed on the first sharing interface.

In a possible implementation, in response to the second input, the first electronic device sends the first specified data to the second electronic device on the first data transmission link, specifically including: in response to The second input, the first electronic device and the second electronic device establish the first data transmission link; after the first data transmission link is established, the first electronic device The first designated data is sent to the second electronic device.

In this way, the data transmission link can be established with the second electronic device only when the user determines to share the data with the second electronic device, thereby saving the power consumption of the first electronic device in maintaining the data transmission link.

In a possible implementation, the first data transmission link includes one or more of the following links: the main link for operator calls between the first electronic device and the second electronic device, the first electronic device One or more auxiliary links to the second electronic device.

In this way, the first electronic device can share data with the second electronic device through a combination of multiple transmission links, thereby increasing the data sharing speed.

In a possible implementation, the one or more auxiliary links include one or more of the following: Internet Protocol IP direct link, point-to-point P2P link, and server relay link.

In a possible implementation, when the first data transmission link includes the one or more auxiliary links, the first electronic device and the second electronic device establish a first data transmission link, which specifically includes: The first electronic device obtains the first communication identifier assigned by the cloud server to the first electronic device; the first electronic device sends the phone number and the first communication identifier of the first electronic device to the cloud server for binding and storage. ; The first electronic device sends a first query request to the cloud server, the first query request includes the phone number of the second electronic device, and the first query request is used to query the second communication identification of the second electronic device; The first electronic device receives the second communication identifier sent by the cloud server; the first electronic device establishes the auxiliary link with the electronic device based on the first communication identifier and the second communication identifier.

In this way, the establishment of the auxiliary link between the first electronic device and the second electronic device can be completed through the cloud server, thereby realizing far-field communication between the first electronic device and the second electronic device.

In a possible implementation, the auxiliary link includes a P2P link; the first communication identifier is a first session identifier used by the first electronic device to communicate with the cloud server, and the second communication identifier is The second session identifier used by the second electronic device to communicate with the cloud server; the first electronic device establishes the auxiliary link with the electronic device based on the first communication identifier and the second communication identifier, which specifically includes: The first electronic device sends a first acquisition request to the cloud server. The first acquisition request is used to request to acquire the first NAT public network information of the first electronic device; the first electronic device receives the first acquisition request sent by the cloud server. A NAT public network information, the first NAT public network information includes the public network IP address of the first electronic device and the port number of the first electronic device from the public network to the intranet; the first electronic device sends to the cloud server The first message carries the second session identifier and the first NAT public network information. The first message is used to exchange NAT public network information between the first electronic device and the second electronic device; An electronic device receives the second NAT public network information of the second electronic device sent by the cloud server. The second NAT public network information includes the public network IP address of the second electronic device and the public network forwarding address of the second electronic device. The port number of the internal network; the first electronic device establishes a P2P link with the second electronic device based on the first NAT public network information and the second NAT public network information.

In this way, the establishment of a P2P link between the first electronic device and the second electronic device can be completed through the cloud server, thereby realizing far-field communication between the first electronic device and the second electronic device.

In a possible implementation, the auxiliary link includes a server relay link; the first communication identifier is a first session identifier used by the first electronic device to communicate with the cloud server; and the second communication identifier The identifier is a second session identifier used by the second electronic device to communicate with the cloud server; the first electronic device establishes the auxiliary link with the electronic device based on the first communication identifier and the second communication identifier, specifically The method includes: the first electronic device sends a second acquisition request, the second acquisition request is used to acquire the first relay address of the first electronic device; the first electronic device receives the first relay address sent by the cloud server ; The first electronic device sends a first message to the cloud server, the first message carries the second session identifier and the first relay address, and the first message is used between the first electronic device and the second Electronic devices exchange relay addresses; the first electronic device receives the second relay address of the second electronic device sent by the cloud server; after the first electronic device and the second electronic device complete the exchange of relay addresses, the first electronic device The first electronic device and the second electronic device have established a server relay link.

In this way, the establishment of the server relay link between the first electronic device and the second electronic device can be completed through the cloud server, thereby realizing far-field communication between the first electronic device and the second electronic device.

In a second aspect, the present application provides an electronic device, which is a first electronic device including a display screen, one or more processors, and one or more memories. The display screen, one or more memories are coupled to one or more processors, and the one or more memories are used to store computer program codes. The computer program codes include computer instructions. When the one or more processors execute the computer instructions, such that The electronic device performs the data sharing method in any possible implementation of any of the above aspects.

In a third aspect, the present application provides an electronic device, which is a first electronic device and includes one or more functional modules. The one or more functional modules are used to perform any of the possible implementations of any of the above aspects. Data Sharing Methods.

In a fourth aspect, embodiments of the present application provide a computer storage medium that includes computer instructions. When the computer instructions are run on a processor, the data sharing method in any of the possible implementations of any of the above aspects is implemented.

In a fifth aspect, embodiments of the present application provide a computer program product. When the computer program product is run on a computer, the data sharing method in any of the possible implementations of any of the above aspects is implemented.

Among them, the beneficial effects of the second to fifth aspects can be obtained with reference to the first aspect and any possible implementation method of the first aspect. This will not be described again.

Description of drawings

Figure 1 is a schematic architectural diagram of a communication system provided by an embodiment of the present application;

Figure 2A is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present application;

Figure 2B is a schematic diagram of the software structure of an electronic device provided by an embodiment of the present application;

Figure 2C is a schematic diagram of the software structure of another electronic device provided by an embodiment of the present application;

Figures 3A to 3Y are schematic interface diagrams of a set of data sharing scenarios provided by embodiments of the present application;

Figures 4A-4O are schematic diagrams of a set of interfaces for sharing data provided by embodiments of the present application;

Figures 5A-5Y are schematic diagrams of another set of interfaces for sharing data provided by embodiments of the present application;

Figures 6A-6G are schematic diagrams of another set of interfaces for sharing data provided by embodiments of the present application;

Figures 7A-7I are schematic diagrams of another set of interfaces for sharing data provided by embodiments of the present application;

Figures 8A-8D are schematic diagrams of another set of interfaces for sharing data provided by embodiments of the present application;

Figure 9 is a schematic architectural diagram of another communication system provided by an embodiment of the present application;

Figure 10 is a schematic flow chart of a data sharing method provided by an embodiment of the present application;

Figure 11 is a schematic flow chart of a data sharing method provided by another embodiment of the present application;

Figures 12A-12C are schematic diagrams of the acquisition process of information on recently interacted contacts provided by the embodiment of the present application;

Figure 13A is a schematic architectural diagram of another communication system provided by an embodiment of the present application;

Figure 13B is a schematic architectural diagram of another communication system provided by an embodiment of the present application;

Figure 13C is an architectural schematic diagram of another communication system provided by an embodiment of the present application;

Figure 14A is a schematic structural diagram of a data packet provided by an embodiment of the present application;

Figure 14B is a schematic structural diagram of fields in a data packet provided by an embodiment of the present application;

Figure 15 is a schematic diagram of an auxiliary link establishment process provided by an embodiment of the present application;

Figure 16 is a schematic diagram of the acquisition principle of a communication identifier provided by an embodiment of the present application;

Figure 17 is a schematic diagram of the addressing process in an auxiliary link provided by an embodiment of the present application;

Figure 18 is a functional module interaction flow chart of an electronic device provided by an embodiment of the present application;

Figure 19 is a schematic diagram of a P2P direct link establishment process provided by an embodiment of the present application;

Figure 20 is a schematic diagram of a relay link establishment process provided by an embodiment of the present application;

Figure 21 is a schematic diagram of a device wake-up process provided by an embodiment of the present application;

Figure 22 is a schematic diagram of the data structure of a data packet provided by an embodiment of the present application;

Figure 23 is a schematic flow chart of a file withdrawal mechanism provided by an embodiment of the present application;

Figure 24 is a schematic architectural diagram of an interactive voice response call system provided by an embodiment of the present application;

Figure 25 is a schematic diagram of the establishment process of an auxiliary link in an interactive voice response call system provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described clearly and in detail below with reference to the accompanying drawings. Among them, in the description of the embodiments of this application, unless otherwise stated, "/" means or, for example, A/B can mean A or B; "and/or" in the text is only a way to describe related objects. The association relationship means that there can be three relationships. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiment of the present application , "plurality" means two or more than two.

Hereinafter, the terms “first” and “second” are used for descriptive purposes only and shall not be understood as implying or implying relative importance or implicitly specifying the quantity of indicated technical features. Therefore, the features defined as “first” and “second” may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, “plurality” The meaning is two or more.

The following introduces a communication system 10 provided in the embodiment of the present application.

FIG. 1 shows a schematic architectural diagram of a communication system 10 provided in an embodiment of the present application.

As shown in FIG. 1 , the communication system 10 may include an electronic device 100 and one or more electronic devices 200 .

The electronic device 100 can communicate with one or more electronic devices 200 through different communication methods.

In some embodiments, electronic device 100 may communicate with one or more electronic devices 200 over a cellular network. Among them, the cellular network may include but is not limited to global system for mobile communications (GSM), code division multiple access Access (code division multiple access, CDMA), wideband code division multiple access (WCDMA), time division synchronous code division multiple access (TD-SCDMA), long-term evolution (long-term evolution) term evolution (LTE), new radio access (new radio, NR) or other future network systems.

In some embodiments, electronic device 100 may communicate with one or more electronic devices 200 via short-range communication technology. Among them, near field communication includes but is not limited to Bluetooth, wireless loca area network (WLAN), near field communication (NFC), ultra wide band (UWB), infrared, etc.

In some embodiments, electronic device 100 may communicate with one or more electronic devices 200 via a satellite communications network. For example, satellite communication networks can include Beidou communication network, Tiantong communication network, Starlink communication network, etc.

In some embodiments, the electronic device 100 can implement an over-the-top (OTT) call with one or more electronic devices 200 through the Internet. In some examples, the OTT call can be a cross-operator development based on the open Internet. A video and other data service business. For example, OTT calls can be implemented through WLAN, and for another example, OTT calls can be implemented based on the operator's cellular data service.

In the embodiment of the present application, the device type of the electronic device 100 may be a mobile phone, a tablet computer, a handheld computer, a desktop computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, Personal digital assistant (PDA), as well as smart home devices such as smart large screens and smart speakers, wearable devices such as smart bracelets, smart watches, and smart glasses, augmented reality (AR), virtual reality (virtual reality (VR), mixed reality (MR) and other extended reality (XR) devices, vehicle-mounted devices or smart city devices, etc. Any of them.

The device type of the electronic device 200 may be a mobile phone, a tablet computer, a handheld computer, a desktop computer, a laptop computer, a super mobile personal computer, a netbook, a cellular phone, a personal digital assistant, as well as smart home devices such as smart large screens and smart speakers. , wearable devices such as smart bracelets, smart watches, and smart glasses, extended reality devices such as augmented reality, virtual reality, and mixed reality, vehicle-mounted devices or smart city devices, and so on.

In the embodiment of the present application, the specific types of the electronic device 100 and the electronic device 200 are not particularly limited.

The hardware structure of the electronic device 100 provided in the embodiment of the present application is introduced below.

FIG. 2A shows a schematic structural diagram of the electronic device 100.

The following uses the electronic device 100 as an example to describe the embodiment in detail. It should be understood that the electronic device 100 shown in FIG. 2A is only an example, and the electronic device 100 may have more or fewer components than shown in FIG. 2A , two or more components may be combined, or Can have different component configurations. The various components shown in Figure 2A may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.

The electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2. Mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 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 gyro 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 invention does not constitute a specific limitation on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

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

The controller may be the nerve center and command center of the electronic device 100 . The controller can generate operation control signals based on the instruction operation code and timing signals to complete the control of fetching and executing instructions.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. Interfaces may include integrated circuit (inter-integrated circuit, I2C) interface, integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, pulse code modulation (pulse code modulation, PCM) interface, universal asynchronous receiver and transmitter (universal asynchronous 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 I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 can separately couple the touch sensor 180K, charger, flash, camera 193, etc. through different I2C bus interfaces. For example, the processor 110 can be coupled to the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through the I2C bus interface to implement the touch function of the electronic device 100 .

The I2S interface can be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 can be coupled with the audio module 170 through the I2S bus to implement communication between the processor 110 and the audio module 170 . In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the I2S interface to implement the function of answering calls through a Bluetooth headset.

The PCM interface can also be used for audio communications to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface to implement the function of answering calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 and the wireless communication module 160 . For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 . MIPI interfaces include camera serial interface (CSI), display serial interface (DSI), etc. In some embodiments, the processor 110 and the camera 193 communicate through the CSI interface to implement the shooting function of the electronic device 100 . The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the electronic device 100 .

The GPIO interface can be configured through software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 with the camera 193, display screen 194, wireless communication module 160, audio module 170, sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, I2S interface, UART interface, MIPI interface, etc.

The USB interface 130 is an interface that complies with the USB standard specification, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transmit data between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio through them. This interface can also be used to connect other electronic devices, such as AR devices, etc.

It can be understood that the interface connection relationships between the modules illustrated in the embodiment of the present invention are only schematic illustrations and do not constitute a structural limitation of the electronic device 100 . In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

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. In some wired charging embodiments, the charging management module 140 may receive charging input from the wired charger through the USB interface 130 . In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through the wireless charging coil of the electronic device 100 . While the charging management module 140 charges the battery 142, it can also provide power to the electronic device through the power management module 141.

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 charging management module 140, and supplies power to the processor 110, internal memory 121, external memory, display screen 194, camera 193, wireless communication module 160, etc. The power management module 141 can also be used to monitor battery capacity, battery cycle times, battery health status (leakage, impedance) and other parameters. In some other embodiments, the power management module 141 may also be provided in the processor 110 . In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

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

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 may 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 reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

The mobile communication module 150 can provide solutions for wireless communication including 2G/3G/4G/5G applied on the electronic device 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them 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 through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be disposed 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.

A 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-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 sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.), or displays images or videos through display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be independent of the processor 110 and may 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) network), Bluetooth (bluetooth, BT), and global navigation satellites. System (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (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 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to 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 (time-division code division multiple access, TD-SCDMA), long term evolution (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).

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

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD). The display panel can also use 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 (flex light-emitting diode, FLED), miniled, microled, micro-oled, quantum dot light emitting diode (quantum dot light emitting diode, QLED) and other manufacturing. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

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

The ISP is used to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, the light is transmitted to the camera sensor through the lens, the optical signal is converted into an electrical signal, and the camera sensor passes the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise and brightness. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 193.

Camera 193 is used to capture still images or video. The object passes through the lens to produce an optical image that is projected onto 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 passes 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, Image signals in YUV and other formats. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

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 a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. In this way, the electronic device 100 can play or record videos in multiple encoding formats, such as moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can continuously learn by itself. Intelligent cognitive applications of the electronic device 100 can be implemented through the NPU, such as image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 can 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 external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The processor 110 executes instructions stored in the internal memory 121 to execute various functional applications and data processing of the electronic device 100 . The internal memory 121 may include a program storage area and a data storage area. Among them, the stored program area can store an operating system, at least one application program required for a function (such as a sound playback function, an image playback function, etc.). The storage data area may store data created during use of the electronic device 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

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

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

Speaker 170A, also called "speaker", is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music through the speaker 170A, or listen to hands-free calls.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a call or a voice message, the voice can be heard by bringing the receiver 170B close to the human ear.

Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak close to the microphone 170C with the human mouth and input the sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C, which in addition to collecting sound signals, may also implement a noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions, etc.

The headphone interface 170D is used to connect wired headphones. The headphone interface 170D may be a USB interface 130, or may be a 3.5mm open mobile terminal platform (OMTP) standard interface, or a Cellular Telecommunications Industry Association of the USA (CTIA) standard interface.

The pressure sensor 180A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, pressure sensor 180A may be disposed on display screen 194 . There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor may include at least two parallel plates of conductive material. When a force is applied to pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation is performed 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 based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch location but with different touch operation intensities may correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold is applied to the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold is applied to the short message application icon, an instruction to create a new short message is executed.

The gyro sensor 180B may be used to determine the motion posture of the electronic device 100 . In some embodiments, the angular velocity of electronic device 100 about three axes (ie, x, y, and z axes) may be determined by gyro sensor 180B. The gyro sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyro sensor 180B detects the angle at which the electronic device 100 shakes, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shake of the electronic device 100 through reverse movement to achieve anti-shake. Gyro sensor 180B can still be used For navigation and somatosensory game scenes.

Air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

Magnetic sensor 180D includes a Hall sensor. The electronic device 100 may utilize the magnetic sensor 180D to detect opening and closing of the flip holster. In some embodiments, when the electronic device 100 is a flip machine, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. Then, based on the detected opening and closing status of the leather case or the opening and closing status of the flip cover, features such as automatic unlocking of the flip cover are set.

The acceleration sensor 180E can detect the acceleration of the electronic device 100 in various directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of electronic devices and be used in horizontal and vertical screen switching, pedometer and other applications.

Distance sensor 180F for measuring distance. Electronic device 100 can measure distance via infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 may utilize the distance sensor 180F to measure distance to achieve fast focusing.

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 electronic device 100 emits infrared light outwardly through the light emitting diode. Electronic device 100 uses photodiodes to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100 . When insufficient reflected light is detected, the electronic device 100 may determine that there is no object near the electronic device 100 . The electronic device 100 can use the proximity light sensor 180G to detect when the user holds the electronic device 100 close to the ear for talking, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in holster mode, and pocket mode automatically unlocks and locks the screen.

The ambient light sensor 180L is used to sense ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in the pocket to prevent accidental touching.

Fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access to application locks, fingerprint photography, fingerprint answering of incoming calls, etc.

Temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 utilizes the temperature detected by the temperature sensor 180J to execute the temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of a processor located near the temperature sensor 180J in order to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to prevent the low temperature from causing the electronic device 100 to shut down abnormally. In some other embodiments, when the temperature is lower than another threshold, the electronic device 100 performs boosting on the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperature.

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

Bone conduction sensor 180M can acquire vibration signals. In some embodiments, the bone conduction sensor 180M can acquire the vibration signal of the vibrating bone mass of the human body's vocal part. The bone conduction sensor 180M can also contact the human body's pulse and receive blood pressure beating signals. In some embodiments, the bone conduction sensor 180M can also be provided in an earphone and combined into a bone conduction earphone. The audio module 170 can analyze the voice signal based on the vibration signal of the vocal vibrating bone obtained by the bone conduction sensor 180M to implement the voice function. The application processor can analyze the heart rate information based on the blood pressure beating signal acquired by the bone conduction sensor 180M to implement the heart rate detection function.

The buttons 190 include a power button, a volume button, etc. Key 190 may be a mechanical key. It can also be a touch button. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100 .

The motor 191 can generate vibration prompts. The motor 191 can be used for vibration prompts for incoming calls and can also be used for touch vibration feedback. For example, touch operations for different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. The motor 191 can also respond to different vibration feedback effects for touch operations in different areas of the display screen 194 . Different application scenarios (such as time reminders, receiving information, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

The indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, or may be used to indicate messages, missed calls, notifications, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195 . The electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. SIM card interface 195 can support Nano SIM card, Micro SIM card, SIM card, etc. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement calls, data communications, etc. Function. In some embodiments, the electronic device 100 uses an eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100 .

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. For example, the layered architecture software system can be the Android system, the Harmony operating system (operating system, OS), or other software systems.

FIG. 2B is a software structure block diagram of the electronic device 100 according to the embodiment of the present invention. FIG. 2B takes the Android system with a layered architecture as an example to illustrate the software architecture of the electronic device 100 .

The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime and system libraries, and kernel layer.

The application layer can include a series of application packages.

As shown in Figure 2B, the application package can include camera, gallery, calendar, calling, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

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

As shown in Figure 2B, the application framework layer can include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

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

Content providers are used to store and retrieve data and make this data accessible to applications. Said data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

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

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

The resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.

The notification manager allows applications to display notification information in the status bar, which can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, text information is prompted in the status bar, a beep sounds, the electronic device vibrates, the indicator light flashes, etc.

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

The core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.

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

System libraries can include multiple functional modules. For example: surface manager (surface manager), media libraries (Media Libraries), 3D graphics processing libraries (for example: OpenGL ES), 2D graphics engines (for example: SGL), etc.

The surface manager is used to manage the display subsystem and provides the fusion 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 static image files, etc. The media library can support a variety of 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, composition, and layer processing.

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 following exemplifies the workflow of the software and hardware of the electronic device 100 in conjunction with capturing the photographing scene.

When the touch sensor 180K receives a touch operation, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes touch operations into raw input events (including touch coordinates, timestamps of touch operations, and other information). Raw input events are stored at the kernel level. The application framework layer obtains the original input event from the kernel layer and identifies the control corresponding to the input event. The touch operation is a touch click operation, and the click operation For example, the corresponding control is the control of the camera application icon. The camera application calls the interface of the application framework layer to start the camera application, and then starts the camera driver by calling the kernel layer to capture still images or videos through the camera 193 .

The software system of the electronic device 100 provided in the embodiment of this application is introduced below.

FIG. 2C exemplarily shows a software system architecture diagram of an electronic device 100 provided in an embodiment of the present application.

As shown in FIG. 2C, the software system of the electronic device 100 may include an application processor system and a wireless communication system. in:

The wireless communication system may include, but is not limited to, at least one of the following: cellular communication system (such as 2G/3G/4G/5G/6G, etc.), satellite system (such as Beidou, Tiantong, Starlink, etc.), Wi-Fi, BT, NFC, UWB, etc. In one implementation, the wireless communication system may include a coprocessor (CoProcessor, CP) and/or a digital signal processor (digital signal processor, DSP), where the CP in the terminal may be a baseband chip plus a coprocessor or Multimedia accelerator, CP can include the digital components required to communicate with the network, CP can include a reduced instruction set computer (RISC) microprocessor (advanced RISC machines, ARM)-based processor and a DSP. The CP can have an operating system and can communicate with an application processor running Android, IOS, Windows and other operating systems through a high speed (HS) serial connection. CP can implement processing logic such as VR, AR, image processing, high fidelity (HiFi), high-speed data transmission (high data rate, HDR), and sensor management. It is not limited to this, the CP can also be a cellular processor (CP).

The application processor system is used to implement control logic such as rendering and presentation of the user interface, input and response to user operations, business functions, and playback of multimedia data such as audio/video.

The application processor system may include a sharing module, a discovery module, a Wi-Fi function module, a BT function module, a UWB function module, a satellite (Satellite) function module, a Wi-Fi link module, a BT link module, and a UWB link module. Satellite link module. in:

The fusion call (FusionCall) module can be understood as the core functional module for sharing data. Among them, the functions of the integrated call module may include but are not limited to the following functions: 1. Responsible for calling the network address service module to manage the auxiliary link (for example, the establishment and release of the auxiliary link). 2. Responsible for reading shared content data (for example, file data, location information, open links, calendars, application installation packages, etc.). 3. Responsible for the offloading, transmission, and unpacking of shared content data, etc. 4. Responsible for writing and storing shared content data. 5. Responsible for the display of relevant user experience (UX) interfaces, including but not limited to: system sharing interface (including options for currently interacting contacts or options for recently interacted contacts), in-app sharing interfaces/windows Options for interactive contacts or options for recently interacted contacts, sending window, receiving window, prompt information, buttons/controls, etc.

The discovery module is used to discover nearby devices through near field communication technologies such as Wi-Fi, BT, and D2D. The discovery module is called Nearby, for example. It is not limited to this, and the device can also be discovered through far-field communication technologies such as cellular communication technology, satellite, and Wi-Fi. This application does not limit the communication technology of the discovered device.

The network address service module can be used to be responsible for managing the auxiliary link (for example, the establishment and release of the auxiliary link).

The Wi-Fi function module is used to implement Wi-Fi communication with other devices based on the Wi-Fi communication protocol.

The BT function module is used to communicate with other devices based on BT or Bluetooth low energy (BLE).

The UWB function module is used to share data based on UWB communication technology.

The satellite function module is used to share data based on satellite communication.

The Wi-Fi link module is used to manage Wi-Fi links, such as but not limited to link establishment, release, data transmission, etc.

The BT link module is used to manage BT links, including but not limited to link establishment, release, data transmission, etc.

The UWB link module is used to manage UWB links, including but not limited to link establishment, release, data transmission, etc.

The satellite link module is used to manage communication satellite links, including but not limited to link establishment, release, data transmission, etc.

The wireless communication system of the electronic device 100 includes a cellular communication module, a Wi-Fi communication module, a BT communication module and a satellite communication module, wherein:

Cellular communication module (modem) includes Internet protocol (IP) multimedia system (IP multimedia subsystem, IMS) communication module, circuit switching (circuited switched, CS) communication module and 3G/4G/5G/6G broadcast module. Among them, IMS The communication module can, but is not limited to, realize LTE voice call (voice over LTE, VoLTE), LTE video call (video over LTE, ViLTE), NR voice call (voice over NR, VoNR), NR video call (video over NR, ViNR) , Wi-Fi voice call (voice over Wi-Fi, VoWiFi), Wi-Fi video call (video over Wi-Fi, ViWiFi), evolved packet system fallback (evolved packet system-Fallback, EPS-Fallback), etc. based on IMS protocol call. The CS communication module can provide the CS Fallback function.

The 3G/4G/5G/6G broadcast module can be used to monitor the 3G/4G/5G/6G broadcast channel. The electronic device 100 may be within the coverage area of at least one base station, and any one of the at least one base station may broadcast to electronic devices (including electronic devices) in the coverage area through broadcast channels. The sub-device 100) sends broadcast data (such as audio stream/video stream and other multimedia data). Any base station can maintain at least one channel, and the broadcast data corresponding to different channels can be different. In some examples, the user can select a channel corresponding to the received broadcast data through the electronic device 100 . In some examples, the electronic device 100 can receive broadcast data sent by the base station through a 3G/4G/5G/6G broadcast module, and the 3G/4G/5G/6G broadcast module can report it through a cellular communication network card (not shown) at the kernel layer. Processed at the system level. In some examples, the electronic device 100 can play the received broadcast data through a system application (such as a call) or a third-party application (such as a chat application, conferencing application), and the electronic device 100 can share the played content with other devices. In other examples, the electronic device 100 may not play the received broadcast data, but directly share the received broadcast data with other devices, or share the processed broadcast data with other devices.

The Wi-Fi communication module may include hardware modules for WiFi communication, such as firmware and chips.

The BT communication module may include hardware modules for BT communication, such as firmware and chips.

The satellite communication module may include hardware modules for satellite communication, such as firmware and chips.

In this embodiment of the present application, the hardware structure of the electronic device 200 may refer to the hardware structure of the electronic device 100 in FIG. 2A , and the software framework of the electronic device 2000 may refer to the software framework of the electronic device 100 shown in FIG. 2B or 2C . The electronic device 200 may include more, less, or the same hardware structure as the electronic device 100 , and the electronic device 200 may include more, fewer, or the same software modules as the electronic device 100 , which is not limited in this application.

The following is an introduction to some data sharing scenarios provided by the embodiments of this application.

Figures 3A to 3Y exemplarily illustrate some data sharing scenarios provided by embodiments of the present application.

In a data sharing scenario, the electronic device 100 can share locally stored files such as pictures or videos with other devices.

For example, as shown in FIG. 3A , the electronic device 100 can display a picture display interface 3010. The picture display interface 3010 includes a picture 3011 and a menu 3012. The menu 3012 may include a share button 3013, a favorite button 3014, an edit button 3015, a delete button 3016, and a more button 3017. The picture 3011 may have a title, for example, "Landscape." Among them, the share button 3013 can be used to trigger opening of the system sharing interface. The collection button 3014 can be used to trigger collection of the picture 3011 to the picture collection folder. The edit button 3015 can be used to trigger editing functions such as rotating, trimming, adding filters, blurring, etc. to the picture 3011. The delete button 3016 can be used to trigger deletion of the picture 3011. The more button 3017 can be used to trigger opening of more image-related functions.

The electronic device 100 may receive user input (eg, click) on the share button 3013, and in response to the input, the electronic device 100 may display the system sharing interface 3020 as shown in FIG. 3B.

As shown in Figure 3B, the system sharing interface 3020 includes an area 3021, an area 3022 and an area 3023. The area 3021 may be used to display one or more pictures or videos in the gallery of the electronic device 100 , and the one or more pictures or videos may include pictures or videos selected by the user. A mark may be displayed on the selected picture, and the mark may be used to indicate that the corresponding picture is selected (that is, the picture has been selected by the user). The pictures or video images displayed in this area 3021 may be thumbnails. The original image corresponding to the picture or video picture displayed in the area 3021 can be stored on the electronic device 100 .

Area 3022 may be used to display options for nearby devices discovered by the electronic device 100 (eg, “Alee’s phone” option, “HUAWEI P50” option, “HUAWEI P50 Pro” option). When the electronic device 100 is searching for a nearby device, it may display a search prompt in the area 3022 (for example, a text prompt such as "Discovering a nearby device, the other party needs to turn on Bluetooth and WLAN"). Icons with one or more service options (for example, chat application icon, welink application icon, smooth connection application icon, chat application icon, mail application icon, browser application icon, information application icon, WLAN direct connection) may be displayed in the area 3023 icon, etc.). The application or protocol corresponding to the service option can support sharing user-selected pictures to contacts or servers. Users can share data through the application or protocol corresponding to the service option. For example, the selected picture is shared to one or more contacts in the chat application, or the selected picture is shared to the dynamic publishing platform (ie, server) of the chat application, and so on.

The electronic device 100 may receive the user's input (such as a click) for the option of "Alee's Phone", and in response to the input, the electronic device 100 may send the picture or video selected by the user to the location corresponding to the option of "Alee's Phone". on the device.

In another data sharing scenario, the electronic device 100 can share the playback link of the specified video in the video application to other devices. The designated videos include but are not limited to short videos (for example, videos that are shorter than the designated playback time, etc.), long videos (for example, movies and TV series that exceed the designated playback time, etc.), live videos, and so on.

For example, as shown in FIG. 3C , the electronic device 100 may display a video application interface 3030. The video application interface 3030 may include a video playback screen 3031 of a short video or a live video, an account icon 3032, a like icon 3033, a comment icon 3034, and a favorite image. logo 3035 and sharing icon 3036, video text (for example, "Seaside Vacation"), video publisher name (for example, "User 1"), etc. Among them, the account icon 3032 can display the avatar of the publishing account of the short video or live video, the like icon 3033 can be used to mark that the short video or live video is liked by the user, and the comment icon 3034 can be used to trigger the electronic device 100 to display Comment information for this short video or live video. The favorite icon 3035 can be used to trigger the electronic device 100 to save the playback link of the short video or live video to the favorites associated with the logged-in account on the video application. The sharing icon 3036 can be used to trigger the electronic device 100 to share the play link of the short video or live video.

The electronic device 100 may receive user input (eg, click) on the share icon 3036, and in response to the input, the electronic device 100 may display a menu window 3040 as shown in FIG. 3D.

As shown in Figure 3D, the menu window 3040 includes one or more options for sharing services. For example, the sharing service options may include sharing options within the video application (for example, forwarding options, private message options) and/or sharing options for other applications (for example, friend circle options, chat application options, Weilink application options, etc. ). This forwarding option can be used to forward the short video or live video to the circle of friends of the logged-in account on the video application. The private message option can be used by the electronic device 100 to forward the short video or live video to contacts associated with the logged-in account on the video application. The circle of friends option can be used to trigger the electronic device 100 to forward the play link of the short video or live video to the circle of friends of the logged-in account in the chat application. The chat application option can be used to trigger the electronic device 100 to forward the play link of the short video or live video to the contact in the chat application. The welink application option can be used to trigger the electronic device 100 to forward the playback link of the short video or live video to the contact in the welink application. The menu window 3040 may also include other functional controls (for example, reporting controls, collection controls, save controls, link copy controls, etc.).

The electronic device 100 may switch to display more options of the sharing service on the menu window 3040 in response to the user's input (eg, sliding input) on the menu window 3040 .

As shown in FIG. 3E, the electronic device 100 may display more controls 3041 in the menu window 3040. The electronic device 100 may receive user input (eg, click) to the more control 3041, and in response to the input, the electronic device 100 may display the system sharing window 3050 as shown in FIG. 3F.

As shown in Figure 3F, the system sharing window 3050 may include the play link option 3051, area 3052 and area 3053 of the above-mentioned short video or live video. The play link option 3051 may display description information for the short video or live video (for example, "I just saw this in the short video, come and watch: [Seaside Vacation]"). This area 3052 can be used to display nearby device options discovered by the electronic device 100, and one or more user options (for example, "Alee's mobile phone" option, "HUAWEI P50" option, "HUAWEI P50 Pro" option). This user option corresponds to nearby devices discovered by the electronic device 100 . When the electronic device 100 is searching for nearby devices, it may display a search prompt in area 3052 (for example, text prompts such as "Discovering nearby devices, the other party needs to turn on Bluetooth and WLAN"). Icons with one or more service options (for example, chat application icon, welink application icon, smooth connection application icon, chat application icon, mail application icon, browser application icon, information application icon, WLAN direct connection) may be displayed in the area 3053 icon, etc.). The application or protocol corresponding to the service option can support sharing the playback link of the short video or live video selected by the user to a contact or server. Users can share data through the application or protocol corresponding to the service option. For example, share the playback link of the selected short video or live video to one or more contacts in the chat application, or share the playback link of the selected short video or live video to the dynamic publishing platform (i.e. server) of the chat application. etc.

The electronic device 100 may receive the user's input (such as a click) for the user option (such as the option of "Alee's mobile phone"), and in response to the input, the electronic device 100 may play the link of the short video or live video selected by the user. and the description information is sent to the nearby device corresponding to the option of the user (for example, the option of "Alee's phone").

In another data sharing scenario, the electronic device 100 can share the open link of a specified online article in an information application to other devices. Among them, the designated online articles include but are not limited to news, blogs, etc.

For example, as shown in FIG. 3G, the electronic device 100 can display a news application interface 3060. The news application interface 3060 may include the title of the news article (for example, "Golf boy Alee won the gold medal in his debut"), the content of the news article (for example, "Yesterday, golf boy Alee made his debut at the golf tournament, winning four rounds of gold"). The total score of 267 won the gold medal."), the name of the publisher of the news article (for example, "Morning News") and avatar, more controls 3061.

The electronic device 100 may receive user input (eg, click) to the more control 3061, and in response to the input, the electronic device 100 may display a share menu 3070 as shown in FIG. 3H.

As shown in Figure 3H, the sharing menu 3070 may include one or more sharing service options. For example, the one or more sharing service options may include sharing options within the news application (for example, private message options and forwarding options, etc.) and/or sharing options for other applications (for example, friend circle options, chat application options , welink application options, etc.), and system sharing options 3071. This forwarding option can be used to forward the open link of the news article to the circle of friends of the logged-in account on the video application. This private message option is available on electronic devices 100 Send the opening link of the news article to the contact associated with the logged-in account on the video application. The friend circle option can be used to trigger the electronic device 100 to forward the open link of the news article to the friend circle of the logged-in account in the chat application. The chat application option may be used to trigger the electronic device 100 to forward the open link of the news article to the contact in the chat application. The welink application option can be used to trigger the electronic device 100 to forward the open link of the news article to the contact in the welink application. The sharing menu 3070 may also include other functional controls (for example, collection controls, link copy controls, etc.).

The electronic device 100 may respond to the user's input (eg, click) on the system sharing option 3071 in the sharing menu 3070, and in response to the input, the electronic device 100 may display the system sharing window 3080 as shown in FIG. 3I.

As shown in Figure 3I, the system sharing window 3080 may include the open link option 3081, area 3082 and area 3083 of the above-mentioned news article. The open link option 3081 may display description information of the news article (for example, "News Information APP: [Golfer Alee wins gold medal in debut]"). This area 3082 can be used to display options for nearby devices discovered by the electronic device 100 (for example, "Alee's mobile phone" option, "HUAWEI P50" option, "HUAWEI P50 Pro" option). When the electronic device 100 is searching for nearby devices, it may display a search prompt in area 3082 (for example, text prompts such as "Discovering nearby devices, the other party needs to turn on Bluetooth and WLAN"). Icons with one or more service options (for example, chat application icon, welink application icon, smooth connection application icon, chat application icon, mail application icon, browser application icon, information application icon, WLAN direct connection) may be displayed in the area 3083 icon, etc.). The application or protocol corresponding to the service option may support the sharing of user-selected news articles to open connections to contacts or servers. Users can share data through the application or protocol corresponding to the service option. For example, the open link of the selected news article is shared to one or more contacts of the chat application, or the open link of the selected news article is shared to the dynamic publishing platform (i.e., server) of the chat application, and so on.

The electronic device 100 may receive user input (eg, click) for the option of "Alee's Phone", and in response to the input, the electronic device 100 may send an open link of the news article that the user is browsing to the option of "Alee's Phone" on the corresponding nearby device.

In another data sharing scenario, the electronic device 100 can share the location information of a specified location with other devices in a map application. The designated location may be an address selected by the user on the map, or the current location of the electronic device 100 .

For example, the electronic device 100 can share the location of the scenic spot selected by the user with other devices in a map application. As shown in Figure 3J, the electronic device 100 can display a map application interface 3090. The map application interface 3090 includes an address search input box 3091, a search control 3092, a map 3093, a mark 3094 of the location of the scenic spot, and a mark 3095 of the location of the electronic device 100 in the map 3093. Among them, the address search input box 3091 can be used to receive the address name input by the user. The search control 3092 can be used to trigger the electronic device 100 to display the location information corresponding to the address name input by the user.

The electronic device 100 may receive a selection operation (eg, click) for the marker 3094 of the attraction location, and in response to the input, the electronic device 100 may display the address details window 3096 as shown in FIG. 3K .

As shown in Figure 3K, the address details window 3096 may include location information 3097 corresponding to the scenic spot location (for example, "No. 4065, Xilihu Road, Nanshan District, Shenzhen City, Guangdong Province", etc.), route controls, and sharing controls. 3098, collection controls, peripheral controls, etc. The route control can be used to trigger the electronic device 100 to display route information corresponding to the location of the electronic device 100 to the location of the scenic spot. The sharing control 3098 can be used to trigger the electronic device 100 to share the scenic spot location with other devices or contacts. The collection control can be used to trigger the electronic device 100 to collect the location information of the scenic spot into favorites, so that the user can quickly find the location information of the scenic spot when opening the map application next time.

Electronic device 100 may receive user input (eg, click) to the share control 3098, and in response to the input, electronic device 100 may display menu window 3100 as shown in FIG. 3L.

As shown in Figure 3L, the menu window 3100 may include one or more options for sharing services. For example, the one or more sharing service options may include sharing options within the map application (for example, private message options) and/or sharing options for other applications (for example, friend circle options, chat application options, welink application options, etc. etc.), and more sharing options3101, etc. The private message option can be used by the electronic device 100 to forward the location information of the attraction location to contacts associated with the logged-in account on the map application. The friend circle option can be used to trigger the electronic device 100 to forward the location information of the scenic spot location to the friend circle of the logged-in account in the chat application. The chat application option may be used to trigger the electronic device 100 to forward the location information of the scenic spot location to the contact in the chat application. The welink application option can be used to trigger the electronic device 100 to forward the location information of the scenic spot location to the contact in the welink application. The more sharing options 3101 can be used to trigger the electronic device 100 to call the system sharing function on the electronic device 100 and display the system sharing window. The sharing menu 3070 may also include other functional controls (eg, picture generation controls, etc.), which may be used to trigger the electronic device 100 to generate a picture of the map portion currently displayed by the electronic device 100 .

The electronic device 100 may receive and respond to user input (eg, click) in the more sharing options 3101, and in response to the input, the electronic device 100 may display a system sharing window 3110 as shown in FIG. 3M.

As shown in Figure 3M, the system sharing window 3110 may include the location information option 3111, area 3112 and area 3113 of the scenic spot location. The location information option 3111 may display the location information of the scenic spot location (for example, "This is No. 4065, Xilihu Road, Nanshan District, Shenzhen City, Guangdong Province..."). This area 3082 can be used to display nearby device options discovered by the electronic device 100 (for example, "Alee's mobile phone" option, "HUAWEI P50" option, "HUAWEI P50 Pro" option). This user option corresponds to nearby devices discovered by the electronic device 100 . When the electronic device 100 is searching for nearby devices, it may display a search prompt in area 3082 (for example, text prompts such as "Discovering nearby devices, the other party needs to turn on Bluetooth and WLAN"). Icons with one or more service options (for example, chat application icon, welink application icon, smooth connection application icon, chat application icon, mail application icon, browser application icon, information application icon, WLAN direct connection) may be displayed in the area 3083 icon, etc.). The application or protocol corresponding to the service option can support sharing user-selected location information to contacts or servers. Users can share data through the application or protocol corresponding to the service option. For example, the selected location information is shared to one or more contacts of the chat application, or the selected location information is shared to the dynamic publishing platform (ie, server) of the chat application, and so on.

The electronic device 100 can receive the user's input (such as a click) for the option of "Alee's Phone", and in response to the input, the electronic device 100 can send the location information of the above-mentioned attraction location to the vicinity corresponding to the option of "Alee's Phone". on the device.

In another example, the electronic device 100 shares the location information of the current location of the electronic device 100 with other devices. As shown in FIG. 3N, the electronic device 100 can display a map application interface 3090. For the text description of the map application interface 3090, you may refer to the text description part of the embodiment shown in FIG. 3J, which will not be described again here.

The electronic device 100 may receive a user's selection operation (eg, click) on the location mark 3095 in the map application interface 3090, and in response to the input, the electronic device 100 may display an address details window 3120 as shown in FIG. 3O.

As shown in Figure 3O, the address details window 3120 may include location information of the current location of the electronic device 100 (for example, "at the parking lot at the southeast gate of Shenzhen Wildlife Park"), sharing controls 3121, check-in controls, and so on. The sharing control 3121 can be used to trigger the electronic device 100 to share the location information of the current location of the electronic device 100 with other devices or contacts.

The electronic device 100 may receive user input (eg, click) to the sharing control 3121, and in response to the input, the electronic device 100 may display a menu window 3130 as shown in FIG. 3P.

As shown in Figure 3P, the menu window 3130 may include one or more options for sharing services. For example, the one or more sharing service options may include sharing options within the map application (for example, private message options) and/or sharing options for other applications (for example, friend circle options, chat application options, welink application options, etc. etc.), and more sharing options 3131, etc. For the text description of the menu window 3130, please refer to the text description of the menu window 3100 in the embodiment shown in FIG. 3L, which will not be described again here.

The electronic device 100 may receive and respond to user input (eg, click) in the more sharing options 3131, and in response to the input, the electronic device 100 may display a system sharing window 3140 as shown in FIG. 3Q.

As shown in Figure 3Q, the system sharing window 3140 may include a location information option 3141, an area 3142 and an area 3143 of the current location of the electronic device 100. The location information option 3141 may display location information of the current location of the electronic device 100 (for example, "I am in the parking lot of the southeast gate of Shenzhen Wildlife Park...") and/or an open link of the location. For the text description of the area 3142, please refer to the text description of the area 3112 in the embodiment shown in FIG. 3M. For the text description of the area 3143, please refer to the text description of the area 3113 in the embodiment shown in FIG. 3M. I won’t go into details here.

The electronic device 100 may receive the user's input (eg, click) for the option of "Alee's mobile phone" in the area 3142, and in response to the input, the electronic device 100 may send location information of the current location of the electronic device 100 to "Alee's mobile phone". ” option on nearby devices.

In another data sharing scenario, the electronic device 100 can share the installation package or download link of the application installed on the electronic device 100 to other devices.

For example, as shown in FIG. 3R, the electronic device 100 may display a desktop 3150. The desktop 3150 displays a page on which application icons are placed. The page includes multiple application icons (for example, weather application icon, stock application icon, calculator application icon, settings application icon, mail application icon, music application icon, video Application icon, browser application icon, map application icon, gallery application icon, memo application icon, voice assistant application icon, etc.). Optionally, a status bar is displayed in an upper part of the desktop 3150. The status bar may include: one or more signal strength indicators of mobile communication signals (also called cellular signals), battery status indicators, and time. Indicators, etc. Page indicators are also displayed below multiple application icons to indicate the total number of pages on the desktop 3150 and the positional relationship between the currently displayed page and other pages. For example, the desktop 3150 may include three pages, and a white dot in the page indicator may indicate that the currently displayed page is the rightmost page among the three pages. Further optionally, there are multiple trays below the page indicator Icons (such as dialer application icon, messaging application icon, contact application icon, camera application icon), the tray icon remains displayed when switching pages.

The electronic device 100 may receive input (eg, long press) for the map application icon 3151, and in response to the input, the electronic device 100 may display a shortcut menu 3152 as shown in FIG. 3S.

As shown in Figure 3S, the shortcut menu 3152 may include a sharing control 3153 and an uninstalling control 3154. The sharing control 3153 can be used to trigger the electronic device 100 to call the system sharing function and display the system sharing window to share the map application with other devices or contacts. The uninstall control 3154 can be used to trigger the electronic device 100 to uninstall the map application.

The electronic device 100 may receive user input (eg, click) to the sharing control 3153, and in response to the input, the electronic device 100 may display the system sharing window 3160 as shown in FIG. 3T.

As shown in FIG. 3T , the system sharing window 3160 may include a map application option 3161 , an area 3162 and an area 3163 . The map application option 3161 may display the name of the map application (for example, "map"), data size (for example, "40.82MB"), file type (for example, "base.apk"), and so on. The text description for the area 3162 may refer to the text description for the area 3112 in the embodiment shown in FIG. 3M. The text description for the area 3163 may refer to the text description for the area 3113 in the embodiment shown in FIG. 3M. I won’t go into details here.

The electronic device 100 can receive the user's input for the option of "Alee's mobile phone" in the area 3162, and in response to the input, the electronic device 100 can send the installation package of the map application or the download link of the map application to "Alee's mobile phone" options on nearby devices.

In another data sharing scenario, the electronic device 100 can share contact information on the electronic device 100 with other devices.

For example, as shown in FIG. 3U, the electronic device 100 may display a contact application interface 3170. The contact application interface 3170 includes options for one or more contacts (eg, "Alice" option 3174, "Anna" option, "Bob" option, "Britney" option, etc.).

The electronic device 100 may receive user input (eg, click) to the "Alice" option 3174, and in response to the input, the electronic device 100 may display the contact information interface 3180 as shown in FIG. 3V.

As shown in Figure 3V, the contact information interface 3180 may include the name, avatar, phone number (for example, "186XXXXXXXX") of the contact "Alice", a voice call control 3181, a video call control 3182, a text message control 3183, and a collection control. 3184, editing control 3185, more options control 3186, and so on. The voice call control 3181 can be used to trigger the electronic device 100 to make a voice call to the electronic device of the contact "Alice". The video call control 3182 can be used to trigger the electronic device 100 to make a video call to the electronic device of the contact "Alice". The text message control 3183 can be used to trigger the electronic device 100 to send a text message to the electronic device of the contact "Alice". The collection control 3184 can be used to trigger the electronic device 100 to collect the contact information of the contact "Alice" into favorites. The editing control 3185 can be used to trigger the electronic device 100 to modify the contact information of the contact "Alice". The more options control 3186 can be used to trigger the electronic device 100 to display more contact functions.

The electronic device 100 may receive user input (eg, click) to the more options control 3186, and in response to the input, the electronic device 100 may display a menu window 3187 as shown in FIG. 3W.

As shown in Figure 3W, the menu window 3187 may include a share contact option 3188, a blacklist option, a create shortcut option, a delete contact option, and so on. The share contact option 3188 can be used to trigger the electronic device 100 to call the system sharing function and display the system sharing window to share the contact information of the contact "Alice" with other contacts or other devices. The add blacklist option can be used to trigger the electronic device 100 to add the contact "Alice" to the blacklist, so as to prohibit the contact "Alice" from making incoming audio calls or video calls and sending text messages. The create shortcut option can be used to trigger the electronic device 100 to create a shortcut of the contact information interface 3180 and place it on the desktop, so that the user can quickly open the contact interface 3180 directly from the desktop through the shortcut. The delete contact option may be used to trigger the electronic device 100 to delete the contact information of the contact "Alice".

The electronic device 100 receives user input (eg, a click) to the share contact option 3188, and in response to the input, the electronic device 100 may display a menu window 3190 as described in FIG. 3X.

As shown in Figure 3X, the menu window 3190 may include one or more sharing mode options and a cancel control 3194. Among them, the one or more sharing method options include QR code option 3191, vCard option 3192, text option 3193, and so on. The QR code option 3191 can be used to trigger the electronic device 100 to share the contact information of the contact "Alice" in the form of a QR code to other contacts or other devices. The vCard option 3192 can be used to trigger the electronic device 100 to share the contact information of the contact "Alice" in the form of a vCard to other contacts or other devices. The text option 3193 can be used to trigger the electronic device 100 to share the contact information of the contact "Alice" to other contacts or other devices in text form. The cancel control 3194 is used to close the menu window 3190.

The electronic device 100 may receive user input (eg, click) on the QR code option 3191, and in response to the input, the electronic device 100 The system sharing window 3200 shown in Figure 3Y may be displayed.

As shown in Figure 3Y, the system sharing window 3200 may include a contact information option 3201, an area 3202, and an area 3203. Among them, the contact information option 3201 may display a QR code or a thumbnail of the QR code generated based on the contact information of the contact "Alice", as well as the data size (for example, 21.79KB), name ( For example, "Alice's contact information.jpg") and so on. The text description for the area 3202 may refer to the text description for the area 3112 in the embodiment shown in FIG. 3M. The text description for the area 3203 may refer to the text description for the area 3113 in the embodiment shown in FIG. 3M. I won’t go into details here.

The electronic device 100 may receive the user's input (eg, click) for the option "Alee's mobile phone" in the area 3202, and in response to the input, the electronic device 100 may generate a QR code based on the contact information of the contact "Alice". , the option to send to "Alee's phone" corresponds to the nearby device.

It can be seen from the above data sharing scenario that in the process of sharing data, when the electronic device 100 calls the system sharing function to share, it can only share the nearby devices that the electronic device 100 searches for at a close distance. If there are devices nearby 100 or the electronic device 100 cannot search for devices through Bluetooth or WiFi, the electronic device 100 cannot share. If the electronic device 100 wants to share data with these devices near the electronic device 100 or devices that the electronic device 100 cannot search through Bluetooth or WiFi, the same designated application needs to be downloaded on both the electronic device 100 and these devices, and the electronic device 100 needs to The logged-in account of the specified application and the logged-in account of the specified application on these devices must have an associated relationship, that is, the two accounts are friends with each other. In this way, the sharing operation is more complicated.

The embodiment of the present application provides a data sharing method, which can enable the electronic device 100 to share data (for example, pictures, videos, document files, location information, links, contacts, calendars, The option to add currently interacting contacts (e.g., current call contacts) and/or recently interacted contacts in the system sharing interface (or window) of an application package, etc.) or in the in-app sharing interface (or window) (For example, recent call contacts, recent private message contacts, etc.) options, and so on. After the electronic device 100 receives the user's input on the options of the currently interacted contact and/or the options of the recently interacted contact, the electronic device 100 shares the specified data selected by the user to the electronic device 200 corresponding to the contact specified by the user. . In this way, the electronic device 100 can share data with devices that are not near the electronic device 100 and can also share content with some unfamiliar devices, which expands the sharing scenarios and improves the user's sharing experience.

In the embodiment of the present application, the interaction between the electronic device 100 and the electronic device 200 may include: operator calls, receiving/sending text messages, interactions within social applications, and so on. Among them, interactions within social applications can include OTT calls, receiving/sending private messages, liking/being liked, commenting/being commented on, following/being followed, collecting/favoriting the other party’s live broadcast, content posted in friend circles, etc. Interactive social. Among them, the social applications include but are not limited to instant messaging applications, live video applications, music playing applications, and other applications with multi-user social attributes.

A data sharing method provided in the embodiment of this application is introduced below in combination with application scenarios.

In some application scenarios, the electronic device 100 may receive and respond to the user's input and trigger the processing of specified data ( For example, sharing of pictures, videos, document files, location information, links, contacts, calendars, application packages, memos, etc.). The electronic device 100 may display a system sharing window or system sharing interface for the specified data, wherein the system sharing window or system sharing interface for the specified data includes a sharing object option corresponding to the device currently being called by the electronic device 100 (for example, , the electronic device 200 corresponds to the sharing object option). The electronic device 100 may receive and respond to the user's input of the option of the sharing object, and transmit specified data to the device being called through a transmission link between the electronic device 100 and the device being called. In this way, the user can share the data content that the user wants to share with the other party in a timely manner while using the electronic device 100 to communicate with the other party, thereby improving the user's experience of sharing data.

4A to 4I exemplarily illustrate an interface diagram of the electronic device 100 sharing data such as pictures to the electronic device 200 when the electronic device 100 is talking to the electronic device 200 in the embodiment of the present application.

For example, as shown in FIG. 4A , the electronic device 100 can make a voice call with the electronic device 200 and display the call interface 4010 . The call interface 4010 may include the phone number 4013 of the electronic device 200 (for example, "186XXXXXXXX"), the call duration 4014 (for example, "00:15"), and one or more call function controls, etc. The one or more call function controls include, but are not limited to, recording controls, waiting controls, add call controls, video call controls, mute controls, contact controls, dial controls, hang up controls, external call controls, and so on. The recording control can be used to trigger the electronic device 100 to record the conversation between the electronic device 100 and the electronic device 200 . The waiting control can be used to trigger the electronic device 100 to suspend the call with the electronic device 200 . The add call control can be used to trigger the electronic device 100 to add a call with other devices. The video call control can be used to trigger the electronic device 100 to switch the voice call with the electronic device 200 to a video call. During the video call, the electronic device 100 can display a video call interface. The video call The interface may include images captured by the camera of the electronic device 200 . Optionally, the video call interface may also include images captured by the camera of the electronic device 100 . The mute control can be used to trigger the electronic device 100 to stop sending voice data to the electronic device 200 .

Optionally, a status bar 4011 is displayed in an upper part of the call interface 4010. The status bar 4011 may include one or more status indicators. The one or more status indicators include mobile communication signals (also known as One or more signal strength indicators for cellular signals, Wi-Fi signal indicators, battery status indicators, time indicators, etc.

Optionally, if the contact name corresponding to the phone number of the electronic device 200 is stored on the electronic device 100, the above-mentioned call interface 4010 may also include the contact name 4012 corresponding to the phone number of the electronic device 200 (for example, "Alice") . If the electronic device 100 also stores a contact avatar corresponding to the phone number of the electronic device 200, the call interface 4010 may also include a contact avatar corresponding to the phone number of the electronic device 200 (for example, "Alice").

The electronic device 100 may receive an input from the user to exit the call interface 4010 (eg, slide upward from the bottom edge of the display screen), and in response to the input, the electronic device 100 may display a desktop 4020 as shown in FIG. 4B .

As shown in Figure 4B, the desktop 4020 displays a page on which application icons are placed. The page includes multiple application icons (for example, a weather application icon, a stock application icon, a calculator application icon, a settings application icon, and an email application icon). , music application icon, video application icon, browser application icon, map application icon 4022, gallery application icon 4023, memo application icon 4024, voice assistant application icon, etc.). Page indicators are also displayed below multiple application icons to indicate the total number of pages on the desktop 4020 and the positional relationship between the currently displayed page and other pages. For example, the desktop 4020 may include three pages, and a white dot in the page indicator may indicate that the currently displayed page is the rightmost page among the three pages. Further optionally, there are multiple tray icons (such as a dialing application icon, a messaging application icon, a contact application icon 4025, and a camera application icon) below the page indicator, and the tray icons remain displayed when the page is switched. Optionally, the above-mentioned status bar 4011 is displayed in an upper part of the desktop 4020.

Because the electronic device 100 and the electronic device 200 are talking and the electronic device 100 exits the above call interface 4010. The electronic device 100 may display a call icon 4021 on the status bar 4011. The call icon 4021 can display the call time (for example, "00:18"). Optionally, the call icon 4021 can also display the phone number of the electronic device 200 (for example, "186XXXXXXXX") and/or the electronic device. 200's phone number corresponds to the contact name (for example, "Alice"). The call icon 4021 can be used to trigger the electronic device 100 to display the above-mentioned call interface 4010. Optionally, the status bar 4011 can remain displayed in the top area of the touch screen when the display interface on the touch screen is switched. The call icon 4021 can also remain displayed in the status bar 4011 when the interface displayed on the touch screen is switched but the interface displayed on the touch screen is not the above-mentioned call interface 4010.

In some examples, the call icon 4021 may not be displayed in the status bar 4011, or may be displayed anywhere on the touch screen in the form of a floating ball. The user may also drag the call icon 4021 to adjust the call icon 4021. Display position on the touch screen.

The electronic device 100 may receive user input (eg, click) on the gallery application icon 4023, and in response to the input, the electronic device 100 may display the gallery application interface 4030 as shown in FIG. 4C.

As shown in Figure 4C, the gallery application interface 4030 may include one or more album options (for example, all photo albums 4031, video albums, camera albums, screenshot directory albums, chat application albums, Changlian application albums, etc.) . Among them, below each album option is the name of the album and the number of photos and/or videos in the album. For example, the photo album 4031 contains 2160 photos, and the video album contains 6 videos. The gallery application interface 4030 also includes a new photo album control. The new photo album control can be used to trigger the creation of a new photo album in the gallery application interface 4030.

The electronic device 100 may receive a user's operation (eg, click) on the all-photo album 4031, and in response to the operation, the electronic device 100 may display an album interface 4040 as shown in FIG. 4D.

As shown in Figure 4D, the title of the album interface 4040 may be "all photos". The album interface 4040 includes thumbnails of one or more pictures (for example, thumbnail 4041).

The electronic device 100 may receive user input (eg, click) on the thumbnail 4041, and in response to the input, the electronic device 100 may display a picture display interface 4050 as shown in FIG. 4E.

As shown in Figure 4E, the title of the picture display interface 4050 may be "Landscape". The picture display interface 4050 displays a picture 4051 and a menu 4052. Among them, the menu 4052 includes a share button 4053, a collection button, an edit button, a delete button, and a more button. The share button 4053 can be used to trigger the electronic device 100 to call the system sharing function and open the system sharing interface. The collection button can be used to trigger collection of the picture 4051 to the picture collection folder. The edit button can be used to trigger editing functions such as rotating, trimming, adding filters, blurring, etc. to the image. The delete button can be used to trigger deletion of the image 4051. The More button can be used to trigger the opening of more features related to that image 4051.

The electronic device 100 may receive user input (eg, click) on the share button 4053, and in response to the input, the electronic device 100 may display the system sharing interface 4060 as shown in FIG. 4F.

As shown in Figure 4F, the system sharing interface 4060 may include an area 4061, an area 4062, and an area 4064. in:

This area 4061 can be used to display one or more pictures or videos in the gallery, and the one or more pictures or videos can include pictures or videos selected by the user. A mark may be displayed on the selected picture, and the mark may be used to indicate that the corresponding picture is selected (that is, the picture has been selected by the user). The pictures or video images displayed in this area 4061 may be thumbnails. The original image corresponding to the picture or video picture displayed in area 4061 can be stored on the electronic device 100 . This area 4062 may be used to display device options 4063 of the electronic device 200 with which the electronic device 100 is talking. Optionally, the device option 4063 may display a contact avatar corresponding to the phone number of the electronic device 200, and the device option 4063 may display a contact name corresponding to the phone number of the electronic device 200 (for example, "Alice"). ), prompt information 4065 (for example, text prompt "on call", etc.) may also be displayed around the device option 4063. The prompt information 4065 is used to prompt that the device option 4063 is an electronic device that is talking to the electronic device 100. Device options corresponding to device 200. The area 4062 may also display nearby device options discovered by the electronic device 100. For example, after searching for nearby devices, the electronic device 100 may display the device options of the nearby devices in the area 4062 (for example, the "Alee's mobile phone" option, "HUAWEI P50" option). This area 4064 displays one or more service options (eg, mail icon, browser icon, information icon, WLAN direct icon, etc.). For the text description of the area 4064, please refer to the text description of the area 3023 in the embodiment shown in FIG. 3B, which will not be described again here.

In one example, the electronic device 100 can talk to multiple contacts at the same time, and the electronic device 100 can display options of the multiple contacts with whom the electronic device 100 is talking in the above-mentioned system sharing interface.

Optionally, the electronic device 100 can make operator calls with multiple contacts. For example, the electronic device 100 can conduct voice conference calls or video conference calls with multiple contacts simultaneously through the operator network.

For another example, the electronic device 100 may receive an incoming call from contact B through the operator network while having an operator call with contact A through the operator network. The electronic device 100 may hold a carrier call with contact A and conduct a carrier call with contact B through the carrier network. At this time, the electronic device 100 may determine that the contacts being called by the electronic device 100 include contact A and contact B.

Optionally, the electronic device 100 can make OTT calls with multiple contacts. For example, the electronic device 100 can make a voice conference call or a video conference call with multiple contacts in the OTT application through the OTT application.

For another example, the electronic device 100 may first make an OTT call with contact A in the OTT application, the electronic device 100 may hold the OTT call with contact A, and make an OTT call with contact B through the OTT application. At this time, the electronic device 100 may determine that the contacts being called by the electronic device 100 include contact A and contact B in the OTT application.

Optionally, the electronic device 100 can conduct operator calls and OTT calls with multiple contacts. For example, the electronic device 100 may receive an incoming call from contact B in the OTT application while having an operator call with contact A through the operator network. The electronic device 100 can keep the operator call with contact A and make an OTT call with contact B in the OTT application through the OTT application. At this time, the electronic device 100 may determine that the contacts being called by the electronic device 100 include contact A who reserves the call with the operator and contact B who makes the OTT call through the OTT application.

For another example, the electronic device 100 may receive an incoming call from contact A through the operator's network while making an OTT call with contact B through an OTT application. The electronic device 100 may keep the OTT call with contact B and conduct a carrier call with contact A through the carrier network. At this time, the electronic device 100 may determine that the contacts being called by the electronic device 100 include contact A who is making the operator call through the operator network and contact B who is holding the OTT call.

The electronic device 100 may receive user input (eg, click) to the device option 4063, and in response to the input, the electronic device 100 may send a data transfer request to the electronic device 200 and display a sending window 4070 as shown in FIG. 4G.

As shown in Figure 4G, the sending window 4070 may include the file name of the above picture 4051, the thumbnail 4071 of the above picture 4051, a sending prompt 4072 and a cancel control 4073. The sending prompt 4072 may be used to prompt the user that the electronic device 100 is currently requesting to send pictures to the electronic device 200 communicating with the electronic device 100 . Among them, the prompt type of the sending prompt 4072 can be a text prompt (for example, "Requesting to send 1 picture (2.4MB) to Alice, waiting for the other party to confirm receipt."), picture prompt, animated picture prompt, video prompt, etc. any one or more. The cancel control 4073 can be used to trigger the electronic device 100 to cancel sending pictures to the electronic device 200 .

As shown in FIG. 4H, after the electronic device 100 receives the confirmation information sent by the electronic device 200, the electronic device 100 may display the sending window 4080. The confirmation information is used to confirm receipt of the picture sent by the electronic device 100 . The sending window 4080 may include a thumbnail 4081 of the above picture 4051 and a sending prompt 4082. Optionally, the sending window 4080 may also include a sending progress bar 4083 and a cancellation control 4084. The sending prompt 4082 may be used to prompt the user that the electronic device 100 is currently sending pictures to the electronic device 200 that is talking to the electronic device 100 . The prompt type of the sending prompt 4082 may be any one or more of text prompts (for example, "Sending 1 picture (2.4MB) to Alice"), picture prompts, animated picture prompts, video prompts, etc. The sending progress bar 4083 can be used to indicate the progress of the electronic device 100 sending the above picture 4051 to the electronic device 200 . The cancel control 4084 can be used to trigger the electronic device 100 to stop sending the above picture 4051 to the electronic device 200 .

Optionally, when the electronic device 100 is sending specified data such as pictures to the electronic device 200, the electronic device 100 may receive the user's input (for example, click) on the above-mentioned cancel control 4084, and in response to the input, the electronic device 100 may The transmission of designated data to the electronic device 200 is stopped, and a cancellation command is sent to the electronic device 200 . After receiving the cancellation command, the electronic device 200 may delete part of the content that has been received in the specified data.

In one example, after receiving the user's input (for example, clicking) on the device option 4063, the electronic device 100 can directly send the above picture 4051 to the electronic device 200 without the need for the electronic device 200 to return confirmation information.

Optionally, as shown in FIG. 4I , the electronic device 100 may display the sending window 4090 after sending the above picture 4051 to the electronic device 200 . The sending window 4090 may include the file name of the above picture 4051, the thumbnail 4091 of the above picture 4051, a sent prompt 4092 and a recall control 4093. The sent prompt 4092 may be used to indicate that the electronic device 100 has currently sent the above picture 4051 to the electronic device 200 . The recall control 4093 may be used to receive and respond to user input, triggering the electronic device 100 to send a recall instruction to the electronic device 200 . After receiving the withdrawal instruction, the electronic device 200 may delete the above-mentioned picture 4051 sent by the electronic device 100.

In one example, the contact information of the electronic device 200 (including phone number, name, avatar, etc.) may be stored on the electronic device 100 in advance by the user.

In one example, the contact information (including phone number, name, avatar, etc.) of the electronic device 200 may be sent by the electronic device 200 to the electronic device 100 .

In one example, the contact information (including phone number, name, avatar, etc.) of the electronic device 200 may be delivered to the electronic device 100 by an intermediate device such as an operator's network device or a server.

In one example, if the electronic device 100 does not obtain the contact name corresponding to the phone number of the electronic device 200, the sending prompt 4072 shown in FIG. 4G, the sending prompt 4082 shown in FIG. 4H, and the sending prompt 4082 shown in FIG. 4I are The recipient identification prompted in the sent prompt 4092 may be the phone number of the electronic device 200 .

In one example, if the electronic device 100 obtains the contact name (for example, “Alice”) corresponding to the phone number of the electronic device 200, the sending prompt 4072 shown in FIG. 4G and the sending prompt 4082 shown in FIG. 4H are The recipient identification prompted in the sent prompt 4092 described in FIG. 4I may be the contact name of the electronic device 200 (for example, "Alice") and/or the phone number of the electronic device 200 (for example, "186XXXXXXXX").

4J to 4N exemplarily show an interface schematic diagram of the electronic device 200 receiving data such as pictures shared by the electronic device 100 when the electronic device 100 talks with the electronic device 200 in the embodiment of the present application.

For example, as shown in FIG. 4J , the electronic device 200 and the electronic device 100 are talking, and the call interface 4100 is displayed. The call interface 4100 may include the phone number 4102 of the electronic device 100 (for example, "132XXXXXXXX"), the call duration 4103 (for example, "00:22"), and one or more call function controls, etc. The one or more call function controls include, but are not limited to, recording controls, waiting controls, add call controls, video call controls, mute controls, contact controls, dial controls, hang up controls, external call controls, and so on. The recording control can be used to trigger the electronic device 200 to record the conversation between the electronic device 200 and the electronic device 100 . The waiting control can be used to trigger the electronic device 200 to suspend the call with the electronic device 100 . The add call control can be used to trigger the electronic device 200 to add a call with other devices. The video call control can be used to trigger the electronic device 200 to switch the voice call with the electronic device 100 to a video call. During the video call, the electronic device 200 can display a video call interface, and the video call interface can include the electronic device 100 Optionally, the video call interface may also include images captured by the camera of the electronic device 200 . The mute control can be used to trigger the electronic device 200 to stop sending voice data to the electronic device 100 .

Optionally, if the contact name corresponding to the phone number of the electronic device 100 is stored on the electronic device 200, the above-mentioned call interface 4100 may also include the contact name 4101 corresponding to the phone number of the electronic device 100 (for example, "Daniel") . If the electronic device 200 also stores a contact avatar corresponding to the phone number of the electronic device 100, the call interface 4100 may also include a contact avatar corresponding to the phone number of the electronic device 100 (for example, "Daniel").

As shown in FIG. 4K , after the electronic device 200 receives the data transmission request sent by the electronic device 100 , the receiving window 4110 may be displayed. The data transfer request may include information related to the data to be shared by the electronic device 100 to the electronic device 200 (for example, including thumbnails and/or data sizes and/or names of picture files, etc.). The receiving window 4110 may include a thumbnail 4111 of a picture that the electronic device 100 wants to share with the electronic device 200 , a receiving prompt 4112 , a reject control 4113 and a receiving control 4114 . The receiving prompt 4112 may be used to prompt the user's electronic device 100 to request sharing the picture to the electronic device 200 . Among them, the prompt type of the receiving prompt 4112 can be any of text prompts (for example, "Daniel wants to share a picture (2.4MB) with you, do you want to accept it?"), picture prompts, animated picture prompts, video prompts, etc. Kind or variety. The rejection control 4113 can be used to trigger the electronic device 200 to send rejection information to the electronic device 100. The rejection The information may be used to instruct the electronic device 100 to cancel sharing the picture to the electronic device 200 . The receiving control 4114 can be used to trigger the electronic device 200 to send confirmation information to the electronic device 100 , and the confirmation information is used to instruct the electronic device 100 to confirm sending the picture to the electronic device 200 .

The electronic device 200 may receive user input (eg, click) to the receiving control 4114, in response to the input, the electronic device 200 may send confirmation information to the electronic device 100, and after sending the confirmation information, the receiving electronic device 100 sends picture of.

As shown in FIG. 4L, during the process of the electronic device 200 receiving the picture sent by the electronic device 100, the electronic device 200 may display a receiving window 4120. The receiving window 4120 may include a thumbnail 4121 of the picture being shared by the electronic device 100 to the electronic device 200 and a receiving prompt 4122. Optionally, the receiving window 4120 may also include a receiving progress bar 4123 and a cancellation control 4124. The receiving prompt 4122 may be used to prompt the user that the electronic device 200 is currently receiving pictures sent by the electronic device 100 . The prompt type of the receiving prompt 4122 can be any one of text prompts (for example, "receiving 1 picture (2.4MB) shared by Daniel with you"), picture prompts, animated picture prompts, video prompts, etc., or Various. The reception progress bar 4123 may be used to indicate the progress of the electronic device 200 receiving the picture sent by the electronic device 100 . The cancel control 4124 can be used to trigger the electronic device 200 to stop receiving pictures sent by the electronic device 200 .

As shown in FIG. 4M, after the electronic device 200 receives the picture sent by the electronic device 100, the electronic device 200 may display a receiving window 4130. The receiving window 4130 may include a thumbnail 4131 of a picture that the electronic device 100 has shared with the electronic device 200, a receiving prompt 4132, an opening control 4133, and a storage control 4134. The reception prompt 4132 may be used to prompt the user that the current electronic device 200 has received the picture sent by the electronic device 100 . The prompt type of the receiving prompt 4132 can be any one or more of text prompts (for example, "I have received a picture sent to you by Daniel"), picture prompts, animated picture prompts, video prompts, etc. The opening control 4133 can be used to trigger the electronic device 200 to display a display interface including pictures sent by the electronic device 100 . The storage control 4134 can be used to trigger the electronic device 200 to save the picture sent by the electronic device 100 in a designated storage path local to the electronic device 200 .

Electronic device 200 may receive user input (eg, click) to storage control 4134, and in response to the input, electronic device 200 may display storage interface 4140 as shown in FIG. 4N.

As shown in Figure 4N, the storage interface 4140 may include one or more storage path options, a return to previous page control 4141, and so on. Among them, since the electronic device 100 shares pictures with the electronic device 200, the one or more storage path options may include one or more album options (for example, the "all photo album" option 4142, the "camera album" option, "Screenshot directory album" option, "Chat application album" option, "Changan application album" option, "Other albums" option, etc.). Optionally, the storage interface 4140 may also include a new control 4143, which may be used to trigger the electronic device 200 to add a new photo album option in the storage interface 4140.

The electronic device 200 may receive user input (eg, click) to the "all photo albums" option 4142, and in response to the input, the electronic device 200 may store the pictures shared by the electronic device 100 to the all photo albums corresponding to under the storage path. After the electronic device 200 stores the pictures shared by the electronic device 100 to the storage paths corresponding to all photo albums, when the electronic device 200 opens the album interface of all photo albums in the gallery application, the album interface of all photo albums The thumbnail of the picture shared by the electronic device 100 to the electronic device 200 may be included.

In one example, if the electronic device 200 does not obtain the contact name corresponding to the phone number of the electronic device 100, the receiving prompt 4112 shown in FIG. 4K, the receiving prompt 4122 shown in FIG. 4L, and the receiving prompt 4122 shown in FIG. 4M are The sender identification prompted in the reception prompt 4132 may be the phone number of the electronic device 100 .

In one example, if the electronic device 200 stores a contact name (for example, “Daniel”) corresponding to the phone number of the electronic device 100, the above-mentioned reception prompt 4112 shown in FIG. 4K and the reception prompt 4122 shown in FIG. 4L The sender identification prompted in the reception prompt 4132 described in FIG. 4M may be the contact name of the electronic device 100 (for example, "Daniel") and/or the phone number of the electronic device 100 (for example, "132XXXXXXXX").

In one example, as shown in Figure 4O, if the electronic device 100 and the electronic device 200 are talking, but the electronic device 100 does not obtain the contact name corresponding to the phone number of the electronic device 200, the electronic device 100 displays the system When sharing the interface 4060, the phone number of the electronic device 200 (for example, 186XXXXXXXX) can be directly displayed around the device option 4063 in the system sharing interface 4060.

In one example, as shown in FIG. 4O, if the electronic device 100 and the electronic device 200 are talking, and the electronic device 100 obtains the contact name corresponding to the phone number of the electronic device 200, the electronic device 100 displays the system sharing message. When the interface 4060 is displayed, the phone number (for example, "186XXXXXXXX") and/or the contact name (for example, "Alice") of the electronic device 200 may be displayed around the device option 4063 in the system sharing interface 4060.

The failure of the electronic device 100 to obtain the contact name corresponding to the phone number of the electronic device 200 includes: the electronic device 100 has not obtained the contact name from the local electronic device 100, and/or the electronic device 200, and/or the operator's network equipment and/or server. The contact name corresponding to the phone number of the electronic device 200 is obtained.

Optionally, the vicinity of the device option 4063 in the system sharing interface 4060 (for example, the upper left corner of the device option 4063) can also be To display the call mark 4066, the call mark 4066 can be used to prompt that the device option 4063 is a device option corresponding to the electronic device 200 with which the electronic device 100 is talking.

In the embodiment of the present application, the electronic device 100 and the electronic device 200 are in the process of talking. The electronic device 100 is not limited to sharing picture data to the electronic device 200, but can also share other types of data, such as audio, video, documents (such as word, excel). , PPT, PDF and other formats of document files), article links, video playback links, web page opening links, application installation packages or application download links, contact information, location information, text, memos and other types of data. When the types of data shared by the electronic device 100 are different, after receiving the data, the electronic device 200 can receive and respond to the user's input and perform operations corresponding to the types of data.

5A to 5E exemplarily show interface diagrams of applications and other data shared by the electronic device 100 to the electronic device 100 when the electronic device 100 communicates with the electronic device 200 in the embodiment of the present application.

For example, as shown in FIG. 5A , the electronic device 100 and the electronic device 200 are talking and the desktop 4020 is displayed. For the text description of the desktop 4020, reference may be made to the text description in the embodiment shown in FIG. 4B, which will not be described again here.

The electronic device 100 may receive user input (eg, click) on the map application icon 4022 in the desktop 4020, and in response to the input, the electronic device 100 may display the shortcut menu 5010 shown in FIG. 5B.

As shown in Figure 5B, the shortcut menu 5010 may include a sharing control 5011 and an uninstalling control 5012. The sharing control 5011 can be used to trigger the electronic device 100 to call the system sharing function and display the system sharing window to share the map application with other devices or contacts. The uninstall control 5012 can be used to trigger the electronic device 100 to uninstall the map application.

The electronic device 100 may receive user input (eg, click) to the sharing control 5011, and in response to the input, the electronic device 100 may display the system sharing window 5020 as shown in FIG. 5C.

As shown in Figure 5C, the system sharing window 5020 may include a map application option 5021, an area 5022, and an area 5024. The map application option 5021 may display the name of the map application (for example, "map"), data size (for example, "40.82MB"), file type (for example, "base.apk"), and so on. This area 5022 may be used to display device options 5023 of the electronic device 200 with which the electronic device 100 is talking. The device option 5023 may display a contact avatar corresponding to the phone number of the electronic device 200 , and the device option 5023 may display a contact name (for example, "Alice") or phone number corresponding to the phone number of the electronic device 200 around the device option 5023 . , the device option 5023 can also be displayed with prompt information 5025 (for example, a text prompt "on call", etc.), the prompt information 5025 is used to prompt that the device option 5023 is an electronic device that is talking to the electronic device 100 200 corresponding device options. The area 5022 may also display options for nearby devices discovered by the electronic device 100. For example, after searching for nearby devices, the electronic device 100 may display device options for nearby devices in the area 5022 (for example, the "Alee's cell phone" option, "HUAWEI P50" option). For the text description of the area 5024, please refer to the text description of the area 3023 in the embodiment shown in FIG. 3B, which will not be described again here.

The electronic device 100 may receive user input (eg, click) to the device option 5023, and in response to the input, the electronic device 100 may send a data transfer request to the electronic device 200 and display a sending window 5030 as shown in FIG. 5D.

As shown in Figure 5D, the sending window 5030 may include a map application icon 5031 as well as the data size (for example, "40.82MB") and file type (for example, "base.apk") of the map application, a sending prompt 5032 and a cancel control. 5033 and so on. The sending prompt 5032 may be used to prompt the user that the electronic device 100 is currently requesting to send a map application to the electronic device 200 communicating with the electronic device 100 . Among them, the prompt type of the sending prompt 5032 can be any of text prompts (for example, "Requesting to send map application (40.82MB) to Alice, waiting for the other party to confirm receipt"), picture prompts, animated picture prompts, video prompts, etc. Kind or variety. The cancellation control 5033 may be used to trigger the electronic device 100 to cancel sending the installation package of the map application to the electronic device 200 .

As shown in FIG. 5E , after the electronic device 100 receives the confirmation information sent by the electronic device 200 , the electronic device 100 may display the sending window 5040 . The confirmation information is used to confirm receipt of the installation package of the map application sent by the electronic device 100 . The sending window 5040 may include a map application icon 5041 as well as the map application's data size (for example, "40.82MB") and file type (for example, "base.apk"), a sending prompt 5042, and so on. The sending prompt 5042 may be used to prompt the user that the electronic device 100 is currently sending the installation package of the map application to the electronic device 200 communicating with the electronic device 100 . Optionally, the sending window 5040 may also include a sending progress bar 5043 and a cancellation control 5044. The prompt type of the sending prompt 5042 may be any one or more of a text prompt (for example, "Sending a map application (40.82MB) to Alice"), a picture prompt, an animation prompt, a video prompt, and so on. The sending progress bar 5043 may be used to indicate the progress of the electronic device 100 sending the installation package of the map application to the electronic device 200 . The cancel control 5044 can be used to trigger the electronic device 100 to stop sending the installation package of the map application to the electronic device 200 .

In one example, after receiving the user's input (for example, clicking) on the device option 5023 shown in FIG. 5C , the electronic device 100 can directly send the above map to the electronic device 200 without the need for the electronic device 200 to return confirmation information. Application installation package.

Optionally, after sending the installation package of the map application to the electronic device 200, the electronic device 100 may receive and respond to the user's input. Enter, and send a withdrawal instruction of the installation package of the map application to the electronic device 200. After receiving the withdrawal instruction, the electronic device 200 may delete the installation package of the map application that has been sent by the electronic device 100 .

In one example, if the electronic device 100 does not obtain the contact name corresponding to the phone number of the electronic device 200, the recipient identification prompted in the above-mentioned sending prompt 5032 shown in Figure 5D and the sending prompt 5042 shown in Figure 5E It may be the phone number of the electronic device 200.

In one example, if the electronic device 100 stores the contact name (for example, “Alice”) corresponding to the phone number of the electronic device 200, the sending prompt 5032 shown in FIG. 5D and the sending prompt 5042 shown in FIG. 5E are The recipient identification prompted in may be the contact name of the electronic device 200 (for example, "Alice") and/or the phone number of the electronic device 200 (for example, "186XXXXXXXX").

5F to 5I exemplarily illustrate the interface diagram of the electronic device 200 receiving application and other data shared by the electronic device 100 when the electronic device 200 talks with the electronic device 100 in the embodiment of the present application.

For example, as shown in FIG. 5F , the electronic device 200 and the electronic device 100 are talking, and the call interface 5050 is displayed. The call interface 5050 may include the phone number 5052 of the electronic device 100 (for example, "132XXXXXXXX"), the call duration 5053 (for example, "00:21"), and one or more call function controls, etc. Optionally, if the contact name corresponding to the phone number of the electronic device 100 is stored on the electronic device 200, the call interface 5050 may also include the contact name 5051 corresponding to the phone number of the electronic device 100 (for example, "Daniel") . If the electronic device 200 also stores a contact avatar corresponding to the phone number of the electronic device 100, the call interface 5050 may also include a contact avatar corresponding to the phone number of the electronic device 100 (for example, "Daniel"). For the text description of the one or more call function controls, please refer to the text description of the call function control in the embodiment shown in FIG. 4J , which will not be described again here.

As shown in FIG. 5G, after the electronic device 200 receives the data transmission request sent by the electronic device 100, the receiving window 5060 may be displayed. Wherein, the data transmission request may include relevant information of the map application to be shared by the electronic device 100 to the electronic device 200. The relevant information of the map application may include the icon of the map application, the name of the map application (for example, "map application"), Data size (e.g., 40.82MB), file type (e.g., base.apk), etc.). The receiving window 5060 may include information related to the map application that the electronic device 100 wants to share with the electronic device 200 (for example, map application icon 5061, name of the map application, data size, file type, etc.), receiving prompt 5062, rejection Control 5063 and receive control 5064, and so on. The receiving prompt 5062 may be used to prompt the user's electronic device 100 to request sharing of the map application to the electronic device 200 . Among them, the prompt type of the receiving prompt 5062 can be any of text prompts (for example, "Daniel wants to share the map application (40.82MB) with you, do you want to accept it?"), picture prompts, animated picture prompts, video prompts, etc. or more. The rejection control 5063 can be used to trigger the electronic device 200 to send rejection information to the electronic device 100 , and the rejection information can be used to instruct the electronic device 100 to cancel sharing the map application to the electronic device 200 . The receiving control 5064 can be used to trigger the electronic device 200 to send confirmation information to the electronic device 100 . The confirmation information is used to instruct the electronic device 100 to confirm sending the installation package of the map application to the electronic device 200 .

The electronic device 200 may receive user input (eg, click) to the receiving control 5064, in response to the input, the electronic device 200 may send confirmation information to the electronic device 100, and after sending the confirmation information, the receiving electronic device 100 sends The installation package of the map application.

As shown in FIG. 5H , during the process of the electronic device 200 receiving the installation package of the map application sent by the electronic device 100 , the electronic device 200 may display a receiving window 5070 . The receiving window 5070 may include information related to the map application (for example, map application icon 5071, name of the map application, data size, file type, etc.) and a receiving prompt 5072. Optionally, the receiving window 5070 may also include a receiving progress bar 5073 and a cancellation control 5074. The receiving prompt 5072 may be used to prompt the user that the electronic device 200 is currently receiving the installation package of the map application sent by the electronic device 100 . The prompt type of the receiving prompt 5072 can be any one or more of text prompts (for example, "receiving the map application (40.82MB) sent to you by Daniel"), picture prompts, animated picture prompts, video prompts, etc. kind. The reception progress bar 5073 may be used to indicate the progress of the electronic device 200 receiving the installation package of the map application sent by the electronic device 100 . The cancel control 5074 can be used to trigger the electronic device 200 to stop receiving the installation package of the map application sent by the electronic device 200 .

As shown in FIG. 5I , after the electronic device 200 receives the installation package of the map application sent by the electronic device 100 , the electronic device 200 may display a receiving window 5080 . The receiving window 5080 may include information related to the map application (for example, map application icon 5081, name of the map application, data size, file type, etc.), and one or more functional controls. The one or more functional controls include the immediate installation control 5082, the re-download control 5083, the next installation control 5084, and so on. The immediate installation control 5082 may be used to trigger the electronic device 200 to install the map application based on the installation package of the map application sent by the electronic device 100 . The re-download control 5083 can be used to trigger the electronic device 200 to switch to display the interface of the application market application and re-download the map application from the application market server. The re-install control 5084 can be used to trigger the electronic device 200 to save the installation package of the map application sent by the electronic device 100, and the next time the user manually triggers the electronic device 200 to install the map application based on the installation package of the map application.

In one example, if the electronic device 200 does not obtain the contact name corresponding to the phone number of the electronic device 100, the sender identification prompted in the above reception prompt 5062 shown in Figure 5G and the reception prompt 5072 shown in Figure 5H It may be the phone number of the electronic device 100 .

In one example, if the electronic device 200 stores the contact name (for example, “Daniel”) corresponding to the phone number of the electronic device 100, the above-mentioned reception prompt 5062 shown in FIG. 5G and the reception prompt 5072 shown in FIG. 5H The sender identification prompted in may be the contact name of the electronic device 100 (for example, "Daniel") and/or the phone number of the electronic device 100 (for example, "132XXXXXXXX").

5J to 5P exemplarily illustrate interface diagrams of contact information and other data shared by the electronic device 100 to the electronic device 200 when the electronic device 100 talks to the electronic device 200 in the embodiment of the present application.

For example, as shown in FIG. 5J , the electronic device 100 and the electronic device 200 are talking, and the contact application interface 5090 is displayed. The contact interface 5090 includes options for one or more contacts (eg, "Alice" options, "Anna" options, "Bob" options 5091, "Britney" options, etc.).

Electronic device 100 may receive user input (eg, click) to the "Bob" option 5091, and in response to the input, electronic device 100 may display contact information interface 5100 as shown in FIG. 5K.

As shown in Figure 5K, the contact information interface 5100 may include the name, avatar, phone number (for example, "180XXXXXXXX") of the contact "Bob", a voice call control 5101, a video call control 5102, a text message control 5103, and a collection control. 5104, edit control 5105, more options control 5106, and so on. The voice call control 5101 can be used to trigger the electronic device 100 to make a voice call to the electronic device of the contact "Bob". The video call control 5102 can be used to trigger the electronic device 100 to make a video call to the electronic device of the contact "Bob". The text message control 5103 can be used to trigger the electronic device 100 to send a text message to the electronic device of the contact "Bob". The collection control 5104 can be used to trigger the electronic device 100 to collect the contact information of the contact "Bob" into favorites. The editing control 5105 can be used to trigger the electronic device 100 to modify the contact information of the contact "Bob". The more options control 5106 can be used to trigger the electronic device 100 to display more contact functions.

Electronic device 200 may receive user input (eg, click) to the more options control 5106, and in response to the input, electronic device 100 may display menu window 5107 as shown in FIG. 5L.

As shown in Figure 5L, the menu window 5107 may include a share contact option 5108, a blacklist option, a create shortcut option, a delete contact option, and so on. The share contact option 5108 can be used to trigger the electronic device 100 to call the system sharing function and display the system sharing window to share the contact information of the contact "Bob" with other contacts or other devices.

Electronic device 100 receives user input (eg, click) to the share contact option 5108, and in response to the input, electronic device 100 may display menu window 5110 as described in FIG. 5M.

As shown in Figure 5M, the menu window 5110 may include one or more sharing mode options, wherein the one or more sharing mode options include a QR code option 5111, a vCard option 5112, a text option 5113, and so on. The QR code option 5111 can be used to trigger the electronic device 100 to share the contact information of the contact "Bob" in the form of a QR code to other contacts or other devices. The vCard option 5112 can be used to trigger the electronic device 100 to share the contact information of the contact "Bob" in the form of a vCard to other contacts or other devices. This text option 5113 can be used to trigger the electronic device 100 to share the contact information of the contact "Bob" in text form to other contacts or other devices.

The electronic device 100 may receive user input (eg, click) on the QR code option 5111, and in response to the input, the electronic device 100 may display the system sharing window 5120 as shown in FIG. 5N.

As shown in Figure 5N, the system sharing window 5120 may include a contact information option 5121, an area 5122, and an area 5124. Among them, the contact information option 5121 can display a QR code or a thumbnail of the QR code generated based on the contact information of the contact "Bob", as well as the data size (for example, 21.79KB), name ( For example, "Bob's contact information.jpg") and so on. This area 5122 may be used to display device options 5123 of the electronic device 200 with which the electronic device 100 is talking. The device option 5123 may display a contact avatar corresponding to the phone number of the electronic device 200 , and the device option 5123 may display a contact name (for example, "Alice") or phone number corresponding to the phone number of the electronic device 200 around the device option 5123 . , prompt information 5125 (for example, text prompt "on call", etc.) may also be displayed around the device option 5123. The prompt information 5125 is used to prompt that the device option 5123 is an electronic device that is talking to the electronic device 100. 200 corresponding device options. The area 5122 may also display nearby device options discovered by the electronic device 100. For example, after searching for nearby devices, the electronic device 100 may display the device options of the nearby devices in the area 5122 (for example, the "Alee's mobile phone" option, "HUAWEI P50" option). For the text description of the area 5124, please refer to the text description of the area 3023 in the embodiment shown in FIG. 3B, which will not be described again here.

The electronic device 100 may receive user input (eg, click) to the device option 5123, and in response to the input, the electronic device 100 may send a data transfer request to the electronic device 200 and display a sending window 5130 as shown in FIG. 5O.

As shown in Figure 5O, the sending window 5130 may include a QR code or a thumbnail 5131 of the QR code generated based on the contact information of the contact "Bob" and the data size of the QR code (for example, "21.79KB" ), send prompt 5132 and cancel control 5133 and so on. Among them, the sending prompt 5132 can be used to prompt the user that the electronic device 100 is currently requesting to send a message to the electronic device 200 that is talking to the electronic device 100. Contact information for contact "Bob". Among them, the prompt type of the sending prompt 5132 can be any one of text prompts (for example, "Requesting to send Bob's contact information to Alice, waiting for the other party to confirm receipt"), picture prompts, animated picture prompts, video prompts, etc., or Various. The cancel control 5033 can be used to trigger the electronic device 100 to cancel sending the contact information of the contact "Bob" of the map application to the electronic device 200 .

As shown in FIG. 5P, after the electronic device 100 receives the confirmation information sent by the electronic device 200, the electronic device 100 may display the sending window 5140. The confirmation information is used to confirm receipt of the contact information of the contact “Bob” sent by the electronic device 100 . The sending window 5140 may include a QR code or a thumbnail 5141 of the QR code generated based on the contact information of the contact "Bob", as well as the data size of the QR code (for example, "21.79KB") and a sending prompt 5142 etc. The sending prompt 5142 may be used to prompt the user that the electronic device 100 is currently sending the contact information of the contact "Bob" to the electronic device 200 that is talking to the electronic device 100 . Optionally, the sending window 5140 may also include a sending progress bar 5143 and a cancellation control 5144. The prompt type of the sending prompt 5142 may be any one or more of a text prompt (for example, "Sending Bob's contact information to Alice"), a picture prompt, an animation prompt, a video prompt, and so on. The sending progress bar 5143 may be used to represent the progress of the electronic device 100 sending the contact information of the contact “Bob” to the electronic device 200 . The cancel control 5144 can be used to trigger the electronic device 100 to stop sending the contact information of the contact "Bob" to the electronic device 200 .

In one example, after receiving the user's input (for example, clicking) on the device option 5123 shown in FIG. 5N , the electronic device 100 can directly send the contact to the electronic device 200 without the need for the electronic device 200 to return confirmation information. Contact information for "Bob".

Optionally, after the electronic device 100 sends the contact information of the contact "Bob" to the electronic device 200, it may receive and respond to the user's input and send the withdrawal of the contact information of the contact "Bob" to the electronic device 200. instruct. After receiving the withdrawal instruction, the electronic device 200 may delete the contact information of the contact "Bob" that has been received.

In one example, if the electronic device 100 does not obtain the contact name corresponding to the phone number of the electronic device 200, the recipient identification prompted in the sending prompt 5132 shown in FIG. 5O and the sending prompt 5142 shown in FIG. 5P It may be the phone number of the electronic device 200.

In one example, if the electronic device 100 stores the contact name (for example, “Alice”) corresponding to the phone number of the electronic device 200, the sending prompt 5132 shown in FIG. 5O and the sending prompt 5142 shown in FIG. 5P are The recipient identification prompted in may be the contact name of the electronic device 200 (for example, "Alice") and/or the phone number of the electronic device 200 (for example, "186XXXXXXXX").

5Q to 5S exemplarily illustrate the interface diagram of the electronic device 200 receiving data such as contact information shared by the electronic device 100 when the electronic device 100 and the electronic device 200 are talking in the embodiment of the present application.

For example, as shown in FIG. 5Q , the electronic device 200 and the electronic device 100 are talking, and the call interface 5150 is displayed. The call interface 5150 may include the phone number 5152 of the electronic device 100 (for example, "132XXXXXXXX"), the call duration 5153 (for example, "00:21"), and one or more call function controls, etc. Optionally, if the contact name corresponding to the phone number of the electronic device 100 is stored on the electronic device 200, the call interface 5150 may also include the contact name 5151 corresponding to the phone number of the electronic device 100 (for example, "Daniel") . If the electronic device 200 also stores a contact avatar corresponding to the phone number of the electronic device 100, the call interface 5150 may also include a contact avatar corresponding to the phone number of the electronic device 100 (for example, "Daniel"). For the text description of the one or more call function controls, please refer to the text description of the call function control in the embodiment shown in FIG. 4J , which will not be described again here.

After receiving the data transmission request sent by the electronic device 100, the electronic device 200 may display the receiving window 5160. The data transmission request may include the name of the above-mentioned QR code (for example, "Bob's contact information (QR code)"), the data size (for example, "21.79KB"), and so on. The receiving window 5160 may include the name of the above-mentioned QR code, data size, receiving prompt 5162, reject control 5163, receiving control 5164, and so on. The reception prompt 5162 may be used to prompt the user electronic device 100 to request sharing the contact information of contact “Bob” to the electronic device 200 . The prompt type of the receiving prompt 5162 can be any one or more of text prompts (for example, "Daniel wants to share Bob's contact information with you, do you want to accept it?"), picture prompts, animated picture prompts, video prompts, etc. kind. The rejection control 5163 can be used to trigger the electronic device 200 to send rejection information to the electronic device 100 , and the rejection information can be used to instruct the electronic device 100 to cancel sharing the contact information of the contact "Bob" with the electronic device 200 . The receiving control 5164 can be used to trigger the electronic device 200 to send confirmation information to the electronic device 100. The confirmation information is used to instruct the electronic device 100 to confirm sending the contact information of the contact "Bob" to the electronic device 200.

The electronic device 200 may receive user input (eg, click) to the receiving control 5164, in response to the input, the electronic device 200 may send confirmation information to the electronic device 100, and after sending the confirmation information, the receiving electronic device 100 sends Contact information for "Bob".

As shown in FIG. 5R, during the process of the electronic device 200 receiving the contact information of the contact "Bob" sent by the electronic device 100, the electronic device 200 may display the receiving window 5170. The receive window 5170 may include a receive prompt 5172. Optionally, the receiving window 5170 may also include a receiving progress bar 5173 and a cancellation control 5174. The receiving prompt 5172 may be used to prompt the user that the electronic device 200 is currently receiving the contact information of the contact "Bob" sent by the electronic device 100 . Among them, the prompt type of the receiving prompt 5172 can be any of text prompts (for example, "receiving Bob's contact information sent to you by Daniel"), picture prompts, animated picture prompts, video prompts, etc. or more. The receiving progress bar 5173 may be used to represent the progress of the electronic device 200 receiving the contact information of the contact “Bob” sent by the electronic device 100 . The cancel control 5174 can be used to trigger the electronic device 200 to stop receiving the contact information of the contact "Bob" sent by the electronic device 200 .

As shown in FIG. 5S, after the electronic device 200 receives the contact information of the contact "Bob" sent by the electronic device 100, the electronic device 200 may display the receiving window 5180. The receiving window 5180 may include a QR code corresponding to the contact information of the contact "Bob" and one or more functional controls. Among them, the one or more functional controls include the recognition QR code control 5182, the save to gallery control 5183, and so on. The recognition QR code control 5182 can be used to trigger the electronic device 200 to recognize the contact information of the contact "Bob" in the QR code. The save to gallery control 5183 can be used to trigger the electronic device 200 to save the above QR code to the gallery.

In one example, if the electronic device 200 does not obtain the contact name corresponding to the phone number of the electronic device 100, the sender identification prompted in the above reception prompt 5162 shown in Figure 5R and the reception prompt 5172 shown in Figure 5S It may be the phone number of the electronic device 100 .

In one example, if the electronic device 200 stores the contact name (for example, "Daniel") corresponding to the phone number of the electronic device 100, the above-mentioned reception prompt 5162 shown in Figure 5R and the reception prompt 5172 shown in Figure 5S The sender identification prompted in may be the contact name of the electronic device 100 (for example, "Daniel") and/or the phone number of the electronic device 100 (for example, "132XXXXXXXX").

5T to 5W exemplarily illustrate interface diagrams of text and other data shared by the electronic device 100 to the electronic device 200 when the electronic device 100 communicates with the electronic device 200 in the embodiment of the present application.

For example, as shown in FIG. 5T , the electronic device 100 and the electronic device 200 are talking, and the document editing interface 5190 is displayed. The document editing interface 5190 may include a text editing area 5191. The text editing area 5191 may display text content (for example, "When you go to the zoo, bring your membership card").

The electronic device 100 may receive the user's selection input (for example, a long press operation) of the text content in the text editing area 5191, and in response to the input, the electronic device 100 may display a menu bar 5192 as shown in FIG. 5U.

As shown in Figure 5U, the menu bar 5192 may include a share control 5193, a cut control, a copy control, a paste control, and so on. The sharing control 5193 can trigger sharing of text content selected by the user.

The electronic device 100 may receive user input (eg, click) to the sharing control 5193, and in response to the input, the electronic device 100 may display the system sharing window 5200 as shown in FIG. 5V.

As shown in Figure 5V, the system sharing window 5200 may include text options 5201, area 5202, and area 5204. Among them, the text option 5201 can display the name, data size, etc. of the text content selected by the user. This area 5202 may be used to display device options 5203 of the electronic device 200 with which the electronic device 100 is talking. Prompt information 5205 may also be displayed around the device option 5023 (for example, a text prompt "on call", etc.). For the text description of the area 5202, please refer to the text description of the area 5202 in the embodiment shown in FIG. 5C. For the text description of the area 5024, please refer to the text description of the area 3023 in the embodiment shown in FIG. 3B. This will not be described again.

The electronic device 100 may receive user input (eg, click) to the device option 5203, and in response to the input, the electronic device 100 may send a data transfer request to the electronic device 200 and display a sending window 5210 as shown in FIG. 5W.

As shown in Figure 5W, the sending window 5210 can include the name 5211 of the text content selected by the user, the sending prompt 5212, the cancel control 5213, and so on. The sending prompt 5212 may be used to prompt the user that the electronic device 100 is currently requesting to send text to the electronic device 200 that is talking to the electronic device 100 . The prompt type of the sending prompt 5212 may be any one or more of text prompts (for example, "Requesting to send text to Alice, waiting for the other party to confirm receipt"), picture prompts, animated picture prompts, video prompts, etc. The cancel control 5213 can be used to trigger the electronic device 100 to cancel sending text to the electronic device 200 .

Optionally, after sending the text to the electronic device 200, the electronic device 100 may receive and respond to the user's input and send a withdrawal instruction for the text to the electronic device 200. After receiving the withdrawal instruction, the electronic device 200 may delete the text sent by the electronic device 100 .

5X to 5Y exemplarily illustrate an interface diagram of the electronic device 200 receiving text and other data shared by the electronic device 100 when the electronic device 100 talks to the electronic device 200 in the embodiment of the present application.

Exemplarily, as shown in Figure 5X, the electronic device 200 and the electronic device 100 are talking, and the call interface 5150 is displayed. For the text description of the call interface 5150, please refer to the aforementioned embodiment shown in Figure 5Q, which will not be described again here. .

After the electronic device 200 receives the data transmission request sent by the electronic device 100, the receiving window 5220 may be displayed. Among them, the data transfer request may include the name of the text, etc. The receiving window 5220 may include a text icon, a receiving prompt 5222, a reject control 5223, a receiving control 5224, and so on. The receiving prompt 5222 may be used to prompt the user's electronic device 100 to request sharing text to the electronic device 200 . The prompt type of the receiving prompt 5222 can be any one or more of text prompts (for example, "Daniel wants to share a text with you, do you want to accept it?"), picture prompts, animated picture prompts, video prompts, etc. The reject control 5223 can be used to trigger the electronic device 200 to electronically The device 100 sends a rejection message, which may be used to instruct the electronic device 100 to cancel sharing the text to the electronic device 200 . The receiving control 5224 can be used to trigger the electronic device 200 to send confirmation information to the electronic device 100 , and the confirmation information is used to instruct the electronic device 100 to confirm sending the text to the electronic device 200 .

The electronic device 200 may receive user input (eg, click) to the receiving control 5224, in response to the input, the electronic device 200 may send confirmation information to the electronic device 100, and after sending the confirmation information, the receiving electronic device 100 sends text.

As shown in FIG. 5Y, after the electronic device 200 has received the text sent by the electronic device 100, the electronic device 200 may display a receiving window 5230. The receiving window 5230 may include part or all of the text content 5231 and one or more functional controls. The one or more functional controls include a copy to clipboard control 5232, a save to memo control 5233, a delete control 5234, and so on. The copy to clipboard control 5232 can be used to trigger the electronic device 200 to save the content in the text to the clipboard. The save to memo control 5233 can be used to trigger the electronic device 200 to save the content in the text to the memo. The delete control 5234 can be used to trigger the electronic device 200 to delete the text.

In some application scenarios, the electronic device 100 may receive and respond to the user's input during a call (voice call, video call, etc.) with other devices (eg, the electronic device 200), and perform the specified application in an application. The interface triggers the display of the sharing menu that comes with the specified application, and adds to the in-application sharing menu a sharing object option corresponding to the device currently talking to the electronic device 100 (for example, the sharing object option corresponding to the electronic device 200). The electronic device 100 may receive and respond to the user's input of the option of the sharing object, and transmit specified data to the device being called through a transmission link between the electronic device 100 and the device being called. In this way, when the user is using the electronic device 100 to communicate with the other party, the other party can be displayed in the sharing menu of the designated application, and the data content selected by the user in the designated application can be shared with the other party in a timely manner, thereby improving the efficiency of the conversation. Improve the user experience of sharing data.

6A to 6D exemplarily illustrate an interface diagram of the electronic device 100 sharing data such as links with the electronic device 200 when the electronic device 100 is talking to the electronic device 200 in the embodiment of the present application.

For example, as shown in FIG. 6A , the electronic device 100 may be talking to the electronic device 200 and display the news information application interface 6010. The news information application interface 6010 may include the title of the news article (for example, "Golf boy Alee won gold in his debut"), the content of the news article (for example, "Yesterday, golf boy Alee made his debut in the golf tournament, winning four rounds of gold"). The total score of 267 won the gold medal."), the name of the publisher of the news article (for example, "Morning News") and avatar, more controls 6013. A status bar 6011 may be displayed on the top of the news information application interface 6010. For the text description of the status bar 6011, please refer to the text description of the status bar in the previous embodiment, which will not be described again here. Since the electronic device 100 may be talking to the electronic device 200, the electronic device 100 may display the call time (for example, "00:18") on the call icon 6012 in the status bar 6011. Optionally, the call icon 6012 The telephone number of the electronic device 200 (for example, "186XXXXXXXX") and/or the contact name corresponding to the telephone number of the electronic device 200 (for example, "Alice") may also be displayed. The call icon 6012 can be used to trigger the electronic device 100 to display a call interface for talking to the electronic device 200 .

The electronic device 100 may receive user input (eg, click) to the more control 6013, and in response to the input, the electronic device 100 may display a share menu 6020 as shown in FIG. 6B.

As shown in FIG. 6B , the sharing menu 6020 may include one or more sharing service options. The one or more sharing service options may include device options 6021 corresponding to the electronic device 200 that the electronic device 100 is talking to, sharing options within the news information application (for example, private message options and forwarding options, etc.) and/ Or other application sharing options (for example, friend circle options, chat application options, welink application options, etc.), and system sharing options 6022. The sharing menu 6020 may also include other functional controls (for example, collection controls, link copy controls, etc.). The system sharing option 6022 can be used to trigger the electronic device 100 to call the system sharing function and display the system sharing interface to share the news article. The text description of the system sharing interface for sharing the news article can refer to the sharing shown in Figure 5C above. The system sharing interface of the map application installation package will not be described in detail here. The contact name corresponding to the phone number of the electronic device 200 (for example, "Alice") and/or the phone number of the electronic device 200 may be displayed around the device option 6021, and a prompt message 6023 may also be displayed around the device option 6021. (For example, a text prompt "on call", etc.), the prompt information 6023 is used to prompt that the device option 6021 is a device option corresponding to the electronic device 200 with which the electronic device 100 is talking. Optionally, a call mark can also be displayed near the device option 6021 (for example, the upper left corner of the device option 6021). The call mark can be used to prompt that the device option 6021 corresponds to the electronic device 200 that the electronic device 100 is talking to. Device options.

In one example, the electronic device 100 can talk to multiple contacts at the same time, and the electronic device 100 can display options for the multiple contacts with whom the electronic device 100 is talking in the above-mentioned sharing menu 6020 .

The electronic device 100 may receive user input (eg, click) on the device option 6021, and in response to the input, the electronic device 100 may send a data transfer request to the electronic device 200 and display a sending window 6030 as shown in FIG. 6C.

As shown in Figure 6C, the sending window 6030 may include the description information 6031 of the above-mentioned news article (for example, "News Information APP: [High Young golfer Alee won gold in his first show]"), sending prompt 6032 and cancel control 6033. Among them, the sending prompt 6032 can be used to prompt the user that the current electronic device 100 is requesting to send a news article to the electronic device 200 that is talking to the electronic device 100 Open the link. The prompt type of the sending prompt 6032 can be any of text prompts (for example, "Requesting to send news information to Alice, waiting for the other party to confirm receipt."), picture prompts, animated picture prompts, video prompts, etc. One or more. The cancel control 6033 can be used to trigger the electronic device 100 to cancel sending the open link of the news article to the electronic device 200 .

As shown in FIG. 6D , after the electronic device 100 receives the confirmation information sent by the electronic device 200 , the electronic device 100 may display the sending window 6040 . The confirmation information is used to confirm receipt of the picture sent by the electronic device 100 . The sending window 6040 may include the description information 6041 of the news article and the sending prompt 6042. Optionally, the sending window 6040 may also include a sending progress bar 6043 and a cancellation control 6044. The sending prompt 6042 may be used to prompt the user that the electronic device 100 is currently sending the open link of the news article to the electronic device 200 that is talking to the electronic device 100 . The prompt type of the sending prompt 6042 may be any one or more of text prompts (for example, "Sending news information to Alice"), picture prompts, animated picture prompts, video prompts, and so on. The sending progress bar 6043 may be used to represent the progress of the electronic device 100 sending the open link of the news article to the electronic device 200 . The cancel control 6044 can be used to trigger the electronic device 100 to stop sending the open link of the news article to the electronic device 200 .

In one example, after receiving the user's input on the device option 6021, the electronic device 100 can directly send the opening link of the above news article to the electronic device 200 without the need for the electronic device 200 to return confirmation information.

Optionally, after the electronic device 100 sends the open link of the news article to the electronic device 200, it may receive and respond to the user's input and send a withdrawal instruction of the open link of the news article to the electronic device 200. After receiving the withdrawal instruction, the electronic device 200 may delete the open link of the news article sent by the electronic device 100 .

6E to 6G exemplarily illustrate an interface diagram of the electronic device 200 receiving data such as a shared link from the electronic device 100 when the electronic device 200 communicates with the electronic device 100 in the embodiment of the present application.

For example, as shown in FIG. 6E , the electronic device 200 and the electronic device 100 are talking, and the call interface 6050 is displayed. For the call interface 6050, reference can be made to the text description of the call interface 4100 in the embodiment shown in FIG. 4J, which will not be described again here.

After receiving the data transmission request sent by the electronic device 100, the electronic device 200 may display the receiving window 6060. The data transmission request may include the description information of the above-mentioned news article (for example, "News Information APP: [Golfer Alee wins gold medal in debut]"). The receiving window 6060 may include the description information 6061 of the above-mentioned news article, a receiving prompt 6062, a reject control 6063, a receiving control 6064, and so on. The receiving prompt 6062 may be used to prompt the user's electronic device 100 to request the electronic device 200 to open a link to the news article. The prompt type of the receiving prompt 6062 can be any one or more of text prompts (for example, "Daniel wants to share news information with you, do you want to accept it?"), picture prompts, animated picture prompts, video prompts, etc. The rejection control 6063 can be used to trigger the electronic device 200 to send rejection information to the electronic device 100 , and the rejection information can be used to instruct the electronic device 100 to cancel the open link of the news article shared with the electronic device 200 . The receiving control 6064 can be used to trigger the electronic device 200 to send confirmation information to the electronic device 100 . The confirmation information is used to instruct the electronic device 100 to confirm sending the open link of the news article to the electronic device 200 .

The electronic device 200 may receive user input (eg, click) to the receiving control 6064, in response to the input, the electronic device 200 may send confirmation information to the electronic device 100, and after sending the confirmation information, the receiving electronic device 100 sends Open link to a news article.

As shown in FIG. 6F , during the process of the electronic device 200 receiving the opening link of the news article sent by the electronic device 100 , the electronic device 200 may display the receiving window 6070 . The receive window 6070 may include a receive prompt 6072. Optionally, the receiving window 6070 may also include a receiving progress bar 6073 and a cancellation control 6074. The receiving prompt 6072 may be used to prompt the user that the electronic device 200 is currently receiving the open link of the news article sent by the electronic device 100 . The prompt type of the receiving prompt 6072 may be any one or more of text prompts (for example, "receiving news information sent to you by Daniel"), picture prompts, animated picture prompts, video prompts, etc. The reception progress bar 6073 may be used to represent the progress of the electronic device 200 receiving the opened link of the news article sent by the electronic device 100 . The cancel control 6074 can be used to trigger the electronic device 200 to stop receiving open links of news articles sent by the electronic device 200 .

As shown in FIG. 6G , after the electronic device 200 receives the opening link of the news article sent by the electronic device 100 , the electronic device 200 may display a receiving window 6080 . The receiving window 6080 may include description information 6081 of the news article and one or more functional controls. Among them, the one or more functional controls include an open control 6082 in a news information application, an open control 6083 using a browser, a copy to memo control 6084, and so on. The open in news information application control 6082 can be used to trigger the electronic device 200 to identify an open link based on the news article in the news information application, and display an interface including the news article. The open with browser control 6083 can be used to trigger the electronic device 200 to use a browser application to open a link based on the news article to display the news article. The copy to memo control 6084 may be used to trigger the electronic device 200 to copy the open link of the news article into the memo.

In one example, if the electronic device 200 does not obtain the contact name corresponding to the phone number of the electronic device 100, the sender identification prompted in the above reception prompt 6062 shown in Figure 6E and the reception prompt 6072 shown in Figure 6F It may be the phone number of the electronic device 100 .

In one example, if the electronic device 200 stores the contact name (for example, "Daniel") corresponding to the phone number of the electronic device 100, the above-mentioned receiving prompt 6062 shown in FIG. 6E and the receiving prompt 6072 shown in FIG. 6F The sender identification prompted in may be the contact name of the electronic device 100 (for example, "Daniel") and/or the phone number of the electronic device 100 (for example, "132XXXXXXXX").

In some application scenarios, the electronic device 100 may display a data sharing control on the call interface when making a call (voice call, video call, etc.) with another device (eg, the electronic device 200) and displaying the call interface. The electronic device 100 can receive and respond to the user's input to the data sharing control, allow the user to select specified data on the electronic device 100, and transmit the specified data to the device being called through a transmission link between the electronic device 100 and the device being called. device for calling. In this way, when the user is using the electronic device 100 to have a call with the other party, the user can trigger the sharing of data to the other party directly on the call interface, which facilitates the user to share the data on the electronic device 100 with the other party and improves the user's ability to share data. experience.

7A to 7G exemplarily illustrate an interface diagram for sharing data with the electronic device 200 when the electronic device 100 communicates with the electronic device 200 and displays the call interface in the embodiment of the present application.

For example, as shown in FIG. 7A , the electronic device 100 may be talking to the electronic device 200 and display the call interface 7010 . The call interface 7010 may include the phone number 7013 of the electronic device 200 (for example, "186XXXXXXXX"), the call duration 7014 (for example, "00:15"), and one or more call function controls, etc. The one or more call function controls include, but are not limited to, recording controls, waiting controls, add call controls, video call controls, mute controls, contact controls, dial controls, hang up controls, external call controls, and so on. For the text description of the one or more call function controls, reference can be made to the aforementioned embodiment shown in FIG. 4A , which will not be described again here. The electronic device 100 can display a sharing menu 7020 in a floating manner on the call interface 7010 . The sharing menu 7020 may include a call mode switching control 7021, a location sending control 7022, a file sharing control 7023, and so on. The call module switching control 7021 can be used to trigger the electronic device 100 to switch the call mode with the electronic device 200 . The location sending control 7022 can be used to trigger the electronic device 100 to send the location information of the electronic device 100 to the electronic device 200 . The file sharing control 7023 can be used to trigger the electronic device 100 to send the file data stored on the electronic device 100 to the electronic device 200 .

The electronic device 100 may receive user input (eg, click) to the file sharing control 7023, and in response to the input, the electronic device 100 may display a file selection interface 7030 as shown in FIG. 7B.

As shown in Figure 7B, a status bar 7011 may be displayed on the top of the file selection interface 7030. Since the electronic device 100 and the electronic device 200 are talking and have exited the call interface, the electronic device 100 can display a call icon 7015 in the status bar 7011. The call icon 7015 can be used to indicate that the electronic device 100 and other devices are currently talking. The file selection interface 7030 may include one or more file options (eg, picture file options 7031, document options, and send controls, etc.), a send control 7035, a delete control 7034, and so on. Each file option may be displayed with a selection box corresponding to it. For example, the picture file option 7031 may be displayed with a thumbnail of the picture 7032, and the right side of the picture file option 7032 may be with a selection box 7032. For example, the document file option may display the name of the document (for example, "Letter to Parents") and the file format (for example, ".docx") and so on. The delete control 7033 can be used to trigger the electronic device 100 to delete the selected file. The sending control can be used to trigger the electronic device 100 to send the selected file to the electronic device 200

The electronic device 100 may receive user input (eg, click) for the selection box 7033, and in response to the input, as shown in FIG. 7C, the electronic device 100 may display a check mark in the selection box 7033, and the check mark may be used to The user is prompted that the image file corresponding to the image file option 7031 is currently selected.

After the user selects the picture file corresponding to the picture file option 7031, the electronic device 100 can receive the user's input (for example, click) on the sending control 7035, and in response to the input, the electronic device 100 can send a data transmission request to the electronic device 200. , and the sending window 7040 shown in Figure 7D is displayed.

As shown in Figure 7D, the sending window 7040 may include a thumbnail 7041 of the above picture file, a sending prompt 7042, and a cancel control 7043. For the text description of the sending window 7040, please refer to the text description of the sending window 4070 in the embodiment shown in FIG. 4G, which will not be described again here.

As shown in FIG. 7E , after the electronic device 100 receives the confirmation information sent by the electronic device 200 , the electronic device 100 may display the sending window 7050 . The confirmation information is used to confirm receipt of the picture file sent by the electronic device 100 . For the text description of the sending window 7050, please refer to the text description of the sending window 4080 in the embodiment shown in FIG. 4H, which will not be described again here.

Optionally, as shown in FIG. 7F , after the electronic device 100 sends the file selected by the user to the electronic device 200 , the electronic device 100 may display a sending window 7060 . The sending window 7060 may include a thumbnail 7061 of the sent picture file, a sending prompt 7062, a withdrawal control 7063, and a continue sending control 7064. Among them, the withdrawal control 7063 can be used to trigger the electronic device 100 to The sub-device 200 sends a withdrawal instruction. After receiving the withdrawal instruction, the electronic device 200 may delete the above picture file sent by the electronic device 100 . The continue sending control 7064 can be used to trigger the electronic device 100 to switch to displaying the file selection interface shown in FIG. 7B , allowing the user to continue selecting files to send to the electronic device 200 .

In one example, the sharing menu 7020 in the embodiment shown in FIG. 7A can remain suspended and displayed at a fixed position on the call interface 7010. For example, the sharing menu 7020 may remain suspended and displayed on the top of the call interface 7010 .

In one example, the sharing menu 7020 in the embodiment shown in FIG. 7A can also remain suspended and displayed at the top of all interfaces. For example, when the electronic device 100 currently switches from the call interface 7010 to display other application interfaces, the sharing menu 7020 can remain suspended and displayed on the top layer of other application interfaces.

In one example, the display position of the sharing menu 7020 in the embodiment shown in FIG. 7A can be adjusted according to the user's input.

In one example, the above-mentioned call mode switching control 7021, location sending control 7022, and file sharing control 7023 can be used as call function controls and displayed on the call interface.

In one example, the sharing menu 7020 in the embodiment shown in FIG. 7A may be displayed after the data transmission link between the electronic device 100 and the electronic device 200 is established. or,

The file sharing control 7023 in the sharing menu 7020 in the embodiment shown in FIG. 7A can be enabled after the data transmission link between the electronic device 100 and the electronic device 200 is established. When in the enabled state, the file sharing control 7023 in the sharing menu 7020 can be enabled. 7023 can trigger the electronic device 100 to display the above file selection interface in response to the user's input. The file sharing control 7023 is in a disabled state before the data transmission link between the electronic device 100 and the electronic device 200 is established. When in the disabled state, the file sharing control 7023 cannot trigger the electronic device 100 to display the above file selection. interface. Among them, the display color of the file sharing control 7023 in the non-enabled state is different from the display color in the enabled state. For example, the display color in the non-enabled state can be gray, and the display color in the enabled state can be white. or green.

In one example, the sharing menu 7020 in the embodiment shown in FIG. 7A may also include the phone number corresponding to the electronic device 200 and/or the contact name (for example, Alice) corresponding to the phone number of the electronic device 200 and/or The contact avatar corresponding to the phone number of the electronic device 200, and so on.

For example, as shown in FIG. 7G , the electronic device 100 can display the sharing menu 7070 in a floating manner on the call interface 7010 . The sharing menu 7070 may include the contact name (for example, Alice) corresponding to the phone number of the electronic device 200, the contact avatar 7071 corresponding to the phone number of the electronic device 200, the exit control 7072, the call mode switching control 7073, and the location. Send control 7074, file sharing control 7075, and so on. For text descriptions of the call mode switching control 7073, the location sending control 7074, and the file sharing control 7075, please refer to the text description of the sharing menu 7020 in the embodiment shown in FIG. 7A, and will not be described again here. The electronic device 100 may receive and respond to the user's input (eg, dragging) on the sharing menu 7070 and adjust the display position of the sharing menu 7070 .

As shown in FIG. 7H , when the electronic device 100 receives user input (eg, click) to the exit control 7072, in response to the input, the electronic device 100 may hide the share menu 7070. After the electronic device 100 hides the sharing menu 7070, the electronic device 100 can display the mark button 7076. The mark button 7076 may be used to trigger the electronic device 100 to re-display the sharing menu 7070 . The mark button 7076 can be displayed on the edge of the touch screen to save the display space of the touch screen. Optionally, when the sharing menu 7070 is moved to the edge of the touch screen by the user or moves to the edge of the touch screen and stays for a certain period of time (for example, 1 second), the electronic device 100 can hide the sharing menu 7070 and display the above-mentioned mark button. 7076. The display position of the mark button 7076 may also be adjusted based on user input.

Optionally, as shown in FIG. 7I , the mark 7076 may also display the telephone number of the electronic device 200 and/or the contact name corresponding to the telephone number of the electronic device 200, and so on.

In some application scenarios, the electronic device 100 can interact with a contact (for example, the contact "Alice" corresponding to the electronic device 200) (for example, make a call, send a text message, or send a private message or like/ After commenting on the content sent by the contact in the circle of friends, etc.), when the user triggers the sharing of the specified data, the specified data will be displayed in the sharing interface (system sharing interface or in-app sharing interface) or sharing window (system sharing window or The option of one or more recent contacts is displayed in the in-app sharing window). When the user chooses to share the specified data with the specified contact in the one or more recent contacts in the sharing interface or sharing window, the electronic device 100 can transmit the specified data to the specified contact's device. In this way, users can share data with recent contacts, improving the user experience of sharing data.

8A-8B exemplarily illustrate an interface diagram for sharing data to recently interacted contacts on the system sharing interface in the embodiment of the present application.

For example, as shown in FIG. 8A , the electronic device 100 can display a picture display interface 8010. The picture display interface 8010 includes a picture 8011 and a menu 8012. Among them, the menu 8012 includes a share button 8013, a collection button, an edit button, a delete button, and a more button. For the text description of menu 8012, reference may be made to menu 4052 in the embodiment shown in FIG. 4E, which will not be described again here.

The electronic device 100 may receive user input (eg, click) on the share button 8013, and in response to the input, the electronic device 100 may display the system sharing interface 8020 as shown in FIG. 8B.

As shown in Figure 8B, the system sharing interface 8020 may include an area 8021, an area 8022, and an area 8023. in:

This area 8021 can be used to display one or more pictures or videos in the gallery, and the one or more pictures or videos can include pictures or videos selected by the user. A mark may be displayed on the selected picture, and the mark may be used to indicate that the corresponding picture is selected (that is, the picture has been selected by the user). The pictures or video images displayed in this area 8021 may be thumbnails. The original image corresponding to the picture or video picture displayed in area 8021 can be stored on the electronic device 100 . The area 8022 may include options (eg, options 8024 and 8027, etc.) corresponding to one or more recently interacted contacts with which the electronic device 100 has recently interacted (eg, interacted in the last half hour). Among them, the option corresponding to the recently interacted contact may display the avatar of the recent contact, and the option corresponding to the recently interacted contact may display the name of the most recent contact. Prompt information (for example, a text prompt "Recent Contact") may also be displayed around the recently interacted contact, and the prompt information is used to remind the user that this option is an option for recent contacts. Optionally, an application mark may be displayed around the option corresponding to the recent contact, and the application mark may be used to indicate the application to which the recent contact belongs. For example, option 8024 corresponds to the contact "Alice" in the phone application on the electronic device 100. The contact name "Alice" and prompt information 8025 (for example, "Recent Contacts") may be displayed below the option 8024. The upper left corner of the option 8024 Corner can be displayed with phone application mark 8026. Option 8027 corresponds to the contact "Kiki" in the chat application on the electronic device 100. The contact name "Kiki" and prompt information 8028 (for example, "Recent Contacts") can be displayed below the option 8027. The upper left corner of the option 8027 can Chat application tag 8029 is displayed. The area 8022 may also display nearby device options discovered by the electronic device 100. For example, after the electronic device 100 searches for nearby devices, the device options of the nearby devices may be displayed in the area 8022 (for example, the "HUAWEI P50" option). This area 8023 displays one or more service options (eg, mail icon, browser icon, information icon, WLAN direct icon, etc.). For the text description of the area 4064, please refer to the text description of the area 3023 in the embodiment shown in FIG. 3B, which will not be described again here.

The electronic device 100 may receive the user's input (for example, click) on the option 8024, and in response to the input, the electronic device 100 may send the picture selected by the user to the electronic device 200 corresponding to the recent interaction contact "Alice".

In one example, the electronic device 100 may send a data transmission request to the electronic device 200 before sending the data selected by the user to the electronic device 200 corresponding to the recent interaction contact "Alice". After the electronic device 100 receives the confirmation information sent by the electronic device 200, the electronic device 100 sends the data selected by the user to the electronic device 200 corresponding to the recent interactive contact "Alice". During the process of the electronic device 100 sending to the electronic device 200, the sending window displayed on the electronic device 100 can refer to the aforementioned embodiment shown in FIGS. 4G-4I, and the receiving window displayed on the electronic device 200 can refer to the aforementioned Figure 4K-FIG. The embodiment shown in 4M will not be described again here.

In one example, when the electronic device 100 recently interacts with a contact in an instant messaging application, the electronic device 100 can send the content selected by the user through the instant messaging application and the server of the instant messaging application. on the electronic device 200 corresponding to the recently interacted contact. Wherein, the instant messaging application is installed on the electronic device 200, and the account of the recently interacted contact is logged in.

Figures 8C-8D exemplarily illustrate the interface diagram of sharing data to recently interacted contacts in the in-application sharing interface in the embodiment of the present application.

For example, as shown in FIG. 8C , the electronic device 100 can display a news information application interface 8030. The news information application interface 8030 may include the title of the news article (for example, "Golf boy Alee won gold in his debut"), the content of the news article (for example, "Yesterday, golf boy Alee made his debut in the golf tournament, winning four rounds of gold"). The total score of 267 won the gold medal."), the name of the publisher of the news article (for example, "Morning News") and avatar, more controls 8031. For the text description of the news information application interface 8030, please refer to the text description of the news information application interface 6010 in the embodiment shown in FIG. 6A, which will not be described again here.

The electronic device 100 may receive user input (eg, click) to the more control 8031, and in response to the input, the electronic device 100 may display a share menu window 8040 as shown in FIG. 6B.

As shown in FIG. 8D , the sharing menu window 8040 may include one or more sharing service options. Wherein, the one or more sharing service options may include options (for example, option 8024 and option 8027, etc.) corresponding to one or more recently interacted contacts with which the electronic device 100 has recently interacted (for example, interacted in the last half hour). ), sharing options within the news information application (e.g., private message options, forwarding options, etc.) and/or sharing options in other applications (e.g., friend circle options, chat application options, welink application options, etc.), and /or system sharing option 8047. The sharing menu 8040 may also include other functional controls (for example, collection controls, link copy controls, etc.). The system sharing option 8047 can be used to trigger the electronic device 100 to call the system sharing function, and display the system sharing interface to share the news article. The text description of the system sharing interface for sharing the news article can refer to the sharing shown in Figure 8B above. pictorial The system sharing interface will not be described in detail here. Among them, the option corresponding to the recently interacted contact may display the avatar of the recent contact, and the option corresponding to the recently interacted contact may display the name of the most recent contact. Prompt information (for example, a text prompt "Recent Contact") may also be displayed around the recently interacted contact, and the prompt information is used to remind the user that this option is an option for recent contacts. Optionally, an application mark may be displayed around the option corresponding to the recent contact, and the application mark may be used to indicate the application to which the recent contact belongs. For example, option 8041 corresponds to the contact "Alice" in the phone application on the electronic device 100. The contact name "Alice" and prompt information 8042 (for example, "Recent Contacts") may be displayed below the option 8041. The upper left corner of the option 8041 Corner can be displayed with phone application mark 8043. Option 8044 corresponds to the contact "Kiki" in the chat application on the electronic device 100. The contact name "Kiki" and prompt information 8045 (for example, "Recent Contacts") can be displayed below the option 8044. The upper left corner of the option 8044 can Shows chat application tag 8046.

The electronic device 100 may receive the user's input (for example, click) on the option 8041, and in response to the input, the electronic device 100 may send the open link of the news article selected by the user to the electronic device corresponding to the recent interaction contact "Alice" 200.

In this embodiment of the present application, the display form of the content in the above-mentioned system sharing interface or in-application sharing interface is not limited, and may be presented in the form of an interface, or may be presented in the form of a window or menu. For example, when the content in the system sharing interface is presented in the form of an interface, it can be called the system sharing interface. When the content in the system sharing interface is presented in the form of a window or menu, it can be called the system sharing window, system sharing menu, etc. wait. For another example, when the content in the in-application sharing interface is presented in the form of an interface, it can be called an in-application sharing interface. When the content in the in-application sharing interface is presented in the form of a window or menu, it can be called a sharing menu window, or Share menu, in-app sharing window, and more.

In the embodiments of this application, there is no limit to the type of user input. The above embodiment only lists preferred user input types. In specific implementation, the user input type can be any one of the following or a combination of multiple operations: Single Click, double-click, long press, slide, drag, multi-finger press and hold, multi-finger swipe, knuckle touch, knuckle slide, and more.

The following introduces a communication system 90 provided in the embodiment of the present application.

Figure 9 shows a schematic architectural diagram of a communication system 90 provided in the embodiment of the present application.

As shown in FIG. 9 , the communication system 90 may include an electronic device 100 and an electronic device 200 . Among them, the electronic device 100 can communicate with the electronic device 200 through the main link. The call between the electronic device 100 and the electronic device 200 may include, but is not limited to, operator calls and/or OTT calls. Among them, the types of calls between the electronic device 100 and the electronic device 200 can also be divided into voice calls, video calls, conference calls, ringback tones, and so on. The electronic device 100 can share content data to the electronic device 200 through the primary link, and can also share content data to the electronic device 200 through the auxiliary link. For example, the electronic device 100 can talk to the electronic device 200 through the operator's call link, and the electronic device 100 can share content data to the electronic device 200 through the operator's call link.

In one example, the electronic device 100 can talk to the electronic device 200 through the operator call link, and the electronic device 100 can share content data to the electronic device 200 through the auxiliary link.

In one example, the electronic device 100 can talk to the electronic device 200 through the operator call link, and the electronic device 100 can share content data to the electronic device 200 through the operator call link and the auxiliary link. Among them, part of the shared content data can use the operator's call link, and the other part can use the auxiliary link.

Among them, the auxiliary link can be a data transmission link established through near field communication technology, for example, through Wi-Fi, BT, end-to-end (device-to-device, D2D), vehicle to everything (V2X) ), and other data transmission links established by communication technology. The auxiliary link can also be a data transmission link established through far-field communication technology, such as primary card/secondary card cellular communication (for example, 2G/3G/4G/5G/6G) technology, satellite communication technology, Wi-Fi Data transmission links established by other communication technologies. The auxiliary link can be a link established by any of the above types of communication technologies, or it can be multiple links established by multiple same or different communication technologies.

The data shared by the electronic device 100 and the electronic device 200 may be local to the electronic device (for example, pictures, videos, audios, contact information, application APKs, PPT/PDF/Word/Excel documents, etc.), or may be Content in third-party applications (for example, pictures, videos, audios, news articles, location information, links, etc.).

The following introduces a data sharing method provided in the embodiment of this application.

Figure 10 shows a data sharing method provided in the embodiment of this application.

As shown in Figure 10, the method may include the following steps:

S1001. The electronic device 100 receives a user's sharing input that triggers sharing of specified data.

Among them, the specified data can be file-type data, text-type data, link-type data, pasteboard-type data, and other types of data. Among them: 1. File data can include pictures, videos, audios, documents in DOCX/PPTX/PDF/XLS and other formats, and application APKs/installations Packages, contact QR codes, contact vCards, location information in the form of images/rich media, etc. 2. Text data can include contact text, textual location information, etc. 3. Link data may include: links to local application or third-party application content (for example, pictures, videos, audios, news, articles, etc.), and location information viewing links. 4. Pasteboard data can include the currently selected content, or the content or objects on the pasteboard. The specified data may also be other types of data content that can be shared with other devices, which is not limited in the embodiments of this application.

Exemplarily, the sharing input can be as shown in the embodiments shown in the above-mentioned Figures 4A to 4O, or Figures 5A to 5Y, or Figures 8A to 8B, etc. For the input of the sharing control/button, in the embodiment of the present application , there is no limit to the operation type of sharing input, for example, it can be click, long press, slide, double-click, etc. For specific content, reference may be made to the embodiments shown in the aforementioned FIGS. 4A to 4O, or FIGS. 5A to 5Y, or FIGS. 8A to 8B, etc., which will not be described again here.

S1002. The electronic device 100 determines whether the electronic device 100 is in a call.

The call may include but is not limited to operator calls and/or OTT calls (for example, chat voice calls or video calls). The types of calls can also be divided into voice calls, video calls, conference calls, ringback tones, and so on.

S1003. When the electronic device 100 is on a call, the electronic device 100 obtains the information of the current call contact.

Among them, if the above call is an operator call, the information of the current call contact may include one or more of the following: the current call contact's phone number, contact name, contact avatar, etc. If the above call is an OTT call, the information of the current call contact may include one or more of the following: contact account ID, contact nickname, contact avatar, etc.

S1004. The electronic device 100 establishes a data transmission link with the electronic device 200 of the current call contact.

Specifically, reference can be made to the subsequent embodiments for the process of establishing a data transmission link between the electronic device 100 and the electronic device 200 and will not be described in detail here.

S1005. The electronic device 100 determines whether the data transmission link has been established with the electronic device 200 of the current call contact.

S1006. After the electronic device 100 and the electronic device 200 have established a data transmission link, the electronic device 100 can display the options of the current call contact on the system sharing interface.

In one example, when the data transmission link completely or partially takes the main link of the current call, the electronic device 100 can immediately display options for the current call contact in the system sharing interface.

In one example, when the data transmission link completely takes the newly established auxiliary link (including one or more links), the electronic device 100 can share the data in the system after at least one of the auxiliary links is established. The interface displays options for current call contacts.

In one example, the timing of establishing a data transmission link between the electronic device 100 and the electronic device 200 of the current call contact may be before the electronic device 100 receives the above sharing input, or after receiving the above sharing input. in:

1. When the time to establish a data transmission link between the electronic device 100 and the electronic device 200 is before receiving the above sharing input, the electronic device 100 can first establish a data transmission link with the electronic device 200 . After displaying the system sharing interface in response to the above sharing input, the electronic device 100 can display the system sharing interface, and display the option of the current call contact in the system sharing interface. After establishing the auxiliary link, the electronic device 100 can display the system sharing interface in the system sharing interface. Updates the option to display current call contacts.

2. When the timing of establishing a data transmission link between the electronic device 100 and the electronic device 200 is after receiving the above sharing input, the electronic device 100 can display the system sharing interface in response to the above sharing input. At this time, there is no system sharing interface. Including options for current call contacts. After the electronic device 100 and electronic device 200 establish a data transmission link, the electronic device 100 can update and display the options for current call contacts in the system sharing interface.

3. The electronic device 100 may first respond to the above sharing input, display the system sharing interface and display the options of the current call contact in the system sharing interface. After receiving the user's selection operation on the option of the current call contact, the electronic device 100 may establish a data transmission link with the electronic device 200 of the current call contact in response to the selection operation. After establishing the data transmission link, the electronic device 100 can send designated data to the electronic device 200 based on the data transmission link.

For the text description of the system sharing interface and the options of the current call contact, please refer to the embodiments shown in FIGS. 4A to 4O, or 5A to 5Y or 8A to 8B, which will not be described again here.

S1007. The electronic device 100 receives the user's selection operation on the options of the current call contact.

S1008. The electronic device 100 obtains specified data in response to the selection operation.

When the designated data is file-type data, the electronic device 100 can open and read the file-type data through an application programming interface (application programming interface, API) of the system file operation. For example, you can open file data through the function "fopen" and read the file content through the function "fread". Among them, the reading method can be text reading or binary stream reading. When the specified data is text, link, or data on the pasteboard, the electronic device 100 can also use a similar system interface function. Data can be read through the interface of digital or third-party APP.

S1009. The electronic device 100 sends the specified data to the electronic device 200 of the current call contact through the data transmission link.

Specifically, during the process of the electronic device 100 sending specified data to the electronic device 200, the displayed interface changes may refer to the embodiments shown in the aforementioned Figures 4A to 4O, or Figures 5A to 5Y, or Figures 8A to 8B, etc. I won’t go into details here.

S1010. When the electronic device 100 is not in a call, the electronic device 100 can obtain information of one or more recently interacted contacts.

The most recently interacted contacts may be contacts with which the user of the electronic device 100 interacted with the contact corresponding to the electronic device 100 within a specified time range (for example, within the last hour).

In the embodiment of the present application, the interaction between the electronic device 100 and the electronic device 200 may include: operator calls, receiving/sending text messages, interactions within social applications, and so on. Among them, interactions within social applications can include OTT calls, receiving/sending private messages, liking/being liked, commenting/being commented on, following/being followed, favorites/being favorites, the other party’s live broadcast, content posted in friend circles, etc. Interactive social interaction. Among them, the social applications include but are not limited to instant messaging applications (for example, Changlian application, etc.), live video applications (for example, Huawei Video application, etc.), music playback applications (for example, Huawei Music application, etc.), and other applications with multi-user social attributes.

In one example, the most recently interacted contacts may also be contacts with whom the user of the electronic device 100 has interacted with one or more of the above specified applications within a specified time range.

In one example, the electronic device 100 can also sort the contacts from recent to far in terms of interaction time, and determine a specified number (for example, 3) of recent interaction contacts with the most recent interaction time.

Information about recently interacted contacts may include one or more of the following: phone number of recently interacted contacts, application ID of recently interacted contacts, account ID of recently interacted contacts, nickname of recently interacted contacts, recently interacted contacts avatar, etc.

S1011. The electronic device 100 displays options for one or more recently interacted contacts on the system sharing interface.

For the option of displaying one or more recently interacted contacts in the system sharing interface, please refer to the system sharing interface 8020 in the embodiment shown in FIG. 8B , which will not be described again here.

When the electronic device 100 receives the user's selection of the option of specifying a recently interacted contact among one or more recently interacted contacts, the electronic device 100 may send the specified data on the data transmission link to the electronic device corresponding to the specified recently interacted contact. 200.

Specifically, when the electronic device 100 sends specified data to the electronic device 200, the displayed interface changes may refer to the embodiments shown in the aforementioned FIGS. 4A to 4O, or FIGS. 5A to 5Y or 8A to 8B, which will not be mentioned here. Again.

Optionally, when the electronic device 100 determines that the electronic device 200 of the current call contact has not completed establishing the data transmission link, the electronic device 100 may perform the above steps S1010 and S1011.

In some embodiments, the electronic device 100 can also simultaneously display options for current call contacts and recently interacted contacts in the system sharing interface. When the user selects the option of the current call contact on the system sharing interface, the electronic device 100 can share the specified data with the device of the current call contact. When the user selects the option of the recently interacted contact on the system sharing interface, the electronic device 100 can Share specified data to devices of recently interacted contacts.

The following introduces a data sharing method provided in another embodiment of the present application.

Figure 11 shows a data sharing method provided in another embodiment of the present application.

As shown in Figure 11, the method may include:

S1101. The electronic device 100 receives a user's input to trigger sharing of specified data in a specified application.

Among them, the specified data can be file-type data, text-type data, link-type data, pasteboard-type data, and other types of data. Among them: 1. File data can include pictures, videos, audios, documents in DOCX/PPTX/PDF/XLS and other formats, application APK/installation packages, contact QR codes, contact vCards, pictures/rich media location information, etc. 2. Text data can include contact text, textual location information, etc. 3. Link data may include: links to local application or third-party application content (for example, pictures, videos, audios, news, articles, etc.), and location information viewing links. 4. Pasteboard data can include the currently selected content, or the content or objects on the pasteboard. The specified data may also be other types of data content that can be shared with other devices, which is not limited in the embodiments of this application.

Exemplarily, the input that triggers the sharing of specified data in the specified application can be the input of the sharing control/button in the embodiments shown in Figures 6A to 6G, or Figure 8C to 8D, etc. In the embodiment of the present application, There is no limit to the operation type of sharing input, for example, it can be click, long press, slide, double click, etc. For specific content, please refer to the embodiments shown in FIGS. 6A to 6G, or 8C to 8D, etc., in This will not be described again.

S1102. The electronic device 100 determines whether to enter system sharing.

S1103. When the electronic device 100 does not enter the system sharing, the electronic device 100 determines whether it is in a call.

Wherein, the call may include but is not limited to operator calls and/or OTT calls (for example, voice calls or video calls of chat applications). The types of calls can also be divided into voice calls, video calls, conference calls, ringback tones, and so on.

S1104. When the electronic device 100 is in a call, the electronic device 100 can obtain the information of the current call contact.

S1105. The electronic device 100 can establish a data transmission link with the electronic device 200 of the current call contact.

S1106. The electronic device 100 may determine whether the data transmission link has been established with the electronic device 200 of the current call contact.

S1107. After the electronic device 100 and the electronic device 200 have established a data transmission link, the electronic device 100 can display options for the current call contact on the in-application sharing interface.

In one example, when the data transmission link completely or partially takes the main link of the current call, the electronic device 100 can immediately display options for the current call contact in the in-application sharing interface.

In one example, when the data transmission link completely takes the newly established auxiliary link (including one or more links), the electronic device 100 can, after at least one of the auxiliary links is established, within the application. Option to display current call contacts in the sharing interface.

In one example, the timing of establishing a data transmission link between the electronic device 100 and the electronic device 200 of the current call contact may be before the electronic device 100 receives the above input that triggers the sharing of specified data in the specified application, or may be after receiving to the above trigger to share the input of specified data in the specified application. in:

1. When the time to establish a data transmission link between the electronic device 100 and the electronic device 200 is before receiving the input of the specified data in the specified application that triggers sharing, the electronic device 100 can first establish a data transmission link with the electronic device 200 . After displaying the in-application sharing interface in response to the input of specified data in the triggering sharing specified application, the electronic device 100 may display the in-application sharing interface, and display the option of the current call contact in the in-application sharing interface to establish the auxiliary link. way, the electronic device 100 can update the option of displaying the current call contact in the system sharing interface.

2. When the timing of establishing a data transmission link between the electronic device 100 and the electronic device 200 is after receiving the input of specified data in the specified application that triggers sharing, the electronic device 100 may respond to the input of specified data in the specified application that triggers sharing. , display the in-application sharing interface. At this time, the in-application sharing interface does not include the option of the current call contact. After the electronic device 100 and the electronic device 200 establish a data transmission link, the electronic device 100 can Updated options showing current call contacts.

3. The electronic device 100 may first respond to the input of specified data in the specified application that triggers sharing, display the in-application sharing interface and display the option of the current call contact in the in-application sharing interface. After receiving the user's selection operation on the option of the current call contact, the electronic device 100 may establish a data transmission link with the electronic device 200 of the current call contact in response to the selection operation. After establishing the data transmission link, the electronic device 100 can send designated data to the electronic device 200 based on the data transmission link.

For text descriptions of the in-application sharing interface and the options of the current call contact, please refer to the aforementioned FIGS. 6A to 6G, or FIGS. 8C to 8D, and other embodiments of the sharing menu or sharing menu window. Here No longer.

S1108. The electronic device 100 may receive the user's selection operation on the options of the current call contact.

S1109. In response to the selection operation, the electronic device 100 can obtain specified data.

When the designated data is file-type data, the electronic device 100 can open and read the file-type data through an application programming interface (API) for system file operations. For example, you can open file data through the function "fopen" and read the file content through the function "fread". Among them, the reading method can be text reading or binary stream reading. When the designated data is text, links, or data on a pasteboard, the electronic device 100 can also use similar system interface functions or third-party APP interfaces to read the data.

S1110. The electronic device 100 can send the specified data to the electronic device 200 of the current call contact.

Specifically, when the electronic device 100 sends specified data to the electronic device 200, the displayed interface changes may refer to the aforementioned embodiments of FIGS. 6A-6G, or 8C-8D, etc., which will not be described again here.

S1111. When the electronic device 100 is not in a call, the electronic device 100 can obtain the information of the recently interacted contacts.

In the embodiment of the present application, the interaction between the electronic device 100 and the electronic device 200 may include: calling with the operator, receiving/sending text messages, Interactions within social apps, and more. Among them, interactions within social applications can include OTT calls, receiving/sending private messages, liking/being liked, commenting/being commented on, following/being followed, favorites/being favorites, the other party’s live broadcast, content posted in friend circles, etc. Interactive social interaction. Among them, the social applications include but are not limited to instant messaging applications (for example, Changlian application, etc.), live video applications (for example, Huawei Video application, etc.), music playback applications (for example, Huawei Music application, etc.), and other applications with multi-user social attributes.

S1112. The electronic device 100 can display recently interacted contacts on the in-application sharing interface.

For the option of displaying one or more recently interacted contacts in the in-application sharing interface, reference may be made to the sharing menu window 8040 in the embodiment shown in FIG. 8D , which will not be described again here.

Optionally, when the electronic device 100 determines that the electronic device 200 of the current call contact has not completed establishing the data transmission link, the electronic device 100 may perform the above steps S1111 and S1112.

S1113. When the electronic device 100 determines that it has entered system sharing, the electronic device 100 can execute the system sharing process.

For the system sharing process, reference may be made to steps S1001 to S1011 in the embodiment shown in FIG. 10 , which will not be described again here.

The following describes the process by which the electronic device 100 obtains information about recently interacted contacts in the embodiment of the present application.

Figures 12A-12C exemplarily illustrate the process of obtaining information about recently interacted contacts in this embodiment of the present application.

The electronic device 100 may include a system sharing module and interactive applications. Among them, the system sharing module can be used to provide the electronic device 100 with the function of sharing data. Interactive applications may include applications that are provided by the system on the electronic device 100 (for example, dialing applications, text messaging applications (which may also be called messaging applications), etc.), or may be social applications that are not provided by the system, where the social application Including but not limited to instant messaging applications (for example, Changlian application, etc.), live video applications (for example, Huawei Video application, etc.), music playback applications (for example, Huawei Music application, etc.), etc. and other applications with multi-user interaction.

in:

1. As shown in Figure 12A, the interactive application can provide a calling interface for the system sharing module to call. The system sharing module can call the acquisition function to obtain the information of a specified number of recent interactive contacts in the interactive application. Among them, the interactive application can return the information of a specified number of recent interactive contacts. The recently interacted contact information may include one or more of the following: interactive application ID (appid), user ID (userid), phone number (phonenumber), avatar (portrait), nickname (nickname), interaction time (time) ),etc.

For example, the system sharing module can obtain the information of a specified number of recently interacted contacts in an interactive application by calling the acquisition function "get_last_interaction(appid, count)", where the interactive application is carried in the calling function "get_last_interaction(appid, count)" ID ("appid") and the number of recently interacted contacts ("count").

After receiving the call request sent by the system sharing module through the acquisition function "get_last_interaction(appid,count)", the interactive application can return the specified number of recent interactive contact information to the system sharing module.

The system sharing module can use recently interacted contacts as objects to be shared, and display options for recently interacted contacts in the system sharing interface.

In one example, when the electronic device 100 has multiple interactive applications, the electronic device 100 can call the acquisition function simultaneously or sequentially to obtain the information of one or more recently interacted contacts in each interactive application, and then obtain information from the multiple interactive applications. From the information of one or more recently interacted contacts in the application, a specified number of recently interacted contacts with the most recent time are filtered out as objects to be shared, and the option of the recently interacted contacts is displayed in the system sharing interface.

In one example, the electronic device 100 may periodically (for example, every 3 minutes) call the acquisition function to obtain information about recent interactive contacts in the interactive application.

2. As shown in Figure 12B, the system sharing module can provide a registration interface for interactive applications to register the information of one or more interactive contacts. The interactive application can actively register the information of one or more interactive contacts with the system sharing module by calling the registration function in the kit mode.

For example, an interactive application can register the information of interactive contacts within the interactive application with the system sharing module by calling the registration function "register interaction(appid, userid, portrait, nickname, status)". The recently interacted contact information may include one or more of the following: interactive application ID (appid), user ID (userid), avatar (portrait), nickname (nickname), status (status), and so on. Among them, the interactive application can register the interactive contact information to the system sharing module by calling the registration function at the beginning and end of the interaction. The status can include interaction start (start) or interaction end (end). The system sharing module can filter out one or more recently interacted contacts from the interactive contacts registered in one or multiple interactive applications as objects to be shared, and display them in the system sharing interface.

In one example, the interactive application can only register the interactive contact information to the system sharing module by calling the registration function at the end of the interaction. At this time, the recent interactive contact information can include one or more of the following: Interactive application ID (appid), user ID (userid), avatar (portrait), nickname (nickname), etc. The system sharing module can filter out one or more recently interacted contacts from the interactive contacts registered by one or multiple interactive applications as objects to be shared, and display them in the system sharing interface.

3. As shown in Figure 12C, after the system sharing module obtains the information of one or more recently interacted contacts through the method shown in Figure 12A or Figure 12B, the system sharing module can provide a calling interface for the sharing application to call, share The application can call the acquisition function to obtain the information of the specified number of recently interacted contacts from the system sharing module. Among them, the system sharing module can return the information of a specified number of recently interacted contacts to the sharing application. The sharing application may be an application with an in-application sharing function in the above embodiment. For example, news information applications, map applications, etc.

For example, a sharing application can obtain the information of a specified number of recently interacted contacts from the system sharing module by calling the acquisition function "get_last_interaction(appid, count)", where the interactive application is carried in the calling function "get_last_interaction(appid, count)" ID ("appid") and the number of recently interacted contacts ("count").

The system sharing module can return the information of a specified number of recently interacted contacts to the sharing application after receiving a request to call the function "get_last_interaction(appid,count)" from the sharing application. The sharing application can filter out one or more recently interacted contacts from a specified number of recently interacted contacts as objects to be shared, and display them in the in-app sharing interface (or in-app sharing window).

In one example, the sharing application module can set the ID ("appid") of the interactive application carried in the calling function "get_last_interaction(appid, count)" to the all-select value (for example, "0"), and the system sharing module can When receiving that the value of the "appid" is a select-all value (for example, "0"), the information of the specified number of recently interacted contacts in all types of applications is given to the sharing application. The sharing application can filter out one or more recently interacted contacts from a specified number of recently interacted contacts in all types of applications as objects to be shared, and display them in the in-app sharing interface (or in-app sharing window).

The following introduces a communication system architecture provided in the embodiment of this application.

FIG. 13A exemplarily shows an architectural diagram of a communication system 1300 provided in the embodiment of the present application.

As shown in FIG. 13A , the communication system 1300 may include an electronic device 100 , an electronic device 200 and a cloud server 300 .

in:

1. The electronic device 100 may include an application processor (application processor, AP) 1310, a high-fidelity (high-fidelity, HiFi) module 1320, and a modem (modem) 1330.

The application processor 1310 may include one or more functional modules, and the one or more functional modules may include a fusion call (FusionCall) module 1311 and a network address translation service (Network address translation service, NatService) module 1312. Among them, the FusionCall module 1311 can be used to perform user-level authentication with the account server 1371 in the cloud server 300 to obtain an access token (access token, AT). The FusionCall module 1311 can also be used to request the business cloud server 1380 to authenticate AT, generate point to point tokens (P2P Token), exchange session identifiers (session identifiers, sessionID) for NAT traversal, and push service docking. ,etc. The NatService module 1312 can be used to interact with the network address translation (NAT) traversal cloud server 1390 for NAT traversal signaling to complete a point-to-point (P2P) auxiliary link between the electronic device 100 and the electronic device 200 NAT traversal and a relay link between the electronic device 100 and the electronic device 200 are established.

In one example, the FusionCall module 1311 can also be used to request the business cloud server 1380 to perform device-level authentication on the electronic device 100, for example, to verify the device certificate of the electronic device 100.

In one example, the FusionCall module 1311 can also be used to perform data interaction with the HiFi module 1320, and perform operations such as intercepting, and/or merging, and/or replacing RTP data packets, so as to realize the data content selected by the user through the call. The main link is sent to the electronic device 200.

The role of the FusionCall module 1311 may also include but is not limited to the following functions: responsible for calling the network address service module to manage the auxiliary link (for example, the establishment and release of the auxiliary link). Responsible for reading shared content data (for example, file data, location information, open links, calendars, application installation packages, etc.). Responsible for offloading, transmitting, unpacking, etc. of shared content data. Responsible for writing and storing shared content data. Responsible for the display of relevant user experience (UX) interfaces, including but not limited to: system sharing interface (including options for currently interacting contacts or options for recently interacted contacts), in-application sharing interfaces/windows for interactive contacts Options for people or recently interacted contacts, sending windows, receiving windows, prompt messages, buttons/controls, etc.

The NatService module 1312 can be used to implement the establishment and release of auxiliary links, etc.

The HiFi module 1320 can be used to realize the transmission of real-time call data through the real-time transport protocol (real-time transport protocol, RTP)/real-time transport control protocol (real-time transport control protocol, RTCP).

The modem 1330 may include a routing Internet protocol (IP) multimedia system (IP multimedia subsystem, IMS) adapter (IMS adapter, IMSA) and an IMS protocol stack. IMSVA can be used to implement protocol data transmission between the RTP/RTCP protocol and the IMS protocol stack. The modem 1330 may be used to implement IMS calls with the electronic device 200 on the main link on the operator's network based on the IMS protocol stack. Among them, IMS calls may include but are not limited to VoLTE, ViLTE, VoNR, ViNR, VoWiFi, ViWiFi, EPS-Fallback and other types of calls.

2. The electronic device 200 may include an application processor 1340, a HiFi module 1350, and a modem 1360.

The application processor 1340 may include one or more functional modules, and the one or more functional modules may include a FusionCall module 1341 and a NatService module 1342. Among them, the FusionCall module 1341 can be used to perform user-level authentication with the account server 1371 in the cloud server 300 to obtain an access token (access token, AT). The FusionCall module 1341 can also be used to request the business cloud server 1380 to authenticate AT, generate P2P Token, exchange session ID for NAT traversal, push service docking, etc. The NatService module 1342 can be used to interact with NAT traversal signaling with the NAT traversal cloud server 1390 to complete NAT traversal between the P2P auxiliary link between the electronic device 100 and the electronic device 200 and between the electronic device 100 and the electronic device 200 The trunk link is established.

In one example, the FusionCall module 1341 can also be used to request the service cloud server 1380 to perform device-level authentication on the electronic device 100, for example, to verify the device certificate of the electronic device 100.

In one example, the FusionCall module 1341 can also be used to perform data interaction with the HiFi module 1320, and perform operations such as interception, and/or merging, and/or replacement of RTP data packets to achieve reception on the main link of the call. The data content sent by the electronic device 100.

The NatService module 1342 can be used to implement the establishment and release of auxiliary links, etc.

The HiFi module 1350 can be used to transmit real-time call data through RTP/RTCP.

The modem 1360 may include IMSVA and IMS protocol stack. The IMSVA can be used to implement protocol data transmission between the RTP/RTCP protocol and the IMS protocol stack. The modem 1360 can be used to implement IMS calls with the electronic device 200 on the main link on the operator's network based on the IMS protocol stack. Among them, IMS calls may include but are not limited to VoLTE, ViLTE, VoNR, ViNR, VoWiFi, ViWiFi, EPS-Fallback and other types of calls.

3. The cloud server 300 may include one or more cloud service function modules. Among them, the one or more cloud service function modules may include an account and wake-up cloud server 1370, a business cloud server 1380, and a network address translation (network address translation, NAT) traversal cloud server 1390. Among them, the account and wake-up cloud server 1370 may include an account server 1371 and a push server 1372. The business cloud server 1380 may include a wise function (WiseFunction) module 1381. The NAT traversal cloud server 1390 may include a terminal router system (TRS) server 1391, a session traversal utilities for NAT (STUN) server 1392 in a NAT environment, and a relay penetration NAT (travelersal using relays around NAT). TURN server 1393, Connector server 1394.

The account server 1371 may be used to authenticate the electronic device 100 or the electronic device 200, where the authentication includes user-level authentication and device-level authentication (for example, verifying the device certificate of the electronic device).

When user-level authentication is used, the account server 1371 may generate an AT to the electronic device 100 or the electronic device 200 after successfully authenticating the user account of the electronic device 100 or the electronic device 200 . Among them, different user accounts generate different ATs. The AT can be used as a resource credential required when the electronic device 100 or the electronic device 200 calls an application programming interface (API) to access resources on the cloud server 300. For example, through the AT, the electronic device 100 can access services. Server 1380.

Taking the account server 1371 to perform user-level authentication on the electronic device 100 as an example, the process of generating AT through user-level authentication can be as follows:

(1) The application client on the electronic device 100 identifies the required user permissions.

(2) The application client on the electronic device 100 redirects the user to the account server 1371 (for example, oAuth server), and carries the permission (scope) list applied to the user in the redirect link.

(3) The electronic device 100 receives the user account and password of the device system input by the user.

(4) The electronic device 100 receives the confirmation input from the user who authorizes the user account and password of the device system to log in to the application client. If the application client is an authorization-free application, the electronic device 100 can directly use the user account and password of the device system to authorize and log in to the application client.

(5) The electronic device 100 can use the user account and password to send a login request to the account server 1371 (eg, oAuth server). After receiving the login request, the account server 1371 (eg, oAuth server) can verify the user account and password on the electronic device 100 . After successful verification, the account server 1371 (for example, oAuth server) can issue an AT and send the AT to the electronic device 100. After the electronic device 100 receives the AT, it can store the AT, for example, into the electronic device 100 In the client's small text file (cookie) or local storage (local stroge). Each time the electronic device 100 requests resources from the cloud server 300, it needs to carry the AT signed by the account server 1371, where the AT can be carried in the header of the HTTP message. After receiving the request from the electronic device 100, the cloud server 300 can first verify the AT carried in the request through the account server 1371. If the verification is successful, the cloud server 300 can return the requested data to the electronic device 100.

Among them, the account server 1371 can generate AT based on the user account and other information. For example, you can use the user information data obtained from the user account, system time, random number, and expiration time, perform RSA asymmetric encryption/AES symmetric encryption on the user information data to obtain an encrypted string, and sign the encrypted string again to obtain a signature. data. Then the signature data and encrypted string are spliced, and finally encoded using the base64 algorithm to obtain the final AT.

For example, the account server 1371 can return AT to the electronic device 100 through an HTTP response, where the content of the HTTP response can be as follows:

In one example, when using device-level authentication, the electronic device (electronic device 100 or electronic device 200) can generate a digest from the device certificate, then use a private key to sign to obtain the signature data, and send the device certificate and signature data to the cloud. Server 300. After receiving the device certificate and signature data, the cloud server 300 can use the public key corresponding to the private key to verify the signature data. If the verification is successful, the cloud server 300 can allow the electronic device 100 to access the data on the cloud server 300 .

In one example, the cloud server 300 can also verify the serial number (SN) code of the electronic device. After the verification is passed, the cloud server 300 can allow the electronic device to access data on the cloud server 300.

Among them, the push server 1372 can be used to wake up the electronic device 200 to start establishing the auxiliary link.

The service cloud server 1380 can be used to implement link addressing, such as session ID exchange for NAT traversal, wake-up docking of wake-up services between the electronic device 100 and the electronic device 200 , and so on. For the session ID exchange process, please refer to subsequent embodiments and will not be described in detail here.

The NAT traversal cloud server 1390 can be used to implement NAT P2P traversal link establishment and transmission between the electronic device 100 and the electronic device 200 based on the NAT traversal signaling between the electronic device 100 or the electronic device 200, or, the electronic device 100 and the electronic device 200. The TURN relay link between devices 200 is established and transmitted. Among them, the specific processes of NAT P2P traversal link establishment and transmission, and TURN relay link establishment and transmission can be referred to subsequent embodiments and will not be described again here.

Figure 13B exemplarily shows the architecture diagram of another communication system provided in the embodiment of the present application.

As shown in Figure 13B, the application processor 1310 of the electronic device 100 may include a FusionCall module 1311, a system sharing module 1313, In-application sharing module 1314 and data channel (DC) module 1315. The modem 1330 of the electronic device 100 may include a data routing module 1331 and a quality of service class identifier (QCI)/5G quality of service class identifier (5QI) configuration module 1332.

Among them, the system sharing module 1313 can be used to provide a system sharing function. The in-application sharing module 1314 may be used to provide functionality for sharing data within the application.

Channel management and routing configuration of data channels can be implemented in the DC module 1315. The DC module 1315 can also realize the transmission of media streams or control streams in the data channel in the main link based on the stream control transmission protocol (stream control transmission protocol, STCP) and datagram transport layer security (DTLS) protocols. . The DC module 1315 may transmit the media stream (including data content of specified data) and the control stream (including control instructions for sharing specified data) to the modem 1330 .

The modem 1330 can realize the transmission of media streams between the electronic device 200 and the data channel of the main link based on the TCP/IP protocol stack. The modem 1330 can implement control flow transmission between the electronic device 200 and the data channel of the main link based on the IMS protocol stack and the TCP/IP protocol stack. The data routing module 1331 in the modem 1330 can implement routing control in the media stream or control stream. The QCI/5QI configuration module 1332 in the modem 1330 may be based on implementing the classification and identification of quality of service levels in media streams or control streams.

The application processor 1340 of the electronic device 200 may include a FusionCall module 1341, a system sharing module 1343, an in-application sharing module 1344, and a data channel (data channel, DC) module 1345. The modem 1360 of the electronic device 200 may include a data routing module 1361 and a quality of service class identifier (QCI)/5G quality of service class identifier (5QI) configuration module 1362.

Among them, the system sharing module 1343 can be used to provide a system sharing function. The in-application sharing module 1344 may be used to provide functionality for sharing data within the application.

Channel management and routing configuration of data channels can be implemented in the DC module 1345. The DC module 1345 can also realize the transmission of media streams or control streams in the data channel in the main link based on the stream control transmission protocol (stream control transmission protocol, STCP) and datagram transport layer security (DTLS) protocols. . The DC module 1345 may transmit the media stream (including the data content of the specified data) and the control stream (including the control instructions when sharing the specified data) to the modem 1360.

The modem 1360 can realize the transmission of media streams between the electronic device 200 and the data channel of the main link based on the TCP/IP protocol stack. The modem 1360 can implement control flow transmission between the electronic device 200 and the data channel of the main link based on the IMS protocol stack and the TCP/IP protocol stack. The data routing module 1361 in the modem 1360 can implement routing control in the media stream or control stream. The QCI/5QI configuration module 1361 in the modem 1360 may be based on implementing the classification and identification of service quality levels in media streams or control streams.

Figure 13C exemplarily shows the architecture diagram of another communication system provided in the embodiment of the present application.

As shown in Figure 13C, the application processor 1310 of the electronic device 100 may include a FusionCall module 1311, a system sharing module 1313, an in-application sharing module 1314, and a data channel (data channel, DC) management module 1316. The modem 1330 of the electronic device 100 may include a data routing module 1331, a quality of service class identifier (QCI)/5G quality of service class identifier (5QI) configuration module 1332, Data channel (DC) protocol module 1333.

The DC management module 1316 can implement channel management and routing configuration of the data channel.

The DC protocol module 1333 can realize the transmission of media streams or control streams in the data channel in the main link based on the stream control transmission protocol (stream control transmission protocol, STCP) and datagram transport layer security (DTLS) protocols. . The DC protocol module 1333 may transmit the media stream (data content including specified data) to the TCP/IP protocol stack of the modem 1330 for processing. The DC protocol module 1333 can transmit the control flow (including control instructions when sharing specified data) to the IMS protocol stack of the modem 1330 for processing. After the IMS protocol stack processes the control flow, it transmits it to the TCP/IP protocol stack for continued processing.

The application processor 1340 of the electronic device 200 may include a FusionCall module 1341, a system sharing module 1343, an in-application sharing module 1344, and a data channel (data channel, DC) management module 1346. The modem 1360 of the electronic device 200 may include a data routing module 1361, a quality of service class identifier (QCI)/5G quality of service class identifier (5QI) configuration module 1362, Data channel (DC) protocol module 1363.

The DC management module 1346 can implement channel management and routing configuration of the data channel.

The DC protocol module 1363 can realize the transmission of the media stream or control stream in the data channel in the main link based on the stream control transmission protocol (stream control transmission protocol, STCP) and the datagram transport layer security (DTLS) protocol. lose. The DC protocol module 1363 may transmit the media stream (data content including specified data) to the TCP/IP protocol stack of the modem 1360 for processing. The DC protocol module 1363 can transmit the control flow (including control instructions when sharing specified data) to the IMS protocol stack of the modem 1360 for processing. After the IMS protocol stack processes the control flow, it transmits it to the TCP/IP protocol stack for continued processing.

For descriptions of other functional modules in the electronic device 100 and the electronic device 200 , reference may be made to the above-mentioned embodiment shown in FIG. 13B , and details will not be described again here.

The following describes the process of establishing a data transmission link between the electronic device 100 and the electronic device 200 in the embodiment of the present application.

In the embodiment of the present application, when the electronic device 100 and the electronic device 200 are talking, the data transmission link may be established in the following ways:

1. Reuse the main link of the call.

For example, when the call between the electronic device 100 and the electronic device 200 is an IMS call, the IMS protocol is used. The original RTP message can be expanded to add message types for transmitting shared data. Alternatively, the synchronization source identifier (SSRC) in the RTP message can be used to mark whether the RTP message carries the voice/video frame data of the call or the designated data shared by the electronic device 100 to the electronic device 200 . In this method, the core network equipment of the cellular network equipment needs to enter the transparent transmission mode and does not filter or transcode the RTP packets.

2. Use the data channel of the call link.

For example, the call link established between the electronic device 100 and the electronic device 200 using the IMS protocol includes a data channel. This data channel is a data transmission channel other than the call signaling QCI5 channel and the audio QCI1/audio QCI2 channel. Among them, the introduction of this data channel can refer to the protocol specification TS 26.114, which will not be repeated here.

3. Establish an auxiliary link.

3.1 Electronic device 100 and electronic device 200 can negotiate to establish a secondary link by carrying connection information through the RTCP packet of the main call link.

Among them, the text data of the connection information can be carried in an RTCP source description (SDES) packet and sent to the electronic device 200 . The connection information may include communication ID, IP address and other information used for NAT traversal. Among them, the connection information can carry the canonical name (CNAME) item in the SDES entry (items) field.

For example, as shown in Figure 14A, RTCP data may include a header and one or more chunks. in,

The header (header) can include a version number (V) field, a source description item number (SC) field, a packet type (packet type, PT) field, a length (length) field, and padding (P). ) field.

Among them, the chunk can include source identifiers (synchronous source identifiers (SSRC) or special source identifiers (CSRC)) and source description items (SDES items). Among them, the value of the version number field can be "2", and the value of the PT field can be "202" (used to indicate that the RTCP data packet is an SDES packet.

As shown in Figure 14B, the SDES items field may include a CNME field (the value may be "1"), a length field (for example, the length may be 36 bits), and connection information. The length field may be used to indicate the The data length of the connection information.

3.2 Electronic device 100 and electronic device 200 can address each other's communication ID through cloud server 300. Electronic device 100 and electronic device 200 can establish an auxiliary link between electronic device 100 and electronic device 200 based on the communication IDs of both parties.

Figure 15 illustrates an auxiliary link establishment process provided in the embodiment of the present application.

As shown in Figure 15, the link establishment process may include the following three stages: registration/login stage, addressing stage, and link establishment stage. The registration/login phase includes the following steps S1501 to S1502, the addressing phase includes the following steps S1503 to S1506, and the link establishment phase includes the following step S1507. in:

S1501. The electronic device 100 binds, registers and logs in the ID group A and the communication identification A of the electronic device 100 to the cloud server 300 and saves them.

S1502. The electronic device 200 binds and registers the ID group B and the communication identification B of the electronic device 200 to the cloud server 300.

The query request A can be used to obtain the communication identification B of the electronic device 200 .

S1503. The electronic device 100 may send a query request A to the cloud server 300, where the query request A carries all or part of the information of the ID group B of the electronic device 200.

S1504. The cloud server 300 may return the communication identification B of the electronic device 200 to the electronic device 100.

S1505. The electronic device 200 may send a query request B to the cloud server 300. The query request B carries all or part of the information of the ID group A of the electronic device 100. The query request B can be used to query the communication identification A of the electronic device 100 .

S1506. The cloud server 300 may return the communication identification A of the electronic device 100 to the electronic device 200.

S1507. The electronic device 100 and the electronic device 200 establish an auxiliary link based on the communication identifier A and the communication identifier B. The auxiliary link includes an IP direct link, a NAT penetration point-to-point link, or a server relay link, etc.

The cloud server 300 shown in FIG. 15 may specifically be the business cloud server 1380 in the cloud server 300 .

The above-mentioned auxiliary link establishment process will be detailed below in conjunction with the principle shown in Figure 16 .

FIG. 16 is a schematic diagram illustrating the principle in which the electronic device 100 obtains the communication identification of the electronic device 200 from the business cloud server 1380 in the implementation of this application.

As shown in Figure 16, the electronic device 100 and the electronic device 200 can register and log in to the business cloud server 1380 after binding their respective ID groups and communication identifiers. That is, the electronic device 100 can bind the ID group A and the communication identification A of the electronic device 100 into binding information A, register and log in to the business cloud server 1380 and save it. The electronic device 200 can bind the ID group B and the communication identification B of the electronic device 200 into binding information B, register it on the service server 1380 and save it. Among them, the ID group may include one or a combination of the following: one or more phone numbers, one or more OTT IDs (for example, user ID of an instant messaging application, email address, etc.), and so on.

In one example, the binding information can be registered and logged into the business server 1380 and saved after being deprived of privacy (for example, hash operation).

The binding information saved on the business server 1380 may be temporary, and the business server 1380 controls whether to delete it, or it may be accurate, and the electronic device (electronic device 100 or electronic device 200) controls whether to delete it.

For temporary ones, the business server 1380 can set a session time threshold (session timer) for the session with the electronic device, for example, 10 minutes. After the session duration between the business server 1380 and the electronic device exceeds the session timer, The service server 1380 can automatically delete the binding information of the electronic device, or set it to an inactive state. The electronic device can refresh the session and extend the session timer before the session exceeds the session timer.

For accuracy, the electronic device can decide when to delete the binding information. For example, the electronic device can request the service server 1380 to delete the saved binding information after the call ends or after the network status changes.

After the binding information A of the electronic device 100 and the binding information B of the electronic device 200 are saved on the business cloud server 1380, the process of the electronic device 100 querying the communication identification of the electronic device 200 from the business cloud server 1380 may include the following steps:

1. The electronic device 100 obtains all or part of the information in the ID group A of the electronic device 200 .

2. The electronic device 100 sends a query request to the service server 1380 to query the communication identification B of the electronic device 200 . The query request carries all or part of the information in ID group B of the electronic device 200 .

3. After receiving the query request of the electronic device 100, the business server 1380 queries the communication identification B of the electronic device 200 based on all or part of the information in the ID group B of the electronic device 200, and returns the electronic device 200 to the electronic device 100. Communication identification B.

In one example, the communication identification may be a session identification (sessionID) generated by the NAT traversal cloud server 1390 for the electronic device (electronic device 100 or electronic device 200). The electronic device can perform session communication with the NAT traversal cloud server 1390 through the session identifier. The electronic device 100 and the electronic device 200 are addressed through the business cloud server 1380 and exchange session IDs of both parties. After the electronic device 100 and the electronic device 200 obtain the other party's session ID, they can perform NAT traversal through the NAT traversal cloud server 1390 to obtain the other party's NAT public network information (including the NAT public network address and port number) to establish a P2P link, or obtain Go to the other party's relay address and establish a server relay link.

In one example, when the electronic device 100 and the electronic device 200 are in the same local area network, the communication identifier can be the IP address of the electronic device in the local area network. After the electronic device 100 and the electronic device 200 obtain the other party's local area network IP address, they can directly use Establish an auxiliary link (including P2P link or server relay link) with the IP address in the other party's LAN. At this time, the electronic device 100 and the electronic device 200 can obtain each other's IP address in the local area network through the cloud server 300, or they can obtain each other's IP address in the local area network through the routing device in the local area network.

In an example, when the electronic device 100 and the electronic device 100 use a network protocol such as Internet Protocol Version 6 (IPV6), the communication identifier may be the IPV6 address of the electronic device (electronic device 100 or electronic device 200). . After the electronic device 100 and the electronic device 200 obtain the other party's IPV6 address information (including the IPV6 address and port number) through the cloud server 300, they directly establish an auxiliary link (including a P2P link or a server) based on the other party's IPV6 address information. relay link).

The following is a detailed introduction to the addressing process in an auxiliary link provided in the embodiment of the present application.

Figure 17 shows a schematic diagram of the addressing process in an auxiliary link provided in this embodiment of the present application.

As shown in Figure 17, the addressing process may include the following four stages: authentication and generation of point-to-point token (P2P Token) stage, binding or refreshing stage, addressing stage, and session end stage. The authentication and P2P Token generation phase may include steps S1701 to S1702, the binding or refreshing phase may include steps S1703 to S1704, and the addressing phase may include steps S1705 to S1704. S1713, the session end phase includes steps S1714 to S1715. in:

S1701. The electronic device 100 performs authentication with the business cloud server 1380 (including user-level authentication or device-level authentication).

For the authentication process of the electronic device 100 to the business cloud server 1380, reference may be made to the authentication process of the electronic device 100 to the account server 1371 in the embodiment shown in FIG. 13A, which will not be described again.

S1702. After the business cloud server 1380 passes the authentication of the electronic device 100, it can return the point-to-point token A (P2P Token-A) to the electronic device 100.

Among them, the P2P Token-A can be used by the electronic device 100 to access the data of the NAT traversal cloud server 1390 and request the service function on the NAT traversal cloud server 1390.

After obtaining the P2P Token-A, the electronic device 100 can send a long connection request to the NAT traversal cloud server 1390, requesting to establish a long connection with the NAT traversal cloud server 1390. Among them, the long connection request carries the P2P Token-A. The NAT traversal cloud server 1390 can request the business cloud server 1380 to verify the P2P Token-A. If the verification is successful, the NAT traversal cloud server 1390 can generate the session ID A (sessionID-A) of the long connection session for the electronic device 100 to the electronic device 100. Equipment 100.

S1703. The electronic device 100 sends the binding information A to the business cloud server 1380 for storage. The binding information A includes the ID group A of the electronic device 100 and the session ID A (sessionID-A) returned by the NAT traversal cloud server 1390 to the electronic device 100 .

The ID group A may include one or more combinations of the following IDs of the electronic device 100: one or more phone numbers, one or more application account IDs (for example, user IDs of instant messaging applications, email addresses, etc. ),etc.

In one example, the electronic device 100 compresses the ID of the electronic device 100 and puts it into ID group A. For example, the electronic device 100 can run two SIM cards, and the mobile phone numbers of these two SIM cards are mobile phone number A1 and mobile phone number A2 respectively. The electronic device 100 can perform a hash operation on the mobile phone number A1 to obtain a hash value 1, and perform a hash operation on the mobile phone number A2 to obtain a hash value 2. And put hash value 1 and hash value 2 into ID group A.

Optionally, S1704, the electronic device 100 can update the binding information A, and save the updated binding information A to the business cloud server 1380.

The electronic device 100 may update the binding information A when the information in the ID group A and/or the session ID A assigned to the electronic device 100 by the NAT traversal cloud server 1390 changes, and save the updated binding information A. Go to business cloud server 1380.

For example, the electronic device 100 may operate with 2 SIM cards, SIM Card 1 and SIM Card 2. Among them, SIM card 1 corresponds to mobile phone number A1, and SIM card 2 corresponds to mobile phone number A2. The electronic device 100 can put the mobile phone number A1 and the mobile phone number A2 into the ID group A and bind the session identifier A to generate the binding information A, and send the binding information A to the business cloud server 1380. When the SIM card 1 on the electronic device 100 is disconnected or the mobile phone number A1 is out of service, etc., it cannot function normally, but when the SIM card 2 works normally, the electronic device 100 can put the mobile phone number A2 into the ID group A and the session identifier. A binds, generates updated binding information A, and sends the updated binding information A to the business cloud server 1380.

For another example, when the long connection between the electronic device 100 and the NAT traversal cloud server 1390 is disconnected and reconnected, the NAT traversal cloud server 1390 may generate a new session identifier A for the electronic device 100 . The electronic device 100 may bind the ID group A and the new session identification A to generate updated binding information A, and send the updated binding information A to the business cloud server 1380 .

S1705. The electronic device 100 can send a query request A to the business cloud server 1380. The query request A can include all or part of the information in the ID group B of the electronic device 200. The query request A can be used to query the session of the electronic device 200. Logo B.

Among them, ID group B may include one or a combination of the following IDs of the electronic device 200: one or more phone numbers, one or more application account IDs (for example, user IDs of instant messaging applications, email addresses, etc. wait wait wait.

All or part of the information in ID group B may refer to all IDs in ID group B or one or more IDs.

S1706. After receiving the query request sent by the electronic device 100, the business cloud server 1380 may determine whether the session identifier B of the electronic device 200 is matched.

S1707. After the business cloud server 1380 matches the session identifier B of the electronic device 200, it may return the session identifier B of the electronic device 200 to the electronic device 100.

Optionally, S1708, when the business cloud server 1380 does not query the session identifier B of the electronic device 200, the business cloud server 1380 may determine whether the electronic device 200 needs to be woken up.

Among them, when the electronic device 200 is in a sleep state or a non-awakened state such as a screen-off state, the electronic device 200 may not be able to access the business cloud. Server 1380. Therefore, the business cloud server 1380 can wake up the electronic device 200 to communicate with the business server 1380 .

Optionally, S1709, if the electronic device 200 needs to be woken up, the business cloud server 1380 can wake up the electronic device 200 through the push server 1372.

Optionally, S1710, if there is no need to wake up the electronic device 200, the business cloud server 1380 can return the failure reason to the electronic device 200.

For example, the failure reasons may include the electronic device 200 not waking up, the electronic device 200 being powered off, and so on.

Optionally, S1711, after waking up the electronic device 200, the electronic device 200 can authenticate with the business cloud server 1380.

For the authentication process of the electronic device 200 by the business cloud server 1380, reference can be made to the authentication process of the electronic device 100 by the business cloud server 1380 in the above embodiment, which will not be described again here.

Optionally, in S1712, the business cloud server 1380 can return a point-to-point token B (P2P Token-B) to the electronic device 200.

Among them, the P2P Token-B can be used by the electronic device 200 to access the data of the NAT traversal cloud server 1390 and request the service function on the NAT traversal cloud server 1390.

After obtaining the P2P Token-B, the electronic device 100 can send a long connection request to the NAT traversal cloud server 1390, requesting to establish a long connection with the NAT traversal cloud server 1390. Among them, the long connection request carries the P2P Token-B. The NAT traversal cloud server 1390 can request the business cloud server 1380 to verify the P2P Token-B. If the verification is successful, the NAT traversal cloud server 1390 can generate the session ID B (sessionID-B) of the long connection session for the electronic device 200 to the electronic device 200. Equipment 100.

Optionally, S1713, the electronic device 200 sends the binding information B to the business cloud server 1380 for storage. The binding information B includes the ID group B of the electronic device 100 and the session identifier B returned by the NAT traversal cloud server 1390 to the electronic device 200 .

After the electronic device 200 uploads the binding information B to the business cloud server 1380, the business cloud server 1380 may return the session identifier B of the electronic device 200 to the electronic device 100.

S1714. After receiving the session identifier B of the electronic device 200, the electronic device 100 can actively request to release the long connection session with the business cloud server 1380.

Optionally, in S1715, the business cloud server 1380 can also automatically release the session with the electronic device 100 after sending the session identifier B of the electronic device 200 to the electronic device 100.

The following describes the functional module interaction process between the electronic device 100 and the electronic device 200 in the embodiment of the present application.

Figure 18 shows the functional module interaction process between the electronic device 100 and the electronic device 200 in the embodiment of the present application.

As shown in Figure 18, the electronic device 100 may include a FusionCall module 1311 and a Network Address Translation Service (NatService) module 1312. The electronic device 200 may include a FusionCall module 1341 and a NatService module 1342. Among them, the interaction process between the above functional modules can be as follows:

S1801. FusionCall module 1311 initializes the transmission service of NatService module 1312.

For example, the FusionCall module 1311 can initialize the transmission service in the NatService module 1312 through the function "RfcManager.int".

S1802. The FusionCall module 1311 applies to the NatService module 1312 for the session identifier A of the long connection channel.

For example, the FusionCall module 1311 can apply to the NatService module 1312 for the session ID A of the long connection channel with the NAT traversal cloud server 1390 through the function "allocTunnelID(p2ptoken, cb)". Among them, the FusionCall module 1311 can provide the P2P Token-A generated by the business cloud server 1380 for the electronic device 100 to the NatService module 1312 through the function "allocTunnelID (p2ptoken, cb)". The NatService module 1312 can carry the P2P Token-A when sending a long connection request to the NAT traversal cloud server 1390.

S1803. The NatService module 1312 returns the session identifier A of the long connection channel to the FusionCall module 1311.

For example, after returning the session ID A of the long connection channel to the NatService module 1312, the NAT traversal cloud server 1390 can return the session ID A to the FusionCall module 1311 through the function "cb(TunnelID)". The parameter "TunnelID" is session ID A.

S1804. The FusionCall module 1311 requests the NatService module 1312 to create a session with the electronic device 200.

Among them, the FusionCall module 1311 can provide the session identifier A of the electronic device 100 and the session identifier B of the electronic device 200 to the NatService module 1312, and request the NatService module 1312 to establish a transmission session with the electronic device 200.

The NatService module 1312 may send the session identifier B of the electronic device 200 to the NAT traversal cloud server 1390, and request the NAT traversal cloud server 1390 to complete the establishment of a transmission session between the electronic device 100 and the electronic device 200.

For example, the FusionCall module 1311 can request the NatService module 1312 to establish a transmission session with the electronic device 200 through the function "createSessionByTunnelID (p2ptoken, remoteTunnelID, flag, IsessionCallback callback)". Among them, the parameter "p2ptoken" in the function "createSessionByTunnelID (p2ptoken, remoteTunnelID, flag, IsessionCallback callback)" is the above-mentioned P2P Token-A, and the parameter "remoteTunnelID" is the session ID B of the electronic device 200.

S1805. The NatService module 1312 returns the transmission session creation result to the FusionCall module 1311.

The transfer session creation result may include creation success and creation failure.

For example, the NatService module 1312 can return the session creation result to the FusionCall module 1311 through the function "ISessionCallback". Among them, the function "ISessionCallback" can include the creation success function "onSessionCreate(Session session)" and the creation failure function "onconnectorState(int errorCode, String desc)".

S1806. After the transmission session is successfully created, the FusionCall module 1311 can add a listening event to the NatService module 1312.

Among them, after the NatService module 1312 adds a listening event, it can be used to monitor the data sent by the electronic device 200 to the electronic device 100 on the transmission session.

For example, the FusionCall module 1311 can add a listening event to the NatService module 1312 through the function "addListener (p2ptoken, ISessionListener listener)" to listen to data from the electronic device 200 on the transmission session. Among them, the NatService module 1312 can return the listening result of the listening event to the FusionCall module 1311 through the function "ISessionListener listener".

S1807. The FusionCall module 1341 on the electronic device 200 provides sending data to the NatService module 1342.

S1808. The NatService module 1342 sends the data to the NatService module 1312 on the electronic device 100 through P2P direct transmission/server relay, etc.

S1809. After receiving the data sent by the NatService module 1342, the NatService module 1312 may return the received data to the FusionCall module 1311.

For example, the NatService module 1312 can use the function "onAcceptBytes(byte[]data)" to return to the FusionCall module 1311 the data sent by the electronic device 200 after being successfully monitored. The NatService module 1312 can use the function "onLisetenError(int errorCode, String desc)" to return the reason for the monitoring failure (for example, error code "errorCode") to the FusionCall module 1311.

S1810. FusionCall module 1311 provides sending data to NatService module 1312.

For example, the FusionCall module 1311 can provide the NatService module 1312 with data to be sent to the electronic device 200 through the function "Session.sendBytes(byte[]data)".

S1811. The NatService module 1312 sends the session transmission data to the NatService module 1342 on the electronic device 200 through P2P direct transmission/server relay, etc.

S1812. After receiving the data sent by the NatService module 1312 on the electronic device 100, the NatService module 1342 on the electronic device 200 may return the received data to the FusionCall module 1341.

S1813. The FusionCall module 1311 removes the listening event from the NatService module 1312.

Among them, the FusionCall module 1311 can remove the listening event to the NatService module 1312 after the data between the electronic device 100 and the electronic device 200 is completed.

For example, the FusionCall module 1311 can remove the listening event to the NatService module 1312 through the function "removeListener (SessionListener listener)".

S1814. The FusionCall module 1311 requests the NatService module 1312 to release the session.

For example, the FusionCall module 1311 can request the NatService module 1312 to release the transmission session with the electronic device 200 through the function "releaseSession (Session session)".

S1815. The FusionCall module 1311 requests the NatService module 1312 to destroy the transmission service.

For example, the FusionCall module 1311 can request the destruction of the initialized transmission service on the NatService module 1312 through the function "RfcManager.free(Session session)".

The following describes the P2P direct link establishment process in the embodiment of this application.

Figure 19 shows a schematic diagram of a P2P direct link establishment process provided in the embodiment of the present application.

As shown in Figure 19, the electronic device 100 may include a FusionCall module 1311 and a NatService module 1312. NAT traversal cloud server The server 1390 may include a TRS server 1391, a Connector server 1394, a TURN server 1393, and a STUN server 1392.

The P2P direct link establishment process may include the following stages:

1. Obtain TRS route: step S1901 to step S1902.

2. Obtain the local session ID (sessionID): step S1903 to step S1904.

3. Exchange session ID: step S1905.

4.NAT traversal process.

Among them, the NAT traversal stage includes:

4.1. Obtain the local NAT public network information: Step S1906 to Step S1907.

4.2. NAT public network information exchange at both ends: step S1908 to step S1910.

4.3. Connection detection and transmission channel establishment: step S1911.

Steps S1901 to S1911 may be as follows:

S1901. The NatService module 1312 may send a route acquisition request to the TRS server 1391.

The route acquisition request is used to obtain the address information of the Connector server 1394, the address information of the TURN server 1393, and the address information of the STUN server 1392. The address information may include an IP address and a port number. The route acquisition request may carry the P2P Token-A sent by the service server 1380 to the electronic device 100.

For example, the NatService module 1312 can obtain the routing information on the TRS server 1391 through the interface "getroute" provided by the TRS server 1391. Among them, the interface protocol of the TRS server 1391 can be transmission control protocol (transmission control protocol, TCP) or hyper text transfer protocol (hyper text transfer protocol over secure socket layer, HTTPS), etc.

S1902. After receiving the route acquisition request, the TRS server 1391 may return routing information to the NatService module 1312.

The routing information includes obtaining the address information of the Connector server 1394, the address information of the TURN server 1393, and the address information of the STUN server 1392. The address information may include an IP address and a port.

S1903. The NatService module 1312 logs in to the TRS server 1391 through a long connection.

Among them, when the NatService module 1312 logs in to the TRS server 1391 through a long connection through the interface provided by the Connector server 1394, it sends P2P Token-A to the Connector server 1394. The interface protocol of the Connector server 1394 may be TCP or transport layer security (TLS). When the interface provided by the Connector server 1394 transmits P2P Token-A to the Connector server 1394, the data reading and writing method of P2P Token-A can be the binary big-endian reading and writing method, that is, the most significant byte of P2P Token-A is stored in the low address.

S1904. The Connector server 1394 returns the session ID A (sessionID-A) to the NatService module 1312.

S1905. FusionCall module 1311 exchanges session identifiers of both parties with electronic device 200 through service server 1380.

For specific content, reference may be made to the aforementioned embodiments shown in FIGS. 15 to 17 , which will not be described again here.

S1906. The NatService module 1312 sends an acquisition request for the NAT public network information of the electronic device 100 to the STUN server 1392.

Among them, the request for obtaining the NAT public network information of the electronic device 100 carries the above-mentioned P2P Token-A.

For example, the NatService module 1312 can send a request for obtaining the NAT public network information of the electronic device 100 to the STUN server 1392 through the function "Binding" through the interface provided by the STUN server 1392. The interface protocol of the STUN server 1392 may be the STUN protocol or the datagram transport layer security (DTLS) protocol.

S1907. The STUN server 1392 returns the NAT public network information A of the electronic device 100 to the FusionCall module 1311.

The NAT public network information A may include the public network IP address of the electronic device 100 and the port number from the public network to the intranet.

In one example, the STUN server 1392 may compress or encrypt the NAT public network information A of the electronic device 100 and return it to the FusionCall module 1311. For example, the NAT public network information A can be XORed and then returned to the FusionCall module 1311.

S1908. The NatService module 1312 sends message A to the Connector server 1394.

The message A carries the NAT public network information A of the electronic device 100 and the session ID-B (sessionID-B) of the electronic device 200 . The session ID-B (sessionID-B) of the electronic device 200 is a session ID generated by the Connector server 1394 for the electronic device 200 . The electronic device 200 can conduct a long connection session with the Connector server 1394 based on sessionID-B.

S1909. The Connector server 1394 forwards the NAT public network information A of the electronic device 100 in the message to the electronic device 200.

S1910. The Connector server 1394 may send the NAT public network information B of the electronic device 200 to the NatService module 1312.

The electronic device 200 may also send a request for obtaining the NAT public network information of the electronic device 200 to the STUN server 1392. The request for obtaining the NAT public network information of the electronic device 200 carries the P2P Token-B assigned to the electronic device 200 by the business cloud server 1380. The STUN server 1392 may return the NAT public network information B of the electronic device 200 to the electronic device 200 . The NAT public network information B includes the public network IP address of the electronic device 200 and the port number from the public network to the intranet. Electronic device 200 may send message B to Connector server 1394. Message B carries the session identifier A of the electronic device 100 and the NAT public network information B of the electronic device 200 . After receiving the message B, the Connector server 1394 can forward the NAT public network information B of the electronic device 200 to the NatService module 1312 on the electronic device 100 .

S1911. After receiving the NAT public network information B of the electronic device 200, the NatService module 1312 can perform connection detection with the electronic device 200 based on the NAT public network information B and establish a P2P transmission link.

The electronic device 100 can transmit specified data content selected by the user to be shared with the electronic device 200 based on the P2P transmission link, as well as control information (such as withdrawal instructions, file destruction instructions, etc.) to the electronic device 200 . The electronic device 200 may also return control information (eg, confirm receipt of instructions, refuse to receive instructions, etc.) or other data to the electronic device 100 based on the P2P transmission link.

The following describes the relay link establishment process in the embodiment of this application.

Figure 20 shows a schematic diagram of a relay link establishment process provided in the embodiment of the present application.

As shown in Figure 20, the electronic device 100 may include a FusionCall module 1311 and a NatService module 1312. The NAT traversal cloud server 1390 may include a TRS server 1391, a Connector server 1394, a TURN server 1393, and a STUN server 1392.

The trunk link establishment process may include the following stages:

1. Obtain TRS route: step S2001 to step S2002.

2. Obtain the local session ID (sessionID): step S2003 to step S2004.

3. Exchange session ID: step S2005.

4. Relay process. Among them, the NAT traversal stage includes:

4.1. Channel allocation: step S2006 to step S2007.

4.2. Relay address exchange at both ends: step S2008 to step S2010.

4.3. Create license: step S2011 to step S2012.

4.4. Send/receive data: step S2013 to step S2016.

Step S2001 to step S2016 may be as follows:

S2001. The NatService module 1312 may send a route acquisition request to the TRS server 1391.

S2002. After receiving the route acquisition request, the TRS server 1391 may return routing information to the NatService module 1312.

S2003. The NatService module 1312 logs in to the TRS server 1391 through a long connection.

S2004. The TRS server 1391 returns the session ID A (sessionID-A) to the NatService module 1312.

S2005. FusionCall module 1311 exchanges session identifiers of both parties with electronic device 200 through service server 1380.

For steps S2001 and S2005, reference may be made to steps S1901 to S1905 in the embodiment shown in FIG. 19 , which will not be described again here.

S2006. The NatService module 1312 sends an acquisition request for the relay address of the electronic device 100 to the TURN server 1393.

Among them, the acquisition request for the relay address of the electronic device 100 carries the above-mentioned P2P Token-A.

For example, the NatService module 1312 may send an acquisition request for the relay address of the electronic device 100 to the TURN server 1393 through the function "Allocation" or "Refresh" in the interface provided by the TURN server 1393. The interface protocol of the TURN server 1393 may be the TURN protocol or the datagram transport layer security (DTLS) protocol. The function "Allocation" or "Refresh" can read and write the data of P2P Token-A in binary big-endian way, that is, the most significant byte of P2P Token-A is stored in the low address. The data format of P2P Token-A can be tag length value (TLV) format.

S2007. The TURN server 1393 returns the relay address A of the electronic device 100 to the FusionCall module 1311.

In an example, the STUN server 1392 may compress or encrypt the relay address A of the electronic device 100 and return it to the FusionCall module 1311. For example, the relay address A can be XORed and then returned to the FusionCall module 1311.

S2008. The NatService module 1312 sends message C to the Connector server 1394.

The message C carries the relay address A of the electronic device 100 and the session ID-B (sessionID-B) of the electronic device 200 . The session ID-B (sessionID-B) of the electronic device 200 is a session ID generated by the Connector server 1394 for the electronic device 200 . The electronic device 200 can conduct a long connection session with the Connector server 1394 based on sessionID-B.

For example, the NatService module 1312 can send message A to the Connector server 1394 through the function "SendMsg()" in the interface provided by the Connector server 1394. Among them, the data in the message C can be read and written in binary big-endian format. The interface protocol of the Connector server 1394 may be the TCP protocol or the TLS protocol.

S2009. The Connector server 1394 forwards the relay address A of the electronic device 100 in the message C to the electronic device 200.

S2010. The Connector server 1394 may send the relay address B of the electronic device 200 to the NatService module 1312.

The electronic device 200 may also send an acquisition request for the relay address of the electronic device 200 to the TURN server 1393. The request for obtaining the relay address of the electronic device 200 carries the P2P Token-B assigned to the electronic device 200 by the business cloud server 1380. The TURN server 1393 may return the relay address B of the electronic device 200 to the electronic device 200 . Electronic device 200 may send message D to Connector server 1394. The message D carries the session identifier A of the electronic device 100 and the relay address of the electronic device 200 . After receiving the message B, the Connector server 1394 may forward the relay address B of the electronic device 200 to the NatService module 1312 on the electronic device 100 .

S2011. The NatService module 1312 may send the license creation request A to the TURN server 1393.

Among them, the license creation request A may carry the P2P Token-A of the electronic device 100 and the relay address B of the electronic device 200. The permission creation request A may be used to request the TURN server 1393 to create a relay forwarding link from the electronic device 100 to the electronic device 200 .

For example, the NatService module 1312 can send the permission creation request A to the TURN server 1393 through the function "CreatePermission()" based on the TURN protocol or the DTLS protocol on the interface of the TURN server 1393.

S2012. The electronic device 200 may send the license creation request B to the TURN server 1393.

Among them, the license creation request B may carry the P2P Token-B of the electronic device 200 and the relay address A of the electronic device 100. This permission creation request B may be used to request the TURN server 1393 to create a relay forwarding link from the electronic device 200 to the electronic device 100 .

For example, the electronic device 200 can send the permission creation request B to the TURN server 1393 through the function "CreatePermission()" based on the TURN protocol or the DTLS protocol on the interface provided by the TURN server 1393.

S2013. The NatService module 1312 can send data packet A to the TURN server 1393.

The data packet A carries the session ID B (sessionID-B) of the electronic device 200, the relay address B and the data A of the electronic device 200.

For example, the NatService module 1312 can send the data packet A to the TURN server 1393 through the function "Send()" on the interface provided by the TURN server 1393. Among them, the data in the data packet A can be read and written in the binary big-endian reading and writing mode, that is, the most significant byte of the data in the data packet A is stored at the low address. The data format of packet A may be tag length value (TLV) format.

S2014. The TURN server 1393 may forward the data packet A to the electronic device 200.

After receiving the data packet A, the TURN server 1393 can parse out the session identifier B of the electronic device 200 and the relay address B of the electronic device 200 carried in the data packet A. Therefore, the TURN server 1393 can determine that the data in the data packet A is sent to the electronic device 200 based on the session identifier B of the electronic device 200 and the relay address B of the electronic device 200 . The TURN server 1393 forwards the data A in the data packet A to the electronic device 200 .

S2015. The electronic device 200 can send data packet B to the TURN server 1393.

The data packet B carries the session ID A (sessionID-A) of the electronic device 100, the relay address B and the data B of the electronic device 200.

S2016. The TURN server 1393 can forward the data packet B to the NatService module 1312.

After receiving the data packet B, the TURN server 1393 can parse out the session identifier A of the electronic device 100 and the relay address A of the electronic device 100 carried in the data packet B. Therefore, the TURN server 1393 can determine that the data in the data packet B is sent to the electronic device 100 based on the session identifier A of the electronic device 100 and the relay address A of the electronic device 100 . The TURN server 1393 may forward data B in the data packet B to the electronic device 100 .

For example, the NatService module 1312 can receive the data B through the function "Recv()" on the interface provided by the TURN server 1393. Among them, the reading and writing method of the data B can be the binary big-endian reading and writing method, that is, the most significant byte of the data B is stored in the low address. The data format of packet A may be tag length value (TLV) format.

The relay address A of the electronic device 100 can be used to instruct the TURN server 1393 to provide a communication interface for the electronic device 200 The IP address of access terminal A. The relay address B of the electronic device 200 may be used to indicate the IP address of the access terminal B on the TURN server 1393 that provides a communication interface for the electronic device 200 . In an example, the IP address of access terminal A and the IP address of access terminal B may be the same. In an example, the IP address of access terminal A and the IP address of access terminal B may also be different.

The following introduces a device wake-up process provided in the embodiment of this application.

Figure 21 shows a schematic diagram of a device wake-up process in an embodiment of the present application.

As shown in Figure 21, taking the cloud server 300 to wake up the electronic device 200 as an example, the electronic device 200 may include applications, mobile services (for example, Huawei mobile service (HMS), etc.), push agents (push agents), etc. agent). The cloud server 300 may include a push server and a business cloud server 1380. The device wake-up process may include the following steps:

S2101. The integrated call application can request a push token from the mobile service.

S2102. The mobile service can send a broadcast to the push agent.

S2103. After receiving the broadcast, the push agent can request the push Token from the push server 1372.

S2104. The push server 1372 returns push token A (push Token-A) to the push agent.

Among them, the push server 1372 can authenticate the electronic device 100, and after successful authentication, return push token-B to the push agent. The authentication includes user-level authentication or device-level authentication. For the authentication process of the electronic device 100, reference can be made to the aforementioned embodiment shown in FIG. 13A, which will not be described again here.

S2105, the push agent can return the push Token to the converged call application.

S2106. The integrated call application can save push Token-B to the application server.

S2107. The converged call application is closed and the long connection with the application server is disconnected.

Among them, due to the electronic device 200 locking or extinguishing the screen or the user actively closing the application, etc., the converged call application is closed, thereby disconnecting the long connection with the business cloud server 1380 .

S2108. The business cloud server 1380 may determine that the electronic device 200 needs to be woken up.

Wherein, after receiving the query request A for querying the session ID of the electronic device 200, the business cloud server 1380 may query whether the session ID of the electronic device 200 is stored on the business cloud server 1380. If the business cloud server 1380 does not query the session ID of the electronic device 200 and the long connection between the business cloud server 1380 and the electronic device 200 has been disconnected, the business cloud server 1380 may determine that the electronic device 200 needs to be woken up.

In one example, when the business cloud server 1380 does not query the session ID of the electronic device 200, the business cloud server 1380 can send a notification to the electronic device 100. The notification is used to notify the electronic device 100 that the electronic device 200 has not woken up. The electronic device 100 may receive an input from the user confirming to wake up the electronic device 200, and in response to the input, the electronic device 100 may send a wake-up indication to the business cloud server 1380. After receiving the wake-up instruction, the business cloud server 1380 may determine that the electronic device 200 needs to be woken up.

S2109. After determining that the electronic device 200 needs to be woken up, the business cloud server 1380 may send a wake-up instruction to the push server 1372. Among them, the wake-up command carries push Token-B.

S2110. After receiving the push server 1372, the business cloud server 1380 can send a wake-up message to the push agent.

S2111, the push agent can wake up the integrated call application to log in to the business cloud server 1380 through a long connection after receiving the wake-up message.

In one example, the push Token-B carries the application identification of the converged call application and the device identification of the electronic device 200 . After the push server 1372 receives the wake-up instruction carrying push Token-B, the push server 1372 can send a wake-up message to one or more push agents that have established long connections with the push server 1372, where the wake-up message includes the following push Token-B. After receiving the wake-up message, the push agent on the electronic device 200 can determine whether the device identification carried in the push Token-B is the device identification of the electronic device 200. If so, the push agent on the electronic device 200 can wake up the push Token. -The converged call application indicated by the application identifier in B.

In one example, when requesting a push Token from the push server 1372, the push agent of the electronic device 200 may send the application identification of the fused call application and the device identification of the electronic device 200 to the push server 1372. The push server 1372 may generate push Token-B based on the application identification of the integrated call application and the device identification of the electronic device 200 . The push server 1372 may bind the application identification of the converged calling application, the device identification of the electronic device 200 and the push Token-B into a mapping relationship and save them. After receiving the wake-up instruction, the push server 1372 may determine from the local storage mapping relationship that the converged call application on the electronic device 200 needs to be awakened based on the push Token-B in the wake-up instruction. The push server 1372 may send a wakeup message to the push agent of the electronic device 200 . The wake-up message carries the application identification of the converged calling application, or the wake-up message carries the application identification of the converged calling application and the device identification of the electronic device 200 . After receiving the wake-up message, the push agent of the electronic device 200 can wake up the human fusion call application of the electronic device 200 .

In one example, the electronic device 200 may not save the push Token-B to the business cloud server 1380. The electronic device 100 may obtain the push Token-B of the electronic device 200 before waking up the electronic device 200, and the electronic device 100 may receive the user The input to wake up the electronic device 200 is confirmed, and in response to the input, the electronic device 100 may send a wake-up indication to the business cloud server 1380 . Among them, the wake-up instruction carries the push Token-B of the electronic device 200. After receiving the wake-up instruction, the business cloud server 1380 may determine that the electronic device 200 needs to be woken up, and send the above-mentioned wake-up message carrying push Token-B to the push agent of the electronic device 200.

The following describes the data packetizing and unpacking process in the embodiment of this application.

After reading the designated data selected by the user, the electronic device 100 can perform packet processing on the designated data. When transmitting the specified data through the network, the data needs to be aligned in network byte order. Therefore, a data packet format is provided in this embodiment of the present application.

Figure 22 shows the data structure of a data packet provided in the embodiment of the present application.

As shown in Figure 22, the data packet may include a transmission header (transmission head, TransHead) and transmission data (transmission data, TransData). Among them, TransData can be the binary data of the specified data selected by the above user.

Among them, the definition of the data package can be as follows:

Among them, in the above definition, TransHead can include a data type (type) field, a length (length) field, and a sequence number (sequence number, seq) field. The data type field can be used to indicate the type of data transmitted in this packet. For example, the types of transmitted data may include raw image format (RAW), command (CMD), voice (voice), and other types. The length field can be used to indicate the data length of the transmitted data. The sequence field can be used to indicate the sequence number of the data packet in multiple data packets after the specified data fragmentation.

Among them, due to the limitation of the maximum transmission unit (MTU) in the network transmission protocol (for example, the maximum length of the data packet cannot exceed 1500 bits). Therefore, the specified data needs to be cut into multiple data packets according to the above data packet format. Among them, since TransHead includes the seq field, it indicates the sequence number of the data packet. Therefore, the receiving end can easily assemble multiple data packets into complete specified data based on the seq field in TransHead. In this way, no matter whether the underlying protocol uses UDP, TCP protocol or quick protocol, the receiving end can still recover the specified data from multiple data packets.

In one example, the seq field can not be set in TransHead and the underlying TCP protocol can be directly used for transmission. In this way, the sequential transmission of specified data can be completed at the TCP layer.

In one example, depending on the type of specified data, a transport protocol appropriate for that type may be used. For example, the RTP protocol can be used to transmit real-time streaming media data, and the file transfer protocol (FTP) can be used to transmit file data.

The following describes the data offloading and transmission strategies provided in the embodiments of this application.

Since the electronic device 100 shares the designated data selected by the user with the electronic device 200, it can use the main link of the call or the auxiliary link. And there can also be multiple auxiliary links. Therefore, a data offloading strategy needs to be determined. Among them, the strategy can be as follows:

1. Transmission speed is priority.

The electronic device 100 may select one or more data transmission links with the fastest transmission speed among the primary link and the auxiliary link, or concurrently transmit specified data selected by the user in multiple links among the primary link and the auxiliary link.

In one example, when the electronic device 100 chooses to concurrently transmit some data packets on multiple links, the electronic device 100 can redundantly and repeatedly transmit some data packets in the multi-links, so that the electronic device 200 can obtain data from the data packets transmitted in the multi-links. Recover the specified data selected by the user.

2. Low power consumption is given priority.

The electronic device 100 can select the link with lower power consumption during transmission among the primary link and the auxiliary link to transmit the specified data selected by the user.

3. Low cost is preferred.

The electronic device 100 can select the link with the lowest cost among the primary link and the auxiliary link to transmit the specified data selected by the user. For example, specified data selected by the user can be prioritized for transmission over the Wi-Fi link.

The following describes the process of a file withdrawal mechanism provided in the embodiment of this application.

Figure 23 illustrates a schematic flow chart of a file recall mechanism provided in the embodiment of the present application.

As shown in Figure 23, the file recall mechanism may include the following steps:

S2301. The electronic device 100 can transmit specified data to the electronic device 200.

For details about the process of the electronic device 100 transmitting the designated data selected by the user to the electronic device 200 and the interface display, reference may be made to the foregoing embodiments and will not be described again here.

S2302. After receiving the specified data, the electronic device 200 can save the specified data and record the saving path of the specified data.

Optionally, S2303, the electronic device 200 can monitor and record the saving path of the specified data after being moved/or copied.

S2304. The electronic device 100 may send a withdrawal instruction to the electronic device 200.

Wherein, the electronic device 100 may send the withdrawal instruction to the electronic device 200 on the data transmission link. For specific information on the interface display when withdrawing designated data, reference may be made to the embodiment shown in FIG. 4I , which will not be described again here.

S2305. After receiving the withdrawal instruction, the electronic device 200 may determine whether the storage time of the specified data has expired.

S2306. When the storage time of the specified data has not expired, the electronic device 200 can find the storage path of the specified data and delete the specified data.

In one example, after receiving the withdrawal instruction, the electronic device 200 may directly find the storage path of the specified data and delete the specified data without determining whether it times out.

Optionally, S2307, after the electronic device 200 deletes the specified data, the reception status of the specified data can be updated.

The electronic device 200 may display a withdrawal prompt, which is used to remind the user that the specified data has been withdrawn.

For example, the electronic device 200 may display an option of specifying data in the received file list, and mark the status of the option of specifying data as a withdrawn status.

The following describes how the electronic device 100 performs permission management on designated data sent to the electronic device 200 in this embodiment of the present application.

In some embodiments, the electronic device 100 can also perform permission management on designated data sent to the electronic device 200 . Among them, the permission management includes burning after reading (that is, only allowing the electronic device 200 to view and not allowing the electronic device 200 to transfer), only allowing the electronic device 200 to store and not allowing the electronic device 200 to forward, allowing the electronic device 200 to forward, and so on. Not limited to this, more rights management can be performed on the designated data, for example, the electronic device 200 is not allowed to modify the content in the designated data, and so on.

Among them, permissions can be managed on designated data in the following ways:

1. Before the electronic device 100 transmits specified data to the electronic device 200, the electronic device 100 can negotiate the key and certificate with the electronic device 200. The certificate includes the permission of the electronic device 100 to allow the electronic device 200 to operate the specified data. The electronic device 100 may encrypt the specified data using the negotiated key, and send the encrypted specified data to the electronic device 200 . After receiving the encrypted designated data, the electronic device 200 may store the encrypted designated data separately from the previously negotiated key device certificate. When receiving input from the user to perform a specified operation (for example, open, transfer, forward, etc.) on the specified data, the electronic device 200 may first verify whether the certificate includes permission for the specified operation. If there is permission, the electronic device 200 200 can continue to verify the key, and perform specified operations on the specified data after verifying the key. If there is no authority, the electronic device 200 may not perform the specified operation on the specified data.

2. The electronic device 100 can add permission information to the file header of the specified data. When the electronic device 200 receives input from the user to perform a specified operation on the specified data, the electronic device 200 may first determine whether there is permission to perform the specified operation on the specified data based on the permission information in the file header of the specified data. If there is permission, the electronic device 200 can perform the specified operation on the specified data. If not, the electronic device 200 refuses to perform the specified operation on the specified data.

The following introduces a call scenario provided in the embodiment of this application.

In some application scenarios, the counterparty of the call to the electronic device 100 may be a non-mobile phone device. For example, the electronic device 100 can communicate with an agent device connected to the service center through a service center. For example, interactive voice response (IVR) call system. The electronic device 100 may send specified data selected by the user to the agent device during the conversation.

Figure 24 shows an IVR call system provided in the embodiment of the present application.

As shown in Figure 24, the IVR call system may include electronic device 100, operator network, service center and agent equipment.

Among them, the electronic device 100 can dial the service number of the service center and establish a call link with the service center through the operator's network. The service center can establish a call link with the agent device and transfer the call from the electronic device 100 to the agent device.

The electronic device 100 can communicate with the agent device through a call link composed of a communication path from the operator network to the service center and a communication path from the service center to the agent device. One or more auxiliary links may be created between the electronic device 100 and the agent device, and designated data selected by the user may be sent to the agent device through the one or more auxiliary links.

In one example, the electronic device 100 can establish an auxiliary link 1 with the service center, and send the specified data selected by the user to the agent device through the auxiliary link 1 and the call link between the service center and the agent device.

In one example, the electronic device 100 can establish an auxiliary link 2 with the agent device, and send the specified data selected by the user to the agent device through the auxiliary link 2 .

In one example, the electronic device 100 can simultaneously use the auxiliary link 1 and the call link between the service center and the agent device, and the auxiliary link 2 to send the specified data selected by the user to the agent device.

Figure 25 shows the establishment process of an auxiliary link in an IVR call system provided in the embodiment of the present application.

As shown in Figure 25, the establishment process of the auxiliary link in the IVR call system may include the following steps:

S2501. The electronic device 100 establishes a call link with the agent device through the operator network and service center.

The electronic device 100 can communicate with the agent device based on the communication link.

S2502. The electronic device 100 may send the call binding information A to the addressing server.

The call binding information A includes the communication identification A of the electronic device 100, the phone number of the electronic device 100, the service number of the service center, and the call device type A of the electronic device 100 (for example, a mobile phone).

After receiving the call binding information A, the addressing server can save the call binding information A.

S2503. The service center can send the call binding information B to the addressing server.

The call binding information B includes the communication identifier B of the service center, the telephone number of the electronic device 100, the service number of the service center, and the call equipment type B of the service center (eg, service center).

After receiving the call binding information B, the addressing server can save the call binding information B.

S2504. The agent device can send the call binding information C to the addressing server.

The call binding information C includes the communication identifier C of the agent device, the phone number of the electronic device 100, the service number of the service center, and the call device type C of the agent device (for example, the agent device).

After receiving the call binding information C, the addressing server can save the call binding information C.

S2505. The electronic device 100 can send a query request A to the addressing server. The query request A can be used to query the communication identifier B of the service center and/or the communication identifier C of the agent device.

Wherein, the query request A carries the calling device type B and/or the calling device type C. When the query request A carries the calling device type B, the query request A is used to query the communication identifier B of the service center. When the query request A carries the calling device type C, the query request A is used to query the communication identifier C of the agent device. When the query request A carries the communication device type B and the communication device type C, the query request A is used to query the communication identifier B of the service center and the communication identifier C of the agent device.

S2506. After receiving the query request A, the addressing server may return the communication identification B of the service center and/or the communication identification C of the agent device to the electronic device 100.

S2507. The service center can send a query request B to the addressing server. The query request B can be used to query the communication identification A of the electronic device 100.

Among them, the query request B carries the calling device type A.

S2508. After receiving the query request B, the addressing server may return the communication identification A of the electronic device 100 to the service center.

S2509. The agent device can send a query request C to the addressing server. The query request C can be used to query the communication identification A of the electronic device 100.

Among them, the query request B carries the calling device type A.

S2510. After receiving the query request B, the addressing server may return the communication identification A of the electronic device 100 to the agent device.

S2511. The electronic device 100 and the service center establish the auxiliary link 1 through the communication identifier A and the communication identifier B.

S2512. The electronic device 100 and the agent device establish the auxiliary link 2 through the communication identifier A and the communication identifier C.

In this embodiment of the present application, to obtain the communication identification A of the electronic device 100, the communication identification B of the service center, and the communication identification C of the agent device, please refer to the aforementioned embodiments shown in Figure 13A and Figures 15-20 The process for the electronic device 100 to obtain the communication identification A will not be described again here.

The addressing server in the embodiment of the present application may be the business cloud server 1380 in the embodiment shown in FIG. 13A and FIG. 15 to FIG. 20 .

For the establishment process of auxiliary link 1 and auxiliary link 2 in the embodiment of the present application, you can refer to the process of establishing a link between the electronic device 100 and the electronic device 200 in the embodiment shown in Figures 15 to 20, and will not be described again here. .

As mentioned above, the above embodiments are only used to illustrate the technical solution of the present application, but not to limit it. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still make the foregoing technical solutions. The technical solutions described in each embodiment may be modified, or some of the technical features may be equivalently replaced; however, these modifications or substitutions do not cause the essence of the corresponding technical solutions to depart from the scope of the technical solutions in each embodiment of the present application.

Claims

A data sharing method, characterized by including:

The first electronic device displays a call interface, the call interface includes contact information of the second electronic device, and the call interface is used to indicate that the first electronic device and the second electronic device are on an operator call;

The first electronic device receives a first input to share the first specified data during the operator call with the second electronic device;

In response to the first input, the first electronic device displays a first sharing interface, and displays a first option corresponding to the second electronic device in the first sharing interface;

the first electronic device receives a second input to the first option;

In response to the second input, the first electronic device sends the first specified data to the second electronic device.
The method according to claim 1, characterized in that a call mark is displayed around the first option, and the call mark is used to indicate that the first option is a third person who is talking to the first electronic device. 2. Options corresponding to electronic equipment.
The method according to claim 1 or 2, characterized in that, the contact information corresponding to the second electronic device is also displayed around the first option, and the contact information corresponding to the second electronic device includes the following: One or more items: the phone number of the second electronic device, the name of the contact person that the first electronic device has noted for the phone number of the second electronic device, the phone number of the first electronic device for the second electronic device. The phone number of the electronic device has been noted as a contact avatar and a call application mark; wherein the call application mark is used to represent the call application to which the call interface belongs.
The method according to any one of claims 1-3, characterized in that, in response to the second input, the first electronic device sends the first designated data to the second electronic device , specifically including:

In response to the second input, the first electronic device sends a data transmission request to the second electronic device, the data transmission request being used to request transmission of the first specified data to the second electronic device;

The first electronic device receives confirmation information sent by the second electronic device, and the confirmation information is used to indicate that the second electronic device allows the first electronic device to send the first designated data to the second electronic device. Electronic equipment;

In response to the confirmation information, the first electronic device sends the first specified data to the second electronic device.
The method of claim 4, further comprising:

In response to the second input, the first electronic device displays a first prompt, the first prompt is used to prompt the user that the first electronic device is requesting to send the first designation to the second electronic device. data.
The method according to any one of claims 1-5, characterized in that the method further includes:

During the process of sending the first designated data to the second electronic device, the first electronic device displays a second prompt and a sending progress bar. The second prompt is used to prompt the user of the first electronic device. The first specified data is being sent to the second electronic device, and the sending progress bar is used to prompt the user of the progress of the first electronic device sending the first specified data to the second electronic device.
The method of claim 6, further comprising:

During the process of sending the first specified data to the second electronic device, the first electronic device displays a sending cancel control, and the cancel control is used to trigger the first electronic device to suspend sending the first specified data. data to the second electronic device.
The method according to any one of claims 1-7, characterized in that the method further includes:

After the first electronic device sends the first designated data to the second electronic device, a third prompt and a withdrawal control are displayed. The third prompt is used to prompt the user that the first electronic device has After sending the first designated data to the second electronic device, the withdrawal control is used to trigger the first electronic device to send a withdrawal instruction to the second electronic device, and the withdrawal instruction is used to request the third electronic device. The second electronic device deletes the first designated data that has been received by the first electronic device.
The method according to any one of claims 1 to 8, characterized in that the first sharing interface is a system sharing interface, and the first sharing interface further includes the first electronic device discovering the system through near field communication technology. options for one or more nearby devices, one or more services Service options, the options of the nearby device are used to trigger the first electronic device to share the first specified data to the nearby device, and the service options can be used to trigger the first electronic device to use the service options. The corresponding application or protocol shares the first specified data.
The method according to any one of claims 1 to 9, characterized in that the first sharing interface is an in-application sharing interface of the first application, and the first sharing interface further includes an in-app sharing interface in the first application. One or more functional options;

During the operator call with the second electronic device, the first electronic device receives a first input to share the first specified data, which specifically includes:

During the operator call with the second electronic device, the first electronic device displays a first interface of the first application, and the first interface includes the first specified data and a first control. , the first control is used to share the first specified data, wherein the sharing the first specified data includes sharing the acquisition link of the first specified data;

The first electronic device receives the first input to the first control.
The method according to any one of claims 1 to 10, characterized in that the first specified data includes one or more of the following: pictures, audio, video, document files, location information, links, contact information , Calendar, Application Package, Notes.
The method according to any one of claims 1-11, characterized in that the method further includes:

After the first electronic device sends the first specified data to the second electronic device, the first electronic device and the second electronic device end the operator call;

The first electronic device receives a third input sharing second specified data;

In response to the third input, the first electronic device displays a second sharing interface, the second sharing interface includes options for one or more recently interacted contacts; wherein the most recently interacted contacts are in the first Contacts who have interacted with the first electronic device within a recent period of time when an electronic device receives the third input, and the options of the one or more recently interacted contacts include second contacts corresponding to the third electronic device. options;

the first electronic device receives a second input of the second option;

In response to the second input, the first electronic device sends the second specified data to the third electronic device.
The method according to claim 12, characterized in that, the contact information of the recently interacted contact is displayed around the option of the recently interacted contact, and the contact information of the recently interacted contact includes one of the following: Item or items: The contact information of the recently interacted contact includes one or more of the following: the phone number of the recently interacted contact, the contact name of the recently interacted contact, the recently interacted contact The contact avatar and the contact application mark; wherein the contact application mark is used to represent the application used by the first electronic device to interact with the recently interacted contact.
The method according to claim 13, characterized in that the interaction includes any of the following: calling with an operator, receiving text messages, sending text messages, over-the-top calls, receiving or sending private messages within social applications.
The method according to any one of claims 1-14, characterized in that, before the first electronic device sends the first designated data to the second electronic device, the method further includes:

The first electronic device establishes a first data transmission link with the second electronic device;

In response to the second input, the first electronic device sends the first specified data to the second electronic device, specifically including:

In response to the second input, the first electronic device sends the first specified data to the second electronic device over the first data transmission link.
The method of claim 15, further comprising:

The first electronic device has established the first data transmission link with the second electronic device during the operator call and before receiving the first input. ;

In response to the first input, the first electronic device displays a first sharing interface, and displays a first option corresponding to the second electronic device in the first sharing interface, specifically including:

In response to the first input, the first electronic device displays the first sharing interface, the first sharing interface includes the second electronic device The first option corresponding to the sub-device.
The method of claim 15, wherein in response to the first input, the first electronic device displays a first sharing interface, and displays the second electronic device in the first sharing interface. The first option corresponding to the device includes:

In response to the first input, the first electronic device displays the first sharing interface;

After the first electronic device and the second electronic device establish the first data transmission link, the first electronic device displays the third data corresponding to the second electronic device in the first sharing interface. One option.
The method of claim 15, wherein in response to the second input, the first electronic device sends the first designated data to the first data transmission link. Second electronic equipment, specifically including:

In response to the second input, the first electronic device establishes the first data transmission link with the second electronic device;

After the first data transmission link is established, the first electronic device sends the first designated data to the second electronic device on the first data transmission link.
The method according to any one of claims 15-18, characterized in that the first data transmission link includes one or more of the following links: the first electronic device and the second electronic device perform The main link of the operator call and one or more auxiliary links between the first electronic device and the second electronic device.
The method according to claim 19, characterized in that the one or more auxiliary links include one or more of the following: Internet Protocol IP direct link, point-to-point P2P link, and server relay link.
The method according to claim 19 or 20, characterized in that when the first data transmission link includes the one or more auxiliary links, the first electronic device and the second electronic device establish The first data transmission link specifically includes:

The first electronic device obtains the first communication identification assigned by the cloud server to the first electronic device;

The first electronic device sends the phone number of the first electronic device and the first communication identification to the cloud server for binding and storage;

The first electronic device sends a first query request to the cloud server. The first query request includes the phone number of the second electronic device. The first query request is used to query the phone number of the second electronic device. second communication identification;

The first electronic device receives the second communication identification sent by the cloud server;

The first electronic device establishes the auxiliary link with the electronic device based on the first communication identifier and the second communication identifier.
The method according to claim 21, wherein the auxiliary link includes a P2P link; the first communication identifier is the first session used when the first electronic device conducts session communication with the cloud server. Identity, the second communication identification is the second session identification used when the second electronic device performs session communication with the cloud server;

The first electronic device establishes the auxiliary link with the electronic device based on the first communication identifier and the second communication identifier, which specifically includes:

The first electronic device sends a first acquisition request to the cloud server, where the first acquisition request is used to request acquisition of the first NAT public network information of the first electronic device;

The first electronic device receives the first NAT public network information sent by the cloud server. The first NAT public network information includes the public network IP address of the first electronic device and the IP address of the first electronic device. The port number from the public network to the intranet;

The first electronic device sends a first message to the cloud server, the first message carries the second session identifier and the first NAT public network information, and the first message is used for the third An electronic device exchanges NAT public network information with the second electronic device;

The first electronic device receives the second NAT public network information of the second electronic device sent by the cloud server. The second NAT public network information includes the public network IP address of the second electronic device and the The port number of the second electronic device from the public network to the intranet;

The first electronic device establishes a P2P link with the second electronic device based on the first NAT public network information and the second NAT public network information.
The method of claim 21, wherein the auxiliary link includes a server relay link; and the first communication identifier is the first communication identifier used by the first electronic device to communicate with the cloud server. a session identifier, the second communication identifier being the first 2. A second session identifier used when the electronic device conducts session communication with the cloud server;

The first electronic device establishes the auxiliary link with the electronic device based on the first communication identifier and the second communication identifier, which specifically includes:

The first electronic device sends a second acquisition request, the second acquisition request is used to acquire the first relay address of the first electronic device;

The first electronic device receives the first relay address sent by the cloud server;

The first electronic device sends a first message to the cloud server, the first message carries the second session identifier and the first relay address, and the first message is used for the first The electronic device exchanges relay addresses with the second electronic device;

The first electronic device receives the second relay address of the second electronic device sent by the cloud server;

After the first electronic device and the second electronic device complete the exchange of relay addresses, the first electronic device and the second electronic device complete establishing a server relay link.
An electronic device, which is a first electronic device, is characterized in that it includes a display screen, one or more processors and one or more memories, and the display screen, the one or more memories and the one or more memories are coupled to a processor, the one or more memories are used to store computer program code, the computer program code includes computer instructions, when the one or more processors execute the computer instructions, the implementation of claims 1-23 any one of the methods.
A computer storage medium, characterized in that the computer storage medium stores computer instructions, and when the computer instructions are executed by a processor, the method according to any one of claims 1-23 is implemented.