A method for starting up and an intelligent television

Abstract

The application provides a starting method of a smart TV, comprising: starting an operating system of the smart TV in response to a starting instruction; starting a home page set by the operating system according to a home page active component registered in a registry during the starting process of the operating system; receiving an instruction of starting a target application sent by a peripheral device in the case of inserting the peripheral device; and starting the target application as a foreground application in response to the instruction of starting the target application; and maintaining the home page set by the operating system as a foreground application in the case of not inserting the peripheral device.

Description

Technical Field

[0001] This application belongs to the field of display technology, and in particular relates to a power-on startup method for smart TVs and a smart TV. Background Technology

[0002] In display technology, smart TVs typically start up by displaying the homepage based on a default signal source. In some implementations, the homepage can be automatically accessed after startup by using the system's built-in software signal source or a physical signal source.

[0003] In some embodiments, a third-party application can be used to modify the smart TV's Home page. Upon power-on, the user will automatically navigate to the third-party application as the homepage. Summary of the Invention

[0004] This application provides a power-on startup method for a smart TV and a smart TV.

[0005] Firstly, this application provides a power-on startup method for smart TVs, comprising: In response to the power-on command, the operating system of the smart TV is launched; During the startup process of the operating system, the homepage set by the operating system is launched according to the homepage activity component registered in the registry; When a peripheral device is inserted, the system receives an instruction from the peripheral device to launch a target application; and in response to the instruction to launch the target application, launches the target application as a foreground application, wherein the target application is an application adapted to the peripheral device, the peripheral device is connected to the smart TV through a physical interface, and the peripheral device is configured to be powered on and started in a controlled manner during the startup process of the smart TV's operating system. Without the external device being inserted, the operating system's homepage is maintained as the foreground application.

[0006] Secondly, this application provides a method for powering on and starting up a smart TV, including: In response to a power-on command sent by the remote control, the operating system of the smart TV is started. The power-on command is a command issued by the remote control after the first press of the first button, instructing the smart TV to power on. During the startup process of the operating system, the homepage set by the operating system is launched according to the homepage activity component registered in the registry; The remote controller receives a command to launch a target application, wherein the command to launch the target application is sent by the remote controller in response to the first press after a preset delay. In response to the instruction to launch the target application, the target application is launched as a foreground application.

[0007] Thirdly, this application provides a method for starting an external device, wherein the external device is installed in a smart TV, the method comprising: Receive and start a power-on command, wherein the power-on command is issued by the smart TV during the startup of the smart TV's operating system, and the smart TV is configured to start the homepage set by the operating system according to the homepage activity component registered in the registry during the startup of the operating system; After a set time has elapsed since startup, a command to launch the target application is sent, causing the smart TV to launch the target application as a foreground application and overwrite the homepage set by the operating system. The target application is an application adapted to the peripheral device. The set time elapsed ensures that the smart TV receives the command to launch the target application after the operating system's AMS has finished starting.

[0008] Fourthly, this application provides a smart TV, comprising: a display; a system-on-a-chip (SoC); said SoC is configured to perform the method described in the first or second aspect.

[0009] Fifthly, this application provides an external device that connects to a smart TV via a physical interface, characterized in that the external device includes a processor for executing the method described in the third aspect.

[0010] This solution utilizes a smart TV's operating system startup process. During startup, the TV uses the HOME Activity registered in the registry to launch the homepage set by the operating system. When a peripheral device connected via a physical interface is detected, the TV obtains the command to launch the target application from that device and launches it as the foreground application. When no peripheral device is detected, the operating system's homepage is maintained as the foreground application. This solves the problem in existing technologies where stable and direct launch of applications compatible with peripheral devices after startup is impossible without modifying the TV's system software. In one implementation, this could be a cable TV application corresponding to a cable TV dongle; in other implementations, it could be a karaoke application corresponding to a microphone Bluetooth dongle. By making peripheral device recognition a necessary prerequisite for receiving the startup command, whether the target application is launched depends entirely on whether the peripheral device is plugged in. This achieves flexible startup path control: "launch the target application if a peripheral device is present, default to launching the homepage if no peripheral device is present." This allows for flexible switching between launching the target application or the default homepage upon plugging in or unplugging the peripheral device. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0012] Figure 1 This is a schematic diagram illustrating an operational scenario between a smart TV and a control device, provided in some embodiments of this application. Figure 2 A schematic diagram of the hardware configuration of a smart TV provided in some embodiments of this application; Figure 3 The present application provides a method for powering on and starting up a smart TV in some embodiments; Figure 4 Security verification steps for smart TVs provided in some embodiments of this application; Figure 5 The present application provides a method for powering on and starting up a smart TV in some embodiments; Figure 6 This application provides an example of a method for starting up a peripheral device; Figure 7 This application provides yet another method for powering on a smart TV, based on some embodiments thereof. Detailed Implementation

[0013] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without inventive effort are within the scope of protection of this application.

[0014] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application can also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods are omitted so as not to obscure the description of this application with unnecessary detail.

[0015] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0016] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0017] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0018] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized.

[0019] Figure 1 This is a schematic diagram illustrating an operational scenario between a display device and a control device provided in some embodiments of this application. For example... Figure 1 As shown, users can operate the smart TV 200 via touch operation, mobile terminal 300, and control device 100. For example, control device 100 can be a remote control, stylus, gamepad, etc.

[0020] The mobile terminal 300 can function as a control device for human-computer interaction between the user and the smart TV 200. It can also function as a communication device for establishing a communication connection with the smart TV 200 and exchanging data. In some embodiments, the mobile terminal 300 can have software applications installed on it and communicate with the smart TV 200 via network communication protocols to achieve one-to-one control and data communication. It can also transmit audio and video content displayed on the mobile terminal 300 to the smart TV 200 for synchronized display.

[0021] like Figure 1 The document also shows that the smart TV 200 communicates with the server 400 via various communication methods. This allows the smart TV 200 to connect and communicate via a local area network (LAN), a wireless local area network (WLAN), and other networks.

[0022] The Smart TV 200 can provide broadcast television reception and can also be equipped with smart network TV functions that provide computer support.

[0023] Figure 2 Provided for some embodiments of this application Figure 1 Hardware configuration block diagram of the Zhongzhi Smart TV 200.

