A boot logo customization method and system

Abstract

The present invention proposes a method and system for customizing a startup logo. The method includes determining whether a device is being powered on for the first time. If so, loading the device's preset logo into the device interface; if not, and a user-defined logo is set, directly loading the user-defined logo into the device interface. After the device is powered on for the first time and the device interface is accessed, authorizing the user to set, store, and upload a customized logo via an API interface; and after a reboot, loading the user-defined logo into the device interface. The system includes modules corresponding to the method steps.

Description

Technical Field

[0001] The invention provides a startup logo customization method and system, belonging to the technical field of software application. Background Art

[0002] Mobile terminal devices are widely used, and different mobile terminals have unique logos. This logo design represents a special meaning, so it plays a vital role in the mobile terminal usage domain. However, with the use of a large number of users, different user groups want to have a unique terminal product to meet their psychological needs. For example, through investigation, many couples need to set a logo with special meaning, which is obviously impossible to make independently. Summary of the Invention

[0003] The present invention provides a method and system for customizing a startup logo, which is used to solve the problem that existing mobile terminals cannot enable users to customize the startup logo. The technical solutions adopted are as follows:

[0004] A method for customizing a startup logo, the method comprising:

[0005] After booting up the device for the first time and entering the device interface, authorize the user to set, store, and upload a custom logo through the API interface;

[0006] After restarting, the user-defined logo is loaded to enter the device interface.

[0007] Furthermore, after the device is turned on for the first time and enters the device interface, the user is authorized to set, store and upload a custom logo through the API interface, including:

[0008] When the device is powered on for the first time, the device boot preset logo is loaded and the device interface is entered through the preset logo;

[0009] Enable custom logo settings through the API interface opened by the UI, and authorize users to set custom logos;

[0010] Storing the user-defined logo in user space memory and uploading the customized logo to a device file;

[0011] After uploading the customized logo, restart the device.

[0012] Furthermore, the custom logo setting is enabled through the API interface opened by the UI, and the user is authorized to set the custom logo, including:

[0013] Determine whether the user has customized the logo setting; if the user does not customize the logo setting, then enter the device interface through the device preset logo loading; if the user has customized the logo setting, then execute the API interface operation;

[0014] Customize and open the API interface opened by the UI;

[0015] Submit a logo change application to the API interface;

[0016] Authorize the user interface and allow the user to set a custom logo.

[0017] Furthermore, after the restart, loading the user-defined logo to enter the device interface includes:

[0018] In the BootLoader phase after the device restarts, it is determined whether the user's custom logo exists; if the custom logo does not exist, the device preset logo is loaded to enter the device interface; if the custom logo exists, the user-defined logo is read;

[0019] The user-defined logo is read from the user space memory, and the data code of the user-defined logo is parsed, and the user-defined logo is set as the boot logo.

[0020] Furthermore, the method further comprises:

[0021] Determine whether the device is powered on for the first time. If so, load the device's preset logo to enter the device interface. If not, and a user-defined logo is set, directly load the user-defined logo to enter the device interface.

[0022] When the device is turned on for the first time, before the API interface authorizes the user to set and upload a custom logo, it uses the user identity information of the cloud-registered account and the personal identity information entered by the user through a matching model to obtain the information matching degree, and judges the relationship between the information matching degree and the pre-set matching degree threshold, obtains the information matching degree judgment result, and realizes the matching authentication of the user information through the information matching degree judgment result.

[0023] Wherein, the matching model is:

[0024]

[0025] Where M represents the user identity information set of the cloud-registered account corresponding to the mobile device, and N represents the personal identity information set entered by the user. Sim(M,N) represents the degree of match between M and N. When Sim(M,N) > 0.8, the information matches; when Sim(M,N) ≤ 0.8, the information does not match. m represents the amount of information contained in the user identity information set; and n represents the amount of identity information contained in the personal identity information set. |N / M| represents the subset of elements in set N that do not belong to set M, and |M / N| represents the subset of elements in set M that do not belong to set N.

[0026] A boot logo customization system, the system comprising:

[0027] The authorization module is used to authorize users to set, store, and upload custom logos through the API interface after the device is turned on for the first time and enters the device interface;

