A cross-terminal quick screen locking synchronization method and system in a multi-device cooperative scenario

Abstract

The application discloses a cross-terminal quick screen locking synchronization method and system in a multi-device cooperative scenario, relates to the technical field of intelligent terminal device cooperative control, and discloses the cross-terminal quick screen locking synchronization method and system in the multi-device cooperative scenario, which synchronizes to the cooperative terminal after generating and verifying the screen locking instruction uniformly by the master terminal, realizes one-key screen locking operation of the multi-device, and can improve the screen locking operation efficiency and safety of the multi-device.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of intelligent terminal device cooperative control, in particular to a cross-terminal quick screen locking synchronization method and system in a multi-device cooperative scenario. BACKGROUND

[0002] In the current digital life, people increasingly rely on multi-device cooperative work, such as smartphones, tablets, laptops, etc. These devices often need to be locked in daily use to protect personal privacy and data security. However, the traditional screen locking method has obvious problems of cumbersome operation, and users must perform screen locking operations on each device individually, which causes great inconvenience in a multi-device cooperative scenario. Especially in emergency situations, such as the need to quickly lock all devices to prevent information leakage, operating each device one by one not only wastes time and effort, but also may cause security risks due to the failure to lock critical devices in time.

[0003] Although there are some cross-device synchronization tools in the prior art, these solutions mainly focus on data synchronization or file sharing and other general functions. For screen locking, which involves core operations related to device security, there are generally problems such as response delay and insufficient synchronization reliability. When the device is in a complex network environment, the existing solutions are difficult to ensure the real-time and security of the screen locking instruction. In addition, the existing technology lacks an intelligent recognition mechanism for user operation intentions, which can easily cause unintended screen locking operations due to accidental touches, affecting user experience.

[0004] The above content is only used to assist in understanding the technical solutions of the present application and does not represent the acknowledgement of the above content as prior art. SUMMARY

[0005] The main purpose of the present application is to provide a cross-terminal quick screen locking synchronization method and system in a multi-device cooperative scenario, aiming to improve the efficiency and security of multi-device screen locking operations.

[0006] To achieve the above purpose, the present application provides a cross-terminal quick screen locking synchronization method in a multi-device cooperative scenario, which comprises:

[0007] Obtaining original touch event data through the touch screen of the master terminal;

[0008] Validating the original touch event data based on a preset rule to obtain effective operation instruction data;

[0009] Generating local screen locking instruction data according to the effective operation instruction data and executing the screen locking action of the master terminal;

[0010] Transmitting the local screen locking instruction data to at least one cooperative terminal through a device cooperative network;

[0011] The terminal performs a synchronous screen locking action on the received screen locking instruction data based on cooperation.

[0012] In an embodiment, the step of performing validity verification processing on the original touch event data based on a preset rule to obtain valid operation instruction data comprises:

[0013] extracting coordinate position data from the original touch event data;

[0014] comparing and verifying the coordinate position data with a screen blank area coordinate range to obtain area verification result data;

[0015] identifying time interval data of continuous touch events based on the area verification result data;

[0016] generating valid operation instruction data when the time interval data meets a preset double-click threshold range and the area verification result data is a blank area.

[0017] In an embodiment, the step of comparing and verifying the coordinate position data with a screen blank area coordinate range to obtain area verification result data comprises:

[0018] obtaining current screen interface layout data through a system interface;

[0019] analyzing an interactive control coordinate range set based on the layout data;

[0020] performing overlapping operation processing on the coordinate position data and the interactive control coordinate range set;

[0021] if the coordinate position data is not contained in any interactive control coordinate range, outputting the area verification result data as a blank area.

[0022] In an embodiment, the step of performing a synchronous screen locking action on the received screen locking instruction data based on cooperation comprises:

[0023] performing identity legality verification on the cooperative terminal through a device authentication protocol to obtain device authentication result data;

[0024] when the device authentication result data is a legal device, encapsulating local screen locking instruction data into encrypted transmission data packets;

[0025] selecting a real-time transmission channel or an offline cache queue based on state detection data of a device cooperation network;

[0026] sending the encrypted transmission data packets to the cooperative terminal through the selected channel.

[0027] In an embodiment, the step of selecting a real-time transmission channel or an offline cache queue based on state detection data of a device cooperation network comprises:

[0028] Periodically acquire signal strength data and delay data of the device coordination network;

[0029] When the signal strength data is below a threshold or the delay data exceeds a threshold, write the encrypted transmission data packet to an offline cache queue;

[0030] When the signal strength data recovers above the threshold, batch push the data packets in the offline cache queue to the coordination terminal.

