Image acquisition component recognition method, image acquisition component recognition device and storage medium

Abstract

The present disclosure relates to an image acquisition component identification method, an image acquisition component identification device, and a storage medium. The image acquisition component identification method is applied to a terminal, and the terminal includes multiple image acquisition components. The method includes: in response to a trigger, loading the corresponding driver files of multiple image acquisition components, calling a driver record file, and recording the driver file names of one or more image acquisition components corresponding to the multiple image acquisition components in the driver record file; if the driver record file is successfully called, then based on the driver file name recorded in the driver record file, a first driver file loading index table is established, and multiple image acquisition components are identified based on the first driver file loading index table. Through the embodiments of the present disclosure, the loading time of the image acquisition component driver is optimized, the terminal performance is improved, and thus the user experience is enhanced.

Description

Technical Field

[0001] The present disclosure relates to the field of terminal technology, and in particular to an image acquisition component recognition method, an image acquisition component recognition device, and a storage medium. Background Art

[0002] With the rapid development of technology, terminal technology has evolved rapidly. To meet people's growing needs, terminal performance and configuration are becoming increasingly advanced. Among them, terminal camera performance is of particular concern. The configuration of image acquisition components has evolved from a few hundred pixels to tens of millions or even hundreds of millions of pixels. The number of cameras has also increased from a single camera to dual cameras and even multiple cameras.

[0003] Terminals equipped with multiple cameras often use different driver software for their camera modules due to differences in production channels and manufacturing processes. Loading multiple cameras in a terminal can increase the time it takes to load the driver software. In severe cases, after the terminal is powered on and the user interface is displayed, the driver may not have finished loading when the user attempts to use the camera to shoot. This can prevent the user from using the camera properly, negatively impacting the user experience. Summary of the Invention

[0004] In order to overcome the problems existing in the related art, the present disclosure provides an image acquisition component recognition method, an image acquisition component recognition device and a storage medium.

[0005] According to one aspect of an embodiment of the present disclosure, there is provided an image acquisition component identification method, which is applied to a terminal, wherein the terminal includes a plurality of image acquisition components, and the image acquisition component identification method includes: in response to a trigger, loading driver files corresponding to the plurality of image acquisition components, calling a driver record file, wherein the driver file name of the driver file corresponding to one or more image acquisition components among the plurality of image acquisition components is recorded in the driver record file; if the driver record file is successfully called, establishing a first driver file loading index table based on the driver file name recorded in the driver record file, and identifying the plurality of image acquisition components based on the first driver file loading index table.

[0006] In one embodiment, the terminal includes a driver file data packet, and the driver file data packet includes a number of driver files that is greater than the number of image acquisition components included in the terminal. The image acquisition component identification method further includes: if the driver record file is not called, creating a driver record file, and creating a second driver file loading index table based on the driver file included in the driver file data packet; identifying the multiple image acquisition components based on the second driver file loading index table, and recording the driver file names of the driver files corresponding to the multiple image acquisition components successfully identified based on the second driver file loading index table in the driver record file.

[0007] In one embodiment, the driver file names of the driver files corresponding to the multiple image acquisition components that are successfully identified based on the second driver file loading index table are recorded in the driver record file, including: traversing each driver file in the second driver file loading index table, and for each driver file, matching multiple driver information corresponding to the driver file with corresponding information of the multiple image acquisition components in sequence; in response to multiple driver information corresponding to the first driver file in the second driver file loading index table and corresponding information of the first image acquisition component in the multiple image acquisition components all being successfully matched, determining that the first driver file is the driver file successfully identified by the first image acquisition component, and recording the file name of the first driver file in the driver record file.

[0008] In one embodiment, identifying the multiple image acquisition components based on the first driver file loading index table includes: traversing each driver file in the first driver file loading index table, and for each driver file, matching multiple driver information corresponding to the driver file with corresponding information of the multiple image acquisition components in turn; in response to successful matching of multiple driver information corresponding to each driver file in the first driver file loading index table with corresponding information of each image acquisition component in the multiple image acquisition components, determining that each image acquisition component in the multiple image acquisition components is successfully identified.

[0009] In one embodiment, the terminal includes a driver file data packet, and the identifying of the multiple image acquisition components based on the first driver file loading index table includes: in response to the presence of driver information that fails to match the information corresponding to the second image acquisition component among the multiple driver information corresponding to the second driver file in the first driver file loading index table, determining a third driver file with the same type identifier as the second driver file in the driver file data packet; traversing the multiple driver information corresponding to the third driver file, and matching the multiple driver information with the information corresponding to the second image acquisition component; and in response to the multiple driver information corresponding to the third driver file all successfully matching the information corresponding to the second image acquisition component, determining that the second image acquisition component has been successfully identified.

[0010] In one embodiment, the image acquisition component identification method further includes: in response to multiple driving information corresponding to the third driving file and the corresponding information of the second image acquisition component all successfully matching, deleting the file name of the second driving file in the driving record file, and recording the file name of the third driving file in the driving record file.

[0011] According to another aspect of an embodiment of the present disclosure, there is provided an image acquisition component identification device, which is applied to a terminal, wherein the terminal includes a plurality of image acquisition components, and the image acquisition component identification device includes: a calling module, for loading driver files corresponding to the plurality of image acquisition components in response to a trigger, and calling a driver record file, wherein the driver file names of the driver files corresponding to one or more image acquisition components among the plurality of image acquisition components are recorded in the driver record file; an establishing module, for establishing a first driver file loading index table based on the driver file name recorded in the driver record file when the driver record file is successfully called; and an identification module, for identifying the plurality of image acquisition components based on the first driver file loading index table.

