Device interaction method, electronic device and storage medium

Abstract

The embodiments of the present application relate to the technical field of terminals. Provided are a device interaction method, an electronic device and a storage medium. The method comprises: a first electronic device establishing a connection with a second electronic device, wherein when the second electronic device is connected to the first electronic device, connection is performed by means of a non-customized connection protocol; the first electronic device acquiring device information of the second electronic device; on the basis of the device information of the second electronic device, the first electronic device determining whether the second electronic device is an electronic device of a specified type; and in the case where the second electronic device is an electronic device of the specified type, the first electronic device displaying a first popup window corresponding to the second electronic device. A first electronic device may prompt by means of a first popup window that a second electronic device is being connected, for example, a third-party headset is being connected. Effective management of the second electronic device is achieved, thereby providing a better user experience for users.

Description

Device interaction method, electronic device, and storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on January 8, 2024, with application number 202410033354.X and invention name “Device interaction method, electronic device and storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The application relates to the field of terminal technology, and in particular to a device interaction method, electronic device and storage medium. Background Art

[0003] Audio output is often required when using a device. However, in noisy or public places, using the external speaker mode for audio output often provides a poor sound experience for the user or easily disrupts others' rest or work. Therefore, using headphones for audio output is a common audio output mode.

[0004] Traditional headphones are usually divided into headphones of the same brand as the terminal device, or headphones of a different brand.

[0005] Currently, when connecting to headphones of different brands, terminal devices can only use the headphones of different brands as audio output devices and cannot manage the headphones of different brands. This greatly limits the use of headphones of different brands and makes it inconvenient for users to understand the usage status of headphones of different brands. Summary of the Invention

[0006] The embodiments of the present application provide a device interaction method, an electronic device, and a storage medium, which can manage third-party headphones connected to a terminal device and improve the user experience.

[0007] In order to achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0008] In a first aspect, an embodiment of the present application provides a device interaction method.

[0009] Applied to a first electronic device, including: the first electronic device establishes a connection with a second electronic device, wherein the second electronic device is connected to the first electronic device through a non-customized connection protocol; the first electronic device obtains device information of the second electronic device; the first electronic device determines whether the second electronic device is an electronic device of a specified type based on the device information of the second electronic device; when the second electronic device is an electronic device of the specified type, the first electronic device displays a first pop-up window corresponding to the second electronic device.

[0010] Among them, the first pop-up window is shown as the first pop-up window 800 in Figure 8.

[0011] Based on the technical solution provided in the embodiments of the present application, when a first electronic device is in communication with a second electronic device, the first electronic device obtains the device information of the second electronic device; the first electronic device determines whether the second electronic device is an electronic device of a specified type based on the device information of the second electronic device; if the second electronic device is an electronic device of the specified type, the first electronic device displays a first pop-up window corresponding to the second electronic device. The first electronic device can use the first pop-up window to indicate that a second electronic device has been connected, such as a third-party headset. This enables management of the second electronic device, thereby providing users with a better user experience.

[0012] In a possible implementation of the first aspect, a first electronic device determines whether the second electronic device is an electronic device of a specified type based on device information of the second electronic device, including: the first electronic device determines that the second electronic device is connected to the first electronic device for communication for the first time; the first electronic device obtains service information of the second electronic device; in response to the service information of the second electronic device including an identifier corresponding to an audio head-mounted device, and the service information of the second electronic device includes power information of the second electronic device, the first electronic device determines that the second electronic device is an electronic device of the specified type; in response to the service information of the second electronic device not including an identifier corresponding to an audio head-mounted device, the first electronic device determines that the second electronic device is not an electronic device of the specified type.

[0013] Based on the above implementation method, it is possible to determine that the second electronic device and the first electronic device are communicating and connecting for the first time; obtain the service information of the second electronic device; in response to the service information of the second electronic device including the first identifier corresponding to the audio head-mounted device, and the service information of the second electronic device including the power information of the second electronic device, the first electronic device determines that the second electronic device is an electronic device of a specified type; in response to the service information of the second electronic device not including the first identifier, the first electronic device determines that the second electronic device is not an electronic device of the specified type, thereby determining whether the second electronic device belongs to an electronic device of the specified type by obtaining the service information and power information of the second electronic device, thereby effectively determining whether the first pop-up window needs to be popped up.

[0014] In a possible implementation of the first aspect, the first electronic device determines whether the second electronic device is an electronic device of a specified type based on the device information of the second electronic device, and also includes: in response to the service information of the second electronic device including a first identifier, and the device name of the second electronic device is in a preset whitelist, the first electronic device determines that the second electronic device is an electronic device of the specified type.

[0015] Based on the above implementation method, it is possible to determine that the second electronic device and the first electronic device are communicating and connecting for the first time; obtain the service information of the second electronic device; in response to the service information of the second electronic device including an identifier corresponding to an audio head-mounted device, and the device name of the second electronic device is in a preset whitelist, the first electronic device determines that the second electronic device is an electronic device of a specified type, thereby determining whether the second electronic device belongs to an electronic device of the specified type through the service information and device name of the second electronic device, thereby effectively determining whether the first pop-up window needs to be popped up.

[0016] In a possible implementation of the first aspect, the first pop-up window includes: an icon of a second electronic device, and the first electronic device displays the first pop-up window corresponding to the second electronic device, including: the first electronic device obtains a second identifier of the second electronic device; the first electronic device obtains an icon corresponding to the second identifier as the icon of the second electronic device; the first electronic device generates a first pop-up window based on the icon of the second electronic device and displays the first pop-up window.

[0017] The icon of the second electronic device is shown as icon 801 in FIG. 8 .

[0018] Based on the above implementation, before generating a first pop-up window corresponding to the second electronic device, the first electronic device can obtain the second identifier of the second electronic device; obtain an icon corresponding to the second identifier as the icon of the second electronic device; and generate the first pop-up window corresponding to the second electronic device based on the icon of the second electronic device. This allows the icon displayed in the first pop-up window to correspond to the second electronic device, thereby providing a better user experience.

[0019] In a possible implementation of the first aspect, the first pop-up window includes a first control, and the method also includes: determining the first communication connection between the second electronic device and the first electronic device; in response to the operation on the first control, the first electronic device displays a first interface of the second electronic device, the first interface includes a second control, and the first interface is used to add the second electronic device to the device management space of the first electronic device; in response to the operation on the second control, the first electronic device adds the third identifier of the second electronic device to the first list, the first list is a list of the first account, and the first account is the account logged in to the device management space.

[0020] The first control is shown as the first control 804 in Figure 8. The first interface is shown as the first interface 900 in Figure 9. The second control is shown as the second control 901 in Figure 9.

[0021] Based on the above implementation, when the third-party headset is connected to the electronic device for communication, the first electronic device can prompt the second electronic device to be connected through the first pop-up window. Moreover, since the first pop-up window includes the first control, the first electronic device can display the first interface in response to the user operating the first control. After the user operates the second control, the third identifier of the second electronic device can be added to the first list. Through the above method, when the second electronic device is connected to the first electronic device for communication for the first time, the second electronic device is associated with the Honor Smart Space application, so that the second electronic device can be managed through the Honor Smart Space application.

[0022] In a possible implementation of the first aspect, in response to the user's operation on the second control, after the first electronic device adds the third identifier of the second electronic device to the first list, the method also includes: the first electronic device displays a second pop-up window; the second pop-up window includes the third control, and a prompt message that the second electronic device is successfully added to the device management space; in response to the operation on the third control, the first electronic device displays a second interface, and the second interface includes device detail information of the second electronic device.

[0023] The second pop-up window is shown as the second pop-up window 1004 in Figures 10 and 11. The third control is shown as the third control 1002 in Figures 10 and 11. The second interface is shown as the second interface 1200 in Figures 12 and 13.

[0024] Based on the above implementation, after the user operates the second control of the management interface, the electronic device can display a second pop-up window after adding the third identifier of the second electronic device to the first list. The first list is a list of the first account, and the first account is the account logged in to the device management space. The second pop-up window includes a third control for triggering the display of the second interface. In response to the operation on the third control, the first electronic device can display the second interface, allowing the user to manage the second electronic device through the second interface and understand the usage of the second electronic device, for example, understanding the power information of the second electronic device, thereby giving the user a better user experience.

[0025] In a possible implementation of the first aspect, the first pop-up window includes a first control, and the method further includes: determining that the second electronic device and the first electronic device are not communicating with each other for the first time; in response to an operation acting on the first control, the first electronic device displays a second interface, and the second interface includes device detail information of the second electronic device.

[0026] Based on the above implementation method, when the second electronic device is not communicating with the first electronic device for the first time, the second interface is directly displayed in response to the operation on the first control. The user can directly access the second interface to manage the second electronic device, thereby simply and quickly managing the second electronic device.

