A booting method and device

Abstract

The application relates to the terminal technical field and discloses a guiding method and equipment. The method can be applied to a multi-device cooperation scene, can select a cooperation protocol that can be used based on cooperation protocols supported by multiple devices respectively, then guides a user to adopt a multi-device cooperation mode corresponding to the selected cooperation protocol for multi-device cooperation, and thus can reduce the occurrence of multi-device cooperation failure. In the method, a second device can receive a discovery message sent by a first device, thereby obtaining a cooperation protocol supported by the first device; then, based on the cooperation protocol supported by the first device and a cooperation protocol supported by the second device, one or more cooperation protocols are selected; and the second device can guide a user based on the selected one or more cooperation protocols, thereby realizing guiding the user to adopt a cooperation mode corresponding to one protocol in the selected cooperation protocols for multi-device cooperation.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a booting method and device. Background Technology

[0002] In recent years, with the rapid development of the electronics industry and communication technology, devices are taking on increasingly diverse forms, such as mobile phones, tablets, and smart TVs, making people's lives more and more intelligent. Furthermore, with the increase in device types and the enrichment of device functions, multi-device collaborative applications are becoming increasingly widespread.

[0003] However, due to differences in the ecosystems and operating system capabilities of various devices, interoperability between devices can present numerous challenges. For instance, when users attempt to perform cross-ecosystem or cross-operating system operations, issues may arise such as the inability to achieve multi-device collaboration or collaboration failures. For example, when mobile phones and televisions use different screen mirroring protocols, users may experience screen mirroring failures or be unable to mirror their devices. Summary of the Invention

[0004] This application provides a guidance method and device. The method can guide users to use a collaboration protocol shared by multiple devices for multi-device collaboration, or guide users on how to use the collaboration method corresponding to the selected collaboration protocol for multi-device collaboration, thereby reducing the occurrence of multi-device collaboration failures and improving the user experience.

[0005] The first aspect provides a guidance method. In this method, a second device receives a first message sent by a first device. The first message instructs the first device to initiate multi-device collaboration using a first protocol. The first message includes collaboration protocols supported by the first device, and the collaboration protocols supported by the first device include the first protocol. The second device selects a second protocol based on the collaboration protocols supported by the first device and the second device. The second device displays a guidance interface, which guides the user to perform m operations. Through these m operations, the first device and the second device perform multi-device collaboration using the multi-device collaboration method corresponding to the second protocol, where m is an integer greater than 0. The first device can be understood as the initiator of multi-device collaboration, and the second device can be understood as the receiver of multi-device collaboration. The first message can be, for example, a discovery message sent by the first device. Multi-device collaboration refers to multiple devices collaboratively processing a business scenario, including but not limited to: screen projection scenarios, audio projection scenarios, file sharing scenarios, etc. Multi-device collaboration is generally implemented based on corresponding collaboration protocols, and different collaboration protocols can correspond to different multi-device collaboration methods. Taking multi-device collaboration as an example of screen casting, there are various screen casting protocols that can be used, including but not limited to: Miracast (a wireless display standard based on Wi-Fi Direct), Cast+ (a screen casting protocol), DMSDP (a screen casting protocol), and Google Cast (a proprietary screen casting protocol). (A screen mirroring protocol), etc.

[0006] In this method, the receiver can be configured to receive discovery messages sent by the initiator. This allows the receiver to receive these messages and, based on the discovery messages, understand the initiator's intent to initiate multi-device collaboration. Furthermore, the receiver can decide on the collaboration protocol for multi-device collaboration, selecting from at least one available protocol. It can also guide the user to adopt the chosen collaboration method to achieve multi-device collaboration. Therefore, this method does not require binding relationships or pre-negotiation between multiple devices, enabling cross-ecosystem or cross-operating system multi-device collaboration. This avoids collaboration failures or inability to collaborate, such as issues with screen mirroring failures.

[0007] In one possible implementation, the second device displays a guide interface, including but not limited to: displaying the guide interface using a sidebar, notification bar, or full-screen interface.

[0008] In this embodiment, the second device can employ various display methods to provide a guidance interface to the user. For example, it can display the guidance interface in a full-screen format for easy viewing, or it can use a sidebar or notification bar to minimize obstruction of the display. Therefore, this enhances the diversity of user guidance and ensures a better user experience.

[0009] In one possible implementation, the second device selects a second protocol based on the collaboration protocols supported by the first device and the collaboration protocols supported by the second device, including: the second device selecting the second protocol from one or more collaboration protocols supported by both the first device and the second device.

[0010] In this embodiment, the second device selects a collaboration protocol from those supported by both devices, which improves the efficiency of switching between multi-device collaboration modes and reduces user operations. For example, through negotiation between the two devices, the multi-device collaboration mode selected by the user can be switched to the multi-device collaboration mode corresponding to the collaboration protocol selected by the second device, thereby achieving multi-device collaboration.

[0011] In one possible implementation, the second protocol is a collaboration protocol supported by the second device and a collaboration protocol not supported by the first device; the guide interface is used to guide the user to perform m operations on the first device.

[0012] In this implementation, different guidance interfaces can be displayed based on the collaboration protocol selected by the second device and the support capabilities of the two devices for the collaboration protocol. Therefore, the accuracy of user guidance can be improved. For example, when the selected collaboration protocol is one that the first device does not support, the user can be guided to perform user operations on the first device, thus ensuring that the first device supports the collaboration protocol.

[0013] In one possible implementation, the guide interface includes one or more of the following: a QR code for establishing a communication connection between the first device and the second device, and user operation steps on the first device.

[0014] In this implementation, by providing a guidance interface to the user, the multi-device collaboration mode can be switched, thereby solving the problem that collaboration cannot be achieved when using the multi-device collaboration mode selected by the user.

[0015] In one possible implementation, the second protocol is a collaboration protocol supported by the first device and a collaboration protocol not supported by the second device; the guide interface is used to guide the user to perform m operations on the second device.

[0016] In this implementation, different guidance interfaces can be displayed based on the collaboration protocol selected by the second device and the support capabilities of the two devices for the collaboration protocol. Therefore, the accuracy of user guidance can be improved. For example, when the selected collaboration protocol is one that the second device does not support, the user can still be guided to perform user operations on the second device, thus ensuring that the second device supports the collaboration protocol.

[0017] In one possible implementation, the method further includes: the second device receiving a second message sent by the first device using a second protocol, the second message including multi-device collaborative data sent by the first device to the second device.

[0018] In this embodiment, the multi-device collaboration mode selected by the user can be switched to the multi-device collaboration mode selected by the second device, thereby enabling successful multi-device collaboration based on the switched multi-device collaboration mode and avoiding the problem that multi-device collaboration cannot be achieved due to the multi-device collaboration mode selected by the user.

[0019] In one possible implementation, the second device receiving the first message sent by the first device includes: the second device receiving the first message sent by the first device via Bluetooth connection or wireless-fidelity (Wi-Fi) connection.

[0020] In this embodiment, the second device can be equipped with the ability to receive discovery messages sent by other devices by using commonly used Bluetooth or Wi-Fi connections, thereby enabling the guidance methods described in the above embodiments and improving the success rate of multi-device collaboration.