[0024] In some embodiments, the smart TV 200 may include at least one of the following: a tuner 210, a communication device 220, a detector 230, a device interface 240, a controller 250, a display 260, an audio output device 270, a memory, a power supply, and a user input interface.

[0025] The smart TV mentioned in this application specification is a TV that can connect to the Internet, run its own operating system, and has its own software signal source application.

[0026] The homepage of the operating system mentioned in this application refers to the homepage (HOME page) that the smart TV enters after it is turned on. In some existing technologies, when the software signal source application is used as the default Home option, the HOME page can be the homepage of the default software signal source application of the smart TV. When the physical signal source is used as the default Home option, it can also be the page corresponding to the HDMI interface as the signal source or the page corresponding to the other physical interface as the signal source.

[0027] The existing technology allows the HOME page to be set in the following way: After the operating system's AMS starts, the corresponding home page is launched through the home page activity component registered in the registry. In some smart TVs, a default signal source can be set or the signal source at the last shutdown can be used as the default signal source. When the default signal source is set, the HomeActivity corresponding to that signal source will be registered as the default in the registry so that the HOME page can be launched automatically the next time it is started.

[0028] This method relies on system or user presets. This application provides an alternative method for launching a target application upon startup. It determines whether to launch the target application based solely on the insertion or absence of a peripheral device. No system or user presets are required.

[0029] This application provides a boot-up method for smart TVs in several embodiments. In some scenarios, a user inserts a peripheral device into the smart TV's physical interface, presses the power button on the remote, and the smart TV's operating system boots up and directly displays the application interface of the target application corresponding to the peripheral device, such as the homepage of a cable TV application or a karaoke application. When the user no longer needs to access the target application upon boot, they simply remove the peripheral device from the physical interface, and the smart TV will revert to the normal operating system homepage upon the next boot, such as the JUUI homepage or the HDMI page.

[0030] In smart TVs, software signal source applications and cable TV content service applications run independently on the TV operating system. In related technologies, users need to enter the homepage set by the system before launching the target application to watch its content, which is complicated.

[0031] When the target application is cable TV, traditional all-in-one TV solutions require the set-top box function to be built into the TV hardware, which modifies the entire system and increases hardware certification costs. Furthermore, they cannot flexibly specify the cable TV application that starts up when the TV is turned on.

[0032] Some existing technologies involve installing a desktop launcher, setting the launcher as a HOME item for startup, and then selecting the corresponding application to launch after the launcher starts.

[0033] Some embodiments of this application provide a method for launching a fixed homepage via an external device. Without modifying the existing TV system SDK or changing the system's default homepage application settings, the method enables direct access to the specified application upon startup by receiving a command from the external device to launch the target application.

[0034] During operating system startup, the homepage set by the operating system is launched based on the homepage activity components registered in the registry. Simultaneously, the system's built-in input source management service executes a standardized hardware scanning process. Once a peripheral device is detected and its command is received, the command is mapped to a system-level application launch operation, launching the target application and placing it in the foreground. If no peripheral device is detected, the operating system's homepage is maintained as the foreground application.

[0035] This dual-path design, which starts the target application when there is a peripheral device and keeps the default homepage when there is no peripheral device, externalizes the decision-making power of starting the target application at boot to a pluggable physical device, providing a low-cost, highly adaptable, and quick-deployment solution.

[0036] Please refer to the attached document. Figure 1 This application provides a smart TV. As a display terminal, the smart TV is equipped with an operating system. The operating system reinstalls software signal source applications and target applications, and can also receive and display audio and video content from various physical signal sources. In one working state, after the smart TV is powered on, it loads and displays the software signal source applications (such as JUUI applications) set by the operating system as the homepage. The homepage aggregates various internet audio-visual content and application entry points.

[0037] In some implementations, a smart TV includes basic hardware such as a system-on-a-chip (SoC), memory, and a display. The SoC is configured to execute an operating system and various applications stored in the memory. The display, under the control of the SoC and the operating system, presents images and a user interface to the user. A smart TV has multiple physical interfaces for connecting external hardware devices to expand its functionality. These physical interfaces include a Universal Serial Bus (USB) interface and a High-Definition Multimedia Interface (HDMI).

[0038] In some implementations, the system-on-a-chip is configured to execute a bootloader, load the operating system kernel, and start system service processes containing framework-layer system services upon power-up. These framework-layer system services include at least a TV Input Service for managing input source switching, an Activity Manager Service (AMS) for managing active components, a Package Manager Service for managing application package information, a Window Manager Service for managing window display, and an Interface Manager Service for managing physical interface connections.

[0039] In some implementations, the memory stores the software source application, the target application, the system firmware, and the system security configuration file. The software source application declares a desktop activity category identifier in its activity manifest file to be scheduled by the system activity manager and occupy the foreground interface after the smart TV system starts up. The target application is a target application that needs to be quickly launched by triggering from an external device, and its activity manifest file does not declare a desktop activity category identifier.

[0040] In some implementations, the Universal Serial Bus interface and the High Definition Multimedia interface are used to connect corresponding types of physical interface peripherals.

[0041] In some embodiments, such as Figure 3 As shown in steps S401-S404, in response to the power-on command, the smart TV starts the operating system. During the operating system startup process, the homepage set by the operating system is launched according to the homepage active component registered in the registry. Simultaneously, if a peripheral device connected via a physical interface is inserted, an instruction to launch a target application sent by the peripheral device is received, and in response to this instruction, the target application is launched as the foreground application, wherein the target application is an application compatible with the peripheral device. If no peripheral device is inserted, the homepage set by the operating system is maintained as the foreground application.

[0042] This solution utilizes a smart TV's operating system startup process. During startup, the TV uses the Home Activity registered in the registry to launch the homepage set by the operating system. When a peripheral device connected via a physical interface is detected, the system obtains the command to launch the target application from that device and launches it as the foreground application. When no peripheral device is detected, the operating system's homepage is maintained as the foreground application. This solves the problem in existing technologies where stable and direct launch of applications compatible with peripheral devices after startup is impossible without modifying the TV's system software. In one implementation, this could be a cable TV application corresponding to a cable TV dongle; in other implementations, it could be a karaoke application corresponding to a microphone Bluetooth dongle. By making peripheral device recognition a necessary prerequisite for receiving the startup command, the launch of the target application depends entirely on whether a peripheral device is plugged in. This achieves flexible startup path control: "launch the target application when a peripheral device is present, default to launching the homepage when no peripheral device is present." This allows for flexible switching between the target application and the default homepage upon startup simply by plugging and unplugging the peripheral device. In some embodiments, whether the target application is launched depends entirely on whether an instruction to launch the target application is received from a peripheral device, which facilitates flexible boot path control by launching the target application when a peripheral device is available and launching the homepage by default when no peripheral device is available.

