Application updating method and device, electronic equipment and storage medium

By obtaining device information and deciding to apply updates based on their matching, the compatibility problems caused by hardware differences during device updates in the prior art are solved, and a safer and more accurate update process is achieved.

CN118916057APending Publication Date: 2024-11-08SHENZHEN SKYWORTH INT TRADE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411135401.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-15
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

When pushing operating system and application updates, existing device updates fail to fully consider the hardware differences between different devices, resulting in the software being incompatible with certain hardware configurations, which may cause system crashes or 'bricking' problems.

Method used

By obtaining device information, determine whether the current version of the target application needs to be updated to the target version, and decide whether to update based on the device information and update information to ensure that the updated version matches the device information, thereby avoiding device failure.

Benefits of technology

Effectively reduce or even avoid device failures, ensure that updated applications are compatible with devices, and improve the accuracy and security of updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916057A_ABST
    Figure CN118916057A_ABST
Patent Text Reader

Abstract

The embodiment of the invention relates to an application updating method and device, electronic equipment and a storage medium, and the method comprises the steps that equipment information of first equipment is acquired, and a target application is installed in the first equipment; determining whether the current version of the target application is a to-be-updated target version; under the condition that the current version is not the target version, whether the current version of the target application is updated to the target version or not is determined based on the equipment information; and under the condition that the current version of the target application is determined to be updated to the target version, controlling the first equipment to update the current version of the target application to the target version. Therefore, whether the target application of the first equipment is updated or not can be determined based on the equipment information of the first equipment, so that equipment faults of the first equipment caused by application updating can be reduced or even avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of device control, and in particular to an application updating method, device, electronic device and storage medium. Background Art

[0002] At present, the device information such as the hardware configuration of the device is becoming more and more diverse. Among them, the above hardware configuration includes different screen sizes, processor capabilities, storage space and other characteristics. This diversity requires the update of the application software installed in the device to adapt to the specific needs of different devices to ensure functional compatibility and performance optimization.

[0003] Currently, device manufacturers rely on unified software update systems to push updates to operating systems and applications. However, these systems are often designed without fully considering the differences between different devices, especially when dealing with a large number of different models and batches of devices. For example, traditional update systems for Android smart TVs often adopt a "one-size-fits-all" update strategy, that is, the same software version is pushed to all devices regardless of hardware configuration. This approach ignores the impact that hardware differences may have on software performance and stability, and sometimes even causes the software to be incompatible with certain hardware configurations, causing the system to crash or "brick".

[0004] It can be seen that how to reduce device failures caused by application updates is a technical issue worthy of attention. Summary of the invention

[0005] In view of this, in order to solve some or all of the above technical problems, the embodiments of the present application provide an application updating method, device, electronic device and storage medium.

[0006] In a first aspect, an embodiment of the present application provides an application update method, the method comprising:

[0007] Acquire device information of a first device, wherein the target application is installed in the first device;

[0008] Determining whether the current version of the target application is the target version to be updated;

[0009] If the current version is not the target version, determining whether to update the current version of the target application to the target version based on the device information;

[0010] In a case where it is determined to update the current version of the target application to the target version, the first device is controlled to update the current version of the target application to the target version.

[0011] In a possible implementation, determining whether to update the current version of the target application to the target version based on the device information includes:

[0012] Acquire update information of the first device, wherein the update information indicates an update preference of a user of the first device for an application installed on the first device;

[0013] Based on the device information and the update information, it is determined whether to update the current version of the target application to the target version.

[0014] In a possible implementation manner, the update information indicates the application type of the application authorized to be updated; and

[0015] The determining, based on the device information and the update information, whether to update the current version of the target application to the target version includes:

[0016] Determining whether the target application belongs to the application type;

[0017] In a case where the target application belongs to the application type, determining whether to update the current version of the target application to the target version based on the device information;

[0018] When the target application does not belong to the application type, it is determined that there is no need to update the current version of the target application to the target version.

[0019] In a possible implementation manner, the update information indicates a system function module that is authorized to be updated; and

[0020] The determining, based on the device information and the update information, whether to update the current version of the target application to the target version includes:

[0021] Determining whether the target application is the system function module;

[0022] In a case where the target application is the system function module, determining whether to update the current version of the target application to the target version based on the device information;

[0023] When the target application is not the system function module, it is determined that there is no need to update the current version of the target application to the target version.

[0024] In one possible implementation,

[0025] The first device is a television; and / or

[0026] The device information represents at least one of the following: operating system, device architecture, whether a voice remote control is included, screen size, time to market, and device identification information.

