Camera upgrading method and device, storage medium and electronic equipment

Abstract

The invention provides a camera upgrading method and device, a storage medium and electronic equipment. The upgrading method comprises the following steps: receiving an upgrading request, wherein the upgrading request comprises an image effect parameter file upgrading request sent by electric detection equipment, a direction data upgrading request sent by the electric detection equipment, and / or a main program firmware file upgrading request sent by remote equipment; in response to the upgrading request, burning an image effect parameter file, direction data and / or a main program firmware file to a corresponding area of a camera memory; and judging whether the camera is successfully upgraded. According to the technical scheme provided by the invention, image effect parameter file upgrading, main program firmware file upgrading and / or camera image direction adjustment can be realized.

Description

Technical Field

[0001] The present application belongs to the field of image acquisition technology, and relates to a camera upgrade method, and in particular to a camera upgrade method, device, storage medium and electronic device. Background Art

[0002] With the rapid development of automobile intelligence and autonomous driving technology, cameras have been widely used as an important component of automobile perception systems, such as driving assistance, automatic parking, blind spot monitoring and panoramic surround view, etc. The number of cameras installed on cars is increasing, from front and rear view cameras to multiple wide-angle cameras around the car body, which can capture images from different angles to improve vehicle safety and driving experience.

[0003] In order to improve production efficiency and reduce costs, automobile OEMs usually use the same camera hardware on multiple models. This approach can simplify supply chain management, reduce production complexity, and facilitate bulk purchases to reduce unit costs. However, since the body design, camera installation position, and camera orientation of different models may be different, the requirements for camera image quality (IQ) may also be different. These factors will bring difficulties to the upgrade of cameras. Summary of the invention

[0004] The embodiments of the present application provide a camera upgrade method, device, storage medium and electronic device for implementing image effect parameter file upgrade, main program firmware file upgrade and / or camera image direction adjustment.

[0005] In a first aspect, an embodiment of the present application provides an upgrade method for a camera, the upgrade method comprising: receiving an upgrade request, the upgrade request comprising: an image effect parameter file upgrade request sent by an electrical inspection device, a direction data upgrade request sent by the electrical inspection device, and / or a main program firmware file upgrade request sent by a remote device; in response to the upgrade request, burning the image effect parameter file, direction data and / or main program firmware file to a corresponding area of ​​a camera memory; and determining whether the camera has been upgraded successfully.

[0006] In some implementations, the camera memory includes a main program firmware area, a calibration parameter area, an image effect parameter area, a direction data area and / or a camera internal parameter area; and / or the image effect parameter file and / or the main program firmware file includes camera version information, and the camera version information includes sensor manufacturer, sensor model, version number, host manufacturer, vehicle model, lens manufacturer and / or lens model.

[0007] In some implementations, in response to an image effect parameter file upgrade request sent by the electrical inspection device, burning the image effect parameter file to the corresponding area of ​​the camera memory includes: obtaining the upgrade file according to the vehicle model; determining whether the upgrade file and the status of the camera meet the first upgrade condition; if the upgrade file and the status of the camera meet the first upgrade condition, determining whether the model of the camera matches the model information in the upgrade file; if the model of the camera matches the model information in the upgrade file, burning the upgrade file to the image effect parameter area of ​​the camera memory; determining whether the camera has been successfully upgraded includes: after the burning is completed, reading back the burned data from the image effect parameter area of ​​the camera memory, and determining whether the read-back data is consistent with the upgrade file; if the read-back data is consistent with the upgrade file, powering off and restarting the camera, and determining whether the camera version information is consistent with the version information in the upgrade file.

[0008] In some implementations, determining whether the upgrade file and the status of the camera meet the first upgrade condition includes: verifying the signature of the upgrade file; if the signature verification of the upgrade file is successful, initializing the deserialization pair and the camera to determine whether the camera is in place and whether the connection and communication of the camera are normal; if the camera is in place and the connection and communication of the camera are normal, reading the identification header of the upgrade file, and determining whether the upgrade file is the image effect parameter file based on the identification header; if the upgrade file is the image effect parameter file, determining that the upgrade file and the status of the camera meet the first upgrade condition.

[0009] In some implementations, in response to a direction data upgrade request sent by the electrical inspection device, burning the direction data into a corresponding area of ​​the camera memory includes: obtaining the serial number of the camera; determining whether the state of the camera meets a second upgrade condition; if the state of the camera meets the second upgrade condition, burning the direction data into the direction data area of ​​the camera; determining whether the camera has been successfully upgraded includes: after the burning is completed, powering off and restarting the camera, reading the direction data of the current running state from the camera, and determining whether the read-back data is consistent with the direction data.

[0010] In some implementations, determining whether the status of the camera meets the second upgrade condition includes: initializing the deserialization pair and the camera, determining whether the camera is in place and whether the connection and communication of the camera are normal; if the camera is in place and the connection and communication of the camera are normal, then determining that the status of the camera meets the second upgrade condition.

