CMS preloading method and device, storage medium and product

Abstract

The invention discloses a CMS pre-installation method and device of a digital signage, a storage medium and a product, the CMS pre-installation method of the digital signage is applied to a terminal device, the CMS pre-installation method of the digital signage comprises the steps that when the terminal device compiles a system, a compressed installation package of the CMS is pre-installed to a system partition of the terminal device, and the terminal device endows a system main program with an access right to the system partition; the installation process of the compressed installation package of the CMS from the system partition to the data partition is predefined in the system partition, and the terminal device endows a user with the access permission to the data partition.

Description

Technical Field

[0001] The present application relates to the field of digital signage technology, and in particular to a CMS preinstallation method, device, storage medium and product. Background Art

[0002] Digital signage refers to a multimedia professional audio-visual system that uses large-screen terminal display devices to publish advertising, commercial, financial and entertainment information. Digital signage is widely used in large shopping malls, supermarkets, hotel lobbies, restaurants, cinemas and other places where people gather.

[0003] Nowadays, digital signage advertising machines can be seen everywhere in major shopping malls and stores. Traditional stand-alone digital signage has high maintenance costs and is prone to display errors, so the network information distribution system CMS has gradually become popular. CMS refers to a system that provides a variety of information services to the public based on Internet technology. In order to achieve safe and batch network information distribution, many large customers configure terminal devices themselves; specifically, by installing CMS on the terminal device, the terminal device can connect to multiple digital signage devices, so that CMS can push information to multiple digital signage devices.

[0004] Normally, the terminal device pre-installs the CMS installation package in the terminal device's own data partition, such as the data / app partition. The terminal device usually grants users access to the data partition, which means that the CMS installation package and the CMS installation process can be read, written, modified, and deleted by the user at will. If malicious operations are performed, in serious cases, the CMS installed at the end may suffer from data tampering, application deletion, or even system failure.

[0005] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0006] The main purpose of this application is to provide a CMS pre-installation method, device, storage medium and product for digital signage, aiming to solve the problem in the prior art that terminal devices usually grant users access rights to data partitions, which causes users to interfere with the CMS installation package and the CMS installation process through the access rights to the above-mentioned data partitions, resulting in technical problems such as data tampering, application deletion and even system failure in the finally installed CMS.

[0007] To achieve the above purpose, the present application proposes a CMS pre-installation method for digital signage, which is applied to a terminal device. The CMS pre-installation method includes:

[0008] When the terminal device is compiling the system, the system main program pre-installs the compressed installation package of CMS to the system partition of the terminal device, wherein the system partition only allows the system main program to have access rights;

[0009] The system main program predefines the preinstallation process of CMS from the system partition to the data partition.

[0010] Specifically, as a preferred embodiment, the method further includes:

[0011] When the terminal device starts the system, it is determined whether there is a pre-installed mark of CMS in the data partition, wherein the data partition allows the user to have access rights;

[0012] If it is determined that the data partition has a pre-installed flag, run CMS; or,

[0013] If it is determined that the data partition does not have a pre-installation mark, the compressed installation package is decompressed according to the pre-installation process, the decompressed CMS is installed in the data partition, and a pre-installation mark is generated in the data partition.

[0014] Preferably, in the above CMS preinstallation method, when the above terminal device starts the system, the step of determining whether there is a CMS preinstallation mark in the data partition includes:

[0015] Determine whether the terminal device is running normally or resetting when starting the system;

[0016] If the terminal device is reset, the pre-installation mark is cleared, and the step of determining whether the data partition has the pre-installation mark of the CMS is performed.

[0017] Preferably, the CMS preinstallation method further comprises, after the steps of decompressing the compressed installation package, installing the decompressed CMS into the data partition and generating a preinstallation identifier in the data partition:

[0018] When receiving the user uninstallation instruction, uninstall the CMS from the data partition and retain the pre-installation mark of the data partition;

[0019] When the terminal device restarts the system, the step of determining whether the data partition has a pre-installed identifier of the CMS is performed again.

[0020] Preferably, the CMS preinstallation method comprises the steps of decompressing the compressed installation package, installing the decompressed CMS into the data partition and generating a preinstallation mark in the data partition:

[0021] Decompress the compressed installation package in the system partition to obtain the CMS application package and pre-installed identification file;

[0022] Copy the application package and pre-installed identification file to the data partition respectively;

