Camera control method and device

Abstract

The present application relates to a camera control method and device. The method includes: receiving and determining the first application corresponding to the call request; obtaining the access permission record of the first application, at least one first camera being part or all of the multiple cameras installed; determining the second camera that the first application can currently call from at least one first camera and determining the second access permission of the second camera based on the current call status, corresponding call strategy and corresponding first access permission of each first camera; granting the second access permission of the second camera to the first application. It can achieve precise management and control of the permission authorization control of multiple cameras installed, control each camera according to the type of camera and the type of application that calls each camera, ensure the normal operation of the subject while realizing the classification and hierarchical control of the camera, and meet the needs of users in complex application scenarios using multiple camera subjects.

Description

Technical Field

[0001] The present application relates to the field of camera control, and in particular to a camera control method and device. Background Art

[0002] With the continuous development and advancement of smart devices such as smart cars and smart robots, the number of cameras in these devices is increasing to meet the diverse needs of users. The functions and uses of different cameras are also becoming increasingly diverse, and the application scenarios of cameras are becoming increasingly complex. For example, smart cars are equipped with multiple cameras to meet the needs of functions such as autonomous driving, reverse image assistance, and driving records. A car's computer can be installed with multiple applications that can use multiple cameras. How to achieve controllable and precise access to multiple cameras by multiple applications is a pressing technical challenge. Summary of the Invention

[0003] In view of this, a camera control method and device are proposed to solve the above technical problems.

[0004] In a first aspect, an embodiment of the present application provides a camera control method, the method comprising:

[0005] receiving a call request for applying to call a camera, and determining a first application corresponding to the call request;

[0006] Obtaining an access permission record for the first application, where the access permission record is used to record at least one first camera that the corresponding application is allowed to call and a first access permission for the corresponding application to access the corresponding first camera, where the at least one first camera is part or all of the plurality of installed cameras;

[0007] Determining, from the at least one first camera, a second camera that the first application can currently call and determining a second access permission for the second camera based on the current call state, the corresponding call policy, and the corresponding first access permission of each first camera;

[0008] Grant the first application a second access permission for the second camera.

[0009] In a possible implementation, the method further includes:

[0010] receiving an access request for applying for camera access rights, and determining a second application corresponding to the access request;

[0011] determining, from a plurality of installed cameras, based on an application type of the second application and a mapping relationship between each of the cameras and the application type, at least one third camera that the second application is allowed to access and a third access permission corresponding to each of the third cameras, where the third access permission includes a control permission and / or a data permission;

[0012] The access permission record of the second application is updated according to the at least one third camera and the third access permission corresponding to each of the third cameras, where the second application includes the first application.

[0013] In one possible implementation, updating the access permission record of the second application according to the at least one third camera and the third access permission corresponding to each of the third cameras includes:

[0014] The third camera and the corresponding third access permission are respectively determined as the first camera and the corresponding first access permission, and are recorded in the access permission record of the second application.

[0015] In one possible implementation, updating the access permission record of the second application according to the at least one third camera and the third access permission corresponding to each of the third cameras includes:

[0016] sending the first information of each of the third cameras to the second application, so that the second application displays a first prompt based on the first information, wherein the first prompt is used to remind the user of the third cameras that the second application is allowed to access, remind the user to select a first camera designated by the user to be accessible by the second application from the third cameras, and / or remind the user to determine the first access permission for each first camera;

[0017] receiving a user-specified permission report sent by the second application, the user-specified permission report being used to indicate first access permissions for a first camera designated by the user in the third camera and the first camera designated by the user, as determined by the second application based on the detected permission adjustment operation;

[0018] The first camera and the corresponding first access permission indicated in the user-specified permission report are recorded in the access permission record of the second application.

[0019] In a possible implementation, the method further includes:

[0020] According to the camera-related parameters of each camera, the camera type of each camera is set and the camera application scenarios corresponding to the exclusive camera and the shared camera are set, where the camera type of each camera includes any one of an exclusive class, a shared class and a general class;

[0021] Establishing a mapping relationship between the application type and the camera according to a matching result between the program application scenario corresponding to the application type and the camera application scenario;

[0022] According to the usage characteristics of different camera types, set corresponding calling strategies for each camera type.

[0023] In one possible implementation, establishing a mapping relationship between an application type and a camera based on a matching result between a program application scenario corresponding to the application type and the camera application scenario includes:

[0024] If the program application scenario corresponding to the application type matches the camera application scenario corresponding to the shared camera, a mapping relationship between the shared camera and the application is established; and / or

[0025] If the program application scenario corresponding to the application type matches the camera application scenario corresponding to the dedicated camera, a mapping relationship between the dedicated camera and the application is established; and / or

[0026] If the program application scenario corresponding to the application type does not match any camera application scenario, a mapping relationship between the general camera and the application program is established.

[0027] In a possible implementation, the method further includes:

[0028] A mapping relationship between all the application types and the general cameras is established.

[0029] In one possible implementation, determining, from the at least one first camera, a second camera that the first application can currently call and determining the second access permission for the second camera based on the current call state, the corresponding call policy, and the corresponding first access permission of each first camera includes at least one of the following operations:

[0030] If the first cameras include an exclusive camera, determining an exclusive camera whose current call state is idle among the exclusive cameras as the second camera, and determining the corresponding first access permission as the corresponding second access permission;

[0031] If the first cameras include a shared camera, determining a shared camera whose current call state is idle among the shared cameras as the second camera, and determining the corresponding first access permission as the corresponding second access permission;

[0032] If the first cameras include a shared camera, determining a shared camera whose current call state is in a used state among the shared cameras as the second camera, and determining the data permission in the corresponding first access permission as the corresponding second access permission;

[0033] If the first cameras include a general camera, the general camera is determined as the second camera, and the corresponding first access permission is determined as the corresponding second access permission.

[0034] In a possible implementation, granting the second access permission of the second camera to the first application includes:

[0035] If there are multiple second cameras, determining a target camera among the multiple second cameras;

[0036] Grant the first application a second access permission for the target camera.

[0037] In a possible implementation, if there are multiple second cameras, determining a target camera among the multiple second cameras includes any one of the following operations:

[0038] receiving a camera selection report sent by the first application, and determining a camera indicated in the camera selection report among the plurality of second cameras as a target camera, wherein the camera selection report is used to indicate a selected target camera among the plurality of second cameras;

[0039] determining a camera preferred by the user among the plurality of second cameras as a target camera according to the camera call history of the first application;

[0040] According to the camera calling history of the first application, a camera among the plurality of second cameras that was last called by the first application is determined as a target camera.

[0041] In a possible implementation, receiving a camera selection report sent by the first application, and determining a camera indicated in the camera selection report among the plurality of second cameras as a target camera includes:

[0042] If there is more than one second camera, sending authorization information to the first application, where the authorization information is used to indicate the multiple second cameras and the second access permission corresponding to each second camera, so that the first application issues a camera selection prompt based on the authorization information, where the camera selection prompt is used to remind the user to select a target camera from the multiple second cameras;

[0043] receiving a camera selection report sent by the first application, wherein the camera selection report is used to indicate a target camera selected from the plurality of second cameras, the target camera being determined by the first application based on a detected user operation in response to the camera selection prompt;

[0044] The camera indicated in the camera selection report among the plurality of second cameras is determined as a target camera.

[0045] In a possible implementation, the method further includes:

[0046] If the second camera called by the first application is a general-purpose camera and multiple control instructions for controlling the second camera are received at the same time, determining a priority response control instruction from the multiple control instructions;

[0047] Control the second camera to execute the priority response control instruction.

[0048] In a possible implementation, determining a priority response control instruction from multiple control instructions includes:

[0049] Determining a priority response control instruction from the multiple control instructions according to the priority of the application corresponding to each control instruction and / or the historical usage record of the application corresponding to each control instruction;

[0050] The priority of the application is determined according to the application type of the application.

[0051] In a second aspect, an embodiment of the present application provides a data transmission device, characterized by comprising:

[0052] processor;

[0053] a memory for storing processor-executable instructions;

[0054] The processor is configured to implement the camera control method of the first aspect or one or more of the multiple possible implementations of the first aspect when executing the instruction.

[0055] In a third aspect, a non-volatile computer-readable storage medium stores computer program instructions thereon, characterized in that when the computer program instructions are executed by a processor, the camera control method of the first aspect or one or more of the multiple possible implementation methods of the first aspect is implemented.

[0056] In a fourth aspect, a computer program product includes a computer-readable code, or a non-volatile computer-readable storage medium carrying the computer-readable code. When the computer-readable code runs in an electronic device, the processor in the electronic device executes the camera control method of the first aspect or one or more of the multiple possible implementations of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate exemplary embodiments, features, and aspects of the application and, together with the description, serve to explain the principles of the application.

[0058] Figure 1 A schematic diagram showing a prompt for an application in a mobile phone to apply for camera permission in the related art.