[0011] In some implementations, in response to a main program firmware file upgrade request sent by the remote device, burning the main program firmware file to the corresponding area of ​​the camera memory includes: receiving an upgrade package sent by the remote device, the upgrade package including an upgrade file; determining whether the upgrade file and the status of the camera meet a third upgrade condition; if the upgrade file and the status of the camera meet the third upgrade condition, determining whether the model of the camera and the current vehicle model all match the model information, vehicle model information, and lens information in the upgrade file; if the model of the camera and the current vehicle model all match the model information, vehicle model information, and lens information in the upgrade file, burning the upgrade file to the main program firmware area of ​​the camera memory; determining whether the camera has been successfully upgraded includes: after the burning is completed, reading back the burned data from the main program firmware area of ​​the camera memory, and determining whether the read-back data is consistent with the upgrade file; if the read-back data is consistent with the upgrade file, powering off and restarting the camera, and determining whether the camera version information is consistent with the version information in the upgrade file.

[0012] In a second aspect, an embodiment of the present application provides an upgrade device for a camera, the upgrade device comprising: an upgrade request receiving module, used to receive upgrade requests, the upgrade requests comprising: an image effect parameter file upgrade request sent by an electrical inspection device, a direction data upgrade request sent by the electrical inspection device, and / or a main program firmware file upgrade request sent by a remote device; an upgrade file burning module, used to burn the image effect parameter file, direction data and / or main program firmware file to a corresponding area of ​​a camera memory in response to the upgrade request; an upgrade result judgment module, used to judge whether the camera has been successfully upgraded.

[0013] In a third aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the upgrade method described in any one of the first aspects of the embodiments of the present application is implemented.

[0014] In a fourth aspect, an embodiment of the present application provides an electronic device, comprising: a memory storing a computer program; and a processor communicatively connected to the memory, for executing the upgrade method described in any one of the first aspects of the embodiments of the present application when the computer program is called.

[0015] In summary, the embodiments of the present application provide a method for upgrading a camera, which can realize image effect parameter file upgrade, main program firmware file upgrade and / or camera image direction adjustment.

[0016] When different car models use the same camera hardware, the upgrade method provided in the embodiment of the present application can upgrade the image effect parameter file, direction data and / or main program firmware file of the camera hardware to a version that matches the car model. Therefore, the upgrade method provided in the embodiment of the present application can be applied to the situation where different car models use the same model of camera hardware.

[0017] The embodiment of the present application proposes a partitioning method for the camera memory, which separates the storage areas of the main program firmware, image effect parameters and image direction data from each other to avoid mutual influence between these data.

[0018] The embodiment of the present application defines a new firmware version number rule, which can fully represent information such as sensor manufacturer, sensor model, version number, host manufacturer, vehicle model, lens manufacturer and / or lens model, which is conducive to users' convenient version management and version verification, and can avoid upgrading the wrong version.

[0019] The embodiment of the present application includes an electrical inspection upgrade process and a remote upgrade process, which can be used to implement image effect parameter upgrades, vehicle model version information changes, and image direction adjustments. In the embodiment of the present application, the electrical inspection upgrade process can be used to upgrade image effect files and / or direction data, which can improve upgrade speed and factory efficiency. In the embodiment of the present application, the remote upgrade process can be used to upgrade the main program firmware file, which can be applicable to the scenario where the main program and image effect files are upgraded at the same time.

[0020] In addition, the embodiment of the present application defines the upgrade process and verification rules in detail. The upgrade process and verification rules provided by the embodiment of the present application can improve the success rate of version upgrades, prevent the occurrence of version burning errors, and ensure that the version burned into the camera memory is a version that can be used normally, avoiding the situation where the burning is successful but cannot be used normally. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1A and Figure 1B Shown is an example diagram of the overall implementation environment of an embodiment of the present application.

[0022] Figure 2 Shown is a flowchart of the upgrade method provided by an embodiment of the present application.

[0023] Figure 3 Shown is an example diagram of the partitioning of the camera memory in an embodiment of the present application.

[0024] Figure 4 Shown is an example diagram of the camera version information in an embodiment of the present application.

[0025] Figure 5Shown is a schematic diagram of the process of a camera manufacturer releasing an upgrade file in an embodiment of the present application.

[0026] Figure 6 Shown is a flow chart of burning the image effect parameter file to the corresponding area of ​​the camera memory in an embodiment of the present application.

[0027] Figure 7 Shown is a flowchart for determining whether the upgrade file and the status of the camera meet the first upgrade condition in an embodiment of the present application.

[0028] Figure 8 Shown is a flow chart of burning direction data into the corresponding area of ​​the camera memory in an embodiment of the present application.

[0029] Fig. 9 Shown is a flow chart of burning the main program firmware file to the corresponding area of ​​the camera memory in an embodiment of the present application.

[0030] Fig.10 Shown is a flowchart for determining whether the upgrade file and the status of the camera meet the third upgrade condition in an embodiment of the present application.

[0031] Fig.11 Shown is a flow chart of upgrading the image effect file using the electronic inspection method in an embodiment of the present application.

[0032] Fig.12 Shown is a flow chart of upgrading direction data using electrical inspection in an embodiment of the present application.

[0033] Fig.13 Shown is a flowchart of upgrading the main program firmware file using OTA method in an embodiment of the present application.

[0034] Fig.14 Shown is a schematic diagram of the structure of an upgrading device provided in an embodiment of the present application.

[0035] Fig.15 Shown is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0036] Component number description

[0037] 1400 Upgrade Device

[0038] 1401 Upgrade request receiving module

[0039] 1402 Upgrade file burning module

[0040] 1403 Upgrade result judgment module

[0041] 1500 Electronic equipment

[0042] 1501 Processor

[0043] 1502 Memory

[0044] 15021 Operating System

[0045] 15022 Applications

[0046] 1503 Network Interface

[0047] 1504 Bus System

[0048] 1505 User Interface

[0049] Steps S21 to S23

[0050] Steps S61 to S64

[0051] Steps S71 to S74

[0052] Steps S81 to S83

[0053] Steps S91 to S94

[0054] Steps S101 to S104

[0055] Steps S1101 to S1118

[0056] Steps S1201 to S1211

[0057] Steps S1301 to S1317 DETAILED DESCRIPTION

[0058] The following describes the embodiments of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0059] It should be noted that the illustrations provided in the following embodiments are only used to illustrate the basic concept of the present application in a schematic manner, and therefore the illustrations only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0060] In the embodiments of the present application, the words "exemplary" or "for example" represent examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0061] In the embodiments of the present application, "at least one" refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can represent: a, b, c, ab, ac, bc or abc, where a, b, c can be single or multiple.

[0062] In order to improve production efficiency and reduce costs, automobile OEMs usually use the same model of camera hardware on multiple models. However, due to the different body designs, camera installation positions and camera orientations of different models, the requirements for camera image effects may also be different. Therefore, it is necessary to upgrade the camera's image effect parameter files and / or direction data according to the specific model. In addition, there may also be a need to upgrade the camera's main program firmware file. Therefore, how to provide a solution suitable for upgrading image effect parameter files, direction data and main program firmware files has become one of the technical problems that relevant technicians urgently need to solve.

[0063] At least to address the above-mentioned problem, an embodiment of the present application provides a method for upgrading a camera. Figure 1A and Figure 1B Two example diagrams of implementation scenarios of the embodiments of the present application are shown, but the present application is not limited thereto.

[0064] Figure 1A The implementation scenario of local upgrade is shown, which includes an electric inspection device, a domain control device and cameras 1 to n. The electric inspection device is connected to the domain control device for communication, and the domain control device is connected to the cameras 1 to n for communication. The camera includes a camera memory, which is, for example, a flash memory for storing the camera's firmware, image effect parameters, direction data, etc.

[0065] Figure 1BThe implementation scenario of remote upgrade is shown, which includes a cloud server, a domain control device and cameras 1 to n. It can be understood that in Figure 1B In the implementation scenario shown, the remote device is a cloud server, but the present application is not limited to this.

[0066] Figure 2 The flowchart of the camera upgrade method provided by the embodiment of the present application is shown. The method can be applied to Figure 1A and / or Figure 1B Domain controller in the. Figure 2 As shown, the upgrading method includes the following steps S21 to S23.

[0067] S21, receiving an upgrade request, the upgrade request including: an image effect parameter file upgrade request sent by the electrical inspection device, a direction data upgrade request sent by the electrical inspection device, and / or a main program firmware file upgrade request sent by a remote device.

[0068] S22, in response to the received upgrade request, burning the image effect parameter file, the direction data and / or the main program firmware file into the corresponding area of ​​the camera memory.

[0069] S23, determining whether the camera upgrade is successful.

[0070] In some implementations, the domain control device restarting the camera includes: the domain control device sending a restart instruction through a communication interface; and the camera stopping a current task and restarting after receiving the restart instruction.

[0071] See also Figure 3 In some implementations, the camera memory includes a main program firmware area, a calibration parameter area, an image effect parameter area, a direction data area, and a camera internal reference area. Among them, the main program firmware area is used to store the main program firmware file, and the main program firmware file includes two parts: the main program and the image effect parameter. The calibration parameter area is used to store calibration data, such as optical center calibration data, etc. The image effect parameter area is used to store the image effect parameters of the camera, and the image effect parameters can be extracted from the main program firmware area. The direction data area is used to store the direction data of the camera, and the direction data is used to determine the image direction of the camera. The camera internal reference area is used to store the internal reference data obtained by calibration. After the camera is powered on, the data in the above areas except the internal reference data can be loaded in sequence, and the data loaded later can be used to overwrite the same data loaded previously.

[0072] Exemplarily, the main program firmware area, calibration parameter area, image effect parameter area, direction data area and camera internal reference area can be aligned according to 4KB, but the present application is not limited to this.

[0073] In some implementations, the image effect parameter file and / or the main program firmware file includes camera version information, which includes sensor manufacturer, sensor model, version number, host manufacturer, vehicle model, lens manufacturer and / or lens model. Figure 4 An example of camera version information is shown, but the present application is not limited thereto.

[0074] For example, the process of the camera manufacturer releasing the upgrade file is as follows: Figure 5 As shown. The main program firmware file includes the main program and image effect parameters. The image effect parameter file can be obtained by extracting the image effect parameters in the main program firmware. The image effect parameter file and the main program firmware file both include camera version information. The two use the same version number. The version number of any file will increase after it is updated. Figure 5 As shown, when version 1 is updated to version 2, image effect parameter 1 (IQ parameter 1 shown in the figure) is upgraded to image effect parameter 2 (IQ parameter 2 shown in the figure), the version number is upgraded from version 1 to version 2, and image effect parameter 2 in the main program firmware file is extracted to obtain the upgraded image effect parameter file. When version 2 is updated to version 3, main program 1 is upgraded to main program 2, image effect parameter 2 is upgraded to image effect parameter 3 (IQ parameter 3 shown in the figure), the version number is upgraded from version 2 to version 3, and image effect parameter 3 in the main program firmware file is extracted to obtain the upgraded image effect file.

