Recording method, electronic equipment and system

Abstract

The invention provides a recording method, an electronic device and a system, and the method comprises the steps: receiving a first message sent by a second device, the first message being sent when the second device receives a first operation; sending the state of the first device to the second device according to the first message; receiving a first instruction sent by the second equipment, wherein the first instruction is sent when the second equipment determines that the state of the first equipment meets a first preset condition; a first interface displayed by the first device is recorded according to the first instruction, a first file is generated, and the first interface is used for playing first multimedia; and sending the first file to the second device. According to the method and the device, the user does not need to manually select the equipment needing to be shared, so that the user operation and time cost is reduced, the multimedia file sharing efficiency in the recording scene is improved, and the function availability is improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a recording method, electronic equipment and system. Background Art

[0002] When users use large-screen devices to watch multimedia, they hope to record the highlights in the multimedia (such as clips of goals in football games) to store or share them with other devices. Currently, users can use the remote control to start the recording function of the large-screen device to record the above highlights. After the recording is completed, the large-screen device can search for nearby devices that can be shared, and then transfer the recorded multimedia files to the devices that need to be shared. This method requires the user to manually select the device to be shared after the recording is completed, which costs the user's time, has low efficiency in multimedia file sharing, and has low functional availability. Summary of the invention

[0003] The present application discloses a recording method, electronic device and system, which do not require users to manually select devices to be shared, reducing user operations and time costs, thereby improving the efficiency of multimedia file sharing in recording scenarios and improving functional availability.

[0004] In a first aspect, an embodiment of the present application provides a recording method, which is applied to a first device, and the method includes: receiving a first message sent by a second device, the first message being sent by the second device when it receives a first operation; sending the status of the first device to the second device according to the first message; receiving a first instruction sent by the second device, the first instruction being sent when the second device determines that the status of the first device meets a first preset condition; recording a first interface displayed by the first device according to the first instruction to generate a first file, the first interface being used to play a first multimedia; and sending the first file to the second device.

[0005] In the above method, the second device can act as a master device to control the first device (which can be called a controlled device) in real time to record the first multimedia. After the recording is completed, the controlled device can directly return the recorded first file to the master device. In this way, the user no longer needs to manually select the device to be shared, but can directly select the master device in the recording scene and perform an operation on the master device to realize the recording and sharing process of the first file, which reduces user operation and time costs, thereby improving the efficiency of sharing the first file in the recording scene and improving the user experience.

[0006] In a possible implementation, the state of the first device includes the state of a first function and the state of a second function, the first function is a function of recording the first interface displayed by the first device, and the second function is a function that cannot be turned on when the first device turns on the first function.

[0007] In a possible implementation manner, the state of the first device satisfies a first preset condition, including: the second function of the first device is not enabled.

[0008] In the above method, before the first device receives the first instruction sent by the second device, the status of the first device can be detected first. When the status of the first device meets the first preset condition, the recording of the first multimedia is started. Otherwise, the first multimedia is not recorded, thereby avoiding problems such as abnormalities in the recording process of the first multimedia and interruption of the processing of other functions in progress, thereby further improving the user experience.

[0009] In a possible implementation, the first operation is an operation on a recording control in a second interface displayed by the second device, and the second interface is an operation interface of the first device.

[0010] In the above method, the user can directly perform a first operation in the recording scene to realize the recording and sharing process, rather than performing cumbersome operations (for example, operating once to start recording, and operating again to select the device to be shared), thereby reducing user operations and time costs, thereby improving the efficiency of the first file sharing in the recording scene and improving the user experience.

[0011] In a possible implementation, the method also includes: receiving a second instruction sent by the second device, the second instruction being sent when the second device receives a second operation; stopping recording the first interface according to the second instruction; or detecting a first duration for recording the first interface, and stopping recording the first interface when the first duration is greater than or equal to a preset duration.

[0012] In the above method, during the recording process, the second device can control the first device to stop recording in real time, and the first device can also stop recording according to the actual recording time (ie, the first time). For example, when the recording time can support up to 5 minutes, the recording can be stopped in time.

[0013] In a possible implementation, the first file includes multiple file blocks, and the method further includes: receiving a second message sent by the second device, the second message including the file blocks received by the second device; and sending a third message to the second device according to the second message, the third message including the file blocks not received by the second device, and the file blocks not received by the second device are any file blocks among the multiple file blocks except the file blocks received by the second device.

[0014] In the above method, in the process of the first device sending the first file to the second device, some file blocks may be lost. In this way, the first device can send the file blocks in the first file that are missing from the second device to the second device multiple times, thereby ensuring the integrity of the first file.

[0015] In a possible implementation, the first device is a large-screen device, and the second device is a terminal device.

[0016] In a second aspect, an embodiment of the present application provides a recording method, which is applied to a second device, and the method includes: receiving a first operation; sending a first message to the first device according to the first operation; receiving a status of the first device sent by the first device, the status of the first device being obtained by the first device according to the first message; when the status of the first device meets a first preset condition, sending a first instruction to the first device, the first instruction being used by the first device to record a first interface displayed by the first device and generate a first file, the first interface being used to play a first multimedia; receiving the first file sent by the first device.

[0017] In a possible implementation, the method also includes: displaying a second interface, where the second interface is an operation interface of the first device, and when the second device displays the second interface, the first interface displayed by the first device is used to play the first multimedia; receiving the first operation includes: receiving the first operation acting on the recording control in the second interface; in response to the first operation, displaying a prompt message on the second interface, and the prompt message is used to prompt the first device to start recording the first multimedia.

[0018] In a possible implementation, after displaying the prompt information on the second interface, the method further includes: displaying a third interface, the third interface including progress information indicating a progress of the second device receiving the first file.

[0019] In a possible implementation, the first device is a large-screen device, and the second device is a terminal device.

[0020] In a third aspect, the present application provides an electronic device, including a transceiver, a processor and a memory, wherein the memory is used to store a computer program, and the processor calls the computer program to execute a recording method in any possible implementation of the first aspect or the second aspect.

[0021] In a fourth aspect, the present application provides an electronic device, comprising one or more processors and one or more memories. The one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer program codes, and the computer program codes include computer instructions, and when the one or more processors execute the computer instructions, the electronic device executes the recording method in any possible implementation of the first aspect or the second aspect.

[0022] In a fifth aspect, the present application provides a computer storage medium storing a computer program, which, when executed by a processor, implements the recording method in any possible implementation of any of the above aspects.

[0023] In a sixth aspect, the present application provides a computer program product. When the computer program product runs on an electronic device, the electronic device executes the recording method in any possible implementation of the first aspect or the second aspect.

[0024] In a seventh aspect, the present application provides an electronic device, the electronic device comprising a method or device for executing any implementation of the first aspect or the second aspect of the present application. The electronic device is, for example, a chip.

[0025] It should be understood that the description of technical features, technical solutions, beneficial effects or similar language in this application does not imply that all features and advantages can be realized in any single embodiment. On the contrary, it is understood that the description of features or beneficial effects means that specific technical features, technical solutions or beneficial effects are included in at least one embodiment. Therefore, the description of technical features, technical solutions or beneficial effects in this specification does not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions and beneficial effects described in this embodiment can also be combined in any appropriate manner. Those skilled in the art will understand that the embodiment can be implemented without one or more specific technical features, technical solutions or beneficial effects of a specific embodiment. In other embodiments, additional technical features and beneficial effects can also be identified in a specific embodiment that does not embody all embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0027] Figure 1A is a schematic diagram of the architecture of a recording system 10 provided by the present application;