[0012] In one embodiment, the terminal includes a driver file data packet, and the driver file data packet includes a number of driver files that is greater than the number of image acquisition components included in the terminal. The device also includes: a creation module, which is used to create a driver record file when the driver record file is not called, and create a second driver file loading index table based on the driver file included in the driver file data packet, and record in the driver record file the driver file names of the driver files corresponding to the multiple image acquisition components that are successfully identified based on the second driver file loading index table; the identification module is also used to identify the multiple image acquisition components based on the second driver file loading index table.

[0013] In one embodiment, the creation module records the driver file names of the driver files corresponding to the multiple image acquisition components successfully identified based on the second driver file loading index table in the driver record file in the following manner: traverse the driver files in the second driver file loading index table, and for each driver file, match the multiple driver information corresponding to the driver file with the corresponding information of the multiple image acquisition components in turn; in response to the multiple driver information corresponding to the first driver file in the second driver file loading index table and the corresponding information of the first image acquisition component in the multiple image acquisition components all matching successfully, determine that the first driver file is the driver file successfully identified by the first image acquisition component, and record the file name of the first driver file in the driver record file.

[0014] In one embodiment, the identification module identifies the multiple image acquisition components based on the first driver file loading index table in the following manner: traverse each driver file in the first driver file loading index table, and for each driver file, match the multiple driver information corresponding to the driver file with the corresponding information of the multiple image acquisition components in turn; in response to the multiple driver information corresponding to each driver file in the first driver file loading index table successfully matching the corresponding information of each image acquisition component in the multiple image acquisition components, determine that each image acquisition component in the multiple image acquisition components is successfully identified.

[0015] In one embodiment, the terminal includes a driver file data packet, and the identification module identifies the multiple image acquisition components based on the first driver file loading index table in the following manner: in response to the presence of driver information that fails to match the information corresponding to the second image acquisition component in the multiple driver information corresponding to the second driver file in the first driver file loading index table, determining a third driver file with the same type identifier as the second driver file in the driver file data packet; traversing the multiple driver information corresponding to the third driver file, and matching the multiple driver information with the information corresponding to the second image acquisition component; in response to the multiple driver information corresponding to the third driver file all successfully matching the information corresponding to the second image acquisition component, determining that the second image acquisition component has been successfully identified.

[0016] In one embodiment, the device also includes: an update module, which is used to delete the file name of the second drive file in the drive record file and record the file name of the third drive file in the drive record file in response to all the multiple drive information corresponding to the third drive file successfully matching the corresponding information of the second image acquisition component.

[0017] According to another aspect of an embodiment of the present disclosure, there is provided an image acquisition component recognition device, comprising: a processor; and a memory for storing processor-executable instructions; wherein the processor is configured to: execute any one of the aforementioned image acquisition component recognition methods.

[0018] According to another aspect of the embodiments of the present disclosure, a non-transitory computer-readable storage medium is provided. When the instructions in the storage medium are executed by the processor of the mobile terminal, the mobile terminal can execute any one of the aforementioned image acquisition component recognition methods.

[0019] The technical solution provided by the embodiments of the present disclosure may include the following beneficial effects: optimizing the loading time of the image acquisition component driver, improving terminal performance, and thus enhancing user experience.

[0020] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0022] Figure 1 The flowchart of the image acquisition component identification method in the current technology is shown.

[0023] Figure 2 The figure is a flowchart of a method for identifying an image acquisition component according to an exemplary embodiment of the present disclosure.

[0024] Figure 3 The figure is a flowchart of a method for identifying an image acquisition component according to another exemplary embodiment of the present disclosure.

[0025] Figure 4 The figure is a flowchart of a method for identifying an image acquisition component according to another exemplary embodiment of the present disclosure.

[0026] Figure 5 The figure is a flowchart of a method for identifying an image acquisition component according to another exemplary embodiment of the present disclosure.

[0027] Figure 6 The figure is a flowchart of a method for identifying an image acquisition component according to another exemplary embodiment of the present disclosure.

[0028] Figure 7 The figure is a flowchart of a method for identifying an image acquisition component according to another exemplary embodiment of the present disclosure.

[0029] Figure 8The figure is a flowchart of a method for identifying an image acquisition component according to an exemplary embodiment of the present disclosure.

[0030] Figure 9 The figure is a flowchart of a method for identifying an image acquisition component according to an exemplary embodiment of the present disclosure.

[0031] Figure 10 The figure is a block diagram of an image acquisition component recognition device according to an exemplary embodiment of the present disclosure.

[0032] Figure 11 The figure is a block diagram of an image acquisition component recognition device according to an exemplary embodiment of the present disclosure.

[0033] Figure 12 The figure is a block diagram of an image acquisition component recognition device according to an exemplary embodiment of the present disclosure.

[0034] Figure 13 The figure is a block diagram of a device for identifying an image acquisition component according to an exemplary embodiment. DETAILED DESCRIPTION

[0035] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0036] Smart terminals with camera functions are becoming more and more common. The camera function has become one of the important functions of smart terminals. The camera function is realized through the image acquisition component set in the terminal. The camera function of smart terminals is an important evaluation indicator of terminal performance. In order to improve the user experience and meet the needs of users, the multi-camera function has become a major development direction of camera technology.

[0037] In related technologies, the terminal motherboard and camera module communicate via the I2C (Inter-Integrated Circuit) bus. The camera module connects to the control chip on the phone motherboard via the I2C bus. The control chip is the master, and the camera module's multiple functional modules connected to the I2C bus are slaves. The I2C bus is a bidirectional, two-wire serial bus that transmits information between connected devices via the serial data (SDA) and serial clock (SCL) lines.