[0043] In some embodiments, the smart TV boots up its operating system in response to a power-on command, including: In response to the power-on command, power is supplied and the bootloader is loaded. The bootloader initializes and loads the kernel into RAM. Subsequently, the kernel starts, driving the USB power-on and init / Zygote startup. After Zygote starts SystemServer, SystemServer starts core services such as AMS (component management), UsbService (USB device management), and BluetoothManagerService (Bluetooth management). After the system services are ready, AMS starts an "Home" type Activity (Intent.CATEGORY_HOME). If the application with the default Home attribute on the smart TV is a JUUI application, the corresponding Activity is started through AMS. After the Activity starts, the user enters the default home page of this JUUI application.

[0044] In some embodiments, the improved scheme does not adjust the startup logic of the software signal source, which allows older televisions to be compatible with the scheme of launching the target application through a peripheral device without modifying the television hardware or making major adjustments to the software.

[0045] In some embodiments, receiving an instruction to launch a target application sent by a peripheral device includes: receiving an instruction to launch a target application, wherein the instruction to launch a target application is generated and sent by the peripheral device based on component information of the target application internally stored therein, and the component information includes at least identification information characterizing the target application.

[0046] In some embodiments, the peripheral device is plugged into the smart TV via a Universal Serial Bus (USB) interface. The peripheral device's internal memory stores component information of the target application, including at least identification information characterizing the target application. For example, this identification information may be the package name of the target application, and may also include the name of the target application's target active component. For instance, when the target application is a cable TV application, the stored component information corresponds to the startup active component of that cable TV application. This peripheral device is a hardware device adapted to the target application; different target applications correspond to different peripheral devices.

[0047] In some embodiments, such as Figure 6 As shown in steps S501-S502, the peripheral device is powered on and started under control during the startup process of the smart TV's operating system. After a set time has elapsed since startup, a command to launch the target application is sent, causing the smart TV to launch the target application as the foreground application and overwrite the homepage set by the operating system.

[0048] In some embodiments, when the input source management service module in the smart TV operating system scans and identifies the peripheral device and establishes a data communication channel, the peripheral device generates an instruction to launch the target application based on its internally embedded component information and sends the instruction to the smart TV.

[0049] In some implementations, component information within the peripheral device is permanently written into a read-only memory or an electrically erasable programmable read-only memory during the device manufacturing stage. After the peripheral device is powered on, it sends a command to launch the target application to the smart TV. In some embodiments, after the peripheral device is powered on, it sends the command to launch the target application to the smart TV for a predetermined period of time. This predetermined period ensures that the smart TV receives the command to launch the target application after the operating system's Active Directory (AMS) has finished booting.

[0050] In some embodiments, the sending of the set duration is achieved through a timer, which is automatically set after the peripheral device is started. The duration of the timer is determined based on a preset duration, which is determined after research on numerous smart TVs, to ensure that the smart TV receives the instruction to launch the target application after the AMS of the operating system is started.

[0051] In some embodiments, the peripheral device generates a command to launch a target application based on internally stored component information, and determines whether a timer has expired. If the timer has not expired, the command to launch the target application is not sent; if the timer has expired, the command to launch the target application is sent. The component information includes at least identification information representing the target application, so that the command to launch the target application includes the identification information representing the target application.

[0052] In some embodiments, the peripheral device determines whether the timer has ended. If it has not ended, it does not generate an instruction to start the target application based on the internal component information. If it has ended, it generates an instruction to start the target application based on the internal component information and sends the instruction to start the target application.

[0053] In some embodiments, launching the target application as a foreground application in response to the instruction to launch the target application includes: in response to receiving the instruction to launch the target application sent by the peripheral device, constructing an explicit instruction without a desktop activity category identifier based on the identifier information representing the target application in the instruction to launch the application, and launching the activity instance of the target application in a new independent task stack and placing it at the top of the foreground interface stack through the activity management service.

[0054] In some embodiments, when a peripheral device is inserted into a specified physical interface, the corresponding interface controller detects the physical connection, and the kernel driver layer generates a standard device event and reports it to the framework layer system service. An event listener instance within the framework layer system service captures this event.

[0055] In some embodiments, launching the target application as a foreground application in response to the instruction to launch the target application may include: after listening to an event, obtaining the target application's identification information from the event-associated information, encapsulating it into an application launch request, and passing it to the scheduling agent. The scheduling agent constructs an explicit instruction without a desktop activity category identifier and launches the target application's activity instance in a new independent task stack and places it on top of the foreground interface stack through the activity management service. The entire process achieves a complete closed loop from the peripheral device to the target application's interface presentation without modifying the software signal source application.

[0056] In some embodiments, the framework layer system services provided in this application include TV input management service, activity management service, package management service, window management service, and interface management service. The TV input management service is the core system service of the Android TV input framework, running within the system service process, and is responsible for managing the registration, switching, and lifecycle scheduling of all input sources in the smart TV. Input sources are categorized into hardware signal sources and software signal sources. Hardware signal sources are directly related to physical hardware, representing actual physical interfaces or built-in receivers on the TV, including HD Multimedia Interface, Universal Serial Bus Interface, and broadcast tuner. Software signal sources do not depend on specific hardware; they receive data via the network and are processed at the software level by applications running as TV input service components. The Internet TV homepage is a special type of software signal source. The interface management service includes Universal Serial Bus Service and HD Multimedia Control Service, responsible for connection management, device identification, and event distribution of Universal Serial Bus devices and HD Multimedia Interface devices, respectively. The activity management service is responsible for the lifecycle management and task stack scheduling of all activity components in the system. The package management service is responsible for the installation, uninstallation, and component information query of application packages. The window management service is responsible for the display hierarchy management and focus allocation of all windows. The TV input management service and the interface management service work together through an internal communication mechanism within the system service process. For example, when the Universal Serial Bus service detects a device insertion, the TV input management service can be triggered to update the input source status.

