Scene file management method, device, system, electronic device, and storage medium

Abstract

Embodiments of the present application provide a scene file management method, device, system, electronic equipment and storage medium. The scene file management method comprises: receiving a scene instruction issued by a vehicle cloud service, wherein the scene instruction is sent to the vehicle cloud service by a scene cloud engine according to a received download notification, and the download notification is sent to the scene cloud engine by a scene experience center in response to a download request; downloading a corresponding scene file from the scene cloud engine according to the scene instruction; and controlling at least one vehicle component to operate according to the scene file in response to a received execution instruction. This scheme does not require the user to spend time defining the scene file, thereby improving the user's use experience.

Description

Technical Field

[0001] This application relates to the field of vehicle networking technology, and in particular to a method, apparatus, system, electronic device and storage medium for scene file management. Background Technology

[0002] With the development and advancement of automotive technology, users can customize components such as air conditioning, ambient lighting, audio-visual systems, and seats according to their application scenarios to meet their personalized needs. However, customizing different components individually can be time-consuming, impacting the user experience.

[0003] Currently, to improve the user experience of cars, users can customize scene files. Scene files define the operating states of multiple components on the car. After selecting the corresponding scene file, users can quickly set the components on the car to the state corresponding to the scene, eliminating the need for users to set multiple components on the car separately.

[0004] However, users have different needs for the operating status of various components in a car under different usage scenarios. Therefore, users need to define scenario files for different usage scenarios. However, defining scenario files takes a long time, resulting in a poor user experience. Summary of the Invention

[0005] In view of the above, embodiments of this application provide a method, apparatus, system, electronic device, and storage medium for managing scene files, so as to at least partially solve the above problems.

[0006] According to a first aspect of the embodiments of this application, a scene file management method is provided, applied to a vehicle. The method includes: receiving a scene instruction issued by a vehicle cloud service, wherein the scene instruction is sent to the vehicle cloud service by a scene cloud engine according to a received download notification, and the download notification is sent to the scene cloud engine by a scene experience center in response to a download request; downloading a corresponding scene file from the scene cloud engine according to the scene instruction; and controlling at least one vehicle component to operate according to the scene file in response to a received execution instruction.

[0007] According to a second aspect of the embodiments of this application, a scene file management device is provided, applied to a vehicle. The device includes: a receiving module, configured to receive scene instructions issued by a vehicle cloud service, wherein the scene instructions are sent to the vehicle cloud service by a scene cloud engine according to a received download notification, and the download notification is sent to the scene cloud engine by a scene experience center in response to a download request; an obtaining module, configured to download a corresponding scene file from the scene cloud engine according to the scene instructions; and a control module, configured to control at least one vehicle component to operate according to the scene file in response to a received execution instruction.

[0008] According to a third aspect of the embodiments of this application, a scene file management system is provided. The system includes: a scene experience center, a scene cloud engine, and a vehicle terminal; the scene experience center is used to send a download notification to the scene cloud engine in response to a received download request; the scene cloud engine is used to send scene instructions to the vehicle cloud service according to the received download notification; the vehicle terminal is used to receive the scene instructions sent by the vehicle cloud service, download the corresponding scene file from the scene cloud engine according to the scene instructions, and control at least one vehicle component to operate according to the scene file in response to a received execution instruction.

[0009] According to a fourth aspect of the present application, an electronic device is provided, the device comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other through the communication bus; the memory is used to store at least one executable instruction, the executable instruction causing the processor to perform an operation corresponding to the scene file management method described in the first aspect.

[0010] According to a fifth aspect of the embodiments of this application, a computer storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the scene file management method as described in the first aspect.

[0011] According to the solution provided in this application embodiment, the scene command is sent by the scene cloud engine to the vehicle cloud service based on the received download notification. The download notification is sent by the scene experience center to the scene cloud engine in response to the download request. Then, the vehicle cloud service sends the scene command to the vehicle. The vehicle downloads the corresponding scene file from the scene cloud engine based on the received scene command, and then the vehicle executes the command, controlling at least one vehicle component to operate according to the acquired scene file. During the process of acquiring the scene file, the user can directly send a download request to the scene experience center, thereby pushing the scene command to the vehicle, eliminating the need for the user to spend time defining the scene file, thus improving the user experience. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings.

[0013] Figure 1 This is a schematic diagram of a scene file management method according to an embodiment of this application;

[0014] Figure 2 This is a schematic diagram of a scene file management device according to an embodiment of this application;

[0015] Figure 3 This is a schematic diagram of a scene file management system according to an embodiment of this application;

[0016] Figure 4 This is a schematic diagram of a scene file management system according to another embodiment of this application;

[0017] Figure 5 This is a schematic diagram of an electronic device according to an embodiment of this application. Detailed Implementation

[0018] The present application is described below based on embodiments, but it is not limited to these embodiments. In the detailed description of the present application below, certain specific details are described in detail. Those skilled in the art can fully understand the present application without these details. To avoid obscuring the essence of the present application, well-known methods, processes, and flows are not described in detail. Furthermore, the accompanying drawings are not necessarily drawn to scale.

[0019] Scene file management method

[0020] This application provides a scenario file management method, which will be described in detail below through multiple embodiments.

[0021] Figure 1 This is a flowchart of a scene file management method according to an embodiment of this application. Figure 1 As shown, the file management method for this scenario includes the following steps:

[0022] Step S102: Receive scenario instructions issued by the vehicle cloud service.

[0023] Scene instructions are sent from the scene cloud engine to the vehicle cloud service based on the received download notification. The download notification can be any appropriate form of notification. The download notification is sent from the scene experience center to the scene cloud engine in response to the download request. The download request is sent from the vehicle or mobile device via the network and can be any appropriate form of request.

[0024] The download notification includes some user information, such as user ID, scene file information, and the vehicle ID corresponding to the user ID, but is not limited to these.

[0025] Vehicle cloud services can send scenario commands to the scenario vehicle engine through the vehicle-cloud link and vehicle-cloud communication module.

[0026] Step S104: Download the corresponding scene file from the scene cloud engine according to the scene instructions.

[0027] The vehicle can download the corresponding scene file from the scene cloud engine according to the scene command. The download progress and status are synchronized to the scene cloud engine in real time so that the mobile device can see it in real time.

[0028] Step S106: In response to the received execution command, control at least one vehicle component to operate according to the scenario file.

[0029] The vehicle responds to the execution command and controls the operation of at least one vehicle component according to the scene file. The vehicle component may include, but is not limited to, components such as air conditioning, ambient lighting, audio-visual system, and seats.

[0030] In this embodiment, the scene command is sent from the scene cloud engine to the vehicle cloud service based on the received download notification. The download notification is sent from the scene experience center to the scene cloud engine in response to the download request. The vehicle cloud service then sends the scene command to the vehicle. The vehicle downloads the corresponding scene file from the scene cloud engine based on the received scene command, and then executes the command, controlling at least one vehicle component to operate according to the acquired scene file. During the scene file acquisition process, the user can directly send a download request to the scene experience center, thereby pushing the scene command to the vehicle. This eliminates the need for the user to spend time defining scene files, thus improving the user experience.

[0031] In one possible implementation, users can access the Scene Experience Center on the vehicle side to query the scenes provided by the Scene Experience Center. Specifically, the vehicle side can send a query request to the Scene Experience Center, then receive a list of scenes in response to the query request, and then, in response to the selection of a target scene in the scene list, send a download request to the Scene Experience Center.

[0032] The scenario list includes scenario information for at least one scenario. For example, the scenario list includes scenario information for scenarios such as rest, leisure, and entertainment. The scenario information includes control strategies for multiple vehicle components involved in the corresponding scenario, such as playing soothing music, automatic seat heating, and setting the air conditioning to 26°C, but is not limited to these.

[0033] The vehicle can display a list of scenarios, from which users can select a target scenario. After the user selects a target scenario, the vehicle sends a download request to the scenario experience center.

[0034] In this embodiment, the user can send a query request to the scene experience center via the vehicle to obtain a scene list. The vehicle can display the scene list, and the user can select the target scene information from the list according to their needs. Based on the user's selection, the vehicle sends a download request to the scene experience center, thereby downloading the scene file corresponding to the target scene information. The scene file is then executed to construct the corresponding scene. The scene experience center provides directly accessible scene files, making it more convenient and faster for users.

[0035] In one possible implementation, the scene file is uploaded from the scene development platform to the scene experience center, and then sent by the scene experience center to the scene cloud engine. After the scene file is approved by the operation management terminal, the scene information corresponding to the scene file is published in the scene experience center.

[0036] Scene files can be generated by Original Equipment Manufacturer (OEM) professionals or external developers through the scene development platform and uploaded to the Scene Experience Center. When an uploaded scene file needs to be updated, OEM professionals or external developers can update the scene file and upload it to the Scene Experience Center.

[0037] The operations management terminal can manage scene data on the scene cloud engine. When there is a problem with a scene under a personal account, the operations personnel can view the scene data through the operations management terminal.

[0038] In vehicle usage scenarios, if users want to control the operation of multiple vehicle components with one click, they need to spend time customizing and editing scenario files. If users are not familiar with the various components of the car, they cannot effectively maximize the utilization of the capabilities of each component.

[0039] In this embodiment, the scene file can be developed by OEM professionals or external developers. Users only need to query the scene from the scene experience center through the vehicle or mobile terminal. After the vehicle or mobile terminal obtains the scene list, the user selects the target scene information from the scene list. Then, the vehicle or mobile terminal sends a download request to the scene experience center. The vehicle then downloads the scene file corresponding to the target scene information and constructs the scene by executing the scene file. This saves the user's time and helps the user effectively maximize the utilization of the capabilities of various components of the vehicle.

[0040] In one possible implementation, after receiving the editing instruction, the vehicle can edit the scene file according to the editing instruction to obtain the edited scene file, and then send the edited scene file to the scene cloud engine so that the mobile terminal connected to the scene cloud engine can manage the edited scene file.

[0041] Scene files can be edited by users on the vehicle or mobile device. The mobile device can retrieve the edited scene file from the scene cloud engine via a query request, edit the retrieved scene file again, and then upload it to the scene cloud engine via the network. The scene cloud engine then synchronizes the scene file to the vehicle via the vehicle cloud service, ensuring real-time synchronization between the scene files on the vehicle and mobile devices.

[0042] Edited scene files can also be shared on the shared platform, making it convenient for other users to search, download, and use them.

[0043] In this embodiment, users can customize and edit scene files and then upload them to the scene cloud engine so that the scene files seen on the vehicle and mobile devices are synchronized in real time. The edited scene files can be shared to the sharing platform, making it convenient for other users to query, download and use them. The sharing platform can increase user stickiness, provide customers with a convenient way to obtain scene files, and improve the user experience.

[0044] In one possible implementation, the vehicle can receive execution commands input by the user through the vehicle or receive execution commands sent by the vehicle cloud service, and then respond to the execution commands to control the operation of vehicle components according to the scenario file.

[0045] When an execution command is received from the vehicle cloud service, the execution command is sent from the mobile terminal to the vehicle cloud service through the scene cloud engine.

[0046] In this embodiment, the user can send execution commands to the scene cloud engine via a mobile device, and then the scene cloud engine will send the corresponding scene commands to the vehicle via the vehicle cloud service to achieve remote control of the operation of at least one vehicle component, providing a faster and more convenient way for the user to execute scene files.

[0047] Scene file management device

[0048] Figure 2 This is a schematic diagram of a scene file management device provided in one embodiment of this application, as shown below. Figure 2 As shown, the scene file management device 200 includes:

[0049] The receiving module 202 is used to receive scenario instructions issued by the vehicle cloud service.

[0050] Scene instructions are received through receiving module 202. The scene instructions are sent to the vehicle cloud service by the scene cloud engine based on the received download notification. The download notification can be any appropriate notification form. The download notification is sent to the scene cloud engine by the scene experience center in response to the download request. The download request is sent by the vehicle or mobile terminal through the network and can be any appropriate request form.

[0051] The download notification includes some user information, such as user ID, scene file information, and the vehicle ID corresponding to the user ID, but is not limited to these.

[0052] Vehicle cloud services can send scenario commands to the scenario vehicle engine through the vehicle-cloud link and vehicle-cloud communication module.

[0053] The acquisition module 204 is used to download the corresponding scene file from the scene cloud engine according to the scene instructions.

[0054] The vehicle-side downloads the corresponding scene file from the scene cloud engine through the acquisition module 204. The download progress and status are synchronized to the scene cloud engine in real time so that the mobile device can see it in real time.

