Guiding method, and device

Abstract

A guiding method, and a device. The method can be applied to a multi-device collaboration scenario, in which a usable collaboration protocol can be selected on the basis of collaboration protocols respectively supported by multiple devices, and then a user is guided to use a multi-device collaboration mode corresponding to the selected collaboration protocol to perform multi-device collaboration, and thus the occurrence of a multi-device collaboration failure problem can be reduced. In the method, a second device can receive a discovery message sent by a first device, and can thus acquire a collaboration protocol supported by the first device; then, on the basis of the collaboration protocol supported by the first device and a collaboration protocol supported by the second device, one or more collaboration protocols are selected; and the second device can guide a user on the basis of the selected one or more collaboration protocols, and thus the user can be guided to use a collaboration mode corresponding to one of the selected collaboration protocols to perform multi-device collaboration.

Description

A booting method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on August 2, 2023, with application number 202310970257.9 and invention name "A Guiding Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The embodiments of the present application relate to the field of terminal technology, and in particular to a booting method and device. Background Art

[0004] In recent years, with the rapid development of the electronics industry and communications technology, there are now more and more devices, such as mobile phones, tablets, and smart TVs, and people's lives are becoming more and more intelligent. In addition, with the increase in device types and the enrichment of device functions, the application scenarios of multi-device collaboration are becoming increasingly widespread.

[0005] However, due to differences in device ecosystems or operating system capabilities, interoperability between devices can present numerous issues. For example, when a user attempts to perform cross-ecosystem or cross-operating system device operations, multi-device collaboration may not be possible, or collaboration may fail. For example, when the screen projection protocols used by a mobile phone and a TV are inconsistent, screen projection may fail or the user may be unable to cast their screen.

[0006] Summary of the Invention

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

[0008] The first aspect provides a guidance method. In this method, a second device receives a first message sent by a first device, wherein the first message is used to instruct the first device to initiate multi-device collaboration using a first protocol, and 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; 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 second device displays a guidance interface, wherein the guidance interface is used to guide the user to perform m operations, and through the m operations, the first device and the second device use the multi-device collaboration method corresponding to the second protocol to perform multi-device collaboration, 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 the collaborative processing of a business scenario by multiple devices, and multi-device collaboration includes but is not limited to: screen projection scenario, audio projection scenario, file sharing scenario, etc.; wherein, multi-device collaboration is generally implemented based on the corresponding collaboration protocol, and different collaboration protocols can correspond to different multi-device collaboration methods. Taking multi-device collaboration as an example, there are many screen projection protocols that can be used for screen projection, such as but not limited to: miracast (a wireless display standard based on Wi-Fi direct connection), cast+ (a screen projection protocol), dmsdp (a screen projection protocol), google cast (a screen projection proprietary protocol), (a screen projection protocol), etc.

[0009] In this method, the receiver is configured with the ability to receive the discovery message sent by the initiator, so that the receiver can receive the message sent by the initiator, and thus the receiver can learn the operational intention of the multi-device collaboration initiated by the initiator based on the discovery message. In addition, the receiver can also make decisions on the collaboration protocol for multi-device collaboration, select a collaboration protocol from at least one optional collaboration protocol, and can guide the user based on the collaboration method corresponding to the selected collaboration protocol, so as to guide the user to adopt the collaboration method corresponding to the selected collaboration protocol to achieve multi-device collaboration. Therefore, this method does not require a binding relationship or prior negotiation between multiple devices, and can achieve multi-device collaboration across ecosystems or operating systems, thereby avoiding the problem of collaboration failure or inability to collaborate in multi-device collaboration, such as the problem of being unable to cast screens or screen casting failures.

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

[0011] In this embodiment, the second device can use a variety of possible display methods to provide the user with a guidance interface. For example, the guidance interface can be displayed to the user in a full-screen interface to facilitate user viewing, or in a sidebar or notification bar to reduce obstruction of the display interface. This can enhance the diversity of user guidance and ensure the user experience.

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

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

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

[0015] In this embodiment, 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. This can improve the accuracy of user guidance. For example, when the selected collaboration protocol is not supported by the first device, the user can be guided to perform user operations on the first device so that the first device can support the collaboration protocol.

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

[0017] In this embodiment, by providing a guidance interface to the user, it is possible to switch the multi-device collaboration mode, thereby solving the problem that collaboration cannot be achieved using the multi-device collaboration mode selected by the user.

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

[0019] In this embodiment, 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. This can improve the accuracy of user guidance. For example, when the selected collaboration protocol is not supported by the second device, the user can be guided to perform user operations on the second device so that the second device can support the collaboration protocol.

[0020] In a possible implementation, the method further includes: the second device receiving a second message sent by the first device using a second protocol, where the second message includes multi-device collaboration data sent by the first device to the second device.

[0021] In this embodiment, based on the second device, it is possible to switch from the multi-device collaboration mode selected by the user to the multi-device collaboration mode selected by the second device, thereby successfully achieving multi-device collaboration based on the switched multi-device collaboration mode, and avoiding the problem of being unable to achieve multi-device collaboration due to the multi-device collaboration mode selected by the user.

[0022] In a 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 through a Bluetooth connection or a wireless-fidelity (Wi-Fi) connection.

[0023] In this embodiment, the frequently used Bluetooth connection or Wi-Fi connection can be used to enable the second device to have the ability to receive discovery messages sent by other devices, thereby realizing the guidance method introduced in the above embodiments, and further improving the success probability of multi-device collaboration.

[0024] In a possible implementation, before the second device selects the second protocol based on the collaborative protocol supported by the first device and the collaborative protocol 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 detects that multi-device collaboration with the first device using the first protocol has failed.

[0025] In this embodiment, the second device detects the multi-device collaboration with the first device using the first protocol, and only provides user guidance when it detects that the multi-device protocol cannot be performed with the first device using the first protocol, thereby avoiding the impact when the second device can successfully collaborate with the first device using the first protocol.

[0026] The second aspect also provides a guidance method. The method can be applied to a second device. In the method, the second device receives a first message sent by the first device, where the first message is used to instruct the first device to initiate a Digital Living Network Alliance (DLNA) screen projection; the second device displays a guidance interface, where the guidance interface is used to guide the user to turn on the hotspot on the first device; the second device accesses the hotspot of the first device, and performs DLNA screen projection of the first device and the second device based on the hotspot of the first device.

[0027] This method addresses the issue of multiple devices being unable to discover each other in DLNA screen projection scenarios due to the router's restrictions on multicast message forwarding. By configuring the receiver to receive discovery messages sent by the initiator, the receiver can receive messages sent by the initiator, thereby enabling the receiver to receive the initiator's sent messages and, based on the discovery messages, to learn the initiator's multi-device collaborative operation intentions. Furthermore, the receiver can also guide the initiator to enable a hotspot, switching from router forwarding to the initiator building a local area network via the hotspot, thus ensuring successful screen projection.

[0028] A third aspect provides a bootstrapping method. This method can be applied to a first device. In this method, the first device detects and responds to a user operation triggering multi-device collaboration by a user, and sends a first message, wherein the first message is used to instruct the first device to initiate multi-device collaboration using a first protocol, and the first message includes a collaboration protocol supported by the first device, and the collaboration protocols supported by the first device include the first protocol. Exemplarily, the first device can send the first message using unicast, multicast, or broadcast.

[0029] The first device may receive a guidance message from the second device, where the guidance message may be used to enable the first device to perform multi-device collaboration with the second device using a multi-device collaboration method corresponding to the second protocol. The guidance message may, for example, be used to instruct the first device to enable a hotspot, download an application for multi-device collaboration, or automatically trigger a switch to a multi-device collaboration method corresponding to the second protocol, etc., which is not limited in this application.

[0030] Alternatively, based on the second device displaying the guidance interface, the first device may also detect a user operation, such as a code scanning operation, etc. The first message may be, for example, a discovery message.

[0031] In this method, the first device can act as the initiator of multi-device collaboration and send a discovery message in response to the user operation of initiating multi-device collaboration, so that the second device can receive the message sent by the first device and learn the operational intention of the multi-device collaboration initiated by the initiator, etc., thereby realizing the guidance method described in the first aspect and its various embodiments.

[0032] A fourth aspect provides a guidance system. The system includes the second device described in the first aspect or the second aspect and its respective embodiments, and the first device described in the third aspect and its respective embodiments. The second device can be used to perform the method described in the first aspect or the second aspect and its respective embodiments, and the first device can be used to perform the method described in the third aspect and its respective embodiments.

[0033] A fifth aspect provides a second device, comprising multiple functional modules; the multiple functional modules interact with each other to implement the method performed by the second device in the first aspect and its respective embodiments, or to implement the method performed by the second device in the second aspect and its respective embodiments. 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 the specific implementation.

[0034] A sixth aspect provides a first device, comprising multiple functional modules; the multiple functional modules interact with each other to implement the method performed by the first device in the third aspect and its respective embodiments. 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 the specific implementation.

[0035] The seventh aspect also provides a second device, including at least one processor and at least one memory, wherein a program is stored in the at least one memory. When the second device is running, the at least one processor executes the method executed by the second device in the above-mentioned first aspect and its various embodiments, or executes the method executed by the second device in the above-mentioned second aspect and its various embodiments.

[0036] 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. When the first device is running, the at least one processor executes the method executed by the first device in the above-mentioned third aspect and its various embodiments.

[0037] The ninth aspect provides a readable storage medium, which stores instructions. When the instructions are executed on a second device, the second device executes the method described in the first aspect and its possible implementation methods, or executes the method described in the second aspect and its possible implementation methods; or, when the instructions are executed on a first device, the first device executes the method described in the third aspect and its possible implementation methods.

[0038] The tenth aspect provides a program product, which, when running on a second device, enables the second device to execute the method described in the first aspect and its possible implementation methods, or execute the method described in the second aspect and its possible implementation methods; or, when running on a first device, enables the first device to execute the method described in the third aspect and its possible implementation methods.

[0039] The eleventh aspect also provides a chip, which is used to read the program stored in the memory, execute the method executed by the second device of the above-mentioned first aspect and its possible implementation methods, or execute the method executed by the second device of the above-mentioned second aspect and its possible implementation methods, or execute the method executed by the first device of the above-mentioned third aspect and its possible implementation methods.

[0040] The twelfth aspect also provides a chip system, which includes a processor for supporting a second device to implement the method executed by the second device in the first aspect and its possible implementation methods, or for supporting a second device to implement the method executed by the second device in the second aspect and its possible implementation methods, or for supporting a first device to implement the method executed by the first device in the third aspect and its possible implementation methods. In one possible implementation, the chip system also includes a memory, which is used to store programs and data necessary for the device. The chip system can be composed of chips, or it can include chips and other discrete devices.

[0041] For the beneficial effects of any of the second to twelfth aspects and their possible implementations, please refer to the beneficial effects of various possible implementations in the first aspect, which will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] FIG1 is a schematic diagram of the hardware structure of a possible device provided in an embodiment of the present application;

[0043] FIG2 is a block diagram of a software system architecture of a device provided in an embodiment of the present application;

[0044] FIG3 is a schematic diagram of one application scenario of a guidance method provided in an embodiment of the present application;

[0045] FIG4 is a second schematic diagram of an application scenario of a guidance method provided in an embodiment of the present application;

[0046] FIG5 is a third schematic diagram of an application scenario of a guidance method provided in an embodiment of the present application;

[0047] FIG6 is a fourth schematic diagram of an application scenario of a guidance method provided in an embodiment of the present application;

[0048] FIG7 is a fifth schematic diagram of an application scenario of a guidance method provided in an embodiment of the present application;

[0049] FIG8 is a flow chart of a guidance method according to an embodiment of the present application;

[0050] FIG9 is a second flow chart of a guidance method provided in an embodiment of the present application;

[0051] FIG10 is a third flow chart of a guidance method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0052] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0053] Devices such as mobile phones, tablets, smart screens and smart home devices are becoming more and more popular, and as the types of devices gradually increase and the functions of devices gradually become richer, the application scenarios of multi-device collaboration are becoming increasingly extensive; among them, multi-device collaboration refers to the collaborative processing of a business scenario by multiple devices. For example, multi-device collaboration includes but is not limited to: screen projection scenarios, audio projection scenarios, file sharing scenarios, etc. It can be understood that the application scenarios of multi-device collaboration are implemented using corresponding collaboration protocols; for example, the screen projection scenario is implemented using the screen projection protocol, the audio projection scenario is implemented using the audio projection protocol, and the file sharing scenario is implemented using the file sharing protocol. However, due to the differences in the ecology, operating system capabilities, etc. of different devices, there may be many problems in the interoperability between devices.

[0054] For ease of understanding, the following embodiments use the screen projection scenario as an example to introduce the method provided in this application. For other application scenarios of multi-device collaboration, please refer to the embodiments of the screen projection scenario, which will not be repeated in the following embodiments.

[0055] The current mainstream screen projection scenarios include mirror projection and application projection. Among them, mirror projection can, for example, project the display interface of the mobile phone onto the large screen for mirror display; application projection can, for example, project the video data of the video application included in the mobile phone onto the large screen for video display. Based on different screen projection scenarios, different types of devices, etc., there are also many screen projection protocols, such as but not limited to: miracast (a wireless display standard based on Wi-Fi direct connection), cast+ (a screen projection protocol), dmsdp (a screen projection protocol), google cast (a proprietary screen projection protocol), (a screen projection protocol), etc. Due to reasons such as the device's ecology and operating system, the screen projection protocols supported by devices from different manufacturers may be different or not completely the same. It can be understood that when the source device (for example, it can be understood as the initiator in the screen projection scenario) selects the screen projection method and the screen projection protocol adopted, and the target device (for example, it can be understood as the receiver that can receive the projection data in the screen projection scenario) cannot support the screen projection protocol, it will cause the user to be unable to project the screen or the screen projection fails, and the user experience is poor.

[0056] In one possible implementation, in a scenario where a mobile phone and a large screen support the same system and distributed capabilities, after the mobile phone and the large screen are bound, the user can maintain a connection with the large screen through a distributed soft bus when playing content on the mobile phone; wherein, the binding of the mobile phone and the large screen can also be understood as the mutual authentication and authentication when the mobile phone and the large screen need to establish a connection for the first time for multi-device collaboration, and the binding relationship between the mobile phone and the large screen can be stored, so that when the mobile phone and the large screen need to establish a connection again for multi-device collaboration, there is no need to authenticate again. Since the viewing experience of the large screen is better, the user can be prompted on the mobile phone whether to transfer the playback. When the user agrees to the transfer, the mobile phone can send a transfer instruction to the large screen through the distributed soft bus, so that the content on the mobile phone can be played by the large screen, and the playback control interface can be displayed on the mobile phone. It can be understood that in this implementation, it is possible to actively send a prompt to the user through the interface whether to transfer the content playback. However, this implementation cannot solve the problem that screen casting cannot be achieved when the screen casting protocols used by the source device and the target device are different.

[0057] In view of this, an embodiment of the present application provides a guidance method. In this method, a target device can determine the source device's operational intent and the collaborative capabilities supported by the source device based on a discovery message from the source device. The target device can then select one or more collaboration modes 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 one or more pages of guidance interfaces for implementing collaboration based on the selected one or more collaboration modes. Alternatively, the target device can send the selected one or more collaboration modes to the source device, which then provides the user with one or more pages of guidance interfaces for implementing collaboration based on the selected one or more collaboration modes. Therefore, this method eliminates the need for a binding relationship between the source and target devices, nor does it require the source and target devices to negotiate in advance. The binding relationship between the source and target devices can be understood as the stored relationship between a mobile phone and a large screen after binding. Based on the target device's perception capabilities and the collaborative capabilities of the source and target devices, a collaborative capability supported by both the source and target devices is selected. Furthermore, based on the supported collaborative capabilities, the user is guided to use the collaborative mode corresponding to the collaborative capability for device collaboration. In this way, the method can increase the success rate of multi-device collaboration, thereby optimizing the user experience.

[0058] It is understandable that the source device of the embodiment of the present application can be a device such as a mobile phone, tablet computer, laptop computer, or even a large screen that has the ability to initiate multi-device collaboration; and the target device of the embodiment of the present application can be a device such as a large screen, projector, smart speaker, or even a mobile phone, tablet computer, laptop computer, or other device that has the ability to receive multi-device collaboration. In addition, the embodiment of the present application does not impose any restrictions on the specific type of source device or target device. The devices to which the embodiment of the present application can be applied include, but are not limited to, devices equipped with Or devices with other operating systems.

[0059] FIG1 shows a schematic diagram of the hardware structure of a possible device. Among them, 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 the hardware structure of the device 100 shown in FIG1 does not constitute a limitation on the device 100. The device 100 provided in the embodiment of the present application may include more or fewer components than shown, may combine two or more components, or may have different component configurations. The various components shown in FIG1 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.

[0060] The following is a detailed introduction to the various components of the device 100 in conjunction with FIG1 :

[0061] The RF circuit 210 can be used to receive and transmit data during communications or calls. Specifically, after receiving downlink data from the base station, the RF circuit 210 sends it to the processor 230 for processing. Furthermore, it sends uplink data 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, and the like.

[0062] In addition, 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 of mobile communication (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), long term evolution (LTE), 5G, email, short messaging service (SMS), etc.

[0063] 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 to access a data network. The Wi-Fi module 290 can be used to receive and send data during the communication process.

[0064] The device 100 can be physically connected to other devices via the communication interface 280. Optionally, the communication interface 280 is connected to the communication interface of the other device via a cable to achieve data transmission between the device 100 and the other device.

[0065] The device 100 can also implement communication services and interact with service-side devices or other devices. Therefore, the device 100 needs to have a data transmission function, that is, the device 100 needs to include a communication module. Although Figure 1 shows communication modules such as the RF circuit 210, the Wi-Fi module 290, and the communication interface 280, it is understandable that the device 100 contains at least one of the above components or other communication modules (such as a Bluetooth module) for implementing communication to perform data transmission.

[0066] 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 (not shown in Figure 1); 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 Figure 1). In an embodiment of the present application, when the device 100 is a mobile phone, it can communicate with the large screen through a communication module such as the RF circuit 210 or the Wi-Fi module 290. For example, when the mobile phone detects the user's screen projection operation, in response to the screen projection operation, a discovery message can be sent through a communication module such as the RF circuit 210 or the Wi-Fi module 290; the large screen can receive the discovery message sent by the mobile phone through a communication module such as the RF circuit 210 or the Wi-Fi module 290. For another example, when a mobile phone and a large screen can perform multi-device collaboration through the guidance method provided in the embodiment of the present application, the mobile phone can send collaborative data to the large screen through communication modules such as the RF circuit 210 or the Wi-Fi module 290. Similarly, the large screen can receive collaborative data sent by the mobile phone through communication modules such as the RF circuit 210 or the Wi-Fi module 290.