[0027] In a possible implementation, when the method is applied to a second device, determining whether to update the current version of the target application to the target version based on the device information includes:

[0028] Obtaining a target version of the target application to be updated;

[0029] Determine at least one device information matching the target version from a preset device information set to obtain a device information subset;

[0030] Determine whether the device information of the first device belongs to the device information subset to obtain a determination result;

[0031] Based on the determination result, it is determined whether to update the current version of the target application to the target version.

[0032] In one possible implementation,

[0033] In the case where the method is applied to the first device, controlling the first device to update the current version of the target application to the target version includes: downloading and installing an installation package of the target application of the target version to update the current version of the target application to the target version; or

[0034] When the method is applied to a second device, controlling the first device to update the current version of the target application to the target version includes: sending an installation package of the target application of the target version to the first device, so that the first device updates the current version of the target application to the target version.

[0035] In a second aspect, an embodiment of the present application provides an application updating device, the device comprising:

[0036] An acquiring unit, configured to acquire device information of a first device, wherein the target application is installed in the first device;

[0037] A first determining unit, configured to determine whether a current version of the target application is a target version to be updated;

[0038] a second determining unit, configured to determine, based on the device information, whether to update the current version of the target application to the target version if the current version is not the target version;

[0039] A control unit is used to control the first device to update the current version of the target application to the target version when it is determined that the current version of the target application is updated to the target version.

[0040] In a possible implementation, determining whether to update the current version of the target application to the target version based on the device information includes:

[0041] Acquire update information of the first device, wherein the update information indicates an update preference of a user of the first device for an application installed on the first device;

[0042] Based on the device information and the update information, it is determined whether to update the current version of the target application to the target version.

[0043] In a possible implementation manner, the update information indicates the application type of the application authorized to be updated; and

[0044] The determining, based on the device information and the update information, whether to update the current version of the target application to the target version includes:

[0045] Determining whether the target application belongs to the application type;

[0046] In a case where the target application belongs to the application type, determining whether to update the current version of the target application to the target version based on the device information;

[0047] When the target application does not belong to the application type, it is determined that there is no need to update the current version of the target application to the target version.

[0048] In a possible implementation manner, the update information indicates a system function module that is authorized to be updated; and

[0049] The determining, based on the device information and the update information, whether to update the current version of the target application to the target version includes:

[0050] Determining whether the target application is the system function module;

[0051] In a case where the target application is the system function module, determining whether to update the current version of the target application to the target version based on the device information;

[0052] When the target application is not the system function module, it is determined that there is no need to update the current version of the target application to the target version.

[0053] In one possible implementation,

[0054] The first device is a television; and / or

[0055] The device information represents at least one of the following: operating system, device architecture, whether a voice remote control is included, screen size, time to market, and device identification information.

[0056] In a possible implementation, when the apparatus is applied to a second device, determining whether to update the current version of the target application to the target version based on the device information includes:

[0057] Obtaining a target version of the target application to be updated;

[0058] Determine at least one device information matching the target version from a preset device information set to obtain a device information subset;

[0059] Determine whether the device information of the first device belongs to the device information subset to obtain a determination result;

[0060] Based on the determination result, it is determined whether to update the current version of the target application to the target version.

[0061] In one possible implementation,

[0062] In the case where the apparatus is applied to the first device, controlling the first device to update the current version of the target application to the target version includes: downloading and installing an installation package of the target application of the target version to update the current version of the target application to the target version; or

[0063] In the case where the apparatus is applied to a second device, controlling the first device to update the current version of the target application to the target version includes: sending the installation package of the target application of the target version to the first device, so that the first device updates the current version of the target application to the target version.

[0064] In a third aspect, an embodiment of the present application provides an electronic device, including:

[0065] Memory for storing computer programs;

[0066] The processor is used to execute the computer program stored in the memory, and when the computer program is executed, the method of any embodiment of the application updating method of the first aspect of the present application is implemented.

[0067] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method of any embodiment of the application update method of the first aspect described above is implemented.

[0068] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes a computer-readable code. When the computer-readable code runs on a device, the processor in the device implements a method as in any embodiment of the application update method of the first aspect above.

[0069] The application update method provided in the embodiment of the present application can obtain the device information of the first device, wherein the target application is installed in the first device, and then determine whether the current version of the target application is the target version to be updated, and then, if the current version is not the target version, determine whether to update the current version of the target application to the target version based on the device information, and then, if it is determined that the current version of the target application is updated to the target version, control the first device to update the current version of the target application to the target version. In this way, it can be ensured that the target version to be updated of the target application installed on the first device matches the device information of the first device, thereby reducing or even avoiding device failures of the first device caused by application updates. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

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

