Charging management method, apparatus, device, and medium

Abstract

The application discloses a charging management method and device, equipment and medium, and relates to the technical field of charging. The method comprises the following steps: in response to the access of the charging device being monitored, the device type of the charging device is determined according to historical operation programs; in the case that the device type of the charging device is the shared charging device, the privacy risk item corresponding to the shared charging device is determined through system broadcast, the privacy risk item is used to represent the privacy type that exists the risk of leakage caused by the shared charging device; and the privacy risk item of the shared charging device is displayed. The application can detect whether the shared charging device will cause the leakage of the privacy of the mobile terminal when the charging device is the shared charging device.

Description

Technical Field

[0001] This application relates to the field of charging technology, and in particular to a charging management method, device, equipment and medium. Background Technology

[0002] Charging equipment can be divided into two types: shared charging equipment and private charging equipment. Shared charging equipment includes, but is not limited to, at least one of the following: shared power banks, shared charging cabinets, and charging massage chairs in public places such as bus stations, high-speed rail stations, and airports.

[0003] Taking shared power banks as an example, the relevant technology requires users to scan a QR code on the shared charging cabinet using a mobile app before using the power bank. The charging cabinet contains multiple usable shared power banks. After the user confirms the use of the power bank on the app, one of the power banks in the cabinet becomes available. The user can then retrieve the available power bank and use it to charge their mobile device.

[0004] Because the charging and data interfaces of mobile terminals are integrated on the same physical interface, such as a USB interface, the charging device may steal private information stored in the mobile device while charging it. Moreover, in reality, criminals have already created malicious shared power banks that exploit the above characteristics to intrude into mobile terminals during charging, steal the privacy of mobile terminals, and damage the information security of mobile terminals. Summary of the Invention

[0005] This application provides a charging management method, apparatus, device, and medium. The method determines the type of charging device, and when the charging device is a shared charging device, it detects whether the charging device will cause privacy leakage of the mobile terminal.

[0006] According to one aspect of this application, a charging management method is provided, the method comprising:

[0007] In response to the detection of a charging device access, the historical running program of the terminal is obtained;

[0008] The device type of the charging device is determined based on the historical messages of the historical running program.

[0009] When the device type of the charging device is the shared charging device, the privacy risk item corresponding to the shared charging device is determined through system broadcast. The privacy risk item is used to indicate the type of privacy that has a risk of leakage due to the shared charging device.

[0010] Display the privacy risk items of the shared charging device, and manage the charging of the terminal based on the privacy risk items.

[0011] According to one aspect of this application, a charging management device is provided, the device comprising:

[0012] The monitoring module is used to obtain the historical running program of the terminal in response to the detection of the charging device access;

[0013] The determination module is used to determine the device type of the charging device based on the historical messages of the historical running program;

[0014] The determining module is further configured to determine the privacy risk item corresponding to the shared charging device through system broadcast when the device type of the charging device is the shared charging device. The privacy risk item is used to indicate the type of privacy that has a risk of leakage due to the shared charging device.

[0015] The display module is used to display the privacy risk items of the shared charging device and to manage the charging of the terminal based on the privacy risk items.

[0016] In an optional design of this application, the determining module is further configured to, in response to the existence of a target program in the historical running program, determine, based on the historical messages of the target program, that the charging device is the shared charging device, and that the target program is a program related to renting the shared charging device.

[0017] In an optional design of this application, the determining module is further configured to, in response to the existence of the target program in the historical running program, acquire and identify the notification bar message of the target program between a second time and a first time, wherein the second time is earlier than the first time; and, in response to the existence of a target keyword in the notification bar message, determine that the device type of the charging device is the shared charging device, wherein the target keyword is a word related to renting the shared charging device.

[0018] In an optional design of this application, the monitoring module is further configured to, in response to detecting the access of the charging device at a first moment, obtain the historical running program that runs within the most recent time period determined based on the first moment.

[0019] In an optional design of this application, the monitoring module is further configured to, in response to detecting the access of the charging device at the first moment, acquire the historical running program located at the top of the application stack between the second moment and the first moment, wherein the second moment is earlier than the first moment; wherein the application stack is a stack used to record the historical running program.

[0020] In an optional design of this application, the determining module is further configured to, when the device type of the charging device is the shared charging device, determine from the system broadcast the charging mode of the shared charging device, wherein the charging mode includes at least one of Universal Serial Bus (USB) charging mode and pure charging mode; determine the status value returned by the USB interface based on the charging mode; and determine the privacy risk item corresponding to the charging device based on the status value.

[0021] In an optional design of this application, the determining module is further configured to determine the privacy risk item corresponding to the charging device based on the state value, including: determining that the shared charging device has at least one of the risks of illegal installation program and clipboard leakage in response to the USB debugging state value being a first value indicating that the USB debugging switch is in the on state; or, determining that the shared charging device has an image leakage risk in response to the image transmission state value being a second value indicating that the image is in a readable state; or, determining that the shared charging device has a file leakage risk in response to the file transmission state value being a third value indicating that the file is in a readable state.

[0022] In an optional design of this application, the determining module is further configured to determine, in response to the USB debug status value being a first value indicating that the USB debug switch is in the on state, that the shared charging device has at least one of the risks of illegal installation program and clipboard leakage.

[0023] In an optional design of this application, the determining module is further configured to obtain device information of the shared charging device, the device information including at least one of rental brand, rental time and rental channel.

[0024] The display module is also used to display the device information and the device type.

[0025] In an optional design of this application, the determining module is further configured to identify the text content of the notification bar message; extract the device information of the shared charging device from the text content; or receive the device information through a first physical port, wherein the first physical port is the physical port through which the shared charging device connects to the mobile terminal.

[0026] According to another aspect of this application, a computer device is provided, comprising: a processor and a memory, wherein the memory stores at least one instruction, at least one program, code set or instruction set, wherein the at least one instruction, at least one program, code set or instruction set is loaded and executed by the processor to implement the charging management method as described above.

[0027] According to another aspect of this application, a computer storage medium is provided, wherein at least one piece of program code is stored in the computer-readable storage medium, the program code being loaded and executed by a processor to implement the charging management method as described above.

[0028] According to another aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the charging management method described above.

[0029] The beneficial effects of the technical solutions provided in this application include at least the following:

[0030] Upon detecting a charging device connection, the system first determines the type of device. If it's a shared charging device, it identifies and displays the privacy risks associated with that device to inform the user. This method addresses the security risks associated with using shared charging devices by introducing risk detection capabilities, automatically detecting the security risks of shared charging devices connected to the phone, and protecting user privacy. Attached Figure Description

[0031] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0032] Figure 1 This is a schematic diagram of the structure of a computer system provided in an exemplary embodiment of this application;