[0028] Figure 1B is an interactive schematic diagram of a recording system 10 provided by the present application;

[0029] Figure 2 is a hardware structure diagram of an electronic device 100 provided in this application;

[0030] Figure 3 is a schematic diagram of a software architecture of an electronic device 100 provided in this application;

[0031] Figure 4-Figure 7 is a schematic diagram of some user interfaces provided by this application;

[0032] Figure 8 It is a flowchart of a recording method provided by this application;

[0033] Fig. 9 It is a flowchart of another recording method provided by the present application;

[0034] Fig.10 It is a flowchart of another recording method provided by the present application;

[0035] Fig.11 It is a flowchart of another recording method provided by this application. DETAILED DESCRIPTION

[0036] The technical solution in the embodiment of the present application will be described below in conjunction with the accompanying drawings. In the description of the embodiment of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in the text is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiment of the present application, "multiple" means two or more than two.

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

[0038] When users use large-screen devices to watch multimedia, they hope to record the highlights in the multimedia (such as the clips of goals in football games) to store or share them with other devices. At present, users can operate the remote control to start the recording function of the large-screen device to record the above-mentioned highlights. The recording process may include: the large-screen device can receive the user operation sent by the remote control (such as the operation of the recording control in the interface of the control center), and determine to start the recording function to record multimedia data according to the user operation. After the recording is completed, the large-screen device can search for surrounding devices that can be shared, and display the identifiers of multiple devices searched on the interface. The user needs to find the identifier of the device to be shared from these multiple identifiers and select it to transfer the recorded multimedia file to the device to be shared. This method requires the user to manually select the device to be shared after the recording is completed, which costs the user's time cost, the efficiency of multimedia file sharing is low, the function availability is low, and the user experience is affected. In addition, the identifier of the device is usually represented by characters (such as letters), and it is difficult for the user to match the device represented by the character with the device to be shared. In other words, the readability of the character is poor, which further affects the user experience.

[0039] In addition, when a large-screen device is recording multimedia data, due to the limited processing capabilities of the chip of the large-screen device, for example, the chip only supports single-channel decoding, the large-screen device cannot merge the processing of other functions, such as mirroring the display interface of the large-screen device on the terminal device used by the user, and controlling the large-screen device by operating the terminal device (which can be called mirror control). When the large-screen device is performing mirror control processing, if the user wants to record multimedia data, since the mirror control processing and the multimedia recording processing will conflict, problems such as failure to record multimedia data and interruption of mirror control will occur, affecting the user experience.

[0040] An embodiment of the present application provides a recording method, which is applied to a recording system. The recording system may include an electronic device 100 and an electronic device 200. The electronic device 100 can be used as a master device to control the electronic device 200 (which may be referred to as a controlled device) in real time to record multimedia data. After the recording is completed, the controlled device can directly return the recorded multimedia file to the master device. In this way, the user does not need to perform the above-mentioned recording process again, and can directly select the master device in the recording scene and perform an operation on the master device to realize the recording and sharing process of the multimedia file (which may be referred to as the recording and sharing process for short), thereby reducing user operation and time costs, thereby improving the efficiency of multimedia file sharing in the recording scene and improving the user experience.

[0041] In addition, before recording multimedia data, the method can first detect the working status of the controlled device. When the working status of the controlled device meets the first preset condition (for example, the mirror control function is not used), the multimedia data recording is started. Otherwise, the multimedia data is not recorded, thereby avoiding problems such as abnormalities in the multimedia data recording process and interruption of the processing of other ongoing functions, thereby further improving the user experience.

[0042] A recording system 10 involved in an embodiment of the present application is introduced below.

[0043] Figure 1A A schematic diagram of the architecture of a recording system 10 is exemplarily shown.

[0044] like Figure 1A As shown, the recording system 10 may include an electronic device 100 and an electronic device 200. The electronic device 100 may communicate with the electronic device 200 via wired (e.g., universal serial bus (USB), twisted pair, coaxial cable, optical fiber, etc.) and / or wireless (e.g., wireless local area networks (WLAN), peer to peer (P2P) direct connection, wireless fidelity (Wi-Fi), Bluetooth, cellular communication network, etc.).

[0045] The electronic device 100 may be a mobile phone, a tablet computer, a handheld computer, a desktop computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), and smart home devices such as smart TVs and projectors, wearable devices such as smart bracelets, smart watches, and smart glasses, and extended reality (XR) devices such as augmented reality (AR), virtual reality (VR), and mixed reality (MR) or vehicle-mounted devices. The description of the electronic device 200 is consistent with the description of the electronic device 100. The embodiment of the present application does not impose any special restrictions on the specific type of the electronic device. The embodiment of the present application is described by taking the electronic device 100 as a terminal device such as a mobile phone and the electronic device 200 as a large-screen device such as a smart TV and a projector as an example.

[0046] In one embodiment, the electronic device 100 can act as a master device to implement a multimedia file recording and sharing process (referred to as a recording and sharing process) with the electronic device 200 as a controlled device. In the recording and sharing process, the electronic device 100 can receive a user operation 1, and in response to the user operation 1, send a first message to the electronic device 200, and the first message may include a recording instruction. When the state of the electronic device 200 meets the first preset condition (for example, when other functions that conflict with the recording function are not used), the electronic device 200 can record the played multimedia data according to the recording instruction, generate a multimedia file, and return the multimedia file to the electronic device 100.

[0047] In one embodiment, during the process of recording multimedia data, the electronic device 100 may receive a user operation 2, and in response to the user operation 2, send an end instruction to the electronic device 200, and the electronic device 200 may stop recording the played multimedia data according to the end instruction. In another embodiment, when the duration of the multimedia data recorded and played by the electronic device 200 (which may be referred to as the recording duration) is greater than or equal to a preset duration, the electronic device 200 may stop recording the played multimedia data.

[0048] Understandably, Figure 1A The number and form of the electronic devices shown are only examples. In a specific implementation, the number may be more or less. For example, the recording system 10 may also include other electronic devices, which is not limited in this application.

[0049] Figure 1B An interactive schematic diagram of a recording system 10 is exemplarily shown.

[0050] like Figure 1B As shown, the electronic device 100 in the recording system 10 may include a user interface (UI) module 101, a recording status module 102, and a WebSocket communication module 103. The electronic device 200 in the recording system 10 may include a CmdServer module 201, a first application module 202, a second application module 203, and a recording module 204 (including a video recording module 2041 and an audio recording module 2042). Among them:

[0051] The UI module 101 can be used to receive instructions input by the user, such as receiving a request for starting recording, and for example, receiving a request for ending recording. It can also be used to output the received information, such as displaying the received information on a display screen. The UI module can send the acquired instruction for starting recording (such as a recording instruction) to the recording status module 102, and the recording status module 102 can send a status detection message to the CmdServer module 201 of the electronic device 200 through the WebSocket communication module 103. The CmdServer module 201 can send a request message 1 to the first application module 202 and the second application module 203 respectively. After receiving the request message 1, the first application module 202 can send the status of the function corresponding to the first application (which can be referred to as the first function) to the CmdServer module 201. After receiving the request message, the second application module 203 can send the status of the function corresponding to the second application (which can be referred to as the second function) to the CmdServer module 201. Optionally, the first function can be a recording function, and the second function can be other functions that conflict with the recording function, such as a mirror control function. The CmdServer module 201 can send a status message to the recording status module 102 through the WebSocket communication module 103, and the status message can include the status of the above-mentioned first function and the status of the above-mentioned second function. When the status of the electronic device 200 indicated by the status message meets the first preset condition (for example, when the second function is not used), the recording status module 102 can send a recording start message to the CmdServer module 201 through the WebSocket communication module 103, and the CmdServer module 201 can send a recording instruction to the first application module 202, and the first application module 202 can send the recording instruction to the recording module 204, so that the recording module 204 records the played multimedia data. In the process of recording multimedia data, the first application module 202 can send request information 2 to the video recording module 2041 and the audio recording module 2042 in the recording module 204 respectively to obtain the video data returned by the video recording module 2041 and the audio data returned by the audio recording module 2042. When the recording of multimedia data is completed, the first application module 202 can generate a multimedia file based on the above-mentioned video data and the above-mentioned audio data, and send the multimedia file to the WebSocket communication module 103 through the CmdServer module 201. The WebSocket communication module 103 can send the multimedia file to the recording status module 102. The recording status module 102 can send a prompt message to the UI module, and the prompt message indicates that the multimedia file has been successfully received. The UI module can output the multimedia file, for example, by displaying a gallery interface on a display screen, and the gallery interface can be used to play the multimedia file.