[0027] In a possible implementation of the first aspect, the device detail information includes at least one or a combination of the following: power information of the second electronic device, the connection status of the second electronic device, the current sound effects and optional sound effects of the second electronic device, the current sound quality and optional sound quality of the second electronic device, and a setting entry for functions recommended for the second electronic device, where the functions include executing preset operations when preset trigger conditions are triggered.

[0028] Based on the above implementation, the battery information of the second electronic device is displayed in the second interface, so that the user can know whether the battery of the second electronic device is sufficient to support the subsequent use. The connection status of the second electronic device is displayed in the second interface, so that the user can know whether the second electronic device is already connected to the first electronic device for communication. The current sound effects and optional sound effects of the second electronic device are displayed in the second interface, which can meet the user's needs to change the sound effects of the headphones. The current sound quality and optional sound quality of the second electronic device are displayed in the second interface, which can meet the user's needs to change the sound quality of the headphones. The setting entry of the recommended functions for the second electronic device is displayed in the second interface, which can meet the user's needs to set functions for the second electronic device.

[0029] In a possible implementation of the first aspect, when the second electronic device is not communicating with the first electronic device for the first time, the device detail information further includes: a historically set function of the current second electronic device.

[0030] Based on the above implementation, the second interface also includes the historically set functions of the current second electronic device, so that the user can access the functions previously set for the current second electronic device at any time when needed, and can also delete or modify these functions.

[0031] In a possible implementation of the first aspect, before the first electronic device establishes a connection with the second electronic device, the method also includes: the first electronic device determines that connection broadcast information of the second electronic device is received; the first electronic device obtains a fourth identifier of the second electronic device from the connection broadcast information; the first electronic device determines that it is not the first connection with the second electronic device based on the fourth identifier; the first electronic device displays a third pop-up window, and the third pop-up window includes a fourth control; in response to an operation on the fourth control, the first electronic device connects to the second electronic device.

[0032] Based on the above implementation, after determining that it has received the connection broadcast information of the second electronic device that is not the first connection, the first electronic device can prompt the user through a second pop-up window that there is currently a second electronic device that can be connected. Because the second pop-up window includes a fourth control for triggering the connection to the second electronic device, in response to the operation of the fourth control, the first electronic device can establish a communication connection with the second electronic device. The first electronic device asks the user for their opinion before communicating with the second electronic device, which can make the operation of the first electronic device better meet the user's needs and provide the user with a better user experience.

[0033] In a possible implementation of the first aspect, the device interaction method provided by the embodiment of the present application also includes: displaying a third interface in response to an access operation on a setting entrance of a function recommended for a second electronic device; the third interface includes a tenth control and / or an eleventh control; when the third interface includes the tenth control, the first electronic device sets a trigger condition in response to the operation on the tenth control; when the third interface includes the eleventh control, the first electronic device sets an executable operation in response to the operation on the eleventh control.

[0034] Among them, the third interface is shown as the third interface 1400 in Figure 14.

[0035] Based on the above implementation, the first electronic device can set a trigger condition in response to an operation on the tenth control in the third interface. The first electronic device can also set an executable operation in response to an operation on the eleventh control in the third interface. When the first electronic device detects that the trigger condition is met, it executes the executable operation corresponding to the satisfied trigger condition, thereby meeting the user's functional requirements for the second electronic device.

[0036] In a possible implementation of the first aspect, when the MAC address of the second electronic device has been added to the account of the Honor Smart Space application, the device interaction method provided by the embodiment of the present application also includes: in response to the operation of accessing the device management space, displaying the eighth interface, the eighth interface including the thirteenth control for triggering the display of the second interface; in response to the operation acting on the thirteenth control, displaying the second interface.

[0037] Among them, the eighth interface is shown as the eighth interface 1900 in Figure 19.

[0038] Based on the above implementation, when a user accesses the Honor Smart Space app, the first electronic device can display a thirteenth control on the eighth interface displayed by the Honor Smart Space app, which triggers the display of the second interface. When the user operates the thirteenth control, the second interface can be displayed, allowing the user to access the second interface and manage the second electronic device. In this way, after the user closes the second interface, they can still find the second interface by accessing the Honor Smart Space app.

[0039] In a possible implementation of the first aspect, when the MAC address of the second electronic device has been added to the account of the Honor Smart Space application, if the second electronic device is not the only audio device currently connected to the first electronic device, the device interaction method provided in the embodiment of the present application also includes: in response to the operation of accessing the device management space, displaying the eighth interface, the eighth interface includes a fourteenth control that triggers the display of the third interface; in response to the operation acting on the fourteenth control, displaying the third interface, the third interface is used to manage all audio devices currently connected to the first electronic device, and the third interface includes a fifteenth control that triggers the display of the second interface; in response to the operation acting on the fifteenth control, displaying the second interface.

[0040] Based on the above implementation, when the first electronic device is also connected to other electronic devices of the same device type as the second electronic device, the entrance to the second interface can be set on the third interface, and the third interface is used to manage all audio devices currently connected to the first electronic device. In a second aspect, the present application provides an electronic device, which includes a display screen, a memory, and one or more processors; the display screen, the memory, and the processor are coupled; wherein the memory stores computer program code, and the computer program code includes computer instructions. When the computer instructions are executed by the processor, the electronic device executes the device interaction method provided in the first aspect and any possible design thereof.

[0041] In a third aspect, the present application provides a computer-readable storage medium comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the device interaction method provided in the first aspect and any possible design thereof.

[0042] In a fourth aspect, the present application provides a computer program product, which, when executed on an electronic device, enables the electronic device to execute the device interaction method provided in the first aspect and any possible design thereof.

[0043] It can be understood that the beneficial effects that can be achieved by the technical solutions provided in the second to fourth aspects mentioned above can be referred to the beneficial effects in the first aspect and any possible design method thereof, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] FIG1 is a schematic diagram of a third-party headset connection interface provided in an embodiment of the present application;

[0045] FIG2 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application;

[0046] FIG3 is a schematic diagram of a layered architecture of a software system of an electronic device provided in an embodiment of the present application;

[0047] FIG4 is a flow chart of a device interaction method provided in an embodiment of the present application;

[0048] FIG5 is a schematic diagram of a setting interface provided in an embodiment of the present application;

[0049] FIG6 is a schematic diagram of a Bluetooth setting interface provided in an embodiment of the present application;

[0050] FIG7 is a schematic diagram of another Bluetooth setting interface provided in an embodiment of the present application;

[0051] FIG8 is a schematic diagram of a first pop-up window interface provided in an embodiment of the present application;

[0052] FIG9 is a schematic diagram of a first interface provided in an embodiment of the present application;

[0053] FIG10 is a schematic diagram of a second pop-up window interface provided in an embodiment of the present application;

[0054] FIG11 is a schematic diagram of another second pop-up window interface provided in an embodiment of the present application;

[0055] FIG12 is a schematic diagram of a second interface provided in an embodiment of the present application;

[0056] FIG13 is a schematic diagram of another second interface provided in an embodiment of the present application;

[0057] FIG14 is a schematic diagram of a third interface provided in an embodiment of the present application;

[0058] FIG15 is a schematic diagram of a fourth interface provided in an embodiment of the present application;

[0059] FIG16 is a schematic diagram of a fifth interface provided in an embodiment of the present application;

[0060] FIG17 is a schematic diagram of a sixth interface provided in an embodiment of the present application;

[0061] FIG18 is a schematic diagram of a seventh interface provided in an embodiment of the present application;

[0062] FIG19 is a schematic diagram of an eighth interface provided in an embodiment of the present application;

[0063] FIG20 is a schematic diagram of a ninth interface provided in an embodiment of the present application;

[0064] FIG21 is a flow chart of another device interaction method provided in an embodiment of the present application;

[0065] Figure 22 is a structural diagram of a multi-device collaboration device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0066] The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments and are not intended to be limiting of the present application. As used in the specification and appended claims of the present application, the singular expressions "a", "an", "said", "above", "the" and "this" are intended to include plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that " / " means or, for example, A / B can mean A or B; "and / or" in the text is merely a description of an association relationship of associated objects, indicating that three relationships can exist, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0067] References to "embodiments" in this application mean that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described in this application may be combined with other embodiments.

[0068] The terms "first" and "second" in the following embodiments of this application are used for descriptive purposes only and should not be understood as implying or suggesting relative importance or implicitly indicating the number of the technical features indicated. 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" means two or more.

[0069] To facilitate the technical solution of the application, some concepts involved in this application are first explained below.

[0070] Bluetooth device: Bluetooth technology is an open global specification for wireless data and voice communications. It is a special short-range wireless technology that establishes a communication environment for fixed and mobile devices based on low-cost short-range wireless connections. A Bluetooth device is a device that supports Bluetooth technology and can connect to other Bluetooth-enabled devices through Bluetooth technology.

[0071] The technical solutions provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0072] The technical solution provided in this application can be applied to electronic devices with image display functions, for example, a first electronic device. In some embodiments, the electronic device can be a mobile phone, a tablet computer, a handheld computer, a personal computer (PC), an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device, and / or a smart city device, etc. The embodiments of this application do not impose any special restrictions on the specific type of the electronic device.

