Picture display control method and control device

Abstract

The invention provides a picture display control method and device, and the method comprises the steps: receiving a first signal which comprises a power-on signal or a wake-up signal; sending a first data frame to the first device, wherein the first data frame is used for indicating the first picture; a second data frame is sent to the first device, the second data frame is used for indicating a second picture, the second picture comprises a startup picture or a wake-up interface, and the first picture and the second picture are different. According to the scheme of the embodiment of the invention, the required picture can be quickly displayed in the process that the electronic equipment enters the working state from the non-working state, so that the user experience can be improved.

Description

Technical Field

[0001] This application relates to the field of flat panel display technology, specifically to a control method and control device for screen display. Background Technology

[0002] Image output devices can take a considerable amount of time to transition from a non-working state to a working state. During this process, the time required to display the first screen (such as an image or video) can be long, impacting the user experience. For example, a set-top box (STB) requires a period of time to boot up after power-on. To reduce user boredom while waiting for the device to start, a boot screen, or boot logo, is typically displayed. Specifically, after the user powers on the device, an image or video is displayed on the screen for the user to enjoy, while background processes begin running until the device boots up completely. This image or video is the boot screen. However, currently, the time between powering on the device and displaying the boot screen is too long, thus affecting the user experience. Summary of the Invention

[0003] This application provides a screen display control method and control device, which is beneficial for quickly displaying the required screen when an electronic device transitions from a non-working state to a working state, thereby improving the user experience.

[0004] In a first aspect, a method for controlling screen display is provided. This control method can be executed by an electronic device (such as a second device) or a device applied to the electronic device (e.g., a chip or circuit).

[0005] The control method includes: receiving a first signal, wherein the first signal includes a power-on signal or a wake-up signal; sending a first data frame to a first device, wherein the first data frame is used to indicate a first screen; and sending a second data frame to the first device, wherein the second data frame is used to indicate a second screen, wherein the second screen includes a power-on screen or a wake-up interface, and the first screen and the second screen are different.

[0006] According to the solution of this application embodiment, before sending the actual screen to be displayed (such as the second data frame) to the receiving end (such as the first device), other data frames (such as the first data frame) are sent to the receiving end to trigger the receiving end to start the preparation work for screen display (i.e., output). Alternatively, the signal of the screen to be displayed is separated from the trigger signal for the first device to operate. In this way, the startup or wake-up process of the sending end (such as the second device) and the preparation work of the first device before output can be executed in parallel, or the first device can enter the working mode in advance, thereby shortening the output time of the actual screen to be displayed. At the same time, the parallel execution method helps reduce the impact of the execution time on the first device side on the output time, thereby helping to ensure the stability of the output time. Moreover, the solution of this application embodiment does not increase additional costs.

[0007] For example, the solution of this application embodiment can be applied to the scenario of power-on startup, in which case the first signal can be a power-on signal and the second screen can be a power-on screen.

[0008] For example, the solution of this application embodiment can be applied to a standby wake-up scenario, in which the first signal can be wake-up information and the second screen can be a wake-up interface.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the first data frame is used to trigger the first device to perform a clock locking operation.

[0010] In other words, the first data frame can be used to trigger the first device to enter the working state, or to activate the first device to enter the working mode, or to trigger the initialization of the first device.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the format of the first screen and the format of the second screen are the same.

[0012] For example, the standard may include at least one of the following: resolution, refresh rate, or color format.

[0013] According to the solution of the embodiment of this application, the format of the second screen and the format of the first screen can be the same. In this way, there is no need to switch the format of the screen, that is, the first device does not need to adjust the configuration, which can avoid problems such as black screen or image flickering, thereby helping to further ensure the user experience.

[0014] In conjunction with the first aspect, in some implementations of the first aspect, the control method further includes: reading the format of the second screen from external memory.

[0015] External memory can be used to store one or more standards.

[0016] For example, the external storage device can be flash memory or a hard disk.

[0017] According to the scheme of this application embodiment, the standard information can be stored in an external memory. After power-on, the required standard information (such as the standard of the second screen) can be read from the external memory. This makes it easier to adjust or customize the standard information to better meet user needs. At the same time, the external memory has a large storage space, which is conducive to storing more standard information, thereby facilitating comprehensive coverage of all standards and better meeting user needs.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, sending a first data frame to a first device includes: sending the first data frame to the first device when the format of the second screen is the first format, and skipping the transmission of the first data frame when the format of the second screen is the second format, wherein the first format and the second format are different.

[0019] If the format of the second screen belongs to the format set, then the first data frame is sent; if the format of the second screen does not belong to the format set, then the sending of the first data frame is skipped. The first format belongs to the format set, and the second format does not belong to the format set.

[0020] For example, the first standard can be a standard supported by the second device during the construction of the first data frame, and the second standard can be a standard that the second device cannot support during the construction of the first data frame.

[0021] According to the scheme of the embodiment of this application, if the format of the second screen meets the preset conditions, for example, the second device currently supports the target format, then the first data frame is sent. If the format of the second screen does not meet the preset conditions, for example, the second device currently cannot support the target format, then the sending of the first data frame can be skipped and the conventional boot screen display scheme can be executed. This is beneficial to improving compatibility and thus to ensuring user experience.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the first frame is a black frame.

[0023] If the first device completes display initialization but the second data frame has not yet arrived at the first device, the first device can display the first screen based on the first data frame. When the second data frame arrives, the boot screen or wake-up interface will be displayed.

[0024] In the embodiments of this application, the first data frame can be a black frame. Using a black frame for the first data frame has a relatively small impact on the user experience.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, sending a first data frame to a first device includes: sending a first data frame to the first device via an HDMI interface; and sending a second data frame to the first device includes: sending a second data frame to the first device via an HDMI interface.

[0026] For example, the first device and the second device can be directly connected via an HDMI cable. The first device and the second device transmit data based on the HDMI protocol, and the second device can send data frames to the first device through the HDMI interface.

[0027] For example, data frames can be carried in timing signals.

[0028] Secondly, a screen display control device is provided, comprising: a receiving module for receiving a first signal, wherein the first signal includes a power-on signal or a wake-up signal; and a sending module for: sending a first data frame to a first device, wherein the first data frame is used to indicate a first screen; and sending a second data frame to the first device, wherein the second data frame is used to indicate a second screen, wherein the second screen includes a power-on screen or a wake-up interface, and the first screen and the second screen are different.