[0059] Figure 2 A schematic diagram illustrating an application scenario of a camera control method according to an embodiment of the present application.

[0060] Figure 3 A flowchart of a camera control method according to an embodiment of the present application is shown.

[0061] Figure 4 A flowchart of a camera control method according to an embodiment of the present application is shown.

[0062] Figures 5A-5C A schematic diagram showing a first prompt according to an embodiment of the present application.

[0063] Figure 6 A schematic diagram showing the camera permissions displayed by the vehicle computer through the interface according to one embodiment of the present application is shown.

[0064] Figure 7 A block diagram of the architecture of a control device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0065] Various exemplary embodiments, features, and aspects of the present application will be described in detail below with reference to the accompanying drawings. The same reference numerals in the accompanying drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise indicated.

[0066] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0067] In addition, numerous specific details are provided in the detailed description below to better illustrate the present application. Those skilled in the art will appreciate that the present application can be practiced without certain specific details. In some instances, methods, means, components, and circuits well known to those skilled in the art are not described in detail in order to highlight the main purpose of the present application.

[0068] In related technologies, mobile phones, tablets and other terminal devices are equipped with at least one camera, and the application in the terminal device can apply for camera usage rights when it is first installed on the terminal device and opened by the user. The usage rights include whether the camera can be used and the time of use of the camera. For example, Figure 1 The following is a schematic diagram showing a prompt for an application in a mobile phone to apply for camera permissions in the related art. Figure 1 As shown, taking the terminal device as a mobile phone as an example, after an application 1 in the mobile phone is opened for the first time, it can be determined according to the configuration parameters of the application 1 itself that it needs to apply for the camera permission of the mobile phone (for example, the application 1 can apply for the camera permission of the mobile phone through its own AndroidManifest.xml file).<uses-permissionandroid:name="android.permission.CAMERA" / > The user then determines that the system camera needs to be requested for permission (a prompt T1 for requesting camera permission is displayed on the screen). This prompt T1 can remind the user to select one of the three permissions: "Reject," "Ask," or "Allow only during use" to authorize application 1. Based on the detected user operation, the system then requests permission from the phone to obtain the user-authorized permission, allowing application 1 to access the phone's camera according to the permission granted by the user. However, this camera permission authorization method has the following problems:

[0069] First, taking a mobile phone with a front-facing camera and a rear-facing camera as an example, the camera authorization in the related art grants application 1 a unified permission to use all cameras on the phone, including the front and rear cameras, without granting separate permission to use the front and rear cameras. The granularity of the camera usage authorization is too coarse and only applies to relatively simple camera usage scenarios. While the camera is being used by application 1, if it is detected that the user wants to use the camera through application 2, the terminal device will stop application 1 from using the camera and then control the camera to continue being used by application 2. In other words, the camera can only be used by one application at a time, which limits the user's access to the camera through the application and prevents the user from using the same camera through multiple applications at the same time.

[0070] Second, in complex camera usage scenarios involving multiple cameras, such as cars, existing technologies require dedicated cameras for each function to ensure the proper functioning of various functions, such as driving recorder, driver monitoring, assisted driving, and rearview camera. For example, assume a car includes camera 1 for driving recorder, camera 2 for rearview camera display, camera 3 for assisted driving, and camera 4 for monitoring the driver's safety. While driving, the user activates the car's driving recorder application C, driver monitoring application A, and assisted driving application to ensure driving safety. Cameras 1, 3, and 4 all need to be activated and transmit collected data to each application. However, the data from cameras 1, 3, and 4 is only used by the corresponding application and is not authorized for use by other applications controlled by the car's onboard computer. The onboard computer may be installed inside the car, with its screen mounted on the center console. Users can install various applications, such as music and video players, on the computer. The driver can control each application and configure the car's functions by clicking on the user interface displayed on the computer screen. For example, the driver can click the virtual button for the function of automatically closing all windows when locking the car on the car computer to close all the windows of the car when locking the car. The driver can click the icon of the music player application on the car computer to enter the application and select songs to play. The existing technology does not provide a feasible method for authorizing the use rights of multiple cameras separately. If the camera use permission authorization method of mobile phones, tablets, etc. given in the existing technology is used to authorize and control multiple cameras in the car, it will happen that when camera 4 is being used for assisted driving, if other applications use camera 4, camera 4 will transmit data to the new application. No longer transmitting data to the assisted driving application will cause the data of the assisted driving application to be interrupted, and the driver cannot be assisted in driving normally, which seriously endangers driving safety.

[0071] Alternatively, even if the data from the same camera can be shared with different applications, there are still the following problems:

[0072] For example, suppose application A controls driver monitoring camera 4 to capture the driver's facial information, enabling timely notification of driver fatigue. If application B also gains control of the driver monitoring camera and sends a zoom command to camera 4, the facial information captured by application A will be generated based on the zoomed image, compromising application A's fatigue monitoring function and endangering the driver's driving safety. Another example: While driving, a user controls dashcam 1 through application C. Upon seeing a beautiful scene, the user launches application D to record it. However, to capture a clear view through application D, the user zooms in on a portion of camera 1. Application C then captures a zoomed-in dashcam video, potentially preventing proper recording of traffic accidents and other situations. Furthermore, the dashcam video may not include relevant reference images, rendering the dashcam video useless.

[0073] The aforementioned problem may also arise in intelligent robots equipped with multiple cameras. For example, the intelligent robot is equipped with an obstacle detection camera M, which enables the robot to automatically avoid obstacles by analyzing images captured by camera M. In this case, if a user wishes to experience the robot's perspective, they can obtain control rights for the obstacle detection camera M through an application 7 (which has already obtained permission to use camera M). However, if the user zooms in or out of the image captured by camera M through application 7, even if the data from camera M is simultaneously transmitted to application 7 and used as the basis for obstacle detection, the zoomed-in or zoomed-out image captured by camera M will result in inaccurate or abnormal obstacle detection results. This may prevent the robot from timely or accurately avoiding actual obstacles, potentially causing damage to the robot.

[0074] It can be seen that the camera permission control in related technologies is difficult to achieve precise control over the authorized use of multiple cameras, and even serious problems such as damage to objects such as cars equipped with cameras and threats to user safety may occur.

[0075] To address the above-mentioned issues, embodiments of the present application provide a camera control method and device. This method can precisely manage and control the camera permissions of a multi-camera system, controlling each camera based on its type and the type of application that calls it. This ensures the normal operation of the system while enabling categorized and hierarchical control of the cameras, meeting the needs of users in complex application scenarios involving multi-camera systems.

[0076] In order to illustrate the camera control method and device provided in the embodiments of the present application, the embodiments of the present application will take a smart car as an example of a subject equipped with multiple cameras to illustrate the implementation of the camera control method and device. The implementation of the camera control method and device in other subjects will not be repeated. Figure 2 A schematic diagram illustrating an application scenario of a camera control method according to an embodiment of the present application. Figure 3 A flowchart of a camera control method according to an embodiment of the present application is shown.

[0077] like Figure 2 As shown, it is assumed that a plurality of cameras are installed in the car 10, including: a camera C1 for recording driving. A rearview auxiliary monitoring camera C2 for monitoring the rear seats in the car. A camera C3 for implementing lane keeping assistance in assisted driving. A camera C4 for monitoring the driver's safe driving. A camera C5 for implementing reversing assistance in assisted driving. A camera C6 for in-car entertainment for the driver and passengers. A camera C7 for monitoring the interior cabin of the car 10. The applications installed in the car computer 100 in the car 10 can call the cameras of the car 10. Among them, the applications installed in the car 10 may include built-in applications that can call cameras that match the various functions of the car 10, such as applications for driving recording, driver monitoring, rearview monitoring, lane keeping assistance, reversing assistance, and in-car entertainment lens control. The applications installed in the car 10 may also include applications downloaded and installed by users according to their own needs, and so on.

[0078] like Figure 3 As shown, the camera control method provided in this application includes setting phase steps and use phase steps.

[0079] The “setting phase steps” may be executed before the subject is actually used, and the subject’s R&D personnel may ensure that the subsequent “use phase steps” can proceed as normal by executing the “setting phase steps” in advance. The “setting phase steps” may be executed by the subject itself (such as a control device such as a processor in the subject used to control the subject), an external device that does not belong to the subject and is used to configure the subject, etc. For example, assuming that the subject is a car, the car’s R&D personnel may use the car’s onboard computer or the equipment that implements the car’s pre-factory configuration to execute the setting phase steps before the car leaves the factory. Assuming that the subject is an intelligent robot, the robot’s R&D personnel may use the robot’s internal control device or the equipment that implements the robot’s pre-factory configuration to execute the setting phase steps before the robot leaves the factory. Among them, if Figure 3 As shown, the "setting phase step" may include steps S11 to S16.

[0080] The “use phase steps” can be applied to the main body and executed by the control device of the main body, so that the control device of the main body can realize the camera control according to each step of the use phase during the use of the main body. Figure 3 As shown, the “use phase steps” may include steps S21 to S28.

