CN114845035A - Distributed shooting method, electronic equipment and medium - Google Patents

Abstract

A distributed shooting method, electronic device and medium can reduce the network bandwidth occupied by data transmission between a remote device and a local device in the process of realizing distributed shooting. In this method, the first device may receive a first operation of the user selecting to shoot synchronously with the second device. In response to the first operation, the first device may start acquiring the first image data, and the first device may also instruct the second device to start acquiring the image data. Afterwards, the first device may receive second image data from the second device, where the second image data includes the original image captured by the camera of the second device. Finally, the first device may display the first shooting picture corresponding to the first image data in the first window, and display the second shooting picture corresponding to the second image data in the second window. The first window and the second window are located on the same display interface.

Description

A distributed shooting method, electronic device and medium

technical field

The embodiments of the present application relate to the field of photographing technologies, and in particular, to a distributed photographing method, an electronic device, and a medium.

Background technique

With the development of Internet technology, multiple electronic devices including cameras can form a distributed camera system. For example, the electronic device may be a mobile phone, a tablet computer, a smart watch, or a smart TV. In the distributed camera system, an electronic device (called the local device) can not only present the picture captured by the camera of the electronic device to the user, but also acquire and display the camera captured by other electronic devices (called the remote device). screen.

Specifically, the local device can obtain the screen of the remote device in the following ways: (1) the local device sends a control command to the remote device, instructing the remote device to collect images and return the preview result to the local device; (2) the remote device After receiving the control command, the end device collects images and performs image signal processing (ISP) on the collected images to obtain a preview result; (3) the remote device sends the preview result to the local device.

In the above-mentioned cross-device image data transmission process, what the remote device sends to the local device is the result of image processing (that is, the above-mentioned preview result), which increases the amount of data and needs to occupy a large network bandwidth, which is a waste of time. network resources.

SUMMARY OF THE INVENTION

The present application provides a distributed shooting method, an electronic device and a medium, which can reduce the network bandwidth occupied by the remote device and the local device for data transmission during the process of realizing the distributed shooting.

In a first aspect, the present application provides a distributed shooting method, which is applied to a first device. In this method, the first device may receive a first operation of the user selecting to perform synchronous shooting with the second device. In response to the first operation, the first device may start acquiring the first image data and instruct the second device to start acquiring the image data. Thereafter, the first device may receive second image data from the second device, the second image data including the original image. Finally, the first device may display the first shooting picture corresponding to the first image data in the first window, and display the second shooting picture corresponding to the second image data in the second window. The first window and the second window are located on the same display interface.

It should be noted that the above-described original image may also be referred to as a RAW image. RAW can be translated as "unprocessed". That is, the above-mentioned original image is an image that has not been processed by the second device. Compared with the image processed by the second device, the data amount of the original image is smaller. In this way, the network bandwidth occupied by the distributed shooting service across the devices can be reduced.

In a possible design of the first aspect, the above method may further include: the first device sends first image data to the second device, where the first image data includes an original image. The original image (also referred to as a RAW image) is an image that has not been processed by the first device.

In this way, not only the first device can simultaneously display the shooting image of the first device and the shooting image of the second device, but also the second device can simultaneously display the shooting image of the first device and the shooting image of the second device.

In another possible design manner of the first aspect, after the first device receives the first operation that the user selects to shoot synchronously with the second device, the method of the present application may further include: the first device acquires the second device's A shooting capability parameter, where the shooting capability parameter is used to indicate an image processing algorithm supported by the second device.

Afterwards, the first device may perform image processing on the first image data according to the shooting capability parameters of the first device to obtain a first shooting picture; and according to the shooting capability parameters of the second device, perform image processing on the second image data to obtain the first image Two pictures. The shooting capability parameter of the first device is used to indicate an image processing algorithm supported by the first device.

It should be understood that, based on the algorithm capability of the second device (that is, the image processing algorithm supported by the second device indicated by the shooting capability parameter of the second device), the first device performs image processing on the RAW image collected by the second device. The second device performs the same or similar effect of image processing on the RAW image. In this way, the picture effect of the second device can be restored on the first device.

In another possible design manner of the first aspect, the first device may perform image processing on the first image data according to the shooting capability parameter of the first device to obtain the first shooting picture; The shooting capability parameter of the first device is used, and image processing is performed on the second image data to obtain the second shooting picture. Wherein, the shooting capability parameter of the first device is used to indicate an image processing algorithm supported by the first device.

It should be understood that, based on the algorithm capability of the first device, the first device performs image processing on the RAW images collected by the first device and the second device, so that the image effects of the shooting screen of the second device and the shooting screen of the first device can be consistent.

Moreover, in this design manner, the first device does not need to acquire and save the shooting capability parameters of the second device. In this way, the network bandwidth occupied by the distributed shooting service across the devices can be further reduced, and the storage space of the first device can also be saved.

In another possible design of the first aspect, the above-mentioned first device instructing the second device to start capturing image data includes: the first device sends a shooting instruction to the second device.

Wherein, the shooting instruction includes a preset mark, the shooting instruction is used to instruct the second device to collect image data, and the preset mark is used to instruct the second device to transmit the original image collected by the second device to the first device. After the second device receives the shooting instruction including the above-mentioned preset mark, it does not process the captured original image; instead, it transparently transmits the captured original image to the first device.

In another possible design of the first aspect, before the first device receives the first operation, the first device may receive the second operation. The second operation is the user's click operation on the function button for realizing distributed shooting, the preview interface of the camera application of the first device, the chat interface of the video communication application of the first device, the control center of the first device, the drop-down menu Or at least one item in the negative screen includes function buttons. In response to the second operation for clicking the function button, the first device displays a list of candidate devices in the preview interface. The second device is included in the candidate device list. The first operation is an operation in which the user selects the second device in the candidate device list.

In another possible design manner of the first aspect, the above-mentioned synchronous shooting includes at least one of synchronous video recording, synchronous photographing, synchronous live broadcast, or synchronous video call. That is, the method of the present application can be applied to the process of video recording, photographing, live broadcasting, or video calling with other devices by the first device.

In another possible design manner of the first aspect, after the first device receives the first operation that the user selects to shoot synchronously with the second device, the method of the present application further includes: the first device creates the A control session and a data session between the first device and the second device.

Wherein, the above-mentioned control session is used to transmit a control command between the first device and the second device, the control command includes a shooting instruction used to instruct the second device to capture an image, and the data session is used for The second image data from the second device is transmitted.

The first device and the second device can distinguish the transmission paths of the control flow and the data flow during the process of executing the distributed photographing service across the devices. In this way, the problem that the control flow and the data flow mutually occupy the bandwidth can be avoided.

In a second aspect, the present application provides an electronic device, the electronic device is a first device, and the electronic device includes: one or more cameras, one or more processors, a display screen, a memory, and a communication module. The above camera, display screen, memory, communication module and processor are coupled.

Wherein, the memory is used to store computer program codes, and the computer program codes include computer instructions. When the computer instructions are executed by the electronic device, the electronic device is made to execute the method described in the first aspect and any possible design manner thereof.

In a third aspect, the present application provides a chip system, which is applied to an electronic device including a display screen, a memory and a communication module; the chip system includes one or more interface circuits and one or more processors; the An interface circuit and the processor are interconnected by a wire; the interface circuit is configured to receive signals from a memory of the electronic device and send the signals to the processor, the signals comprising computer instructions stored in the memory ; When the processor executes the computer instructions, the electronic device executes the method described in the first aspect and any possible design manner thereof. The electronic device is the first device.

In a fourth aspect, the present application provides a computer storage medium, the computer storage medium comprising computer instructions, when the computer instructions are executed on an electronic device, the electronic device is made to perform the first aspect and any possible design methods thereof the method described.

In a fifth aspect, the present application provides a computer program product, which, when the computer program product runs on a computer, causes the computer to execute the method described in the first aspect and any possible design manners thereof.

In a sixth aspect, the present application provides a distributed shooting system, which includes the first device described in the second aspect and any possible design manner, and the second aspect involved in the first aspect and any possible design manner. equipment.

It can be understood that the electronic device according to the second aspect, the chip system according to the third aspect, the computer storage medium according to the fourth aspect, the computer program product according to the fifth aspect, and the sixth aspect For the beneficial effects that can be achieved by the distributed shooting system, reference may be made to the beneficial effects in the first aspect and any possible design manners thereof, which will not be repeated here.

Description of drawings

1 is a schematic diagram of the architecture of a distributed shooting system provided by an embodiment of the present application;

2A is a schematic diagram of functions implemented by a distributed shooting method provided by an embodiment of the present application;

2B is a schematic diagram of a hardware structure of a mobile phone according to an embodiment of the application;

2C is a schematic diagram of a software architecture of the local device 101 or the remote device 102;

2D is a schematic diagram of the software architecture of the local device 101 and the remote device 102;

FIG. 2E is a schematic diagram of a software architecture of a local device 101 and a remote device 102 according to an embodiment of the application;

Figure 2F is a simplified diagram of the software architecture shown in Figure 2E;

3A is a schematic diagram of a distributed shooting interface provided by an embodiment of the present application;

3B is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

6A is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

6B is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

8 is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

10 is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

12 is a schematic diagram of a data structure of a shooting capability parameter provided by an embodiment of the present application;

13 is a schematic diagram of a data transmission flow between a local device and a remote device according to an embodiment of the present application;

FIG. 14 is a schematic flowchart of data processing and transmission in a remote device provided by an embodiment of the present application;

FIG. 15 is a schematic diagram of another distributed shooting interface provided by an embodiment of the present application;

16 is a schematic diagram of a data transmission flow between a local device and a remote device according to an embodiment of the present application;

FIG. 17 is a schematic structural diagram of a chip system provided by an embodiment of the present application.

Detailed ways

Hereinafter, the terms "first" and "second" are only used for descriptive purposes, and should not be construed as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may expressly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

A distributed shooting method provided by the embodiment of the present application can be applied to the distributed shooting system 100 shown in FIG. 1 . As shown in FIG. 1 , the distributed shooting system 100 may include a local device 101 and N remote devices 102 , where N is an integer greater than 0. The local device 101 and any remote device 102 may communicate in a wired manner, or may communicate in a wireless manner. The local device 101 is the first device, and the remote device 102 is the second device.

Exemplarily, a wired connection may be established between the local device 101 and the remote device 102 using a universal serial bus (universal serial bus, USB). For another example, between the local device 101 and the remote device 102, a global system for mobile communications (GSM), a general packet radio service (GPRS), a code division multiple access (CDMA) can be used. code division multiple access (CDMA), wideband code division multiple access (WCDMA), time division code division multiple access (TD-SCDMA), long term evolution (LTE), 5G and subsequent standard protocols, Bluetooth, wireless fidelity (Wi-Fi), NFC, voice over Internet protocol (VoIP), and communication protocols supporting network slicing architecture establish wireless connections.

In some embodiments, the local device 101 may directly communicate with the remote device 102 by using the above-mentioned wireless connection. In other embodiments, the local device 101 may use the above wireless connection to communicate with the remote device 102 through a cloud server, which is not limited in this embodiment of the present application.

Wherein, both the local device 101 and the remote device 102 can be provided with one or more cameras. The local device 101 can use its own camera to collect image data, and the remote device 102 can also use its own camera to collect image data. In this embodiment of the present application, the local device 101 and the remote device 102 can use their own cameras to collect image data at the same time, and the remote device 102 can send the image data to the local device 101, and the local device 101 can simultaneously display images from The image data of the local device 101 and the remote device 102, so as to realize the distributed shooting function across the devices.

As shown in FIG. 2A , the local device 101 may include a preset application (application, APP). The local device 101 can implement the above-mentioned distributed shooting function across devices through the application. For example, the preset application may be a system camera application or a third-party camera application. In this embodiment of the present application, the system camera application or the third-party camera application may be collectively referred to as a camera application. The system application may also be referred to as an embedded application, and an embedded application is an application program provided as a part of the realization of an electronic device (eg, the local device 101 or the remote device 102 ). Third-party applications may also be referred to as downloadable applications. A downloadable application is an application that can provide its own internet protocol multimedia subsystem (IMS) connection. The downloadable application may be an application pre-installed in the electronic device or may be an application downloaded and installed on the electronic device by a user.

Specifically, as shown in FIG. 2A , the local device 101 can be connected to the remote device 102 , and can also control the remote device 102 to open the camera of the remote device 102 through the connection between the local device 101 and the remote device 120 . As shown in FIG. 2A , an image preview of the remote device 102 can be implemented on the local device 101 to control the preview effect. As shown in FIG. 2A , the local device 101 can control the remote device 102 to take pictures, and control the photographing effect of the remote device 102 . As shown in FIG. 2A , the local device 101 can control the video recording of the remote device 102 and control the video recording effect of the remote device 102 . The above-mentioned distributed shooting function across devices is implemented. As shown in FIG. 2A , the local device 101 can display the shooting images of the local device 101 and the remote device 102 . In this way, on the local device 101 , the user can not only see the shooting picture of the local device 101 , but also the shooting picture of the remote device 102 . Of course, the local device 101 can also control the remote device 102 to turn off the camera of the remote device 102 through the connection between the local device 101 and the remote device 120 .

Exemplarily, the local device 101 (or the remote device 102) may specifically be a mobile phone, a tablet computer, a TV (also referred to as a smart TV, a smart screen or a large-screen device), a notebook computer, an ultra-mobile personal computer (Ultra- mobilePersonal Computer, UMPC), handheld computers, cameras (such as digital cameras), video cameras (such as digital video cameras), netbooks, personal digital assistants (Personal Digital Assistant, PDA), wearable electronic devices (such as: smart watches, smart bracelets, Smart glasses), vehicle-mounted devices, virtual reality devices, and other electronic devices with a shooting function, which are not limited in this embodiment of the present application.

Illustratively, taking a mobile phone as the local device 101 in the above-mentioned distributed shooting system 100 as an example, FIG. 2B shows a schematic structural diagram of the mobile phone. As shown in FIG. 2B, the mobile phone may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, an antenna 1, an antenna 2, a mobile communication module 150, and a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, and the like.

It can be understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the mobile phone. In other embodiments of the present application, the mobile phone may include more or less components than shown, or some components may be combined, or some components may be separated, or different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor ( image signal processor, ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and/or neural-network processing unit (NPU), etc. . Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have just been used or recycled by the processor 110 . If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby increasing the efficiency of the system.

The wireless communication function of the mobile phone can be realized by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, the baseband processor, and the like. Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G etc. applied on the mobile phone. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the same device as at least part of the modules of the processor 110 .

The wireless communication module 160 can provide applications on the mobile phone including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite systems (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions.

In some embodiments, the antenna 1 of the mobile phone is coupled with the mobile communication module 150, and the antenna 2 is coupled with the wireless communication module 160, so that the mobile phone can communicate with the network and other devices through wireless communication technology.

The mobile phone realizes the display function through the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel. In some embodiments, the handset may include 1 or N display screens 194, where N is a positive integer greater than 1.

The mobile phone can realize the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194 and the application processor. Camera 193 is used to capture still images or video. The object is projected through the lens to generate an optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other formats of image signals. In some embodiments, the mobile phone may include 1 or N cameras 193 , where N is a positive integer greater than 1.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone. The external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example to save files like music, video etc in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the mobile phone by executing the instructions stored in the internal memory 121 . The internal memory 121 may include a storage program area and a storage data area. The storage program area can store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), and the like. The storage data area can store data (such as audio data, phone book, etc.) created during the use of the mobile phone. In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), and the like.

The mobile phone can implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, and an application processor. Such as music playback, recording, etc.

The sensor module 180 may include a pressure sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

Of course, the mobile phone may also include a charging management module, a power management module, a battery, a button, an indicator, and one or more SIM card interfaces, which are not limited in this embodiment of the present application.

FIG. 2C is a block diagram of a software structure of a mobile phone according to an embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into five layers, which are, from top to bottom, an application layer, an application framework layer, an Android runtime (Android runtime) and a system library, and a HAL (hardware abstraction layer, hardware abstraction layer) layer. and the kernel layer. It should be understood that the Android system is used as an example to illustrate, in other operating systems (such as Hongmeng system, IOS system, etc.), as long as the functions implemented by each functional module are similar to the embodiments of the present application, the solution of the present application can also be implemented.

The application layer can include a series of application packages.

As shown in Figure 2C, applications such as calls, memos, browsers, contacts, gallery, calendar, maps, Bluetooth, music, video, and short messages can be installed in the application layer.

In this embodiment of the present application, an application with a shooting function, for example, a camera application, may be installed in the application layer. Of course, when other applications need to use the shooting function, the camera application can also be called to realize the shooting function.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for the applications of the application layer. The application framework layer includes some predefined functions.

For example, the application framework layer may include a window manager, a content provider, a view system, a resource manager, a notification manager, etc., which is not limited in this embodiment of the present application.

For example, the above-mentioned window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, take screenshots, etc. The above content providers are used to store and retrieve data and make these data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone book, etc. The view system described above can be used to build the display interface of an application. Each display interface can consist of one or more controls. Generally speaking, controls may include interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets. The above resource managers provide various resources for the application, such as localized strings, icons, pictures, layout files, video files, and so on. The notification manager described above enables applications to display notification information in the status bar, which can be used to convey notification-type messages, and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also display notifications in the status bar at the top of the system in the form of graphs or scroll bar text, such as notifications from applications running in the background, and notifications on the screen in the form of dialog windows. For example, prompt text information in the status bar, send out a sound, vibrate, and flash the indicator light, etc.

As shown in Figure 2C, the Android runtime includes core libraries and virtual machines. The Android runtime is responsible for the scheduling and management of the Android system.

The core library consists of two parts: one is the function functions that the java language needs to call, and the other is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, safety and exception management, and garbage collection.

A system library can include multiple functional modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL) and so on.

Among them, the surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications. The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc. The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing. 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is located under the HAL and is the layer between hardware and software. The kernel layer at least includes a display driver, a camera driver, an audio driver, a sensor driver, and the like, which are not limited in this embodiment of the present application.

In the embodiment of the present application, still as shown in FIG. 2C , taking a camera application as an example, a camera service (Camera Service) is set in the application framework layer. The camera application can start the Camera Service by calling the preset API. CameraService can interact with CameraHAL in HAL (hardware abstraction layer, hardware abstraction layer) during the running process. Among them, the Camera HAL is responsible for interacting with the hardware devices (such as cameras) that realize the shooting function in the mobile phone. On the one hand, the Camera HAL hides the implementation details of the relevant hardware devices (such as specific image processing algorithms), and on the other hand can provide the Android system. Call the interface of the relevant hardware device.

