Screenshot method, wearable device and electronic device

Abstract

The invention discloses a screenshot method, wearable equipment and electronic equipment, and relates to the technical field of terminals. The wearable device can realize the screenshot function, and the screenshot efficiency is improved. The method comprises the steps of obtaining a negotiation result in response to a received screen capture operation when the wearable device displays a user interface; the negotiation result indicates M screenshot processing operations needing to be executed by the wearable device, the M screenshot processing operations are partial operations in N screenshot processing operations used for generating a first screenshot of the user interface, and the negotiation result can be determined based on the processing capability of the wearable device and the processing capability of the electronic device. The wearable device executes M screenshot processing operations on the screenshot original data of the user interface to generate a second screenshot and then sends the second screenshot to the electronic device, and the electronic device executes N-M screenshot processing operations on the second screenshot to generate a first screenshot.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to screenshot methods, wearable devices, and electronic devices. Background Technology

[0002] With the development of terminal technology, the variety of terminal products is increasing, and their applications are becoming more widespread. For example, wearable devices, as mainstream terminal products, can be used for user exercise and health measurement. As users increasingly use wearable devices, they expect them to have richer functions, such as screenshot capabilities. However, currently, some wearable devices, due to their limited processing power, do not support screenshot functionality. Summary of the Invention

[0003] This application provides a screenshot method, a wearable device, and an electronic device, enabling the wearable device to perform screenshot functions and improving screenshot efficiency.

[0004] To achieve the above objectives, this application adopts the following technical solution:

[0005] In a first aspect, a screenshot method is provided, applied to a wearable device including a display screen, the wearable device being connected to an electronic device. The method includes: when the wearable device displays a user interface, in response to a received screenshot operation, obtaining a negotiation result, the negotiation result indicating M screenshot processing operations to be performed by the wearable device, the M screenshot processing operations being a subset of N screenshot processing operations used to generate a first screenshot of the user interface, where M and N are both positive integers, and the negotiation result is determined based on the processing capabilities of the wearable device and the electronic device; the wearable device performing the M screenshot processing operations on the original screenshot data of the user interface to generate a second screenshot; and the wearable device sending the second screenshot to the electronic device, the second screenshot being used by the electronic device to perform NM screenshot processing operations to generate the first screenshot.

[0006] Based on the above technical solution, when the wearable device displays a user interface, if a screenshot operation is received, a negotiation result can be obtained in response to the screenshot operation. This negotiation result indicates several screenshot processing operations that the wearable device needs to perform. These screenshot processing operations are part of the operations used to generate a first screenshot of the user interface displayed by the wearable device. Then, the wearable device can use the screenshot processing operations indicated in the negotiation result to process the original screenshot data of the user interface to generate a second screenshot, and send the second screenshot to the electronic device. This allows the electronic device to perform another part of the screenshot processing operations to generate the first screenshot. This enables the wearable device to achieve screenshot functionality. Furthermore, the wearable device only needs to perform a portion of the screenshot processing operations, while the remaining screenshot processing operations are performed by the electronic device. Compared to a method where all screenshot processing operations are performed by the wearable device, this improves screenshot efficiency.

[0007] Furthermore, the negotiation results are determined based on the processing power of the wearable device and the electronic device. For example, if the processing power of the wearable device indicates that the CPU of the wearable device has weak computing power, while the processing power of the electronic device indicates that the CPU of the wearable device has strong computing power, then the wearable device can perform screenshot processing operations with lower computing power, while the electronic device can perform screenshot processing operations with higher computing power, which can also improve screenshot efficiency.

[0008] In one possible design, the negotiation result also indicates the processing parameters for the M screenshot processing operations. It is understood that some of the M screenshot processing operations may have processing parameters, while others may not. Thus, since the negotiation result also indicates the processing parameters for the screenshot processing operations, the wearable device and electronic device can process the screenshots based on the corresponding processing parameters when performing the screenshot processing operations, ensuring that the screenshots processed by the wearable device can be parsed and processed by the electronic device.

[0009] In one possible design, before the wearable device obtains the negotiation result, the method further includes: the wearable device sending its processing power to the electronic device; and the wearable device receiving the negotiation result from the electronic device. In this way, the wearable device can send its processing power to the electronic device, which then determines the negotiation result, and subsequently sends the determined negotiation result back to the wearable device. Compared to the method where the electronic device sends its processing power to the wearable device, allowing the wearable device to determine the negotiation result, the electronic device has higher computing power, which can improve negotiation efficiency.

[0010] In one possible design, the processing parameters include the target image format.

[0011] In one possible design, the processing capability of the wearable device indicates the image formats it supports, the processing capability of the electronic device indicates the image formats it supports, and the target image format is an image format supported by both the wearable device and the electronic device. Since the target image format is the processing parameter of the M screenshot processing operations indicated in the negotiation result, the image format of the second screenshot is the target image format. Thus, the image format of the second screenshot, i.e., the target image format, can be determined based on the image formats supported by the wearable device and the electronic device, and the target image format is an image format supported by both the wearable device and the electronic device. This allows the electronic device to successfully parse and process the second screenshot upon receiving it.

[0012] In one possible design, the M screenshot processing operations include a compression operation performed using a target compression algorithm. In this way, the wearable device compresses the second screenshot using the target compression algorithm before sending it to the electronic device, which reduces the transmission time of the screenshot data compared to sending an uncompressed screenshot, thereby improving screenshot efficiency.

[0013] In one possible design, the processing capability of the wearable device indicates the compression algorithm it supports, and the processing capability of the electronic device indicates the decompression algorithm it supports. The target compression algorithm is the compression algorithm corresponding to the decompression algorithm supported by the electronic device and is also a compression algorithm supported by the wearable device. In this way, the algorithm for compressing the second screenshot, i.e., the target compression algorithm, can be determined based on the compression algorithms supported by the wearable device and the electronic device. Since the target compression algorithm is a compression algorithm supported by the wearable device and corresponds to the decompression algorithm supported by the electronic device, this allows the electronic device to successfully decompress and process the second screenshot upon receipt.

[0014] In one possible design, the processor installed in the wearable device is one or more of a microprocessor unit (MCU) and an application processor (AP).

[0015] In one possible design, the M screenshot processing operations include at least one of cropping rounded corners and adding borders.

[0016] Secondly, a screenshot method is provided, applied to an electronic device, wherein the electronic device is connected to a wearable device. The method includes: the electronic device acquiring a negotiation result and a second screenshot, wherein the negotiation result indicates NM screenshot processing operations to be performed by the electronic device, the second screenshot being obtained by the wearable device performing M of the N screenshot processing operations on the original data of the displayed user interface, the N screenshot processing operations being operations used to generate a first screenshot of the user interface, wherein M and N are both positive integers, and the negotiation result is determined based on the processing capabilities of the wearable device and the electronic device; the electronic device performing the NM screenshot processing operations on the second screenshot to generate the first screenshot.

[0017] In one possible design, before the electronic device obtains the negotiation result, the method further includes: the electronic device obtaining the processing power of the wearable device; and the electronic device determining the negotiation result based on the processing power of the wearable device and the processing power of the electronic device.

[0018] In one possible design, after determining the negotiation result, the method further includes: the electronic device sending the negotiation result to the wearable device.

[0019] In one possible design, the method further includes: the electronic device receiving an image resolution from the wearable device; and the electronic device cropping the second screenshot using the image resolution to generate the first screenshot. Here, the image resolution is also the screen resolution of the wearable device. In this way, the electronic device can also receive an image resolution from the wearable device. Since the image resolutions of wearable devices with different display shapes (such as circles, rectangles, etc.) are different, the electronic device can crop the second screenshot based on the image resolution of the wearable device to generate the first screenshot. This allows the shape of the first screenshot to match the shape of the wearable device's display screen. For example, when the wearable device's display screen is circular, the first screenshot is circular; when the wearable device's display screen is rectangular, the first screenshot is rectangular. This avoids a single screenshot method and improves the screenshot effect.

[0020] In one possible design, the negotiation result also indicates the processing parameters of the screenshot processing operation.

[0021] In one possible design, the processing parameters include the target image format.

[0022] In one possible design, the acquired processing power of the wearable device indicates the image formats supported by the wearable device, the processing power of the electronic device indicates the image formats supported by the electronic device, and the target image format is an image format supported by both the wearable device and the electronic device.