[0073] The communication connection involved in this application includes the communication connection between the second electronic device and the first electronic device. The second electronic device includes a third-party headset. The third-party headset is a headset of a different ecosystem from the first electronic device. When the third-party headset is connected to the first electronic device, it is not connected through a customized connection protocol. Usually, when the first electronic device and the headset are in the same ecosystem, the headset of the same ecosystem is connected to the first electronic device through a customized connection protocol, and the third-party headset is connected to the first electronic device through a non-customized protocol. Taking Bluetooth connection as an example, the electronic device is connected to the headset of the same ecosystem through a customized Bluetooth protocol. When connected, the Bluetooth broadcast data format sent by the headset of the same ecosystem is the Bluetooth broadcast data format customized by the manufacturer of the headset and the first electronic device. The Bluetooth broadcast data of the headset of the same ecosystem usually includes information related to the functions customized by the manufacturer of the headset and the first electronic device. The first electronic device and the third-party headset are connected through a non-customized Bluetooth protocol. The non-customized Bluetooth protocol is usually a standard Bluetooth protocol. The Bluetooth broadcast data format sent by the third-party headset is the standard Bluetooth broadcast data format.

[0074] As shown in Figure 1, in a traditional connection method between a third-party headset and a first electronic device, such as connecting via Bluetooth, after receiving a Bluetooth broadcast message from the third-party headset, the first electronic device cannot directly connect to the third-party headset. Instead, the user must open the settings interface, find Bluetooth in the settings interface, open the Bluetooth interface, and select the third-party headset device to connect to in the Bluetooth interface to pair and connect. After the third-party headset is successfully connected, the Bluetooth interface is displayed as shown in Figure 1. The audio device is the successfully connected third-party headset. After receiving the Bluetooth broadcast message from the headset in the same ecosystem, the first electronic device can directly connect to the third-party headset without the user opening the settings interface. Furthermore, after the headset in the same ecosystem is connected to the first electronic device, a pop-up window will appear on the first electronic device, allowing the first electronic device to manage the headset in the same ecosystem in response to the actions taken in the pop-up window. After the third-party headset is connected to the first electronic device, no pop-up window will appear on the first electronic device, and the first electronic device cannot manage the third-party headset. The third-party headset can only provide simple audio output.

[0075] In order to manage third-party headphones and improve the user experience, the present application provides a device interaction method, an electronic device and a storage medium.

[0076] For example, taking the electronic device as a mobile phone as an example, FIG2 shows a schematic structural diagram of an electronic device provided in an embodiment of the present application.

[0077] 2 , the electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a display 193, a subscriber identification module (SIM) card interface 194, and a camera 195. The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

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

[0079] The controller can be the nerve center and command center of the electronic device. The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0080] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0081] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0082] The charging management module 140 is used to receive charging input from a power supply device (e.g., a charger, laptop charger, etc.). The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input through the wireless charging coil of the electronic device.

[0083] While charging the battery 142, the charging management module 140 can also power the electronic device through the power management module 141. Specifically, the battery 142 can be composed of multiple batteries connected in series. The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110.

[0084] 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 provides power to the processor 110, the internal memory 121, the display 193, the camera 195, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery voltage, current, battery cycle count, and battery health status (leakage, impedance). In other embodiments, the power management module 141 can also be provided in the processor 110.

[0085] The external memory interface 120 can be used to connect to an external non-volatile memory device to expand the storage capacity of the electronic device. The external non-volatile memory device communicates with the processor 110 via the external memory interface 120 to implement data storage. For example, files such as music and videos can be stored in the external non-volatile memory device.

[0086] The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM). The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (such as machine instructions) of the operating system or other running programs, and can also be used to store user and application data, etc. The non-volatile memory can also store executable programs and store user and application data, etc., and can be loaded into the random access memory in advance for direct reading and writing by the processor 110. In an embodiment of the present application, a diffusion model may be stored in the internal memory 121. The internal memory 121 may also store relevant models that can convert images into noise images and text identifiers, or may also store noise images and text identifiers corresponding to multiple images.

[0087] A touch sensor, also known as a "touch control device," can be provided on the display screen 193. The touch sensor and the display screen 193 form a touch screen, also known as a "touch screen." The touch sensor is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided via the display screen 193. In other embodiments, the touch sensor can also be provided on the surface of the electronic device, at a location different from that of the display screen 193.

[0088] The pressure sensor is used to sense pressure signals and can convert pressure signals into electrical signals. In some embodiments, the pressure sensor can be set on the display screen 193. There are many types of pressure sensors, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. When a touch operation is applied to the display screen 193, the electronic device monitors the touch operation intensity based on the pressure sensor. The electronic device can also calculate the position of the touch based on the monitoring signal of the pressure sensor. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, the 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 acts on the short message application icon, the instruction to create a new short message is executed.

[0089] In some embodiments, the electronic device may include 1 or N cameras 195, where N is a positive integer greater than 1. In an embodiment of the present application, the type of camera 195 can be distinguished based on the hardware configuration and physical location. For example, the camera provided on the side of the display screen 193 of the electronic device can be called a front camera, and the camera provided on the side of the back cover of the electronic device can be called a rear camera; for another example, a camera with a short focal length and a larger viewing angle can be called a wide-angle camera, and a camera with a long focal length and a small viewing angle can be called a normal camera. Among them, the length of the focal length and the size of the viewing angle are relative concepts, and there are no specific parameters to limit them. Therefore, wide-angle cameras and normal cameras are also relative concepts, and can be specifically distinguished based on physical parameters such as focal length and viewing angle.

[0090] The electronic device implements display functionality through a GPU, display screen 193, and an application processor. The GPU is a microprocessor for image processing that connects display screen 193 and the application processor. The GPU is 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 modify display information.

[0091] The electronic device can implement a shooting function through an ISP, a camera 195, a video codec, a GPU, a display screen 193, and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information. In the embodiment of the present application, the GPU function is used during the frame drawing process of each image frame to achieve better display effects and performance of the final displayed image.

[0092] The ISP processes data fed back by camera 195. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and converted into a visible image. The ISP can also perform algorithmic optimization on image noise and brightness. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be incorporated into camera 195. Camera 195 is used to capture still images or video.

[0093] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when an electronic device selects a frequency, the DSP performs a Fourier transform on the frequency energy.

[0094] Display screen 193 is used to display images, videos, and the like. Display screen 193 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, or a quantum dot light-emitting diode (QLED). In some embodiments, the electronic device can include one or N display screens 193, where N is a positive integer greater than one.

[0095] In an embodiment of the present application, the display screen 193 can be used to display the interface of the electronic device (for example, the desktop, the lock screen interface, etc.), and display images stored in the electronic device (for example, wallpapers, photos, etc.), or images captured by any one or more cameras 195 in the interface.

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

[0097] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in an electronic device can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization.

[0098] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to electronic devices. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, filter, amplify, and perform other processing on the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0099] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted 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 being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 193. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0100] The wireless communication module 160 can provide wireless communication solutions for electronic devices, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc. The wireless communication module 160 can be one or more devices that integrate 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 for radiation through the antenna 2.

[0101] SIM card interface 194 is used to connect a SIM card. A SIM card can be connected to and disconnected from the electronic device by inserting or removing it from the SIM card interface 194. An electronic device may support one or more SIM card interfaces. SIM card interface 194 can support Nano SIM cards, Micro SIM cards, and SIM cards. Multiple cards can be inserted into the same SIM card interface 194 simultaneously. SIM card interface 194 is also compatible with external memory cards. Electronic devices interact with the network through SIM cards to implement functions such as call and data communications. Each SIM card corresponds to one user number.

[0102] It is understood that the interface connection relationship between the modules illustrated in the embodiments of the present invention is only a schematic illustration and does not constitute a structural limitation of the electronic device. In other embodiments of the present application, the electronic device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0103] Of course, it is understood that FIG2 is merely an example of an electronic device in the form of a mobile phone. If the electronic device is a tablet computer, handheld computer, PC, PDA, wearable device (such as a smart watch, smart bracelet), or other device form factors, the structure of the electronic device may include fewer or more structures than shown in FIG1, and this is not limited here.

[0104] It is understandable that, in general, the realization of electronic device functions requires not only hardware support but also software cooperation. The software system of the electronic device can adopt a layered architecture, event-driven architecture, micro-core architecture, micro-service architecture, or cloud architecture. Taking the system as an example, the software structure of the electronic device is illustrated.

[0105] Figure 3 is a schematic diagram of the layered architecture of the software system of the electronic device provided in an embodiment of the present application. The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces (e.g., APIs).

[0106] In some examples, as shown in FIG3 , in an embodiment of the present application, the software of an electronic device is divided into five layers, namely, from top to bottom, the application layer, the framework layer (or application framework layer), the system library and Android runtime (Android runtime), the HAL layer (hardware abstraction layer), and the driver layer (or kernel layer). Among them, the system library and Android runtime can also be called the local framework layer or native layer.