[0052] Understandably, Figure 1B The recording system 10 shown may include more or fewer modules. Any module in the recording system 10 may be a hardware module or a software module. Any of the above modules may be a separate module, and at least one of the above modules may also be integrated together. This application does not limit this.

[0053] Next, an exemplary electronic device 100 according to an embodiment of the present application is introduced.

[0054] Figure 2 A schematic diagram of the hardware structure of an electronic device 100 is exemplarily shown.

[0055] It should be understood that Figure 2 The electronic device 100 shown is only an example, and the electronic device 100 may have more Figure 2 More or fewer components may be shown, two or more components may be combined, or there may be a different configuration of components. Figure 2 The various components shown in the drawings may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0056] like Figure 2 As shown, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, 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 speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0057] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or separate some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

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

[0059] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

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

[0061] In one embodiment, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0062] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In one embodiment, the processor 110 may include multiple groups of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through the I2C interface, so that the processor 110 communicates with the touch sensor 180K through the I2C bus interface to realize the touch function of the electronic device 100.

[0063] The I2S interface can be used for audio communication. In one embodiment, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to achieve communication between the processor 110 and the audio module 170. In one embodiment, the audio module 170 can transmit an audio signal to the wireless communication module 160 via the I2S interface to achieve the function of answering a call through a Bluetooth headset.

[0064] The PCM interface can also be used for audio communication, sampling, quantizing and encoding analog signals. In one embodiment, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In one embodiment, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface to implement the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0065] The UART interface is a universal serial data bus for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In one embodiment, the UART interface is generally used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In one embodiment, the audio module 170 can transmit an audio signal to the wireless communication module 160 through the UART interface to implement the function of playing music through a Bluetooth headset.

[0066] The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In one embodiment, the processor 110 and the camera 193 communicate via the CSI interface to realize the shooting function of the electronic device 100. The processor 110 and the display screen 194 communicate via the DSI interface to realize the display function of the electronic device 100.

[0067] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In one embodiment, the GPIO interface can be used to connect the processor 110 with the camera 193, the display screen 194, the wireless communication module 160, the audio module 170, the sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0068] The USB interface 130 is an interface that complies with the USB standard specification, and specifically can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and a peripheral device. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other electronic devices, such as AR devices, etc.

[0069] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present invention is only a schematic illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0070] The charging management module 140 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 may receive charging input from a wired charger through the USB interface 130. In some wireless charging embodiments, the charging management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. While the charging management module 140 is charging the battery 142, it may also power the electronic device through the power management module 141.

[0071] 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, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0072] The wireless communication function of the electronic device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0073] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0074] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In one embodiment, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In one embodiment, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0075] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 170A, a receiver 170B, etc.), or displays an image or video through a display screen 194. In one embodiment, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0076] The wireless communication module 160 can provide wireless communication solutions 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), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0077] In one embodiment, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with the network and other devices through wireless communication technology. 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 technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0078] The electronic device 100 implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

[0079] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In one embodiment, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

[0080] The electronic device 100 can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0081] ISP is used to process the data fed back by camera 193. For example, when taking a photo, the shutter is opened, and the light is transmitted to the camera photosensitive element through the lens. The light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to ISP for processing and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on the noise, brightness, and color of the image. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In one embodiment, ISP can be set in camera 193.

[0082] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In one embodiment, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0083] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0084] Video codecs are used to compress or decompress digital videos. The electronic device 100 may support one or more video codecs. Thus, the electronic device 100 may play or record videos in a variety of coding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0085] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of electronic device 100 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

[0086] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.

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

[0088] The electronic device 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0089] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In one embodiment, the audio module 170 can be arranged in the processor 110, or some functional modules of the audio module 170 can be arranged in the processor 110.

[0090] The speaker 170A, also called a "speaker", is used to convert an audio electrical signal into a sound signal. The electronic device 100 can listen to music or listen to a hands-free call through the speaker 170A.

[0091] The receiver 170B, also called a "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or voice message, the voice can be received by placing the receiver 170B close to the human ear.

[0092] Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to microphone 170C to input the sound signal into microphone 170C. The electronic device 100 can be provided with at least one microphone 170C. In other embodiments, the electronic device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the sound source, realize directional recording function, etc.

[0093] The earphone interface 170D is used to connect a wired earphone and can be a USB interface 130 or a 3.5 mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0094] The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In one embodiment, the pressure sensor 180A can be set on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The electronic device 100 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 194, the electronic device 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 can also calculate the touch position according to the detection signal of the pressure sensor 180A. In one embodiment, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

[0095] The gyro sensor 180B can be used to determine the motion posture of the electronic device 100. In one embodiment, the angular velocity of the electronic device 100 around three axes (i.e., x, y, and z axes) can be determined by the gyro sensor 180B. The gyro sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyro sensor 180B detects the angle of the electronic device 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking of the electronic device 100 through reverse movement to achieve anti-shake. The gyro sensor 180B can also be used for navigation and somatosensory game scenes.

[0096] The air pressure sensor 180C is used to measure air pressure. In one embodiment, the electronic device 100 calculates the altitude through the air pressure value measured by the air pressure sensor 180C to assist positioning and navigation.

[0097] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip leather case. In one embodiment, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover according to the magnetic sensor 180D. Then, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, the flip cover automatic unlocking and other features are set.

[0098] The acceleration sensor 180E can detect the magnitude of the acceleration of the electronic device 100 in all directions (generally three axes). When the electronic device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device and is applied to applications such as horizontal and vertical screen switching and pedometers.

[0099] The distance sensor 180F is used to measure the distance. The electronic device 100 can measure the distance by infrared or laser. In one embodiment, when shooting a scene, the electronic device 100 can use the distance sensor 180F to measure the distance to achieve fast focusing.

[0100] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 uses a photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 can use the proximity light sensor 180G to detect that the user holds the electronic device 100 close to the ear to talk, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode and pocket mode to automatically unlock and lock the screen.

[0101] The ambient light sensor 180L is used to sense the ambient light brightness. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.

[0102] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0103] The temperature sensor 180J is used to detect temperature. In one embodiment, the electronic device 100 uses the temperature detected by the temperature sensor 180J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 180J exceeds a threshold, the electronic device 100 reduces the performance of a processor located near the temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 heats the battery 142 to avoid abnormal shutdown of the electronic device 100 due to low temperature. In other embodiments, when the temperature is lower than another threshold, the electronic device 100 boosts the output voltage of the battery 142 to avoid abnormal shutdown due to low temperature.

[0104] The touch sensor 180K is also called a "touch control device". The touch sensor 180K can be set on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch control screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the electronic device 100, which is different from the position of the display screen 194.