[0075] Since different models have different requirements for camera image effects and / or image directions, different models have different image effect parameters and / or version numbers. When different models of cars use the same camera hardware, the camera initialization version is the same, so the image effect parameter files and / or direction data in the cameras of different models need to be upgraded to the version of the corresponding model before the vehicle is off the assembly line at the factory.

[0076] See also Figure 6 In order to upgrade the image effect parameter file, in some implementations, burning the image effect parameter file to the corresponding area of ​​the camera memory includes the following steps S61 to S64.

[0077] S61, obtaining an upgrade file according to the vehicle model, wherein the upgrade file is located in the memory of the domain control device.

[0078] Exemplarily, when the car power is in the ON position, the electrical inspection device can send an image effect parameter file upgrade request to the domain control device.

[0079] S62, determining whether the upgrade file and the state of the camera meet the first upgrade condition.

[0080] S63: If the upgrade file and the state of the camera meet the first upgrade condition, determine whether the model of the camera matches the model information in the upgrade file.

[0081] S64, if the camera model matches the model information in the upgrade file, the upgrade file is burned into the image effect parameter area of ​​the camera memory.

[0082] In these implementations, determining whether the camera has been successfully upgraded includes: after the burning is completed, reading back the burned data from the image effect parameter area of ​​the camera memory to determine whether the read-back data is consistent with the upgrade file; if the read-back data is consistent with the upgrade file, powering off and restarting the camera to determine whether the camera version information is consistent with the version information in the upgrade file; if they are consistent, confirming that the upgrade is successful, otherwise confirming that the upgrade has failed.

[0083] See also Figure 7 In some implementations, determining whether the upgrade file and the camera status meet the first upgrade condition includes the following steps S71 to S74.

[0084] S71, verifying the signature of the upgrade file.

[0085] S72, if the signature verification of the upgrade file succeeds, initialize the deserialization pair and the camera to determine whether the camera is in place and whether the connection and communication of the camera are normal.

[0086] Exemplarily, determining whether the camera is in place and whether the connection and communication of the camera are normal includes: initializing the deserialization pair and the camera, and checking whether the camera is in place, whether the connection of the camera is normal, and whether the communication of the camera is normal.

[0087] S73, if the camera is in place and the connection and communication of the camera are normal, read the identification header of the upgrade file, and determine whether the upgrade file is an image effect parameter file according to the identification header.

[0088] S74: If the upgrade file is an image effect parameter file, determine whether the upgrade file and the state of the camera meet the first upgrade condition.

[0089] As described above, since the image effect parameter file is relatively small, its upgrade speed is fast, so in the embodiment of the present application, the image effect file can be upgraded by the electric inspection method. In the process of upgrading the image effect file by the electric inspection method, the vehicle model information can be not verified, and the version information of the default camera can be configured as the version information of the current vehicle model.

[0090] It should be noted that the judgment sequence shown in S71 to S74 is only one feasible method of the present application, but the present application is not limited thereto. For example, in some embodiments, it is also possible to first determine whether the camera is in place and whether the connection and communication of the camera are normal, and then determine whether the signature of the upgrade file is successfully verified when the camera is in place and the connection and communication of the camera are normal.

[0091] See also Figure 8 In some implementations, in response to a direction data upgrade request sent by the electrical inspection device, burning the direction data into a corresponding area of ​​the camera memory includes the following steps S81 to S83.

[0092] S81, obtaining the serial number of the camera.

[0093] Exemplarily, when the car power is in the ON position, the electrical inspection device may send a direction data upgrade request to the domain control device.

[0094] S82, determining whether the camera status meets the second upgrade condition.

[0095] Exemplarily, determining whether the state of the camera meets the second upgrade condition may include: initializing the deserialization pair and the camera, checking whether the camera is in place, whether the connection of the camera is normal, and whether the communication of the camera is normal. If the camera is in place and the connection and communication of the camera are normal, then determining that the state of the camera meets the second upgrade condition, otherwise determining that the state of the camera does not meet the second upgrade condition.

[0096] S83, if the state of the camera meets the second upgrade condition, the direction data is burned into the direction data area of ​​the camera.

[0097] In these implementations, determining whether the camera has been successfully upgraded includes: after the burning is completed, powering off and restarting the camera, reading the direction data of the current running state from the camera, and determining whether the read-back data is consistent with the direction data; if they are consistent, the upgrade is determined to be successful, otherwise the upgrade is determined to have failed.

[0098] In some implementations, a remote upgrade method, such as OTA (Over-The-Air), can be used to upgrade the main program firmware file. Fig. 9 In response to a main program firmware file upgrade request sent by a remote device, burning the main program firmware file to a corresponding area of ​​a camera memory includes the following steps S91 to S94.

[0099] S91, receiving an upgrade package sent by a remote device, where the upgrade package includes an upgrade file.

