An image shooting method, electronic device and system

Abstract

The application discloses an image shooting method, an electronic device and a system, and relates to the technical field of terminals. In the case that a first device needs to acquire an image, a second device can be called to shoot the image. Then, the second device returns the shot image to the first device. Thus, the limitation that the image can only be acquired from a local gallery of the first device or shot by using a local camera of the first device can be broken.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to an image capturing method, electronic device and system. Background Technology

[0002] When using applications on electronic devices such as tablets and laptops, the applications may need to access the camera to take pictures or videos at any time. For example, when editing a document on a tablet or laptop, the user may need to insert pictures taken of the surrounding environment. However, due to the large size of tablets and laptops or the limited capabilities of their cameras, the flexibility and quality of taking pictures are usually low, making it difficult to easily capture ideal images. Summary of the Invention

[0003] This application provides an image capturing method, electronic device, and system that can provide users with a convenient and comfortable picture or video capturing experience.

[0004] In a first aspect, this application provides an image capturing method applied to a first device. The first device displays a first interface of a first application. In response to a user's first operation on the first interface (such as inserting an image), the first device displays a first option, the first operation being used to acquire an image (including a picture or video). In response to the user's selection of the first option, the first device sends a first request to a second device indicated by the first option. The first request includes device information of the first device and a request type. The device information of the first device is used by the remote camera of the second device to distribute images captured by the system camera of the second device to the first device based on the device information of the first device. The remote camera is an application with the capability to invoke the system camera to capture images and distribute the images captured by the system camera. The request type indicates that the first request invokes the remote camera. The first device receives the image captured by the second device and an application identifier. The first device displays the image captured by the second device on the first interface based on the application identifier.

[0005] In summary, by adopting this application, when the first device needs to acquire an image, it can request a second device to capture the image. This overcomes the limitation of only being able to acquire images locally (including from a local camera or local photo library). Especially for first devices with limited shooting flexibility, such as tablets and laptops, the ability to use a second device (such as a mobile phone) to capture images provides users with a convenient and comfortable image-capturing experience.

[0006] In one possible design of the first aspect, the method further includes: a first device receiving first information from a second device, the first information indicating that the second device has the capability of a remote camera. In response to the first information, the first device records information indicating that the second device has the capability of a remote camera. Accordingly, the first device displays a first option, including: if the first device has recorded information indicating that the second device has the capability of a remote camera, the first device displays the first option.

[0007] Only if the second device has remote camera functionality, such as having a remote camera installed and allowing the use of the remote camera to capture images for other devices, can the second device capture images for other devices. Therefore, before displaying the first option, the first device needs to determine if the second device has remote camera functionality to accurately call upon the device with remote camera capability to capture images.

[0008] In one possible design of the first aspect, devices with the same account can synchronize in real time whether a remote camera is occupied. Accordingly, the method further includes: a first device receiving second information from a second device, the second information indicating that the remote camera is occupied. In response to the second information, the first device updates the status of the remote camera to occupied. And / or, the first device receiving third information from the second device, the third information indicating that the remote camera is not occupied. In response to the third information, the first device updates the status of the remote camera to unoccupied. The first device displays a first option, including: if the remote camera's status is unoccupied, the first device displays the first option.

[0009] In this way, the first device can accurately call up the remote camera that is not in use, avoiding conflicts in the call.

[0010] In one possible design of the first aspect, the aforementioned first option is an option for a device within the near-field communication range of the first device and / or a device logged into the same user account as the first device.

[0011] If the second device is within the near-field communication range of the first device, it indicates that the first and second devices can transmit data such as request calls and images via near-field communication. Furthermore, if the first and second devices are logged into the same user account, it indicates that the first and second devices can trust each other.

[0012] This allows for the transmission of call requests, image data, and other data between mutually trusted devices via near-field communication.

[0013] In one possible design of the first aspect, the first device includes a device management service. The first device receives first information from the second device, including: the device management service receiving synchronized first information from the second device. The first device records information about the second device's ability to use a remote camera, including: the device management service recording this information.

[0014] In another possible design of the first aspect, the first device may further include a communication service. The method further includes: the communication service discovering that the second device is within the near-field communication range of the first device, and / or that the second device is logged into the same user account as the first device. The communication service updates the second device as an online device to the device management service.

[0015] In other words, the device management service of the first device can maintain devices that support remote camera functions and devices with the same account within the near-field communication range.

[0016] In another possible design of the first aspect, the first device further includes a continuity service. Before the first device displays the first option, the method further includes: a first application sending a query request to the continuity service; the continuity service forwarding the query request to a device management service; in response to the query request, if the device management service includes information that the second device has the capability of a remote camera and the second device is an online device, the device management service returning device information of the second device to the continuity service; the continuity service returning the device information of the second device to the first application; and the first device displaying the first option including: the first application displaying the first option corresponding to the second device based on the device information of the second device.

[0017] In this way, the first device can query the device management service to identify available devices that support remote cameras, are within the near-field communication range, and coincidentally encounter the same user account, and provide the user with the option of available devices to choose from.

[0018] In one possible design of the first aspect, the device information of the second device includes the username of the user account (e.g., Tom, Jenny), the device model of the second device (e.g., Model A, Model B) and / or the device type of the second device (e.g., mobile phone, tablet), and the first option includes the username, device model and / or device type.

[0019] This allows the first option to indicate the corresponding available device. At the same time, the username, device model, and device type are not unique identifiers; multiple devices may have the same username, device model, and device type, thus avoiding excessive disclosure of available device information.

[0020] In one possible design of the first aspect, after the communication service discovers that the second device is within the near-field communication range of the first device, and / or that the second device is logged into the same user account as the first device, the method further includes: the communication service assigning a temporary ID to the second device, wherein the device information of the second device includes the temporary ID. Correspondingly, the first device sends a first request to the second device indicated by the first option, including: the first application sending the first request to the second device indicated by the temporary ID.

[0021] This avoids privacy leaks caused by sending fixed identification information such as the MAC address and serial number of available devices to target applications.

[0022] In one possible design of the first aspect, the method further includes: if the second device meets preset conditions, in response to the user's selection of the first option, the first device issues a first prompt message, indicating that the second device is taking pictures. Meeting the preset conditions indicates that the second device can take pictures of the first device. For example, preset conditions include the system camera being in an idle state and / or the second device being powered on. This provides the user with a clear instruction.

[0023] In one possible design of the first aspect, the first device includes a connection service and a communication service. Accordingly, in response to a user's selection of a first option, the first device sends a first request to a second device indicated by the first option, including: in response to the user's selection of the first option, the first application sends a second request to the connection service, the second request including device information of the second device and a request type, the device information of the second device indicating the device used to capture the image. In response to the second request, the connection service sends a third request to the communication service, the third request including device information of the first device, device information of the second device, an application identifier, and a request type. In response to the third request, the communication service sends the first request to the second device indicated by the device information of the second device in the third request.

[0024] In this way, the first request can be sent to the second device through connection service and communication service.

[0025] In one possible design of the first aspect, the first device includes a communication service and a connection service. Accordingly, the first device receives an image captured by the second device and an application identifier of the first application, including: the communication service receiving the image captured by the second device and the application identifier of the first application; and the communication service sending the image and application identifier to the connection service. Thus, the image captured by the second device can be received through the communication service and the connection service.

[0026] Furthermore, the first device displays the image captured by the second device on the first interface based on the application identifier, including: the continuity service sending the image to the first application indicated by the application identifier; and the first application displaying the image. In this way, the first device can accurately return the image to the first application indicated by the application identifier.

[0027] Secondly, this application provides an image capturing method applied to a second device. The second device receives a first request, which includes device information of the first device, an application identifier of a first application, and a request type. The request type indicates that the first request invokes a remote camera, and the remote camera is an application within the second device. In response to the first request, the second device activates the remote camera and records the device information and application identifier of the first device in the remote camera. In response to activating the remote camera, the second device displays a second interface, which is a shooting preview interface for the system camera within the second device. In response to a user's shooting operation, the second device captures an image. The second device sends the image, along with the application identifier from the remote camera, to the first device indicated by the device information of the first device.

[0028] In summary, by employing this application, the second device can activate a remote camera to invoke the system camera to capture images, and then distribute the images captured by the system camera to the first device. This provides the first device with a remote shooting capability.

[0029] In one possible design of the second aspect, the method further includes: the second device issuing a second prompt message to prompt the first device to request that it (i.e., the second device) capture an image. The second device activating the remote camera includes: in response to a user's confirmation of the second prompt message, the second device activating the remote camera.

[0030] This way, the remote camera can be started only after user confirmation, avoiding interference with the normal use of the second device.

[0031] In one possible design of the second aspect, the second device includes a communication service and a connection service. Accordingly, the second device receives a first request, including: the communication service receiving the first request. And, in response to the first request, the second device activates a remote camera and records device information of the first device and application identifier of the first application in the remote camera, including: in response to receiving the first request, the communication service sends a fourth request to the connection service, the fourth request including device information of the first device, application identifier of the first application, and request type. In response to receiving the fourth request, the connection service activates the remote camera and sends the device information of the first device and application identifier of the first application to the remote camera. The remote camera records the device information of the first device and application identifier of the first application.

[0032] In this way, the application identifier of the first application and the device information of the first device can be accurately transmitted to the remote camera through communication services and connection services, so that the remote camera can understand the reason for starting and facilitate subsequent image distribution.

[0033] In one possible design of the second aspect, the second device also includes a system camera. The second device displays a second interface, including: a remote camera invoking the system camera within the second device, and the system camera displaying the second interface. The second device captures images, including: the system camera capturing images.

[0034] In one possible design of the second aspect, the second device sends an image to the first device indicated by the device information of the first device recorded in the remote camera, and sends an application identifier of the first application recorded in the remote camera, including: the remote camera sending the image, the device information of the first device, and the application identifier of the first application to the connection service; the connection service sending the image, the device information of the first device, and the application identifier of the first application to the communication service; and the communication service sending the image and the application identifier of the first application to the first device indicated by the device information of the first device.

[0035] When the second device transmits images to the first device, it will also send the application identifier of the first application recorded in the remote camera to the first device in sequence through the connection service and the communication service, so that the first device can clearly identify the application receiving the image as the first application.

[0036] In one possible design of the second aspect, before the second device receives the first request, the method further includes: the second device synchronizing first information to the first device, the first information indicating that the second device has the capability of a remote camera.

