OTA verification code sending method and device, equipment, medium and program product

Abstract

The application relates to the technical field of communication, in particular to a method and device for sending an OTA verification code, equipment, medium and program product, wherein the method comprises the following steps: obtaining an OTA upgrade request of a user; generating a target verification code according to the OTA upgrade request, matching user account information according to the target verification code, and identifying verification code information in the user account information; determining a marking state of the verification code information according to the target verification code, and sending the verification code information in the target marking state to a message robot. Therefore, the method solves the problems that the related art has a delay in sending a verification code through an email, cannot adapt to the requirements in different scenes, and has low upgrade efficiency.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, device, medium and program product for sending OTA verification codes. Background Technology

[0002] To prevent accidental or malicious operations, OTA (Over-The-Air) version upgrades for in-vehicle infotainment systems require verification codes for the current action. Currently, the verification code delivery method mainly relies on email notifications. However, email transmission and reception are not instantaneous, especially during network congestion, busy mail servers, or when sending verification codes in bulk. In such cases, the verification code may not be delivered in a short time, which can affect the response speed of technicians and the efficiency of the upgrade. Summary of the Invention

[0003] This application provides a method, apparatus, device, medium, and program product for sending OTA verification codes, in order to solve the problems of delay, inability to adapt to different scenarios, and low upgrade efficiency in the related technologies of sending verification codes via email.

[0004] The first aspect of this application provides a method for sending OTA verification codes, including the following steps: obtaining a user's OTA upgrade request; generating a target verification code based on the OTA upgrade request; matching the target verification code with user account information and identifying the verification code information in the user account information; determining the marking status of the verification code information based on the target verification code; and sending the verification code information with the target marking status to a message robot.

[0005] Optionally, the target is marked as unsent and unused, and the verification code information is stored in the verification code pool.

[0006] Optionally, the marking status of the verification code information is determined based on the target verification code, including: if the target verification code and the verification code information are consistent, the verification code information is marked as fatigued; otherwise, the verification code information is updated to the target verification code, and the updated verification code information is marked as unsent and unused.

[0007] Optionally, after calling the target interface to send the verification code information with the target marked status to the message robot, the process includes: detecting the status of the verification code information; if the status of the verification code information is "used", then deleting the verification code information in the "used" status.

[0008] Optionally, sending the verification code information of the target marked state to the message robot includes: creating a running script; and calling the target interface based on the running script to send the verification code information of the unsent and unused state to the message robot.

[0009] Optionally, it also includes: monitoring the running status of the script; if the running status is abnormal, restarting the script.

[0010] A second aspect of this application provides an OTA verification code sending device, comprising: an acquisition module for acquiring a user's OTA upgrade request; a matching module for generating a target verification code based on the OTA upgrade request, matching the target verification code with user account information, and identifying the verification code information in the user account information; and a sending module for determining the marking status of the verification code information based on the target verification code and sending the verification code information with the target marking status to a message robot.

[0011] Optionally, the target is marked as unsent and unused, and the verification code information is stored in the verification code pool.

[0012] Optionally, the sending module is further configured to mark the verification code information as fatigued if the target verification code and the verification code information are consistent; otherwise, update the verification code information to the target verification code and mark the updated verification code information as unsent and unused.

[0013] Optionally, the OTA verification code sending device further includes: an update module, used to call the target interface to send the verification code information with the target marked state to the message robot, and then detect the state of the verification code information; if the state of the verification code information is "used", then delete the verification code information in the "used" state.

[0014] Optionally, the sending module is further used to create a running script; based on the running script, the target interface is called to send the verification code information that has not been sent and is in an unused state to the message robot.

[0015] Optionally, the OTA verification code sending device further includes: a monitoring module, used to monitor the running status of the running script; if the running status is abnormal, the running script is restarted.

[0016] A third aspect of this application provides an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor executes the program to implement the OTA verification code sending method as described in the above embodiments.

[0017] A fourth aspect of this application provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed, are used to implement the OTA verification code sending method as described in the above embodiments.

[0018] A fifth aspect of this application provides a computer program product, including: a computer program or instructions, which, when executed, implement the OTA verification code sending method as described in the above embodiments.