[0033] Figure 2 This is a flowchart illustrating a charging management method provided in an exemplary embodiment of this application;

[0034] Figure 3 This is a schematic diagram of the interface of a charging management method provided in an exemplary embodiment of this application;

[0035] Figure 4 This is a schematic diagram of the interface of a charging management method provided in an exemplary embodiment of this application;

[0036] Figure 5 This is a schematic diagram of the interface of a charging management method provided in an exemplary embodiment of this application;

[0037] Figure 6This is a flowchart illustrating a charging device type determination method provided in an exemplary embodiment of this application;

[0038] Figure 7 This is a schematic diagram of the interface of a notification bar message provided in an exemplary embodiment of this application;

[0039] Figure 8 This is a flowchart illustrating a method for determining privacy risk items provided in an exemplary embodiment of this application;

[0040] Figure 9 This is a schematic diagram of a USB debugging interface provided in an exemplary embodiment of this application;

[0041] Figure 10 This is a schematic diagram of an interface for USB use provided in an exemplary embodiment of this application;

[0042] Figure 11 This is a flowchart illustrating a charging management method provided in an exemplary embodiment of this application;

[0043] Figure 12 This is a schematic diagram of the structure of a charging management device provided in an exemplary embodiment of this application;

[0044] Figure 13 This is a schematic diagram of the structure of a computer device provided in an exemplary embodiment of this application. Detailed Implementation

[0045] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0046] First, let's introduce the terms used in the embodiments of this application:

[0047] A stack, also known as a stack array, is a linear data structure with restricted operations. The restriction is that insertion and deletion operations are only allowed at one end of the linear data structure. This end is called the top of the stack, and the other end is called the bottom of the stack. Inserting a new element into a stack is called pushing, which places the new element on top of the existing top element, making it the new top element. Deleting an element from a stack is called popping, which removes the top element from the stack and makes its adjacent element the new top element.

[0048] Notification bar management: refers to the system used to manage displayed messages in the top display area of ​​the operating system. Correspondingly, the notification bar is the area on the terminal used to display application messages.

[0049] System broadcast: A messaging mechanism on the Android system that pushes events to users.

[0050] An interface is a connection between two different systems or two parts with different characteristics within a system, used to ensure that the two parts with different characteristics can work properly after being connected.

[0051] Status value: This refers to the characters or strings in the return value of the interface, used to indicate the running status of the data interface. For example, a return status value of "401" indicates that the authorization request failed; a return status value of "403" indicates that the request is not allowed.

[0052] USB (Universal Serial Bus): is a serial bus standard and a technical specification for input / output interfaces, widely used in information and communication products such as personal computers and mobile devices.

[0053] When shared charging devices connect to a mobile terminal's physical interface via a data cable, not only can power be transferred, but data transfer may also occur. These physical interfaces include at least one of the following: Micro USB (a type of USB interface), Lightning (an interface type introduced by Apple), Type-C (a type of USB interface), and 30-pin (an interface type introduced by Apple). When shared charging devices transfer data, the following problems may occur: 1. Privacy data such as images and files stored on the mobile terminal may be viewed or copied. 2. Malicious applications or Trojans may be installed on the mobile terminal. 3. The mobile terminal's contacts, SMS messages, and clipboard contents may be maliciously viewed and copied.

[0054] Furthermore, given the current societal reliance on mobile phones, shared charging equipment has gradually become a necessity for users. However, most users have only a superficial understanding of the safety risks associated with shared charging equipment, often finding themselves torn between charging and insurance when using it. On the other hand, with the development of new energy vehicles, shared charging equipment that provides power to these vehicles may also steal user information stored within the vehicles during the charging process, causing losses to users.

[0055] Therefore, in the first stage, this application will detect the device type of the charging equipment to determine if it is a shared charging device. In the second stage, it will detect the potential risks posed by the shared charging device and promptly alert users to the relevant charging risks, guiding them to take actions such as unplugging the device or revoking relevant permissions to avoid unnecessary losses.

[0056] Figure 1 A block diagram of a computer system provided in an exemplary embodiment of this application is shown. The computer system includes a terminal 120 and a charging device 140.

[0057] Terminal 120 has an application for renting shared charging equipment. This application can be a mini-program within an app, a dedicated application, or a web client. Terminal 120 can be at least one of a smartphone, a new energy vehicle, a tablet, an e-book reader, an MP3 player, an MP4 player, a laptop, and a desktop computer. For example, if terminal 120 is a mobile terminal, after receiving a scanned QR code, the user pays the rental fee, confirms the rental of the shared charging equipment, and can then begin using the charging equipment 140. Alternatively, if terminal 120 is a new energy vehicle, it can be directly connected to the shared charging equipment, and after charging is complete, the payment amount is determined based on the amount charged.

[0058] The charging device 140 is connected to the physical interface on the terminal 120 via a data cable. Alternatively, the charging device 140 can also be connected to the terminal 120 via wireless charging technology.

[0059] Charging equipment 140 includes shared charging equipment and non-shared charging equipment. Shared charging equipment includes, but is not limited to, at least one of shared power banks, shared charging cabinets, and charging massage chairs in public places such as bus stations / high-speed rail stations / airports. Users need to use at least one of the following methods to access shared charging equipment: payment currency, points, coins, tokens, payment points, and credit points.

[0060] Figure 2 A flowchart illustrating a charging management method provided in an exemplary embodiment of this application is shown. This method can be... Figure 1 The method, executed by the terminal 120 or a client on the terminal 120, includes the following steps:

[0061] Step 202: In response to the detection of charging device access, obtain the terminal's historical running programs.

[0062] According to the usage steps of shared charging equipment, users need to open a specific target program to rent shared charging equipment. Therefore, when a user uses shared charging equipment, it is very likely that the user has used the aforementioned target program at some point in history.

[0063] In this application embodiment, the charging equipment is categorized into shared charging equipment and non-shared charging equipment (also known as personal charging equipment). Shared charging equipment includes, but is not limited to, at least one of shared power banks, shared charging cabinets, and charging massage chairs in public places such as bus stations / high-speed rail stations / airports.

[0064] Optionally, the presence of a charging device can be determined by listening to the system power connection broadcast (ACTION_POWER_CONNECTED). Upon receiving the system power connection broadcast, the presence of a charging device is confirmed.

[0065] Step 204: Determine the device type of the charging equipment based on the historical messages of the historical operation program.

[0066] Since users may use the target program for other purposes, in order to ensure that the user's purpose in using the target program is to rent shared power banks, we can further determine whether the charging device is a shared charging device based on historical messages.