[0037] Specifically, when the second device has a remote camera installed and is permitted to use the remote camera to capture images for other devices, it can synchronize its remote camera capability with the account device, so that the account device is aware that the second device has a remote camera capability. This allows the second device to invoke its remote camera capability when needed.

[0038] In one possible design of the second aspect, after the second device starts capturing images and before the second device stops capturing images, the method further includes: the second device synchronizing second information to the first device, the second information indicating that the remote camera of the second device is occupied. After the second device stops capturing images, the method further includes: the second device synchronizing third information to the first device, the third information indicating that the remote camera of the second device is not occupied.

[0039] In this way, the second device can synchronize the working status (occupied or unoccupied) of its remote camera to other devices on the same account in real time, so that other devices on the same account can know the working status of the remote camera of the second device and avoid conflicts in the calls.

[0040] In one possible design of the second aspect, the second device includes a device management service, and the method further includes: the device management service synchronizing information to the first device regarding the second device's ability to have a remote camera and / or whether the second device's remote camera is occupied or not.

[0041] Thirdly, this application provides an image capturing method. A first device displays a first interface of a first application. In response to a user's first operation on the first interface, the first device displays a first option, the first operation being used to acquire an image. In response to the user's selection of the first option, the first device sends a first request to a second device indicated by the first option. The first request includes device information of the first device, an application identifier of the first application, and a request type. The request type indicates that the first request invokes a remote camera, and the remote camera is an application in the second device. The second device receives the first request. In response to the first request, the second device activates the remote camera and records the device information of the first device and the application identifier of the first application in the remote camera. In response to activating the remote camera, the second device displays a second interface, which is the viewfinder interface of the system camera in the second device. In response to the user's shooting operation, the second device captures an image. The second device sends the image, along with the application identifier from the remote camera, to the first device indicated by the device information of the first device.

[0042] In summary, by adopting this application, when the first device needs to acquire an image, it can request a second device to capture the image. This overcomes the limitation of only being able to acquire images locally (including from a local camera or local photo library). Especially for first devices with limited shooting flexibility, such as tablets and laptops, the ability to use a second device (such as a mobile phone) to capture images provides users with a convenient and comfortable image-capturing experience.

[0043] Fourthly, this application also provides an electronic device, which is a first device or a second device, comprising: a memory and one or more processors, wherein the memory is coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, and when the computer instructions are executed by the processor, the electronic device performs the methods in the first aspect, the second aspect and any possible design of the above.

[0044] Fifthly, this application also provides a chip system applied to an electronic device including a processor and a memory. The chip system includes one or more interface circuits and one or more processors, which are interconnected via lines. The interface circuits are used to receive signals from the memory of the electronic device and send signals to the processor. The signals include computer instructions stored in the memory. When the processor executes the computer instructions, it causes the electronic device to perform the methods in the first aspect, the second aspect, and any possible design of the above.

[0045] Sixthly, this application also provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause a server to perform the methods described in the first aspect, the second aspect, and any possible design of the above.

[0046] In a seventh aspect, this application provides a computer program product that, when run on a computer, causes the computer to perform a method as described in the first aspect, the second aspect, and any possible design thereof.

[0047] Understandably, the beneficial effects that the servers, electronic devices, chip systems, computer storage media, and computer program products provided above can be referenced to the beneficial effects in the first aspect, the second aspect, and any possible design method thereof, and will not be repeated here. Attached Figure Description

[0048] Figure 1 One of the interface diagrams of a laptop computer provided in an embodiment of this application;

[0049] Figure 2 This is a schematic diagram of the composition of a communication system provided in an embodiment of this application;

[0050] Figure 3 A hardware structure diagram of an electronic device provided in an embodiment of this application;

[0051] Figure 4A A software architecture diagram of the first device provided in the embodiments of this application;

[0052] Figure 4B A software architecture diagram of the second device provided in the embodiments of this application;

[0053] Figure 5 This is one of the interactive flowcharts of the image capturing method provided in the embodiments of this application;

[0054] Figure 6A A schematic diagram illustrating the principle of the synchronous remote camera capability provided in the embodiments of this application;

[0055] Figure 6BThis is a schematic diagram illustrating the principle of online device discovery provided in an embodiment of this application.

[0056] Figure 7A A second interface diagram of a laptop computer provided in an embodiment of this application;

[0057] Figure 7B The third interface diagram of the laptop provided in this application embodiment;

[0058] Figure 7C The fourth diagram of the interface of a laptop computer provided in the embodiments of this application;

[0059] Figure 8A One of the interface diagrams of a mobile phone provided in the embodiments of this application;

[0060] Figure 8B A second screenshot of a mobile phone interface provided in an embodiment of this application;

[0061] Figure 8C The third screenshot of the mobile phone interface provided in this application embodiment;

[0062] Figure 9 Fifth of the interface diagrams of a laptop computer provided in the embodiments of this application;

[0063] Figure 10 A schematic diagram illustrating how multiple devices sequentially invoke the remote camera of the same device, as provided in an embodiment of this application;

[0064] Figure 11 This is the second interactive flowchart of the image capturing method provided in the embodiments of this application;

[0065] Figure 12 The third interactive flowchart of the image capturing method provided in the embodiments of this application;

[0066] Figure 13 The fourth screenshot of the mobile phone interface provided in this application embodiment;

[0067] Figure 14 This is a structural diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0068] The technical solutions of the embodiments of this application are described below with reference to the accompanying drawings. In the description of the embodiments of this application, the terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to limit the application. As used in the specification and appended claims of this application, the singular expressions "a," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, "at least one" and "one or more" refer to one or more (including two). The term "and / or" is used to describe the relationship between related objects, indicating that three relationships can exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0069] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized. The term "connection" includes direct connections and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated.

[0070] In the embodiments of this application, the words "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0071] The image capture method provided in this application can be applied to scenarios where images / videos are acquired while running applications on electronic devices such as tablets and laptops. It should be understood that a video typically consists of multiple image frames, each of which is an image. Therefore, for ease of explanation, images / videos will be referred to simply as images in the following text.

[0072] Taking image acquisition as an example, the aforementioned applications can be any application with functions such as inserting, editing, sending, and scanning images. During the operation of these applications, images can be acquired and processed such as inserting, editing, sending, and scanning.

[0073] For example, word processing systems (WPS), Office, and memos are all document editing applications that have the function of inserting images. Therefore, some of the above-mentioned applications can be document editing applications such as WPS, Office, and memos.

[0074] For example, shopping apps have the function of scanning product images, and banking apps have the function of scanning ID card images; thus, some of the aforementioned apps can be shopping apps or banking apps.

[0075] For another example, video editing applications and image processing applications both have image editing functions, so some of the above applications can be video editing applications and image processing applications.

[0076] For example, if a chat application has the function of sending pictures, then some of the above applications can be chat applications.

[0077] In the following text, for ease of explanation, the above applications will be collectively referred to as the target application (or the first application).

[0078] The following example, using a document editing application as the target application, illustrates the application scenario of this application:

[0079] See Figure 1 When a laptop is running a document editing application, it can display... Figure 1 The interface 101 shown includes editable document content, such as "travel diary...", and also includes a control 102 for inserting images. The laptop can receive user clicks on the control 102, and in response, the laptop acquires an image and inserts it into the document content. The image capturing method provided in this embodiment can be applied to scenarios where the user clicks the control 102 to acquire an image.

[0080] In some conventional technologies, in the aforementioned image acquisition scenario, electronic devices can only acquire images already stored locally. For example, a laptop computer responds to a user's request... Figure 1 The click operation of control 102 in interface 101 shown can display Figure 1 The interface 103 shown includes a dialog box 104. In dialog box 104, the user can select an image from locally stored images on the laptop and insert it into the document being edited.

[0081] However, in some cases, the electronic devices currently running the target application (such as...) Figure 1 The laptop (in the case of the user) does not store the images the user needs, therefore it cannot meet the user's need to obtain images.

[0082] In other conventional technologies, electronic devices can support directly capturing images by accessing the local camera and then acquiring those images. For example, a laptop computer responds to a user's... Figure 1 The click operation of control 102 in the interface 101 shown can display Figure 1 The interface 103 shown includes a dialog box 104. Users can first take a picture using the laptop's camera, then locate the corresponding picture in dialog box 104 and insert it into the document being edited.

[0083] However, in some situations, the electronic device currently running the target application may not be able to easily capture suitable images. A typical reason is that the large size of electronic devices such as tablets and laptops, or the limited capabilities of their cameras, often results in lower flexibility or poorer image quality, making it difficult to easily capture ideal pictures.

[0084] Therefore, if, in the above-mentioned image acquisition scenarios, electronic devices can only use their local cameras to capture images or acquire images already stored locally, it is highly likely that they will not be able to meet the target application's image requirements.

[0085] Based on this, this application provides an image capturing method that can be applied to the aforementioned image acquisition scenarios. Specifically, when an electronic device is capturing an image, it can call upon another device to capture the image. Then, the other device returns the captured image to the electronic device. In this way, the method not only overcomes the limitation of only being able to acquire images locally (including from a local camera or local image library), but also provides a convenient and comfortable image capturing experience, especially for electronic devices with limited shooting flexibility such as tablets and laptops, by allowing the use of other electronic devices for capturing images.

