CN113489898B - Camera calling method, device, vehicle and storage medium - Google Patents
Camera calling method, device, vehicle and storage medium Download PDFInfo
- Publication number
- CN113489898B CN113489898B CN202110729098.4A CN202110729098A CN113489898B CN 113489898 B CN113489898 B CN 113489898B CN 202110729098 A CN202110729098 A CN 202110729098A CN 113489898 B CN113489898 B CN 113489898B
- Authority
- CN
- China
- Prior art keywords
- camera
- application program
- target
- application
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000004590 computer program Methods 0.000 claims description 8
- 230000006870 function Effects 0.000 abstract description 11
- 230000008569 process Effects 0.000 description 11
- 238000012546 transfer Methods 0.000 description 7
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 241000282836 Camelus dromedarius Species 0.000 description 3
- 230000000977 initiatory effect Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 241001234745 Camelina Species 0.000 description 1
- 235000016401 Camelina Nutrition 0.000 description 1
- 206010063385 Intellectualisation Diseases 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000002929 anti-fatigue Effects 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 239000011230 binding agent Substances 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011112 process operation Methods 0.000 description 1
- 239000004984 smart glass Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N23/00—Cameras or camera modules comprising electronic image sensors; Control thereof
- H04N23/60—Control of cameras or camera modules
- H04N23/64—Computer-aided capture of images, e.g. transfer from script file into camera, check of taken image quality, advice or proposal for image composition or decision on when to take image
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units
- G06F3/1423—Digital output to display device ; Cooperation and interconnection of the display device with other functional units controlling a plurality of local displays, e.g. CRT and flat panel display
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N23/00—Cameras or camera modules comprising electronic image sensors; Control thereof
- H04N23/60—Control of cameras or camera modules
- H04N23/63—Control of cameras or camera modules by using electronic viewfinders
- H04N23/631—Graphical user interfaces [GUI] specially adapted for controlling image capture or setting capture parameters
- H04N23/632—Graphical user interfaces [GUI] specially adapted for controlling image capture or setting capture parameters for displaying or modifying preview images prior to image capturing, e.g. variety of image resolutions or capturing parameters
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Abstract
The application discloses a camera calling method, a camera calling device, a vehicle and a computer readable storage medium. The calling method comprises the following steps: receiving a call request sent by an application program, wherein the call request comprises an application program identifier and a target camera identifier, corresponding camera services are determined according to the application program identifier, the camera services comprise a security camera service and an entertainment camera service, each application program identifier corresponds to one camera service, the camera services are called to determine a target camera according to the target camera identifier, each camera service corresponds to at least one camera, an application program is established through the security camera service to be connected with the target camera so that the application program can call the target camera, and/or an application program is established through the entertainment camera service to be connected with the target camera so that the application program can call the target camera. The calling method manages cameras with different functions through different camera services, and meets the requirement of simultaneously opening the cameras with different functions under different scenes.
Description
Technical Field
The present application relates to a vehicle technology, and in particular, to a camera calling method, a camera calling device, a vehicle, and a computer readable storage medium.
Background
With the development of vehicle intellectualization, more cameras are configured on the vehicle, and a user can control the cameras through a central control large screen configured on the vehicle so as to realize different application scenes. However, under the current application framework, only one application is allowed to call the camera at the same time, so that the requirement that the vehicle simultaneously opens cameras with different functions under different scenes is difficult to meet.
Disclosure of Invention
In view of this, the present application aims to solve, at least to some extent, one of the problems in the related art. To this end, an object of the present application is to provide a camera calling method, a camera calling device, a vehicle, and a computer-readable storage medium.
The calling method of the camera comprises the following steps:
receiving a call request sent by the application program, wherein the call request comprises an application program identifier and a target camera identifier;
determining corresponding camera services according to the application program identifiers, wherein the camera services comprise a security camera service and an entertainment camera service, and each application program identifier corresponds to one camera service;
invoking the camera services to determine a target camera according to the target camera identification, wherein each camera service corresponds to at least one camera;
establishing a connection between the application program and the target camera through the security camera service so that the application program calls the target camera; and/or
And establishing connection between the application program and the target camera through the entertainment camera service so that the application program calls the target camera.
In some embodiments, the vehicle further comprises a plurality of display screens, the vehicle further comprising a plurality of display screens, the establishing the application connection with the target camera such that the application invokes the target camera comprising:
and transmitting the data of the target camera to a display screen corresponding to the camera service for display.
In some embodiments, the vehicle further comprises a plurality of display screens, the establishing the application connection with the target camera such that the application invokes the target camera comprises:
and transmitting the data of the target camera to a display screen corresponding to the application program for display.
In some embodiments, the application includes an entertainment application and a security application, and the determining the corresponding camera service based on the application identification includes:
confirming the type of the application program according to the application program identification;
determining the entertainment camera service when the application is the entertainment application;
the secure camera service is determined when the application is a secure application.
In some implementations, the establishing the application to connect with the target camera through the secure camera service to cause the application to invoke the target camera includes:
determining the number of the security application programs according to the call request;
when the number of the security application programs is a plurality of, the security application program corresponding to the calling request received at first is taken as a target security application program;
establishing connection between the target security application program and the target camera;
the establishing, by the entertainment camera service, the application program to connect with the target camera so that the application program invokes the target camera includes:
determining the number of entertainment applications according to the call request;
when the number of the safety application programs is a plurality of, the entertainment application program corresponding to the calling request received at first is taken as a target entertainment application program;
and establishing connection between the target entertainment application program and the target camera.
In some implementations, invoking the camera service to determine the target camera from the target camera identification includes:
creating a virtual interface between the camera service and a corresponding camera;
determining a target virtual interface corresponding to the camera service according to the target camera identification;
and determining the target camera through the target virtual interface.
In some embodiments, the calling method further comprises:
receiving an operation instruction sent by an application program;
and controlling the target camera according to the operation instruction.
The calling device of the camera of the embodiment of the application comprises:
the receiving module is used for receiving a call request sent by the application program, wherein the call request comprises an application program identifier and a target camera identifier;
the determining module is used for determining corresponding camera services according to the application program identifiers, each application program identifier corresponds to one camera service, and the camera services comprise a security camera service and an entertainment camera service;
the starting module is used for calling the camera services to determine a target camera according to the target camera identification, and each camera service corresponds to at least one camera; and
and the calling module is used for establishing the connection between the application program and the target camera through the security camera service so as to enable the application program to call the target camera, and is also used for establishing the connection between the application program and the target camera through the entertainment camera service so as to enable the application program to call the target camera.
The vehicle of the embodiment of the application comprises a processor, a plurality of application programs and a plurality of cameras, wherein the processor is used for:
receiving a call request sent by the application program, wherein the call request comprises an application program identifier and a target camera identifier;
determining corresponding camera services according to the application program identifications, wherein each application program identification corresponds to one camera service, and the camera services comprise a security camera service and an entertainment camera service;
invoking the camera services to determine a target camera according to the target camera identification, wherein each camera service corresponds to at least one camera;
establishing a connection between the application program and the target camera through the security camera service so that the application program calls the target camera; and/or
And establishing connection between the application program and the target camera through the entertainment camera service so that the application program calls the target camera.
The computer readable storage medium according to an embodiment of the present application includes a computer program that, when executed by one or more processors, implements the method for invoking the camera according to any one of the above.
In the method, the device, the vehicle and the computer readable storage medium for calling the camera, the corresponding camera service process is started by receiving the calling request sent by the application program and determining according to the application program identification in the calling request, so that the target camera to be called is determined according to the target camera identification in the calling request through different camera service processes, and the connection between the target camera and the application program is established, thereby responding to the application program calling request. Therefore, the requirements that different programs open cameras with different functions at the same time are met.
Drawings
The foregoing and/or additional aspects and advantages of the application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
fig. 1 is a schematic flow chart of a method for invoking a camera according to some embodiments of the present application.
Fig. 2 is a block diagram of a camera recall device according to some embodiments of the present application.
FIG. 3 is a schematic block diagram of a vehicle according to some embodiments of the application.
FIG. 4 is a schematic diagram of one scenario of a calling method of some embodiments of the application.
Fig. 5-8 are flow diagrams of calling methods according to some embodiments of the application.
Description of main reference numerals:
the system comprises a vehicle 100, a calling device 10, a receiving module 11, a determining module 12, a starting module 13, a calling module 14, a control module 15, a camera 20, a display screen 40, a processor 30, a memory 50 and a computer program 52.
Detailed Description
Embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the drawings are exemplary only for explaining the present application and are not to be construed as limiting the present application.
With the development of the intelligence of vehicles, more and more vehicle-mounted cameras are configured on the vehicles. The vehicle-mounted cameras can be basically divided into two types, wherein one type is a safety function, such as a look-around camera, a DMS camera, a VPM camera and a DVR camera; one type is entertainment functions, such as in-car cameras. Meanwhile, more and more screens are arranged on the vehicle, and along with the gradual enrichment of the application ecology of the intelligent automobile, the scenes of using the camera in the vehicle are enriched.
Currently, android (Android) systems implement CAMERA management and call by using a camel framework, and under the camel framework, CAMERA hardware is managed through a CAMERA service (camel service) process, and an App end is responded to control a CAMERA request.
For example, when there are multiple cameras on the mobile phone device, one camera service manages all cameras in the bottom layer driving, and different cameras are distinguished by different IDs through the hardware abstraction layer (Hardware Abstraction Layer, HAL). The cameras are entertainment cameras except for special purposes such as face unlocking.
Different from the cell-phone, because the camera is numerous in the vehicle, its distribution position, the picture visual angle that presents are also obvious with the cell-phone camera difference, and in addition, the function and the factor of safety requirement of different cameras are also different, if look around the camera needs to ensure driving safety, and the requirement is higher to camera functional stability, and the priority is higher moreover. Under the CAMERA framework, only one application is allowed to call the CAMERA at the same time, so that the requirement that the vehicle simultaneously opens CAMERAs with different functions under different scenes is difficult to meet.
In view of this, referring to fig. 1, the present application provides a method for calling a camera, the method for calling includes the steps of:
s11: receiving a call request sent by an application program, wherein the call request comprises an application program identifier and a target camera identifier;
s12: determining corresponding camera services according to application program identifiers, wherein the camera services comprise a security camera service and an entertainment camera service, and each application program identifier corresponds to one camera service;
s13: invoking camera services to determine target cameras according to target camera identifications, wherein each camera service corresponds to at least one camera;
s14: establishing connection between an application program and a target camera through a security camera service so that the application program calls the target camera; and/or
S15: and establishing the connection between the application program and the target camera through the entertainment camera service so that the application program calls the target camera.
Referring further to fig. 2, an embodiment of the present application provides a camera recall device 10. The invoking device 10 comprises a receiving module 11, a determining module 12, an initiating module 13 and an invoking module 14.
Step S11 may be implemented by the receiving module 11, step S12 may be implemented by the determining module 12, step S13 may be implemented by the starting module 13, and steps S14 and S15 may be implemented by the calling module 14.
Alternatively, the receiving module 11 may be configured to receive a call request sent by an application program, where the call request includes an application program identifier and a target camera identifier. The determination module 12 may be configured to determine corresponding camera services based on application identifications, including a secure camera service and an entertainment camera service, one for each application identification. The starting module 13 may be configured to invoke camera services to determine the target cameras according to the target camera identifications, where each camera service corresponds to at least one camera. The invocation module 14 may cause the application to invoke the target camera in accordance with establishing the application to interface with the target camera through the secure camera service and the application to invoke the target camera in accordance with establishing the application to interface with the target camera through the entertainment camera service.
Referring to fig. 3, an embodiment of the present application provides a vehicle 100, and the calling method of the present application is applied to the vehicle 100. The vehicle 100 includes a plurality of cameras 20, a plurality of applications, a plurality of ECUs, a processor 30, and a memory 50. The memory 50 has stored therein a computer program 52.
The processor 30 may be configured to receive a call request sent by an application program, where the call request includes an application program identifier and a target camera identifier, and determine a corresponding camera service according to the application program identifier, where each application program identifier corresponds to one camera service, and the camera service includes a secure camera service and an entertainment camera service. The processor 30 may be configured to invoke camera services to determine a target camera from a target camera identification, each camera service corresponding to at least one camera 20. Processor 30 may also cause the application to invoke the target camera in accordance with establishing the application's connection with the target camera through the secure camera service. And establishing a connection between the application program and the target camera through the entertainment camera service so that the application program calls the target camera.
In the calling method, the calling device 10 and the vehicle 100 of the camera 20, the corresponding camera service process is started by receiving the calling request sent by the application program and determining according to the application program identification in the calling request, so that the target camera to be called is determined according to the target camera identification in the calling request through different camera service processes, and the target camera is established to be connected with the application program, thereby responding to the application program calling request. In this way, the requirement that different application programs open different functional cameras 20 at the same time is met.
The vehicle 100 may include a vehicle, a flying car, a high speed train, or the like. The present application will be described with reference to a vehicle.
Please refer to fig. 4, it should be noted that the processor 30 may be a central control processor, and the cameras 20 may be classified according to different application scenarios, and in the present application, the cameras 20 may be classified into two types, namely a functional camera and an entertainment camera. The functional camera is used for assisting driving, for example, is used for identifying a mark line of a driving lane, providing surrounding driving environment information and providing reversing images. Camera 20 may include, but is not limited to, a look-around camera, an anti-fatigue pre-warning (Driver Monitor Status, DMS) camera, a panoramic (VPM) camera, or a DVR camera, among others. Entertainment cameras are used to provide functions other than driving assistance. For example, providing live video, video conferencing, enabling face unlocking, etc., the entertainment camera may be an in-car camera, a roof camera, etc., such as a camera on a co-pilot screen.
The plurality of applications are classified into entertainment applications and security applications according to an application scenario of each application. Entertainment applications may include applications including social chat classes, audiovisual classes, gaming classes, and the like. The security application program can be application software such as reversing images, journey records and the like.
The application is not limited to the application carried by the vehicle 100, but may be, for example, an application of an electronic device when the vehicle 100 is in communication with a mobile phone, a tablet, a smart wearable device (smart watch, smart bracelet, smart helmet, smart glasses, etc.), a virtual reality device, or other electronic device of an augmented reality device. The present application is illustrated with an application onboard the vehicle 100.
Camera Service (Camera Service) is an independent process in a Camera Framework for managing cameras, and is used as a Service end for processing a cross-process request from a client in the Camera Framework, and performing certain operations internally, and then sending the request to a Camera Provider as a Service end again as a client, wherein the whole process involves two cross-process operations, the former is realized through an AIDL mechanism, and the latter is realized through an HIDL mechanism.
The camera service comprises a security camera service and an entertainment camera service, wherein the security camera service is used for managing a security camera. Entertainment camera services are used to manage entertainment cameras. The security camera service and the entertainment camera service may run simultaneously, and only one entertainment application call request is executed while the entertainment camera service is running, and only one security application is executed while the security camera service is running.
The application identification is used to characterize the application. The application identity comprises an identity code (Identity document, ID) of the application, and the camera identity may be a camera ID already present in the application. It will be appreciated that the target camera identifier is the ID of the target camera.
The application program identification and the camera service form a mapping relation, the application program identification of the security application program corresponds to the security camera service, and the application program identification of the entertainment application program corresponds to the entertainment camera service. Upon receiving a call request from an application, a secure camera service and/or an entertainment camera service may be determined and started based on the application identification.
Further, when the number of the call requests is one, the corresponding camera service can be determined and started directly according to the application program identifier of the call request. For example, the application program is an entertainment application program, and after receiving a call request of the entertainment application program, the entertainment camera service process can respond according to an application program identifier of the entertainment application program, and for example, the application program is a security application program, and after receiving a call request of the security application program, the entertainment camera service process can respond according to an application program identifier of the security application program.
Further, the camera service directly establishes the connection between the application program and the target camera, so that the control of the application program on the target camera is realized.
If the call request includes a plurality of call requests, the number of secure applications and the number of entertainment applications are determined by the call request. And when the number of the security application programs is a plurality of, taking the security application program corresponding to the finally received calling request as a target security application program, and establishing connection between the target security application program and the target camera. And when the number of entertainment application programs is a plurality of, taking the entertainment application program corresponding to the finally received calling request as a target entertainment application program;
and establishing connection between the target entertainment application program and the target camera.
For example, processor 30 receives call requests for five applications A, B, C, E and F, where A, B, C is the entertainment application and C is the last call request sent in A, B, C, E and F are the security applications and F is the last call request sent in E and F. Then after the entertainment camera service and the security camera service are turned on, a connection of the C-target entertainment camera and a connection of the F-target security camera are established.
In this way, the cameras 20 are distinguished by functional division. On one hand, the method can avoid debugging and compatibility of cameras 20 with different parameters, and conflict management and maintenance on different service implementations, avoid controlling mutually exclusive service logic of the entertainment camera and the safety camera, and on the other hand, the method can improve the stability of the high-function camera service to a certain extent and improve driving safety.
The calling method can be realized by modifying the Camera framework in the android system. The following describes modification contents in the Camera frame.
As will be appreciated by those skilled in the relevant art, the Camera framework includes a Camera Java layer interface, a Java Native layer interface (JNI), a Native layer interface, and a HAL layer interface. The Native layer interface consists of a camera local framework (client end) and a camera Service.
The application realizes the calling method mainly by modifying the camera Java layer interface, java local calling interface (JNI) and Native layer interface.
The class provided by the Camera Java layer to the application layer interface is android.hardware.Camera, and the corresponding source code file is: camera, java, some of these methods are implemented by JNI invoking code in the native framework.
Java native call interface (JNI), code path: the frame works/base/core/jni/android_hardware_camera_cpp is compiled into libandroid_run_so, which does not perform any processing and is equivalent to an intermediate station, and goes to the next-layer camera local framework (client end) to be implemented.
code path of camera local framework (client side): the framework/av/camera/camera.cpp is compiled into library libcata_client.so, and can be also understood as a transfer station to communicate with the camera local service through a binder mechanism call.
CameraService, code path: the framework/av/services/camera/libcataservice/camera service.cpp is compiled into libcataservice.so, and a specific camera is realized by the framework and the codec library which are combined with the related hardware driving framework of the bottom layer.
camera HAL hardware abstraction layer, code path: frames/av/services/camera/libcatarService +.
device1/Camera Hardwareinterface.h, and based on the HAL completed by the interface, camera data transmission and function control are realized.
Specifically, modification of the camera Java layer interface:
the getnumberofcamera () and the nattice_getcamelnfo (int camelid, camelina) in camera. Native getNumberOfCameras (String packageName) is newly added to getnumberofcam (). The gnaticegete camerainfo (int cameraId, camerainfocarbainfo) is modified to getCameraInfo (String packageName, intcameraId, camerainfocarbainfo), and at the same time, the native_getcamerainfo () is called in getCameraInfo (int cameraId, camerainfocarbainfo).
Modification of Java native Call interface (JNI):
the android_hardware_camera_getnumberofcamera (JNIEnv, jobjectthiz) and android_hardware_camera_getcamera info (JNIEnv, jobjectthiz) in the android_hardware_camera. Thus, android_hardware_camera_getnumberofcamera (JNIEnv, jobjectthiz, jstringclientPackageName) is passed into Camera::: getnumberofcamera (const String16& clientPackageName), and android_hardware_camera_getcamera info (JNIEnv, jobjectthiz, jstringclientPackageName) is passed into Camera::: getcamera info (const String16& clientPackageName, intcamera id, struct hardware:: camera info).
Modification of Native layer interface:
(1) The status_t Camera in Camera.cpp is modified by the process of connecting legacy (int Camera Id, int halVersion, const String16& clients PackageName, intclients UId, sp < Camera > & Camera).
(2) The template < typenameTCam, typenameTCamTraits > sp < TCam > CameraBase < TCam, TCamTraits > in CameraBase cpp is modified by connect (int Camera Id, const String16& clientPackageName, intclientUid, int clientPid).
(3) In the modified CameraBase.cpp, template < typenameTCam, typenameTCamTraits > int CameraBase < TCam, TCamTraits >:getNumberOfCameras (), the specific modifications are: template < typenameTCam, typenameTCamTraits > int CameraBase < TCam, TCamTraits >: getNumberOfCameras (const String16& clientPackageName).
(4) The template < typenameTCam, typenameTCamTraits > status_tcamerapase < TCam, TCamTraits > in amerapase cpp is modified by getamerainfo (int amerapid, structhardware:: amerainfo) as: template < typenameTCam, typenameTCamTraits > status_tCameraBase < TCam, TCamTraits >: getCameraInfo (const String16& friendly PackageName, int Camera Id, structhardware:: cameraInfo).
Referring to fig. 5, in some embodiments, the vehicle 100 further includes a plurality of display screens 40, and step S14 includes the sub-steps of:
s141: and transmitting the data of the target camera to a display screen corresponding to the security camera service for display.
Step S15 includes the sub-steps of:
s151: and transmitting the data of the target camera to a display screen corresponding to the entertainment camera service for display.
In some embodiments, the substep S141 and the substep S151 may be implemented by the calling module 14, or the calling module 14 may be configured to transfer the data of the target camera to the display screen corresponding to the security camera service for display, and transfer the data of the target camera to the display screen corresponding to the entertainment camera service for display.
In some embodiments, the processor 30 is configured to transfer the data of the target camera to a display screen display corresponding to the security camera service, and the processor 30 is further configured to transfer the data of the target camera to a display screen display corresponding to the entertainment camera service.
The vehicle 100 includes a display screen 40 of a graphical user interface display, which display screen 40 may include, but is not limited to, a meter screen, a center control screen, a co-driver screen, a rear seat display screen, and other area display screens 40 of the vehicle 100, and the like.
Further, the security camera service and the entertainment camera service correspond to different display screens 40, respectively. The safety camera service can correspond to the instrument screen, the central control screen and the co-driver screen, and the entertainment camera service can correspond to the co-driver screen, the rear seat display screen and the like. Thus, the data of the safety camera is only displayed on the instrument screen or the central control screen, and the data of the entertainment camera is only displayed on the copilot screen or the rear seat screen.
Each display 40 may display a plurality of applications, and a user may control the applications to perform corresponding operations by clicking on the applications in the display 40.
In this embodiment, each display 40 may display the same class of applications, for example, the central control may display only security applications. The co-driver screen displays only entertainment applications. Different classes of applications may also be displayed, for example, a center screen may display both security applications and entertainment applications.
Referring to fig. 6, in some embodiments, step S14 includes the sub-steps of:
s142: and transmitting the data of the target camera to a display screen corresponding to the application program for display.
In some embodiments, the substep S141 may be implemented by the calling module 14, or the calling module 14 may be configured to transfer the data of the target camera to a display screen corresponding to the application program for display.
In some embodiments, the processor 30 is configured to transfer data of the target camera to a display screen display corresponding to the camera service.
In this embodiment, the display 40 may display only the same class of applications, for example, the central control may display only the security applications. The co-driver screen displays only entertainment applications. In this way, when the user clicks on the application program to call the camera, the camera can be displayed on the display 40 where the application program is located.
Referring to fig. 7, in some embodiments, step S13 includes the sub-steps of:
s131: creating a virtual interface between the camera service and a corresponding camera;
s132: determining a target virtual interface corresponding to the camera service according to the target camera identification;
s133: and determining the target camera through the target virtual interface.
In some embodiments, sub-steps 131, S132 and sub-step S133 may be performed by the initiation module 13, or the initiation module 13 may be used to create a virtual interface of the camera service with the corresponding camera. The starting module 13 may be configured to determine a target virtual interface corresponding to the camera service according to the target camera identifier. The activation module 13 may also be used to determine a target camera through a target virtual interface.
In some embodiments, the processor 30 is used to create a virtual interface of the camera service with the corresponding camera. The processor 30 may also be configured to determine a target virtual interface corresponding to the camera service based on the target camera identification and determine a target camera through the target virtual interface.
Therefore, the target camera is determined according to the target camera identification, and the application program can call the target camera.
Referring to fig. 8, in some embodiments, the calling method further comprises the steps of:
s16: receiving an operation instruction sent by an application program;
s17: and controlling the target camera according to the operation instruction.
Referring further to fig. 2, in some embodiments, the calling device 10 further includes a control module 15, and step S16 may be implemented by the receiving module 11. Step S17 may be implemented by the control module 15.
In other words, the receiving module 11 is further configured to receive an operation instruction sent by the application program, and the control module 15 may be configured to control the target camera according to the operation instruction.
In some embodiments, the processor 30 may be configured to receive an operation instruction sent by the application program, and the processor 30 may be further configured to control the target camera according to the operation instruction.
Specifically, after the application program establishes connection with the target camera, the application program may send an operation instruction to the corresponding camera service, and the camera service may control the target camera to execute the corresponding operation according to the operation instruction after receiving the operation instruction. The operation instruction may be to control the shooting angle of the target camera, set shooting parameters of the target camera, and the like.
Embodiments of the present application also provide one or more non-transitory computer-readable storage media storing a computer program that, when executed by one or more processors, implements the method of invoking a camera of any of the above embodiments.
Those skilled in the art will appreciate that implementing all or part of the processes in the methods of the embodiments described above may be accomplished by computer programs to instruct related software. The program may be stored in a non-transitory computer readable storage medium, which when executed may include the flow of embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), etc.
The foregoing examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.
Claims (9)
1. A camera recall method for a vehicle, the vehicle comprising a plurality of applications and a plurality of cameras, the recall method comprising:
receiving a call request sent by the application program, wherein the call request comprises an application program identifier and a target camera identifier;
determining corresponding camera services according to the application program identifiers, wherein the camera services comprise a security camera service and an entertainment camera service, and each application program identifier corresponds to one camera service;
invoking the camera services to determine a target camera according to the target camera identification, wherein each camera service corresponds to at least one camera;
establishing a connection between the application program and the target camera through the security camera service so that the application program calls the target camera; and/or
Establishing a connection between the application program and the target camera through the entertainment camera service so that the application program calls the target camera;
the application programs comprise entertainment application programs and security application programs, and the determining the corresponding camera service according to the application program identification comprises the following steps: confirming the type of the application program according to the application program identification; determining the entertainment camera service when the application is the entertainment application; the secure camera service is determined when the application is a secure application.
2. The invocation method of claim 1, wherein the vehicle further comprises a plurality of display screens, the establishing the application connection with the target camera through the secure camera service to cause the application to invoke the target camera comprising:
transmitting the data of the target camera to the display screen corresponding to the security camera service for display;
the establishing, by the entertainment camera service, the application program to connect with the target camera so that the application program invokes the target camera includes:
and transmitting the data of the target camera to the display screen corresponding to the entertainment camera service for display.
3. The invocation method of claim 1, wherein the vehicle further comprises a plurality of display screens, the establishing the application connection with the target camera through the secure camera service to cause the application to invoke the target camera comprising:
and transmitting the data of the target camera to the display screen corresponding to the application program for display.
4. The invocation method of claim 1, wherein the establishing the application connection with the target camera through the secure camera service to cause the application to invoke the target camera comprises:
determining the number of the security application programs according to the call request;
when the number of the security application programs is a plurality of, the security application program corresponding to the calling request received at first is taken as a target security application program;
establishing connection between the target security application program and the target camera;
the establishing, by the entertainment camera service, the application program to connect with the target camera so that the application program invokes the target camera includes:
determining the number of entertainment applications according to the call request;
when the number of the safety application programs is a plurality of, the entertainment application program corresponding to the calling request received at first is taken as a target entertainment application program;
and establishing connection between the target entertainment application program and the target camera.
5. The invocation method of claim 1, wherein the invoking the camera service to determine a target camera from the target camera identification comprises:
creating a virtual interface between the camera service and the corresponding camera;
determining a target virtual interface corresponding to the camera service according to the target camera identification;
and determining a target camera through the target virtual interface.
6. The calling method of claim 1, wherein the calling method further comprises:
receiving an operation instruction sent by the application program;
and controlling the target camera according to the operation instruction.
7. A camera recall device for a vehicle, the vehicle comprising a plurality of applications and a plurality of cameras, the recall device comprising:
the receiving module is used for receiving a call request sent by the application program, wherein the call request comprises an application program identifier and a target camera identifier;
the camera service comprises a security camera service and an entertainment camera service, and each application program identifier corresponds to one camera service;
the starting module is used for calling the camera services to determine a target camera according to the target camera identification, and each camera service corresponds to at least one camera; and
the calling module is used for establishing connection between the application program and the target camera through the security camera service so as to enable the application program to call the target camera, and is also used for establishing connection between the application program and the target camera through the entertainment camera service so as to enable the application program to call the target camera;
the application programs comprise entertainment application programs and security application programs, and the determining the corresponding camera service according to the application program identification comprises the following steps: confirming the type of the application program according to the application program identification; determining the entertainment camera service when the application is the entertainment application; the secure camera service is determined when the application is a secure application.
8. A vehicle comprising a memory and a processor, the memory having stored therein a computer program which, when executed by the processor, implements the invoking method according to any of claims 1-6.
9. A non-transitory computer readable storage medium containing a computer program, characterized in that the method of invoking the camera of any of claims 1-6 is implemented when the computer program is executed by one or more processors.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110729098.4A CN113489898B (en) | 2021-06-29 | 2021-06-29 | Camera calling method, device, vehicle and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110729098.4A CN113489898B (en) | 2021-06-29 | 2021-06-29 | Camera calling method, device, vehicle and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113489898A CN113489898A (en) | 2021-10-08 |
| CN113489898B true CN113489898B (en) | 2023-10-31 |
Family
ID=77937192
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110729098.4A Active CN113489898B (en) | 2021-06-29 | 2021-06-29 | Camera calling method, device, vehicle and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113489898B (en) |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102883139A (en) * | 2011-07-12 | 2013-01-16 | 北京中星微电子有限公司 | Camera application system and method |
| CN105955779A (en) * | 2016-05-03 | 2016-09-21 | 深圳Tcl数字技术有限公司 | Process closing method and device |
| CN106101526A (en) * | 2016-06-01 | 2016-11-09 | 北京金山安全软件有限公司 | Screen recording method and device |
| CN106791356A (en) * | 2016-11-10 | 2017-05-31 | 北京智能管家科技有限公司 | For the method and device of camera data distribution |
| CN107544298A (en) * | 2017-06-27 | 2018-01-05 | 新华三云计算技术有限公司 | A kind of camera call method and device |
| CN108848317A (en) * | 2018-09-25 | 2018-11-20 | Oppo（重庆）智能科技有限公司 | Camera control method and Related product |
| CN109144728A (en) * | 2018-08-22 | 2019-01-04 | Oppo广东移动通信有限公司 | The occupancy control method and device of camera applications |
| CN109729270A (en) * | 2018-12-30 | 2019-05-07 | 联想(北京)有限公司 | A kind of control method, device and electronic equipment |
| CN109976918A (en) * | 2019-04-09 | 2019-07-05 | 努比亚技术有限公司 | Camera Resource allocation and smoothing method, mobile terminal and computer readable storage medium |
| CN110166564A (en) * | 2019-05-28 | 2019-08-23 | 北京小米移动软件有限公司 | Information communicating method, terminal and storage medium |
| CN110386064A (en) * | 2018-04-20 | 2019-10-29 | 比亚迪股份有限公司 | Control system, method, mobile unit and the automobile of vehicle-mounted camera |
| JP2019193145A (en) * | 2018-04-26 | 2019-10-31 | キヤノン株式会社 | Information processing device |
| CN110401766A (en) * | 2019-05-22 | 2019-11-01 | 华为技术有限公司 | A kind of image pickup method and terminal |
| CN110727382A (en) * | 2019-09-06 | 2020-01-24 | 华为技术有限公司 | Split-screen display method and electronic equipment |
| CN112181333A (en) * | 2015-02-02 | 2021-01-05 | 三星电子株式会社 | Multi-display based device |
| CN112363767A (en) * | 2020-11-11 | 2021-02-12 | 广州小鹏汽车科技有限公司 | Vehicle-mounted camera calling method and device |
| CN112671976A (en) * | 2019-09-30 | 2021-04-16 | 华为技术有限公司 | Control method of electronic equipment and electronic equipment |
| CN112689086A (en) * | 2020-12-10 | 2021-04-20 | 联想(北京)有限公司 | Information determination method, electronic equipment and computer readable storage medium |
| CN112995562A (en) * | 2019-12-13 | 2021-06-18 | 南京酷派软件技术有限公司 | Camera calling method and device, storage medium and terminal |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8284267B2 (en) * | 2009-03-11 | 2012-10-09 | O2Micro Inc. | Virtual camera for sharing a physical camera |
| CN106790490B (en) * | 2016-12-14 | 2019-10-15 | 北京小米移动软件有限公司 | The method and device conversed based on intelligent camera |
-
2021
- 2021-06-29 CN CN202110729098.4A patent/CN113489898B/en active Active
Patent Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102883139A (en) * | 2011-07-12 | 2013-01-16 | 北京中星微电子有限公司 | Camera application system and method |
| CN112181333A (en) * | 2015-02-02 | 2021-01-05 | 三星电子株式会社 | Multi-display based device |
| CN105955779A (en) * | 2016-05-03 | 2016-09-21 | 深圳Tcl数字技术有限公司 | Process closing method and device |
| CN106101526A (en) * | 2016-06-01 | 2016-11-09 | 北京金山安全软件有限公司 | Screen recording method and device |
| CN106791356A (en) * | 2016-11-10 | 2017-05-31 | 北京智能管家科技有限公司 | For the method and device of camera data distribution |
| CN107544298A (en) * | 2017-06-27 | 2018-01-05 | 新华三云计算技术有限公司 | A kind of camera call method and device |
| CN110386064A (en) * | 2018-04-20 | 2019-10-29 | 比亚迪股份有限公司 | Control system, method, mobile unit and the automobile of vehicle-mounted camera |
| JP2019193145A (en) * | 2018-04-26 | 2019-10-31 | キヤノン株式会社 | Information processing device |
| CN109144728A (en) * | 2018-08-22 | 2019-01-04 | Oppo广东移动通信有限公司 | The occupancy control method and device of camera applications |
| CN108848317A (en) * | 2018-09-25 | 2018-11-20 | Oppo（重庆）智能科技有限公司 | Camera control method and Related product |
| CN109729270A (en) * | 2018-12-30 | 2019-05-07 | 联想(北京)有限公司 | A kind of control method, device and electronic equipment |
| CN109976918A (en) * | 2019-04-09 | 2019-07-05 | 努比亚技术有限公司 | Camera Resource allocation and smoothing method, mobile terminal and computer readable storage medium |
| CN110401766A (en) * | 2019-05-22 | 2019-11-01 | 华为技术有限公司 | A kind of image pickup method and terminal |
| CN110166564A (en) * | 2019-05-28 | 2019-08-23 | 北京小米移动软件有限公司 | Information communicating method, terminal and storage medium |
| CN110727382A (en) * | 2019-09-06 | 2020-01-24 | 华为技术有限公司 | Split-screen display method and electronic equipment |
| CN112671976A (en) * | 2019-09-30 | 2021-04-16 | 华为技术有限公司 | Control method of electronic equipment and electronic equipment |
| CN112995562A (en) * | 2019-12-13 | 2021-06-18 | 南京酷派软件技术有限公司 | Camera calling method and device, storage medium and terminal |
| CN112363767A (en) * | 2020-11-11 | 2021-02-12 | 广州小鹏汽车科技有限公司 | Vehicle-mounted camera calling method and device |
| CN112689086A (en) * | 2020-12-10 | 2021-04-20 | 联想(北京)有限公司 | Information determination method, electronic equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113489898A (en) | 2021-10-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111634188A (en) | Method and device for projecting screen | |
| CN110347464B (en) | User interface rendering method, device and medium of application program and electronic equipment | |
| WO2020030071A1 (en) | Shared bike unlocking method | |
| CN110233998A (en) | A kind of method of transmitting video data, device, equipment and storage medium | |
| CN109995861B (en) | Relay communication method and system for vehicle-mounted system application and vehicle-mounted peripheral device | |
| CN107291319A (en) | A kind of window display method, information interacting method and system | |
| KR20170047918A (en) | Apparatus and method for controlling mobile device engaging with vehicle | |
| US20170034551A1 (en) | Dynamic screen replication and real-time display rendering based on media-application characteristics | |
| CN114780049A (en) | Screen projection display method and device, electronic equipment and storage medium | |
| CN113489898B (en) | Camera calling method, device, vehicle and storage medium | |
| CN104285207A (en) | Method, mobile device and infotainment system for projecting user interface onto screen | |
| CN113961156A (en) | Multi-screen display method, device and system, electronic equipment and computer medium | |
| CN116088784A (en) | Image screen projection method, device, electronic equipment, chip, storage medium and vehicle | |
| WO2023020207A1 (en) | Vehicle location sharing method, system, apparatus and device, medium, and program product | |
| CN114077368B (en) | Vehicle-mounted applet running method and device, computer equipment and storage medium | |
| CN114461158B (en) | Application screen projection method and device, vehicle-mounted terminal and readable storage medium | |
| CN112543431A (en) | Account synchronization method, medium and server | |
| CN114363654B (en) | Video push method, device, terminal equipment and storage medium | |
| EP4106357A1 (en) | Method for logging into on-board computer system and related device | |
| CN109669898B (en) | System and method for aggregating vehicle data from infotainment application accessories | |
| CN116069199A (en) | Interface interaction method, electronic device, medium and program product | |
| CN113504870A (en) | Hypervisor intelligent cockpit input method sharing system and method | |
| CN112929723A (en) | Control method and device for automobile theater and storage medium | |
| CN111741444A (en) | Display method, device, equipment and storage medium | |
| CN110745084A (en) | Multimedia system middleware design method for intelligent automobile |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |