Security patch detection method and terminal equipment
By determining the security patch integration status on the terminal device and outputting prompts, the problem of security patch delays is solved, improving device security and the timeliness of user operations, and reducing security risks.
Patent Information
- Application Number
- CN202310580956.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-22
- Publication Date
- 2024-11-22
AI Technical Summary
In existing technologies, the delayed integration of security patches poses security risks to terminal devices, and users are unwilling to upgrade, resulting in significant security vulnerabilities to data and privacy.
The system determines the security patch integration status based on the system time and the security patch release time of the terminal device, and outputs a prompt message in case of delay to remind the user to integrate the security patch in time.
This reduces the probability of security patch delays, improves the security of terminal devices, ensures that users are aware of and can perform patch integration operations in a timely manner, and reduces security risks.
Smart Images

Figure CN119004444A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network security technology, and in particular to a security patch detection method and terminal device. Background Art
[0002] Security patches are security improvement patches regularly provided to smart terminal device manufacturers. They are a public, monthly push "security upgrade" service. These security patches not only improve the security and privacy of terminal devices, but also often aim to correct errors, improve system stability and daily optimization to eliminate potential vulnerabilities.
[0003] However, there is a problem with the integration lag of the above security patches. Summary of the invention
[0004] The present application provides a security patch detection method and terminal device, which reduces the probability of security patch lag.
[0005] In a first aspect, a security patch detection method is provided, which is applied to a terminal device, and the method comprises: judging the security patch integration status of the terminal device according to the system time and the security patch release time; and outputting a security patch delay prompt message when it is determined that the terminal device is in a security patch integration delay state.
[0006] In this application, the terminal device can determine the security patch integration status of the terminal device according to the system time and the security patch release time; and when it is determined that the security patch integration is delayed, a prompt message of the security patch delay is output. In other words, the user can learn from the prompt message of the security patch delay that the current terminal device may have security risks, which can prompt the user to perform the security patch integration operation as soon as possible, or avoid events involving important information, thereby reducing the probability of security patch delay and improving the security of the terminal device.
[0007] In a second aspect, a terminal device is provided, which includes: a judgment module and a processing module, wherein the judgment module is used to judge the security patch integration status of the terminal device according to the system time and the security patch release time; the above-mentioned processing module is used to output a prompt information of security patch delay when it is determined that the terminal device is in a security patch integration delay state.
[0008] In a third aspect, another terminal device is provided, including a processor, the processor is coupled to a memory, and can be used to execute instructions in the memory to implement the method in any possible implementation of the first aspect. Optionally, the terminal device also includes a memory. Optionally, the terminal device also includes a communication interface, and the processor is coupled to the communication interface.
[0009] In a fourth aspect, a processor is provided, comprising: an input circuit, an output circuit and a processing circuit. The processing circuit is used to receive a signal through the input circuit and transmit a signal through the output circuit, so that the processor executes the method in any possible implementation of the first aspect.
[0010] In the specific implementation process, the processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a trigger, and various logic circuits. The input signal received by the input circuit can be, for example, but not limited to, received and input by a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter, and the input circuit and the output circuit can be the same circuit, which is used as an input circuit and an output circuit at different times. The embodiments of the present application do not limit the specific implementation methods of the processor and various circuits.
[0011] In a fifth aspect, a processing device is provided, comprising a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in any possible implementation of the first aspect.
[0012] Optionally, there are one or more processors and one or more memories.
[0013] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.
[0014] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated with the processor on the same chip or can be set on different chips respectively. The embodiments of the present application do not limit the type of memory and the setting method of the memory and the processor.
[0015] It should be understood that the relevant data interaction process, such as sending indication information, can be a process of outputting indication information from a processor, and receiving capability information can be a process of receiving input capability information from a processor. Specifically, the processed output data can be output to a transmitter, and the input data received by the processor can come from a receiver. Among them, the transmitter and the receiver can be collectively referred to as a transceiver.
[0016] The processing device in the fifth aspect mentioned above can be a chip. The processor can be implemented by hardware or by software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor or can be located outside the processor and exist independently.
[0017] In a sixth aspect, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute a method in any possible implementation of the first aspect.
[0018] In a seventh aspect, a computer-readable storage medium is provided, which stores a computer program (also referred to as code, or instructions) which, when executed on a computer, enables the computer to execute a method in any possible implementation of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] Figure 1 is a flow chart of a method for incorporating a security patch;
[0020] Figure 2 is a schematic diagram of an interface of a terminal device provided in an embodiment of the present application;
[0021] Figure 3 A schematic diagram of the system architecture of a terminal device provided in an embodiment of the present application;
[0022] Figure 4 is a flow chart of a security patch detection method provided in an embodiment of the present application;
[0023] Figure 5 is a flowchart of a first specific example of a method for detecting a security patch provided in an embodiment of the present application;
[0024] Figure 6 is a schematic diagram of an interface of a terminal device provided in an embodiment of the present application;
[0025] Figure 7 is a schematic diagram of an interface of a terminal device provided in an embodiment of the present application;
[0026] Figure 8 is a schematic diagram of an interface of a terminal device provided in an embodiment of the present application;
[0027] Fig. 9 is a flowchart of another specific example of the security patch detection method provided in an embodiment of the present application;
[0028] Fig.10is a schematic diagram of an interface of a terminal device provided in an embodiment of the present application;
[0029] Fig.11 is a schematic diagram of an interface of a terminal device provided in an embodiment of the present application;
[0030] Fig.12 is a schematic diagram of an interface of a terminal device provided in an embodiment of the present application;
[0031] Fig.13 is a structural block diagram of an example of a terminal device provided in an embodiment of the present application;
[0032] Fig.14 It is a structural diagram of another example of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0033] The technical solution in this application will be described below in conjunction with the accompanying drawings.
[0034] Security patches are security improvement patches regularly provided to smart terminal device manufacturers. They are a public, monthly push "security upgrade" service. These security patches not only improve the security and privacy of terminal devices, but also often aim to correct errors, improve system stability and daily optimization to eliminate potential vulnerabilities.
[0035] Figure 1 FIG. 1 is a flow chart of a current security patch integration method 100. Figure 1 As shown, the method 100 may include the following steps:
[0036] S101, a first device issues a security patch, and correspondingly, a second device receives the security patch.
[0037] Exemplarily, the first device may be a device corresponding to Google or Vendor, and the second device may be a device corresponding to the manufacturer of the terminal device.
[0038] S102: The second device adapts to the security patch.
[0039] S103, the second device releases and pushes the security patch to the terminal device. The terminal device receives the security patch.
[0040] S104, the terminal device integrates the security patch.
[0041] Exemplarily, the terminal device may receive the security patch via over-the-air download technology OTA, and may integrate the security patch by upgrading the OTA version.
[0042] Figure 2 FIG. 2 shows an interface 200 of a terminal device. Figure 2As shown, the interface 200 displays the OTA version received by the terminal device. When the user clicks the "Upgrade Now" function button, the terminal device can generate an instruction to upgrade the OTA version and execute the operation corresponding to the instruction to integrate the security patches that may exist in the OTA version.
[0043] However, currently the vast majority of users (such as middle-aged and elderly users) do not understand the relationship between OTA versions and security patches. At the same time, some users may be unwilling to upgrade for reasons such as the time-consuming nature of the upgrade and the possible system freezes after the upgrade, resulting in a lag in security patches, posing huge security risks to users' data assets and privacy data.
[0044] In view of this, the embodiment of the present application provides a security patch detection method and terminal device, the terminal device can determine the security patch integration status of the terminal device according to the system time and the security patch release time; and when it is determined that the security patch integration is delayed, a prompt message of the security patch delay is output. In other words, the user can learn from the prompt message of the security patch delay that the current terminal device may have security risks, which can prompt the user to perform the security patch integration operation as soon as possible, or avoid events involving important information, thereby reducing the probability of security patch delay and improving the security of the terminal device.
[0045] It should be understood that the terminal device in the embodiments of the present application may also be referred to as: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc. The terminal device involved in the embodiments of the present application may be a device that provides voice / data connectivity to a user, for example, a handheld device with a wireless connection function, a vehicle-mounted device, etc. At present, some examples of terminals are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (public land mobile communication networks) Mobile network, PLMN) and the like, the embodiments of the present application are not limited to this.
[0046] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
[0047] In addition, in the embodiments of the present application, the terminal device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing human-machine interconnection and intelligent network of things-to-things interconnection. The terminal device of the present application can also be a vehicle-mounted unit, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit built into the vehicle as one or more components or units. The vehicle can implement the method of the present application through the built-in vehicle-mounted unit, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit. Therefore, the embodiments of the present application can be applied to vehicle networking, such as vehicle to everything (V2X), long-term evolution-vehicle (LTE-V), vehicle-to-vehicle (V2V), etc.
[0048] For example, Figure 3 A schematic diagram of the system architecture of a terminal device provided in an embodiment of the present application.
[0049] like Figure 3 As shown, the terminal device includes a processor 310, a transceiver 320 and a display unit 370. The display unit 370 may include a display screen.
[0050] Optionally, the terminal device may further include a memory 330. The processor 310, the transceiver 320 and the memory 330 may communicate with each other through an internal connection path to transfer search data. The memory 330 is used to store computer programs, and the processor 310 is used to call and run the computer program from the memory 330.
[0051] The processor 310 and the memory 330 may be combined into a processing device, or more commonly, they are independent components, and the processor 310 is used to execute the program code stored in the memory 330 to implement the above functions. In specific implementation, the memory 330 may also be integrated into the processor 310, or may be independent of the processor 310.
[0052] In addition, in order to make the functions of the terminal device more complete, the terminal device may further include one or more of an input unit 360 , an audio circuit 380 , and a sensor 301 .
[0053] Optionally, the terminal device may further include a power supply 350 for providing power to various devices or circuits in the terminal device.
[0054] Understandably, Figure 3 The operations and / or functions of each module in the terminal device shown are respectively for implementing the corresponding processes in the following method embodiments. For details, please refer to the description in the following method embodiments. To avoid repetition, detailed description is appropriately omitted here.
[0055] Understandably, Figure 3 The processor 310 in the terminal device shown may include one or more processing units, for example: the processor 310 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and / or a neural-network processing unit (neural-network processing unit, NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.
[0056] The processor 310 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 310 is a cache memory. The memory may store instructions or data that the processor 310 has just used or cyclically used. If the processor 310 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 310, and thus improves the efficiency of the system.
[0057] In some embodiments, the processor 310 may include one or more interfaces. The interface 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, etc.
[0058] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the terminal device. In other embodiments of the present application, the terminal device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.
[0059] Understandably, Figure 3 The power supply 350 shown is used to supply power to the processor 310 , the memory 330 , the display unit 370 , the input unit 360 , the transceiver 320 , and the like.
[0060] The transceiver 330 can provide wireless communication solutions for terminal devices, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc. The transceiver 320 can be one or more devices integrating at least one communication processing module.
[0061] The terminal device implements the display function through a GPU, a display unit 370, and an application processor. The GPU is a microprocessor for image processing, connecting the display unit 370 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 310 may include one or more GPUs that execute program instructions to generate or change display information.
[0062] The display unit 370 is used to display images, videos, etc. (such as the search interface of the present application). The display unit 370 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 or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light emitting diode (QLED), etc.
[0063] The memory 330 can be used to store computer executable program codes, which include instructions. The memory 330 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the terminal device (such as search data), etc. In addition, the memory 330 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. The processor 310 executes various functional applications and data processing of the terminal device by running instructions stored in the memory 330 and / or instructions stored in a memory provided in the processor.
[0064] The terminal device can realize audio functions such as music playing and recording through the audio circuit 380 and the application processor.
[0065] The technical solution in this application will be described below in conjunction with the accompanying drawings.
[0066] In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit the difference.
[0067] It should be noted that, in this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplarily" or "for example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a specific way.
[0068] In addition, "at least one" means one or more, and "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.
[0069] In order to make the purpose and technical solution of this application clearer and more intuitive, the following will be combined with the accompanying drawings and embodiments to describe in detail a security patch detection method and terminal device provided by the embodiment of this application. It should be understood that the specific embodiments described here are only used to explain this application and are not used to limit this application.
[0070] Figure 4 4 is a schematic flow chart of a security patch detection method 400 provided in an embodiment of the present application. Figure 4 As shown, the method 400 may include the following steps:
[0071] S401, the terminal device determines the security patch integration status of the terminal device according to the system time and the security patch release time.
[0072] In a possible implementation, the terminal device can obtain the system time through networking, and obtain the security patch release time by reading "getpropro.build.version.security_patch".
[0073] It should be understood that the system time can be understood as the current time. The security patch release time can be the release time of the most recent security patch integrated into the terminal device, or the release time of the latest security patch before the terminal device leaves the factory.
[0074] In a possible case, the terminal device may execute the above S401 when a preset event is detected, or the terminal device may also periodically execute the above S401, which is not limited in the present application.
[0075] In a possible implementation, the terminal device may determine the security patch integration status of the terminal device according to the time difference between the security patch release time and the system time.
[0076] S402: When the terminal device determines that the security patch integration is delayed, the terminal device outputs a prompt message indicating that the security patch is delayed.
[0077] In a possible implementation, the terminal device may display a prompt message indicating that the security patch is delayed through an interface.
[0078] In another possible implementation, the terminal device may also play the prompt information that the security patch is delayed by voice, which is not limited in this application.
[0079] In this application, the terminal device can determine the security patch integration status of the terminal device according to the system time and the security patch release time; and when it is determined that the security patch integration is delayed, a prompt message of the security patch delay is output. In other words, the user can learn from the prompt message of the security patch delay that the current terminal device may have security risks, which can prompt the user to perform the security patch integration operation as soon as possible, or avoid events involving important information, thereby reducing the probability of security patch delay and improving the security of the terminal device.
[0080] It should be understood that the terminal device can receive and integrate the security patch through the over-the-air OTA technology. The terminal device can periodically receive the above OTA version. Corresponding to the above S401, the terminal device can consider the reception period of the OTA version based on the above security patch release time and system time to improve the accuracy of the judgment of the security patch integration status of the terminal device. For details, see the following Figure 5 Description.
[0081] Figure 5 FIG. 5 is a schematic flow chart of a security patch detection method 500 provided in an embodiment of the present application. Figure 5 As shown, the method 500 may include the following steps:
[0082] S501: The terminal device calculates the time period during which the security patch has been released according to the system time and the security patch release time.
[0083] It should be understood that the security patch release time may be the release time of the most recent security patch merged into the terminal device, i.e. the terminal device may update and store the release time after merging the security patch. Alternatively, it may be the release time of the latest security patch before the terminal device leaves the factory, i.e. the relevant personnel may store the security patch release time in the terminal device when the terminal device leaves the factory.
[0084] Exemplarily, the terminal device can obtain the current time, ie, the above-mentioned system time, through networking.
[0085] Exemplarily, the terminal device may obtain the security patch release time by reading “getpropro.build.version.security_patch”.
[0086] Exemplarily, the terminal device may subtract the system time from the security patch release time to obtain the security patch release time period, that is, the security patch release time period from the current moment.
[0087] S502: The terminal device determines the security patch integration status of the terminal device based on the release time period of the security patch and the receiving cycle of the over-the-air OTA version.
[0088] In a possible implementation, the terminal device may determine the security patch integration status of the terminal device by comparing the release time period of the security patch and the receiving period of the over-the-air OTA version.
[0089] Optionally, before S502, the terminal device may also determine the receiving cycle of the corresponding OTA version based on the type of the device, so as to further improve the accuracy of the judgment on the security patch integration status of the terminal device.
[0090] S503: When the terminal device determines that the security patch integration is delayed, the terminal device outputs a prompt message indicating that the security patch is delayed.
[0091] Exemplarily, when it is determined that the released time period of the security patch is greater than the receiving period of the over-the-air OTA version, it can be determined that the terminal device is in a security patch integration lag state.
[0092] Optionally, the terminal device may also determine that the terminal device is not in a security patch integration lag state when it is determined that the released time period of the security patch is less than or equal to the receiving period of the over-the-air OTA version.
[0093] Optionally, to improve user experience, following 402 or S503, the terminal device may further display a prompt message indicating that the security patch is delayed on the interface, so that the user can quickly learn about the security patch integration status of the terminal device.
[0094] Figure 6 Schematic diagram of the interface 600 of the terminal device provided in the embodiment of the present application. Figure 6 As shown in the figure, the interface displays a prompt message of "Security patch lag". Users can quickly learn about the current security patch integration status of the terminal device through this interface, so as to take upgrade measures in time to avoid the security patch lag from worsening and affecting the device security and normal use of users.
[0095] It should be understood that the above Figure 6 The specific content of the security patch delay prompt information shown is only exemplary, and the specific content of the security patch delay prompt information can also be set according to specific needs, and this application does not limit this.
[0096] Optionally, following the above S503, the terminal device may also determine whether there is a received OTA version currently, and if it is determined that there is no received OTA version currently, the terminal device may also display a first pop-up window, in which a prompt message for booking an OTA version upgrade and a function button for implementing a booking an OTA version upgrade may be displayed, as follows: Figure 7 shown.
[0097] Figure 7 This is an interface 700 of a terminal device provided in an embodiment of the present application. Figure 7 As shown, a pop-up window (i.e., the first pop-up window mentioned above) is displayed on the interface 700, and the prompt information of "Appointment to upgrade OTA version" and the first function button are displayed in the first pop-up window. The user can learn about the OTA version that has not been received at present through the first pop-up window, but can make an appointment for the terminal device to automatically upgrade the next received OTA version, so as to avoid the user forgetting to manually upgrade the next received OTA version, resulting in a possible delay in the integration of the security version in the OTA version. The user can click on the first function button, and the terminal device generates an instruction to make an appointment to upgrade the OTA version when detecting the click operation on the first function button, and executes the upgrade operation corresponding to the instruction when the OTA version is received. In other words, when the terminal device receives the OTA version, it can automatically and timely perform the upgrade operation without the user's perception and operation, thereby reducing the probability of a possible delay in the integration of security patches in the OTA version and improving device security.
[0098] Optionally, if the user does not click the first function button, the terminal device can determine that the user has no need to make an appointment to upgrade the OTA version, and the terminal device can restore the interface used by the user.
[0099] Optionally, in addition to the first function button shown above, the terminal device can also display other function buttons so that when the terminal device detects that the user clicks the other function button, it can determine that the user has no need to make an appointment to upgrade the OTA version and can restore display of the interface used by the user.
[0100] It should be understood that the above user operations can all be detected within a preset time period, and the user operation "click" shown above is only exemplary, and this application does not limit this.
[0101] It should also be understood that the first pop-up window can be displayed in the above Figure 6 The interface shown may also be displayed on other interfaces, and this application does not limit this.
[0102] Optionally, following the above S503, when determining whether there is a received OTA version, and when determining that there is a received OTA version, the terminal device may further display a second pop-up window, in which a prompt message for upgrading the OTA version and a function button for implementing the upgrade of the OTA version may be displayed, as follows: Figure 8 shown.
[0103] Figure 8 The interface 800 of the terminal device provided in the embodiment of the present application. Figure 8 As shown, a pop-up window (i.e., the second pop-up window mentioned above) is displayed on the interface 800, and the pop-up window displays a prompt message of "upgrade the current OTA version" and a second function button for upgrading the current OTA version. The user can learn about the currently received OTA version through the prompt message of the second pop-up window. In order to avoid the delay in the integration of security patches that may exist in the OTA version due to not upgrading the current OTA version, which affects the device security, the user can click the second function button. Correspondingly, when the terminal device detects a click operation on the second function button mentioned above, it can generate an instruction to upgrade the current OTA version and execute the operation corresponding to the instruction to reduce the probability of delayed integration of security patches and improve device security.
[0104] Optionally, when no user operation (such as the click operation) on the second function button is detected, the terminal device resumes displaying the interface used by the user.
[0105] Optionally, the terminal device may also display other function buttons, such as a third function button, and when a user operation on the third function button is detected, the terminal device may restore the display of the interface used by the user.
[0106] It should be understood that the above user operation can be detected within a preset time period, and the user operation "click" shown is only exemplary, and the present application does not limit this.
[0107] It should also be understood that the second pop-up window can be displayed in the above Figure 6 The interface shown may also be displayed on other interfaces, and this application does not limit this.
[0108] It should be understood that the terminal device can also determine the integration status of the security patch by referring to whether there is a received OTA version currently, so as to further improve the accuracy of determining the integration status of the security patch of the terminal device.
[0109] Fig. 9 FIG. 9 is a schematic flow chart of a security patch detection method 900 provided in an embodiment of the present application. Fig. 9 As shown, the method 900 may include the following steps:
[0110] S901: The terminal device calculates the time period during which the security patch has been released according to the system time and the security patch release time.
[0111] It should be understood that S901 is similar to S501 above, and the specific details can be referred to above. Figure 5 To avoid repetition, the description of S501 is not repeated here.
[0112] S902, the terminal device determines whether the released time period of the above security patch is greater than the receiving period of the over-the-air OTA version.
[0113] It should be understood that there may be multiple receiving periods for the above-mentioned OTA version, and the terminal device may determine the receiving period for obtaining the corresponding OTA version based on the type of the device.
[0114] S903: When the terminal device determines that the released time period of the security patch is greater than the receiving period of the OTA version downloaded over the air, it determines whether there is a received OTA version currently.
[0115] S904: When there is a received OTA version, the terminal device determines that the security patch integration is delayed, and outputs a prompt message indicating that the security patch is delayed.
[0116] Optionally, following S904, the terminal device may also display a prompt message that the security patch is delayed. For details, see the above description. Figure 6 To avoid repetition, the description will not be repeated here.
[0117] Optionally, following the above S904, in the case where the received OTA version currently exists, the terminal device may also display a prompt message for upgrading the OTA version and a function button for upgrading the OTA version. For details, see the above Figure 8 To avoid repetition, the description will not be repeated here.
[0118] Optionally, following the above S402, S503 or S904, the terminal device may also determine the type of the currently ongoing event, and when determining that the currently ongoing event is a security event, close the currently ongoing event to avoid losses to the user.
[0119] Fig.10 The interface 1000 of the terminal device provided in the embodiment of the present application. Fig.10 As shown, interface a in the terminal device interface 1000 is a payment interface. In this case, if the terminal device determines that the terminal device is in a security patch integration lag state, the user can be prompted with the security patch integration status of the terminal device through the above-mentioned security patch lag prompt information, and the currently displayed payment interface can also be closed, thus ending the payment event.
[0120] As described in interface b, the interface displays a prompt message of "security patch delayed", and the interface is an interface other than the above-mentioned payment interface, such as an application desktop, etc., to indicate that the current payment event has been ended.
[0121] Optionally, to avoid directly ending the security event "such as a payment event" and causing a bad user experience, the terminal device can close the payment interface after reminding the user that the terminal device is in the first time period after the security patch is integrated.
[0122] Fig.11 The interface 1100 of the terminal device provided in the embodiment of the present application. Fig.11 As shown, interface a in the terminal device interface 1100 is a payment interface. In this case, if the terminal device determines and confirms that the security patch is in a delayed state, the user can be prompted with the security patch prompt information of the current security patch integration status of the terminal device and the currently displayed payment interface can be closed, thereby ending the payment event.
[0123] As described in interface b, the interface displays a payment interface and a prompt message of "security patch delayed". When it is determined that the prompt message of "security patch delayed" is displayed beyond the above-mentioned first time period, the terminal device ends the above-mentioned payment event.
[0124] As shown in interface c, the interface displays the above-mentioned prompt message of "security patch delayed", and the interface is other interfaces besides the above-mentioned payment interface, such as application desktop, etc., to indicate that the current payment event has been ended.
[0125] Fig.12 The interface 1200 of the terminal device provided in the embodiment of the present application. Fig.12 As shown, interface a in the terminal device interface 1200 is a payment interface. In this case, if the terminal device determines and confirms that the security patch is in a delayed state, the user can be prompted with a security patch delayed prompt message of the security patch integration status of the terminal device and the currently displayed payment interface can be closed, thereby terminating the payment event.
[0126] As described in interface b, this interface is the above-mentioned payment interface, and displays a prompt message of "security patch lag" and a timer. The counter can display the length of time left until the security event ends. When it is determined that the timer displays "0", the terminal device ends the above-mentioned payment event.
[0127] As shown in interface c, the interface displays the above-mentioned prompt message of "security patch delayed", and the interface is other interfaces other than the above-mentioned payment interface, such as the application desktop, to indicate that the current payment event has been ended.
[0128] Optionally, the terminal device can also Fig.10 The interface a, Fig.11 Interface b or Fig.12 The interface b in the figure displays function buttons for managing the currently ongoing security events, so that the user can determine whether to close the security event according to their own needs, thereby improving the user experience.
[0129] Exemplarily, the above-mentioned function buttons may include a fourth function button. When the user is determined to end the security event, the user may click the fourth function button, so that the terminal device may generate the above-mentioned instruction for receiving the current security event based on the user's click operation on the fourth function button, and execute the operation corresponding to the instruction, thereby reducing the probability of losses to users caused by delayed security patches.
[0130] Exemplarily, the above-mentioned function buttons may also include a fifth function button. The user clicks the fifth function button according to his own needs, so that the terminal device can maintain the current security event based on the user's click operation on the fifth function button, thereby improving the user experience.
[0131] Optionally, the terminal device may also determine whether there is a preset time period before outputting the above-mentioned security patch delay prompt information; and if it is determined that the above-mentioned preset time period exists, the terminal device outputs the security patch delay prompt information if the current moment is within the preset time period; or, if it is determined that the above-mentioned preset time period does not exist, the terminal device outputs the security patch delay prompt information in real time.
[0132] Exemplarily, the reminder message that the security patch is delayed may be displayed during the user's non-sleeping time period to avoid affecting the user.
[0133] In a possible implementation, the preset time period may be determined by the terminal device based on a setting operation of the user.
[0134] It should be understood that, in addition to the user settings shown above, the above-mentioned preset time period may also be preset before the terminal device leaves the factory, and this application does not limit this.
[0135] Optionally, the terminal device may also detect that a security event is currently occurring, and trigger the above S401, S501 or S901 to determine the security patch integration status of the terminal device to avoid losses to the user.
[0136] Exemplarily, before determining the integration status of the security patch based on the system time and the security patch release time, the terminal device may, upon detecting a first event, determine whether the first event is a security event, and upon determining that the first event is the above-mentioned security event, obtain the above-mentioned system time and security patch time to determine the security patch integration status of the terminal device.
[0137] It should be understood that the above-mentioned security events may be events involving user information, such as payment events, picture transmission events, etc., and this application does not limit them.
[0138] Optionally, the above S401, S501 or S901 may also be executed periodically triggered by the terminal device, which is not limited in the present application.
[0139] It should be understood that the system time and the security patch release time in the above S401, S501 or S901 have the same format, that is, before judging the integration status of the security patch based on the system time and the security patch release time, the terminal device may also perform a format conversion operation on the above system time and / or the security patch release time; and judge the security patch integration status of the terminal device when it is determined that the above system time and the security patch release time are converted into the same format of time.
[0140] Optionally, the prompt information for upgrading the OTA version may also be when the terminal device detects the OTA version (such as the above Figure 2 OTA shown) is displayed if it has not been manually upgraded by the user within a time threshold.
[0141] Optionally, the terminal device may also automatically perform an upgrade operation upon receiving the OTA version to avoid possible security patch delays.
[0142] In a possible implementation, the terminal device may provide an OTA version setting interface, through which the user may configure the terminal device to automatically upgrade the OTA version.
[0143] Optionally, the user can also use the above-mentioned OTA version setting interface to enable the terminal device to automatically upgrade some of the received OTA versions.
[0144] For example, the user can manually set the terminal device to automatically upgrade the OTA version whose size does not exceed the threshold. In the case of receiving an OTA whose file size is greater than or equal to the threshold, the terminal device needs to implement the upgrade under the user's operation.
[0145] It should be understood that the above embodiments may be coupled to each other, and this application does not limit this. Moreover, the size of the sequence number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0146] Combined with the above Figures 1 to 12 , describes in detail the security patch detection method of the present application embodiment, and will be combined with Figure 13 to Figure 14 , describe in detail the terminal device of an embodiment of the present application.
[0147] Fig.13 A terminal device 1300 provided in an embodiment of the present application is shown. The terminal device 1300 includes: a determination module 1301 and a processing module 1302 .
[0148] Among them, the judgment module 1301 is used to: judge the security patch integration status of the terminal device according to the system time and the security patch release time; the processing module 1302 is used to: output a prompt message of security patch delay when it is determined that the terminal device is in a security patch integration delay state.
[0149] Optionally, the judgment module 1301 is used to: calculate the released time period of the above-mentioned security patch according to the above-mentioned system time and the above-mentioned security patch release time; judge the security patch integration status of the terminal device based on the released time period of the above-mentioned security patch and the receiving period of the over-the-air OTA version; wherein the receiving period of the above-mentioned over-the-air OTA version is determined based on the type of the above-mentioned terminal device.
[0150] Optionally, the judgment module 1301 is used to: determine that the terminal device is in a security patch integration lag state when the released time period of the above-mentioned security patch is greater than the receiving period of the above-mentioned OTA version; or determine that the terminal device is not in a security patch integration lag state when the released time period of the above-mentioned security patch is less than or equal to the receiving period of the above-mentioned OTA version.
[0151] Optionally, the processing module 1302 is used to: detect a first event; the judgment module 1301 is used to: judge whether the above-mentioned first event is a security event, and the above-mentioned security event is an event involving user information; when it is determined that the above-mentioned first event is the above-mentioned security event, judge the security patch integration status of the terminal device according to the above-mentioned system time and the above-mentioned security patch release time.
[0152] Optionally, the security patch integration status is judged and determined by the terminal device periodically based on the system time and the security patch release time.
[0153] Optionally, the judgment module 1301 is used to: judge whether there is a preset time period; the processing module 1302 is used to: when it is determined that the above-mentioned preset time period exists, when the current moment is within the above-mentioned preset time period, output a prompt message that the above-mentioned security patch is delayed; or, when it is determined that the above-mentioned preset time period does not exist, output a prompt message that the above-mentioned security patch is delayed in real time; wherein the above-mentioned preset time period is determined by the terminal device based on the user's setting operation, or is preset before the above-mentioned terminal device leaves the factory.
[0154] Optionally, the processing module 1302 is used to: close the currently ongoing security event, where the security event includes an event involving user information.
[0155] Optionally, the processing module 1302 is used to: automatically upgrade the above OTA version when it is determined that the received OTA version currently exists.
[0156] Optionally, the processing module 1302 is used to: when it is determined that a received OTA version currently exists, display a pop-up window, wherein the pop-up window displays prompt information for upgrading the OTA version and a function button for implementing the upgrade of the OTA version.
[0157] Optionally, the processing module 1302 is used to: perform a format conversion operation on the above-mentioned system time and / or the release time of the above-mentioned security patch; the judgment module 1301 is used to: when determining to convert the above-mentioned system time and the release time of the above-mentioned security patch into the time of the same format, judge the security patch integration status of the terminal device according to the above-mentioned system time and the release time of the above-mentioned security patch.
[0158] It should be understood that the terminal device 1300 here is embodied in the form of a functional module. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art may understand that the terminal device 1300 may be specifically the terminal device in the above-mentioned embodiment, or the functions of the terminal device in the above-mentioned embodiment may be integrated in the terminal device 1300, and the terminal device 1300 may be used to execute the various processes and / or steps corresponding to the terminal device in the above-mentioned method embodiment, and to avoid repetition, it will not be repeated here.
[0159] The terminal device 1300 has the function of implementing the corresponding steps performed by the terminal device in the above method; the above functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In the embodiment of the present application, Fig.13 The terminal device 1300 in the embodiment may also be a chip or a chip system, for example, a system on chip (SoC).
[0160] Fig.14 Another terminal device 1400 provided in an embodiment of the present application is shown. The terminal device 1400 includes: a processor 1401 and a memory 1402, a communication interface 1403 and a bus 1404. The memory 1402 is used to store instructions, and the processor 1401 is used to execute the instructions stored in the memory 1402. The processor 1401, the memory 1402 and the communication interface 1403 are connected to each other through the bus 1404.
[0161] The processor 1401 is used to: determine the security patch integration status of the terminal device according to the system time and the security patch release time; and output a security patch delay prompt message when it is determined that the terminal device is in a security patch integration delay state.
[0162] It should be understood that the terminal device 1400 can specifically be the terminal device in the above-mentioned embodiment, the functions of the terminal device in the above-mentioned embodiment can be integrated in the terminal device 1400, and the terminal device 1400 can be used to execute the various steps and / or processes corresponding to the terminal device in the above-mentioned method embodiment.
[0163] Optionally, the memory 1402 may include a read-only memory and a random access memory, and provide instructions and data to the processor 1401. A portion of the memory 1402 may also include a non-volatile random access memory. For example, the memory 1402 may also store information about the device type. The processor 1401 may be used to execute the instructions stored in the memory, and when the processor executes the instructions, the processor 1401 may execute the various steps and / or processes corresponding to the terminal device in the above method embodiment.
[0164] It should be understood that in the embodiments of the present application, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
[0165] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor executes the instructions in the memory, and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.
[0166] Those of ordinary skill 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 to be beyond the scope of this application.
[0167] Those skilled in the art can 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.
[0168] In the several embodiments provided in the present 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 only schematic. For example, the division of the above units is only a logical function division. There may be other division methods in actual implementation, 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.
[0169] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0170] 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.
[0171] If the above 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, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or terminal device, etc.) to perform all or part of the steps of the above methods in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.
[0172] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the above claims.
Claims
1. A method for detecting a security patch, characterized in that: Applied to terminal equipment, including: Determining the security patch integration status of the terminal device according to the system time and the security patch release time; When it is determined that the terminal device is in a security patch integration delay state, a prompt message of the security patch delay is output.
2. The method according to claim 1, characterized in that The determining, according to the system time and the security patch release time, the security patch integration status of the terminal device includes: Calculate the time period of the security patch release according to the system time and the security patch release time; Determining the security patch integration status of the terminal device based on the release time period of the security patch and the receiving period of the over-the-air OTA version; Among them, the receiving period of the OTA version is determined based on the type of the terminal device.
3. The method according to claim 2, characterized in that The determining, based on the released time period of the security patch and the receiving period of the over-the-air OTA version, of the security patch integration status of the terminal device includes: In a case where the time period of the security patch being released is greater than the receiving period of the OTA version, determining that the terminal device is in a security patch integration hysteresis state; or, When the released time period of the security patch is less than or equal to the receiving period of the OTA version, it is determined that the terminal device is not in a security patch integration hysteresis state.
4. The method according to claim 1, characterized in that: Before determining the security patch integration status of the terminal device according to the system time and the security patch release time, the method further includes: A first event is detected; Determining whether the first event is a security event, wherein the security event is an event involving user information; The determining, according to the system time and the security patch release time, the security patch integration status of the terminal device includes: When it is determined that the first event is the security event, the security patch integration status of the terminal device is determined according to the system time and the security patch release time.
5. The method according to claim 1, characterized in that The security patch integration status is judged and determined by the terminal device periodically according to the system time and the security patch release time.
6. The method according to claim 1, characterized in that Before outputting the prompt information that the security patch is delayed, the method further includes: Determine whether there is a preset time period; The output of the security patch delay prompt information includes: If it is determined that the preset time period exists, when the current time is within the preset time period, outputting a prompt message that the security patch is delayed; or, When it is determined that the preset time period does not exist, outputting prompt information that the security patch is delayed in real time; The preset time period is determined by the terminal device based on the setting operation of the user, or is preset before the terminal device leaves the factory.
7. The method according to claim 1 or 6, characterized in that: The method further comprises: Closes currently ongoing security events, including events involving user information.
8. The method according to claim 7, characterized in that The method further comprises: In the case where it is determined that there is currently a received over-the-air OTA version, the OTA version is automatically upgraded.
9. The method according to any one of claims 1, 6 or 7, characterized in that: The method further comprises: When it is determined that there is currently a received over-the-air OTA version, a pop-up window is displayed, in which prompt information for upgrading the OTA version and a function button for implementing the upgrade of the OTA version are displayed.
10. The method according to claim 1, characterized in that Before determining the security patch integration status of the terminal device according to the system time and the security patch release time, the method further includes: Performing a format conversion operation on the system time and / or the release time of the security patch; The determining, according to the system time and the security patch release time, the security patch integration status of the terminal device includes: When it is determined that the system time and the security patch release time are converted into time in the same format, the security patch integration status of the terminal device is determined according to the system time and the security patch release time.
11. A terminal device, characterized in that: include: A determination module, used to determine the security patch integration status of the terminal device according to the system time and the security patch release time; The processing module is used to output a prompt message of security patch delay when it is determined that the terminal device is in a security patch integration delay state.
12. A terminal device, characterized in that: The system comprises a processor and a memory, wherein the memory is used to store code instructions, and the processor is used to run the code instructions to execute the method according to any one of claims 1 to 10.
13. A chip, characterized in that: The system comprises a processor and a memory, wherein the memory is used to store code instructions, and the processor is used to run the code instructions to execute the method according to any one of claims 1 to 10.
14. A computer-readable storage medium, characterized in that: Used to store a computer program, the computer program comprising instructions for implementing the method according to any one of claims 1 to 10.
15. A computer program product, comprising computer program code, characterized in that: When the computer program code is executed on a computer, the computer is caused to implement the method according to any one of claims 1 to 10.