[0029] In conjunction with the second aspect, in some implementations of the second aspect, the first data frame is used to trigger the first device to perform a clock locking operation.

[0030] In conjunction with the second aspect, in some implementations of the second aspect, the format of the first screen and the format of the second screen are the same.

[0031] In conjunction with the second aspect, in some implementations of the second aspect, the control device further includes: a reading module for reading the format of the second screen from an external memory.

[0032] In conjunction with the second aspect, in some implementations of the second aspect, the sending module is specifically used to: send a first data frame to the first device when the format of the second screen is the first format, and skip sending the first data frame when the format of the second screen is the second format, wherein the first format and the second format are different.

[0033] In conjunction with the second aspect, in some implementations of the second aspect, the first frame is a black frame.

[0034] In conjunction with the second aspect, in some implementations of the second aspect, the sending module is specifically used to: send a first data frame to the first device via the high-definition multimedia interface (HDMI); and send a second data frame to the first device via the HDMI interface.

[0035] It should be understood that the extensions, limitations, explanations and descriptions of the relevant content in the first aspect above also apply to the same content in the second aspect.

[0036] Thirdly, an electronic device is provided, including a processor and a memory, and optionally, an input / output interface. The processor controls the input / output interface to send and receive information, the memory stores a computer program, and the processor retrieves and runs the computer program from the memory, causing the electronic device to perform the method described in the first aspect and any possible implementation thereof.

[0037] Optionally, the electronic device may include any of the following: STB, laptop, personal computer (PC), game console, tablet, or mobile phone.

[0038] Optionally, the processor can be a general-purpose processor, which can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. This memory can be integrated into the processor or located outside the processor and exist independently.

[0039] Fourthly, a chip system is provided that acquires and executes instructions to implement the methods described in the first aspect and any of the implementation methods above.

[0040] Optionally, as one implementation, the chip system includes a processor and a data interface, through which the processor reads instructions stored in the memory and executes the methods described in the first aspect and any of the implementations.

[0041] Optionally, as one implementation, the chip system may further include a memory storing instructions, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to perform the method in the first aspect and any of the implementations.

[0042] Fifthly, a computer program product containing instructions is provided, which, when executed by a computing device, causes the computing device to perform the methods described in the first aspect and any of the implementations above.

[0043] In a sixth aspect, a computer-readable storage medium is provided, including computer program instructions that, when executed by a computing device, perform the methods described in the first aspect and any of its implementations.

[0044] As examples, these computer-readable storage media include, but are not limited to, one or more of the following: read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), flash memory, electrically EPROM (EEPROM), and hard drive.

[0045] Alternatively, as one implementation method, the aforementioned storage medium can specifically be a non-volatile storage medium. Attached Figure Description

[0046] Figure 1 This is a diagram illustrating an application scenario for a startup logo.

[0047] Figure 2 This is a schematic diagram of the HDMI communication process between the STB and the TV.

[0048] Figure 3 This is a schematic diagram of the processing flow on the TX and RX sides.

[0049] Figure 4 This is a schematic flowchart of a screen display control method according to an embodiment of this application.

[0050] Figure 5 This is a schematic flowchart illustrating the screen display control method of this application applied to a power-on startup scenario.

[0051] Figure 6 This is a schematic flowchart illustrating a control method for screen display based on HDMI according to an embodiment of this application.

[0052] Figure 7 This is a schematic flowchart illustrating another control method for screen display based on HDMI, according to an embodiment of this application.

[0053] Figure 8 This is a schematic flowchart illustrating the screen display control method of this application applied to a standby wake-up scenario.

[0054] Figure 9 This is a schematic block diagram of a screen display control device according to an embodiment of this application.

[0055] Figure 10 This is a schematic diagram of the architecture of a control device for screen display according to another embodiment of this application. Detailed Implementation

[0056] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0057] The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” and “the” are intended to include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the following embodiments of this application, “at least one,” “at least one,” and “one or more” refer to one, two, or more than two. “First,” “second,” and various numerical designations are merely distinctions for descriptive convenience and are not intended to limit the scope of the embodiments of this application. “And / or” is used to describe the correspondence between corresponding objects, indicating that three relationships can exist. For example, “A and / or B” can represent: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character “ / ” generally indicates that the preceding and following related objects are in an “or” relationship. The order of the process numbers below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic and should not constitute any limitation on the implementation process of the embodiments of this application. For example, in the embodiments of this application, the words "301", "401", "501" etc. are merely identifiers made for the convenience of description and do not limit the order of execution steps.

[0058] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. In this application, the words "exemplary" or "for example" are used to indicate that something is illustrative, exemplary, or descriptive. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner. The terms "comprising," "including," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized. In the embodiments of this application, descriptions such as "when," "in the case of," "if," and "if" all refer to the fact that the device will perform a corresponding processing under certain objective circumstances, and are not a limitation on time, nor do they require the device to perform a judgment action during implementation, nor do they imply any other limitations.

[0059] In this application, "for indicating" can include both direct and indirect indication. When describing an indication message as indicating A, it can include whether the indication message directly indicates A or indirectly indicates A, but does not necessarily mean that the indication message carries A.

[0060] In this application, "device A sends signal A to device B" can be understood as device B being the destination of signal A or an intermediate device in the transmission path between the destination and device B, and may include sending information directly or indirectly to device B. "device B receives signal A from device A" can be understood as signal A being the source of signal A or an intermediate signal in the transmission path between the source and device B, and may include receiving information directly or indirectly from signal A. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here. Signals can include information, signaling, or data, etc.

[0061] Image output devices may take some time to transition from a non-working state to a working state, and the time required to display the first image is relatively long, which affects the user experience.

[0062] The following explanation uses the power-on startup scenario as an example. Image output devices require a period of time to complete startup after being powered on. During this time, a startup screen, i.e., a startup logo, is usually displayed.

[0063] Figure 1 This diagram illustrates an application scenario for a boot-up logo. For example... Figure 1 As shown, in this application scenario, the STB is the transmitting (TX) end of the power-on logo, and the receiving (RX) end can be a television (TV). The STB can be connected to the TV via a high-definition multimedia interface (HDMI) cable. Before entering the main function interface, the STB will display an image or animation, which is the power-on screen. It usually takes some time from the STB being powered on until the power-on screen appears on the TV; during this time, the TV remains in a no-signal state.

[0064] HDMI is a digital interface used to transmit uncompressed audio and video data. HDMI supports a variety of video and audio formats, which are often referred to as "standards".

[0065] Figure 2 A schematic diagram of an HDMI communication process between an STB and a TV is shown.

[0066] like Figure 2 As shown, the HDMI communication process between the STB and TV during the display of the boot logo can include the following steps.

[0067] 1) Power on and start.

[0068] After the STB is powered on, it first enters the boot read-only memory (bootrom) stage.

[0069] 2) Bootrom startup.

[0070] The STB enters the bootrom stage, loading basic boot code and initializing the hardware.

[0071] 3) Hot plug detection (HPD).

[0072] After the TV detects the STB connection, it pulls the HPD signal high to notify the STB that it is connected. The STB, upon detecting the HPD signal, knows that the TV is connected.

[0073] 4) Display initialization entry (display init entry).

[0074] STB enters the display initialization phase and configures appropriate timing parameters.

[0075] 5) Display initialization exit (display initialization exit, display init exit).

[0076] After STB completes display initialization, it exits the display initialization phase.

[0077] 6) STB sends timing signals.

[0078] STB sends timing signals to TV via HDMI interface.

[0079] After receiving the timing signal, the TV starts working, and its subsequent working state does not depend on the STB.

[0080] 7) TV performs clock lock (Clk lock).

[0081] The TV locks the HDMI clock signal to ensure clock synchronization.

[0082] 8) TV timing is stable.

[0083] The TV's timing signal is stable, ensuring that all timing parameters are correct.

[0084] 9) TV completes display initialization.

[0085] The TV completes its internal display initialization and is ready to receive and display image data.

[0086] 10) TV receives images from STB.

[0087] After approximately 1.2 to 1.5 seconds, the TV receives the image data sent by the STB and begins displaying the image.

[0088] The operation on the TV can be completed by various components in the TV. These components may include HDMI driver (DRV), middleware (MIDWARE), audio input / output and extended data packet (AIAO & XDP), video buffer output (VBO) module, and display panel, etc.

[0089] The approximate time required for each stage is as follows: Figure 1 As shown.

[0090] Figure 3 This diagram illustrates the processing flow of the TX and RX sides in a scenario where the boot logo is displayed.

[0091] like Figure 3 As shown, the boot process on the TX side involves multiple components such as bootrom, auxiliary code (auxcode), and bootloader, which correspond to ROM firmware (firmware in ROM), RAM firmware (firmware in RAM), and double data rate random access memory (DDR) firmware (firmware in DDR), respectively.

[0092] The driver services related to the boot logo are concentrated in the bootloader software running on the DDR. Specifically, the bootloader performs actions such as service driver initialization, logo data reading, and logo data decoding to obtain the data to be sent. This data can be sent to the RX end in the form of a logo frame timing signal. After completing operations such as clock locking, timing stabilization, and display initialization, the RX end can display the boot logo. The logo frame timing signal is sent based on the horizontal synchronization signal (HSYNC) and the vertical synchronization signal (VSYNC).

[0093] The above scheme is executed serially, and the total time required from power-on to the display of the startup logo is approximately T. bootrom +T auxcode +T bootloader +T clock_lock +T timing_stable +T display T bootrom T auxcode T bootloader T clock_lock T timing_stable T display These represent the time for the bootrom stage, auxcode stage, bootloader stage, clock lock stage, timing stable stage, and display initialization stage, respectively. Furthermore, because the system initialization process in the bootloader involves numerous steps, the time required for the boot logo display is relatively long and the duration is unpredictable.

[0094] In view of this, the embodiments of this application provide a screen display control method, which is beneficial for quickly displaying the required screen in scenarios where the device transitions from a non-working state to a working state, thereby improving the user experience.

[0095] Figure 4 A schematic flowchart illustrating a screen display method according to an embodiment of this application is shown. Figure 4 The method 400 shown can be applied to scenarios where the device transitions from a non-working state to a working state, so that the required screen can be displayed quickly in such scenarios.

[0096] For example, the non-operating state may include a power-off state, in which case the process of the device transitioning from a non-operating state to an operating state is the process from powering on the device to completing the startup process. In other words, method 400 can be applied to scenarios involving the power-on and startup of electronic devices. For example, Figure 4 The method shown can be applied to Figure 1 The scene shown on the boot screen.

[0097] For example, the non-working state may include standby state, low-power mode, or hibernation mode, etc. In this case, the process of the device transitioning from the non-working state to the working state is the process of waking the device from the standby state. In other words, method 400 can be applied to scenarios where electronic devices wake up from standby.

[0098] Method 400 is applicable to interaction scenarios between devices connected via TX&RX class protocols. Exemplarily, TX&RX class protocols may include HDMI, Mobile Industry Processor Interface (MIPI), or General Purpose Media Interface (GPMI) TX&RX class protocols. For ease of description, this application embodiment primarily uses the interaction between devices connected via HDMI as an example.

[0099] Method 400 can be performed by an electronic device or a device applied to an electronic device (e.g., a chip or circuit). In other words, in this embodiment, the device for implementing the function of the electronic device can be an electronic device or a device capable of supporting the electronic device in implementing that function, such as a chip system, which can be installed in or used in conjunction with the electronic device. In this embodiment, the chip system can be composed of chips or may include chips and other discrete devices. In this embodiment, the example of an electronic device (such as a second device) being used to implement the function of the electronic device is only provided and does not constitute a limitation on the solution of this embodiment.

[0100] In method 400, the second device and the first device can be either a general-purpose media device or a general-purpose display device. The second device can be considered as the TX end, and the first device can be considered as the RX end.

[0101] For example, the second device can be an STB, laptop, PC, game console, tablet, or mobile phone, etc. The first device can be a TV, commercial display, or projector, etc.

[0102] The above are merely examples; in other implementations, the second device can also be replaced by a chip or circuit, etc. For instance, the chip can be a system-on-chip (SOC) chip. For example, the chip can be a general-purpose media SOC chip.

[0103] like Figure 4 As shown, method 400 may include the following steps.

[0104] 410, the second device receives the first signal. The first signal is used to indicate that the second device enters the working state from the non-working state.

[0105] 420, the second device sends a first data frame to the first device. The first data frame is used to indicate the first screen.

[0106] 430, the second device sends a second data frame to the first device. The second data frame is used to indicate a second screen. The second screen includes a boot screen or wake-up interface. The first screen and the second screen are different.

[0107] 440, the first device displays the second screen.

[0108] After receiving the second data frame, the first device can display the second screen.

[0109] The second device begins operating later than the second data frame is transmitted.

[0110] The "first" in "first signal" is for ease of use only and does not have a limiting effect.

[0111] Optionally, the first signal can be a startup signal. The startup signal can also be replaced by a power-on signal, a power-on signal, or a power-on-power-on signal, etc. In this case, the second screen can be the startup screen.

[0112] As mentioned above, method 400 can be applied to power-on scenarios. In this scenario, the first signal can be a startup signal, and the second data frame is used to indicate the startup screen. That is, after the second device is powered on, i.e., after receiving the power-on signal, it executes steps 420 to 430 to cause the first device to display the startup screen. Afterward, the second device completes the startup process and enters a working state. For example, the second device entering a working state can be the main interface for controlling the display and interacting with the user.

[0113] Optionally, the first signal can be a wake-up signal. In this case, the second screen can be a wake-up interface.

[0114] As previously described, method 400 can be applied to standby wake-up scenarios. In this scenario, the first signal can be a wake-up signal, and the second data frame is used to indicate the wake-up interface. That is, after receiving the wake-up signal, the second device executes steps 420 to 430 to cause the first device to display the wake-up interface.

[0115] The "second" in "second device" is only used to indicate that the device can be used as a TX terminal and has no other limiting function.

[0116] The word "first" in "first device" is only used to indicate that the device can be used as the RX end and has no other limiting function.

[0117] The second device and the first device are different devices.

[0118] The second device can send data frames to the first device. The second device can be understood as the source of the data frame, and the first device can be understood as the destination of the data frame.

[0119] As one possible implementation, the second device and the first device can be directly connected. In this case, the second device directly sends data frames to the first device.

[0120] Alternatively, the second device and the first device can be directly connected via an HDMI cable. In other words, the first and second devices transmit data based on the HDMI protocol. The second device sends data frames to the first device through the HDMI interface.

[0121] For example, the second device can be an STB, and the first device can be a TV.

[0122] In this scenario, the data frame can be carried within a timing signal. Alternatively, the second device can send a data frame to the first device via an HDMI interface, and this timing signal can be used to carry the data frame.

[0123] As another possible implementation, the second device and the first device can be indirectly connected. In this case, the second device can send data frames to the first device via forwarding from other devices.

[0124] For example, the second device and the first device can be connected via a docking station. For instance, the second device could be a laptop, and the first device could be a monitor.

[0125] For example, the second device can be directly connected to the docking station, and the docking station can be directly connected to the first device via an HDMI cable.

[0126] In this scenario, the second device can send data frames to the docking station via other types of interfaces. The docking station can then encapsulate these data frames into timing signals and send them to the first device via an HDMI interface.

[0127] Data frames are used to indicate the image, but can also be replaced by data frames used to indicate image or video frames, etc.

[0128] For example, a data frame may include image data or video data. For instance, a data frame may include pixel data of an image.

[0129] The format of the data frame can be determined according to the transmission protocol, and this application embodiment does not limit it. For example, if the second device and the first device transmit via HDMI, the data frame can be sent in a format that conforms to the HDMI standard (such as a timing signal).

[0130] The terms "first" and "second" in "first data frame" and "second data frame" are used only to distinguish between two different data frames and have no other limiting function.

[0131] The first data frame can be any data frame that is different from the second data frame.

[0132] For example, the first data frame may be acquired before it is sent. Acquiring the first data frame may include: generating the first data frame, or constructing the first data frame.

[0133] The faster the acquisition of the first data frame, the faster the transmission of the first data frame.

[0134] For example, the first data frame can be constructed by the second device itself, i.e., without external input. Alternatively, the first data frame may not be obtained through decoding.

[0135] Constructing the first data frame yourself can accelerate its transmission.

[0136] Optionally, the first data frame can be a black frame.

[0137] A black frame can be understood as a completely black image. A black frame can also be replaced with a dark frame, etc.

[0138] Optionally, step 420 may include: the second device sending a first data frame to the first device during the bootrom stage.

[0139] The bootrom is the ROM firmware. The bootrom stage is the execution stage of the ROM firmware. Taking advantage of the fact that the second device executes the bootrom first after power-on, the drivers that the data frames depend on are executed in advance to the bootrom stage.

[0140] For example, taking HDMI as an example, the drivers upon which the data frame transmission depends can include a driver for transmitting signals and a display-related driver. For example, the driver for transmitting signals can be an HDMI TX driver. For example, the display-related driver can include a video display processor (VDP) driver. The first data frame is constructed and transmitted using the HDMI TX and VDP drivers. In this way, the timing of data frame transmission can be advanced to the bootrom stage.

[0141] Optionally, step 420 may include: the second device sending a first data frame to the first device during the auxcode stage.

[0142] The auxcode stage refers to the RAM firmware. The auxcode stage is the execution stage of the RAM firmware. Leveraging the relatively early execution order of the RAM firmware, the drivers that the data frames depend on are executed in advance during the auxcode stage. This allows the data frame transmission to occur earlier in the auxcode stage. Descriptions of the drivers that the data frames depend on can be found in the descriptions of the relevant drivers in the bootrom stage; to avoid repetition, they will not be repeated here.

[0143] For example, the second data frame can be acquired before it is sent. Acquiring the second data frame may include: generating the second data frame, or constructing the second data frame.

[0144] In some possible implementations, the second data frame is used to indicate the boot screen or wake-up interface, and may include the boot screen or wake-up interface. For example, the second data frame may include pixel data of the boot screen or the wake-up interface.

[0145] The boot screen can also be replaced with the boot banner, the first large image of startup, the boot logo, or a boot logo image, etc.

[0146] For example, the first data frame can be used to trigger the first device to enter a working state, or to activate the first device to enter a working mode, or to trigger the initialization of the first device. The content in the second data frame is the actual screen to be displayed. For example, triggering the first device to enter a working state may include triggering the initialization of the display-related driver in the first device.