[0057] In some embodiments, because the event listening instance is registered in the process space of the TV input management service or interface management service during the initialization phase of the system service in this application, the event listening instance can run at the permission level of the system service, enabling it to access underlying device events and call the application interface of the activity management service. This deployment method avoids the limitations of setting up broadcast receivers or relying on accessibility services at the application layer, and the ability to perceive peripheral events is pushed down to the core service layer of the system, achieving the shortest triggering chain and the highest response priority. In one specific implementation, the event listening instance completes its registration during the initialization phase of the TV input management service, high-definition multimedia control service, or universal serial bus service in the system service process. After registration, it runs continuously in the process space of the host service in the form of a callback object or a listening thread, and its lifecycle is bound to the host service.

[0058] In some embodiments, the smart TV starts the operating system in response to a power-on command. During the operating system startup process, the activity management service constructs a main action after the system services are ready. This main action includes an intent for a homepage category to query matching homepage activity components via the package management service and, based on the homepage activity components registered in the registry, starts the homepage set by the operating system. Simultaneously, if a peripheral device connected via a physical interface is detected, an instruction to launch a target application sent by the peripheral device is received, and in response to this instruction, the target application is launched as the foreground application, wherein the target application is an application adapted to the peripheral device. If no peripheral device is detected, the homepage set by the operating system remains as the foreground application. By making peripheral device recognition a necessary prerequisite for receiving the startup command, whether the target application is launched depends entirely on whether a peripheral device is plugged in, achieving flexible startup path control where the target application launches when a peripheral device is present, and the homepage is launched by default when no peripheral device is present.

[0059] In one specific implementation, the operating system constructs explicit instructions for the target application and launches the target application's active component. Once the active component is launched, the window management service sets its window as the foreground window, thus overriding the homepage interface. This method utilizes the operating system's own activity management mechanism, does not involve intrusive modifications to the system framework, and offers good compatibility.

[0060] In some embodiments, within the smart TV provided in this application embodiment, the framework layer system service registers and starts an event listener instance pointing to a specified physical interface in its process space during initialization.

[0061] In some embodiments, the physical entity of an event listener instance is a broadcast receiver instance registered in the TV Input Management Service, High Definition Multimedia Control Service, or Universal Serial Bus Service, or a listener object that implements the Hardware Abstraction Layer callback interface. The event listener instance and the framework layer system service have a host-extension relationship; the lifecycle of the event listener instance is bound to the host system service, and it completes its registration and initialization in the final stage of the host service initialization. After registration, the event listener instance enters a passive listening state, without continuous polling, but is awakened based on an interrupt or event callback mechanism.

[0062] In some embodiments, the event listener instance obtains the target application's identification information from the captured events. The identification information includes the target application's package name and activity name, sufficient to uniquely identify a launchable activity component within the target application. In a specific implementation, the target application is a second-type application already installed on a smart TV, such as a cable TV application; its package name could be com.cabletv.app, and the activity name to be launched could be com.cabletv.app.MainActivity. In some embodiments, the event can be a command sent by a peripheral device to launch the target application.

[0063] In some embodiments, and in others, the identification information may also include other information that can locate a specific interface within the application, such as a custom URI scheme or a deep link path. This allows the launch screen of the target application to be configured via an external device. On the one hand, user preferences for the launch screen can be stored as configuration files on the external device, making it unrestricted by the television and allowing users to maintain their preferences even when the external device is moved to different televisions. On the other hand, the server can control the batch setting of launch screen styles through software, achieving standardization and adaptability to different television systems or different applications or versions on different televisions.

[0064] In some embodiments, launching the target application as a foreground application includes: launching a cable TV application; and reading pre-stored configuration information, wherein the configuration information represents different launch interfaces set by the user. This configuration information can be written by the user during use through a selection of a control button in the cable TV application. The target application can generate different launch interface modes based on the configuration information stored on the TV. This allows TV users to set the launch interface style of their current TV according to their personal preferences. Different TVs in a home, such as living room TVs, adult bedroom TVs, and children's bedroom TVs, can share the same peripheral device but can have different launch interfaces set according to their respective TVs.

[0065] In some embodiments, the event listener instance encapsulates identification information into an application launch request and passes it to the scheduling agent built into the framework layer system service. The scheduling agent and the event listener instance run in the same system service process space, and communicate with each other through in-process method calls or internal message passing. After receiving the application launch request, the scheduling agent constructs an explicit launch intent that clearly points to the target application and does not contain a desktop activity category identifier. The scheduling agent then uses the system activity manager to launch the activity instance of the target application pointed to by the explicit launch intent in a new independent task stack and places it on top of the foreground interface stack, so that it covers the homepage interface of the first type of software signal source system currently displayed on the smart TV.

[0066] The following section provides a detailed explanation of the working process of an event listener instance, using specific command acquisition methods as an example.

[0067] In some embodiments, the process by which the event listening instance obtains the identity information of the target application from the captured physical connection events adopts a method based on private protocol data parsing. Specifically, the event listening instance first verifies whether the peripheral device is a preset authorized device. When the peripheral device is a preset authorized device, the event listening instance reads the private protocol data transmitted by the peripheral device through the specified physical interface, and performs parsing and integrity verification on the private protocol data.

[0068] In some embodiments, after successful verification, the event listener instance extracts the package name and activity name of the target application from the command to launch the target application sent by the peripheral device. The command to launch the target application is generated and sent by the peripheral device based on internally embedded component information of the target application. This component information includes at least identification information representing the target application, such as the package name and activity name. The advantage of this approach lies in its dual filtering mechanism of authorization verification and integrity verification, ensuring the legitimacy of the command source and the correctness of the command data, effectively avoiding the risk of accidental launch due to unauthorized devices or data corruption.

[0069] In some embodiments, for implementations where the specified physical interface is a Universal Serial Bus (USB) interface, the peripheral is a USB device.