[0100] S92, determining whether the upgrade file and the camera status meet the third upgrade condition.

[0101] S93: If the upgrade file and the state of the camera meet the third upgrade condition, determine whether the camera model and the current vehicle model match the model information, vehicle model information, and lens information in the upgrade file.

[0102] S94, if the camera model and the current vehicle model match the model information, vehicle model information and lens information in the upgrade file, the upgrade file is burned into the main program firmware area of ​​the camera memory.

[0103] In these implementations, determining whether the camera has been successfully upgraded includes: after the burning is completed, reading back the burned data from the main program firmware area of ​​the camera memory to determine whether the read-back data is consistent with the upgrade file; if the read-back data is consistent with the upgrade file, powering off and restarting the camera to determine whether the camera version information is consistent with the version information in the upgrade file; if they are consistent, confirming that the upgrade is successful, otherwise confirming that the upgrade has failed.

[0104] For example, see Fig.10 , judging whether the upgrade file and the state of the camera meet the third upgrade condition includes the following steps S101 to S104.

[0105] S101, verifying the signature of the upgrade file.

[0106] S102, if the signature verification of the upgrade file is successful, initialize the deserialization pair and the camera to determine whether the camera is in place and whether the connection and communication of the camera are normal.

[0107] Exemplarily, determining whether the camera is in place and whether the connection and communication of the camera are normal includes: initializing the deserialization pair and the camera, and checking whether the camera is in place, whether the connection of the camera is normal, and whether the communication of the camera is normal.

[0108] S103, if the camera is in place and the connection and communication of the camera are normal, read the identification header of the upgrade file, and determine whether the upgrade file is a main program firmware file according to the identification header.

[0109] S104: If the upgrade file is a main program firmware file, determine whether the upgrade file and the state of the camera meet the third upgrade condition.

[0110] It should be noted that the judgment sequence shown in S101 to S104 is only one feasible method of the present application, but the present application is not limited thereto. For example, in some embodiments, it is also possible to first determine whether the camera is in place and whether the connection and communication of the camera are normal, and then determine whether the signature of the upgrade file is successfully verified when the camera is in place and the connection and communication of the camera are normal.

[0111] As described above, in the embodiment of the present application, the main program firmware file can be upgraded by remote upgrade, which is applicable to the scenario where both the main program and the image effect parameters need to be upgraded. In addition, the vehicle model information will be checked during the upgrade of the main program firmware file to prevent the wrong vehicle model version from being burned.

[0112] In some implementations, the upgrade method provided in the embodiments of the present application may also include: unprotecting the camera memory before burning the image effect parameter file, direction data and / or main program firmware file to the corresponding area of ​​the camera memory; and write-protecting the camera memory after restarting the camera.

[0113] Fig.11 The flowchart of upgrading the image effect file by electronic inspection in one embodiment of the present application is shown. In this embodiment, the domain control device includes an upgrade program and an algorithm library, and the number of cameras is n, where n is a positive integer. Fig.11 As shown, upgrading the image effect file by electronic inspection includes the following steps S1101 to S1118.

[0114] S1101, when the vehicle power gear is in the ON gear, the electric inspection equipment sends an image effect file upgrade request to the upgrade program.

[0115] S1102, in response to the image effect file upgrade request, the upgrade program obtains the image effect parameter file of the corresponding vehicle model as an upgrade file.

[0116] S1103, the upgrade program sends an upgrade request to the algorithm library.

[0117] S1104, in response to the upgrade request, the algorithm library verifies the signature of the upgrade file. If the verification is successful, step S1105 is executed, otherwise the upgrade failure is returned.

[0118] S1105, the algorithm library initializes the deserialization pair and the camera.

[0119] S1106, the algorithm library checks whether the n cameras are all in place, and whether the connection and communication of the n cameras are normal. If there are cameras that are not in place, abnormally connected and / or abnormally communicated, it returns that the upgrade failed, otherwise execute step S1107.

[0120] S1107, the algorithm library reads the file identification header of the upgrade file, and determines whether the upgrade file is an image effect parameter file according to the file identification header. If the upgrade file is not an image effect parameter file, it returns that the upgrade fails, otherwise it executes step S1108.

[0121] S1108, the algorithm library reads version information of the image effect file.

[0122] S1109, the algorithm library performs deprotection processing on the camera memory.

[0123] S1110, the algorithm library determines whether the model of the current camera matches the camera model information in the upgrade file. If they match, execute step S1111. If they do not match, jump to step S1113.

[0124] S1111, the algorithm library burns the image effect parameter file into the corresponding area of ​​the camera memory according to the predefined image effect parameter storage address.

[0125] S1112, after the burning is completed, the algorithm library reads back the data to determine whether the read-back data is consistent with the image effect parameter file. If they are consistent, jump to step S1114. If they are inconsistent, execute step S1113.

[0126] S1113: The algorithm library marks the current camera as failed to upgrade.

[0127] S1114, the algorithm library determines whether the traversal of n cameras has been completed. If the traversal of n cameras has been completed, step S1115 is executed, otherwise jump to step S1109 to start upgrading the next camera to be upgraded.

[0128] S1115, the algorithm library is powered off and the camera is restarted.

[0129] S1116, the algorithm library performs write protection processing on the camera.