[0055] The control module 206 is used to control the operation of at least one vehicle component in response to a received execution command, based on a scenario file.

[0056] Based on the scenario file, the vehicle controls at least one vehicle component to operate through the control module 206, such as air conditioning, ambient lighting, audio-visual system, seats, etc., but not limited to these.

[0057] In this embodiment, the scene command is sent from the scene cloud engine to the vehicle cloud service via the receiving module 202 based on the received download notification. The download notification is sent from the scene experience center to the scene cloud engine in response to the download request. The vehicle cloud service then sends the scene command to the vehicle. The vehicle downloads the corresponding scene file from the scene cloud engine via the acquisition module 204. The vehicle then executes the command via the control module 206 and controls at least one vehicle component to operate based on the acquired scene file. During the scene file acquisition process, the user can directly send a download request to the scene experience center, thereby pushing the scene command to the vehicle. This eliminates the need for the user to spend time defining scene files, thus improving the user experience.

[0058] It should be noted that the above-described scenario file management device embodiment and the aforementioned scenario file management method embodiment are based on the same inventive concept. For details, please refer to the description in the aforementioned scenario file management method embodiment, which will not be repeated here.

[0059] Scene File Management System

[0060] Figure 3 This is a schematic diagram of a scene file management system provided in one embodiment of this application, as shown below. Figure 3 As shown, the scene file management system includes: a scene experience center 302, a scene cloud engine 304, a vehicle cloud server 306, and a vehicle terminal 308. The vehicle terminal 302 can be an in-vehicle system device installed inside a vehicle.

[0061] The Scene Experience Center 302 can respond to a received download request by sending a download notification to the Scene Cloud Engine 304. Upon receiving the download notification, the Scene Cloud Engine 304 can send scene commands to the vehicle terminal 308 via the Vehicle Cloud Service 306. After receiving the scene commands from the Vehicle Cloud Service 306, the vehicle terminal 308 can download the corresponding scene file from the Scene Cloud Engine 304 according to the scene commands. After downloading the scene file, the vehicle terminal 308 can respond to a received execution command and control at least one vehicle component to operate according to the scene file.

[0062] The sender of the aforementioned download request can be either the vehicle-side (302) or a mobile device, such as a smartphone or tablet. For example, if a user has installed an application on their mobile device that can manage scene files, they can send a download request to the scene experience center (302) through the application. After receiving the download request, the scene experience center (302) sends a download notification to the scene cloud engine (304). This download notification may include user information, such as the user ID, scene file information, and the vehicle ID corresponding to the user ID, but is not limited to these.

[0063] When the scene cloud engine 304 receives the download notification sent by the scene experience center 302, it will send the corresponding scene instructions to the vehicle cloud service 306 with the corresponding vehicle ID according to the information included in the download notification.

[0064] The scene status (including download progress, status, etc.) when the scene file is downloaded on the vehicle side 302 is synchronized to the vehicle cloud service 306 through the vehicle-cloud communication module and vehicle-cloud link. The vehicle cloud service 306 then synchronizes the scene status to the scene cloud engine 304 in real time, so that the mobile terminal connected to the scene cloud engine 304 can see the scene status in real time.

[0065] The downloaded scene file will be stored in the user's personal account on the scene cloud engine 304. The user can select the downloaded scene file in the vehicle terminal 308 and issue a scene execution command. The vehicle terminal 302 receives the execution command and controls at least one vehicle component to operate according to the scene file to be executed, such as air conditioning, ambient lighting, audio-visual system, seats, etc., but not limited to these.

[0066] In this embodiment, the scene command is sent by the scene cloud engine 304 to the vehicle cloud service 306 based on the received download notification. The download notification is sent by the scene experience center 302 to the scene cloud engine 304 in response to the download request. Then, the vehicle cloud service 306 sends the scene command to the vehicle terminal 308. The vehicle terminal 308 downloads the corresponding scene file from the scene cloud engine 304 based on the received scene command. Then, the vehicle terminal 308 responds to the execution command and controls at least one vehicle component to operate based on the obtained scene file.

[0067] Figure 4 This is a schematic diagram of a scene file management system according to another embodiment of this application. Figure 4 As shown, the scene file management system, in addition to the scene experience center 408, scene cloud engine 406, vehicle cloud service 404 and vehicle terminal 402, may also include a scene development platform 410 and an operation management terminal 412.

[0068] The scene development platform 410 can respond to file upload commands and send scene files to the scene experience center 408. The operation management terminal 412 can review the scene files received by the scene experience center 408 and send approval information to the scene experience center 408 after the scene files have been approved. The scene experience center 408 can then send the received scene files to the scene cloud engine 406.

[0069] Original Equipment Manufacturer (OEM) professionals or external developers can develop scenarios through the scenario development platform 410. The developed scenario files can be uploaded to the scenario experience center 408 through the interface opened by the scenario experience center 302. The scenario experience center 408 will send the received scenario files to the scenario cloud engine 406 to store the scenario data.

[0070] Scene files published from the scene development platform 410 to the scene experience center 408 cannot be immediately pushed to the mobile terminal 414 or the vehicle terminal 402. They need to be reviewed by the operation management personnel through the operation management terminal 412. If a fee is required, a quotation must also be provided. After the review is approved, the review approval information is sent to the scene experience center 408. After receiving the review approval information, the scene experience center 408 publishes the scene information corresponding to the scene file to provide users with directly accessible scene files for management.

[0071] The vehicle-side 408 installs a scene vehicle-side application, a scene vehicle-side engine, and a vehicle-cloud communication module. When the vehicle cloud service 404 sends scene instructions to the scene vehicle-side engine through the vehicle-cloud link and the vehicle-cloud communication module, the scene vehicle-side engine downloads the corresponding scene file from the scene cloud engine 406 via the network according to the received scene instructions.

[0072] Users can query the scene cloud engine 406 through the application on mobile device 414 or vehicle device 402 to obtain a scene list. The scene list includes scene information for at least one scene. For example, the scene list includes scene information for scenarios such as resting, relaxation, and entertainment. Scene information includes, but is not limited to, playing soothing music, automatic seat heating, and setting the air conditioner to cooling 26°C. Users can select target scene information from the obtained scene list to trigger a download request sent to the scene experience center 408.

[0073] The downloaded scene files will be stored in the personal account on the scene cloud engine 406. When there are problems with user management of scenes, the operators can query the scene data on the scene cloud engine 406 through the operation management terminal 410 and manage the scene data.

[0074] Users can edit the obtained scene files. The edited scene files are sent to the scene cloud engine 406 to be synchronized to the vehicle terminal 402 in real time. Users can also share the edited scene files to the sharing square so that other users can query, download and use them through the sharing square, thus realizing scene sharing.

[0075] In this embodiment, users can customize and edit scene files through vehicle terminal 402 or mobile terminal 414, and then upload them to scene cloud engine 406 so that the scene files seen by vehicle terminal 402 and mobile terminal 414 are synchronized in real time. The edited scene files can be shared to the sharing square, making it convenient for other users to query, download and use. The sharing square can increase user stickiness, provide customers with a convenient way to obtain scene files, and improve the user experience.

[0076] It should be noted that the above-described scenario file management system embodiment and the aforementioned scenario file management method embodiment are based on the same inventive concept. For details, please refer to the description in the aforementioned scenario file management method embodiment, which will not be repeated here.

[0077] electronic devices

[0078] Figure 5 This is a schematic block diagram of an electronic device provided in an embodiment of this application. Specific embodiments of this application do not limit the specific implementation of the electronic device. Figure 5 As shown, the electronic device may include: a processor 502, a communications interface 504, a memory 506, and a communications bus 508. Wherein:

[0079] The processor 502, communication interface 504, and memory 506 communicate with each other via communication bus 508.

[0080] Communication interface 504 is used to communicate with other electronic devices or servers.

[0081] The processor 502 is used to execute program 510, which can specifically execute the relevant steps in any of the aforementioned scenarios of the file management method embodiments.

[0082] Specifically, program 510 may include program code that includes computer operation instructions.

[0083] The processor 502 may be a CPU, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application. The smart device may include one or more processors of the same type, such as one or more CPUs; or it may include processors of different types, such as one or more CPUs and one or more ASICs.

[0084] Memory 506 is used to store program 510. Memory 506 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0085] Specifically, program 510 can be used to cause processor 502 to execute the scene file management method in any of the foregoing embodiments.