[0067] Because users accumulate a large number of historical running programs while using mobile terminals, it is necessary to impose time limits on the detection of these historical running programs to prevent some of them from affecting the results. For example, in response to detecting the connection of a charging device at a first moment, the historical running programs located at the top of the application stack between the first and second moments are retrieved. The first moment is the moment when the charging device connection is detected. For example, in response to receiving a system power connection broadcast at the first moment, the connection of the charging device is confirmed.

[0068] The second time slot is earlier than the first time slot. For example, the first time slot is 12:03:00 and the second time slot is 11:59:00.

[0069] Optionally, the duration between the second time point and the first time point conforms to a preset value, which can be set by a technician. For example, if the technician sets the preset value to 1 minute, then when the first time point is 12:00:00, the second time point is 11:59:00, and the duration between the first time point and the second time point conforms to the preset value.

[0070] Optionally, the second time can be determined based on the first time and a preset value. For example, if the preset value is 1 minute and the first time is 12:00:00, then by going back 1 minute from the first time, the second time is 11:59:00.

[0071] Step 206: If the charging device is a shared charging device, determine the privacy risk item corresponding to the shared charging device through system broadcast. The privacy risk item is used to indicate the type of privacy that may be leaked due to the shared charging device.

[0072] System broadcasts are used to enable communication between different processes. For example, when a mobile terminal is connected to a power source and begins charging, a system broadcast is generated. This system broadcast allows the mobile terminal to monitor the charging status and determine whether the mobile terminal has finished charging.

[0073] The privacy risk item indicates the type of privacy risk that may arise from shared charging devices. Optionally, the privacy risk item may include at least one of the following: risk of unauthorized installation of programs, risk of clipboard leakage, risk of image leakage, and risk of file leakage.

[0074] For example, when the file transfer status value (USB_FUNCTION_PTP) broadcast by the system equals 1, it indicates that the file stored on the terminal is in a readable state. In this case, the mobile terminal is at risk of file leakage. Similarly, when the image transfer status value (USB_FUNCTION_MTP) broadcast by the system equals 1, it indicates that the image stored on the mobile terminal is in a readable state. In this case, the terminal is at risk of image leakage. And when the USB debugging status value (USB_FUNCTION_ADB) broadcast by the system equals 1, it indicates that the USB debugging switch is on. With the USB debugging switch on, data can be copied between the terminal and the charging device, applications can be installed on the terminal, log data can be read, etc. In this case, the terminal is at risk of either unauthorized installation of programs or clipboard leakage.

[0075] When a mobile terminal identifies privacy risks associated with a shared charging device via system broadcast, a detection notification bar will be displayed. This notification bar informs the user that the mobile terminal is detecting privacy risks associated with the shared charging device. For example, such as... Figure 3 As shown, when the mobile terminal is detecting privacy risks associated with the shared charging device, a detection notification bar 301 is displayed. The detection notification bar 301 displays the text "Detecting whether the charging device has a risk of information leakage", "Whether it unreasonably reads your contacts", and "Security detection in progress" to inform the user that the mobile terminal is detecting privacy risks associated with the shared charging device.

[0076] Step 208: Display the privacy risk items of the shared charging device, and manage the charging of the terminal according to the privacy risk items.

[0077] Optionally, a brief detection result and viewing control for the shared device can be displayed; in response to a trigger action on the viewing control, a privacy risk item for the shared charging device can be displayed.

[0078] The method of managing terminal charging based on the obtained privacy risk items is not limited here. For example, it could be to display prompts to guide the user to perform corresponding operations; or it could be to automatically perform certain operations, such as revoking certain permissions. The charging management method can be implemented automatically by the terminal or implemented at the user's request.

[0079] To cater to users' operating habits, the charging management method can optionally be automatically determined based on the user's historical operation records. For example, if a user frequently uses the "disable permissions" method to manage the terminal's charging during a historical period, the terminal will automatically adopt the "disable permissions" method to manage the terminal's charging based on the user's historical operation records, thus catering to the user's operating habits and improving human-computer interaction efficiency.

[0080] For example, such as Figure 4 As shown, when a mobile terminal detects a privacy risk associated with a shared charging device, user interface 41 is displayed. Within user interface 41, a brief detection result 401 is shown, containing the text "It is recommended to immediately disconnect this charging device" and "This charging device poses a security risk," informing the user of the privacy risk. The user can further click on control 402 to display user interface 42, which shows detection details 403. Detection details 403 displays privacy risk items and their detection results. For example, displaying "Disable developer permissions for security" indicates that the shared charging device will not affect the mobile terminal's developer permissions, and the mobile terminal's developer permissions are unaffected by the shared charging device; displaying "Is there a risk of reading photos?" indicates that the shared charging device can read photos stored on the mobile terminal, posing a risk of photo leakage.

[0081] For example, such as Figure 5 As shown, when the mobile terminal detects that the shared charging device does not pose a privacy risk, user interface 51 is displayed. User interface 51 displays a brief detection result 501, which includes the text "This charging device is safe" and "Grant permission to accurately identify the device being charged," informing the user that the shared charging device poses no privacy risk and can be used with confidence. The user can further click on control 502 to display user interface 52, which displays detection details 503. Detection details 503 displays privacy risk items and their detection results. For example, displaying "Is it safe to disable developer permissions?" indicates that the shared charging device will not affect the mobile terminal's developer permissions, and the mobile terminal's developer permissions are unaffected by the shared charging device; displaying "Is it safe to read photos?" indicates that the shared charging device cannot read photos on the mobile terminal, and there is no risk of photo leakage.

[0082] In summary, this embodiment, upon detecting the connection of a charging device, first determines the type of the charging device. If the charging device is a shared charging device, it identifies and displays the privacy risks associated with that shared charging device to inform the user. This method addresses the security risks associated with users using shared charging devices by introducing risk detection capabilities, automatically detecting the security risks of shared charging devices connected to the phone to protect user privacy.

[0083] In the following optional embodiments, based on the characteristics of the user interface during the rental of shared charging equipment, when a target program exists in the historical running program and the target keyword exists in the historical messages of the target program, the charging equipment type is considered to be a shared charging equipment. This method can accurately identify the equipment type of the charging equipment.

[0084] Figure 6 A flowchart illustrating a keyword extraction method provided in an exemplary embodiment of this application is shown. This method can be... Figure 1 The method, executed by the terminal 120 or a client on the terminal 120, includes the following steps:

[0085] Step 601: Monitor the connection status of the charging device.

[0086] Optionally, the access status of charging devices can be determined by listening to system broadcasts.

[0087] Step 602: In response to the first moment of listening for the access of the charging device, obtain the historical running program located at the top of the application stack between the second moment and the first moment.