[0028] The custom logo loading module is used to load the user-defined logo to enter the device interface after restart.

[0029] Furthermore, the authorization module includes:

[0030] The preset logo loading module is used to load the device boot preset logo when the device is turned on for the first time, and enter the device interface through the preset logo;

[0031] The logo customization module is used to open the custom logo setting through the API interface opened by the UI, and authorize users to set the custom logo;

[0032] An upload module, configured to store the user-defined logo in a user space memory and upload the customized logo to a device file;

[0033] The restart module is used to restart the device after the custom logo is uploaded.

[0034] Furthermore, the Logo customization module includes:

[0035] The custom judgment module is used to judge whether the user sets a custom logo; if the user does not set a custom logo, the device preset logo is loaded to enter the device interface; if the user sets a custom logo, the interface opening module is opened;

[0036] The interface opening module is used to customize the opening of the API interface opened by the UI;

[0037] API application module, used to submit a logo change application to the API interface;

[0038] The authorization implantation module is used to authorize the user interface and allow the user to set a customized logo.

[0039] Furthermore, the custom logo loading module includes:

[0040] A logo judgment module is used to determine whether the user's custom logo exists in the BootLoader stage after the device is restarted; if the custom logo does not exist, the device preset logo is loaded to enter the device interface; if the custom logo exists, the startup logo loading module is used;

[0041] The logo loading module is used to read the user-defined logo from the user space memory, perform data code analysis on the user-defined logo, and set the user-defined logo as the boot logo.

[0042] Furthermore, the system further comprises:

[0043] The first boot judgment module is used to judge whether the device is powered on for the first time. If it is the first time, the preset logo of the device is loaded to enter the device interface. If it is not the first time and a user-defined logo is set, the user-defined logo is directly loaded to enter the device interface.

[0044] The user confirmation module is used to obtain information matching degree by using the user identity information of the cloud-registered account and the personal identity information entered by the user through a matching model before the authorization module, and to determine the relationship between the information matching degree and a preset matching degree threshold, and obtain the information matching degree determination result. The information matching degree determination result is used to implement matching authentication of the user information, wherein the matching model is:

[0045]

[0046] Where M represents the user identity information set of the cloud-registered account corresponding to the mobile device, and N represents the personal identity information set entered by the user. Sim(M,N) represents the degree of match between M and N. When Sim(M,N) > 0.8, the information matches; when Sim(M,N) ≤ 0.8, the information does not match. m represents the amount of information contained in the user identity information set; and n represents the amount of identity information contained in the personal identity information set. |N / M| represents the subset of elements in set N that do not belong to set M, and |M / N| represents the subset of elements in set M that do not belong to set N.

[0047] Beneficial effects of the present invention:

[0048] The present invention proposes a boot logo customization method and system that allows users to flexibly set a customized boot logo on a mobile terminal, satisfying user satisfaction and gaining product-friendly support. Furthermore, by reserving memory in user space to store the user-set custom logo, the read permission of this user space reserved memory belongs to the user group, not requiring root permissions. This ensures that the mobile terminal system meets the custom logo settings while reducing system security risks and ensuring the security of the terminal device. Furthermore, by changing the logo loading method set by the user, the boot speed is faster than directly compiling into the boot program. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 A flow chart of the method of the present invention;

[0050] Figure 2 Schematic diagram of the method of the present invention;

[0051] Figure 3 Schematic diagram of the system structure of the system of the present invention. DETAILED DESCRIPTION

[0052] The preferred embodiments of the present invention are described below with reference to the accompanying drawings. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present invention, and are not used to limit the present invention.

[0053] The embodiments of the present invention provide a method and system for customizing a startup logo, so as to solve the problem of ...

[0054] The present invention proposes a method for customizing the startup logo in real time, such as Figure 1 As shown, the method includes:

[0055] S1. Determine whether the device is powered on for the first time. If so, load the device's preset logo to enter the device interface. If not, and a user-defined logo is set, directly load the user-defined logo to enter the device interface.

[0056] S2. After the device is turned on for the first time and enters the device interface, the user is authorized to set, store and upload a custom logo through the API interface;