[0072] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0073] Figure 1 A flowchart of an application update method provided in an embodiment of the present application;

[0074] Figure 2 A flowchart of another application update method provided in an embodiment of the present application;

[0075] Figure 3 A flowchart of another application update method provided in an embodiment of the present application;

[0076] Figure 4 A schematic diagram of the structure of an application updating device provided in an embodiment of the present application;

[0077] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0078] Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. It should be noted that unless otherwise specifically stated, the relative arrangement of the components and steps, the numerical expressions and the numerical values ​​described in these embodiments do not limit the scope of the present application.

[0079] Those skilled in the art will understand that the terms "first" and "second" in the embodiments of the present application are only used to distinguish between different steps, devices, modules and other objects, and do not represent any specific technical meanings, nor do they indicate the logical order between them.

[0080] It should also be understood that in this embodiment, “plurality” may refer to two or more than two, and “at least one” may refer to one, two or more than two.

[0081] It should also be understood that any component, data or structure mentioned in the embodiments of the present application can generally be understood as one or more, unless explicitly limited or otherwise indicated in the context.

[0082] In addition, the term "and / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this application generally indicates that the associated objects before and after are in an "or" relationship.

[0083] It should also be understood that the description of the various embodiments in this application focuses on the differences between the various embodiments, and the same or similar aspects thereof can be referenced to each other, and for the sake of brevity, they will not be described one by one.

[0084] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the present application, its application, or uses.

[0085] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the above-mentioned technologies, methods, and equipment should be considered as part of the specification.

[0086] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0087] It should be noted that, in the absence of conflict, the embodiments in this application and the features in the embodiments can be combined with each other. To facilitate the understanding of the embodiments of the present application, the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0088] In order to solve the technical problem of how to reduce device failures caused by application updates in the prior art, the present application provides an application update method, apparatus, electronic device and storage medium, which can reduce or even avoid device failures caused by application updates in a first device.

[0089] Figure 1 A flow chart of an application update method provided for an embodiment of the present application. This method can be applied to one or more electronic devices such as smart TVs, smart phones, laptops, desktop computers, portable computers, servers, etc. In addition, the execution subject of this method can be hardware or software. When the above-mentioned execution subject is hardware, the execution subject can be one or more of the above-mentioned electronic devices. For example, a single electronic device can execute this method, or multiple electronic devices can cooperate with each other to execute this method. When the above-mentioned execution subject is software, this method can be implemented as multiple software or software modules, or it can be implemented as a single software or software module. It is not specifically limited here.

[0090] like Figure 1 As shown, the method specifically includes:

[0091] Step 101: Obtain device information of a first device, wherein a target application is installed in the first device.

[0092] In this embodiment, the first device may include but is not limited to: a smart TV, a smart phone, etc. The system of the first device may be an Android system or other systems.

[0093] The target application may be an application installed in the first device. As an example, the target application may include but is not limited to: video playback software, audio playback software, shopping software, system software, etc.

[0094] The device information may be any information of the first device. As an example, the device information may be hardware configuration information of the first device, or may be production batch information of the first device.

[0095] In some optional implementations of this embodiment, the first device is a television; and / or

[0096] The device information represents at least one of the following: operating system, device architecture, whether a voice remote control is included, screen size, time to market, and device identification information.

[0097] Step 102: Determine whether the current version of the target application is the target version to be updated.

[0098] In this embodiment, the current version of the target application may be a version of the target application installed by the first device.

[0099] The target version may be a version of the target application to be updated. As an example, the target version may be the latest version of the target application.

[0100] Step 103 : When the current version is not the target version, determine whether to update the current version of the target application to the target version based on the device information.

[0101] In this embodiment, multiple methods may be used to determine whether to update the current version of the target application to the target version based on the device information.

[0102] In some optional implementations of this embodiment, when the method is applied to a second device, the following method may be used to determine whether to update the current version of the target application to the target version based on the device information:

[0103] The first step is to obtain the target version of the target application to be updated.

[0104] The second step is to determine at least one device information matching the target version from the preset device information set to obtain a device information subset.

[0105] Among them, the preset device information set may include multiple device information. In practice, for each device information in the preset device information set, it can be determined whether the device (e.g., the first device) represented by the device information supports or authorizes the installation of the target application of the target version. In the case where the device represented by the device information supports and authorizes the installation of the target application of the target version, it can be determined that the device information matches the target version; in the case where the device represented by the device information does not support or is not authorized to install the target application of the target version, it can be determined that the device information does not match the target version.

[0106] The device information subset may be a set of device information in a preset device information set that matches the target version.