[0021] In one possible implementation, before the second device selects a second protocol based on the collaboration protocol supported by the first device and the collaboration protocol supported by the second device, the method further includes: the second device determining that it does not support the first protocol; or the second device detecting that multi-device collaboration with the first device using the first protocol has failed.

[0022] In this embodiment, the second device detects the situation of multi-device collaboration with the first device using the first protocol. The user is only guided when it is detected that the second device cannot use the first protocol to conduct multi-device collaboration with the first device. This can avoid the impact when the second device can successfully collaborate with the first device using the first protocol.

[0023] The second aspect also provides a guidance method. This method can be applied to a second device. In this method, the second device receives a first message sent by the first device, the first message being used to instruct the first device to initiate Digital Living Network Alliance (DLNA) screen mirroring; the second device displays a guidance interface, the guidance interface being used to guide the user to turn on the hotspot on the first device; the second device connects to the hotspot of the first device, and performs DLNA screen mirroring between the first device and the second device based on the hotspot of the first device.

[0024] This method addresses the issue of multiple devices being unable to discover each other in DLNA screen mirroring scenarios due to router limitations on multicast packet forwarding. By configuring the receiver to receive discovery packets sent by the initiator, the receiver can understand the initiator's intent to initiate multi-device collaboration based on these packets. Furthermore, the receiver can guide the initiator to create a hotspot, switching from router forwarding to the initiator building a local area network via the hotspot, thus ensuring successful screen mirroring.

[0025] The third aspect provides a guidance method. This method can be applied to a first device. In this method, the first device detects and responds to a user operation that triggers multi-device collaboration, and sends a first message. The first message instructs the first device to initiate multi-device collaboration using a first protocol. The first message includes a collaboration protocol supported by the first device, and the collaboration protocol supported by the first device includes the first protocol. For example, the first device can send the first message using unicast, multicast, or broadcast methods.

[0026] The first device can receive a guidance message from the second device. This guidance message can be used by the first device to perform multi-device collaboration with the second device using a multi-device collaboration mode corresponding to the second protocol. For example, the guidance message can be used to instruct the first device to enable a hotspot, download an application for multi-device collaboration, or automatically trigger a switch to the multi-device collaboration mode corresponding to the second protocol; this application does not limit the scope of this instruction.

[0027] Alternatively, based on the guidance interface displayed on the second device, the first device may also detect user actions, such as scanning a QR code. The first message could be, for example, a discovery message.

[0028] In this method, the first device can act as the initiator of multi-device collaboration. In response to the user's operation of initiating multi-device collaboration, it can send a discovery message, thereby enabling the second device to receive the message sent by the first device, learn the operation intention of the initiator of multi-device collaboration, and thus realize the guidance method as described in the first aspect and its various embodiments.

[0029] A fourth aspect provides a guidance system. The system includes a second device as described in the first or second aspect and its embodiments, and a first device as described in the third aspect and its embodiments. The second device is configured to perform the methods described in the first or second aspect and its embodiments, and the first device is configured to perform the methods described in the third aspect and its embodiments.

[0030] A fifth aspect provides a second device comprising a plurality of functional modules; the plurality of functional modules interact to implement the methods performed by the second device in the first aspect and its embodiments, or to implement the methods performed by the second device in the second aspect and its embodiments. The plurality of functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the plurality of functional modules can be arbitrarily combined or divided based on specific implementations.

[0031] A sixth aspect provides a first device comprising a plurality of functional modules; the plurality of functional modules interact to implement the methods performed by the first device in the third aspect and its embodiments described above. The plurality of functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the plurality of functional modules can be arbitrarily combined or divided based on specific implementations.

[0032] The seventh aspect also provides a second device, including at least one processor and at least one memory, wherein the at least one memory stores a program, and when the second device is run, the at least one processor executes the method executed by the second device in the first aspect and its embodiments, or executes the method executed by the second device in the second aspect and its embodiments.

[0033] The eighth aspect also provides a first device, including at least one processor and at least one memory, wherein the at least one memory stores a program, and when the first device is run, the at least one processor executes the method executed by the first device in the third aspect and its various embodiments described above.

[0034] A ninth aspect provides a readable storage medium storing instructions that, when executed on a second device, cause the second device to perform the methods described in the first aspect and its possible embodiments, or to perform the methods described in the second aspect and its possible embodiments; or, when executed on a first device, cause the first device to perform the methods described in the third aspect and its possible embodiments.

[0035] A tenth aspect provides a program product that, when run on a second device, causes the second device to execute the method described in the first aspect and its possible embodiments, or to execute the method described in the second aspect and its possible embodiments; or, when run on a first device, causes the first device to execute the method described in the third aspect and its possible embodiments.

[0036] The eleventh aspect also provides a chip for reading a program stored in a memory, executing the method executed by the second device according to the first aspect and its various possible embodiments, or executing the method executed by the second device according to the second aspect and its various possible embodiments, or executing the method executed by the first device according to the third aspect and its various possible embodiments.

[0037] The twelfth aspect also provides a chip system including a processor for supporting a second device in implementing the methods of the first aspect and its possible embodiments described above, or for supporting a second device in implementing the methods of the second aspect and its possible embodiments described above, or for supporting a first device in implementing the methods of the third aspect and its possible embodiments described above. In one possible embodiment, the chip system further includes a memory for storing programs and data necessary for the device. The chip system may be composed of chips or may include chips and other discrete devices.

[0038] For details on the beneficial effects of any of the second to twelfth aspects and their possible implementations, please refer to the beneficial effects of the various possible implementations in the first aspect above; they will not be repeated here. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of the hardware structure of a possible device provided in an embodiment of this application;

[0040] Figure 2 A software system architecture block diagram of a device provided in an embodiment of this application;

[0041] Figure 3 This is a schematic diagram illustrating one application scenario of a guiding method provided in an embodiment of this application;

[0042] Figure 4 This is a second schematic diagram illustrating an application scenario of a guiding method provided in an embodiment of this application.

[0043] Figure 5 This is a third schematic diagram illustrating an application scenario of a guiding method provided in an embodiment of this application.

[0044] Figure 6 This is a fourth schematic diagram illustrating an application scenario of a guiding method provided in an embodiment of this application.

[0045] Figure 7 This is the fifth schematic diagram illustrating an application scenario of a guiding method provided in an embodiment of this application.

[0046] Figure 8 One of the flowcharts of a guiding method provided in an embodiment of this application;

[0047] Figure 9 A second schematic flowchart illustrating a guiding method provided in an embodiment of this application;

[0048] Figure 10 This is a third schematic flowchart of a guiding method provided in an embodiment of this application. Detailed Implementation

[0049] The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0050] Devices such as smartphones, tablets, smart screens, and smart home devices are becoming increasingly common. As the types and functions of these devices increase, the application scenarios for multi-device collaboration are becoming more widespread. Multi-device collaboration refers to multiple devices working together to process a single business scenario. Examples of multi-device collaboration include, but are not limited to, screen mirroring, audio projection, and file sharing. It's understood that multi-device collaboration applications utilize corresponding collaboration protocols; for example, screen mirroring uses a screen mirroring protocol, audio projection uses an audio projection protocol, and file sharing uses a file sharing protocol. However, due to differences in the ecosystems and operating system capabilities of different devices, interoperability between devices can present numerous challenges.