[0038] Terminals equipped with multiple cameras often use different driver software due to differences in production channels and manufacturing processes. Loading multiple cameras in a terminal can increase the time it takes to load the driver software. In severe cases, after the terminal is powered on and the user interface is displayed, the driver may not have finished loading when the user attempts to use the camera to shoot. This can prevent the user from using the camera properly, negatively impacting the user experience.

[0039] Figure 1 A flow chart showing the image acquisition component identification method in the current technology is shown. Figure 1 , the image acquisition component identification method includes the following steps.

[0040] In step S101, all driver files are traversed and an index table is created according to the file names.

[0041] In step S102, the camera module's EEPROM information is read through the I2C configuration configured in the driver file. EEPROM, or electrically erasable programmable read-only memory, is primarily used to store factory-programmed data for calibration and to maintain module consistency.

[0042] In step S103, it is determined whether the information of the driver file in the index table is consistent with the read EEPROM information.

[0043] When the information of the driver file in the index table is inconsistent with the read EEPROM information, step S102 is executed, that is, the next driver file is read in the driver file, and the EEPROM information of the camera module is read through the I2C configuration configured in the driver.

[0044] When the information of the driver file in the index table is consistent with the read EEPROM information, step S104 is executed to read the sensor ID through the I2C configuration of the sensor in the driver file.

[0045] In step S105 , it is determined whether the information of the driving file in the index table matches the read sensor ID.

[0046] When the information of the driver file in the index table does not match the read sensor ID, step S102 is executed, that is, the next driver file is read in the driver file, and the EEPROM information of the camera module is read through the I2C configuration configured in the driver.

[0047] When the information of the driver file in the index table matches the read sensor ID, step S106 is executed, the current driver file is loaded, and step S102 is executed, that is, the next driver file is read in the driver file until all driver files of the terminal are traversed.

[0048] In the above process, the driver files of the terminal are traversed in a loop to detect and load the driver of the image acquisition component. When the terminal driver files include a large number of driver files of the image acquisition components, the driver loading time of the image acquisition components is too long.

[0049] Based on this, the present disclosure provides an image acquisition component identification method. When the terminal loads the corresponding driver files of multiple image acquisition components, a first driver file loading index table is established based on the driver record file, and multiple image acquisition components are identified based on the index table, thereby optimizing the loading time of the image acquisition component driver.

[0050] Figure 2 This is a flowchart of a method for identifying an image acquisition component according to an exemplary embodiment. The method is used in a terminal that includes multiple image acquisition components. The terminal may be, for example, a smartphone, a tablet computer, or a wearable device. The present disclosure does not limit the type of device to which the present disclosure is applied. Figure 2 As shown, the image acquisition component identification method includes the following steps.

[0051] In step S201, in response to a trigger, the driver files corresponding to the multiple image acquisition components are loaded, and a driver record file is called, which records the driver file names of the driver files corresponding to one or more image acquisition components among the multiple image acquisition components.

[0052] In step S202, if the driver record file is successfully called, a first driver file loading index table is established based on the driver file name recorded in the driver record file, and multiple image acquisition components are identified based on the first driver file loading index table.

[0053] In the disclosed embodiment, upon startup, the terminal loads driver files corresponding to multiple image acquisition components. A driver log file is called, which records the driver file names corresponding to one or more of the multiple image acquisition components. It is understood that the image acquisition components and driver files have a corresponding relationship.

[0054] When the driver record file is successfully called, a first driver file loading index table is created based on the driver file name recorded in the driver record file. The first driver file loading index table records the driver file name and the file contents of the driver file corresponding to the driver file name. The driver file may include, for example, the address information and the value of the image acquisition component. Multiple image acquisition components are identified based on the first driver file loading index table.

[0055] According to an embodiment of the present disclosure, when loading driver files corresponding to multiple image acquisition components in a terminal, a first driver file loading index table is established based on a driver record file, and multiple image acquisition components are identified based on the index table, thereby optimizing the loading time of the image acquisition component driver, improving terminal performance, and thus enhancing user experience.

[0056] Figure 3 FIG. 1 is a flow chart showing a method for identifying an image acquisition component according to another exemplary embodiment of the present disclosure. Figure 3 As shown, the image acquisition component identification method includes the following steps.

[0057] In step S301, in response to a trigger, the driver files corresponding to the multiple image acquisition components are loaded, and a driver record file is called, which records the driver file names of the driver files corresponding to one or more image acquisition components among the multiple image acquisition components.

[0058] In step S302, if the driver record file is successfully called, a first driver file loading index table is established based on the driver file name recorded in the driver record file, and multiple image acquisition components are identified based on the first driver file loading index table.

[0059] In step S303, if the driver record file is not called, a driver record file is created, and a second driver file loading index table is created based on the driver files included in the driver file data package.

[0060] In step S304, multiple image acquisition components are identified based on the second driver file loading index table, and the driver file names of the driver files corresponding to the multiple image acquisition components successfully identified based on the second driver file loading index table are recorded in the driver record file.

[0061] In an embodiment of the present disclosure, the terminal loads driver files corresponding to multiple image acquisition components. The driver record file is called, and the driver record file records the driver file names corresponding to one or more image acquisition components among the multiple image acquisition components. When the driver record file is called successfully, a first driver file loading index table is established based on the driver file name recorded in the driver record file. The index table records the driver file name and the file content of the driver file corresponding to the driver file name. The driver file may include, for example, the address information of the image acquisition component, the ID value of the image acquisition component and other information. Multiple image acquisition components are identified based on the first driver file loading index table.