[0023] In one possible design, the second screenshot is a screenshot compressed using the target compression algorithm, and the NM screenshot processing operations include decompressing the second screenshot using the decompression algorithm corresponding to the target compression algorithm.

[0024] In one possible design, the acquired processing power of the wearable device indicates the compression algorithm supported by the wearable device, the processing power of the electronic device indicates the decompression algorithm supported by the electronic device, and the target compression algorithm is the compression algorithm corresponding to the decompression algorithm supported by the electronic device and is also the compression algorithm supported by the wearable device.

[0025] In one possible design, the NM screenshot processing operations include at least one of cropping rounded corners and adding borders. This allows the electronic device to perform various screenshot processing operations on the second screenshot, such as cropping rounded corners and adding borders, making the screenshot more aesthetically pleasing and improving the screenshot quality. Furthermore, having the electronic device perform the cropping rounded corners and adding borders operations, rather than having the wearable device do so, improves screenshot efficiency due to the higher computing power of the electronic device.

[0026] For the technical effects of other designs in the second aspect, please refer to the technical effects of the corresponding designs in the first aspect.

[0027] Thirdly, a device is provided, the terminal device having the function of implementing the method as described in the first or second aspect and any of the designs therein. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function.

[0028] Fourthly, a wearable device is provided, comprising: a processor, a display screen, a communication interface, and a memory, wherein the memory, the display screen, and the communication interface are coupled to the processor, the communication interface is used for communicating with other devices, the memory is used for storing program code, the program code including instructions, and the processor reads the instructions from the memory to cause the wearable device to perform the method as described in the first aspect and any of the designs above.

[0029] Fifthly, an electronic device is provided, comprising: a processor, a communication interface, and a memory, wherein the memory and the communication interface are coupled to the processor, the communication interface is used for communicating with other devices, the memory is used for storing program code including instructions, and the processor reads the instructions from the memory to cause the electronic device to perform the method as described in the second aspect above and any of the designs therein.

[0030] Optionally, in the fourth and fifth aspects above, the memory can be coupled to the processor or independent of the memory. For example, the communication interface can be a transceiver, an input / output interface, an interface circuit, an output circuit, an input circuit, pins, or related circuits, etc.

[0031] A sixth aspect provides a computer-readable storage medium comprising a computer program that, when executed on a device, causes the device to perform the method as described in the first or second aspect above and any one thereof.

[0032] A seventh aspect provides a computer program product comprising: a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in the first or second aspect and any of the designs herein.

[0033] Eighthly, a chip system is provided, including at least one processor and at least one interface circuit, the at least one interface circuit being used to perform transceiver functions and send instructions to at least one processor, wherein when at least one processor executes instructions, at least one processor performs the method as described in either the first or second aspect above.

[0034] A ninth aspect provides a communication system including a wearable device and an electronic device, the wearable device being configured to perform the method as described in the first aspect and any of the designs therein, and the electronic device being configured to perform the method as described in the second aspect and any of the designs therein.

[0035] It should be noted that the technical effects of any of the designs in the third to ninth aspects mentioned above can be found in the technical effects of the corresponding designs in the first or second aspects, and will not be repeated here. Attached Figure Description

[0036] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0037] Figure 2 This application provides a schematic diagram of the structure of a mobile phone according to an embodiment of the present application.

[0038] Figure 3 This is a schematic diagram of the structure of a smartwatch provided in an embodiment of this application;

[0039] Figure 4 A schematic diagram of the software structure of a mobile phone and a smartwatch provided for embodiments of this application;

[0040] Figure 5 A schematic diagram of the interface for establishing a connection between a mobile phone and a smartwatch is provided in an embodiment of this application;

[0041] Figure 6 This application provides a schematic diagram of the interface related to a screenshot of a smartwatch.

[0042] Figure 7 A flowchart illustrating a screenshot method provided in an embodiment of this application;

[0043] Figure 8 A flowchart illustrating yet another screenshot method provided in this application embodiment;

[0044] Figure 9 A set of screenshots provided as an embodiment of this application;

[0045] Figure 10 A schematic diagram of another set of screenshots provided for embodiments of this application;

[0046] Figure 11 A schematic diagram of the interface of a gallery application in a mobile phone provided in an embodiment of this application;

[0047] Figure 12 A set of schematic diagrams of the interface of a smartwatch provided in the embodiments of this application;

[0048] Figure 13 This is a schematic diagram of the structure of a device provided in an embodiment of this application;

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

[0050] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0051] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, a and b and c, where a, b, and c can be single or multiple.

[0052] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0053] Currently, some wearable devices (such as those using a microcontroller unit (MCU) or an application processor (AP) as their main control unit) have relatively weak processing capabilities. In one screenshotting scheme, it would take these wearable devices a very long time to perform various complex screenshot processing operations, such as cropping, rounding corners, compression, and border editing, so they generally do not support screenshot functionality. In another screenshotting scheme, other devices (such as mobile phones or other devices with higher processing power than wearable devices) can perform the aforementioned complex screenshot processing operations, meaning that other devices perform the screenshot processing operations on behalf of the wearable devices. In this scheme, the wearable device needs to send the screenshot data to other devices first so that the other devices can process the screenshot data. However, since the wearable device cannot determine the processing capabilities of other devices, such as what image formats, compression algorithms, or decompression algorithms the other devices support, this approach is problematic. Therefore, the screenshot data sent by wearable devices to other devices is the raw screenshot data, i.e., the data without any processing. This screenshot data is very large, which leads to a very long data transmission time and consequently, low screenshot efficiency.

[0054] Furthermore, in this solution, for wearable devices with different display shapes (such as rectangular, circular, or other shapes), i.e., wearable devices with different screen resolutions, since the display modules are all rectangular, the original screenshots (i.e., the original screenshot data) generated in response to screenshot operations are all rectangular. Consequently, the screenshot data received by other devices is also rectangular. For example, for a smartwatch with a rectangular display and a screen resolution of 3×4, the original screenshot generated by the smartwatch will be a rectangle with a resolution of 3×4. Similarly, for a smartwatch with a circular display and a screen resolution of 3×5 with a diameter of 3, the original screenshot generated by the smartwatch will be a rectangle with a resolution of 3×5. Consequently, the final screenshots generated by other devices for this wearable device are all rectangular screenshots, resulting in monotonous screenshot effects and a poor user experience.

[0055] Based on this, the embodiments of this application provide a screenshot method that not only enables wearable devices to perform screenshot functions, but also improves screenshot efficiency and enhances screenshot effects.

[0056] For example, Figure 1 This illustration shows a schematic diagram of the architecture of a communication system in which a screenshot method provided in an embodiment of this application is applied. Figure 1 As shown, the communication system 100 includes a first device 101 and a second device 102.

[0057] The first device 101 can be a display terminal of a user interface used to generate a screenshot. In some embodiments, the first device 101, while serving as a display terminal of the user interface used to generate a screenshot, can also serve as a screenshot initiator, receiving screenshot operations. That is, the display terminal of the user interface used to generate a screenshot and the screenshot initiator can be the same device. The first device 101 can send screenshot data to the second device 102 based on the received screenshot operation to generate a screenshot corresponding to the user interface displayed on the first device 101. In other embodiments, the display terminal of the user interface used to generate a screenshot and the screenshot initiator can also be different devices, such as the second device 102 serving as a screenshot initiator, receiving screenshot operations. Accordingly, in this embodiment, the first device 101 can send screenshot data to the second device 102 based on the screenshot operation received by the second device 102. For example, the first device 101 can be various wearable devices with a display screen, such as, but not limited to, smartwatches, smart bracelets, smart ankle bracelets, smart helmets, etc.

[0058] The second device 102 can act as a screenshot processing end to generate screenshots. In some embodiments, the second device 102 can receive screenshot data from the first device 101 and generate a screenshot corresponding to the user interface displayed on the first device 101 based on the screenshot data. For example, the second device 102 can be various devices with higher processing capabilities than the first device 101, such as including but not limited to mobile phones, tablets, desktop computers, laptops, handheld computers, ultra-mobile personal computers (UMPCs), netbooks, and various electronic devices such as personal digital assistants (PDAs) and artificial intelligence (AI) devices. Optionally, the second device 102 can be a fixed device or a portable device.

[0059] Optionally, the operating system installed on the first device 101 or the second device 102 may include, but is not limited to, the following: Or other operating systems.