[0086] The specific implementation of each step in program 510 can be found in the corresponding steps and units described in any of the aforementioned scenario file management method embodiments, and will not be repeated here. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the devices and modules described above can be referred to the corresponding process descriptions in the aforementioned method embodiments, and will not be repeated here.

[0087] In the electronic device of this application embodiment, scene commands are sent from the scene cloud engine to the vehicle cloud service based on a received download notification. The download notification is sent from the scene experience center to the scene cloud engine in response to the download request. The vehicle cloud service then sends the scene commands to the vehicle. The vehicle downloads the corresponding scene file from the scene cloud engine based on the received scene commands, and then executes the command, controlling at least one vehicle component to operate according to the acquired scene file. During the process of acquiring the scene file, the user can directly send a download request to the scene experience center, thereby pushing the scene commands to the vehicle, eliminating the need for the user to spend time defining scene files, thus improving the user experience.

[0088] storage media

[0089] In this embodiment, a computer-readable storage medium is provided, storing instructions for causing a machine to execute the scene file management method as described herein. Specifically, a system or apparatus equipped with a storage medium may be provided, on which software program code implementing the functions of any of the embodiments described above is stored, and the computer (or CPU or MPU) of the system or apparatus may read and execute the program code stored in the storage medium.

[0090] In this case, the program code read from the storage medium can itself implement the function of any of the above embodiments, and therefore the program code and the storage medium storing the program code constitute part of this application.

[0091] Examples of storage media used to provide program code include floppy disks, hard disks, magneto-optical disks, optical disks (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), magnetic tapes, non-volatile memory cards, and ROMs. Alternatively, program code can be downloaded from a server computer via a communication network.

[0092] It should be noted that in the description of this application, the terms "first" and "second" are used only for convenience in describing different components or names, and should not be construed as indicating or implying a sequential relationship, relative importance, or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of those features.

[0093] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

[0094] It should be noted that although specific embodiments of this application have been described in detail with reference to the accompanying drawings, this should not be construed as limiting the scope of protection of this application. Various modifications and variations that can be made by those skilled in the art without inventive effort within the scope described in the claims still fall within the scope of protection of this application.

[0095] The examples of the embodiments in this application are intended to concisely illustrate the technical features of the embodiments in this application, so that those skilled in the art can intuitively understand the technical features of the embodiments in this application, and are not intended to be improper limitations on the embodiments in this application.

[0096] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A scenario file management method, applied to the vehicle end, characterized in that, The vehicle terminal is located in the scene file management system, which includes the vehicle terminal, a scene experience center, a scene cloud engine, and a vehicle cloud service. The method includes: Send a query request to the scene experience center, so that the scene experience center responds to the query request and sends a scene list to the vehicle terminal, the scene list including scene information of at least one scene; The system receives the scene list sent by the scene experience center and displays it to the user. In response to the user's selection of target scene information in the scene list, the system sends a download request to the scene experience center. The target scene information describes the scene corresponding to the scene file. In response to the download request, the scene experience center sends a download notification to the scene cloud engine. The scene cloud engine sends a scene instruction to the vehicle cloud service according to the received download notification. The vehicle cloud service then sends the scene instruction to the vehicle. The system receives scene instructions from the vehicle cloud service and downloads the scene file corresponding to the target scene information from the scene cloud engine according to the scene instructions. The scene status of the vehicle during the download is synchronized to the vehicle cloud service via the vehicle-cloud communication module and vehicle-cloud link. The vehicle cloud service then synchronizes the scene status to the scene cloud engine in real time, so that mobile devices connected to the scene cloud engine can see the scene status in real time. The scene status includes download progress and status. The downloaded scene file is stored in a personal account on the scene cloud engine. In response to a received execution command, at least one vehicle component is controlled to operate according to the scenario file, wherein the user selects the downloaded scenario file on the vehicle terminal and then issues the execution command.

2. The method according to claim 1, characterized in that, The scene file is uploaded from the scene development platform to the scene experience center, and then sent by the scene experience center to the scene cloud engine. After the scene file is approved by the operation management terminal, the scene information of the scene corresponding to the scene file is published in the scene experience center.

