Method and system for sharing whole vehicle image acquisition device data

Abstract

The application discloses a method and system for sharing data of a whole vehicle image acquisition device. The method comprises the following steps: receiving a data request for a target image acquisition device sent by a target application module; judging whether the target application module has a request right according to the data request, the attribute of the target image acquisition device and the name of the target application module; judging whether the target image acquisition device is in a working state in the case that the target application module has the request right; obtaining the domain where the target image acquisition device is located in the case that the target image acquisition device is not in the working state; and sending target data of the target image acquisition device to the target application module according to the domain where the target image acquisition device is located. The application realizes sharing of the data of the whole vehicle image acquisition device by judging the request right and the domain of the target application, and realizes sharing of the data of the whole vehicle in the case of multiple channels.

Description

Technical Field

[0001] This invention relates to the field of vehicle camera technology, and specifically to a method and system for sharing data from a vehicle image acquisition device. Background Technology

[0002] As the automotive market matures, in-vehicle infotainment systems are becoming increasingly intelligent, with various manufacturers launching their own smart cockpit systems. As market coverage expands, user demands for intelligence are rising, particularly regarding cameras. Early systems have evolved from simple reversing and right blind spot cameras to surround view, DMS, IMS, panoramic, front view, and rear view camera configurations. The number of in-vehicle cameras is increasing, leading to higher vehicle costs. Currently, cameras are categorized into several functional areas: autonomous driving, driver assistance, and entertainment. The hardware systems connecting each camera differ according to the vehicle architecture, making unified management difficult. With diversified needs, the central control unit will increasingly require data collection from various cameras. If cameras cannot be managed uniformly, data transmission becomes complex, hindering the overall architecture. The inability to reuse camera data can cause functional conflicts, failing to meet user experience requirements, and adding more cameras results in wasted costs. While existing technologies can achieve data sharing for native camera channels, unified management and data sharing for audio encoder channels and other domain cameras are not feasible. Therefore, traditional solutions cannot achieve unified management and data sharing for all vehicle cameras. Summary of the Invention

[0003] The purpose of this application is to provide a method and system for sharing vehicle image acquisition equipment data, so as to solve the problem that the prior art cannot share vehicle data across multiple channels.

[0004] To achieve the above objectives, the first aspect of this application provides a method for sharing data from a vehicle image acquisition device, applied to an image acquisition device management service module. The image acquisition device management service module communicates with multiple application modules and multiple image acquisition devices. The method includes:

[0005] Receive data requests from the target application module for the target image acquisition device;

[0006] Based on the data request, the attributes of the target image acquisition device, and the name of the target application module, determine whether the target application module has the request permission;

[0007] If the target application module has the requested permissions, determine whether the target image acquisition device is in a working state;

[0008] When the target image acquisition device is not in operation, obtain the domain where the target image acquisition device is located;

[0009] Based on the domain of the target image acquisition device, the target data of the target image acquisition device is sent to the target application module.

[0010] In this embodiment of the application, the method further includes:

[0011] If the target application module does not have the permission to request, a request failure command is sent to the target application module.

[0012] In this embodiment of the application, the method further includes:

[0013] When the target image acquisition device is in operation, share the target image acquisition device data with the target application module.

[0014] In this embodiment, the image acquisition device management service module communicates with multiple application modules through the image acquisition module software development kit.

[0015] In this embodiment of the application, the domain includes the driving domain and other domains besides the driving domain. When the domain is another domain, sending the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device includes:

[0016] Data transmission between the target image acquisition device and the target application is achieved through low-voltage differential signals; or

[0017] Data transmission between the target image acquisition device and the target application is achieved via a ring network Ethernet.

[0018] In this embodiment, the driving domain includes a system native image service module and a system native video service module. When the domain is the driving domain, sending the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device includes:

[0019] By accessing the system's native image acquisition device management service module, the target image acquisition device data is sent to the target application module;

[0020] By connecting to the audio encoder management module, data from the target image acquisition device is sent to the target application module.