Exemplarily, when the camera application is running, the relevant control commands (such as preview, zoom in, photographing or video recording instructions) issued by the user may be sent to the Camera Service. On the one hand, the Camera Service can send the received control commands to the Camera HAL, so that the Camera HAL can call the camera driver in the kernel layer according to the received control commands, and the camera driver drives the camera and other hardware devices to collect images in response to the control command. data. For example, the camera can transmit each frame of image data collected to the Camera HAL through the camera driver at a certain frame rate. For the transfer process of the control command inside the operating system, reference may be made to the specific transfer process of the control flow in FIG. 2C .

On the other hand, after receiving the above-mentioned control command, the Camera Service can determine the shooting strategy at this time according to the received control command, and the specific image processing task that needs to be performed on the collected image data is set in the shooting strategy. For example, in preview mode, Camera Service can set image processing task 1 in the shooting strategy to implement the face detection function. For another example, if the user enables the beauty function in the preview mode, the Camera Service may further set image processing task 2 in the shooting policy to implement the beauty function. Furthermore, the Camera Service can send the determined shooting strategy to the Camera HAL.

After the Camera HAL receives each frame of image data collected by the camera, it can perform corresponding image processing tasks on the above-mentioned image data according to the shooting strategy issued by the Camera Service, and obtain each frame of shooting picture after image processing. For example, Camera HAL can perform image processing task 1 for each frame of image data received according to shooting strategy 1, and obtain each corresponding frame of shooting picture. After the shooting strategy 1 is updated to the shooting strategy 2, the Camera HAL can perform image processing task 2 and image processing task 3 for each frame of image data received according to the shooting strategy 2, and obtain each corresponding shooting picture.

Subsequently, the Camera HAL can report each frame of the captured image after image processing to the camera application through the Camera Service, and the camera application can display each frame of the captured image on the display interface, or the camera application can display each frame of the captured image in the form of a photo or video. Each frame shot is saved in the phone. Wherein, for the transfer process of the above-mentioned shooting images within the operating system, reference may be made to the specific transfer process of the data flow in FIG. 2C .

Please refer to FIG. 2D , which shows a schematic diagram of a software architecture of the local device 101 and the remote device 102 . In this embodiment of the present application, the solution for realizing cross-device distributed shooting by the local device 101 and the remote device 102 is described with reference to the software architecture shown in FIG. 2D .

The local device 101 has the functions of device discovery and remote registration. For example, the local device 101 can discover the remote device 102, such as the TV 1, the watch 2, and the mobile phone 3 as shown in FIG. 4 . When the user selects TV 1 as the remote device 102 and the local device 101 to perform cross-device distributed shooting (for example, the user selects the TV 1 shown in FIG. 4 ), the local device 101 can use the remote device 102 (such as the TV 1) ) is registered on the local device 101.

For example, the local device 101 may create a distributed mobile sensing development platform (Distributed MobileSensing Development Platform, DMSDP) HAL for the remote device 102 at the hardware abstraction layer (HAL) of the local device 101, which may also be called For the virtual camera HAL (ie virtual CameraHAL). Wherein, different from the traditional Camera HAL in the local device 101, the DMSDP HAL does not correspond to the actual hardware device of the local device 101, but corresponds to the remote device 102 currently connected to the local device 101. The DMSDP HAL shown in FIG. 2D is the HAL created by the local device 101 according to the shooting capability parameters of the remote device 102 . The local device 101 can send and receive data with the remote device 102 through the DMSDP HAL, and the remote device 102 is used as a virtual device of the local device 101 to cooperate with the remote device 102 to complete the cross-device distributed shooting service.

The following describes a specific process for the local device 101 and the remote device 102 to cooperate to complete the cross-device distributed shooting service. As shown in FIG. 2D, the process may include steps ①-step ⑩.

Step ①: The application layer of the local device 101 issues a control command for controlling the camera of the remote device 102 to the camera service of the service layer. Step ②: The service layer of the local device 101 sends the control command to the DMSDP HAL of the HAL. Step ③: The DMSDP HAL of the local device 101 transmits a control command to the remote device 102 . Step ④: After receiving the control command, the remote device 102 transmits the control command to the service layer. Step ⑤: The service layer of the remote device 102 transmits a control command to the Camera HAL of the HAL. The Camera HAL of the remote device 102 corresponds to the actual hardware device of the remote device 102 . In this way, the HAL of the remote device 102 can call its bottom layer (eg, the kernel layer) to perform corresponding shooting tasks (eg, start the camera, switch the camera, or adjust the relevant parameters of the camera, etc.) according to the control command. Wherein, the data transmitted in the above steps ①-step ⑤ may be referred to as a control flow.

Step ⑥: The HAL of the remote device 101 uploads the preview stream to the camera service of the service layer. The preview stream includes one or more frames of preview images collected by the bottom camera device of the remote device 102 and processed by the bottom layer image signal processor (image signal processor, ISP). Step ⑦: The service layer of the remote device 101 transmits the preview stream to the application layer of the remote device 102 . Step 8: The application layer of the remote device 101 transmits the preview stream to the DMSDP HAL of the local device 101 . Step 9: The DMSDP HAL of the local device 101 transmits the preview stream to the camera service of the service layer. Step ⑩: The service layer of the local device 101 reports the preview stream to the application layer. In this way, the camera application of the local device 101 can present the preview stream from the remote device 102 to the user (such as the above-mentioned shooting picture 2, shooting picture 3 or shooting picture c). Of course, the camera application of the local device 101 can also present the preview stream from the local device 101 to the user, and the specific process can refer to the related introduction of the conventional technology, which will not be repeated here. Wherein, the data transmitted in the above steps ⑥-step ⑩ may be referred to as a preview stream or a data stream.

It should be noted that, as shown in FIG. 2D , the service layer of the local device 101 or the remote device 102 may be included in the framework layer, and the service layer may be implemented in the framework layer. Certainly, the service layer of the service layer of the local device 101 or the remote device 102 may also be independent of the framework layer, which is not limited in this embodiment of the present application.

On the one hand, although executing the above process can complete the distributed shooting service across devices; however, in the above-mentioned cross-device preview stream transmission process, the preview stream transmitted from the remote device 102 to the local device 101 is obtained through image processing. If the data volume is increased, a large amount of network bandwidth needs to be occupied, and network resources are wasted.

On the other hand, different devices have different performances for image processing. For example, compared with the local device 101, the performance of the layer processing performed by the remote device 102 may be lower. In this way, the drawing efficiency of the remote device 102 is lower. To realize the simultaneous display of the captured images from the local device 101 and the remote device 102 on the local device 101, a relatively long time delay is required. Moreover, in the above process, the transmission paths of the control flow and the data flow (or preview flow) are not distinguished, and the control flow and the data flow may occupy the bandwidth of each other.

An embodiment of the present application provides a distributed shooting method. During the process of performing a distributed shooting service across devices between the local device 101 and the remote device 102, the local device 101 can directly obtain the remote device 102 from the remote device 102. Raw image captured by device 102 . The original image may also be referred to as a RAW image. RAW can be translated as "unprocessed". That is to say, the original image collected by the remote device 102 is an image that has not been processed by the remote device 102 . In the following embodiments, a RAW image is used to represent the original image, and the method of the embodiment of the present application is introduced.

Wherein, compared with the image processed by the remote device 102, the data amount of the RAW image is smaller. In this way, the network bandwidth occupied by the distributed shooting service across the devices can be reduced.

In addition, the local device 101 processes the RAW image from the remote device 102, which can avoid the problem of increasing the time delay due to the large performance difference between the two devices. With this solution, the time delay of the distributed shooting service can be reduced. Further, in the process of executing the cross-device distributed photographing service between the local device 101 and the remote device 102, the transmission paths of the control flow and the data flow can be distinguished. In this way, it is possible to avoid the problem of the control flow and the data flow occupying the bandwidth with each other.

Please refer to FIG. 2E , which shows a schematic diagram of a software architecture of a local device 101 and a remote device 102 provided by an embodiment of the present application. As shown in FIG. 2E , the local device 101 may include an application layer 200 , a framework layer 201 , a service layer 201 a and a HAL 202 ; the remote device 102 may include an application layer 210 , a framework layer 211 , a service layer 211 a and a HAL 212 . Among them, the service layer can be implemented in the framework layer. For example, as shown in FIG. 2E , the service layer 201 a may be implemented in the framework layer 201 , and the service layer 211 a may be implemented in the framework layer 211 .

Among them, the application layer may include a series of application packages. For example, the application layer 200 may include multiple applications, such as a camera application and a Dv application 200a. Of course, when other applications need to use the shooting function, the camera application can also be called to realize the shooting function. For another example, the application layer 210 includes a camera proxy service 210a for supporting the remote device 102 and the local device 101 to cooperate to complete a distributed shooting service. The camera proxy service 210a may also be called a camera proxy application, which is not limited in this embodiment of the present application.

In addition, in the present application, a device virtualization (device virtualization, Dv) application 200a for realizing a distributed shooting function may also be installed in the application layer 200 . The Dv application 200a may run in the local device 101 as a system application. Alternatively, the functions implemented by the Dv application 200a may also be resident in the local device 101 and run in the form of system services.