[0023] The system main program starts the package management service PKMS, and PKMS scans the application directory of the data partition;

[0024] When PKMS scans an application package, it installs the application package in the data partition.

[0025] Preferably, in the above CMS preinstallation method, the system partition is provided with an application whitelist, and the application whitelist is used to filter the encryption verification permissions of the application; when the PKMS scans the application package, the step of installing the application package in the data partition includes:

[0026] Use PKMS to query the application whitelist and determine whether CMS is in the application whitelist;

[0027] If it is determined that the CMS is in the application whitelist, the encryption verification machine permission of the CMS is skipped and the pre-installation process of the application package in the data partition is started.

[0028] Preferably, the CMS preinstallation method further comprises, after the step of installing the decompressed CMS to the data partition and generating a preinstallation identifier in the data partition:

[0029] When the CMS is installed, the MD5 value of the installed CMS is calculated and uploaded to the blockchain storage;

[0030] Calculate the MD5 value of CMS at predetermined intervals, and compare the calculated MD5 value with the MD5 value stored in the blockchain for consistency;

[0031] When the calculated MD5 value is inconsistent with the MD5 value stored in the blockchain, the pre-installed logo is cleared and the terminal device is controlled to restart the system.

[0032] In addition, to achieve the above-mentioned purpose, the present application also provides a terminal device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the CMS pre-installation method for digital signage as described in any of the above-mentioned technical solutions.

[0033] In addition, to achieve the above-mentioned purpose, the present application also provides a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the CMS pre-installation method for digital signage in any of the above-mentioned technical solutions are implemented.

[0034] In addition, to achieve the above objectives, the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the CMS pre-installation method for digital signage in any of the above technical solutions.

[0035] One or more technical solutions proposed in this application have at least the following technical effects:

[0036] When the terminal device is compiling the system, the terminal will package and compress the CMS application to obtain a compressed installation package of the CMS, and pre-install the compressed installation package into the system partition of the terminal device. The terminal device grants the system main program access rights to the system partition, but the user does not have access rights. Therefore, the user cannot arbitrarily read, write, modify, or delete the compressed installation package of the CMS, thereby ensuring the information security of the compressed installation package of the CMS. In addition, the installation process of the compressed installation package of the CMS from the system partition to the data partition is predefined in the system partition. Because the installation process is stored in the system partition as a system file, the user does not have access rights to the system partition, thereby preventing the user from operating the installation process of the CMS. Through the above-mentioned two-part operation of the compressed installation package of the CMS and the installation process of the CMS, the problem of the CMS installation package and the installation process of the CMS being arbitrarily read, written, modified, and deleted by the user, or even maliciously operated, is avoided. In this way, the security of the CMS information is guaranteed. In addition, even if the CMS is installed in the data partition, the user can access the data partition to read, write, modify or delete the CMS. In this way, the system partition only needs to reinstall the compressed installation package of the CMS to the data partition according to the above installation process, so that the CMS data can be restored. In summary, the information security of the CMS is guaranteed through the above method. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] 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.

[0038] 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.

[0039] Figure 1 A schematic diagram of a flow chart of a first CMS pre-installation method for digital signage provided in an embodiment of the present application;

[0040] Figure 2 For this application Figure 1 The illustrated embodiment provides a flow chart of a method for installing a CMS in a data partition;

[0041] Figure 3 For this application Figure 2 A schematic diagram of a flow chart of a method for installing a CMS when a terminal device is reset is provided in the illustrated embodiment;

[0042] Figure 4 A flow chart of a CMS uninstallation method provided in an embodiment of the present application;

[0043] Figure 5 For this application Figure 2 A schematic diagram of a flow chart of a CMS installation method provided in the illustrated embodiment;

[0044] Figure 6 This application Figure 5 A schematic diagram of a flow chart of a method for installing an application package provided in the illustrated embodiment;

[0045] Figure 7 It is a flow chart of a CMS data verification method provided in an embodiment of the present application;

[0046] Figure 8 is a flow chart of a second CMS preinstallation method for digital signage provided in an embodiment of the present application;

[0047] Fig. 9 It is a structural diagram of a terminal device provided in an embodiment of the present application.