[0021] In this embodiment of the application, the image acquisition device management service module also communicates with the configuration command module to determine whether the target application has requested permissions, including:

[0022] Receive the whitelist sent by the configuration command module;

[0023] Determine whether the target application has the permission to request the permission based on the whitelist.

[0024] A second aspect of this application provides an image acquisition device management service module, including:

[0025] The memory is configured to store instructions; and

[0026] The processor is configured to retrieve instructions from memory and, when executing the instructions, to implement the method described above for sharing vehicle image acquisition device data.

[0027] A third aspect of this application provides a system for sharing data from a vehicle image acquisition device, the system comprising:

[0028] Based on the aforementioned image acquisition device management service module;

[0029] Multiple application modules communicate with the image acquisition device management service module and are configured to send image acquisition device data requests to the image acquisition device management service module.

[0030] Multiple image acquisition modules communicate with the image acquisition device management service module and are configured to provide target data;

[0031] The configuration command module communicates with the image acquisition device management service module and is configured to send a whitelist to the image acquisition device management service module.

[0032] A fourth aspect of this application provides a machine-readable storage medium storing instructions for causing a machine to perform the method described above for sharing vehicle image acquisition device data.

[0033] Through the above technical solution, the image acquisition device management service module receives a data request for the target image acquisition device sent by the target application module; based on the data request, the attributes of the target image acquisition device, and the name of the target application module, it determines whether the target application module has the request permission; if the target application module has the request permission, it determines whether the target image acquisition device is in a working state; if the target image acquisition device is not in a working state, it obtains the domain of the target image acquisition device; finally, it sends the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device. This application solution achieves the sharing of vehicle image acquisition device data by judging the request permission and domain of the target application, realizing vehicle data sharing in a multi-channel environment. Attached Figure Description

[0034] The accompanying drawings are provided to further illustrate the embodiments of this application and form part of the specification. They are used together with the following detailed description to explain the embodiments of this application, but do not constitute a limitation on the embodiments of this application. In the drawings:

[0035] Figure 1This diagram schematically illustrates an application environment diagram of a method for sharing whole vehicle image acquisition device data according to an embodiment of this application;

[0036] Figure 2 A flowchart illustrating a method for sharing whole vehicle image acquisition device data according to an embodiment of this application is shown schematically;

[0037] Figure 3 A flowchart illustrating a method for synchronous whole-vehicle image acquisition device according to a specific embodiment of this application is shown schematically.

[0038] Figure 4 A flowchart illustrating an access method for an image acquisition device according to a specific embodiment of this application is shown schematically.

[0039] Figure 5 This schematic diagram illustrates a structural block diagram of an image acquisition device management service module according to an embodiment of this application;

[0040] Figure 6 The diagram illustrates the structure of a system for sharing whole-vehicle image acquisition device data according to an embodiment of this application.

[0041] Explanation of reference numerals in the attached figures

[0042] 601 Image Acquisition Device Management Service Module; 602 Multiple Application Modules

[0043] 603 Multiple image acquisition modules; 604 Configuration command module Detailed Implementation

[0044] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are only for illustration and explanation of the embodiments of this application and are not intended to limit the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0045] It should be noted that if the embodiments of this application involve directional indicators (such as up, down, left, right, front, back, etc.), the directional indicators are only used to explain the relative positional relationship and movement of the components in a certain specific posture (as shown in the figure). If the specific posture changes, the directional indicators will also change accordingly.

[0046] Furthermore, if the embodiments of this application involve descriptions such as "first" or "second," these descriptions are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first" or "second" may explicitly or implicitly include at least one of those features. Additionally, the technical solutions of various embodiments can be combined with each other, but this must be based on the ability of those skilled in the art to implement them. If the combination of technical solutions is contradictory or impossible to implement, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection claimed in this application.