[0147] Optionally, the first data frame can be used to trigger the first device to perform at least one of the following operations: clk lock, timing stable, or display initialization, etc.

[0148] In the solution of this application embodiment, before sending the actual screen to be displayed (such as the second data frame) to the receiving end (such as the first device), other data frames (such as the first data frame) are sent to the receiving end to trigger the receiving end to start the preparation work for screen display (i.e., output). Alternatively, the signal for the actual screen to be displayed is separated from the trigger signal for the first device to operate. In this way, the startup or wake-up process of the second device and the preparation work before outputting the image by the first device can be executed in parallel, or the first device can enter the working mode earlier, thereby shortening the output time of the actual screen to be displayed. At the same time, the parallel execution method helps reduce the impact of the execution time on the first device side on the output time, thereby helping to ensure the stability of the output time. Moreover, the solution of this application embodiment does not increase additional costs.

[0149] Typically, it takes a relatively long time for the first device to enter working mode. By the time the first device completes display initialization, the second data frame has already arrived. At this point, the first device can directly display the boot screen or wake-up interface.

[0150] If the first device completes display initialization before the second data frame arrives, the first device can display the first screen based on the first data frame. Once the second data frame arrives, it can then display the boot screen or wake-up interface. In this embodiment, the first data frame can be a black frame. Using a black frame for the first data frame has minimal impact on the user experience.

[0151] It should be understood that the embodiments of this application only use the first data frame as an example for illustration, and are not limited to sending other data frames only once before sending the actual screen to be displayed (the second data frame). In other implementations, other data frames can be sent multiple times before sending the actual screen to be displayed. The embodiments of this application do not limit the number of times data frames are sent.

[0152] The second data frame will be explained below with the first signal being the start signal as an example.

[0153] The second data frame is used to indicate the boot screen. In this case, the second data frame can also be called the logo image frame or logo frame, etc.

[0154] Optionally, in this case, method 400 may also include steps 421 and 422 (not shown in the figure).

[0155] 421, The second device acquires the target encoded data.

[0156] 422, The second device decodes the target encoded data to obtain the boot screen.

[0157] The first data frame can be sent before the decoding operation is complete.

[0158] Further, step 421 may include the second device reading target encoded data from the first memory. The first memory may be used to store one or more pieces of encoded data.

[0159] The "first" in "first memory" is for descriptive convenience only and has no limiting effect; any memory that stores coded data can be regarded as the first memory.

[0160] Encoded data can be understood as the encoding result of an image or video frame. Decoding this encoded data yields the image or video frame, or in other words, the pixel data of the image or video frame. This decoding operation can be an image decoding operation or a video decoding operation, etc.

[0161] The different encoded data in the first memory represent the encoding results of different images. These different images represent different candidate boot screens. The multiple encoded data represent the encoding data of multiple candidate boot screens. The start screen indicated by the second data frame is one of these multiple candidate boot screens. The target encoded data is the encoding result of the boot screen indicated by the second data frame.

[0162] Further, optionally, step 421 may include: the second device acquiring target encoded data from multiple encoded data.

[0163] If the first memory stores the encoded data of multiple boot screens, after power-on, the second device can select the encoded data of the desired boot screen (i.e., the target encoded data) as needed for decoding to obtain the desired boot screen, and send it to the first device for display.

[0164] The method for determining the target encoded data can be set as needed.

[0165] For example, the target encoded data can be randomly determined from these multiple encoded data.

[0166] For example, the target encoded data can be determined based on the user's selection. The user can select the desired boot screen from multiple boot screens, and the second device can determine the corresponding encoded data based on the user's selection, and then perform image decoding to obtain the boot screen selected by the user.

[0167] The above are merely examples; the target encoded data can also be determined in other ways, and this application does not limit this.

[0168] Optionally, the first memory can be an external memory. For example, the external memory can be flash memory or a hard disk.

[0169] In the solution of this application embodiment, the sending of the decoding operation and the trigger signal for the first device to operate are separated. That is, the triggering timing for the first device to enter the working mode no longer depends on the completion time of the decoding operation, and the trigger signal (i.e., the first data frame) can be sent before the decoding operation is completed. In this way, while the first device is entering the working mode, the second device performs decoding operations in parallel, which helps to shorten the image output time of the second data frame.

[0170] Furthermore, in the embodiments of this application, the boot screen information can be stored in an external memory. After power-on, the second device can read the required boot screen information from the external memory. This allows for more convenient adjustment or customization of the boot screen to better meet user needs. Simultaneously, the external memory has a larger storage space, which is beneficial for storing more boot screens, thus further enhancing user satisfaction.

[0171] The format of the second screen can be the same as that of the first screen.

[0172] In this way, there is no need to switch the screen format, meaning the first device does not need to adjust its configuration, which can avoid problems such as black screen or image flickering, thus further ensuring the user experience.

[0173] The standard can also be replaced with other descriptions such as format. For example, the standard may include at least one of the following: resolution, refresh rate, color depth, or color output format.

[0174] The format of the first frame can be indicated by the first data frame. The format of the second frame can be indicated by the second data frame. For example, the second device can send data frames to the first device via an HDMI interface, and these data frames can be timing signals.

[0175] It should be understood that the above is only an example, and the format of the image can also be indicated by signals other than data frames.

[0176] Optionally, method 400 may also include step 411 (not shown in the figure).

[0177] 411, The second device acquires the target system.

[0178] The target format can be used as the format for the boot screen.

[0179] The second device can construct a first data frame according to the target format so that the format of the first image is the same as the target format.

[0180] Further, step 411 may include the second device reading the target standard from the second memory. The second memory may be used to store one or more standards.

[0181] The term "second" in "second memory" is for descriptive convenience only and has no limiting effect; any memory that stores a standard can be considered a second memory. The first memory and the second memory can be the same memory or different memory.

[0182] Further, optionally, step 411 may include: the second device obtaining the target standard from multiple standards.

[0183] If the second memory stores multiple standards, after power-on, the second device can determine the required standard (i.e., target standard data) from the multiple standards to construct the first data frame and send it to the first device.

[0184] The method for determining the target system can be set as needed.

[0185] For example, the target standard can be determined based on the user's selection. The user can choose the desired standard, and the second device can determine the target standard based on the user's selection.

[0186] For example, the target standard can be adaptively determined based on the performance of the first device.