[0062] When the driver record file is not called and the driver record file does not exist in the terminal, a driver record file is created, and based on the driver file included in the driver file data packet, a second driver file loading index table is created. In one embodiment of the present disclosure, the terminal includes a driver file data packet, and the driver file data packet includes driver files whose number is greater than the number of image acquisition components included in the terminal. That is to say, since the multiple image acquisition components included in the terminal are applicable to different driver files, even if the image acquisition components are arranged at the same part of the terminal, the applicable driver files are different due to their production factors. Therefore, in order to achieve the correct identification and loading of multiple image acquisition components of the terminal, the number of driver files for the number of image acquisition components in the driver file data packet of the terminal is greater than the number of image acquisition components actually included in the terminal. It can be understood that the second driver file loading index table corresponds to all driver file names in the driver file data packet included in the terminal, that is, the second driver file contains the file names of driver files whose number is greater than the number of image acquisition components included in the terminal.

[0063] Multiple image acquisition components are identified based on the second driver file loading index table, and the driver file names of the driver files corresponding to the multiple image acquisition components successfully identified based on the second driver file loading index table are recorded in the driver record file.

[0064] According to an embodiment of the present disclosure, when a terminal loads driver files corresponding to multiple image acquisition components, when a driver record file exists, a first driver file loading index table is established based on the driver record file, and multiple image acquisition components are identified based on the index table; when a driver record file does not exist, a driver record file is created, and based on the driver file included in the driver file data packet, a second driver file loading index table is created, multiple image acquisition components are identified based on the second driver file loading index table, and the driver file names of the driver files corresponding to the multiple image acquisition components successfully identified based on the second driver file loading index table are recorded in the driver record file, thereby saving the loading time of the image acquisition component driver.

[0065] Figure 4 FIG. 1 is a flow chart showing a method for recording a driver file name in a driver record file according to an exemplary embodiment of the present disclosure. Figure 4 As shown, the method for recording a driver file name in a driver record file includes the following steps.

[0066] In step S401, each driver file in the second driver file loading index table is traversed, and for each driver file, multiple driver information corresponding to the driver file is matched with corresponding information of multiple image acquisition components in sequence.

[0067] In step S402, in response to the successful matching of multiple driving information corresponding to the first driving file in the second driving file loading index table with the corresponding information of the first image acquisition component in the multiple image acquisition components, it is determined that the first driving file is the driving file successfully identified by the first image acquisition component, and the file name of the first driving file is recorded in the driving record file.

[0068] In an embodiment of the present disclosure, the terminal loads the driver files corresponding to the multiple image acquisition components. When the driver record file is not called, a driver record file is created, and a second driver file loading index table is created based on the driver file included in the driver file data packet. When creating the driver record file, each driver file in the second driver file loading index table is traversed, and for each driver file, the multiple driver information corresponding to the driver file is matched with the corresponding information of the multiple image acquisition components in turn. The driver information may include the address information of the image acquisition component, the value of the image acquisition component, and other driver information, for example, the EEPROM information of the image acquisition component, the sensor ID of the image acquisition component, etc.

[0069] When traversing each driver file in the second driver file loading index table, if the multiple driver information corresponding to the first driver file successfully matches the corresponding information of the first image acquisition component in the multiple image acquisition components, the first driver file is determined to be the driver file successfully recognized by the first image acquisition component, and the file name of the first driver file is recorded in the driver record file. This cycle continues until all driver files in the second driver file loading index table are traversed and the driver record file is created.

[0070] According to an embodiment of the present disclosure, each driver file in the second driver file loading index table is traversed, and for each driver file, multiple driver information corresponding to the driver file is matched with corresponding information of multiple image acquisition components in turn, and the first driver file that successfully matches the first image acquisition component is recorded in the driver record file. Until the traversal is completed, the driver record file is successfully created, providing a basis for subsequent loading of the image acquisition component driver.

[0071] Figure 5 FIG. 1 is a flow chart showing a method for identifying multiple image acquisition components based on a first drive file loading index table according to an exemplary embodiment of the present disclosure. Figure 5 As shown, the method for identifying multiple image acquisition components by loading an index table based on a first drive file includes the following steps.

[0072] In step S501, each driver file in the first driver file loading index table is traversed, and for each driver file, multiple driver information corresponding to the driver file is matched with corresponding information of multiple image acquisition components in sequence.

[0073] In step S502, in response to a successful match between a plurality of driving information corresponding to each driving file in the first driving file loading index table and corresponding information of each image acquisition component in the plurality of image acquisition components, it is determined that each image acquisition component in the plurality of image acquisition components is successfully identified.

[0074] In an embodiment of the present disclosure, the terminal loads driver files corresponding to multiple image acquisition components and calls a driver record file, which records the driver file names of the driver files corresponding to one or more image acquisition components among the multiple image acquisition components.

[0075] When the driver record file is successfully called, a first driver file loading index table is established based on the driver file name recorded in the driver record file. The first driver file loading index table records the driver file name and the file content of the driver file corresponding to the driver file name. It can be understood that the number of driver file names in the first driver file loading index table is less than or equal to the number of image acquisition component driver files included in the terminal driver file data packet. The driver information may include the EEPROM information of the image acquisition component, the image acquisition component sensor ID, etc. The driver files in the first driver file loading index table are traversed, and for each driver file, the multiple driver information corresponding to the driver file is matched with the corresponding information of the multiple image acquisition components in turn. When the multiple driver information corresponding to the driver files in the first driver file loading index table is successfully matched with the corresponding information of each image acquisition component in the multiple image acquisition components, it is determined that the recognition of each image acquisition component in the multiple image acquisition components is successful, that is, the terminal has successfully loaded multiple image acquisition components.

[0076] According to an embodiment of the present disclosure, when identifying multiple image acquisition components based on the first driver file loading index table, it is only necessary to traverse each driver file in the first driver file loading index table. The number of driver files is less than the number of driver files in the driver file data packet in the terminal, saving the time spent on driver file traversal during loading, thereby reducing the loading time of the image acquisition component driver.

[0077] Figure 6 FIG. 1 is a flow chart showing a method for identifying multiple image acquisition components based on a first drive file loading index table according to an exemplary embodiment of the present disclosure. Figure 6 As shown, the method for identifying multiple image acquisition components by loading an index table based on a first drive file includes the following steps.

[0078] In step S601, in response to the presence of driving information that fails to match the information corresponding to the second image acquisition component among the multiple driving information corresponding to the second driving file in the first driving file loading index table, a third driving file having the same type identifier as the second driving file is determined in the driving file data packet.

[0079] In step S602, multiple driving information corresponding to the third driving file is traversed, and the multiple driving information is matched with the corresponding information of the second image acquisition component.

[0080] In step S603, in response to the multiple driving information corresponding to the third driving file and the corresponding information of the second image acquisition component all being successfully matched, it is determined that the second image acquisition component is successfully recognized.

[0081] In an embodiment of the present disclosure, the terminal loads driver files corresponding to multiple image acquisition components and calls a driver record file, in which the driver file names of multiple image acquisition components are recorded. The image acquisition components and the driver files have a one-to-one correspondence, but when the image acquisition components of the terminal are changed, for example, one or more image acquisition components are repaired and replaced, the driver files in the driver record file may not be able to achieve normal loading of the replaced image acquisition components. In this case, among the multiple driver information corresponding to the second driver file in the first driver file loading index table, there is driver information that fails to match the corresponding information of the second image acquisition component, and a third driver file with the same type identifier as the second driver file is determined in the driver file data packet. The third driver file can be one or more. The second driver file type identifier, for example, can be the slot ID of the image acquisition component, which is used to identify the setting position of the image acquisition component in the terminal, that is, the main camera, front camera, etc. of the terminal. The setting position of the image acquisition component corresponding to the driver file can be located by the slot ID, and multiple driver information corresponding to the third driver file is traversed, and the multiple driver information is matched with the corresponding information of the second image acquisition component. When all matches are successful, it is determined that the second image acquisition component is successfully identified, and the third driver file is the driver file that matches the second image acquisition component. The third driver file can be used to load the second image acquisition component.

[0082] According to an embodiment of the present disclosure, the second driver file in the driver record file cannot realize the normal loading of the second image acquisition component. A third driver file with the same type identifier as the second driver file is determined in the driver file data packet. The third driver file successfully matches all the corresponding information of the second image acquisition component, and it is determined that the second image acquisition component is successfully identified. The successfully matched third driver file can normally identify the second image acquisition component.

[0083] Figure 7 FIG. 1 is a flow chart of a method for identifying an image acquisition component according to an exemplary embodiment of the present disclosure. Figure 7 As shown, the image acquisition component identification method includes the following steps.

[0084] In step S701, in response to the presence of driving information that fails to match the information corresponding to the second image acquisition component among the multiple driving information corresponding to the second driving file in the first driving file loading index table, a third driving file having the same type identifier as the second driving file is determined in the driving file data packet.

[0085] In step S702, multiple driving information corresponding to the third driving file is traversed, and the multiple driving information is matched with the corresponding information of the second image acquisition component.

[0086] In step S703, in response to the multiple driving information corresponding to the third driving file and the corresponding information of the second image acquisition component all being successfully matched, it is determined that the second image acquisition component is successfully recognized.

[0087] In step S704 , the file name of the second driving file is deleted from the driving record file, and the file name of the third driving file is recorded in the driving record file.

[0088] In an embodiment of the present disclosure, a terminal loads driver files corresponding to multiple image acquisition components and calls a driver record file, which records the driver file names of the driver files corresponding to the multiple image acquisition components. If, among the multiple driver information corresponding to the second driver file in the first driver file loading index table, there is driver information that fails to match the information corresponding to the second image acquisition component, a third driver file with the same type identifier as the second driver file is determined in the driver file data packet. The third driver file can be one or more. The terminal then traverses the multiple driver information corresponding to the third driver file and matches the multiple driver information with the information corresponding to the second image acquisition component. If all of the driver information matches successfully, it is determined that the second image acquisition component has been successfully identified. The third driver file is the driver file that matches the second image acquisition component, and the third driver file can be used to load the second image acquisition component. To ensure that the driver record file loads normally the next time multiple image acquisition components are loaded, the file name of the second driver file is deleted from the driver record file, and the file name of the third driver file is recorded in the driver record file. The next time the driver for the second image acquisition component is loaded, the third driver file is used to load and identify the second image acquisition component normally.

[0089] According to an embodiment of the present disclosure, if the second driver file in the driver record file fails to properly load the second image acquisition component, a third driver file with the same type identifier as the second driver file is identified in the driver file data packet. If the third driver file successfully matches all corresponding information of the second image acquisition component, the second image acquisition component is successfully identified. The successfully matched third driver file can properly identify the second image acquisition component. The third driver file is then recorded in the driver record file to enable subsequent proper identification of the second image acquisition component.

[0090] Figure 8 FIG. 1 is a flow chart of a method for identifying an image acquisition component according to an exemplary embodiment of the present disclosure. Figure 8 As shown, the image acquisition component identification method includes the following steps.