[0107] The third step is to determine whether the device information of the first device belongs to the device information subset to obtain a determination result.

[0108] The determination result may indicate whether the device information of the first device belongs to the device information subset.

[0109] The fourth step is to determine whether to update the current version of the target application to the target version based on the determination result.

[0110] As an example, when the determination result indicates that the device information of the first device belongs to the device information subset, the current version of the target application can be updated to the target version; when the determination result indicates that the device information of the first device does not belong to the device information subset, there is no need to update the current version of the target application to the target version.

[0111] In addition, the second device may be another electronic device other than the first device. As an example, the second device may be a server.

[0112] Optionally, the fourth step may be performed in other ways, which will be described later and will not be described in detail here.

[0113] It can be understood that in the above optional implementation, by presetting the device information set, it can be determined more quickly whether to update the current version of the target application to the target version.

[0114] Step 104: When it is determined that the current version of the target application is updated to the target version, control the first device to update the current version of the target application to the target version.

[0115] In this embodiment, when it is determined that the current version of the target application is updated to the target version, the first device may first download the installation package of the target application of the target version, and then install the installation package to update the current version of the target application to the target version.

[0116] In some optional implementations of the present embodiment, when the method is applied to the first device, the following method can be used to control the first device to update the current version of the target application to the target version: download and install the installation package of the target application of the target version to update the current version of the target application to the target version.

[0117] It can be understood that in the above optional implementation, the first device can determine whether to update the target application installed by it based on its device information. In this way, the first device can filter the applications it needs to update by itself, thereby reducing or even avoiding device failures of the first device caused by application updates.

[0118] In some optional implementations of the present embodiment, when the method is applied to a second device, the following method can be used to control the first device to update the current version of the target application to the target version: send the installation package of the target application of the target version to one or more of the first devices, so that one or more of the first devices update the current version of the target application to the target version.

[0119] The second device may be another electronic device other than the first device. As an example, the second device may be a server.

[0120] It can be understood that in the above optional implementation, the second device can determine whether to update the target application installed by the first device based on the device information of the first device. In this way, the second device can batch update one or more applications that need to be updated by the first device, thereby improving the update efficiency of the first device.

[0121] The application update method provided in the embodiment of the present application can obtain the device information of the first device, wherein the target application is installed in the first device, and then determine whether the current version of the target application is the target version to be updated, and then, if the current version is not the target version, determine whether to update the current version of the target application to the target version based on the device information, and then, if it is determined that the current version of the target application is updated to the target version, control the first device to update the current version of the target application to the target version. In this way, it can be ensured that the target version to be updated of the target application installed on the first device matches the device information of the first device, thereby reducing or even avoiding device failures of the first device caused by application updates.

[0122] Figure 2 A flowchart of another application updating method provided in an embodiment of the present application.

[0123] like Figure 2 As shown, the method specifically includes:

[0124] Step 201: Acquire device information of a first device, wherein the target application is installed in the first device.

[0125] In this embodiment, step 201 and Figure 1Step 101 in the corresponding embodiment is basically the same and will not be described again here.

[0126] Step 202: Determine whether the current version of the target application is the target version to be updated.

[0127] In this embodiment, step 202 and Figure 1 Step 102 in the corresponding embodiment is basically the same and will not be described again here.

[0128] Step 203: When the current version is not the target version, update information of the first device is obtained, wherein the update information indicates an update preference of a user of the first device for an application installed on the first device.

[0129] In this embodiment, the user of the first device may be a user who uses the first device.

[0130] The update information may be set via the user object of the first device. As an example, the update information may indicate the update time determined by the user object of the first device, the application type of the application authorized to be updated, the system function module authorized to be updated, etc.

[0131] Step 204: Determine whether to update the current version of the target application to the target version based on the device information and the update information.

[0132] In this embodiment, multiple methods may be used to determine whether to update the current version of the target application to the target version based on the device information and the update information.

[0133] In some optional implementations of this embodiment, the update information indicates the application type of the application authorized to be updated.

[0134] As an example, the above application types may include at least one of the following: shopping applications, video playback applications, audio playback applications, screen projection applications, etc.

[0135] On this basis, the following method may be used to determine whether to update the current version of the target application to the target version based on the device information and the update information:

[0136] The first step is to determine whether the target application belongs to the application type.

[0137] In the second step, if the target application belongs to the application type, based on the device information, determine whether to update the current version of the target application to the target version; or, if the target application does not belong to the application type, determine that it is not necessary to update the current version of the target application to the target version.

[0138] Here, as to how to determine whether to update the current version of the target application to the target version based on the device information, please refer to the above description, which will not be repeated here.