[0031] In an embodiment, after the step of generating local lock screen instruction data according to valid operation instruction data and performing a lock screen action of the master terminal, the method further comprises:

[0032] Collect device posture data through the master terminal sensor;

[0033] If the posture data indicates that the device is in a flat state, enable the power saving mode to perform the lock screen action;

[0034] Attach the device posture data to the local lock screen instruction data and synchronize to the coordination terminal.

[0035] In an embodiment, the step of performing a synchronous lock screen action by the coordination terminal based on the received lock screen instruction data comprises:

[0036] Perform integrity verification on the received lock screen instruction data by the coordination terminal;

[0037] If the verification passes, parse the device identification data in the instruction;

[0038] Match the local terminal configuration file according to the device identification data;

[0039] Perform the lock screen action based on the security policy data in the configuration file.

[0040] In an embodiment, the security policy data requires biometric authentication; the step of performing the lock screen action based on the security policy data in the configuration file comprises:

[0041] Start the fingerprint sensor to acquire biometric data;

[0042] Match and verify the biometric data with pre-stored template data;

[0043] When the matching is successful, trigger a screen closing circuit control signal to perform the lock screen action.

[0044] In an embodiment, the method further comprises:

[0045] When the master terminal does not detect valid operation instruction data, generate operation log data and store it to the local cache;

[0046] Analyze continuous invalid operation frequency data in the operation log data;

[0047] If the frequency data exceeds the alarm threshold, the user terminal is sent a false touch reminder notification data.

[0048] In addition, to achieve the above-mentioned purpose, the present application also proposes a cross-terminal quick screen locking synchronization system in a multi-device collaborative scenario, which comprises a memory, a processor and a cross-terminal quick screen locking synchronization program in a multi-device collaborative scenario stored in the memory and executable on the processor. The cross-terminal quick screen locking synchronization program in a multi-device collaborative scenario is configured to implement the steps of the cross-terminal quick screen locking synchronization method in a multi-device collaborative scenario.

[0049] The cross-terminal quick screen locking synchronization method and system in a multi-device collaborative scenario proposed by the present application can realize one-key screen locking operation of multiple devices by generating and verifying screen locking instructions by the master terminal and synchronizing to the collaborative terminal, which can improve the efficiency and security of multi-device screen locking operation. BRIEF DESCRIPTION OF DRAWINGS

[0050] The accompanying drawings incorporated in and forming a part of the specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application.

[0051] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the accompanying drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, for those skilled in the art, other drawings can also be obtained from these drawings without creative labor.

[0052] Figure 1 The flowchart provided by an embodiment of the cross-terminal quick screen locking synchronization method in a multi-device collaborative scenario of the present application;

[0053] Figure 2 The structural diagram provided by an embodiment of the cross-terminal quick screen locking synchronization system in a multi-device collaborative scenario of the present application.

[0054] Explanation of the reference signs:

[0055] 10, memory; 20, processor.

[0056] The purpose implementation, functional characteristics and advantages of the present application will be further described with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION

[0057] The technical solutions in the present application will be described clearly and completely in the present application in combination with the drawings. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. The components of the present application described and shown in the drawings can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the claimed present application, but only represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work belong to the scope of protection of the present application.

[0058] It should be understood that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. Meanwhile, in the description of the present application, the terms "first", "second", etc. are only used to distinguish the description, and cannot be understood as indicating or implying relative importance.

[0059] In the prior art, the lock screen operation in the multi-device collaboration scenario usually requires the user to perform the lock screen action on each terminal separately. This operation method has the problems of low efficiency and delayed response in the case of a large number of devices or emergency situations. When the user needs to protect the data security of multiple devices at the same time, the traditional method cannot realize instant linkage across terminals, resulting in cumbersome operation and security risks.

[0060] In order to solve the above problems, the inventors observed that the user has a potential demand for unified control of the lock screen state in a multi-device environment. By analyzing the limitations of existing synchronization tools, it is found that a simple data transmission protocol cannot meet the dual requirements of real-time and security for the lock screen operation. Therefore, it is proposed to construct an instruction generation mechanism based on touch event recognition, and to design a device collaboration network to realize reliable transmission of instructions.

[0061] Based on this, the embodiments of the present application provide a cross-terminal quick lock screen synchronization method in a multi-device collaboration scenario, with reference to Figure 1 , the method comprises steps S100-S500, wherein:

[0062] Step S100, obtaining original touch event data through the touch screen of the master terminal;

[0063] Step S200, performing validity verification processing on the original touch event data based on a preset rule to obtain valid operation instruction data;

[0064] Step S300, generating local lock screen instruction data according to the valid operation instruction data, and performing a lock screen action of the master terminal;