[0187] The above are merely examples; the target standard can also be determined in other ways, and this application does not limit this.

[0188] Optionally, the second memory can be an external memory. For example, the external memory can be flash memory or a hard disk.

[0189] In the embodiments of this application, the format information can be stored in an external memory. After power-on, the second device can read the required format information (such as the target format) from the external memory. This allows for more convenient adjustment or customization of the format information to better meet user needs. For example, if the first data frame is constructed during the bootrom stage, obtaining the format information from the external memory helps avoid the rigidity of ROM-based systems, enabling flexible support for multiple image formats to better meet user needs. Furthermore, the external memory has a larger storage space, which is beneficial for storing more format information, thereby facilitating comprehensive coverage of all formats and better meeting user needs.

[0190] Further, optionally, if the target format meets the preset conditions, step 420 is executed.

[0191] If the target system does not meet the preset conditions, step 420 can be skipped. Alternatively, if the target system does not meet the preset conditions, the standard boot screen display scheme can be executed.

[0192] Optionally, the target standard meeting preset conditions may include: the target standard belongs to a standard set. The standard set includes one or more standards.

[0193] If the target standard belongs to the standard set, proceed to step 420; if the target standard does not belong to the standard set, skip the transmission of the first data frame.

[0194] Alternatively, it can be understood as follows.

[0195] If the target system is the first system, proceed to step 420; if the target system is the second system, skip step 420. The first and second systems are different.

[0196] In other words, if the format of the second screen is certain, step 420 can be executed; if the format of the second screen is other, step 420 can be skipped.

[0197] The first system type belongs to the set of system types, while the second system type does not belong to the set of system types.

[0198] For example, the standards set may include one or more standards supported by the second device during the construction of the first data frame.

[0199] For example, after the second device is powered on, the target standard can be read. If the second device supports the target standard, a first data frame is constructed and sent to the first device. If the second device does not support the target standard, the transmission of the first data frame is skipped, and step 430 is executed.

[0200] Taking the sending of the first data frame during the bootrom stage as an example, that is, during the execution of the ROM firmware, the standard set can, for instance, include all standards supported by the ROM firmware. If the ROM firmware cannot support the target standard, the sending of the first data frame can be skipped.

[0201] The contents of the ROM are generally immutable, while the contents of the bootloader can be modified. For standards that the ROM firmware cannot support, the bootloader can provide support.

[0202] In the solution of this application embodiment, if the target standard meets the preset conditions, for example, the second device currently supports the target standard, then the first data frame is sent. If the target standard does not meet the preset conditions, for example, the second device currently cannot support the target standard, then the sending of the first data frame can be skipped, and the conventional boot screen display scheme can be executed. This is beneficial to improving compatibility, thereby helping to ensure user experience.

[0203] The second data frame will be explained below using the example of the first signal being a wake-up signal.

[0204] The wake-up interface can be customized as needed.

[0205] For example, the wake-up interface can be the user interface before the second device enters standby mode, or the user interface that controls the display of the first device before the second device enters standby mode.

[0206] Alternatively, the wake-up screen can be a pre-set screen. The method for setting a pre-set screen is similar to that for setting the boot screen, and will not be repeated here.

[0207] The solution implemented in this application reduces the image rendering time by approximately 500ms in a standby wake-up scenario.

[0208] The following example, taking the scenario of an electronic device powering on, provides an exemplary description of the solution in this application.

[0209] Figure 5 A schematic diagram of a screen display control method according to an embodiment of this application is shown. Figure 5 The scheme shown can be regarded as Figure 4 The method shown has two specific implementations. For example, in... Figure 5 In the illustrated scheme, the second device and the first device can be connected via HDMI, and data frames can be sent via timing signals. HDMI RX class devices (such as the first device) rely on timing signals to display the power-on logo.

[0210] The second data frame may include the boot logo, i.e. Figure 5 The logo frame timing signal in the data. The first data frame can be a black frame, i.e. Figure 5 The black frame in the image represents the timing signal. This is just an example; the black frame can be replaced with other non-logo frames. The timing signal is transmitted based on HSYNC and VSYNC.

[0211] For example, such as Figure 5 As shown, the boot process of the second device can include three stages: the bootrom stage, the auxcode stage, and the bootloader stage.

[0212] like Figure 5 As shown in (a), the second device can send a black frame timing signal to the first device during the bootrom stage to trigger the first device to enter the working mode, and send a logo frame timing signal to the first device during the bootloader stage.

[0213] exist Figure 5In the scheme shown in (a), the driver on which the timing signal depends is executed earlier in the bootrom process. For example, the driver on which the timing signal depends may include HDMI TX and VDP drivers. The HDMI TX and VDP drivers can construct the black frame timing signal. This allows the timing signal to be sent earlier, at the bootrom stage.

[0214] The first device enters working mode after receiving the black frame timing signal, for example, as follows: Figure 5 As shown in (a), clock locking and other operations begin. The process of the first device entering operating mode can be referenced. Figure 2 or Figure 3 The relevant descriptions will not be repeated here.

[0215] In this case, the boot logo will take approximately T seconds to load. clock_lock +T timing_stable +T display Compared to Figure 3 The proposed scheme Figure 5 The scheme shown in (a) significantly reduces the output time without increasing costs. Furthermore, the initialization of the RX side does not need to wait until the bootloader system initialization is complete, which helps ensure stable output time.

[0216] Optionally, the format of the boot screen can be stored in external memory. The second device can read the required format information (i.e., the target format) from external memory (such as flash) during the bootrom stage.

[0217] By storing the standard in external memory and reading the required standard from external memory during the bootrom stage, the rigidity caused by ROM-based systems is avoided, which facilitates the modification and customization of the standard and thus improves the user experience.

[0218] Optionally, the encoded data for the boot screen can be stored in external memory. The second device can read the required encoded data (i.e., target encoded data) from external memory (such as flash) during the bootloader stage.

[0219] Further, the encoded data is decoded to obtain the boot screen. This boot screen is then sent via the logo frame timing signal.

[0220] like Figure 5 As shown in (b), the second device can send a black frame timing signal to the first device during the auxcode stage to trigger the first device to enter the working mode, and send a logo frame timing signal to the first device during the bootloader stage.

[0221] exist Figure 5 In the scheme shown in (b), the driver on which the timing signal depends is executed earlier than the auxcode stage. In this way, the timing of the timing signal can be advanced to the auxcode stage.