[0091] In step S801, a drive record file is created.

[0092] In an embodiment of the present disclosure, the terminal loads driver files corresponding to multiple image acquisition components. When the driver record file is not called, for example, when the terminal is used for the first time to load driver files corresponding to multiple image acquisition components, the driver record file does not exist in the terminal, then a driver record file is created.

[0093] In step S802 , a second driver file loading index table is created based on the driver files included in the driver file data package.

[0094] In step S803, the EEPROM information of the camera module is read through the I2C configuration configured in the driver file.

[0095] In step S804, it is determined whether the information of the driver file is consistent with the read EEPROM information.

[0096] When the information of the driver file is consistent with the read EEPROM information, step S805 is executed.

[0097] When the information of the driver file is inconsistent with the read EEPROM information, step S803 is executed to read the next driver file in the second driver file loading index table, and read the EEPROM information of the camera module through the I2C configuration configured in the driver file.

[0098] In step S805 , the sensor ID is read through the I2C configuration of the sensor in the driver file.

[0099] In step S806 , it is determined whether the information in the driver file matches the read sensor ID.

[0100] When the information of the driving file matches the read sensor ID, step S807 is executed.

[0101] When the information of the driver file does not match the read sensor ID, step S803 is executed to read the next driver file in the second driver file loading index table.

[0102] In step S807, the driver file name is recorded in the driver file, and the driver files in the second driver file loading index table are traversed.

[0103] Figure 9 FIG. 1 is a flow chart of a method for identifying an image acquisition component according to an exemplary embodiment of the present disclosure. Figure 9 As shown, the image acquisition component identification method includes the following steps.

[0104] In step S901, the drive record file is called.

[0105] In an embodiment of the present disclosure, the terminal loads driver files corresponding to multiple image acquisition components. When the driver record file is called, for example, the terminal is not used for the first time, and multiple driver files corresponding to image acquisition components have been loaded, and a driver record file exists at the terminal, the driver record file is called.

[0106] In step S902, a first driver file loading index table is established based on the driver file name recorded in the driver record file.

[0107] In step S903, each driver file in the first driver file loading index table is traversed.

[0108] In step S904, the EEPROM information of the camera module is read through the I2C configuration configured in the driver file.

[0109] In step S905 , it is determined whether the information of the driver file is consistent with the read EEPROM information.

[0110] When the information of the driving file is consistent with the read EEPROM information, step S906 is executed.

[0111] When the information of the driving file is inconsistent with the read EEPROM information, step S909 is executed.

[0112] In step S906 , the sensor ID is read through the I2C configuration of the sensor in the driver file.

[0113] In step S907 , it is determined whether the information in the driver file matches the read sensor ID.

[0114] When the information of the driving file matches the read sensor ID, step S908 is executed.

[0115] In step S908, the image acquisition component is identified successfully.

[0116] When the information in the driving file does not match the read sensor ID, step S909 is executed.

[0117] In step S909 , a third driver file having the same type identifier as the second driver file is determined in the driver file data packet.

[0118] In step S910, multiple driving information corresponding to the third driving file is traversed, and the multiple driving information is matched with the corresponding information of the second image acquisition component.

[0119] In step S911, in response to the multiple driving information corresponding to the third driving file and the corresponding information of the second image acquisition component all being successfully matched, it is determined that the second image acquisition component is successfully recognized.

[0120] In step S912, the file name of the second driving file is deleted from the driving record file, and the file name of the third driving file is recorded in the driving record file.

[0121] According to an embodiment of the present disclosure, when loading driver files corresponding to multiple image acquisition components in a terminal, a first driver file loading index table is established based on a driver record file, and multiple image acquisition components are identified based on the index table, thereby optimizing the loading time of the image acquisition component driver, improving terminal performance, and thus enhancing user experience.

[0122] Based on the same concept, an embodiment of the present disclosure also provides an image acquisition component recognition device.

[0123] It is understandable that the image acquisition component recognition device provided by the embodiment of the present disclosure includes hardware structures and / or software modules corresponding to the execution of each function in order to realize the above functions. In combination with the units and algorithm steps of each example disclosed in the embodiment of the present disclosure, the embodiment of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiment of the present disclosure.

[0124] Figure 10 This is a block diagram of an image acquisition component recognition device according to an exemplary embodiment of the present disclosure. The image acquisition component recognition device is applied to a terminal, which includes multiple image acquisition components. Figure 10 The image acquisition component recognition device 100 includes a calling module 101, a building module 102 and a recognition module 103.

[0125] The calling module 101 is used to load the corresponding driver files of multiple image acquisition components in response to a trigger, and call the driver record file, which records the driver file name of the driver file corresponding to one or more image acquisition components among the multiple image acquisition components.

[0126] The establishing module 102 is configured to establish a first driver file loading index table based on the driver file name recorded in the driver record file when the driver record file is successfully called.

[0127] The identification module 103 is configured to load an index table based on the first driver file and identify multiple image acquisition components.

[0128] In one embodiment, the terminal includes a driver file data package, and the driver file data package includes driver files whose number is greater than the number of image acquisition components included in the terminal. Figure 11 This is a block diagram of an image acquisition component recognition device according to an exemplary embodiment of the present disclosure, referring to Figure 11 The image acquisition component recognition device 100 also includes a creation module 104.

[0129] The creation module 104 is used to create a drive record file when the drive record file is not called, and to create a second drive file loading index table based on the drive file included in the drive file data packet, and to record in the drive record file the drive file names of the drive files corresponding to the multiple image acquisition components that are successfully identified based on the second drive file loading index table.

[0130] The identification module 103 is further configured to load the index table based on the second driver file and identify multiple image acquisition components.