[0060] Optionally, the first device 101 and the second device 102 can establish a connection through wired or wireless communication technologies. For example, wireless communication technologies may include, but are not limited to, Bluetooth (BT) (e.g., classic Bluetooth or Bluetooth Low Energy (BLE) Bluetooth), Sparklink (e.g., classic Sparklink or Sparklink Low Energy (SLE)), Near Field Communication (NFC), Wireless Local Area Networks (WLAN) (e.g., Wireless Fidelity (Wi-Fi) networks), Zigbee, Frequency Modulation (FM), Infrared (IR), etc.

[0061] For example, taking the second device 102 as a mobile phone, Figure 2 A schematic diagram of the structure of a mobile phone according to an embodiment of this application is shown. Figure 2As shown, the mobile phone 200 may include a processor 110, a memory 120, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, buttons 190, a camera 191, a display screen 192, and a subscriber identification module (SIM) card interface 193, etc.

[0062] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0063] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0064] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0065] In some embodiments, processor 110 may include one or more interfaces, such as USB interface 130.

[0066] In some embodiments of this application, the processor 110 may be used to perform one or more screenshot processing operations, such as including but not limited to decompressing screenshots, cropping screenshots, cropping rounded corners, adding borders, etc.

[0067] The charging management module 140 receives charging input from the charger. While charging the battery 142, the charging management module 140 can also supply power to the mobile phone through the power management module 141.

[0068] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, memory 120, display 192, camera 191, and wireless communication module 160, etc.

[0069] The wireless communication function of mobile phone 200 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, etc.

[0070] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in mobile phone 200 can be used to cover one or more communication frequency bands.

[0071] The mobile communication module 150 can provide wireless communication solutions, including 2G / 3G / 4G / 5G, for use on the mobile phone 200. In some embodiments, at least some functional modules of the mobile communication module 150 can be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 can be housed in the same device.

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

[0073] In some embodiments, antenna 1 of mobile phone 200 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling mobile phone 200 to communicate with networks and other devices (such as mobile communication modules) via wireless communication technology. Figure 1The first device 101 shown communicates. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc.

[0074] In some embodiments of this application, the wireless communication module 160 can be used to establish a communication connection between the mobile phone 200 and the first device 101. In still other embodiments of this application, the wireless communication module 160 can also be used to receive one or more of the following: screenshot data from the first device 101, the processing capabilities of the first device 101, etc. In still other embodiments of this application, the wireless communication module 160 can also be used to send the screenshot generated by the mobile phone 200 to the first device 101.

[0075] Display screen 192 is used to display images, videos, etc. Display screen 192 includes a display panel. In some embodiments, mobile phone 200 may include one or N displays screens 192, where N is a positive integer greater than 1. In some embodiments of this application, display screen 192 can be used to display screenshots generated by mobile phone 200.

[0076] Camera 191 is used to capture still images or videos. In some embodiments, mobile phone 200 may include one or N cameras 191, where N is a positive integer greater than 1.

[0077] The memory 120 can be used to store computer executable program code, which includes instructions. The memory 120 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 mobile phone 200. Furthermore, the memory 120 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. The processor 110 executes various functional applications and data processing of the mobile phone 200 by running instructions stored in the memory 120 and / or instructions stored in memory disposed in the processor. In some embodiments of this application, the memory 120 can be used to store screenshots generated by the mobile phone 200.

[0078] The mobile phone 200 can achieve audio functions through the audio module 170 and application processor, such as music playback and recording.

[0079] The sensor module 180 may include one or more sensors, such as, but not limited to, pressure sensors, gyroscope sensors, touch sensors, etc.

[0080] Keypad 190 includes a power button, volume buttons, etc. Keypad 190 can be a mechanical keypad or a touch keypad. Mobile phone 200 can receive keypad input and generate key signal inputs related to user settings and function control of mobile phone 200.

[0081] The SIM card interface 193 is used to connect the SIM card.

[0082] For example, taking the first device 102 as a smartwatch, Figure 3 A schematic diagram of the structure of a smartwatch provided in an embodiment of this application is shown. Figure 3 As shown, the smartwatch 300 may include a processor 310, a memory 320, a charging management module 330, a power management module 341, a battery 342, an antenna, a communication module 350, a sensor module 360, buttons 370, a display screen 380, etc.

[0083] The processor 310, as the main control chip of the smartwatch 300, can process various data and implement various functions of the smartwatch 300. In some embodiments, the processor 310 can be an MCU. In other embodiments, the processor 310 can be an application processor (AP). In still other embodiments, the processor 310 can be both an AP and an MCU. That is, the processor 310 can be implemented as at least one of an AP and an MCU.

[0084] The memory 320 can be used to store computer executable program code, which includes instructions. The processor 310 executes various functional applications and data processing of the smartwatch 300 by running instructions stored in the memory 320 and / or instructions stored in memory disposed within the processor. In some embodiments of this application, the memory 320 can be used to store screenshots generated by the smartwatch 300. In still other embodiments of this application, the memory 320 can also be used to store screenshots generated by the second device 102. Further details regarding the memory 320 can be found in the corresponding description of the memory 120 described above.

[0085] The charging management module 330 receives charging input from the charger. While charging the battery 342, the charging management module 330 can also power the smartwatch via the power management module 341. Optionally, the charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 330 receives charging input from the wired charger via a charging interface, etc. In some wireless charging embodiments, the charging management module 330 receives wireless charging input via the wireless charging coil of the smartwatch 300. For a description of the power management module 341 and the battery 342, please refer to the description of the relevant modules above.

[0086] The antenna is used to transmit and receive electromagnetic waves. The communication module 350 is used to enable the smartwatch 300 to communicate with networks or other devices. In some embodiments, the antenna may specifically include, for example, Figure 2 Antennas 1 and 2 are shown, and the communication module 350 may specifically include, for example, antennas 1 and 2. Figure 2 The mobile communication module 150 and wireless communication module 160 are shown. In other embodiments, the antenna may include only the following: Figure 2 Antenna 2 as shown, the communication module may include only the following: Figure 2 The wireless communication module 160 shown.

[0087] For information on sensor module 360, button 370, and display screen 380, please refer to [link / reference]. Figure 2The relevant descriptions of the corresponding modules are shown below. In some embodiments of this application, the display screen 380 can be used to display one or more screenshots generated by the smartwatch 300 and the mobile phone 200.

[0088] For example, Figure 4 This diagram illustrates the software structure of a smartwatch 300 and a mobile phone 200 according to an embodiment of this application. Figure 4 As shown, the smartwatch 300 includes a screenshot module, a gallery application, and a file transfer service. The screenshot module can be used to receive screenshot operations and enable the screenshot function of the smartwatch 300. The gallery application in the smartwatch 300 can be used to store screenshots generated by the smartwatch 300 and / or the mobile phone 200. Of course, in other embodiments, Figure 4 The gallery application shown can also be implemented as other applications, such as a camera application, a file management application, etc. The file transfer service can be used to enable file transfer and information sharing between the smartwatch 300 and the mobile phone 200. As a specific example, the file transfer service can be a Wear Engine service; of course, in other examples, the file transfer service can also be implemented as other services with file transfer and information sharing functions.

[0089] Optionally, in this embodiment, an application may refer to a software program specifically designed to perform a specific task, capable of running independently, and possessing a user interface and functionality. A module or service may refer to a program running within a system, or a packaged version of a program. Optionally, an application may contain one or more services. A service may include one or more modules. Alternatively, services and modules may exist independently of the application, and modules may exist independently of the service.

[0090] The mobile phone 200 includes a sports and health application and a gallery application. The sports and health application can be used to pair and bind the smartwatch 300 with the mobile phone 200, establishing a connection. The sports and health application may integrate a file transfer service. For a description of this file transfer service, please refer to the corresponding description above. It is understood that this embodiment uses the integration of the file transfer service in the mobile phone 200 into the sports and health application as an example. In other embodiments, the file transfer service in the mobile phone 200 may also be integrated into other applications besides the sports and health application, or it may exist independently in the same way as the smartwatch 300, without being integrated into other applications. The gallery application in the mobile phone 200 can be used to store screenshots and other images generated by the mobile phone 200.