[0222] The first device enters working mode after receiving the black frame timing signal, for example, as follows: Figure 5 As shown in (b), clock locking and other operations are started.

[0223] In this case, the boot logo will take approximately T seconds to load. bootrom +T clock_lock +T timing_stable +T display Compared to Figure 3 The proposed scheme Figure 5 The scheme shown in (b) significantly reduces the output time without increasing costs. Furthermore, the initialization of the RX side does not need to wait until the bootloader system initialization is complete, which helps ensure stable output time.

[0224] Optionally, the format of the boot screen can be stored in external memory. The second device can read the required format information (i.e., the target format) from external memory (such as flash) during the auxcode stage.

[0225] In the solution of this application embodiment, the standard is stored in external memory, and the required standard is read from external memory during the auxcode stage. This facilitates the modification and customization of the standard, thereby improving the user experience.

[0226] Optionally, the encoded data for the boot screen can be stored in external memory. The second device can read the required encoded data (i.e., target encoded data) from external memory (such as flash) during the bootloader stage.

[0227] Further, the encoded data is decoded to obtain the boot screen. This boot screen is then sent via the logo frame timing signal.

[0228] Figure 5 Scheme (b) and Figure 5 The main difference between scheme (a) and scheme (b) lies in the timing of the black frame timing signal transmission; other descriptions can be found in [reference needed]. Figure 5 To avoid repetition, the description of (a) will not be repeated here.

[0229] exist Figure 5In the illustrated scheme, the sending and decoding operations of the timing signal used to trigger the first device to enter the working mode can be separated. Taking advantage of the time-consuming image output of the first device, the timing signal is sent in advance. Thus, while the first device is entering the working mode, the second device performs decoding and other operations in parallel, completing the preparation work for the boot screen in parallel, thereby shortening the time for the boot logo to be displayed.

[0230] The following is combined with Figure 6 and Figure 7 right Figure 5 The implementation process of the two schemes is illustrated by example.

[0231] Figure 6 for Figure 5 This is a specific implementation of the scheme shown in (a). The black frame timing signal is issued during the bootrom stage, which can be understood as deploying the scheme of this application embodiment in the ROM firmware.

[0232] The second device executes the bootrom first after power-on. For example, ... Figure 6 As shown, the bootrom stage may include the following operations.

[0233] 11) Decryption verification related to format image: Verify the integrity and validity of the boot image file.

[0234] 12) Read the target standard from the flash, construct the black frame timing signal through the HDMI TX&VDP driver, and send the black frame timing signal to the second device.

[0235] If timing parsing fails, meaning the ROM firmware does not support the target standard, then the black frame timing signal will be skipped.

[0236] 13) Decryption verification related to auxcode to verify the integrity and validity of the auxiliary code.

[0237] Next, the auxcode phase, or RAM firmware, is executed. The auxcode phase is the execution process of the RAM firmware. For example, ... Figure 6 As shown, the auxcode stage can include the following operations.

[0238] 21) Boot table initialization, that is, initializing the boot table to prepare for the subsequent boot process.

[0239] 22) DDR initialization: Ensure the memory system is working properly.

[0240] Then return to bootrom and perform decryption verification related to the bootloader: verify the integrity and validity of the bootloader.

[0241] Then the bootloader is executed. The bootloader stage is the execution process of the bootloader. For example, as... Figure 6 As shown, the bootloader stage can include the following operations.

[0242] 31) System initialization (systeminit) includes configuring hardware and initializing peripherals.

[0243] 32) Image Decoding: The boot logo image is obtained by performing image decoding using an image decoder. The boot logo image can be used to construct the logo frame timing signal.

[0244] For example, such as Figure 6 As shown, the encoded data of the boot logo can be read from the flash memory, and the boot logo image is obtained after image decoding.

[0245] For example, encoded data can be in JPEG format, and image decoding is JPEG decoding.

[0246] 33) Send the logo frame timing signal to the first device.

[0247] Figure 7 for Figure 5 This is a specific implementation of the scheme shown in (b). The black frame timing signal is issued during the auxcode stage, which can be understood as deploying the scheme of this application embodiment in the RAM firmware. Figure 6 and Figure 7 The main difference between the two schemes is that, Figure 6 In the illustrated scheme, the HDMI TX & VDP drivers are executed during the bootrom stage. Correspondingly, the target standard reading and the transmission of the black frame timing signal are both executed during the bootrom stage. Figure 7 In the illustrated scheme, the HDMI TX & VDP drivers are executed during the auxcode stage. Correspondingly, the target standard reading and the transmission of the black frame timing signal are also performed during the auxcode stage. Further details can be found in [reference needed]. Figure 6 To avoid repetition, the relevant descriptions will not be repeated here.

[0248] Figure 8 A schematic diagram of a standby wake-up scenario according to an embodiment of this application is shown. Figure 8 and Figure 5The main difference in the proposed solution is that the logo frame timing signal is replaced with a timing signal that carries the wake-up interface (such as...). Figure 8 (The wake-up interface timing signal). The method for obtaining the wake-up interface can be found in the description in method 400.

[0249] Other descriptions can be found in the following text. Figure 5 To avoid repetition, the relevant descriptions will not be repeated here.

[0250] The following is combined with Figures 9 to 10 The apparatus of the embodiments of this application will be described below. It should be understood that the apparatus described below is capable of performing the methods of the foregoing embodiments of this application. To avoid unnecessary repetition, repeated descriptions will be appropriately omitted when describing the apparatus of the embodiments of this application below.

[0251] Figure 9 A schematic block diagram of the apparatus provided in an embodiment of this application is shown. Figure 9 The apparatus 1800 shown can be used to perform the methods of the embodiments of this application, for example, Figure 4 The method is illustrated. The steps in the above method can be implemented by hardware, or by software or by software executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0252] like Figure 9 As shown, the device 1800 may include a receiving module 1810 and a transmitting module 1820. The receiving module 1810 and the transmitting module 1820 are coupled together.

[0253] The receiving module 1810 is used to receive a first signal, wherein the first signal includes a power-on signal or a wake-up signal.

[0254] The sending module 1820 is used to send a first data frame to the first device, and the first data frame is used to indicate the first screen.