[0065] Step S400, transmitting the local lock screen instruction data to at least one cooperative terminal through a device cooperative network;

[0066] Step S500, performing a synchronous lock screen action based on the lock screen instruction data received by the cooperative terminal.

[0067] In the embodiment, the master terminal refers to a control device with touch screen processing capability, such as a smart phone or a tablet computer, for initiating a lock screen operation instruction. The original touch event data contains coordinate, pressure and timestamp information generated when the user's finger contacts the screen, which can be obtained through the underlying interface provided by the operating system. The validity verification process filters out invalid operations through preset rules, such as a combination of coordinate area comparison and time interval judgment, to ensure that only touch events that meet certain conditions will trigger the subsequent process. The device cooperative network refers to a transmission channel that supports short-distance wireless communication, such as a Bluetooth Mesh network or a Wi-Fi direct connection, for establishing a secure data transmission link between devices.

[0068] In the embodiment, when the user performs a specific touch operation on the phone screen, the system first captures the original data of the touch event. Through the coordinate analysis module, it is determined whether the touch position is in the blank area of the screen, and whether the time interval of continuous touch meets the double-click operation characteristics. After verification, the phone immediately performs local lock screen and generates an encrypted instruction package. The instruction package is sent to associated devices such as tablets, laptops, etc. through the established device cooperative network. After receiving the instruction, each cooperative terminal first performs identity authentication and instruction decryption, and then performs a lock screen action according to the current state of the device.

[0069] In the embodiment, the instruction synchronization mechanism is used to realize one-time operation and multi-device response, and the touch event validity verification and network state adaptive transmission strategy are added, which not only avoids accidental lock screen caused by misoperation, but also ensures the reachability of the instruction in different network environments. In addition, the application effectively solves the operation redundancy problem existing in the traditional method, reduces the probability of false triggering through the intelligent verification mechanism, and ensures the reliability of the instruction under complex network conditions by using the adaptive transmission strategy. The cooperative terminal synchronously receives additional information such as device posture when performing lock screen, providing differentiated lock screen strategy execution basis for different terminals.

[0070] In an implementation, the step of performing validity verification on the original touch event data based on preset rules to obtain valid operation instruction data comprises: extracting coordinate position data from the original touch event data; comparing and checking the coordinate position data with a blank area coordinate range of the screen to obtain area verification result data; identifying time interval data of continuous touch events based on the area verification result data; and generating valid operation instruction data when the time interval data meets a preset double-click threshold range and the area verification result data is a blank area.

[0071] In the embodiment, the coordinate position data refers to specific position information of a touch event in a screen coordinate system, which can be implemented by using coordinate values output by a touch chip, and is used to determine whether a user operation occurs in a non-interaction area. The blank area coordinate range of the screen refers to boundary data of an area in a current interface that does not contain an interactive control, which can be implemented by calculating a remaining area after obtaining control positions by parsing a system interface layout file, and is used to exclude the possibility of a false touch control. The time interval data of continuous touch events refers to a time duration difference between two valid touch operations, which can be implemented by using a system timer to record a time difference between a touch point being lifted and being pressed again, and is used to identify a double-click operation feature. The preset double-click threshold range refers to a legal double-click operation time interval defined by the system, which can be set to a numerical range of 200 milliseconds to 500 milliseconds, and is used to filter non-intentional continuous touch.

[0072] In the embodiment, when a user performs a touch operation on a screen of a master terminal, the system first extracts touch point coordinate data and matches the coordinate data with a current blank area of the screen. If the touch point is located in the blank area and a time interval between two continuous touch operations is within a preset threshold range, the system determines that the operation is a valid double-click lock screen instruction. For example, when a user performs a long press and then a quick double-click on a desktop blank area, the system excludes false triggering of an application icon area by coordinate checking, and confirms a user intention by combining time interval analysis, and finally generates a valid lock screen instruction. This process ensures the accuracy of an operation instruction by using a double verification mechanism, and avoids false locking caused by false touch or non-standard operation.

[0073] In the embodiment, by introducing a screen area checking mechanism and combining dynamic analysis of a touch point position and an interface layout, a user's real intention and false operation are effectively distinguished, the accuracy of instruction verification is improved, a specific double-click operation of a user in a non-interaction area is accurately identified, invalid instruction generation caused by interface control blocking or false touch is avoided, and the accuracy of triggering of a cross-terminal lock screen instruction and operation reliability are ensured, thereby providing accurate instruction verification basis for safe lock screen in a multi-device collaboration scenario.

[0074] In an implementation, the step of comparing the coordinate position data with the blank region coordinate range to obtain region verification result data comprises: obtaining current screen interface layout data through a system interface; parsing an interactive control coordinate range set based on the layout data; performing overlapping operation processing on the coordinate position data and the interactive control coordinate range set; and outputting the region verification result data as a blank region if the coordinate position data is not contained in any interactive control coordinate range.