The framework layer provides APIs and programming frameworks for applications in the application layer. For example, both the framework layer 201 and the framework layer 211 may provide Camera API 2.0. For other functions of the framework layer 201 and the framework layer 211, reference may be made to the detailed introduction of the application framework layer shown in FIG. 2C in the embodiment of the present application, which is not repeated here.

As shown in FIG. 2E , taking a camera application as an example, the frame layer 201 is provided with a Camera kit 201c. Among them, Camera kit 201c can encapsulate a variety of camera modes. For example, the photographing mode, video recording mode and dual scene mode shown in FIG. 2E.

As shown in FIG. 2E, a camera service (Camera Service) 201a1 may be provided in the service layer 201a. Camera applications can start Camera Service 201a1 by calling a preset API (such as Camera API 2.0). The HAL 202 is provided with a Camera HAL 202a and a DMSDP HAL 202b. Camera Service 201a1 can interact with Camera HAL 202a and/or DMSDP HAL 202b in HAL 202 during operation.

Among them, the Camera HAL 202a is responsible for interacting with the hardware device (such as a camera) that implements the shooting function in the local device 101. On the one hand, the Camera HAL 202a hides the implementation details of the relevant hardware devices (such as specific image processing algorithms), and on the other hand It can provide the Android system with an interface for calling related hardware devices.

It should be noted that, when the camera application in the application layer 200 is running, the interaction process between the application layer 200 and the framework layer 201, the service layer 201a, the Camera HAL 202a, and the DMSDP HAL 202b, etc., can refer to the above embodiment for the corresponding software modules in FIG. 2C. , which is not repeated in this embodiment of the present application.

The above-mentioned framework layer 201 may also be provided with a Dv kit (kit) 201b for realizing a distributed shooting function. The Dvkit 201b can be called by the Dv application 200a provided in the application layer 200 to realize the function of discovering and connecting to the remote device 102 . Alternatively, the functions implemented by the Dv application 200a can also be resident and run in the mobile phone in the form of system services.

When the mobile phone needs to use the cameras of other electronic devices to realize the distributed shooting function, in the camera mode (eg dual-view mode) provided by the Camera kit 201c, the local device 101 can discover and connect to the remote device 102 through the Dv kit 201b. After the local device 101 establishes a connection with the remote device 102, the local device 101 may create a DMSDP HAL 202b for the remote device 102 in the HAL 202 of the local device 101. Then the remote device 102 can be registered with the local device 101 . The DMSDP HAL 202b shown in FIG. 2E is the HAL created by the local device 101 according to the shooting capability parameters of the remote device 102 .

The remote device 102 may also include a Dv application and a Dv kit. For the functions of the Dv application and the Dvkit in the remote device 102, reference may be made to the description of the functions of the Dv application 200a and the Dv kit 201b in the embodiments of the present application, which will not be repeated here.

Still as shown in FIG. 2E, in addition to creating the corresponding DMSDP HAL 202b for the remote device 201 in the HAL 202, the shooting capability parameters of the remote device 102 can also be sent to the Camera Service 201a1 for saving, that is, in the Camera Service In 201a1, the current shooting capability parameters of the remote device 102 (including device capability information and algorithm capability information) are registered. The device capability information is used to indicate the hardware capability of the remote device 102 to capture images, and the algorithm capability information is used to indicate the algorithm capability of the remote device 102 to perform image processing on the captured images. The capability information of the remote device 102 can be registered or mapped to the Camera Service 201a1 through the DMSDP HAL 202b. Further, the "peer Meta synchronization mapping" function can also be set in the DMSDP HAL 202b. The peer Meta refers to a tag in the remote device 102 that is used to indicate the shooting capability parameter of the remote device 102 .

It should be noted that the DMSDP HAL 202b may also be called a virtual Camera HAL or a DMSDP CameraHAL. Different from the traditional Camera HAL, the DMSDP HAL 202b does not correspond to the actual hardware device of the local device 101 , but corresponds to the remote device 102 . As shown in FIG. 2F , the remote device 102 (eg, a device including a camera such as a TV, a tablet computer, a mobile phone, etc.) can be used as a virtual camera of the local device 101 . The local device 101 (the virtual frame shown in FIG. 2F ) can send and receive data with the remote device 102 through the DMSDP HAL 202b, and the remote device 102 is used as a virtual camera of the local device 101 to communicate with the remote device 102. Collaborate to complete various businesses in distributed shooting scenarios.

In some embodiments, the Dv application 200a of the local device 101 can also obtain the audio capability parameters (such as audio playback delay, audio sampling rate or number of sound channels, etc.), display capability parameters ( such as screen resolution, codec algorithm for display data, etc.). Of course, if the remote device 102 also has other capabilities (such as printing capabilities, etc.), the remote device 102 can also send the relevant capability parameters to the Dv application 200a of the local device 101 . At this time, the DMSDP HAL 202b not only has the image processing capability of the remote device 102, but also has the audio and display capabilities of the remote device 102, so that the remote device 102 can act as a virtual device of the local device 101 to cooperate with the local device 101 Complete various businesses in distributed scenarios.

Different from the solution shown in FIG. 2D , after the local device 101 establishes the connection with the remote device 102 , two camera sessions (Camera Sessions) can be created respectively. For example, the local device 101 may create a control session (Control Session) for transmitting a control stream and a data session (Data Session) for transmitting a data stream (ie, a preview stream) through the DMSDP HAL 202b.

Among them, in addition to creating the corresponding DMSDP HAL 202b for the remote device 102 in the HAL, the shooting capability parameters of the remote device 102 can also be sent to the Camera Service 201a1 for saving, that is, the current remote device is registered in the CameraService 201a1. 102 shooting capability.

When the mobile phone runs the camera application, the Camera Service 201a1 can determine the shooting strategy in the shooting process in real time according to the control commands (such as preview, zoom, video, etc.) issued by the camera application, combined with the shooting capability of the remote device 102 . For example, the Camera Service can set the image processing tasks that the mobile phone needs to perform and the image processing tasks that the remote device 102 needs to perform in the shooting policy according to the shooting capability parameters of the slave device. Furthermore, the CameraService can use the DMSDP HAL 202b to send a shooting instruction corresponding to the shooting strategy to the remote device 102 through the Control Session, and trigger the remote device 102 to perform the corresponding image processing task.

After that, after the shooting instruction is transmitted to the Camera HAL 212a of the remote device 102, the Camera HAL 212a of the remote device 102 can call the camera driver in the kernel layer according to the received shooting instruction, and drive hardware devices such as the camera to respond to the shooting instruction to collect image data. For example, the camera can transmit each frame of image data collected to the Camera HAL through the camera driver at a certain frame rate.

After receiving each frame of image data collected by the camera, the Camera HAL 212a of the remote device 102 transmits a data stream including the RAW image collected by the camera to the upper layer. Wherein, after the application layer 210 of the remote device 102 receives the data stream including the RAW image, the camera proxy service 210a (or also referred to as the camera proxy application) of the application layer 210 can send the data stream including the RAW image to the local device 101 through the DMSDP HAL 202b. Data stream of RAW images. For example, the camera proxy service 210a may send a data stream including RAW images to the local device 101 through the Data Session provided by the DMSDP HAL 202b.

After receiving the data stream including the RAW image, the DMSDP HAL 202b of the local device 101 can call the relevant algorithm to perform post-processing (algorithm) according to the shooting capability parameters saved in the CameraService 201a1, perform image processing on the RAW image, and obtain each corresponding RAW image. frame the shot screen. Subsequently, the DMSDP HAL 202b can report each frame of the captured image after image processing to the camera application through the Camera Service 201a1, and the camera application can display each frame of the captured image on the display interface.

In this way, when the local device 101 and the remote device 102 implement the distributed shooting function, the local device 101 can perform corresponding processing on the image data according to its own shooting capabilities and the shooting capabilities of the remote device 102 based on the above shooting strategy. Image processing to achieve better shooting results in distributed shooting scenes.

In some embodiments, the local device 101 may also send the RAW image collected by the local device 101 to the remote device 102 . The camera service 211a1 of the remote device 102 may also save the shooting capability parameters of the local device 101. The remote device 102 may also call a related algorithm according to the shooting capability parameter of the local device 101 to perform image processing on the RAW image from the local device 101 to obtain each corresponding frame of shooting images. The remote device 102 may call a related algorithm according to the shooting capability parameter of the remote device 102 to perform image processing on the RAW image collected by the remote device 102 to obtain each corresponding frame of shooting images. In this way, the far-end device 102 can also display the photographing picture of the local device 101 and the photographing picture of the far-end device 102 at the same time. With this solution, the above-mentioned distributed shooting function across devices can be implemented on the local device 101 and the remote device 102 at the same time.

The following examples illustrate application scenarios of the methods provided by the embodiments of the present application. The methods of the embodiments of the present application may be applicable to at least the following application scenarios (1)-application scenarios (2).

Application Scenario (1): Cross-device multi-shot shooting scenario.

For example, the cross-device multi-scene shooting scene may be a cross-device dual-scene shooting scene. The cross-device dual-view shooting scene may include a cross-device dual-view photography scene and a cross-device dual-view video recording scene. In the following embodiments, the cross-device dual-view shooting scene is taken as an example to introduce the cross-device dual-view shooting scene.