[0107] Among them, the application layer may include a series of applications. As shown in Figure 3, the application layer may include applications (APP) such as camera, gallery, calendar, map, WLAN, Bluetooth, music, video, short message, call, navigation, instant messaging, wallpaper, Honor Smart Space and automatic discovery. Among them, the Honor Smart Space application is an application for aggregating and managing external devices connected to electronic devices, and the automatic discovery application is an application for discovering external devices. The Honor Smart Space application may also be referred to as a device management space application. The Honor Smart Space application may be an application pre-installed by the manufacturer of the electronic device for the electronic device, or it may be an application that the user downloads from the application store and then installs when using the electronic device. The automatic discovery application may be a system application, such as an application pre-installed by the manufacturer of the electronic device for the electronic device. In some examples, the automatic discovery application may not display an icon on the home screen of the electronic device.

[0108] The 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 or services. For example, the application framework layer may include an activity manager, a window manager, a content provider, an audio service, a view system, a telephony manager, a resource manager, a notification manager, a package manager, etc., but the embodiments of this application do not impose any restrictions on this.

[0109] The 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, take screenshots, etc.

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

[0111] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0112] The phone manager is used to provide communication functions for electronic devices. For example, the phone manager can manage the call status of the call application (including initiation, connection, and hang up).

[0113] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0114] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0115] Package Manager in The system is used to manage application packages. It allows applications to obtain detailed information about installed applications and their services, permissions, etc. The package manager is also used to manage events such as application installation, uninstallation, and upgrades.

[0116] System libraries can include multiple functional modules, such as the surface manager, media libraries, OpenGL ES, and SGL. The surface manager manages the display subsystem and provides fusion of 2D and 3D layers for multiple applications. The media library supports playback and recording of various common audio and video formats, as well as still image files. The media library supports a variety of audio and video codecs, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG. OpenGL ES is used for 3D graphics drawing, image rendering, compositing, and layer processing. SGL is a drawing engine for 2D drawing. The Android runtime consists of the core library and the ART virtual machine. The Android runtime is responsible for scheduling and management of the Android system. The core library consists of two parts: one for Java language functions and the other for the Android core library. The application layer and application framework layer run in the ART virtual machine. The ART virtual machine executes Java files from the application layer and application framework layer as binary files. The ART virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0117] The HAL layer is an interface layer located between the operating system kernel and the hardware circuit. Its purpose is to abstract the hardware. It hides the hardware interface details of a specific platform and provides a virtual hardware platform for the operating system, making it hardware-independent and portable across multiple platforms. The HAL layer provides a standard interface to display device hardware capabilities to the higher-level Java API framework (i.e., the framework layer). The HAL layer contains multiple library modules, each of which implements an interface for a specific type of hardware component, such as the audio HAL audio module, the bluetooth HAL Bluetooth module, the camera HAL camera module (also known as the camera HAL or camera hardware abstraction module), and the sensors HAL sensor module (or sensor service).

[0118] The kernel layer is the layer between hardware and software. The kernel layer includes at least a display driver, a camera driver, an audio driver, a sensor driver, a battery driver, and other components, though this application does not limit these. Specifically, the sensor driver may include drivers for each sensor included in the electronic device, such as the ambient light sensor driver. For example, the ambient light sensor driver may respond to an instruction or command from the sensor module to acquire detection data and promptly transmit the detection data from the ambient light sensor to the sensor module.

[0119] The technical solutions provided in the embodiments of the present application can all be implemented in a first electronic device having the above-mentioned hardware architecture or software architecture.

[0120] The embodiments of the present application mainly solve the problem of being unable to manage third-party headphones.

[0121] The method flow of the embodiment of the present application is shown in FIG4 , wherein the automatic discovery application and the Honor Smart Space application are both installed on the first electronic device. The method flow mainly includes the following steps:

[0122] S401: A third-party headset is communicatively connected to a first electronic device.

[0123] When the third-party headset is communicatively connected to the first electronic device, the first electronic device may identify the third-party headset as an external device, and then determine the identity of the third-party headset after the communication connection is established.

[0124] The third-party headset can be connected to the first electronic device through communication in a variety of ways, for example, through Bluetooth or through Near Field Communication (NFC).

[0125] Taking Bluetooth connection as an example, when a third-party headset is in a searchable state, it will send a Bluetooth broadcast signal so that other nearby devices can detect and establish a connection.

[0126] After the first electronic device turns on the Bluetooth function in the settings interface, it will actively search for nearby Bluetooth devices, including third-party headphones. By receiving the Bluetooth broadcast sent by the third-party headphones, the first electronic device can find the third-party headphones and send a connection request to the third-party headphones. After receiving the connection request, the third-party headphones will verify and perform handshake protocol processing, and send a connection response signal to the first electronic device. After the first electronic device receives the connection response signal, the first electronic device and the third-party headphones will negotiate the communication frequency based on the information in the connection response signal. The two parties will negotiate which frequency to use for communication to ensure that both parties can transmit data on the same frequency. During the connection establishment process, the first electronic device and the third-party headphones also need to perform an authorization and authentication process to ensure the security of the connection. The authorization and authentication process may include personal identification number (PIN) verification, digital certificate authentication, etc. to ensure the security and legitimacy of the connection.

[0127] After the connection is successful, data can be transmitted between the first electronic device and the third-party headset.

[0128] The Bluetooth broadcasts sent by third-party headsets can include the following information:

[0129] Device Name: The name of the third-party headset, usually a set of characters or numbers preset by the manufacturer.

[0130] Device Category: Indicates the device type to which the third-party headset belongs, such as audio device, mouse, keyboard, etc.

[0131] Service information: describes the services supported by the third-party headset so that the first electronic device can understand what interactive operations they can perform with the third-party headset, such as AUDIO_VIDIO_WEARABLE_HEADSET or AUDIO_VIDIO_HEADPHONES.

[0132] Bluetooth version: Indicates the Bluetooth specification version that the Bluetooth headset complies with.

[0133] Other parameters: May also include additional information such as the Bluetooth headset's MAC address and signal strength.

[0134] The above information is encoded into a broadcast packet and sent via the Bluetooth module. When a nearby first electronic device detects this broadcast packet, it can parse the information. After receiving the broadcast packet data sent by the third-party headset, the first electronic device can store the broadcast packet data in the driver layer.

[0135] After the first electronic device establishes a connection with the third-party headset, the Bluetooth driver of the first electronic device driver layer can send the broadcast packet data to the Android native interface through the access control list (ACL) broadcast.

[0136] In some embodiments, when a third-party headset establishes a connection with a first electronic device for the first time, if the first electronic device has pre-stored a whitelist of Bluetooth broadcast data formats for the third-party headset, the first electronic device can automatically connect to the third-party headset after comparing the Bluetooth broadcast data format of the third-party headset with the whitelist and determining that the Bluetooth broadcast data format of the third-party headset is on the whitelist. If the first electronic device does not pre-store a whitelist of Bluetooth broadcast data formats for the third-party headset, or if the first electronic device determines that the Bluetooth broadcast data format of the third-party headset is not on the whitelist, the user can open the settings interface 100 shown in FIG5 . The settings interface 100 includes a fifth control 101 for configuring Bluetooth settings. In response to a user triggering operation on the fifth control 101, the first electronic device displays a Bluetooth settings interface 200 shown in FIG6 . The Bluetooth settings interface 200 shown in FIG6 includes a device name label 202 and a sixth control 201. The device name label 202 displays the name of the first electronic device. The text on the sixth control 201 can include the name and model of the third-party headset. A sixth control 201 is displayed in the available device options. In response to a user's operation on the sixth control 201, the first electronic device is connected to the third-party headset. After the connection is established, the first electronic device may display a Bluetooth setup interface 300 as shown in FIG7 . The Bluetooth setup interface 300 includes a list 301 of paired devices. The third-party headset is added to the list 301 of paired devices.

[0137] S402. Determine whether the third-party headset is communicating with the first electronic device for the first time. If so, execute step S403. If not, execute step S413.

[0138] In some embodiments, taking Bluetooth as an example, the first electronic device may store the MAC address information of previously connected Bluetooth devices, for example, by storing the MAC address of the previously connected Bluetooth device in a connected device list. Then, after the first electronic device establishes a communication connection with a third-party headset, the first electronic device may check whether the MAC address of the third-party headset exists in the connected device list. If not, the first electronic device may determine that the third-party headset is connected for the first time; if so, the first electronic device may determine that the third-party headset is not connected for the first time.

[0139] S403: When the third-party headset is connected to the first electronic device for communication for the first time, the automatic discovery application obtains service information of the third-party headset.

[0140] In some embodiments, the automatic discovery application obtains the service information of the third-party headset by accessing the Android native interface. In some embodiments, the service information of the third-party headset can be obtained by accessing the Android native interface bluetoothClass.getDeviceClass().

