CN114845035B - Distributed shooting method, electronic device 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 during the distributed shooting process. In the method, a first device can receive a first operation in which a user selects to perform synchronous shooting with a second device. In response to the first operation, the first device can start to collect first image data, and the first device can also instruct the second device to start collecting image data. Afterwards, the first device can receive second image data from the second device, and the second image data includes the original image collected by the camera of the second device. Finally, the first device can display a first shooting picture corresponding to the first image data in a first window, and display a second shooting picture corresponding to the second image data in a second window. The first window and the second window are located on the same display interface.

Description

Distributed shooting method, electronic device and medium

Technical Field

The embodiments of the present application relate to the field of photographing technology, and in particular to a distributed photographing method, electronic equipment and 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 can be a mobile phone, a tablet computer, a smart watch or a smart TV. In the distributed camera system, an electronic device (called a local device) can not only present the images taken by the camera of the electronic device to the user, but also obtain and display the images taken by the cameras of other electronic devices (called remote devices).

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 capture an image and return a preview result to the local device; (2) after receiving the control command, the remote device captures an image and performs image signal processing (ISP) on the captured image to obtain a preview result; (3) the remote device sends the preview result to the local device.

In the above-mentioned image data transmission process across devices, the remote device sends to the local device the finished image (i.e., the above-mentioned preview result) obtained after image processing, and the data volume is increased, which requires a large network bandwidth and wastes 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 data transmission between a remote device and a local device during the distributed shooting process.

In a first aspect, the present application provides a distributed shooting method, which is applied to a first device. In the method, the first device can receive a first operation in which a user selects to perform synchronous shooting with a second device. In response to the first operation, the first device can start collecting first image data and instruct the second device to start collecting image data. Afterwards, the first device can receive second image data from the second device, and the second image data includes an original image. Finally, the first device can display a first shooting picture corresponding to the first image data in a first window, and display a second shooting picture corresponding to the second image data in a second window. The first window and the second window are located on the same display interface.

It should be noted that the above original image can also be called a RAW image. RAW can be translated as "unprocessed". That is to say, the above 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 volume of the original image is smaller. In this way, the network bandwidth occupied by the distributed shooting service across devices can be reduced.

In a possible design of the first aspect, the method may further include: the first device sends first image data to the second device, the first image data including an original image. The original image (also called 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 picture of the first device and the shooting picture of the second device, but the second device can also simultaneously display the shooting picture of the first device and the shooting picture of the second device.

In another possible design of the first aspect, after the first device receives a first operation in which the user selects to perform synchronous shooting with the second device, the method of the present application may further include: the first device obtains a shooting capability parameter of the second device, and 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 parameter of the first device to obtain a first shooting picture, and perform image processing on the second image data according to the shooting capability parameter of the second device to obtain a second shooting picture. The shooting capability parameter of the first device is used to indicate the image processing algorithm supported by the first device.

It should be understood that the first device performs image processing on the RAW image captured by the second device based on the algorithm capability of the second device (i.e., the image processing algorithm supported by the second device indicated by the shooting capability parameter of the second device), and can obtain the same or similar effect as the image processing performed by the second device 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 a shooting capability parameter of the first device to obtain the first shooting picture; and perform image processing on the second image data according to the shooting capability parameter of the first device to obtain the second shooting picture. 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 the first device performs image processing on the RAW images captured by the first device and the second device based on the algorithm capability of the first device, so that the image effect of the picture taken by the second device is consistent with that of the picture taken by the first device.

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

In another possible design manner of the first aspect, the first device instructs the second device to start collecting image data, including: the first device sends a shooting instruction to the second device.

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 preset mark, it will not process the collected original image; instead, it will transparently transmit the collected 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 a second operation. The second operation is a user clicking operation on a function button for implementing distributed shooting, and at least one of a preview interface of a camera application of the first device, a chat interface of a video communication application of the first device, a control center of the first device, a drop-down menu, or a negative screen includes a function button. 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 list of candidate devices includes the second device. The first operation is an operation of the user selecting the second device in the list of candidate devices.

In another possible design of the first aspect, the synchronous shooting includes at least one of synchronous video recording, synchronous photo taking, synchronous live broadcasting or synchronous video calling. That is, the method of the present application can be applied to the process of the first device recording, taking photos, live broadcasting or video calling with other devices.

In another possible design of the first aspect, after the first device receives the first operation of the user selecting to perform synchronous shooting with the second device, the method of the present application also includes: the first device creates a control session and a data session between the first device and the second device.

The control session is used to transmit control commands between the first device and the second device, wherein the control commands include shooting instructions for instructing the second device to capture images, and the data session is used to transmit the second image data from the second device.

In the process of the first device and the second device executing the cross-device distributed shooting service, the transmission paths of the control flow and the data flow can be distinguished, so as to avoid the problem of the control flow and the data flow occupying each other's bandwidth.

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

The memory is used to store computer program code, which includes computer instructions. When the computer instructions are executed by the electronic device, the electronic device executes the method described in the first aspect and any possible design 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 interface circuit and the processor are interconnected through a line; the interface circuit is used to receive a signal from the memory of the electronic device and send the signal to the processor, the signal including a computer instruction stored in the memory; when the processor executes the computer instruction, the electronic device executes the method as described in the first aspect and any possible design thereof. The electronic device is a first device.

In a fourth aspect, the present application provides a computer storage medium, which includes computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the method described in the first aspect and any possible design thereof.

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

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

It can be understood that the beneficial effects that can be achieved by the electronic device described in the second aspect, the chip system described in the third aspect, the computer storage medium described in the fourth aspect, the computer program product described in the fifth aspect, and the distributed shooting system described in the sixth aspect provided above can refer to the beneficial effects in the first aspect and any possible design method thereof, and will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIG2A is a functional schematic diagram of a distributed shooting method implemented by an embodiment of the present application;

FIG2B is a schematic diagram of the hardware structure of a mobile phone provided in an embodiment of the present application;

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

FIG2D is a schematic diagram of a 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 provided in an embodiment of the present application;

FIG2F is a simplified diagram of the software architecture shown in FIG2E ;

FIG3A is a schematic diagram of a distributed shooting interface provided in an embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

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

FIG13 is a schematic diagram of a data transmission process between a local device and a remote device provided in an embodiment of the present application;

FIG14 is a schematic diagram of a data processing and transmission process in a remote device provided in an embodiment of the present application;

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

FIG16 is a schematic diagram of a data transmission process between a local device and a remote device provided in an embodiment of the present application;

FIG17 is a schematic diagram of the structure of a chip system provided in an embodiment of the present application.

Detailed ways

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

A distributed shooting method provided in an embodiment of the present application can be applied to a distributed shooting system 100 shown in FIG1 . As shown in FIG1 , 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 can communicate with any remote device 102 via a wired manner or a wireless manner. The local device 101 is a first device, and the remote device 102 is a second device.

Exemplarily, a universal serial bus (USB) can be used to establish a wired connection between the local device 101 and the remote device 102. For another example, a wireless connection can be established between the local device 101 and the remote device 102 through a global system for mobile communications (GSM), a general packet radio service (GPRS), 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 a communication protocol supporting a network slicing architecture.

In some embodiments, the local device 101 can use the above wireless connection to communicate directly with the remote device 102. In other embodiments, the local device 101 can 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.

Among them, one or more cameras may be set in both the local device 101 and the remote device 102. 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 the 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 simultaneously displays the image data from the local device 101 and the remote device 102, thereby realizing a distributed shooting function across devices.

As shown in Figure 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 an embodiment of the present application, the system camera application or the third-party camera application may be collectively referred to as a camera application. Among them, the system application may also be referred to as an embedded application, and the embedded application is an application provided as part of the implementation of an electronic device (such as the local device 101 or the remote device 102). A third-party application may also be referred to as a downloadable application. 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 an electronic device or may be an application downloaded and installed by a user in an electronic device.

Specifically, as shown in FIG2A , the local device 101 can be connected to the remote device 102, and can also control the remote device 102 to turn on the camera of the remote device 102 through the connection between the local device 101 and the remote device 120. As shown in FIG2A , the local device 101 can realize image preview of the remote device 102 and control the preview effect. As shown in FIG2A , the local device 101 can control the remote device 102 to take pictures and control the picture taking effect of the remote device 102. As shown in FIG2A , the local device 101 can control the remote device 102 to record and control the video recording effect of the remote device 102. Among them, the above-mentioned distributed shooting function across devices is realized, as shown in FIG2A , the local device 101 can display the shooting pictures of the local device 101 and the remote device 102. In this way, the user can not only see the shooting pictures of the local device 101 on the local device 101, but also see the shooting pictures 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) can be a mobile phone, a tablet computer, a television (also called a smart TV, a smart screen or a large-screen device), a laptop computer, an ultra-mobile personal computer (UMPC), a handheld computer, a camera (such as a digital camera), a camcorder (such as a digital video camera), a netbook, a personal digital assistant (PDA), a wearable electronic device (for example: a smart watch, a smart bracelet, a smart glasses), a vehicle-mounted device, a virtual reality device, and other electronic devices with a shooting function. The embodiments of the present application do not impose any restrictions on this.