[0105] The bone conduction sensor 180M can obtain vibration signals. In one embodiment, the bone conduction sensor 180M can obtain vibration signals of the vibrating bones of the vocal part of the human body. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure pulse signals. In one embodiment, the bone conduction sensor 180M can also be set in headphones to form bone conduction headphones. The audio module 170 can parse out voice signals based on the vibration signals of the vibrating bones of the vocal part obtained by the bone conduction sensor 180M to realize the voice function. The application processor can parse the heart rate information based on the blood pressure pulse signal obtained by the bone conduction sensor 180M to realize the heart rate detection function.

[0106] The key 190 includes a power key, a volume key, etc. The key 190 may be a mechanical key or a touch key. The electronic device 100 may receive key input and generate key signal input related to user settings and function control of the electronic device 100.

[0107] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0108] Indicator 192 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0109] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and separated from the electronic device 100 by inserting it into the SIM card interface 195 or pulling it out from the SIM card interface 195. The electronic device 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In one embodiment, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0110] The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. For example, the software system of the layered architecture may be an Android system, or a Harmony operating system (OS), or other software systems. The embodiment of the present application takes the Android system of the layered architecture as an example to exemplify the software structure of the electronic device 100.

[0111] Figure 3 A schematic diagram of the software architecture of an electronic device 100 is exemplarily shown.

[0112] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In one embodiment, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.

[0113] The application layer can include a series of application packages.

[0114] like Figure 3 As shown, the application layer may include applications such as camera, gallery, music, calendar, short message, call, navigation, Bluetooth, browser, and screen projection.

[0115] like Figure 3 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and the like.

[0116] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0117] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0118] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

[0119] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including connecting, hanging up, etc.).

[0120] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0121] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0122] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

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

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

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

[0126] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

[0127] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0128] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0129] A 2D graphics engine is a drawing engine for 2D drawings.

[0130] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

[0131] The following is an illustrative description of the workflow of the software and hardware of the electronic device 100 in conjunction with the recording scenario.

[0132] When the touch sensor 180K receives a touch operation, the corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into an original input event (including touch coordinates, timestamp of the touch operation, and other information). The original input event is stored in the kernel layer. The application framework layer obtains the original input event from the kernel layer and identifies the control corresponding to the input event. For example, if the touch operation is a touch single-click operation and the control corresponding to the single-click operation is a control for starting the recording function, the first application calls the interface of the application framework layer to start the recording function, and then controls the display driver by calling the kernel layer to display the user interface for recording multimedia data through the display screen 194.

[0133] Description of electronic device 200 and Figure 2 and Figure 3 The description of the electronic device 100 is similar and will not be repeated here.

[0134] The following describes an application scenario involved in an embodiment of the present application and a user interface diagram in the scenario.

[0135] Figure 4 A schematic diagram of a user interface for recording multimedia data is exemplarily shown.

[0136] like Figure 4As shown in (A), the electronic device 100 can display a user interface 110 (including the title "Master Bedroom Smart Screen"). The user interface 110 can be a control interface of the electronic device 200, such as a remote control interface. The user interface 110 can include a control 111 (including the character "OK"), and the control 111 can be used to turn on or off the recording function of the electronic device 200. The electronic device 200 can display Figure 4 The user interface 210 shown in (B) is, for example, an interface for the electronic device 200 to play multimedia data.

[0137] In one embodiment, the electronic device 100 may send a recording instruction to the electronic device 200 in response to a user operation on the control 111 (for example, the user operation is a touch operation). After receiving the recording instruction, the electronic device 200 may start recording the currently playing multimedia data. At this time, the electronic device 100 may display Figure 5 The user interface 120 shown in (A) of the electronic device 200 may display Figure 5 The user interface 220 shown in (B).

[0138] like Figure 5 As shown in (A), the user interface 120 and Figure 4 The user interface 120 is similar to the user interface 110 shown in (A), except that the user interface 120 may include prompt information 121, and the prompt information 121 includes the characters "start recording" for prompting the user that the recording function is currently turned on.

[0139] like Figure 5 As shown in (B), the user interface 220 and Figure 4 The user interface 220 is similar to the user interface 210 shown in (B), except that the user interface 220 may include a control 221, and the control 221 includes the characters "recording" for prompting the user that the multimedia data played by the user interface 220 is currently being recorded.

[0140] In one embodiment, Figure 5 After the embodiment shown, the electronic device 100 may respond to the Figure 5 The user operation (for example, the user operation is a touch operation) of the control 111 in the user interface 120 shown in (A) sends an end instruction to the electronic device 200. After receiving the end instruction, the electronic device 200 can stop recording and playing the multimedia data and generate a multimedia file. At this time, the electronic device 200 can display Figure 6 User interface 230 is shown.

[0141] like Figure 6 As shown, the user interface 230 is Figure 5The user interface 220 shown in (B) is similar to the user interface 220 shown in (B), except that the user interface 220 does not include the control 221, which can indicate that the recording of multimedia data has ended. The user interface 220 can include an icon 231, a control 232, and a control 233. The icon 231 can indicate a recorded multimedia file. The icon 231 includes the characters "The video has been saved to the gallery" and the characters "03:00", wherein the characters "The video has been saved to the gallery" can indicate that the multimedia file is saved in the gallery of the electronic device 200, and the characters "03:00" can indicate the duration of the multimedia file. The control 232 includes the characters "Cancel", which can be used to cancel the display of the icon 231. The control 233 includes the characters "Share", which can be used to enable the sharing function of the electronic device 200 to share the multimedia file with the electronic device 100.

[0142] In one embodiment, the electronic device 200 may send the generated multimedia file to the electronic device 100 in response to a user operation on the control 233 (for example, the user operation is a touch operation). At this time, the electronic device 100 may display the generated multimedia file. Figure 7 The user interface 130 shown in (A) of FIG. The user interface 130 may be Figure 4 The user interface 110 shown in (A) is similar to the user interface 110 shown in (A), except that the control 131 in the user interface 130 does not include the character "OK", but includes a progress ring 1311, which can represent the progress of the electronic device 100 receiving the multimedia file.

[0143] In one embodiment, after the electronic device 100 successfully receives the multimedia file (for example, when the progress ring 1311 indicates that the progress of receiving the multimedia file is 100%), the electronic device 100 may display information about the multimedia file, for example, display Figure 7 The user interface 140 is shown in (B).

[0144] like Figure 7 As shown in (B), the user interface 140 is an interface of a gallery, the user interface 140 may include a multimedia file 141 , and the user interface 140 may be used to play the multimedia file 141 .

[0145] Not limited to the above example where the electronic device 100 sends an end instruction to the electronic device 200 after receiving a user operation, in another embodiment, when the recording time of the electronic device 200 is greater than or equal to a preset time, the electronic device 200 can stop recording and playing multimedia data and generate a multimedia file.

[0146] Next, the recording method provided by the embodiment of the present application is introduced.

[0147] See also Figure 8 , Figure 8is a flowchart of a recording method provided in an embodiment of the present application. The method can be applied to Figure 1A The recording system 10 shown. The method may include but is not limited to the following steps:

[0148] S101: The UI module receives a first operation.

[0149] In one embodiment, the first operation may include, but is not limited to, a touch operation, voice input, brain waves, etc. In some examples, the UI module may receive a first operation for a control for turning on a recording function, wherein the control for turning on a recording function is, for example, Figure 4 Control 111 in user interface 110 shown in (A).

[0150] S102: The UI module sends instruction 1 to the recording status module.