[0057] S3. After restarting, load the user-defined logo to enter the device interface.

[0058] The working principle of the above scheme is: first, determine whether the device is turned on for the first time. If it is the first time, load the device preset logo to enter the device interface. If it is not the first time and a user-defined logo is set, directly load the user-defined logo to enter the device interface; then, after the first boot and entering the device interface, authorize the user to set, store and upload the custom logo in the API interface; finally, after restarting, load the user-defined logo to enter the device interface. The method for customizing the boot logo proposed in this embodiment mainly provides relevant interface settings on the user side and authorizes user permissions instead of root permissions. Users can flexibly use the interface to set the logo. This interface setting is permanently valid. If it needs to be replaced, the user needs to reactivate it by applying for permission. The principle is as follows: Figure 2 As shown, the factory boot preset logo is used for the first boot. After entering the desktop, the custom logo setting can be opened through the API opened by the UI. At this time, the authorization mode is turned on, the logo is uploaded, and it is valid after restart. After restart, the bootloader stage will determine whether the user logo exists. If it exists, the factory preset logo loading is directly skipped, and the user space loads the custom logo to speed up the boot speed. The method proposed in this embodiment has a one-time and permanent authorization. If the user is not satisfied with the existing logo, and for security reasons, the user needs to apply for re-authorization through a specific interface (this permission is managed by the cloud service) and reset it.

[0059] The technical effects of the above solution are: enabling users to flexibly set a custom startup logo on their mobile terminals, satisfying user satisfaction and gaining product-friendly support. Furthermore, by reserving memory in user space to store the user-set custom logo, the read permission of this user space reserved memory belongs to the user group, not requiring root privileges. This ensures that the mobile terminal system meets the custom logo settings while reducing system security risks and ensuring the security of the terminal device. Furthermore, the user-side setting of the logo loading method changes the boot speed compared to directly compiling into the boot.

[0060] In one embodiment of the present invention, after the device is turned on for the first time and the device interface is entered, the user is authorized to set, store, and upload a custom logo through the API interface, including:

[0061] S201, when the device is turned on for the first time, load the device boot preset logo and enter the device interface through the preset logo;

[0062] S202: Open the custom logo setting through the API interface opened by the UI, and authorize the user to set the custom logo;

[0063] S203, storing the user-defined logo in the user space memory, and uploading the customized logo to the device file;

[0064] S204: After the customized logo is uploaded, the device is restarted.

[0065] The working principle of the above scheme is as follows: First, when the device is turned on for the first time, the device boot preset logo is loaded, and the device interface is entered through the preset logo; then, the custom logo setting is opened through the API interface opened by the UI, and the user is authorized to set a custom logo; then, the user-defined logo is stored in the user space memory, and the custom logo is uploaded to the device file; finally, after the custom logo is uploaded, the device is restarted. In this embodiment, memory is reserved in the user space for storing the logo to be set. The memory read permission belongs to the user group and does not require root permission; a related switch interface is set in the user space, and the custom logo setting is displayed when the switch is turned on. The custom logo icon is uploaded to the specified file. At the same time, the machine is restarted, and the boot logo image parsing data code of the user space memory segment is read when the device is turned on and set as the boot logo.

[0066] The technical effect of this solution is that it reserves memory in user space to store the user-defined logo. This reserved memory is read by the user group, not requiring root privileges. This ensures that the mobile terminal system meets the custom logo settings while reducing system security risks and ensuring the security of the terminal device. Furthermore, the user-defined logo loading method changes, resulting in faster boot times compared to directly compiling the system into the bootloader.

[0067] In one embodiment of the present invention, the step of opening a custom logo setting through an API interface opened by a UI and authorizing a user to set a custom logo includes:

[0068] S2021. Determine whether the user has set a custom logo. If the user has not set a custom logo, load the device's preset logo to enter the device interface. If the user has set a custom logo, open the API interface.

[0069] S2022. After determining that the user has customized the logo setting, the API interface opened by the UI is customized and opened;

[0070] S2023. After the API interface customization is enabled, submit an application to the API interface to change the logo;

[0071] S2024. After the API interface receives the logo change application, the user is authorized to set a customized logo.