Exemplarily, taking a mobile phone as the local device 101 in the above-mentioned distributed shooting system 100, FIG2B shows a schematic diagram of the structure of the mobile phone. As shown in FIG2B, 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, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, etc.

It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the mobile phone. In other embodiments of the present application, the mobile phone may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure 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 (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

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

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

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

In some embodiments, the antenna 1 of the mobile phone is coupled to the mobile communication module 150, and the antenna 2 is coupled to 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 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In some embodiments, the mobile phone 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 ISP, camera 193, video codec, GPU, display screen 194 and application processor. Camera 193 is used to capture static images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can 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 for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. 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 implement a data storage function. For example, files such as music and videos can be stored in the external memory card.

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

The mobile phone can realize audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor.

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, buttons, indicators, and one or more SIM card interfaces, etc., and the embodiments of the present application do not impose any restrictions on this.

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

The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into five layers, from top to bottom, namely the application layer, the application framework layer, the Android runtime (Android runtime) and the system library, the HAL (hardware abstraction layer, hardware abstraction layer) layer, and the kernel layer. It should be understood that: This article uses the Android system as an example to illustrate that 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 FIG. 2C , the application layer may be installed with applications such as calls, memos, browsers, contacts, gallery, calendar, maps, Bluetooth, music, videos, and short messages.

In the embodiment of the present application, an application with a shooting function, such as a camera application, can 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 implement the shooting function.

The application framework layer provides an application programming interface (API) and a programming framework for the applications in 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., and the embodiments of the present application do not impose any restrictions on this.

For example, the above-mentioned window manager is used to manage window programs. The window manager can obtain the size of the display screen, determine whether there is a status bar, lock the screen, capture the screen, etc. The above-mentioned content provider is used to store and obtain data, and make these data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc. The above-mentioned view system can be used to build the display interface of the application. Each display interface can be composed of one or more controls. Generally speaking, controls can include interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. The above-mentioned resource manager provides various resources for applications, such as localized strings, icons, pictures, layout files, video files, etc. The above-mentioned notification manager 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 be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as a notification of an application running in the background, or a notification that appears on the screen in the form of a dialog window. For example, displaying text messages in the status bar, making beep sounds, vibrating, or flashing indicator lights.

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

The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

The application layer and the application framework layer run in a virtual machine. 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 life cycle management, stack management, thread management, security and exception management, and garbage collection.

The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

Among them, the surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications. The media library supports playback and recording of multiple commonly used audio and video formats, as well as static image files. The media library can support multiple 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, synthesis, and layer processing. The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is located below the HAL and is a layer between hardware and software. The kernel layer at least includes a display driver, a camera driver, an audio driver, a sensor driver, etc., and the present application embodiment does not impose any restrictions on this.

In an embodiment of the present application, still as shown in FIG. 2C , taking the camera application as an example, a camera service (Camera Service) can be set in the application framework layer. The camera application can start the Camera Service by calling a preset API. During operation, the CameraService can interact with the CameraHAL in the HAL (hardware abstraction layer). Among them, the Camera HAL is responsible for interacting with the hardware device (such as a camera) that implements 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, it can provide the Android system with an interface for calling the relevant hardware devices.

For example, when the camera application is running, the relevant control commands (such as preview, zoom, photo or video recording instructions) issued by the user can be sent to the Camera Service. On the one hand, the Camera Service can send the received control command to the Camera HAL, so that the Camera HAL can call the camera driver in the kernel layer according to the received control command, and the camera driver drives the camera and other hardware devices to respond to the control command to collect image data. For example, the camera can pass each frame of image data collected to the Camera HAL through the camera driver at a certain frame rate. Among them, the transmission process of the control command within the operating system can refer to the specific transmission process of the control flow in Figure 2C.

On the other hand, after receiving the above control command, the Camera Service can determine the current shooting strategy based on the received control command. The shooting strategy sets the specific image processing tasks that need to be performed on the collected image data. For example, in preview mode, the Camera Service can set image processing task 1 in the shooting strategy to implement the face detection function. For another example, if the user turns on the beauty function in preview mode, the Camera Service can also set image processing task 2 in the shooting strategy to implement the beauty function. Then, the Camera Service can send the determined shooting strategy to the Camera HAL.

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

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 in the display interface, or the camera application can save each frame of the captured image in the form of a photo or video in the mobile phone. The transmission process of the above-mentioned captured image within the operating system can be referred to the specific transmission process of the data flow in Figure 2C.

Please refer to Figure 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 application, in conjunction with the software architecture shown in Figure 2D, a solution for the local device 101 and the remote device 102 to implement cross-device distributed shooting is described.

Among them, the local device 101 has device discovery and remote registration functions. For example, the local device 101 can discover the remote device 102, such as the TV 1, watch 2 and mobile phone 3 shown in Figure 4. When the user selects TV 1 as the remote device 102 to perform cross-device distributed shooting with the local device 101 (such as the user selects TV 1 as shown in Figure 4), the local device 101 can register the remote device 102 (such as TV 1) to the local device 101.

For example, the local device 101 can create a distributed mobile sensing development platform (Distributed Mobile Sensing Development Platform, DMSDP) HAL, which can also be called a virtual camera HAL (i.e., virtual Camera HAL), for the remote device 102 in the hardware abstract layer (HAL) of the local device 101. Among them, unlike 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 Figure 2D is a 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, regard the remote device 102 as a virtual device of the local device 101, and collaborate with the remote device 102 to complete the distributed shooting service across devices.

The following describes a specific process of the local device 101 and the remote device 102 cooperating to complete the cross-device distributed shooting service. As shown in FIG2D , the process may include steps ① to ⑩.

Step ①: The application layer of the local device 101 sends 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 the 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 the control command to the Camera HAL of the HAL. Among them, 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 (such as the kernel layer Kernel) according to the control command to perform the corresponding shooting task (such as starting the camera, switching the camera, or adjusting the relevant parameters of the camera, etc.). Among them, the data transmitted in the above steps ① to ⑤ can be called 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 preview images collected by the bottom-layer Camera device of the remote device 102 and processed by the bottom-layer 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 ⑧: The application layer of the remote device 101 transmits the preview stream to the DMSDP HAL of the local device 101. Step ⑨: 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. The specific process can refer to the relevant introduction of conventional technology, which will not be repeated here. The data transmitted in the above steps ⑥ to ⑩ may be referred to as a preview stream or a data stream.

It should be noted that, as shown in Figure 2D, the service layer of the local device 101 or the remote device 102 can be included in the framework layer, and the service layer can be implemented in the framework layer. Of course, the service layer of the service layer of the local device 101 or the remote device 102 can also be independent of the framework layer, and this embodiment of the application does not limit this.

On the one hand, although the execution of the above process can complete the distributed shooting service across devices; however, in the above-mentioned preview stream transmission process across devices, the preview stream transmitted by the remote device 102 to the local device 101 is a finished film obtained after image processing (that is, a preview result that can be directly displayed), and its data volume is increased, which requires a larger network bandwidth and wastes network resources.

On the other hand, different devices have different image processing performance. For example, compared with the local device 101, the performance of the remote device 102 in layer processing may be lower. As a result, the efficiency of the remote device 102 in outputting images is lower. To achieve the simultaneous display of the captured images from the local device 101 and the remote device 102 on the local device 101, a larger delay is required. In addition, the above process does not distinguish between the transmission paths of the control stream and the data stream (or preview stream), and the control stream and the data stream may occupy each other's bandwidth.

The embodiment of the present application provides a distributed shooting method. During the process of the local device 101 and the remote device 102 performing a distributed shooting service across devices, the local device 101 can directly obtain the original image captured by the remote device 102 from the remote device 102. The original image can also be called a RAW image. RAW can be translated as "unprocessed". In other words, the original image captured by the above-mentioned 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 to introduce the method of the embodiment of the present application.

Among them, the data volume of the RAW image is smaller than that of the image processed by the remote device 102. In this way, the network bandwidth occupied by the distributed shooting service across devices can be reduced.

Furthermore, the local device 101 processes the RAW image from the remote device 102, which can avoid the problem of increased latency due to the large performance difference between the devices at both ends. This solution can reduce the latency of the distributed shooting service. Furthermore, during the process of the local device 101 and the remote device 102 performing the cross-device distributed shooting service, the transmission paths of the control stream and the data stream can be distinguished. In this way, the problem of the control stream and the data stream occupying each other's bandwidth can be avoided.

Please refer to FIG. 2E , which shows a schematic diagram of the software architecture of a local device 101 and a remote device 102 provided in 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 201a, and a HAL 202; the remote device 102 may include: an application layer 210, a framework layer 211, a service layer 211a, and a HAL 212. Among them, the service layer may be implemented in the framework layer. For example, as shown in FIG. 2E , the service layer 201a may be implemented in the framework layer 201, and the service layer 211a 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, they can also call the camera application to implement 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 collaborate to complete the distributed shooting service. The camera proxy service 210a can also be called a camera proxy application, which is not limited in the embodiments of the present application.

Furthermore, in the present application, a device virtualization (Dv) application 200a for implementing a distributed shooting function may also be installed in the application layer 200. The Dv application 200a may be resident and run in the local device 101 as a system application. Alternatively, the functions implemented by the Dv application 200a may be resident and run in the local device 101 as a system service.

The framework layer provides an API and programming framework for the application of the application layer. For example, both the framework layer 201 and the framework layer 211 can provide Camera API 2.0. For other functions of the framework layer 201 and the framework layer 211, please refer to the detailed description of the application framework layer described in FIG. 2C in the embodiment of the present application, which will not be repeated here.

As shown in FIG2E , taking a camera application as an example, a Camera kit 201c is provided in the framework layer 201. The Camera kit 201c may encapsulate a variety of camera modes, such as the photo mode, video mode, and dual-view mode shown in FIG2E .

As shown in FIG2E , a camera service (Camera Service) 201a1 may be provided in the service layer 201a. The camera application may start the Camera Service 201a1 by calling a preset API (e.g., Camera API 2.0). A Camera HAL 202a and a DMSDP HAL 202b are provided in the HAL 202. The Camera Service 201a1 may interact with the Camera HAL 202a and/or the DMSDP HAL 202b in the HAL 202 during operation.

Among them, 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, 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 the relevant 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 introduction of the corresponding software modules in Figure 2C in the above embodiment, and the embodiment of the present application will not be repeated here.

The framework layer 201 may also be provided with a Dv kit 201b for implementing a distributed shooting function. The Dvkit 201b may be called by the Dv application 200a provided in the application layer 200 to implement the function of discovering and connecting to the remote device 102. Alternatively, the function implemented by the Dv application 200a may be resident in the mobile phone in the form of a system service.

When the mobile phone needs to use the camera of other electronic devices to realize the distributed shooting function, in the camera mode (such as dual view mode) provided by Camera kit 201c, the local device 101 can discover and connect to the remote device 102 through Dv kit 201b. After the local device 101 establishes a connection with the remote device 102, the local device 101 can create a DMSDP HAL 202b for the remote device 102 in the HAL 202 of the local device 101. The remote device 102 can be registered with the local device 101. The DMSDP HAL 202b shown in FIG. 2E is a 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. The functions of the Dv application and the Dv kit in the remote device 102 can refer to the functional introduction of the Dv application 200a and the Dv kit 201b in the embodiment of the present application, which will not be repeated here.

Still as shown in FIG. 2E , in addition to creating a corresponding DMSDP HAL 202b for the remote device 201 in HAL 202, the shooting capability parameters of the remote device 102 can also be sent to the Camera Service 201a1 for storage, that is, the shooting capability parameters (including device capability information and algorithm capability information) of the current remote device 102 are registered in the Camera Service 201a1. Among them, the device capability information is used to indicate the hardware capability of the remote device 102 for shooting images, and the algorithm capability information is used to indicate the algorithm capability of the remote device 102 for image processing of 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. Furthermore, the "peer Meta synchronization mapping" function can also be set in the DMSDP HAL 202b. Peer Meta refers to a label in the remote device 102 used to indicate the shooting capability parameters of the remote device 102.

It should be noted that DMSDP HAL 202b can also be called virtual Camera HAL or DMSDP CameraHAL. Different from the traditional Camera HAL, 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 FIG2F, the remote device 102 (such as a TV, tablet computer, mobile phone, etc. including a camera) can be used as a virtual camera of the local device 101. Among them, the local device 101 (the virtual framework shown in FIG2F) can send and receive data with the remote device 102 through the DMSDP HAL 202b, and use the remote device 102 as a virtual camera of the local device 101, and cooperate with the remote device 102 to complete various services in the distributed shooting scene.

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.) and display capability parameters (such as screen resolution, encoding and decoding algorithm of display data, etc.) of the remote device 102 through the Dv kit 201b. 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, display and other capabilities of the remote device 102, so that the remote device 102 can serve as a virtual device of the local device 101 and collaborate with the local device 101 to complete various services in the distributed scenario.

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

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

When the mobile phone runs the camera application, the Camera Service 201a1 can determine the shooting strategy in real time during the shooting process according to the control commands (such as preview, zoom, and record instructions) issued by the camera application and 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 strategy according to the shooting capability parameters of the slave device. Furthermore, the CameraService can use the DMSDP HAL 202b to send the shooting instructions corresponding to the shooting strategy to the remote device 102 through the Control Session, triggering the remote device 102 to perform the corresponding image processing tasks.

Afterwards, 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 the camera and other hardware devices to respond to the shooting instruction to collect image data. For example, the camera can pass each frame of image data collected to the Camera HAL through the camera driver at a certain frame rate.

After the Camera HAL 212a of the remote device 102 receives each frame of image data collected by the camera, it transmits a data stream including the RAW image collected by the camera to the upper layer. 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. For example, the camera proxy service 210a can send the data stream including the RAW image 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 CameraService201a1, perform image processing on the RAW image, and obtain each corresponding frame of the shooting picture. Subsequently, the DMSDP HAL 202b can report each frame of the shooting picture after image processing to the camera application through the Camera Service 201a1, and the camera application can display each frame of the shooting picture in 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 image processing on the image data based on the above-mentioned shooting strategy according to its own shooting capabilities and the shooting capabilities of the remote device 102, so as to achieve better shooting effects in the distributed shooting scene.

In some embodiments, the local device 101 may also send a RAW image captured by the local device 101 to the remote device 102. The camera service 211a1 of the remote device 102 may also store the shooting capability parameters of the local device 101. The remote device 102 may also call relevant algorithms according to the shooting capability parameters of the local device 101, perform image processing on the RAW image from the local device 101, and obtain each corresponding frame of the shooting picture. The remote device 102 may call relevant algorithms according to the shooting capability parameters of the remote device 102, and perform image processing on the RAW image captured by the remote device 102, and obtain each corresponding frame of the shooting picture. In this way, the remote device 102 may also display the shooting pictures of the local device 101 and the shooting pictures of the remote device 102 at the same time. By adopting this solution, the above-mentioned distributed shooting function across devices can be implemented on both the local device 101 and the remote device 102.

The following examples illustrate the application scenarios of the method provided in the embodiments of the present application. The method in the embodiments of the present application can be applied to at least the following application scenarios (1) to (2).

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

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

Exemplarily, the preset application may be a camera application for realizing the shooting function. Taking mobile phone 0 as the local device 101 as an example, a camera application may be installed in mobile phone 0. Mobile phone 0 (i.e., local device 101) may perform cross-device multi-view shooting with remote device 102 through the camera application. As shown in FIG3A , after detecting that the user opens the camera application, mobile phone 0 may open its own camera to start collecting image data, and display the corresponding shooting picture in real time in the preview box 302 of the preview interface 301 according to the collected image data.