[0067] 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. Among them, the program storage area can store an operating system (mainly including the kernel layer, system layer, application framework layer and application layer, etc., each corresponding software program or software module). In addition, the memory 240 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage device. In an embodiment of the present application, when the device 100 is a large screen, a screen projection protocol supported by the large screen may be stored in the memory 240. For example, the screen projection protocols stored in the memory 240 of the large screen may include miracast, cast+, and dmsdp.

[0068] The input unit 250 may be used to receive user input of various types of data objects such as numbers or characters, 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.

[0069] Among them, the touch panel 251, also known as a touch screen, can collect the user's touch operations on or near it (such as the user's operation using any suitable object or accessory such as a finger, stylus, etc. on or near the touch panel 251), and drive the corresponding connection device according to a pre-set program. In an embodiment of the present application, 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 for indicating triggering screen projection through the touch panel 251. For another example, when the device 100 is a large screen, the guidance interface provided to the user on the large screen can collect user operations for indicating the user based on the guidance of the large screen through the touch panel 251, such as the user determines to adopt the screen projection method provided by the large screen on the guidance interface.

[0070] Optionally, the other input devices 252 may include, but are not limited to, one or more of a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a mouse, a joystick, etc.

[0071] The display unit 260 can be used to display information input by the user or information provided to the user and various menus of the device 100. The display unit 260 is the guidance system of the device 100, which is 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 display. In an embodiment of the present application, the display unit 260 can be used to display the display content involved in the method provided in the present application. For example, when the device 100 is a large screen, the display unit 260 can be used to display the guidance interface, and can also be used to display the projection data from the mobile phone in a scenario where the large screen and the mobile phone can perform multi-device collaboration. For another example, when the device 100 is a mobile phone, the display unit 260 can be used to display the video data being played on the mobile phone, and can also display controls for the user to project the video data.

[0072] The processor 230 is the control center of the device 100. It connects various components using various interfaces and lines, executes or runs software programs and / or software modules stored in the memory 240, and calls data stored in the memory 240 to perform various functions of the device 100 and process data, thereby implementing various services based on the device 100. In the embodiment of the present application, the processor 230 can be used to implement the method provided in the embodiment of the present application.

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

[0074] As shown in Figure 1, the device 100 also includes an audio circuit 270, a microphone 271 and a speaker 272, which can provide an audio interface between the user and the device 100. The audio circuit 270 can be used to convert audio data into a signal that can be recognized by the speaker 272, and transmit the signal to the speaker 272, which is converted into a sound signal for output by the speaker 272. The microphone 271 is used to collect external sound signals (such as the sound of a person speaking or other sounds, etc.), and convert the collected external sound signals into signals that can be recognized by the audio circuit 270 and send them to the audio circuit 270. The audio circuit 270 can also be used to convert the signal sent by the microphone 271 into audio data, and then output the audio data to the RF circuit 210 to send it to, for example, another device, or output the audio data to the memory 240 for subsequent further processing.

[0075] Although not shown, the device 100 may further include a camera, at least one sensor, etc., which will not be described in detail herein. The at least one sensor may include but is not limited to an acceleration sensor, a distance sensor, a fingerprint sensor, a touch sensor, a temperature sensor, etc.

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

[0077] The operating system (OS) involved in the embodiments of the present application 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. The embodiments of the present application use an operating system adopting a layered architecture as an example to illustrate the software structure of device 100.

[0078] Figure 2 is a block diagram of the software structure of a device provided in an embodiment of the present application. As shown in Figure 2, the software structure of the device can be a layered architecture. For example, the software can be divided into several layers, each with a clear role and division of labor. The 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 library, the kernel layer, and the hardware layer.

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

[0080] In one possible implementation, applications can be developed using Java by calling the application programming interface (API) provided by the application framework layer. Developers can use the application framework layer to interact with the underlying operating system layers (e.g., the hardware layer, kernel layer, etc.) to develop their own applications. The application framework layer primarily provides a series of services and management systems for the operating system.

[0081] The application framework layer provides an application programming interface and programming framework for applications in the application layer. The application framework layer includes some predefined functions. As shown in Figure 2, the application framework layer can include an activity manager, a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and so on.

[0082] The activity manager is used to manage the life cycle of each application and provide common navigation back functions, providing an interactive interface for all program windows.

[0083] The window manager manages windowed applications. It can determine the display size, determine whether a status bar is present, lock the screen, and take screenshots. The content provider stores and retrieves data and makes it accessible to applications. This data can include video, images, audio, and more.

[0084] The view system includes visual controls, such as those that display text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, it might include a view that displays text and another that displays images.

[0085] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, etc.

[0086] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically, without requiring user interaction. For example, the Notification Manager can be used to announce the completion of 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 that appear on the screen.

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

[0088] The core library consists of two parts: one containing the Java language's callable functions and the other containing the operating system's core libraries. The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0089] The system library can include multiple functional modules, such as a surface manager, a media framework, a 3D graphics processing library (such as OpenGL ES), and a 2D graphics engine (such as SGL).

[0090] The surface manager is used to manage the display subsystem and provide the fusion of two-dimensional and 3D layers for multiple applications.

[0091] The media framework supports playback and recording of a variety of common audio and video formats, as well as static image files. The media framework can support a variety of audio and video encoding formats, such as MPEG4, H.264, MP3, etc.

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

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

[0094] In some embodiments, a 3D graphics processing library may be used to render 3D motion images, and a 2D graphics engine may be used to render 2D motion images.

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

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

[0097] Typically, the device 100 can run multiple applications simultaneously. In simpler cases, one application corresponds to one process, while in more complex cases, one application corresponds to multiple processes. Each process has a process ID.

[0098] It should be understood that in the embodiments of the present application, "at least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural 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, c can be single or multiple. "Multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship.

[0099] In addition, it should be understood that, in the description of this application, words such as "first" and "second" are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

[0100] It should be understood that the hardware structure of the device can be as shown in Figure 1, and the software system architecture can be as shown in Figure 2, wherein 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 process of a boot method provided in an embodiment of the present application.

[0101] In order to facilitate understanding of a guidance method provided by the present application, the implementation process of the method provided by the present application is introduced below in combination with the contents shown in Figures 3 to 9.

[0102] The method provided in the embodiment of the present application can be applied to the scenario of multi-device interconnection, and can be used for multi-device collaboration of multiple devices, so as to have a better device usage experience. For ease of understanding, in the following embodiments, the multi-device collaboration scenario takes the screen projection scenario as an example, and Figure 3 is a schematic diagram of an application scenario of the screen projection operation. The application scenario can include at least a mobile phone 310 and a large screen 320. In the scenario of projecting the display interface of the mobile phone 310 to the large screen 320, the user can trigger the screen projection scene by clicking on the icon 300 for wireless screen projection in the drop-down notification interface of the mobile phone 310; wherein, the mobile phone 310 responds to the user's touch operation on the icon 300, and can trigger the screen projection operation based on the screen projection protocol corresponding to the icon 300 (assuming it is screen projection protocol 1). In a possible application scenario, when the large screen 320 can also support the screen projection protocol 1, the large screen 320 can be scanned on the mobile phone 310, so that the display interface of the mobile phone 310 can be projected onto the large screen 320. For example, the display screen of the large screen 320 in Figure 3 can display the display interface of the mobile phone 310.

[0103] In another possible application scenario, when the large screen 320 in Figure 3 does not support screen projection protocol 1, the mobile phone 310 may not be able to scan the large screen 320, or even if it scans the large screen 320, the screen projection may fail. Through the method provided in the embodiment of the present application, the user can be guided to achieve successful screen projection in this scenario through one or more pages of guidance interface. Among them, the guidance method provided in the embodiment of the present application may also include one or more possible application scenarios, which may include but are not limited to the following scenarios A to D, as follows:

[0104] Scenario A and Figure 4 are schematic diagrams of an application scenario of a guidance method provided in an embodiment of the present application. In this application scenario, the large screen 320 can display an interface 410; wherein, the interface 410 may include a prompt box, and the prompt box is used to indicate other screen projection protocols that the user can use to implement screen projection. 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 understand how to operate", "Confirm" control, "Reject" control, etc. Among them, other screen projection protocols can be understood as screen projection protocols supported by both the mobile phone 310 and the large screen 320, such as screen projection protocol 2; or, other screen projection protocols can also be understood as screen projection protocols that are easy for users to operate. For example, although the mobile phone 310 does not support screen projection protocol 3, screen projection protocol 3 can be implemented by downloading the corresponding application (application, APP).

[0105] In a possible embodiment, when the large screen 320 detects a user's touch operation on the "Confirm" control on the interface 410, the interface 420 may be displayed in response to the touch operation; wherein, the interface 420 may include an operation guide box, and the operation guide box may be used to instruct the user how to implement screen projection using a projection method corresponding to other screen projection protocols. As shown in the interface 420, the operation guide box may include but is not limited to: a QR code for implementing screen projection by scanning a code, a screen projection tutorial including an operation tutorial, etc.; wherein, the operation tutorial can be used to instruct how to implement screen projection through user operation. It is understandable that when the large screen 320 detects a user's touch operation on the "Reject" control on the interface 410, the homepage interface or the currently playing interface of the large screen may be displayed in response to the touch operation.

[0106] Based on the QR code provided by the interface 420 in Figure 4, it is possible to guide the user to perform a code scanning operation through the mobile phone 310. It is understandable that the mobile phone 310 can identify the content corresponding to the QR code in response to the code scanning operation. Exemplarily, after the mobile phone 310 identifies the content corresponding to the QR code, it can directly realize the projection of the display interface of the mobile phone 310 to the large screen 320. Another exemplary embodiment, after the mobile phone 310 recognizes the content corresponding to the QR code, it can also display an interface for realizing screen projection, through which it can be realized to guide the user to project the display interface of the mobile phone 310 to the large screen 320.

[0107] In addition, the large screen 320 can also collect and count the user operations on the interface 410, analyze the user preferences based on the statistical results, and then guide the user according to the user preferences. For example, when the large screen 320 analyzes that the user preference is to confirm the need for screen projection and understand how to operate, the next time the user's screen projection scene is detected and guidance is required, the interface 420 can be directly displayed, thereby simplifying the user operation. Another example is that when the large screen 320 analyzes that the user preference is to refuse the need for screen projection and understand how to operate, even if the user's screen projection scene is detected next time and guidance is required, the interface 410 and interface 420 will no longer be displayed to the user, thereby avoiding a bad user experience.

[0108] It should be noted that interface 410 is only one possible example. The embodiments of this application do not limit the style of the prompt box. For example, it can also be implemented through notification messages, voice playback, or a combination of multiple methods. In another possible embodiment, Figure 5 is a schematic diagram of another application scenario of a guidance method provided by the embodiments of this application. Compared to interface 410 in Figure 4, the prompt box included in interface 510 in Figure 5 may include, but is not limited to, prompt information such as "Do you need to cast the screen?", a "Confirm" control, a "Reject" control, and a "Confirm and learn how to cast the screen" control. When the mobile phone detects a user touch operation on the "Confirm" control, in response to the touch operation, interface 520 may be displayed. However, compared to interface 420 in Figure 4, the operation guidance box included in interface 520 may not include a casting tutorial. It is understood that when the mobile phone detects a user touch operation on the "Confirm and learn how to cast the screen" control, in response to the touch operation, interface 420 as shown in Figure 4 may be displayed. In this case, the operation guidance box included in interface 420 may not only include scanning a code to cast the screen, but also include display content such as a casting tutorial.

[0109] It should also be noted that interface 420 is only a possible example, and the style and display content of the operation guide box are not limited in the embodiments of the present application. For example, when the other screen projection protocol is a screen projection protocol that is easy for the user to operate, the operation guide box displayed on interface 420 includes an APP icon corresponding to downloading screen projection protocol 3; or, when the guidance is implemented on mobile phone 310, the operation guide box may also include a control to guide the jump to the application market. For another example, the operation tutorial in the screen projection tutorial included in interface 420 can be in a folded state or a slidable state, etc.