[0131] In one embodiment, the creation module 104 records the driver file names of the driver files corresponding to the multiple image acquisition components that are successfully identified based on the second driver file loading index table in the driver record file in the following manner:

[0132] Traversing each driver file in the second driver file loading index table, and for each driver file, sequentially matching multiple driver information corresponding to the driver file with corresponding information of multiple image acquisition components;

[0133] In response to the successful matching of multiple driving information corresponding to the first driving file in the second driving file loading index table with the corresponding information of the first image acquisition component in the multiple image acquisition components, it is determined that the first driving file is the driving file successfully identified by the first image acquisition component, and the file name of the first driving file is recorded in the driving record file.

[0134] In one embodiment, the identification module 103 identifies multiple image acquisition components based on the first driver file loading index table in the following manner: traverse each driver file in the first driver file loading index table, and for each driver file, match multiple driver information corresponding to the driver file with corresponding information of multiple image acquisition components in turn; in response to the multiple driver information corresponding to each driver file in the first driver file loading index table successfully matching the corresponding information of each image acquisition component in the multiple image acquisition components, determine that each image acquisition component in the multiple image acquisition components is successfully identified.

[0135] In one embodiment, the terminal includes a driver file data packet, and the identification module 103 identifies multiple image acquisition components based on the first driver file loading index table in the following manner: in response to the presence of driver information that fails to match the information corresponding to the second image acquisition component in the multiple driver information corresponding to the second driver file in the first driver file loading index table, a third driver file with the same type identifier as the second driver file is determined in the driver file data packet; the multiple driver information corresponding to the third driver file is traversed, and the multiple driver information is matched with the information corresponding to the second image acquisition component; in response to the multiple driver information corresponding to the third driver file being successfully matched with the information corresponding to the second image acquisition component, it is determined that the second image acquisition component has been successfully identified.

[0136] Figure 12 This is a block diagram of an image acquisition component recognition device according to an exemplary embodiment of the present disclosure, referring to Figure 12 The image acquisition component recognition device 100 also includes an updating module 105.

[0137] The updating module 105 is used to delete the file name of the second driving file in the driving record file and record the file name of the third driving file in the driving record file in response to all the driving information corresponding to the third driving file successfully matching the corresponding information of the second image acquisition component.

[0138] Regarding the apparatus in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0139] Figure 13 FIG1 is a block diagram of an apparatus 800 for identifying an image acquisition component according to an exemplary embodiment. For example, the apparatus 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0140] Reference Figure 13, the apparatus 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .

[0141] The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operation, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the above-described method. In addition, the processing component 802 may include one or more modules to facilitate interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

[0142] The memory 804 is configured to store various types of data to support the operations of the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device, or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk.

[0143] The power component 806 provides power to the various components of the device 800. The power component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the device 800.

[0144] The multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor can not only sense the boundaries of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each front camera and the rear camera can be a fixed optical lens system or have focal length and optical zoom capabilities.

[0145] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), which is configured to receive external audio signals when the device 800 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal can be further stored in the memory 804 or transmitted via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0146] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as a keyboard, click wheel, buttons, etc. These buttons may include but are not limited to: a home button, volume buttons, a start button, and a lock button.

[0147] The sensor assembly 814 includes one or more sensors for providing various aspects of the status assessment of the device 800. For example, the sensor assembly 814 can detect the open / closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800. The sensor assembly 814 can also detect changes in the position of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration / deceleration of the device 800, and temperature changes of the device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0148] The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0149] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the above-described method.

[0150] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by the processor 820 of the apparatus 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0151] It is understood that in this disclosure, "plurality" refers to two or more than two, and other quantifiers are similar. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects before and after are in an "or" relationship. The singular forms "a", "an", and "the" are also intended to include plural forms, unless the context clearly indicates otherwise.

[0152] It will be further understood that the terms "first," "second," and the like are used to describe various types of information, but such information should not be limited to these terms. These terms are used solely to distinguish information of the same type from one another and do not indicate a particular order or level of importance. In fact, the terms "first," "second," and the like are fully interchangeable. For example, first information could be referred to as second information, and similarly, second information could be referred to as first information without departing from the scope of this disclosure.

[0153] It is further understood that, unless otherwise specified, “connection” includes a direct connection where there are no other components between the two elements, and also includes an indirect connection where there are other elements between the two elements.

[0154] It is further understood that although operations are described in a particular order in the drawings in the embodiments of the present disclosure, this should not be construed as requiring that the operations be performed in the particular order shown or in a serial order, or that all of the operations shown be performed to obtain the desired results. In certain circumstances, multitasking and parallel processing may be advantageous.

[0155] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the disclosure herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0156] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for identifying an image acquisition component, characterized in that: Applied to a terminal, the terminal including a plurality of image acquisition components, the terminal including a driver file data packet, the driver file data packet including a number of driver files greater than the number of the image acquisition components, the method comprising: In response to a trigger, loading of driver files corresponding to the plurality of image acquisition components is performed, and a driver record file is called, wherein the driver record file records the driver file names of the driver files corresponding to one or more image acquisition components among the plurality of image acquisition components; If the driver record file is successfully called, a first driver file loading index table is established based on the driver file name recorded in the driver record file, and the plurality of image acquisition components are identified based on the first driver file loading index table; If the driver record file is not called, creating a driver record file, and creating a second driver file loading index table based on the driver file included in the driver file data package; Identify the multiple image acquisition components based on the second drive file loading index table, and record the driver file names of the driver files corresponding to the multiple image acquisition components successfully identified based on the second drive file loading index table in the created drive record file; The driver file names of the driver files corresponding to the multiple image acquisition components successfully identified based on the second driver file loading index table are recorded in the created driver record file, including: Traversing each driver file in the second driver file loading index table, and for each driver file, sequentially matching multiple driver information corresponding to the driver file with corresponding information of the multiple image acquisition components; In response to the second driver file loading index table successfully matching all the multiple driver information corresponding to the first driver file with the corresponding information of the first image acquisition component among the multiple image acquisition components, it is determined that the first driver file is the driver file successfully identified by the first image acquisition component, and the file name of the first driver file is recorded in the created driver record file.