The captured image 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 may perform image processing tasks such as anti-shake, focus, soft focus, blur, filter, beauty, face detection or AR recognition on the collected image data to obtain the captured image after image processing. Furthermore, the mobile phone 0 may display the captured image after image processing in the preview frame 302.

Similarly, the remote device 102 can also turn on its own camera to start collecting image data, and perform image processing tasks such as anti-shake, focus, soft focus, blur, filter, beauty, face detection or AR recognition on the collected image data to obtain the captured picture after image processing. The embodiments of the present application do not impose any restrictions on this.

In the embodiment of the present application, as shown in FIG3A , the mobile phone 0 can 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-view images shot by the mobile phone 0 and the remote device 102 on the mobile phone 0, the function button 303 can be clicked to start the cross-device multi-view shooting function.

Alternatively, the mobile phone 0 may also set the function button 304 of the synchronous shooting function in the control center, drop-down menu, negative one screen or other application (such as a video call application) of the mobile phone, and the embodiment of the present application does not impose any restrictions on this. For example, as shown in FIG3B , the mobile phone may 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 button 304. If the user wants to use the mobile phone and other electronic devices to perform synchronous shooting together, the function button 304 may be clicked.

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

For example, the cloud server may record whether each electronic device has a shooting function. Then, mobile phone 0 may query the cloud server for electronic devices with a shooting function that are logged in with the same account (e.g., Huawei account) as mobile phone 0. Furthermore, mobile phone 0 may display the queried electronic devices as candidate devices in dialog box 401.

Alternatively, mobile phone 0 may search for electronic devices in the same Wi-Fi network as mobile phone 0. Further, mobile phone 0 may send a query request to each electronic device in the same Wi-Fi network, triggering the electronic device that receives the query request to send a response message to mobile phone 0, and the response message may indicate whether it has a shooting function. Then, mobile phone 0 may determine the electronic device with a shooting function in the current Wi-Fi network based on the received response message. Further, mobile phone 0 may display the electronic device with a shooting function as a candidate device in dialog box 401.

Alternatively, an application for managing smart home devices (such as televisions, air conditioners, speakers, or refrigerators, etc.) in the home may be installed in mobile phone 0. Taking the smart home application as an example, the user can add one or more smart home devices to the smart home application so that the smart home devices added by the user are associated with mobile phone 0. For example, a QR code containing device information such as a device identifier may be set on the smart home device. After the user scans the QR code using the smart home application of mobile phone 0, the corresponding smart home device can be added to the smart home application, thereby establishing an association between the smart home device and mobile phone 0. In an embodiment of the present application, when one or more smart home devices added to the smart home application are online, for example, when mobile phone 0 detects a Wi-Fi signal sent by the added smart home device, mobile phone 0 may display the smart home device as a candidate device in dialog box 401, prompting the user to choose to use the corresponding smart home device for synchronous shooting with mobile phone 0.

As shown in FIG4 , for example, the candidate devices searched by mobile phone 0 include TV 1, watch 2, and mobile phone 3. The user can select one or more remote devices 102 for cross-device multi-view shooting with mobile phone 0 from TV 1, watch 2, and mobile phone 3. In the embodiment of the present application, cross-device dual-view shooting is taken as an example. For example, if it is detected that the user selects TV 1, mobile phone 0 can use TV 1 as the remote device 102 to establish a network connection with 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; or mobile phone 0 can directly establish a Bluetooth connection with TV 1; or mobile phone 0 can directly establish a short-range wireless connection with TV 1, and the short-range wireless connection includes but is not limited to near field communication (NFC) connection, infrared connection, ultra-wideband (Ultra Wideband, UWB) connection, ZigBee connection; or mobile phone 0 can directly establish a mobile network connection with TV 1, and the mobile network includes but is not limited to mobile networks supporting 2G, 3G, 4G, 5G and subsequent standard protocols.

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 shooting function according to the above method. Then, the mobile phone 0 can automatically establish a network connection with the searched electronic devices. In this case, the user does not need to manually select a specific device to establish 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 with a shooting function. For example, before the user opens the camera application in the mobile phone 0, a Bluetooth connection has been established with the tablet computer. Subsequently, after the mobile phone 0 opens the camera application and displays the preview interface 301 of the camera application, if it is detected that the user clicks the function button 303, the mobile phone 0 may no longer search for electronic devices with a shooting function, but execute the following method.

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

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

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 shooting objects (such as parent-child shooting or friend shooting, etc.). For example, assume that the local device 101 is the mobile phone 0 shown in FIG5, and the remote device 102 is the mobile phone 3 shown in FIG6A. Among them, the mobile phone 0 or the mobile phone 3 can achieve co-shooting of multiple shooting objects through the above-mentioned preset application (such as a camera application or other applications that can be used to achieve photo or video shooting).