[0110] Scenario B, FIG6 is a schematic diagram of another application scenario of a guidance method provided in an embodiment of the present application. In this application scenario, the large screen 320 can display an interface 610; wherein, the interface 610 may include an operation guide frame, and the operation guide frame can be used to indicate the operation guide frame shown in the interface 420 in FIG4 , and the operation guide frame can be used to instruct the user how to use other screen projection methods to achieve screen projection. In combination with FIG4 and FIG6 , it can be seen that the operation guide frame in the interface 610 can be displayed on one side of the large screen 320; and, compared to the scenario shown in FIG4 , the scenario shown in FIG6 can directly superimpose the operation guide frame on one side of the large screen 320. Through this scenario, compared to the implementation method in FIG4 in which the "Confirm" control or the "Reject" control needs to be clicked in the interface 410, user operations can be reduced, and by displaying it on one side of the large screen 320, the blocking effect on the playing interface of the large screen 320 can be reduced.

[0111] In a possible embodiment, when the large screen 320 detects that the user slides the operation guide frame on the interface 610 toward the outside of the screen, in response to the sliding operation, the operation guide frame in the interface 610 may no longer be displayed.

[0112] Alternatively, in another possible embodiment, the operation guide frame in the interface 610 may be pre-set for a display duration; wherein the display duration may be, for example, 5 seconds or 10 seconds. Exemplarily, the timing starts from the display of the operation guide frame, and when the timing reaches the set display duration, the operation guide frame may no longer be displayed. Therefore, this embodiment can reduce user operations and avoid long-term obstruction of the display screen of the large screen 320. In addition, the display duration can also be manually set by the user on a display interface such as a settings interface.

[0113] Scenario C, Figure 7 is another application scenario diagram of a guidance method provided by an embodiment of the present application. In this application scenario, the large screen 320 can display an interface 710; wherein, the interface 710 may include a prompt box of a different style from the prompt box in Figure 4, and the prompt box may also be used to indicate other screen projection protocols that the user can use to implement screen projection. As shown in interface 710, the prompt box may include but is not limited to: prompt information such as "Do you need to project the screen and learn how to operate it?". In combination with Figures 4 and 6, it can be seen that the prompt box in interface 710 can be displayed on top of the large screen 320; and, compared to the scenario shown in Figure 4, the scenario shown in Figure 7 can directly superimpose the prompt box on the top of the large screen 320.

[0114] In one possible embodiment, when the large screen 320 detects the user's first touch operation on the prompt box on the interface 710, the interface 720 may be displayed in response to the first touch operation. For example, the first touch operation may be a click operation, a long press operation, etc. Among them, the interface 720 may include an operation guide box, and the operation guide box may be used to instruct the user how to implement screen projection using projection methods corresponding to other screen projection protocols. As shown in the interface 720, the operation guide box may include but is not limited to: a QR code for implementing scan code projection, a screen projection tutorial, etc. In another possible embodiment, when the large screen 320 detects the 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 may be, for example, a sliding operation to the outside of the screen.

[0115] Alternatively, in another possible embodiment, the prompt box in interface 710 may be pre-set for a display duration. For example, a timer may be set starting from the time the prompt box is displayed, and when the timer reaches the set display duration, the prompt box may no longer be displayed. Therefore, this embodiment can reduce user operations and avoid long-term obstruction of the display image of large screen 320.

[0116] Scenario D, as shown in the embodiments of Figures 4 to 7, in addition to implementing guidance on the large screen 320, guidance can also be implemented on the mobile phone 310, thereby improving the convenience of user operation. The specific implementation scenarios can refer to the introduction of the above scenarios A to C, which will not be repeated here.

[0117] Based on the above description of the interface processing effect that can be achieved by using the method provided in the embodiment of the present application, the following introduces the implementation process of the guidance method provided in the present application to illustrate how to use the method provided in the present application to achieve the interface processing effects shown in Figures 4 to 7 introduced above.

[0118] In a possible embodiment, FIG8 is a flowchart of a boot method provided in an embodiment of the present application. The method can be applied to the second device, and the process may include the following steps:

[0119] Step 801: A first device detects a first user operation for screen projection. The first device may be, for example, a source device as described in the preceding embodiments, such as the mobile phone 310 described in Scenarios A through D. For example, as shown in FIG3 , the first user operation may be a user touching an icon 300.

[0120] Step 802: The first device sends a discovery message in response to the first user operation. The discovery message can be used by the first device to discover other nearby devices and can indicate the screen projection intention of the first device. For example, the screen projection intention can be to initiate screen projection using screen projection protocol 1; the discovery message can also include at least one screen projection protocol supported by the first device. In one possible embodiment, the first device can send the discovery message via a connection such as Bluetooth, Wi-Fi, etc. The connection method for the first device to send the discovery message is not limited in the embodiment of the present application.

[0121] 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 aforementioned embodiments, such as the large screen 320 described in scenarios A to D.

[0122] 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 the embodiments of the present application do not limit the number of discovery messages that the second device can receive. For example, the second device can receive discovery messages from both source device 1 and source device 2.

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

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

[0125] In an optional embodiment, the first device supports screen projection protocol 1 and screen projection protocol 2, and the second device supports screen projection protocol 2 and screen projection protocol 3. When the first device detects that screen projection protocol 1 is used for screen projection in step 801, the discovery message sent by the first device in step 802 can indicate that the operation intention of the first device is to use the screen projection method corresponding to screen projection protocol 1 for screen projection. After the second device receives the discovery message sent by the first device, the second device determines that the operation intention of the first device is to use screen projection protocol 1 for screen projection, and determines that the first device not only supports screen projection protocol 1 but also supports screen projection protocol 2. At this time, the second device can select screen projection protocol 2 supported by both the first device and the second device for screen projection. Then, the second device can guide the user to use screen projection protocol 2 for screen projection. For example, the projection method corresponding to projection protocol 1 can be mirror projection. Since the mobile phone and the large screen use different operating systems, the mobile phone cannot use the mirror projection method to project the screen to the large screen; the projection method corresponding to projection protocol 2 can be application projection. Based on the mobile phone and the large screen being connected to the same Wi-Fi, the large screen can guide users to use the application projection method to project the screen to the large screen.