[0139] It can be understood that in the above optional implementation, the user of the first device can set the application type that needs to be updated by himself. Thus, the target application is updated only when the installed version of the target application of the specified application type is inconsistent with the target version and the target version matches the device information of the first device. In this way, not only can the device failure of the first device caused by application update be reduced or even avoided, but also the update of the target application can meet the differentiated update requirements of different users and realize the update of applications of the specified application type.

[0140] In some optional implementations of this embodiment, the update information indicates the system function module that is authorized to be updated.

[0141] The system of the first device can realize multiple functions. The system function module can be used to realize one or more functions. As an example, the system function module can be used to realize at least one of the following functions: image processing function, Bluetooth function, audio playback function, wireless transmission function, etc.

[0142] On this basis, the following method may be used to determine whether to update the current version of the target application to the target version based on the device information and the update information:

[0143] The first step is to determine whether the target application is the system function module.

[0144] In the second step, when the target application is the system function module, based on the device information, determine whether to update the current version of the target application to the target version; when the target application is not the system function module, determine that it is not necessary to update the current version of the target application to the target version.

[0145] Here, as to how to determine whether to update the current version of the target application to the target version based on the device information, please refer to the above description, which will not be repeated here.

[0146] It can be understood that in the above optional implementation, the user of the first device can set the system function modules that need to be updated by itself. Therefore, the target application is updated only when the target application of the first device is the system function module set by the user of the first device and the target version matches the device information of the first device. In this way, not only can the device failure of the first device caused by application update be reduced or even avoided, but also the update of the target application can meet the differentiated update requirements of different users and more fine-grained application updates can be achieved.

[0147] Step 205: When it is determined that the current version of the target application is updated to the target version, control the first device to update the current version of the target application to the target version.

[0148] In this embodiment, step 205 and Figure 1 Step 104 in the corresponding embodiment is basically the same and will not be described again here.

[0149] It should be noted that, in addition to the above contents, this embodiment may also include Figure 1 The corresponding technical features described in the corresponding embodiments are realized Figure 1 For details on the technical effects of the application update method shown, please refer to Figure 1 For the sake of brevity, the relevant description is not repeated here.

[0150] The application update method provided in the embodiment of the present application can make the update of the target application meet the differentiated update requirements of different users by using the first device to set the update preference of the application.

[0151] The following takes the first device as a smart TV as an example to exemplify the embodiments of the present application, but it should be noted that the embodiments of the present application may have the features described below, but the following description does not constitute a limitation on the scope of protection of the embodiments of the present application.

[0152] With the rapid development of the smart TV market, the hardware configuration of devices is becoming more and more diverse, including different screen sizes, processor capabilities, storage space, and other features such as voice remote control. This diversity requires software updates to adapt to the specific needs of different hardware to ensure functional compatibility and optimal performance.

[0153] Currently, most smart TV manufacturers rely on unified software update systems, such as GOTA (Google Over the Air Technology) system, to push updates for operating systems and applications. However, these systems are often not designed to fully consider the differences between different hardware configurations, especially when dealing with a large number of different models and batches of devices.

[0154] The related technologies usually have the following disadvantages:

[0155] a. Update the generalization of the system:

[0156] Traditional update systems for Android smart TVs often adopt a "one-size-fits-all" update strategy, which means that the same software version is pushed to all devices regardless of their hardware configuration. This approach ignores the impact that hardware differences may have on software performance and stability, and sometimes even causes software to be incompatible with certain hardware configurations, causing system crashes or "bricks".

[0157] b. Lack of targeted update control:

[0158] The related technology fails to provide an effective mechanism to identify and distinguish devices with different hardware configurations, thus failing to implement targeted update strategies. This not only increases the risk of upgrade failure, but may also lead to a decline in user experience, as inappropriate software updates may reduce device performance or cause incompatibility of new features.

[0159] c. Insufficient order and batch management:

[0160] In mass production, the same model of TV may have different hardware configurations due to different production batches or orders. Existing systems are usually unable to distinguish these differences, resulting in the inability to customize software updates for specific orders or batches, thereby increasing management complexity and operating costs.

[0161] In view of this, this solution proposes a smart TV software update management system based on the attributes of ro.oem.key1 (that is, the above-mentioned device information), which achieves more refined software update control by accurately identifying the hardware configuration of the equipment in each batch of production orders. The system distinguishes different orders or batches based on the detailed information encoded in ro.oem.key1, such as screen size, whether a voice remote control is included, year of production, and other OEM (original equipment manufacturer) custom parameters, allowing centralized management and updates of groups of devices with the same or similar hardware configurations. The custom parameter part in this solution is the internal order number or PID (Plan Identification Number).