Exemplarily, the above-mentioned preset application may be a camera application for implementing a shooting function. Taking mobile phone 0 as the terminal device 101 as an example, a camera application may be installed in mobile phone 0 . The mobile phone 0 (ie, the local device 101 ) can perform cross-device multi-view shooting with the remote device 102 through the camera application. As shown in FIG. 3A , after detecting that the user has opened the camera application, the mobile phone 0 can open its own camera to start collecting image data, and display the corresponding shooting image in the preview frame 302 of the preview interface 301 in real time according to the collected image data.

Wherein, the shooting picture displayed by the mobile phone 0 in the preview frame 302 may be different from the image data collected by the mobile phone 0 using the camera. For example, after the mobile phone 0 obtains the image data collected by the camera, it can perform image processing tasks such as anti-shake, focus, soft focus, blur, filter, beauty, face detection, or AR recognition on the collected image data, and obtain The captured image after image processing. Furthermore, the mobile phone 0 may display the image-processed shooting screen in the above-mentioned preview frame 302 .

Similarly, the remote device 102 can also turn on its own camera to start collecting image data, and perform anti-shake, focus, soft focus, blur, filter, beauty, face detection or AR recognition on the collected image data, etc. The image processing task is to obtain a photographed picture after image processing, which is not limited in this embodiment of the present application.

In this embodiment of the present application, as shown in FIG. 3A , the mobile phone 0 may set a function button 303 for cross-device multi-view shooting in the preview interface 301 of the camera application. When the user wants to see the multi-scene pictures shot by the mobile phone 0 and the remote device 102 on the mobile phone 0, the user can click the function button 303 to enable the cross-device multi-scene shooting function.

Alternatively, the mobile phone 0 may also set the function button 304 of the synchronous shooting function in the control center, pull-down menu, negative screen, or other applications (eg, video calling application) of the mobile phone, which is not limited in this embodiment of the present application. For example, as shown in FIG. 3B , the mobile phone can display the control center 305 in response to the user's operation of opening the control center, and the control center 305 is provided with the above-mentioned function buttons 304 . If the user wishes to use the mobile phone and other electronic devices to shoot synchronously, the user can click the function button 304 .

Exemplarily, after the mobile phone 0 detects that the user clicks the function button 303 and the function button 304, as shown in FIG. 4, the mobile phone 0 can display one or more candidate devices that can collect image data currently searched by the mobile phone 0 in the dialog box 401. .

For example, whether each electronic device has a shooting function can be recorded in the cloud server. Then, the mobile phone 0 can query the cloud server for an electronic device with a photographing function that is logged into the same account (eg, a Huawei account) as the mobile phone 0 . Furthermore, the mobile phone 0 may display the queried electronic device as a candidate device in the dialog 401 .

Alternatively, mobile phone 0 can search for electronic devices located in the same Wi-Fi network as mobile phone 0 . Furthermore, the mobile phone 0 can send a query request to each electronic device in the same Wi-Fi network, and the electronic device triggered to receive the query request can send a response message to the mobile phone 0, and the response message can indicate whether it has a shooting function. Then, the mobile phone 0 can determine, according to the received response message, an electronic device with a photographing function in the current Wi-Fi network. Furthermore, the mobile phone 0 can display the electronic device with the photographing function as a candidate device in the dialog 401 .

Alternatively, an application for managing smart home devices in the home (such as a TV, an air conditioner, a speaker, a refrigerator, etc.) may be installed in the mobile phone 0 . Taking a smart home application as an example, the user can add one or more smart home devices in the smart home application, so that the smart home device added by the user is associated with the mobile phone 0 . For example, a two-dimensional code containing device information such as device identification can be set on the smart home device. After the user scans the two-dimensional code with the smart home application of the mobile phone 0, the corresponding smart home device can be added to the smart home application, thereby establishing The association between smart home devices and mobile phone 0. In this embodiment of the present application, when one or more smart home devices added in the smart home application go online, for example, when the mobile phone 0 detects the Wi-Fi signal sent by the added smart home device, the mobile phone 0 can use the smart home device. The home device is displayed in the dialog 401 as a candidate device, and the user is prompted to choose to use the corresponding smart home device to shoot synchronously with the mobile phone 0 .

As shown in FIG. 4 , the candidate devices searched by mobile phone 0 include TV 1, watch 2 and mobile phone 3 as an example, the user can select from TV 1, watch 2 and mobile phone 3 to perform cross-device multi-view shooting with mobile phone 0 this time. One or more remote devices 102 . In the embodiments of the present application, cross-device dual-view shooting is used as an example. For example, if it is detected that the user selects the TV 1, the mobile phone 0 can use the TV 1 as the remote device 102 to establish a network connection with the TV 1. For example, mobile phone 0 can establish a Wi-Fi connection with TV 1 through a router, or mobile phone 0 can directly establish a Wi-Fi P2P connection with TV 1, or mobile phone 0 can directly establish a Bluetooth connection with TV 1; Establish a Bluetooth connection with the TV 1; or, the mobile phone 0 can directly establish a short-range wireless connection with the TV 1, and the short-range wireless connection includes but is not limited to a near field communication (Near Field Communication, NFC) connection, an infrared connection, an ultra-wideband (Ultra Wideband, UWB) connection, ZigBee protocol (ZigBee) connection; or, mobile phone 0 can directly establish a mobile network connection with TV 1, the mobile network including but not limited to supporting 2G, 3G, 4G, 5G and subsequent standard protocols mobile networks.

In other embodiments, after the mobile phone 0 detects that the user clicks the function button 303, the mobile phone can search for one or more electronic devices with a photographing function according to the above method. Furthermore, the mobile phone 0 can automatically establish a network connection with the searched electronic device. At this time, the user does not need to manually select a specific device for establishing a network connection with the mobile phone 0 .

Alternatively, before the user opens the camera application, the mobile phone may have established a network connection with one or more electronic devices having a photographing function. For example, before the user opens the camera application in phone 0, a Bluetooth connection has been established with the tablet. Subsequently, after the mobile phone 0 opens the camera application to display the preview interface 301 of the camera application, if it is detected that the user clicks the function button 303, the mobile phone 0 can no longer search for an electronic device with a shooting function, but execute the following method.

After the mobile phone 0 establishes a network connection with the TV 1, on the one hand, as shown in FIG. On the other hand, as shown in FIG. 5 , the mobile phone 0 can instruct the TV 1 to turn on its own camera to start collecting image data, and perform image processing on the collected image data to obtain the shooting picture 2 . Subsequently, the TV 1 can send the captured image 2 to the mobile phone 0 . In this way, the mobile phone 0 can simultaneously display the shooting picture 1 from the mobile phone 0 and the shooting picture 2 from the TV 1 on the display interface of the camera application.

As described in the above embodiment, in the first case of the application scenario (1), in the above-mentioned cross-device multi-view shooting scenario, multiple cameras can be used to achieve multi-view shooting of the same shooting object, which can improve the fun of shooting sex.

In the second case of application scenario (1), in the above-mentioned cross-device multi-scene shooting scenario, multiple cameras can also be used to achieve co-shooting of multiple subjects (such as parent-child co-shooting or friends co-shooting, etc.). For example, it is assumed that the local device 101 is the mobile phone 0 shown in FIG. 5 , and the remote device 102 is the mobile phone 3 shown in FIG. 6A . Wherein, the mobile phone 0 or the mobile phone 3 may use the above-mentioned preset application (such as a camera application or other applications that can be used to realize photo or video shooting) to realize the combined shooting of multiple shooting objects.

For example, it is assumed that the preset application is a camera application. When the user wants to see the co-photographing screen of the mobile phone 0 and the mobile phone 3 on the mobile phone 0, the user can click the function button 303 or the function button 304 to enable the cross-device multi-view co-photography function.

Exemplarily, after the mobile phone 0 detects that the user clicks the function button 303 or the function button 304, as shown in FIG. 4, the mobile phone 0 can display one or more candidate devices that can collect image data currently searched by the mobile phone 0 in the dialog box 401. . As shown in FIG. 4 , the candidate devices searched by mobile phone 0 include TV 1, watch 2 and mobile phone 3 as an example, the user can select from TV 1, watch 2 and mobile phone 3 to perform cross-device multi-scene co-photography with mobile phone 0 this time. Remote device 102 . For example, if it is detected that the user selects the mobile phone 3, the mobile phone 0 can use the mobile phone 3 as the remote device 102 to establish a network connection with the mobile phone 3.

After the mobile phone 0 and the mobile phone 3 establish a network connection, on the one hand, as shown in FIG. On the other hand, as shown in FIG. 6A , the mobile phone 0 may instruct the mobile phone 3 to turn on its own camera to start collecting image data, and perform image processing on the collected image data to obtain a shooting picture 3 . Subsequently, the mobile phone 3 may send the captured image 3 to the mobile phone 0 . In this way, the mobile phone 0 can simultaneously display the shooting screen 1 from the mobile phone 0 and the shooting screen 3 from the mobile phone 3 on the display interface of the camera application.

It should be noted that, different from the first situation above, in the process of performing cross-device multi-scene co-photography, the mobile phone 0 can send the photographed image 1 to the mobile phone 3 . As shown in FIG. 6A , the mobile phone 3 can also display the shooting screen 1 from the mobile phone 0 and the shooting screen 3 from the mobile phone 3 at the same time. At this time, the mobile phone 0 can be used as the local device and the remote device at the same time. Specifically, the mobile phone 0 is used as the local device, and the mobile phone 3 is used as the remote device. The mobile phone 3 is used as the local device, and the mobile phone 0 is used as the remote device.