[0081] The "Setup Phase Step" is executed before the "Use Phase Step." The interval between the completion of the "Setup Phase Step" and the start of the "Use Phase Step" is not fixed. After the "Setup Phase Step" is completed, the "Use Phase Step" can be executed repeatedly, and the "Setup Phase Step" can be skipped before each "Use Phase Step" is executed. For example, assuming the subject is a car, the "Setup Phase Step" is executed before the car leaves the factory. During the period of use by the user, the car's computer only executes the "Use Phase Step" and no longer executes the "Setup Phase Step." The following describes the implementation of the "Setup Phase Step" and "Use Phase Step" using examples.

[0082] Set Stage Steps

[0083] In step S11, camera-related parameters are determined for each camera to be controlled. These camera-related parameters may be parameters related to the camera and can be used to subsequently classify the cameras into different types and application scenarios. In some embodiments, the camera-related parameters may include: the functional purpose of the camera; the camera's installation parameters in the subject, such as the installation position and lens orientation; and the type of subject in which the camera is located, such as a robot, vehicle, drone, etc.

[0084] In step S12, the camera type of each camera is set based on the camera-related parameters of each camera. Step S13 is then executed after step S12 is completed. Step S13 may be executed after determining the type of each camera individually, or after determining the types of all cameras in the subject.

[0085] In a possible implementation, in step S12, multiple cameras installed in a subject such as a car can be directly divided into camera types according to the different functions and uses of each camera. Camera types can include: exclusive class (also known as exclusive class, dedicated class, etc.), shared class (also known as public class, same-use class, etc.) and general class (also known as ordinary class, general class, etc.). In some embodiments, in step S12, the camera type of the camera can also be marked through a specific field in the configuration file of each camera after the camera type is set, so that the camera type of the camera can be determined through the configuration file of each camera in the subsequent "use phase step". For example, assuming the subject is as follows Figure 2 In the illustrated car 10, based on the different functions and uses of the cameras, camera C1 can be determined as a shared camera. Camera C2 is a dedicated camera. Camera C3 is a shared camera. Camera C4 is a dedicated camera. Camera C5 is a shared camera. Camera C6 is a universal camera. Camera C7 is a shared camera.

[0086] In step S13, the type of the camera is determined. If the camera is a dedicated camera or a shared camera, step S14 is executed. If the camera is a universal camera, step S15 is executed.

[0087] In step S14, the camera application scene corresponding to the camera is set. After completing step S14, step S15 is executed.

[0088] In one possible implementation, in step S14, when the camera is an exclusive camera or a shared camera, the camera application scenario corresponding to the camera can be determined based on the camera-related parameters of the camera. Since the actual functions of exclusive cameras and shared cameras in different subjects are different, the camera application scenarios that can be applied to each exclusive camera and each shared camera can be set according to the subject on which the camera is installed and the functions of the exclusive camera and the shared camera. Among them, the camera application scenarios of cameras with different functional uses may be different. The camera application scenarios corresponding to the same camera may be one or more. For example, assuming the subject is Figure 2For the car 10 shown, camera application scenarios may include: driving recording scenario, driver safety monitoring scenario, cockpit monitoring scenario, rearview assist scenario, reversing assist scenario, lane keeping assist scenario, etc. Figure 2 The camera application scenario for camera C1 (shared camera) is the driving recording scenario, while the camera application scenario for camera C2 (exclusive camera) is the rearview assist scenario. The camera application scenario for camera C3 (shared camera) is the lane keeping assist scenario. The camera application scenario for camera C4 (exclusive camera) is the driver safety monitoring scenario. The camera application scenario for camera C5 (shared camera) is the reversing assist scenario. The camera application scenario for camera C7 (shared camera) is the cabin monitoring scenario.

[0089] In step S15, a mapping relationship between the camera and the application type is established. After step S15 is completed, step S16 is executed.

[0090] In a possible implementation, in step S15, all applications that can be installed by the subject and the application type of each application can be determined first to obtain multiple application types; then, according to each application type, the program application scenario corresponding to the corresponding application in actual operation is determined; and the program application scenario is matched with at least one camera application scenario (including the camera application scenario corresponding to the shared camera and / or the camera application scenario corresponding to the exclusive camera). If there is a camera application scenario that matches the program application scenario in at least one camera application scenario, the exclusive camera or shared camera that matches the camera application scenario with the program application scenario can be determined as the camera that can be called by the application of the application type corresponding to the program application scenario, and a mapping relationship between the application type corresponding to the program application scenario and the exclusive camera or shared camera that matches the camera application scenario with the program application scenario is established. If the program application scenario and the camera application scenario do not match, the general camera can be determined as the camera that can be called by the application of the application type corresponding to the program application scenario, and a mapping relationship between the application type corresponding to the program application scenario and the general camera is established.

[0091] In one possible implementation, in step S15, the camera that can be called by the application corresponding to the application type whose program application scenario is different from the camera application scenario can be set as a general-type camera. In this way, the same application type only has a mapping relationship with one type of camera. Alternatively, in step S15, a general-type camera can be set to correspond to all application types. Then, for the application type whose program application scenario matches the camera application scenario, there is a mapping relationship between it and the matching shared-type camera or exclusive-type camera, and the application type also has a mapping relationship with the general-type camera; for the application type whose program application scenario does not match the camera application scenario, there is only a mapping relationship with the general-type camera. In this way, application programs of all application types can call the general-type camera, and the camera whose program application scenario matches the camera application scenario can call the general-type camera and the shared-type camera or exclusive-type camera whose camera application scenario matches the program application scenario.

[0092] In some embodiments, whether the program application scene matches each camera application scene can be determined by the degree of scene similarity. The higher the scene similarity, the higher the degree of match. A similarity threshold can be pre-set. If the similarity between the program application scene and the camera application scene is greater than or equal to the similarity threshold, it can be determined that the program application scene matches the camera application scene. For example, assuming the similarity threshold is 80%, if the similarity between the program application scene and a certain camera application scene is greater than or equal to 80%, it can be determined that the camera application scene matches the program application scene.

[0093] For example, suppose the subject is Figure 2 The car 10 shown is equipped with Figure 2Cameras C1, C2, ..., C7 are shown. Camera C1 (a shared camera) corresponds to the driving recording scenario, while camera C2 (a dedicated camera) corresponds to the rearview assist scenario. Camera C3 (a shared camera) corresponds to the lane keeping assist scenario. Camera C4 (a dedicated camera) corresponds to the driver safety monitoring scenario. Camera C5 (a shared camera) corresponds to the reversing assist scenario. Camera C7 (a shared camera) corresponds to the cabin monitoring scenario. Camera C6 is a general-purpose camera. Then, in step S15, when it is determined that the application types of the application programs that can be installed on the car 10 include: application type 1, application type 2...application type 9, the program application scenario corresponding to each application type can be determined (as shown in Table 1 below), and then based on the implementation method of the above step S15, the mapping relationship between application type 1, application type 2...application type 10 and the camera of the car 10 is determined (as shown in Table 1 below), and the application type and camera mapping relationship table shown in Table 1 below is obtained.

[0094] As shown in Table 1, application types 1, 2, ..., and 9 are mapped to camera C6. Application type 1 is mapped to camera C4. Application type 2 is mapped to camera C2. Application types 3 and 4 are mapped to camera C3. Application type 6 is mapped to camera C5. Application types 7 and 8 are mapped to camera C7. Application type 9 is mapped to camera C6. Therefore, based on the camera access permissions, we can determine:

[0095] Applications of application type 1 have permission to call cameras C4 and C6.

[0096] Applications of application type 2 have permission to call cameras C2 and C6.

[0097] Applications of application type 3 have permission to call cameras C1 and C6.

[0098] Applications of application type 4 have the permission to call cameras C3 and C6.

[0099] Applications of application type 5 have the permission to call cameras C3 and C6.

[0100] Applications of application type 6 have the permission to call cameras C5 and C6.

[0101] Applications of application type 7 have permission to call cameras C7 and C6.

[0102] Applications of application type 8 have the permission to call cameras C7 and C6.

[0103] Applications of application type 9 have permission to call camera C6.

[0104] Table 1 Application type and camera mapping relationship table

[0105]

[0106] In one possible implementation, in step S15, the classification type corresponding to the application may be set based on the application type of the application. The classification type of the application may be one of general, shared, and dedicated. Specifically, if the cameras mapped to the application type of the application only include general cameras, the classification type of the application may be set to general. If the cameras mapped to the application type of the application include general cameras and shared cameras, the classification type of the application may be set to shared. If the cameras mapped to the application type of the application include general cameras and dedicated cameras, the classification type of the application may be set to dedicated. General applications can access general cameras. Shared applications can access shared cameras and general cameras. Dedicated applications can access dedicated cameras and general cameras.

[0107] In step S16, a calling strategy for each type of camera is determined.