[0048] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0049] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0050] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0051] The prior art has the following technical problems: Normally, when the CMS is directly installed on a terminal device, especially when the CMS can be granted excessive permissions, such as permissions to directly access the core area of ​​the system, the application may become a security risk. Usually, the CMS is installed in the data partition of the terminal device like ordinary applications, such as the data / app partition. The data partition allows users to have access rights, so users can read and delete the CMS, and even use the CMS's own permissions to perform malicious operations. If the CMS has security vulnerabilities or is maliciously exploited, it may be used by hackers to access or modify system data that should not be changed, or even control the entire device, causing data leakage, malicious software deletion, or even system crashes. Once the above problems occur, it will be difficult to recover the application and system.

[0052] In order to solve the above technical problems, the present application provides a solution, a CMS preinstallation solution, including: when the system is compiled, the system main program preinstalls the compressed installation package of CMS to the system partition of the terminal device, wherein the system partition only allows the system main program to have access rights; the system main program predefines the preinstallation process of CMS from the system partition to the data partition. The technical solution of the present application can solve the problem in the prior art that CMS is preinstalled in the data partition, CMS is preinstalled in the data partition, users have access rights, can read or delete the CMS, which is easy to cause data leakage, malicious deletion and even system crash.

[0053] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device that can realize the above functions, a computer-readable storage medium, etc.

[0054] In order to better understand the above technical solution, the exemplary embodiments of the present application will be described in more detail with reference to the accompanying drawings. Although the exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments shown here. On the contrary, these embodiments are provided to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0055] To achieve the above technical objectives, see Figure 1 , Figure 1 A flow chart of a CMS pre-installation method for a digital signage is provided for an embodiment of the present application, and is applied to a terminal device, wherein the terminal device includes a system partition and a data partition. The CMS pre-installation method includes:

[0056] S110: When the terminal device compiles the system, the compressed installation package of CMS is preinstalled in the system partition of the terminal device, wherein the system partition only allows the system main program to have access rights. The system partition here can be the system / prebuilt partition. In the system partition, since only the system main program is allowed to access and users are not allowed to access, users cannot operate the compressed installation package of the CMS. This can prevent users from reading and deleting the compressed installation package of the CMS, and can also prevent users from using the CMS's own permissions to perform malicious operations, thereby avoiding data tampering, malicious deletion, and system crashes.

[0057] S120: Predefine the preinstallation process of CMS from the system partition to the data partition in the system partition. The preinstallation process here is the process of installing CMS from the system partition to the data partition of the terminal device. By predefining the preinstallation process, the compressed installation package of CMS can be decompressed and installed from the system partition to the data partition. On the one hand, this can ensure that the functions of CMS are available to users and will not affect customer services; on the other hand, the installation process is predefined in the system partition, and the system partition is not open to users. Users cannot operate the installation process, which can ensure the correct installation of the compressed installation package of CMS to the data partition. Even if there is a problem with the CMS installed in the data partition or it is misoperated by the customer, such as data tampering or malicious deletion, the CMS can be restored through the above preinstallation process. Thereby ensuring the normal operation of CMS and meeting customer needs.

[0058] The technical solution provided by the embodiment of the present application is that when the terminal device is compiling the system, the terminal will package and compress the CMS application to obtain the compressed installation package of the CMS, and pre-install the compressed installation package into the system partition of the terminal device. The terminal device grants the system main program access rights to the system partition, but the user does not have access rights, so the user cannot arbitrarily read, write, modify, and delete the compressed installation package of the CMS, thus ensuring the information security of the compressed installation package of the CMS; in addition, the installation process of the compressed installation package of the CMS from the system partition to the data partition is predefined in the system partition, because the installation process is stored in the system partition as a system file, and the user does not have access rights to the system partition, thus the user cannot operate the installation process of the CMS. Through the above-mentioned two-part operation of the compressed installation package of the CMS and the installation process of the CMS, the problem of the CMS installation package and the installation process of the CMS being arbitrarily read, written, modified, and deleted by the user, or even maliciously operated, is avoided. In this way, the security of the CMS information is guaranteed. In addition, even if the CMS is installed in the data partition, the user can access the data partition to read, write, modify or delete the CMS. In this way, the system partition only needs to reinstall the compressed installation package of the CMS to the data partition according to the above installation process, so that the CMS data can be restored. In summary, the information security of the CMS is guaranteed through the above method.

[0059] In addition, for the installation and operation of CMS, see Figure 2 Specifically, as a preferred embodiment, the method further includes:

[0060] S130: When the terminal device starts the system, it determines whether there is a preinstallation mark of CMS in the data partition, wherein the data partition allows the user to have access rights. The preinstallation mark of CMS is written into the preinstallation mark file preinstall.txt. The preinstallation mark file preinstall.txt can be set in the compressed installation package of the above-mentioned CMS, and is installed in the data partition according to the above-mentioned preinstallation program after the first decompression. The preinstallation mark is contained in the above-mentioned preinstall.txt file, which is used to mark whether the CMS is effectively preinstalled in the data partition. Preinstallation means that it has been installed before the system is started, and the relevant installation operations of CMS are performed through the preinstallation mark.

[0061] S140: If it is determined that the data partition has a pre-installation mark, then run the CMS; the pre-installation mark is a label used to determine whether the CMS is successfully installed in the data partition. If the data partition has the pre-installation mark, then directly run the CMS.

[0062] or,

[0063] S150: If it is determined that there is no preinstallation mark in the data partition, the compressed installation package is decompressed according to the preinstallation process, the decompressed CMS is installed in the data partition and a preinstallation mark is generated in the data partition. If there is no preinstallation mark in the data partition, it means that the CMS has not been successfully installed in the data partition or is being installed for the first time. At this time, the compressed installation package can be decompressed according to the above-defined preinstallation process, the decompressed CMS is installed in the data partition and a preinstallation mark is generated in the data partition. The preinstallation mark can be pre-stored in the compressed installation package, and automatically generated in the system partition after decompression, and can be directly copied when installing the CMS to the data partition.

[0064] Specifically, the compressed installation package of CMS is pre-installed in the system / prebuilt partition. This application uses the init.rc command to start this process when the system is on boot based on the customized preinstall system process after solving a series of SELinux permission issues. It first determines whether the identification file preinstall.txt is in the data / app partition; if not, the application compressed installation package under system / prebuilt is unzipped and the application is copied to the data / app partition, together with the identification file preinstall.txt; otherwise, it proves that the application has been installed.

[0065] The technical solution provided in the embodiment of the present application allows third-party CMS applications to be installed only in data partitions, such as data / app partitions, for security reasons, so that users can uninstall them, but they need to be reinstalled after the system is reset. Because the data partition allows users to have access rights, users may tamper with data and maliciously delete CMS.

[0066] To solve the above problems, specifically, as a preferred embodiment, as Figure 3 As shown, in the above CMS preinstallation method, step S130: when the terminal device starts the system, the step of determining whether there is a CMS preinstallation mark in the data partition includes:

[0067] S131: Determine whether the system is running normally or resetting when it is started. Normal operation here means that when the terminal device starts the system, the system starts and runs according to the normal operation process; reset operation means that after the terminal device resets the system, the system starts and runs according to the reset operation process.

[0068] S132: If it is determined that the system is reset, the pre-installation mark is cleared, and the above step of determining whether there is a pre-installation mark of the CMS in the data partition is executed.

[0069] The technical solution provided by the embodiment of the present application is that when the CMS has problems such as data tampering, erroneous deletion or application crash, the terminal device can reset the system and reinstall the CMS. At this time, the pre-installation mark is cleared. After the pre-installation mark is cleared, the terminal device starts the system and jumps to the step of judging whether the data partition is in the pre-installation mark of the CMS. Because the pre-installation mark has been cleared, the step S150 is executed to decompress the compressed installation package in the system partition, install the decompressed CMS in the data partition, and generate the pre-installation mark in the data partition.

[0070] In this way, even if the user tampers with the data or maliciously deletes the CMS, the CMS can be reinstalled through the compressed installation package of the CMS in the system partition, and only the system needs to be reset.

[0071] In addition, as a preferred embodiment, Figure 4 As shown, the CMS preinstallation method further includes the following steps after step S150: decompressing the compressed installation package, installing the decompressed CMS to the data partition, and generating a preinstallation identifier in the data partition:

[0072] S210: When receiving a user uninstallation instruction, uninstall the CMS from the data partition, and retain the pre-installation mark of the data partition.

[0073] S220: When the terminal device restarts the system, the step of determining whether the data partition has a pre-installed mark of the CMS is executed again.

[0074] According to the technical solution provided in the embodiment of the present application, when the user manually uninstalls, the system will restart and the above-mentioned step of determining whether there is a pre-installed mark of CMS in the data partition will be executed again. In this way, because the pre-installed mark is retained, the traditional system startup method will not re-install the compressed installation package of the system partition to the data partition, so that the normal uninstall operation can be satisfied.