[0088] The first moment is the moment when the charging device is detected to be connected. For example, in response to receiving a system power connection broadcast at the first moment, the connection of the charging device is confirmed.

[0089] The second time slot is earlier than the first time slot. For example, the first time slot is 12:03:00 and the second time slot is 11:59:00.

[0090] Optionally, the duration between the second time point and the first time point conforms to a preset value, which can be set by a technician. For example, if the technician sets the preset value to 1 minute, then when the first time point is 12:00:00, the second time point is 11:59:00, and the duration between the first time point and the second time point conforms to the preset value.

[0091] Optionally, the second time can be determined based on the first time and a preset value. For example, if the preset value is 1 minute and the first time is 12:00:00, then by going back 1 minute from the first time, the second time is 11:59:00.

[0092] An application stack is a stack used to record the running history of programs. Optionally, the application stack also records the running time of historical applications. For example, if program 1 ran on the mobile terminal from 12:00:00 to 12:00:10, program 2 ran on the mobile terminal from 12:00:10 to 12:00:30, and program 3 ran on the mobile terminal from 12:00:30 to 12:01:00, then the order of the historical running programs from the bottom to the top of the application stack during the period from 12:00:00 to 12:01:00 is program 1, program 2, and program 3.

[0093] Step 603: Determine if the target program exists in the historical running program.

[0094] If the target program exists in the historical execution program, proceed to step 604;

[0095] If the target program is not found in the historical running program, proceed to step 605.

[0096] The target program is a program related to renting shared charging equipment. Optionally, the target program is a program that enables interaction between the shared charging equipment and the mobile terminal during the rental process. For example, taking a shared power bank as an example, when renting a shared power bank, program A needs to scan the QR code on the shared power bank cabinet to complete the rental. Scanning the QR code is the process of program A interacting with the shared power bank; therefore, program A is the target program.

[0097] Optionally, the target program is the program related to payment during the rental of shared charging equipment. For example, taking a shared power bank as an example, when renting a shared power bank, the user needs to use program B to pay the rental fee; program B is then the target program.

[0098] The target program can be a mini-program within an app, an application for renting shared charging equipment, or a web client.

[0099] Optionally, the target program is set up by a technician.

[0100] Optionally, the target program is determined based on the functionality that the application can perform. For example, if application A has payment functionality, then application A is set as the target program.

[0101] Optionally, the target program is determined based on the name of the application. For example, if the name of application B is "Power Bank Rental", then application B is set as the target program.

[0102] Step 604: Obtain and identify the notification bar messages of the target program between the second time point and the first time point.

[0103] The notification bar is used to display messages pushed by the application; the pushed messages are the notification bar messages. For example, such as... Figure 7 As shown, Figure 7 Notification bar 701 is shown. Notification bar 701 displays the content of notification bar message 702, which is "Application A payment: Payment points service order confirmed...". Notification bar message 702 is used to inform the user that the payment function of application A has been used.

[0104] Step 605: Determine that the charging device is a non-shared charging device.

[0105] When the target program is not found in the historical running program, the device type of the charging device is determined to be a non-shared charging device.

[0106] Step 606: Determine if the target keyword exists in the notification bar message.

[0107] When the notification message contains the target keyword, proceed to step 607;

[0108] If the target keyword is not found in the notification message, proceed to step 608.

[0109] The target keywords are terms related to renting shared charging equipment. Optionally, the target keywords are set by technical personnel. For example, target keywords include at least one of the following: payment, rental, leasing, use, payment, bill, transaction, order, scan code, charging, sharing, currency, points, gold coins, tokens, payment points, and credit score. For example, taking shared charging equipment as a shared power bank as an example, when renting a shared power bank, program A scans the QR code on the shared power bank cabinet to complete the rental, generating a notification message "Use Company A's shared power bank?" Here, the term "shared power bank" is related to renting shared charging equipment, so "payment points" is a target keyword.

[0110] Optionally, the target keywords are terms related to payment during the rental of shared charging equipment. For example, such as... Figure 7 As shown, the content of notification message 702 is "Program A Payment: Payment Points Service Order Confirmation...", where "Payment Points" is a term related to payment fees, so "Payment Points" is the target keyword.

[0111] Since different words sometimes have the same meaning—for example, the words "payment" and "payment fee" have the same meaning in some scenarios—optionally, a semantic analysis model can be invoked to extract the semantic analysis results of the notification message; based on the semantic analysis results, it can be determined whether the notification message contains the target keyword.

[0112] Step 607: Determine that the charging device type is a shared charging device.

[0113] The notification bar message contains the target keyword, indicating that the charging device is a shared charging device.

[0114] Step 608: Determine that the charging device is a non-shared charging device.

[0115] In response to the notification message indicating that the target keyword was not found, the device type of the charging equipment was determined to be a shared charging device.

[0116] Step 609: Obtain device information for the charging device.

[0117] The equipment information includes at least one of the following: rental brand, rental time, and rental channel. The rental brand refers to the merchant name of the shared charging equipment; the rental time includes at least one of the following: start rental time and end rental time; the rental channel includes at least one of the following: rental location, the application used for rental, and payment method.

[0118] Optionally, the text content of the notification message is identified; device information of the charging device is extracted from the text content; or, device information is received through a first physical port, which is the physical port through which the charging device connects to the mobile terminal.

[0119] Step 610: Display device information and device type.

[0120] Optionally, device information can be uploaded to a server. This device information can be used to conduct a preliminary privacy risk assessment of the charging device. For example, if mobile terminal A determines that a shared charging device from brand B poses a privacy risk, and uploads the device information of that shared charging device to the server, then when a user intends to use a shared charging device from brand B to charge mobile terminal C, the server will, based on the device information of the shared charging device from brand B already stored in the server, preliminarily determine that the shared charging device from brand B poses a privacy risk.

[0121] In summary, this embodiment determines the type of charging device by checking if the target program exists in the historical running programs and if the target program's notification messages contain target keywords. This provides a novel method for determining the type of charging device, enabling rapid identification and allowing the mobile terminal to perform appropriate security checks based on the device type.

[0122] In the following optional embodiments, privacy risks of charging devices are determined through system broadcasting. It should be noted that these optional embodiments can determine privacy risks for both shared and non-shared charging devices. This allows for timely notification of relevant privacy risks to users, guiding them to take actions such as unplugging the device or revoking relevant permissions, thus avoiding unnecessary losses.

[0123] Figure 8 A flowchart illustrating a keyword extraction method provided in an exemplary embodiment of this application is shown. This method can be... Figure 1 The method, executed by the terminal 120 or a client on the terminal 120, includes the following steps:

[0124] Step 801: If the charging device type is a shared charging device, determine the charging method from the system broadcast.