[0255] The sending module 1820 is also used to send a second data frame to the first device. The second data frame is used to indicate a second screen, which includes a power-on screen or a wake-up interface, and the first screen and the second screen are different.

[0256] Optionally, the first data frame is used to trigger the first device to perform a clock locking operation.

[0257] Optionally, the format of the first screen and the format of the second screen are the same.

[0258] Optionally, the device 1800 further includes a reading module for reading the format of the second screen from an external memory.

[0259] Optionally, the sending module 1820 is specifically used to: send a first data frame to the first device when the format of the second screen is the first format, and skip sending the first data frame when the format of the second screen is the second format, wherein the first format and the second format are different.

[0260] Optionally, the first frame is a black frame.

[0261] Optionally, the sending module 1820 is specifically used to: send a first data frame to the first device via the high-definition multimedia interface (HDMI); and send a second data frame to the first device via the HDMI interface.

[0262] For a detailed description, please refer to Method 400 above; it will not be repeated here.

[0263] It should be noted that the division of units in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. In other embodiments, the sending module 1820 can be used to execute any step in the method described above, and other modules can be used to implement any step in the method described above. The steps that each module is responsible for implementing can be specified as needed. By having each module implement different steps in the method described above, all functions of the device 1800 can be achieved.

[0264] Figure 10 This is a schematic block diagram of another device provided in an embodiment of this application. Device 1900 may include a processor 1910, a transceiver 1920, and a memory 1930. The processor 1910, transceiver 1920, and memory 1930 are connected via internal interconnection paths. The memory 1930 is used to store instructions, and the processor 1910 is used to execute the instructions stored in the memory 1930 to receive / send data via the transceiver 1920. Optionally, the memory 1930 may be coupled to the processor 1910 via an interface or integrated with the processor 1910.

[0265] It should be noted that the transceiver 1920 mentioned above may include, but is not limited to, transceiver devices such as input / output interfaces, to enable communication between device 1900 and other devices or communication networks.

[0266] The memory 1930 can be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM).

[0267] In one implementation, the processor 1910 can be a circuit with instruction read and execute capabilities, such as a central processing unit (CPU), microprocessor, or digital signal processor (DSP). In another implementation, the processor 1910 can implement certain functions through the logical relationships of hardware circuits. These logical relationships can be fixed or reconfigurable. For example, the processor 1910 can be a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as a field-programmable gate array (FPGA). In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the processor loading instructions to implement some or all of the functions of the aforementioned units.

[0268] This application also provides an electronic device. This electronic device may include the aforementioned device 1800, or device 1900. For example, the electronic device may be an STB, a laptop computer, a PC, a game console, a tablet computer, or a mobile phone, etc.

[0269] This application also provides a computer program product, which includes computer program code that, when run on a computer, causes the computer to perform the methods described in the above embodiments.

[0270] This application also provides a computer-readable medium storing program code that, when run on a computer, causes the computer to perform the methods described in the above embodiments.

[0271] This application also provides a chip, including a processor and a memory connected together. The memory stores computer execution instructions. When the chip is running, the processor can execute the computer execution instructions stored in the memory to cause the chip to perform the methods described in the above-described method embodiments.

[0272] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules within the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, power-on erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0273] It should also be understood that, in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0274] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

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

[0276] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0277] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0278] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

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

Claims

1. A method for controlling screen display, characterized in that, include: Receive a first signal, wherein the first signal includes a power-on signal or a wake-up signal; Send a first data frame to the first device, the first data frame being used to indicate the first screen; A second data frame is sent to the first device, wherein the second data frame is used to indicate a second screen, the second screen including a power-on screen or a wake-up interface, and the first screen and the second screen are different.

2. The control method according to claim 1, characterized in that, The first data frame is used to trigger the first device to perform a clock locking operation.

3. The control method according to claim 1 or 2, characterized in that, The format of the first screen is the same as that of the second screen.

4. The control method according to claim 3, characterized in that, The control method further includes: Read the format of the second screen from external memory.

5. The control method according to claim 4, characterized in that, Sending the first data frame to the first device includes: When the format of the second screen is the first format, the first data frame is sent to the first device, and If the format of the second screen is the second format, the transmission of the first data frame is skipped, since the first format and the second format are different.

6. The control method according to any one of claims 1 to 5, characterized in that, The first frame is a black frame.

7. The control method according to any one of claims 1 to 6, characterized in that, Sending the first data frame to the first device includes: sending the first data frame to the first device via an HDMI (High-Definition Multimedia Interface); and Sending the second data frame to the first device includes: The second data frame is sent to the first device via the HDMI interface.

8. A control device for screen display, characterized in that, include: A receiving module is configured to receive a first signal, wherein the first signal includes a power-on signal or a wake-up signal; The sending module is used for: Send a first data frame to the first device, the first data frame being used to indicate the first screen; A second data frame is sent to the first device, wherein the second data frame is used to indicate a second screen, the second screen including a power-on screen or a wake-up interface, and the first screen and the second screen are different.

9. The control device according to claim 8, characterized in that, The first data frame is used to trigger the first device to perform a clock locking operation.

10. The control device according to claim 8 or 9, characterized in that, The format of the first screen is the same as that of the second screen.

11. The control device according to claim 10, characterized in that, The control device further includes a reading module for reading the format of the second screen from an external memory.

12. The control device according to claim 11, characterized in that, The sending module is specifically used for: When the format of the second screen is the first format, the first data frame is sent to the first device, and If the format of the second screen is the second format, the transmission of the first data frame is skipped, since the first format and the second format are different.

13. The control device according to any one of claims 8 to 12, characterized in that, The first frame is a black frame.

14. The control device according to any one of claims 8 to 13, characterized in that, The sending module is specifically used for: The first data frame is sent to the first device via the high-definition multimedia interface (HDMI). The second data frame is sent to the first device via the HDMI interface.

15. An electronic device, characterized in that, It includes a processor and a memory, the processor being configured to execute instructions stored in the memory to cause the electronic device to perform the method as described in any one of claims 1 to 7.

16. A computer program product containing instructions, characterized in that, When the instructions are executed by the computing device, the computing device performs the method as described in any one of claims 1 to 7.

17. A computer-readable storage medium, characterized in that, It includes computer program instructions, which, when executed by a computing device, cause the computing device to perform the method as described in any one of claims 1 to 7.

Images