[0091] In some embodiments, after receiving a screenshot operation, the screenshot module in the smartwatch 300 generates screenshot data in response to the operation and transmits the screenshot data to the file transfer service in the smartwatch 300. Then, the file transfer service in the smartwatch 300 sends the screenshot data to the file transfer service in the mobile phone 200 via Bluetooth or Wi-Fi. Accordingly, the mobile phone 200 can process the received screenshot data to generate a screenshot.

[0092] In some embodiments, screenshots generated on mobile phone 200 can also be sent to the gallery application on mobile phone 200 for storage. And / or, screenshots generated on mobile phone 200 can also be sent to smartwatch 300 via a file transfer service. Accordingly, after receiving the screenshots generated by mobile phone 200, the file transfer service of smartwatch 300 can also send them to the gallery application on smartwatch 300 for storage.

[0093] Understandable, Figure 2 , Figure 3 , Figure 4 The illustrated structures do not constitute a specific limitation on smartwatches and mobile phones. In other embodiments of this application, smartwatches and mobile phones may include more or fewer components than illustrated, or combine or separate certain components, or have different component arrangements. The processing steps or functional characteristics of the illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0094] The technical solutions described in the following embodiments can all be implemented in [various applications]. Figure 2 , Figure 3 , Figure 4 The device with the structure shown, and Figure 1 The system is implemented using the architecture shown. The technical solution provided in this application embodiment will be described below with reference to the accompanying drawings, taking a smartwatch as the first device 101 and a mobile phone as the second device 102 as examples.

[0095] In some embodiments, a connection needs to be established between the smartwatch and the mobile phone. In this embodiment, as one possible implementation, the mobile phone can have an application installed for managing the smartwatch, which enables pairing and connection between the smartwatch and the mobile phone. Taking a fitness and health application as an example, the process of establishing a connection between the smartwatch and the mobile phone will be described. For example, as... Figure 5As described in (1), the mobile phone can display a main interface 500 (also known as a desktop 500), which may include icons of one or more applications, such as icons for calendar applications, weather applications, etc., which will not be listed here. The icons of different applications can be used to open the running interface of the corresponding application and realize the functions of the corresponding application. Among these icons of one or more applications is the icon 501 of the sports and health application, which the user can launch through the icon 501 of the sports and health application.

[0096] If a user performs an action such as clicking the icon 501 of the fitness and health app, the app will respond to that action as follows: Figure 5 As shown in (2), the mobile phone can display a health and fitness interface 510. The interface 510 contains one or more modules, such as a heart health module and a body temperature module, which can be used to view the user's health data. The user can bind the smartwatch by accessing the device addition function in the interface 510. If a function button 511 is displayed in the interface 510, the user can perform operations such as clicking on the function button 511, and the system will respond to the operation as follows: Figure 5 As shown in (3), the mobile phone can display a "Scan" control 521. Users can use the "Scan" control 521 to activate the phone's camera and scan objects such as... Figure 5 Scan the device identification code 530 (such as a QR code, barcode, etc.) of the smartwatch shown in (4) to bind the smartwatch to the Sports Health account. Optionally, Figure 5 In section (3), an "Add Device" control 522 can also be displayed. Users can also use this control to search for the smartwatch's identifier and then bind the smartwatch to their Sports & Health account. Of course, in other embodiments, the smartwatch and the mobile phone can also be connected through various methods such as tapping or Bluetooth pairing. This application embodiment does not limit the way the smartwatch and the mobile phone establish a connection.

[0097] Furthermore, after the smartwatch and the mobile phone establish a connection through the methods described above, when the smartwatch receives a screenshot request, for example, the screenshot request can be performed as follows: Figure 6 The screenshot operation shown in Figure (1) involves simultaneously pressing side buttons 601 and 602. Of course, the screenshot operation can also be performed using other button operations, gesture operations, voice operations, etc. This application embodiment does not impose specific limitations on the screenshot operation. In response to the screenshot operation as described above, the smartwatch can generate screenshot data (as described below). Figure 1 Then, the screenshot data is sent to the mobile phone, which generates a screenshot based on the screenshot data.

[0098] Understandably, smartwatches can display various user interfaces when receiving a screenshot request. For example, a smartwatch might display various user interfaces when receiving a screenshot request. Figure 6 Taking interface 600 shown in (1) as an example, the screenshot generated by the mobile phone is the screenshot corresponding to interface 600.

[0099] In some embodiments, to avoid the user perceiving that the smartwatch is not responding to the screenshot operation, the smartwatch may first display the screenshot corresponding to interface 600 during the process of the phone generating the screenshot, or before the smartwatch sends the screenshot data to the phone, as described below for screenshot 0, screenshot 600. Figure 1 Etc. Please refer to the following section for details on the implementation of this screenshot. Optional, such as... Figure 6 Screenshot 610 shown in (2) is as follows: Figure 6 As shown in screenshot 620 in (3), the smartwatch can use a center-zoomed screenshot animation to present the screenshot. That is, during the process of center-zooming the screenshot, the smartwatch can use a center-zoomed screenshot animation to present the screenshot. Figure 6 The screenshot 610 shown in (2) can be gradually reduced to, as shown in Figure 6 Screenshot 620 shown in (3).

[0100] In some embodiments, since the screenshot is generated by the mobile phone, it may be saved on the phone. For user convenience, after receiving the screenshot operation, the smartwatch may also display, in response to the screenshot operation, the following: Figure 6 The reminder message 630 shown in (4) reminds the user of the saved location of the screenshot so that the user can view it.

[0101] The following is combined Figure 4 The architecture shown illustrates the specific implementation of a smartwatch sending screenshot data to a mobile phone, and the mobile phone generating a screenshot. For example, Figure 7 A flowchart illustrating a screenshot method provided in an embodiment of this application is shown. Figure 7 As shown, the method includes the following steps:

[0102] S701, the sports and health features of the mobile phone are linked to the smartwatch.

[0103] For details on the implementation of this binding, please refer to [reference needed]. Figure 5 The relevant implementation is shown below.

[0104] S702, negotiate screenshot parameters for file transfer service in smartwatch and file transfer service in mobile phone.

[0105] In some embodiments, the screenshot parameter can be used to indicate the screenshot processing operations that the smartwatch needs to perform, the screenshot processing operations that the mobile phone needs to perform, etc. The screenshot processing operations that the smartwatch needs to perform and the screenshot processing operations that the mobile phone needs to perform are different. The screenshot processing operations that the smartwatch needs to perform and the screenshot processing operations that the mobile phone needs to perform constitute all the operations used to generate a screenshot of the user interface displayed on the smartwatch. That is, the smartwatch and the mobile phone each perform a portion of the screenshot processing operations to generate a screenshot of the user interface displayed on the smartwatch. For example, generating a screenshot of the user interface displayed on the smartwatch requires N screenshot processing operations; the smartwatch can perform M of these operations, and the mobile phone can perform NM operations, where N and M are both positive integers.

[0106] For example, in the embodiments of this application, the above-mentioned screenshot processing operations may include, but are not limited to, setting the image format of the screenshot, compressing the screenshot, decompressing the screenshot, cropping the screenshot, cropping rounded corners, adding a border to the screenshot, and other preprocessing operations (such as noise reduction).

[0107] In some embodiments, the screenshot parameter can also be used to indicate the processing parameters of the screenshot processing operation. For example, when the screenshot processing operation is to set the image format of the screenshot, the processing parameter corresponding to the screenshot processing operation can be the image format; when the screenshot processing operation is to compress the screenshot, the processing parameter corresponding to the screenshot processing operation can be the compression algorithm; when the screenshot processing operation is to decompress the screenshot, the processing parameter corresponding to the screenshot processing operation can be the decompression algorithm; when the screenshot processing operation is to crop rounded corners, the processing parameter corresponding to the screenshot processing operation can be the crop rounded corner algorithm, etc. Optionally, a screenshot processing operation may or may not have corresponding processing parameters. For example, there are corresponding processing parameters for compressed screenshots and decompressed screenshots, but there are no corresponding processing parameters for preprocessing operations such as noise reduction. When a screenshot processing operation has corresponding processing parameters, the smartwatch or mobile phone can use the corresponding processing parameters to perform the screenshot processing operation.