[0125] The charging method includes at least one of Universal Serial Bus (USB) charging and pure charging. In the USB charging method, data transfer and charging can occur simultaneously between the mobile terminal and the shared charging device. In the USB charging method, only charging can occur between the mobile terminal and the shared charging device.

[0126] For example, when listening to the system battery change broadcast (ACTION_BATTERY_CHANGED), if the charging method is USB charging, the system battery change broadcast will carry the system broadcast BATTERY_PLUGGED_USB; if the charging method is USB charging, the system battery change broadcast will carry the system broadcast BATTERY_PLUGGED_AC.

[0127] Step 802: Determine whether the charging method of the shared charging device is USB charging.

[0128] If the shared charging device uses USB charging, proceed to step 803;

[0129] If the shared charging device is a pure charging mode, proceed to step 815.

[0130] Step 803: Determine that the charging method of the shared charging device is USB charging.

[0131] The mobile terminal determines that the charging method of the shared charging device is USB charging.

[0132] Step 804: Determine the status value returned by the USB interface based on the USB charging method.

[0133] When the shared charging device is charging via USB, the status value includes at least one of the following: USB debugging status value, image transfer status value, and file transfer status value. The USB debugging status value indicates whether the USB debugging switch is on; the image transfer status value indicates whether the image is readable; and the file transfer status value indicates whether the file is readable.

[0134] Step 805: Determine if the USB debug status value is the first value.

[0135] If the USB debug status value is the first value, proceed to steps 806 and 807.

[0136] If the USB debug status value is not the first value, proceed to step 808.

[0137] Optionally, the USB debug status value can be determined by listening to the USB status system broadcast. For example, the USB debug status value (USB_FUNCTION_ADB) carried in the USB status system broadcast can be used to read whether the USB debug switch is in the on state.

[0138] For example, such as Figure 9 As shown, Figure 9 This indicates that the USB debugging switch on the mobile device is turned on.

[0139] Step 806: Determine if there is a risk of illegal installation of shared charging equipment.

[0140] The USB debug status value is the first value used to indicate that the USB debug switch is in the on state, indicating that there is a risk of illegal installation program in the shared charging device.

[0141] Step 807: Determine if there is a risk of clipboard leakage in shared charging devices.

[0142] In response to the USB debug status value being the first value used to indicate that the USB debug switch is in the on state, it is determined that there is a risk of clipboard leakage in the shared charging device.

[0143] Step 808: Confirm that there is no risk of privacy leakage from shared charging devices.

[0144] The USB debugging status value is the first value used to indicate that the USB debugging switch is in the on state, ensuring that there is no risk of privacy leakage from the shared charging device.

[0145] Step 809: Determine whether the image transmission status value is the second value.

[0146] If the image transmission status value is the second value, proceed to step 810;

[0147] If the image transmission status value is not the second value, proceed to step 811.

[0148] Optionally, the image transfer status value can be determined by listening to the USB status system broadcast. For example, the image is read to determine if it is in a readable state based on the image transfer status value (USB_FUNCTION_MTP) carried in the USB status system broadcast.

[0149] For example, such as Figure 10 As shown, Figure 10 This indicates that the image transmission status value is not the second value, and the image is in an unreadable state.

[0150] Step 810: Determine if there is a risk of image leakage from shared charging devices.

[0151] In response to the image transmission status value being a second value used to indicate that the image is in a readable state, it is determined that there is a risk of image leakage from the shared charging device.

[0152] Step 811: Determine that there is no risk of image leakage from the shared charging equipment.

[0153] In response to the fact that the image transmission status value is not a second value used to indicate that the image is in a readable state, it is determined that there is no risk of image leakage from the shared charging device.

[0154] Step 812: Determine if the file transfer status value is a third value.

[0155] If the file transfer status value is the third value, proceed to step 813;

[0156] If the file transfer status value is not the third value, proceed to step 814.

[0157] Optionally, the file transfer status value can be determined by listening to the USB status system broadcast. For example, the file transfer status value (USB_FUNCTION_PTP) carried in the USB status system broadcast can be used to determine whether the file is in a readable state.

[0158] For example, such as Figure 10 As shown, Figure 10 This indicates that the file transfer status value is the third value, meaning the file is in a readable state.

[0159] Step 813: Determine if there is a risk of file leakage with shared charging devices.

[0160] In response to the file transfer status value being a third value used to indicate that a file is in a readable state, it is determined that there is a risk of file leakage from the shared charging device.

[0161] Step 814: Determine that there is no risk of file leakage from the shared charging equipment.

[0162] Since the file transfer status value is not a third value used to indicate that the file is in a readable state, it is determined that there is no risk of file leakage from the shared charging device.

[0163] Step 815: Determine whether the charging mode of the shared charging device is pure charging mode.

[0164] The mobile terminal determines that the charging method of the shared charging device is USB charging.

[0165] Step 816: Determine the status value returned by the USB interface based on the pure charging mode.

[0166] When the shared charging device is in pure charging mode, the status value includes the USB debugging status value.

[0167] Step 817: Determine if the USB debug status value is the first value.

[0168] If the USB debug status value is the first value, proceed to steps 818 and 819.

[0169] If the USB debug status value is not the first value, proceed to step 820.

[0170] Step 818: Determine if there is a risk of illegal installation of shared charging equipment.

[0171] The USB debug status value is the first value used to indicate that the USB debug switch is in the on state, indicating that there is a risk of illegal installation program in the shared charging device.

[0172] Step 819: Determine if there is a risk of clipboard leakage in shared charging devices.

[0173] In response to the USB debug status value being the first value used to indicate that the USB debug switch is in the on state, it is determined that there is a risk of clipboard leakage in the shared charging device.

[0174] Step 820: Confirm that there is no risk of privacy leakage from shared charging devices.

[0175] Since the USB debugging status value is not the first value used to indicate that the USB debugging switch is on, it is determined that there is no risk of privacy leakage from the shared charging device.

[0176] Step 821: Identify the privacy risks associated with shared charging devices.

[0177] Optionally, privacy risk items corresponding to the shared charging device are determined according to steps 806, 807, 810, 813, 818, and 819. For example, in step 806, it can be determined that the shared charging device specifically has the risk of illegally installing programs.

[0178] Step 822: Display the privacy risk items for shared charging devices.

[0179] Optionally, in response to a trigger action on the view control, a privacy risk item for the shared charging device can be displayed.

[0180] For example, such as Figure 4 As shown, when a mobile terminal detects a privacy risk associated with a shared charging device, user interface 41 is displayed. User interface 41 shows a brief detection result 401, which includes the text "It is recommended to immediately disconnect this charging device" and "This charging device poses a security risk," informing the user of the privacy risk. The user can further click on control 402 to display user interface 42, which shows detection details 403. Detection details 403 displays privacy risk items and their detection results.