[0051] For ease of understanding, the following embodiments use a screen projection scenario as an example to illustrate the method provided in this application. Other multi-device collaborative application scenarios can be found in the embodiments of the screen projection scenario, which will not be repeated in the following embodiments.

[0052] Currently, the mainstream screen mirroring scenarios include screen mirroring and app mirroring. Screen mirroring, for example, projects the phone's display onto a large screen for mirrored display; app mirroring, for example, projects video data from video apps on the phone onto a large screen for video display. Based on different screen mirroring scenarios and different types of devices, there are various screen mirroring protocols, including but not limited to: Miracast (a wireless display standard based on Wi-Fi Direct), Cast+ (a screen mirroring protocol), DMSDP (a screen mirroring protocol), and Google Cast (a proprietary screen mirroring protocol). (A type of screen mirroring protocol), etc. Due to differences in device ecosystems, operating systems, and other factors, the screen mirroring protocols supported by devices from different manufacturers may vary or not be entirely the same. It is understandable that when the source device (e.g., the initiator in a screen mirroring scenario) selects a screen mirroring method whose corresponding protocol is not supported by the target device (e.g., the receiver capable of receiving screen mirroring data), it will lead to problems such as the user being unable to mirror or screen mirroring failing, resulting in a poor user experience.

[0053] In one possible implementation, in scenarios where both the phone and the large screen support the same system and distributed capabilities, after the phone and the large screen are bound together, the user can maintain a connection with the large screen via a distributed soft bus when playing content on the phone. Binding the phone and the large screen can also be understood as mutual authentication during the initial multi-device collaboration, and storing the binding relationship between the phone and the large screen so that subsequent multi-device collaborations do not require re-authentication. Since the large screen offers a better viewing experience, the phone can prompt the user whether to stream playback. When the user agrees, the phone sends a streaming command to the large screen via the distributed soft bus, enabling the large screen to play the content from the phone, and displaying the playback control interface on the phone. This implementation allows for proactive prompting to the user via the interface. However, this implementation cannot solve the problem of screen mirroring failing when the source and target devices use different mirroring protocols.

[0054] In view of this, embodiments of this application provide a guidance method. In this method, the target device can determine the source device's operational intent and the collaborative capabilities supported by the source device based on the discovery message from the source device. Then, the target device can select one or more collaborative methods based on the collaborative capabilities supported by the source device and the collaborative capabilities supported by the target device. Furthermore, the target device can provide the user with a one-page or multi-page guidance interface for achieving collaboration based on the selected one or more collaborative methods; alternatively, the target device can send the selected one or more collaborative methods to the source device, which then provides the user with a one-page or multi-page guidance interface for achieving collaboration based on the selected one or more collaborative methods. Therefore, this method eliminates the need for a binding relationship between the source and target devices, and also eliminates the need for prior negotiation between the source and target devices; the binding relationship between the source and target devices can be understood as the stored relationship after a mobile phone and a large screen are bound together. Through the target device's sensing capabilities and based on the collaborative capabilities of the source and target devices, collaborative capabilities supported by both the source and target devices are selected. Furthermore, based on the supported collaborative capabilities, the user is guided to use the corresponding collaborative method for device collaboration. Thus, this method can improve the success rate of multi-device collaboration, thereby optimizing the user experience.

[0055] It is understood that the source device in this application embodiment can be a device capable of initiating multi-device collaboration, such as a mobile phone, tablet computer, laptop computer, or even a large screen; and the target device in this application embodiment can be a device capable of receiving multi-device collaboration, such as a large screen, projector, smart speaker, or even a mobile phone, tablet computer, or laptop computer. Furthermore, this application embodiment does not impose any limitations on the specific type of the source or target device. Devices that can be applied to this application embodiment include, but are not limited to, those equipped with… Or devices with other operating systems.

[0056] Figure 1 A schematic diagram of a possible device hardware structure is shown. The device 100 includes components such as: a radio frequency (RF) circuit 210, a power supply 220, a processor 230, a memory 240, an input unit 250, a display unit 260, an audio circuit 270, a communication interface 280, and a wireless-fidelity (Wi-Fi) module 290. Those skilled in the art will understand that... Figure 1 The hardware structure of the device 100 shown in the figure does not constitute a limitation on the device 100. The device 100 provided in the embodiments of this application may include more or fewer components than shown, may combine two or more components, or may have different component configurations. Figure 1The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0057] The following is combined Figure 1 The various components of the device 100 are described in detail below:

[0058] The RF circuit 210 can be used for receiving and transmitting data during communication or a call. Specifically, after receiving downlink data from the base station, the RF circuit 210 sends it to the processor 230 for processing; additionally, it sends uplink data to be transmitted to the base station. Typically, the RF circuit 210 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier (LNA), a duplexer, etc.

[0059] Furthermore, the RF circuit 210 can also communicate with other devices via a wireless communication network. The wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), 5G, email, and Short Messaging Service (SMS).

[0060] Wi-Fi technology is a short-range wireless transmission technology. The device 100 can connect to an access point (AP) via the Wi-Fi module 290, thereby enabling access to the data network. The Wi-Fi module 290 can be used for receiving and sending data during communication.

[0061] The device 100 can physically connect to other devices through the communication interface 280. Optionally, the communication interface 280 can be connected to the communication interfaces of other devices via a cable to enable data transmission between the device 100 and other devices.

[0062] The device 100 can also perform communication services and interact with server-side devices or other devices. Therefore, the device 100 needs to have data transmission capabilities, meaning that the device 100 needs to include a communication module. Although Figure 1 The RF circuit 210, the Wi-Fi module 290, and the communication interface 280 are shown, but it is understood that the device 100 contains at least one of the above-mentioned components or other communication modules (such as a Bluetooth module) for data transmission.

[0063] For example, when the device 100 is a mobile phone, the communication module included in the device 100 may include the RF circuit 210, and may also include the Wi-Fi module 290, or may include a Bluetooth module. Figure 1 (Not shown in the image); when the device 100 is a tablet computer, the communication module included in the device 100 may include the Wi-Fi module, or may include a Bluetooth module (not shown in the image); Figure 1 (Not shown in the image). In this embodiment, when device 100 is a mobile phone, it can communicate with the large screen through a communication module such as RF circuit 210 or Wi-Fi module 290. For example, when the mobile phone detects a user's screen projection operation, it can send a discovery message through RF circuit 210 or Wi-Fi module 290 in response to the screen projection operation; the large screen can receive the discovery message sent by the mobile phone through RF circuit 210 or Wi-Fi module 290. As another example, when the mobile phone and the large screen can perform multi-device collaboration through the guidance method provided in this embodiment, the mobile phone can send collaboration data to the large screen through RF circuit 210 or Wi-Fi module 290, and similarly, the large screen can receive the collaboration data sent by the mobile phone through RF circuit 210 or Wi-Fi module 290.

[0064] The memory 240 can be used to store software programs and software modules. The processor 230 executes various functional applications and data processing of the device 100 by running the software programs and software modules stored in the memory 240. Optionally, the memory 240 may mainly include a program storage area and a data storage area. The program storage area may store the operating system (mainly including software programs or software modules corresponding to the kernel layer, system layer, application framework layer, and application layer). Furthermore, the memory 240 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. In this embodiment, when the device 100 is a large screen, the memory 240 may store screen projection protocols supported by the large screen. For example, the screen projection protocols stored in the memory 240 of the large screen may include Miracast, Cast+, and DMSDP.

[0065] The input unit 250 can be used to receive editing operations on various types of data objects, such as numbers or characters, input by the user, and to generate key signal inputs related to user settings and function control of the device 100. Optionally, the input unit 250 may include a touch panel 251 and other input devices 252.

[0066] The touch panel 251, also known as a touchscreen, can collect user touch operations on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 251), and drive corresponding connection devices according to a pre-set program. In this embodiment, the touch panel 251 can collect user operations on or near it. For example, when the device 100 is a mobile phone, the mobile phone can collect operations used to indicate and trigger screen projection through the touch panel 251. As another example, when the device 100 is a large screen, the touch panel 251 can collect user operations used to instruct the user to perform based on the large screen's guidance interface, such as the user confirming the use of the screen projection method provided on the large screen's guidance interface.

[0067] Optionally, the other input device 252 may include, but is not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), mouse, joystick, etc.

[0068] The display unit 260 can be used to display information input by the user or information provided to the user, as well as various menus of the device 100. The display unit 260 is the guidance system of the device 100, used to present the interface and realize human-computer interaction. The display unit 260 may include a display panel 261, for example, the display unit 260 may be a monitor. In this embodiment, the display unit 260 can be used to display the display content involved in the method provided in this application. For example, when the device 100 is a large screen, the display unit 260 can be used to display a guidance interface, and in scenarios where multiple devices can collaborate between the large screen and the mobile phone, it can also be used to display screen projection data from the mobile phone. As another example, when the device 100 is a mobile phone, the display unit 260 can be used to display video data being played on the mobile phone, and can also display controls for the user to project the video data.

[0069] The processor 230 is the control center of the device 100. It connects various components via various interfaces and lines, and executes software programs and / or software modules stored in the memory 240, as well as calling data stored in the memory 240, to perform various functions of the device 100 and process data, thereby realizing multiple services based on the device 100. In this embodiment, the processor 230 can be used to implement the methods provided in this embodiment.

[0070] The device 100 also includes a power supply 220 (such as a battery) for supplying power to various components. Optionally, the power supply 220 can be logically connected to the processor 230 through a power management system, thereby enabling the power management system to manage functions such as charging, discharging, and power consumption.

[0071] like Figure 1 As shown, device 100 also includes audio circuitry 270, microphone 271, and speaker 272, providing an audio interface between the user and device 100. Audio circuitry 270 converts audio data into signals recognizable by speaker 272 and transmits these signals to speaker 272, where they are converted into sound signals for output. Microphone 271 collects external sound signals (such as human speech or other sounds) and converts these signals into signals recognizable by audio circuitry 270, sending them to audio circuitry 270. Audio circuitry 270 can also convert the signals transmitted by microphone 271 into audio data and output the audio data to RF circuitry 210 for transmission to, for example, another device, or output the audio data to memory 240 for further processing.

[0072] Although not shown, the device 100 may also include a camera, at least one sensor, etc., which will not be described in detail here. The at least one sensor may include, but is not limited to, an accelerometer, a proximity sensor, a fingerprint sensor, a touch sensor, a temperature sensor, etc.

[0073] Alternatively, the device 100 may also include a graphics processing unit (GPU). The GPU can be used to render images.

[0074] The operating system (OS) involved in this application embodiment is the most basic system software running on device 100. The software system of device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment takes an operating system adopting a layered architecture as an example to illustrate the software structure of device 100.

[0075] Figure 2This is a software structure block diagram of a device provided in an embodiment of this application. For example... Figure 2 As shown, the device's software architecture can be a layered architecture, for example, the software can be divided into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the operating system is divided into five layers, from top to bottom: the application layer, the application framework layer (framework, FWK), the runtime and system libraries, the kernel layer, and the hardware layer.

[0076] The application layer can include a series of application packages. For example... Figure 2 As shown, the application layer can include camera, settings, user interface (UI), wireless local area network (WLAN), music, Bluetooth, video, etc.

[0077] In one possible implementation, the application can be developed using Java, by calling the application programming interface (API) provided by the application framework layer. Developers can then interact with the underlying operating system layers (such as the hardware layer and kernel layer) to develop their own applications. This application framework layer primarily consists of a series of services and management systems within the operating system.

[0078] The application framework layer provides application programming interfaces and a programming framework for applications within the application layer. The application framework layer includes some predefined functions. For example... Figure 2 As shown, the application framework layer may include an activity manager, window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0079] The Activity Manager manages the lifecycle of each application and provides commonly used navigation and back functions, offering an interactive interface for all program windows.

[0080] The window manager is used to manage windowed applications. It can obtain the screen size, determine if a status bar is present, lock the screen, and capture screenshots, among other things. The content provider stores and retrieves data, making this data accessible to applications. This data can include video, images, audio, etc.

[0081] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, it may include views for displaying text and views for displaying images.

[0082] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, etc.

[0083] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of download completion or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen.

[0084] The runtime includes the core libraries and the virtual machine. The runtime is responsible for the scheduling and management of the operating system.

[0085] The core library consists of two parts: one part contains the functionalities that the Java language needs to call, and the other part contains the core libraries of the operating system. The application layer and application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0086] A system library can include multiple functional modules. For example: a surface manager, a media framework, a 3D graphics processing library (e.g., OpenGL ES), a 2D graphics engine (e.g., SGL), etc.

[0087] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0088] The media framework supports playback and recording of various commonly used audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, and MP3.

[0089] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0090] A 2D graphics engine is a drawing engine for 2D drawing.

[0091] In some embodiments, a 3D graphics processing library can be used to draw 3D motion images, and a 2D graphics engine can be used to draw 2D motion images.

[0092] The kernel layer is the layer between hardware and software. The kernel layer contains at least display drivers, audio drivers, and sensor drivers.

[0093] The hardware layer may include display units, audio circuits, etc.

[0094] Typically, a device 100 can run multiple applications simultaneously. In a simpler scenario, one application corresponds to one process; in a more complex scenario, one application can correspond to multiple processes. Each process has a unique process ID.

[0095] It should be understood that in the embodiments of this application, "at least one of the following" or similar expressions refer to any combination of these items, including any combination of a single item or a plurality of items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be single or multiple. "Multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0096] In addition, it should be understood that in the description of this application, the words "first" and "second" are used only for the purpose of distinguishing descriptions and should not be construed as indicating or implying relative importance or order.

[0097] It should be understood that the hardware structure of the device can be as follows: Figure 1 As shown, the software system architecture can be as follows: Figure 2 As shown, the software programs and / or modules corresponding to the software system architecture in the device can be stored in the memory 240, and the processor 230 can run the software programs and applications stored in the memory 240 to execute the flow of a booting method provided in the embodiments of this application.

[0098] To facilitate understanding of the guidance method provided in this application, the following is combined with... Figures 3 to 9 The content shown describes the implementation process of the method provided in this application.