It should be noted that the above-mentioned cross-device multi-view shooting scenario may be a scenario in which at least two devices perform cross-device multi-view shooting. Exemplarily, three electronic devices may also apply the method of the embodiment of the present application to realize the cross-device multi-scene shooting function. For example, the mobile phone 0 shown in FIG. 6B can be used as the local device, and the mobile phone 3 and the TV 1 can be used as the remote devices; the mobile phone 0 and the mobile phone 3 and the TV 1 can realize cross-device multi-view shooting. As shown in FIG. 6B , the mobile phone 0 can simultaneously display the shooting picture 1 from the mobile phone 0 , the shooting picture 3 from the mobile phone 3 , and the shooting picture 2 from the TV 1 .

Application scenario (2): a scenario in which the local device 101 calls the remote device 102 to perform a video call, live broadcast, photograph or record. Wherein, the local device 102 can call the camera of the remote device 102, or the camera and display screen of the remote device 102, to assist the local device 101 to make a video call, live broadcast, take pictures or record videos.

Exemplarily, in this embodiment of the present application, the application scenario (2) is introduced by taking the local device 101 calling the remote device 102 for a video call as an example. The above-mentioned preset application may be a video communication application (such as a WeChat TM application) for implementing a video call. Taking the mobile phone 0 as the end device 101 and the TV 1 as the remote device 102 as an example, the mobile phone 0 may have the above video communication application installed.

In an implementation manner, the mobile phone 0 can call the camera and display screen of the remote device 102 (such as the TV 1 ) during the video call with the mobile phone 4 to assist the mobile phone 0 and the mobile phone 4 in the video call. For example, as shown in FIG. 7 , the mobile phone 0 displays a video call interface 701 , and the video call interface 701 is provided with a function button 702 for calling other devices to assist the mobile phone 0 to make a video call. When the user wants the mobile phone 0 to call other devices to assist the mobile phone 0 to make a video call, the user can click the function button 702 .

In another implementation manner, the mobile phone 0 may call the camera and display screen of the remote device 102 (such as the TV 1 ) before requesting the video call with the mobile phone 4 to assist the mobile phone 0 to conduct the video call with the mobile phone 4 . For example, as shown in FIG. 8, in response to the user's click operation on the "video call" option 801 in the chat interface, the mobile phone 0 may display a confirmation window 802, which is used to request the user to confirm whether to use the large screen to assist the mobile phone to make voice calls call. When the user wants the mobile phone 0 to call other devices to assist the mobile phone 0 to make a video call, the user can click the “Yes” button in the confirmation window 802 .

Exemplarily, after detecting that the user clicks the function button 702 or the “Yes” button in the confirmation window 802, the mobile phone 0 can search for candidate devices. A dialog box 401 as shown in FIG. 4 may be displayed. The specific method for the mobile phone to search for candidate devices and display the dialog box 401 may refer to the detailed description in the above-mentioned embodiment, which will not be repeated here.

When the mobile phone 0 detects that the user selects the TV 1, the mobile phone 0 can use the TV 1 as the remote device 102 to establish a network connection with the TV 1. After the mobile phone 0 establishes a network connection with the TV 1, on the one hand, as shown in FIG. On the other hand, as shown in FIG. 9 , the mobile phone 0 can instruct the TV 1 to turn on its own camera to start collecting image data, and perform image processing on the collected image data to obtain a shooting picture c. Subsequently, the TV 1 can send the shooting picture c to the mobile phone 0 , and the mobile phone 0 transmits the shooting picture c to the mobile phone 4 . In this way, the TV 1 can simultaneously display the shooting screen b from the mobile phone 4 and the shooting screen c from the TV 1 ; the mobile phone 4 can also simultaneously display the shooting screen c from the TV 1 and the shooting screen b from the mobile phone 4 .

In other embodiments, the mobile phone 0 calls the camera and display screen of the TV 1 to assist the mobile phone 0 to conduct a video call with the mobile phone 4, and the mobile phone 0 can also display the shooting screen b from the mobile phone 4 and/or the shooting from the TV 1. screen c.

Alternatively, the mobile phone 0 may call the camera and the display screen of the TV 1 to assist the mobile phone 0 to conduct a video call with the mobile phone 4, and the mobile phone 0 may display a preset interface. The preset interface may be the main interface 901 shown in FIG. 9 . Alternatively, the preset interface may also be a preset picture or a preset animation or the like.

Alternatively, when mobile phone 0 invokes the camera and display screen of TV 1 to assist mobile phone 0 to conduct a video call with mobile phone 4, mobile phone 0 may have a black screen. In this way, the power consumption of the mobile phone 0 can be reduced.

It should be noted that since the shooting angles of the mobile phone 0 and the TV 1 are different, the shooting picture of the mobile phone 0 may be different from that of the TV 1 . For example, the shooting screen a shown in FIG. 7 is shot by the mobile phone 0, the shooting screen c shown in FIG. 9 is shot by the TV 1, and the shooting screen a is different from the shooting screen c.

In any of the above application scenarios, the local device 101 can use and control the camera of the remote device 102, and use the camera of the remote device 102 to assist the local device 101 to complete shooting tasks, video tasks or other related tasks. Of course, the remote device 102 can also use and control the camera of the local device 101, and use the camera of the local device 101 to assist the remote device 102 to complete the above tasks. For example, as shown in FIG. 6A , the mobile phone 3 can also simultaneously display the shooting screen 1 from the mobile phone 0 and the shooting screen 3 from the mobile phone 3 .

In this embodiment of the present application, the local device 101 and the remote device 102 may perform shooting in a distributed shooting scenario (eg, multi-scene shooting). In the following embodiments, the methods of the embodiments of the present application are described in detail by taking the local device 101 as a mobile phone as an example.

For example, as shown in the above embodiment, the local device 101 (eg, a mobile phone) can provide a dual-view mode (including a dual-view camera mode and a dual-view video mode). As shown in FIG. 10 , a function button 1001 and a function button 1002 for cross-device multi-view shooting can be set in the preview interface of the camera application on the mobile phone. Specifically, the function button 1001 is used to trigger the mobile phone to enter the multi-view photographing mode. The function button 1002 is used to trigger the mobile phone to enter the multi-view recording mode. When the user wants to see the multi-scene pictures shot by the mobile phone and the remote device 1002 on the mobile phone, the user can click the function button 1001 or the function button 1002 to enable the cross-device multi-scene shooting function. In this embodiment of the present application, the user's click operation on the function button 1001 , the function button 1002 , or the function button 303 is the second operation.

Exemplarily, after the mobile phone detects that the user clicks the above function button 1001, a preset application of the mobile phone (such as a camera application) may trigger the mobile phone to search for one or more nearby candidate devices with a shooting function. For example, the preset application of the mobile phone can discover (ie search) one or more candidate devices with a shooting function through the Dv kit.

And, as shown in FIG. 11 , the mobile phone can display one or more candidate devices found in the dialog box 1101 . For example, the mobile phone may query the server for an electronic device that is logged in to the same account as the mobile phone and has a photographing function, and displays the electronic device as a candidate device in the dialog 1101 . In this embodiment of the present application, the user's click operation on a candidate device in the dialog box 1101 and the dialog box 401 (also referred to as a candidate device list) is the first operation.

For example, the candidate devices in the dialog 1101 include the TV 1102 , the TV 1103 and the watch 1104 , the user can select the remote device in the dialog 1101 that cooperates with the mobile phone to realize the synchronous shooting function this time. For example, if the mobile phone detects that the user selects the TV 1102 in the dialog 1101, it means that the user wishes to use the mobile phone and the TV 1102 to shoot at the same time. At this time, the Dv kit of the mobile phone can use the TV 1102 as a remote device of the mobile phone to establish a network connection with the mobile phone.

After the mobile phone establishes a network connection with the TV 1102, the TV 1102 can be registered in the HAL of the mobile phone. Specifically, the mobile phone can obtain the shooting capability parameters of the TV 1102 from the TV 1102 based on the network connection; and create a corresponding DMSDP HAL in the HAL according to the shooting capability parameters of the TV 1102 .

Among them, the shooting capability parameter of the TV 1002 is used to reflect the specific shooting capability of the TV 1102 . The shooting capability parameter may include device capability information. The device capability information is used to indicate the hardware capability of the TV 1102 to capture images. For example, the device capability information may indicate parameters such as the number of cameras in the TV 1102, the resolution of the cameras, or the model of the image processor. The device capability information can be used by the mobile phone to determine the shooting strategy of the TV 1102 .

The above-mentioned shooting capability parameters of the TV 1102 may be stored in the Camera Service of the mobile phone. Exemplarily, the shooting capability parameters of the TV 1102 may be stored in the Camera Service of the mobile phone in the form of a tag.

In this embodiment of the present application, the device capability information is used as an example to introduce the storage format of the shooting capability parameter of the TV 1102 in the Camera Service of the mobile phone. For example, please refer to FIG. 12 , which shows a schematic diagram of a format of the device capability information of the TV 1102 stored in the CameraService of the mobile phone in the embodiment of the present application.

