Device management method and electronic equipment

Abstract

The present application provides a control method and electronic device, which is applied to electronic devices. The method includes: the first device and the second device start collaboration, when the input control state is on, and the position of the first operation corresponding to the first event is within the first area, the first device blocks the transmission of the first event; when the input control state is on, and the position of the first operation corresponding to the first event is within the second area, the first device releases the input control, and the first area and the second area are respectively part of the display area of ​​the first device. In this way, the user's local operations on the first device can be restricted, and the user's local operations on the first device can be prevented from affecting the collaboration between the second device and the first device, such as screen projection. At the same time, an escape area is reserved, and the first device can autonomously release the control state when the input control state is on. After the control state is released, the user of the first device can operate freely, which helps to improve the user experience.

Description

Technical Field

[0001] The present application relates to the field of terminals, and in particular to a device management method and electronic equipment. Background Art

[0002] With the development of electronic devices, users have increasingly higher requirements for them. For example, users often want cross-device operation or multi-screen collaboration. For example, screen projection reverse control can support users' reverse control operations on the projection screen, but users in this scenario have more needs. How to meet user needs and improve the user experience is an urgent problem to be solved. Summary of the Invention

[0003] The present application provides a device management method and an electronic device, which helps to improve user experience.

[0004] In a first aspect, a device management method is provided. The method is applied to a system including a first device and a second device, wherein an interface of the first device is projected onto the second device for display. The method includes: the first device receiving a first event, where the first event is triggered by a first operation, where the first operation is a local operation of the first device;

[0005] When the input control state is on and the location of the first operation is within the first area, the first device blocks the transmission of the first event, wherein the input control state being on indicates that the local operation of the first device is controlled;

[0006] or,

[0007] When the input control state is on and the location of the first operation is within the second area, the first device adjusts the input control state to off, wherein the input control state being off indicates that the local operation of the first device is not controlled, the first area and the second area are respectively part of the display area of ​​the first device, and the first area and the second area do not overlap.

[0008] It is understood that the device management method can be extended to a system including at least two devices, wherein a first device of the at least two devices is capable of receiving user operation information from a second device of the at least two devices and performing the action indicated by the user operation information. In other words, the device management method is not limited to screen projection scenarios.

[0009] In the technical solution of the present application, when the first device and the second device cooperate and turn on input control, when a local input event occurs on the first device, the processing of the first event can be determined according to the operation position corresponding to the first event, such as rejecting the first event or triggering an escape process. In this way, the user's local operations on the first device can be restricted to prevent the user's local operations on the first device from affecting the collaboration between the second device and the first device, such as screen projection. At the same time, an escape area is reserved, and the first device can autonomously release the control state when the input control state is turned on. After the control state is released, the user of the first device can operate freely, which helps to improve the user experience.

[0010] In combination with the first aspect, in some implementations of the first aspect, when the input control state is off, the first device allows the transmission of the first event.

[0011] In this manner, when the input control state is not enabled, there is no restriction on local input events of the first device, and the user of the first device can operate freely.

[0012] In combination with the first aspect, in some implementations of the first aspect, the first device receives a first message, where the first message is used to instruct to adjust the input control state to on.

[0013] That is to say, the first device can enable input control after receiving the first message. In other words, the first device enables input control after receiving the enable instruction. In this way, when the first device does not receive the enable instruction, the user of the first device can freely operate the first device, or the user of the first device can freely use the first device. When input control needs to be enabled, the first device receives the instruction and then enables input domain control, which can be enabled on demand and ensure the user of the first device's freedom of use as much as possible.

[0014] It should be understood that the manner in which the first device turns on the input control state is not limited thereto.

[0015] In combination with the first aspect, in certain implementations of the first aspect, when the input control state is on, the first device opens a full-screen transparent floating window, and the full-screen transparent floating window covers the display area of ​​the first device.

[0016] It should be understood that the first device is an electronic device, such as a tablet, a mobile phone, etc. The first device may also be a display screen, such as a car screen, or multiple display screens of the same electronic device, etc. The first device input control state is turned on, which means that the first device is controlled, and the full-screen transparent floating window covering the first device can be understood as the full-screen transparent floating window covering the controlled electronic device or the controlled display screen.

[0017] In combination with the first aspect, in some implementations of the first aspect, the full-screen transparent floating window includes the second area.

[0018] That is, the escape area on the first device is set on the full-screen transparent floating window.

[0019] In combination with the first aspect, in certain implementations of the first aspect, the first event corresponds to a screen-off processing, and when the input control state is off, the method further includes: the first device performs a screen-off processing.

[0020] In other words, the first event corresponds to the screen-off processing, and when the input control is not turned on, the first device performs the screen-off processing.

[0021] In combination with the first aspect, in certain implementations of the first aspect, the first device receives indication information from the second device, the indication information is used to instruct to turn off the screen, and the indication information is triggered by a local reverse control operation of the second device; the first device performs screen turning off processing, including: the first device performs screen turning off processing according to the indication information.

[0022] In other words, in this method, the first device performs the screen-off processing due to the reverse control operation of the second device, such as the second device reversely controls the first device to turn off the screen.

[0023] In combination with the first aspect, in some implementations of the first aspect, the first device receives a second event, where the second event is triggered by a reverse control operation from the second device; in response to the second event, the first device performs processing corresponding to the second event.

[0024] In combination with the first aspect, in some implementations of the first aspect, the first device receives a second event, where the second event is triggered by a reverse control operation from the second device; in response to the second event, the first device performs processing corresponding to the second event.

[0025] In other words, when the screen of the first device is turned off, the second device can still control the first device through screen projection.

[0026] In combination with the first aspect, in some implementations of the first aspect, when the processing corresponding to the second event calls a sensitive sensor of the first device, the first device blocks the call.

[0027] When the screen of the first device is turned off, the sensitive device refuses to call to protect the privacy of the user of the first device.

[0028] In a second aspect, a device management method is provided, which is applied to a system including a first device and a second device, wherein the interface of the first device is projected to the second device for display, and the method includes: the first device establishes a connection with the second device; the first device performs a screen-off operation; when a sensitive sensor of the first device is called, the first device blocks the call.

[0029] In other words, the device management method can be applied to a system including at least two devices, wherein a first device among the at least two devices is capable of receiving user operation information from a second device among the at least two devices and performing an action indicated by the user operation information.

[0030] In this method, when the first device establishes a connection with the second device and the screen is turned off, the sensitive sensor of the first device can reject the call when it is called to protect the privacy of the first device or the user of the first device, which helps to improve the user experience.

[0031] In combination with the second aspect, in some implementations of the second aspect, establishing a connection between the first device and the second device includes: the first device and the second device start collaboration, and the first device projects its own display interface to the second device.

[0032] In combination with the second aspect, in certain implementations of the second aspect, indication information is received, where the indication information is used to instruct the screen to be turned off; the first device performs the screen turning off operation, including: the first device performs the screen turning off operation according to the indication information.

[0033] Optionally, the indication information may be sent by the second device to the first device.

[0034] In a third aspect, a device is provided, which includes: a display unit for displaying a collaborative interface; a processing unit for receiving a first event, and determining whether to block the first event based on an input control status, wherein the input control status indicates whether a first operation of the first device is controlled, the first operation is an input operation on the first device, and the input control status includes on or off; when the input control status is on and the position of the first operation corresponding to the first event is within a first area, the processing unit blocks the first event; when the input control status is on and the position of the first operation corresponding to the first event is within a second area, the processing unit triggers an escape process, and the first area and the second area are respectively part of the display area of ​​the first device.

[0035] In combination with the third aspect, in some implementations of the third aspect, when the input control state is not enabled, the processing unit allows the first event.

[0036] In combination with the third aspect, in some implementations of the third aspect, the processing unit is further used to receive a first message, where the first message is used to instruct to adjust the input control state to on.

[0037] In combination with the third aspect, in certain implementations of the third aspect, when the input control status is on, the processing unit is used to open a full-screen transparent floating window, and the display unit is used to display the full-screen transparent floating window, and the full-screen transparent floating window covers the display area of ​​the first device.

[0038] In combination with the third aspect, in some implementations of the third aspect, the full-screen transparent floating window includes the second area.

[0039] In combination with the third aspect, in certain implementations of the third aspect, the first event corresponds to a screen-off processing, and when the input control state is off, the processing unit is used to perform the screen-off processing.

[0040] In other words, the first event corresponds to the screen-off processing, and when the input control is not turned on, the first device performs the screen-off processing.

[0041] In combination with the third aspect, in certain implementations of the third aspect, the processing unit receives indication information from a second device, wherein the indication information is used to instruct to turn off the screen, and the indication information is triggered by a local reverse control operation of the second device; the processing unit performs screen turning off processing according to the indication information.

[0042] In combination with the third aspect, in certain implementations of the third aspect, the processing unit is used to receive a second event, which is triggered by a reverse control operation from the second device; in response to the second event, the processing unit is used to perform processing corresponding to the second event.

[0043] In combination with the third aspect, in certain implementations of the third aspect, when the processing corresponding to the second event calls a sensitive sensor of the first device, the processing unit is further configured to block the call.

[0044] In a fourth aspect, a device is provided, which includes: a display unit for displaying an application interface; a processing unit for establishing a connection with a second device; the processing unit is also used to perform a screen-off operation, and when the sensitive sensor of the first device is called, the processing unit blocks the call.