[0151] In one embodiment, instruction 1 may be a recording instruction for opening / starting the recording function in the recording and sharing process. In one embodiment, after receiving the first operation, the UI module may send instruction 1 to the recording state module in response to the first operation.

[0152] In one embodiment, after receiving instruction 1, the recording status module can start a recording detection task, and the recording detection task can create a subtask. The subtask can be used to establish a communication connection (such as a WebSocke connection) between the electronic device 100 and the electronic device 200. The subtask can be represented as new HighlightTask(ip).

[0153] In one implementation, the recording status module executes a subtask before executing the recording detection task, that is, executes the following S103-S105.

[0154] S103: The recording status module sends the information of the electronic device 200 to the WebSocket communication module.

[0155] In one implementation, the information of the electronic device 200 may include, but is not limited to, an Internet Protocol (IP) address of the electronic device 200 .

[0156] S104: The WebSocket communication module and the CmdServer module establish a WebSocket connection.

[0157] In one implementation, after the WebSocketClient in the WebSocket communication module receives the information of the electronic device 200 , it can establish a WebSocket connection with the electronic device 200 according to the IP address of the electronic device 200 .

[0158] In some examples, the WebSocketClient can send a request message to the WebSocketServer in the CmdServer module based on the IP address of the electronic device 200. The request message can be used to request to establish a connection with the electronic device 200. After receiving the request message, the WebSocketServer can establish a connection with the electronic device 100 and return a result message to the WebSocketClient. The result message can indicate that the connection is successfully established.

[0159] S105: The WebSocket communication module sends message 1 to the recording status module.

[0160] In one implementation, message 1 may indicate that the WebSocket communication module and the CmdServer module have successfully established a WebSocket connection, that is, the electronic device 100 and the electronic device 200 have successfully established a communication connection.

[0161] In one implementation, when WebSocketClient completes executing the subtask, it can jump to the recording detection task through the onConnect(intstatus) function and execute the recording detection task.

[0162] S106: The recording status module sends message 2 to the WebSocket communication module.

[0163] In one embodiment, message 2 can be used to request the status of the electronic device 200. The status of the electronic device 200 may include, but is not limited to, the status of a first function and the status of a second function. The first function may be a recording function, and the second function may be other functions that conflict with the recording function (i.e., the first function), such as a mirror control function.

[0164] S107: The WebSocket communication module sends message 3 to the CmdServer module.

[0165] In one implementation, message 3 may be a status detection message. After receiving message 2, the WebSocketClient in the WebSocket communication module may send a status detection message to the WebSocketServer module in the CmdServer.

[0166] In some examples, the format of the status detection message can be characterized as follows:

[0167] {

[0168] "taskId":"5C0E***FE6FA",

[0169] "acticon":"checkHighlightStatus"

[0170] }

[0171] Among them, "acticon":"checkHighlightStatus" can indicate that the recording status module is currently performing the recording detection task.

[0172] S108: The CmdServer module sends message 4 to the first application module.

[0173] In one embodiment, message 4 can be used to request the status of the first function. In some examples, when the WebSocketServer in the CmdServer module receives message 3, process communication (e.g., represented by RecordManager) can be established between services (e.g., Android services) through the first application module.

[0174] S109: The first application module sends message 5 to the CmdServer module.

[0175] In one implementation, the message 5 may include the state of the first function. In some examples, the first application module may obtain the state of the first function through the getSwitchState() function in the RecordManager.

[0176] In one implementation, the state of the first function may be that the first function is enabled, or that the first function is not enabled.

[0177] S110: The CmdServer module sends a message 6 to the second application module.

[0178] In one implementation, message 6 may be used to request the status of the second function. In some examples, when WebSocketServer receives message 3, it may establish a cross-process communication mechanism (eg, represented as PlayerClient) with the second application module.

[0179] S111: The second application module sends message 7 to the CmdServer module.

[0180] In one implementation, message 7 may include the state of the second function. In some examples, the second application module may obtain the state of the second function through the getSwitchState() function in PlayerClient.

[0181] In one implementation, the status of the second function may be that the second function is being used, or that the second function is not being used.

[0182] S112: The CmdServer module sends message 8 to the WebSocket communication module.

[0183] In one implementation, the message 8 may be a status message, and the message 8 may include the status of the first function and the status of the second function.

[0184] In some examples, the format of the status message can be characterized as follows:

[0185] {

[0186] "taskId":"5C0E***FE6FA",

[0187] "acticonCode":"**"

[0188] }

[0189] Among them, "acticonCode":"**" can represent the status of the first function and the status of the second function. For example, a acticonCode of 101 can represent that the first function is turned on and the second function is not in use; a acticonCode of 102 can represent that the first function is not turned on and the second function is not in use; a acticonCode of 103 can represent that the second function is in use.

[0190] S113: The WebSocket communication module sends message 8 to the recording status module.

[0191] S114 : The recording status module may determine the status of the electronic device 200 according to the message 8 .

[0192] In one implementation, the recording status module may parse the message 8 to determine the status of the first function and the status of the second function in the electronic device 200 .

[0193] In one implementation, the recording status module may determine whether to enable the first function of the electronic device 200 according to the status of the electronic device 200 .

[0194] S115: The UI module displays prompt information 1.

[0195] In one embodiment, when the first function is turned on and the second function is not used, the prompt information 1 can be used to prompt the user that the recording function has been turned on and the recording has started, for example, displaying Figure 5The prompt information 121 in the user interface 120 shown in (A), wherein the first function is a recording function; when the first function is not turned on and the second function is not in use, the prompt information 1 can be used to prompt the user to manually turn on the recording function; when the second function is in use, the prompt information 1 can be used to prompt the user that the second function is currently in use and recording cannot be performed.

[0196] exist Figure 8 In the method shown, before recording multimedia data, the electronic device 100 as the main control device can first detect the status of the controlled device (electronic device 200), and determine whether to enable the function of recording multimedia data of the electronic device 200 according to the status, so as to avoid the problem of failure in recording multimedia data or interruption of other ongoing function processing, thereby improving the user experience.

[0197] See also Fig. 9 , Fig. 9 is a flowchart of another recording method provided in an embodiment of the present application. This method can be applied to Figure 1A The recording system 10 shown. The method may include but is not limited to the following steps:

[0198] S201: The UI module receives a second operation.

[0199] In one implementation, S201 is an optional step.

[0200] In one implementation, before S201, the following steps may also be included: Figure 8 S101-S115.

[0201] In one implementation, when the prompt information 1 displayed by the UI module is used to prompt the user to manually start the recording function, the UI module may receive a second operation on a control for starting the first function (eg, the recording function).

[0202] S202: The UI module sends instruction 2 to the recording status module.

[0203] In one implementation, S202 is an optional step.

[0204] In one implementation, instruction 2 may be a start instruction for starting to record multimedia data. In one implementation, after receiving the second operation, the UI module may send instruction 2 to the recording state module in response to the second operation.

[0205] S203: The recording status module sends instruction 3 to the WebSocket communication module.

[0206] In one implementation, when the recording status module determines that the status of the electronic device 200 satisfies a first preset condition (for example, when the second function is not used), a recording task may be started, and the recording task may be characterized as a HighlightRecordTask.

[0207] In one implementation, instruction 3 may be a recording instruction. After the recording status module starts the recording task, instruction 3 may be sent to the WebSocketClient in the WebSocket communication module.

[0208] S204: The WebSocket communication module sends message 9 to the CmdServer module.

[0209] In one implementation, message 9 may be a recording start message. In some examples, the format of the recording start message may be characterized as follows:

[0210] {

[0211] "taskId":"5C0E***FE6FA",

[0212] "acticon":"startHighlightRecord"

[0213] }