2. The image acquisition component recognition method according to claim 1, characterized in that: Identifying the plurality of image acquisition components based on the first driver file loading index table includes: Traversing each driver file in the first driver file loading index table, and for each driver file, sequentially matching multiple driver information corresponding to the driver file with corresponding information of the multiple image acquisition components; In response to a successful match between a plurality of driving information corresponding to each driving file in the first driving file loading index table and corresponding information of each image acquisition component in the plurality of image acquisition components, it is determined that each image acquisition component in the plurality of image acquisition components is successfully identified.

3. The image acquisition component recognition method according to claim 1, characterized in that: The terminal includes a driver file data packet, and the identifying the plurality of image acquisition components based on the first driver file loading index table includes: In response to the presence of driving information that fails to match the information corresponding to the second image acquisition component among the plurality of driving information corresponding to the second driving file in the first driving file loading index table, determining a third driving file having the same type identifier as the second driving file in the driving file data packet; Traversing multiple driving information corresponding to the third driving file, and matching the multiple driving information with the corresponding information of the second image acquisition component; In response to all successful matching between the plurality of driving information corresponding to the third driving file and the corresponding information of the second image acquisition component, it is determined that the second image acquisition component has been successfully recognized.

4. The image acquisition component recognition method according to claim 3, characterized in that: The method further comprises: In response to the multiple driving information corresponding to the third driving file successfully matching the corresponding information of the second image acquisition component, the file name of the second driving file in the driving record file is deleted, and the file name of the third driving file is recorded in the driving record file.

5. An image acquisition component recognition device, characterized in that: Applied to a terminal, the terminal including a plurality of image acquisition components, the terminal including a driver file data packet, the driver file data packet including a number of driver files greater than the number of the image acquisition components, the device comprising: a calling module, configured to load the driver files corresponding to the plurality of image acquisition components in response to a trigger, and call a driver record file, wherein the driver record file records the driver file names of the driver files corresponding to one or more of the plurality of image acquisition components; An establishing module, configured to establish a first driver file loading index table based on the driver file name recorded in the driver record file when the driver record file is successfully called; an identification module, configured to identify the plurality of image acquisition components based on the first driver file loading index table; a creation module, configured to create a drive record file when the drive record file is not called, and create a second drive file loading index table based on the drive files included in the drive file data packet, and record in the created drive record file the names of the drive files corresponding to the multiple image acquisition components that are successfully identified based on the second drive file loading index table; The identification module is further configured to load an index table based on the second drive file to identify the plurality of image acquisition components; The creation module records the driver file names of the driver files corresponding to the multiple image acquisition components that are successfully identified based on the second driver file loading index table in the created driver record file in the following manner: Traversing each driver file in the second driver file loading index table, and for each driver file, sequentially matching multiple driver information corresponding to the driver file with corresponding information of the multiple image acquisition components; In response to the second driver file loading index table successfully matching all the multiple driver information corresponding to the first driver file with the corresponding information of the first image acquisition component among the multiple image acquisition components, it is determined that the first driver file is the driver file successfully identified by the first image acquisition component, and the file name of the first driver file is recorded in the created driver record file.

6. The image acquisition component recognition device according to claim 5, characterized in that: The identification module identifies the multiple image acquisition components based on the first drive file loading index table in the following manner: Traversing each driver file in the first driver file loading index table, and for each driver file, sequentially matching multiple driver information corresponding to the driver file with corresponding information of the multiple image acquisition components; In response to a successful match between a plurality of driving information corresponding to each driving file in the first driving file loading index table and corresponding information of each image acquisition component in the plurality of image acquisition components, it is determined that each image acquisition component in the plurality of image acquisition components is successfully identified.

7. The image acquisition component recognition device according to claim 5, characterized in that: The terminal includes a driver file data package, and the identification module identifies the multiple image acquisition components based on the first driver file loading index table in the following manner: In response to the presence of driving information that fails to match the information corresponding to the second image acquisition component among the plurality of driving information corresponding to the second driving file in the first driving file loading index table, determining a third driving file having the same type identifier as the second driving file in the driving file data packet; Traversing multiple driving information corresponding to the third driving file, and matching the multiple driving information with the corresponding information of the second image acquisition component; In response to all successful matching between the plurality of driving information corresponding to the third driving file and the corresponding information of the second image acquisition component, it is determined that the second image acquisition component has been successfully recognized.

8. The image acquisition component recognition device according to claim 7, characterized in that: The device further comprises: An update module is used to delete the file name of the second drive file in the drive record file and record the file name of the third drive file in the drive record file in response to all the multiple drive information corresponding to the third drive file successfully matching the corresponding information of the second image acquisition component.

9. An image acquisition component recognition device, characterized in that: include: processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to: execute the image acquisition component identification method described in any one of claims 1 to 4.

10. A non-transitory computer-readable storage medium, characterized in that When the instructions in the storage medium are executed by the processor of the mobile terminal, the mobile terminal is enabled to execute the image acquisition component identification method according to any one of claims 1 to 4.

Images