[0162] Specifically, see Figure 3 , this scheme includes the following steps:

[0163] a. Generation and distribution of OEM Key:

[0164] During the production process of Android Smart TVs, a unique ro.oem.key1 will be generated for each batch of orders to ensure uniform device configuration.

[0165] ro.oem.key1 corresponds to the DeviceProfile.ini file and will be packaged together when making the image burning package. This specific ro.oem.key1 can be written to the fixed storage of each TV and serve as the unique identifier of the batch throughout the life cycle of the device.

[0166] ro.oem.key1 is a string of up to 32 characters that uniquely identifies the hardware configuration and production batch of the smart TV and is stored in a specific partition file of the system. Each part of this code carries key information, allowing the software update system to identify and execute the update strategy suitable for a specific device.

[0167] 1-3 digits: "ATV" - This is a fixed string indicating that the project is Android TV.

[0168] Positions 4-5: "00" - This is a fixed value indicating the current version of ro.oem.key1. No other value may be used until Google releases a schema change.

[0169] 6 bits: Indicates whether the voice remote control is included (0 or 1).

[0170] 0 0 Not included

[0171] 1 0 included

[0172] 7-9 digits: Indicates the screen size, expressed as three digits (for example, "065" means a 65-inch screen).

[0173] For non-TV devices, this part is set to "000".

[0174] Digits 10-11: Indicates the year of launch, using two digits (for example, "20" means launch in 2020).

[0175] 12-32 bits: The remaining 21 characters are free for the OEM to use to identify the specific device in the GOTA system.

[0176] b. Update detection and distribution:

[0177] Each TV first reports its ro.oem.key1 when connecting to the update server to check for new software updates.

[0178] The update system will only allow TV batches with a specific ro.oem.key1 to receive updates based on the rules configured on the server. This ensures that each update is strictly targeted to the TV batch with the corresponding hardware configuration.

[0179] c. Configuration update and control:

[0180] In the background update management system, the administrator can set which specific ro.oem.key1 (that is, the above-mentioned device information subset) devices are to be updated, or exclude certain ro.oem.key1 to avoid updating specific batches.

[0181] Such a setup ensures that only eligible batches of devices receive update notifications, and other non-matching devices will not be interfered with or receive inappropriate software updates, thereby minimizing update errors and device compatibility issues.

[0182] This refined update control and device management strategy can significantly improve the accuracy and security of software updates, ensuring that each batch of devices can get the update that best suits its hardware configuration while avoiding device failures caused by inappropriate updates. This not only improves user satisfaction, but also enhances brand reputation and market competitiveness.

[0183] In addition, the following solutions can be further adopted:

[0184] a. Cloud control update:

[0185] The cloud platform is used to dynamically manage the ro.oem.key1 and corresponding update policies of each device, rather than writing them fixedly when the device is produced. This allows for flexible response to hardware upgrades or changes, and real-time adjustment of update policies.

[0186] b. User chooses to update content:

[0187] Allow users to choose to receive specific types of updates (such as security updates, feature improvements, or system optimization) through device settings, providing a more personalized update experience.

[0188] c. Modular update package:

[0189] Develop independent update modules (such as security modules, multimedia playback modules, etc.), and users can choose to update specific modules as needed. This reduces the risk of full system updates and saves data usage.

[0190] d. Open API update interface:

[0191] Providing open APIs allows third-party developers or partners to develop and push software updates based on public interface documents. This strategy can accelerate innovation and attract participation from a wider developer community.

[0192] It should be noted that, in addition to the contents recorded above, this embodiment may also include the technical features described in the above embodiments, so as to achieve the technical effects of the application update method shown above. Please refer to the above description for details. For the sake of brevity, it will not be repeated here.

[0193] The application update solution provided in the embodiment of the present application can customize the update strategy based on the batch OEM Key. By introducing a batch-specific ro.oem.key1 to control and manage software updates, manufacturers can be allowed to customize software updates for different batches of hardware configurations to ensure that each batch of devices can receive the most appropriate updates. In addition, data separation technology can be applied to OEM Key writing in the production process: data separation technology is applied in the production process of smart TVs to directly write the ro.oem.key1 of each batch of orders into the device. Such technical implementation ensures that a clear update path is established for each device during the production stage, thereby greatly improving the efficiency and security of subsequent software maintenance and updates. In terms of fine control of the update strategy, the update server can determine whether to allow the update based on the ro.oem.key1 reported by the TV. This fine control of the strategy can reduce unnecessary update pushes and potential update errors, especially when facing batches with special hardware configurations, which can reduce or even avoid device failures caused by application updates.