[0108] In a possible implementation, in step S16, corresponding calling strategies may be set for different camera types according to usage characteristics of the cameras of different camera types to ensure normal control of the cameras.

[0109] To illustrate the differences between different types of cameras, the following describes dedicated cameras, shared cameras, and universal cameras, as well as the calling strategies for each type of camera, with examples.

[0110] Dedicated cameras can also be called exclusive cameras, exclusive cameras, etc. The dedicated camera can be a camera installed in the main body, with specific functions and used exclusively by only one application, for example, Figure 2Consider the driver safety monitoring camera C4 installed in vehicle 10. In some embodiments, the dedicated camera access policy may include: each dedicated camera can only be accessed by the first application that first requests access to the dedicated camera at a time, and the application currently accessing the dedicated camera has full access rights to the camera. Full access rights include both control and data permissions for the dedicated camera. This allows the application currently accessing the dedicated camera to have exclusive access, preventing interference from other applications. For example, while vehicle 10 is in motion, camera C4 (the dedicated camera) is always available only to the application that monitors driver safety. Assume that vehicle 10's onboard computer 100 includes applications 1, 2, and 3 capable of monitoring driver safety. At a certain moment, application 1 is accessing camera C4 for driver safety monitoring. If the onboard computer 100 detects that application 2 has also requested access to camera C4, the onboard computer 100 will deny application 2's access to camera C4 because it determines that camera C4 has already been accessed by application 1.

[0111] Shared cameras can also be called shared cameras, same-use cameras, etc. The shared cameras can be installed in the main body, with specific functions that can be used by multiple applications, for example, Figure 2 In some embodiments, the shared camera call policy may include: each shared camera can be called simultaneously by one or more applications of the same application type. Furthermore, if there are multiple applications calling a shared camera, the application that first requests to call the shared camera has full access rights to the shared camera, while the remaining applications only have data rights to the shared camera. This ensures that the application that first requests to call the shared camera has complete and exclusive access to the shared camera, preventing interference from other applications. The data rights granted to other applications ensure that they can use the data collected by the shared camera. For example, while the car 10 is moving, if camera C1 (a shared camera) is called by a driving recording application, and the vehicle computer 100 receives a call from application 4 to camera C1, then, since the vehicle computer 100 determines that camera C1 has already been called by the driving recording application, it will allow application 4 to call camera C1 and grant application 4 data rights to camera C1.

[0112] A general-purpose camera can also be called an ordinary camera or a general-purpose camera. The general-purpose camera can be installed in the main body and has no specific functions that can be used by multiple applications. For example, Figure 2 The in-car entertainment camera C6 installed in automobile 10 can be called by one or more applications of the same application type at the same time. Each application that calls the general-purpose camera has full access to the general-purpose camera. If multiple applications send control instructions to the general-purpose camera at the same time, the multiple control instructions can be filtered according to pre-set response rules to determine which control instruction should be prioritized. This ensures that multiple applications that call the general-purpose camera can use the camera independently and that the general-purpose camera can respond to the control instructions in an orderly manner even when multiple control instructions are sent simultaneously. The control instructions can correspond to the camera's control permissions and / or data permissions.

[0113] In one possible implementation, the response rules may include determining a priority response control instruction from multiple control instructions based on the priority order of the application programs corresponding to each control instruction. In some embodiments, the priorities of different application types can be pre-set. For example, the priority order of application types can be set from high to low as follows: application types corresponding to dedicated cameras, application types corresponding to shared cameras, and application types corresponding to general cameras. In other words, the priority order of application types can be set from high to low as follows: application types classified as dedicated, application types classified as shared, and application types classified as general.

[0114] In some embodiments, the response rules may also include: if there are multiple applications with the highest priority among multiple applications that simultaneously issue control instructions to general-purpose cameras, then the priority response control instruction may be further selected from the multiple control instructions with the highest application priority based on the historical usage records of the application corresponding to each control instruction. The content recorded in the historical usage records may include data characterizing the historical usage status of the application, such as the frequency of application use, the total duration of use, and the interval between the last use and the current moment. In some embodiments, the control instructions corresponding to the applications with high frequency of use, long total usage duration, and short interval duration in the "multiple control instructions with the highest application priority" may be determined as priority response control instructions. In some embodiments, the usage status evaluation value of each application may be determined based on the historical usage records of each application, and then the control instruction of the application with the highest usage status evaluation value in the "multiple control instructions with the highest application priority" may be determined as priority response control instructions. In some embodiments, a corresponding weight may be set for each type of historical usage record, and then the usage status evaluation value of the application may be calculated in a weighted summation manner. For example, assuming that Figure 2 In the illustrated example, camera C6 in car 10 is simultaneously called by applications a, b, c, d, and e, and all five applications simultaneously issue control commands to camera C6. For example, if application e is determined to have the highest priority among applications a, b, c, d, and e, then the control command issued by application e can be prioritized. For example, if applications a, b, and c have the same priority and are all higher than applications d and e, then the usage status evaluation values ​​of applications a, b, and c can be calculated separately. Then, the control command issued by the application with the highest usage status evaluation value among applications a, b, and c, such as application a, can be prioritized.

[0115] In a possible implementation, the response rule may also be simply: based on the historical usage records of the application corresponding to each control instruction, a priority response control instruction is selected from multiple control instructions. In some embodiments, the control instruction corresponding to the application with high usage frequency, long total usage time, and short interval time among the "multiple control instructions" can be determined as the priority response control instruction. In some embodiments, the control instruction of the application with the highest usage status evaluation value among the multiple control instructions can be determined as the priority response control instruction. For example, assuming that Figure 2As shown, camera C6 in car 10 is simultaneously used by applications a, b, c, d, and e, and all five applications simultaneously issue control commands to camera C6. If application d is determined to have the highest usage status evaluation value among applications a, b, c, d, and e, the control command issued by application d can be prioritized.

[0116] In a possible implementation, the access rights of the application to each camera include control permissions and / or data permissions for the camera, and the full access rights include control permissions and data permissions.

[0117] Among them, control permissions can be control permissions that can change the way the camera collects images or change the images or videos collected by the camera. After the application has control permissions, it can adjust or process the way the camera collects images or videos, or the content of the collected images or videos itself, based on the user operations detected by the application, so that the images or videos collected by the camera ultimately obtained by all applications currently calling the camera change. Control permissions for the camera can include: automatic or manual control of the camera's exposure, focus, and white balance. Control of the zoom and shooting angle of the image collected by the camera. Control of whether the camera's flash is turned on, for example, automatically adjusting the flash on or off according to the intensity of the light, and manually controlling the flash on or off. Control of the picture effects of the images or videos collected by the camera, for example, adding filters to the collected images, beautifying, cropping, correcting, etc., and setting algorithms for processing the images or videos collected by the camera.

[0118] Data permissions can include the ability to access and display or store data collected by the camera. With this permission, applications can access images or videos captured by the camera based on user actions detected by the application, without changing the images or videos ultimately captured by all other applications currently accessing the camera. Data permissions can also include: Preview permissions, which control previewing of images captured by the camera. Applications that detect a user's preview operation can access the camera's captured data, obtain the real-time image, and then display the preview to the user, allowing the user to view the real-time image captured by the camera in preview form. Photo permissions, which control taking photos of images captured by the camera. Applications that detect a user's photo operation can access the camera's captured data, obtain the real-time image, and then take photos for the user. Video recording permissions, which control recording (also known as filming, shooting, etc.) of images captured by the camera. Applications that detect a user's recording operation can access the camera's captured data, obtain the real-time video recorded by the camera (also known as recording). Real-time thumbnail permissions allow you to obtain part or all of the data collected by the camera to obtain a "small image" with a small amount of data, so as to further control the analysis and processing of the "small image", so that the application that detects the user's real-time thumbnail operation can obtain the "small image" of the image collected by the camera for analysis and processing, and feedback the results of the analysis and processing to the user, so that the user can further respond based on the results of the analysis and processing. "Small image" can refer to an image that is smaller in size and / or has a lower resolution than the image collected by the camera in real time. This can facilitate the application's analysis and processing of the "small image" and increase the speed of analysis and processing. For example, if an AR application has real-time thumbnail permissions, it can obtain a continuous data stream of "small image" so that the AR application can generate AR virtual images in real time and realize AR navigation functions.

[0119] In the camera control method of the present application, after executing the aforementioned "setup phase steps," the mapping relationship between cameras and application types may change due to changes in the applications that can be installed by the subject, their application types, and their application scenarios. Furthermore, to optimize the user experience with cameras, manufacturers of subjects such as automobiles may also continuously update the call policies for some or all camera types. Therefore, the subject can periodically update the "map between cameras and application types" and / or the "call policy for each camera type." This update process can be initiated proactively by the subject to the server and / or by the server to the subject. In some embodiments, the call policy, camera type, camera application scenario, the mapping relationship between camera and application type, and the application classification type can be stored in read-only memory on the vehicle computer to reduce the probability of malicious modification of this information and ensure normal and secure operation of the subject. For example, without considering security, users can be given permission to modify at least one of the call policy, camera type, camera application scenario, the mapping relationship between camera and application type, and the application classification type to increase user controllability and meet diverse user needs.

