Implementation method and system for same national language different entries of an Android smart television

Abstract

The application discloses a kind of implementation method and system of same country language different word item of Android smart television, comprising: system layer constructs customer special MCC / MNC system configuration: from customer identification definition to system safety transmission, to before starting configuration takes effect, complete customer special MCC / MNC from whole machine configuration to system global configuration landing;Application layer is based on the hierarchical word item resource adaptation of MCC / MNC configuration: rely on the customer special MCC / MNC configuration that system has taken effect, in combination with Android native resource loading rule, complete the different organization and loading of application layer word item resource.The application uses the characteristics that Android smart television does not use native MCC / MNC configuration, to define customer special MCC / MNC, and in the early stage of system startup inject system configuration method, solve the technical problems that Android smart television ODM multi-client same country language word item cannot be unified maintenance, multi-version application or multi-version overlay application leads to high maintenance cost.

Description

Technical Field

[0001] This invention relates to the field of Android smart TV software development technology, specifically, to a method and system for implementing different terms in the same national language on an Android smart TV. Background Technology

[0002] In the Android smart TV market, different customers in the same country may have different translations of the same term in the same language, leading to incompatibility. To meet the needs of various customers, the current common practice is as follows:

[0003] 1) Maintain independent term resources for different customers, select the term resources corresponding to the customer when compiling the application, generate the customer's specific application, and pre-install the corresponding different applications for different customers;

[0004] 2) Use the Android runtime overlay mechanism to compile the overlay application for the corresponding term resources of the customer, and pre-install the corresponding overlay application for different customers.

[0005] It has certain drawbacks: it requires maintaining a separate application or overlay application for each customer, and adding new customers and modifying common entries involves a huge workload, high risk, and is difficult to maintain. Summary of the Invention

[0006] The purpose of this invention is to provide a method and system for implementing different terms in the same language for Android smart TVs. By taking advantage of the fact that Android smart TVs do not use native MCC / MNC configuration, a method is used to customize a customer-specific MCC / MNC and inject the system configuration early in the system startup. This solves the technical problems of the inability to uniformly maintain terms in the same language for multiple customers of Android smart TV ODM, and the high maintenance costs caused by multiple versions of applications or multiple versions of overlay applications.

[0007] The present invention solves the above problems through the following technical solution:

[0008] A method for implementing different glossary entries in the same national language on an Android smart TV includes:

[0009] The system layer constructs a customer-specific MCC / MNC system configuration: from customer identification definition to secure system transmission, and then to pre-boot configuration activation, completing the implementation of customer-specific MCC / MNC from device-wide configuration to system-wide configuration. The application layer uses layered term resource adaptation based on the MCC / MNC configuration: relying on the already activated customer-specific MCC / MNC configuration and combining it with Android's native resource loading rules, it completes the differentiated organization and loading of application-layer term resources, achieving automatic multi-customer adaptation through layered resource organization. By constructing a customer-specific MCC / MNC system configuration at the system layer, from customer identification definition to secure system transmission, and then to pre-boot configuration activation, it completes the implementation of customer-specific MCC / MNC from device-wide configuration to system-wide configuration, solving the core technical problems of "existing systems lacking customer-dimensional resource differentiation identifiers and being unable to complete customer configuration synchronization before application loading," laying the system foundation for accurate loading of application-layer resources. Furthermore, by adapting application-layer term resources based on MCC / MNC configuration, relying on the customer-specific MCC / MNC configuration already in effect in the system, and combining Android's native resource loading rules, the differentiated organization and loading of application-layer term resources are completed, solving the core technical problems of "existing technologies require the maintenance of multiple complete applications or overlay applications, high cost of modifying common terms, and poor scalability".

[0010] As a further improvement of the present invention, the system layer constructs a customer-specific MCC / MNC system configuration, the specific steps of which include: customer-specific MCC / MNC whole machine configuration based on ITU standards, MCC / MNC system attribute injection at the vendor level isolation, and dynamic update of MCC / MNC configuration before the first Activity of the system is launched.

[0011] As a further improvement of the present invention, the specific method for configuring a customer-specific MCC / MNC system based on the ITU standard is as follows: For customers with different translation needs for the same term in the same language from the same country, a national MCC code conforming to the ITU standard is assigned to the customer, which is then combined with an unused MNC code from that country to form a unique mcc-mnc identifier, which is written into the corresponding customer's system configuration file to achieve a one-to-one binding between the customer and the MCC / MNC.

[0012] As a further improvement of the present invention, the Vendor-level isolated MCC / MNC system attribute injection method is as follows: add a configuration reading instruction to the init.rc script of the Android system. During the system initialization phase, the mcc-mnc field value in the whole device configuration file is read through the init.rc script, the Vendor partition system attribute prefixed with ro.vendor.sys. is set, and the mcc-mnc field value is written into the Vendor-level system attribute ro.vendor.sys.customer.mccmnc prefixed with ro.vendor.sys., thereby realizing the secure transfer of MCC / MNC identifier from the whole device configuration to the system layer.

[0013] As a further improvement of the present invention, the Vendor partition-level system attribute is a read-only system attribute that cannot be modified during device operation, thus ensuring the security and stability of the customer identifier.

[0014] As a further improvement of the present invention, the dynamic update of the MCC / MNC configuration before the first Activity of the system is performed as follows: In the onCreate phase of the first invisible FallbackHome Activity of the Android system, the MCC / MNC configuration update operation is performed: the MCC / MNC system attributes prefixed with ro.vendor.sys. are read, and when a valid mcc-mnc attribute is detected, the MCC and MNC fields are separated and the system interface is called to update the MCC / MNC in the system configuration.

[0015] As a further improvement of the present invention, the application layer is based on hierarchical term resource adaptation of MCC / MNC configuration, specifically including hierarchical term resource organization of "MCC / MNC and language" combination.

[0016] As a further improvement of the present invention, the hierarchical terminology resource organization of the "MCC / MNC and language" combination includes:

[0017] Organize the resources for the Android smart TV application by creating resource files for default terms, common national language terms, and customer-customized terms in the application's res resource folder. The default term resource file is stored in the values ​​directory, the customer's common national language term resource file is stored in the values-language directory, and the customer's national language customized term resource file is stored in the values-mccXYY-mncXYY-language directory.

[0018] Resource files for customized terms in the same national language are created for different customers according to "mcc-mnc-language". Only the differentiated translations of the same term for each customer are stored in this file. Common terms are stored in the resource file for general national language terms. Default terms are stored in the resource file for default terms. By utilizing the Android native resource loading priority mechanism, customized terms are overridden and common terms are automatically inherited.

[0019] Furthermore, the present invention also solves the above problems through the following technical solutions:

[0020] An implementation system for different terms in the same language on an Android smart TV is provided. When the system runs, it executes the implementation method for different terms in the same language on an Android smart TV as described above.

[0021] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0022] This invention establishes a complete differentiated management system for Android smart TV ODM entries in the same national language across multiple clients by coordinating a customer-specific MCC / MNC system configuration at the system layer with a layered terminology resource adaptation based on the MCC / MNC configuration at the application layer. This fundamentally overcomes the technical shortcomings of existing technologies, such as high maintenance costs, poor scalability, and weak compatibility. It achieves technological breakthroughs in multiple dimensions, including application deployment, terminology maintenance, system adaptation, and customer expansion. The specific technical effects achieved are as follows:

[0023] (1) Achieve multi-customer adaptation of a single application package, eliminating the need to compile and pre-install specific applications or overlay applications for different customers, greatly simplifying the application pre-installation and management process in the Android smart TV ODM scenario, and reducing software management costs and error probability.

[0024] (2) Implement hierarchical maintenance and management of term resources. Public terms are uniformly placed in the general national language resource directory. Customers only need to maintain differentiated customized terms, which greatly reduces the workload of term modification and iteration and avoids the consistency risk of multiple sets of resources being updated simultaneously.

[0025] (3) It adopts a non-intrusive system configuration update method, without modifying the core framework of the Android system. It relies on the native mechanism to implement the function, ensuring the stability and compatibility of the system, adapting to various versions of Android smart TV systems, and eliminating the need for customized development for different versions.

[0026] (4) Enables rapid adaptation for customer expansion. If there are conflicting terms for new customers, it is only necessary to configure the customer's exclusive MCC / MNC whole machine parameters, create the corresponding resource directory and supplement the differentiated terms. There is no need to modify the core code and general resources, which greatly improves the delivery efficiency of new customers and reduces the cost of customized development.

[0027] (5) The system automatically and accurately loads the term resources. Based on the effective MCC / MNC configuration and the current system language, the system automatically matches and loads the corresponding customized terms for the customer. Uncustomized terms inherit the general content by default. This is a resource loading mechanism natively supported by Android. No manual intervention is required for the resource loading logic, which improves the intelligence and convenience of term management. Attached Figure Description

[0028] Figure 1 This is a schematic diagram illustrating a method for implementing different terms in the same national language on an Android smart TV according to the present invention. Detailed Implementation

[0029] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0030] Example 1:

[0031] See attached document Figure 1 A method for implementing different terms in the same language for Android smart TVs includes two core technologies: building a customer-specific MCC / MNC system configuration at the system layer and layered term resource adaptation based on the MCC / MNC configuration at the application layer. The goal is to "solve the problem of differentiated maintenance of terms in the same language for multiple customers of Android smart TV ODMs" and achieve the technical effect of "one application adapting to multiple customers, and customization can be completed by only maintaining the different terms".

[0032] MCC (Mobile Country Code) is a three-digit code uniformly assigned and managed by the International Telecommunication Union (ITU) to uniquely identify the country or region to which a mobile user belongs. MNC (Mobile Network Code) is a two- or three-digit code assigned by individual countries to identify different mobile network operators within the same country. Together, MCC and MNC form a unique PLMN (Public Land Mobile Network) ID, used to identify a specific mobile network operator globally. The Android system natively supports automatically loading corresponding resources based on the MCC / MNC configuration.

[0033] Among them, the system layer builds a customer-specific MCC / MNC system configuration;

[0034] From defining customer identifiers to secure system transfer, and then to pre-boot configuration activation, the system successfully implements customer-specific MCC / MNC configurations from system-wide to global configuration. This solves the core technical problem of "existing systems lacking customer-level resource differentiation identifiers and being unable to synchronize customer configurations before application loading," laying the system foundation for accurate application-layer resource loading. Specific steps include:

[0035] 1) Customer-specific MCC / MNC system configuration based on ITU standards;

[0036] Technical approach: For customers with different translation needs for the same term in the same language from the same country, a country-specific MCC code conforming to ITU standards is assigned to each customer. This code is then combined with an unused MNC code from that country to form a unique MCC-MNC identifier, which is written into the corresponding customer's system configuration file, thus achieving a one-to-one binding between the customer and the MCC / MNC.

[0037] Leveraging the hardware characteristics of Android smart TVs—namely, the absence of SIM cards and native MCC / MNC configurations—the MCC / MNC fields, originally used for mobile network identification, are reused as unique customer identifiers. This approach adheres to industry standards to ensure configuration standardization while enabling precise customer differentiation through dedicated coding. It defines a system-level identifier for customers from the source, resolving the technical pain point of "the inability to load resources on demand without a unified customer identifier."

[0038] 2) Vendor-level isolated MCC / MNC system property injection;

[0039] Technical approach: Add a configuration read instruction to the init.rc script of the Android system. During the system initialization phase, the init.rc script reads the value of the mcc-mnc field in the whole device configuration file, sets the Vendor partition system property with the prefix ro.vendor.sys., and writes the mcc-mnc field value into the Vendor-level system property ro.vendor.sys.customer.mccmnc with the prefix ro.vendor.sys., thereby realizing the secure transfer of the mcc-mnc identifier from the whole device configuration to the system layer.

[0040] The Vendor partition-level system attributes are read-only system attributes and cannot be modified during device operation, ensuring the security and stability of the customer identifier.

[0041] Addressing the architectural features of Android system Framework and Vendor isolation, as well as SELinux permission restrictions, a Vendor-level system attribute is used to pass identifiers. This avoids the permission issues of directly accessing the entire device configuration, while ensuring the security and compatibility of configuration transfer. It also solves the technical problem of "customer identifiers cannot be effectively passed across partitions to the system framework," providing an effective data source for system configuration updates.

[0042] 3) Dynamic updates to the MCC / MNC configuration before the first Activity is launched;

[0043] Technical approach: In the onCreate phase of the first invisible FallbackHome Activity in the Android system, read the MCC / MNC system attributes prefixed with ro.vendor.sys. When a valid mcc-mnc attribute is detected, separate the MCC and MNC fields and call the system interface to update the MCC / MNC in the system configuration.

[0044] During the initial system startup phase, before application resources are loaded, the MCC / MNC system properties are read in the onCreate phase of FallbackHome, and the system-wide MCC / MNC configuration is updated to ensure that the customer identifier is effective before application startup. Before updating the system-wide MCC / MNC configuration, the read MCC-MNC encoding is validated for validity. Configuration updates are only performed if the encoding is valid and not empty. If no valid MCC-MNC encoding is read, the system default configuration remains unchanged, ensuring that customers without translation conflicts for the same terms in the same language (who do not need to configure MCC-MNC) are not affected. FallbackHome is selected as the system configuration update node to ensure that the system configuration MCC / MNC is effective before all business activities start, allowing the application to directly identify the customer-specific identifier when loading subsequent application resources. At the same time, a non-system framework modification method is used, which ensures the timeliness of configuration updates and avoids the stability risks caused by modifying the core system code. This solves the technical problem that "the customer identifier cannot be synchronized to the system-wide configuration before resource loading" and achieves timing matching between configuration and resource loading.

[0045] Among them, the application layer is based on hierarchical term resource adaptation configured by MCC / MNC;

[0046] Based on the system's existing customer-specific MCC / MNC configurations and combined with Android's native resource loading rules, differentiated organization and loading of application-layer terminology resources are achieved. This layered resource organization enables automatic adaptation for multiple customers. It solves the core technical problems of "existing technologies requiring the maintenance of multiple complete applications or overlay applications, high costs for modifying common terms, and poor scalability." Specific steps include:

[0047] 4) Hierarchical organization of terminology resources combining "MCC / MNC and language";

[0048] Technical approach: Organize the resources of the Android smart TV application. In the application's res resource folder, create resource files for default terms, common national language terms, and customer-customized terms respectively. Create resource files for the same national language terms for different customers according to "mcc-mnc-language". This file only contains the differentiated translations of the same term for each customer. Common terms are uniformly stored in the resource file for common national language terms, and default terms are stored in the resource file for default terms. Utilize the Android native resource loading priority mechanism to achieve custom term overriding and automatic inheritance of common terms.

[0049] The system automatically loads the corresponding resources according to priority based on the current MCC / MNC and system language; the same application APK does not need to be recompiled for different customers, and differentiated translation adaptation for the same terms in the same country language can be achieved by switching the MCC / MNC configuration.

[0050] Leveraging Android's native resource loading rules, the system automatically prioritizes loading customized terms from customer-specific resource files based on the updated MCC / MNC configuration and the current system language. For terms not customized, it defaults to loading resource files containing terms in the common national language, eliminating the need for additional resource loading logic. This approach directly enables "one application package to adapt to multiple customers," while allowing term maintenance to achieve "unified management of common parts and separate maintenance of customized parts." It fundamentally solves the technical pain points of "existing technologies requiring the maintenance of multiple complete or overlay resources, and the large workload and high risk associated with adding new customers and modifying common terms."

[0051] This embodiment also includes an implementation system for different terms in the same language on an Android smart TV. When the system runs, it executes the implementation method for different terms in the same language on an Android smart TV as described above.

[0052] Example 2:

[0053] Taking two clients, A and B, in China with conflicting Simplified Chinese customization needs, as examples, and combining the operating logic of the Android smart TV system, this paper provides a detailed explanation of the aforementioned technical solution, divided into two parts: system configuration and application adaptation. The implementation steps are as follows:

[0054] Build a customer-specific MCC / MNC system configuration;

[0055] 1) Select the ITU standard MCC code 460 for China, assign the unused MNC code 501 for customer A, and combine them into mcc-mnc=460501; assign the unused MNC code 502 for customer B, and combine them into mcc-mnc=460502. Write the above mcc-mnc configuration field into the corresponding system configuration files for customer A and customer B respectively.

[0056] 2) Add a configuration read instruction to the init.rc script of the Android system. During the system initialization phase, the script reads the value of the mcc-mnc field in the whole device configuration file and then writes the value into the Vendor-level system property ro.vendor.sys.customer.mccmnc with the prefix ro.vendor.sys., thus completing the system-level transfer of the customer MCC / MNC identifier.

[0057] 3) In the FallbackHome Activity, which is the first activity to launch in the Android system, the MCC / MNC configuration update operation is performed in the onCreate() phase of its lifecycle: First, the value of the system property ro.vendor.sys.customer.mccmnc is read. If the value is not empty, it is split. The first 3 characters are the MCC code and the last 3 characters are the MNC code. Then, the updateMccMncConfiguration() interface of AM is called, and the split MCC and MNC codes are passed as parameters to the interface to complete the update of the system-wide MCC / MNC configuration.

[0058] The application uses a hierarchical term resource adaptation based on MCC / MNC configuration;

[0059] 4) Organize the resources for the Android smart TV application. In the application's res resource folder, create resource files for default terms, general national language terms, and customer-customized terms respectively: the default term resource file is stored in the values ​​directory, the general Simplified Chinese term resource file is stored in the values-zh directory, the Simplified Chinese term resource file for customer A is stored in the values-mcc460-mnc501-zh directory, and the Simplified Chinese term resource file for customer B is stored in the values-mcc460-mnc502-zh directory; note that the customer-customized term resource files for customers A and B only contain translations that differ from the general Simplified Chinese term, and there is no need to reconfigure the general Simplified Chinese term.

[0060] After implementing the above steps, when the Android smart TV system switches to Simplified Chinese, the system will automatically load the customized translations from the mcc460-mnc501-zh directory for Simplified Chinese entries customized for Customer A's products, and automatically load the customized translations from the mcc460-mnc502-zh directory for Simplified Chinese entries customized for Customer B's products, based on the updated global MCC / MNC configuration. For entries not configured in the customized directory, the general Simplified Chinese entries from the values-zh directory will be loaded. Only if those do not exist will the entries from the default values ​​directory be loaded.

[0061] Although the present invention has been described herein with reference to illustrative embodiments, the above embodiments are merely preferred embodiments of the present invention, and the implementation of the present invention is not limited to the above embodiments. It should be understood that those skilled in the art can devise many other modifications and implementations, which will fall within the scope and spirit of the principles disclosed in this application.

Claims

1. A method for implementing different terms in the same national language on an Android smart TV, characterized in that, include: The system layer constructs a customer-specific MCC / MNC system configuration: from defining the customer identifier to the secure transfer of the system, and then to the configuration taking effect before startup, it completes the implementation of the customer-specific MCC / MNC from the whole machine configuration to the global system configuration; Application layer hierarchical term resource adaptation based on MCC / MNC configuration: Relying on the customer-specific MCC / MNC configuration that has been enabled in the system, combined with the native Android resource loading rules, the application layer term resources are organized and loaded in a differentiated manner, and automatic adaptation for multiple customers is achieved through hierarchical resource organization.

2. The method for implementing different terms in the same national language on an Android smart TV according to claim 1, characterized in that, The system layer constructs a customer-specific MCC / MNC system configuration, and the specific steps include: customer-specific MCC / MNC whole machine configuration based on ITU standards, MCC / MNC system attribute injection at the vendor level isolation, and dynamic update of MCC / MNC configuration before the first Activity of the system is launched.

3. The method for implementing different terms in the same national language on an Android smart TV according to claim 2, characterized in that, The specific method for configuring the customer-specific MCC / MNC system based on ITU standards is as follows: For customers with different translation needs for the same term in the same language from the same country, a country-specific MCC code conforming to ITU standards is assigned to each customer. This code is then combined with an unused MNC code from that country to form a unique MCC-MNC identifier, which is written into the corresponding customer's system configuration file, thus achieving a one-to-one binding between the customer and the MCC / MNC.

4. The method for implementing different terms in the same national language on an Android smart TV according to claim 3, characterized in that, The specific method for injecting the Vendor-level isolated MCC / MNC system attributes is as follows: Add a configuration read instruction to the init.rc script of the Android system. During the system initialization phase, the init.rc script reads the value of the mcc-mnc field in the whole device configuration file, sets the Vendor partition system property with the prefix ro.vendor.sys., and writes the mcc-mnc field value into the Vendor-level system property ro.vendor.sys.customer.mccmnc with the prefix ro.vendor.sys., thus realizing the secure transfer of MCC / MNC identifier from the whole device configuration to the system layer.

5. The method for implementing different terms in the same national language on an Android smart TV according to claim 4, characterized in that, The Vendor partition-level system attributes are read-only system attributes and cannot be modified during device operation, ensuring the security and stability of customer identification.

6. The method for implementing different terms in the same national language on an Android smart TV according to claim 4, characterized in that, The system dynamically updates the MCC / MNC configuration before the first Activity is launched, using the following method: In the onCreate phase of the first invisible FallbackHome Activity in the Android system, the MCC / MNC configuration update operation is performed: read the MCC / MNC system properties prefixed with ro.vendor.sys. When a valid mcc-mnc property is detected, the MCC and MNC fields are separated and the system interface is called to update the MCC / MNC in the system configuration.

7. The method for implementing different terms in the same national language on an Android smart TV according to claim 1, characterized in that, The application layer is based on hierarchical term resource adaptation configured by MCC / MNC, specifically including hierarchical term resource organization of the combination of "MCC / MNC and language".

8. The method for implementing different terms in the same national language on an Android smart TV according to claim 7, characterized in that, The hierarchical organization of the terminology resource based on the "MCC / MNC and language" combination includes: Organize the resources for the Android smart TV application by creating resource files for default terms, common national language terms, and customer-customized terms in the application's res resource folder. The default term resource file is stored in the values ​​directory, the customer's common national language term resource file is stored in the values-language directory, and the customer's national language customized term resource file is stored in the values-mccXYY-mncXYY-language directory. Resource files for customized terms in the same national language are created for different customers according to "mcc-mnc-language". Only the differentiated translations of the same term for each customer are stored in this file. Common terms are stored in the resource file for general national language terms. Default terms are stored in the resource file for default terms. By utilizing the Android native resource loading priority mechanism, customized terms are overridden and common terms are automatically inherited.

9. A system for implementing different terms in the same national language on an Android smart TV, characterized in that, When the system runs, it executes the method described in any one of claims 1-8 for implementing different terms in the same country language on an Android smart TV.

Images