The three-layer data structure shown in FIG. 12 can be used in the Camera Service of the mobile phone to store the device capability information of the TV 1102 . Among them, the mobile phone can store the capability information of each device of the TV 1102 in segments in the Camera Service. The Section_name shown in FIG. 12 is the storage address of the TV 1102; the Tag_name is the multiple Tag names under one address of the Section_name; and the Tag_index is the index of the capability information of the Tag name. The index is used to indicate the storage address of specific capability information.

For example, the device capability information of the TV 1102 may include five Section_names shown in FIG. 12 : com.huawei.capture.metadata; com.huawei.device.capabilities; android.huawei.device.parameters; android.huawei.stream.info ; android.huawei.stream.parameters.

Take a Section_name (such as com.huawei.device.capabilities) shown in FIG. 12 as an example. As shown in FIG. 12 , the device capability information of the TV 1102 may further include: Tag names of multiple tags stored in the storage address corresponding to the Section_name, such as device_sensor_position, hidden_camera_id, colerBarCheckUnsupport, amoothZoomSupport, and tofType. For example, device_sensor_position represents the sensor of the camera of TV 1102 .

Take a Tag name shown in Figure 12 as an example. As shown in FIG. 12 , the device capability information of the TV 1102 may further include: an index of the capability information of the tag name, such as CAMERA_HUAWEI_DEVICE_CAPABILITIES_START and CAMERA_HUAWEI_DEVICE_CAPABILITIES_END.

Among them, CAMERA_HUAWEI_DEVICE_CAPABILITIES_START may indicate the starting address of the capability information of a Tag name stored in the TV 1102 . CAMERA_HUAWEI_DEVICE_CAPABILITIES_END may indicate the end address of the capability information in which a Tag name is stored in the TV 1102 . According to the starting address and ending address, the mobile phone can query the TV 1102 for various device capabilities of the TV 1102 .

It should be understood that, as shown in FIG. 13 , the TAG (ie, the above-mentioned shooting capability parameter) stored in the Camera Service can be combined with the post-processing (algorithm) module in the mobile phone to process the RAW image returned by the TV 1102 . The specific method for the mobile phone to process the RAW image returned by the TV 1102 according to the above TAG combined with the post-processing (algorithm) module is described in detail in the following embodiments, and will not be repeated here.

Subsequently, when the mobile phone is running the camera application, on the one hand, it can call its own camera to obtain each frame of the shot, on the other hand, the mobile phone can instruct the TV 1102 to obtain RAW images, and send the obtained RAW images to the mobile phone through the DMSDP HAL 202b camera application. Among them, the mobile phone can call its own camera to acquire each frame of shooting images according to a certain frame rate, and instruct the TV 1102 to acquire RAW images according to the same frame rate.

The mobile phone can send a shooting instruction to the TV 1102 through the DMSDP HAL to instruct the TV 1102 to obtain a RAW image. For example, as shown in FIG. 13 , the application layer 200 of the mobile phone can transmit the shooting instruction to the DMSDP HAL 202b of the HAL 202 through the framework layer 201 and the service layer 201a; the DMSDP HAL 202b of the HAL 202 can perform step a to transmit the shooting instruction to the TV 1102. After the TV 1102 receives the shooting instruction transmitted by the mobile phone through the DMSDP HAL 202b, the camera proxy service 210a of the application layer 210 can add a preset mark to the shooting instruction. The preset flag is used to instruct to directly acquire the RAW data collected by the underlying Camera device, and transparently transmit the RAW data to the camera proxy service 210a of the application layer 211 . For example, as shown in FIG. 13, the camera proxy service 210a of the application layer 210 may add a preset mark to the shooting instruction, and transmit the preset mark to the Camera HAL 212a in the HAL 212 through the framework layer 211 and the service layer 211a. shooting order. After the Camera HAL 212a in the HAL 212 receives the shooting instruction, it can call the Camera device of the kernel layer 213 to execute the shooting instruction. For example, the Camera HAL 212a in the HAL 212 can call the Camera device in the kernel layer 213 to collect RAW images, and perform step b to transparently transmit the RAW data to the camera proxy service 210a of the application layer 211 . Then, step c is performed by the camera proxy service 210a of the application layer 211 to transmit the RAW image to the DMSDP HAL 202b of the mobile phone.

Wherein, the Camera device of the core layer 213 may include a photosensitive device, a digital signal processor (DSP) and an image processor (ISP) as shown in FIG. 14 . The photosensitive device may include a lens, a sensor, and the like. This sensor is used to capture RAW images. A digital signal processor (DSP) is used to perform sampling processing on the multi-frame RAW images collected by the photosensitive device; then, the sampled RAW images are transmitted to an image processor (ISP). In general, an image processor (ISP) can perform image processing on RAW images from the DSP. However, in this embodiment of the present application, the ISP does not perform image processing on the RAW image from the DSP, but transparently transmits the RAW image from the DSP to the Camera HAL 212a in the HAL 212 .

It should be noted that the step b in FIG. 13 directly points from the kernel layer 213 to the application layer 210, just to illustrate that the mobile phone will not perform image processing on the RAW image, and does not mean that the RAW image does not pass through the Camera HAL212a, the service in the HAL 212, and the The layer 211a and the framework layer 211 can be directly transferred from the kernel layer 213 to the application layer 210 . The RAW image collected by the Camera device in the kernel layer 213 needs to be transmitted to the application layer 210 through the Camera HAL 212a , the service layer 211a and the framework layer 211 in the HAL 212 . However, as shown in FIG. 14 , the Camera HAL 212a, the service layer 211a, and the framework layer 211 in the HAL 212 can only transparently transmit the RAW image without performing any processing on the RAW image.

In this embodiment of the present application, what the TV 1102 transmits to the mobile phone is not a processed image that can be directly displayed, but a RAW image without image processing. After the TV 1102 uses the camera to capture the RAW image, it can directly transmit the RAW image to the mobile phone without performing image processing on the RAW image. This RAW image is an image that has not been processed by the television 1102 . The data volume of the RAW image is smaller than that of the image processed by the TV 1102 . In this way, the network bandwidth occupied by the distributed shooting service across the devices can be reduced.

Then, the mobile phone can perform image processing on the RAW image from the TV 1102 to obtain a corresponding shooting picture. In this way, the camera application of the mobile phone can not only acquire each frame of the photographed image from the mobile phone, but also can acquire each frame of the photographed image of the TV 1102 . Furthermore, the camera application can synchronously display the photographed image of the mobile phone and the photographed image of the TV 1102 on the display interface of the camera application, so as to realize a distributed photographing function across devices. For example, as shown in FIG. 15 , the preview interface of the camera application of the mobile phone includes the shooting screen 1501 of the mobile phone and the shooting screen 1502 of the TV 1102 .

Among them, the mobile phone processes the RAW image from the TV 1102, which can avoid the problem of increasing the time delay due to the large difference in the performance of the devices at both ends. With this solution, the time delay of the distributed shooting service can be reduced.

In addition, in this embodiment of the present application, after the mobile phone and the TV 1102 are connected, two camera sessions (Camera Sessions) can be created based on the DMSDPHAL 202b shown in FIG. Session (Control Session) and Data Session (DataSession) for transferring data streams (such as the above-mentioned RAW data). Among them, Control Session and Data Session may correspond to different transmission paths (or called transmission pipes). The DMSDP HAL 202b of the mobile phone performs step a shown in FIG. 13 , and can transmit the shooting instruction to the camera proxy service 210a of the TV 1102 through the transmission pipeline of the above-mentioned Control Session. The camera proxy service 210a of the TV 1102 executes step c shown in FIG. 13, and can transmit a data stream (such as the above-mentioned RAW data) to the DMSDP HAL 202b of the mobile phone through the transmission pipeline of the above-mentioned Data Session.

Among them, in the process of the mobile phone and the TV 1102 executing the distributed shooting service across the devices, the transmission paths of the control flow and the data flow can be distinguished. In this way, the problem that the control flow and the data flow mutually occupy the bandwidth can be avoided.

In some embodiments, the above-mentioned shooting capability parameters of the television 1102 may further include algorithm capability information. The algorithm capability information is used to indicate the algorithm capability of the television 1102 to perform image processing on the captured image. For example, the algorithm capability information may indicate one or more image processing algorithms such as a face recognition algorithm, an auto-focus algorithm, etc. supported by the TV 1102 . That is to say, the mobile phone can also synchronize the post-processing algorithm of the TV 1002 to the mobile phone. For example, as shown in FIG. 13 , the post-processing algorithm of the TV set 1102 is reserved in the service layer 201a of the mobile phone.

In this embodiment, the service layer 201a of the mobile phone can call the reserved post-processing algorithm of the TV 1102 based on the algorithm capability information of the TV 1102 to perform image processing on the RAW image from the DMSDP HAL 202b. Afterwards, the mobile phone can synchronously render the image collected by the mobile phone and the post-processed image from the TV 1102 based on the time stamp to obtain and display the shooting screen 1501 of the mobile phone and the shooting screen 1502 of the TV 1102 shown in FIG. 15 .

It should be noted that, based on the algorithm capability information of the TV 1102, the mobile phone calls the reserved post-processing algorithm of the TV 1102 to perform image processing on the RAW image collected by the TV 1102. similar effect.

Wherein, even if the RAW image collected by the TV 1102 is processed on the mobile phone side; however, the image processed by the image can also achieve the same effect as the image processing on the TV 1102 side. That is to say, by using the method of the embodiment of the present application, not only the network bandwidth occupied by the distributed shooting service across the devices can be reduced, but also the image effect of the remote device can be restored.