[0045] In combination with the fourth aspect, in certain implementations of the fourth aspect, the processing unit is used to enable collaboration, and the processing unit is also used to project its own display interface to the second device.

[0046] In combination with the fourth aspect, in certain implementations of the fourth aspect, the processing unit is used to receive indication information, where the indication information is used to instruct to turn off the screen; the processing unit performs a screen turning off operation according to the indication information.

[0047] In a fifth aspect, a computer program product comprising instructions is provided. When the computer program product is run on an electronic device, the electronic device executes the management and control method described in the first aspect and / or the second aspect, or any achievable manner of the first aspect and / or any achievable manner of the second aspect.

[0048] In a sixth aspect, a computer-readable storage medium is provided, which may be non-volatile. The storage medium includes instructions that, when executed on an electronic device, cause the electronic device to execute the control method described in the first aspect and / or the second aspect, or any implementable manner of the first aspect and / or any implementable manner of the second aspect.

[0049] In the seventh aspect, a chip system is provided, comprising: a processor for calling and running a computer program from a memory, so that an electronic device equipped with the chip system executes the management and control method described in the above-mentioned first aspect and / or second aspect, or any achievable method of the first aspect and / or any achievable method of the second aspect.

[0050] In an eighth aspect, a device management method is provided. The method is applied to an electronic device and to a system including a first device and a second device, wherein an interface of the first device is projected to the second device for display, and the method includes:

[0051] The first device receives a first reverse control event, where the first reverse control event is triggered by a local reverse control operation of the second device;

[0052] In response to the first counter-control event, the first device performs a process corresponding to the first counter-control event;

[0053] The first device receives a first local event, where an operation corresponding to the first local event is within a first area;

[0054] In response to the first local event, the first device does not perform processing corresponding to the first local event;

[0055] The first device receives a second local event, and the operation corresponding to the second local event is within a second area, wherein the first area and the second area are respectively part of a display area of ​​the first device, and the first area and the second area do not overlap;

[0056] In response to the second local event, the first device performs processing corresponding to the second local event.

[0057] In other words, the second device can reverse control the screen projection of the first device. When the first device is operated in the first area, since the first area is input controlled, the first device does not perform corresponding processing. When the first device is operated in the second area, the control of the first device can be released.

[0058] It is understood that the device management method can be extended to a system including at least two devices, wherein a first device of the at least two devices is capable of receiving user operation information from a second device of the at least two devices and performing the action indicated by the user operation information. In other words, the device management method is not limited to screen projection scenarios.

[0059] In combination with the eighth aspect, in certain implementations of the eighth aspect, the processing corresponding to the second local event is to adjust the input control state of the first device to off, wherein the input control state being off indicates that the local operation of the first device is not controlled.

[0060] With reference to the eighth aspect, in some implementations of the eighth aspect, after the first device performs processing corresponding to the second local event in response to the second local event, the method further includes:

[0061] The first device receives a third local event, where an operation corresponding to the third local event is located at any position in the display area of ​​the first device;

[0062] In response to the third local event, the first device performs processing corresponding to the third local event.

[0063] That is to say, after releasing the control of the first device through operations in the second area, the first device can be operated at any position in the display area of ​​the first device, and the first device can perform corresponding processing.

[0064] With reference to the eighth aspect, in certain implementations of the eighth aspect, the first device receives a second reverse control event, where the second reverse control event is triggered by a local reverse control operation of the second device;

[0065] In response to the second counter-control event, the first device performs a screen-off operation;

[0066] The first device receives a third reverse control event, where the third reverse control event is triggered by a local reverse control operation of the second device;

[0067] In response to the third reverse control event, the first device starts a first application.

[0068] That is to say, after the screen of the first device is turned off by the second device, the first device can still be controlled by the second device to start the first application.

[0069] With reference to the eighth aspect, in some implementations of the eighth aspect, the first device receives a fourth local event, where the fourth local event instructs the first device to turn off the screen;

[0070] In response to the fourth local event, the first device performs a screen-off operation;

[0071] The first device receives a fourth reverse control event, where the fourth reverse control event is triggered by a local reverse control operation of the second device;

[0072] In response to the fourth reverse control event, the first device starts a first application.

[0073] That is to say, after the first device performs the screen-off operation locally, the second device can still perform reverse control operations on the first device to start the first application.

[0074] In combination with the eighth aspect, in certain implementations of the eighth aspect, when the first application calls the sensitive sensor of the second device, a prompt indicating call failure is displayed on the first device and / or the second device.

[0075] In a ninth aspect, a device management system is provided, which includes the first device and the second device in any achievable manner of the eighth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] Figure 1 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application is shown.

[0077] Figure 2 A software structure block diagram of an electronic device provided in an embodiment of the present application is shown.

[0078] Figure 3 An example diagram of an application scenario 200 provided in an embodiment of the present application is shown.

[0079] Figure 4 A schematic diagram of a control method provided in an embodiment of the present application is shown.

[0080] Figure 5 A set of GUIs provided by an embodiment of the present application is shown.

[0081] Figure 6 A schematic diagram of the interaction process between a vehicle computer and a tablet provided in an embodiment of the present application is shown.

[0082] Figure 7 Another set of GUIs provided by an embodiment of the present application is shown.

[0083] Figure 8 A schematic diagram of another interaction process between a vehicle computer and a tablet provided in an embodiment of the present application is shown.

[0084] Figure 9 Another set of GUIs provided by an embodiment of the present application is shown.

[0085] Figure 10 A schematic diagram of the interaction process between a vehicle computer, a mobile phone and a tablet provided in an embodiment of the present application is shown.

[0086] Figure 11 A schematic diagram of the interaction process between different vehicle-mounted screens provided in an embodiment of the present application is shown.

[0087] Figure 12 A schematic diagram of a control method provided in an embodiment of the present application is shown.

[0088] Figure 13 A schematic diagram of the interaction process between a vehicle computer and a tablet provided in an embodiment of the present application is shown.

[0089] Figure 14 A schematic block diagram of an example device provided in an embodiment of the present application is shown.

[0090] Figure 15 A schematic structural diagram of an electronic device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0091] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" or "multiple" refers to two or more than two.

[0092] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0093] The method provided in the embodiments of the present application can be applied to electronic devices such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), smart cars, etc. The embodiments of the present application do not impose any restrictions on the specific types of electronic devices.

[0094] For example, Figure 1 : The figure shows a schematic structural diagram of an electronic device 100. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0095] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

[0097] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

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

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

[0100] The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C bus lines. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, and the like via different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K via the I2C interface, enabling communication between the processor 110 and the touch sensor 180K via the I2C bus interface, thereby implementing the touch function of the electronic device 100.

[0101] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface, enabling the function of answering calls through a Bluetooth headset.

[0102] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

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

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

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

[0106] The USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100, or to transfer data between the electronic device 100 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as augmented reality devices.

[0107] It is understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is merely an illustrative illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0108] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 142, the charging management module 140 can also provide power to the electronic device via the power management module 141.

[0109] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

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

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

[0112] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0113] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0114] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0115] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0116] Electronic device 100 implements display functionality through a GPU, display screen 194, and an application processor. A GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

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

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

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

[0120] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0121] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0122] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. This allows electronic device 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0123] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU can enable intelligent cognitive applications in electronic device 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0124] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0125] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an App required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 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, a universal flash storage (UFS), etc.

[0126] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

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

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

[0129] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the user can place the receiver 170B close to the ear to hear the voice.

[0130] Microphone 170C, also known as "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 170C to input the sound signal into the microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the source of sound, realize directional recording function, etc.

[0131] The headphone jack 170D is used to connect a wired headphone and can be the USB interface 130 or a 3.5mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0132] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be located on display screen 194. There are many types of pressure sensors 180A, such as resistive, inductive, and capacitive. A capacitive pressure sensor can include at least two parallel plates made of conductive material. When force acts on pressure sensor 180A, the capacitance between the electrodes changes. Electronic device 100 determines the intensity of the pressure based on this change in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the touch intensity based on pressure sensor 180A. Electronic device 100 can also calculate the touch location based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch location but with different touch intensities can correspond to different operation instructions. For example, when a touch operation with an intensity less than a first pressure threshold is applied to a short message application icon, a command to view short messages is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to a short message application icon, a command to create a new short message is executed.

[0133] The gyroscope sensor 180B can be used to determine the motion posture of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 around three axes (i.e., x, y, and z axes) can be determined by the gyroscope sensor 180B. The gyroscope sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the electronic device 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking of the electronic device 100 through reverse movement to achieve anti-shake. The gyroscope sensor 180B can also be used for navigation and somatosensory game scenes.

[0134] The air pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates the altitude using the air pressure value measured by the air pressure sensor 180C to assist in positioning and navigation.

[0135] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip case. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover based on the magnetic sensor 180D. Based on the detected opening and closing status of the case or flip cover, features such as automatic unlocking of the flip cover can be configured.

[0136] Accelerometer 180E can detect the magnitude of acceleration of electronic device 100 in all directions (generally three axes). It can also detect the magnitude and direction of gravity when electronic device 100 is stationary. It can also be used to identify the electronic device's posture, enabling applications such as switching between landscape and portrait modes and pedometers.

[0137] The distance sensor 180F is used to measure distance. The electronic device 100 can measure distance using infrared or laser. In some embodiments, when shooting a scene, the electronic device 100 can use the distance sensor 180F to measure distance to achieve fast focusing.

[0138] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 can use the proximity light sensor 180G to detect that the user is holding the electronic device 100 close to the ear to talk, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode and pocket mode to automatically unlock and lock the screen.

[0139] Ambient light sensor 180L is used to sense ambient light brightness. Electronic device 100 can adaptively adjust the brightness of display screen 194 based on the perceived ambient light. Ambient light sensor 180L can also be used to automatically adjust white balance when taking photos. Ambient light sensor 180L can also work with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent accidental touches.

[0140] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0141] The temperature sensor 180J is used to detect temperature. In some embodiments, the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of the processor located near the temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to prevent the electronic device 100 from shutting down abnormally due to low temperature. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 boosts the output voltage of the battery 142 to prevent abnormal shutdown due to low temperature.

[0142] The touch sensor 180K is also called a "touch panel." The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180K is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the electronic device 100, in a location different from that of the display screen 194.

[0143] The bone conduction sensor 180M can obtain vibration signals. In some embodiments, the bone conduction sensor 180M can obtain vibration signals from the vibrating bones of the human body. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure pulse signals. In some embodiments, the bone conduction sensor 180M can also be set in headphones to form bone conduction headphones. The audio module 170 can parse out voice signals based on the vibration signals of the vibrating bones of the human body obtained by the bone conduction sensor 180M to implement voice functions. The application processor can parse heart rate information based on the blood pressure pulse signals obtained by the bone conduction sensor 180M to implement heart rate detection functions.

[0144] The buttons 190 include a power button, a volume button, and the like. The buttons 190 may be mechanical buttons or touch buttons. The electronic device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 100.

[0145] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0146] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0147] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to or disconnected from the electronic device 100 by inserting it into or removing it from the SIM card interface 195. The electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the electronic device 100 uses an embedded SIM (eSIM) card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0148] It should be understood that the phone card in the embodiments of the present application includes but is not limited to a SIM card, an eSIM card, a universal subscriber identity module (USIM), a universal integrated circuit card (UICC), and the like.

[0149] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present application, the Android system with a layered architecture is used as an example to illustrate the software structure of the electronic device 100.

[0150] Figure 2 This is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present application. The layered architecture divides the software 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 Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer. The application layer may include a series of application packages.

[0151] like Figure 2 As shown, the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

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

[0153] like Figure 2 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

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

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

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

[0157] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.).

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

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

[0160] Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

[0161] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0162] The application layer and application framework layer run in a virtual machine. The virtual machine executes 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.

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

[0164] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0165] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

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

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

[0168] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0169] It should be understood that the technical solutions in the embodiments of the present application can be used in Android, IOS, Hongmeng and other systems.

[0170] Users can use multiple apps on electronic devices to perform various functions. For example, users can use map apps on electronic devices to perform positioning or navigation functions, and users can also use audio and video apps on electronic devices to listen to audio and video functions.

[0171] The App can run in the foreground of the electronic device or in the background of the electronic device. When the App runs in the foreground of the electronic device, the electronic device 100 can display the user interface of the App on the display screen. The user can interact with the App through the controls in the user interface of the App. The App runs in the electronic device, but it does not fall into the above-mentioned situation of running in the foreground, that is, the App runs in the background of the electronic device. The situation where the App runs in the background of the electronic device may include the existence of the App process in the electronic device, but the user interface of the App is not displayed on the display screen. Since the user interface of the App running in the background is not displayed on the display screen, the user usually cannot directly interact with the App running in the background. The above-mentioned background can also be called "non-foreground".

[0172] There may be one or more apps running in the foreground of the electronic device, and one or more apps running in the background of the electronic device. While one or more apps are running in the foreground of the electronic device, one or more apps may also be running in the background of the electronic device.

[0173] With the development of electronic devices, users have higher and higher requirements for electronic devices. For example, after user A projects an electronic device A onto another electronic device B, he can control the projected electronic device A by operating on electronic device B. However, the operations of another user B on the projected electronic device A cannot be restricted, which is not a good user experience for user A. The present application proposes a device control method that can limit the operations of other users on the projected or coordinated electronic device to meet the control needs of the controlling user (such as user A mentioned above), thereby helping to improve the user experience.

[0174] Figure 3 This is an example diagram of an application scenario 200 provided by an embodiment of the present application. Figure 3 As shown, the application scenario 200 includes a vehicle 210 and a driver 220. The driver 220 is in the driving position of the vehicle 210. The vehicle 210 is equipped with an onboard device 230, which has a display screen. It should be understood that the onboard device 230 is a Figure 1 and Figure 2 An example of an electronic device 100, the hardware structure and software structure of which can refer to the above Figure 1 and Figure 2 The description of the electronic device 100 is omitted here. Optionally, the vehicle 210 may further include a rear-seat tablet computer. Optionally, the tablet computer may be a rear-mounted device.

[0175] The embodiment of the present application does not limit the specific form of the vehicle-mounted device 230, as long as it has a display screen.

[0176] Optionally, in some embodiments, the in-vehicle device 230 may be an in-vehicle infotainment product installed in the vehicle 210 .

[0177] Optionally, in some embodiments, the in-vehicle device 230 may also be a device connected to an in-vehicle infotainment product installed in the vehicle 210 , such as a mobile phone.

[0178] It should be noted that Figure 3 The scenes shown are merely examples and should not be construed as limiting the present application. For example, the scenes may also include more electronic devices or people.

[0179] The solution of this application is described in detail below with reference to the drawings.

[0180] Figure 4 A device management method provided by an embodiment of the present application is shown, which can be applied to Figure 3 In the scenario, for example, a first device (e.g., a rear-seat tablet computer) and a second device (e.g., an in-vehicle device) may be included in the vehicle cabin. The method may include the following steps:

[0181] S401: A first device receives a first event.

[0182] Here, the event can be understood as input information received by the first device.

[0183] Optionally, an input event (InputEvent) may include a motion event (MotionEvent) and a key event (KeyEvent). For example, an input event may be a sensor input event (SensorInputEvent), a headphone input event (HookInputEvent), a power button input event (OnInputEvent), a touch screen input event (TouchScreenInputEvent, hereinafter also referred to as a touch event), a key input event (KeyInputEvent), or a mouse motion input event (HoverInputEvent).

[0184] Among them, touch screen input events include the following basic events: finger pressing on the screen (ACTION_DOWN), finger moving on the screen (ACTION_MOVE), and finger leaving the screen (ACTION_UP). Each user interaction will generate an event sequence, which starts with ACTION_DOWN, has 0 or n ACTION_MOVE events in the middle, and ends with ACTION_UP. Event sequences can often form complex events, such as click events, double-click events, gesture events, etc. The input events in the embodiments of the present application can be basic events or complex events composed of basic events, which are not limited in the embodiments of the present application.

[0185] The first event may be a local input event. The so-called local input event may be understood as an event corresponding to the user's operation on the first device (that is, the local operation of the first device). For example, if the user clicks a certain position on the screen of the first device, then "a certain position being clicked" is a local input event. In other words, for the user, clicking the screen is a user operation (that is, an input operation); for the first device, the event triggered by "click" is an input event. In other words, the event is triggered by the user's action (or operation). It can also be understood that the first event is the above-mentioned input event that occurs locally on the first device.

[0186] The events in this application also include reverse control events, which can be understood as events triggered by controlling a device through another device. For example, when a first device is controlled by a second device, such as through screen projection control, an event on the first device triggered by an operation on the second device is a reverse control event.

[0187] S402: The first device determines whether to block the first event according to the state of input control.

[0188] The state of the input control is used to characterize whether the input operation of the first device is controlled, wherein the input operation of the first device can be understood as the input operation of the user on the first device. In other words, the state of the input control is used to characterize whether the input event triggered by the user's input operation is controlled. For example, the input operation of the first device can be touch input, key input, voice input or gesture input, etc. In other words, corresponding to the description of the input event in S401, the user's operation on the first device can be key, touch, air input, or input operation of the device by a peripheral connected to it, such as input through a keyboard. The embodiments of the present application are not limited to this.

[0189] The following describes this solution using touch input as an example of input operation.

[0190] For example, the touch operation of the first device can be controlled by the second device, which can be a device that cooperates with the first device and has input control enabled with the first device. In other words, when the touch operation of the first device is controlled, the touch operation on the first device is restricted.

[0191] It is understandable that the status of input control includes enabled or disabled.

[0192] In one example, a user may enable input control on the second device. This input control can be understood as managing touch operations on the first device, such as limiting operations on the first device.

[0193] In one possible implementation, the user can enable input control through a physical button on the second device. The physical button can be installed on the second device or elsewhere in the cabin, such as on the steering wheel.

[0194] In another possible implementation, the user can enable input control through a virtual function button on the second device. For example, the user can enable input control through the input control function button on the second device. The input control function button can be set in the homepage display interface of the second device, or in the second device control page, or it can be hidden in the menu function. This application does not limit this.

[0195] In another example, a user turns on input control on a first device. This input control can be understood as managing touch operations on the first device, for example, limiting operations on the first device.

[0196] In one possible implementation, the user may enable input control through a physical button on the first device. The physical button may be mounted on the first device, for example, the physical button may be a volume button on a tablet computer.