[0086] This application also provides a communication system, see [link to relevant documentation] Figure 2 The communication system includes a first device (such as...) Figure 2 The laptop computer 210 shown) and at least one second device (such as Figure 2 (The mobile phone 220 and tablet 230 shown).

[0087] The first device contains a target application, which may require image acquisition during its operation. The second device includes an application (referred to as a remote camera) that enables remote image capture and distribution. The remote camera can receive requests from the first device and distribute images captured by the second device's system camera to the first device.

[0088] The first and second devices can communicate with each other. This communication connection includes an internet connection. Through the internet connection, the second device can synchronize (i.e., send) its remote camera functionality to the first device, allowing the first device to discover and access the second device's remote camera. The communication connection also includes a near-field communication (NFC) connection. Through NFC, the first device can send point-to-point access requests to the second device, and the second device can transmit captured images to the first device. NFC includes technologies such as Bluetooth, Wireless Fidelity (Wi-Fi), and Near Field Communication (NFC).

[0089] It should be noted that, in this embodiment of the application, compared with an internet connection, transmitting request requests and image data via near-field communication (NFC) offers several advantages. First, it allows for point-to-point information transmission, which is more conducive to ensuring information security. Second, if NFC technologies such as Bluetooth or NFC are used, which do not rely on a network, the information transmission rate is not affected by network factors, allowing for more stable and faster information transmission. Moreover, even if the first device and / or the second device are not connected to a network, remote camera access and image data transmission can still be achieved.

[0090] It should be noted that the first and second devices do not need to establish both an internet connection and a near-field communication (NFC) connection simultaneously. For example, when calling a remote camera, only an NFC connection needs to be established, without needing to establish an internet connection.

[0091] In some examples, the same system-level user account can be logged in on both the first and second devices, such as the same Account, same Accounts, etc. It should be understood that devices logged into the same user account (such as the first device and the second device) can join the same trust ring through identity authentication. This allows information exchange to occur only within the trust ring, such as the ability to synchronize remote cameras, transmit request calls, and transfer images, ensuring device security.

[0092] The distinction between the first device and the second device is based solely on the different functional roles played by the electronic device in the image acquisition scenario. The first device is the image-requiring device, and the second device is the image-providing device. It should be understood that the same electronic device can function as the first device in some scenarios and as the second device in others. For example, if the above... Figure 2 The mobile phone 220 or tablet 230 in the image acquires images from other devices, which is the device requiring the image; it can also be the first device. If the above... Figure 2 The laptop computer 210 has a remote camera capability, which can also be used as an image-providing device, i.e., as a second device.

[0093] For example, the aforementioned first / second device can be a handheld device, in-vehicle device, etc., such as a mobile phone, tablet, laptop, PDA, mobile internet device (MID), virtual reality (VR) device, augmented reality (AR) device, wireless device in industrial control, wireless device in self-driving, wireless device in remote medical surgery, wireless device in smart grid, wireless device in transportation safety, wireless device in smart city, wireless device in smart home, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, personal computer, etc. The embodiments of this application do not limit this to computers (PCs), computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks or terminal devices in future evolved public land mobile networks (PLMNs).

[0094] The aforementioned first / second device can also be a wearable device. For example, smartwatches or smart glasses, as well as devices that focus on a specific type of application function and can be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0095] The aforementioned first / second device can also be a terminal device in an Internet of Things (IoT) system.

[0096] See Figure 3 This is a hardware structure diagram of an electronic device (such as a first device / second device) provided in an embodiment of this application. Figure 3 As shown, taking a mobile phone as an example, the electronic device may include: a processor 310, an external memory interface 320, an internal memory 321, a universal serial bus (USB) interface 330, a charging management module 340, a power management module 341, a battery 342, an antenna 1, an antenna 2, a mobile communication module 350, a wireless communication module 360, an audio module 370, a speaker 370A, a receiver 370B, a microphone 370C, a headphone jack 370D, a sensor module 380, buttons 390, a motor 391, an indicator 392, a camera 393, a display screen 394, and a subscriber identification module (SIM) card interface 395, etc.

[0097] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device. In other embodiments, the electronic device may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0098] Processor 310 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. The different processing units may be independent devices or integrated into one or more processors.

[0099] A controller can be the nerve center and command center of an electronic device. Based on the instruction opcode and timing signals, the controller generates operation control signals to control the fetching and execution of instructions.

[0100] The charging management module 340 receives charging input from a charger, which can be a wireless charger or a wired charger. While charging the battery 342, the charging management module 340 can also supply power to electronic devices via the power management module 341.

[0101] The power management module 341 connects the battery 342, the charging management module 340, and the processor 310. The power management module 341 receives input from the battery 342 and / or the charging management module 340, providing power to the processor 310, internal memory 321, external memory, display screen 394, camera 393, and wireless communication module 360. The power management module 341 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance).

[0102] The wireless communication function of electronic devices can be realized through antenna 1, antenna 2, mobile communication module 350, wireless communication module 360, modem processor and baseband processor, etc.

[0103] Electronic devices implement display functions through a GPU, a display screen 394, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 394 and the application processor. The GPU performs mathematical and geometric calculations and is used for graphics rendering. The processor 310 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0104] Electronic devices can achieve shooting functions through ISP, camera 393, video codec, GPU, display 394 and application processor.

[0105] In some embodiments, when the electronic device is used as a second device, it can invoke the camera 393 to capture images and return them to the first device based on a request from the first device.

[0106] The external storage interface 320 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor 310 through the external storage interface 320 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0107] Internal memory 321 can be used to store computer executable program code, which includes instructions. Processor 310 executes various functional applications and data processing of the electronic device by running the instructions stored in internal memory 321. Internal memory 321 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the electronic device (such as audio data, phonebook, etc.). Furthermore, internal memory 321 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0108] Electronic devices can implement audio functions through audio modules 370, speakers 370A, receivers 370B, microphones 370C, headphone jacks 370D, and application processors. Examples include music playback and recording.

[0109] Buttons 390 include a power button, volume buttons, etc. Buttons 390 can be mechanical buttons or touch-sensitive buttons. Electronic devices can receive button inputs and generate key signal inputs related to user settings and function control.

[0110] Motor 391 can generate vibration alerts. Motor 391 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can be corresponding to touch operations applied to different applications (such as taking photos, playing audio, etc.). Motor 391 can also correspond to different vibration feedback effects for touch operations applied to different areas of the display screen 394. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0111] Indicator 392 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0112] The SIM card interface 395 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 395 to establish contact with the electronic device. The electronic device can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 395 supports Nano SIM cards, Micro SIM cards, and other SIM cards.

[0113] In this embodiment, the software system of the electronic device (such as the first device / second device) can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. In this document, a layered architecture is used as the primary consideration. Taking the system as an example, the software structure of the first device and the second device are illustrated.

[0114] See Figure 4A This is a software architecture diagram of the first device provided in an embodiment of this application. See also... Figure 4B This is a software architecture diagram of the second device provided in an embodiment of this application. Figure 4A and Figure 4B As shown, the layered architecture divides the software into several layers, each with a clear role and function. Data is transferred and communicated between layers through software interfaces. In some embodiments, [the following is omitted as the text is incomplete and likely refers to a specific implementation or feature]. The system is divided into five layers, from top to bottom: application layer, application framework layer, etc. runtime ( The runtime and system libraries, the hardware abstraction layer (HAL), and the kernel layer.

[0115] The application layer can include a series of application packages. Application packages can include applications such as memos, calculators, calling apps, and browsers.

[0116] In this embodiment, the application layer of the first device also includes target applications, such as document editing applications like WPS, Office, and Notes, shopping applications, banking applications, video editing applications, image processing applications, and social applications.

[0117] The application layer of the second device also includes a remote camera. The remote camera receives calls from the first device, calls the second device's system camera to take images, and then sends them back to the first device. In other words, compared to the system camera, the remote camera supports orchestrated transmission by the caller and can decide who receives the images.

[0118] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0119] The application framework layer may include a notification manager, window manager, resource manager, content provider, and view system.

[0120] The notification manager allows applications to display notifications in the status bar. These notifications can be used to convey informational messages and can disappear automatically after a short pause, requiring no user interaction. Examples include notifications of download completion and message alerts. Notifications can also appear as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating the device, and flashing indicator lights. The window manager manages windowed applications. It can obtain the screen size, determine if a status bar is present, lock the screen, allow screen touch, dragging, and screenshotting. The resource manager provides applications with various resources, such as localized strings, icons, images, layout files, and video files. The content provider enables data sharing between different applications, allowing one application to access data in another while ensuring the security of the accessed data. The view system is responsible for rendering the application's interface and handling events.

[0121] In addition, the application framework layer may also include connection services, application authentication services, communication services, and device management services (Profile).

[0122] The connection service provides the target application with near-field device discovery and awareness, as well as the ability to send data and files. For example, the connection service can be responsible for the target application's access. Furthermore, after the target application accesses the connection service, the service can also be responsible for querying devices that the target application can invoke and take pictures of (i.e., available devices hereinafter), and transferring invocation requests, images, and other data across devices.

[0123] Application authentication services can be responsible for verifying the legitimacy of applications, such as verifying the application's identity and permissions. For example, the application authentication module can verify the legitimacy of the target application requesting access to the connection service, and only allow the target application to access the connection service if its legitimacy is confirmed. This prevents unauthorized applications from being provided with services that allow them to access remote cameras for taking pictures.

[0124] Communication services, such as The Magic Link intelligent interconnection service can be used to achieve data transmission between devices, secure authentication and account authorization for devices with the same account, device self-discovery and self-organizing networks, etc. For example, through the communication service, a first device can discover a second device located in the near field and verify the identity of the second device. After verifying that the second device is a trusted device (i.e., a device logged into the same user account), the first device and the second device can transmit call requests and images, etc.

[0125] Device management services can be viewed as a database for synchronizing data between devices. This database can record the capabilities of devices with the same account, the availability of those capabilities, and information about near-field devices. For example, the device management service for the first device can record information such as the second device's ability to use a remote camera, the availability of that remote camera's capability, and devices within the near-field communication range.

[0126] The runtime includes the core libraries and the virtual machine. runtime is responsible for System scheduling and management.

[0127] The core library consists of two parts: one part is the functionalities called by the Java language, and the other part is the Android core library.

[0128] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0129] A system library can include multiple functional modules. For example, media libraries, function libraries, and graphics processing libraries (such as OpenGL ES).

[0130] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0131] The function library provides developers with API interfaces for various services, making it easy for them to quickly integrate and implement various functions.

[0132] Graphics processing libraries are used to implement graphics drawing, image rendering, compositing, and layer processing.

[0133] The Hardware Abstraction Layer (HAL) is a layer of abstraction situated between the kernel layer and the Android runtime. The HAL can be a wrapper around hardware drivers, providing a unified interface for upper-layer applications to call them. The HAL can include modules such as Bluetooth and Wi-Fi. For example, the Bluetooth and Wi-Fi modules can shield the specific hardware implementation details of the Bluetooth and Wi-Fi drivers in the kernel layer, allowing upper-layer applications to implement Bluetooth and Wi-Fi functions by calling interfaces without needing to know the specific implementation details of the kernel-level hardware drivers.

[0134] The kernel layer is the layer between hardware and software. The kernel layer can include display drivers, camera drivers, audio drivers, Bluetooth drivers, WiFi drivers, Universal Serial Bus (USB) drivers, central processing unit (CPU) drivers, and so on.

[0135] In some embodiments, communication services (such as Magic Link) can connect across devices through relevant near-field communication modules such as Bluetooth drivers and WiFi drivers, enabling devices to discover themselves and form their own networks.

[0136] The embodiments of this application will be combined with Figure 4A and Figure 4B The software architecture is described below to explain the implementation of the image capture method: After the target application on the first device connects to the connection service, if the target application needs to acquire an image, it can sequentially query available devices through the connection service and device management service of the first device, including the second device. Then, the target application sequentially sends a call request to the second device among the available devices through the connection service and communication service of the first device, requesting to invoke the remote camera of the second device. The second device's connection service receives the call request and activates its remote camera to capture an image. After the second device's system camera captures the image, it can transmit the image to the target application on the first device through the remote camera, connection service, and communication service of the second device, as well as the communication service and connection service of the first device. In this way, the target application on the first device obtains the image captured by the second device, breaking the limitation of only being able to acquire images locally (including local cameras or local image libraries), and more flexibly meeting the image needs of electronic devices.

[0137] At this point, it should be noted that the above... Figure 4A and Figure 4B All based on Android TM Taking the system as an example, the software architecture of the first and second devices is illustrated. In practice, the operating system of the first and / or second devices can also be Windows. TM System. In Windows TM In the operating system, the application layer (such as a PC management application) can also integrate the connection services, application authentication services, communication services, and device management services from the aforementioned application framework layer, as well as the functions of the Bluetooth and Wi-Fi modules from the hardware abstraction layer. The application layer completes near-field communication with the peer device by calling the Bluetooth or Wi-Fi driver, enabling data transmission between devices.

[0138] The image capturing method provided in this application embodiment can be completed in a communication system consisting of a first device and a second device having the above-described hardware and software structure. The image capturing method provided in this application embodiment will be further described in detail below with reference to the accompanying drawings, taking a laptop computer 210 as the first device and a mobile phone 220 as the second device.

[0139] See Figure 5 The image capturing method provided in this application includes the following steps:

[0140] S501 and laptop 210 discover (phone 220) devices that support remote cameras and online devices.

[0141] The laptop computer 210 can identify available devices that support remote cameras and can transmit images using near-field communication, and then invoke the remote camera of the available device to capture images. Thus, the laptop computer 210 can discover devices that support remote cameras, as well as online devices within the near-field communication range.

[0142] In some embodiments, the process by which the laptop 210 discovers a device that supports a remote camera may include:

[0143] For any device, if the same user account is logged in on the device and the laptop 210, and the device supports a remote camera, then the device can synchronize its remote camera capability with the laptop 210 via the internet. Correspondingly, the laptop 210 can record the device as a device that supports a remote camera.

[0144] For example, see Figure 6A The user accounts logged in on laptop 210, mobile phone 220, and tablet 230 are all... Account 'a' belongs to the same account and both mobile phone 220 and tablet 230 support remote cameras. Therefore, mobile phone 220 and tablet 230 can report their remote camera capability to the cloud via the internet. The cloud can then distribute this information to all devices under the same account, such as sending it to laptop 210 and tablet 230, and vice versa. Laptop 210, upon receiving this information, can record the following information: "Tablet 230 supports remote camera; Mobile phone 220 supports remote camera." For example, laptop 210 can record "Tablet 230 supports remote camera; Mobile phone 220 supports remote camera" in array or matrix form; this embodiment does not specifically limit this.

[0145] Furthermore, the process by which the laptop 210 discovers online devices may include:

[0146] For any device, if the laptop 210 detects that the device is within its near-field communication (NFC) range and verifies that the user account logged in on the device is the same as the user account logged in on the laptop 210, the laptop 210 can mark the device as an online device. For example, if both the laptop 210 and the device have Bluetooth enabled, and the laptop 210 scans for the device via Bluetooth, or if the device and the laptop 210 are connected to the same Wi-Fi network, it can be determined that the device is within the near-field communication range of the laptop 210. Based on this, the laptop 210 and the device verify that both are logged in with the same user account through near-field identity information exchange, thus confirming that the device is an online device.

[0147] Taking Bluetooth communication as an example of near-field communication, see [link to relevant documentation]. Figure 6B Laptop 210 can scan for mobile phone 220, tablet 230 and mobile phone 610 via Bluetooth. All three devices are logged in with user account a. Laptop 210 can then mark mobile phone 220, tablet 230 and mobile phone 610 as online devices.

[0148] After S501 detects devices that support remote cameras and online devices, the laptop 210 responds to user actions to acquire images (such as clicking). Figure 7A (As shown in the operation of "Pictures" 702 in interface 701), the laptop 210 can identify online devices that support remote cameras as available devices for capturing images. For example, Figure 6A In this context, the devices that support remote camera access are the mobile phone 220 and the tablet 230. Figure 6B In this context, the online devices are mobile phone 220, tablet 230, and mobile phone 610. Therefore, laptop computer 210 can identify mobile phone 220 and tablet 230 as available devices for capturing images.

[0149] It should be noted that the above S501 is continuous. After powering on, the laptop 210 continuously detects devices that support remote cameras and online devices. For example, if a new device is logged into the same user account as the laptop 210 and supports remote cameras, then the laptop 210 will detect this new device as a remote camera-enabled device. Alternatively, if a device already detected as supporting remote cameras no longer provides remote camera capabilities, the laptop 210 will remove this device from the list of remote camera-enabled devices. Another example is if a new device enters the near-field communication range of the laptop 210 and is logged into the same user account as the laptop 210, then the new device will be detected as an online device. Yet another example is if a device already detected as an online device goes beyond the near-field communication range of the laptop 210, or switches its logged-in user account, the laptop 210 will remove this device from the list of online devices.

[0150] S502, the laptop computer 210 receives the image acquisition operation (also known as the first operation).

[0151] In some embodiments, the application interface (also referred to as the first interface) of the target application provides a capture control for capturing images. The capture operation can be a preset operation of the user on the capture control, such as clicking, long-pressing, etc.

[0152] For example, see Figure 7A Get the control as Figure 7A The "image" 702 in the interface 701 shown can be accessed by the user clicking on the "image" 702 in the interface 701.

[0153] For example, participants Figure 7B Get controls including Figure 7B The "image" 702 in the interface 701 shown can be accessed via a user's click on the "image" 702 in the interface 701. In response to the user's click on the "image" 702 in the interface 701, the laptop 210 can display... Figure 7B The interface 706 shown includes two options: "Local Gallery" and "Remote Camera" 707. "Local Gallery" can be used to trigger the acquisition of images from the local gallery of the laptop 210. "Remote Camera" 707 can be used to trigger the use of the remote camera of another device (such as mobile phone 220) to capture images. In this example, the acquisition control also includes... Figure 7B The acquisition operation of the "remote camera" 707 in the interface 706 also includes the user's click operation on the "remote camera" 707 in the interface 706. That is, the acquisition operation includes multiple user operations.

[0154] Of course, the acquisition operation is not limited to this. In other embodiments, the acquisition operation can also be a user's preset gesture on the target application's interface, such as a swipe or long press. Alternatively, the acquisition operation can also be a user's input of a preset voice, such as inputting "insert image".

[0155] S503, in response to the acquisition operation, the laptop 210 displays an option for available devices, which are online devices that support remote cameras.

[0156] If there are multiple available devices, multiple options corresponding to each available device can be displayed. Each option for an available device is used to trigger the remote camera of the corresponding available device to capture an image.

[0157] In addition, the available device options include at least one of the following: the username of the user account logged in on the available device (e.g., Tom, Jenny), the device model of the available device (e.g., Model A, Model B, etc.), and the device type (e.g., mobile phone, tablet, etc.), to indicate the available device corresponding to each option.

[0158] The operation to obtain is the user's Figure 7A Taking the click operation of "image" 702 in the interface 701 as an example, the laptop computer 210 responds to the user's click. Figure 7A Clicking on the "image" 702 in interface 701 will display... Figure 7A The interface 703 is shown. Compared to interface 103, interface 703 not only includes the option to retrieve images from the local gallery (i.e., "Local Gallery" in interface 703), but also includes options for available devices, such as "Camera of Tom's Model A Phone" 704 and "Camera of Tom's Model B Tablet" 705. Here, "Tom" is the username of the user account, "Model A" and "Model B" are the device models, and "Phone" and "Tablet" are the device types. "Camera of Tom's Model A Phone" can be used to trigger the use of the remote camera of Tom's Model A phone (e.g., phone 220) to capture images, and "Camera of Tom's Model B Tablet" can be used to trigger the use of the remote camera of Tom's Model B tablet (e.g., tablet 230) to capture images.

[0159] To obtain operations, including user input Figure 7B The click operation of "image" 702 in the interface 701 shown and the user's interaction with it. Figure 7B Taking the click operation of "Remote Camera" 707 in the interface 706 as an example, the laptop computer 210 responds to the user's click. Figure 7B The click operation on "Remote Camera" 707 in interface 706 can display... Figure 7BThe interface shown is 708. Similar to interface 703, interface 708 also includes options for available devices, such as "Camera for Tom's Model A mobile phone" 704 and "Camera for Tom's Model B tablet" 705.

[0160] S504, the laptop computer 210 receives the user's selection of the option for the mobile phone 220 among the available devices.

[0161] The options on phone 220 can also be called the first option. Selection can be done by tapping, long-pressing, or swiping. The following explanation will primarily use tapping as an example.

[0162] The option for mobile phone 220 is Figure 7A Taking "Tom's A-type mobile phone camera" 704 in the interface 703 as an example, the selection operation of the mobile phone 220 can be the clicking operation of "Tom's A-type mobile phone camera" 704 in the interface 703.

[0163] It should be noted that in the aforementioned S503 and S504, the user manually selects the mobile phone 220. In practice, in response to the acquisition operation, the laptop 210 can also automatically select the mobile phone 220.

[0164] For example, the laptop 210 can automatically select the mobile phone 220 based on the priority of available devices. For instance, if the priority is ranked from highest to lowest according to shooting flexibility: mobile phone, tablet, and laptop, then when the available devices include mobile phone 220 and tablet 230, the laptop 210 can automatically select mobile phone 220 to access the remote camera. As another example, the more times a device is accessed, the higher its priority; the fewer times it is accessed, the lower its priority. If the available devices include mobile phone 220 and tablet 230, and mobile phone 220 is accessed more often than tablet 230, then the laptop 210 can automatically select mobile phone 220 to access the remote camera.

[0165] For example, the laptop 210 can record the information of the selected available device after each selection, and automatically select the previously selected available device based on the recorded information in response to the current acquisition operation. In some scenarios, the available devices determined by the laptop 210 in response to the acquisition operation may not include the previously selected available device. If the previously selected available device is not included, the laptop 210 can automatically select one based on priority, or the user can manually select one. This ensures that an available device is selected.

[0166] S505, In response to the selection operation, the laptop 210 sends a request to the mobile phone 220 to access the remote camera.

[0167] The invocation request (also known as the first request) is used to request the invocation of the remote camera.

[0168] For example, in response to user input Figure 7A In the interface 703 shown, the selection operation of "Tom's A-type mobile phone camera" 704 allows the laptop to send a remote camera access request to the mobile phone 220 to request the access of the mobile phone 220's remote camera for shooting.

[0169] The request includes the capability information of the remote camera (which indicates the capability being invoked, i.e., the type of invocation; therefore, the remote camera capability information can also be called the request type), the device information of the laptop 210, and the application identifier of the target application. The remote camera capability information, such as the identifier "remote camera," indicates that the invoked capability is a remote camera capability. The laptop 210 device information, such as the Media Access Control Address (MAC) and device serial number, uniquely identifies the laptop 210 and indicates that the requested device is the laptop 210. The application identifier of the target application indicates that the requested application is the target application. This device information and application identifier are primarily used by the mobile phone 220 to determine the receiving object of the image after it has captured it, i.e., the receiving object is the target application on the laptop 210.

[0170] In some embodiments, if the mobile phone 220 meets the preset conditions for capturing an image, in response to the selection operation, the laptop computer 210 can also issue a prompt indicating that the mobile phone 220 is capturing an image (also referred to as a first prompt message). Meeting the preset conditions indicates that the mobile phone 220 is ready to capture an image. In one specific implementation, the preset conditions include: the second device being powered on, the system camera of the mobile phone 220 being in an idle state, etc. An idle state means that the system camera is not running in the foreground; for example, the mobile phone 220 is not currently displaying a shooting viewfinder.

[0171] For example, if the system camera of mobile phone 220 is in an idle state and mobile phone 220 is powered on, then, in response to the user's... Figure 7A The interface shown is 703 or Figure 7B The selection operation of "Tom's Model A mobile phone camera" 704 in the interface 708 shown can be displayed on the laptop 210. Figure 7CThe interface 709 shown includes a prompt "Tom's Model A phone's camera is taking pictures" 710, indicating that the phone 220 is taking pictures. This prompt may automatically disappear after a preset duration. Alternatively, after displaying the prompt, the laptop 210 will only remove the prompt in response to a user's cancellation operation. For example, the cancellation operation could be a user clicking the "Cancel" button on interface 706. If no cancellation operation is received, the laptop 210 will continue to display the prompt.

[0172] Conversely, if the mobile phone 220 does not meet the preset conditions for capturing an image, such as the mobile phone 220 displaying a shooting viewfinder or being powered off, the laptop 210 can also issue a prompt that the mobile phone 220 cannot capture an image. In this case, in response to the user's preset operation (such as a return operation, closing the prompt, etc.), the laptop 210 can continue to display the options of available devices. In this way, the user can reselect and call up an available device.

[0173] It should be understood that, in response to the selection operation, the laptop 210 can send a remote camera access request to the mobile phone 220, meaning that the laptop 210 can interact with the mobile phone 220 at this time. Therefore, the laptop 210 can obtain information such as whether the mobile phone 220's system camera is idle and whether the mobile phone 220 is powered on, in order to determine whether the mobile phone 220 meets the preset conditions for capturing images.

[0174] S506. In response to the call request, mobile phone 220 starts the remote camera to call the system camera to capture images.

[0175] After activating the remote camera, mobile phone 220 can access the system camera to capture images. For example, upon receiving a request to access the camera, mobile phone 220 can display... Figure 8A The interface 801 shown is the system camera's shooting viewfinder (also known as the second interface). The mobile phone 220 can capture a picture in response to the user's click on the shooting button 802 in interface 801.

[0176] In addition, when the mobile phone 220 starts the remote camera, it also records the device information in the call request in the remote camera, which is used to instruct the laptop 210 to call the remote camera so that the remote camera can identify the recipient of the image.

[0177] It should be understood that the system camera only has the ability to take pictures and does not have the business function of remote distribution. In this embodiment, a remote camera is deployed on top of the system camera. The remote camera can call the system camera to take pictures. Furthermore, the remote camera can also perform remote distribution based on the device information in the call request. This enables the distribution of images captured by the system camera to the laptop computer 210.

[0178] In some scenarios, when phone 220 receives a request, it may already be in use, such as while someone is making a call or playing a game. In this case, directly accessing the remote camera to further access the system camera for taking pictures might affect the usability of phone 220.

[0179] Therefore, in some embodiments, in response to a call request, the mobile phone 220 may issue a prompt (also known as a second prompt message) indicating that the laptop 210 is calling the remote camera, and only after receiving a confirmation event confirming the activation of the remote camera will the remote camera be activated. This avoids affecting the use of the mobile phone 220.

[0180] For example, in response to the call request, mobile phone 220 can display... Figure 8B The interface 803 shown includes a prompt: "Laptop 210 wants to turn on the remote camera, do you want to turn it on now?", and also includes two options: "Yes" and "No". The mobile phone 220 will only start the remote camera in response to the user's selection of the "Yes" option in interface 803. That is, the confirmation event includes the user's selection of the "Yes" option in interface 803. For example, the mobile phone 220 will only display [the following text is missing from the original] in response to the user's selection of the "Yes" option in interface 803. Figure 8B The interface shown is 801.

[0181] Conversely, in response to the user's selection of the "No" option in interface 803, mobile phone 220 can restore the interface before the prompt for laptop 210 to call the remote camera was displayed, such as... Figure 8B The screen displayed is error 804. Please continue playing the video.

[0182] For example, in response to the call request, mobile phone 220 can display... Figure 8C The interface 805 shown includes a prompt: "Laptop 210 wants to turn on the remote camera, do you want to turn it on now?", and also includes two options: "Yes" and "No, turn it on later". Mobile phone 220 can start the remote camera in response to the user's selection of the "Yes" option in interface 805. That is, the confirmation event includes the user's selection of the "Yes" option in interface 805. For example, mobile phone 220 will only display this message in response to the user's selection of the "Yes" option in interface 805. Figure 8CThe interface shown is 801.

[0183] Conversely, in response to the user's selection of the "No, open later" option in interface 805, phone 220 can display... Figure 8C The interface 806 shown includes multiple delay durations, such as 1 minute, 2 minutes, 3 minutes, etc. The user can select a target duration from these options. In response to the user's selection of the target duration (e.g., 5 minutes), the mobile phone 220 can start timing (e.g., starting at 9:00). After the timing reaches the target duration (e.g., 5 minutes at 9:05), the remote camera is activated, as shown in interface 807. That is, the confirmation event includes the user's selection of the target duration in interface 806 and the timing reaching the target duration. For example, the mobile phone 220 will only display the screen after the user selects the target duration in interface 805 and the timing reaches the target duration. Figure 8C The interface shown is 801.

[0184] Additionally, in response to a rejection event indicating a refusal to activate the remote camera, mobile phone 220 does not activate the remote camera and returns a rejection message to laptop computer 210. For example, the prompt from laptop computer 210 to activate the remote camera includes a rejection control, such as... Figure 8B The "No" option in interface 803 shows a rejection event that could be a user's click, long press, or other action on the rejection control. For example, the rejection event could also be an event where phone 220 is displaying a preset interface. This preset interface could be the application interface of a high-privilege application, such as the call interface of a calling application. This would interrupt the operation of the high-privilege application. Alternatively, the preset interface could be the interface for using the system camera, such as a photo-taking interface or a video call interface. This would prevent interruption of the system camera's operation.

[0185] S507. After shooting, the mobile phone 220 transmits the image to the laptop 210.

[0186] In mobile phone 220, after the system camera captures an image, mobile phone 220 can transmit the image to laptop computer 210 based on the device information of laptop computer 210 recorded by the remote camera.

[0187] In some scenarios, multiple applications on laptop 210 may successively access the remote cameras of different devices within a short interval. For example, application 1 on laptop 210 accesses the remote camera of mobile phone 220, and then application 2 on laptop 210 accesses the remote camera of tablet 230. In this case, mobile phone 220 and tablet 230 may transmit the captured images to laptop 210 almost simultaneously. At this point, laptop 210 may struggle to decide which application on laptop 210 to send the images from mobile phone 220 and tablet 230 to.

[0188] To address the aforementioned issues, in some embodiments, in S505, the laptop 210 can further include the application identifier of the target application in the call request. The application identifier of the target application is then transmitted to the mobile phone 220. Correspondingly, in S506, when the mobile phone 220 activates the remote camera, it not only records the device information in the call request in the remote camera but also records the application identifier, instructing the target application on the laptop 210 to call the remote camera to further clarify the recipient of the image. Furthermore, in S507, when the mobile phone 220 transmits an image to the laptop 210, it also transmits the application identifier of the target application recorded in the remote camera, instructing the laptop 210 to send the image back to the target application. Thus, by sending the image and application identifier back to the laptop 210 together, the laptop 210 can identify the receiving application of the image upon receiving it, thereby accurately sending the image back to the corresponding application.

[0189] The S508 and laptop computer 210 display images captured by the mobile phone 220.

[0190] For example, after receiving an image, the laptop 210 can display... Figure 9 The interface 901 shown includes an image 902. Interface 901 also includes a prompt "Tom's Model A phone's camera is taking pictures" 903 and a "Cancel" button 904. In response to the user clicking the "Cancel" button 904, the laptop computer 210 can display... Figure 9 The interface shown is 905. The prompt "Tom's Model A phone's camera is taking pictures" 903 is no longer displayed in interface 905, and the user can continue editing the document.

[0191] In some scenarios, multiple devices may successively access the same device's remote camera within a short interval. For example, see... Figure 10 At 8:30 o'clock, the laptop 210 called the remote camera of the mobile phone 220 to take a picture. Between 8:30 and 8:32, the tablet 230 called the remote camera of the mobile phone 220 to take a picture.

[0192] However, at any given time, only one device can access a remote camera from the same device. In other words, only one device can use a remote camera from the same device at any given time. See also... Figure 10After the laptop 210 accesses the remote camera of the mobile phone 220, the remote camera of the mobile phone 220 remains occupied by the laptop 210 from 8:30 to 8:32. Therefore, during this period, the tablet 230 will be unable to successfully access the remote camera of the mobile phone 220 and will only be able to do so after the remote camera of the mobile phone 220 is released from its occupancy. This results in low access efficiency.

[0193] In response to the above Figure 10 For similar scenarios, see Figure 11 In some embodiments, after the laptop computer 210 sends a call request to the mobile phone 220, such as after S505, it further includes:

[0194] S1101. In response to starting the remote camera, the mobile phone 220 synchronizes the working status of its remote camera with the same account device (such as the laptop 210) to show that it is occupied (also known as second information).

[0195] For example, if the user account logged in on the laptop 210, mobile phone 220 and tablet 230 is Honor account a, then after the mobile phone 220 responds to the call request from the laptop 210 and starts the remote camera, it can synchronize the working status of its remote camera to the laptop 210 and tablet 230 as occupied.

[0196] After executing S1101, devices with the same account (such as laptop 210) can determine that the remote camera on mobile phone 220 is being used.

[0197] Furthermore, in this embodiment, after the shooting is completed, such as after S507, the following steps are also included:

[0198] S1102. In response to the completion of shooting, the mobile phone 220 synchronizes the working status of the remote camera of the mobile phone 220 to a device with the same account (such as a laptop 210) to show that it is not occupied (which can also be called third information).

[0199] After executing S1102, devices with the same account can confirm that the remote camera on mobile phone 220 is not in use.

[0200] In this embodiment, an available device is an online device that supports a remote camera and whose remote camera is not currently in use. For example, if mobile phone 220 is an online device that supports a remote camera, but its remote camera is currently in use, it will not be identified as an available device. Therefore, between S1101 and S1102, if a device with the same account (such as tablet 230) receives an image acquisition operation, the online device that supports a remote camera but whose remote camera is in use (such as mobile phone 220) will not be identified as an available device. Subsequently, the option for mobile phone 220 will not be displayed, or the option for mobile phone 220 in an inoperable state (such as a grayed-out state) will be displayed. This prevents the remote camera of mobile phone 220 from being invoked, thus avoiding conflicts in invocation.

[0201] Previous text Figures 5-11 The image capturing method provided in this application embodiment was mainly described using a laptop computer 210 and a mobile phone 220 as the execution entities. The image capturing method provided in this application embodiment will be further explained below in conjunction with the software modules of the laptop computer 210 and the mobile phone 220. For details regarding the various software modules in the laptop computer 210 and the mobile phone 220 and their respective hierarchical levels, please refer to the preceding text. Figure 4A and Figure 4B The explanation will not be repeated here.

[0202] For details, see Figure 12 Before S501, there are also S1201-S1203:

[0203] S1201, the remote camera of mobile phone 220 has the ability to register the remote camera with the device management service of mobile phone 220.

[0204] The ability to register a remote camera refers to the ability of a remote camera to inform the device management service of its remote camera capabilities (the ability to take images for devices under the same account and transmit them back).

[0205] In some embodiments, when the mobile phone 220 is powered on for the first time, the mobile phone 220 may prompt the user to enable the remote camera in a user wizard. If the user's action to enable the remote camera is received, the remote camera will be triggered to register its capabilities with the device management service. For example, when the mobile phone 220 is powered on for the first time, the mobile phone 220 may display... Figure 13 Interface 1301 is shown in (a) above. Interface 1301 is a user guide interface, which includes language options such as "Simplified Chinese", "Traditional Chinese", "English", and "Japanese". After the user selects "Simplified Chinese" in interface 1301, mobile phone 220 can display... Figure 13Interface 1302 is shown in (b) above. Interface 1302 is another interface of the user guide. Interface 1302 includes a prompt: "After enabling the remote camera, other devices are allowed to use this device to capture images. Do you want to enable it?", which prompts the user to enable the remote camera. Interface 1302 also includes two options: "Yes" and "No". Enabling the remote camera can be done by selecting "No" in interface 1302. Therefore, in response to the user's selection of "No" in interface 1302, the remote camera in mobile phone 220 will be triggered to register its capabilities with the device management service.

[0206] It should be noted that, Figure 13 In the example, the user selects a language on interface 1301, and then interface 1302 is displayed. In actual implementation, after the user selects a language on interface 1301, the mobile phone 220 can also display other guided interfaces first, such as a guided interface for setting fingerprint, face, password, or data import, etc. After the user completes the settings on these other guided interfaces, the mobile phone 220 will jump to interface 1302.

[0207] In other embodiments, when the mobile phone 220 is powered on for the first time, the user does not perform the operation of enabling the remote camera, but during subsequent use of the mobile phone 220, if the user's operation of enabling the remote camera is received, the remote camera may be triggered to register its capabilities with the device management service.

[0208] When registering its capabilities, a remote camera can send its application identifier, such as the app package name, to the device management service to indicate that the registered application is a remote camera. Additionally, the remote camera can also send its capability information to the device management service to indicate that the registered capability is a remote camera capability.

[0209] S1202 and Mobile Phone 220's device management service can record remote cameras and their registration capabilities.

[0210] For example, the device management service records the application identifier of the remote camera and the capability information of the remote camera.

[0211] S1203, the device management service of mobile phone 220 sends a message to the remote camera of mobile phone 220 indicating successful registration.

[0212] This completes the registration of the remote camera's capabilities.

[0213] In some embodiments, after registering the remote camera's capabilities, if the user does not wish to continue using mobile phone 220 to take images for other devices with the same account, they can also deactivate the remote camera on mobile phone 220. In response to the user's deactivation of the remote camera, the remote camera will request the device management service to deregister its capabilities. Upon receiving the deregistration request from the remote camera, the device management service will delete the remote camera's registration information, such as the application identifier and capability information of the remote camera.

[0214] See also Figure 12 In the notebook computer 210, S501 further includes the following S5011-S5013:

[0215] The device management service of S5011 and mobile phone 220 can synchronize remote camera capabilities with the device management service of devices with the same account (such as laptop 210) via the Internet.

[0216] If mobile phone 220 and laptop 210 are logged into the same user account, their device management services can synchronize the remote camera's capabilities via the internet (i.e., the cloud). Of course, if there are other devices with the same account, mobile phone 220's device management service can also synchronize their remote camera capabilities with the device management services of those other devices.

[0217] When synchronizing the remote camera capability (i.e., synchronizing the first information), the device management service of mobile phone 220 can synchronize the device information of mobile phone 220 (such as the name of mobile phone 220) and the capability information of remote camera capability to the device management service of laptop computer 210, so as to indicate that mobile phone 220 supports remote camera.

[0218] It should be understood that if the remote camera in mobile phone 220 cancels its remote camera capability with the device management service, then the device management service of mobile phone 220 will also cancel the remote camera capability in sync with the device management service of laptop 210. Accordingly, the device management service of laptop 210 will delete the information that mobile phone 220 supports remote cameras, such as deleting the device information of mobile phone 220 and the capability information of remote camera capability.

[0219] S5012, the communication service of the laptop 210 discovers (for the mobile phone 220) online devices within the near-field communication range.

[0220] The communication services of the laptop 210 (such as Magic Link) can periodically scan and discover devices within the near-field communication range of the laptop 210.

[0221] After the laptop 210 detects the mobile phone 220, the laptop 210 and the mobile phone 220 can transfer data through communication services (such as Magic Link), such as transferring call requests, images, etc.

[0222] S5013, the communication service of the laptop 210 updates the online device (for the mobile phone 220) to the device management service of the laptop 210.

[0223] In this way, the device management service of the laptop 210 can identify the mobile phone 220 as an online device.

[0224] In some embodiments, in the laptop computer 210, the connection service can only provide services such as querying available devices, transferring call requests across devices, and data such as images to the target application if the connection service is connected.

[0225] Based on this, see further. Figure 12 The laptop computer 210 also includes the following steps S1204-S1208. It should be noted that there is no strict order requirement between S1204-S1208 and the aforementioned S1201-S5013. In practice, whenever the target application undergoes a cold boot, S1204-S1208 will be executed in the laptop computer 210.

[0226] S1204. In response to a cold start of the target application on the laptop 210, an access request is sent to the connection service of the laptop 210.

[0227] The access request is used to request access to the continuity service. The access request includes the application identifier of the target application, indicating that the target application wants to access the continuity service.

[0228] In the laptop 210, during a cold start, the target application can send an access request to the connection service. A cold start means that before the target application starts, there is no process for the target application in the laptop 210's system. During the cold start process, sending an access request to the connection service allows the connection between the target application's process and the connection service's process to be re-established, facilitating subsequent calls to the remote camera.

[0229] S1205, the continuity service of the laptop 210 sends an authentication request to the application authentication service of the laptop 210.

[0230] The authentication request is used to request authentication of the application. The authentication request includes the application identifier of the target application, which is used to instruct that the target application be authenticated.

[0231] The S1206 and Notebook 210 application authentication services authenticate target applications.

[0232] Before the target application is connected to the service, its legitimacy is verified, such as its identity and permissions.

[0233] S1207, the application authentication service of the laptop 210 sends a message of successful authentication to the connection service of the laptop 210.

[0234] The successful authentication message includes the application identifier of the target application, indicating that the target application has been successfully authenticated.

[0235] S1208, the connection service of the laptop 210 returns a message of successful access to the target application of the laptop 210.

[0236] Only after verifying the legitimacy of the target application will the connection service return a successful connection message to the target application, thus allowing the target application to access the connection service. This avoids providing services such as querying available devices, transferring call requests across devices, and transmitting data such as images to unauthorized applications.

[0237] See also Figure 12 In the laptop 210, the user can perform an image acquisition operation within the target application; correspondingly, S502 is specifically S5021:

[0238] The target application of S5021 and notebook computer 210 receives and acquires images.

[0239] For example, the acquisition operation is a user's... Figure 7A The click operation of "Image" 702 in the interface 701 shown.

[0240] See also Figure 12 In the notebook computer 210, S503 further includes S5031-S5036:

[0241] S5031. In response to the acquisition operation, the target application of the laptop 210 requests the connection service of the laptop 210 to query available devices.

[0242] In this context, "available devices" refers to online devices that support remote cameras. In some embodiments, the device management services for devices under the same account will not only synchronize the capabilities of the remote cameras but also their availability status, such as whether they are currently occupied or not. See the preceding text for details. Figure 10 Related explanations. In this embodiment, available devices refer to online devices that support remote cameras and whose remote cameras are not currently in use.

[0243] Since the target application in the laptop 210 has already obtained the call information for the connection service, the target application can call the connection service to query available devices.

[0244] S5032, the connection service of the laptop 210 queries the device management service of the laptop 210 for available devices, including the mobile phone 220.

[0245] The S5033 and Notebook 210's Device Management Service identifies available devices.

[0246] The device management service of the laptop 210 records devices that support remote cameras and online devices. Therefore, the device management service of the laptop 210 can identify devices that are both remote camera-enabled and online devices as available devices.