[0075] In addition, as a preferred embodiment, Figure 5 As shown, the CMS preinstallation method, step S150: decompressing the compressed installation package, installing the decompressed CMS to the data partition and generating a preinstallation mark in the data partition includes:

[0076] S151: decompress the compressed installation package in the system partition to obtain the CMS application package and the preinstallation identification file. For example, decompress the compressed installation package in the system partition system / prebuilt to obtain the CMS application package and the preinstallation identification file preinstall.txt.

[0077] S152: Copy the application package and the preinstallation identification file to the data partition respectively. The preinstallation identification file contains a preinstallation identification, which is used to confirm whether the application package has been installed to the data partition.

[0078] S153: The system main program starts the package management service PKMS, and PKMS scans the application directory of the data partition.

[0079] S154: When PKMS scans the application package, it installs the application package in the data partition.

[0080] The technical solution provided by the embodiment of the present application is that the specific CMS installation process is to decompress the compressed installation package in the system partition to obtain the above-mentioned application package and the pre-installed identification file, so that the system main program calls the package management service PKMS to install the above-mentioned package. PKMS is the core service of the Android system, which is mainly responsible for the management of the Package in the system, the installation, uninstallation and information query of the application program, etc. After PLMS is started, it can scan the app directory of each partition. In this way, when PKMS scans the application package, PKMS determines whether the package is the package of the above-mentioned CMS. If so, the above-mentioned encryption verification permission is skipped and the package is installed to the data partition. In the technical solution of the present application, the system checks the system application through the PKMS service to confirm whether the CMS complies with the preset security rules, such as not accessing sensitive system data, thereby ensuring the security of the application during runtime.

[0081] In addition, as a preferred embodiment, in the above CMS preinstallation method, the system partition is provided with an application whitelist, and the application whitelist is used to filter the encryption verification permissions of the application. The purpose of setting the application whitelist is to filter the encryption verification permissions, so that when installing the CMS, the encryption verification permission check is directly skipped and the CMS is directly installed, so that the customer can use the CMS immediately.

[0082] Specific as Figure 6 As shown, the above step S154: when PKMS scans the application package, the step of installing the application package in the data partition includes:

[0083] S1541: Use PKMS to query the application whitelist and determine whether CMS is in the application whitelist.

[0084] S1542: If it is determined that the CMS is in the application whitelist, the encryption verification machine permission of the CMS is skipped, and the pre-installation process of the application package in the data partition is started.

[0085] In the embodiment of the present application, by setting an application whitelist, it is determined whether the CMS has filtered out the encryption verification permission of the application. When the system main program starts working, it will scan all service areas to ensure that everything is ready. When the CMS is scanned, it will be determined that the CMS is a special application, so the conventional security checks such as encryption verification are skipped and it is directly installed to ensure that the third-party service can be used immediately.

[0086] In addition, as a preferred embodiment, Figure 7 As shown, the above CMS preinstallation method, after the step S150: installing the decompressed CMS to the data partition and generating a preinstallation mark in the data partition, further includes:

[0087] S310: When the CMS is installed, the MD5 value of the CMS is calculated and the MD5 value is uploaded to the blockchain storage;

[0088] S320: Calculate the MD5 value of the CMS at a predetermined time interval, and compare the calculated MD5 value with the MD5 value stored in the blockchain for consistency;

[0089] S330: When the calculated MD5 value is inconsistent with the MD5 value stored in the blockchain, clear the pre-installed flag and control the terminal device to restart the system.

[0090] When installing the CMS, the embodiment of the present application calculates the MD5 value of the CMS after installation. The MD5 value is a hash function widely used in the field of computer security to provide message integrity protection. The MD5 value of the CMS is uploaded to the blockchain for storage, which can ensure the data security of the MD5 value.

[0091] The MD5 value of CMS is recalculated at a predetermined time, and then compared with the MD5 value stored in the blockchain for consistency, so as to determine whether CMS has data tampering or program modification. When the two are inconsistent, it means that the data of CMS has been tampered with. At this time, the above pre-installed mark is cleared, and the terminal device is controlled to restart the system to reinstall CMS using the compressed installation package in the system partition.