[0181] For example, such as Figure 5 As shown, when the mobile terminal detects that the shared charging device does not pose a privacy risk, user interface 51 is displayed. User interface 51 displays a brief detection result 501, which includes the text "This charging device is safe" and "Grant permission to accurately identify the device being charged," informing the user that the shared charging device does not pose a privacy risk and can be used with confidence. The user can further click on control 502 to display user interface 52, which displays detection details 503. Detection details 503 displays privacy risk items and their detection results.

[0182] In summary, this embodiment determines the status value returned by the interface to be detected based on the charging method of the shared charging device, and determines whether the shared charging device may have privacy leakage based on the status value. In response to the security risks of users using shared power banks, it introduces charging risk detection capabilities, automatically detects the security risks of shared charging devices, matches technical solutions, and protects the security of users' mobile phones.

[0183] It can also generate charging risk reports and promptly alert users to relevant charging risks, guiding them to take actions such as unplugging the power or revoking relevant permissions to avoid unnecessary losses.

[0184] Figure 11A flowchart illustrating a charging management method provided in an exemplary embodiment of this application is shown.

[0185] Step 1101: Monitor the connection status of the charging device.

[0186] Optionally, the presence of a charging device can be determined by listening to the system power connection broadcast (ACTION_POWER_CONNECTED). Upon receiving the system power connection broadcast, the presence of a charging device is confirmed.

[0187] Step 1102: In response to the detection of charging device access, invoke the general recognition model for shared scenarios.

[0188] A general identification model for shared scenarios is used to determine the device type of charging equipment. In this application embodiment, the device types of charging equipment are divided into shared charging equipment and non-shared charging equipment (also known as personal charging equipment). Shared charging equipment includes, but is not limited to, at least one of shared power banks, shared charging cabinets, and charging massage chairs in public places such as bus stations / high-speed rail stations / airports.

[0189] Optionally, the shared scene general recognition model will perform the following steps:

[0190] 1. Determine the historical program running between the second time step and the first time step by using the top of the stack.

[0191] The second time slot is earlier than the first time slot. For example, the first time slot is 12:03:00 and the second time slot is 11:59:00.

[0192] Optionally, the duration between the second moment and the first moment conforms to a preset value, which can be set by technicians.

[0193] Optionally, the second time can be determined based on the first time and a preset value. For example, if the preset value is 1 minute and the first time is 12:00:00, then by going back 1 minute from the first time, the second time is 11:59:00.

[0194] The application stack is a stack used to record the history of running programs. Optionally, the application stack also records the running time of historical applications.

[0195] 2. Obtain and identify the notification bar messages of the target program between the second time point and the first time point.

[0196] The notification bar is used to display messages pushed by the application; the pushed messages are the notification bar messages. For example, such as... Figure 7 As shown, Figure 7Notification bar 701 is shown. Notification bar 701 displays the content of notification bar message 702, which is "Application A payment: Payment points service order confirmed...". Notification bar message 702 is used to inform the user that the payment function of application A has been used.

[0197] The presence of target keywords in the notification bar indicates that the charging equipment is a shared charging device. The target keywords are terms related to renting shared charging devices. Optionally, the target keywords are set by technical personnel. Optionally, the target keywords are terms related to payment during the rental process of shared charging devices.

[0198] Since different words sometimes have the same meaning—for example, the words "payment" and "payment fee" have the same meaning in some scenarios—optionally, a semantic analysis model can be invoked to extract the semantic analysis results of the notification message; based on the semantic analysis results, it can be determined whether the notification message contains the target keyword.

[0199] Step 1103: Determine if the charging device is a shared charging device and determine the device information.

[0200] The equipment information includes at least one of the following: rental brand, rental time, and rental channel. The rental brand refers to the merchant name of the shared charging equipment; the rental time includes at least one of the following: start rental time and end rental time; the rental channel includes at least one of the following: rental location, the application used for rental, and payment method.

[0201] Optionally, the text content of the notification message is identified; device information of the charging device is extracted from the text content; or, device information is received through a first physical port, which is the physical port through which the charging device connects to the mobile terminal.

[0202] Step 1104: Determine the privacy risk items corresponding to the shared charging devices through system broadcast.

[0203] The privacy risk item indicates the type of privacy risk that may arise from shared charging devices. Optionally, the privacy risk item may include at least one of the following: risk of unauthorized installation of programs, risk of clipboard leakage, risk of image leakage, and risk of file leakage.

[0204] Step 1105: Display the privacy risk items for shared charging devices.

[0205] For example, such as Figure 4As shown, when a mobile terminal detects a privacy risk associated with a shared charging device, user interface 41 is displayed. User interface 41 shows a brief detection result 401, which includes the text "It is recommended to immediately disconnect this charging device" and "This charging device poses a security risk," informing the user of the privacy risk. The user can further click on control 402 to display user interface 42, which shows detection details 403. Detection details 403 displays privacy risk items and their detection results.

[0206] For example, such as Figure 5 As shown, when the mobile terminal detects that the shared charging device does not pose a privacy risk, user interface 51 is displayed. User interface 51 displays a brief detection result 501, which includes the text "This charging device is safe" and "Grant permission to accurately identify the device being charged," informing the user that the shared charging device does not pose a privacy risk and can be used with confidence. The user can further click on control 502 to display user interface 52, which displays detection details 503. Detection details 503 displays privacy risk items and their detection results.

[0207] In summary, this embodiment, upon detecting the connection of a charging device, first determines the type of the charging device. If the charging device is a shared charging device, it identifies the privacy risks associated with that shared charging device and displays these risks to inform the user. This method addresses the security risks associated with users using shared charging devices by introducing risk detection capabilities, automatically detecting the security risks of shared charging devices connected to the phone, and matching technical solutions to protect user privacy and security.

[0208] It should be noted that the above steps can also be used to detect potential safety hazards in non-shared charging devices. For example, through the above... Figure 8 The illustrated embodiments perform security checks on non-shared charging devices, or, through the above... Figure 11 The illustrated embodiments perform security checks on non-shared charging devices, or a combination of the above. Figure 8 and Figure 11 The illustrated embodiment performs safety testing on non-shared charging devices.

[0209] The following are device embodiments of this application. For details not described in detail in the device embodiments, please refer to the corresponding descriptions in the above method embodiments. They will not be repeated here.

[0210] Figure 12A schematic diagram of a charging management device provided in an exemplary embodiment of this application is shown. This device can be implemented as all or part of a computer device through software, hardware, or a combination of both. The device 120 includes:

[0211] The monitoring module 121 is used to obtain the historical running program of the terminal in response to the detection of the access of the charging device;

[0212] The determination module 122 is used to determine the device type of the charging device based on the historical messages of the historical running program;

[0213] The determination module 122 is used to determine the privacy risk item corresponding to the shared charging device through system broadcast when the device type of the charging device is the shared charging device. The privacy risk item is used to indicate the type of privacy that has a risk of leakage due to the shared charging device.

[0214] Display module 123 is used to display the privacy risk items of the shared charging device, and to manage the charging of the terminal based on the privacy risk items.

[0215] In an optional design of this application, the determining module 122 is further configured to, in response to the existence of a target program in the historical running program, determine, based on the historical messages of the target program, that the charging device is the shared charging device, and that the target program is a program related to renting the shared charging device.

[0216] In an optional design of this application, the determining module 122 is further configured to, in response to the existence of the target program in the historical running program, acquire and identify the notification bar message of the target program between a second time and a first time, wherein the second time is earlier than the first time; and, in response to the existence of a target keyword in the notification bar message, determine that the device type of the charging device is the shared charging device, wherein the target keyword is a word related to renting the shared charging device.

[0217] In an optional design of this application, the monitoring module 121 is further configured to, in response to detecting the access of the charging device at a first moment, obtain the historical running program that runs within the most recent time period determined based on the first moment.

[0218] In an optional design of this application, the listening module 121 is further configured to, in response to listening to the access of the charging device at the first moment, obtain the historical running program located at the top of the application stack between the second moment and the first moment, wherein the second moment is earlier than the first moment; wherein the application stack is a stack used to record the historical running program.

[0219] In an optional design of this application, the determining module 122 is further configured to, when the device type of the charging device is the shared charging device, determine the charging mode from the system broadcast, the charging mode including at least one of Universal Serial Bus (USB) charging mode and pure charging mode; determine the status value returned by the USB interface according to the charging mode; and determine the privacy risk item corresponding to the charging device according to the status value.

[0220] In an optional design of this application, the determining module 122 is further configured to determine the privacy risk item corresponding to the charging device based on the state value, including: in response to the USB debugging state value being a first value indicating that the USB debugging switch is in the on state, determining that the charging device has at least one of the risks of illegal installation program and clipboard leakage; or, in response to the image transmission state value being a second value indicating that the image is in a readable state, determining that the shared charging device has an image leakage risk; or, in response to the file transmission state value being a third value indicating that the file is in a readable state, determining that the shared charging device has a file leakage risk.

[0221] In an optional design of this application, the determining module 122 is further configured to determine, in response to the USB debug status value being a first value indicating that the USB debug switch is in the on state, that the shared charging device has at least one of the risks of illegal installation program and clipboard leakage.

[0222] In an optional design of this application, the determining module 122 is further configured to obtain device information of the shared charging device, the device information including at least one of rental brand, rental time and rental channel.

[0223] The display module 123 is also used to display the device information and the device type.

[0224] In an optional design of this application, the determining module 122 is further configured to identify the text content of the notification bar message; extract the device information of the shared charging device from the text content; or receive the device information through a first physical port, wherein the first physical port is the physical port through which the shared charging device connects to the mobile terminal.

[0225] In summary, this embodiment, upon detecting the connection of a charging device, first determines the type of the charging device. If the charging device is a shared charging device, it identifies the privacy risks associated with that shared charging device and displays these risks to inform the user. This method addresses the security risks associated with users using shared charging devices by introducing risk detection capabilities, automatically detecting the security risks of shared charging devices connected to the phone, and matching technical solutions to protect user privacy and security.

[0226] Figure 13 This is a schematic diagram illustrating the structure of a computer device according to an exemplary embodiment. The computer device 1300 includes a Central Processing Unit (CPU) 1301, a system memory 1304 including Random Access Memory (RAM) 1302 and Read-Only Memory (ROM) 1303, and a system bus 1305 connecting the system memory 1304 and the CPU 1301. The computer device 1300 also includes a basic input / output system (I / O system) 1306 to facilitate information transfer between various devices within the computer device, and a mass storage device 1307 for storing the operating system 1313, application programs 1314, and other program modules 1315.

[0227] The basic input / output system 1306 includes a display 1308 for displaying information and an input device 1309 for user input, such as a mouse or keyboard. Both the display 1308 and the input device 1309 are connected to the central processing unit 1301 via an input / output controller 1310 connected to the system bus 1305. The basic input / output system 1306 may also include the input / output controller 1310 for receiving and processing input from multiple other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 1310 also provides output to a display screen, printer, or other types of output devices.

[0228] The mass storage device 1307 is connected to the central processing unit 1301 via a mass storage controller (not shown) connected to the system bus 1305. The mass storage device 1307 and its associated computer device-readable media provide non-volatile storage for the computer device 1300. That is, the mass storage device 1307 may include computer device-readable media (not shown), such as a hard disk or a compact disc read-only memory (CD-ROM) drive.

[0229] Without loss of generality, the computer device readable medium may include computer device storage media and communication media. Computer device storage media include volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing information such as computer device readable instructions, data structures, program modules, or other data. Computer device storage media include RAM, ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM, digital video disc (DVD) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Of course, those skilled in the art will recognize that the computer device storage media are not limited to the above-mentioned types. The system memory 1304 and mass storage device 1307 described above can be collectively referred to as memory.

[0230] According to various embodiments of this disclosure, the computer device 1300 can also be connected to a remote computer device on a network, such as the Internet. That is, the computer device 1300 can be connected to the network 1311 via a network interface unit 1312 connected to the system bus 1305, or it can use the network interface unit 1312 to connect to other types of networks or remote computer device systems (not shown).

[0231] The memory also includes one or more programs, which are stored in the memory. The central processing unit 1301 executes the one or more programs to implement all or part of the steps of the above-mentioned charging management method.

[0232] In an exemplary embodiment, a computer-readable storage medium is also provided, which stores at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the charging management method provided in the above-described method embodiments.

[0233] This application also provides a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by the processor to implement the charging management method provided in the above method embodiments.

[0234] Optionally, this application also provides a computer program product containing instructions that, when run on a computer device, causes the computer device to perform the charging management methods described in the above aspects.

[0235] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0236] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0237] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A charging management method, characterized in that, The method includes: In response to the detection of a charging device access, the terminal's historical running programs are obtained; In response to the existence of a target program in the historical running program, the notification bar message of the target program between a second time and a first time is obtained and identified, where the second time is earlier than the first time. The target program is a program related to renting shared charging equipment or a program related to payment during the process of renting the shared charging equipment. In response to the presence of a target keyword in the notification bar message, it is determined that the device type of the charging device is the shared charging device, and the target keyword is a word related to renting the shared charging device. When the device type of the charging device is the shared charging device, the privacy risk item corresponding to the shared charging device is determined through system broadcast. The privacy risk item is used to indicate the type of privacy that has a risk of leakage due to the shared charging device. Display the privacy risk items of the shared charging device, and manage the charging of the terminal based on the privacy risk items.