[0070] In some embodiments, the process of verifying whether a peripheral device is a preset authorized device specifically involves the event listener instance obtaining the vendor identifier and product identifier from the device descriptor of the UPS device after the UPS device is enumerated. The event listener instance compares the vendor identifier and product identifier with authorized device identifiers stored in a preset whitelist. Only when both the vendor identifier and product identifier match records in the preset whitelist is the UPS device determined to be a preset authorized device. The vendor identifier and product identifier are inherent identity information that the UPS protocol can obtain during the device enumeration phase, without the peripheral device actively sending additional identification data. For example, the preset whitelist can be stored in the system security configuration file, containing one or more pairs of vendor identifiers and product identifiers for authorized devices, such as a vendor identifier of 0x1234 and a product identifier of 0x5678. When the vendor identifier and product identifier of an inserted device completely match a pair in the whitelist, the device passes the first level of filtering. For devices not in the whitelist, the event listener instance does not perform any processing, returning control of the device to the original system service, which manages it as a standard UPS device.

[0071] In some embodiments, after device authorization verification, the event listener instance performs parsing and integrity verification of the private protocol data using a state machine-driven approach. Specifically, the event listener instance uses a state machine to perform synchronization header locking, payload length reading, instruction type and data payload extraction, and checksum comparison on the private protocol data. The frame structure of the private protocol data sequentially includes a preset synchronization header field, payload length field, instruction type field, data payload field, and checksum field. The synchronization header field is two bytes, fixed at 0xF0 and 0x0F, used for frame start positioning. The payload length field is one byte, an unsigned integer, representing the total number of bytes in the subsequent instruction type field and data payload field. The instruction type field is one byte, for example, 0x01 indicates an application start instruction. The data payload field is of variable length, carrying the target application's package name and activity name in a length-encoded format. The encoding format is one byte of the package name string length plus a byte sequence of the package name string, followed by one byte of the activity name string length plus a byte sequence of the activity name string. After obtaining the identifier representing the target application, the smart TV starts the target application after a predetermined delay.

[0072] In other embodiments, the event listening instance obtains the target application's identity information from the captured physical connection events using a direct reading method based on port binding configuration. Specifically, after capturing a physical connection event on a specified physical interface, the event listening instance reads the preset port binding configuration in the smart TV. The event listening instance directly obtains the package name and activity name of the target application uniquely bound to the specified physical interface from the port binding configuration. This method skips the parsing step of peripheral device data transmission, treating the generation of the physical connection event itself as a complete startup command, without requiring the peripheral device to have any data sending capabilities. The port binding configuration can be stored in the system property service or the system's built-in configuration file in the form of key-value pairs. The configuration item maps a specific physical interface identifier to a target application's package name and activity name. For example, the specified high-definition multimedia interface identifier is HDMI1, and the corresponding bound target application package name is com.cabletv.app, and the activity name is com.cabletv.app.MainActivity. After capturing the port connection event, the event listening instance can directly read the corresponding binding value based on the interface identifier to obtain the target application's identity information. This implementation breaks away from the traditional mindset that information transmission must rely on peripherals actively sending data payloads. It minimizes the hardware performance requirements of peripherals, requiring only physical connections and basic electrical responses. This achieves zero data payload and startup triggering driven solely by physical connection state transitions. After obtaining the identifier representing the target application, the smart TV starts the target application after a predetermined delay.

[0073] In some embodiments, maintaining the operating system's homepage as the foreground application when no peripheral device is inserted can be achieved by the TV input service not detecting any peripheral devices during the scanning process. Therefore, the TV input service only performs default operations such as creating input source records for regular devices, and the operating system's startup process proceeds independently without interference. After the activity management service completes initialization, it queries the package management service for a matching default homepage activity component and starts that component. The system-defined homepage activity component undergoes a normal startup and recovery lifecycle, is displayed on the screen by the window management service, and remains as the foreground application. The user sees the standard smart TV system desktop.

[0074] In some implementations, where the target application is a cable TV application that provides the reception and playback of live cable TV content, the peripheral device is manufactured as supporting hardware provided by the cable TV service operator. After applying for or purchasing the hardware, users only need to plug it into a smart TV to watch cable TV directly upon startup.

[0075] In some implementations, the peripheral device acts as a carrier for embedding and externalizing the boot-up decision information. This ensures that regardless of any configuration information (software signal source application, HDMI signal source, etc.) stored on the smart TV side, the smart TV will automatically launch the target application upon boot. If the user removes the peripheral device, the smart TV will not receive the instruction to launch the target application upon the next boot and will naturally revert to the default behavior of booting into the system settings homepage. This is completely different from the existing technology that changes boot-up items through various software settings, and it also avoids the problems of software settings being easily retained, difficult to clear, or conflicting configurations between different users.

[0076] In some implementations, the physical interface is designated as a high-definition multimedia interface.

[0077] In some implementations, the physical interface is specified as a Universal Serial Bus interface.

[0078] In some embodiments, this implementation is for a Bluetooth remote control as the peripheral device. The process by which the event listening instance obtains the target application's identity information from captured events is as follows: After the Bluetooth remote control establishes a Bluetooth connection with the smart TV, the event listening instance discovers the private service containing writable feature values ​​declared by the Bluetooth remote control on the general attribute protocol server, and configures itself to listen for these writable feature values. When the Bluetooth remote control writes a start command encoded according to a preset frame structure using the writable feature values, the event listening instance receives the start command in the data write callback and parses it to obtain the target application's identity information. Simultaneously, the Bluetooth remote control's standard button events are transmitted through the Bluetooth protocol channel and processed by the input event distribution system according to standard procedures.

[0079] In some embodiments, the Bluetooth remote control firmware is designed as a dual-mode Bluetooth device, appearing as two logical devices to the smart TV: a human-computer interaction device remote control and a generic attribute protocol (AAA) peripheral device. The AAA server declares a private service, whose universally unique identifier is a non-standard value containing a write-enabled feature value. When a specific button combination on the remote control is long-pressed, the firmware encodes the start command according to a preset frame structure and sends it via a write-feature value operation. The TV's event listener instance registers a AAA client with the Bluetooth service. After device pairing and connection establishment, it performs service discovery, finds the target private service, and enables notification or write callback for the feature value. When the callback is triggered, the event listener instance reads and parses the byte array from the feature value. Standard human-computer interaction device button events are processed through an input reader, input distributor, and standard channel processing via window management service strategy. The two sets of logic are completely separated at the framework layer. This implementation isolates the logical channels of control commands and standard button commands at the protocol level. The communication process of the private service channel does not interfere with core control functions such as volume and channel under the standard human-computer interaction device protocol, ensuring the reliability of basic remote control operations.