[0214] Among them, "acticon":"startHighlightRecord" can indicate that the recording status module is currently executing the recording task.

[0215] S205: The CmdServer module sends instruction 4 to the first application module.

[0216] In one embodiment, instruction 4 may be a recording instruction. In some examples, when the WebSocketServer in the CmdServer module receives message 9, the recording task may be started through the doRecord(true, callback) function in the RecordManager, where true may be used to determine whether to return information, and callback may be used to return data (e.g., recorded multimedia data) and information (e.g., recording status).

[0217] S206: The first application module sends a message 10 to the recording module.

[0218] In one implementation, when the first application module receives instruction 4, it may start a recording task to start recording the played multimedia data.

[0219] In one embodiment, message 10 may be used to request to obtain recorded multimedia data, which may include video data and audio data. In some examples, the first application module may obtain video data from a video recording module in a recording module through the acquireCastStream() function in MtkCast, and the first application module may obtain audio data from an audio recording module in a recording module through the acquireAudioCastStream() function in MtkCast.

[0220] In one embodiment, when the first application module starts the recording task to start recording the multimedia data to be played, timer 1 can be started synchronously. Timer 1 can be used to detect whether the recording time is greater than or equal to a preset time (for example, 5 minutes), and can also be used to periodically obtain multimedia data, that is, periodically execute S206-S207, for example, start timer 1 every 30 milliseconds, and obtain the multimedia data recorded within this 30 milliseconds when it is started.

[0221] Optionally, when the first application module starts the recording task, result information may be sent to the WebSocket communication module through the CmdServer module, where the result information indicates that the recording has been started.

[0222] S207: The recording module sends a message 11 to the first application module.

[0223] In one embodiment, message 11 may include recorded multimedia data. In some examples, the first application module may write video data (e.g., represented by VencStreamInf) and audio data (e.g., represented by AudioEncoderStreamInfo) into the cache respectively through the writeSampleData() function of MediaMuxer in the Android Framework.

[0224] In one implementation, when the first application module uses MediaMuxer for the first time, it needs to create newMediaMuxer and determine the storage path and format (eg, MP4 format) of the multimedia file (hereinafter referred to as the first file) generated by recording.

[0225] The order of S206-S207 and S208-S211 is not limited.

[0226] S208: The recording status module sends a message 12 to the WebSocket communication module.

[0227] In one implementation, the message 12 may be used to request the recording status of the electronic device 200 .

[0228] In one embodiment, when the recording status module starts the recording task, that is, when executing S203, the recording status module can synchronously start timer 2, which can be used to periodically obtain the recording status of the electronic device 200, that is, periodically execute S208-S211, for example, start timer 2 every 1 second, and obtain the recording status of the current electronic device 200 when it is started.

[0229] S209: The WebSocket communication module sends message 13 to the CmdServer module.

[0230] In one implementation, message 13 may be a recording status request message. After receiving message 12, the WebSocketClient in the WebSocket communication module may send a recording status message to the WebSocketServer module in the CmdServer.

[0231] In some examples, the format of the recording status request message can be characterized as follows:

[0232] {

[0233] "taskId":"5C0E***FE6FA",

[0234] "acticon":"checkHighlightRecordStatus"

[0235] }

[0236] Among them, "acticon":"checkHighlightRecordStatus" can indicate that the recording status module is currently performing the recording detection task.

[0237] S210: The CmdServer module sends message 14 to the WebSocket communication module.

[0238] In one embodiment, message 14 may be a recording status message, and message 14 may include the recording status of the electronic device 200. The recording status of the electronic device 200 may include, but is not limited to, any one of recording, recording successful, and recording timeout, wherein the recording timeout may be a recording duration greater than a preset duration.

[0239] In some examples, the format of the recording status message can be characterized as follows:

[0240] {

[0241] "taskId":"5C0E***FE6FA",

[0242] "acticonCode":"**"

[0243] }

[0244] Among them, "acticonCode":"**" can represent the recording status of the electronic device 200. For example, an acticonCode of 100 can represent a successful recording; an acticonCode of 105 can represent a recording in progress; and an acticonCode of 106 can represent a recording timeout.

[0245] S211: The WebSocket communication module sends message 14 to the recording status module.

[0246] The order of S208-S211 and S204-S207 is not limited.

[0247] S212: The UI module receives a third operation.

[0248] In one implementation, S212 is an optional step.

[0249] In one implementation, the third operation may include, but is not limited to, a touch operation, voice input, brain waves, etc. In some examples, the UI module may receive a third operation for a control for turning off a recording function.

[0250] S213: The UI module sends instruction 5 to the recording status module.

[0251] In one implementation, S213 is an optional step.

[0252] In one implementation, instruction 5 may be an end instruction for stopping recording multimedia data. In one implementation, after receiving the third operation, the UI module may send instruction 5 to the recording state module in response to the third operation.

[0253] In some examples, after receiving instruction 5, the recording status module can stop recording multimedia data by calling the stop() function of the recording HighlightRecordTask.

[0254] S214: The recording status module sends instruction 5 to the WebSocket communication module.

[0255] In one implementation, S214 is an optional step.

[0256] S215: The WebSocket communication module sends message 15 to the CmdServer module.

[0257] In one implementation, S215 is an optional step.

[0258] In one implementation, the message 15 may be an end message. In some examples, the format of the end message may be characterized as follows:

[0259] {

[0260] "taskId":"5C0E***FE6FA",

[0261] "acticon":"stopHighlightRecord"

[0262] }

[0263] Among them, "acticon":"stopHighlightRecord" can indicate stopping / ending the currently executing recording task.

[0264] S216: The CmdServer module sends instruction 6 to the first application module.

[0265] In one implementation, S216 is an optional step.

[0266] In one implementation, instruction 6 may be an end instruction. In some examples, when the CmdServer module receives the end message, the recording task may be ended through the stopRecord() function of the RecordManager.

[0267] S217: The first application module generates a first file.

[0268] In one implementation, after receiving the end instruction, the first application module may end the recording task and generate a multimedia file (i.e., the first file) based on the acquired multimedia data (e.g., the multimedia data periodically acquired in S207 above). In some examples, the first application module may stop recording the multimedia data through the stop() function of MediaMuxer.

[0269] Without limitation thereto, in another embodiment, the first application module may detect whether the recording duration is greater than or equal to a preset duration through timer 1. When the recording duration is equal to the preset duration, the first application module may end the recording task and generate a first file.

[0270] S218: The first application module sends a message 16 to the CmdServer module.

[0271] In one embodiment, the message 16 may include information about the first file, such as but not limited to the name of the first file. In some examples, after the first application module generates the first file, it may send the information about the first file to the CmdServer module, and the CmdServer module may store the information about the first file.

[0272] In one embodiment, after S218, when the CmdServer module receives the recording status request message sent by the WebSocket communication module, that is, when S209 is periodically executed, the CmdServer module can return the current recording status of the electronic device 200 (that is, recording is successful) and the information of the first file to the recording status module through the WebSocket communication module. It can be understood that when S208-S211 is periodically executed, if S218 is executed, the message in this execution of S210-S211 can also include the information of the first file. In some examples, the format of the recording status message returned to the recording status module at this time can be characterized as:

[0273] {

[0274] "taskId":"5C0E***FE6FA",

[0275] "acticonCode":"100",

[0276] "fileName":"Highlight2023-08-30.mp4",

[0277] "partCount":"100",

[0278] "fileSize":"101238912",

[0279] "filesha256":"50529************************7B6F77DFE6F"

[0280] }