[0126] In another optional embodiment, the first device supports screen projection protocol 1 and screen projection protocol 2, and the second device supports screen projection protocol 3 and screen projection protocol 4. When the first device detects in step 801 that screen projection is performed using screen projection protocol 1, the discovery message sent by the first device in step 802 may indicate that the operation intention of the first device is to perform screen projection using the screen projection method corresponding to screen projection protocol 1. After the second device receives the discovery message sent by the first device, the second device determines that the operation intention of the first device is to perform screen projection using screen projection protocol 1, and determines that the first device not only supports screen projection protocol 1 but also supports screen projection protocol 2, while the second device supports screen projection protocol 3 and screen projection protocol 4. Based on the fact that the first device and the second device do not have the same screen projection protocol, the second device may select one screen projection protocol from screen projection protocol 3 and screen projection protocol 4 to guide the user to perform screen projection using the selected screen projection protocol. For example, the projection method corresponding to projection protocol 1 can be mirror projection. Since the mobile phone and the large screen use different operating systems, the mobile phone cannot use the mirror projection method to project the screen to the large screen; the projection method corresponding to projection protocol 2 can be application projection. Since the mobile phone and the large screen are not connected to the same Wi-Fi, the mobile phone cannot use the application projection method to project the screen to the large screen; the projection method corresponding to projection protocol 3 is with the help of the projection APP. When the large screen selects projection protocol 3, the large screen can guide the user to download the projection APP on the mobile phone, so that the screen can be projected to the large screen based on the projection APP.

[0127] In the above embodiment, the large screen can select the projection protocol based on one or more factors such as the complexity of the user's operation, the user experience of the projection protocol, etc.

[0128] Step 805: The second device performs screen projection guidance according to the selected screen projection protocol. For example, the screen projection guidance can be interface 410 and interface 420 as shown in Figure 4. For another example, the screen projection guidance can be interface 510 and interface 520 as shown in Figure 5. Or for example, the screen projection guidance can also be interface 610 as shown in Figure 6. Or for another example, the screen projection guidance can also be interfaces 710 and 720 as shown in Figure 7. It can be understood that the second device can also detect user operations during the process of screen projection guidance, such as detecting the user's touch operation on the "Confirm" control on interface 410, and the user's touch operation on the prompt box on interface 710.

[0129] In a possible embodiment, the second device can collect touch operations during the screen projection guidance process, perform statistics and analysis on the touch operations, and obtain user preferences, so that the next screen projection guidance method can be set based on the user preferences. For example, when the second device analyzes that the user preference is to accept the screen projection protocol selected by the second device, the next time the user's screen projection scene is detected and guidance is required, it can be assumed that the user accepts the screen projection protocol selected by the second device, and the operation guidance box is directly displayed to the user without user feedback. For example, the interface 420 shown in Figure 4 is directly displayed, and the interface 410 shown in Figure 4 is no longer displayed, thereby simplifying user operations. For another example, when the second device analyzes that the user preference is not to accept the screen projection protocol selected by the second device, it can be assumed that the user rejects the screen projection protocol selected by the second device, and the guidance interface is no longer provided to the user, thereby avoiding a bad user experience.

[0130] It should be noted that the embodiment of the present application does not limit the implementation method of the screen projection guidance. For example, it can be implemented through at least one of the guidance interface, prompt box interface, notification interface, voice, etc.

[0131] Step 806: The first device detects a second user operation, where the second user operation 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 interface 420 shown in FIG. 4 , the second user operation that the first device can detect can be a code scanning operation. For another example, when the guidance of the second device is to download a screen projection app, the second user operation that the first device can detect can be a download operation of the screen projection app.

[0132] Step 807: The first device and the second device exchange messages, wherein the interaction message is used to execute screen projection of the first device to the second device. Exemplarily, the interaction message can be used to establish a screen projection connection between the first device and the second device, for example, the interaction message can be used to enable the second device to access the same Wi-Fi network as the first device; or, when the first device establishes a screen projection connection with the second device through step 806, the interaction message can be the data to be projected, etc.

[0133] In another possible embodiment, FIG9 is a flow chart of a boot method provided in an embodiment of the present application. The method can be applied to a scenario where the first device uses the Digital Living Network Alliance (DLNA) to project the screen. The process may include the following steps:

[0134] Step 901: A first device detects a first user operation for screen projection. The first device may be, for example, a source device as described in the preceding embodiments, such as the mobile phone 310 described in Scenarios A through D. For example, as shown in FIG3 , the first user operation may be a user touching an icon 300.

[0135] Step 902a: The router receives a discovery message multicasted by the first device. DLNA screen casting discovery is based on the local area network CoAP protocol, and the CoAP message is a multicast message.

[0136] Step 903a: The router does not forward the discovery message and directly discards it. However, since some routers may restrict the forwarding of multicast messages in their processing policies, the first device may not be able to find the second device when casting the screen, and thus the first device cannot cast the screen to the second device.

[0137] Step 902b: The second device receives the discovery message multicasted by the first device. In this embodiment of the present application, the second device can be configured with the capability to receive layer 2 messages, so the second device can receive the discovery message multicasted by the first device without relying on router forwarding.

[0138] Step 903b: The second device determines the operation intention of the first device based on the discovery message. It can be understood that based on the content of step 901, it can be determined that the operation intention of the first device is to perform screen projection.

[0139] Step 904: The second device performs screen projection guidance, which is used to instruct the first device to turn on the hotspot. It is understandable that the content of the screen projection tutorial displayed on the guidance interface of the second device in this scenario can be a prompt message of "Please start hotspot".

[0140] Step 905: The first device detects a third user operation, wherein the third user operation is to enable a hotspot. It is understood that the user can enable the hotspot of the first device by using the screen projection guidance of the second device.

[0141] Step 906: The second device connects to the hotspot of the first device. It is understandable that after the second device performs the screen projection guidance based on step 904, it can start the wireless local area scanning process based on the screen projection guidance, thereby facilitating the connection to the hotspot of the first device.

[0142] Step 907: The first device begins to project its screen to the second device. It is understood that after the second device connects to the hotspot of the first device, the first device and the second device are in the same local area network, and a communication connection can be established between the first device and the second device. The projected screen data of the first device can then be sent to the second device based on the communication connection, thereby enabling the first device to project its screen to the second device.

[0143] In the method provided in the embodiment of the present application, the target device is configured with the ability to receive discovery messages from other devices, so that the target device can receive messages sent by the source device, thereby realizing the operation intention of multi-device collaboration initiated by the source device based on the discovery message. In addition, the target device can also make decisions on the collaboration mode of multi-device collaboration, select a collaboration mode from at least one optional collaboration mode, and can perform collaboration guidance based on the selected collaboration mode to guide the user to adopt the selected collaboration mode to achieve multi-device collaboration. Therefore, the method does not require a binding relationship or prior negotiation between multiple devices, and can achieve multi-device collaboration across ecosystems or operating systems, thereby avoiding the problem of collaboration failure or inability to collaborate in multi-device collaboration, such as the problem of inability to cast screen or failure of screen casting.