[0099] The method provided in this application can be applied to multi-device interconnection scenarios, enabling multi-device collaboration and thus providing a better user experience. For ease of understanding, the following embodiments use a screen mirroring scenario as an example of multi-device collaboration. Figure 3This diagram illustrates an application scenario for screen mirroring. This scenario includes at least a mobile phone 310 and a large screen 320. In the scenario where the display interface of the mobile phone 310 is mirrored onto the large screen 320, the user can trigger the mirroring by clicking the icon 300 for wireless screen mirroring in the pull-down notification interface of the mobile phone 310. The mobile phone 310, responding to the user's touch operation on the icon 300, can trigger the mirroring operation based on the mirroring protocol corresponding to the icon 300 (assuming mirroring protocol 1). In one possible application scenario, if the large screen 320 also supports mirroring protocol 1, then the mobile phone 310 can scan for the large screen 320, thus enabling the mirroring of the mobile phone 310's display interface onto the large screen 320. For example… Figure 3 The large screen of the 320 can display the interface of the 310 mobile phone.

[0100] In another possible application scenario, when Figure 3 When the large screen 320 does not support screen mirroring protocol 1, the mobile phone 310 may not be able to scan the large screen 320, or even if it does scan the large screen 320, screen mirroring may fail. The method provided in this application embodiment can guide the user to successfully mirror the screen in this scenario through one or more pages of guided interfaces. The guided method provided in this application embodiment may also include one or more possible application scenarios, including but not limited to the following scenarios A to D:

[0101] Scene A. Figure 4 This is a schematic diagram illustrating an application scenario of a guidance method provided in this application embodiment. In this application scenario, the large screen 320 can display interface 410; wherein, interface 410 may include a prompt box, which is used to indicate to the user other screen casting protocols that can be used to achieve screen casting. As shown in interface 410, the prompt box may include, but is not limited to: prompt information such as "Do you need to cast the screen and learn how to operate it?", "Confirm" control, "Reject" control, etc. Here, other screen casting protocols can be understood as screen casting protocols that are supported by both the mobile phone 310 and the large screen 320, such as screen casting protocol 2; or, other screen casting protocols can also be understood as screen casting protocols that are easy for users to operate, for example, although the mobile phone 310 does not support screen casting protocol 3, screen casting protocol 3 can be achieved by downloading the corresponding application (APP).

[0102] In one possible embodiment, when the large screen 320 detects a user's touch operation on the "Confirm" control on the interface 410, in response to the touch operation, the interface 420 can be displayed. The interface 420 may include an operation guide box, which can be used to instruct the user on how to use other screen mirroring protocols and corresponding screen mirroring methods. As shown in the interface 420, the operation guide box may include, but is not limited to: a QR code for enabling QR code screen mirroring, a screen mirroring tutorial including operation instructions, etc.; wherein, the operation tutorial can be used to instruct how to achieve screen mirroring through user operation. It is understood that when the large screen 320 detects a user's touch operation on the "Reject" control on the interface 410, in response to the touch operation, the large screen's homepage interface or the currently playing interface, etc., can be displayed.

[0103] based on Figure 4 The QR code provided on interface 420 guides users to scan it using their mobile phone 310. Understandably, mobile phone 310 responds to the scanning operation and recognizes the content corresponding to the QR code. For example, after recognizing the content of the QR code, mobile phone 310 can directly project its display onto the large screen 320. Alternatively, after recognizing the content of the QR code, mobile phone 310 can also display an interface for projection, guiding users to project their mobile phone 310's display onto the large screen 320.

[0104] In addition, the large screen 320 can also collect and analyze user actions on interface 410, analyze user preferences based on the statistical results, and then guide users according to these preferences. For example, if the large screen 320 analyzes that the user's preference is to confirm the need for screen casting and understand how to operate it, then the next time a screen casting scenario is detected and guidance is needed, interface 420 can be displayed directly, thereby simplifying the user's operation. Alternatively, if the large screen 320 analyzes that the user's preference is to refuse screen casting and understand how to operate it, then even if a screen casting scenario is detected and guidance is needed, interfaces 410 and 420 will not be displayed to the user again, thus avoiding a poor user experience.

[0105] It should be noted that interface 410 is only one possible example. The style of the prompt box is not limited in this embodiment; for example, it can also be implemented through notification messages, voice playback, or a combination of multiple methods. In another possible embodiment, Figure 5 This is a schematic diagram illustrating another application scenario of a guiding method provided in an embodiment of this application. Compared to Figure 4 Interface 410 in the middle, Figure 5The prompt box in interface 510 may include, but is not limited to: a prompt message such as "Do you need to cast?", a "Confirm" control, a "Decline" control, and a "Confirm and learn how to cast" control. When the phone detects a user's touch operation on the "Confirm" control, in response to the touch operation, interface 520 can be displayed; wherein, compared to Figure 4 Interfaces 420 and 520 may include operation guide boxes that do not include screen mirroring tutorials. Understandably, when the phone detects a user's touch on the "Confirm and learn how to mirror" control, it may display, in response to that touch, a screen mirroring tutorial. Figure 4 The interface 420 shown here includes an operation guide box that can include not only QR code scanning and screen mirroring, but also screen mirroring tutorials and other display content.

[0106] It should also be noted that interface 420 is only one possible example, and the style and display content of the operation guide box are not limited in this embodiment. For example, when other screen casting protocols are user-friendly, the operation guide box displayed on interface 420 includes an APP icon for downloading screen casting protocol 3; or, when the guidance is implemented on mobile phone 310, the operation guide box may also include a control to guide users to the app store. Furthermore, the operation tutorial in the screen casting tutorial included in interface 420 may be in a collapsed or swiped state, etc.

[0107] Scene B Figure 6 This is a schematic diagram illustrating another application scenario of the guidance method provided in this application embodiment. In this application scenario, the large screen 320 can display an interface 610; wherein, the interface 610 may include an operation guidance box, which can be used to indicate, for example... Figure 4 The operation guide box shown in interface 420 can be used to instruct the user on how to use other screen mirroring methods. Combined with... Figure 4 and Figure 6 As can be seen, the operation guide box in interface 610 can be displayed on one side of the large screen 320; and, compared to Figure 4 The scene shown, Figure 6 The scenario shown allows the operation guide box to be directly overlaid and displayed on one side of the 320-inch large screen. Through this scenario, compared to... Figure 4 The implementation method of requiring users to click the "Confirm" or "Reject" control in interface 410 can reduce user operations, and by displaying it on one side of the large screen 320, it can reduce the obstruction of the playing interface on the large screen 320.

[0108] In one possible embodiment, when the large screen 320 detects that the user has slid the operation guide box outward on the interface 610, the operation guide box in the interface 610 may no longer be displayed in response to the sliding operation.

[0109] Alternatively, in another possible embodiment, the operation guide box in interface 610 can have a preset display duration; the display duration can be, for example, 5 seconds or 10 seconds. For example, timing begins from the display of the operation guide box, and when the set display duration is reached, the operation guide box can be stopped from being displayed. Therefore, this embodiment can reduce user operations and avoid prolonged obstruction of the display screen 320. Furthermore, the display duration can also be manually set by the user on a display interface such as a settings interface.

[0110] Scene C Figure 7 This is a schematic diagram illustrating another application scenario of a guidance method provided in an embodiment of this application. In this application scenario, the large screen 320 can display an interface 710; wherein, the interface 710 may include... Figure 4 The prompt boxes within the interface can have different styles, and they can also be used to indicate other screen mirroring protocols that the user can use to achieve screen mirroring. As shown in interface 710, the prompt boxes may include, but are not limited to, prompts such as "Do you need to mirror your screen and learn how to do it?". Figure 4 and Figure 6 As can be seen, the prompt box in interface 710 can be displayed at the top of the large screen 320; and, compared to Figure 4 The scene shown, Figure 7 The scene shown can be directly overlaid and displayed on the top of the 320-inch large screen.