[0247] For example, devices that support remote cameras include mobile phone 220 and tablet 230. If the online device is mobile phone 220, then the available device can be determined to be mobile phone 220.

[0248] S5034, The device management service of the laptop 210 returns device information of available devices to the connection service of the laptop 210.

[0249] S5035, the continuity service of the laptop 210 returns device information of available devices to the target application of the laptop 210.

[0250] In this way, the target application obtains device information that allows it to access available devices.

[0251] Typically, the device information of an available device includes the MAC address, serial number, and other information that can uniquely identify each available device.

[0252] In some embodiments, to avoid privacy leaks, the device information of available devices can be represented by the temporary identity (ID) of available devices.

[0253] For example, mobile phone 220 not only provides remote camera capabilities but also other remote capabilities (such as remote translation and remote search) that can be invoked. When one or more applications in laptop 210 invoke these capabilities, they will discover that mobile phone 220 has a camera app, a translation app, and a search app installed simultaneously, leading to a privacy breach. For instance, if these one or more applications are from the same developer, that developer can use big data analytics to create a profile of mobile phone 220.

[0254] Specifically, in this embodiment, after the laptop 210 discovers an online device (e.g., S5012) (as in mobile phone 220), the communication service of the laptop 210 negotiates a temporary ID for each device (e.g., laptop 210 and mobile phone 220) with the communication services of each online device (e.g., mobile phone 220). For example, the negotiated temporary ID for the laptop 210 is 111, and the temporary ID for the mobile phone 220 is 222. Furthermore, the communication service of the laptop 210 can also send the temporary IDs of each online device to the laptop 210's device management service. Then, when returning device information of available devices to the target application (e.g., S5034 and S5035), the temporary IDs of the available devices can be returned. This avoids privacy leaks caused by sending fixed identification information such as the MAC address and serial number of available devices to the target application.

[0255] The target application of S5036 and notebook computer 210 displays options for available devices.

[0256] The available device information may also include the username of the user account logged into the available device (e.g., Tom, Jenny), the device model (e.g., Model A, Model B, etc.), and / or device type (e.g., mobile phone, tablet, etc.). Accordingly, the target application can display the username, device model, and / or device type in the available device options to indicate the available devices corresponding to each option.

[0257] For example, the laptop 210 can display Figure 7A The interface 703 shown includes options for two available devices: "Camera for Tom's Model A mobile phone" and "Camera for Tom's Model B tablet".

[0258] See also Figure 12 In the laptop 210, S504 is specifically S5041:

[0259] S5041, The target application of the laptop 210 receives the user's selection of options on the mobile phone 220.

[0260] For example, Tom's model A phone is phone 220, so the selection operation can be the user's choice of... Figure 7A The click operation for "Tom's Model A Phone" in interface 703 shown.

[0261] It should be understood that when a user selects an option on mobile phone 220, it means that the user selects the remote camera of mobile phone 220 to take an image.

[0262] See also Figure 12 S505 further includes S5051-S5054:

[0263] S5051, the target application of the laptop 210 sends a request to the laptop 210's connection service to invoke the remote camera of the mobile phone 220.

[0264] Since the target application in the laptop 210 has successfully registered with the connection service, the target application can call the connection service to send a remote camera access request (also known as a second request) to the mobile phone 220.

[0265] In the laptop 210, when the target application requests to call the remote camera from the connection service, it needs to carry the device information of the mobile phone 220 (such as the temporary ID of the mobile phone 220) and the capability information of the remote camera, which is used to indicate that the calling object is the capability of the remote camera in the mobile phone 220.

[0266] For example, the call request sent by the target application to the continuity service includes the following:

[0267]

[0268]

[0269] This allows you to access the remote camera of phone 220.

[0270] S5052, the connection service of the laptop 210 sends a request to the communication service of the laptop 210 for the target application of the laptop 210 to call the remote camera of the mobile phone 220.

[0271] In the laptop 210, when the connecting service sends a request (also known as a third request) to the communication service, it may carry the device information of the mobile phone 220 and the capability information of the remote camera, to indicate that the calling object is the capability of the remote camera in the mobile phone 220; and it may also carry the device information of the laptop 210 (such as the temporary ID of the laptop 210), to indicate that the requester is the laptop 210.

[0272] In addition, after receiving a call request from the target application, the connection service of the laptop 210 can obtain the application identifier of the target application by parsing it, and carry the application identifier in the request sent to the communication service to further indicate that the requester is the target application.

[0273] That is, based on the call request in S5051 mentioned above, the device information of the laptop 210 and the application identifier of the target application are added.

[0274] S5053, the communication service of the laptop 210 sends a request to the communication service of the mobile phone 220 for the target application of the laptop 210 to call the remote camera of the mobile phone 220.

[0275] In some embodiments, the request in S5053 (i.e., the first request) may be device information of the laptop 210, compared to S5052.

[0276] S5054, the communication service of mobile phone 220 sends a request to the connection service of mobile phone 220 for the target application of laptop 210 to call the remote camera.

[0277] In mobile phone 220, when the communication service sends a request (also known as a fourth request) to the call service, it can carry capability information of the remote camera capability to indicate that the called capability is the remote camera capability; and it also carries device information of laptop 210 and application identifier of the target application to indicate that the requester is the target application in laptop 210. That is, based on the call request in S5053 mentioned above, the device information of mobile phone 220 can be reduced.

[0278] See also Figure 12 In the 220 phone, S506 is specifically S5061:

[0279] S5061, the mobile phone 220 initiates the remote camera service and sends the device information of the laptop 210 and the application identifier of the target application to the remote camera.

[0280] In mobile phone 220, the call-to-action service activates the remote camera based on the capability information in the received request. After the remote camera is activated, it can access the system camera to capture images. After the system camera is activated, it can display a viewfinder interface, such as... Figure 8A The interface shown is 801.

[0281] The device information of the laptop 210 recorded in the remote camera is used by the remote camera to distribute images captured by the system camera to the laptop 210. Additionally, the application identifier of the target application recorded in the remote camera is used by the laptop 210 to determine the target application for acquiring the image.

[0282] In some embodiments, see continue to see Figure 12 S1101 after activating the remote camera further includes S11011-S11012:

[0283] S11011 and mobile phone 220's remote camera update the working status to the device management service as occupied.

[0284] The working status includes two types: occupied and unoccupied, which can be indicated by two tags. For example, the first tag, such as 1, indicates that it is unoccupied, and the second tag, such as 0, indicates that it is occupied. In mobile phone 220, the remote camera can send either the first tag or the second tag to the device management service to instruct the device management service to update the status.

[0285] The working status of the device management service of S11012 and mobile phone 220, which synchronizes the remote camera's working status with the device management service of the same account device (such as laptop 210) via the Internet, is occupied.

[0286] When the status of the remote camera on mobile phone 220 changes, it will be synchronized to other devices with the same account, such as laptop 210. Subsequently, when other devices with the same account access the remote camera, they can avoid accessing the remote camera that is in use, such as the remote camera on mobile phone 220, to prevent conflicts.

[0287] Furthermore, S1102, after the remote camera calls the system camera to complete image capture, further includes S11021-S11022:

[0288] The remote camera of S11021 and mobile phone 220 updates its working status to the device management service to show that it is not occupied.

[0289] S11022, the device management service of mobile phone 220 synchronizes the working status of its remote camera capability with the device management service of the same account device (such as laptop 210) via the Internet, and is not occupied.

[0290] Subsequently, when devices with the same account access remote cameras, they can continue to access remote cameras that are not currently in use, such as the remote camera in mobile phone 220.

[0291] See also Figure 12 In mobile phone 220, S507 further includes S5071-S5075:

[0292] S5071, the remote camera of mobile phone 220 sends images to the connection service of mobile phone 220, and the target application whose receiving object is laptop computer 210.

[0293] In mobile phone 220, when the remote camera sends images to the connection service, it can simultaneously transmit the device information of the laptop 210 recorded by the remote camera and the application identifier of the target application, so that the connection service can clearly define the transmission path.

[0294] S5072, the mobile phone 220's connection service sends images to the mobile phone 220's communication service, and transmits to the target application whose receiving object is the laptop 210.

[0295] S5073, the communication service of mobile phone 220 is based on the communication service of receiving object to laptop computer 210 to send images, and transmit the target application of receiving object (such as the application identifier of the target application).

[0296] In mobile phone 220, the receiving object of the communication service is the target application of laptop 210. Therefore, the communication service can send images to laptop 210 based on the device information in the receiving object, that is, the device information of laptop 210.

[0297] S5074, the communication service of the laptop 210 sends images to the connection service of the laptop 210, and the transmission and reception object is the target application.

[0298] S5075, the continuity service of the laptop 210 sends an image to the target application of the laptop 210 based on the receiving object.

[0299] In the laptop 210, the receiving object of the connection service is the target application. Therefore, the connection service can send an image to the target application based on the application identifier in the receiving object, that is, the application identifier of the target application.

[0300] See also Figure 12 In the laptop 210, S508 is specifically S5081:

[0301] The target application displays images on the S5081 and notebook computer 210.

[0302] Taking images as an example, after receiving an image, the laptop 210 can display it. Figure 9 The interface 901 shown includes image 902.

[0303] This application also provides an electronic device, which may include a memory and one or more processors. The memory and processors are coupled. The memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instructions, the electronic device can perform various functions or steps performed by the mobile phone in the above method embodiments.

[0304] This application also provides a chip system, such as... Figure 14As shown, the chip system 1400 includes at least one processor 1401 and at least one interface circuit 1402. The processor 1401 and the interface circuit 1402 are interconnected via lines. For example, the interface circuit 1402 can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit 1402 can be used to send signals to other devices (e.g., the processor 1401). Exemplarily, the interface circuit 1402 can read instructions stored in memory and send those instructions to the processor 1401. When the instructions are executed by the processor 1401, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, and this application embodiment does not specifically limit this.

[0305] This embodiment also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the various functions or steps performed by the mobile phone in the above method embodiment.

[0306] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the various functions or steps performed by the mobile phone in the above method embodiment.

[0307] In addition, embodiments of this application also provide an apparatus, which may specifically be a chip, component or module. The apparatus may include a connected processor and a memory. The memory is used to store computer execution instructions. When the apparatus is running, the processor can execute the computer execution instructions stored in the memory to cause the chip to perform the various functions or steps performed by the mobile phone in the above method embodiments.

[0308] In this embodiment, the electronic device, communication system, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0309] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above 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.