[0197] In another possible implementation, the user can enable input control through a virtual function button on the first device. For example, the user can enable input control through the input control function button on the screen of the first device. The input control function button can be set on the homepage of the first device display interface, or it can be hidden in a menu function, such as a drop-down menu. This application is not limited to this.

[0198] The embodiment of the present application does not limit the method for enabling input control.

[0199] It should be understood that the embodiments of the present application do not limit the manner in which the first device and the second device enable collaboration. For example, collaboration can be enabled via a wired connection or wirelessly. After collaboration is enabled between the first device and the second device, they can access each other. For example, the first device can project its own interface to the second device.

[0200] For example, screen projection can be projecting the interface of the first device to the second device through a wired connection.

[0201] Alternatively, the interface of the first device can be projected onto the second device through a wireless connection. For example, the first device can be projected onto the second device through a projection button, such as a projection button in an APP, or a projection button in a function menu. Or the first device can be projected onto the second device through a physical button of the projection function. Optionally, the physical button for projection can be mounted on the first device and / or the second device. Furthermore, the first device can be projected onto the second device through a virtual key of the projection function in the function menu. It should be understood that the embodiment of the present application does not limit the method of projecting the first device onto the second device.

[0202] After the first device has projected its interface onto the second device, you can control the first device by operating on the second device. After the projection is complete, you can enable input control.

[0203] Blocking the first event can be understood as preventing the operation corresponding to the first event from being executed on the first device. For example, the first device may reject the operation corresponding to the first event, or the first device may not respond to the operation corresponding to the first event. It should be understood that the embodiments of this application do not limit the term "blocking the first event," and alternative statements that can achieve the above effect are within the scope of protection of this application.

[0204] Exemplarily, the first device determines whether to block the first event according to the input control state, which may be in the following situations:

[0205] S4021: When the input control state is on and the operation position corresponding to the first event is within the first area, the first device blocks the first event.

[0206] S4022: When the input control state is on and the operation position corresponding to the first event is within the second area, the first device triggers the escape process.

[0207] S4023: When the input control status is off (that is, input control is not turned on), the user's operations on the first device can be unrestricted. In other words, the user's operations on the first device can be implemented normally. It should be noted that, under the premise of turning on collaboration, the user can still control the first device through operations on the second device.

[0208] Exemplarily, the first area and the second area may be part of the screen area of ​​the first device respectively. For example, the first area and the second area do not overlap. Optionally, the sum of the first area and the second area is the screen range of the first device. The above "range" may refer to a two-dimensional range. For example, taking the screen of the first device as a reference, one side of the screen of the first device as the horizontal axis, and the other side as the vertical axis, the second area may be the range within the closed figure obtained by connecting four points with coordinates (x1, y1), (x1, y2), (x2, y1), and (x2, y2), then the first area is the range of the screen of the first device excluding the second area. The above is an example of a rectangle as the second area. It should be understood that the embodiment of the present application does not limit the shape and size of the second area. For example, the shape of the second area may be a circle, triangle, square, ellipse or irregular shape, etc. Since the first area is adjacent to the second area and together constitutes the range of the screen of the first device, the shape and size of the first area are also not limited.

[0209] In other words, when the first device determines that the state of input control is on, it can further determine whether to block the first event based on the position of the operation corresponding to the first event.

[0210] When the operation corresponding to the first event falls within the first area, the first device blocks the first event, or in other words, the local input event of the first device is limited.

[0211] When the operation corresponding to the first event falls within the second area, the first device triggers the escape process. In other words, the first device releases input control, or in other words, the first device adjusts the input control state from on to off.

[0212] In one possible approach, the first device itself can complete the escape process. Optionally, the escape process is triggered when the user clicks once within the second area. Optionally, when the operation corresponding to the first event falls within the second area, a pop-up confirmation interface can be triggered to confirm the triggering of the escape process. For example, for an arithmetic problem, the user triggers the escape process after entering or clicking the correct answer. It should be understood that the arithmetic problem is only an example of a confirmation interface, and the embodiments of the present application are not limited to this. For example, it can also be a picture verification interface, an option confirmation interface, etc.

[0213] In another possible approach, the second device may execute the escape process after allowing the escape process. For example, the first device may request the second device to release input control, and after the second device agrees, the first device may release input control.

[0214] It should be understood that the above method is only an example of the first device triggering the escape process, and the embodiments of the present application do not limit this. All methods that can trigger the escape process should be within the scope of protection of this application.

[0215] In one possible implementation, when input control is enabled, the first device may determine how to handle the first event based on whether the first event is on a whitelist of events that the first device may allow.

[0216] When the first event belongs to the whitelist, the first device allows the first event to pass. When the first event does not belong to the whitelist, the first device blocks the first event.

[0217] Optionally, the whitelist may be predefined. Optionally, the whitelist may also be indicated, for example, the second device sends information to the first device, the information being used to indicate the whitelist. This application does not limit the method for determining the whitelist.

[0218] Optionally, the state of the input control can be represented by a flag. For example, the first device can set a flag that is used to represent the state of the input control, that is, the flag is used to represent whether the input control state is on or off, or in other words, the flag is used to represent whether the input control is enabled. Specifically, the flag can be set to true or false. When the flag is true, it indicates that the input control state is enabled or the input control is enabled, and when the flag is false, it indicates that the input control state is disabled or the input control is not enabled. It should be understood that the setting of the above flag is only an example and not a limitation. For example, the flag can also be set to 0 or 1. When the flag is 1, it indicates that the input control state is enabled or the input control is enabled, and when the flag is 0, it indicates that the input control state is disabled or the input control is not enabled. It should also be understood that the correspondence between the specific value of the flag and the meaning represented by the value is not limited in the embodiments of the present application. It should also be understood that the correspondence between the specific value of the flag and the meaning represented by the value can be predefined or configured, and the embodiments of the present application do not limit this.

[0219] In this method, after the first device and the second device start collaboration and input control, the operation location of the local event of the first device is judged to further determine whether to restrict the operation or release the input control. This can restrict other users' local operations on the first device and improve the user experience in the collaborative scenario of the first device and the second device.

[0220] The above describes a method for limiting the local operation of the first device. The following describes implementation of this method in detail with reference to several possible scenarios.

[0221] In one possible implementation, the above method is applicable to vehicle-mounted devices and tablets.

[0222] Figure 51 shows a set of graphical user interfaces (GUIs) provided by an embodiment of the present application, including an in-vehicle display screen 510 and a flat screen 520 .

[0223] One possible approach is to control the touch screen 520 via the vehicle-mounted display screen 510 (also referred to herein as the vehicle-mounted screen). Figure 4 As an example of the second device, the flat screen 520 is Figure 4 An example of a first device in .

[0224] It is understandable that the vehicle display screen 510 and the flat screen 520 are enabled to cooperate and then enable input control. Specifically, the method of enabling cooperation and enabling input control between the vehicle display screen 510 and the flat screen 520 can refer to the description of S402 and will not be repeated here.

[0225] After collaboration is turned on, the flat screen 520 can be controlled through the vehicle display screen 510. For example, video A is playing on the flat screen 520, and the screen of video A is 5201 in the figure. The screen 5201 can be projected onto the vehicle display screen 510, such as the screen 5101 in the vehicle display screen 510, and the content displayed on the screen 5101 is exactly the same as that displayed on the screen 5201. The screen includes a video progress bar 5106, and the user can control the progress of the video A played on the flat screen 520 by dragging the video progress bar 5106 in the vehicle display screen 510, that is, the user can realize reverse control of the projection of the flat screen 520 on the vehicle display screen 510.

[0226] It should be understood that after screen casting, the contents of the screens on the two electronic devices are exactly the same, but the contents on the screens of the two electronic devices may not necessarily be the same. For example, if the screen 5201 described above is cast to the in-vehicle display screen 510, the screen 5101 on the in-vehicle display screen 510 is the same as the screen 5201 on the tablet, but the content displayed on the in-vehicle display screen 510 may be different from that on the tablet screen 520.

[0227] After input control is turned on, operations corresponding to local events on the flat-panel screen 520 are restricted.

[0228] For example, on the right side of the flat screen 520, the cover legend (5202) of video B, the cover legend (5203) of video C, and the cover legend (5204) of video D are arranged in sequence, which can be used by the user to select or switch videos.

[0229] The flat screen 520 may further include an escape area 5205, which is an example of the first area in S402. All portions of the flat screen 520 other than the escape area 5205 are restricted areas (also known as non-escape areas), which are examples of the second area in S402.

[0230] For example, when a user clicks on the cover legend (5202) of video B on tablet screen 520, intending to switch the currently playing video A to video B, the tablet determines the user's operation location, i.e., the click location, to determine subsequent processing. For example, if the tablet determines that the click location is in a non-escape zone, the tablet blocks the "video switching event." In other words, the user's video switching operation on tablet screen 520 is limited.

[0231] In another example, when a user's operation on tablet screen 520 falls within the escape zone, for example, if the user clicks location M, and the tablet determines that location M is within the escape zone, the tablet initiates the escape process and releases input control. After the input control is released, the user can freely operate on tablet screen 520.

[0232] This solution opens up new use cases for screen projection control. For example, in a cockpit scenario, when a child is watching a video on a tablet in the back seat, the screen can be projected onto the front display. Parents in the front seat can then use the screen projection to control the tablet and select the content the child is watching. They can also restrict the child's local tablet operations to prevent accidental touches. Furthermore, if the tablet user switches to an adult, they can self-escape and remove input control.