[0111] In one possible embodiment, when the large screen 320 detects a user's first touch operation on the prompt box on the interface 710, the interface 720 can be displayed in response to the first touch operation. For example, the first touch operation can be a click operation, a long press operation, etc. The interface 720 may include an operation guide box, which can be used to instruct the user on how to use other screen casting protocols to achieve screen casting. As shown in the interface 720, the operation guide box may include, but is not limited to, a QR code for implementing QR code screen casting, a screen casting tutorial, etc. In another possible embodiment, when the large screen 320 detects a user's second touch operation on the prompt box on the interface 710, the prompt box in the interface 710 may no longer be displayed in response to the second touch operation. The second touch operation can be, for example, a swipe operation to the outside of the screen.

[0112] Alternatively, in another possible embodiment, the display duration of the prompt box in interface 710 can be preset. For example, timing begins from the display of the prompt box, and when the preset display duration is reached, the prompt box may no longer be displayed. Therefore, this embodiment can reduce user operations and also avoid prolonged obstruction of the display screen 320.

[0113] Scenario D, such as Figures 4 to 7The illustrated embodiment, in addition to providing guidance on the large screen 320, can also provide guidance on the mobile phone 310, thereby improving the convenience of user operation. Specific implementation scenarios can be found in the descriptions of scenarios A to C above, and will not be repeated here.

[0114] Based on the foregoing description of the interface processing effects achievable using the methods provided in this application, the following describes the implementation process of the guidance method provided in this application, to illustrate how the methods provided in this application can achieve the aforementioned results. Figures 4 to 7 The interface processing effect shown.

[0115] In one possible embodiment, Figure 8 This is a flowchart illustrating a guiding method provided in an embodiment of this application. The method can be applied to a second device, and the process may include the following steps:

[0116] Step 801: The first device detects a first user operation, which is used for screen projection. The first device can be, for example, the source device described in the preceding embodiments, such as the mobile phone 310 described in scenarios A to D. For example,... Figure 3 As shown, the first user operation can be, for example, a user's touch operation on icon 300.

[0117] Step 802: In response to the first user's operation, the first device sends a discovery message. The discovery message can be used by the first device to discover other nearby devices and can indicate the first device's screen mirroring intention, such as initiating screen mirroring using screen mirroring protocol 1. The discovery message may also include at least one screen mirroring protocol supported by the first device. In one possible embodiment, the first device can send the discovery message via Bluetooth, Wi-Fi, or other connections. This embodiment does not limit the connection method used by the first device to send the discovery message.

[0118] Step 803: The second device determines at least one screen projection protocol supported by the first device based on the discovery message. The second device may be, for example, the target device described in the preceding embodiments, such as the large screen 320 described in scenarios A to D.

[0119] In one possible embodiment, the second device can receive discovery messages from nearby devices in real time. Thus, after the first device sends a discovery message, the second device can receive the discovery message sent by the first device. It should be noted that this embodiment does not limit the number of discovery messages the second device can receive; for example, it can receive discovery messages from source device 1 as well as discovery messages from source device 2.

[0120] In one optional embodiment, the second device can determine, based on step 803, that at least one screen mirroring protocol supported by the first device, and the second device can store at least one screen mirroring protocol it supports. Therefore, when it is determined that the second device does not support screen mirroring protocol 1 supported by the first device in the screen mirroring intent, it can continue to execute step 804 to select other screen mirroring protocols and guide the user to use the screen mirroring method corresponding to other screen mirroring protocols to achieve successful screen mirroring. In another optional embodiment, the second device can also continue to execute step 804 when it detects that screen mirroring with the first device using screen mirroring protocol 1 has failed; wherein, the screen mirroring failure detected by the second device can be indicated to the second device by the first device or detected by the second device itself. In yet another optional embodiment, the second device can also continue to execute step 804 when it detects that screen mirroring with the first device using screen mirroring protocol 1 has been successful, thereby determining whether there is a better screen mirroring protocol to improve the user experience. Alternatively, it can be understood that the second device can also stop executing step 804 when it detects that screen mirroring with the first device using screen mirroring protocol 1 has been successful, thereby avoiding impacting the successful screen mirroring scenario.

[0121] Step 804: The second device selects a projection protocol based on at least one projection protocol supported by the first device and at least one projection protocol supported by the second device.

[0122] In one optional embodiment, the first device supports screen mirroring protocol 1 and screen mirroring protocol 2, and the second device supports screen mirroring protocol 2 and screen mirroring protocol 3. When the first device detects screen mirroring using screen mirroring protocol 1 in step 801, the discovery message sent by the first device in step 802 can indicate that the first device's operational intent is to use the screen mirroring method corresponding to screen mirroring protocol 1. After receiving the discovery message sent by the first device, the second device determines that the first device's operational intent is to use screen mirroring protocol 1, and determines that the first device supports not only screen mirroring protocol 1 but also screen mirroring protocol 2. At this time, the second device can select screen mirroring protocol 2, which is supported by both the first and second devices, for screen mirroring. Then, the second device can guide the user to use screen mirroring protocol 2 for screen mirroring. For example, the screen mirroring method corresponding to screen mirroring protocol 1 can be mirroring. Since the mobile phone and the large screen use different operating systems, the mobile phone cannot use mirroring to cast its screen to the large screen. The screen mirroring method corresponding to screen mirroring protocol 2 can be application casting. Based on the fact that the mobile phone and the large screen are connected to the same Wi-Fi, the large screen can guide the user to use application casting to cast its screen to the large screen.

[0123] In another optional embodiment, the first device supports screen mirroring protocol 1 and screen mirroring protocol 2, and the second device supports screen mirroring protocol 3 and screen mirroring protocol 4. When the first device detects screen mirroring using screen mirroring protocol 1 in step 801, the discovery message sent by the first device in step 802 can indicate that the first device's operation intention is to use the screen mirroring method corresponding to screen mirroring protocol 1. After receiving the discovery message sent by the first device, the second device determines that the first device's operation intention is to use screen mirroring protocol 1, and determines that the first device supports not only screen mirroring protocol 1 but also screen mirroring protocol 2, while the second device supports screen mirroring protocols 3 and 4. Based on the fact that the first device and the second device do not have the same screen mirroring protocol, the second device can select one screen mirroring protocol from screen mirroring protocol 3 and screen mirroring protocol 4 to guide the user to use the selected screen mirroring protocol. For example, the screen mirroring method corresponding to screen mirroring protocol 1 is mirroring. Since the mobile phone and the large screen use different operating systems, the mobile phone cannot use mirroring to mirror its screen onto the large screen. The screen mirroring method corresponding to screen mirroring protocol 2 is application mirroring. Since the mobile phone and the large screen are not connected to the same Wi-Fi network, the mobile phone cannot use application mirroring to mirror its screen onto the large screen. The screen mirroring method corresponding to screen mirroring protocol 3 is using a screen mirroring app. When the large screen selects screen mirroring protocol 3, the large screen can guide the user to download a screen mirroring app on their mobile phone, thereby enabling screen mirroring to the large screen based on the screen mirroring app.