[0080] In some embodiments, during the power-on process of a smart TV, the instruction to launch the target application is received after the operating system's activity management service has started and before the homepage set by the operating system is displayed. The physical interface peripheral can be configured with a power-on delay in its firmware. This delay is greater than or equal to the typical time required for the smart TV to complete loading of the activity management service from receiving the power-on instruction, and less than the typical time required for the smart TV to complete displaying the homepage. This ensures that the launch instruction is received and processed just as the system has application scheduling capabilities and before the homepage is fully displayed. This timing design avoids reception failures caused by sending instructions before the system is ready, and also allows the target application to be scheduled before the homepage is fully displayed, shortening the perceived waiting time for the user.

[0081] In some embodiments, the scheduling agent provided in this application is a functional component running within a system service process. Its implementation can be a callback handle of the activity management service, or a proxy instance embedded within the TV input management service that communicates with the activity management service through the activity management interface. The scheduling agent communicates with the event listener instance through direct in-process method calls. The scheduling agent exposes a standard internal interface to receive application launch requests from the event listener instance, containing identification information such as the target application package name and activity name. The core function of the scheduling agent is to construct an intent at the system service level that does not contain a desktop activity category identifier but whose component information is fully explicit. It then injects the launch request into the scheduling queue through the activity management service's scheduling interface, allowing the system activity manager to bypass the desktop application selection logic and directly place the target application's activity instance at the top of the task stack.

[0082] After receiving an application launch request, the scheduling agent constructs an explicit launch intent that clearly identifies the target application and does not contain a desktop activity category identifier. The specific process involves the scheduling agent creating an intent object and uniquely binding the target component to the target application's package name and activity name using the component name setting method. The scheduling agent sets the intent object's action category to the "Launch Home" action but does not add a desktop activity category identifier. For example, the scheduling agent creates an empty intent object using the constructor of the new intent object, then calls the component name setting method, passing in a component name object constructed from the target application's package name and activity name, thus uniquely and explicitly pointing the intent's target component to the target application. Next, the scheduling agent calls the action category setting method to set the intent object's action category to the main action, but explicitly does not call the category addition method to add a desktop activity category identifier. Because this intent is explicit and does not contain a desktop activity category identifier, when it is passed to the activity management service, the activity management service only recognizes it as a normal, deterministic component launch request and does not trigger a multi-desktop selection process requiring user intervention.

[0083] The specific process by which the scheduling agent launches the activity instance of the target application pointed to by the explicit launch intent in a new, independent task stack and places it at the top of the foreground interface through the system activity manager is as follows: When constructing the explicit launch intent, the scheduling agent adds a new task flag and an exclusion flag from the recent tasks list to the explicit launch intent. The scheduling agent passes the explicit launch intent carrying the new task flag and the exclusion flag from the recent tasks list to the system activity manager, causing the activity instance of the target application to launch in a new task stack, and this new task stack does not appear in the system's recent tasks list. For example, the scheduling agent calls the flag setting method to add the new task flag and the exclusion flag from the recent tasks list to the intent object in a bitwise OR operation. The new task flag causes the activity instance of the target application to generate a root activity in a separate new task stack, not mixed with the task stack of the Internet TV homepage. The exclusion flag from the recent tasks list makes this task stack invisible in the system's recent tasks interface, and the user will not see this application when long-pressing the home button or the multitasking button. The scheduling agent passes the explicit intent carrying the specific flags to the activity management service through the activity launch method of the activity management interface. The activity management service locates the target activity based on the component name in the intent, checks the process status of the target application, and if the process is not running, it creates a new process for it by incubating the process and initializes it; if it is already running, it directly calls back the new intent or restores the lifecycle method of the target activity. After the activity management service schedules the target activity to execute its lifecycle from creation to restoration, the window management service places its corresponding window layer on top of all windows for rendering, so that the user sees the target application interface completely covering the Internet TV homepage interface.

[0084] In some embodiments, when a user presses the back button in the target application interface and gradually exits each activity of the target application, and finally exits the root activity, since there are no more activities in this task stack, the system automatically completes the task stack, and the interface naturally switches back to the previous user-visible task stack, namely the task stack of the Internet TV homepage, and the screen restores the display of the Internet TV homepage interface.

[0085] In some embodiments, when a user presses the back button in the target application interface, the target application determines whether the current activity is the root activity. If not, it exits each activity of the target application step by step; if so, it remains in the root activity. The root activity is the activity corresponding to the target application's homepage.

[0086] In some embodiments, when a user presses the Home button on the remote control from any interface, the system activity manager constructs a standard home page intent containing a desktop activity category identifier, directly returning to the Internet TV home page, ensuring the predictability and consistency of system interaction behavior.

[0087] In some embodiments, after the smart TV receives the Home button sent by the remote control, the framework layer system service will determine whether the current foreground application is the target application. If the current foreground application is the target application, the home page of the target application will be launched; if the current foreground application is not the target application, the home page of the software signal source application will be launched.

[0088] In some embodiments, switching between the target application and the software signal source application after power-on can be achieved by receiving a direct button command sent by the remote control. This is compatible with situations where the back button can only return to the home page and / or the Home button returns to different home pages, while also allowing switching between applications.

[0089] In some embodiments, such as Figure 4 As shown in S4031-4034, before launching the target application through the system activity manager, the scheduling agent performs the following security verification steps. The scheduling agent retrieves a preset list of allowed applications from the system security store. This list contains identification information for one or more authorized applications. The scheduling agent compares the identification information of the target application passed from the event listener instance with the list of allowed applications. If the target application's identification information exists in the list, the agent proceeds to construct the explicit launch command and launch the target application. If the target application's identification information is not in the list, the scheduling agent does not launch the target application. This list of allowed applications can be stored in a system security configuration file and can only be configured and updated by the system administrator or a process with system-level privileges. Through this distributed security decision-making mechanism of external triggering plus internal authentication, even if the peripheral device is physically compromised or the command is maliciously tampered with, attackers cannot launch any application outside the whitelist, effectively improving the security of the solution.