[0108] In some embodiments, screenshot parameters can be determined based on the processing power of the smartwatch and the mobile phone; that is, the screenshot parameters are related to the processing power of the smartwatch and the mobile phone. In this embodiment, as a possible implementation, the screenshot parameters can be determined by the mobile phone. The smartwatch can send its processing power to the mobile phone, and correspondingly, after receiving the processing power of the smartwatch, the mobile phone can determine the screenshot parameters based on its own processing power, thereby achieving screenshot parameter negotiation. Finally, to facilitate the smartwatch to perform the screenshot processing operation, the mobile phone can also send the screenshot parameters to the smartwatch. That is, the smartwatch can store the screenshot parameters. In this implementation, the mobile phone can only indicate the screenshot processing operation that needs to be performed by the smartwatch, and the processing parameters of the screenshot processing operation, to the smartwatch. For example, taking the screenshot parameters indicating that the smartwatch needs to perform M screenshot processing operations as an example, the mobile phone can indicate the identifier (such as the sequence number) of each of these M screenshot processing operations to the smartwatch, or the mobile phone can indicate the identifier of the last screenshot processing operation among these M screenshot processing operations to the smartwatch, or the mobile phone can indicate the identifier of the screenshot processing operation that does not need to be performed by the smartwatch to the smartwatch, etc. This application embodiment does not impose specific limitations on the indication method.

[0109] Optionally, this implementation does not restrict whether the mobile phone should indicate to the mobile phone the screenshot processing operations it needs to perform and the processing parameters of these screenshot processing operations.

[0110] In this embodiment, as another possible implementation, the screenshot parameters can be determined by the smartwatch. The mobile phone can send its processing power to the smartwatch, and correspondingly, after receiving the processing power from the mobile phone, the smartwatch can determine the screenshot parameters based on its own processing power. Similarly, to facilitate the mobile phone to perform screenshot processing operations, the smartwatch can also send the screenshot parameters to the mobile phone. That is to say, the mobile phone can store the screenshot parameters. Similarly, in this implementation, the smartwatch can only indicate to the mobile phone the screenshot processing operations that need to be performed, and the processing parameters of these screenshot processing operations. Optionally, there is no restriction on whether the smartwatch indicates the screenshot processing operations it needs to perform and the processing parameters of these screenshot processing operations to the mobile phone. Regarding the method of the smartwatch instructing the mobile phone to perform the screenshot processing operations, please refer to the implementation of the method of the mobile phone instructing the smartwatch to perform the screenshot processing operations described above.

[0111] In this embodiment of the application, the screenshot parameters stored in the smartwatch and mobile phone may also have other names, such as negotiation result, first parameter, etc.

[0112] It is understood that in this embodiment, the processing power of the smartwatch and the mobile phone can refer to capabilities directly related to screenshotting, such as supported image formats, supported compression algorithms, supported decompression algorithms, and supported rounded corner algorithms. It can also include capabilities indirectly related to screenshotting, such as processor speed and system memory. For example, taking the processor installed in the smartwatch as an MCU, the processing power of the smartwatch can be indicated by the type of processor installed, processor speed, and system memory. Since the processing power of a smartwatch is much weaker than that of a mobile phone, the screenshot processing operations indicated in the screenshot parameters can be operations that do not require high processor capabilities, such as setting the image format for the screenshot and compressing the screenshot. Conversely, the screenshot processing operations indicated in the screenshot parameters can be operations that require high processor capabilities, such as cropping the screenshot, cropping rounded corners, and adding borders. For example, taking the processor installed in a smartwatch as an AP (Application Processor), the smartwatch's processing power is indicated by factors such as the processor type, processor speed, and system memory. Since the AP's processing power is relatively higher than that of an MCU (Microcontroller Unit), the number or type of screenshot processing operations that the smartwatch needs to perform, as indicated in the screenshot parameters, can differ from the previous example. For instance, the number of screenshot processing operations indicated in the screenshot parameters can be greater than in the previous example, such as including setting the image format and compressing the screenshot, as mentioned above, as well as decompressing the screenshot. Alternatively, the screenshot processing operations indicated in the screenshot parameters can include several operations that place higher demands on the processor, such as cropping, rounding corners, and adding borders, or one or more of these.

[0113] For example, taking a smartwatch with an MCU and an AP processor as an example, the smartwatch can be in different operating modes, such as AP mode and MCU mode. When the smartwatch is in AP mode, the AP is active; when the smartwatch is in MCU mode, the MCU is active and the AP is inactive. When the smartwatch is in AP mode, the screenshot processing operations indicated in the screenshot parameters can be similarly implemented when the processor is an AP. When the smartwatch is in MCU mode, the screenshot processing operations indicated in the screenshot parameters can also be similarly implemented when the processor is an MCU.

[0114] Of course, in other examples, the screenshot processing operations that the smartwatch needs to perform, as indicated in the screenshot parameters, can be the same regardless of the processor installed in the wearable device.

[0115] In a specific example, assuming that the processing power of a smartwatch indicates the image formats supported by the smartwatch, and the processing power of a mobile phone indicates the image formats supported by the watch, the screenshot processing operation indicated by the screenshot parameters can include setting the image format. The processing parameters of this screenshot processing operation can be the target image format, or in other words, the screenshot parameters can include the target image format, which can be an image format supported by both the smartwatch and the mobile phone.

[0116] In another specific example, assuming the smartwatch's processing power indicates a compression algorithm supported by the smartwatch, and the phone's processing power indicates a decompression algorithm supported by the phone, then the screenshot processing operation indicated by the screenshot parameters can include compressed screenshots. The processing parameters for this screenshot processing operation can be the target compression algorithm, or in other words, the screenshot parameters can include the target compression algorithm. The target compression algorithm can be the compression algorithm corresponding to the decompression algorithm supported by the phone and also a compression algorithm supported by the smartwatch. It is understood that this example uses the smartwatch to perform the compressed screenshot operation and the phone to perform the decompressed screenshot operation.

[0117] Optionally, since different processing parameters may have corresponding relationships—for example, a certain image format may only support a certain compression algorithm or decompression algorithm—the target compression algorithm can be determined once the target image format is determined. In other words, different processing parameters, such as image format and compression algorithm, can be negotiated separately based on the processing capabilities of the smartwatch and the phone. Alternatively, a subset of processing parameters can be negotiated based on the processing capabilities of the smartwatch and the phone. Since other processing parameters have corresponding relationships with these negotiated parameters, the remaining processing parameters can be directly determined based on these negotiated parameters. For example, regarding image format and compression algorithm, both can be negotiated simultaneously, or only the image format can be negotiated, with the compression algorithm determined based on the negotiated image format.

[0118] Optionally, in the above example, since the smartwatch is linked to the fitness and health app on the phone, the compression algorithms, decompression algorithms, image formats, and rounded corner cropping algorithms supported by the phone can be the same as those supported by the fitness and health app. Different versions of the fitness and health app can support the same or different image formats and decompression algorithms.

[0119] In some embodiments, the smartwatch can also send an image resolution to the phone. This image resolution can be used by the phone to crop screenshots, ensuring that the screenshots appear consistent with the shape of the smartwatch screen (e.g., square, round, etc.). This image resolution is also the screen resolution of the smartwatch. Optionally, this image resolution can be considered part of the smartwatch's processing power, sent to the phone along with its own processing capabilities; that is, the image resolution can be used as a processing parameter. Alternatively, the smartwatch can send the image resolution to the phone independently, meaning it may not be used as a processing parameter. For example, when the smartwatch screen is square, the image resolution can be represented by the product of the number of pixels in the horizontal direction and the number of pixels in the vertical direction. When the smartwatch screen is round, the image resolution can be represented by the product of the number of pixels in the horizontal direction and the number of pixels in the vertical direction, plus the diameter in pixels. Thus, when the phone receives the image resolution from the smartwatch, it can determine the shape of the smartwatch screen and perform a cropped screenshot operation.

[0120] Optionally, when the phone performs a cropping screenshot operation, the smartwatch can perform the aforementioned operation of sending the image resolution to the phone. Of course, in other examples, if the smartwatch performs the cropping screenshot operation, the smartwatch may not perform the aforementioned operation of sending the image resolution to the phone.

[0121] S703, the screenshot module of the smartwatch receives the screenshot operation.

[0122] For example, the screenshot operation can be as follows: Figure 6 Example shown in (1). Optionally, the smartwatch can display any user interface when it receives a screenshot operation, which can be used to take a screenshot of the user interface displayed by the smartwatch.

[0123] S704: The screenshot module of the smartwatch sends a screenshot event to the file transfer service of the smartwatch.