[0124] In the above embodiments, the large screen can select a screen projection protocol based on one or more factors such as the complexity of user operation and the user experience of the screen projection protocol.

[0125] Step 805: The second device guides the screen mirroring process according to the selected mirroring protocol. For example, the screen mirroring guidance can be as follows: Figure 4 Interfaces 410 and 420 are shown. For example, screen mirroring guidance can be as follows: Figure 5 Interfaces 510 and 520 are shown. Alternatively, for example, screen mirroring guidance can also be as follows: Figure 6 The interface shown is 610. Alternatively, for example, screen mirroring guidance can also be as follows: Figure 7 Interfaces 710 and 720 are shown. It can be understood that during the screen projection guidance process, the second device can also detect user operations, such as detecting the user's touch operation on the "Confirm" control on interface 410, or the user's touch operation on the prompt box on interface 710, etc.

[0126] In one possible embodiment, the second device can collect touch operations during the screen mirroring guidance process, statistically analyze these operations to determine user preferences, and then set the next screen mirroring guidance method based on these preferences. For example, if the second device analyzes that the user prefers to accept the screen mirroring protocol selected by the second device, then the next time a screen mirroring scenario is detected that the user needs guidance, it can assume that the user accepts the screen mirroring protocol selected by the second device and directly display the operation guidance box to the user without requiring user feedback. For example, it can directly display something like... Figure 4 The interface shown in 420 will no longer display the following: Figure 4 The interface 410 shown simplifies user operation. For example, if the second device analyzes that the user prefers not to accept the screen mirroring protocol selected by the second device, it can default to the user rejecting the screen mirroring protocol selected by the second device and no longer provide the user with a guide interface, thereby avoiding a bad user experience.

[0127] It should be noted that the implementation method of screen projection guidance is not limited in the embodiments of this application. For example, it can be implemented by at least one of the following methods: guidance interface, prompt box interface, notification interface, voice, etc.

[0128] Step 806: The first device detects a second user operation, which is an operation performed by the user according to the guidance of the second device. For example, when the guidance of the second device is... Figure 4 When the interface is 420 as shown, the second user operation that the first device can detect can be a QR code scanning operation. In another example, when the second device guides the user to download a screen mirroring app, the second user operation that the first device can detect can be a download operation for the screen mirroring app.

[0129] Step 807: The first device interacts with the second device using a message exchanged between them. This message is used to cast the screen from the first device to the second device. For example, the message can be used to establish a casting connection between the first and second devices; for instance, the message can be used for the second device to access the same Wi-Fi network as the first device. Alternatively, when the first device establishes a casting connection with the second device through step 806, the message can be the data to be cast.

[0130] In another possible embodiment, Figure 9 This is a flowchart illustrating a guidance method provided in an embodiment of this application. This method can be applied to scenarios where the first device uses the Digital Living Network Shield (DLNA) for screen projection. The process may include the following steps:

[0131] Step 901: The first device detects a first user operation, which is used for screen projection. The first device can be, for example, the source device described in the preceding embodiments, such as the mobile phone 310 described in scenarios A to D. For example, ... Figure 3 As shown, the first user operation can be, for example, a user's touch operation on icon 300.

[0132] Step 902a: The router receives a multicast discovery message from the first device. The DLNA projection discovery process is based on the LAN coap protocol, and coap messages are multicast messages.

[0133] Step 903a: The router does not forward the discovery packet and discards it directly. This is because some routers may have policies that restrict the forwarding of multicast packets, which could prevent the first device from discovering the second device, thus preventing the first device from projecting its screen to the second device.

[0134] Step 902b: The second device receives the discovery message multicast by the first device. In this embodiment, the second device can be configured to receive Layer 2 messages. Therefore, the second device can receive the discovery message multicast by the first device without relying on router forwarding.

[0135] Step 903b: The second device determines the operational intent of the first device based on the discovery message. It can be understood that, based on the content of step 901, the operational intent of the first device can be determined to be screen projection.

[0136] Step 904: The second device provides screen mirroring guidance, which instructs the first device to turn on its hotspot. It is understood that in this scenario, the screen mirroring tutorial displayed on the second device's guidance interface may contain a "Please start hotspot" message.

[0137] Step 905: The first device detects a third user operation, which is used to enable a hotspot. It is understood that the user can enable the hotspot on the first device through screen mirroring guidance from the second device.

[0138] Step 906: The second device connects to the hotspot of the first device. It is understood that after the second device executes the screen mirroring guide in step 904, it can initiate a wireless local area scanning process based on the screen mirroring guide, thereby facilitating connection to the hotspot of the first device.

[0139] Step 907: The first device begins casting its screen to the second device. It is understood that after the second device connects to the first device's hotspot, both devices are on the same local area network. The first and second devices can establish a communication connection, allowing the first device to send its casting data to the second device, thus enabling screen casting from the first device to the second device.

[0140] The method provided in this application embodiment enables the target device to receive discovery messages from other devices by configuring the target device. This allows the target device to receive messages sent by the source device, thereby enabling it to understand the multi-device collaboration intent initiated by the source device based on the discovery messages. Furthermore, the target device can decide on the collaboration mode for multi-device collaboration, selecting from at least one optional mode, and can provide collaboration guidance based on the selected mode to guide the user to adopt the chosen mode for multi-device collaboration. Therefore, this method does not require binding relationships or pre-negotiation between multiple devices, enabling cross-ecosystem or cross-operating system multi-device collaboration. This avoids collaboration failures or inability to collaborate, such as preventing screen mirroring failures.

[0141] In one alternative implementation, Figure 10 An interactive flow for a guidance method provided in this application embodiment. This interactive flow may include the following steps:

[0142] Step 1001: The second device receives a first message sent by the first device. The first message is used to instruct the first device to initiate multi-device collaboration using a first protocol. The first message includes a collaboration protocol supported by the first device, and the collaboration protocol supported by the first device includes the first protocol.

[0143] In this context, the first device can be understood as the initiator of multi-device collaboration, such as the mobile phone described in the previous embodiments; the second device can be understood as the receiver of multi-device collaboration, such as the large screen described in the previous embodiments; and the first message can be, for example, a discovery message sent by the first device.

[0144] Step 1002: The second device selects a second protocol based on the collaboration protocols supported by the first device and the collaboration protocols supported by the second device.

[0145] Step 1003: The second device displays a guidance interface, which guides the user to perform m operations. These m operations enable multi-device collaboration between the first device and the second device using the multi-device collaboration method corresponding to the second protocol, where m is an integer greater than 0. For example, the guidance interface can be as follows: Figure 4Interfaces 410 and 420 are shown. For example, a guide interface can be like... Figure 5 The interfaces 510 and 520 are shown. Alternatively, for example, the guide interface may also be as follows: Figure 6 The interface shown is 610. Alternatively, for example, the guide interface could also be like... Figure 7 The interfaces shown are 710 and 720.

[0146] Based on the above embodiments, this application also provides a second device, which includes multiple functional modules. These multiple functional modules interact to implement the functions performed by the second device in the methods described in the embodiments of this application. The multiple functional modules can be implemented based on software, hardware, or a combination of both, and can be arbitrarily combined or divided based on specific implementations. For example, [the following is an example of implementation details]. Figure 8 In the illustrated embodiment, the second device performs steps 802 to 805 and step 807. Alternatively, it performs... Figure 9 In the illustrated embodiment, the second device executes steps 902b, 903b to 904, and 906 to 907. Alternatively, it executes... Figure 10 Steps 1001 to 1003 are performed by the second device in the illustrated embodiment.