[0090] In other embodiments, the framework layer system service is a TV input management service, specifying the physical interface as a high-definition multimedia interface or a universal serial bus interface. In this implementation, the scheduling agent processes the application startup request as follows: the scheduling agent constructs an internal input source switching instruction pointing to a pre-registered software signal source identifier, where the pre-registered software signal source identifier is obtained by the target application through pre-registration in the TV input framework. The scheduling agent sends the internal input source switching instruction to the TV input management service, causing the TV input management service to start the target application associated with the pre-registered software signal source according to the standard signal source scheduling process. Specifically, the target application is pre-encapsulated as an application implementing a TV input service component and registered as a software signal source in the TV input framework, obtaining the corresponding input identifier. A mapping relationship between the specified physical interface and the input identifier is established in the system configuration. The scheduling agent calls the switching method of the TV input management service through the internal binder interface, passing the target input identifier as a parameter. The TV input management service, according to the standard signal source scheduling logic, shuts down the currently active signal source, starts the TV input service component corresponding to the specified input identifier, calls its tuning and other lifecycle methods, and finally outputs the interface of the cable TV application to the screen. This approach fully follows the architectural design of the TV input framework, utilizing the standard channels within the system for switching input sources to achieve rapid display of the target application, resulting in better system consistency and broad compatibility.

[0091] In some embodiments, the smart TV is also configured to perform retry processing if the target application fails to launch. For example... Figure 5 As shown in S405-S407, after the target application is started, the event listening instance or scheduling agent monitors the startup process of the target application. If the target application starts normally, a first flag indicating successful startup is sent to the peripheral device. If the target application fails to start normally, a second flag indicating startup failure is sent to the peripheral device, causing the peripheral device to resend the command to start the target application. Alternatively, after detecting a startup failure, the smart TV can have the scheduling agent automatically re-initiate a startup attempt without requiring the peripheral device to resend the command. This startup failure retry mechanism avoids target application startup failures due to occasional system resource constraints or timing contention, improving the reliability of direct startup from boot.

[0092] In some embodiments, if the number of resends reaches a set threshold, a failure message needs to be displayed on the TV screen to indicate that the target application has failed to start.

[0093] In some embodiments, even if startup fails, the user can still watch TV using the software source application because it remains displayed as the foreground application.

[0094] In some embodiments, the smart TV is also configured to handle user key input during startup. Since the internet TV homepage and the target application may start in parallel, and the homepage typically finishes displaying before the target application, if a user's key input is received during this startup window, the smart TV distributes the key input to the internet TV homepage, which is in the foreground, and interrupts the startup process of the target application. Through this mechanism, the system prioritizes responding to the user's intentions, avoiding forced switching to the target application when the user wants to operate the homepage, thus ensuring a natural and smooth user experience.

[0095] In this embodiment, in other implementations, such as Figure 7 As shown in steps S601-S604, the command to launch the target application may not be transmitted via a physical interface through an external device, but rather wirelessly via a remote control or other button device. This includes: the remote control being configured to send a power-on command to the smart TV in response to a first press of a first button, and then sending the command to launch the target application after a preset delay following the power-on command. The smart TV, in response to the power-on command from the remote control, launches the operating system and, during the operating system startup process, launches the homepage set by the operating system according to the homepage activity component registered in the registry. The smart TV receives the delayed command to launch the target application from the remote control and, in response to this command, launches the target application as a foreground application. The command to launch the target application is sent by the remote control in response to the first press of the first button, after a preset delay following the first press. The preset delay is greater than or equal to the typical time required for the smart TV to complete the loading of the operating system's activity management service from receiving the power-on command, ensuring that the activity management service has already been loaded and the application can be loaded when the smart TV receives and processes the command to launch the target application, avoiding the problem of reception failure caused by sending the command before the system is ready. In response to the instruction to launch the target application, the target application is launched as a foreground application.

[0096] Furthermore, the preset delay time can be set to be greater than or equal to the typical time required for the smart TV to complete the loading of the activity management service from receiving the power-on command, and less than the typical time required for the smart TV to complete the display of the homepage set by the operating system from receiving the power-on command. This allows the command to launch the target application to be received after the activity management service has started and before the homepage has been displayed, thereby improving the startup speed of the target application through parallel processing in timing without requiring additional user operation.

[0097] The following describes in detail the application startup method based on the physical interface provided in this application embodiment, following the complete timeline from power-on of the smart TV to the completion of the target application interface display, and combining the input parameters, processing procedures, judgment conditions and execution actions in each step.

[0098] When a smart TV is powered on, it performs basic system service initialization. The input parameter is the power-on signal from the power supply or remote control. The process involves the system-on-a-chip (SoC) starting execution from the built-in boot read-only memory, loading and running the bootloader to start the kernel. For example, after initializing the double-rate synchronous dynamic random access memory and the base clock, the bootloader verifies and loads the operating system kernel from the storage medium into memory.

[0099] Kernel startup follows existing technologies. For example, after startup, the kernel sequentially initializes the central processing unit subsystem, memory management unit, and device driver model, loads the Universal Serial Bus host controller driver and high-definition multimedia interface driver, and initializes the corresponding physical layer hardware. The kernel mounts the root file system and starts the initialization process.

[0100] The initialization process parses the initialization script and starts the service manager and incubation process. After preloading commonly used class libraries, the incubation process starts the system service processes through self-replication. For example, the system service processes sequentially start framework layer system services such as activity management service, package management service, TV input management service, universal serial bus service, and high-definition multimedia control service. The system is deemed ready when all critical services within the system service processes have started and the system-ready method of the activity management service has been executed. At this point, the system is capable of handling peripheral events and starting applications. The output action is "System core service layer is ready." Event listener instances within the framework layer system services are synchronously registered during host service initialization and enter a passive listening state.

[0101] Event listener instances capture physical connection events and receive commands from external devices to launch the target application, thereby obtaining the target application's identification information. For example, input parameters are divided into two main categories based on the peripheral type and the specified physical interface type. In the case of data-based peripherals, the input is a byte array passed via a Universal Serial Bus bulk endpoint or interrupt endpoint, or a byte array passed via a Bluetooth Low Energy General Attribute Protocol (BLE) feature value write callback. In the case of event-based peripherals, the input is the hot-plug detection event signal itself from the specified High Definition Multimedia Interface (HD Multimedia Interface), without any subsequent data payload.