[0194] Figure 4 A schematic diagram of the structure of an application updating device provided in an embodiment of the present application. Specifically comprising:

[0195] An acquiring unit 401 is configured to acquire device information of a first device, wherein the target application is installed in the first device;

[0196] A first determining unit 402 is used to determine whether the current version of the target application is a target version to be updated;

[0197] A second determining unit 403 is configured to determine whether to update the current version of the target application to the target version based on the device information if the current version is not the target version;

[0198] The control unit 404 is configured to control the first device to update the current version of the target application to the target version when it is determined that the current version of the target application is updated to the target version.

[0199] In a possible implementation, determining whether to update the current version of the target application to the target version based on the device information includes:

[0200] Acquire update information of the first device, wherein the update information indicates an update preference of a user of the first device for an application installed on the first device;

[0201] Based on the device information and the update information, it is determined whether to update the current version of the target application to the target version.

[0202] In a possible implementation manner, the update information indicates the application type of the application authorized to be updated; and

[0203] The determining, based on the device information and the update information, whether to update the current version of the target application to the target version includes:

[0204] Determining whether the target application belongs to the application type;

[0205] In a case where the target application belongs to the application type, determining whether to update the current version of the target application to the target version based on the device information;

[0206] When the target application does not belong to the application type, it is determined that there is no need to update the current version of the target application to the target version.

[0207] In a possible implementation manner, the update information indicates a system function module that is authorized to be updated; and

[0208] The determining, based on the device information and the update information, whether to update the current version of the target application to the target version includes:

[0209] Determining whether the target application is the system function module;

[0210] In a case where the target application is the system function module, determining whether to update the current version of the target application to the target version based on the device information;

[0211] When the target application is not the system function module, it is determined that there is no need to update the current version of the target application to the target version.

[0212] In one possible implementation,

[0213] The first device is a television; and / or

[0214] The device information represents at least one of the following: operating system, device architecture, whether a voice remote control is included, screen size, time to market, and device identification information.

[0215] In a possible implementation, when the apparatus is applied to a second device, determining whether to update the current version of the target application to the target version based on the device information includes:

[0216] Obtaining a target version of the target application to be updated;

[0217] Determine at least one device information matching the target version from a preset device information set to obtain a device information subset;

[0218] Determine whether the device information of the first device belongs to the device information subset to obtain a determination result;

[0219] Based on the determination result, it is determined whether to update the current version of the target application to the target version.

[0220] In one possible implementation,

[0221] In the case where the apparatus is applied to the first device, controlling the first device to update the current version of the target application to the target version includes: downloading and installing an installation package of the target application of the target version to update the current version of the target application to the target version; or

[0222] In the case where the apparatus is applied to a second device, controlling the first device to update the current version of the target application to the target version includes: sending the installation package of the target application of the target version to the first device, so that the first device updates the current version of the target application to the target version.

[0223] The application updating device provided in this embodiment may be as follows Figure 4 The application update device shown in can execute all the steps of the application update methods described above, thereby achieving the technical effects of the application update methods described above. Please refer to the above related description for details. For the sake of brevity, it will not be repeated here.

[0224] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application, Figure 5The electronic device 500 shown includes: at least one processor 501, a memory 502, at least one network interface 504 and other user interfaces 503. The various components in the electronic device 500 are coupled together via a bus system 505. It is understood that the bus system 505 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 505 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, the bus system 505 is not shown in FIG. Figure 5 Various buses are labeled as bus system 505 .

[0225] The user interface 503 may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touch pad, or a touch screen).

[0226] It can be understood that the memory 502 in the embodiment of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct RAM bus random access memory (DRRAM). The memory 502 described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0227] In some implementations, the memory 502 stores the following elements, executable units or data structures, or a subset thereof, or an extended set thereof: an operating system 5021 and an application program 5022 .

[0228] Among them, the operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application 5022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present application can be included in the application 5022.

[0229] In this embodiment, by calling the program or instruction stored in the memory 502, specifically, the program or instruction stored in the application 5022, the processor 501 is used to execute the method steps provided by each method embodiment, for example, including:

[0230] Acquire device information of a first device, wherein the target application is installed in the first device;

[0231] Determining whether the current version of the target application is the target version to be updated;

[0232] If the current version is not the target version, determining whether to update the current version of the target application to the target version based on the device information;

[0233] In a case where it is determined to update the current version of the target application to the target version, the first device is controlled to update the current version of the target application to the target version.