[0120] Use Phase Steps

[0121] Figure 4 FIG. 1 is a flow chart showing a camera control method according to an embodiment of the present application. Figure 3 、 Figure 4 As shown, in the "use phase step" the vehicle computer (control device of the main body) is used to perform steps S21 to S28, wherein, Figure 3 The "use phase steps" shown may include: permission authorization and camera call. "Permission authorization" includes steps S21-S24, and the vehicle computer implements the camera permissions of different applications through "permission authorization", and the authorization selected by the vehicle computer and the user, and completes the storage of access rights records for each application. "Camera call" includes steps S25-S26, and the vehicle computer can control the camera call according to the access rights record. In the camera control method provided in the embodiment of the present application, Figure 4 As shown, in the "Authorization" step, the second application is used to execute steps S31-S34. The second application can be any application installed on the vehicle computer. "Camera Call" is a step that the vehicle computer executes each time the first application calls for camera use. "Authorization" is actually a pre-step to the "Use Phase Step," and can only be executed by the second application (including the first application involved in "Camera Call") if the requested conditions are met.

[0122] "Authorization"

[0123] like Figure 4 As shown, in step S31, the second application program issues an access request when determining that the request condition is met.

[0124] In one possible implementation, the request condition may include at least one of the following: the second application is opened and used for the first time and needs to obtain camera access permission during operation, or the second application is opened and does not have the camera access permission required for operation. In this way, the second application can issue an access request even if it needs to obtain camera access permission but does not have it.

[0125] In step S21, Figure 3 picture, Figure 4 As shown, the vehicle computer receives an access request for applying for camera access rights and determines a second application corresponding to the access request.

[0126] In one possible implementation, the access request may indicate a second application requesting camera access rights. The access request may include a program identifier for indicating which of the multiple applications installed in the car's onboard computer (the main body's control device) the second application is. The program identifier may be the name, number, or other information that can identify the application, and this application does not impose any restrictions on this. After receiving the access request, the car's onboard computer (the main body's control device) may determine the second application that issued the access request based on the program identifier in the access request. In one possible implementation, if the access request does not contain information such as a program identifier indicating the second application, the car's onboard computer may also directly determine the application that issued the access request as the second application.

[0127] In step S22, as Figure 3 picture, Figure 4 As shown, according to the application type of the second application and the mapping relationship between cameras and application types, at least one third camera allowed to be accessed by the second application and the third access permission of each third camera are determined from the installed multiple cameras.

[0128] In one possible implementation, in step S22, the vehicle computer can determine at least one third camera that the vehicle computer allows the second application to access from the multiple cameras installed, based on the application type of the second application and the mapping relationship between the camera and the application type. In some embodiments, the access request may also include the application type of the second application. In step S22, the vehicle computer can directly filter out at least one third camera that the second application is allowed to access from the multiple cameras installed in the car where the vehicle computer is located, based on the application type in the access request and the mapping relationship between the locally stored camera and the application type (the mapping relationship determined in step S15 above). In some embodiments, if the access request does not include the application type of the second application, the vehicle computer can directly obtain the program type of the second application from the program configuration file of the second application, and then in step S22, the vehicle computer can filter out at least one third camera that the second application is allowed to access from the multiple cameras installed in the car where the vehicle computer is located, based on the determined application type and the mapping relationship between the locally stored camera and the application type. For example, referring to Figure 2 In the example of the mapping relationship shown in the car 10 and Table 1, assuming that the application type of the second application is "application type 3", the vehicle computer can determine according to Table 1 that the third cameras allowed to be accessed by the second application include camera C3 and camera C6.

[0129] In one possible implementation, in step S22, the vehicle computer may first select at least one candidate camera corresponding to the classification type of the second application from multiple cameras. If all candidate cameras are general cameras, the candidate camera is directly determined as the third camera. Otherwise, if not all candidate cameras are general cameras, at least one third camera that the vehicle computer allows the second application to access may be determined from the candidate cameras based on the application type of the second application and the mapping relationship between cameras and application types. For example, assuming the second application is a shared application, all shared and general cameras may be determined as the third camera. Then, based on the mapping relationship between cameras and application types, unselectable cameras among the shared cameras that do not correspond to the application type of the second application are determined. Finally, all cameras among the candidate cameras, excluding the unselectable cameras, are determined as the third camera. If the second application is a dedicated application, all dedicated and general cameras may be determined as candidate cameras. Then, based on the mapping relationship between cameras and application types, unselectable cameras among the dedicated cameras that do not correspond to the application type of the second application are determined. Finally, all cameras among the candidate cameras, excluding the unselectable cameras, are determined as the third camera. Assuming that the second application is a general application, all general cameras can be determined as the third camera. In this way, the process of determining the third camera can be simplified and the speed of determining the third camera can be increased.

[0130] In one possible implementation, in step S22, after determining at least one third camera or during the process of determining the third camera, the vehicle computer may further determine the third access permission for the second application to access each third camera based on the third camera's call history and call policy. Determining the third access permission is optional. In some embodiments, the second application's third access permission for each third camera may include: full access permission (including control permissions and data permissions), data permissions, or no access permission.

[0131] In some embodiments, due to the different functions of different cameras, the states in which they are called may differ. Therefore, when determining the third access permission for each third camera, the vehicle computer may first determine, based on the third camera's call history, whether the third camera is always on and called. If the third camera is always on and called, the vehicle computer may determine, based on the third camera's call policy, which type of third access permission the vehicle computer can grant to the second application for the third camera. If the third camera is not always on and called, the vehicle computer may determine that the third access permission that can be granted to the second application for the third camera is full access permission.

[0132] For example, Figure 2 Taking the car 10 as an example, some car users will set the camera C1 used only for driving recording to be in a state of being always on and called in order to protect the safety of the vehicle, so as to record the driving. In this case, if the third camera includes camera C1, and it is determined based on the call record of camera C1 that camera C1 is in a state of being always on and called, then according to the call policy of the third camera C1 (such as the call policy of the shared camera described above), it can be determined that the third access right of the second application to camera C1 is only a data-type permission, and does not have full access right to camera C1 (that is, it does not have control-type permission to camera C1). For another example, Figure 2 Taking the car 10 as an example, if the third camera includes camera C4, and it is determined from the call record of camera C4 that camera C4 is always in the on-call state, then according to the call policy of the third camera C4 (such as the call policy of the exclusive camera described above), it can be determined that the second application has no third access right to camera C4. Figure 2 Taking the car 10 as an example, if the third camera includes camera C6, and it is determined according to the calling record of camera C6 that camera C6 is in a state of being always turned on and called, then according to the calling strategy of the third camera C6 (such as the calling strategy of the general camera described above), it can be determined that the third access permission of the second application to camera C6 is full access permission.

[0133] In step S23, as Figure 3 picture, Figure 4 As shown, the first information of each third camera is sent, and the first information includes at least one of the camera identification of each third camera, the functional purpose of the camera, and the installation parameters. In some embodiments, the first information may also include the third access permission of each third camera.

[0134] In one possible implementation, Figure 4 As shown, after the second application receives the first information, it can execute step S32. In some embodiments, in step S32, after the second application receives the first information, it can display a first prompt to the user. To illustrate different implementations of the first prompt provided in this application, Figures 5A-5C A schematic diagram showing a first prompt according to an embodiment of the present application.

[0135] In one possible implementation, the first prompt may be used to remind the user that the vehicle computer allows the second application to call and access the third camera. The first prompt may include at least one of the first information. In some embodiments, the first prompt may be displayed to the user in a pop-up window, sidebar, etc. on a display screen (such as a vehicle computer display screen). The first prompt may be a schematic diagram (such as a diagram) that can indicate the third camera. Figure 5A Q11 shown), and / or lists (such as Figure 5B Q12 shown) and so on. For example, Figure 2 As an example of the car 10 shown in FIG. 1 , assuming that the third camera is camera C1 and camera C6, then Figure 5B As shown, the first prompt can be displayed to the user through a list (table line is not shown in the figure) on the display screen of the vehicle computer, or it can be displayed as shown in FIG. Figure 5A As shown in the display screen of the vehicle computer, a first prompt is presented to the user through a schematic diagram.

[0136] In one possible implementation, the first prompt, while reminding the user that the vehicle computer allows the second application to access the third camera, may also be used to remind the user to select a first camera from among the third cameras that the user specifies as being accessible by the second application, and / or to remind the user to determine a first access permission for the first camera. The first access permission may be the access permission determined by the user from among the third access permissions of the third camera selected by the user as the first camera.