[0075] In the embodiment, the current screen interface layout data refers to arrangement information of all visual elements in a current display interface of a terminal device, and can be obtained by calling an interface rendering interface provided by an operating system, such as View Hierarchy of an Android system or UIWindow hierarchical structure data of iOS. The interactive control coordinate range set refers to a position information set of all operation components that can trigger a response in an interface, and can be obtained by traversing buttons, input boxes and other interactive elements in the layout data to extract position and size parameters in a screen coordinate system. The overlapping operation processing refers to a calculation process of judging whether a touch point coordinate and a control coordinate range have an intersection, and can be implemented by using a rectangular collision detection algorithm, such as by comparing whether X and Y values of the coordinate point are simultaneously located between left / right boundaries and upper / lower boundaries of a control rectangular region.

[0076] In the embodiment, when a user performs a touch operation on a screen of a master terminal, the system first obtains complete layout data of a current active interface through an interface. The layout data contains types, positions and size information of all interactive controls. Then, by traversing the layout data, rectangular region parameters of each interactive control in a screen coordinate system are extracted to form a coordinate range set covering all controls. Coordinate position data generated by a touch event is sequentially compared with each control region in the set, for example, by using a coordinate point and a rectangular region boundary value comparison algorithm. If the coordinate point does not fall into any control region, it is determined as a blank region touch event, and corresponding region verification result data is generated. This process can dynamically adapt to changes in different application interface layouts, for example, when a user switches to different applications, the system can update the control coordinate range set of the current interface in real time.

[0077] In this embodiment, by analyzing the control position in the current interface layout in real time, the coordinate range of all interactive areas can be accurately excluded, ensuring that the lock screen instruction is triggered only in the blank area without any control, and avoiding the problem of misoperation caused by the change of interface element position. Through the above technical solution, the present application can accurately identify whether the user touch operation occurs in the invalid area of the current screen, effectively preventing the unintended lock screen behavior caused by mis-touching the control. At the same time, by dynamically obtaining the interface layout data, the interface changes in different application scenarios can be adapted, and the accuracy and reliability of the cross-terminal lock screen operation are improved.

[0078] In a feasible implementation, the step of executing a synchronous lock screen action on the received lock screen instruction data based on the cooperative terminal includes: performing identity legality verification on the cooperative terminal through a device authentication protocol to obtain device authentication result data; when the device authentication result data is a legal device, encapsulating the local lock screen instruction data into an encrypted transmission data packet; selecting a real-time transmission channel or an offline cache queue based on the state detection data of the device cooperative network; and sending the encrypted transmission data packet to the cooperative terminal through the selected channel.

[0079] In this embodiment, the device authentication protocol refers to a communication protocol for verifying the legality of the device identity, which can be implemented by a two-way certificate verification mechanism. The device identity is verified in both directions by pre-stored digital certificates and keys to prevent illegal devices from accessing the cooperative network. The encrypted transmission data packet refers to a data encapsulation structure processed by an encryption algorithm. AES-GCM mode can be used for encryption and integrity protection to ensure that the lock screen instruction is not tampered with or stolen during transmission. The real-time transmission channel refers to an instant communication link established based on the current network state. TCP long connection or QUIC protocol can be used to achieve low-latency transmission. The offline cache queue refers to a storage area for temporarily storing data when the network is unavailable. Local database or memory cache can be used to achieve batch transmission after the network is restored.

[0080] In this embodiment, when the master terminal generates a lock screen instruction, the identity of the target cooperative terminal is first verified through the device authentication protocol. For example, the certificate exchange has been completed when the device is initially networked, and the legality of the device is determined by comparing the certificate fingerprint with the pre-stored record. For a legal device, the lock screen instruction is converted into a binary data packet that meets the encryption standard, which contains a timestamp and device identification information. The signal quality of the device cooperative network is monitored by a periodic detection mechanism, such as collecting RSSI value and round-trip delay every 500 milliseconds. When the network quality indicator is below the set threshold, the encrypted data packet is stored in a cache queue with persistent storage capability, and a network state monitoring thread is started; when the network is restored, the data in the cache queue is sent to the target device in batches according to the priority order.

[0081] In this embodiment, through the combination of dynamic network state detection and multiple security mechanisms, the reliability of instruction transmission is ensured in a complex network environment, and the man-in-the-middle attack of illegal devices is effectively prevented, ensuring that legal devices can receive encrypted lock screen instructions in time under various network conditions, avoiding the loss of instructions or device lock due to network fluctuations, and preventing sensitive operation instructions from being illegally intercepted through encrypted transmission and device authentication double mechanisms.