[0072] The working principle of the above scheme is: first, determine whether the user sets a customized logo; if the user does not set a customized logo, enter the device interface through the device preset logo; if the user sets a customized logo, execute the API interface opening operation; then, after determining that the user sets a customized logo, customize the API interface open to the UI and open it; then, after the API interface is customized and opened, submit a logo change application to the API interface; finally, after the API interface receives the logo change application, authorize the user to set a customized logo.

[0073] The technical effect of the above solution is: interface authorization for custom logo settings can be performed without root authorization of the mobile device, and the mobile device can provide users with flexible custom settings while ensuring the security performance of the mobile device.

[0074] In one embodiment of the present invention, after restarting, loading the user-defined logo to enter the device interface includes:

[0075] S301. In the BootLoader phase after the device is restarted, it is determined whether the user's custom logo exists; if the custom logo does not exist, the device preset logo is loaded to enter the device interface; if the custom logo exists, the user-defined logo is read, and S302 is executed;

[0076] S302: Read the user-defined logo from the user space memory, perform data code analysis on the user-defined logo, and set the user-defined logo as the boot logo.

[0077] The working principle of the above scheme is: first, in the BootLoader stage after the device restarts, it is determined whether the user's custom logo exists; if the custom logo does not exist, the device preset logo is loaded to enter the device interface; if the custom logo exists, the user-defined logo is read, and then the user-defined logo is read from the user space memory, and the data code of the user-defined logo is parsed, and the custom logo is set as the boot logo.

[0078] The technical effect of the above scheme is: by reserving memory in the user space to place the custom logo set by the user, the read permission of the user space reserved memory belongs to the user group and does not require root permission, which ensures that the mobile terminal system meets the custom logo settings while reducing the security risks of the mobile terminal device system and ensuring the security of the terminal device.

[0079] In one embodiment of the present invention, the method further comprises:

[0080] When the device is first powered on, before the API interface authorizes the user to set and upload a custom logo, the matching model uses the user identity information of the cloud-registered account and the personal identity information entered by the user to obtain the information matching degree, and determines the relationship between the information matching degree and the pre-set matching degree threshold, obtains the information matching degree judgment result, and implements the matching authentication of the user information based on the information matching degree judgment result. The matching model is:

[0081]

[0082] Among them, M represents the user identity information set of the cloud-registered account corresponding to the mobile device, and N represents the personal identity information set input by the user; Sim(M,N) represents the matching degree between M and N, when Sim(M,N)>0.8, it indicates that the information matches, and when Sim(M,N)≤0.8, it indicates that the information does not match; m represents the amount of information contained in the user identity information set; n represents the amount of identity information contained in the personal identity information set; |N / M| represents the subset of elements in set N that do not belong to set M, and |M / N| represents the subset of elements in set M that do not belong to set N.

[0083] Wherein, before the authorization module, user information matching is performed through the matching model, including:

[0084] Read the user identity information of the cloud-registered account corresponding to the mobile device;

[0085] When the device is first powered on, the user is prompted to enter personal identification information into the device;

[0086] The matching model is used to match the user identity information in the cloud corresponding to the mobile device with the personal identity information input by the user.

[0087] The working principle of the above scheme is as follows: In this embodiment, since customized changes need to be made to the mobile terminal and API interface authorization is required, user information needs to be verified before authorization operations are performed to prevent non-users from making unauthorized changes to the mobile terminal. When the mobile terminal is first powered on, a cloud-based registered account login interface corresponding to the mobile terminal brand is provided. The user can log in to their cloud account, and the mobile device then reads the user identity information of the cloud-based registered account. The mobile terminal then enters the personal identity information input interface, and the user enters personal information into the mobile terminal. Finally, the mobile terminal uses the above formula to calculate the degree of match between the user identity information in the cloud-based registered account and the personal identity information entered by the current user. If the match meets the matching criteria, subsequent customized authorization operations are allowed for the user.

[0088] The technical effect of the above scheme is: using the user's personal identity information input to match the account information in the cloud-based registered account corresponding to the mobile device, thereby improving the security performance of device use, and calculating the matching degree through the above formula, effectively improving the accuracy of information matching, ensuring that the authorization and changes of the mobile terminal are performed on the user himself, greatly improving the security and privacy of the customized settings of the boot logo, and effectively preventing non-users from changing and setting the boot logo.