[0047] Figure 1 This diagram schematically illustrates an application environment diagram of a method for sharing vehicle image acquisition device data according to an embodiment of this application. For example... Figure 1 As shown in the illustration, this application provides an application environment for a method of sharing data from a vehicle image acquisition device. This application environment includes a driving domain or other domains and a cockpit central control platform. The driving domain operating system provides data from hardware-accessible cameras, which is transmitted to the cockpit central control platform system via Ethernet. The cockpit central control platform includes CameraHAL & CameraService, EvsHAL & EvsManager, CameraManagerService, CameraServiceSDK, and Config. Specifically, CameraHAL & CameraService refer to the system's native Camera2 service (generally used for ordinary entertainment cameras); EvsHAL & EvsManager refer to the system's native image module service (generally used for panoramic & DVR and other image-type cameras); CameraManagerService refers to a custom vehicle camera management service, which simultaneously accesses and manages data from other domains and all cameras within the system; CameraServiceSDK is a software development kit that provides unified camera on / off and data sharing capabilities; Config refers to permission control configuration and other configuration modules.

[0048] Figure 2 A flowchart illustrating a method for sharing vehicle image acquisition device data according to an embodiment of this application is shown schematically. Figure 2 As shown in the figure, this application provides a method for sharing data from a vehicle image acquisition device. This method is applied to an image acquisition device management service module, which communicates with multiple application modules and multiple image acquisition devices. The method includes the following steps:

[0049] Step 201: Receive the data request for the target image acquisition device sent by the target application module;

[0050] Step 202: Based on the data request, the attributes of the target image acquisition device, and the name of the target application module, determine whether the target application module has the request permission;

[0051] Step 203: If the target application module has the requested permission, determine whether the target image acquisition device is in a working state;

[0052] Step 204: If the target image acquisition device is not in operation, obtain the domain where the target image acquisition device is located;

[0053] Step 205: Send the target data of the target image acquisition device to the target application module according to the domain where the target image acquisition device is located.

[0054] In this embodiment, the target application module refers to the application module that requires image data. Multiple application modules may include multiple target application modules. The target image acquisition device refers to the image acquisition device to which data is to be acquired, and the image acquisition device may include, but is not limited to, a camera. The working state refers to whether the image acquisition device is acquiring images. The location domain refers to the area where the image acquisition device is located, and the location domain may include the driving domain and other domains besides the driving domain.

[0055] When sharing vehicle image acquisition equipment data, the image acquisition equipment management service module communicates with multiple application modules. The target application module first sends a data request to the target image acquisition equipment. The target application module obtains the data by sending the data request. The image acquisition equipment management service module first receives the data request from the target application module. Then, based on the received data request, the attributes of the target image acquisition equipment, and the name of the target application module, it determines whether the target application module has the necessary permissions. If the target application module has the necessary permissions, it means it can obtain the target data. The image acquisition equipment management service module then obtains the domain of the target image acquisition equipment and, depending on the domain, selects different data transmission methods to send the target data to the target application module. Through unified management of the vehicle image acquisition equipment data, the sharing of vehicle image acquisition equipment data among multiple application modules can be achieved.

[0056] Through the above technical solution, the image acquisition device management service module receives a data request for the target image acquisition device sent by the target application module; based on the data request, the attributes of the target image acquisition device, and the name of the target application module, it determines whether the target application module has the request permission; if the target application module has the request permission, it determines whether the target image acquisition device is in a working state; if the target image acquisition device is not in a working state, it obtains the domain of the target image acquisition device; finally, it sends the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device. This application solution achieves the sharing of vehicle image acquisition device data by judging the request permission and domain of the target application, realizing vehicle data sharing in a multi-channel environment.

[0057] In this embodiment of the application, the method may further include:

[0058] If the target application module does not have the permission to request, a request failure command is sent to the target application module.

[0059] Specifically, if the target application module lacks the requested permission, indicating that it cannot obtain the target data, the image acquisition device management service module sends a request failure command to the target application module and terminates the application process. By determining whether the target application module has the requested permission, the data sharing process of the vehicle image acquisition device can be controlled in the initial steps, improving the accuracy of data sharing.

[0060] In this embodiment of the application, the method may further include:

[0061] When the target image acquisition device is in operation, share the target image acquisition device data with the target application module.