[0233] Specifically, a detailed interaction process is given below.

[0234] Figure 6 The diagram shows an interaction process between a vehicle computer and a tablet provided in an embodiment of the present application.

[0235] Optionally, the car computer can include a reverse control module, which can also be used to receive the projection screen. The tablet can include a reverse control receiving module, an input subsystem, a screen management module, and a privacy sensor service module.

[0236] Specifically, the following steps may be included:

[0237] S601: The vehicle computer and the tablet are connected.

[0238] For example, the car computer can start collaboration with the tablet. For example, the tablet will project its own interface onto the display screen of the car computer. Specifically, the method of starting collaboration can refer to the description of S402 and will not be repeated here.

[0239] S602: The vehicle computer operation user turns on input control.

[0240] It should be understood that the method of enabling input control by the vehicle computer is only an example of a method of enabling input control and is not intended to be limiting. Specifically, the method of enabling input control can refer to the description in S402 and will not be repeated here.

[0241] S603: The reverse control module of the vehicle computer sends an input control message to the reverse control receiving module of the tablet computer. Correspondingly, the reverse control receiving module of the tablet computer receives the input control message.

[0242] S604: The reverse control receiving module of the tablet displays a full-screen transparent floating window to the foreground.

[0243] The full-screen transparent floating window includes an escape area.

[0244] S605: The vehicle computer user performs a reverse control operation.

[0245] For example, a vehicle user can perform operations on the vehicle's display to control the tablet. This reverse control operation can be understood as an example of an input operation. For details about the reverse control operation, refer to the description of the input operation in S402. Alternatively, the reverse control operation can be understood as a non-native operation of the tablet. For example, the reverse control operation can be controlling the tablet's display through the vehicle's display. For example, a vehicle user can drag the video progress bar on the vehicle's display to control the video progress on the tablet's display.

[0246] S606: The reverse control module of the vehicle computer sends a reverse control event to the reverse control receiving module of the tablet computer. Correspondingly, the reverse control receiving module of the tablet computer receives the reverse control event.

[0247] The reverse control event is an event corresponding to the reverse control operation. In other words, the reverse control event is an event triggered by the reverse control operation. The reverse control event can be understood as an example of an input event. For details, please refer to the description of the input event in S401.

[0248] S607: The reverse control receiving module of the tablet sends the reverse control event to the input subsystem. Correspondingly, the input subsystem receives the reverse control event.

[0249] S608: The tablet receives a first operation from the tablet operation user.

[0250] It should be understood that a tablet user can click any position on the tablet screen. For example, a tablet user can click on an App.

[0251] S609: The input subsystem of the tablet determines a transparent floating window currently used to manage input according to the touch position corresponding to the first operation.

[0252] It should be understood that the transparent floating window can be displayed on the screen of a tablet.

[0253] In other words, the input subsystem of the tablet further determines whether the transparent floating window exists according to the touch position of the first operation. Generally, when the input control state is turned on, the transparent floating window is displayed on the screen of the tablet.

[0254] Optionally, before the input subsystem of the tablet determines the transparent floating window, the input control state of the tablet screen can also be determined according to the flag bit. Specifically, please refer to the description of the flag bit in S402, which will not be repeated here.

[0255] S610: The input subsystem of the tablet processes the first event according to the source of the first event.

[0256] The first event is an event corresponding to the first operation in S608. In other words, the first event is an event triggered by the first operation. The first event is an example of the input event in S401. For details, please refer to the relevant description in S401 and will not be repeated here.

[0257] Optionally, if the input event is a reverse control event, that is, the input event comes from the vehicle computer, the input subsystem does not process it and continues to distribute it in the system.

[0258] Optionally, if the input event is a local event, that is, the input event comes from the tablet, the input subsystem redirects the first event back to the floating window and blocks the event delivery process outside the escape area.

[0259] Redirecting back to the floating window can be understood as follows: before input control is enabled, the distribution path of local input events is fixed. After input control is enabled, the distribution path is modified. Redirection is to distribute the input events to the floating window. It should be understood that the explanation of redirection below can be referred to here and will not be repeated here.

[0260] In this process, the tablet can determine how to handle the event corresponding to the user's operation based on the location of the user's operation. It can limit the tablet user's operations under the premise that the car computer and the tablet work together and input control is turned on. At the same time, it reserves a way for the tablet user to self-help cancel input control, effectively improving the user experience.

[0261] Figure 7 1 shows another set of graphical user interfaces (GUIs) provided by an embodiment of the present application, including an in-vehicle display screen 710 and a flat-panel screen 720 .

[0262] Another possible way is to control the vehicle display screen 710 by touch via the flat screen 720. Figure 4 An example of the first device in FIG. 7 is a flat screen 720. Figure 4 An example of a second device in .

[0263] It is understandable that the vehicle display screen 710 and the flat screen 720 are enabled to start input control after the collaboration is enabled. Specifically, the method of enabling the collaboration and input control of the vehicle display screen 710 and the flat screen 720 can refer to the description of S402 and will not be repeated here.

[0264] After the collaboration is turned on, the vehicle display screen 710 can be controlled through the tablet screen 720. For example, video A is playing on the vehicle display screen 710, and the screen of video A is 7101 in the figure. The screen 7101 can be projected onto the tablet screen 720, such as the screen 7201 on the tablet screen 720, and the content displayed on the screen 7101 is exactly the same. The screen includes a video progress bar 7206, and the user can control the progress of the video A played on the vehicle display screen 710 by dragging the video progress bar 7206 on the tablet screen 720, that is, the user can reversely control the projection of the vehicle display screen 710 on the tablet.

[0265] After input control is turned on, operations corresponding to local events on the vehicle display screen 710 are restricted.

[0266] For example, on the right side of the vehicle display screen 710, the cover legend (7102) of video B, the cover legend (7103) of video C, and the cover legend (7104) of video D are arranged in sequence, which can be used by users to select or switch videos.

[0267] The vehicle display screen 710 also includes an escape area 7105, which is an example of the first area in S402. The portion of the vehicle display screen 710 other than the escape area 7105 is a restricted area (also called a non-escape area), which is an example of the second area in S402.

[0268] For example, when a user clicks on the cover legend (7202) of video B on the in-vehicle display screen 720, intending to switch the currently playing video A to video B, the in-vehicle computer determines the user's operation location, i.e., the click location, to determine subsequent processing. For example, if the in-vehicle computer determines that the click location is in a non-escape zone, the in-vehicle computer blocks the "video switching event." In other words, the user's video switching operation on the in-vehicle display screen 720 is restricted.

[0269] In another example, when the user's operation on the vehicle display screen 720 falls within the escape zone, the tablet determines that the location is within the escape zone, and the vehicle computer initiates the escape process and releases the input control. After the input control is released, the user can freely operate on the vehicle display screen 720.

[0270] Specifically, a detailed interaction process is given below.

[0271] Figure 8 The diagram shows an interaction process between a vehicle computer and a tablet provided in an embodiment of the present application.

[0272] Optionally, the tablet may include a reverse control module, which can also be used to receive the projection screen. The vehicle computer may include a reverse control receiving module, an input subsystem, a screen management module, and a privacy sensor service module.

[0273] Specifically, the following steps may be included:

[0274] S801: The vehicle computer and the tablet are connected.

[0275] For example, the car computer can start collaboration with the tablet. For example, the tablet will project its own interface onto the display screen of the car computer. Specifically, the method of starting collaboration can refer to the description of S402 and will not be repeated here.

[0276] S802: The tablet user turns on input control.

[0277] It should be understood that the method of enabling input control by the tablet user is only an example of a method of enabling input control and is not intended to be limiting. Specifically, the method of enabling input control can refer to the description in S402 and will not be repeated here.

[0278] S803: The reverse control module of the tablet sends an input control message to the reverse control receiving module of the vehicle computer. Correspondingly, the reverse control receiving module of the vehicle computer receives the input control message.

[0279] S804: The vehicle computer's reverse control receiving module displays a full-screen transparent floating window to the foreground.

[0280] The full-screen transparent floating window includes an escape area.

[0281] S805: The tablet user performs a counter-control operation.

[0282] For example, a tablet user can perform operations to control the in-vehicle display screen. A reverse control operation can be understood as an example of an input operation. Specifically, the reverse control operation can refer to the description of the input operation in S402. Alternatively, a reverse control operation can be understood as a non-local operation. For example, the reverse control operation can be controlling the display of the in-vehicle device through the tablet. For example, a tablet user can drag the progress bar of a video on the tablet screen to control the progress of the video on the in-vehicle device's display screen.

[0283] S806: The reverse control module of the tablet sends a reverse control event to the reverse control receiving module of the vehicle computer. Correspondingly, the reverse control receiving module of the vehicle computer receives the reverse control event.

[0284] The reverse control event is an event corresponding to the reverse control operation. In other words, the reverse control event is an event triggered by the reverse control operation. The reverse control event can be understood as an example of an input event. For details, please refer to the description of the input event in S401.

[0285] S807: The reverse control receiving module of the vehicle computer sends the reverse control event to the input subsystem. Correspondingly, the input subsystem receives the reverse control event.

[0286] S808: The vehicle operation user touches the vehicle display to complete the first operation.

[0287] It should be understood that the vehicle operating user can click any position on the vehicle display screen. For example, the vehicle operating user can click on an App.