[0130] S1117, the algorithm library reads the version number of the camera, marks the camera whose version number is the same as the version number information in the image effect parameter file as having been successfully upgraded, and marks the remaining cameras as having failed to upgrade.

[0131] S1118, if n cameras are upgraded successfully, the algorithm library returns upgrade success, otherwise the algorithm library returns upgrade failure.

[0132] Fig.12 The flowchart of upgrading the direction data of the camera by electronic inspection in one embodiment of the present application is shown. In this embodiment, the domain control device includes an upgrade program and an algorithm library. Fig.12 As shown, the process of upgrading the direction data by means of electrical inspection includes the following steps S1201 to S1211.

[0133] S1201, when the vehicle power gear is in the ON gear, the electric inspection equipment sends a direction data upgrade request to the upgrade program.

[0134] S1202: The upgrade program obtains the camera serial number in response to the direction data upgrade request.

[0135] S1203, the upgrade program sends an upgrade request to the algorithm library.

[0136] S1204: The algorithm library initializes the deserialization pair and the camera in response to the upgrade request.

[0137] S1205, the algorithm library checks whether the n cameras are all in place, and whether the connection and communication of the n cameras are normal. If there are cameras that are not in place, abnormally connected and / or abnormally communicated, it returns that the upgrade failed, otherwise execute step S1206.

[0138] S1206, the algorithm library deprotects the camera memory.

[0139] S1207, the algorithm library burns the direction data of the specified camera into the corresponding area of ​​the camera memory.

[0140] S1208, the algorithm library is powered off and the camera is restarted.

[0141] S1200: The algorithm library performs write protection processing on the camera memory.

[0142] S1210, the algorithm library reads the image direction of the camera.

[0143] S1211, the algorithm library determines whether the read image direction is consistent with the direction data. If they are consistent, it returns that the upgrade is successful, otherwise it returns that the upgrade fails.

[0144] Fig.13 The flowchart of the main program firmware file of the camera is upgraded by OTA in one embodiment of the present application. In this embodiment, the domain control device includes an upgrade program and an algorithm library, and the remote device is a cloud server. Fig.13 As shown, upgrading the main program firmware file by OTA includes the following steps S1301 to S1317.

[0145] S1301, the cloud server sends the upgrade file to the domain control device.

[0146] S1302: After receiving the upgrade file, the domain control device sends an upgrade request to the algorithm library.

[0147] S1303, in response to the upgrade request, the algorithm library verifies the signature of the upgrade file. If the verification is successful, step S1304 is executed, otherwise the upgrade failure is returned.

[0148] S1304, the algorithm library initializes the deserialization pair and the camera.

[0149] S1305, the algorithm library checks whether the n cameras are all in place, and whether the connection and communication of the n cameras are normal. If there are cameras that are not in place, abnormally connected and / or abnormally communicated, it returns that the upgrade failed, otherwise execute step S1306.

[0150] S1306, the algorithm library reads the file identification header of the upgrade file, and determines whether the upgrade file is a main program firmware file according to the file identification header. If the upgrade file is not a main program firmware file, it returns that the upgrade failed, otherwise executes step S1307.

[0151] S1307, the algorithm library reads the version information of the main program firmware file.

[0152] S1308, the algorithm library deprotects the camera memory.

[0153] S1309, the algorithm library determines whether the current camera model and vehicle model match the camera model information and vehicle model information in the upgrade file. If they match, execute step S1310. If not, jump to step S1312.

[0154] S1310, the algorithm library burns the main program firmware file into the corresponding area of ​​the camera memory according to the predefined main program firmware storage address.

[0155] S1311, after the burning is completed, the algorithm library reads back the data to determine whether the read-back data is consistent with the main program firmware file. If they are consistent, jump to step S1313. If they are inconsistent, execute step S1312.

[0156] S1312: The algorithm library marks the current camera as failed to upgrade.

[0157] S1313, the algorithm library determines whether the traversal of n cameras has been completed. If the traversal of n cameras has been completed, step S1314 is executed, otherwise jump to step S1308 to start upgrading the next camera to be upgraded.

[0158] S1314, the algorithm library is powered off and the camera is restarted.

[0159] S1315, the algorithm library performs write protection processing on the camera.

[0160] S1316, the algorithm library reads the version number of the camera, marks the camera whose version number is the same as the version number information in the main program firmware file as upgraded successfully, and marks the remaining cameras as upgraded failed.

[0161] S1317, if n cameras are upgraded successfully, the algorithm library returns an upgrade success, otherwise the algorithm library returns an upgrade failure.

[0162] The protection scope of the camera upgrade method provided in the embodiment of the present application is not limited to the execution order of the steps listed in the present embodiment. All solutions implemented by adding, reducing or replacing steps in the prior art based on the principles of the present application are included in the protection scope of the present application.

[0163] The embodiment of the present application also provides an upgrade device for a camera, which can implement the upgrade method for a camera described in the present application. However, the implementation device of the upgrade method for a camera described in the present application includes but is not limited to the structure of the upgrade device for a camera listed in the present embodiment. All structural deformations and replacements of the prior art made according to the principles of the present application are included in the protection scope of the present application.