[0019] Therefore, this application has at least the following beneficial effects:

[0020] This application embodiment can generate a target verification code based on a user's OTA upgrade request. The target verification code is used to mark the verification code information in the user's account information, ensuring that the same verification code information under that account is sent only once. The target-marked verification code information is then sent to the message robot, resulting in a more accurate delivery method, reducing unnecessary information interference, and improving work efficiency. This solves the problems of latency, inability to adapt to different scenarios, and low upgrade efficiency associated with sending verification codes via email in related technologies.

[0021] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0022] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0023] Figure 1 This is a flowchart of an OTA verification code sending method provided according to an embodiment of this application;

[0024] Figure 2 This is an example diagram of an OTA verification code sending method according to an embodiment of this application;

[0025] Figure 3 This is a block diagram of an OTA verification code sending device according to an embodiment of this application;

[0026] Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0027] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0028] The following description, with reference to the accompanying drawings, details an OTA verification code sending method, apparatus, device, medium, and program product according to embodiments of this application. Addressing the problems mentioned in the background section, this application provides an OTA verification code sending method. In this method, a target verification code is generated based on the user's OTA upgrade request. The target verification code is used to mark the verification code information in the user's account information, ensuring that the same verification code information under that account is sent only once. The target-marked verification code information is then sent to a message robot. This method is more accurate, reduces unnecessary information interference, and improves work efficiency. Therefore, it solves the problems of latency, inability to adapt to different scenarios, and low upgrade efficiency associated with sending verification codes via email in related technologies.

[0029] Specifically, Figure 1 This is a flowchart illustrating an OTA verification code sending method provided in an embodiment of this application.

[0030] like Figure 1 As shown, the method for sending the OTA verification code includes the following steps:

[0031] In step S101, the user's OTA upgrade request is obtained.

[0032] It is understood that the embodiments of this application can receive OTA upgrade requests from users, such as triggering an OTA upgrade for the vehicle's infotainment system through a vehicle networking platform. Requests can be submitted through various means, such as user interfaces, remote management systems, etc.

[0033] In step S102, a target verification code is generated based on the OTA upgrade request, the target verification code is matched with user account information, and the verification code information in the user account information is identified.

[0034] After a user triggers an upgrade request, this embodiment of the application can generate a target verification code through a vehicle networking program. The new verification code information will be stored in a Redis database, and the generated verification code needs to be matched with the user account information to identify which account initiated the upgrade request. Once the verification code is associated with the user account, this embodiment of the application can obtain the current verification code information of the user account for subsequent verification and notification processes.

[0035] In step S103, the marking status of the verification code information is determined according to the target verification code, and the verification code information with the target marking status is sent to the message robot.

[0036] The target is marked as unsent and unused, and the verification code information is stored in the verification code pool.

[0037] In one embodiment of this application, determining the marking status of verification code information based on the target verification code includes: if the target verification code and the verification code information are consistent, then marking the verification code information as fatigued; otherwise, updating the verification code information to the target verification code and marking the updated verification code information as unsent and unused.

[0038] Specifically, such as Figure 2 As shown, this embodiment of the application can periodically scan all CAPTCHA information in the Redis database using a sniffing module. Upon first run, the CAPTCHA pool is empty, and all unused CAPTCHA information will be sent. If a CAPTCHA has already been used, and the user account information matches a CAPTCHA in the pool, then that CAPTCHA will be removed from the pool.

[0039] In another implementation, such as Figure 2 As shown, if the verification code is not used, it will be matched with the verification code information in the pool: if the user account information and the verification code information match, a verification code fatigue flag will be set to avoid unnecessary duplicate message sending; if the user account information matches but the verification code information does not match, the latest verification code information will be sent, the user's original verification code will be deleted from the pool, and the user's latest verification code will be added to the pool; if neither the user account information nor the verification code information matches, the user's verification code information will also be added to the pool.

[0040] In one embodiment of this application, sending verification code information with a target marked state to a message robot includes: creating a running script; and calling the target interface based on the running script to send verification code information with an unsent and unused state to the message robot.