2. The method according to claim 1, characterized in that, The step of obtaining the terminal's historical running procedures in response to the detection of a charging device access includes: In response to detecting the access of the charging device at the first moment, the historical running program that ran within the most recent time period determined based on the first moment is obtained.

3. The method according to claim 2, characterized in that, The step of responding to the detection of the charging device's access at the first moment by acquiring the historical running program that ran within the most recent time period determined based on the first moment includes: In response to detecting the access of the charging device at the first moment, the historical running program located at the top of the application stack between the second moment and the first moment is obtained; The application stack is a stack used to record the historical running programs.

4. The method according to any one of claims 1 to 3, characterized in that, When the device type of the charging device is the shared charging device, the privacy risk items corresponding to the shared charging device are determined through system broadcast, including: When the device type of the charging device is the shared charging device, the charging mode of the shared charging device is determined from the system broadcast, and the charging mode includes at least one of Universal Serial Bus (USB) charging mode and pure charging mode; Determine the status value returned by the USB interface based on the charging method; The privacy risk item corresponding to the shared charging device is determined based on the status value.

5. The method according to claim 4, characterized in that, When the charging method of the shared charging device is the USB charging method, the status value includes at least one of the following: USB debugging status value, image transmission status value, and file transmission status value; The step of determining the privacy risk item corresponding to the shared charging device based on the status value includes: In response to the USB debugging status value being a first value used to indicate that the USB debugging switch is in the on state, it is determined that the shared charging device has at least one of the risks of illegal installation and clipboard leakage. or, In response to the fact that the image transmission status value is a second value used to indicate that the image is in a readable state, it is determined that the shared charging device has a risk of image leakage; or, In response to the fact that the file transfer status value is a third value used to indicate that the file is in a readable state, it is determined that there is a risk of file leakage in the shared charging device.

6. The method according to claim 4, characterized in that, When the charging mode of the shared charging device is the pure charging mode, the status value includes: USB debugging status value; The step of determining the privacy risk item corresponding to the shared charging device based on the status value includes: In response to the USB debugging status value being a first value used to indicate that the USB debugging switch is in the on state, it is determined that the shared charging device has at least one of the risks of illegal installation and clipboard leakage.

7. The method according to claim 1, characterized in that, After determining that the charging device type is a shared charging device in response to the presence of a target keyword in the notification message, the process further includes: Obtain the device information of the shared charging equipment, wherein the device information includes at least one of the following: rental brand, rental time, and rental channel; Display the device information and the device type.

8. The method according to claim 7, characterized in that, The step of obtaining the device information of the shared charging device includes: Identify the text content of the notification message; extract the device information of the charging device from the text content; Alternatively, the device information can be received through a first physical port, which is the physical port through which the shared charging device connects to the mobile terminal.

9. A charging management device, characterized in that, The device includes: The monitoring module is used to respond to the detection of charging device access and obtain the terminal's historical running programs; The determination module is configured to, in response to the presence of a target program in the historical running program, acquire and identify the notification bar message of the target program between a second time and a first time, wherein the second time is earlier than the first time, and the target program is a program related to renting shared charging equipment or a program related to payment during the process of renting the shared charging equipment; and in response to the presence of a target keyword in the notification bar message, determine that the device type of the charging equipment is the shared charging equipment, and the target keyword is a word related to renting the shared charging equipment. The determining module is further configured to determine the privacy risk item corresponding to the shared charging device through system broadcast when the device type of the charging device is the shared charging device. The privacy risk item is used to indicate the type of privacy that has a risk of leakage due to the shared charging device. The display module is used to display the privacy risk items of the shared charging device and to manage the charging of the terminal based on the privacy risk items.

10. The apparatus according to claim 9, characterized in that, The monitoring module is also used for: In response to detecting the access of the charging device at the first moment, the historical running program that ran within the most recent time period determined based on the first moment is obtained.

11. The apparatus according to claim 10, characterized in that, The monitoring module is also used for: In response to detecting the access of the charging device at the first moment, the historical running program located at the top of the application stack between the second moment and the first moment is obtained; The application stack is a stack used to record the historical running programs.

12. The apparatus according to any one of claims 9 to 11, characterized in that, The determining module is further configured to: When the device type of the charging device is the shared charging device, the charging mode of the shared charging device is determined from the system broadcast, and the charging mode includes at least one of Universal Serial Bus (USB) charging mode and pure charging mode; Determine the status value returned by the USB interface based on the charging method; The privacy risk item corresponding to the shared charging device is determined based on the status value.

13. The apparatus according to claim 12, characterized in that, When the charging method of the shared charging device is the USB charging method, the status value includes at least one of the following: USB debugging status value, image transmission status value, and file transmission status value; The determining module is further configured to: In response to the USB debugging status value being a first value used to indicate that the USB debugging switch is in the on state, it is determined that the shared charging device has at least one of the risks of illegal installation and clipboard leakage. or, In response to the fact that the image transmission status value is a second value used to indicate that the image is in a readable state, it is determined that the shared charging device has a risk of image leakage; or, In response to the fact that the file transfer status value is a third value used to indicate that the file is in a readable state, it is determined that there is a risk of file leakage in the shared charging device.

14. The apparatus according to claim 13, characterized in that, When the charging mode of the shared charging device is the pure charging mode, the status value includes: USB debugging status value; The determining module is further configured to: In response to the USB debugging status value being a first value used to indicate that the USB debugging switch is in the on state, it is determined that the shared charging device has at least one of the risks of illegal installation and clipboard leakage.

15. The apparatus according to claim 9, characterized in that, The determining module is further configured to: Obtain the device information of the shared charging equipment, wherein the device information includes at least one of the following: rental brand, rental time, and rental channel; Display the device information and the device type.

16. The apparatus according to claim 15, characterized in that, The determining module is further configured to: Identify the text content of the notification message; extract the device information of the charging device from the text content; Alternatively, the device information can be received through a first physical port, which is the physical port through which the shared charging device connects to the mobile terminal.

17. A computer device, characterized in that, The computer device includes a processor and a memory, wherein the memory stores at least one program, which is loaded and executed by the processor to implement the charging management method as described in any one of claims 1 to 7.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one piece of program code, which is loaded and executed by a processor to implement the charging management method as described in any one of claims 1 to 7.

19. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the charging management method as described in any one of claims 1 to 7.

Images