CN113489898A - Camera calling method and device, vehicle and storage medium - Google Patents
Camera calling method and device, vehicle and storage medium Download PDFInfo
- Publication number
- CN113489898A CN113489898A CN202110729098.4A CN202110729098A CN113489898A CN 113489898 A CN113489898 A CN 113489898A CN 202110729098 A CN202110729098 A CN 202110729098A CN 113489898 A CN113489898 A CN 113489898A
- Authority
- CN
- China
- Prior art keywords
- camera
- target
- application program
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 238000004590 computer program Methods 0.000 claims description 11
- 230000006870 function Effects 0.000 abstract description 13
- 230000008569 process Effects 0.000 description 10
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 3
- 206010063385 Intellectualisation Diseases 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 1
- 239000011230 binding agent Substances 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- 230000000977 initiatory effect Effects 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
- 238000012546 transfer Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
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 method and a device for calling a camera, a vehicle and a computer-readable storage medium. The calling method comprises the following steps: receiving a calling request sent by an application program, wherein the calling request comprises an application program identifier and a target camera identifier, determining corresponding camera services 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, calling the camera services to determine a target camera according to the target camera identifier, each camera service corresponds to at least one camera, establishing 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 connection between the application program and the target camera through the entertainment camera service so that the application program calls the target camera. According to the calling method, the cameras with different functions are managed through different camera services, and the requirement that the cameras with different functions are opened at the same time in different scenes is met.
Description
Technical Field
The present application relates to vehicle technologies, and in particular, to a method and an apparatus for invoking a camera, a vehicle, and a computer-readable storage medium.
Background
With the development of vehicle intellectualization, more and 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 that different application scenes are realized. However, in the current application framework, only one application is allowed to call the camera at the same time, and it is difficult to meet the requirement that the vehicle simultaneously opens the cameras with different functions in different scenes.
Disclosure of Invention
In view of the above, the present application is directed to solving, at least to some extent, one of the problems in the related art. To this end, the present application aims to provide a camera calling method, a camera calling device, a vehicle and a computer readable storage medium.
The method for calling the camera comprises the following steps:
receiving a calling request sent by the application program, wherein the calling request comprises an application program identifier and a target camera identifier;
determining corresponding camera services according to the application program identifications, wherein the camera services comprise a security camera service and an entertainment camera service, and each application program identification corresponds to one camera service;
calling the camera services to determine target cameras according to the target camera identifications, wherein each camera service corresponds to at least one camera;
establishing 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, by the entertainment camera service, the application program in connection with the target camera to cause the application program to invoke the target camera.
In some embodiments, the vehicle further comprises a plurality of display screens, and establishing the application in 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 camera service for display.
In some embodiments, the vehicle further comprises a plurality of display screens, and establishing the application in connection with the target camera to cause the application to invoke 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 applications include 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;
determining the secure camera service when the application is a secure application.
In some embodiments, the establishing, by the secure camera service, the application connection with the target camera to cause the application to invoke the target camera comprises:
determining the number of the safety application programs according to the calling request;
when the number of the safe application programs is multiple, taking the safe application program corresponding to the calling request received firstly as a target safe application program;
establishing connection between the target security application program and the target camera;
the establishing, by the entertainment camera service, the application program in connection with the target camera to cause the application program to invoke the target camera comprises:
determining the number of entertainment applications according to the call request;
when the number of the safety application programs is multiple, taking the entertainment application program corresponding to the calling request received firstly as a target entertainment application program;
establishing a connection between the target entertainment application and the target camera.
In some embodiments, invoking the camera service to determine the target camera from the target camera identification comprises:
creating a virtual interface of a camera service and a 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.
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 calling request sent by the application program, wherein the calling request comprises an application program identifier and a target camera identifier;
a determining module, configured to determine corresponding camera services according to the application identifiers, where each application identifier corresponds to one of the camera services, and the camera services include 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
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 the calling module 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 calling request sent by the application program, wherein the calling 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;
calling the camera services to determine target cameras according to the target camera identifications, wherein each camera service corresponds to at least one camera;
establishing 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, by the entertainment camera service, the application program in connection with the target camera to cause the application program to invoke the target camera.
The computer-readable storage medium of the embodiment of the present application includes a computer program, and when the computer program is executed by one or more processors, the computer program implements the method for invoking the camera according to any one of the above items.
In the camera calling method, the camera calling device, the vehicle and the computer-readable storage medium according to the embodiments of the present application, by receiving a calling request sent by an application program and determining a corresponding camera service process according to an application program identifier in the calling request, a target camera to be called is determined according to a target camera identifier in the calling request through different camera service processes, and a target camera is established to be connected with the application program, so as to respond to the application program calling request. Therefore, the requirements that different programs open the cameras with different functions at the same time are met.
Drawings
The foregoing and/or additional aspects and advantages of the present application will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
fig. 1 is a schematic flowchart of a method for calling a camera according to some embodiments of the present disclosure.
Fig. 2 is a block diagram of a calling device of a camera according to some embodiments of the present disclosure.
FIG. 3 is a block schematic diagram of a vehicle according to certain embodiments of the present application.
FIG. 4 is a schematic diagram of a scenario of a calling method according to some embodiments of the present application.
Fig. 5-8 are flow diagrams of a calling method according to some embodiments of the present application.
Description of the main element symbols:
the vehicle 100, the calling device 10, the receiving module 11, the determining module 12, the starting module 13, the calling module 14, the control module 15, the camera 20, the display 40, the processor 30, the memory 50, and the computer program 52.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative and are only for the purpose of explaining the present application and are not to be construed as limiting the present application.
With the development of the intellectualization of the vehicle, more and more vehicle-mounted cameras are arranged on the vehicle. The vehicle-mounted camera 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 is entertainment, such as an in-vehicle camera. Meanwhile, the number of screens on the vehicle is more and more, and with the gradual enrichment of the application ecology of the intelligent automobile, the scenes using the camera in the vehicle are also enriched accordingly.
Currently, an Android (Android) system manages and calls a CAMERA by using a CAMERA framework, manages CAMERA hardware by using a CAMERA service (CAMERA service) process under the CAMERA framework, and responds to an App end to control a CAMERA request.
For example, when there are multiple cameras on a mobile phone device, one camera service manages all the cameras during the bottom-Layer driving, and a Hardware Abstraction Layer (HAL) distinguishes different cameras by different IDs. The camera is an entertainment camera except for the camera which has special purposes such as face unlocking.
Different from a mobile phone, due to the fact that the cameras are numerous in the vehicle, the distribution positions and the displayed picture visual angles of the cameras are obvious in difference with those of the mobile phone camera, in addition, the functions and safety factor requirements of different cameras are different, driving safety is guaranteed if the cameras are looked around, requirements for the stability of the functions of the cameras are higher, and the priority is higher. And under the CAMERA framework, only one application is allowed to call the CAMERA at the same time, so that the requirement that the vehicle opens the CAMERAs with different functions simultaneously in different scenes is difficult to meet.
In view of this, referring to fig. 1, the present application provides a method for calling a camera, where the method for calling the camera includes the steps of:
s11: receiving a calling request sent by an application program, wherein the calling request comprises an application program identifier and a target camera identifier;
s12: 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;
s13: calling 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: an application is established with the target camera through the entertainment camera service to cause the application to invoke the target camera.
Referring further to fig. 2, the present embodiment provides a calling device 10 for a camera. The calling device 10 comprises a receiving module 11, a determining module 12, an initiating module 13 and a calling module 14.
The step S11 may be implemented by the receiving module 11, the step S12 may be implemented by the determining module 12, the step S13 may be implemented by the starting module 13, and the steps S14 and S15 may be implemented by the calling module 14.
In other words, 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 a corresponding camera service from the application identifications, the camera services including a security 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 target cameras according to target camera identifications, where each camera service corresponds to at least one camera. The invoking module 14 may cause the application to invoke the target camera based on establishing a connection with the target camera via the security camera service for the application and establishing a connection with the target camera via the entertainment camera service for the application to invoke the target camera.
Referring to fig. 3, the embodiment of the present application provides a vehicle 100, and the invoking 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, where the call request includes an application identifier and a target camera identifier, and determine corresponding camera services according to the application identifiers, where each application identifier corresponds to a camera service, and the camera services include a security camera service and an entertainment camera service. The processor 30 may be configured to invoke camera services to determine a target camera based on the target camera identification, each camera service corresponding to at least one camera 20. The processor 30 may also cause the application to invoke the target camera based on establishing a connection with the target camera by the secure camera service. 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.
In the method for calling the camera 20, the calling device 10 and the vehicle 100, the corresponding camera service process is started by receiving the calling request sent by the application program and determining the calling request according to the application program identifier in the calling request, so that the target camera to be called is determined according to the target camera identifier in the calling request through different camera service processes, and the target camera is connected with the application program, so that the application program calling request is responded. Thus, the requirement that different application programs open the cameras 20 with different functions at the same time is met.
The vehicle 100 may comprise a vehicle, a flying automobile, a high speed train, or the like. The present application will be described with reference to a vehicle as an example.
Please refer to fig. 4, it should be noted that the processor 30 may be a central processor, and the cameras 20 may be classified according to different application scenarios, and in this application, the cameras 20 may be classified into two types, i.e., a functional camera and an entertainment camera. The functional camera is used for assisting driving, for example, for recognizing a sign line of a driving lane, providing surrounding driving environment information, and providing a reverse image. The cameras 20 may include, but are not limited to, a look-around camera, a Driver Monitor Status (DMS) camera, a panoramic (VPM) camera, or a DVR camera, among others. Entertainment cameras are used to provide other functions besides driving assistance. For example, live video, video conferencing, face unlocking, etc. are provided, and the entertainment camera may be an in-vehicle camera, a roof camera, etc., such as a camera on a copilot 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 social chat-type, audiovisual video-type, game-type applications, and the like. The safety application program can be application software for backing images, travel records and the like.
The application is not limited to the application of the vehicle 100 itself, and may be an application of an electronic device when other electronic devices communicate with the vehicle 100, such as a mobile phone, a tablet, a smart wearable device (smart watch, smart bracelet, smart helmet, smart glasses, etc.), a virtual reality device, or an augmented reality device. The present application is described in terms of an application that is onboard the vehicle 100.
The Camera Service (Camera Service) is an independent process used for managing a Camera in a Camera Framework, serves as a server, is used for processing a cross-process request from a client in a Camera Framework, performs certain operation inside the Camera Framework, serves as the client, and sends the request to a Camera Provider serving as the server again, and the whole process involves two cross-process operations, wherein the Camera Service is realized through an AIDL mechanism, and the Camera Service is realized through an HIDL mechanism.
The camera service includes a security camera service for managing a security camera and an entertainment camera service. The entertainment camera service is used to manage entertainment cameras. The security camera service and the entertainment camera service may run simultaneously, and only one entertainment application's 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 identifier includes an Identity Document (ID) of the application, and the camera identifier may be an existing camera ID in the application. It is understood that the target camera ID is the ID of the target camera.
The application identifier forms a mapping relationship with the camera service, the application identifier of the secure application corresponds to the secure camera service, and the application identifier of the entertainment application corresponds to the entertainment camera service. Upon receiving a call request of an application, the security camera service and/or the entertainment camera service may be determined and turned on according to the application identification.
Further, when the number of the call requests is one, the corresponding camera service can be directly determined and started according to the application program identifier of the call request. For example, if the application is an entertainment application, then the entertainment camera service process may respond according to the application identifier of the entertainment application after receiving a call request for the entertainment application, or if the application is a security application, then the security camera service process may respond according to the application identifier of the security application after receiving a call request for the security application.
Furthermore, the connection between the application program and the target camera is directly established through the camera service, and the control of the application program on the target camera is realized.
If the calling request comprises a plurality of calling requests, the number of the safety application programs and the number of the entertainment application programs are determined through the calling requests. And when the number of the safety application programs is multiple, establishing the connection between the target safety application program and the target camera by taking the safety application program corresponding to the received calling request as the target safety application program. And when the number of the entertainment application programs is multiple, taking the entertainment application program corresponding to the 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 invocation requests for A, B, C, E and F five applications, where A, B, C is the entertainment application and C is the last invocation request sent in A, B, C, E and F are the security applications and F is the last invocation request sent in E and F. Then the connection of the C-target entertainment camera and the connection of the F-target security camera are established after the entertainment camera service and the security camera service are turned on.
As such, the cameras 20 are differentiated by functional division. On one hand, conflict management and maintenance on the realization of different services can be avoided when the cameras 20 with different parameters are debugged and compatible, and service logic for controlling mutual exclusion of the entertainment camera and the safety camera is avoided, and on the other hand, the stability of the service of the strong function camera can be improved to a certain extent, and the driving safety is improved.
The calling method can be realized by modifying a Camera framework in the android system. The following describes the modifications in the Camera framework.
As will be appreciated by those skilled in the relevant art, the Camera framework includes a Camera Java layer interface, a Java Native invocation 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 calling method is mainly realized by modifying a camera Java layer interface, a Java local calling interface (JNI) and a Native layer interface.
The class provided by the Camera Java layer to the application layer interface is android. Java, some of these methods are implemented by calling code in the native framework through the JNI.
Java native call interface (JNI), code path: frame/base/core/jni/android _ hardware _ camera. cpp, this part is compiled into libandroid _ runtime. so, it is equivalent to an intermediate station without any processing, and moves to the next layer of camera local frame (client end) for implementation.
code path of camera local framework (client side): framework/av/camera. cpp, this part of the content is compiled into the library libframera _ client. so, and this part can also be understood as a transit station, which communicates with the camera local service by means of binder mechanism calls.
CameraService, code path: the part is compiled into librameservice.so, and the part realizes a specific camera by matching with an underlying related hardware driving framework and a codec library.
camera HAL hardware abstraction layer, code path: frame/av/services/camera/libframer service/device1/camera Hardwarneinter face.h, and realizing camera data transmission and function control based on HAL completed by the interface.
Specifically, the modification of the camera Java layer interface:
the getnumberofcameraas () and the natejgetcamerainfo (int cameraId, CameraInfo) in camera. A native getNumberOfCameras (String packageName) is newly added to getNumberOfCameras (). The recognition getCameraInfo (int camera Id, Camera Info camera Info) is modified to getCameraInfo (String packagName, int camera Id, Camera Info camera Info), and at the same time, the native-calling _ getCameraInfo () in getCameraInfo (int camera Id, Camera Info camera Info) is modified.
Modification of the Java native Call interface (JNI):
the android _ hardware _ Camera _ getNumberOfCameras (JNIENv. env., job(s) thiz) and android _ hardware _ Camera _ getCameraInfo (JNIENv. env., job(s) thiz, job(s) Camera Id, job info _ obj)) in the android _ hardware _ Camera. cpp are modified. Thus, android _ hardware _ Camera _ getNumberOfCameras (JNIENv _ env, jbject third, jstring clientPackageName) is introduced into the Camera:, getNumberOfCameras (const String16& clientPackName), and android _ hardware _ Cameras _ getCameraInfo (IEnv, jbject third, jstrintPackageName, jint Camera Id, jibject info _ obj) is introduced into the Camera:, getCameraInfo (const 16& clientPackName, int Camera Id, struct:: Cameras:. CamerageName).
Modification of Native layer interface:
(1) status _ t Camera:: connected Legacy (int Camera Id, int halVersion, const String16& clientPackageName, int clientUid, sp < Camera > & Camera) in Camera. cpp.
(2) And modifying template < type TCam, type TCamTraits > sp < TCam > CameraBase < TCam, TCamTraits > in CameraBase. cpp: connect (int camera Id, const String16& clientPackageName, int clientUid, int clientPid).
(3) In CameraBase. cpp, template < typeTCam, typeTCamTraits > int CameraBase < TCam, TCamTraits:getNumberOfCameras (), the concrete modification is as follows: template < typename TCam, typename TCamTraits > int CameraBase < TCam, TCamTraits > getNumberOfCameras (const String16& clientPackageName).
(4) And modifying template < type TCam, type TCamTraits > status _ t CameraBase < TCam, TCamTraits > getCameraInfo (int CameraId, structure hardware:: CameraInfo) in CameraBase. cpp to: template < typeTCam, typeTCamTraits > status _ t CameraBase < TCam, TCamTraits > getCameraInfo (const String16& clientPackageName, int CameraId, struct hardware:: 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 safety 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, substeps 141 and substep S151 may be implemented by the invoking module 14, or the invoking module 14 may be configured to pass the data of the target camera to the display screen display corresponding to the security camera service and pass the data of the target camera to the display screen display corresponding to the entertainment camera service.
In some embodiments, the processor 30 is configured to communicate 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 communicate 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 for graphical user interface display, the display screen 40 may include, but is not limited to, a dashboard screen, a center console screen, a copilot screen, a rear seat display screen, and other area display screens 40 of the vehicle 100, among others.
Further, the security camera service and the entertainment camera service correspond to different display screens 40, respectively. The safety camera service can correspond to an instrument screen, a central control screen and a copilot screen, and the entertainment camera service can correspond to the copilot screen, a rear seat display screen and the like. Therefore, 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 screen 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 screen 40.
In this embodiment, each display screen 40 may display the same type of application, for example, the center control screen may only display the security application. The copilot screen only displays entertainment applications. Different classes of applications may also be displayed, for example, the central control screen may display both security 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 sub-step 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 displaying.
In some embodiments, the processor 30 is configured to communicate data from the target camera to a display screen display corresponding to the camera service.
In this embodiment, the display 40 may display only the same type of application, for example, the center control screen may display only the security application. The copilot screen only displays entertainment applications. In this way, when the user clicks the application to call the camera, the image can be displayed on the display screen 40 where the application is located.
Referring to fig. 7, in some embodiments, step S13 includes the sub-steps of:
s131: creating a virtual interface of a 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 a target camera through the target virtual interface.
In some embodiments, substeps 131, S132 and substep S133 may be performed by the starting module 13, or the starting module 13 may be used to create a virtual interface of the camera service and 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 start module 13 may also be configured to determine a target camera through the 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 is also operable to determine a target virtual interface corresponding to the camera service based on the target camera identification and determine a target camera via 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 includes 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 invoking device 10 further includes a control module 15, and the step S16 can be implemented by the receiving module 12. Step S17 may be implemented by the control module 15.
Or, the receiving module 12 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 a 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, to set the shooting parameters of the target camera, and the like.
The embodiment of the application also provides one or more nonvolatile computer readable storage media storing computer programs, and when the computer programs are executed by one or more processors, the calling method of the camera in any embodiment is realized.
It will be understood by those skilled in the art that all or part of the processes in the method for implementing the above embodiments may be implemented by a computer program instructing relevant software. The program may be stored in a non-volatile computer readable storage medium, which when executed, may include the flows of embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), or the like.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A camera calling method for a vehicle, wherein the vehicle comprises a plurality of application programs and a plurality of cameras, and the camera calling method comprises the following steps:
receiving a calling request sent by the application program, wherein the calling request comprises an application program identifier and a target camera identifier;
determining corresponding camera services according to the application program identifications, wherein the camera services comprise a security camera service and an entertainment camera service, and each application program identification corresponds to one camera service;
calling the camera services to determine target cameras according to the target camera identifications, wherein each camera service corresponds to at least one camera;
establishing 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, by the entertainment camera service, the application program in connection with the target camera to cause the application program to invoke the target camera.
2. The method for invoking as defined in claim 1, wherein the vehicle further comprises a plurality of display screens, the establishing the application with the target camera connection through the secure camera service to cause the application to invoke the target camera comprises:
transmitting the data of the target camera to the display screen corresponding to the safety camera service for displaying;
the establishing, by the entertainment camera service, the application program in connection with the target camera to cause the application program to invoke the target camera comprises:
and transmitting the data of the target camera to the display screen corresponding to the entertainment camera service for display.
3. The method for invoking as defined in claim 1, wherein the vehicle further comprises a plurality of display screens, the establishing the application with the target camera connection through the secure camera service to cause the application to invoke the target camera comprises:
and transmitting the data of the target camera to the display screen corresponding to the application program for displaying.
4. The calling method of claim 1, wherein the applications comprise an entertainment application and a security application, and wherein determining the corresponding camera service based on the application identification comprises:
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;
determining the secure camera service when the application is a secure application.
5. The calling method of claim 4, wherein the establishing, by the secure camera service, the application program to connect with the target camera to cause the application program to call the target camera comprises:
determining the number of the safety application programs according to the calling request;
when the number of the safe application programs is multiple, taking the safe application program corresponding to the calling request received firstly as a target safe application program;
establishing connection between the target security application program and the target camera;
the establishing, by the entertainment camera service, the application program in connection with the target camera to cause the application program to invoke the target camera comprises:
determining the number of entertainment applications according to the call request;
when the number of the safety application programs is multiple, taking the entertainment application program corresponding to the calling request received firstly as a target entertainment application program;
establishing a connection between the target entertainment application and the target camera.
6. The calling method of claim 1, wherein the calling 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.
7. 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.
8. A camera invocation device for a vehicle, wherein the vehicle comprises a plurality of applications and a plurality of cameras, the invocation device comprising:
the receiving module is used for receiving a calling request sent by the application program, wherein the calling request comprises an application program identifier and a target camera identifier;
a determining module, configured to determine, according to the application identifiers, corresponding camera services, where the camera services include a security camera service and an entertainment camera service, and each application identifier corresponds to one of the camera services;
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 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 the calling module 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.
9. A vehicle comprising a memory and a processor, the memory having stored thereon a computer program that, when executed by the processor, implements the method of calling of any of claims 1-7.
10. A non-transitory computer-readable storage medium containing a computer program, wherein the computer program, when executed by one or more processors, implements the method of invoking the camera of any of claims 1-7.
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 true CN113489898A (en) | 2021-10-08 |
| CN113489898B 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 (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100231754A1 (en) * | 2009-03-11 | 2010-09-16 | Wang Shaolan | Virtual camera for sharing a physical camera |
| 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 |
| US20180167546A1 (en) * | 2016-12-14 | 2018-06-14 | Beijing Xiaomi Mobile Software Co., Ltd. | Method, device and computer readable medium for communiation using smart video cameras |
| 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 |
-
2021
- 2021-06-29 CN CN202110729098.4A patent/CN113489898B/en active Active
Patent Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100231754A1 (en) * | 2009-03-11 | 2010-09-16 | Wang Shaolan | Virtual camera for sharing a physical camera |
| 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 |
| US20180167546A1 (en) * | 2016-12-14 | 2018-06-14 | Beijing Xiaomi Mobile Software Co., Ltd. | Method, device and computer readable medium for communiation using smart video cameras |
| 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 |
|---|---|
| CN113489898B (en) | 2023-10-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111634188A (en) | Method and device for projecting screen | |
| CN109388467A (en) | Map information display method, device, computer equipment and storage medium | |
| US9609270B2 (en) | Method for performing a video talk enhancement function and an electric device having the same | |
| CN107909378B (en) | Vehicle information auditing method and device, storage medium and electronic equipment | |
| CN113032080B (en) | Page implementation method, application program, electronic device and storage medium | |
| CN105549821A (en) | Interconnecting method, device and system of mobile equipment and car-mounted information entertainment product | |
| CN107291319A (en) | A kind of window display method, information interacting method and system | |
| DE112013004672T5 (en) | Vehicle-side device, communication method and program | |
| CN110991368A (en) | Camera scene recognition method and related device | |
| CN113992958A (en) | Multi-window same-screen interaction method, terminal and storage medium | |
| CN104285207A (en) | Method, mobile device and infotainment system for projecting user interface onto screen | |
| CN109889877A (en) | Car multi-screen display control method and device | |
| CN113489898A (en) | Camera calling method and device, vehicle and storage medium | |
| CN115550886B (en) | Vehicle-mounted augmented reality equipment control method and system and vehicle-mounted interaction system | |
| CN114461158B (en) | Application screen projection method and device, vehicle-mounted terminal and readable storage medium | |
| CN115002274B (en) | Control method and device, electronic equipment and computer readable storage medium | |
| CN115220842A (en) | Vehicle navigation method, system, vehicle and storage medium | |
| WO2019172463A1 (en) | Method, system, and non-transitory computer-readable recording medium for recommending profile photo | |
| US20190132548A1 (en) | Traffic stop communications system | |
| US20190225082A1 (en) | System Having an Infotainment System | |
| JP2019114000A (en) | Information processing device, control method therefor, and program | |
| CN114398018A (en) | Picture display method, device, storage medium and electronic equipment | |
| CN111600839A (en) | Traffic accident handling method, equipment and storage medium | |
| TWM573308U (en) | The fleet monitoring management system and vehicle hosts | |
| CN209118492U (en) | A kind of device of vehicle detection, vehicle identification system and parking management system |
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 |