[0062] Specifically, if the target image acquisition device is active, it means that another process has already requested to open the target image acquisition device, and the target image acquisition device is currently working. The image acquisition device is also acquiring data. The image acquisition device management service module can directly share a copy of the image acquisition device data with the target application module. By directly sharing the image acquisition device data to the target application module while the target image acquisition device is active, processes can be streamlined and sharing efficiency improved while sharing the entire vehicle's image acquisition device data.

[0063] In this embodiment, the image acquisition device management service module communicates with multiple application modules through the image acquisition module software development kit.

[0064] Specifically, the CameraService Software Development Kit (CameraService SDK) is a collection of many functional functions—a toolkit. The image acquisition device management service module communicates with multiple application modules through the CameraService SDK. Multiple application modules access the CameraService SDK and send data requests to the ImageAcquisition Device Management Service module through corresponding interfaces. Each data request can be marked with the model and code of the target image acquisition device to obtain data from that device. Using the CameraService SDK for communication between multiple application modules and the ImageAcquisition Device Management Service module improves the stability of data transmission.

[0065] In this embodiment of the application, the domain includes the driving domain and other domains besides the driving domain. When the domain is another domain, sending the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device includes:

[0066] Data transmission between the target image acquisition device and the target application is achieved through low-voltage differential signals; or

[0067] Data transmission between the target image acquisition device and the target application is carried out via a ring network Ethernet.

[0068] Specifically, Low-Voltage Differential Signaling (LVDS) is a differential signaling technology characterized by low power consumption, low bit error rate, low crosstalk, and low radiation. The core of LVDS technology is the use of extremely low voltage swing for high-speed differential data transmission, enabling point-to-point or point-to-multipoint connections. It facilitates cross-domain image acquisition device data transmission when the domain is different from other domains. Image acquisition device data from other domains can be transmitted to the image acquisition device management service module via LVDS or ring network Ethernet in the hardware solution. For the LVDS transmission scheme, the image acquisition device management service module can obtain image acquisition device data by accessing the native Android image acquisition device service module to obtain camera data and the audio encoder management module, or by accessing a customized image acquisition device software development kit (SDK) for the vehicle's hardware platform through platform-specific adaptation. By selecting different data transmission methods based on the domain, the stability of data transmission can be improved.

[0069] In this embodiment, the driving domain includes a system native image service module and a system native video service module. When the domain is the driving domain, sending the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device includes:

[0070] By accessing the system's native image acquisition device service module, data from the target image acquisition device is sent to the target application module;

[0071] By connecting to the audio encoder management module, data from the target image acquisition device is sent to the target application module.

[0072] Specifically, the driving domain includes the system native image service module and the system native video service module. The system native image service module (CameraHAL & CameraService) is generally used for ordinary entertainment cameras. The system native video service module (EvsHAL & EvsManager) is generally used for panoramic and DVR-type video cameras. When the domain is the driving domain, the data transmission method differs depending on the module. When transmitting data to the system native image service module, the target image acquisition device data is sent to the target application module by connecting to the system native image acquisition device service module (Camera Service). When transmitting data to the system native video service module, the target image acquisition device data is sent to the target application module by connecting to the audio encoder management module (Evs Manager). By selecting different data transmission methods for different modules, the stability of data transmission can be improved.

[0073] In this embodiment of the application, the image acquisition device management service module also communicates with the configuration command module to determine whether the target application has requested permissions, including:

[0074] Receive the whitelist sent by the configuration command module;

[0075] Determine whether the target application has the permission to request the permission based on the whitelist.

[0076] Specifically, the configuration command module (Config) can be used for access control configuration and other configuration modules. The configuration command module can send a whitelist to the image acquisition device management service module. The whitelist sets the allowed users, while users not on the whitelist are denied access. The whitelist contains a list of target applications with the necessary permissions. The image acquisition device management service module can determine whether a target application has the required permissions based on the whitelist. By determining whether a target application module has the necessary permissions, the data sharing process of the vehicle's image acquisition devices can be controlled in the initial steps, improving the accuracy of data sharing.

[0077] Through the above technical solution, the image acquisition device management service module receives a data request for the target image acquisition device sent by the target application module; based on the data request, the attributes of the target image acquisition device, and the name of the target application module, it determines whether the target application module has the request permission; if the target application module has the request permission, it determines whether the target image acquisition device is in a working state; if the target image acquisition device is not in a working state, it obtains the domain of the target image acquisition device; finally, it sends the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device. This application solution achieves the sharing of vehicle image acquisition device data by judging the request permission and domain of the target application, realizing vehicle data sharing in a multi-channel environment.

[0078] Figure 3 The flowchart illustrating a method for synchronous whole-vehicle image acquisition equipment according to a specific embodiment of this application is shown schematically. Figure 3 As shown in the figure, a specific embodiment of this application provides a method for synchronously acquiring images of a vehicle, which may include the following steps:

[0079] S31. Start the CameraManagerService service;

[0080] S32. Connect to other domains via Ethernet;

[0081] S33. Determine whether a connection has been established. If yes, proceed to S34; otherwise, return to S32.

[0082] S34, synchronize camera list, proceed to S36;

[0083] S35. Synchronize the list of internal cameras of this system;

[0084] S36. Add to camera management list.

[0085] Specifically, after the CameraManagerService service (i.e., the image acquisition device management service module of this application) starts, the CameraManagerService service module connects to other domains via Ethernet and determines whether the connection is successfully established. If the CameraManagerService service module successfully establishes a connection with other domains, it synchronizes the list of cameras (i.e., the image acquisition devices of this application) and adds the camera list to the camera management list. If the CameraManagerService service module fails to establish a connection with other domains, it continues to establish connections with other domains via Ethernet. By connecting to other domains and synchronizing cameras in other domains through the CameraManagerService service module, synchronous management of the vehicle's image acquisition devices can be achieved.

[0086] Figure 4 A flowchart illustrating an access method for an image acquisition device according to a specific embodiment of this application is shown. Figure 4 As shown in the figure, a specific embodiment of this application provides a method for accessing an image acquisition device, which may include the following steps:

[0087] S41, The APP application requests camera data;

[0088] S42, Camera management service receives request;

[0089] S43. Determine if permission to use the camera is granted. If yes, proceed to S44. If no, return to S41.

[0090] S44. Determine if the camera is turned on. If yes, proceed to S46; otherwise, proceed to S45.

[0091] S45. Determine the camera's location domain by its ID and notify the camera to be turned on;

[0092] S46. Synchronize camera data with the requesting process and return S41.

[0093] Specifically, firstly, the APP application (i.e., the multiple application modules of this application) sends camera data (i.e., the image acquisition device data of this application) to the camera management service module (i.e., the image acquisition device management service module of this application). Upon receiving the request, the camera management service module determines whether the APP application has permission to use the camera. If the APP application has permission, it determines whether the camera is currently open. If the camera is open, it directly synchronizes the camera data to the requesting process, i.e., the APP application. If the camera is not open, it determines the domain of the camera through the camera's ID and notifies the application to open the camera. If the APP application does not have permission to use the camera, it directly sends an error command to the APP application, indicating that the request failed. By determining the APP application's request permissions and domain, access to the vehicle image acquisition device can be achieved in a multi-channel environment, enabling vehicle data sharing.

[0094] Figure 5 This diagram schematically illustrates a structural block diagram of an image acquisition device management service module according to an embodiment of this application. Figure 5 As shown in the figure, this application embodiment provides an image acquisition device management service module, which may include:

[0095] Memory 510 is configured to store instructions; and

[0096] The processor 520 is configured to retrieve instructions from the memory 510 and, when executing the instructions, to implement the method of sharing vehicle image acquisition device data as described above.

[0097] Specifically, in this embodiment of the application, the processor 520 can be configured to:

[0098] Receive data requests from the target application module for the target image acquisition device;

[0099] Based on the data request, the attributes of the target image acquisition device, and the name of the target application module, determine whether the target application module has the request permission;

[0100] If the target application module has the requested permissions, determine whether the target image acquisition device is in a working state;