[0137] In some embodiments, as Figure 5A Q11 and Figure 5B As shown in Q12 of FIG, the third access rights of the third camera and the first selection control K1 corresponding to each third access right and / or the second selection control K2 corresponding to each third camera can be displayed in the first prompt. The second selection control K2 can indicate whether the corresponding third camera is selected by the user as the first camera (e.g. Figure 5A 、 5B The state of K2 shown in FIG indicates that the corresponding third camera is selected as the first camera by the user, such as Figure 5C The state of K2 corresponding to the camera C6 indicates that the user has chosen not to authorize C6 to the second application, and C6 is not the first camera). Figure 5A 、 Figure 5B The third access rights of the camera C1 shown include: preview rights, photo rights, video rights, and real-time thumbnail rights. The third access rights of the camera C6 include: exposure, focus, white balance control rights, zoom, flash, picture effect control rights, preview rights, photo rights, video rights, and real-time thumbnail rights. In some embodiments, the first selection control K1 can also indicate whether the corresponding third access rights are currently authorized by the user to be assigned to the second application (such as Figure 5A 、 5B The status of K1 shown in FIG indicates that the corresponding third access right is authorized by the user to the second application program. Figure 5C The state of K1 corresponding to each third access right of camera C6 indicates that each third access right of C6 has been chosen by the user not to be authorized to the second application). The second application can control the second selection control K2 to respond to the detected user's click, slide, and other triggering operations on K2, and determine that the user has selected the first camera from the third camera. The second application can control the first selection control K1 to respond to the detected user's click, slide, and other triggering operations on K1, and determine that the user has selected the first access right from the third access right. For example, the second application can display the following information to the user based on the received first information: Figure 5B The first prompt Q12 is shown. Then, based on the user's triggering operation on the second selection control K2 of camera C6, it is determined that the user chooses not to authorize C6 to be called by the second application; and based on the user's triggering operation on "K1 corresponding to the recording permission" and "K1 corresponding to the real-time thumbnail permission" of C1, it is determined that the user does not authorize C6's "recording permission and real-time thumbnail permission" to the second application. Then the second application displays the following to the user: Figure 5C As shown, after the user operation is detected and the user's selection is determined, the first prompt Q13 is shown. From Q13, the user can see that the third camera is camera C1, and the third access rights of C1 are preview permission and photo taking permission.

[0138] In one possible implementation, Figure 4 As shown, when the first prompt can remind the user to specify the first camera and / or specify the first access permission of the first camera, the second application can also execute step S33. Step S33 is an optional step.

[0139] In step S33, the second application can determine the first camera in the third camera that the user specifies the second application can call and the first access permission of the first camera based on the detected user's permission adjustment operation for the first prompt (such as the user's trigger operation for K1 and / or K2 as described above). If the first camera and the first access permission of the first camera are determined in step S33, the second application can also execute step S34. In step S34, the second application sends a user-specified permission report to the vehicle computer. The user-specified permission report can be used to indicate the first camera selected by the user from the third camera and the first access permission of the first camera. For example, the user-specified permission report can include the camera identifier of the first camera and the first access permission of the first camera; or the user-specified permission report can include the camera identifier of the third camera that the user chooses not to authorize the second application to call, and the access permission of the third camera that the user chooses not to authorize the second application to control; and so on.

[0140] In some embodiments, if step S33 is not performed, if no permission adjustment operation is detected in step S33, or if the permission adjustment operation in step S33 indicates that no change has been made to the permissions after the adjustment (e.g., all third cameras are selected by the user as first cameras, and the third access permission of each third camera is the corresponding first access permission), then after executing step S32, the second application may directly execute step S34' or may not return any information to the vehicle computer. In step S34', the second application returns a successful reception report to the vehicle computer, indicating that the second application has successfully received the first information.

[0141] In step S24, as Figure 3 、 Figure 4 As shown, the access permission record of the second application is updated. The access permission record records at least one first camera that the second application can call with user authorization and the first access permission corresponding to each first camera.

[0142] In some embodiments, the vehicle computer can directly update the access permission record of the second application by treating each third camera and the corresponding third access permission determined by the vehicle computer as the first camera and the corresponding first access permission when it receives a "successful reception report" or does not receive any feedback from the second application. For example, if the vehicle computer determines that camera C1 and camera C6 are third cameras, and the third access permissions of C1 and C6 are both full access permissions, then if it receives a "successful reception report" or does not receive any feedback from the second application, the vehicle computer can directly treat cameras C1 and C6 as first cameras, and the first access permissions of C1 and C6 as full access permissions, and record these in the access permission record of the second application, thereby completing the update of the access permission record of the second application.

[0143] In some embodiments, upon receiving a user-specified permission report, the vehicle computer can determine the user-specified first camera and the first access permission of each first camera based on the user-specified permission report, and update the record to the access permission record of the second application to complete the update of the access permission record of the second application.

[0144] In one possible implementation, the vehicle computer can set up a designated local storage space for storing access permission records for each application. Each access permission record corresponds to a first camera that the vehicle computer allows and that the user authorizes to access, as well as the first access permission associated with the first camera. In some embodiments, the user can also configure camera access permissions for each application installed on the vehicle computer through the vehicle computer. For example, the user can use the "Settings" function on the vehicle computer to access a functional interface for configuring permissions for each application. This interface displays the various permissions currently granted to each application. The vehicle computer can update permissions based on user actions on the various permissions in this interface. The "various permissions" may include camera permissions. The interface may display the third camera that the vehicle computer allows the corresponding application to access and the corresponding third access permissions, as well as the first camera of the third camera that the user has selected to be authorized and the first access permission for the first camera. Alternatively, the interface may also display other cameras that the vehicle computer does not allow the corresponding application to access. The permission update may include: upon detecting an adjustment operation for the first camera and the first access permission for the first camera, determining the adjusted first camera and the first access permission for the first camera corresponding to the application, and updating the corresponding access permission record.

[0145] For example, Figure 6 A schematic diagram showing the camera permissions displayed by the vehicle computer through the interface according to an embodiment of the present application is shown. Figure 6As shown, the third camera, the first camera, and other cameras that the vehicle computer does not allow application m to access are displayed in the interface Q2 through corresponding controls and identifiers. Specifically: controls K31, K32, K41, and K42 are all user-operable controls, and B1 is an access-forbidden identifier. K31 and K32 can respectively indicate the first access right and the third access right in the access rights corresponding to the camera. K31 indicates that the corresponding access right is the first access right, K32 indicates that the corresponding access right is the third access right but is currently prohibited by the user for application m to use. K41 indicates that the corresponding camera is the third camera and the third camera has been selected by the user as the first camera, and K42 indicates that the corresponding camera is the third camera but is currently prohibited by the user for application m to use. B1 is used to indicate that the corresponding camera is a camera that the vehicle computer does not allow application m to access. That is, as Figure 6 The first camera of application m is camera C1, and the first access rights of C1 are preview and photo permissions. The third cameras of application m are C1 and C6. The third access rights of C1 are preview, photo permission, video recording permission, and real-time thumbnail permission. The third access right of C6 is not shown in the figure (if the control K42 corresponding to C6 is detected to be triggered and switched to K41, the third access right of C6 can be displayed with reference to C1). The camera that the vehicle computer does not allow application m to access is camera C5. If the vehicle computer detects the triggering operation of the control K32 corresponding to the video recording permission of C1, the vehicle computer can switch K32 to K31 and determine that the first access right of the first camera C1 of application m has been adjusted by the user to preview, photo permission, and video recording permission.

[0146] Steps S21-S24 in the aforementioned "authorization" process are intended to ensure that the finalized first camera of the second application and the first access rights of the first camera are obtained with the dual guarantee of the vehicle computer's permission and user authorization. If the vehicle computer grants permissions to the application without user selection, there is another implementation method for "authorization": upon detecting that the second application has been installed, receiving an access request, or receiving a call request, the vehicle computer directly determines at least one third camera that the second application is allowed to access based on the application type of the second application and the mapping relationship between the application type and the camera; and, based on the call record and call policy of the third camera, determines the third access rights of the second application to each third camera (see the implementation process of step S22 above). Then, the at least one third camera of the second application is directly recorded as the first camera, and the third access rights of each third camera are updated in the access rights record as the corresponding first access rights. This simplifies the implementation process of "authorization."

[0147] Camera call

[0148] In step S25, as Figure 3 As shown, a call request for applying to call a camera is received, and a first application corresponding to the call request is determined, wherein the first application is any one of the above-mentioned second applications.

[0149] In some embodiments, the first application may send a call request to the vehicle computer if it determines that the camera call condition is met. The camera call condition may be that the first application is spontaneously started due to its own operating needs, or it may be that the first application responds to the user's operation to start the camera, etc. For example, if the first application is an application w1 for photo shooting and photo processing, if the application w1 detects that the user has issued an operation to take a photo, it can be determined that the camera needs to be called, and a call request can be generated and sent to the vehicle computer. If the first application is an application w2 that requires face recognition for login, if the application w2 detects that the user has issued an operation to start the application w2, it can be determined that the camera needs to be called, and a call request can be generated and sent to the vehicle computer.