[0041] This application embodiment compares each obtained target verification code with the verification codes already stored in the verification code pool to match the user account and verification code information. For the latest unsent verification code, the SendMSG interface is called to send the message via a message robot. Even under network congestion or busy mail server conditions, the verification code can be delivered accurately.

[0042] Specifically, once the script (such as a Python script) successfully retrieves the verification code information to be sent, it will call an interface called SendMsg. This interface sends the verification code information to a designated messaging group on a communication tool, notifying the relevant personnel through a message bot.

[0043] It should be noted that the embodiments of this application can also mark the verification codes and user account information that have already been sent, to ensure that the same verification code information under the account is only sent once, and will be resent only when there is new verification code information, so as to avoid a large number of invalid messages flooding the screen.

[0044] Furthermore, to ensure the high availability and stability of the script, this embodiment of the application can monitor the running status of the script; if the running status is abnormal, the script will be restarted.

[0045] This application embodiment can use the process management tool Supervisor. Supervisor's task is to monitor the running status of Python scripts. If the script stops running for any reason (such as server restart, program error, etc.), Supervisor will automatically detect this situation and immediately restart the script so that it can continue to perform its task, namely sending verification codes, thereby ensuring the continuity and reliability of the entire system and improving the overall operation and maintenance efficiency.

[0046] Furthermore, after sending the verification code information with the target marked status to the message robot by calling the target interface, the process includes: detecting the status of the verification code information; if the status of the verification code information is "used", then the "used" verification code information will be deleted to ensure that the verification code pool retains unused or still valid verification codes. Detecting the status of the verification code information can improve the efficiency and security of the OTA upgrade process, while reducing the risk caused by verification code delays or loss.

[0047] The OTA verification code sending method proposed in this application generates a target verification code based on the user's OTA upgrade request. The target verification code is used to mark the verification code information in the user's account information, ensuring that the same verification code information under that account is sent only once. The target-marked verification code information is then sent to the message robot. This method is more accurate, reduces unnecessary information interference, and improves work efficiency. Therefore, it solves the problems of latency, inability to adapt to different scenarios, and low upgrade efficiency associated with sending verification codes via email in related technologies.

[0048] Next, referring to the accompanying drawings, an OTA verification code sending device according to an embodiment of this application is described.

[0049] Figure 3 This is a block diagram of an OTA verification code sending device according to an embodiment of this application.

[0050] like Figure 3 As shown, the OTA verification code sending device 10 includes: an acquisition module 100, a matching module 200, and a sending module 300.

[0051] The acquisition module 100 is used to acquire the user's OTA upgrade request; the matching module 200 is used to generate a target verification code based on the OTA upgrade request, match the user account information based on the target verification code, and identify the verification code information in the user account information; the sending module 300 is used to determine the marking status of the verification code information based on the target verification code, and send the verification code information with the target marking status to the message robot.

[0052] Optionally, the target is marked as unsent and unused, and the verification code information is stored in the verification code pool.

[0053] In one embodiment of this application, the sending module 300 is further configured to mark the verification code information as fatigued if the target verification code and the verification code information are consistent; otherwise, update the verification code information to the target verification code and mark the updated verification code information as unsent and unused.

[0054] In one embodiment of this application, the OTA verification code sending device 10 further includes: an update module, used to call the target interface to send the verification code information with the target marked state to the message robot, and then detect the state of the verification code information; if the state of the verification code information is the used state, then the used verification code information will be deleted.

[0055] In one embodiment of this application, the sending module 300 is further configured to create a running script; and based on the running script, call the target interface to send the verification code information that has not been sent and is in an unused state to the message robot.

[0056] In one embodiment of this application, the OTA verification code sending device 10 further includes: a monitoring module, used to monitor the running status of the running script; if the running status is abnormal, the running script is restarted.

[0057] It should be noted that the foregoing explanation of the OTA verification code sending method embodiment also applies to the OTA verification code sending device of this embodiment, and will not be repeated here.