[0092] See also Figure 8 , Figure 8 The following is a flow chart of a CMS pre-installation method for a digital signage provided in an embodiment of the present application. Figure 8 As shown, the CMS preinstallation method includes the following steps:

[0093] S501: CMS packaging before compilation. The CMS application is packaged and compressed, and copied to the system / prebuilt partition during system compilation.

[0094] S502: Process the system framework and filter the CMS installation verification mechanism. When the PKMS is started later, it scans the app directories of each partition. When the CMS is scanned, it will skip the encryption verification mechanism, start the application installation process, and directly install the application.

[0095] S503: When the system is compiled, mk copies the compressed installation package to the System / prebuild partition.

[0096] S504: Copy the identification file prebuilt.txt. When the application is installed, if the data / app partition does not have the identification file, the prebuilt.txt file is directly copied to the data / app partition.

[0097] S505: The system customizes the system preinstall process. The preinstall process can solve a series of SELinux permission problems and then perform the installation operation of the CMS.

[0098] S506: After the init.rc process is started, the node executes the NOKA preinstall process. First, determine whether the identification file preinstall.txt is in data / app; if it does not exist, unzip the application compressed installation package under system / prebuilt and copy the application to the data / app partition. At the same time, copy the identification file preinstall.txt together. The identification file preinstall.txt indicates that the CMS has been correctly copied to the data / app partition.

[0099] S507: System compilation.

[0100] S508: Burn the firmware and start the machine. After the system starts, the following steps S509 and S510 are executed.

[0101] S509: Copy the CMS to the data partition.

[0102] S510: The script is installed using pminstall. After the system PKMS is started, it scans the app directories of each partition. When data / app is scanned, if PKMS determines that it is CMS, it will skip the encryption verification mechanism to start the application installation process and directly install the application.

[0103] S511: Preinstallation is completed.

[0104] S512: User uninstallation. After the user manually uninstalls the CMS, the system will continue to retain the identification file in data / app. The identification file indicates that the CMS is still in data / app, so even if the system is restarted, the system will not restart the installation process of the CMS.

[0105] S513: Restarting does not affect the process. Because when the system restarts, the identification file is still retained, and the identification file indicates that the data / app has correctly installed the CMS, the system will directly run the CMS.

[0106] S514: System Reset, i.e., system reset. When the system is reset, the identification file is deleted and the machine restarts. Since the identification file is deleted, the system can reinstall the CMS.

[0107] The technical solution of this application can ensure the normal operation of CMS for users without changing the properties of CMS, thus meeting customer needs. For manufacturers, pre-installation of third-party CMS is completed without granting system permissions, thus ensuring the safety of terminal products.

[0108] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the CMS preinstallation method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0109] In addition, to achieve the above-mentioned purpose, the present application also provides a terminal device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the CMS pre-installation method for digital signage provided in any of the above-mentioned embodiments.

[0110] Reference below Fig. 9, which shows a schematic diagram of the structure of a terminal device suitable for implementing the embodiment of the present application. The terminal device in the embodiment of the present application can include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig. 9 The terminal device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0111] like Fig. 9 As shown, the terminal device can include a processing device 1001 (such as a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the terminal device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can operate the terminal device to communicate with other devices wirelessly or wired to exchange data. Although the figure shows a terminal device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0112] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0113] The terminal device provided by the present application adopts the CMS preinstallation method in the above embodiment, which can solve the technical problem that the prior art method easily causes data leakage, malicious deletion and even system crash. Compared with the prior art, the beneficial effects of the terminal device provided by the present application are the same as the beneficial effects of the CMS preinstallation method provided by the above embodiment, and the other technical features in the terminal device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0114] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0115] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

[0116] In addition, to achieve the above-mentioned purpose, the present application also provides a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the CMS pre-installation method for digital signage in any of the above-mentioned technical solutions are implemented.

[0117] The computer-readable storage medium provided in the present application can be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM: Random Access Memory), a read-only memory (ROM: Read Only Memory), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium can be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency: Radio Frequency), etc., or any suitable combination of the above.

[0118] The computer-readable storage medium may be included in the terminal device, or may exist independently without being installed in the terminal device.

[0119] The above-mentioned computer-readable storage medium carries one or more programs. When the above-mentioned one or more programs are executed by the terminal device, the terminal device: when the system is compiled, the system main program pre-installs the compressed installation package of CMS to the system partition of the terminal device, wherein the system partition only allows the system main program to have access rights; the system main program pre-defines the pre-installation process of CMS from the system partition to the data partition.