[0288] S809: The input subsystem of the vehicle computer determines a transparent floating window currently used for controlling input according to the touch position corresponding to the first operation.

[0289] Optionally, before the input subsystem of the vehicle computer determines the transparent floating window, the input control state of the vehicle computer screen can also be determined according to the flag bit. Specifically, please refer to the description of the flag bit in S402, which will not be repeated here.

[0290] S810: The input subsystem of the vehicle computer processes the first event according to the source of the first event.

[0291] The first event is an event corresponding to the first operation in S808. In other words, the first event is an event triggered by the first operation. The first event is an example of the input event in S401. For details, please refer to the relevant description in S401 and will not be repeated here.

[0292] Optionally, if the first event is a counter-control event, that is, the first event comes from the tablet, the input subsystem does not process it and continues to distribute it in the system.

[0293] Optionally, if the first event is a local event, that is, the first event comes from the vehicle computer, the input subsystem redirects the first event back to the floating window and blocks the event transmission process outside the escape area.

[0294] In this process, the car computer can determine how to handle the event corresponding to the user's operation based on the location of the user's operation. It can limit the car computer user's operation under the premise that the tablet and the car computer work together and input control is turned on. At the same time, it reserves a way for the car computer user to self-help cancel input control, effectively improving the user experience.

[0295] In another possible embodiment, a third device may be present in the aforementioned system in which the first device and the second device communicate. For example, the third device may be a mobile phone. It should be understood that the following description uses a mobile phone as an example, but the present application is not limited to this type of third device. For example, the third device may also be a tablet or a laptop.

[0296] Figure 9 Another set of graphical user interfaces (GUIs) provided by an embodiment of the present application is shown, including a vehicle display screen 910 , a tablet screen 920 , and a mobile phone screen 930 .

[0297] The mobile phone can share its own interface with the car computer, and the car computer can then project its own interface to the tablet, and the tablet can be used to control the input of the car display. For example, the car display 910 can be controlled by touch via the tablet screen 920. Figure 4 As an example of the first device, the flat screen 920 is Figure 4 An example of a second device in .

[0298] It should be understood that Figure 9 The solution shown uses mobile phone sharing and car-mounted screen projection to a tablet as an example for illustration, but the present application is not limited to this. For example, a mobile phone can also share its own interface with a tablet, and the tablet can then project its own interface to the car-mounted computer, allowing the car-mounted computer to control the tablet's input. This will not be repeated here.

[0299] It is understandable that input control is enabled after the vehicle display screen 910 and the flat screen 920 are enabled to collaborate. Specifically, the method of enabling collaboration and input control for the vehicle display screen 910 and the flat screen 920 can refer to the description of S402 and will not be repeated here. The interface sharing between the mobile phone and the vehicle computer can also be achieved by enabling collaboration. Specifically, the description of the method of enabling collaboration in S402 also applies to the collaboration between the mobile phone and the vehicle computer and will not be repeated here.

[0300] After the collaboration is turned on, the tablet screen 920 can be controlled through the vehicle display screen 910. For example, video A is playing on the vehicle display screen 910, and the screen of video A is 9101 in the figure. The screen 9101 can be projected onto the tablet screen 920, such as the screen 9201 on the tablet screen 920, and the content displayed on the screen 9201 is exactly the same as the content displayed on the screen 9101 and the content displayed on the screen 9301. The screen includes a video progress bar 9206, and the user can control the progress of the video A played on the vehicle display screen 910 by dragging the video progress bar 9206 on the tablet screen 920, that is, the user can reversely control the projection of the vehicle display screen 910 on the tablet.

[0301] After input control is turned on, operations corresponding to local events on the vehicle display screen 910 are restricted.

[0302] For example, on the right side of the vehicle display screen 910, the cover legend (9102) of video B, the cover legend (9103) of video C, and the cover legend (9104) of video D are arranged in sequence, which can be used by users to select or switch videos.

[0303] The vehicle display screen 910 also includes an escape area 9105, which is an example of the first area in S402. The portion of the vehicle display screen 910 other than the escape area 9107 is a restricted area (also called a non-escape area), which is an example of the second area in S402.

[0304] For example, when a user clicks on the cover legend (9202) of video B on the in-vehicle display screen 910, intending to switch the currently playing video A to video B, the in-vehicle computer determines the user's operation location, i.e., the click location, to determine subsequent processing. For example, if the in-vehicle computer determines that the click location is in a non-escape zone, the in-vehicle computer blocks the "video switching event." In other words, the user's video switching operation on the in-vehicle display screen 920 is restricted.

[0305] In another example, if a user's operation on the in-vehicle display screen 910 falls within the escape zone, for example, if the user clicks on location O and the tablet determines that location O is within the escape zone, the in-vehicle computer initiates the escape process and removes the input control restrictions. After the input control restrictions are removed, the user can freely operate on the in-vehicle display screen 910.

[0306] Figure 10 The diagram shows an interaction process among a vehicle computer, a mobile phone, and a tablet provided in an embodiment of the present application.

[0307] Optionally, the tablet may include a reverse control module, which can also be used to receive the projection screen. The vehicle computer may include a reverse control receiving module, an input subsystem, a screen management module, and a privacy sensor service module.

[0308] Specifically, the following steps may be included:

[0309] S1001: Establish a connection between the car computer, mobile phone and tablet.

[0310] For example, the car computer can start collaboration with a mobile phone and a tablet. For example, the mobile phone projects its own interface to the display screen of the car computer. Alternatively, the mobile phone projects its own interface to the tablet. Specifically, the method of starting collaboration can refer to the description of S402 and will not be repeated here. It should be understood that after the mobile phone projects its own interface to the tablet, the tablet can project the projection interface to the car screen. The embodiment of the present application does not limit the screen sharing method of the three-party devices, and the method that can realize the screen sharing of the three-party devices should be within the protection scope of this application.

[0311] S1002: The tablet user turns on input control.

[0312] It should be understood that the method of enabling input control by the tablet user is only an example of a method of enabling input control and is not intended to be limiting. Specifically, the method of enabling input control can refer to the description in S402 and will not be repeated here.

[0313] S1003: The reverse control module of the tablet sends an input control message to the reverse control receiving module of the vehicle computer. Correspondingly, the reverse control receiving module of the vehicle computer receives the input control message.

[0314] S1004: The vehicle computer's reverse control receiving module displays a full-screen transparent floating window to the foreground.

[0315] The full-screen transparent floating window includes an escape area.

[0316] S1005: The tablet user performs a counter-control operation.

[0317] For example, the tablet user can perform operations to control the vehicle-mounted display screen. For details, please refer to the description of S805 and will not be repeated here.

[0318] S1006: The reverse control module of the tablet sends a reverse control event to the reverse control receiving module of the vehicle computer. Correspondingly, the reverse control receiving module of the vehicle computer receives the reverse control event.

[0319] The reverse control event is an event corresponding to the reverse control operation. Specific details can be referred to the description of S806 and will not be repeated here.

[0320] S1007: The reverse control receiving module of the vehicle computer sends the reverse control event to the input subsystem. Correspondingly, the input subsystem receives the reverse control event.

[0321] S1008: The vehicle operation user touches the vehicle display screen to complete the first operation.

[0322] It should be understood that the vehicle operating user can click any position on the vehicle display screen. For example, the vehicle operating user can click on an App.

[0323] S1009: The input subsystem of the vehicle computer determines a transparent floating window currently used for controlling input according to the touch position corresponding to the first operation.

[0324] Optionally, before the input subsystem of the vehicle computer determines the transparent floating window, the input control state of the vehicle computer screen can also be determined according to the flag bit. Specifically, please refer to the description of the flag bit in S402, which will not be repeated here.

[0325] S1010: The input subsystem of the vehicle computer processes the first event according to the source of the first event.

[0326] The first event is an event corresponding to the first operation in S10010. In other words, the first event is an event triggered by the first operation. The first event is an example of the input event in S401. For details, please refer to the relevant description in S401 and will not be repeated here.

[0327] Optionally, if the first event is a counter-control event, that is, the first event comes from the tablet, the input subsystem does not process it and continues to distribute it in the system.

[0328] Optionally, if the first event is a local event, that is, the first event comes from the vehicle computer, the input subsystem redirects the first event back to the floating window and blocks the event transmission process outside the escape area.

[0329] It should be understood that the above method is based on the example of a mobile phone screen projection and a tablet computer managing the touch operations of the vehicle computer, and this application is not limited to this. For example, the vehicle computer can also manage the touch operations of the tablet computer. Alternatively, the vehicle computer can manage the touch operations of the mobile phone. Alternatively, the mobile phone can manage the touch operations of the tablet computer. Alternatively, the mobile phone can manage the touch operations of the vehicle display screen, and so on. I will not list them one by one here.

[0330] In this way, when multiple devices are shared, input control is turned on for a certain device. The device can handle the event through the event source, effectively limiting the local operation of the controlled device and improving the user experience.

[0331] It should also be understood that this method only takes three-party device interaction as an example, and this application does not limit the number of devices included in the communication system. For example, it can also be four-party device interaction, five-party device interaction, and so on.