[0144] In an optional embodiment, FIG10 is an interactive process of a guidance method provided in an embodiment of the present application. The interactive process may include the following steps:

[0145] Step 1001: The second device receives a first message sent by the first device, where 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 protocols supported by the first device include the first protocol.

[0146] Among them, the first device can be understood as the initiator of multi-device collaboration, such as the mobile phone introduced in the aforementioned embodiment; the second device can be understood as the receiver of multi-device collaboration; such as the large screen introduced in the aforementioned embodiment; the first message can be, for example, a discovery message sent by the first device.

[0147] 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.

[0148] Step 1003: The second device displays a guidance interface, wherein the guidance interface is used to guide the user to perform m operations, and through the 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. For example, the guidance interface can be interface 410 and interface 420 as shown in Figure 4. For another example, the guidance interface can be interface 510 and interface 520 as shown in Figure 5. For another example, the guidance interface can also be interface 610 as shown in Figure 6. For another example, the guidance interface can also be interface 710 and interface 720 as shown in Figure 7.

[0149] Based on the above embodiments, the present application also provides a second device, which includes multiple functional modules; the multiple functional modules interact with each other to implement the functions performed by the second device in each method described in the embodiments of the present 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 the specific implementation. For example, execute steps 802 to 805 and step 807 performed by the second device in the embodiment shown in Figure 8. Alternatively, execute steps 902b, 903b to 904, and 906 to 907 performed by the second device in the embodiment shown in Figure 9. Alternatively, execute steps 1001 to 1003 performed by the second device in the embodiment shown in Figure 10.

[0150] Based on the above embodiments, the present application also provides a first device, which includes multiple functional modules; the multiple functional modules interact with each other to implement the functions performed by the first device in each method described in the embodiments of the present 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 the specific implementation. For example, execute steps 801 to 802 and 806 to 807 performed by the first device in the embodiment shown in Figure 8. Alternatively, execute steps 901 to 902b and steps 905 to 907 performed by the first device in the embodiment shown in Figure 9.

[0151] Based on the above embodiments, the present 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 running, the at least one processor performs the functions performed by the second device in each method described in the embodiments of the present application. For example, steps 802 to 805 and 807 performed by the second device in the embodiment shown in Figure 8 are executed. Alternatively, steps 902b, 903b to 904, and 906 to 907 performed by the second device in the embodiment shown in Figure 9 are executed. Alternatively, steps 1001 to 1003 performed by the second device in the embodiment shown in Figure 10 are executed.

[0152] Based on the above embodiments, the present application further provides a first device, comprising at least one processor and at least one memory, wherein the at least one memory stores program instructions, and when the first device is running, the at least one processor performs the functions performed by the first device in each method described in the embodiments of the present application. For example, steps 801 to 802 and 806 to 807 performed by the first device in the embodiment shown in Figure 8 are performed. Alternatively, steps 901 to 902b and steps 905 to 907 performed by the first device in the embodiment shown in Figure 9 are performed.

[0153] Based on the above embodiments, the present application further provides a guidance system, which may include the first device and the second device introduced in the above embodiments.

[0154] Based on the above embodiments, the present application also provides a program product, which includes: a program (also called code, or instructions), which, when executed, enables a device or computer to execute the methods described in the embodiments of the present application.

[0155] Based on the above embodiments, the present application also provides a readable storage medium, in which a program is stored. When the program is executed by a device or a computer, the device or the computer executes the methods described in the embodiments of the present application.

[0156] Based on the above embodiments, the present application further provides a chip, which is used to read the program stored in the memory to implement the various methods described in the embodiments of the present application.

[0157] Based on the above embodiments, the present application provides a chip system, which includes a processor for supporting a device to implement the various methods described in the embodiments of the present application. In one possible design, the chip system also includes a memory, which is used to store necessary programs and data. The chip system can be composed of chips, or it can include chips and other discrete devices. Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or program products. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects.

[0158] Obviously, those skilled in the art may make various modifications and variations to this application without departing from the scope of protection of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A guiding method, characterized in that: include: The second device receives a first message sent by the first device, where 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 protocols supported by the first device include the first protocol; 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 second device displays a guide interface, which is used to guide the user to perform m operations. Through the m operations, the first device and the second device perform multi-device collaboration in a multi-device collaboration manner corresponding to the second protocol, where m is an integer greater than 0.

2. The method according to claim 1, characterized in that The second device displays a guide interface, including: The guide interface is displayed using a sidebar, a notification bar, or a full-screen interface.

3. The method according to claim 1 or 2, characterized in that 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, including: The second device selects the second protocol from one or more collaborative protocols supported by both the first device and the second device.

4. The method according to claim 1 or 2, characterized in that: The second protocol is a collaborative protocol supported by the second device and not supported by the first device; The guidance interface is used to guide the user to perform m operations on the first device.

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

6. The method according to claim 1 or 2, characterized in that: The second protocol is a collaborative protocol supported by the first device and not supported by the second device; The guidance interface is used to guide the user to perform m operations on the second device.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The second device receives a second message sent by the first device using a second protocol, where the second message includes multi-device collaboration data sent by the first device to the second device.

8. The method according to any one of claims 1 to 7, 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 through a Bluetooth connection or a Wireless Fidelity Wi-Fi connection.

9. The method according to any one of claims 1 to 8, characterized in that Before the second device selects the second protocol based on the collaborative protocol supported by the first device and the collaborative protocol 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 detects that multi-device collaboration with the first device using the first protocol fails.

10. A guiding method, characterized in that: include: The second device receives a first message sent by the first device, where the first message is used to instruct the first device to initiate a DLNA screen projection; The second device displays a guidance interface, where the guidance interface is used to guide the user to turn on the hotspot on the first device; The second device accesses the hotspot of the first device, and performs DLNA screen projection of the first device and the second device based on the hotspot of the first device.

11. A second device, characterized in that: The device comprises at least one processor coupled to at least one memory, and the at least one processor is used to read the program stored in the at least one memory so that the second device executes the method according to any one of claims 1 to 9, or executes the method according to claim 10.

Images