[0310] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0311] The unit described as a separate component may or may not be physically separate. The component shown as a unit can be one physical unit or multiple physical units, that is, it can be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of the solution in this embodiment according to actual needs.

[0312] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0313] If the integrated unit is implemented as 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 solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0314] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit it. Although this application has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of this application without departing from the spirit and scope of the technical solutions of this application.

Claims

1. An image capturing method, characterized in that, Applied to a first device, the method includes: After the first device is powered on, it continuously confirms and updates online devices that support remote cameras; the online devices are devices within the near-field communication range of the first device. The first device displays a first interface of a first application; the first application is not a camera application; the first application is used to perform at least one of the following operations based on the acquired image: inserting an image, editing an image, sending an image, and scanning an image; In response to a user's first operation on the first interface, the first device displays a second option and a first option, wherein the first operation is used to acquire an image; and the second option is used to acquire an image stored locally. Each of the first options corresponds to an available device, which is the online device that supports remote cameras; In response to the user's selection of the first option, the first device sends a first request to the second device indicated by the first option. The first request includes device information of the first device, application identifier of the first application, and request type. The device information of the first device is used by the remote camera of the second device to distribute images captured by the system camera of the second device to the first device based on the device information of the first device. The request type is used to indicate that the first request invokes the remote camera. The remote camera is an application with the following capabilities: invoking the system camera to capture images and distributing the images captured by the system camera. If the second device is not occupied, the first device receives the image captured by the second device based on the first request and the application identifier; The first device receives third information, which indicates that the second device is not occupied; The first device displays the image captured by the second device on the first interface based on the application identifier.

2. The method according to claim 1, characterized in that, The method further includes: The first device receives first information from the second device, the first information indicating that the second device has the capability of the remote camera; In response to the first information, the first device records information about the second device's ability to have the remote camera; The first device displays a first option, including: If the first device records information that the second device has the capability of the remote camera, the first device displays the first option.

3. The method according to claim 2, characterized in that, The method further includes: The first device receives second information from the second device, the second information indicating that the remote camera is occupied; in response to the second information, the first device updates the status of the remote camera to occupied; and / or, The first device receives third information from the second device, the third information indicating that the remote camera is not occupied; in response to the third information, the first device updates the status of the remote camera to an unoccupied state; The first device displays a first option, including: If the remote camera is in an unoccupied state, the first device displays the first option.

4. The method according to claim 2 or 3, characterized in that, The first option is an option for devices within the near-field communication range of the first device and / or devices logged into the same user account as the first device.

5. The method according to claim 4, characterized in that, The first device includes device management services; The first device receives first information from the second device, including: The device management service receives first information from the second device; The first device records information about the second device's ability to use the remote camera, including: The device management service records information about the second device's ability to use the remote camera.

6. The method according to claim 5, characterized in that, The first device also includes a communication service, and the method further includes: The communication service discovers that the second device is within the near-field communication range of the first device, and / or that the second device is logged into the same user account as the first device; The communication service updates the second device as an online device to the device management service.

7. The method according to claim 6, characterized in that, The first device also includes a connection service, and the method further includes, before the first device displays the first option: The first application sends a query request to the connection service; The continuity service forwards the query request to the device management service; In response to the query request, if the device management service includes information that the second device has the capability of the remote camera, and the second device is the online device, the device management service returns the device information of the second device to the connection service; The continuity service returns the device information of the second device to the first application; The first device displays a first option, including: The first application displays the first option corresponding to the second device based on the device information of the second device.

8. The method according to claim 7, characterized in that, The device information of the second device includes the username of the user account, the device model of the second device and / or the device type of the second device, and the first option includes the username, the device model and / or the device type.

9. The method according to claim 7 or 8, characterized in that, After the communication service discovers that the second device is within the near-field communication range of the first device, and / or that the second device is logged into the same user account as the first device, the method further includes: The communication service assigns a temporary ID to the second device, and the device information of the second device includes the temporary ID; The first device sends a first request to the second device indicated by the first option, including: The first application sends a first request to the second device corresponding to the temporary ID.

10. The method according to any one of claims 1-3 or any one of claims 5-8, characterized in that, The method further includes: If the second device meets the preset conditions, in response to the user's selection of the first option, the first device issues a first prompt message, which is used to indicate that the second device is recording. The preset conditions include the system camera being in an idle state and / or the second device being powered on.

11. The method according to any one of claims 1-3 or any one of claims 5-8, characterized in that, The first device includes connection services and communication services; In response to the user's selection of the first option, the first device sends a first request to the second device indicated by the first option, including: In response to the user's selection of the first option, the first application sends a second request to the connection service. The second request includes device information of the second device and the request type. The device information of the second device is used to indicate the device that took the image. In response to the second request, the connection service sends a third request to the communication service, the third request including device information of the first device, device information of the second device, the application identifier, and the request type; In response to the third request, the communication service sends the first request to the second device indicated by the device information of the second device in the third request.

12. The method according to any one of claims 1-3 or any one of claims 5-8, characterized in that, The first device includes communication services and connection services; The first device receives an image captured by the second device and an application identifier of the first application, including: The communication service receives the image captured by the second device and the application identifier of the first application; The communication service sends the image and the application identifier to the connection service; The first device displays an image captured by the second device on the first interface based on the application identifier, including: The connection service sends the image to the first application indicated by the application identifier; The first application displays the image.

13. An image capturing method, characterized in that, The method is applied to a second device, which is an online device that supports a remote camera; the method includes: The second device receives a first request, which includes device information of the first device, application identifier of the first application, and request type. The request type indicates that the first request invokes a remote camera, and the remote camera is an application in the second device. In response to the first request, if the second device is not occupied, the second device activates the remote camera and records the device information of the first device and the application identifier in the remote camera; after the second device activates the remote camera, the second device is occupied. In response to activating the remote camera, the second device displays a second interface, which is the shooting preview interface of the system camera in the second device; In response to the user's shooting action, the second device captures an image; The second device sends the image, along with the application identifier in the remote camera, to the first device indicated by the device information of the first device in the remote camera. After the image is sent, the second device is not occupied; a third message is sent to the first device, the third message indicating that the second device is not occupied; The image is used by a first application of the first device to implement a corresponding function, wherein the first application is not a camera application; the first application is used to perform at least one of the following operations based on the acquired image: inserting an image, editing an image, sending an image, and scanning an image.

14. The method according to claim 13, characterized in that, The method further includes: The second device issues a second prompt message, which prompts the first device to request that it take an image. The second device activates the remote camera, including: In response to the user's confirmation of the second prompt message, the second device activates the remote camera.

15. The method according to claim 13 or 14, characterized in that, The second device includes communication services and connection services; The second device receives the first request, including: The communication service receives the first request; In response to the first request, the second device activates the remote camera and records the device information of the first device and the application identifier in the remote camera, including: In response to receiving the first request, the communication service sends a fourth request to the connection service, the fourth request including the device information of the first device, the application identifier and the request type; In response to receiving the fourth request, the connection service starts the remote camera and sends the device information of the first device and the application identifier to the remote camera; The remote camera records the device information of the first device and the application identifier.

16. The method according to claim 15, characterized in that, The second device also includes a system camera; The second device displays a second interface, including: The remote camera invokes the system camera, and the system camera displays the second interface; The images captured by the second device include: The system's camera captures images.

17. The method according to claim 15, characterized in that, The second device sends the image to the first device indicated by the device information of the first device in the remote camera, and sends the application identifier in the remote camera, including: The remote camera sends the image, the device information of the first device, and the application identifier to the connection service; The connection service sends the image, the device information of the first device, and the application identifier to the communication service; The communication service sends the image and the application identifier to the first device, as indicated by the device information of the first device.

18. The method according to claim 13, 14, 16, or 17, characterized in that, Before the second device receives the first request, the method further includes: The second device synchronizes first information to the first device, the first information indicating that the second device has the capability of the remote camera.

19. The method according to claim 18, characterized in that, After the second device begins capturing images and before the second device ends capturing images, the method further includes: The second device synchronizes second information to the first device, the second information indicating that the remote camera of the second device is occupied; After the second device finishes capturing images, the method further includes: The second device synchronizes third information to the first device, the third information indicating that the remote camera of the second device is not occupied.

20. The method according to claim 18, characterized in that, The second device includes a device management service, and the method further includes: The device management service synchronizes information with the first device regarding the second device's ability to have the remote camera and / or whether the remote camera on the second device is occupied or not.

21. An image capturing method, characterized in that, include: After the first device is powered on, continuously confirm and update online devices that support remote cameras; The online device is a device within the near-field communication range of the first device; The first device displays the first interface of the first application; The first application is not a camera application; the first application is used to perform at least one of the following operations based on the acquired image: inserting an image, editing an image, sending an image, and scanning an image; In response to a user's first operation on the first interface, the first device displays a second option and a first option, wherein the first operation is used to acquire an image; and the second option is used to acquire an image stored locally. Each of the first options corresponds to an available device, which is the online device that supports remote cameras; In response to the user's selection of the first option, the first device sends a first request to the second device indicated by the first option. The first request includes device information of the first device, application identifier of the first application, and request type. The request type is used to indicate that the first request invokes a remote camera, and the remote camera is an application in the second device. The second device receives the first request; In response to the first request, if the second device is not occupied, the second device activates the remote camera and records the device information of the first device and the application identifier of the first application in the remote camera; After the second device starts the remote camera, the second device is occupied; In response to activating the remote camera, the second device displays a second interface, which is the viewfinder of the system camera in the second device; In response to the user's shooting action, the second device captures an image; The second device sends the image, along with the application identifier in the remote camera, to the first device indicated by the device information of the first device in the remote camera. After the image is sent, the second device is not occupied; a third message is sent to the first device, the third message indicating that the second device is not occupied.

22. An electronic device, characterized in that, The electronic device includes the first device or the second device according to any one of claims 1-21, the electronic device includes a memory and one or more processors, the memory being coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, which, when executed by the processor, cause the electronic device to perform the method according to any one of claims 1-21.

23. A communication system, characterized in that, The communication system includes the first device and the second device as described in any one of claims 1-21.

24. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1-21.

25. A chip system, characterized in that, The chip system is applied to an electronic device including a processor and a memory. The chip system includes one or more interface circuits and one or more processors, the interface circuits and the processors being interconnected via lines. The interface circuits are used to receive signals from the memory of the electronic device and send the signals to the processors. The signals include computer instructions stored in the memory. When the processor executes the computer instructions, it causes the electronic device to perform the method as described in any one of claims 1-21.

Images