[0141] S404: The automatic discovery application determines whether the third-party headset is an audio head-mounted device based on the service information of the third-party headset.

[0142] In some embodiments, the automatic discovery application can determine whether the third-party headset is an audio head-mounted device by determining whether the obtained service information includes a first identifier, where the first identifier can be AUDIO_VIDIO_WEARABLE_HEADSET or AUDIO_VIDIO_HEADPHONES.

[0143] The obtained service information includes the two services AUDIO_VIDIO_WEARABLE_HEADSET and AUDIO_VIDIO_HEADPHONES, and the process jumps to S405.

[0144] The obtained service information does not include the AUDIO_VIDIO_WEARABLE_HEADSET or AUDIO_VIDIO_HEADPHONES services, and the process ends.

[0145] S405: Automatically discover the application and obtain the device name of the third-party headset.

[0146] In some implementations, after the automatic discovery application determines that the third-party headset is an audio head-mounted device, it can obtain the device name of the third-party headset.

[0147] In some implementations, the automatic discovery application can obtain the name information of the third-party headset by accessing the Android native interface. For example, the automatic discovery application can access the getName interface in the BluetoothDevice.java class to obtain the device name of the third-party headset.

[0148] S406: The automatic discovery application determines whether the device name of the third-party headset exists in a preset whitelist.

[0149] If the device name of the third-party headset exists in the preset white list, S409 is executed. If the device name of the third-party headset does not exist in the preset white list, S407 is executed.

[0150] Among them, the preset whitelist is a whitelist preset by the first electronic device for third-party headphones of known brands and names. In this way, after the first electronic device obtains the name information of the third-party headphones, it finds the obtained name information in the preset whitelist, and can determine that the external device is a headphone of a known brand.

[0151] For example, the automatic discovery application can determine whether the third-party headset is in communication with the first electronic device based on whether the device name of the third-party headset is in a preset whitelist. If the device name of the third-party headset is in the preset whitelist, it can be determined that the third-party headset is a headset of a known brand. If the device name of the third-party headset is not in the preset whitelist, it is necessary to determine the identity of the third-party headset through other means, for example, determining the identity of the third-party headset through S407.

[0152] S407: Automatically discover the application and obtain the battery information of the third-party headset.

[0153] In some embodiments, the automatic discovery application can obtain the battery level information of the third-party headset by accessing the Android native interface. In some embodiments, the automatic discovery application can access the getBatteryLevel interface in the BluetoothDevice.java class to obtain the battery level information of the third-party headset.

[0154] S408: The automatic discovery application determines whether the battery level information of the third-party headset can be obtained.

[0155] Exemplarily, the automatic discovery application may also determine whether the third-party headset is communicatively connected to the first electronic device based on whether the battery level information of the third-party headset can be obtained. If the battery level information of the third-party headset can be obtained, it is determined that the third-party headset is communicatively connected to the first electronic device. If the battery level information of the third-party headset cannot be obtained, it is determined that the third-party headset is not communicatively connected to the first electronic device.

[0156] Some brands of third-party headphones do not provide power information to the first electronic device. Therefore, when the automatic discovery application of the first electronic device accesses the Android native interface, the power information cannot be obtained.

[0157] If the battery information of the third-party headset can be obtained, S409 is executed. If the battery information of the third-party headset cannot be obtained, the process ends.

[0158] In some embodiments, after determining that the third-party headset is an audio headset, the automatic discovery application may first obtain the name information of the third-party headset. After obtaining the name information of the third-party headset and determining that the name of the third-party headset does not belong to the third-party headset whitelist, the automatic discovery application may then obtain the battery information of the third-party headset. In other embodiments, the automatic discovery application may directly obtain the battery information of the third-party headset after determining that the third-party headset is an audio headset. If the battery information of the third-party headset is obtained, it can be determined that the headset that is communicatively connected to the first electronic device is the third-party headset, and step S409 is executed. If the battery information of the third-party headset cannot be obtained, the name information of the third-party headset is obtained again. If the name information of the third-party headset is in the preset whitelist, it is determined that the headset that is communicatively connected to the first electronic device is a known brand, and step S409 is executed. If the name information of the third-party headset is not in the preset whitelist, the process ends.

[0159] S409: Automatically discover the application and pop up the first pop-up window.

[0160] In some embodiments, the first pop-up interface 400 shown in FIG8 includes a first pop-up window 800, which includes an icon 8012 of the headphones and an icon 8011 of the headphone case, battery information 802, the name and model information 803 of the third-party headphones, and a first control 804. The name and model information 803 of the third-party headphones is the name and model information of the third-party headphones read by the first electronic device. A first control 804 may be displayed at the bottom of the first pop-up window 800. The first control 804 is used to trigger the display of the management interface. For example, the first control 804 may include text such as "Experience Now." To highlight the text, a different color may be used below the text than the connection success interface to quickly draw the user's attention to the text "Experience Now." In response to an operation on the first control 804, the first electronic device may display the first interface to guide the user to further manage the third-party headphones. Accordingly, a seventh control 805 may also be displayed on the first pop-up window 800 to trigger the closing of the first pop-up window 800. In response to the user clicking the seventh control 805, the first electronic device may close the first pop-up window 800. In some implementations, the seventh control 805 may be a text such as “Got it”.

[0161] After determining that the third-party headset is in communication connection with the first electronic device, the first electronic device can assign a second identifier to the third-party headset, and the second identifier can be a Model ID. In the first pop-up interface 400 shown in Figure 8, icon 801 can be bound to the Model ID. For third-party headsets, a unified Model ID is set, and the icon 801 of the headset in the first pop-up interface 400 is also the same icon. Correspondingly, for self-developed headsets, different Model IDs can be assigned respectively, and the icon 801 of the headset in the first pop-up interface 400 is a different icon.

[0162] In some embodiments, the first electronic device may also assign different Model IDs to third-party headphones based on the type of headphone, and different Model IDs correspond to different icons. The icons may include a headphone icon 8012 and a headphone box icon 8011. Furthermore, in the first pop-up interface 400 shown in FIG8 , the icons 801 for different headphone types may be different.

[0163] When displaying the first pop-up interface 400 , the first electronic device may search for icons corresponding to the Model IDs of headphones of different ecosystems, generate and display the icon 801 in the first pop-up interface 400 based on the found icons.

[0164] S410. The Honor Smart Space application responds to the operation on the first control 804 of the first pop-up interface and displays the first interface of the third-party headset.

[0165] For third-party headphones that are connected to the first electronic device for the first time, the user needs to be guided to add the third-party headphones to the Honor Smart Space application. Therefore, in some embodiments, when the user performs an operation on the first control 804, the first interface displayed may be the first interface 900 of the third-party headphones as shown in Figure 9. The first interface 900 of the third-party headphones includes a second control 901, an eighth label 902, and a ninth label 903. The second control 901 includes text such as "Add". In response to the operation on the second control 901, the first electronic device can add the third identifier of the third-party headphones to the first list. The third identifier may be a Media Access Control (MAC) address. The first list is a list of the first account, and the first account is the account logged in to the Honor Smart Space. The eighth label 902 includes the words "There are audio devices to add", and the ninth label 902 includes the words "Take care of the audio device".

[0166] Based on the above implementation, when a third-party headset is connected to the first electronic device for the first time, after displaying the first pop-up interface 400, the first electronic device responds to the operation on the first control 804, and the first electronic device displays the first interface 900 of the third-party headset, and the first interface 900 includes a second control 901. Then, in response to the operation on the second control 901, the first electronic device can add the MAC address of the third-party headset to the first list. In this way, when the third-party headset is connected to the first electronic device for the first time, the MAC address of the third-party headset is added to the first list. In this way, the third-party headset can be managed in the Honor Smart Space application later.

[0167] S411. The Honor Smart Space application responds to the operation on the second control 901, adds the MAC address of the third-party headset to the device management space account, and displays a second pop-up window indicating that the addition is complete.

[0168] In some embodiments, after the user operates the second control 901, the MAC address of the third-party headset can be added to the first list and a second pop-up window can be displayed. In some embodiments, when only the MAC address of the third-party headset is added to the first list, the second pop-up window can be displayed as the second pop-up window 1004 in the second pop-up window interface 1000 as shown in Figure 10. The second pop-up window 1004 includes a first label 1001, a third control 1002, and an eighth control 1003. The first label 1001 includes the words "Added successfully, you can access the device on the application homepage." In some embodiments, the third control 1002 can be displayed at the bottom of the second pop-up window 1004. Among them, the third control 1002 can include the words "Experience now". In response to the operation on the third control 1002, the first electronic device can display the second interface. In some embodiments, an eighth control 1003 for closing the second pop-up interface 1000 may be further provided on the second pop-up window 1004, for example, at the lower portion of the second pop-up window 1004. In response to a user clicking on the eighth control 1003, the first electronic device closes the second pop-up interface 1000. The text on the eighth control 1003 may include "I understand."