[0332] The first device and the second device in the above scheme may belong to different devices, such as a car computer and a tablet, or different devices in a multi-core multi-screen car computer. The first device and the second device may also belong to the same device. For example, the first device and the second device may be different electronic screens mounted on a car computer with a single-core multi-screen mechanism. It should be understood that the present application does not limit the number of devices included in the communication system. For example, the communication system of the present application may include multiple electronic screens mounted on a car computer. In order to clearly describe the scheme of the present application, the following is an example of two electronic screens included in the communication system. That is, the first device is the car screen 1, and the second device is the car screen 2.

[0333] Figure 11 The diagram shows an interaction process between different vehicle-mounted screens provided in an embodiment of the present application.

[0334] Optionally, the vehicle screen 1 may include a reverse control module, which can also be used to receive the projection screen. The vehicle screen 2 may include a reverse control receiving module, an input subsystem, a screen management module, and a privacy sensor service module. In other words, the vehicle screen 1 is used as an example of the second device, and the vehicle screen 2 is used as an example of the first device.

[0335] Specifically, the following steps may be included:

[0336] S1101: Car screen 1 establishes a connection with car screen 2.

[0337] For example, the car screen 1 can start collaboration with the car screen 2. For example, the interface of the car screen 2 is projected onto the car screen 1. Specifically, the method of starting collaboration can refer to the description of S402 and will not be repeated here.

[0338] S1102: The user of the vehicle screen 1 operates to turn on input control.

[0339] It should be understood that the method of turning on input control by the user operating the vehicle screen 2 is only an example of a method of turning on input control and is not intended to be limiting. Specifically, the method of turning on input control can refer to the description in S402 and will not be repeated here.

[0340] S1103: The reverse control module of the vehicle-mounted screen 1 sends an input control message to the reverse control receiving module of the vehicle-mounted screen 2. Correspondingly, the reverse control receiving module of the vehicle-mounted screen 2 receives the input control message.

[0341] S1104: The reverse control receiving module of the vehicle-mounted screen 2 displays a full-screen transparent floating window to the foreground.

[0342] The full-screen transparent floating window includes an escape area.

[0343] S1105: The user of the vehicle-mounted screen 1 performs a reverse control operation.

[0344] For example, the user of the in-vehicle screen 1 can perform operations to control the in-vehicle screen 2 .

[0345] This operation is a reverse control operation. A reverse control operation can be understood as an example of an input operation. Specifically, the reverse control operation can refer to the description of the input operation in S402. Alternatively, a reverse control operation can be understood as a non-local operation. For example, the reverse control operation can be controlling the display of vehicle screen 2 via vehicle screen 1. For example, a user on vehicle screen 1 drags the progress bar of a video on vehicle screen 1 to control the progress of the video on vehicle screen 2.

[0346] S1106: The reverse control module of the vehicle-mounted screen 1 sends a reverse control event to the reverse control receiving module of the vehicle-mounted screen 2. Correspondingly, the reverse control receiving module of the vehicle-mounted screen 2 receives the reverse control event.

[0347] The reverse control event is an event corresponding to the reverse control operation. In other words, the reverse control event is an event triggered by the reverse control operation. The reverse control event can be understood as an example of an input event. For details, please refer to the description of the input event in S401.

[0348] S1107: The reverse control receiving module of the vehicle-mounted screen 2 sends the reverse control event to the input subsystem, and correspondingly, the input subsystem receives the reverse control event.

[0349] S1108: The user operates the vehicle screen 2 by touching the vehicle screen 2 to complete the first operation.

[0350] It should be understood that the user operating the vehicle screen 2 can click any position on the vehicle display screen. For example, the user operating the vehicle screen 2 can click on a certain App.

[0351] S1109: The input subsystem of the vehicle screen 2 determines the transparent floating window currently used to control the input according to the touch position corresponding to the first operation.

[0352] Optionally, before the input subsystem of the vehicle-mounted screen 2 determines the transparent floating window, the input control state of the vehicle-mounted screen 2 can also be determined according to the flag bit. Specifically, reference can be made to the description of the flag bit in S402, which will not be repeated here.

[0353] S1111: The input subsystem of the vehicle-mounted screen 2 processes the first event according to the source of the first event.

[0354] The first event is an event corresponding to the first operation in S1108. In other words, the first event is an event triggered by the first operation. The first event is an example of the input event in S401. For details, please refer to the relevant description in S401 and will not be repeated here.

[0355] Optionally, if the first event is a counter-control event, that is, the first event comes from the vehicle-mounted screen 2 , the input subsystem does not process it and continues to distribute it in the system.

[0356] Optionally, if the first event is a local event, that is, the first event comes from the vehicle screen 1, the input subsystem redirects the first event back to the floating window and blocks the event transmission process outside the escape area.

[0357] This approach allows input control to be implemented across different displays within the same device. When one display is controlled, the event's source can be determined based on the event's handling, such as blocking it. This effectively prevents local operations from impacting tasks on the current screen, improving the user experience.

[0358] Taking into account the privacy protection issues of controlled devices in multi-device collaboration scenarios, the present application proposes another embodiment, which provides a privacy protection method that can protect user privacy.

[0359] Figure 12 A device management method provided in an embodiment of the present application is shown, and the method may include the following steps:

[0360] S1201: The second device sends indication information to the first device, and correspondingly, the first device receives the indication information.

[0361] Among them, the first device and the second device have enabled collaboration. For example, the first device projects its own interface to the second device, and the second device can control the first device through local operations on the second device. Specifically, the method of enabling collaboration between the first device and the second device can refer to the description of S402 and will not be repeated here.

[0362] The indication information is used to instruct the second device to turn off the screen.

[0363] S1202: The first device turns off the screen according to the instruction information.

[0364] S1203: The second device performs a second operation to enable the first application of the first device.

[0365] In other words, when the screen of the first device is off, the second device can still control the first device through local operations. For example, the second device opens the first application through the second operation.

[0366] S1204: When the first application calls a sensitive sensor of the first device, the call is blocked.

[0367] The sensitive sensor may be a camera, a microphone, or other sensors. A blocked call may be understood as an inability to call or a rejection of the call.

[0368] Optionally, the method may further include:

[0369] S1205: The first device displays the reason for the call failure.

[0370] That is, the first device can remind the operating user why the call failed. The user can adjust the operation according to the reminder.

[0371] Optionally, the reason for the call failure may also be displayed on the second device, which is not limited in this application.

[0372] In this method, when the second device cooperates with the first device and the screen is turned off, the call of sensitive sensors can be blocked, thereby protecting user privacy and improving user experience.

[0373] Specifically, the following takes the second device as a car computer and the first device as a tablet as an example to provide a specific implementation process of the above method.

[0374] Figure 13 The embodiment of the present invention shows an interaction process between a vehicle computer and a tablet.

[0375] Optionally, the car computer can include a reverse control module, which can also be used to receive the projection screen. The tablet can include a reverse control receiving module, an input subsystem, a screen management module, and a privacy sensor service module.

[0376] S1301: The vehicle computer and the tablet are connected.

[0377] For example, the car computer can start collaboration with the tablet. For example, the tablet will project its own interface onto the display screen of the car computer. Specifically, the method of starting collaboration can refer to the description of S402 and will not be repeated here.

[0378] S1302: The car user clicks to turn off the screen.

[0379] S1303: The reverse control module of the vehicle computer sends a screen-off instruction to the reverse control receiving module of the tablet computer. Correspondingly, the reverse control receiving module of the tablet computer receives the screen-off instruction.

[0380] S1304: The reverse control receiving module of the tablet calls the screen off interface to the screen management module.

[0381] S1305: The screen management module of the tablet executes screen turning off.

[0382] Optionally, S1306: the screen management module of the tablet sends a screen-off success message to the reverse control receiving module of the tablet, and correspondingly, the reverse control receiving module of the tablet receives the screen-off success message.

[0383] S1307: The anti-control receiving module of the tablet sends a message to the privacy sensor service module to close the privacy sensor call. Correspondingly, the privacy sensor service module receives the message to close the privacy sensor call.

[0384] S1308: The privacy sensor service module sets a flag to block the call to the privacy sensor.

[0385] For example, the flag bit is used to represent the call status of the privacy sensor. Specifically, the flag bit is used to represent whether the call status of the privacy sensor is on or off, or in other words, the flag bit is used to represent whether the call of the privacy sensor is allowed. Specifically, the flag bit can be set to true or false. When the flag bit is true, it represents that the call is allowed or the call status is on, and when the flag bit is false, it represents that the call is rejected or the call status is closed. It should be understood that the setting of the above flag bit is only an example and not a limitation. For example, the flag bit can also be set to 0 or 1. When the flag bit is 1, it represents that the call is allowed or the call status is on, and when the flag bit is 0, it represents that the call is rejected or the call status is closed. It should also be understood that the correspondence between the specific value of the flag bit and the meaning represented by the value is not limited in the embodiments of the present application. It should also be understood that the correspondence between the specific value of the flag bit and the meaning represented by the value can be predefined or configured, and the embodiments of the present application do not limit this.

[0386] S1309: The car user completes the screen projection reverse control operation.

[0387] For example, the screen projection reverse control operation is used to trigger a second event.

[0388] S1310: The reverse control receiving module receives a second event.

[0389] The processing corresponding to the second event needs to call the sensitive sensor of the tablet. For example, the processing corresponding to the second event can be to start an application in the second device.

[0390] Optionally, S1311: the privacy sensing service module calls back the application's call message on the sensitive sensor to the counter-control receiving module. Correspondingly, the counter-control receiving module receives the application's call message on the sensitive sensor.