[0124] This screenshot event can be used to establish a connection between the file transfer service of a smartwatch and the file transfer service on a mobile phone.

[0125] S705: The file transfer service of the smartwatch establishes a connection with the file transfer service on the mobile phone.

[0126] In step S705, the smartwatch can initiate a connection. Correspondingly, the mobile phone responds to the smartwatch's initiation by sending a response message to the smartwatch, thus establishing the connection. Similarly, in step S701, the mobile phone can initiate a connection, and the smartwatch responds to the mobile phone's initiation by sending a response message to the mobile phone, thus establishing the connection. Furthermore, the smartwatch and mobile phone can transmit screenshots based on the established connection. Taking the Wear Engine service as an example, the smartwatch and mobile phone can initiate the Wear Engine service via a ping interface and send response messages to each other via P2P messages to achieve interconnection of the Wear Engine service.

[0127] S706, smartwatches generate screenshots based on screenshot parameters Figure 1 .

[0128] In some embodiments, in response to a screenshot operation, the smartwatch can perform M screenshot processing operations as indicated in the screenshot parameters on the original screenshot data of the user interface to generate a screenshot. Figure 1 (This can be used as an example of a second screenshot). It is understood that in this embodiment, the screenshot parameters can be negotiated in step S702.

[0129] In some embodiments, when some of the M screenshot processing operations have processing parameters, the smartwatch can use the processing parameters of the screenshot processing operation to process the original screenshot data of the user interface.

[0130] In some embodiments, the M screenshot processing operations include setting an image format, where the processing parameters of the screenshot processing operation are the target image format as described above. Then step S706 can be specifically implemented as follows: the smartwatch sets the image format of the original screenshot data of the user interface to the target image format to generate the screenshot. Figure 1 That is, cut off Figure 1 The image format is the target image format. Thus, the smartwatch uses an image format supported by both itself and the phone as the capture format. Figure 1 The image format allows the phone to receive the screenshot. Figure 1 After that, it was able to successfully parse the screenshot. Figure 1 .

[0131] In some other embodiments, the M screenshot processing operations include screenshot compression, where the processing parameters of the screenshot processing operation are the target compression algorithm described above. Then step S706 can be specifically implemented as follows: the smartwatch uses the target compression algorithm to compress the original screenshot data of the user interface to generate a screenshot. Figure 1In this way, the smartwatch uses its own supported compression algorithm, and the compression algorithm is the same as the decompression algorithm supported by the phone, to compress the data. Figure 1 This causes the phone to receive intercepted data. Figure 1 After that, the compressed file can be successfully decompressed. Figure 1 Furthermore, compressing the screenshot data before transmission can reduce transmission latency and thus improve screenshot efficiency.

[0132] In some embodiments, the cropping operation is not included in the M screenshot processing operations. That is, in this embodiment, the cropping screenshot operation is performed by the mobile phone. Therefore, in this embodiment, regardless of the shape of the smartwatch display (e.g., circular, rectangular), the cropping... Figure 1 Both can be the shape of the original screenshot, such as a rectangular screenshot. Optionally, in this embodiment, the smartwatch can send the screenshot to the phone. Figure 1 The image resolution, as described above, is sent to the phone at the appropriate time to allow the phone to perform the cropping operation. Alternatively, the image resolution can be sent to the phone when negotiating the screenshot parameters, as described above. In this way, the smartwatch sends the image resolution to the phone, which then crops the screenshot based on that resolution. This allows for different screenshots from smartwatches with different screen shapes, solving the problem of monotonous screenshot effects and improving screenshot quality. Furthermore, since the phone's processing power is greater than that of the smartwatch, having the phone perform the cropping operation improves screenshot efficiency.

[0133] In other embodiments, the M screenshot processing operations include a cropping operation. That is, in this embodiment, the smartwatch can perform the cropping screenshot operation based on the image resolution. Therefore, in this embodiment, when the smartwatch display has different shapes, the cropping... Figure 1 The shape can be different. For example, when the smartwatch display is round, the truncated shape can be different. Figure 1 It can be circular; when the smartwatch display is rectangular, the cut-off value can be... Figure 1 It can be rectangular; that is, in this embodiment, the cut-off... Figure 1 It can maintain the same shape as the smartwatch screen. This allows the smartwatch to crop the screenshot based on image resolution, resulting in different screenshots for smartwatches with different screen shapes. This solves the problem of monotonous screenshot effects and improves the overall screenshot quality.

[0134] S707a, Smartwatch Display Screen Figure 1 .

[0135] In some embodiments, to avoid the user perceiving the smartwatch as unresponsive to the screenshot operation, the smartwatch generates a screenshot... Figure 1 After that, you can first present the cut-off. Figure 1 For example, a smartwatch could use a centered, zoomed-in screenshot animation to display the screenshot. Figure 1 ,like Figure 6 Screenshot 610 shown in (2) is as follows: Figure 6 The screenshots shown in (3) are all screenshots. Figure 1 Of course, smartwatches can also use other effects to present the screenshot. Figure 1 However, the embodiments in this application do not impose any limitations on this.

[0136] It is understood that step S707a is an optional step.

[0137] The file transfer service in the S707b smartwatch sends a screenshot to the file transfer service on the phone. Figure 1 .

[0138] Optionally, there is no restriction on the execution order of steps S707a and S707b.

[0139] S708, mobile phone based on screenshot parameters and screenshot Figure 1 Generate cut Figure 2 .

[0140] In some embodiments, the mobile phone responds to being able to intercept Figure 1 The screenshot will be generated by performing NM screenshot processing operations as indicated in the screenshot parameters. Figure 2 (This can be used as an example for the first screenshot). Similarly, when some of the NM screenshot processing operations have screenshot parameters, the phone can use the processing parameters of that screenshot processing operation to process the screenshot. Figure 1 Process it.

[0141] In some embodiments, the NM screenshot processing operations include decompressing the screenshots, and the processing parameters of the screenshot processing operation can be a decompression algorithm. Then step S708 can be specifically implemented as follows: the mobile phone decompresses the screenshots using the decompression algorithm corresponding to the target compression algorithm as described above. Figure 1 Generate cut Figure 2 .

[0142] In some embodiments, the M screenshot processing operations may further include one or more of the following: cropping rounded corners, adding borders, etc. Then step S708 can be specifically implemented as follows: the mobile phone uses a target rounded corner cropping algorithm to crop the... Figure 1 Rounding corners and cutting edges Figure 1 Add borders to generate screenshots Figure 2 The target rounded corner algorithm can be any rounded corner algorithm supported by the mobile phone.

[0143] In some embodiments, in addition to performing step S708, the mobile phone can also perform image processing based on the image resolution obtained from the smartwatch. Figure 1 Perform cropping to generate cut Figure 2It is understood that, in the embodiments of this application, the cropping operation performed based on image resolution can be included in the process of generating the crop. Figure 2 In the N screenshot processing operations, the cropping operation described in step S706 is an example of being included in the N screenshot processing operations. Of course, it may also not be included in the operations used to generate the screenshot. Figure 2 In the N screenshot processing operations, it exists as an additional processing operation on its own. In this embodiment, it is taken as an example that it is not included in the N screenshot processing operations. When the mobile phone needs to perform NM screenshot processing operations and cropping operations based on image resolution, this application does not limit the order in which they are executed.

[0144] For example, consider a mobile phone cropping a screenshot based on the image resolution obtained from a smartwatch. When the smartwatch displays a user interface like... Figure 9 As shown in (1), when the smartwatch performs M screenshot processing operations, the resulting screenshot... Figure 1 It is possible Figure 9 The image shown in (2) is processed by the mobile phone based on the image resolution obtained from the smartwatch. Figure 9 The cropped image shown in (2) is generated by performing a cropping operation. Figure 2 It is possible Figure 9 The image shown in (3). For example, taking the operation of cropping rounded corners on a mobile phone as an example, when the user interface displayed on the smartwatch is as shown... Figure 9 As shown in (4), the content in this user interface is as follows: Figure 9 The content in the user interface shown in (1) is the same. The smartwatch generates screenshots by performing M screenshot processing operations. Figure 1 It can also be like Figure 9 The image shown in (2) is a cropped image generated after the phone performs a rounded corner cropping operation. Figure 2 It is possible Figure 9 The image described in (5).

