Method for multi-channel business to share starter under intelligent television system

Abstract

The invention provides a method for sharing a starter by multi-channel services in an intelligent television system, and relates to the field of intelligent television systems. According to the method for sharing the starter by the multi-channel services in the intelligent television system, a method for sharing one Launcher by the multi-channel services is provided, high reusability and flexible expansion of the Launcher are realized through a modular design and a dynamic configuration technology, the modular design is adopted in the method, the Launcher is divided into a core module, a service module and a public module, and the Launcher is divided into a plurality of service modules and a plurality of common modules. According to the method, dynamic configuration management is adopted, and interface layout and function modules of the Launcher are dynamically controlled through local or remote configuration files. Compared with the prior art, the method has the advantage of high reusability, multiple channels and businesses share one Launcher, and the development and maintenance cost is reduced.

Description

Technical Field

[0001] The present invention relates to the field of smart TV systems, and specifically to a method for multiple-channel services to share a launcher under a smart TV system. Background Art

[0002] Currently, the Launcher in a smart TV system is usually used to provide an entry for users to access applications and content. However, different channels or user requirements often require the Launcher to provide customized functions and interfaces. In this case, the traditional development method faces the following problems: high development and maintenance costs, each channel or service needs to be developed and maintained separately for the corresponding Launcher, resource waste, many identical functions are repeatedly implemented in the Launchers of different channels, wasting development resources, and poor flexibility: changes in services or channels require the release of a new version, and it is impossible to quickly respond to market demands.

[0003] Therefore, there is an urgent need for a method that enables multiple channels and services to share a unified Launcher and meets different requirements through dynamic configuration and modular design. Summary of the Invention

[0004] (1) Technical Problems to be Solved

[0005] Aiming at the deficiencies of the prior art, the present invention provides a method for multiple-channel services to share a launcher under a smart TV system, which has the advantages of high reusability compared with the existing technical solutions, multiple channels and services share one Launcher, reducing development and maintenance costs, has the advantage of flexibility compared with the existing technologies, through dynamic configuration and modular design, can quickly respond to changes in business requirements, has the advantage of strong scalability compared with the existing technologies, supports the rapid integration of new service modules, without significantly modifying the core framework, and has the advantage of high operating efficiency compared with the existing technologies, loading modules on demand, reducing memory occupancy and startup time.

[0006] (2) Technical Solutions

[0007] To achieve the above object, the present invention is implemented through the following technical solutions: A method for multi-channel services to share a launcher in an intelligent TV system, which provides a method for multi-channel services to share a single Launcher. Through modular design and dynamic configuration technology, high reusability and flexible expansion of the Launcher are achieved. This method adopts modular design and divides the Launcher into three modules: a core module, a service module, and a common module. This method adopts dynamic configuration management and dynamically controls the interface layout and function modules of the Launcher through local or remote configuration files. This method has a dynamic module loading function and realizes the on-demand loading of service modules by using dynamic loading technology. This method adopts a general navigation and communication mechanism. This method has a multi-channel adaptation function and supports compile-time adaptation and runtime adaptation of multi-channel services. This method supports the independent update and maintenance functions of service modules;

[0008] Through the above technical solutions, when the Launcher starts, it checks the version number of the remote configuration file. If there is an update, it downloads the latest configuration and dynamically adjusts the interface layout and functions according to the configuration. For example, during a shopping event, the configuration file can prioritize the display of the "Shopping" module and enable the promotion function.

[0009] Preferably, in the modular design of this method, the core module is responsible for providing the basic functions of the Launcher. Each service of the service module is developed as an independent module and can be dynamically loaded. The common module provides general tools and services. The core module communicates with the service module through a standardized interface to ensure decoupling between modules;

[0010] Through the above technical solutions, the core module includes a navigation bar, a settings interface, theme management, etc. Each service of the service module includes live broadcast, on-demand, shopping, games, etc. The common module includes network requests, data storage, log management, etc.

[0011] Preferably, in the dynamic configuration management of this method, the local configuration loads a pre-set JSON or XML configuration file when the Launcher starts, and loads the service module according to the configuration. The remote configuration: obtains the configuration file from the server and updates the layout and functions of the Launcher in real time.

[0012] Preferably, in the dynamic module loading function of this method, the Android Dynamic Feature Module or DexClassLoader is used to load independent service modules, and the core module provides a unified module management interface, which is responsible for initializing, displaying, and unloading service modules.

[0013] Preferably, in the general navigation and communication mechanism of this method, a unified navigation system is designed to manage interface jumps and the Fragment stack, and inter-module communication is achieved through an event bus or data binding, avoiding strong coupling between modules.

[0014] Preferably, in the multi-channel adaptation function of this method, the compile-time adaptation separates resources and configurations for different channels through the productFlavors of Gradle, and the run-time adaptation dynamically adjusts the functions and layouts of the Launcher through channel identifiers.