[0082] In a feasible implementation, the step of selecting a real-time transmission channel or an offline cache queue based on the state detection data of the device collaborative network includes: periodically acquiring signal strength data and delay data of the device collaborative network; when the signal strength data is lower than a threshold or the delay data exceeds a threshold, writing the encrypted transmission data packet into the offline cache queue; when the signal strength data recovers to above the threshold, pushing the data packets in the offline cache queue to the collaborative terminal in batches.

[0083] In this embodiment, the signal strength data refers to the radio frequency signal energy value received by the wireless communication module, which can be realized by a Wi-Fi signal strength detection interface or a Bluetooth RSSI measurement module, and is used to represent the stability of the communication link between devices. The delay data refers to the transmission time of the data packet from the sending end to the receiving end, which can be realized by ICMP protocol measurement or application layer timestamp difference calculation, and is used to evaluate the real-time performance of network transmission. The offline cache queue refers to a temporary storage area for storing data packets to be sent, which can be realized by a ring buffer or a linked list data structure, and is used to temporarily store lock screen instruction data when the network is abnormal.

[0084] In this embodiment, the master terminal collects signal strength data every 30 seconds through the wireless communication module, for example, quantized by dBm unit, and calculates the data packet transmission delay through the timestamp difference. When the signal strength is detected to be lower than -70dBm or the delay is detected to be more than 500ms, the offline storage mechanism is triggered, and the lock screen instruction data to be sent is written into the cache queue in chronological order. The cache queue is managed by a first-in-first-out strategy, and when the network monitoring module detects that the signal strength recovers to above -60dBm, multiple data packets accumulated in the queue are combined into a batch transmission task, and the data pushing is completed through the TCP protocol.

[0085] In this embodiment, by dynamically switching the transmission channel and combining the cache mechanism, the efficiency advantage of real-time transmission is guaranteed, and the reliability of instruction transmission is maintained when the network is abnormal. The existing technology cannot adapt to the complex and variable network environment by using a single transmission channel. The dual threshold judgment mechanism realizes the intelligent switching of the transmission strategy. Therefore, in the environment of unstable network quality, the application ensures the reliable storage of critical instructions through the offline cache mechanism, and automatically completes the batch transmission after the network is restored, avoiding the loss of instructions caused by network interruption in the traditional scheme. The mechanism significantly improves the execution success rate of cross-terminal lock screen operation under the premise of ensuring safety.

[0086] In a feasible implementation, after the step of generating local lock screen instruction data according to effective operation instruction data and performing a lock screen action of the master terminal, the method further comprises: collecting device posture data by a master terminal sensor; if the posture data indicates that the device is in a flat state, a power saving mode is enabled to perform the lock screen action; and the device posture data is appended to the local lock screen instruction data and synchronized to the collaborative terminal.

[0087] In this embodiment, the device posture data refers to the physical state information of the device in three-dimensional space collected by an acceleration sensor or a gyroscope. Specifically, a three-axis acceleration sensor can be used in combination with a posture solving algorithm to determine the flat state of the device, and this data is used to determine whether the device is in a stationary state. The power saving mode refers to an energy-saving running state by reducing the screen backlight brightness or closing unnecessary background processes. Specifically, a dynamic power management strategy can be used to achieve this mode, which reduces energy consumption when the device is flat. The device posture data appended to the lock screen instruction data refers to data encapsulation of the posture parameters and the lock screen control signal. Specifically, a JSON format data packet structure can be used to achieve this, which enables the collaborative terminal to adjust the lock screen strategy according to the device state.

[0088] In this embodiment, when the master terminal generates the lock screen instruction, its built-in sensor module continuously collects three-dimensional acceleration data of the device. The posture solving algorithm is used to determine whether the device is in a horizontal placement state. For example, when the X-axis and Y-axis acceleration values are within ±0.5g for 5 seconds, the power saving lock screen mode is triggered. In this mode, the master terminal adjusts the screen brightness to the lowest and closes the Bluetooth scanning function, and sends a data packet containing posture parameters to the collaborative terminal through an encrypted channel. After receiving the lock screen instruction with additional posture data, if the collaborative terminal detects that its own device is also in a flat state, it synchronously enables the low-power lock screen mode.

[0089] In the embodiment, by introducing the posture sensing mechanism, the multi-device system can intelligently adjust the lock screen energy consumption strategy according to the physical state, solving the energy optimization problem in the idle state of the device in the prior art. When the user places multiple devices on the desktop, the system automatically switches to the power-saving lock screen mode, prolonging the standby time of the device. The cooperative terminal synchronously executes the energy-saving operation according to the posture data of the master device, avoiding the inconsistent problem of the strategy generated by the independent state judgment of each device in the traditional scheme, and improving the energy utilization efficiency in the multi-device cooperative scene.