[0164] Fig.14 is a schematic block diagram of a camera upgrade device provided in an embodiment of the present application. Fig.14 As shown, the upgrade device 1400 for a camera includes an upgrade request receiving module 1401, an upgrade file burning module 1402, and an upgrade result judgment module 1403. The upgrade request receiving module 1401 is used to receive an upgrade request. The upgrade file burning module 1402 is used to respond to the upgrade request and burn the image effect parameter file, direction data, and / or main program firmware file to the corresponding area of ​​the camera memory. The upgrade result judgment module 1403 is used to judge whether the camera is successfully upgraded.

[0165] It should be understood that the specific process of each module executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0166] The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by the processor, the upgrade method for the camera provided by the embodiment of the present application is implemented. A person of ordinary skill in the art can understand that all or part of the steps in the method for implementing the above embodiment can be completed by instructing the processor through a program, and the program can be stored in a computer-readable storage medium, and the storage medium is a non-transitory medium, such as a random access memory, a read-only memory, a flash memory, a hard disk, a solid-state hard disk, a magnetic tape, a floppy disk, an optical disc, and any combination thereof. The above storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more available media integrated. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a digital video disc (DVD)), or a semiconductor medium (for example, a solid-state disk (SSD)), etc.

[0167] An embodiment of the present application also provides an electronic device. Fig.15 is a schematic block diagram of an electronic device provided in an embodiment of the present application. Fig.15 As shown, the electronic device 1500 includes: at least one processor 1501, a memory 1502, at least one network interface 1503 and a user interface 1505. The various components in the electronic device 1500 are coupled together through a bus system 1504. It can be understood that the bus system 1504 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1504 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Fig.15 In the specification, various buses are labeled as bus systems.

[0168] The user interface 1505 may include a display, a keyboard, a mouse, a trackball, a click gun, keys, buttons, a touch pad or a touch screen.

[0169] It is understood that the memory 1502 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM, Read Only Memory), a programmable read-only memory (PROM, Programmable Read-Only Memory), which is used as an external cache. By way of exemplary but not limiting explanation, many forms of RAM are available, such as static random access memory (SRAM, Static Random Access Memory), synchronous static random access memory (SSRAM, Synchronous Static Random Access Memory). The memory described in the embodiments of the present application is intended to include but is not limited to these and any other suitable categories of memory.

[0170] The memory 1502 in the embodiment of the present application is used to store various categories of data to support the operation of the electronic device 1500. Examples of these data include: any executable program for operating on the electronic device 1500, such as an operating system 15021 and an application 15022; the operating system 15021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks. The application 15022 may include various applications, such as a media player (Media Player), a browser (Browser), etc., for implementing various application services. The upgrade method for the camera provided in the embodiment of the present application may be included in the application 15022.

[0171] The method disclosed in the above embodiment of the present application can be applied to the processor 1501, or implemented by the processor 1501. The processor 1501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor 1501 or an instruction in the form of software. The above processor 1501 may be a general processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 1501 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general processor 1501 may be a microprocessor or any conventional processor, etc. In combination with the steps of the accessory optimization method provided in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0172] In an exemplary embodiment, the electronic device 1500 may be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD) to execute the aforementioned method.

[0173] The terms "component", "module", "system", etc. used in this specification are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program and / or a computer. By way of illustration, both applications running on a computing device and a computing device can be components. One or more components may reside in a process and / or an execution thread, and a component may be located on a computer and / or distributed between two or more computers. In addition, these components may be executed from various computer-readable media having various data structures stored thereon. Components may, for example, communicate through local and / or remote processes according to signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system and / or a network, such as the Internet interacting with other systems through signals).

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

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

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

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

[0178] In the above embodiments, the functions of each functional unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When loading and executing computer program instructions (programs) on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center.

[0179] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk or an optical disk.

[0180] In summary, the embodiments of the present application provide an upgrade method, device, storage medium and electronic device for a camera, which are used to implement image effect parameter file upgrade, main program firmware file upgrade and / or camera image direction adjustment. When different vehicle models use the same camera hardware, the image effect parameter file, direction data and / or main program firmware file of the camera hardware can be upgraded to files matching the vehicle model based on the upgrade method provided by the embodiments of the present application. Therefore, the upgrade method provided by the embodiments of the present application can be applied to the situation where different vehicle models use the same model of camera hardware. In addition, the embodiments of the present application propose a partitioning method for the camera memory, which separates the storage areas of the main program firmware, image effect parameters and image direction data from each other to avoid mutual influence between these data. Furthermore, the embodiments of the present application define a new firmware version number rule, which can fully represent information such as sensor manufacturers, sensor models, version numbers, host manufacturers, vehicle models, lens manufacturers and / or lens models, which is conducive to users to conveniently perform version management and version verification, and can avoid upgrading the wrong version. In addition, the embodiments of the present application include an electric inspection upgrade process and a remote upgrade process, which can be used to implement image effect parameter upgrades, vehicle model version information changes and image direction adjustments. In an embodiment of the present application, an electrical inspection upgrade process can be used to upgrade image effect files and / or direction data, and this method can improve the upgrade speed and factory efficiency. In an embodiment of the present application, a remote upgrade process can be used to upgrade the main program firmware file, and this method can be applicable to the scenario where the main program and image effect files are upgraded at the same time. The embodiment of the present application defines the upgrade process and verification rules in detail. The upgrade process and verification rules provided by the embodiment of the present application can improve the success rate of version upgrades, prevent the occurrence of version burning errors, and ensure that the version burned into the camera memory is a version that can be used normally, avoiding the situation where the burning is successful but cannot be used normally. Therefore, the present application effectively overcomes the various shortcomings in the prior art and has a high industrial utilization value.