[0058] The OTA verification code sending device proposed in this application generates a target verification code based on the user's OTA upgrade request. The target verification code is used to mark the verification code information in the user's account information, ensuring that the same verification code information under that account is sent only once. The target-marked verification code information is then sent to the message robot. This method is more accurate, reduces unnecessary information interference, and improves work efficiency. Therefore, it solves the problems of latency, inability to adapt to different scenarios, and low upgrade efficiency associated with sending verification codes via email in related technologies.

[0059] Figure 4A schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device may include:

[0060] The memory 401, the processor 402, and the computer program stored on the memory 401 and capable of running on the processor 402.

[0061] When the processor 402 executes the program, it implements the OTA verification code sending method provided in the above embodiments.

[0062] Furthermore, electronic devices also include:

[0063] Communication interface 403 is used for communication between memory 401 and processor 402.

[0064] The memory 401 is used to store computer programs that can run on the processor 402.

[0065] The memory 401 may include high-speed RAM (Random Access Memory) memory, and may also include non-volatile memory, such as at least one disk storage.

[0066] If the memory 401, processor 402, and communication interface 403 are implemented independently, then the communication interface 403, memory 401, and processor 402 can be interconnected via a bus to complete communication between them. The bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0067] Optionally, in a specific implementation, if the memory 401, processor 402, and communication interface 403 are integrated on a single chip, then the memory 401, processor 402, and communication interface 403 can communicate with each other through an internal interface.

[0068] Processor 402 may be a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement embodiments of this application.

[0069] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described method for sending OTA verification codes.

[0070] This application also provides a computer program product, including: a computer program or instructions, which, when executed, implement the above-described method for sending OTA verification codes.

[0071] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0072] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "N" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0073] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more N executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0074] It should be understood that the various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (FPGAs), field-programmable gate arrays (FPGAs), etc.

[0075] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0076] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A method for transmitting an OTA authentication code, characterized by, The method comprises the following steps: Obtaining an OTA upgrade request of a user; Generating a target verification code according to the OTA upgrade request, matching user account information according to the target verification code, and identifying verification code information in the user account information; Determining a marking state of the verification code information according to the target verification code, and sending the verification code information in the target marking state to a message robot, wherein the target marking state is an unsent and unused state, and the verification code information is stored in a verification code pool; The step of determining the marking state of the verification code information according to the target verification code comprises: if the target verification code is consistent with the verification code information, marking the verification code information as a fatigue state; otherwise, updating the verification code information to the target verification code, and marking the updated verification code information as the unsent and unused state; After the verification code information in the target marking state is sent to the message robot, the method further comprises: detecting a state of the verification code information; and if the state of the verification code information is a used state, deleting the verification code information in the used state. 2.The method of claim 1, wherein, The step of sending the verification code information in the target marking state to the message robot comprises: Creating a running script; Based on the running script, calling a target interface to send the verification code information in the unsent and unused state to the message robot. 3.The method of claim 2, wherein, The method further comprises: Monitoring a running state of the running script; If the running state is abnormal, restarting the running script.

4. An OTA verification code sending device, characterized in that, The method comprises: An obtaining module configured to obtain an OTA upgrade request of a user; A matching module configured to generate a target verification code according to the OTA upgrade request, match user account information according to the target verification code, and identify verification code information in the user account information; A sending module configured to determine a marking state of the verification code information according to the target verification code, and send the verification code information in the target marking state to a message robot, wherein the target marking state is an unsent and unused state, and the verification code information is stored in a verification code pool; The sending module is further configured to: if the target verification code is consistent with the verification code information, mark the verification code information as a fatigue state; otherwise, update the verification code information to the target verification code, and mark the updated verification code information as the unsent and unused state; An updating module configured to, after the verification code information in the target marking state is sent to the message robot, detect a state of the verification code information; and if the state of the verification code information is a used state, delete the verification code information in the used state.

5. An electronic device, comprising: The method comprises: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method for sending an OTA verification code according to any one of claims 1-3.

6. A computer readable storage medium having stored thereon a computer program or instructions, characterized in that, The computer program or instructions are executed to implement the method for sending an OTA verification code according to any one of claims 1-3.

7. A computer program product, comprising: The computer program or instructions are executed to implement the method for sending an OTA verification code according to any one of claims 1-3.

Images