For example, taking the camera application as the preset application, when the user wishes to see the co-photographed picture of mobile phone 0 and mobile phone 3 on mobile phone 0, the user can click function button 303 or function button 304 to start the cross-device multi-scene co-photographing function.

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

After mobile phone 0 establishes a network connection with mobile phone 3, on one hand, as shown in FIG6A , mobile phone 0 can turn on its own camera to start collecting image data, and perform image processing on the collected image data to obtain shooting picture 1. On the other hand, as shown in FIG6A , mobile phone 0 can instruct 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 shooting picture 3. Subsequently, mobile phone 3 can send shooting picture 3 to mobile phone 0. In this way, mobile phone 0 can simultaneously display shooting picture 1 from mobile phone 0 and shooting picture 3 from mobile phone 3 in the display interface of the camera application.

It should be noted that, unlike the first case above, in the process of cross-device multi-scene co-shooting, mobile phone 0 can send shooting picture 1 to mobile phone 3. As shown in FIG6A , mobile phone 3 can also simultaneously display shooting picture 1 from mobile phone 0 and shooting picture 3 from mobile phone 3. At this time, mobile phone 0 can be used as a local device and a remote device at the same time. Specifically, mobile phone 0 is used as a local device, mobile phone 3 is used as a remote device, and mobile phone 0 can simultaneously display shooting picture 1 of mobile phone 0 and shooting picture 3 from mobile phone 3. Mobile phone 3 is used as a local device, and mobile phone 0 is used as a remote device, and mobile phone 3 can simultaneously display shooting picture 3 of mobile phone 3 and shooting picture 1 from mobile phone 0.

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

Application scenario (2): The scenario where the local device 101 calls the remote device 102 to make a video call, live broadcast, take a photo, or record a video. 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 in making a video call, live broadcast, take a photo, or record a video.

For example, the present application embodiment takes the local device 101 calling the remote device 102 for a video call as an example to introduce the application scenario (2). The above-mentioned preset application can be a video communication application (such as WeChat TM application) for implementing a video call. Taking the mobile phone 0 as the local device 101 and the TV 1 as the remote device 102 as an example, the above-mentioned video communication application can be installed in the mobile phone 0.

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

In another implementation, before requesting a video call with mobile phone 4, mobile phone 0 can call the camera and display of remote device 102 (such as TV 1) to assist mobile phone 0 in making a video call with mobile phone 4. For example, as shown in FIG8 , in response to a user clicking on the “video call” option 801 in the chat interface, mobile phone 0 can 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 in making a voice call. When the user wants mobile phone 0 to call other devices to assist mobile phone 0 in making a video call, the user can click the “Yes” button in the confirmation window 802.

Exemplarily, after the mobile phone 0 detects that the user clicks the function button 702 or the "Yes" button in the confirmation window 802, the candidate device can be searched. For example, the dialog box 401 shown in FIG. 4 can be displayed. The specific method of searching the candidate device and displaying the dialog box 401 by the mobile phone can refer to the detailed description in the above embodiment, which will not be repeated here.

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

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

Alternatively, when mobile phone 0 calls the camera and display screen of TV 1 to assist mobile phone 0 in making a video call with mobile phone 4, 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.

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

It should be noted that, since the shooting angles of mobile phone 0 and TV 1 are different, the picture shot by mobile phone 0 may be different from the picture shot by TV 1. For example, picture shot a shown in FIG7 is shot by mobile phone 0, and picture shot c shown in FIG9 is shot by TV 1, and picture shot a is different from picture shot 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 in completing 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 in completing the above tasks. For example, as shown in FIG6A, the mobile phone 3 can also simultaneously display the shooting picture 1 from the mobile phone 0 and the shooting picture 3 from the mobile phone 3.

In the embodiment of the present application, the local device 101 and the remote device 102 can perform shooting in a distributed shooting scene (such as multi-view shooting). In the following embodiment, the method of the embodiment of the present application is 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 (such as a mobile phone) can provide a dual-view mode (including a dual-view photo mode and a dual-view video recording mode). As shown in Figure 10, the mobile phone can set a function button 1001 and a function button 1002 for cross-device multi-view shooting in the preview interface of the camera application. Specifically, the function button 1001 is used to trigger the mobile phone to enter the multi-view photo mode. The function button 1002 is used to trigger the mobile phone to enter the multi-view video recording mode. When the user wants to see the multi-view pictures taken by the mobile phone and the remote device 1002 on the mobile phone, the function button 1001 or the function button 1002 can be clicked to turn on the cross-device multi-view shooting function. In the 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.

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

Furthermore, as shown in FIG11 , the mobile phone may display one or more searched candidate devices in a dialog box 1101. For example, the mobile phone may query the server for electronic devices that are logged into the same account as the mobile phone and have a camera function, and display the queried electronic devices as candidate devices in the dialog box 1101. In the embodiment of the present application, the user's click operation on the candidate devices in the dialog box 1101 and the dialog box 401 (also referred to as the candidate device list) is the first operation.

For example, if the candidate devices in the dialog box 1101 include TV 1102, TV 1103, and watch 1104, the user can select the remote device that cooperates with the mobile phone to realize the synchronous shooting function in the dialog box 1101. For example, if the mobile phone detects that the user selects TV 1102 in the dialog box 1101, it means that the user wants to use the mobile phone and TV 1102 to shoot at the same time. At this time, the Dv kit of the mobile phone can use TV 1102 as the 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.

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 for shooting 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 may be used by the mobile phone to determine the shooting strategy of the TV 1102.