[0145] Taking the operation of adding a border on a mobile phone as an example, combined with Figure 9 to intercept Figure 1 for Figure 9 For example, take the image shown in (2) as an example: Figure 10 In (1), the mobile phone can adjust the image resolution based on the image obtained from the smartwatch. Figure 9 The image shown in (2) is the result of cropping and adding a border (which can be used as a cropping tool). Figure 2 (One example). For example: Figure 10 (2) can be used for mobile phones to Figure 9 The image shown in (2) is the result of adding a border and cropping rounded corners (which can be used as a cropping tool). Figure 2 (One example). For example: Figure 10 (3) can be used for mobile phones to Figure 9 The image shown in (2) is generated after performing the operation of adding a border but not the operation of cropping rounded corners (which can be used as a cropping tool). Figure 2 (An example).

[0146] Based on the above technical solution, when a smartwatch receives a screenshot request, it can perform some screenshot processing operations based on the screenshot parameters, and then send the processed screenshot to the mobile phone. The mobile phone can then perform other screenshot processing operations based on the screenshot parameters to generate a screenshot. This realizes the screenshot function of wearable devices. Furthermore, the screenshot parameters are determined based on the processing capabilities of the smartwatch and the mobile phone. In other words, the screenshot processing operations performed by the smartwatch and the mobile phone depend on their respective processing capabilities, thereby improving screenshot efficiency.

[0147] In some embodiments, Figure 7 The method shown may also include steps S709 and S710.

[0148] S709, the file transfer service in the mobile phone sends screenshots to the mobile phone's gallery application. Figure 2 .

[0149] In other words, in step S709, the mobile phone can intercept... Figure 2 Stored in the gallery application. For example, such as... Figure 11 As shown in Figure (1), the mobile phone can display the running interface 1000 of the gallery application, which can display one or more images stored in the gallery application. When the file transfer service in the mobile phone sends a screenshot to the gallery application... Figure 2 After that, as Figure 11 As shown in (2), the mobile phone can display the running interface 1010 of the Gallery application, and the running interface 1010 can display screenshots 1011 stored in the Gallery application (which can be used as screenshots). Figure 2 (An example).

[0150] In some embodiments, when the gallery application successfully stores a screenshot Figure 2 Afterward, the phone can send a response message (such as the P2P message mentioned above) to the smartwatch to indicate that the screenshot has been successfully saved to the Gallery app. Correspondingly, when the smartwatch receives this response message from the phone, it can display something like... Figure 6 The reminder message 610 mentioned in (4) reminds the user of the saved location of the screenshot so that the user can view it.

[0151] S710, mobile phone sends screenshot to smartwatch Figure 2 .

[0152] Correspondingly, smartwatches can store screenshots Figure 2In some embodiments, when the smartwatch does not receive an intercept... Figure 2 At that time, the smartwatch can generate screenshots Figure 1 Alternatively, screenshot 0, as described below, may be presented to the user. In other embodiments, when the smartwatch receives a screenshot... Figure 2 At the same time, the smartwatch can simultaneously capture screenshot 0 and screenshot 1. Figure 1 ,cut Figure 2 All of these can be presented to the user, or only the screenshot can be shown. Figure 2 Presented to the user. In this embodiment of the application, there is no restriction on which screenshot the smartwatch specifically presents to the user.

[0153] Optionally, when the phone sends a screenshot to the smartwatch Figure 2 In some embodiments, considering factors such as transmission duration and the processing power of the smartwatch, it can also be determined whether to intercept data based on the processing power of the mobile phone and the smartwatch. Figure 2 Perform compression to compress the segment. Figure 2 The data is sent to the smartwatch to reduce transmission time. Optionally, the timing of screenshot parameter negotiation can be used to determine whether the phone should perform the compression operation and to determine the compression algorithm used. Of course, this determination operation can also be performed before step S710; this embodiment does not limit this.

[0154] Similarly, in this example, the mobile phone needs to perform compression. Figure 2 Taking operation as an example, if the smartwatch's processing power indicates that it supports a decompression algorithm, and the phone's processing power indicates that it supports a compression algorithm, then the phone can use its own supported compression algorithm to decompress the data. Figure 2 The compression operation is performed, and the corresponding decompression algorithm is one supported by the smartwatch. This allows the smartwatch to receive intercepted data... Figure 2 After that, the file can be successfully decompressed. Figure 2 .

[0155] In some embodiments, when the smartwatch receives an intercept Figure 2 At the same time, the smartwatch can also capture... Figure 2 It can be used in different scenarios, such as sharing with friends via tap-to-share or setting it as a global theme. For example, a smartwatch might detect when a user is about to tap... Figure 2 When an action is set as a global theme, the smartwatch can respond to that action by capturing screenshots. Figure 2 It can also be set as a theme for multiple user interfaces, including but not limited to the main interface, the drop-down control center, and the negative one screen. For example, a screenshot... Figure 2 For example Figure 12 Taking screenshot 1200 as an example (1), after setting screenshot 1200 as the global theme, Figure 12The interface 1210 shown in (2) illustrates the effect of the negative one screen of a smartwatch. Figure 12 The interface diagram 1220 shown in (3) illustrates the effect of the main interface of the smartwatch. Figure 12 The interface diagram 1230 shown in (4) illustrates the effect of the pull-down control center of the smartwatch.

[0156] The above embodiments illustrate the negotiation of screenshot parameters between the smartwatch and the mobile phone during pairing. Subsequently, when the smartwatch receives a screenshot request, both the smartwatch and the mobile phone can directly process the screenshot based on the previously negotiated screenshot parameters, improving screenshot efficiency. In other embodiments, the smartwatch and the mobile phone can also negotiate screenshot parameters after the smartwatch receives a screenshot request. For example, Figure 8 This illustration shows a flowchart of yet another screenshot method provided in an embodiment of this application. Figure 8 As shown, the method includes the following steps:

[0157] S801, the screenshot module of the smartwatch receives the screenshot operation.

[0158] S802, the screenshot module of the smartwatch sends a screenshot event to the file transfer service of the smartwatch.

[0159] S803a, Smartwatch screenshot 0.

[0160] The smartwatch can generate a preview image, i.e., screenshot 0, based on the user interface displayed when a screenshot operation is received. Screenshot 0 can be an image that has not undergone any screenshot processing.

[0161] S803b, screenshot of smartwatch display 0.

[0162] Similarly, to avoid users perceiving the smartwatch as unresponsive to screenshot operations, the smartwatch can generate and then display screenshot 0. Likewise, the smartwatch can use the center-zoom animation described above to display screenshot 0, such as... Figure 6 Screenshot 610 shown in (2) is as follows: Figure 6 The screenshots 620 shown in (3) are all screenshots 0. Of course, smartwatches can also use other effects to present screenshots 0, and this application embodiment does not limit this.

[0163] It is understood that steps S803a and S803b can be optional steps.

[0164] The S803c smartwatch establishes a connection with the file transfer service on the mobile phone.

[0165] It is understandable that there is no restriction on the execution order of steps S803a to S803b and steps S803c to S804.

[0166] S804, negotiate screenshot parameters for file transfer service in smartwatch and file transfer service in mobile phone.

[0167] S805, smartwatches generate screenshots based on screenshot parameters Figure 1 .

[0168] S806, the file transfer service in the smartwatch sends a screenshot to the file transfer service on the phone. Figure 1 .

[0169] S807, mobile phone based on screenshot parameters and screenshot Figure 1 Generate cut Figure 2 .

[0170] In some embodiments, Figure 8 The method shown may also include steps S808 and S809.

[0171] The S808 mobile phone's file transfer service sends screenshots to the phone's gallery application. Figure 2 .

[0172] S809, mobile phone sends interception to smartwatch Figure 2 .

[0173] about Figure 8 Please refer to the descriptions of each step in the process. Figure 7 The corresponding steps are explained below.

[0174] The above primarily describes the solutions provided by the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the above functions, the device includes corresponding hardware structures and / or software modules for executing each function. By combining the units and algorithm steps of the various examples described in the embodiments disclosed in this application, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by a computer driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solutions of the embodiments of this application.

[0175] This application provides embodiments that can divide the device into functional modules based on the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods.

[0176] like Figure 13 The diagram shown is a structural schematic of a device provided in an embodiment of this application. The device 1300 can be used to implement the methods executed by the devices described in the above method embodiments.