[0089] A boot logo customization system, such as Figure 3 As shown, the system includes:

[0090] The first boot judgment module is used to judge whether the device is powered on for the first time. If it is the first time, the preset logo of the device is loaded to enter the device interface. If it is not the first time and a user-defined logo is set, the user-defined logo is directly loaded to enter the device interface.

[0091] The authorization module is used to authorize users to set, store, and upload custom logos through the API interface after the device is turned on for the first time and enters the device interface;

[0092] The custom logo loading module is used to load the user-defined logo to enter the device interface after restart.

[0093] The working principle of the above scheme is: first, use the first boot judgment module to determine whether the device is powered on for the first time. If it is the first time, load the device preset logo to enter the device interface. If it is not the first time and a user-defined logo is set, directly load the user-defined logo to enter the device interface; then, through the authorization module, after the first boot and entering the device interface, authorize the user to set, store and upload the custom logo in the API interface; finally, use the custom logo loading module to load the user-defined logo to enter the device interface after restart.

[0094] The technical effects of the above solution are: enabling users to flexibly set a custom startup logo on their mobile terminals, satisfying user satisfaction and gaining product-friendly support. Furthermore, by reserving memory in user space to store the user-set custom logo, the read permission of this user space reserved memory belongs to the user group, not requiring root privileges. This ensures that the mobile terminal system meets the custom logo settings while reducing system security risks and ensuring the security of the terminal device. Furthermore, the user-side setting of the logo loading method changes the boot speed compared to directly compiling into the boot.

[0095] In one embodiment of the present invention, the authorization module includes:

[0096] The preset logo loading module is used to load the device boot preset logo when the device is turned on for the first time, and enter the device interface through the preset logo;

[0097] The logo customization module is used to open the custom logo setting through the API interface opened by the UI, and authorize users to set the custom logo;

[0098] An upload module, configured to store the user-defined logo in a user space memory and upload the customized logo to a device file;

[0099] The restart module is used to restart the device after the custom logo is uploaded.

[0100] The working principle of the above scheme is:

[0101] First, the preset logo loading module is used to load the device boot preset logo when the device is turned on for the first time, and the device interface is entered through the preset logo; then, the custom logo setting is opened through the API interface opened by the UI using the logo customization module, and the user is authorized to set a custom logo; then, the upload module is used to store the user-customized logo in the user space memory, and the custom logo is uploaded to the device file; finally, the restart module is used to restart the device after the custom logo is uploaded.

[0102] The technical effect of this solution is that it reserves memory in user space to store the user-defined logo. This reserved memory is read by the user group, not requiring root privileges. This ensures that the mobile terminal system meets the custom logo settings while reducing system security risks and ensuring the security of the terminal device. Furthermore, the user-defined logo loading method changes, resulting in faster boot times compared to directly compiling the system into the bootloader.

[0103] In one embodiment of the present invention, the Logo customization module includes:

[0104] The custom judgment module is used to judge whether the user sets a custom logo; if the user does not set a custom logo, the device preset logo is loaded to enter the device interface; if the user sets a custom logo, the interface opening module is opened;

[0105] The interface opening module is used to customize the opening of the API interface opened by the UI after determining that the user has customized the logo setting;

[0106] An API application module is used to submit a logo change application to the API interface after the API interface customization is enabled;

[0107] The authorization implantation module is used to authorize the user to customize the logo setting after the API interface receives the logo change application.

[0108] The working principle of the above scheme is: first, the customization judgment module is used to determine whether the user has customized the logo setting; if the user does not customize the logo setting, the device preset logo is loaded into the device interface; if the user customizes the logo setting, the interface opening module is turned on; after the interface opening module determines that the user has customized the logo setting, the API interface opened by the UI is customized and opened; then, after the API interface is customized and opened, the API application module is used to submit a logo change application to the API interface; finally, after the API interface receives the logo change application, the authorization implantation module authorizes the user to the interface, allowing the user to customize the logo setting.

[0109] The technical effect of the above solution is: interface authorization for custom logo settings can be performed without root authorization of the mobile device, and the mobile device can provide users with flexible custom settings while ensuring the security performance of the mobile device.

[0110] In one embodiment of the present invention, the custom logo loading module includes:

[0111] A logo judgment module is used to determine whether the user's custom logo exists in the BootLoader stage after the device is restarted; if the custom logo does not exist, the device preset logo is loaded to enter the device interface; if the custom logo exists, the startup logo loading module is used;

[0112] The logo loading module is used to read the user-defined logo from the user space memory, perform data code analysis on the user-defined logo, and set the user-defined logo as the boot logo.

[0113] The working principle of the above scheme is: the logo judgment module is used to determine whether the user's custom logo exists in the BootLoader stage after the device is restarted; if the custom logo does not exist, the device preset logo is loaded to enter the device interface; if the custom logo exists, the startup logo loading module is used; the logo loading module reads the user-defined logo from the user space memory, and performs data code analysis on the user-defined logo, and sets the custom logo as the boot logo.

[0114] The technical effect of the above scheme is: by reserving memory in the user space to place the custom logo set by the user, the read permission of the user space reserved memory belongs to the user group and does not require root permission, which ensures that the mobile terminal system meets the custom logo settings while reducing the security risks of the mobile terminal device system and ensuring the security of the terminal device.

[0115] In one embodiment of the present invention, the system further comprises:

[0116] The user confirmation module is used to obtain information matching degree by using the user identity information of the cloud-registered account and the personal identity information entered by the user through a matching model before the authorization module, and to determine the relationship between the information matching degree and a preset matching degree threshold, and obtain the information matching degree determination result. The information matching degree determination result is used to implement matching authentication of the user information, wherein the matching model is:

[0117]

[0118] Among them, M represents the user identity information set of the cloud-registered account corresponding to the mobile device, and N represents the personal identity information set input by the user; Sim(M,N) represents the matching degree between M and N, when Sim(M,N)>0.8, it indicates that the information matches, and when Sim(M,N)≤0.8, it indicates that the information does not match; m represents the amount of information contained in the user identity information set; n represents the amount of identity information contained in the personal identity information set; |N / M| represents the subset of elements in set N that do not belong to set M, and |M / N| represents the subset of elements in set M that do not belong to set N.

[0119] Among them, such as Figure 3 As shown, the user confirmation module includes:

[0120] A registration information reading module is used to read the user identity information of the cloud registration account corresponding to the mobile device;

[0121] An information input module, used to allow the user to enter personal identity information into the device when the device is turned on for the first time;

[0122] The information matching module is used to match the user identity information in the cloud corresponding to the mobile device with the personal identity information input by the user using a matching model.

[0123] The working principle of the above scheme is as follows: In this embodiment, since it is necessary to make customized changes to the mobile terminal and obtain API interface authorization, it is necessary to verify the user information before performing the authorization operation in order to prevent non-users from making unauthorized changes to the mobile terminal. When the mobile terminal is turned on for the first time, the registration information reading module provides a cloud registration account login interface corresponding to the mobile terminal brand, and the user can log in to his or her cloud account and read the user identity information of the cloud registration account; then, the mobile terminal enters the personal identity information input interface through the information input module, and the user enters the personal information into the mobile terminal. Finally, the information matching module uses the above formula (1) to calculate the matching degree between the user identity information in the cloud registration account and the personal identity information entered by the current user. If the matching meets the matching standard, the user is allowed to perform subsequent customized authorization operations.

[0124] The technical effect of the above scheme is: using the user's personal identity information input to match the account information in the cloud-based registered account corresponding to the mobile device, thereby improving the security performance of device use, and calculating the matching degree through the above formula, effectively improving the accuracy of information matching, ensuring that the authorization and changes of the mobile terminal are performed on the user himself, greatly improving the security and privacy of the customized settings of the boot logo, and effectively preventing non-users from changing and setting the boot logo.

[0125] Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if such changes and modifications fall within the scope of the claims and their equivalents, the present invention is intended to include such changes and modifications.

Claims