[0102] Upon receiving a command from a peripheral device, the event listener instance first parses the received command. If it is a command to start the target application, it constructs an intent to launch the target application. If it is another control command, such as a directional key command or a volume key command, it controls the current foreground application to perform the corresponding operation.

[0103] During the process of launching the target application using an Intent, the Intent extracts the target package name and Activity from the instructions, constructs the Intent, and calls startActivity(). AMS is responsible for cold or warm starting the target process. After the target application's Activity completes its onCreate → onResume lifecycle, the target application's window is displayed on the screen, and the user sees the target application's interface on the TV.

[0104] It should be understood that the sequence number of each step in the above embodiments 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.

[0105] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail or in a particular embodiment, please refer to the relevant descriptions of other embodiments. Different embodiments can be combined.

[0106] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0107] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for starting up, applied to a smart television, characterized in that, include: In response to the power-on command, the operating system of the smart TV is launched; During the startup process of the operating system, the homepage set by the operating system is launched according to the homepage activity component registered in the registry; When a peripheral device is inserted, the device receives an instruction to launch the target application. In response to the instruction to launch the target application, the target application is launched as a foreground application, wherein the target application is an application adapted to the peripheral device, the peripheral device is connected to the smart TV through a physical interface, and the peripheral device is configured to be powered on and started in a controlled manner during the startup process of the smart TV's operating system. Without the external device being inserted, the operating system's homepage is maintained as the foreground application.

2. The method of claim 1, wherein, The peripheral device is connected to the smart TV via a Universal Serial Bus interface or a High Definition Multimedia Interface. The step of receiving the instruction to launch the target application sent by the peripheral device includes: The device receives an instruction to launch a target application, wherein the instruction to launch the target application is generated and sent by the peripheral device based on the component information of the target application embedded internally, and the component information includes at least identification information that characterizes the target application.

3. The method according to claim 2, characterized in that, The step of launching the target application as a foreground application in response to the instruction to launch the target application includes: Parse the instruction to launch the target application and extract the identification information; The target application is launched as a foreground application based on the identification information.

4. The method according to claim 1, characterized in that, Before launching the target application as a foreground application in response to the instruction to launch the target application, the method further includes: obtaining a preset list of allowed applications from the system security storage area, wherein the list of allowed applications contains identification information of one or more authorized applications. The identification information of the target application contained in the instruction to launch the target application is compared with the list of allowed applications to be launched; If the identification information of the target application exists in the list of allowed applications to be launched, continue to execute the step of launching the target application; If the target application's identifier is not in the list of allowed applications to be launched, then the step of launching the target application will not be performed.

5. The method of claim 1, wherein, The target application is a cable TV application that provides the function of receiving and playing live cable TV content; the peripheral device is a hardware device adapted to the cable TV application, and the peripheral device is configured to send a command to start the target application after power-on.

6. The method of claim 1, wherein, The step of launching the homepage set by the operating system based on the homepage activity component registered in the registry is as follows: After the system service is ready, the activity management service constructs a main action, which includes the intent of the homepage category, queries the matching homepage activity component through the package management service, and starts the homepage activity component set by the operating system. The specific steps of launching the target application as a foreground application are as follows: The operating system constructs an explicit intent for the target application and launches the target activity component of the target application; after the target activity component is launched, the window management service sets the window of the target activity component as the foreground window.

7. The method of claim 1, wherein, The instruction to launch the target application is received after the operating system's AMS has finished starting but before the homepage set by the operating system is displayed.

8. The method of claim 1, wherein, The instruction to launch the target application is transmitted from the peripheral device to the smart TV through the physical interface.

9. The method of claim 1, wherein, After launching the target application as a foreground application, the following is also included: Monitor the startup process of the target application; After the target application starts normally, a first identifier indicating successful startup is sent to the peripheral device; If the target application fails to start normally, a second identifier indicating the startup failure is sent to the peripheral device, so that the peripheral device resends the instruction to start the target application.

10. The method according to claim 1, characterized in that, Receive input key press commands; If the key press command is received before the target application is set to the foreground, the key press command is distributed to the home page set by the operating system of the foreground application, and the startup of the target application is interrupted.

11. The method according to claim 1, characterized in that, The step of receiving an instruction from the inserted peripheral device to launch the target application includes: When a peripheral device is inserted, a power-on command is sent to the peripheral device to start it up; The device receives an instruction from the peripheral device to launch a target application, wherein the instruction to launch the target application is sent by the peripheral device after a preset time has elapsed since the application was launched.

12. A method for starting up, applied to a smart television, characterized in that, include: In response to a power-on command sent by the remote control, the operating system of the smart TV is started. The power-on command is a command sent by the remote control after the first press of the first button, instructing the smart TV to power on. During the startup process of the operating system, the homepage set by the operating system is launched according to the homepage activity component registered in the registry; The remote controller receives a command to launch a target application, wherein the command to launch the target application is sent by the remote controller in response to the first press after a preset delay. In response to the instruction to launch the target application, the target application is launched as a foreground application.

13. The method of claim 12, wherein, The preset delay duration is greater than or equal to the typical time required for the smart TV to complete the AMS loading of the operating system from receiving the power-on command.

14. The method of claim 13, wherein, The preset delay time is greater than or equal to the typical time required for the smart TV to complete the AMS loading of the operating system from receiving the power-on command, and less than the power-on time required for the smart TV to complete the display of the homepage set by the operating system from receiving the power-on command.

15. A method for starting an external device, characterized in that, The external device is installed on the smart TV via a physical interface, and the method includes: Receive and start a power-on command, wherein the power-on command is issued by the smart TV during the startup of the smart TV's operating system, and the smart TV is configured to start the homepage set by the operating system according to the homepage activity component registered in the registry during the startup of the operating system; After a set time has elapsed since startup, a command to launch the target application is sent, causing the smart TV to launch the target application as a foreground application and overwrite the homepage set by the operating system. The target application is an application adapted to the peripheral device. The set time elapsed ensures that the smart TV receives the command to launch the target application after the operating system's AMS has finished starting.

16. A smart television comprising include: monitor; System-on-a-chip (SoC); The system-on-a-chip is configured to perform the method described in any one of claims 1-14.

17. An external device that is on a smart TV through a physical interface, characterized in that The external device includes: a processor, The processor is used to execute the method of claim 15.

Images