[0177] In one possible example, taking device 1300 as an example... Figure 1 Taking the first device 101 as an example, device 1300 may include a processing unit 1301, a communication unit 1302, and a display unit 1303. The processing unit 1301 is used to support device 1300 in performing operations. Figures 1 to 12 The first device's processing function, communication unit 1302, as described in any one of the above, is used to support device 1300 in performing... Figures 1 to 12 The communication function of the first device as described in any one of the following. Display unit 1303, for supporting device 1300 in performing... Figures 1 to 12 The display function of the first device as described in any one of the following statements.

[0178] In another possible example, taking device 1300 as an example... Figure 2 Taking the second device 102 as an example, device 1300 may include a processing unit 1301 and a communication unit 1302. The processing unit 1301 is used to support device 1300 in performing... Figures 1 to 12 The second device processing function, communication unit 1302, as described in any one of the above, is used to support device 1300 in performing [the following actions]. Figures 1 to 12 The communication function of the second device as described in any one of the above. Optionally, in this example, device 1300 may further include a display unit 1303 for supporting device 1300 in performing [the following actions]: Figures 1 to 12 The display function of the second device as described in any one of the above.

[0179] Optional, Figure 13 The device 1300 shown may also include a storage unit ( Figure 13 (not shown in the image), this storage unit stores a program or instruction. When the processing unit 1301 executes the program or instruction, it causes... Figure 13 The device 1300 shown can perform the method described in the above-described method embodiments.

[0180] Figure 13The technical effects of the device 1300 shown can be referred to the technical effects described in the above method embodiments, and will not be repeated here. Figure 13 The processing unit 1301 involved in the illustrated device 1300 can be implemented by a processor or processor-related circuit components, and can be a processor or processing module. The communication unit 1302 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver module. The display unit 1303 can be implemented by display screen-related components.

[0181] This application also provides a chip system, such as... Figure 14 As shown, the chip system 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. 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 device can perform the various steps executed by the device in the above embodiments. Of course, the chip system may also include other discrete components, and this application embodiment does not specifically limit this.

[0182] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0183] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application does not specifically limit the type of memory or the arrangement of the memory and processor.

[0184] For example, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0185] It should be understood that each step in the above method embodiments can be completed by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0186] This application also provides a computer storage medium storing computer instructions, which, when executed on a device, cause the device to perform the methods described in the above-described method embodiments.

[0187] This application provides a computer program product, which includes a computer program or instructions that, when run on a computer, cause the computer to perform the methods described in the above-described method embodiments.

[0188] In addition, this application also provides 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 apparatus to perform the methods in the above-described method embodiments.

[0189] In this embodiment, the device, computer storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0190] Through the above description of the embodiments, those skilled in the art will 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.

[0191] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The embodiments can be combined with or referenced to each other without conflict. The apparatus embodiments described above are merely illustrative; for example, 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 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.

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

[0193] 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.

[0194] 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, in essence, or 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.

[0195] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A screenshot method, characterized in that, Applied to wearable devices including a display screen, the wearable device being connected to an electronic device, the method includes: When the wearable device displays a user interface, in response to a received screenshot operation, a negotiation result is obtained. The negotiation result indicates M screenshot processing operations that the wearable device needs to perform. The M screenshot processing operations are some of the N screenshot processing operations used to generate the first screenshot of the user interface. M and N are both positive integers. The negotiation result is determined based on the processing power of the wearable device and the processing power of the electronic device. The wearable device performs the M screenshot processing operations on the original screenshot data of the user interface to generate a second screenshot; The wearable device sends the second screenshot to the electronic device, and the second screenshot is used by the electronic device to perform NM screenshot processing operations to generate the first screenshot.

2. The method according to claim 1, characterized in that, The negotiation result also indicates the processing parameters for the M screenshot processing operations.

3. The method according to claim 1 or 2, characterized in that, Before the wearable device obtains the negotiation result, the method further includes: The wearable device sends its processing capabilities to the electronic device; The wearable device receives the negotiation result from the electronic device.

4. The method according to claim 2 or 3, characterized in that, The processing parameters include the target image format.

5. The method according to claim 4, characterized in that, The processing capability of the wearable device indicates the image formats supported by the wearable device, the processing capability of the electronic device indicates the image formats supported by the electronic device, and the target image format is an image format supported by both the wearable device and the electronic device.

6. The method according to any one of claims 1-5, characterized in that, The M screenshot processing operations include compression operations performed using the target compression algorithm.

7. The method according to claim 6, characterized in that, The processing capability of the wearable device indicates the compression algorithm supported by the wearable device, the processing capability of the electronic device indicates the decompression algorithm supported by the electronic device, and the target compression algorithm is the compression algorithm corresponding to the decompression algorithm supported by the electronic device and is also the compression algorithm supported by the wearable device.

8. The method according to any one of claims 1-7, characterized in that, The wearable device is equipped with one or more of the following processors: a microprocessor unit (MCU) and an application processor (AP).

9. A screenshot method, characterized in that, Applied to an electronic device that establishes a connection with a wearable device, the method includes: The electronic device acquires a negotiation result and a second screenshot. The negotiation result indicates NM screenshot processing operations that the electronic device needs to perform. The second screenshot is obtained by the wearable device performing M of the N screenshot processing operations on the original data of the displayed user interface. The N screenshot processing operations are operations used to generate the first screenshot of the user interface. M and N are both positive integers. The negotiation result is determined based on the processing capabilities of the wearable device and the electronic device. The electronic device performs the NM screenshot processing operations on the second screenshot to generate the first screenshot.

10. The method according to claim 9, characterized in that, Before the electronic device obtains the negotiation result, the method further includes: The electronic device acquires the processing power of the wearable device; The electronic device determines the negotiation result based on the processing power of the wearable device and the processing power of the electronic device.

11. The method according to claim 10, characterized in that, After determining the negotiation result, the method further includes: The electronic device sends the negotiation result to the wearable device.

12. The method according to any one of claims 9-11, characterized in that, The method further includes: The electronic device receives image resolution from the wearable device; The electronic device uses the image resolution to crop the second screenshot to generate the first screenshot.

13. The method according to any one of claims 10-12, characterized in that, The negotiation result also indicates the processing parameters for the screenshot processing operation.

14. The method according to claim 13, characterized in that, The processing parameters include the target image format.

15. The method according to claim 14, characterized in that, The processing capability of the wearable device indicates the image formats supported by the wearable device, and the processing capability of the electronic device indicates the image formats supported by the electronic device. The target image format is an image format supported by both the wearable device and the electronic device.

16. The method according to any one of claims 13-15, characterized in that, The second screenshot is a screenshot compressed using the target compression algorithm. The NM screenshot processing operations include decompressing the second screenshot using the decompression algorithm corresponding to the target compression algorithm.

17. The method according to claim 16, characterized in that, The processing capability of the wearable device indicates the compression algorithm supported by the wearable device, the processing capability of the electronic device indicates the decompression algorithm supported by the electronic device, and the target compression algorithm is the compression algorithm corresponding to the decompression algorithm supported by the electronic device and is also the compression algorithm supported by the wearable device.

18. The method according to any one of claims 9-17, characterized in that, The NM screenshot processing operations include at least one of cropping rounded corners and adding borders.

19. A wearable device, characterized in that, include: The device includes a processor, a display screen, a communication interface, and a memory, wherein the memory, the display screen, and the communication interface are coupled to the processor, the communication interface is used to communicate with other devices, the memory is used to store program code including instructions, and the processor reads the instructions from the memory to cause the wearable device to perform the method as described in any one of claims 1-8.

20. An electronic device, characterized in that, include: The electronic device includes a processor, a communication interface, and a memory, wherein the memory and the communication interface are coupled to the processor, the communication interface is used to communicate with other devices, the memory is used to store program code including instructions, and the processor reads the instructions from the memory to cause the electronic device to perform the method as described in any one of claims 9-18.

21. A communication system, characterized in that... The invention includes wearable devices and electronic devices, wherein the wearable devices are used to perform the method as described in any one of claims 1-8, and the electronic devices are used to perform the method as described in any one of claims 9-18.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program that, when executed on the device, causes the device to perform the method as claimed in any one of claims 1-8, or causes the device to perform the method as claimed in any one of claims 9-18.

23. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-8, or cause the computer to perform the method as described in any one of claims 9-18.

Images