The shooting capability parameters of the TV 1102 can be stored in the Camera Service of the mobile phone. For example, the shooting capability parameters of the TV 1102 can be stored in the Camera Service of the mobile phone in the form of tags.

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 parameters of the TV 1102 in the Camera Service of the mobile phone. For example, please refer to Figure 12, which shows a format diagram of the device capability information of the TV 1102 stored in the Camera Service of the mobile phone in the embodiment of the present application.

The mobile phone's Camera Service can use the three-layer data structure shown in FIG12 to save the device capability information of the TV 1102. The mobile phone can store each device capability information of the TV 1102 in segments in the Camera Service. Section_name shown in FIG12 is the storage address of the TV 1102; Tag_name is a plurality of tag names under one address of Section_name; Tag_index is the index of the capability information of the tag name. The index is used to indicate the storage address of the specific capability information.

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

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

Take a Tag name as shown in Figure 12 as an example. As shown in Figure 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 capability information of a tag name stored in the TV 1102. CAMERA_HUAWEI_DEVICE_CAPABILITIES_END may indicate the ending address of capability information of a tag name stored in the TV 1102. According to the starting address and the 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 FIG13 , the TAG (i.e., 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 in which the mobile phone processes the RAW image returned by the TV 1102 according to the above-mentioned TAG in combination with the post-processing (algorithm) module is described in detail in the following embodiments and will not be described in detail here.

Subsequently, when the mobile phone runs the camera application, on the one hand, it can call its own camera to obtain each frame of the captured image, and on the other hand, the mobile phone can instruct the TV 1102 to obtain the RAW image, and send the obtained RAW image to the camera application of the mobile phone through the DMSDP HAL 202b. Among them, the mobile phone can call its own camera to obtain each frame of the captured image at a certain frame rate, and instruct the TV 1102 to obtain the RAW image at the same frame rate.

Among them, 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 FIG13, 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 execute 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 mark is used to indicate that the RAW data collected by the underlying Camera device is directly obtained, and the RAW data is transparently transmitted to the camera proxy service 210a of the application layer 211. For example, as shown in FIG13 , the camera proxy service 210a of the application layer 210 may add a preset mark to the shooting instruction, and transmit the shooting instruction with the preset mark added to the Camera HAL 212a in the HAL 212 through the framework layer 211 and the service layer 211a. After receiving the shooting instruction, the Camera HAL 212a in the HAL 212 may call the Camera device in the kernel layer 213 to execute the shooting instruction. For example, the Camera HAL 212a in the HAL 212 may call the Camera device in the kernel layer 213 to collect a RAW image, and execute step b to transparently transmit the RAW data to the camera proxy service 210a of the application layer 211. Then, the camera proxy service 210a of the application layer 211 executes step c to transmit the RAW image to the DMSDP HAL 202b of the mobile phone.

Among them, the Camera device of the kernel layer 213 may include a photosensitive device, a digital signal processor (DSP) and an image processor (ISP) as shown in Figure 14. The photosensitive device may include a lens and a sensor (Sensor), etc. The photosensitive device is used to collect RAW images. The digital signal processor (DSP) is used to sample and process multiple frames of RAW images collected by the photosensitive device; then, the sampled RAW images are transmitted to the image processor (ISP). Generally speaking, the image processor (ISP) can perform image processing on the RAW images from the DSP. However, in an embodiment of the present application, the ISP does not perform image processing on the RAW images from the DSP, but instead transmits the RAW images from the DSP to the Camera HAL 212a in the HAL 212.

It should be noted that the step b in FIG. 13 is directed directly from the kernel layer 213 to the application layer 210 only to illustrate that the mobile phone will not perform image processing on the RAW image, and does not mean that the RAW image can be directly transmitted from the kernel layer 213 to the application layer 210 without passing through the Camera HAL 212a, the service layer 211a and the framework layer 211 in the HAL 212. The Camera device in the kernel layer 213 needs to collect the RAW image and transmit it 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 pass through the RAW image, and will not perform any processing on the RAW image.

In the embodiment of the present application, what the TV 1102 transmits to the mobile phone is not a processed, directly displayable shooting picture, but a RAW image that has not been image processed. After the TV 1102 uses the camera to capture the RAW image, it does not need to process the RAW image, and can directly transmit the RAW image to the mobile phone. The RAW image is an image that has not been processed by the TV 1102. Compared with the image processed by the TV 1102, the data volume of the RAW image is smaller. In this way, the network bandwidth occupied by the distributed shooting service across devices can be reduced.

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

The mobile phone processes the RAW image from the TV 1102, thereby avoiding the problem of increased latency due to the large performance difference of the devices at both ends. This solution can reduce the latency of the distributed shooting service.

Moreover, in the embodiment of the present application, after the mobile phone establishes a connection with the TV 1102, two camera sessions (Camera Session) may be created based on the DMSDPHAL 202b shown in FIG. 13, such as a control session (Control Session) for transmitting a control stream (such as the above-mentioned shooting instruction) and a data session (DataSession) for transmitting a data stream (such as the above-mentioned RAW data). Among them, the Control Session and the Data Session may correspond to different transmission paths (or transmission pipelines). The DMSDP HAL 202b of the mobile phone executes step a shown in FIG. 13, and may 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 may transmit the 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.

In the process of executing the cross-device distributed shooting service, the mobile phone and the TV 1102 can distinguish the transmission paths of the control stream and the data stream, so as to avoid the problem of the control stream and the data stream occupying each other's bandwidth.

In some embodiments, the shooting capability parameters of the TV 1102 may also include algorithm capability information. The algorithm capability information is used to indicate the algorithm capability of the TV 1102 to process the captured images. For example, the algorithm capability information may indicate one or more image processing algorithms such as face recognition algorithm and autofocus algorithm supported by the TV 1102. In other words, the mobile phone may also synchronize the post-processing algorithm of the TV 1102 to the mobile phone. For example, as shown in FIG13 , the post-processing algorithm of the TV 1102 is retained in the service layer 201a of the mobile phone.

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

It should be noted that, based on the algorithm capability information of TV 1102, the mobile phone calls the retained post-processing algorithm of TV 1102 to process the RAW image captured by TV 1102, and can obtain the same or similar effect as the image processing of the RAW image by TV 1102.

Even if the RAW image captured by the TV 1102 is processed on the mobile phone side, the processed image can achieve the same effect as the image processing on the TV 1102 side. That is, the method of the embodiment of the present application can not only reduce the network bandwidth occupied by the distributed shooting service across devices, but also restore the image effect of the remote device.

In other embodiments, the shooting capability parameters of the TV 1102 may not include algorithm capability information. In other words, the mobile phone may not synchronize the post-processing algorithm of the TV 1102 to the mobile phone. For example, as shown in FIG16 , the post-processing algorithm of the TV 1102 is not retained in the service layer 201a of the mobile phone.

In this embodiment, the service layer 201a of the mobile phone can 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 captured by the mobile phone and the post-processed image from the TV 1102 based on the timestamp, and obtain and display the shooting picture 1501 of the mobile phone and the shooting picture 1502 of the TV 1102 shown in FIG. 15.

It should be noted that the mobile phone calls the post-processing algorithm of the mobile phone to perform image processing on the RAW images captured by the TV 1102, although it is impossible to restore the effect of image processing on the TV 1102 side; however, the post-processing algorithm of the mobile phone is called to perform image processing on both the images captured by the mobile phone and the RAW images captured by the TV 1102, so that the image effects of the pictures taken by the mobile phone and the pictures taken by the TV 1102 can be consistent.

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

Furthermore, the post-processing algorithm of the mobile phone is used to process the RAW image collected by the television 1102, and the mobile phone does not need to retain the post-processing algorithm of the television 1102. In this way, the storage space of the mobile phone can be saved.

In addition, the above embodiments are illustrated by taking a mobile phone as the local device in a distributed shooting scenario. It can be understood that the local device in the distributed shooting scenario can also be a tablet computer, a television, or other electronic device with the above-mentioned shooting function, and the embodiments of the present application do not impose any restrictions on this.

It should be noted that the above embodiment uses the Android system as an example to illustrate the specific method for implementing the distributed shooting function between the various functional modules. It can be understood that corresponding functional modules can also be set in other operating systems to implement the above method. As long as the functions implemented by each device and functional module are similar to the embodiments of the present application, they fall within the scope of the claims of the present application and their equivalent technologies.

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

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

For another example, the first shooting picture may be shooting picture 1 shown in Fig. 6A, and the second shooting picture may be shooting picture 3 shown in Fig. 6A. Shooting picture 1 and shooting picture 2 shown in Fig. 6A are displayed on the same display interface of mobile phone 0 and mobile phone 1.

Some other embodiments of the present application provide an electronic device, which may include: the above-mentioned touch screen, a memory and one or more processors. The touch screen, the memory and the processor are coupled. The memory is used to store computer program code, and the computer program code includes computer instructions. When the processor executes the computer instructions, the electronic device can execute the various functions or steps executed by the mobile phone in the above-mentioned method embodiment. The structure of the electronic device can refer to the structure of the mobile phone shown in Figure 2B.

The embodiment of the present application also provides a chip system, as shown in Figure 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 can be interconnected by lines. For example, the interface circuit 1702 can be used to receive signals from other devices (such as the memory of the electronic device). For another example, the interface circuit 1702 can be used to send signals to other devices (such as 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 perform the various steps in the above embodiments. Of course, the chip system can also include other discrete devices, which are not specifically limited in the embodiment of the present application.

An embodiment of the present application also provides a computer storage medium, which includes computer instructions. When the computer instructions are executed on the above-mentioned electronic device, the electronic device executes each function or step executed by the mobile phone in the above-mentioned method embodiment.

The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute each function or step executed by the mobile phone in the above method embodiment.

Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be 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 distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present 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 separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or 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 can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (6)

1. A distributed shooting method, comprising: The first device receives a first operation of a user selecting to perform synchronous shooting with the second device; In response to the first operation, the first device starts to collect 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 a first captured image corresponding to the first image data in a first window, and displays a second captured image corresponding to the second image data in a second window, wherein the first window and the second window are located on the same display interface; After the first device receives a first operation of the user selecting to perform synchronous shooting with the second device, the method further includes: The first device establishes a control session and a data session between the first device and the second device; 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 for instructing the second device to capture an image, and the data session is used to transmit the second image data from the second device; After the first device receives a first operation of the user selecting to perform synchronous shooting with the second device, the method further includes: 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 captured picture corresponding to the first image data in the first window and displays the second captured picture corresponding to the second image data in the second window, the method further includes: The first device performs image processing on the first image data according to a shooting capability parameter of the first device to obtain the first shooting picture, where the shooting capability parameter of the first device is used to indicate an image processing algorithm supported by the first 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; The method also includes: the first device sending 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. 2. The method according to claim 1, wherein the first device instructs the second device to start collecting image data, comprising: The first device sends a shooting instruction to the second device; 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 RAW image collected by the second device to the first device. 3. The method according to claim 1 or 2, characterized in that before the first device receives a 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 clicking operation on a function button for implementing distributed shooting, and at least one of a preview interface of a camera application of the first device, a chat interface of a video communication application of the first device, a control center of the first device, a drop-down menu, or a negative first screen includes the function button; In response to a second operation for clicking the function button, the first device displays a candidate device list in the preview interface, the candidate device list including the second device; The first operation is an operation in which a user selects the second device in the candidate device list. 4. The method according to any one of claims 1-3 is characterized in that the synchronous shooting includes at least one of synchronous video recording, synchronous photo taking, synchronous live broadcast or synchronous video calling. 5. 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; 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 executes the method as described in any one of claims 1 to 4. 6. 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 executes the method as claimed in any one of claims 1 to 4.