[0090] In a feasible implementation, the step of executing the synchronous lock screen action by the cooperative terminal based on the received lock screen instruction data includes: performing integrity verification on the received lock screen instruction data by the cooperative terminal; if the verification passes, parsing the device identification data in the instruction; matching the local terminal configuration file according to the device identification data; and executing the lock screen action based on the security policy data in the configuration file.

[0091] In the embodiment, the integrity verification refers to verifying that the data has not been tampered with or damaged in the transmission process, which can be implemented by using a hash algorithm or a digital signature technology. By comparing the check value of the received data with the check value of the original data, the integrity and reliability of the instruction data are ensured. The device identification data refers to the characteristic information used to uniquely identify the cooperative terminal, which can be implemented by using a device serial number, a MAC address or a device registration code, and is used to accurately identify the identity attribute of the target device in a distributed network. The security policy data refers to the pre-set device operation permission rule, which can be implemented by using a biometric authentication strategy or a password verification strategy, and the security conditions required for executing the lock screen action are determined by matching the device identification with the locally stored configuration file.

[0092] In the embodiment, when the cooperative terminal receives the lock screen instruction data, the data packet is first subjected to integrity verification, and if the check value is found to be abnormal, the instruction is discarded; if the verification passes, the device identification data carried in the instruction is extracted, and the local terminal configuration file is queried to confirm whether the local device is the target device specified by the instruction. After determining the device matching, the security policy data defined in the configuration file is further read, for example, when the security policy requires biometric authentication, the cooperative terminal starts the fingerprint recognition module for identity verification, and only after the verification passes, the screen closing operation is executed.

[0093] In the embodiment, by introducing the integrity verification and device identification matching mechanism, it is ensured that only the target device that has passed the authentication will respond to the lock screen instruction, and the hierarchical permission control is realized in combination with the security policy data, effectively preventing unauthorized devices from executing sensitive operations. At the same time, the multiple verification mechanisms ensure that the instruction is executed on the legal device according to the pre-set security policy, which not only guarantees the operation reliability, but also improves the security level of cross-terminal cooperation.

[0094] In an implementable embodiment, the security policy data requires biological authentication; and the step of performing the screen locking action based on the security policy data in the configuration file comprises: starting a fingerprint sensor to acquire biological feature data; performing matching verification of the biological feature data with pre-stored template data; and triggering a screen-off circuit control signal to perform the screen locking action when the matching is successful.

[0095] In this embodiment, biological authentication refers to a way of identity verification through biological feature recognition technology, which can be implemented by a fingerprint recognition module, and serves to improve the security level of the screen locking operation. The fingerprint sensor refers to a hardware device for collecting user fingerprint images, which can be implemented by a capacitive or optical sensor, and serves to acquire real-time biological feature raw data. The pre-stored template data refers to a standard biological feature sample pre-stored in a device security area, which can be implemented by encryption storage technology, and serves to provide a reference for biological feature comparison. The matching verification refers to a process of similarity calculation of real-time collected data and pre-stored data, which can be implemented by a pattern recognition algorithm, and serves to verify the legitimacy of the operator's identity. The screen-off circuit control signal refers to an electronic instruction for driving a display screen power module, which can be implemented by sending a level signal through a GPIO interface, and serves to directly control the screen power-off state.

[0096] In this embodiment, when the cooperative terminal receives the screen locking instruction, the fingerprint sensor is first activated to enter a working state. The user presses the registered finger on the sensor area, and the sensor converts the captured fingerprint image into a digital feature code. The feature code is compared with the encrypted template stored in the security chip memory point by point, and if the similarity reaches a preset threshold, a verification pass instruction is generated. At this time, the device control module sends a shutdown instruction to the screen power circuit, immediately turns off the backlight power and freezes the touch response, and synchronously updates the screen locking state to the system security log.

[0097] In this embodiment, the device is authenticated through biological feature binding, which ensures the convenience of operation while building a dual verification mechanism. In the prior art, the device directly executes the action after receiving the screen locking instruction, and cannot distinguish the operator's identity. However, the present scheme adds a biological feature verification step in the instruction execution link, effectively preventing others from maliciously triggering the screen locking. Therefore, on the basis of maintaining the coherence of the operation, the present application prevents misoperation or malicious screen locking through a hardware-level security verification mechanism, and is particularly suitable for application scenarios that require quick locking of multiple devices and have high security requirements.