[0150] In one possible implementation, the call request may indicate a request to call a first application for the camera. The call request may include a program identifier indicating which of multiple applications installed in the vehicle computer the first application is, thereby identifying the first application. After receiving the call request, the vehicle computer may determine the first application issuing the call request based on the program identifier in the call request. In one possible implementation, if the call request does not contain information such as a program identifier indicating the first application, the vehicle computer may directly determine the application issuing the call request as the first application.

[0151] In step S26, Figure 3 As shown, after step S25 is executed, the first camera corresponding to the first application and the first access permission of the first application to access the first camera are determined according to the access permission record of the first application.

[0152] In some embodiments, after the vehicle computer determines the first application in step S26, it can obtain the permission access record of the first application from the corresponding local storage space, and then determine the first camera corresponding to the first application and the first access permission of the first camera based on the permission access record.

[0153] In step S27, Figure 3As shown, after executing step S26, based on the current calling state of the first camera of the first application, the corresponding calling policy and the corresponding first access permission, the second camera that the first application can currently call and the second access permission of the second camera are determined from the first camera.

[0154] In one possible implementation, in step S27, after the vehicle computer determines at least one first camera corresponding to the first application and the first access permission corresponding to each first camera, it can determine a corresponding call policy for each first camera based on the camera type. Then, based on the call policy corresponding to each first camera and the current call status of the first camera, it can determine a second camera from the at least one first camera and determine a second access permission from the first access permission. The current call status of the first camera can be either idle or used. The idle state can indicate that the corresponding camera is not currently being called by other applications, and the used state can indicate that the corresponding camera is currently being called by other applications.

[0155] In some embodiments, if the first camera is a dedicated camera and its call status is in used state, it can be determined that the first camera cannot be authorized to be called by the first application, and the first camera cannot be used as the second camera. If the first camera is a dedicated camera and its call status is idle state, it can be determined that the first camera is the second camera, and the corresponding first access permission can be determined as the corresponding second access permission.

[0156] In some embodiments, if the first camera is a shared camera and the calling state of the first camera is in used state, it can be determined that the first camera is the second camera, and the data class permission in the corresponding first access right is used as the second access right (for example, if the first access right is full access right, the second access right is the data class permission. If the first access right is all permissions, preview permission (data class permission), and photo permission (data class permission) in the control class permission, the second access right is the data class permission "preview permission, photo permission" in the first access right). If the first camera is a shared camera and the calling state of the first camera is idle state, it can be determined that the first camera is the second camera, and the corresponding first access right is used as the corresponding second access right.

[0157] In some embodiments, if the first camera is a general camera, no matter whether the first camera has been called by other applications, the first camera can be determined to be the second camera, and the corresponding first access permission can be used as the corresponding second access permission.

[0158] In step S28, Figure 3 As shown, after step S27 is executed, the second access permission of the second camera is granted to the first application.

[0159] In one possible implementation, to grant the first application the second access permission for the second camera, the operation performed by the vehicle computer in step S28 may include: sending authorization information to the first application. The authorization information may indicate the second camera granted to the first application and which second access permissions for the second camera the first application has been granted. In some embodiments, if there are multiple second cameras, the first application may issue a camera selection prompt based on the received authorization information. The camera selection prompt prompts the user to select a target camera from the multiple second cameras that the first application needs to immediately access. In some embodiments, if there are multiple second cameras, the first application may determine the target camera by any of the following methods: selecting the target camera from the multiple second cameras based on a detected user action in response to the camera selection prompt. Alternatively, the target camera may be determined as a user-preferred camera from the multiple second cameras based on the first application's camera access history. Alternatively, the target camera may be determined as the camera from the multiple second cameras that was last accessed by the first application based on the first application's camera access history. In some embodiments, after determining the target camera, the first application may send a camera selection report to the vehicle computer, so that the vehicle computer can determine the selected target camera from the multiple second cameras based on the camera selection report and the first application can obtain real-time data collected by the target camera.

[0160] In one possible implementation, after the first application obtains the data collected in real time by the target camera, if the first application is an "application for taking photos and / or videos for the user" or "the corresponding second access permission includes preview permission" and needs to display the images collected by the target camera to the user, the first application can directly control the display screen of the vehicle computer to display the images collected in real time by the target camera generated based on the data collected in real time by the target camera. In some embodiments, while displaying the real-time image of the target camera on the display screen, the first application can also display a camera switching control and / or at least one operation control corresponding to the second access permission of the target camera (for example, a corresponding operation control can be set for each second access permission).

[0161] In one possible implementation, after the first application obtains the data collected in real time by the target camera or the second camera (if there is only one second camera, there is no need to select the target camera, the second camera is the target camera), if the first application does not need to display the image collected by the target camera to the user, it can directly control the display screen of the vehicle computer to display the camera switching control and / or at least one operation control corresponding to the second access permission of the target camera to the user, so that the user can switch the camera and / or control the target camera.

[0162] In some embodiments, when the first application detects a user triggering operation such as a click or slide on any operation control, it can generate a corresponding control instruction based on the second access permission corresponding to the triggered operation control (for example, if the second access permission corresponding to the triggered operation control is "photograph permission", the first application can generate a control instruction for taking a photo. If the second access permission corresponding to the triggered operation control is "zoom permission", the first application can generate a control instruction for zooming in or out of the target camera). In some embodiments, when the first application detects a user triggering operation such as a click or slide on a camera switching control, it can determine that the camera switching control is triggered. The first application can then switch the target camera to the next camera in the multiple second cameras according to the camera switching order (the camera switching order corresponding to the multiple second cameras can be arbitrary or arranged according to a set rule, and this application is not limited to this). For example, assuming that the second cameras that the first application can call are cameras C3, C5, and C6, and the camera switching order from front to back is C3, C5, and C6, the current target camera of the first application is camera C3. If the first application detects that the camera switching control is triggered, it switches the target camera to camera C5.

[0163] In some embodiments, the first application can directly send the control instruction to the camera or send the control instruction to the vehicle computer (so that the vehicle computer forwards the control instruction to the camera) when it determines that the second access permission corresponding to the control instruction is a control-type permission. In this way, the target camera can respond to the control instruction in a timely manner.

[0164] In one possible implementation, to grant the second access permission of the second camera to the first application, the operation performed by the vehicle computer in step S28 may further include: if there is only one second camera, the vehicle computer may directly identify the second camera as the target camera and, in accordance with the first application's second access permission for the target camera, send some or all of the data collected in real time by the target camera to the first application. Alternatively, the vehicle computer may send a call instruction to the target camera, the call instruction being used to instruct the first application to call the target camera and the first application to call the second access permission granted to the target camera. Thus, after the target camera receives the call instruction, the controller within the target camera may send some or all of the data collected in real time by the target camera to the first application in accordance with the first application's second access permission for the target camera.

[0165] In one possible implementation, to grant the second access permission of the second camera to the first application, the operation performed by the vehicle computer in step S28 may further include: if there are multiple second cameras, the vehicle computer may directly determine a target camera based on the camera selection report. Alternatively, if there are multiple second cameras, and if the vehicle computer does not receive a camera selection report, the vehicle computer may directly determine the target camera from the multiple second cameras. For example, the vehicle computer may determine the user's preferred camera from the multiple second cameras as the target camera based on the first application's camera call history. The vehicle computer may also determine the camera from the multiple second cameras that was last called by the first application as the target camera based on the first application's camera call history. And so on.

[0166] In one possible implementation, after step S28, if the target camera is a general-purpose camera, the target camera is currently called by multiple applications (including the first application), and the vehicle computer (or target camera) receives control instructions from different applications at the same time, a priority response control instruction can be selected from the multiple control instructions according to the response rules, and the target camera can be controlled to execute the priority response control instruction.

[0167] Figure 7 FIG. 1 shows a block diagram of the control device according to an embodiment of the present application. Figure 7 As shown, the architecture of a control device such as a vehicle computer includes an application, a camera service module, and a hardware physical module. When the vehicle computer executes steps S11 to S16 and steps S231 to S28, the application, camera service module, and hardware physical module are used to perform some or all of the operations in each step.

[0168] Application: can be used to implement interaction with the user and execute the above steps S31 to S34.

[0169] Camera Service Module: This module is used to set the call policy for each type of camera (perform step S16 above) and set the camera's access rights (control permissions and / or data permissions). It can also be used to execute the steps in "Permission Authorization" (steps S21-S24 above) and the steps in "Camera Call" (steps S25-S28 above).

[0170] Hardware physics module: used to set the camera type of each camera, define the camera application scenarios corresponding to dedicated cameras and shared cameras, and set the mapping relationship between application types and cameras. The hardware physics module can perform the above steps S11 to S15.

[0171] In one possible implementation, the application involved in the camera control method of the present application may be an application directly installed in the vehicle computer, or an application installed in a terminal device capable of remotely controlling the vehicle computer. The terminal device may include a mobile phone, a foldable electronic device, a tablet computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device, or at least one of a smart city device. The embodiments of the present application do not impose any special restrictions on the specific type of the terminal device.