[0101] When the target image acquisition device is not in operation, obtain the domain where the target image acquisition device is located;

[0102] Based on the domain of the target image acquisition device, the target data of the target image acquisition device is sent to the target application module.

[0103] Furthermore, the processor 520 can also be configured as follows:

[0104] If the target application module does not have the permission to request, a request failure command is sent to the target application module.

[0105] Furthermore, the processor 520 can also be configured as follows:

[0106] When the target image acquisition device is in operation, share the target image acquisition device data with the target application module.

[0107] Furthermore, the processor 520 can also be configured as follows:

[0108] The image acquisition device management service module communicates with multiple application modules through the image acquisition module software development kit.

[0109] Furthermore, the processor 520 can also be configured as follows:

[0110] The domain includes the driving domain and other domains besides the driving domain. When the domain is another domain, sending the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device includes:

[0111] Data transmission between the target image acquisition device and the target application is achieved through low-voltage differential signals; or

[0112] Data transmission between the target image acquisition device and the target application is achieved via a ring network Ethernet.

[0113] Furthermore, the processor 520 can also be configured as follows:

[0114] The driving domain includes the system's native image service module and the system's native video service module. When the domain is the driving domain, sending the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device includes:

[0115] By accessing the system's native image acquisition device service module, data from the target image acquisition device is sent to the target application module;

[0116] By connecting to the audio encoder management module, data from the target image acquisition device is sent to the target application module.

[0117] Furthermore, the processor 520 can also be configured as follows:

[0118] The image acquisition device management service module also communicates with the configuration command module to determine whether the target application has the necessary permissions, including:

[0119] Receive the whitelist sent by the configuration command module;

[0120] Determine whether the target application has the permission to request the permission based on the whitelist.

[0121] Through the above technical solution, the image acquisition device management service module receives a data request for the target image acquisition device sent by the target application module; based on the data request, the attributes of the target image acquisition device, and the name of the target application module, it determines whether the target application module has the request permission; if the target application module has the request permission, it determines whether the target image acquisition device is in a working state; if the target image acquisition device is not in a working state, it obtains the domain of the target image acquisition device; finally, it sends the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device. This application solution achieves the sharing of vehicle image acquisition device data by judging the request permission and domain of the target application, realizing vehicle data sharing in a multi-channel environment.

[0122] Figure 6 This diagram schematically illustrates the structure of a system for sharing whole-vehicle image acquisition device data according to an embodiment of this application. Figure 6 As shown in the figure, this application embodiment provides a system for sharing data from a vehicle image acquisition device. The system includes:

[0123] According to the aforementioned image acquisition device management service module 601;

[0124] Multiple application modules 602 communicate with the image acquisition device management service module 601 and are configured to send image acquisition device data requests to the image acquisition device management service module 601.

[0125] Multiple image acquisition modules 603 communicate with the image acquisition device management service module 601 and are configured to provide target data;

[0126] The configuration command module 604 communicates with the image acquisition device management service module 601 and is configured to send a whitelist to the image acquisition device management service module 601.

[0127] In this embodiment, the system for sharing vehicle image acquisition device data includes an image acquisition device management service module 601, multiple application modules 602, multiple image acquisition modules 603, and a configuration command module 604. The image acquisition device management service module 601 communicates with the multiple application modules 602, the multiple image acquisition modules 603, and the configuration command module 604. The multiple application modules 602 are configured to send image acquisition device data requests to the image acquisition device management service module 601. The multiple image acquisition modules 603 are configured to provide target data. The configuration command module 604 is configured to send a whitelist to the image acquisition device management service module 601. The image acquisition device management service module 601 first receives data requests for target image acquisition devices sent by target application modules, and then determines whether the target application module has permission to request data based on the data request, the attributes of the target image acquisition device, and the name of the target application module. If the target application module has the requested permissions, it determines whether the target image acquisition device is in a working state. If the target image acquisition device is not in a working state, it obtains the domain of the target image acquisition device. Based on the domain of the target image acquisition device, it sends the target data of the target image acquisition device to the target application module. By judging the request permissions of the target application and its domain, it realizes the sharing of whole vehicle image acquisition device data, enabling whole vehicle data sharing in multi-channel scenarios.