[0015] Preferably, in the update and maintenance function of this method, WorkManager or a similar framework is used to regularly check and update business modules, and combined with dynamic configuration, hot updates of business functions are achieved without reinstalling the Launcher.

[0016] Working principle: This method splits the core functions and business functions into independent modules. The core module provides a unified interface and interfaces. The core module loads the navigation bar, and the navigation bar loads different business module entrances according to the configuration file. When the user clicks an entrance, the corresponding business module is dynamically loaded and its content is displayed. Specific resources and functions are pre-set for different channels. The Launcher of Channel A shows live broadcast and on-demand entrances, while the Launcher of Channel B shows shopping and game entrances. Different-channel APK packages are generated through the productFlavors of Gradle.

[0017] (III) Beneficial effects

[0018] The present invention provides a method for multi-channel services to share a launcher in an intelligent TV system. It has the following beneficial effects:

[0019] 1. The present invention provides a method for multi-channel services to share a launcher in an intelligent TV system, which has the advantage of high reusability compared with existing technical solutions. Multiple channels and services share one Launcher, reducing development and maintenance costs.

[0020] 2. The present invention provides a method for multi-channel services to share a launcher in an intelligent TV system, which has the advantage of flexibility compared with existing technologies. Through dynamic configuration and modular design, it can quickly respond to changes in business requirements.

[0021] 3. The present invention provides a method for multi-channel services to share a launcher in an intelligent TV system, which has the advantage of strong scalability compared with existing technologies. It supports the rapid integration of new business modules without significantly modifying the core framework.

[0022] 4. The present invention provides a method for a multi-channel service to share a launcher in an intelligent TV system, which has the advantage of high operating efficiency compared with the existing technology, loads modules on demand, and reduces memory occupation and startup time. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 It is a schematic diagram of the system architecture of the present invention;

[0024] Figure 2 It is a flowchart of dynamic module loading of the present invention;

[0025] Figure 3 It is a flowchart of remote configuration update of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0026] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention. In the description of the present application, it should be noted that the terms used here are only for the purpose of describing specific embodiments, and are not intended to limit the exemplary embodiments according to the present application. For the convenience of description, the sizes of the various parts shown in the drawings are not drawn in actual proportional relationship. Technologies, methods, and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but in appropriate cases, the technologies, methods, and devices should be regarded as part of the authorization specification. In all the examples shown and discussed here, any specific value should be construed as merely exemplary, rather than as a limitation. Therefore, other examples of the exemplary embodiments may have different values. It should be noted that like reference numerals and letters denote like items in the following drawings, and thus, once an item is defined in one drawing, it does not need to be further discussed in subsequent drawings.

[0027] Embodiment 1:

[0028] As Figures 1-3As shown in the figure, an embodiment of the present invention provides a method for multiple-channel services to share a launcher in an intelligent TV system. This method provides a way for multiple-channel services to share a single Launcher. Through modular design and dynamic configuration technology, high reusability and flexible expansion of the Launcher are achieved. This method adopts modular design, dividing the Launcher into three modules: a core module, a service module, and a common module. This method adopts dynamic configuration management, and through local or remote configuration files, dynamically controls the interface layout and functional modules of the Launcher. This method has a dynamic module loading function, and uses dynamic loading technology to achieve the on-demand loading of service modules. This method adopts a general navigation and communication mechanism. This method has a multi-channel adaptation function, supporting compile-time adaptation and run-time adaptation of multi-channel services. This method supports the independent update and maintenance functions of service modules.

[0029] In the modular design of this method, the core module is responsible for providing the basic functions of the Launcher. Each service of the service module is developed as an independent module and can be dynamically loaded. The common module provides general tools and services. The core module communicates with the service module through a standardized interface to ensure decoupling between modules. Example of a configuration file:

[0030] {

[0031] "modules":

[0032] {"name":"live","enabled":true,"position":1},

[0033] {"name":"vod","enabled":true,"position":2},

[0034] {"name":"shopping","enabled":false}

[0036] }

[0037] ​In the dynamic configuration management of this method, the local configuration loads a pre - set JSON or XML configuration file when the Launcher starts, and loads business modules according to the configuration. The remote configuration: obtains the configuration file from the server and updates the layout and functions of the Launcher in real - time. In the dynamic module loading function of this method, the Android Dynamic FeatureModule or DexClassLoader is used to load independent business modules, and the core module provides a unified module management interface, which is responsible for initializing, displaying, and unloading business modules. In the general navigation and communication mechanism of this method, a unified navigation system is designed to manage interface jumps and the Fragment stack, and communication between modules is achieved through an event bus or data binding, avoiding strong coupling between modules. In the multi - channel adaptation function of this method, the compile - time adaptation separates resources and configurations for different channels through the productFlavors of Gradle, and the run - time adaptation dynamically adjusts the functions and layouts of the Launcher through channel identifiers. In the update and maintenance function of this method, WorkManager or a similar framework is used to regularly check and update business modules, and combined with dynamic configuration, hot updates of business functions are realized without reinstalling the Launcher.