[0169] In some embodiments, if the MAC addresses of multiple audio devices are added to the first list, a second pop-up window may be displayed as second pop-up window 1004, as shown in FIG11 . Second pop-up window 1004 includes a second label 1101, a third control 1002, and a ninth control 1103. The second label may include the text "Added successfully and aggregated as an audio device on the app homepage." In some embodiments, second pop-up window 1004, for example, at the bottom of second pop-up window 1000, may also display a third control 1002 for a second interface of a third-party headset. Third control 1002 may include the text "Experience now." Actions on third control 1002 trigger the display of the second interface. In some embodiments, second pop-up window 1000 may also include a ninth control 1103, for example, at the bottom of second pop-up window 1004. Actions on ninth control 1103 cause the first electronic device to close second pop-up interface 1000. For example, ninth control 1103 may include the text "I understand."

[0170] Based on the above implementation, after the user operates the second control 901 of the first interface 900, the first electronic device can add the MAC address of the third-party headset to the first list and display a second pop-up window indicating that the addition is complete. This can inform the user that the action of adding the MAC address of the third-party headset to the first list has been completed, giving the user a better user experience. In addition, the second pop-up window includes a third control 1002 that triggers the display of the second management interface of the third-party headset. In response to the user's operation on the third control 1002, the first electronic device can display the second interface of the third-party headset, allowing the user to manage the third-party headset through the second interface and understand the usage of the third-party headset, for example, the battery information of the third-party headset. This provides the user with a better user experience.

[0171] S412. The Honor Smart Space application responds to the operation on the third control 1002 and displays the second interface of the third-party headset.

[0172] In some embodiments, after the user triggers the third control 1002, the second interface 1200 shown in Figure 12 can be displayed. The second interface 1200 includes a third label 1201, a fourth label 1202, a first entry 1203, a tenth label 1208, and an eleventh label 1209. The third label 1201 is used to display the connection status of different ecological headphones, including the text "Connected". In some embodiments, the fourth label 1202 displays the battery information of the third-party headphones. The first entry 1203 is used to access the currently available sound effect information of the third-party headphones. For third-party headphones, it may not be possible to call the sound effects of the third-party headphones for selection. Therefore, in some embodiments, optional sound effects of the first electronic device can be provided for the user to select, and after the user selects, they are played through the third-party headphones. The tenth label 1208 is used to display the type and name information of different ecological headphones, and the eleventh label 1209 displays the headphone picture information.

[0173] In some embodiments, in response to an operation on third control 1002, the first electronic device displays a second interface 1200 as shown in FIG13 . Second interface 1200 may also display optional sound quality information, allowing the user to select sound quality based on their preferences. In some embodiments, second interface 1200 may also include a second entry 1204 for accessing recommended functions for third-party headphones and a fifth tab 1205. Fifth tab 1205 includes text, and second entry 1204 is displayed below fifth tab 1205. Second entry 1204 includes recommended functions for third-party headphones. These functions may be actions that are executed when a set trigger condition is triggered. For example, a function that reminds the user to drink water on time after wearing the headphones, a function that reminds the user to take medicine on time after wearing the headphones, a function that plays music using a preset player after wearing the headphones, or a function that generates an alarm when a set condition is detected after wearing the headphones. The trigger condition may be related to the headphones, the executable operation may be related to the headphones, or both the trigger condition and the executable operation may be related to the headphones. The trigger condition related to the headphones may be that the headphones are in communication with the first electronic device. Executable operations related to headphones can include playing music through the headphones or playing reminders through the headphones. In some embodiments, the second interface 1200 may also include a third entry 1206 for accessing functions previously set by the user for third-party headphones. For example, if a function has been set for the third-party headphones to play music using a set player after wearing the headphones, the second interface 1200 may include a sixth tab 1207. If the sixth tab 1207 has the words "My Scene", the third entry 1206 may be displayed below the sixth tab 1207. For example, if the user has previously set a function for the third-party headphones to display the function of playing music using a set player after wearing the headphones, the third entry 1206 may display an icon related to the function of playing music using the set player after wearing the headphones.

[0174] In some embodiments, in response to a user clicking on the third entry 1206, a third interface for setting functions can be displayed. As shown in FIG14 , the third interface 1400 may include a tenth control 1401 for setting trigger conditions, an eleventh control 1402 for setting executable operations, and a twelfth control 1403 for creating functions. Furthermore, the third interface 1400 may include a twelfth label 1404, a thirteenth label 1405, and a fourteenth label 1406. The twelfth label 1404 includes the text "Headphone Function," the thirteenth label 1405 includes the label "When the following conditions occur," and the fifteenth label includes the text "Executable Operations." As shown in FIG15 , in response to a user clicking on the tenth control 1401, the first electronic device may be operated to display a fourth interface 1500 as shown in FIG15 . The fourth interface 1500 includes a first settings box 1501 for setting trigger conditions. In response to a user selecting an element displayed in the first settings box 1501, the first electronic device may set the trigger conditions. As shown in Figure 16, in response to a user's operation on the eleventh control 1402, the first electronic device can display a fifth interface 1600, which includes a second settings box 1601. In response to the user selecting an option displayed in the second settings box 1601, the first electronic device can set an executable operation. The trigger condition here can be that the headset is in communication with the first electronic device, or a time is set. The executable operation here can be playing a reminder through the headset, or playing music through a set player. After the trigger condition and the corresponding executable operation are set, the first electronic device can perform the corresponding executable operation when it detects that the trigger condition is met. For example, if the trigger condition and the corresponding executable operation are set as "When the headset is in communication with the first electronic device, use the set player to play music," then when the first electronic device detects that the third-party headset is in communication with the first electronic device, it can use the set player to play music.

[0175] S413: When the automatic discovery application is not the first time that the third-party headset is communicating with the first electronic device, a first pop-up interface 400 is popped up.

[0176] In some embodiments, the first pop-up interface 400 may be as shown in FIG. 8 , where the first control 804 in the first pop-up interface 400 is used to trigger the display of the second interface 1200 .

[0177] S414. The Honor Smart Space application responds to the operation of the first control 804 on the first pop-up interface 400 and displays the second interface 1200 of the third-party headset.

[0178] If the third-party headset is not connected for the first time, when the user triggers the first control 804 on the first pop-up interface 400, the second interface 1200 of the third-party headset is directly displayed.

[0179] In some embodiments, if a user closes the second interface 1200 of a third-party headset and wishes to access it again, they can access the Honor Smart Space app from the sixth interface 1700 shown in FIG. The sixth interface 1700 displays the control center of the first electronic device and can be displayed in response to a user's pull-down operation on the top right side of the first electronic device. The entrance to the Honor Smart Space app can be displayed as the fourth entrance 1701 shown in FIG. In some embodiments, the entrance to the Honor Smart Space app can also be configured as the Honor Smart Space app icon 1801 on the seventh interface 1800 shown in FIG. In response to a user clicking on the app icon 1801, the first electronic device displays the interface for the Application Management Space app. In some embodiments, the Honor Smart Space app can also be triggered to open via voice commands. For example, the first electronic device can open the Honor Smart Space app by receiving a voice command such as "Please open the device management space." In some embodiments, the Honor Smart Space app can also open in response to gesture commands, such as a swipe down gesture. When the first electronic device detects a user making a swipe down gesture on the first electronic device's screen, the first electronic device can open the Honor Smart Space app.

[0180] The Honor Smart Space app can access the second interface 1200 of the third-party headset. In some embodiments, a thirteenth control can be set in the Honor Smart Space app interface to trigger the display of the second interface 1200 of the third-party headset. In response to a user's operation on the thirteenth control, the second interface 1200 of the third-party headset is displayed. The main interface of the device management space can be the eleventh interface 1900 shown in Figure 19. The eleventh interface 1900 includes a thirteenth control 1901, a fifteenth tab 1902, a fourth entry 1903, a fifth entry 1904, a sixteenth tab 1905, and a switch bar 1906. The thirteenth control 1901 can display an image of the headset, the name and model of the headset, and the battery level of the headset. In response to a user's operation on the thirteenth control 1901, for example, when the user clicks on the thirteenth control 1901, the first electronic device can display the second interface 1200 of the third-party headset. The thirteenth control 1901 is displayed below the sixteenth tab 1905, which includes the text "All Devices." The fifteenth label 1902 is displayed in the upper left corner of the ninth interface 1900, and the fifteenth label 1902 includes the text "My Home". The fourth entrance 1903 is the entrance to access commonly used devices, which may include icons and names of commonly used devices. And in response to operations on the icons and names of any commonly used devices, the first electronic device displays the interface of the corresponding commonly used device. There may be multiple fourth entrances 1903, each corresponding to a different commonly used device. The fifth entrance 1904 is the entrance to access commonly used functions, which may include icons and names of commonly used functions, and in response to operations on the icons and names of any commonly used functions, the first electronic device calls the corresponding external device to perform the corresponding function. There may be multiple fifth entrances 1904, each corresponding to a different commonly used function. The switch bar 1906 is used to display different interfaces of the device management control application, in which icons of different interfaces are displayed, and the first electronic device can switch interfaces in response to operations on icons of different interfaces.