[0128] Through the above technical solution, the image acquisition device management service module receives a data request for the target image acquisition device sent by the target application module; based on the data request, the attributes of the target image acquisition device, and the name of the target application module, it determines whether the target application module has the request permission; if the target application module has the request permission, it determines whether the target image acquisition device is in a working state; if the target image acquisition device is not in a working state, it obtains the domain of the target image acquisition device; finally, it sends the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device. This application solution achieves the sharing of vehicle image acquisition device data by judging the request permission and domain of the target application, realizing vehicle data sharing in a multi-channel environment.

[0129] This application also provides a machine-readable storage medium storing instructions for causing a machine to execute the above-described method for sharing vehicle image acquisition device data.

[0130] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0131] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0132] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0133] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0134] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0135] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0136] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0137] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0138] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for sharing data from a vehicle image acquisition device, characterized in that, An image acquisition device management service module is applied to the image acquisition device management service module, which communicates with multiple application modules and multiple image acquisition devices. The method includes: Receive data requests from the target application module for the target image acquisition device; Based on the data request, the attributes of the target image acquisition device, and the name of the target application module, determine whether the target application module has request permission; If the target application module has the requested permission, determine whether the target image acquisition device is in a working state; When the target image acquisition device is not in operation, obtain the domain where the target image acquisition device is located; The target data of the target image acquisition device is sent to the target application module according to the domain where the target image acquisition device is located. Wherein, the domain includes the driving domain and other domains besides the driving domain. When the domain is one of the other domains, sending the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device includes: Data transmission between the target image acquisition device and the target application is performed using low-voltage differential signals; or Data transmission between the target image acquisition device and the target application is performed via a ring network Ethernet. The driving domain includes a system native image service module and a system native video service module. The system native image service module CameraHAL & CameraService is used for general entertainment cameras, and the system native video service module EvsHAL & EvsManager is used for panoramic & DVR video cameras. When the domain is the driving domain, sending the target data of the target image acquisition device to the target application module according to the domain of the target image acquisition device includes: When transmitting data to the system's native image service module, the target image acquisition device data is sent to the target application module by accessing the system's native image acquisition device service module. When transmitting data to the system's native image service module, the target image acquisition device data is sent to the target application module by connecting to the audio encoder management module.

2. The method according to claim 1, characterized in that, The method further includes: If the target application module does not have the permission to request, a request failure command is sent to the target application module.

3. The method according to claim 1, characterized in that, The method further includes: When the target image acquisition device is in operation, the data of the target image acquisition device is shared with the target application module.

4. The method according to claim 1, characterized in that, The image acquisition device management service module communicates with the multiple application modules through the image acquisition module software development kit.

5. The method according to claim 1, characterized in that, The image acquisition device management service module also communicates with the configuration command module, and the determination of whether the target application has requested permission includes: Receive the whitelist sent by the configuration command module; The whitelist is used to determine whether the target application has the permission to request permission.

6. An image acquisition device management service module, characterized in that, include: The memory is configured to store instructions; as well as A processor is configured to retrieve the instructions from the memory and, when executing the instructions, to implement the method of sharing whole-vehicle image acquisition device data according to any one of claims 1 to 5.

7. A system for sharing data from a whole-vehicle image acquisition device, characterized in that, The system includes: Image acquisition device management service module according to claim 6; Multiple application modules communicate with the image acquisition device management service module and are configured to send image acquisition device data requests to the image acquisition device management service module. Multiple image acquisition device modules communicate with the image acquisition device management service module and are configured to provide target data; The configuration command module communicates with the image acquisition device management service module and is configured to send a whitelist to the image acquisition device management service module.

8. A machine-readable storage medium, characterized in that, The machine-readable storage medium stores instructions for causing the machine to perform a method for sharing vehicle image acquisition device data according to any one of claims 1 to 5.

Images