[0172] An embodiment of the present application further provides a camera control device, comprising: a processor and a memory for storing processor-executable instructions; wherein the processor is configured to implement the above method when executing the instructions.

[0173] An embodiment of the present application further provides a non-volatile computer-readable storage medium having computer program instructions stored thereon, which implement the above method when the computer program instructions are executed by a processor.

[0174] An embodiment of the present application also provides a computer program product, including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code. When the computer-readable code runs in a processor of a terminal device, the processor in the terminal device executes the above method.

[0175] A computer-readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disc (DVD), a memory stick, a floppy disk, a mechanical encoding device, such as a punch card or a raised structure in a groove on which instructions are stored, and any suitable combination thereof.

[0176] The computer-readable program instructions or codes described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to be stored in the computer-readable storage medium in each computing / processing device.

[0177] The computer program instructions for performing the operations of the present application may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, by utilizing the state information of computer-readable program instructions to personalize an electronic circuit, such as a programmable logic circuit, a field-programmable gate array (FPGA), or a programmable logic array (PLA), the electronic circuit can execute the computer-readable program instructions, thereby implementing various aspects of the present application.

[0178] Various aspects of the present application are described herein with reference to flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0179] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processor of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0180] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0181] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, systems, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or instruction, and the part for the module, program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes can actually be performed substantially in parallel, and they can sometimes also be performed in the opposite order, depending on the function involved.

[0182] It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented by hardware that performs the corresponding function or action (such as a circuit or ASIC (Application Specific Integrated Circuit)), or can be implemented by a combination of hardware and software, such as firmware.

[0183] Although the present invention is described herein in conjunction with various embodiments, in the process of implementing the claimed invention, those skilled in the art can understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0184] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, systems, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or instruction, and the part for the module, program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes can actually be performed substantially in parallel, and they can sometimes also be performed in the opposite order, depending on the function involved.

[0185] It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart, can be implemented by hardware that performs the corresponding function or action (such as a circuit or ASIC (Application Specific Integrated Circuit)), or can be implemented by a combination of hardware and software, such as firmware.

[0186] Although the present invention is described herein in conjunction with various embodiments, in the process of implementing the claimed invention, those skilled in the art can understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0187] The embodiments of the present application have been described above. The above description is illustrative and not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, practical applications, or improvements to the technology in the market, or to enable other persons skilled in the art to understand the embodiments disclosed herein.

Claims

1. A camera control method, characterized in that: The method comprises: receiving a call request for applying to call a camera, and determining a first application corresponding to the call request; Obtaining an access permission record for the first application, where the access permission record is used to record at least one first camera that the corresponding application is allowed to call and a first access permission for the corresponding application to access the corresponding first camera, where the at least one first camera is part or all of the plurality of installed cameras; Determining, from the at least one first camera, a second camera that the first application can currently call and determining a second access permission for the second camera based on the current call state, the corresponding call policy, and the corresponding first access permission of each first camera; Granting the first application a second access permission for the second camera; The method further comprises: According to the camera-related parameters of each camera, the camera type of each camera is set and the camera application scenarios corresponding to the exclusive camera and the shared camera are set, where the camera type of each camera includes any one of an exclusive class, a shared class and a general class; Establishing a mapping relationship between the application type and the camera based on a matching result between the program application scenario corresponding to the application type and the camera application scenario; According to the usage characteristics of different camera types, set corresponding calling strategies for each camera type.

2. The method according to claim 1, characterized in that The method further comprises: receiving an access request for applying for camera access rights, and determining a second application corresponding to the access request; determining, from a plurality of installed cameras, based on an application type of the second application and a mapping relationship between each of the cameras and the application type, at least one third camera that the second application is allowed to access and a third access permission corresponding to each of the third cameras, where the third access permission includes a control permission and / or a data permission; The access permission record of the second application is updated according to the at least one third camera and the third access permission corresponding to each of the third cameras, where the second application includes the first application.

3. The method according to claim 2, characterized in that Updating the access permission record of the second application according to the at least one third camera and the third access permission corresponding to each of the third cameras includes: The third camera and the corresponding third access permission are respectively determined as the first camera and the corresponding first access permission, and are recorded in the access permission record of the second application.

4. The method according to claim 2, characterized in that Updating the access permission record of the second application according to the at least one third camera and the third access permission corresponding to each of the third cameras includes: sending the first information of each of the third cameras to the second application, so that the second application displays a first prompt based on the first information, wherein the first prompt is used to remind the user of the third cameras that the second application is allowed to access, remind the user to select a first camera designated by the user to be accessible by the second application from the third cameras, and / or remind the user to determine the first access permission for each first camera; receiving a user-specified permission report sent by the second application, the user-specified permission report being used to indicate first access permissions for a first camera designated by the user in the third camera and the first camera designated by the user, as determined by the second application based on the detected permission adjustment operation; The first camera and the corresponding first access permission indicated in the user-specified permission report are recorded in the access permission record of the second application.

5. The method according to claim 1, wherein According to the matching result between the program application scenario corresponding to the application type and the camera application scenario, a mapping relationship between the application type and the camera is established, including: If the program application scenario corresponding to the application type matches the camera application scenario corresponding to the shared camera, a mapping relationship between the shared camera and the application is established; and / or If the program application scenario corresponding to the application type matches the camera application scenario corresponding to the dedicated camera, a mapping relationship between the dedicated camera and the application is established; and / or If the program application scenario corresponding to the application type does not match any camera application scenario, a mapping relationship between the general camera and the application program is established.

6. The method according to claim 1, characterized in that The method further comprises: A mapping relationship between all the application types and the general cameras is established.

7. The method according to claim 1, characterized in that Determining, from the at least one first camera, a second camera that the first application can currently call and determining the second access permission for the second camera, based on the current call state, the corresponding call policy, and the corresponding first access permission of each first camera, includes at least one of the following operations: If the first cameras include an exclusive camera, determining an exclusive camera whose current call state is idle among the exclusive cameras as the second camera, and determining the corresponding first access permission as the corresponding second access permission; If the first cameras include a shared camera, determining a shared camera whose current call state is idle among the shared cameras as the second camera, and determining the corresponding first access permission as the corresponding second access permission; If the first cameras include a shared camera, determining a shared camera whose current call state is in a used state among the shared cameras as the second camera, and determining the data permission in the corresponding first access permission as the corresponding second access permission; If the first cameras include a general camera, the general camera is determined as the second camera, and the corresponding first access permission is determined as the corresponding second access permission.

8. The method according to claim 1, characterized in that Granting the first application a second access permission for the second camera, including: If there are multiple second cameras, determining a target camera among the multiple second cameras; Grant the first application a second access permission for the target camera.

9. The method according to claim 8, characterized in that If there are multiple second cameras, determining a target camera among the multiple second cameras includes any one of the following operations: receiving a camera selection report sent by the first application, and determining a camera indicated in the camera selection report among the plurality of second cameras as a target camera, wherein the camera selection report is used to indicate a selected target camera among the plurality of second cameras; determining a camera preferred by the user among the plurality of second cameras as a target camera according to the camera call history of the first application; According to the camera calling history of the first application, a camera among the plurality of second cameras that was last called by the first application is determined as a target camera.

10. The method according to claim 9, characterized in that Receiving a camera selection report sent by the first application, and determining a camera indicated in the camera selection report among the plurality of second cameras as a target camera, comprising: If there is more than one second camera, sending authorization information to the first application, where the authorization information is used to indicate the multiple second cameras and the second access permission corresponding to each second camera, so that the first application issues a camera selection prompt based on the authorization information, where the camera selection prompt is used to remind the user to select a target camera from the multiple second cameras; receiving a camera selection report sent by the first application, wherein the camera selection report is used to indicate a target camera selected from the plurality of second cameras, the target camera being determined by the first application based on a detected user operation in response to the camera selection prompt; The camera indicated in the camera selection report among the plurality of second cameras is determined as a target camera.

11. The method according to claim 1, characterized in that The method further comprises: If the second camera called by the first application is a general-purpose camera and multiple control instructions for controlling the second camera are received at the same time, determining a priority response control instruction from the multiple control instructions; Control the second camera to execute the priority response control instruction.

12. The method according to claim 11, characterized in that Determine the priority response control instruction from multiple control instructions, including: Determining a priority response control instruction from the multiple control instructions according to the priority of the application corresponding to each control instruction and / or the historical usage record of the application corresponding to each control instruction; The priority of the application is determined according to the application type of the application.

13. A data transmission device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to implement the method according to any one of claims 1 to 12 when executing the instructions.

14. A non-volatile computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the method according to any one of claims 1 to 12 is implemented.

15. A computer program product comprising a computer-readable code, or a non-volatile computer-readable storage medium carrying the computer-readable code, wherein when the computer-readable code is executed in an electronic device, a processor in the electronic device executes the method according to any one of claims 1 to 12.

Images