[0391] S1312: The counter-control receiving module reminds the operating user of the reason for the call failure.

[0392] In this approach, even when the tablet screen is off, the car computer can still control the tablet through local operations. At the same time, the tablet uses the privacy sensor service module to deny user operations to sensitive sensors, protecting user privacy and improving the user experience.

[0393] It should be understood that this method can be applied to the aforementioned embodiments, such as the aforementioned screen projection reverse control scenario. Figures 4 to 11 In the method described.

[0394] It should also be understood that the above process uses a tablet and a car computer as an example, but this application is not limited to this. For example, the car computer can also turn off the screen, rejecting the tablet's call to the car computer's privacy sensor. For another example, the first device and the second device can be different display screens of the same device, such as car screen 1 and car screen 2. For another example, the communication system can also include more devices, for example, the interaction between a mobile phone, a tablet and the car computer, etc. For the sake of brevity, we will not list them one by one here.

[0395] It should also be understood that the embodiments of the present application can also be applied to scenarios with multiple devices and multiple screens. If these multiple devices and multiple screens share a system, the specific solution can be referred to Figure 11 If the multiple devices belong to different systems and each system manages multiple screens, the solution within the same system can refer to Figure 11 For cross-system (or multiple system) solutions, please refer to Figures 5 to 8 The description in , will not be repeated here.

[0396] It should also be understood that the full-screen transparent floating window in the embodiment of the present application is covered in the display area of ​​the controlled device, or in other words, the full-screen transparent floating window is covered in the display area of ​​the device that is input controlled. For example, in the interaction process between the tablet and the car computer, when the tablet is input controlled, the full-screen transparent floating window is covered in the display screen of the tablet; between multiple screens belonging to the same system, the full-screen transparent floating window is covered on the screen that is input controlled, such as when the vehicle screen 1 and the vehicle screen 2 are interactive, the vehicle screen 2 is input controlled, and the full-screen transparent floating window is covered on the vehicle screen 2. In short, the first device in the present application can be an electronic device, such as a tablet, or a screen, such as a tablet screen, a vehicle screen, etc. The first device is the device that is input controlled, and the full-screen transparent floating window is displayed on the device that is input controlled.

[0397] Next, combine Figures 14 and 15 , describes the device provided in the embodiments of the present application.

[0398] Figure 14 The schematic block diagram of the device provided by the embodiment of the present application is shown. The device can be set in the above Figures 4 to 13 The vehicle-mounted device or electronic device described in.

[0399] For example, Figure 14 As shown, the device 400 includes: a display unit 415 and a processing unit 420.

[0400] In one possible implementation, the display unit 415 is used to execute the above Figures 4 to 13 The processing unit 420 is used to perform the steps related to the display of the second device (such as the vehicle computer) in the embodiment described above; Figures 4 to 13 The steps related to the processing of the second device (such as the vehicle computer) in the embodiment described in.

[0401] Optionally, in some embodiments, the device may further include a playback unit configured to execute the above Figures 4 to 13 The steps related to playback of the second device (such as a car computer) in the embodiment described in.

[0402] In another possible implementation, the display unit 415 is used to execute the above Figures 4 to 13 The processing unit 420 is used to perform the display-related steps of the first device (such as a tablet) in the embodiment described above; Figures 4 to 13 The processing-related steps of the first device (such as a tablet) in the embodiment described in.

[0403] Optionally, in some embodiments, the device may further include a playback unit configured to execute the above Figure 8 The steps related to playback of the electronic device in the embodiment described in.

[0404] Figure 15 A schematic structural diagram of an electronic device 500 provided in an embodiment of the present application is shown.

[0405] For example, Figure 15 As shown, the electronic device 500 includes: one or more processors 515, one or more memories 520, the one or more memories 520 storing one or more computer programs, the one or more computer programs including instructions. When the instructions are executed by the one or more processors 515, the above Figures 4 to 13 The second device (such as a vehicle computer) described in the above Figures 4 to 13 The technical solution in the embodiment of the present invention, or, as described above Figures 4 to 13 The first device (such as a tablet) described above executes the above Figures 4 to 13 The technical solution of the embodiment in FIG.

[0406] The present application provides a computer program product that, when executed on an electronic device, enables the electronic device to execute the technical solution in the above embodiment. The implementation principle and technical effects are similar to those of the above method-related embodiments and will not be described in detail here.

[0407] The embodiment of the present application provides a readable storage medium, which contains instructions. When the instructions are executed on an electronic device, the electronic device executes the technical solution of the above embodiment. The implementation principle and technical effect are similar and will not be repeated here.

[0408] The present application provides a chip for executing instructions. When the chip is running, the technical solution of the above embodiment is executed. The implementation principle and technical effect are similar and will not be described here.

[0409] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0410] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

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

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

[0413] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

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

[0415] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A device management method, characterized in that: Applied to a system including a first device and a second device, wherein an interface of the first device is projected onto the second device for display, the method comprising: The first device receives a first event, where the first event is triggered by a first operation, and the first operation is a local operation of the first device; When the input control state is on and the location of the first operation is within the first area, the first device blocks the transmission of the first event, wherein the input control state being on indicates that the local operation of the first device is controlled. When the input control state is on and the location of the first operation is within the second area, the first device adjusts the input control state to off, wherein the input control state being off indicates that the local operation of the first device is not controlled, the first area and the second area are respectively part of the display area of ​​the first device, and the first area and the second area do not overlap.

2. The method according to claim 1, characterized in that The method further comprises: When the input control state is off, the first device allows the transmission of the first event.

3. The method according to claim 1 or 2, characterized in that The method further comprises: The first device receives a first message, where the first message is used to instruct to adjust the input control state to on.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: When the input control state is on, the first device opens a full-screen transparent floating window, and the full-screen transparent floating window covers the display area of ​​the first device.

5. The method according to claim 4, characterized in that The full-screen transparent floating window includes the second area.

6. The method according to any one of claims 1 to 5, characterized in that The first event corresponds to screen-off processing, and when the input control state is off, the method further includes: The first device performs screen-off processing.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The first device receives instruction information from the second device, where the instruction information is used to instruct to turn off the screen, and the instruction information is triggered by a local reverse control operation of the second device; The first device performing screen-off processing includes: The first device performs screen-off processing according to the instruction information.

8. The method according to claim 6 or 7, characterized in that The method further comprises: The first device receives a second event, where the second event is triggered by a screen projection reverse control operation from the second device; In response to the second event, the first device performs processing corresponding to the second event.

9. The method according to claim 8, characterized in that The method further comprises: When the processing corresponding to the second event calls the sensitive sensor of the first device, the first device blocks the call.

10. A computer-readable storage medium, characterized in that The method comprises computer instructions, which, when executed on an electronic device, cause the electronic device to execute the method according to any one of claims 1 to 9.

11. A chip system, characterized in that: The device comprises: a processor configured to call and run a computer program from a memory, so that an electronic device equipped with the chip system executes the device management method according to any one of claims 1 to 9.

12. An electronic device, characterized in that: The electronic device includes a display screen, a memory and one or more processors, wherein the memory is used to store computer program code, and the computer program code includes computer instructions; when the computer instructions are executed by the one or more processors, the electronic device executes the method as described in any one of claims 1 to 9.

13. A device management method, characterized in that: Applied to a system including a first device and a second device, wherein an interface of the first device is projected onto the second device for display, the method comprising: The first device receives a first reverse control event, where the first reverse control event is triggered by a local reverse control operation of the second device; In response to the first counter-control event, the first device performs a process corresponding to the first counter-control event; The first device receives a first local event, where an operation corresponding to the first local event is within a first area; In response to the first local event, the first device does not perform processing corresponding to the first local event; The first device receives a second local event, and the operation corresponding to the second local event is within a second area, wherein the first area and the second area are respectively part of a display area of ​​the first device, and the first area and the second area do not overlap; In response to the second local event, the first device performs processing corresponding to the second local event; The processing corresponding to the second local event is to adjust the input control state of the first device to off, wherein the input control state being off indicates that the local operation of the first device is not controlled.

14. The method according to claim 13, characterized in that In response to the second local event, after the first device performs processing corresponding to the second local event, the method further includes: The first device receives a third local event, where an operation corresponding to the third local event is located at any position in the display area of ​​the first device; In response to the third local event, the first device performs processing corresponding to the third local event.

15. The method according to claim 13, characterized in that The method further comprises: The first device receives a second reverse control event, where the second reverse control event is triggered by a local reverse control operation of the second device; In response to the second counter-control event, the first device performs a screen-off operation; The first device receives a third reverse control event, where the third reverse control event is triggered by a local reverse control operation of the second device; In response to the third reverse control event, the first device starts a first application.

16. The method according to claim 13, characterized in that The method further comprises: The first device receives a fourth local event, where the fourth local event instructs the first device to turn off the screen; In response to the fourth local event, the first device performs a screen-off operation; The first device receives a fourth reverse control event, where the fourth reverse control event is triggered by a local reverse control operation of the second device; In response to the fourth reverse control event, the first device starts a first application.

17. The method according to claim 15 or 16, characterized in that The method further comprises: When the first application calls the sensitive sensor of the second device, a prompt indicating that the call failed is displayed on the first device and / or the second device.

18. A device management system, characterized in that: The device comprises the first device and the second device according to any one of claims 13 to 17.

Images