[0147] Based on the above embodiments, this application also provides a first device, which includes multiple functional modules; the multiple functional modules interact to implement the functions performed by the first device in the methods described in the embodiments of this application. The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on specific implementations. For example, [the following is an example of implementation details]. Figure 8 In the illustrated embodiment, the first device performs steps 801 to 802, and 806 to 807. Alternatively, it performs... Figure 9 In the illustrated embodiment, the first device performs steps 901 to 902b and steps 905 to 907.

[0148] Based on the above embodiments, this application also provides a second device, which includes at least one processor and at least one memory, wherein the at least one memory stores program instructions. When the second device is executed, the at least one processor performs the functions performed by the second device in the methods described in the embodiments of this application. For example, when executing... Figure 8 In the illustrated embodiment, the second device performs steps 802 to 805 and step 807. Alternatively, it performs... Figure 9 In the illustrated embodiment, the second device executes steps 902b, 903b to 904, and 906 to 907. Alternatively, it executes... Figure 10 Steps 1001 to 1003 are performed by the second device in the illustrated embodiment.

[0149] Based on the above embodiments, this application also provides a first device, which includes at least one processor and at least one memory, wherein the at least one memory stores program instructions. When the first device is executed, the at least one processor performs the functions performed by the first device in the methods described in the embodiments of this application. Figure 8 In the illustrated embodiment, the first device performs steps 801 to 802, and 806 to 807. Alternatively, it performs... Figure 9 In the illustrated embodiment, the first device performs steps 901 to 902b and steps 905 to 907.

[0150] Based on the above embodiments, this application also provides a boot system, which may include the first device and the second device described in the above embodiments.

[0151] Based on the above embodiments, this application also provides a program product, which includes a program (also referred to as code or instructions) that, when run, causes a device or computer to execute the methods described in the embodiments of this application.

[0152] Based on the above embodiments, this application also provides a readable storage medium storing a program that, when executed by a device or computer, causes the device or computer to perform the methods described in the embodiments of this application.

[0153] Based on the above embodiments, this application also provides a chip for reading programs stored in a memory and implementing the methods described in the embodiments of this application.

[0154] Based on the above embodiments, this application provides a chip system including a processor for supporting devices in implementing the methods described in the embodiments of this application. In one possible design, the chip system further includes a memory for storing necessary programs and data. This chip system may be composed of chips or may include chips and other discrete devices. Those skilled in the art will understand that the embodiments of this application can be provided as methods, systems, or program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects.

[0155] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A booting method, characterized in that, include: The second device receives a first message sent by the first device. The first message is used to instruct the first device to initiate multi-device collaboration using a first protocol. The first message includes the collaboration protocol supported by the first device, and the collaboration protocol supported by the first device includes the first protocol. The second device selects a second protocol based on the collaboration protocols supported by the first device and the collaboration protocols supported by the second device; The second device displays a guide interface, which guides the user to perform m operations. Through these m operations, the first device and the second device can perform multi-device collaboration using the multi-device collaboration method corresponding to the second protocol, where m is an integer greater than 0.

2. The method as described in claim 1, characterized in that, The second device displays a boot screen, including: The guide interface can be displayed using a sidebar, notification bar, or full-screen interface.

3. The method as described in claim 1, characterized in that, The second device selects a second protocol based on the collaboration protocols supported by the first device and the collaboration protocols supported by the second device, including: The second device selects the second protocol from one or more collaboration protocols supported by both the first device and the second device.

4. The method as described in claim 2, characterized in that, The second device selects a second protocol based on the collaboration protocols supported by the first device and the collaboration protocols supported by the second device, including: The second device selects the second protocol from one or more collaboration protocols supported by both the first device and the second device.

5. The method as described in claim 1, characterized in that, The second protocol is a collaboration protocol supported by the second device and a collaboration protocol not supported by the first device; The guide interface is used to guide the user to perform m operations on the first device.

6. The method as described in claim 2, characterized in that, The second protocol is a collaboration protocol supported by the second device and a collaboration protocol not supported by the first device; The guide interface is used to guide the user to perform m operations on the first device.

7. The method as described in claim 5, characterized in that, The guide interface includes one or more of the following: a QR code for establishing a communication connection between the first device and the second device, and user operation steps on the first device.

8. The method as described in claim 6, characterized in that, The guide interface includes one or more of the following: a QR code for establishing a communication connection between the first device and the second device, and user operation steps on the first device.

9. The method as described in claim 1, characterized in that, The second protocol is a collaboration protocol supported by the first device and a collaboration protocol not supported by the second device; The guide interface is used to guide the user to perform m operations on the second device.

10. The method as described in claim 2, characterized in that, The second protocol is a collaboration protocol supported by the first device and a collaboration protocol not supported by the second device; The guide interface is used to guide the user to perform m operations on the second device.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: The second device receives a second message sent by the first device using a second protocol, the second message including multi-device collaborative data sent by the first device to the second device.

12. The method according to any one of claims 1 to 10, characterized in that, The second device receives a first message sent by the first device, including: The second device receives the first message sent by the first device via Bluetooth or Wi-Fi connection.

13. The method according to claim 11, characterized in that, The second device receives a first message sent by the first device, including: The second device receives the first message sent by the first device via Bluetooth or Wi-Fi connection.

14. The method according to any one of claims 1 to 10, characterized in that, Before selecting a second protocol based on the collaboration protocols supported by the first device and the collaboration protocols supported by the second device, the method further includes: The second device determines that it does not support the first protocol; or The second device detected a failure in multi-device collaboration with the first device using the first protocol.

15. The method according to claim 11, characterized in that, Before selecting a second protocol based on the collaboration protocols supported by the first device and the collaboration protocols supported by the second device, the method further includes: The second device determines that it does not support the first protocol; or The second device detected a failure in multi-device collaboration with the first device using the first protocol.

16. The method according to claim 12, characterized in that, Before selecting a second protocol based on the collaboration protocols supported by the first device and the collaboration protocols supported by the second device, the method further includes: The second device determines that it does not support the first protocol; or The second device detected a failure in multi-device collaboration with the first device using the first protocol.

17. The method according to claim 13, characterized in that, Before selecting a second protocol based on the collaboration protocols supported by the first device and the collaboration protocols supported by the second device, the method further includes: The second device determines that it does not support the first protocol; or The second device detected a failure in multi-device collaboration with the first device using the first protocol.

18. A guiding method, characterized in that, include: The second device receives a first message sent by the first device via multicast. The first message is used to instruct the first device to initiate DLNA screen mirroring. The second device has been configured to receive the first message. The second device displays a guide interface, which guides the user to enable the hotspot on the first device; The second device connects to the hotspot of the first device and performs DLNA screen mirroring between the first device and the second device based on the hotspot of the first device.

19. A second device, characterized in that, The device includes at least one processor coupled to at least one memory, the at least one processor being configured to read a program stored in the at least one memory to cause the second device to perform the method as claimed in any one of claims 1 to 17, or to perform the method as claimed in claim 18.

Images