A method and system for pushing Easter egg files
By pushing out Easter egg files, configuration information and display files are processed separately, which solves the problems of limited vehicle interaction methods and excessive storage space, and achieves rich user interaction and optimized storage space.
Patent Information
- Application Number
- CN202311020815.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-14
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-08-14
AI Technical Summary
In existing technologies, the preset audio-visual and voice interaction methods of vehicles are limited, occupy a large amount of storage space, and cannot be modified or updated, thus limiting user interaction methods.
By using the push method of Easter egg files, configuration information and display files are processed separately. Users configure the display files on the first terminal, and the server stores and pushes the configuration information to the second terminal. This avoids storing the same files repeatedly, simplifies the user configuration operation, and reduces the risk of information leakage.
It enables a variety of user-vehicle interaction methods, reduces server storage space usage, and improves interaction convenience and content diversity.
Smart Images

Figure CN116980407B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of vehicle-machine interaction technology, and in particular to a method and system for pushing Easter egg files. Background Technology
[0002] With the improvement of living standards and the development of science and technology, users' needs for vehicles are no longer limited to the basic functions of vehicles, and the need for interaction between users and vehicles is also increasing.
[0003] Currently, users typically interact with their vehicles through display devices, audio systems, and lighting systems. For example, after the vehicle is powered on, preset audio and video content can be automatically played on the display, preset voice prompts can be played through the audio system, or ambient lighting can be controlled to display preset lighting effects. These preset audio and video content and voice prompts are usually stored in the vehicle's storage device before the vehicle leaves the factory, and users generally cannot modify or delete them. On the one hand, these preset audio and video content and voice prompts occupy a significant amount of storage space in the vehicle's storage device and cannot be modified or updated; on the other hand, this makes the interaction between the user and the vehicle relatively limited. Summary of the Invention
[0004] This application provides a method and system for pushing Easter egg files, which makes it more convenient for users to interact with a second terminal, enriches the content of interaction between users and the second terminal, and reduces the storage space occupied by the Easter egg files on the server during interaction.
[0005] On one hand, this application provides a method for pushing Easter egg files, applied to a server. The method includes: receiving an Easter egg upload instruction sent by a first terminal; the Easter egg upload instruction carries configuration information and a first display file corresponding to the configuration information; in response to the Easter egg upload instruction, storing the configuration information, and discarding the first display file carried by the Easter egg upload instruction if a first display file matching the configuration information exists in the display file repository in the server; sending a push instruction carrying the first display file to a second terminal according to the configuration information; the push instruction is used to instruct the second terminal to perform a display action based on the first display file.
[0006] In the method for pushing Easter egg files provided in this application, since the configuration information and the corresponding first display file are separated into two files, the first terminal can configure only the first display file, which simplifies the user's configuration operation and reduces the possibility of leakage of user information included in the configuration information. At the same time, after the server receives the configuration information and the corresponding first display file, it can store the configuration information in a storage location that only stores configuration information. If a first display file matching the already stored configuration information already exists in the display file repository on the server, the first display file will not be stored again. This avoids multiple storage of first display files with the same content but different configuration information, thereby reducing the storage space occupied by the server. Moreover, based on the configuration information, a second terminal that can push the first display file can be determined, so that the second terminal can perform corresponding display actions according to the content of the first display file. By using the Easter egg file push method provided in this application, users can configure a variety of first display files on the first terminal according to their needs, and push first display files with different configuration information but the same display file content to the second terminal through the server. The same first display file can be pushed multiple times, thereby reducing the storage space occupied by the display file on the server during interaction, making the interaction between the user and the second terminal more convenient, and enriching the interactive content between the user and the second terminal.
[0007] On the other hand, this application also provides a method for pushing Easter egg files, applied to a first terminal. The method includes: sending an Easter egg upload instruction to a server; the Easter egg upload instruction carries configuration information and a first display file corresponding to the configuration information, the Easter egg upload instruction is used to instruct the server to store the configuration information, and if a first display file matching the configuration information exists in the display file repository in the server, the first display file carried by the Easter egg upload instruction is discarded.
[0008] On another front, this application also provides a method for pushing Easter egg files, applied to a second terminal. The method includes: receiving a push instruction from a server carrying a first display file, and responding to the Easter egg upload instruction by storing configuration information. If a first display file matching the configuration information exists in the display file repository on the server, the first display file carried by the Easter egg upload instruction is discarded; and a display action is performed based on the first display file.
[0009] Furthermore, this application also provides a push system for Easter egg files, which includes a first terminal, a second terminal, and a server, wherein: the first terminal is used to send an Easter egg upload instruction to the server; the Easter egg upload instruction carries an Easter egg file including a display file and configuration information; the server is used to respond to the Easter egg upload instruction, determine the storage status of the display file according to the configuration information; if the display file exists in the display file repository in the server's storage status representation, discard the display file carried by the Easter egg upload instruction and store the configuration information; according to the configuration information, send a push instruction carrying the Easter egg file to the second terminal; the second terminal is used to receive and store the Easter egg file pushed by the server, and perform a display action based on the display file. Attached Figure Description
[0010] Figure 1 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0011] Figure 2 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0012] Figure 3 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0013] Figure 4 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0014] Figure 5 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0015] Figure 6 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0016] Figure 7 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0017] Figure 8 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0018] Figure 9 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0019] Figure 10 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0020] Figure 11 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0021] Figure 12 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0022] Figure 13 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0023] Figure 14 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0024] Figure 15 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0025] Figure 16 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0026] Figure 17 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0027] Figure 18 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0028] Figure 19 A schematic diagram illustrating the contents of the Easter egg file provided in this application embodiment;
[0029] Figure 20 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment;
[0030] Figure 21 This is a functional diagram of the Easter egg file push system provided in the embodiments of this application;
[0031] Figure 22 A schematic diagram of the configuration interface of the mobile phone configuration software provided in the embodiments of this application;
[0032] Figure 23 This is a schematic diagram of the configuration interface of the mobile phone configuration software provided in the embodiments of this application. Detailed Implementation
[0033] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the specific technical solutions of this application will be further described in detail below with reference to the accompanying drawings of the embodiments of this application. The following embodiments are used to illustrate this application, but are not intended to limit the scope of this application.
[0034] This application provides a method for pushing Easter egg files, which can be executed by a server with data processing capabilities. The server with data processing capabilities can be a cloud server, computer, laptop, tablet, desktop computer, mobile device, etc.
[0035] Reference Figure 1 , Figure 1 This is a flowchart illustrating the method for pushing Easter egg files according to an embodiment of this application. This method can be executed by a device with data processing capabilities. (The last sentence appears to be incomplete and possibly refers to a separate topic.) Figure 1 The steps shown are explained.
[0036] S101, Receive the Easter egg upload instruction sent by the first terminal; the Easter egg upload instruction carries configuration information and the first display file corresponding to the configuration information.
[0037] In some possible embodiments, the first terminal can be a device with data processing capabilities, such as a mobile phone, a computer, or a vehicle with data processing capabilities. Users or operators can configure multiple display files stored on the first terminal, where each display file includes content that enables the second terminal to perform display actions.
[0038] In this embodiment, during the process of a user or operator uploading a first display file configured on a first terminal to the server, the first terminal first generates the configuration information for the first display file. After the first terminal generates the configuration information for the first display file, it generates an "Easter Egg" upload command carrying an Easter Egg file including the first display file and the configuration information, and sends the Easter Egg upload command to the server. The server receives the Easter Egg upload command sent by the first terminal. For example, the server can first cache the received Easter Egg upload command in the server's cache library; that is, the server first caches the received configuration information and the corresponding first display file in the cache library.
[0039] For example, the configuration information may include upload time, uploading user, Easter egg type, push target, triggering account, storage address, execution status, and verification information of the displayed file. For instance, based on the display action performed by the second terminal, the Easter egg file can be categorized into different types, such as a birthday Easter egg file with a birthday greeting theme, an operational Easter egg file with a promotional theme configured by the operations staff for product promotion, or a custom Easter egg file with other themes defined by the user. The push target is the second terminal to which the user wants to push the Easter egg file. The triggering account can be an account selected by the user that can trigger the Easter egg file's triggering conditions. The storage address can be added to the configuration information by the server after the Easter file is stored on the server, specifying the storage location of the configuration information. The execution status indicates whether the Easter egg file has been executed on the second terminal or whether the execution failed. Verification information for display files can be generated through algorithms or other methods. For example, a hash algorithm can be used to generate a hash value for each display file. This hash value can uniquely identify a display file. This hash value is used as the verification information for the display file and stored in the configuration information. In other words, a display file can be uniquely identified through the verification information.
[0040] S102. In response to the Easter egg upload command, store the configuration information, and if a first display file matching the configuration information exists in the display file repository on the server, discard the first display file carried by the Easter egg upload command.
[0041] In some possible embodiments, after receiving the Easter egg upload instruction from the first terminal, the server downloads and stores the configuration information carried by the Easter egg upload instruction in the server, such as storing the configuration information in a configuration information repository. Simultaneously, the server compares the stored configuration information of the first display file with all existing configuration information in the server. If it is determined that no configuration information matching the configuration information of the first display file exists in the server, the first display file is also stored in the server's display file repository. However, if it is determined that a first display file matching the received configuration information already exists in the server's display file repository, the server stops downloading and storing the first display file carried by the Easter egg upload instruction and discards it.
[0042] For example, after the server receives the Easter egg upload command, it can first obtain the hash value of the configuration information of the first display file. This hash value is then compared with the hash values of all configuration information in the server's configuration information repository to determine if a display file identical to the first display file exists in the server's repository. If the hash value of the first display file does not exist in the server, it means that a display file identical to the first display file does not exist in the server's repository, and the first display file is stored in the repository. If the hash value of the first display file exists in the server, it means that a display file identical to the first display file exists in the repository, and the first display file carried by the Easter egg upload command is discarded. This reduces the storage space occupied by display files with different configuration information (uploading user, upload time, push target, and triggering account) but identical verification information on the server. In other words, the same display file is stored only once in the server's display file repository, and can be pushed multiple times along with different configuration information, thus avoiding the problem of storing the same display file multiple times on the server and occupying unnecessary server storage space.
[0043] Reference Figure 2 , Figure 2 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 2 As shown, based on Figure 1 , Figure 1 The content of the storage configuration information in S102 can be implemented through S201 to S202, which will combine Figure 2 The steps shown are explained.
[0044] S201. Determine the storage location of the configuration information based on the Easter egg type corresponding to the configuration information.
[0045] In some possible embodiments, the configuration information for each display file includes information about the Easter egg type. A display file repository and multiple configuration information repositories can be set up on the server. The display file repository stores different display files; the configuration information repositories can be set up according to different Easter egg file types, with at least one configuration information repository corresponding to each Easter egg file type. For example, one birthday Easter egg configuration repository, nine operational Easter egg configuration repositories, and ten custom Easter egg configuration repositories can be set up. In this way, each piece of configuration information can be stored in a corresponding configuration information repository. After the server receives the Easter egg upload instruction, it can first obtain the Easter egg type information from the configuration information, and determine the storage location of the configuration information based on the obtained Easter egg type information, that is, determine the configuration information repository where the configuration information is stored.
[0046] S202. Store configuration information in the server based on the storage location.
[0047] In some possible embodiments, after the server determines the configuration information repository to be stored based on the Easter egg type, the configuration information can be stored in the configuration information repository corresponding to the Easter egg type.
[0048] For example, after a user uploads a first custom Easter egg file to the server, the server stores the display file of the first custom Easter egg file in a display file repository and the configuration information of the first custom Easter egg file in a custom configuration information repository. When another user uploads a second custom Easter egg file to the server, and the server determines that the display file of the second custom Easter egg file is the same as the display file of the first custom Easter egg file, the server only stores the configuration information of the second custom Easter egg file in a different custom configuration information repository. Alternatively, after a third user uploads a third custom Easter egg file to the server, and the server determines that the display file of the third custom Easter egg file is different from all the display files stored on the server, the server stores the configuration information of the third custom Easter egg file in a third custom configuration information repository and the display file of the third custom Easter egg file in the display file repository. In other words, when the server receives a first display file that is the same as a stored display file but has different configuration information than the stored configuration information, it only saves the configuration information and does not save the first display file.
[0049] S103. Based on the configuration information, send a push instruction carrying the first display file to the second terminal; the push instruction is used to instruct the second terminal to perform a display action based on the first display file.
[0050] In some possible embodiments, the second terminal may be a device or apparatus capable of executing the content corresponding to the first display file. For example, the second terminal may be different passenger vehicles, freight vehicles, and special vehicles, such as sedans, multi-purpose vehicles (MPVs), sport utility vehicles (SUVs), vans, and cranes, or it may be an electric toy vehicle or other electric toys. The server can determine the second terminal that can push the first display file based on the push target and verification information in the stored configuration information. After determining the second terminal that can push the first display file, a push instruction carrying the first display file is sent to the second terminal. After receiving the push instruction and storing the first display file, the second terminal can perform the corresponding display action based on the information included in the first display file.
[0051] For example, a user can send verification information to a second terminal that is preparing to push a first display file. This verification information is the verification information of the first display file that the user wants to push to the second terminal. The second terminal receives and saves the verification information, and the verification information saved to the second terminal serves as the terminal verification information of the second terminal. For example, if the push target in the server configuration information stored in the server is a car, the server can first determine the car to be pushed based on the push target information, then obtain the terminal verification information saved by all the cars to be pushed. If the obtained terminal verification information is the same as a server verification information stored in the server, then the car to be pushed corresponding to the terminal verification information is determined as the target vehicle, and the first display file corresponding to the server verification information is then pushed to the target vehicle.
[0052] In this embodiment, since the configuration information and the corresponding first display file are divided into two files, the first terminal can configure only the first display file, which simplifies the user's configuration operation and reduces the possibility of leakage of user information included in the configuration information. Simultaneously, after receiving the configuration information and the corresponding first display file, the server can store the configuration information in a storage location that only stores configuration information. If a first display file matching the already stored configuration information exists in the server's display file repository, the server will not store that first display file again. This avoids multiple storage of first display files with the same content but different configuration information, thereby reducing the storage space occupied by the server. Furthermore, based on the configuration information, a second terminal that can push the first display file can be determined, allowing the second terminal to perform corresponding display actions based on the content of the first display file. The method for pushing Easter egg files provided in this application allows users to configure various first display files on a first terminal according to their needs, and push first display files with different configuration information but the same display file content to a second terminal through a server. The same first display file can be pushed multiple times, thereby reducing the storage space occupied by the display file on the server during interaction, making the interaction between the user and the second terminal more convenient, and enriching the interactive content between the user and the second terminal.
[0053] Reference Figure 3 , Figure 3 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 3 As shown, the method further includes S301 to S303, combining Figure 3 The steps shown are explained.
[0054] S301. Receive the Easter egg update command sent by the second terminal; the Easter egg update command carries terminal configuration information; the terminal configuration information includes all configuration information existing in the second terminal.
[0055] In some possible embodiments, the Easter egg files stored on the server can be updated according to the user's choice. After the Easter egg files stored on the server are updated, the Easter egg files stored on the second terminal will be inconsistent with the Easter egg files stored on the server. Then the second terminal can update the stored Easter egg files.
[0056] For example, the second terminal can send an Easter egg update instruction carrying terminal configuration information to the server. The server receives the Easter egg update instruction, and the terminal configuration information includes all the configuration information existing in the second terminal.
[0057] S302. In response to the Easter egg update command, obtain server configuration information; the server configuration information includes all existing configuration information of the server.
[0058] In some possible embodiments, after receiving the Easter egg update instruction, the server first obtains all the server configuration information that exists on the server so that it can compare the server configuration information with the received terminal configuration information.
[0059] S303. Based on the terminal configuration information and server configuration information, send an Easter egg synchronization command to the second terminal; the Easter egg synchronization command is used to synchronize the Easter egg files stored in the second terminal and the server.
[0060] In some possible embodiments, the configuration information of each terminal received by the server can be compared with the server configuration information stored on the server to determine whether the Easter egg file stored in the second terminal is the same as the Easter egg file stored on the server. If it is determined that the Easter egg file stored in the second terminal is different from the Easter egg file stored on the server, the server can send an Easter egg synchronization command to the second terminal, which will ensure that the terminal Easter egg file stored in the second terminal is consistent with the server Easter egg file stored on the server.
[0061] In some other possible embodiments, each terminal repository of the second terminal shares the same storage address as a configuration information repository on the server. However, because updates to the Easter egg files in the second terminal lag behind updates to the Easter egg files on the server, the Easter egg files stored at the same storage address on the second terminal and the server may be different. That is, the verification information included in the configuration information at the same storage address on the second terminal and the server may be different. Conversely, the verification information included in the configuration information at different storage addresses on the second terminal and the server is usually different. Therefore, it is possible to determine whether the Easter egg files on the second terminal and the server are consistent based on the storage address and verification information in the configuration information.
[0062] For example, firstly, based on a first storage address in a terminal configuration information, a second storage address in a server that is identical to the first storage address is determined, thereby determining the server configuration information corresponding to the second storage address; then, first verification information is obtained from the terminal configuration information of the first storage address; then, second verification information is obtained from the server configuration information of the second storage address, thereby determining whether the first verification information and the second verification information are the same, and further determining whether the Easter egg files in the second terminal and the server are consistent. If the verification information in the obtained terminal storage repository is empty, it indicates that the Easter egg file does not exist in the terminal storage repository; if the verification information in the obtained configuration information storage repository is empty, it indicates that the configuration information storage repository does not contain configuration information, that is, the Easter egg file corresponding to the second verification information does not exist in the server.
[0063] Reference Figure 4 , Figure 4 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 4 As shown, based on Figure 3 The configuration information includes verification information. Figure 3 S303 in the above can be implemented through S401 to S402, which will combine Figure 4 The steps shown are explained.
[0064] S401. Obtain the first verification information in the terminal configuration information and the second verification information in the server configuration information; the configuration information corresponding to the first verification information and the configuration information corresponding to the second verification information have a matching relationship.
[0065] S402, if the first verification information is empty and the second verification information is not empty, send a first synchronization command to the second terminal; the first synchronization command carries the Easter egg file corresponding to the second verification information.
[0066] In some possible embodiments, after obtaining the first verification information in the terminal configuration information and the second verification information in the server configuration information, it is necessary to determine whether the first verification information and the second verification information are the same. For example, if the first verification information in a terminal repository of the second terminal is null, and the second verification information on the server is not null, it indicates that the server stores a server easter egg file, but the second terminal does not have a terminal easter egg file identical to that server easter egg file. In this case, the server can send a first synchronization instruction to the second terminal, which carries the server easter egg file stored on the server corresponding to the second verification information. After receiving the first synchronization instruction, the second terminal stores the server easter egg file in the corresponding terminal repository.
[0067] Reference Figure 5 , Figure 5A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 5 As shown, based on Figure 3 The configuration information includes verification information. Figure 3 S303 in the above can also be implemented through S501 to S502, combining Figure 5 The steps shown are explained.
[0068] S501. Obtain the first verification information from the terminal configuration information and the second verification information from the server configuration information; the configuration information corresponding to the first verification information and the configuration information corresponding to the second verification information have a matching relationship;
[0069] S502, if the first verification information is not empty and the second verification information is empty, a second synchronization command is sent to the second terminal; the second synchronization command is used to delete the Easter egg file corresponding to the first verification information in the second terminal.
[0070] In some possible embodiments, if the first verification information in a terminal storage repository of the second terminal is non-empty, and the second verification information on the server is empty, it indicates that the Easter egg file on the server has been deleted, but the second terminal still stores the Easter egg file. In this case, the server can send a second synchronization command to the second terminal, which carries either the first verification information or the terminal storage address corresponding to the first verification information. After receiving the second synchronization command, the second terminal can delete the corresponding Easter egg file based on the first verification information or the terminal storage address corresponding to the first verification information.
[0071] Reference Figure 6 , Figure 6 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 6 As shown, based on Figure 3 The configuration information includes verification information. Figure 3 S303 in the above can also be implemented through S601 to S602, combining Figure 6 The steps shown are explained.
[0072] S601. Obtain the first verification information in the terminal configuration information and the second verification information in the server configuration information; the configuration information corresponding to the first verification information and the configuration information corresponding to the second verification information have a matching relationship.
[0073] S602. If both the first verification information and the second verification information are non-empty and inconsistent, a third synchronization instruction is sent to the second terminal. The third synchronization instruction carries the Easter egg file corresponding to the second verification information. The third synchronization instruction is used to update the Easter egg file corresponding to the first verification information in the second terminal to the Easter egg file corresponding to the second verification information.
[0074] In some possible embodiments, if both the first verification information in a terminal repository of the second terminal and the second verification information in the server are non-empty values, and the first and second verification information are inconsistent, it indicates that the Easter egg file corresponding to the second verification information in the server is an updated Easter egg file, while the second terminal has not yet updated the Easter egg file corresponding to the first verification information to the one corresponding to the second verification information. In this case, the server can send a third synchronization command to the second terminal, which carries the Easter egg file corresponding to the second verification information. After receiving the third synchronization command, the second terminal first deletes the stored Easter egg file corresponding to the first verification information, and then saves the Easter egg file corresponding to the second verification information to complete the update of the Easter egg file, thereby ensuring that the Easter egg file stored on the second terminal is consistent with the Easter egg file stored on the server.
[0075] In this embodiment, since the second terminal can send an Easter egg update command to the server, and the Easter egg update command carries terminal configuration information, the server, based on the Easter egg update command and according to the terminal configuration information and the server configuration information, can send an Easter egg synchronization command to the second terminal if it is determined that the Easter egg file of the second terminal is inconsistent with the Easter egg file stored on the server. This allows the second terminal to update the Easter egg file stored on the second terminal based on the Easter egg synchronization command, so that the Easter egg file stored on the second terminal is consistent with the Easter egg file stored on the server, and thus the display action corresponding to the display file can be executed in a timely manner on the second terminal.
[0076] Reference Figure 7 , Figure 7 This is a flowchart illustrating the method for pushing Easter egg files provided in this application embodiment. The configuration information also includes status change information, such as... Figure 7 As shown, the method further includes S701 to S702, combining Figure 7 The steps shown are explained.
[0077] S701, Receive a status change instruction sent by the second terminal in response to an execution status change event for the first displayed file; the status change instruction carries the execution status of the second terminal for the first displayed file.
[0078] In some possible embodiments, after the Easter egg file stored on the second terminal meets the trigger condition and the trigger condition is triggered, the second terminal will perform the corresponding display action according to the content of the stored first display file. Alternatively, after the Easter egg file stored on the second terminal meets the trigger condition and the trigger condition is triggered, but due to some factors of the second terminal, the second terminal does not complete the display action related to the content of the first display file. In both cases, the first display file stored on the second terminal has undergone an execution status change event. Then the second terminal can send a status change instruction to the server. This status change instruction carries information about the execution status of the second terminal for the first display file, which can be executed or failed.
[0079] S702. In response to the status change command, update the execution status information in the configuration information based on the execution status.
[0080] In some possible embodiments, when the server receives a state change instruction sent by the second terminal, it determines the server configuration information in the server according to the configuration information, and updates the execution status information in the server configuration information based on the execution status in the state change instruction.
[0081] In this embodiment, since the server can receive the status change instruction sent by the second terminal, it can update the execution status of the configuration information of the Easter egg file in the server according to the status change instruction, thereby making it easier for the user to know the execution status of the Easter egg file stored in the second terminal.
[0082] Reference Figure 8 , Figure 8 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 8 As shown, the method also includes S801 to S803, combining Figure 8 The steps shown are explained.
[0083] S801: Receive the management instruction sent by the first terminal. The management instruction carries the third configuration information of the third Easter egg file.
[0084] In some possible embodiments, a user can manage the third Easter egg file stored on the server through a first terminal. The first terminal can send a management command to the server, which carries third configuration information of the third Easter egg file. After receiving the management command sent by the first terminal, the server can perform corresponding management actions on the third Easter egg file stored on the server.
[0085] For example, when a user needs to delete a third-party Easter egg file on the server, they can send a first management command to the server through a first terminal. This first management command carries third configuration information and instructs the server to delete the stored third-party Easter egg file. A user can also obtain a third-display file of a third-party Easter egg file uploaded by another user from the server. After editing the obtained third-display file to create a new display file, the user can send a second management command to the server through the first terminal. This second management command carries the third configuration information of the third-party Easter egg file and instructs the server to send a download command carrying the third-display file to the first terminal.
[0086] S802, In response to the Easter egg management command, determine the server configuration information stored in the server that matches the third configuration information of the third Easter egg file.
[0087] In some possible embodiments, after receiving the management instruction sent by the first terminal, the server needs to first determine the server configuration information that matches the third configuration information, and then determine the corresponding Easter egg file based on the server configuration information.
[0088] S803, execute management commands for the Easter egg files corresponding to the server configuration information.
[0089] In some possible embodiments, since an Easter egg file can be uniquely identified through the verification information in the configuration information, the user can delete the Easter egg file from the server or download the display file from the server based on the verification information.
[0090] For example, when a user needs to delete a third-party Easter egg file, they can send a first management command carrying third-party verification information to the server through a first terminal. After receiving the first management command, the server determines the third-party Easter egg file stored on the server based on the third-party verification information and deletes it. When another user shares third-party verification information with another user, that user can send a second management command carrying the third-party verification information to the server through a first terminal. After receiving the second management command, the server determines the third-party display file of the third-party Easter egg file stored on the server based on the third-party verification information and sends a download command carrying the third-party display file to the first terminal. After receiving the download command, the first terminal saves the third-party display file carried by the download command.
[0091] In this embodiment, since the server can receive management instructions sent by the user through the first terminal, it can delete the Easter egg files stored on the server, or the user can download the display file of an Easter egg file stored on the server to the first terminal, so that the user can obtain a new display file.
[0092] Reference Figure 9 , Figure 9 This is a flowchart illustrating the method for pushing Easter egg files provided in an embodiment of this application. The method is applied to a first terminal, such as... Figure 9 As shown, the method includes S901, which combines... Figure 9 The steps shown are explained.
[0093] S901. Send an Easter egg upload command to the server; the Easter egg upload command carries configuration information and a first display file corresponding to the configuration information. The Easter egg upload command is used to instruct the server to store the configuration information, and if a first display file matching the configuration information exists in the display file repository on the server, discard the first display file carried by the Easter egg upload command.
[0094] In some possible embodiments, users or operators can configure multiple display files stored on the first terminal, where each display file includes content that enables the second terminal to perform display actions. For example, users can use the first terminal's configuration software to edit the push target and triggering account in the display file, thereby creating a new display file. Users can also download, export, or delete display files on the first terminal.
[0095] In this embodiment, after the user or operator completes the configuration of the first display file on the first terminal, they can send an Easter egg upload command to the server. During the process of the first terminal uploading the first display file to the server, the first terminal first generates the configuration information for the first display file. After generating the configuration information, the first terminal generates an Easter egg upload command carrying the first display file and the configuration information, and sends the Easter egg upload command to the server. The server receives the Easter egg upload command sent by the first terminal. This Easter egg upload command can instruct the server to store the configuration information, and also instruct the server to discard the first display file carried by the Easter egg upload command if a first display file matching the configuration information exists in the display file repository on the server.
[0096] For example, the Easter egg upload command can instruct the server to perform the following actions: First, obtain the hash value from the configuration information of the first display file; then compare the hash value of the first display file with the hash values in all configuration information on the server to determine whether a display file identical to the first display file exists in the server's display file repository. If the hash value of the first display file does not exist on the server, it means that a display file identical to the first display file does not exist in the server's display file repository, and the first display file is also stored on the server. However, if the hash value of the first display file exists on the server, it means that a display file identical to the first display file exists in the server's display file repository, and the server only saves the configuration information of the first display file, without saving the first display file itself.
[0097] In this embodiment, since the configuration information and the corresponding first display file are two separate files, the first terminal can configure only the first display file, simplifying the user's configuration process and reducing the possibility of leakage of user information included in the configuration information. Furthermore, the upload command can instruct the server to save the configuration information and the first display file according to different storage strategies. If the first display file already exists on the server, it will not be saved a second time, reducing the storage space occupied by the first display file.
[0098] Reference Figure 10 , Figure 10 This is a flowchart illustrating the method for pushing Easter egg files provided in an embodiment of this application. Figure 10 As shown, based on Figure 9 The method also includes steps S1001 to S1002, which combine... Figure 10 The steps shown are explained.
[0099] S1001, Receive the configuration instructions for the first display file.
[0100] In some possible embodiments, the user can configure the first display file stored in the first terminal in different ways to form different first display files. For example, the user can configure the first display file stored in the mobile phone, which is the first terminal. The user can send a configuration command to the mobile phone by touching the configuration interface of the first display file displayed on the mobile phone. After receiving the configuration command, the mobile phone will perform the corresponding configuration action.
[0101] Users can edit, delete, export, and create the first display file via their mobile phones, or obtain the first display file from other places.
[0102] In some possible embodiments, the above-described S1001 can be implemented by at least one of S10011 to S10013.
[0103] S10011. Receive the configuration instruction to determine the push target in the first display file.
[0104] S10012. Receive the configuration instruction that determines the trigger conditions in the first display file.
[0105] S10013, Receive a configuration instruction that determines the configuration items of the second terminal in the first display file and the execution order of the configuration items; the configuration items include the hardware in the second terminal that performs display actions based on the first display file.
[0106] In some possible embodiments, a user can create a new first display file on a first terminal. For example, if a user creates a new first display file using a mobile phone, the user can generate a first display file through different configuration options in the touch configuration interface. For instance, the user can select the target of the Easter egg file to be pushed to a second terminal; they can also select or set the trigger conditions for the Easter egg file; and they can determine the configuration items required by the second terminal when performing the display action, as well as the execution order of each configuration item. These configuration items are different hardware that the second terminal can support, such as windows, displays, and speakers in different vehicles. The mobile phone then generates a new display file based on the different configuration instructions received from the user via touch.
[0107] S1002. In response to the configuration command, generate the first display file.
[0108] In some possible embodiments, the first terminal may generate a new first display file based on the configuration instructions received from the user, or a new first display file may be generated by editing other display files.
[0109] The method for pushing Easter egg files provided in this application can be applied to a second terminal. (Refer to...) Figure 11 , Figure 11 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 12 As shown, the method includes S1101 to S1102, combining Figure 11 The steps shown are explained.
[0110] S1101, Receive push instruction sent by server carrying first display file; The server is used to receive the Easter egg upload instruction sent by first terminal carrying configuration information and first display file, and in response to the Easter egg upload instruction, store configuration information, and if there is a first display file matching the configuration information in the display file repository in the server, discard the first display file carried by the Easter egg upload instruction.
[0111] S1102. Perform the display action based on the first display file.
[0112] In some possible embodiments, the second terminal may be a device or apparatus capable of executing the content corresponding to the first display file. The second terminal may receive a push command sent by the server. Specifically, after receiving the easter egg upload command from the first terminal, the server stores the configuration information corresponding to the first display file in the server; simultaneously, it compares the configuration information of the first display file with all configuration information stored in the server. If it determines that there is configuration information in the server that matches the configuration information of the first display file, it discards the first display file carried by the easter egg upload command. In this way, the server can determine the second terminal that can push the first display file based on the push target and verification information in the stored configuration information. After determining the second terminal that can push the first display file, the server sends a push command to the second terminal, which carries the first display file. After receiving the push command and storing the first display file, the second terminal can perform the corresponding display action based on the information included in the first display file.
[0113] Reference Figure 12 , Figure 12 This is a flowchart illustrating the method for pushing Easter egg files provided in an embodiment of this application. Figure 12 As shown, the method further includes S1201 to S1203, combining Figure 12 The steps shown are explained.
[0114] S1201, Receive the Easter egg detection command sent by the server; the Easter egg detection command carries server configuration information; the server configuration information includes the configuration information of the server.
[0115] In some possible embodiments, users can delete or upload new Easter egg files stored on the server. When the Easter egg files stored on the server change, the Easter egg files stored on the second terminal will be inconsistent with the Easter egg files stored on the server. The second terminal can then match the stored Easter egg files to ensure that the Easter egg files stored on the second terminal are consistent with the Easter egg files stored in the cloud.
[0116] For example, the server can send an Easter egg detection command carrying server configuration information to the second terminal at a preset frequency. The second terminal receives the Easter egg detection command, and the server configuration information includes all configuration information stored on the server.
[0117] S1202, In response to the Easter egg detection command, obtain terminal configuration information; the terminal configuration information includes all configuration information existing in the second terminal.
[0118] In some possible embodiments, after receiving the Easter egg detection instruction, the second terminal first obtains all the terminal configuration information existing in the second terminal so that it can compare the terminal configuration information with the received server configuration information.
[0119] S1203. Based on the terminal configuration information and server configuration information, send an Easter egg matching instruction to the server; the Easter egg matching instruction is used to match the Easter egg files stored in the second terminal and the server.
[0120] In some possible embodiments, the second terminal can compare each server configuration information received from the server with the terminal configuration information stored in the second terminal to determine whether the Easter egg file stored in the second terminal is the same as the Easter egg file stored in the server. If it is determined that the Easter egg file stored in the second terminal is different from the Easter egg file stored in the server, the second terminal can send an Easter egg matching command to the server. This command ensures that the terminal Easter egg file stored in the second terminal is consistent with the server Easter egg file stored in the server.
[0121] In some other possible embodiments, each terminal repository of the second terminal shares the same storage address as a configuration information repository on the server. However, because updates to the Easter egg files in the second terminal lag behind updates to the Easter egg files on the server, the Easter egg files stored at the same storage address on the second terminal and the server may be different. That is, the verification information included in the configuration information at the same storage address on the second terminal and the server may be different. Conversely, the verification information included in the configuration information at different storage addresses on the second terminal and the server is usually different. Therefore, it is possible to determine whether the Easter egg files on the second terminal and the server are consistent based on the storage address and verification information in the configuration information.
[0122] For example, firstly, based on the second storage address in a server configuration information, the first storage address in a second terminal that has the same second storage address is determined, thereby determining the terminal configuration information corresponding to the first storage address; then, the second verification information in the server configuration information of the second storage address is obtained; then, the first verification information in the terminal configuration information of the first storage address is obtained, thereby determining whether the first verification information and the second verification information are the same, and further determining whether the Easter egg file in the second terminal and the server is consistent. If the verification information in the obtained terminal storage repository is empty, it indicates that the Easter egg file does not exist in the terminal storage repository; if the verification information in the obtained configuration information storage repository is empty, it indicates that the configuration information storage repository does not contain configuration information, that is, the Easter egg file corresponding to the second verification information does not exist in the server.
[0123] Reference Figure 13 , Figure 13 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 13 As shown, based on Figure 12 The configuration information includes verification information. Figure 12 S1203 in the above can be implemented through S1301 to S1302, which will combine Figure 13 The steps shown are explained.
[0124] S1301. Obtain the first verification information in the terminal configuration information and the second verification information in the server configuration information; the configuration information corresponding to the first verification information and the configuration information corresponding to the second verification information have a matching relationship.
[0125] S1302, if the first verification information is empty and the second verification information is not empty, a first matching instruction is sent to the server; the first matching instruction carries the configuration information corresponding to the second verification information; the first matching instruction is used to instruct the server to send the Easter egg file corresponding to the second verification information to the second terminal.
[0126] In some possible embodiments, after the second terminal obtains the first verification information in the terminal configuration information and the second verification information in the server configuration information, it needs to determine whether the first verification information and the second verification information are the same. For example, if the first verification information in a terminal repository of the second terminal is null, and the second verification information on the server is not null, it indicates that the server stores a server Easter egg file, while the second terminal does not have a terminal Easter egg file identical to that server Easter egg file. In this case, the second terminal can send a first matching instruction to the server, which carries the second verification information or the configuration information corresponding to the second verification information. After receiving the first matching instruction, the server sends the Easter egg file corresponding to the second verification information stored on the server to the second terminal, and the second terminal saves the Easter egg file corresponding to the second verification information.
[0127] Reference Figure 14 , Figure 14 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 14 As shown, based on Figure 12 The configuration information includes verification information. Figure 12 S1203 in the process can be implemented through S1401 to S1402, which will combine Figure 14 The steps shown are explained.
[0128] S1401. Obtain the first verification information in the terminal configuration information and the second verification information in the server configuration information; the configuration information corresponding to the first verification information and the configuration information corresponding to the second verification information have a matching relationship.
[0129] S1402. If the first verification information is not empty and the second verification information is empty, generate a second matching instruction; the second matching instruction is used to delete the Easter egg file corresponding to the first verification information in the second terminal.
[0130] In some possible embodiments, if the first verification information obtained by the second terminal from a terminal storage repository of the second terminal is a non-empty value, and the second verification information of the server is an empty value, it indicates that the Easter egg file in the server has been deleted, while the second terminal still stores the Easter egg file. In this way, the second terminal can generate a second matching instruction, which includes the first verification information. Based on the second matching instruction, the second terminal deletes the Easter egg file corresponding to the first verification information.
[0131] Reference Figure 15 , Figure 15 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 15 As shown, based on Figure 12 The configuration information includes verification information. Figure 12S1203 in the above can be implemented through S1501 to S1502, which will combine Figure 15 The steps shown are explained.
[0132] S1501. Obtain the first verification information in the terminal configuration information and the second verification information in the server configuration information; the configuration information corresponding to the first verification information and the configuration information corresponding to the second verification information have a matching relationship.
[0133] S1502, if the first verification information and the second verification information are both non-empty and inconsistent, a third matching instruction is sent to the server; the third matching instruction carries the configuration information corresponding to the second verification information, and the third matching instruction is used to instruct the server to send the Easter egg file corresponding to the second verification information to the second terminal.
[0134] In some possible embodiments, if both the first verification information in the second terminal's terminal storage repository and the second verification information in the server are non-empty values, and the first and second verification information are inconsistent, it indicates that the Easter egg file corresponding to the second verification information in the server is an updated Easter egg file, while the second terminal has not yet updated the Easter egg file corresponding to the first verification information to the one corresponding to the second verification information. In this case, the second terminal can send a third matching instruction to the server, which carries the Easter egg file corresponding to the second verification information. After receiving the third matching instruction, the server sends the Easter egg file corresponding to the second verification information stored in the server to the second terminal. The second terminal deletes the Easter egg file corresponding to the first verification information and saves the received Easter egg file corresponding to the second verification information, thus completing the matching with the Easter egg file in the server, ensuring that the Easter egg file stored in the second terminal is consistent with the Easter egg file stored in the server.
[0135] In this embodiment, since the server can send an Easter egg detection command to the second terminal, and the Easter egg detection command carries server configuration information, the second terminal, based on the Easter egg detection command and according to the terminal configuration information and server configuration information, if it is determined that the Easter egg file of the second terminal is inconsistent with the Easter egg file stored on the server, the second terminal then sends an Easter egg matching command to the server. This allows the server to send an Easter egg file that does not exist on the second terminal, or the second terminal can delete the terminal Easter egg file corresponding to the server Easter egg file that is no longer stored on the server. This ensures that the Easter egg file stored on the second terminal matches and is consistent with the Easter egg file stored on the server, and thus the display action corresponding to the display file can be executed in a timely manner on the second terminal.
[0136] Reference Figure 16 , Figure 16 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 16 As shown, based on Figure 11 The method also includes steps S1601 to S1602, combining Figure 16 The steps shown are explained.
[0137] S1601. Check the integrity of the first display file sent by the server.
[0138] S1602. If the first display file is confirmed to be complete, add an executable tag to the first display file.
[0139] In some possible embodiments, after the second terminal receives the first display file sent by the server and saves the first display file, the integrity of the first display file can be checked. Only if the first display file is determined to be complete can the first display file be executed.
[0140] For example, after the second terminal receives the first display file sent by the server, it can calculate the hash value of the first display file using a hash algorithm to determine whether the first display file is complete. If the first display file is determined to be complete, an executable tag can be added to it. The second terminal then determines whether to execute the first display file based on whether it has the executable tag. This avoids situations where the user selects to trigger a condition in the first display file even if it is incomplete, resulting in the second terminal being unable to fully execute the display action.
[0141] Reference Figure 17 , Figure 17 A flowchart illustrating the method for pushing Easter egg files provided in this application embodiment is shown below. Figure 17 As shown, based on Figure 11 The method also includes S1701, which combines Figure 17 The steps shown are explained.
[0142] S1701. In the event that the execution status of the first display file changes, a status change instruction is sent to the server; the status change instruction carries the configuration information of the first display file and the execution status of the Easter egg file.
[0143] In some possible embodiments, after the Easter egg file stored on the second terminal meets the trigger condition and the trigger condition is triggered, the second terminal will perform the corresponding display action according to the content of the stored first display file. Alternatively, after the Easter egg file stored on the second terminal meets the trigger condition and the trigger condition is triggered, but due to some factors of the second terminal, the second terminal does not complete the display action related to the content of the first display file. In both cases, the first display file stored on the second terminal has undergone an execution status change event. Then, the second terminal can send a status change instruction to the server. This status change instruction carries information about the execution status of the second terminal for the first display file, which can be executed or failed. When the server receives the status change instruction sent by the second terminal, it determines the server configuration information according to the configuration information and updates the execution status information in the server configuration information based on the execution status in the status change instruction.
[0144] In this embodiment, since the second terminal can send a status change instruction to the service, the server can update the execution status of the configuration information of the Easter egg file in the server according to the status change instruction, thereby making it easier for users to know the execution status of the Easter egg file.
[0145] This application also provides a system for pushing Easter egg files, as described in the embodiments of this application. Figure 18 , Figure 18 This is a schematic diagram illustrating the composition of the Easter egg file push system provided in the embodiments of this application, such as... Figure 18 The Easter egg file push system 1800 includes: a first terminal 1801, a server 1802, and a second terminal 1803, wherein:
[0146] The first terminal 1801 is used to send an Easter egg upload command to the server 1802; the Easter egg upload command carries an Easter egg file including a display file and configuration information.
[0147] Server 1802 responds to the Easter egg upload command by determining the storage status of the display file based on the configuration information. If the display file exists in the display file repository in server 1802, the server discards the display file carried by the Easter egg upload command and stores the configuration information. Based on the configuration information, the server sends a push command carrying the Easter egg file to the second terminal 1803.
[0148] The second terminal 1803 is used to receive and store the Easter egg files pushed by the server 1802, and to perform display actions based on the display files.
[0149] The following describes the application of the Easter egg file push method provided in this application embodiment in a real-world scenario, using a mobile phone as the first terminal, a passenger vehicle as the second terminal, and cloud storage as the server as an example. Easter egg configuration software is installed on the mobile phone, the required Easter egg file management software is installed in the cloud, and the vehicle-side Easter egg file management software is installed in the passenger vehicle's controller.
[0150] Reference Figure 19 , Figure 19 This is a schematic diagram illustrating the content of the Easter egg file provided in this embodiment of the application. The Easter egg file 1900 mainly includes two parts: configuration information 1901 and display file 1902. The display file 1902 includes the Easter egg file name, the vehicle model information to be pushed, the triggering method of the Easter egg file, information on the display materials, and execution order information.
[0151] For example, the name of the Easter egg file can be a birthday Easter egg, an operational Easter egg, or a user-defined name. Vehicle information can be sedan, multi-purpose vehicle (MPV), sportutility vehicle (SUV), etc. The triggering method for the Easter egg file can be expiration date triggering, voice triggering, interface click triggering, required number of clicks, passenger entry triggering, and unlock triggering, etc. The expiration date triggering method can be set as follows: from a first time to a second time, the Easter egg file is triggered when the vehicle's system time reaches the first time, and the vehicle begins executing the display action corresponding to the content of the displayed file; when the vehicle's system time reaches the second time, the vehicle ends the execution of the display action. The voice triggering method can be set as follows: add trigger corpus, and the Easter egg file is triggered when the vehicle receives a voice message matching the trigger corpus. The interface click method can be achieved by setting a target button in the vehicle as the trigger button. When a target button in the vehicle is pressed, the vehicle begins to execute a demonstration action. The trigger method for the required number of touches can be set to: the button in the vehicle is pressed a certain number of times consecutively, such as 2 to 8 consecutive presses, at which point the vehicle begins to execute the demonstration action. The trigger method for the passenger entering the vehicle can be set to: the vehicle begins to execute the demonstration action when the vehicle's camera detects an occupant in the passenger seat, or when the pressure sensor on the passenger seat detects pressure exceeding a preset value. The trigger method for unlocking the vehicle can be set to: displaying a prompt for the execution of the Easter egg file on the vehicle's display screen, along with an unlocking pattern; after the user unlocks the vehicle, the vehicle begins to execute the demonstration action. It should be noted that multiple trigger methods can be selected simultaneously, or only one trigger method can be selected. Demonstration material information includes the type of demonstration material, such as video, audio, images, and text. Execution order information can include the execution order and coordination relationships of the vehicle's configuration items.
[0152] Configuration information 1901 includes the uploader, upload time, Easter egg file type, target vehicle model, triggering account, hash value of the displayed file, storage address, and Easter egg file execution status. The uploader and upload time are automatically generated by the Easter egg configuration software on the phone when the Easter egg file is uploaded. The Easter egg file type, target vehicle model, triggering account, hash value, and execution status are also generated by the Easter egg configuration software based on the displayed file. The storage address is empty when uploaded to the cloud; after uploading, the cloud automatically fills it in based on the availability of Easter egg files in the target vehicle's repository. The execution status includes not executed, executed, and executed but failed. When uploading the Easter egg file to the cloud via phone, the default execution status is not executed.
[0153] Reference Figure 20 and Figure 21 , Figure 20 This is a flowchart illustrating the method for pushing Easter egg files provided in an embodiment of this application. Figure 21 This is a functional diagram of the Easter egg file push system provided in the embodiments of this application, which will be combined with Figure 20 and Figure 21 The content shown is explained.
[0154] S2001: Receive Easter egg files uploaded by users or operators in the cloud.
[0155] After users edit the Easter egg file on their mobile phones, they can choose to upload it to the cloud. Before uploading, the mobile app generates corresponding configuration information for the file, and then sends the file and configuration information together as an Easter egg file to the cloud. Operations personnel can also edit the Easter egg file and upload it to the cloud; their uploads also generate configuration files. The cloud receives Easter egg files uploaded by users or operations personnel and caches them.
[0156] In one possible implementation, such as Figure 21 As shown, users can use their mobile phones to manage, save, export, upload, download, and edit the display files in the Easter egg files, and operators can also upload the Easter egg files to the cloud.
[0157] For example, after a user finishes editing a presentation file stored on their mobile device, when they need to upload the edited presentation file to the cloud, the mobile device first generates a configuration file based on the current time, the user uploading, the type of the Easter egg file, vehicle model information, and the verification information of the presentation file, and then sends the Easter egg file, which includes the presentation file and the configuration file, to the cloud. Users can also obtain presentation files from other electronic devices with storage capabilities, edit the obtained presentation files to create new presentation files. Users can also obtain presentation files from the cloud; for example, after a user enters a hash value shared by another customer, the cloud sends the presentation file from the Easter egg file corresponding to that hash value to the mobile device. The user can then edit the presentation file received on the mobile device, for example, by modifying the vehicle model information.
[0158] Users can also delete the display files saved on their mobile devices and send a deletion command to the cloud to delete the corresponding Easter egg files. After receiving the deletion command, the cloud will delete the display files corresponding to the command and set all information in the configuration information to null. Users can also export the display files in the mobile configuration software to the local storage of their mobile phones.
[0159] Users can also choose to create a new display file, referring to Figure 22 and... Figure 23 , Figure 22 and Figure 23 These are schematic diagrams of a configuration interface of the mobile phone configuration software provided in the embodiments of this application. The process of creating a new display file is as follows:
[0160] First, select the target vehicle model information. After confirming the model information, the configuration interface 2200 will display the configuration items included in the target model, such as windows, seats, glove box, and ambient lighting. Then, based on the selected target model, select the supported trigger methods that appear. Trigger methods include: validity period trigger, voice trigger, passenger entry trigger, and unlock trigger. Next, based on the configuration items supported by the target model that appear in the configuration interface, you can easily configure them by dragging and dropping. For example, you can drag configuration item 2202 from the configurable item bar 2201 to the timeline 2203; configuration items on the same timeline 2203 will start executing simultaneously. You can also drag configuration item 2202 from the timeline 2203 to another location; dragging it back to the configurable item bar 2201 is considered deletion. Double-clicking or using other interactive methods to operate a timeline allows you to edit the length of the time period occupied by that timeline. Figure 23 As shown, the time interval 2303 can be selected to be accurate to the second. If the time interval differs from the audio and video durations on that timeline, the time interval shall prevail. Double-clicking or using other interactive methods to operate a configuration item 2202 on a timeline allows you to set the controller for that configuration item to control the display actions performed by that item. Figure 23As shown, the options for window operation 2301 are: open or close the driver's side window, open or close the passenger side window; the options for central control screen operation 2302 are: play video or play audio; finally, if the user clicks save 2204, the display file will be saved according to the above configuration; if the user clicks cancel 2205, the user will return to the previous screen.
[0161] In another example, when a user needs to push an Easter egg file to a target vehicle, they first select the vehicle model information in the Easter egg configuration interface. If the available vehicle models in the configuration interface match or are compatible with the target vehicle, the user can then select a trigger user. The trigger user can be a user already bound to the target vehicle or a guest. After the user completes the selection, the mobile device calculates the hash value of the display file and sends the display file and its configuration information together as an Easter egg file to the cloud.
[0162] S2002, Easter egg files stored in the cloud.
[0163] After receiving a command from a user or operations staff to upload an Easter egg file and caching the file, the cloud first retrieves the hash value from the configuration information and performs a check on it. Based on the hash value check result, it determines how to save the received Easter egg file.
[0164] For example, to save storage space, a display file repository and multiple configuration information repositories can be set up in the cloud, with each configuration information repository assigned a unique storage address. The configuration information repositories can also be categorized into different types based on the type of Easter egg file. For instance, if 20 configuration information repositories are set up, each repository has an independent storage address. The first configuration information repository has storage address 1 and is the birthday Easter egg repository; the second to tenth configuration information repositories have storage addresses 2 to 10 respectively and are all operation Easter egg repositories; and the eleventh to twentieth configuration information repositories have storage addresses 11 to 20 respectively and are all custom Easter egg repositories. If the size of each Easter egg file is set to not exceed 20MB, then when all Easter egg files reach their maximum storage space requirement, the total storage space occupied on the vehicle side will be approximately 400MB.
[0165] If the cloud determines that the hash value in the received Easter egg file does not exist, it stores the cached Easter egg file's display file in the display file repository, stores the configuration information in the corresponding type of configuration information repository, adds the storage address of the configuration information repository to the configuration information, and sets the execution status in the configuration information to "not executed." If the cloud determines that the hash value in the received Easter egg file exists, it only stores the cached configuration information in the corresponding type of configuration information repository and discards the cached display file.
[0166] S2003, The cloud pushes the Easter egg file to the target vehicle.
[0167] In some possible embodiments, 20 storage packets with storage addresses can be preset in the target vehicle. The storage packets of the target vehicle have the same storage address as the configuration information repository in the cloud and correspond one-to-one with the configuration information repository.
[0168] For example, after uploading an Easter egg file to the cloud, a user can synchronize the hash value to the target vehicle, or obtain the hash value of an Easter egg file shared by other users through the Easter egg sharing section in the mobile phone configuration software, and synchronize the hash value obtained through sharing to the target vehicle. If the cloud detects that the target vehicle stores a hash value, and the cloud also stores that hash value, then it pushes the Easter egg file corresponding to that hash value to the target vehicle. After receiving the push instruction from the cloud, the target vehicle stores the received Easter egg file in a storage package with the same storage address as the cloud, according to the storage address in the configuration information.
[0169] In other possible embodiments, after the target vehicle's infotainment system is activated, it can proactively determine whether the first hash value of each Easter egg file in the target vehicle matches the second hash value of the Easter egg file in the cloud. The first and second hash values correspond to Easter egg files with the same storage address in the target vehicle and the cloud, respectively. If the first and second hash values are inconsistent, an Easter egg update command is sent to the cloud, carrying the configuration information of the Easter egg file that needs to be updated. After receiving the Easter egg update command, the cloud sends an Easter egg synchronization command carrying the updated Easter egg file to the target vehicle.
[0170] For example, if a first Easter egg file exists in the cloud but the target vehicle does not have this first Easter egg file, the cloud sends an Easter egg synchronization command carrying the first Easter egg file to the target vehicle. Upon receiving the first Easter egg file, the target vehicle saves it. If the target vehicle has a second Easter egg file but the cloud does not have it, the target vehicle deletes the second Easter egg file. If a third Easter egg file exists in the cloud and the target vehicle has a fourth Easter egg file, the cloud sends an Easter egg synchronization command carrying the third Easter egg file to the target vehicle. Upon receiving the third Easter egg file, the target vehicle updates the fourth Easter egg file to the fourth Easter egg file.
[0171] In some other possible embodiments, after receiving the Easter egg file, the target vehicle can recalculate the hash value of the received display file to determine whether the received Easter egg file is complete. Only complete Easter egg files can enter the execution process.
[0172] In some other possible embodiments, when the trigger condition of the Easter egg file stored in the target vehicle is triggered and the Easter egg file is complete, the target vehicle begins to execute the display action corresponding to the content of the display file. After the display action is completed, the target vehicle can send a status change command to the cloud carrying the Easter egg file "executed". If the execution condition is met, but the display action corresponding to the content of the display file is not successfully executed due to reasons attributable to the target vehicle, the target vehicle can send a status change command to the cloud carrying the Easter egg file "execution failed". After receiving the status change command, the cloud modifies the execution status in the configuration information of the corresponding Easter egg file, thereby facilitating user review.
[0173] For example, if the conditions in the vehicle meet the triggering method of the Easter egg file, the corresponding configuration items in the vehicle are controlled by the vehicle controller to perform the display action based on the display file. For example, if the display actions include "opening the driver's side window", "playing a video on the passenger side screen", and "turning on the ambient lights", then the driver's side window is opened, the video in the display file is played on the passenger side screen, and the ambient lights are turned on.
[0174] In this embodiment, the Easter egg file is configured to include both a display file and configuration information. The configuration of the display information within the Easter egg file is set on the mobile device with a visual configuration interface. Users can quickly and easily modify the display file by simply selecting and dragging options on the configuration interface. This allows the Easter egg file, including the display file, to be pushed to multiple target vehicles of different models via the cloud. Storing the configuration information in a different location in the cloud than the display file avoids the leakage of users' personal privacy information. Furthermore, a hash value is set for the display file, which uniquely identifies each Easter egg file. This hash value allows for different management of Easter egg files in the cloud and on the target vehicles. The cloud can also push Easter egg files to target vehicles by obtaining the hash value stored in the target vehicle, ensuring accurate delivery. Setting a hash value for the display file also prevents the target vehicle from failing to perform the complete display action due to an incomplete Easter egg file. Furthermore, setting a hash value facilitates mutual analysis of Easter egg files among users. Meanwhile, because the Easter egg files are formatted as including both display files and configuration information, and these are stored independently, Easter egg files with identical display file content but different configuration information are saved only once, reducing the storage space required in the cloud. By setting Easter egg update strategies for target vehicles and combining this with the management methods of users and operations personnel for Easter egg files in the cloud, for illegal Easter egg files containing inappropriate materials, the files stored in the cloud can be directly deleted, thus deleting all illegal Easter egg files stored for all target vehicles.
[0175] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
1. A method of pushing a file of a color egg, characterized by, Applied to a server, the method includes: The system receives an Easter egg upload instruction sent by a first terminal; the Easter egg upload instruction carries configuration information and a first display file corresponding to the configuration information; the configuration information includes at least a push target and verification information; the verification information is generated based on the first display file. In response to the Easter egg upload command, the configuration information is stored, and if the first display file matching the configuration information exists in the display file repository in the server, the first display file carried by the Easter egg upload command is discarded; Based on the push target, at least one target to be pushed is determined, and terminal verification information saved by the at least one target to be pushed is obtained. If the terminal verification information is the same as the verification information, the target to be pushed corresponding to the terminal verification information is determined as a second terminal, and a push instruction carrying the first display file is sent to the second terminal. The push instruction is used to instruct the second terminal to perform a display action based on the first display file. The system receives an Easter egg update command sent by the second terminal; the Easter egg update command carries terminal configuration information; the terminal configuration information includes all configuration information existing in the second terminal; In response to the Easter egg update command, server configuration information is obtained; the server configuration information includes all configuration information existing on the server; the configuration information includes verification information. Obtain first verification information from the terminal configuration information and second verification information from the server configuration information; the configuration information corresponding to the first verification information and the configuration information corresponding to the second verification information have a matching relationship. If the first verification information is empty and the second verification information is not empty, a first synchronization instruction is sent to the second terminal; the first synchronization instruction carries the Easter egg file corresponding to the second verification information.
2. The push method of the Easter egg file according to claim 1, wherein, The storage of the configuration information includes: Based on the type of Easter egg corresponding to the configuration information, determine the storage location of the configuration information; The configuration information is stored on the server based on the storage location.
3. The push method of the Easter egg file according to claim 1, wherein, The method further includes: If the first verification information is not empty and the second verification information is empty, a second synchronization command is sent to the second terminal; the second synchronization command is used to delete the Easter egg file corresponding to the first verification information in the second terminal. And / or, if both the first verification information and the second verification information are non-empty and inconsistent, a third synchronization instruction is sent to the second terminal; the third synchronization instruction carries the Easter egg file corresponding to the second verification information, and the third synchronization instruction is used to update the Easter egg file corresponding to the first verification information in the second terminal to the Easter egg file corresponding to the second verification information.
4. The push method of the Easter egg file according to claim 1, wherein, The configuration information includes execution status information, and the method further includes: The system receives a status change instruction sent by the second terminal in response to an execution status change event for the first displayed file; the status change instruction carries the execution status of the second terminal for the first displayed file. In response to the status change instruction, the execution status information in the configuration information is updated based on the execution status.
5. The push method of the Easter egg file according to claim 1, wherein, The method further includes: Receive a management instruction sent by the first terminal, the management instruction carrying configuration information of the third Easter egg file; In response to the Easter egg management instruction, determine the configuration information stored in the server that matches the configuration information of the third Easter egg file; Execute management commands for the Easter egg files corresponding to the configuration information stored in the server.
6. A method for pushing Easter egg files, characterized in that, Applied to a second terminal, the method includes: The server receives a push instruction carrying a first display file from a server; the server receives an "Easter egg upload instruction" carrying configuration information and the first display file from a first terminal, and in response to the "Easter egg upload instruction," stores the configuration information, and discards the first display file carried by the "Easter egg upload instruction" if a first display file matching the configuration information exists in the display file repository in the server; wherein, the configuration information includes at least a push target and verification information; the verification information is generated based on the first display file; the push instruction is sent by the server to the second terminal after determining at least one push target according to the push target, obtaining terminal verification information saved by the at least one push target, and determining the push target corresponding to the terminal verification information as a second terminal if the terminal verification information is the same as the verification information; Perform the display action based on the first display file; An Easter egg update command is sent to the server, causing the server to respond to the Easter egg update command and obtain server configuration information; the server configuration information includes all configuration information existing on the server; the configuration information includes verification information; first verification information in the terminal configuration information and second verification information in the server configuration information are obtained; the configuration information corresponding to the first verification information and the configuration information corresponding to the second verification information have a matching relationship; if the first verification information is empty and the second verification information is not empty, a first synchronization command is sent to the second terminal; the first synchronization command carries the Easter egg file corresponding to the second verification information; wherein, the Easter egg update command carries terminal configuration information; the terminal configuration information includes all configuration information existing on the second terminal.
7. The push method of the Easter egg file according to claim 6, wherein, The method further includes: Detect the integrity of the first display file sent by the server; If the first display file is confirmed to be complete, an executable tag is added to the first display file.
8. A system for pushing Easter egg files, characterized in that, The push system includes a first terminal, a second terminal, and a server, wherein: The first terminal is used to send an Easter egg upload instruction to the server; the Easter egg upload instruction carries an Easter egg file including a display file and configuration information; the configuration information includes at least a push target and verification information; the verification information is generated based on the first display file; and is also used to send the verification information to the second terminal; The server is configured to respond to the Easter egg upload command, determine the storage status of the display file based on the configuration information; if the storage status indicates that the display file exists in the display file repository on the server, discard the display file carried by the Easter egg upload command and store the configuration information; determine at least one target to be pushed to based on the push target, obtain terminal verification information saved by the at least one target to be pushed to, and if the terminal verification information is the same as the verification information, determine the target to be pushed to corresponding to the terminal verification information as the second terminal, and send a push command carrying the Easter egg file to the second terminal; and is also configured to receive an Easter egg update command sent by the second terminal; the Easter egg... The egg update command carries terminal configuration information; the terminal configuration information includes all configuration information existing in the second terminal; in response to the egg update command, server configuration information is obtained; the server configuration information includes all configuration information existing in the server; the configuration information includes verification information; first verification information in the terminal configuration information and second verification information in the server configuration information are obtained; the configuration information corresponding to the first verification information and the configuration information corresponding to the second verification information have a matching relationship; if the first verification information is empty and the second verification information is not empty, a first synchronization command is sent to the second terminal; the first synchronization command carries the egg file corresponding to the second verification information; The second terminal is used to receive and store the Easter egg file pushed by the server, and to perform a display action based on the display file.
Citation Information
Patent Citations
Method and system for eliminating multiplicating storage based on cloud storage
CN103516774A
Festival painted egg display method combining vehicle-mounted voice and message center
CN115510315A