[0181] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A camera upgrade method, characterized in that: include: receiving an upgrade request, the upgrade request including: an image effect parameter file upgrade request sent by an electrical inspection device, a direction data upgrade request sent by the electrical inspection device, and / or a main program firmware file upgrade request sent by a remote device; In response to the upgrade request, burning the image effect parameter file, the direction data and / or the main program firmware file into the corresponding area of ​​the camera memory; Determine whether the camera upgrade is successful.

2. The upgrading method according to claim 1, characterized in that: The camera memory includes a main program firmware area, a calibration parameter area, an image effect parameter area, a direction data area and / or a camera internal parameter area; and / or The image effect parameter file and / or the main program firmware file include camera version information, and the camera version information includes sensor manufacturer, sensor model, version number, host manufacturer, vehicle model, lens manufacturer and / or lens model.

3. The upgrading method according to claim 1, characterized in that: In response to the image effect parameter file upgrade request sent by the electrical inspection device, burning the image effect parameter file to a corresponding area of ​​the camera memory includes: Get the upgrade file according to the vehicle model; Determining whether the upgrade file and the state of the camera meet a first upgrade condition; If the upgrade file and the state of the camera meet the first upgrade condition, determining whether the model of the camera matches the model information in the upgrade file; If the model of the camera matches the model information in the upgrade file, burning the upgrade file into the image effect parameter area of ​​the camera memory; Determining whether the camera is successfully upgraded includes: After the burning is completed, the burned data is read back from the image effect parameter area of ​​the camera memory to determine whether the read-back data is consistent with the upgrade file; If the read-back data is consistent with the upgrade file, the camera is powered off and restarted to determine whether the camera version information is consistent with the version information in the upgrade file.

4. The upgrading method according to claim 3, characterized in that: Determining whether the upgrade file and the state of the camera meet the first upgrade condition includes: Verifying the signature of the upgrade file; If the signature verification of the upgrade file succeeds, the deserialization pair and the camera are initialized to determine whether the camera is in place and whether the connection and communication of the camera are normal; If the camera is in place and the connection and communication of the camera are normal, then reading the identification header of the upgrade file, and judging whether the upgrade file is the image effect parameter file according to the identification header; If the upgrade file is the image effect parameter file, it is determined that the upgrade file and the state of the camera meet the first upgrade condition.

5. The upgrading method according to claim 1, characterized in that: In response to the direction data upgrade request sent by the electrical inspection device, burning the direction data into a corresponding area of ​​the camera memory includes: Obtain the serial number of the camera; Determining whether the state of the camera meets the second upgrade condition; If the state of the camera meets the second upgrade condition, burning the direction data into the direction data area of ​​the camera; Determining whether the camera is successfully upgraded includes: after the burning is completed, powering off and restarting the camera, reading the direction data of the current running state from the camera, and determining whether the read-back data is consistent with the direction data.

6. The upgrading method according to claim 5, characterized in that: Determining whether the state of the camera meets the second upgrade condition includes: Initialize the deserialization pair and the camera, determine whether the camera is in place and whether the connection and communication of the camera are normal; If the camera is in place and the connection and communication of the camera are normal, it is determined that the state of the camera meets the second upgrade condition.

7. The upgrading method according to claim 1, characterized in that: In response to the main program firmware file upgrade request sent by the remote device, burning the main program firmware file to the corresponding area of ​​the camera memory includes: Receiving an upgrade package sent by the remote device, wherein the upgrade package includes an upgrade file; Determining whether the upgrade file and the state of the camera meet a third upgrade condition; If the upgrade file and the state of the camera meet the third upgrade condition, determining whether the camera model and the current vehicle model match the model information, vehicle model information and lens information in the upgrade file; If the camera model and the current vehicle model match the model information, vehicle model information and lens information in the upgrade file, the upgrade file is burned into the main program firmware area of ​​the camera memory; Determining whether the camera is successfully upgraded includes: After the burning is completed, the burned data is read back from the main program firmware area of ​​the camera memory to determine whether the read-back data is consistent with the upgrade file; If the read-back data is consistent with the upgrade file, the camera is powered off and restarted to determine whether the camera version information is consistent with the version information in the upgrade file.

8. An upgrading device for a camera, characterized in that: include: An upgrade request receiving module, used for receiving an upgrade request, wherein the upgrade request includes: an image effect parameter file upgrade request sent by an electric inspection device, a direction data upgrade request sent by the electric inspection device, and / or a main program firmware file upgrade request sent by a remote device; An upgrade file burning module, used for burning the image effect parameter file, the direction data and / or the main program firmware file into the corresponding area of ​​the camera memory in response to the upgrade request; The upgrade result judgment module is used to judge whether the camera upgrade is successful.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the upgrading method according to any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: The electronic device comprises: A memory storing a computer program; A processor is communicatively connected to the memory, and executes the upgrading method according to any one of claims 1 to 7 when calling the computer program.

Images