[0281] Among them, "fileName" can represent information of the first file, such as the name of the first file, "fileSize" can represent the size of the first file, and "filesha256" can represent identification information of the first file, such as a hash value used by a secure hash algorithm (SHA).

[0282] S219: The recording status module sends message 17 to the UI module.

[0283] In one implementation, the message 17 may indicate the end of recording. When the recording status module receives information indicating that the recording status of the electronic device 200 is successful, the recording task may be ended and the message 17 may be sent to the UI module.

[0284] S220: The UI module displays prompt information 2.

[0285] In one embodiment, the prompt information 2 can be used to prompt the user that the recording has ended. For example, the display interface of the UI module can be switched to display Figure 7 The user interface 130 shown in (A).

[0286] exist Fig. 9 In the method shown, when the state of the controlled device meets the first preset condition, the master device can control the controlled device to record multimedia data, and the controlled device can directly generate a multimedia file after recording. In addition, during the recording process, the master device can control the controlled device to stop recording in real time.

[0287] See also Fig.10 , Fig.10 is a flowchart of another recording method provided in an embodiment of the present application. This method can be applied to Figure 1A The recording system 10 shown. The method may include but is not limited to the following steps:

[0288] S301: The recording status module sends instruction 7 to the WebSocket communication module.

[0289] In one implementation, before S301, the following steps may also be included: Fig. 9 S201-S220.

[0290] In one implementation, when the recording status module finishes the recording task, the receiving task may be started, and the receiving task may be represented as HighlightReceiveTask.

[0291] In one implementation, instruction 7 may be used to request to obtain the first file, and after the recording status module starts the receiving task, instruction 7 may be sent to the WebSocketClient in the WebSocket communication module.

[0292] In one embodiment, the above-mentioned first file may include multiple file blocks. When the recording status module starts the receiving task, timer 3 can be started synchronously. Timer 3 can be used to cyclically obtain these multiple file blocks, that is, cyclically execute S301-S307, for example, start timer 3 once every 5 seconds, execute S301-S307 when started, then cancel timer 3, and restart, and only obtain one file block each time S301-S307 is executed.

[0293] S302: The WebSocket communication module sends message 18 to the CmdServer module.

[0294] In one implementation, the message 18 may be a file request message. In some examples, the format of the file request message may be characterized as follows:

[0295] {

[0296] "taskId":"5C0E***FE6FA",

[0297] "acticonCode":"receiveFile"

[0298] "fileName":"Highlight2023-08-30.mp4",

[0299] "part":"",

[0300] "partSize":"10240"

[0301] }

[0302] Among them, "part" can represent the subscript of the file block received by the recording status module, "part":"" can represent that the subscript of the received file block is empty, and "partSize" can represent the size of the file block.

[0303] In one implementation, when the WebSocket communication module sends a file request message to the CmdServer module for the first time, the recording status module has not yet received a file block, and therefore, the "part" in the file request message sent for the first time is empty.

[0304] S303: The CmdServer module sends message 19 to the WebSocket communication module.

[0305] In one implementation, the subscripts of the multiple file blocks may be consecutive integers. When the WebSocketServer in the CmdServer module receives a file request message, it may parse the file request message to determine the file blocks to be sent.

[0306] In one implementation, the WebSocket Server may determine the file block to be sent based on the index of the file block received by the electronic device 100, wherein the file block to be sent may be one of at least one file block that has not been received / is missing by the electronic device 100.

[0307] In some examples, when the "part" in the file request message is empty, the electronic device 100 lacks all the file blocks included in the first file. At this time, the WebSocket Server can determine the file block with the smallest subscript (for example, subscript 0) as the file block to be sent according to the order of the subscripts (for example, from small to large). In other examples, when the "part" in the file request message is "0,1,2,4,5", the WebSocket Server can determine the file block with subscript 3 as the file block to be sent.

[0308] In one implementation, the message 19 may be a file message, which may include a file block to be sent. In some examples, the format of the file message may be characterized as follows:

[0309] {

[0310] "taskId":"5C0E***FE6FA",

[0311] "fileName":"Highlight2023-08-30.mp4",

[0312] "fileSize":"1024111",

[0313] "fileSha256":"50529************************7B6F77DFE6F",

[0314] "currentIndex":1,

[0315] "dataStart":"0",

[0316] "dataSize":"10240",

[0317] "data":"D5052951A89E32******************************************7B6110F7796859DFE6FA"

[0318] }

[0319] Among them, "currentIndex" can represent the sequence number of the file block, "dataStart" can represent the subscript of the file block, "dataSize" can represent the size of the file block, and "data" can represent the data of the file block.

[0320] S304: The WebSocket communication module sends message 19 to the recording status module.

[0321] S305: The recording status module determines whether the first file is successfully received.

[0322] In one embodiment, after receiving the file message, the recording status module can parse the file message and determine whether the size of the file block received by the electronic device 100 is consistent with the size of the first file. When the two are consistent, the recording status module can obtain the second file based on the sequence number / subscript combination of the file block; when the two are inconsistent, the recording status module can re-execute S301-S305 to continue receiving the file blocks of the first file that are missing from the electronic device 100.

[0323] In one embodiment, when the recording status module obtains the second file, it can determine the identification information of the second file, such as the hash value (Sha256) used by SHA, and judge whether the identification information of the second file is consistent with the identification information of the first file in the file message. When the two are consistent, the recording status module determines that the first file is successfully received, and executes S308-S309 at this time; when the two are inconsistent, the recording status module can re-execute S301-S305 to re-receive the file blocks of the first file.

[0324] S306: The recording status module sends a message 20 to the UI module.

[0325] In one embodiment, each time the recording status module receives a file message (e.g., message 19), it can determine the current message 20 according to the file message and send the message 20 to the UI module. The message 20 may include the current progress information, which may be the percentage of the size of the file block received by the electronic device 100 to the size of the first file. In some examples, the recording status module may determine the progress information according to the size of the file block received by the electronic device 100 and the size of the first file.

[0326] S307: The UI module displays progress information.

[0327] In one embodiment, the progress information can be used to prompt the user the progress of currently receiving the first file. The UI module can display the progress information on the display screen, for example, Figure 7 The user interface 130 shown in (A).

[0328] The order of S305 and S306-S307 is not limited.

[0329] S308: The recording status module sends a message 21 to the UI module.

[0330] In one implementation, the message 21 may indicate that the recording status module successfully receives the first file.

[0331] S309: The UI module displays the first interface.

[0332] In one embodiment, the first interface may be a gallery interface, and the first interface may be used to play the received first file. For example, the UI module displays Figure 7 The user interface 140 is shown in (B).

[0333] exist Fig.10 In the method shown, after the controlled device finishes recording, the recorded multimedia file can be directly returned to the main control device, without the user having to manually select the device to be shared (i.e., electronic device 200), thereby reducing user operation and time costs, improving the efficiency of multimedia file sharing in the recording scenario, and improving user experience.

[0334] See also Fig.11 , Fig.11 is a flowchart of another recording method provided in an embodiment of the present application. This method can be applied to Figure 1A The recording system 10 shown. The method may include but is not limited to the following steps:

[0335] S401: A first device receives a first message sent by a second device.

[0336] In one implementation, the first message may be sent by the second device when receiving the first operation. For a description of the first message, see Figure 8 The specific description of message 3 in S107 is omitted here.

[0337] In one implementation, the first operation may be an operation of a recording control in a second interface displayed by the second device, and the second interface may be an operation interface of the first device. For a description of the first operation, see Figure 8 The specific description of the first operation in S101 is omitted. The second interface is, for example, Figure 4 The user interface 110 shown in (A).