In other embodiments, the above-mentioned shooting capability parameters of the television 1102 may not include algorithm capability information. That is, the mobile phone does not need to synchronize the post-processing algorithm of the TV 1002 to the mobile phone. For example, as shown in FIG. 16, the post-processing algorithm of the television 1102 is not reserved in the service layer 201a of the mobile phone.

In this embodiment, the service layer 201a of the mobile phone may call the post-processing algorithm of the mobile phone based on the algorithm capability information of the mobile phone to perform image processing on the RAW image from the DMSDP HAL 202b. Afterwards, the mobile phone can synchronously render the image collected by the mobile phone and the post-processed image from the TV 1102 based on the time stamp to obtain and display the shooting screen 1501 of the mobile phone and the shooting screen 1502 of the TV 1102 shown in FIG. 15 .

It should be noted that the mobile phone calls the mobile phone's post-processing algorithm to process the RAW images collected by the TV 1102, although the effect of image processing on the TV 1102 side cannot be restored; however, for the images collected by the mobile phone and the RAW images collected by the TV 1102, Both call the post-processing algorithm of the mobile phone to perform image processing, so that the image effects of the photographed image of the mobile phone and the photographed image of the TV 1102 can be consistent.

In addition, when the algorithm processing capability of the mobile phone is better than the algorithm processing capability of the TV 1102, compared with calling the post-processing algorithm of the TV 1102 to perform image processing on the RAW image collected by the TV 1102, calling the post-processing algorithm of the mobile phone for the RAW image. Performing image processing on the image can also improve the image effect of the captured image of the TV 1102 displayed by the mobile phone.

Further, the post-processing algorithm of the mobile phone is used to perform image processing on the RAW image collected by the TV 1102, and the post-processing algorithm of the TV 1102 does not need to be retained in the mobile phone. In this way, the storage space of the phone can be saved.

In addition, in the above embodiment, the mobile phone is used as an example for the local device in the distributed shooting scene. It can be understood that the local device in the distributed shooting scene can also be a tablet computer, a TV, etc. with the above shooting functions. An electronic device, this embodiment of the present application does not impose any limitation on this.

It should be noted that, in the above embodiment, the Android system is used as an example to illustrate the specific method for realizing the distributed shooting function among the various functional modules. It can be understood that corresponding functional modules can also be set in other operating systems to realize the above-mentioned method. As long as the functions implemented by various devices and functional modules are similar to the embodiments of the present application, they fall within the scope of the claims of the present application and their technical equivalents.

In the embodiment of the present application, the image data collected by the local device 101 is the first image data, and the shooting picture of the local device 101 is the first shooting picture, and the first shooting picture is displayed in the first window. The image data collected by the remote device 102 is the second image data, the shooting picture of the remote device 102 is the second shooting picture, and the second shooting picture is displayed in the second window. The above-mentioned second image data includes a RAW image.

For example, the first photographing picture may be the photographing picture 1 shown in FIG. 5 , and the second photographing picture may be the photographing picture 2 shown in FIG. 5 . The shooting screen 1 and the shooting screen 2 shown in FIG. 5 are displayed on the same display interface.

For another example, the first photographing picture may be the photographing picture 1 shown in FIG. 6A , and the second photographing picture may be the photographing picture 3 shown in FIG. 6A . The shooting screen 1 and the shooting screen 2 shown in FIG. 6A are displayed on the same display interface on both the mobile phone 0 and the mobile phone 1 .

Other embodiments of the present application provide an electronic device, and the electronic device may include: the above-mentioned touch screen, a memory, and one or more processors. The touch screen, memory and processor are coupled. The memory is used to store computer program code comprising computer instructions. When the processor executes the computer instructions, the electronic device can execute each function or step executed by the mobile phone in the foregoing method embodiments. For the structure of the electronic device, reference may be made to the structure of the mobile phone shown in FIG. 2B .

An embodiment of the present application further provides a chip system. As shown in FIG. 17 , the chip system 1700 includes at least one processor 1701 and at least one interface circuit 1702 . The processor 1701 and the interface circuit 1702 may be interconnected by wires. For example, the interface circuit 1702 may be used to receive signals from other devices, such as the memory of an electronic device. As another example, the interface circuit 1702 may be used to send signals to other devices (eg, the processor 1701). Exemplarily, the interface circuit 1702 can read the instructions stored in the memory and send the instructions to the processor 1701 . When the instructions are executed by the processor 1701, the electronic device can be caused to perform the various steps in the above-mentioned embodiments. Certainly, the chip system may also include other discrete devices, which are not specifically limited in this embodiment of the present application.

Embodiments of the present application further provide a computer storage medium, where the computer storage medium includes computer instructions, when the computer instructions are executed on the above-mentioned electronic device, the electronic device is made to perform various functions or steps performed by the mobile phone in the above-mentioned method embodiments .

Embodiments of the present application further provide a computer program product, which, when the computer program product runs on a computer, enables the computer to perform various functions or steps performed by the mobile phone in the above method embodiments.

From the description of the above embodiments, those skilled in the art can clearly understand that, for the convenience and brevity of the description, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions can be allocated by Different functional modules are completed, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be Incorporation may either be integrated into another device, or some features may be omitted, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place, or may be distributed to multiple different places . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, which are stored in a storage medium , including several instructions to make a device (may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a removable hard disk, a read only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk and other media that can store program codes.

The above contents are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the present application should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims (10)

1. a distributed shooting method, is characterized in that, comprises: The first device receives a first operation of the user selecting to perform synchronous shooting with the second device; In response to the first operation, the first device starts collecting first image data, and the first device instructs the second device to start collecting image data; The first device receives second image data from the second device, where the second image data includes an original image captured by a camera of the second device; The first device displays the first shot picture corresponding to the first image data in the first window, and displays the second shot picture corresponding to the second image data in the second window, the first window and the The second window is located on the same display interface. 2. The method according to claim 1, wherein the method further comprises: The first device sends the first image data to the second device, where the first image data includes an original image captured by a camera of the first device. 3. The method according to claim 1 or 2, wherein after the first device receives the first operation of the user selecting to shoot synchronously with the second device, the method further comprises: The first device acquires a shooting capability parameter of the second device, where the shooting capability parameter of the second device is used to indicate an image processing algorithm supported by the second device; Wherein, before the first device displays the first shooting picture corresponding to the first image data in the first window and displays the second shooting picture corresponding to the second image data in the second window, the method Also includes: The first device performs image processing on the first image data according to the shooting capability parameter of the first device to obtain the first shooting picture, and the shooting capability parameter of the first device is used to indicate the first image. an image processing algorithm supported by the device; The first device performs image processing on the second image data according to the shooting capability parameter of the second device to obtain the second shooting picture. 4 . The method according to claim 1 or 2 , wherein, on the first device, a first captured picture corresponding to the first image data is displayed in a first window, and the second image data corresponding to the second image data is displayed on the first window. 5 . The second captured image is displayed before the second window, and the method further includes: The first device performs image processing on the first image data according to the shooting capability parameter of the first device to obtain the first shooting picture, and the shooting capability parameter of the first device is used to indicate the first image. an image processing algorithm supported by the device; The first device performs image processing on the second image data according to the shooting capability parameter of the first device to obtain the second shooting picture. 5. The method according to any one of claims 1-4, wherein the first device instructing the second device to start collecting image data, comprising: The first device sends a shooting instruction to the second device; Wherein, the shooting instruction includes a preset mark, the shooting instruction is used to instruct the second device to collect image data, and the preset mark is used to instruct the second device to transmit the image data to the first device RAW images captured by the second device. 6. The method according to any one of claims 1-5, wherein before the first device receives the first operation of the user selecting to perform synchronous shooting with the second device, the method further comprises: The first device receives a second operation, where the second operation is a user's click operation on a function button for realizing distributed shooting, a preview interface of a camera application of the first device, a video of the first device At least one of the chat interface of the communication application, the control center of the first device, the pull-down menu or the negative screen includes the function button; In response to a second operation for clicking the function button, the first device displays a list of candidate devices in the preview interface, and the list of candidate devices includes the second device; The first operation is an operation of the user selecting the second device in the candidate device list. 7. The method according to any one of claims 1-6, wherein the synchronous shooting comprises at least one of synchronous video recording, synchronous photographing, synchronous live broadcast or synchronous video call. 8. The method according to any one of claims 1-7, wherein after the first device receives the first operation of the user selecting to perform synchronous shooting with the second device, the method further comprises: The first device creates a control session and a data session between the first device and the second device; Wherein, the control session is used to transmit a control command between the first device and the second device, the control command includes a shooting instruction used to instruct the second device to capture an image, and the data session uses for transmitting the second image data from the second device. 9. An electronic device, characterized in that the electronic device is a first device, and the electronic device comprises: one or more cameras, one or more processors, a display screen, a memory, and a communication module; the camera , the display screen, the memory, the communication module and the processor are coupled; Wherein, the memory is used for storing computer program codes, and the computer program codes include computer instructions, when the computer instructions are executed by the electronic device, the electronic device is made to execute any one of claims 1-8 the method described. 10. A computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, wherein, when the instructions are executed on an electronic device, the electronic device is caused to perform the execution as in claims 1-8. The method of any one.

Images