[0181] In some embodiments, when the third-party headset is not the only audio device connected to the first electronic device, a fourteenth control that triggers the display of the third interface can be set in the interface of the Honor Smart Space application, where the third interface is used to manage audio devices. When the user performs an operation on the fourteenth control, the third interface is displayed. Among them, the bth control can be displayed below the words "All Devices". The fourteenth control may include the words "Audio Device". In response to the user's operation on the bth control, for example, the user clicks on the fourteenth control, the third interface can be displayed. On the third interface, a fifteenth control is provided that triggers the display of the second interface 1200 of the third-party headset. The fifteenth control can be provided with an image of the headset, the name and model of the headset, and the battery level of the headset. In response to the user's operation on the fifteenth control, for example, when the user clicks on the fifteenth control, the first electronic device can display the second interface 1200 of the third-party headset.

[0182] In some embodiments, if the user clicks the seventh control 805 while the first electronic device displays the first pop-up interface 400, the first electronic device will terminate the process directly, and the MAC address of the third-party headset will not be added to the Honor Smart Space app account. However, when the Honor Smart Space app interface is displayed, the ninth interface 2000 shown in Figure 20 will be displayed. The ninth interface 2000 includes a seventh label 2001, a fourteenth control 2002, and a fifteenth control 2003. The seventh label 2001 includes the words "Discover a device, connect?", the fourteenth control 2002 includes the words "Ignore", and the fifteenth control 2003 includes the words "Add". In response to the user clicking the fourteenth control 2002, the first electronic device does not add the MAC address of the third-party headset to the first list. In response to the user clicking the fifteenth control 2003, the first electronic device adds the MAC address of the third-party headset to the first list. The ninth interface 2000 may also include elements from the eighth interface 1900. The ninth interface 2000 may also include a fifteenth tab 1902, a fourth entry 1903, a fifth entry 1904, a sixteenth tab 1905, and a switch bar 1906. The seventh tab 2001, the fourteenth control 2002, and the fifteenth control 2003 are generally disposed between the fifteenth tab 1902 and the fourth entry 1903.

[0183] As shown in FIG21 , the present application further provides a device interaction method, which is applied to a first electronic device. The device interaction method includes:

[0184] S2101: The first electronic device establishes a connection with the second electronic device, wherein the second electronic device and the first electronic device are connected via a non-customized connection protocol;

[0185] The second electronic device is a third-party headset.

[0186] S2102: The first electronic device obtains device information of the second electronic device;

[0187] When the first electronic device and the second electronic device are connected for the first time, S2102 may be performed with reference to steps S403 , S405 , and S407 .

[0188] When the first electronic device and the second electronic device are not connected for the first time, the device information of the second electronic device may be the Model ID of the second electronic device.

[0189] S2103: The first electronic device determines whether the second electronic device is an electronic device of a specified type based on the device information of the second electronic device;

[0190] When the first electronic device and the second electronic device are not connected for the first time, the first electronic device determines that the device type of the second electronic device is a third-party headset according to the Model ID of the second electronic device.

[0191] In one possible implementation, when a first electronic device and a second electronic device are connected for the first time, the first electronic device determines whether the second electronic device is an electronic device of a specified type based on device information of the second electronic device, including: determining that the second electronic device and the first electronic device are connected for communication for the first time; obtaining service information of the second electronic device; in response to the service information of the second electronic device including an identifier corresponding to an audio head-mounted device, and the service information of the second electronic device including power information of the second electronic device, the first electronic device determines that the second electronic device is an electronic device of the specified type; in response to the service information of the second electronic device not including an identifier corresponding to an audio head-mounted device, the first electronic device determines that the second electronic device is not an electronic device of the specified type.

[0192] Based on the above implementation method, it is possible to determine that the second electronic device and the first electronic device are communicating and connecting for the first time; obtain the service information of the second electronic device; in response to the service information of the second electronic device including the identifier corresponding to the audio head-mounted device, and the service information of the second electronic device including the power information of the second electronic device, the first electronic device determines that the second electronic device is an electronic device of a specified type; in response to the service information of the second electronic device not including the identifier corresponding to the audio head-mounted device, the first electronic device determines that the second electronic device is not an electronic device of the specified type, thereby determining whether the second electronic device belongs to the specified type of electronic device by obtaining the service information and power information of the second electronic device, thereby effectively determining whether the first pop-up window 800 needs to be popped up.

[0193] In one possible implementation, when a first electronic device and a second electronic device are connected for the first time, the first electronic device determines whether the second electronic device is an electronic device of a specified type based on the device information of the second electronic device, and also includes: in response to the service information of the second electronic device including an identifier corresponding to an audio head-mounted device, and the device name of the second electronic device is in a preset whitelist, the first electronic device determines that the second electronic device is an electronic device of the specified type.

[0194] Based on the above implementation method, it is possible to determine that the second electronic device is communicating with the first electronic device for the first time; obtain the service information of the second electronic device; in response to the service information of the second electronic device including an identifier corresponding to the audio head-mounted device, and the device name of the second electronic device is in a preset whitelist, the first electronic device determines that the second electronic device is an electronic device of a specified type, thereby determining whether the second electronic device belongs to an electronic device of the specified type through the service information and device name of the second electronic device, thereby effectively determining whether the first pop-up window 800 needs to be popped up.

[0195] S2103 can be executed with reference to steps S404, S406 and S408.

[0196] S2104: When the second electronic device is an electronic device of a specified type, the first electronic device displays a first pop-up window 800 corresponding to the second electronic device.

[0197] In one possible implementation, the first pop-up window 800 includes: an icon of the second electronic device, and the first electronic device displays the first pop-up window 800 corresponding to the second electronic device, including: the first electronic device obtains the Model ID of the second electronic device; the first electronic device obtains the icon corresponding to the Model ID as the icon of the second electronic device; the first electronic device generates the first pop-up window 800 corresponding to the second electronic device based on the icon of the second electronic device, and displays it.

[0198] The icon of the second electronic device is shown as icon 801 in FIG. 8 .

[0199] Based on the above implementation, before generating the first pop-up window 800 corresponding to the second electronic device, the first electronic device can obtain the model ID of the second electronic device; obtain the icon corresponding to the model ID as the icon of the second electronic device; and generate the first pop-up window corresponding to the second electronic device based on the icon of the second electronic device. This allows the icon displayed in the first pop-up window 800 to correspond to the second electronic device, thereby providing a better user experience.

[0200] S2104 can be executed with reference to step S409.

[0201] Based on the technical solution provided in the embodiments of the present application, when a first electronic device is in communication with a second electronic device, the first electronic device obtains the device information of the second electronic device; the first electronic device determines whether the second electronic device is an electronic device of a specified type based on the device information of the second electronic device; if the second electronic device is an electronic device of the specified type, the first electronic device displays a first pop-up window corresponding to the second electronic device. The first electronic device can use the first pop-up window 800 to indicate the presence of the second electronic device, such as when a third-party headset is connected. This enables management of the second electronic device, thereby providing a better user experience for the user.

[0202] When a third-party headset is in communication with an electronic device, the first electronic device can display a first pop-up window 800 notifying the user of the access to the second electronic device. Furthermore, since the first pop-up window 800 includes a first control 804, the first electronic device can display a management interface in response to a user operating the first control. In response to the operation on the management interface, the first electronic device can perform management actions on the second electronic device. This facilitates user management of the second electronic device through the management interface, thereby providing a better user experience.

[0203] When the second electronic device is communicating with the first electronic device for the first time, after displaying the first pop-up window 800, the electronic device responds to the operation on the first control 804 and displays the first interface 900 of the second electronic device. The first interface 900 includes a second control 901 that triggers the addition of the MAC address of the second electronic device to the first list. After the user operates the second control 901, the MAC address of the second electronic device can be added to the first list. In this way, when the second electronic device is communicating with the first electronic device for the first time, the second electronic device is associated with the Honor Smart Space application, so that the second electronic device can be managed through the Honor Smart Space application.

[0204] After the user operates the second control 901 on the first interface 900, the electronic device adds the MAC address of the second electronic device to the first list and displays a second pop-up window 1000. The second pop-up window 1000 includes a third control 1001 for triggering the display of the second interface 1200. In response to the operation on the third control 1001, the first electronic device can display the second interface 1200, allowing the user to manage the second electronic device through the second interface 1200 and understand the usage of the second electronic device, for example, the battery level of the second electronic device, thereby providing the user with a better user experience.

[0205] When the second electronic device is not communicating with the first electronic device for the first time, the second interface 1200 is directly displayed in response to the operation on the first control 804. The user can directly access the second interface 1200 to manage the second electronic device, thereby simply and quickly managing the second electronic device.

[0206] In the second interface 1200, the battery information of the second electronic device is displayed, so that the user can know whether the battery of the second electronic device is sufficient to support the next use. The connection status of the second electronic device is displayed on the second interface 1200, so that the user can know whether the second electronic device is already connected to the first electronic device for communication. The current sound effects and optional sound effects of the second electronic device are displayed on the second interface 1200, which can meet the user's needs to change the sound effects of the headphones. The current sound quality and optional sound quality of the second electronic device are displayed on the second interface 1200, which can meet the user's needs to change the sound quality of the headphones. The setting entry for the recommended functions for the second electronic device is displayed on the second interface 1200, which can meet the user's needs to set functions for the second electronic device.

[0207] The second interface 1200 also includes the historically set functions of the current second electronic device, so that the user can access the functions previously set for the current second electronic device at any time when needed, and can also delete or modify these functions.

[0208] In one possible implementation, before the first electronic device establishes a connection with the second electronic device, the method also includes: the first electronic device determines that connection broadcast information of the second electronic device is received; the first electronic device obtains a fourth identifier of the second electronic device from the connection broadcast information; the first electronic device determines that it is not the first connection with the second electronic device based on the fourth identifier; the first electronic device displays a third pop-up window corresponding to the second electronic device, and the third pop-up window includes a fourth control; in response to an operation on the fourth control, the first electronic device connects to the second electronic device.

[0209] The fourth identifier may be a MAC address. The first electronic device may store the MAC address information of previously connected Bluetooth devices, for example, by storing the MAC address of previously connected Bluetooth devices in a list of connected devices. Therefore, after the first electronic device establishes a communication connection with the third-party headset, the first electronic device may check whether the MAC address of the third-party headset exists in the list of connected devices. If not, the first electronic device may determine that the third-party headset is connected for the first time. If so, the first electronic device may determine that the third-party headset is not connected for the first time.

[0210] After determining that it has received a connection broadcast message from a second electronic device that is not being connected for the first time, the first electronic device can prompt the user through a third pop-up window that there is a second electronic device that can be connected. Because the third pop-up window includes a fourth control for triggering the connection to the second electronic device, in response to an operation on the fourth control, the first electronic device can establish a communication connection with the second electronic device. The first electronic device asks the user for their opinion before establishing a communication connection with the second electronic device, which can make the operation of the first electronic device more meet the user's needs and provide the user with a better user experience.

[0211] It is understandable that, in order to realize the above functions, the above electronic device includes hardware structures and / or software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of the present application.

[0212] Figure 22 is a schematic diagram of the structure of a multi-device collaboration device provided in an embodiment of the present application. In one embodiment, the electronic device can implement the corresponding functions through the hardware device shown in Figure 22. As shown in Figure 22, the multi-device collaboration device may include: a display screen 1001, a memory 1002, a processor 1003, and a communication module 1004. The above-mentioned components can be connected via one or more communication buses 1005.

[0213] In one embodiment, the display screen 1001 may include a display panel 10011 and a touch sensor 10012, wherein the display panel 10011 is used to display images, and the touch sensor 10012 can transmit the detected touch operation to the application processor to determine the type of touch event and provide visual output related to the touch operation through the display panel 10011. The processor 1003 may include one or more processing units, for example: the processor 1003 may include an application processor, a modem processor, a graphics processor, an image signal processor, a controller, a video codec, a digital signal processor, a baseband processor, and / or a neural network processor. The different processing units may be independent devices or integrated into one or more processors. The memory 1002 is coupled to the processor 1003 and is used to store various software programs and / or multiple sets of instructions. The memory 1002 may include volatile memory and / or non-volatile memory.

[0214] When the software program and / or multiple groups of instructions in the memory 1002 are executed by the processor 1003, the method steps in the embodiments of the present application are performed.

[0215] An embodiment of the present application also provides an electronic device, which includes a display screen, a memory and one or more processors; the display screen, the memory and the processor are coupled; wherein the memory stores computer program code, and the computer program code includes computer instructions, and when the computer instructions are executed by the processor, the electronic device executes the device interaction method provided by the first aspect and any possible design method thereof.

[0216] An embodiment of the present application also provides a computer-readable storage medium, which includes computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the device interaction method provided in the above embodiment.

[0217] An embodiment of the present application further provides a computer program product, which includes executable instructions. When the computer program product is run on an electronic device, the electronic device executes the device interaction method provided in the aforementioned embodiment.

[0218] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0219] In the several embodiments provided in this application, it should be understood that the disclosed devices / equipment and methods can be implemented in other ways. For example, the device / equipment embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0220] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0221] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0222] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0223] The above content is only a specific embodiment of this application, but the scope of protection of this application is not limited to this. Any changes or replacements within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A device interaction method, characterized in that, The method is applied to a first electronic device, and the method includes: The first electronic device establishes a connection with a second electronic device. When the second electronic device connects to the first electronic device, it connects through a non-custom connection protocol; The first electronic device obtains device information of the second electronic device; The first electronic device determines whether the second electronic device is a specified type of electronic device according to the device information of the second electronic device; When the second electronic device is the specified type of electronic device, the first electronic device displays a first pop-up window corresponding to the second electronic device.

2. The method according to claim 1, wherein The first electronic device determines whether the second electronic device is a specified type of electronic device according to the device information of the second electronic device, including: The first electronic device determines that the second electronic device establishes a first communication connection with the first electronic device; The first electronic device obtains service information of the second electronic device; In response to that the service information of the second electronic device includes a first identifier corresponding to an audio headset device and the service information of the second electronic device includes power information of the second electronic device, the first electronic device determines that the second electronic device is a specified type of electronic device; In response to the first identifier, the first electronic device determines that the second electronic device is not a specified type of electronic device.

3. The method according to claim 2, wherein The first electronic device determines whether the second electronic device is a specified type of electronic device according to the device information of the second electronic device, and further includes: In response to the first identifier and the device name of the second electronic device being within a preset whitelist, the first electronic device determines that the second electronic device is a specified type of electronic device.

4. The method according to claim 1, wherein The first pop-up window includes: an icon of the second electronic device. The first electronic device displays the first pop-up window corresponding to the second electronic device, including: The first electronic device obtains a second identifier of the second electronic device; The first electronic device obtains an icon corresponding to the second identifier as the icon of the second electronic device; The first electronic device generates the first pop-up window according to the icon of the second electronic device and displays the first pop-up window.

5. The method according to claim 1, wherein The first pop-up window includes a first control, and the method further includes: Determine that the second electronic device establishes a first communication connection with the first electronic device; In response to an operation on the first control, the first electronic device displays a first interface of the second electronic device. The first interface includes a second control, and the first interface is used to add the second electronic device to the device management space of the first electronic device; In response to an operation on the second control, the first electronic device adds a third identifier of the second electronic device to a first list. The first list is a list of a first account, and the first account is an account logged in to the device management space.

6. The method according to claim 5, characterized in that, After the first electronic device adds the third identifier of the second electronic device to the first list in response to the user's operation on the second control, the method further includes: The first electronic device displays a second pop-up window; The second pop-up window includes a third control and a prompt message indicating that the second electronic device has been successfully added to the device management space; In response to an operation on the third control, the first electronic device displays the second interface, which includes device details information of the second electronic device.

7. The method according to claim 1, characterized in that The first pop-up window includes a first control, and the method further includes: Determining that the second electronic device and the first electronic device are not communicating for the first time; In response to an operation on the first control, the first electronic device displays a second interface, which includes device details information of the second electronic device.

8. The method according to claim 6 or 7, characterized in that, The device details information includes at least one of the following or a combination thereof: Battery information of the second electronic device, connection status of the second electronic device, current sound effects and selectable sound effects of the second electronic device, current audio quality and selectable audio quality of the second electronic device, a setting entry for a function recommended for the second electronic device, where the function includes performing a preset operation when a preset trigger condition is triggered.

9. The method according to claim 8, wherein In the case where the second electronic device is not communicating with the first electronic device for the first time, the device details information further includes: Functions of the current second electronic device set historically.

10. The method according to claim 1, wherein Before the first electronic device establishes a connection with the second electronic device, the method further includes: The first electronic device determines that it has received connection broadcast information from the second electronic device; The first electronic device obtains a fourth identifier of the second electronic device from the connection broadcast information; The first electronic device determines that it is not connecting to the second electronic device for the first time based on the fourth identifier; The first electronic device displays a third pop-up window corresponding to the second electronic device, and the third pop-up window includes a fourth control; In response to an operation on the fourth control, the first electronic device connects to the second electronic device.

11. An electronic device, characterized in that, Including: A display screen, a memory, and one or more processors; the display screen and the memory are coupled to the processor; wherein, computer program code is stored in the memory, and the computer program code includes computer instructions, and when the computer instructions are executed by the processor, the electronic device executes the device interaction method according to any one of claims 1-10.

12. A computer-readable storage medium, characterized in that, Including computer instructions, and when the computer instructions run on an electronic device, the electronic device executes the device interaction method according to any one of claims 1-10.

Images