3. The method according to claim 1, characterized in that, The method further includes: Receive editing instructions; The scene file is edited according to the editing instructions to obtain the edited scene file; The edited scene file is sent to the scene cloud engine so that the mobile terminal connected to the scene cloud engine can manage the edited scene file.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: Receive the execution command input by the user through the vehicle terminal; or, The system receives the execution instruction sent by the vehicle cloud service, wherein the execution instruction is sent by the mobile terminal to the vehicle cloud service through the scene cloud engine.

5. A scene file management device, applied to a vehicle, characterized in that, The vehicle terminal is located in the scene file management system, which includes the vehicle terminal, a scene experience center, a scene cloud engine, and a vehicle cloud service. The device includes: A receiving module is used to receive scene instructions issued by the vehicle cloud service. The scene instructions are sent to the vehicle cloud service by the scene cloud engine based on a received download notification. The download notification is sent to the scene cloud engine by the scene experience center in response to a download request. The download request is sent to the scene experience center by the vehicle terminal in response to the user's selection of target scene information in the displayed scene list. The target scene information describes the scene corresponding to the scene file. The scene list is sent to the vehicle terminal by the scene experience center in response to a query request sent by the vehicle terminal. The scene list includes scene information of at least one scene. The acquisition module is used to download the scene file corresponding to the target scene information from the scene cloud engine according to the scene instruction; wherein, the scene status of the vehicle terminal when downloading the scene file is synchronized to the vehicle cloud service through the vehicle cloud communication module and the vehicle cloud link, and the vehicle cloud service synchronizes the scene status to the scene cloud engine in real time, so that the mobile terminal connected to the scene cloud engine can see the scene status in real time, and the scene status includes download progress and status; the downloaded scene file is stored in a personal account on the scene cloud engine; A control module is used to control at least one vehicle component to operate in response to a received execution command, based on the scenario file, wherein the user selects the downloaded scenario file in the vehicle terminal and then issues the execution command.

6. A scene file management system, characterized in that, The system includes: a scene experience center, a scene cloud engine, vehicle-side and vehicle cloud services; The vehicle terminal is used to send a query request to the scene experience center; The scene experience center is used to respond to the query request and send a scene list to the vehicle terminal. The scene list includes scene information of at least one scene. The vehicle terminal is also configured to receive the scene list sent by the scene experience center and display it to the user, and in response to the user's selection of target scene information in the scene list, send a download request to the scene experience center, wherein the target scene information is used to describe the scene corresponding to the scene file; The scene experience center is also used to send a download notification to the scene cloud engine in response to the received download request; The scene cloud engine is used to send scene instructions to the vehicle cloud service based on the received download notification; The vehicle cloud service is used to send the scene instructions to the vehicle. The vehicle terminal is also configured to receive the scene instructions issued by the vehicle cloud service, and download the scene file corresponding to the target scene information from the scene cloud engine according to the scene instructions, and control at least one vehicle component to operate according to the scene file in response to the received execution instructions; wherein, the scene status of the vehicle terminal when downloading the scene file is synchronized to the vehicle cloud service through the vehicle-cloud communication module and the vehicle-cloud link, and the vehicle cloud service synchronizes the scene status to the scene cloud engine in real time, so that the mobile terminal connected to the scene cloud engine can see the scene status in real time, and the scene status includes download progress and status; the downloaded scene file is stored in a personal account on the scene cloud engine; the user selects the downloaded scene file on the vehicle terminal and issues the execution instructions.

7. The system according to claim 6, characterized in that, The system also includes: a scenario development platform and an operation management terminal; The scene development platform is used to send the scene file to the scene experience center in response to the file upload command; The operation management terminal is used to review the scene file after receiving it in the scene experience center, and send the review approval information to the scene experience center after the scene file has been approved. The scene experience center is also used to send the received scene file to the scene cloud engine, and after receiving the approval information, to publish the scene information of the scene corresponding to the scene file.

8. An electronic device, characterized in that, The device includes: The processor, communication interface, memory, and communication bus communicate with each other through the communication bus. The memory is used to store at least one executable instruction, which causes the processor to perform the operation corresponding to the scene file management method as described in any one of claims 1-4.

9. A computer storage medium having a computer program stored thereon, which, when executed by a processor, implements the scene file management method as described in any one of claims 1-4.

Images