[0098] In an implementation, the method further comprises: when the master terminal does not detect valid operation instruction data, generating operation log data and storing the operation log data to a local cache; analyzing continuous invalid operation frequency data in the operation log data; and if the frequency data exceeds an alarm threshold, sending a false touch reminding notification data to the user terminal.

[0099] In the embodiment, the operation log data refers to a time series data set recording user operation behaviors, which can be implemented in a structured database table or a log file form, and is used to trace the occurrence time and operation trajectory of invalid operations. The continuous invalid operation frequency data refers to a statistical value of the number of operations in a unit time that are not recognized by the system, which can be implemented by a sliding time window algorithm, and is used to quantify the intensity of false touch behaviors of the user. The alarm threshold refers to a condition parameter triggering a reminding function, which can be implemented by a dynamic adjustment strategy, for example, setting a baseline value according to the historical operation habits of the user, and triggering an alarm when the invalid operation frequency deviates from the baseline value by a set amplitude.

[0100] In the embodiment, when the user continuously performs touch operations in the non-interaction area of the device screen, the system determines invalid operations through the coordinate verification module, and writes the operation time, touch coordinates and determination results into the local cache. The log analysis module counts the number of invalid operations with a five-minute time window, and when it detects that the number of invalid operations in the window exceeds a preset threshold, triggers a notification service to push a reminding message to the user device. For example, when the device is in the pocket, the user may generate continuous invalid operations due to false touch, and the system actively pushes a vibration prompt or a pop-up window reminder after identifying the abnormal pattern by analyzing the log data.

[0101] In some embodiments, the log analysis module can be configured to use a sliding time window mechanism, for example, a ten-minute window that scrolls forward every 30 seconds, to dynamically count the frequency of invalid operations. The alarm threshold can be set as the upper limit of the number of invalid operations allowed per hour, for example, triggering a reminder when more than 15 invalid operations per hour are detected. The notification data can use a multi-channel transmission strategy, for example, preferentially sending through the local notification system of the device, and synchronizing to the cloud account associated device when the network is connected.

[0102] In the embodiment, by constructing an operation log analysis system, invalid instructions generated due to environmental interference or user misoperation can be actively identified, ensuring the reliability of the cross-device lock screen function while effectively reducing the continuous occupation of system resources by invalid operations. In the embodiment, the method can monitor abnormal patterns in user operation behaviors in real time, and actively initiate a reminder when the false touch behavior reaches a critical value, avoiding waste of device resources or false triggering of security policies due to continuous invalid operations. This mechanism can significantly improve the timeliness and accuracy of false touch identification when the device is in an uncontrolled environment, preventing the risk of system misjudgment caused by the accumulation of invalid operations.

[0103] In the embodiment, the cross-terminal quick screen locking synchronization method in the multi-device cooperative scenario synchronizes the screen locking instruction to the cooperative terminal after the master terminal uniformly generates and verifies the screen locking instruction, realizes one-key screen locking operation of multiple devices, and can improve the screen locking operation efficiency and security of multiple devices.

[0104] It should be noted that the above examples are only used for understanding the present application and do not constitute a limitation on the multi-device cooperative scenario cross-terminal quick screen locking synchronization method of the present application. More forms of simple transformation based on the technical concept are within the protection scope of the present application.

[0105] The present application also provides a cross-terminal quick screen locking synchronization system in a multi-device cooperative scenario, which refers to Figure 2 The cross-terminal quick screen locking synchronization in the multi-device cooperative scenario includes a memory 10, a processor 20, and a cross-terminal quick screen locking synchronization program in the multi-device cooperative scenario stored on the memory 10 and executable on the processor 20. The cross-terminal quick screen locking synchronization program in the multi-device cooperative scenario is configured to implement the steps of the cross-terminal quick screen locking synchronization method in the multi-device cooperative scenario.

[0106] The cross-terminal quick screen locking synchronization system in the multi-device cooperative scenario provided by the present application adopts the cross-terminal quick screen locking synchronization method in the multi-device cooperative scenario in the above embodiment, which can improve the screen locking operation efficiency and security of multiple devices. Compared with the prior art, the cross-terminal quick screen locking synchronization system in the multi-device cooperative scenario provided by the present application has the same beneficial effects as the cross-terminal quick screen locking synchronization method in the multi-device cooperative scenario provided by the above embodiment, and other technical features in the cross-terminal quick screen locking synchronization system in the multi-device cooperative scenario are the same as the features disclosed in the above embodiment method. Therefore, no further description is given here.

[0107] The above only describes some embodiments of the present application, and does not limit the patent scope of the present application. Any equivalent structural transformation based on the technical concept of the present application, or direct / indirect application in other related technical fields is included in the patent protection scope of the present application.

Claims