[0120] Computer program code for performing the operations of the present application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0121] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes also be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented by a dedicated hardware-based system that performs a specified function or operation, or can be implemented by a combination of dedicated hardware and computer instructions.

[0122] The modules involved in the embodiments of the present application can be implemented by software or hardware, wherein the name of the module does not limit the unit itself in some cases.

[0123] The readable storage medium provided in the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned CMS preinstallation method. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in the present application are the same as the beneficial effects of the CMS preinstallation method provided in the above-mentioned embodiment, and will not be described in detail here.

[0124] In addition, to achieve the above objectives, the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the CMS pre-installation method for digital signage in any of the above technical solutions.

[0125] The present application also provides a computer program product, including a computer program, which implements the steps of the CMS preinstallation method as described above when the computer program is executed by a processor. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as the beneficial effects of the CMS preinstallation method provided by the above embodiment, and will not be repeated here.

[0126] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A CMS preinstallation method, characterized in that: Applied to a terminal device, the terminal device includes a system partition and a data partition; the CMS preinstallation method includes: When the terminal device compiles the system, the compressed installation package of CMS is preinstalled into the system partition of the terminal device, wherein the terminal device grants the system main program access rights to the system partition; The installation process of the compressed installation package of the CMS from the system partition to the data partition is predefined in the system partition, wherein the terminal device grants the user access rights to the data partition.

2. The method according to claim 1, characterized in that The method further comprises: When the system is started, the terminal device determines whether the data partition has a pre-installed identifier of the CMS; If it is determined that the data partition has the pre-installed identifier, the CMS is run; or, If it is determined that the pre-installation mark does not exist in the data partition, the compressed installation package is decompressed according to the installation process, the decompressed CMS is installed in the data partition and a pre-installation mark is generated in the data partition.

3. The method according to claim 2, characterized in that The step of determining whether the data partition has a pre-installed identifier of the CMS when the terminal device starts the system includes: Determine whether the system is running normally or resetting when it starts; If it is determined that the system is in reset operation, the pre-installation mark is cleared, and the step of determining whether the data partition has a pre-installation mark of the CMS is performed.

4. The method according to claim 2, characterized in that After the step of installing the decompressed CMS to the data partition and generating a pre-installation mark in the data partition, the method further includes: When receiving a user uninstallation instruction, uninstalling the CMS from the data partition, and retaining the pre-installation identifier in the data partition; When the system is restarted, the step of determining whether the data partition has a pre-installed identifier of the CMS is performed again.

5. The method according to claim 2, characterized in that The step of decompressing the compressed installation package according to the installation process, installing the decompressed CMS to the data partition and generating a pre-installation mark in the data partition comprises: Decompressing the compressed installation package in the system partition to obtain the application package and preinstallation identification file of the CMS; Copying the application package and the preinstalled identification file to the data partition respectively; Start a package management service PKMS, where the PKMS is used to scan an application directory of a data partition; When the application package is scanned, the PKMS is controlled to determine whether the application permissions of the CMS comply with preset security rules; If the application permissions of the CMS meet the preset security rules, the PKMS is used to install the application package in the data partition.

6. The method according to claim 5, characterized in that The system partition is provided with an application whitelist, and the application whitelist is used to filter the encryption verification permissions of applications; The step of installing the application package in the data partition using the PKMS comprises: Using the PKMS to query the application whitelist, and determining whether the CMS is in the application whitelist; If it is determined that the CMS is in the application whitelist, the encryption checker permission of the CMS is skipped and the pre-installation process of the application package in the data partition is started.

7. The method according to claim 2, characterized in that After the step of installing the decompressed CMS to the data partition and generating a pre-installation mark in the data partition, the method further includes: When the CMS is installed, the MD5 value of the CMS is calculated and uploaded to the blockchain for storage; Calculate the MD5 value of the CMS at predetermined intervals, and compare the calculated MD5 value with the MD5 value stored in the blockchain for consistency; When the calculated MD5 value is inconsistent with the MD5 value stored in the blockchain, the pre-installation flag is cleared and the terminal device is controlled to restart the system.

8. A terminal device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the CMS preinstallation method according to any one of claims 1 to 7.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the CMS preinstallation method according to any one of claims 1 to 7 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the CMS preinstallation method according to any one of claims 1 to 7 are implemented.

Images