[0234] The method disclosed in the above embodiment of the present application can be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the processor 501. The above processor 501 can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to execute, or the hardware and software units in the decoding processor can be executed. The software unit can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and completes the steps of the above method in combination with its hardware.

[0235] It is understood that the embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit may be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPDevice, DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the above functions of the present application, or a combination thereof.

[0236] For software implementation, the technology described above in this article can be implemented by a unit that performs the functions described above in this article. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0237] The electronic device provided in this embodiment may be Figure 5 The electronic device shown in can execute all the steps of the above-mentioned application update methods, thereby achieving the technical effects of the above-mentioned application update methods. Please refer to the above related description for details. For the sake of brevity, it will not be repeated here.

[0238] The embodiment of the present application also provides a storage medium (computer-readable storage medium). The storage medium here stores one or more programs. The storage medium may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a read-only memory, a flash memory, a hard disk or a solid-state drive; the memory may also include a combination of the above-mentioned types of memory.

[0239] When one or more programs in the storage medium can be executed by one or more processors, the above-mentioned application updating method executed on the electronic device side can be implemented.

[0240] The processor is used to execute the application update program stored in the memory to implement the following steps of the application update method performed on the electronic device side:

[0241] Acquire device information of a first device, wherein the target application is installed in the first device;

[0242] Determining whether the current version of the target application is the target version to be updated;

[0243] If the current version is not the target version, determining whether to update the current version of the target application to the target version based on the device information;

[0244] In a case where it is determined to update the current version of the target application to the target version, the first device is controlled to update the current version of the target application to the target version.

[0245] The professionals should also be further aware that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0246] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0247] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0248] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. An application update method, characterized in that: The method comprises: Acquire device information of a first device, wherein the target application is installed in the first device; Determining whether the current version of the target application is the target version to be updated; If the current version is not the target version, determining whether to update the current version of the target application to the target version based on the device information; In a case where it is determined to update the current version of the target application to the target version, the first device is controlled to update the current version of the target application to the target version.

2. The method according to claim 1, characterized in that The determining, based on the device information, whether to update the current version of the target application to the target version includes: Acquire update information of the first device, wherein the update information indicates an update preference of a user of the first device for an application installed on the first device; Based on the device information and the update information, it is determined whether to update the current version of the target application to the target version.

3. The method according to claim 2, characterized in that The update information indicates the application type of the application authorized to be updated; as well as The determining, based on the device information and the update information, whether to update the current version of the target application to the target version includes: Determining whether the target application belongs to the application type; In a case where the target application belongs to the application type, determining whether to update the current version of the target application to the target version based on the device information; When the target application does not belong to the application type, it is determined that there is no need to update the current version of the target application to the target version.

4. The method according to claim 2, characterized in that: The update information indicates the system function modules that are authorized to be updated; as well as The determining, based on the device information and the update information, whether to update the current version of the target application to the target version includes: Determining whether the target application is the system function module; In a case where the target application is the system function module, determining whether to update the current version of the target application to the target version based on the device information; When the target application is not the system function module, it is determined that there is no need to update the current version of the target application to the target version.

5. The method according to claim 1, characterized in that The first device is a television; and / or The device information represents at least one of the following: operating system, device architecture, whether a voice remote control is included, screen size, time to market, and device identification information.

6. The method according to claim 1, characterized in that In the case where the method is applied to a second device, determining whether to update the current version of the target application to the target version based on the device information includes: Obtaining a target version of the target application to be updated; Determine at least one device information matching the target version from a preset device information set to obtain a device information subset; Determine whether the device information of the first device belongs to the device information subset to obtain a determination result; Based on the determination result, it is determined whether to update the current version of the target application to the target version.

7. The method according to any one of claims 1 to 5, characterized in that: In the case where the method is applied to the first device, controlling the first device to update the current version of the target application to the target version includes: downloading and installing an installation package of the target application of the target version to update the current version of the target application to the target version; or When the method is applied to a second device, controlling the first device to update the current version of the target application to the target version includes: sending an installation package of the target application of the target version to the first device, so that the first device updates the current version of the target application to the target version.

8. An application updating device, characterized in that: The device comprises: An acquiring unit, configured to acquire device information of a first device, wherein the target application is installed in the first device; A first determining unit, configured to determine whether a current version of the target application is a target version to be updated; a second determining unit, configured to determine, based on the device information, whether to update the current version of the target application to the target version if the current version is not the target version; A control unit is used to control the first device to update the current version of the target application to the target version when it is determined that the current version of the target application is updated to the target version.

9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor is used to execute a computer program stored in the memory, and when the computer program is executed, the application update method of any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the application updating method of any one of claims 1 to 7 is implemented.