1. A method for cross-terminal quick screen lock synchronization in a multi-device collaborative scenario, characterized in that, The method includes: Raw touch event data is obtained through the touchscreen of the main control terminal; The original touch event data is validated based on preset rules to obtain valid operation command data; Generate local screen lock command data based on valid operation command data, and execute the screen lock action of the main control terminal; Transmit local lock screen command data to at least one collaborative terminal via the device collaboration network; Based on the collaborative terminal, a synchronous screen locking action is performed on the received screen locking command data; The step of performing validity verification processing on the original touch event data based on preset rules to obtain valid operation command data includes: Extract coordinate position data from raw touch event data; The coordinate position data is compared and verified with the coordinate range of the blank area on the screen to obtain the area verification result data; Identify the time interval data of continuous touch events based on the area verification result data; When the time interval data meets the preset double-click threshold range and the area verification result data is a blank area, valid operation instruction data is generated. The step of comparing and verifying the coordinate position data with the coordinate range of the blank area on the screen to obtain the area verification result data includes: Obtain the current screen layout data through the system interface; Based on layout data parsing, the set of coordinate ranges for interactive controls is analyzed. Perform overlapping operations on the coordinate position data and the set of coordinate ranges of interactive controls; If the coordinate location data is not included in the coordinate range of any interactive control, the output area verification result data will be a blank area.

2. The cross-terminal quick screen lock synchronization method in a multi-device collaborative scenario as described in claim 1, characterized in that, The steps of performing a synchronized screen-locking action based on the received screen-locking command data by the collaborative terminal include: The device authentication protocol is used to verify the identity and legitimacy of the collaborative terminal in order to obtain the device authentication result data; When the device authentication result data indicates that the device is legitimate, the local lock screen command data is encapsulated into an encrypted transmission data packet; Based on the status detection data of the device collaborative network, select a real-time transmission channel or an offline cache queue; Send encrypted data packets to the cooperating terminal through the selected channel.

3. The cross-terminal quick screen lock synchronization method in a multi-device collaborative scenario as described in claim 2, characterized in that, The steps for selecting a real-time transmission channel or an offline cache queue for status detection data based on a device collaborative network include: Periodically acquire signal strength and latency data of the device collaborative network; When the signal strength data is below the threshold or the delay data exceeds the threshold, the encrypted transmission data packet is written to the offline buffer queue; When the signal strength data recovers to above the threshold, the data packets in the offline cache queue will be pushed to the collaborative terminal in batches.

4. The cross-terminal quick screen lock synchronization method in a multi-device collaborative scenario as described in claim 1, characterized in that, After the step of generating local lock screen instruction data based on valid operation instruction data and executing the lock screen action of the main control terminal, the method further includes: The device's attitude data is collected via sensors on the main control terminal. If the posture data indicates that the device is in a flat position, then power saving mode is enabled to perform the screen lock action; The device posture data is attached to the local lock screen command data and synchronized to the collaborative terminal.

5. The cross-terminal quick screen lock synchronization method in a multi-device collaborative scenario as described in claim 1, characterized in that, The steps of performing a synchronized screen-locking action based on the received screen-locking command data by the collaborative terminal include: The integrity of the received screen lock command data is verified through the collaborative terminal; If the verification passes, then parse the device identification data in the instruction; Match the local terminal configuration file based on the device identification data; The screen lock action is performed based on the security policy data in the configuration file.

6. The cross-terminal quick screen lock synchronization method in a multi-device collaborative scenario as described in claim 5, characterized in that, The security policy data requires biometric authentication; the step of performing the screen lock action based on the security policy data in the configuration file includes: Activate the fingerprint sensor to acquire biometric data; The biometric data is matched and verified against the pre-stored template data; When a match is successful, the screen off circuit control signal is triggered to perform the screen lock action.

7. The cross-terminal quick screen lock synchronization method in a multi-device collaborative scenario as described in claim 1, characterized in that, The method further includes: When the main control terminal does not detect valid operation command data, the generated operation log data is stored in the local cache; Analyze the frequency data of consecutive invalid operations in the operation log data; If the frequency data exceeds the alarm threshold, a notification of accidental touch will be sent to the user's device.

8. A cross-terminal quick screen lock synchronization system for multi-device collaboration scenarios, characterized in that, The cross-terminal quick lock screen synchronization in the multi-device collaboration scenario includes: a memory, a processor, and a cross-terminal quick lock screen synchronization program for the multi-device collaboration scenario stored on the memory and capable of running on the processor. The cross-terminal quick lock screen synchronization program for the multi-device collaboration scenario is configured to implement the steps of the cross-terminal quick lock screen synchronization method for the multi-device collaboration scenario as described in any one of claims 1 to 7.

Images