[0038] Embodiment 2:

[0039] As Figures 1-3 shown,

[0040] The key technical points of this method are the following six:

[0041] 1: Modular architecture design (separation and independent development of core modules, business modules, and common modules, definition of standardized interfaces, ensuring loose coupling and flexibility between modules);

[0042] 2: Dynamic configuration management (dynamically adjusting the interface layout and functions of the Launcher through local or remote configuration files, supporting the enabling, disabling, and priority setting of multiple business modules)

[0043] 3: Dynamic module loading (on - demand loading technology based on Android Dynamic Feature Module or DexClassLoader, realizing dynamic loading, updating, and unloading of modules, improving system performance and scalability);

[0044] 4: General navigation and communication mechanism (a unified navigation system, such as Jetpack Navigation, manages interface jumps, and a decoupled design of the inter - module communication mechanism, such as EventBus, LiveData);

[0045] 5: Multi-channel adaptation (channel-differentiated resource packaging during compilation, such as Gradle's productFlavors, and dynamically adjusting functions and interfaces based on channel identifiers at runtime);

[0046] 6: Independent update of business modules (utilizing dynamic configuration and modularization technologies to enable the update of business modules without reinstalling the Launcher, and the hot update mechanism to enhance the user experience).

[0047] The technical protection points of this method are the following six:

[0048] 1: Modular architecture design of Launcher (separation design of core module and business modules, and dynamic integration of business modules using a unified interface);

[0049] 2: Design and implementation of dynamic configuration files (format and parsing logic of configuration files, and technical methods for dynamically adjusting Launcher functions and interfaces);

[0050] 3: On-demand loading technology (process and optimization strategies for dynamically loading business modules, and implementation details of using dynamic loading technology to improve system performance);

[0051] 4: Multi-channel business adaptation solution (channel adaptation methods during compilation and runtime, and conflict resolution solutions for different channel configurations);

[0052] 5: Inter-module communication mechanism (design of loose-coupling communication using event bus or data binding, and communication solution to ensure module independence and scalability);

[0053] 6: Update and maintenance mechanism (implementation methods of independent update and hot update of business modules, and long-term stability guarantee solution for Launcher).

[0054] Although the embodiments of the present invention have been shown and described, it will be understood by those of ordinary skill in the art that various changes, modifications, substitutions, and variations can be made to these embodiments without departing from the principles and spirit of the present invention, and the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A method for sharing a launcher for multiple channel services in a smart TV system, characterized in that: The method provides a method for multiple channel services to share a Launcher, and realizes the high reusability and flexible expansion of the Launcher through modular design and dynamic configuration technology. The method adopts modular design to divide the Launcher into three modules: a core module, a business module and a common module. The method adopts dynamic configuration management to dynamically control the interface layout and functional modules of the Launcher through local or remote configuration files. The method has a dynamic module loading function and adopts dynamic loading technology to realize on-demand loading of business modules. The method adopts a general navigation and communication mechanism. The method has a multi-channel adaptation function and supports compile-time adaptation and runtime adaptation of multi-channel services. The method supports independent update and maintenance functions of business modules.

2. The method for sharing a launcher for multiple channel services in a smart TV system according to claim 1, characterized in that: In the modular design of the method, the core module is responsible for providing the basic functions of the Launcher, each business of the business module is developed as an independent module and can be dynamically loaded, the common module provides general tools and services, and the core module communicates with the business module through a standardized interface to ensure decoupling between modules.

3. The method for sharing a launcher for multiple channel services in a smart TV system according to claim 1, characterized in that: In the dynamic configuration management of this method, the local configuration loads a preset JSON or XML configuration file when the Launcher is started, and loads the business module according to the configuration. The remote configuration obtains the configuration file from the server and updates the layout and functions of the Launcher in real time.

4. The method for sharing a launcher for multiple channel services in a smart TV system according to claim 1, characterized in that: In the dynamic module loading function of this method, Android Dynamic Feature Module or DexClassLoader is used to load independent business modules, and the core module provides a unified module management interface, which is responsible for initializing, displaying and unloading business modules.

5. The method for sharing a launcher for multiple channel services in a smart TV system according to claim 1, characterized in that: In the general navigation and communication mechanism of this method, a unified navigation system is designed to manage interface jumps and Fragment stacks, and inter-module communication is achieved through event bus or data binding to avoid strong coupling between modules.

6. The method for sharing a launcher for multiple channel services in a smart TV system according to claim 1, characterized in that: In the multi-channel adaptation function of this method, the compile-time adaptation realizes the separation of resources and configurations of different channels through Gradle's productFlavors, and the runtime adaptation dynamically adjusts the function and layout of the Launcher through the channel identifier.

7. The method for sharing a launcher for multiple channel services in a smart TV system according to claim 1, characterized in that: In the update and maintenance function of this method, WorkManager or a similar framework is used to regularly check and update the business module, and combined with dynamic configuration, hot update of business functions is implemented without reinstalling the Launcher.

Images