[0338] In one implementation, the first device may be a large-screen device, and the second device may be a terminal device. For example, the first device may be Figure 8 The electronic device 200 in the embodiment of the present invention, the second device is for example Figure 8 An electronic device 100 is provided in the embodiment of the present invention.

[0339] S402: The first device sends the status of the first device to the second device according to the first message.

[0340] In one embodiment, the state of the first device may include the state of the first function and the state of the second function. The first function may be a function of recording the first interface displayed by the first device, and the second function may be a function that cannot be turned on when the first function is turned on by the first device. It can be understood that the second function may be other functions that conflict with the first function, such as a mirror control function. The description of the state of the first function can be found in Figure 8 For a detailed description of the state of the first function in S109, and a description of the state of the second function, see Figure 8 For a detailed description of the state of the second function in S111, the state of the first device can be found in Figure 8 The specific description of message 8 in S112 is omitted here.

[0341] S403: The first device receives a first instruction sent by the second device.

[0342] In one implementation, the first instruction may be a recording instruction. For a description of the first instruction, see Fig. 9 The specific description of instruction 3 in S203 is omitted here.

[0343] In one embodiment, the first instruction is sent by the second device when it determines that the state of the first device meets the first preset condition. The first preset condition may include that the second function of the first device is not turned on. For an explanation of the first preset condition, see Fig. 9 The specific description of the first preset condition in S203 is omitted here.

[0344] S404: The first device records the first interface displayed by the first device according to the first instruction to generate a first file.

[0345] In one implementation, the first interface can be used to play the first multimedia. For a description of the first multimedia, see Fig. 9 The specific description of the multimedia data in S206 is omitted here.

[0346] In one implementation, the first device may start recording the first interface displayed by the first device according to the first instruction, and obtain the recorded multimedia data. For details, see Fig. 9 The description of S206-S207 is omitted here.

[0347] In one implementation, the first device may generate a first file based on the acquired multimedia data. For details, see Fig. 9 The specific description of S217 is omitted here.

[0348] In one implementation, the first device may receive a second instruction sent by the second device, and stop recording the first interface according to the second instruction. The second instruction is sent by the second device when receiving the second operation. The second instruction may be an end instruction. For a description of the second instruction, see Fig. 9 For a detailed description of instruction 5 in S213, the description of the second operation can be found in Fig. 9 Specific description of the third operation in S212.

[0349] In one implementation, the first device may detect a first duration of recording the first interface, and when the first duration is greater than or equal to a preset duration, stop recording the first interface. For details, see Fig. 9 The description of S217 is omitted here.

[0350] S405: The first device sends the first file to the second device.

[0351] In one implementation, the first file includes multiple file blocks, the first device may receive a second message sent by the second device, and send a third message to the second device according to the second message, wherein the second message may include the file blocks received by the second device, and the third message may include the file blocks not received by the second device, and the file blocks not received by the second device are any file blocks among the multiple file blocks except the file blocks received by the second device. For an explanation of the second message, see Fig.10 For details of message 18 in S302, please refer to Fig.10 For a detailed description of message 19 in S303 and a description of the file block not received by the second device, see Fig.10 The description of the file blocks to be sent in S303 is omitted here.

[0352] In one implementation, the second device may display progress information, which may be used to prompt the user of the progress of currently receiving the first file. For details, see Fig.10 The description of S307 is omitted here.

[0353] In one implementation, the second device can determine whether the first file is successfully received. When the second device successfully receives the first file, a third interface can be displayed. The third interface can be a gallery interface for playing the received first file. For instructions on whether the second device successfully receives the first file, see Fig.10 The specific description of S305 is omitted here.

[0354] exist Fig.11In the method shown, the terminal device can act as a master control device to control the large-screen device (which can be called the controlled device) in real time to record the first multimedia. After the large-screen device finishes recording, the recorded first file can be directly returned to the terminal device. In this way, the user no longer needs to manually select the device to be shared, but can directly select the terminal device in the recording scene and perform an operation on the terminal device to realize the recording and sharing process of the first file, which reduces user operation and time costs, thereby improving the efficiency of sharing the first file in the recording scene and improving the user experience.

[0355] The methods provided in the embodiments of the present application may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiments of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (DWD), or a semiconductor medium (e.g., a solid state drive (SSD)). As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application is described in detail with reference to the above embodiments, a person skilled in the art should understand that the technical solutions described in the above embodiments can still be modified, or some of the technical features can be replaced by equivalents; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A recording method, characterized in that: Applied to a first device, the method includes: receiving a first message sent by a second device, where the first message is sent when the second device receives a first operation; sending the status of the first device to the second device according to the first message; receiving a first instruction sent by the second device, where the first instruction is sent when the second device determines that a state of the first device satisfies a first preset condition; Record a first interface displayed by the first device according to the first instruction to generate a first file, where the first interface is used to play a first multimedia; Send the first file to the second device.

2. The method according to claim 1, characterized in that The state of the first device includes the state of a first function and the state of a second function, the first function is a function of recording the first interface displayed by the first device, and the second function is a function that cannot be turned on when the first device turns on the first function.

3. The method according to claim 2, characterized in that The state of the first device satisfies a first preset condition, including: The second function of the first device is in an unactivated state.

4. The method according to any one of claims 1 to 3, characterized in that: The first operation is an operation on a recording control in a second interface displayed by the second device, and the second interface is an operation interface of the first device.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: receiving a second instruction sent by the second device, where the second instruction is sent by the second device when the second device receives a second operation; stopping recording the first interface according to the second instruction; or, Detect a first duration of recording the first interface, and stop recording the first interface when the first duration is greater than or equal to a preset duration.

6. The method according to any one of claims 1 to 5, characterized in that: The first file includes a plurality of file blocks, and the method further includes: receiving a second message sent by the second device, where the second message includes a file block received by the second device; A third message is sent to the second device according to the second message, wherein the third message includes a file block not received by the second device, and the file block not received by the second device is any file block among the multiple file blocks except the file block received by the second device.

7. The method according to any one of claims 1 to 6, characterized in that: The first device is a large-screen device, and the second device is a terminal device.

8. A recording method, characterized in that: Applied to the second device, the method includes: receiving a first operation; Sending a first message to a first device according to a first operation; receiving a state of the first device sent by the first device, where the state of the first device is acquired by the first device according to the first message; When the state of the first device meets a first preset condition, sending a first instruction to the first device, the first instruction is used for the first device to record a first interface displayed by the first device to generate a first file, and the first interface is used to play a first multimedia; Receive the first file sent by the first device.

9. The method according to claim 8, characterized in that The method further comprises: Displaying a second interface, where the second interface is an operation interface of the first device, and when the second device displays the second interface, the first interface displayed by the first device is used to play the first multimedia; The receiving first operation includes: receiving the first operation acting on the recording control in the second interface; In response to the first operation, a prompt message is displayed on the second interface, where the prompt message is used to prompt the first device to start recording the first multimedia.

10. The method according to claim 9, characterized in that After displaying the prompt information on the second interface, the method further includes: A third interface is displayed, wherein the third interface includes progress information, and the progress information indicates a progress of the second device receiving the first file.

11. The method according to any one of claims 8 to 10, characterized in that: The first device is a large-screen device, and the second device is a terminal device.

12. An electronic device, characterized in that: The method comprises a transceiver, a processor and a memory, wherein the memory is used to store a computer program, and the processor calls the computer program to execute the method according to any one of claims 1 to 7 or claims 8 to 11.

13. A computer storage medium, characterized in that: The computer storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 11 is implemented.

Images