1. A method for customizing a startup logo, characterized in that: The method comprises: After booting up the device for the first time and entering the device interface, authorize the user to set, store, and upload a custom logo through the API interface; After restarting, load the user-defined logo to enter the device interface; After the device is turned on for the first time and enters the device interface, the user is authorized to set, store and upload a custom logo through the API interface, including: When the device is powered on for the first time, the device boot preset logo is loaded and the device interface is entered through the preset logo; Enable custom logo settings through the API interface opened by the UI, and authorize users to set custom logos; Storing the user-defined logo in user space memory and uploading the customized logo to a device file; After uploading the customized logo, restart the device.

2. The method according to claim 1, characterized in that The custom logo setting is enabled through the API interface opened by the UI, and the user is authorized to set the custom logo, including: Determine whether the user has customized the logo setting; if the user does not customize the logo setting, then enter the device interface through the device preset logo loading; if the user has customized the logo setting, then execute the API interface operation; Customize and open the API interface opened by the UI; Submit a logo change application to the API interface; Authorize the user interface and allow the user to set a custom logo.

3. The method according to claim 1, characterized in that After the restart, loading the user-defined logo to enter the device interface includes: In the BootLoader phase after the device restarts, it is determined whether the user's custom logo exists; if the custom logo does not exist, the device preset logo is loaded to enter the device interface; if the custom logo exists, the user-defined logo is read; The user-defined logo is read from the user space memory, and the data code of the user-defined logo is parsed, and the user-defined logo is set as the boot logo.

4. The method according to claim 1, characterized in that The method further comprises: Determine whether the device is powered on for the first time. If so, load the device's preset logo to enter the device interface. If not, and a user-defined logo is set, directly load the user-defined logo to enter the device interface. When the device is turned on for the first time, before the API interface authorizes the user to set and upload a custom logo, it uses the user identity information of the cloud-registered account and the personal identity information entered by the user through a matching model to obtain the information matching degree, and judges the relationship between the information matching degree and the pre-set matching degree threshold, obtains the information matching degree judgment result, and realizes the matching authentication of the user information through the information matching degree judgment result.

5. A boot logo customization system, characterized in that: The system comprises: The authorization module is used to authorize users to set, store, and upload custom logos through the API interface after the device is turned on for the first time and enters the device interface; A custom logo loading module is used to load the user-defined logo to enter the device interface after restart; The authorization module includes: The preset logo loading module is used to load the device boot preset logo when the device is turned on for the first time, and enter the device interface through the preset logo; The logo customization module is used to open the custom logo setting through the API interface opened by the UI, and authorize users to set the custom logo; An upload module, configured to store the user-defined logo in a user space memory and upload the customized logo to a device file; The restart module is used to restart the device after the custom logo is uploaded.

6. The system according to claim 5, characterized in that The Logo customization module includes: The custom judgment module is used to judge whether the user sets a custom logo; if the user does not set a custom logo, the device preset logo is loaded to enter the device interface; if the user sets a custom logo, the interface opening module is opened; The interface opening module is used to customize the opening of the API interface opened by the UI; API application module, used to submit a logo change application to the API interface; The authorization implantation module is used to authorize the user interface and allow the user to set a customized logo.

7. The system according to claim 5, characterized in that The custom logo loading module includes: A logo judgment module is used to determine whether the user's custom logo exists in the BootLoader stage after the device is restarted; if the custom logo does not exist, the device preset logo is loaded to enter the device interface; if the custom logo exists, the startup logo loading module is used; The logo loading module is used to read the user-defined logo from the user space memory, perform data code analysis on the user-defined logo, and set the user-defined logo as the boot logo.

8. The system according to claim 5, characterized in that: The system further comprises: The first boot judgment module is used to judge whether the device is powered on for the first time. If it is the first time, the preset logo of the device is loaded to enter the device interface. If it is not the first time and a user-defined logo is set, the user-defined logo is directly loaded to enter the device interface. The user confirmation module is used to obtain information matching degree by using the user identity information of the cloud-registered account and the personal identity information entered by the user through a matching model before starting the authorization module, and to judge the relationship between the information matching degree and a preset matching degree threshold, obtain the information matching degree judgment result, and realize the matching authentication of the user information through the information matching degree judgment result.

Images