Multi-vehicle coordination method, apparatus, and system based on scene service orchestration, device, and storage medium

Abstract

The present application discloses a multi-vehicle coordination method, apparatus, and system based on scene service orchestration, a computer device, and a storage medium. The method comprises: receiving an action allocation synchronization instruction sent by a first user, wherein the action allocation synchronization instruction is used for synchronizing a service combination obtained by orchestrating scene services by the first user, and fleet information for executing the service combination; generating a scene file on the basis of the action allocation synchronization instruction, wherein the scene file is used for indicating a plurality of pieces of scene service information comprised in the service combination and vehicle information for executing each scene service; and on the basis of the scene file, issuing an execution instruction to a vehicle for executing a scene service, wherein the execution instruction is used for instructing the vehicle to execute the scene service. In this solution, a user can perform customized orchestration on scene services and allocate services needing to be executed by a plurality of vehicles in a fleet, thereby achieving multi-vehicle coordination based on scene service customized orchestration and greatly improving the degree of freedom and use experience of users.

Description

Multi-vehicle linkage method, device, system, equipment and storage medium based on scenario service orchestration

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on July 21, 2023, with application number 202310898218.2, and entitled “Multi-vehicle linkage method, device, system, equipment and storage medium based on scenario service orchestration”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of vehicle linkage technology, and more specifically, to a multi-vehicle linkage method, apparatus, system, device and storage medium based on scenario service orchestration. Background Art

[0003] With the rise and development of connected vehicle technology, several multi-vehicle collaboration solutions, such as multi-vehicle rhythmic motion, have emerged. However, these solutions rely on multi-vehicle collaboration within pre-defined scenario modes, failing to meet user customization needs. Furthermore, existing scenario service orchestration technologies only support simple scene editing for a single vehicle. While scene files for a single vehicle can be copied to multiple vehicles, the execution of these scenarios across multiple vehicles is unconnected, preventing the coordinated multi-vehicle collaboration of a swarm.

[0004] Summary of the Invention

[0005] This application proposes a multi-vehicle linkage method, device, system, equipment and storage medium based on scene service orchestration to improve the above-mentioned defects.

[0006] In the first aspect, an embodiment of the present application provides a multi-vehicle linkage method based on scene service orchestration, the method comprising: receiving an action allocation synchronization instruction sent by a first user, the action allocation synchronization instruction being used to synchronize a service combination obtained based on the orchestration of the scene service by the first user and the fleet information for executing the service combination; generating a scenario file according to the action allocation synchronization instruction, the scenario file being used to indicate multiple scenario service information included in the service combination and vehicle information for executing each scenario service; and sending an execution instruction to a vehicle executing the scene service according to the scenario file, the execution instruction being used to instruct the vehicle to execute the scene service.

[0007] On the second aspect, an embodiment of the present application also provides a multi-vehicle linkage method based on scene service orchestration, the method including: receiving a user's scene service orchestration instruction, orchestrating the scene service according to the scene service orchestration instruction, and obtaining service combination information after the scene service orchestration; receiving a user's action allocation instruction for the scene, allocating multiple scene services included in the service combination to vehicles in the fleet according to the action allocation instruction, and sending an action allocation synchronization instruction to the cloud, so that the cloud generates a scene file according to the action allocation synchronization instruction, and sends the execution instruction to the vehicles in the fleet according to the scene file, to realize the scheduling of multi-vehicle linkage, and the action allocation synchronization instruction is used to synchronize the service combination and the fleet information of the execution service combination.

[0008] On the third aspect, an embodiment of the present application also provides a multi-vehicle linkage device based on scene service orchestration, the device including: an instruction receiving module for receiving an action allocation synchronization instruction sent by a first user, the action allocation synchronization instruction is used to synchronize the service combination obtained based on the orchestration of the scene service by the first user and the fleet information for executing the service combination; a scene file generation module for generating a scene file according to the action allocation synchronization instruction, the scene file is used to indicate multiple scene service information included in the service combination and the vehicle information for executing each scene service; a scheduling module for sending an execution instruction to a vehicle executing the scene service according to the scene file, the execution instruction is used to instruct the vehicle to execute the scene service.

[0009] Fourthly, an embodiment of the present application also provides a multi-vehicle linkage device based on scene service orchestration, the device including: a scene service orchestration module, used to receive the user's scene service orchestration instructions, orchestrate the scene service according to the scene service orchestration instructions, and obtain the service combination information after the scene service orchestration; an action allocation module, used to receive the user's action allocation instructions for the scene, allocate the multiple scene services included in the service combination to the vehicles in the fleet according to the action allocation instructions, and send an action allocation synchronization instruction to the cloud, so that the cloud generates a scene file according to the action allocation synchronization instruction, and sends the execution instruction to the vehicles in the fleet according to the scene file, to realize the scheduling of multi-vehicle linkage, and the action allocation synchronization instruction is used to synchronize the service combination and the fleet information of the execution service combination.

[0010] In the fifth aspect, an embodiment of the present application also provides a multi-vehicle linkage system based on scene service orchestration, the system including a first user terminal, a vehicle associated with the first user terminal, and a cloud; the first user terminal is used to receive the user's scene service orchestration instruction, orchestrate the scene service according to the scene service orchestration instruction, and obtain the service combination information after the scene service orchestration; receive the user's action allocation instruction for the service combination, and allocate the multiple scene services included in the service combination to the vehicles in the fleet according to the action allocation instruction, and the fleet includes at least the vehicle associated with the first user terminal; send an action allocation synchronization instruction to the cloud, the action allocation synchronization instruction is used to synchronize the service combination obtained based on the user's orchestration of the scene service and the fleet information that executes the service combination; the cloud is used to receive the action allocation synchronization instruction sent by the first user terminal, generate a scene file according to the action allocation synchronization instruction, the scene file is used to indicate the multiple scene service information included in the service combination and the vehicle information that executes each scene service; send an execution instruction to the vehicle that executes the scene service according to the scene file, and the execution instruction is used to instruct the vehicle to execute the scene service.

[0011] In a sixth aspect, an embodiment of the present application further provides a computer device, comprising: one or more processors; a memory; one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by one or more processors, and the one or more programs are configured to execute the above method.

[0012] In a seventh aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores a program code executable by a processor, and when the program code is executed by the processor, the processor executes the above method.

[0013] In a multi-vehicle linkage method based on scene service orchestration disclosed in the present application, the user can, as the orchestrator, customize the scene service on the user terminal to obtain a personalized multi-vehicle linkage scene, and allocate the services in the scene to each vehicle in the fleet executing the multi-vehicle linkage scene. The cloud server generates a scene file based on the action allocation and uniformly schedules the multi-vehicle linkage according to the scene file. This method realizes multi-vehicle collaboration based on customized orchestration of scene services, greatly enhancing the user's freedom and usage experience.

[0014] Other features and advantages of the embodiments of the present application will be described in the following description and, in part, will become apparent from the description or be understood by practicing the embodiments of the present application. The objectives and other advantages of the embodiments of the present application can be achieved and obtained through the structures particularly pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0016] FIG1 shows a schematic diagram of a hardware environment applicable to an embodiment of the present application.

[0017] FIG2 shows a flow chart of a multi-vehicle linkage method based on scenario service orchestration proposed according to an embodiment of the present application.

[0018] FIG3(a), FIG3(b), FIG3(c) and FIG3(d) show interface diagrams of scene service orchestration.

[0019] FIG4 shows a schematic diagram of the mapping relationship between the basic configuration and optional packages of vehicle models and the service interface stored in the metamodel system.

[0020] FIG5 shows an interface diagram of action allocation.

[0021] FIG6 shows a flow chart of a multi-vehicle linkage method based on scenario service orchestration proposed according to another embodiment of the present application.

[0022] FIG7 shows a structural block diagram of a multi-vehicle linkage device based on scenario service orchestration according to an embodiment of the present application.

[0023] FIG8 shows a structural block diagram of a multi-vehicle linkage device based on scenario service orchestration proposed in another embodiment of the present application.

[0024] FIG9 shows a structural block diagram of a computer-readable storage medium provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application for which protection is claimed, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work fall within the scope of protection of the present application.

[0026] It should be noted that similar reference numerals and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined or explained in subsequent drawings. At the same time, in the description of this application, the terms "first", "second", etc. are only used to distinguish the description and should not be understood as indicating or implying relative importance.

[0027] As shown in Figure 1, the hardware environment of the scenario-based multi-vehicle linkage system of the present invention includes at least a cloud server 100, a first user terminal 200, a second user terminal 300, a first vehicle 400 associated with the first user terminal, and a second vehicle 500 associated with the second user terminal. A cloud server is a computer or device that provides and manages network resources on a network. In the present invention, the cloud server can be a cloud-controlled V2X platform. V2X (Vehicle to Everything) refers to the exchange of information between vehicles and the outside world. The first user terminal 200 and the second user terminal 300 can refer to various types of devices, including (but not limited to) wireless phones, cellular phones, laptops, multimedia wireless devices, wireless communication personal computer (PC) cards, personal digital assistants (PDAs), external or internal modems, and vehicle computers (on-board computers). A user terminal can be any data device that communicates with the server via wireless channels and / or wired channels (e.g., optical fibers). In the present invention, each user terminal is associated with at least one or more vehicles, allowing users to orchestrate scenario services on the user terminal (e.g., a mobile phone app) and control the associated vehicles to execute the orchestrated scenario services. Here, the first user terminal 200 refers to the user terminal controlled by the scene composer, and the second user terminal 300 refers to the user terminal controlled by other users who join the multi-vehicle linkage fleet. It can be understood that the second user terminal 300 can include multiple, that is, the fleet can include multiple second vehicles 500.

[0028] Optionally, the hardware environment of the multi-vehicle linkage system based on scene choreography in the present invention may only include a cloud server, a first user terminal, and a second user terminal. Among them, the first user terminal and the second user terminal are both car computers (on-board computers), the first user terminal refers to the car computer controlled by the scene choreographer, and the second user terminal refers to the car computer controlled by other users who join the multi-vehicle linkage fleet. The user performs scene service choreography on the car computer APP, establishes a fleet to realize the multi-vehicle linkage scene, and allocates the services required to be executed in the multi-vehicle linkage scene to each vehicle in the fleet. The cloud server instructs the vehicles corresponding to the first and second car computers to execute the allocated services based on the arranged service combination information and action allocation sent by the user, so as to realize multi-vehicle linkage scheduling.

[0029] As mentioned above, existing multi-vehicle linkage solutions all rely on pre-defined scenario modes, failing to meet user customization needs. Furthermore, existing scenario service orchestration technologies only support simple scenario editing for a single vehicle. This allows for copying a single vehicle's scenario file to multiple vehicles, with each vehicle executing the same single scenario. This lacks collaborative interaction between vehicles. Therefore, a multi-vehicle linkage method that meets user customization needs is urgently needed.

[0030] Based on this, the inventors proposed a multi-vehicle linkage method, device, system, computer equipment and computer storage medium based on scene service orchestration, the method including: a first user terminal receives a user's scene service orchestration instruction, orchestrates the scene service according to the scene service orchestration instruction, and obtains service combination information after the scene service orchestration; receives the user's action allocation instruction for the service combination, allocates the multiple scene services included in the service combination to the vehicles in the fleet according to the action allocation instruction, and sends an action allocation synchronization instruction to the cloud, wherein the action allocation synchronization instruction is used to synchronize the service combination obtained based on the user's orchestration of the scene service and the fleet information that executes the service combination; the cloud receives the action allocation synchronization instruction sent by the first user terminal, and generates a scene file according to the action allocation synchronization instruction, wherein the scene file is used to indicate the multiple scene service information included in the service combination and the vehicle information that executes each scene service; the cloud sends the execution instruction to the vehicle that executes the scene service according to the scene file to realize the scheduling of multi-vehicle linkage. It can be seen that in the present invention, the user can act as an arranger to customize the scene service on the user terminal to obtain a personalized multi-vehicle linkage scene, and allocate the services in the scene to each vehicle in the fleet executing the multi-vehicle linkage scene. The cloud server generates a scene file according to the action allocation situation, and uniformly schedules the multi-vehicle linkage according to the scene file. This method allows users to customize the multi-vehicle linkage scene based on personalized needs, and perform multi-vehicle collaborative scheduling according to the multi-vehicle linkage scene, which greatly improves the user experience.

[0031] Please refer to FIG2 , which shows a flow chart of a multi-vehicle linkage method based on scenario service orchestration proposed in one embodiment of the present application, which is used in a cloud server. The method includes:

[0032] S201: Receive an action allocation synchronization instruction sent by a first user, where the action allocation synchronization instruction is used to synchronize a service combination obtained based on the first user's arrangement of scenario services and information about a fleet that executes the service combination;

[0033] It is understandable that the first user is the scene service orchestrator, and the first user performs scene service orchestration and action allocation by controlling the first user terminal. A scene service orchestration APP is installed on the first user terminal for users to perform multi-vehicle scene service orchestration on the APP. Here, "scene services" refer to in-vehicle functional services and third-party ecological services that can be called through the vehicle side. "In-vehicle functional services" specifically refer to SOA (Service-Oriented Architecture) services that can be controlled and executed by various electronic control units (ECUs) on the vehicle, such as window control, seat control, air conditioning control, etc.; "third-party ecological services" specifically refer to services provided by third-party service providers, such as weather services, navigation services, music services, etc.

[0034] Before the first user assigns an action, they must first perform scenario service orchestration on the aforementioned scenario service orchestration app to obtain a multi-vehicle service combination. After entering the scenario service orchestration interface, the first user can modify existing scenario templates or customize the scenario services they want to use. A scenario template is a pre-set scenario in the app that includes several pre-programmed services. The first user can modify the services and service parameters based on the scenario template and save it as their own new scenario.

[0035] As shown in Figure 3(a), the aforementioned scene templates may include templates such as "Multi-car light show", "Celebration begins", and "One-click opening of doors and windows". Figure 3(b) shows the interface of the scene template "One-click opening of doors and windows", which includes three information pages: scene details, scene formation, and action allocation. The scene details list the scene name, scene description, execution actions included in the scene, and parameter information of the execution actions. After the first user opens the interface shown in Figure 3(b), he can click the "Edit" control to edit the relevant information of the scene template to obtain a customized new scene. Figure 3(c) shows the editing interface of the scene template, where the first user can modify the scene name, scene description, set the loop execution to on or off, add or delete various execution actions, and change the service parameters of each execution action.

[0036] When the first user chooses to compose a new scene, he or she can select one or more services to be used from the currently available in-vehicle services and third-party ecological services to create the new scene, and the user can set the service status according to needs, such as: opening the front left window, opening the sunroof, etc. As shown in Figure 3(d), the first user can click the "Add Scene" control, and the right interface pops up for the first user to edit. The first user can add the scene name, scene description, and set the execution action in this interface. When the first user clicks the "Add Action" control on the right interface, he or she can add the required execution action and set the specific service parameters of the execution action (for example, whether the services to be executed are executed simultaneously or in steps, setting the interval between step executions, etc.). After the execution action is set, the execution method of the entire service combination can also be set according to needs, including whether the entire scene is executed in a loop, the number of loop executions, the loop execution interval, etc.

[0037] Supports user-defined orchestration services controlled by the cloud. The cloud can provide specific services to users based on demand and security assessment, including but not limited to:

[0038] Car lights: specify lights and flashing frequency, light language, etc.

[0039] active suspension;

[0040] Doors: including side doors, electric tailgate, and sliding doors;

[0041] Window: including car windows and sunroof;

[0042] front cover;

[0043] Wipers;

[0044] air conditioner;

[0045] Music: play designated or random songs;

[0046] Speaker: volume;

[0047] Voice reading;

[0048] Fragrance.

[0049] In an embodiment of the present invention, the vehicle-side services that support choreography must have corresponding SOA service interfaces, and the vehicles that apply new scenarios must support the vehicle-side services or third-party services required by the new scenarios. Among them, the ability to identify the vehicle-side services supported by the vehicle is provided by the cloud, specifically by the cloud-side meta-model system. The cloud-side meta-model system stores the mapping relationship between the basic configurations and optional packages of all vehicle models and the service interfaces. Therefore, the cloud can obtain the vehicle model and optional packages based on the vehicle's VIN code, and then determine the services supported by the specific vehicle through the mapping relationship, and provide them for scene choreography and runtime identification. As shown in Figure 4, the same car series can include multiple models, and the basic configuration and optional packages of each model may have certain differences. The cloud-side V2X platform manages multiple services, each of which includes multiple service interfaces. The services that the model can support are set according to the basic configuration and optional packages of the model, thereby constructing the mapping relationship shown in Figure 4. In a specific implementation, the scenario service orchestration APP of the first user terminal communicates with the cloud and sends the VIN code of the first vehicle associated with the first user terminal to the cloud. The cloud can identify the model and optional package of the first vehicle based on the VIN code of the first vehicle, and determine the services supported by the first vehicle based on the mapping relationship between all basic configurations and optional packages of the models and service interfaces stored in the cloud meta-model system, and open the services supported by the first vehicle to the first user for selection and orchestration by the first user.

[0050] Different from the single-vehicle scenario service arrangement, the user can set the number of vehicles (such as a minimum value or a range of numbers) for the multi-vehicle linkage scenario in the scenario service arrangement step.

[0051] After the first user completes the orchestration of the scenario service, they save the orchestrated service combination and may also send the orchestrated service combination to the cloud server. Specifically, the cloud server receives a scenario synchronization command sent by the first user, where the scenario synchronization command is used to synchronize the service combination based on the first user's orchestration of the scenario service. Based on the scenario synchronization command, the cloud server generates a first scenario file, which indicates the multiple scenario service information included in the service combination. This first scenario file can be reused and used for multiple multi-vehicle linkages within the same fleet. Each multi-vehicle linkage uses the scenario service information in this scenario file as the basis for subsequent action allocation, thereby customizing the services required to be executed by each vehicle in the same fleet across multiple multi-vehicle linkages. It is understood that this first scenario file can also be used for multi-vehicle linkages across different fleets. When the first user establishes a new fleet, the user can use the scenario service information in this scenario file as the basis for action allocation for the new fleet. It is understood that the first user does not need to synchronize the orchestrated service combination information to the cloud server, and this is not a limitation in the present invention.

[0052] After the scene service is arranged, the first user can establish a fleet that applies the arranged service combination, or directly select the vehicle under his own name (such as the first vehicle associated with the first user terminal) to apply. When the first user chooses to establish a fleet, the fleet initially includes at least the vehicle under the name of the first user (such as the first vehicle associated with the first user terminal). Specifically, the first user terminal responds to the user's selection instruction for the scene application vehicle and establishes a fleet that applies the multi-vehicle linkage scene according to the selection instruction. After the fleet is established, the first user can invite other users to join the fleet by sharing the invitation QR code generated by the first user terminal to other users, and the other users use the APP to scan the code to join; or share the invitation link generated by the first user terminal to other users, and the other users click on the link and call up the APP through the browser to join. Specifically, the first user terminal receives the user's invitation to join the fleet instruction, generates an invitation QR code or invitation link according to the invitation instruction, and sends it to the second user terminal in response to the user's sharing instruction, where the second user terminal refers to the user terminal held by other users, and the second user terminal is associated with at least one or more second vehicles.

[0053] After the second user receives the invitation QR code or invitation link, he can scan the code or click the invitation link to trigger the generation of a request to join the team, and send the request to join the team to the cloud. After the cloud receives the request to join the team sent by the second user, it authenticates the second vehicle associated with the second user. The request to join the team may include the second user identification code and the VIN code of the second vehicle. The cloud authenticates the user identification code and VIN code to ensure that the second vehicle is the vehicle bound to the second user. Optionally, the request to join the team may also include the second user's mobile phone number and the second vehicle VIN code. The cloud authenticates the mobile phone number and VIN code to ensure that the second vehicle is bound to the second user's mobile phone number and the second vehicle is the vehicle bound to the second user. The identity authentication method may also be other methods, which are not limited in the present invention.

[0054] After successful verification, the cloud authorizes vehicle control to the choreographer. Joining the vehicle is only possible after the choreographer's approval. All vehicle and user information joining the fleet is synchronized and stored in the cloud. The cloud also distributes the scenario file to all vehicles already in the fleet. Specifically, after the aforementioned identity verification is successful, the cloud sends a request for the second vehicle associated with the second user to join the fleet to the first user, who then reviews the request. After the first user terminal receives the request from the cloud, the first user can choose to approve the second vehicle's addition. Based on the first user's approval, the first user terminal updates the fleet information in real time and sends feedback and the updated fleet information to the cloud. Based on this feedback, the cloud notifies the second user terminal that its associated second vehicle has joined the fleet. At this point, the fleet executing the multi-vehicle linkage scenario includes not only the first vehicle associated with the first user terminal, but also the second vehicle that has been approved and joined. The second user who has subsequently joined the fleet can view the scheduled scenario services and their progress on the mobile app.

[0055] The first user, the scheduler, can close the joining request at any time. After closing the request or starting the scenario, other users can no longer apply to join the fleet. Specifically, in response to the user's closing joining request instruction, upon receiving the second vehicle's joining request from the cloud, the first user terminal sends a closing joining request feedback message to the cloud. Based on this closing joining request feedback message, the cloud notifies the second user terminal that the fleet has closed its joining request.

[0056] Optionally, since the first user has set the number of vehicles to be used in the multi-vehicle linkage scenario when arranging the scenario service, when the number of vehicles in the fleet reaches the upper limit, the fleet automatically closes the joining application.

[0057] Vehicles that have joined the fleet can exit the fleet at any time. Exiting the fleet does not require review and is effective immediately. The scene the vehicle is executing will stop immediately, and the exit fleet notification instruction will be triggered and sent to the first user terminal.

[0058] Once a fleet closes its membership application, all vehicles in the fleet will be used in the multi-vehicle linkage. As the first user, the orchestrator can freely schedule services for the vehicles invited to join the fleet in the Scenario Service Orchestration App. They can schedule all vehicles in the fleet to execute one or more of the services in the scenario. For example, a user can have all vehicles in the scenario flash their lights and play a specified song simultaneously. They can also schedule specific vehicles in the fleet to execute one or more of the services, such as flashing the lights of cars A and B and playing a specified song in car C.

[0059] Figure 5 shows a schematic diagram of the interface for the first user to assign actions on the scene service arrangement app. On this interface, the first user can add vehicles that perform actions or services under each action, thereby arranging corresponding scene services for each vehicle in the fleet.

[0060] Specifically, the first user terminal receives an action assignment instruction from the first user for a service combination and assigns each scenario service included in the service combination to the first vehicle and / or the second vehicle in the fleet. After the first user completes the action assignment, the first user terminal sends an action assignment synchronization instruction to the cloud, which generates a scenario file based on the action assignment synchronization instruction and issues execution instructions to the vehicles in the fleet based on the scenario file, thereby implementing multi-vehicle coordinated scheduling. The action assignment synchronization instruction is used to synchronize information about the service combination and the fleet that executes the service combination.

[0061] S202: Generate a scenario file according to the action allocation synchronization instruction, where the scenario file is used to indicate information of multiple scenario services included in the service combination and information of a vehicle executing each scenario service;

[0062] In one embodiment, after the cloud receives the action allocation synchronization instruction sent by the first user, it parses the action allocation synchronization instruction to obtain multiple scene service information and vehicle information for executing each scene service. The cloud generates a scene file based on the multiple scene service information and vehicle information obtained by parsing.

[0063] In another embodiment, after completing scenario service orchestration, the first user terminal synchronizes the orchestrated service combination information to the cloud, causing the cloud to generate a reusable first scenario file. This first scenario file is used to indicate the multiple scenario service information included in the service combination. Therefore, when the cloud receives the action allocation synchronization instruction sent by the first user, it can parse the action allocation synchronization instruction, obtain the vehicle information for executing each scenario service, and generate a scenario file based on the first scenario file and the vehicle information.

[0064] After the scene file is generated in the cloud, it is distributed to all vehicles in the fleet.

[0065] S203: Send an execution instruction to a vehicle that executes the scenario service according to the scenario file, where the execution instruction is used to instruct the vehicle to execute the scenario service.

[0066] Once all vehicles requiring a multi-vehicle linkage scenario have joined the fleet and successfully downloaded the scenario file, the scenario can begin running. Specifically, the first user, acting as the orchestrator, can click the "Run Scenario" control on the scenario service orchestration app to trigger a scenario execution command, which is then sent to the cloud. In response to this scenario execution command, the cloud sends execution instructions based on the scenario file to the vehicles executing the scenario service, initiating the multi-vehicle linkage scenario. It should be understood that before the scenario can be executed, all vehicles in the fleet must be powered on, meet safety requirements, and have successfully downloaded the latest version of the scenario file. In response to the scenario execution command, the cloud sends a scenario execution start signal to all vehicles in the fleet. The scenario execution engines in all vehicles in the fleet immediately parse the scenario file and configure the execution of the relevant services according to the cloud schedule. In this embodiment, the scenario file primarily contains information related to the scenario execution, including the scenario name, ID, all services to be executed, and specific parameter information (such as service ID, interface ID, input parameters, interval, and loop). By parsing the scenario file, the vehicle can obtain the specific information of the services to be executed and can then respond to the execution instructions sent by the cloud to execute the relevant services based on the service details.

[0067] In addition, the scene running instruction can also be preset by the composer as a timed trigger when composing the scene service. When the timer reaches the preset time, the scene running instruction can be triggered.

[0068] Specifically, the cloud receives the start-up scenario instruction sent by the first user or automatically triggered, and also performs time base calibration on the vehicles in the fleet according to the start-up scenario instruction; after each preset time interval, the time base calibration is performed again on the vehicles in the fleet. To ensure that multiple vehicles execute instructions accurately and synchronously, when the scenario starts running, the vehicles in the fleet need to immediately sync with the cloud, and then sync again every preset time interval (for example, 1 minute). In the present invention, the syncing method is not specifically limited.

[0069] Sending an execution instruction to a vehicle executing the scenario service according to the scenario file includes:

[0070] Sending a first execution instruction to a vehicle executing the first scenario service according to the first scenario service information among the plurality of scenario service information;

[0071] Receive the feedback result of the vehicle executing the first scenario service after executing the first scenario service, and issue a second execution instruction to the vehicle executing the second scenario service according to the second scenario service information in the multiple scenario service information, until all the multiple scenario services are executed, wherein the execution timing of the first scenario service is earlier than the execution timing of the second scenario service.

[0072] After the initial synchronization is complete, the cloud dispatches execution instructions based on the scenario file's instruction steps. After each vehicle completes each step and reports the results to the cloud, the cloud then issues the next step's instructions to the associated vehicle, and so on, until the scenario execution completes. The cloud obtains the results of all service executions through subscription events, and subscription results are returned asynchronously.

[0073] In another embodiment, the execution instructions sent by the cloud include service information for each scene in the scene file, so that vehicles in the fleet can directly obtain the service information required for execution according to the received execution instructions and execute related services according to the service information.

[0074] Before each service is executed, the vehicle's scenario execution engine calls the service's current status acquisition interface to obtain and record the service's current status, ensuring restoration after the scenario ends. Specifically, after all scenarios have completed execution, each vehicle in the fleet restores each scenario service to its initial state based on the status recorded before the start of each scenario service.

[0075] After all services in the multi-vehicle linkage scenario are executed and the cycle is completed, the multi-vehicle linkage scenario ends. The fleet will not be disbanded automatically after the scenario ends, so that the arranger can run it again. If the arranger does not need to use the current formation to execute the scenario again, the formation can be disbanded manually. After the formation is disbanded, if the scenario needs to be run again, it is necessary to create another formation and invite vehicles to join. Specifically, the first user terminal receives the first user's disband fleet instruction, and disbands the current fleet according to the disband fleet instruction. Of course, the arranger can also choose not to disband the formation, only remove some vehicles, and invite new vehicles to join the formation for re-run.

[0076] This invention proposes a technology for orchestrating vehicle cluster scenario services based on a cloud-based control platform and incorporating an onboard SOA service-oriented architecture to achieve real-time, multi-vehicle collaborative intelligent scenario operation. Specifically, users, acting as orchestrators, can customize and orchestrate available scenario services on their user terminals, creating personalized multi-vehicle linkage scenarios. These scenarios' services are then assigned to each vehicle in the fleet executing the multi-vehicle linkage scenario. The cloud server generates a scenario file based on the action assignments and centrally schedules the multi-vehicle linkage based on the scenario file. This method allows users to customize multi-vehicle linkage scenarios based on their individual needs and implement multi-vehicle collaborative scheduling based on these scenarios, addressing the limitations of existing methods, which are limited in their application scenarios and inflexible, significantly improving the user experience. Users other than orchestrators can freely and flexibly join the fleet and participate in this personalized multi-vehicle linkage scenario, significantly enhancing user freedom and user experience. Furthermore, since the multi-vehicle linkage is centrally scheduled by the cloud, and vehicles in the fleet synchronize their timings through the cloud, precise and synchronized execution of commands across multiple vehicles is ensured, fully guaranteeing the presentation of the scene effects.

[0077] Please refer to Figure 6, which shows a multi-vehicle linkage method based on scenario service orchestration applied to a user terminal. In conjunction with the previous embodiment, this method is applied to a first user terminal and mainly describes the method executed by the user terminal controlled by the orchestrator, including orchestrating scenario services, establishing a fleet, inviting other users to join the fleet, reviewing joining requests, closing joining applications, assigning actions, and disbanding the fleet. The method mainly includes the following steps:

[0078] S301, receiving a scene service arrangement instruction from a user, arranging the scene service according to the scene service arrangement instruction, and obtaining service combination information after the scene service arrangement;

[0079] S302. Receive the user's action allocation instruction for the scenario, allocate the multiple scenario services included in the service combination to the vehicles in the fleet according to the action allocation instruction, and send an action allocation synchronization instruction to the cloud, so that the cloud generates a scenario file according to the action allocation synchronization instruction, and sends the execution instruction to the vehicles in the fleet according to the scenario file to realize the scheduling of multiple vehicles. The action allocation synchronization instruction is used to synchronize the service combination and the fleet information that executes the service combination.

[0080] With reference to the aforementioned embodiment, after the first user completes personalized scenario service orchestration on the scenario service orchestration app, they can continue to establish a fleet using the multi-vehicle linkage scenario on the scenario service orchestration app and invite other users to join the fleet by sharing a QR code or invitation link. The first user has the right to review requests from other users for vehicles associated with the fleet to join, and upon approval, the vehicle associated with the user will be added to the fleet. After establishing the fleet, the first user can assign actions to the vehicles in the fleet and synchronize the orchestrated service combinations and action assignments to the cloud, so that the cloud generates a scenario file based on the orchestrated service combinations and action assignments, and performs unified scheduling of multiple vehicles in the fleet based on the scenario file.

[0081] Referring again to FIG1 , FIG1 shows a multi-vehicle linkage system based on scenario service orchestration, which includes at least: a first user terminal, a vehicle associated with the first user terminal, and a cloud;

[0082] The first user terminal is configured to receive a scenario service orchestration instruction from a user, orchestrate the scenario service according to the scenario service orchestration instruction, and obtain service combination information after the scenario service orchestration; receive an action allocation instruction from a user for the scenario, and allocate multiple scenario services included in the service combination to vehicles in a fleet according to the action allocation instruction, where the fleet includes at least the vehicle associated with the first user terminal; and send an action allocation synchronization instruction to the cloud, where the action allocation synchronization instruction is used to synchronize the service combination obtained based on the user's orchestration of the scenario service and the fleet information that executes the service combination;

[0083] The cloud end is used to receive the action allocation synchronization instruction sent by the first user terminal, generate a scenario file according to the action allocation synchronization instruction, and the scenario file is used to indicate the multiple scenario service information included in the service combination and the vehicle information for executing each scenario service; and send the execution instruction to the vehicle executing the scenario service according to the scenario file, and the execution instruction is used to instruct the vehicle to execute the scenario service.

[0084] The system may further include a second user terminal and a second vehicle associated with the second user terminal to execute the multi-vehicle linkage method mentioned in the above embodiment.

[0085] Referring to FIG. 7 , a multi-vehicle linkage device based on scenario service orchestration in one embodiment of the present invention is shown. The device can be set up in a cloud server and specifically includes:

[0086] An instruction receiving module 701 is configured to receive an action allocation synchronization instruction sent by the first user, wherein the action allocation synchronization instruction is used to synchronize a service combination obtained based on the first user's arrangement of the scenario service and information about a fleet executing the service combination;

[0087] A scenario file generating module 702 is configured to generate a scenario file according to the action allocation synchronization instruction, wherein the scenario file is used to indicate information of multiple scenario services included in the service combination and information of a vehicle executing each scenario service;

[0088] The scheduling module 703 is used to send an execution instruction to a vehicle that executes the scenario service according to the scenario file, and the execution instruction is used to instruct the vehicle to execute the scenario service.

[0089] It is understandable that the device may also be provided with other functional modules to implement other method steps executed in the cloud.

[0090] The apparatus further includes: an identity authentication module for authenticating a second vehicle associated with the second user in response to a request sent by the second user to join the fleet;

[0091] an instruction sending module, configured to send a request for the second vehicle associated with the second user to join the fleet to the first user after the identity verification is passed;

[0092] The fleet management module is further configured to add the second vehicle associated with the second user to the fleet in response to feedback information that the first user agrees that the second vehicle associated with the second user will be added to the fleet.

[0093] The device further comprises: an instruction parsing module for parsing the action allocation synchronization instruction to obtain a plurality of scene service information and vehicle information for executing each scene service;

[0094] The aforementioned scenario file generation module is specifically used to generate the scenario file according to the multiple scenario service information and the vehicle information.

[0095] Optionally, the aforementioned scheduling module is specifically used to: send a first execution instruction to a vehicle executing the first scenario service according to the first scenario service information among the multiple scenario service information; receive feedback results from the vehicle executing the first scenario service after executing the first scenario service, and send a second execution instruction to the vehicle executing the second scenario service according to the second scenario service information among the multiple scenario service information, until all the multiple scenario services are executed, wherein the execution timing of the first scenario service is earlier than the execution timing of the second scenario service.

[0096] Optionally, the aforementioned instruction receiving module is also used to receive an instruction to start the running scene sent by the first user.

[0097] The device also includes a time synchronization module, which is used to perform time base calibration on the vehicles in the fleet according to the start-up operation scenario instruction; and perform time base calibration on the vehicles in the fleet again after each preset time interval.

[0098] Optionally, the instruction receiving module of the device is further used to receive a scene synchronization instruction sent by the first user, where the scene synchronization instruction is used to synchronize a service combination obtained based on the arrangement of the scene service by the first user;

[0099] The aforementioned scenario file generation module can also be used to generate a first scenario file according to the scenario synchronization instruction, where the first scenario file is used to indicate multiple scenario service information included in the service combination; and to generate a scenario file based on the first scenario file and the vehicle information obtained by the aforementioned analysis.

[0100] Referring to FIG8 , it shows a multi-vehicle linkage device based on scenario service arrangement in another embodiment of the present invention. The device can be provided in a user terminal and specifically includes:

[0101] The scene service arrangement module 801 is used to receive a scene service arrangement instruction from a user, arrange the scene service according to the scene service arrangement instruction, and obtain service combination information after the scene service arrangement;

[0102] The action allocation module 802 is used to receive the user's action allocation instructions for the scene, allocate the multiple scene services included in the service combination to the vehicles in the fleet according to the action allocation instructions, and send an action allocation synchronization instruction to the cloud, so that the cloud generates a scene file according to the action allocation synchronization instruction, and sends the execution instruction to the vehicles in the fleet according to the scene file to realize the scheduling of multiple vehicles. The action allocation synchronization instruction is used to synchronize the service combination and the fleet information that executes the service combination.

[0103] It is understandable that the device may also be provided with other functional modules to implement other method steps executed by the user terminal.

[0104] The device also includes a fleet establishment module for receiving a user's selection instruction for a vehicle to be applied to a scenario, and establishing a fleet for applying the scenario according to the selection instruction, wherein the fleet includes at least a first vehicle associated with the first user.

[0105] The device also includes an invitation module for receiving a user's instruction to invite a user to join a fleet, generating an invitation QR code or an invitation link, and sending the code to a second user terminal.

[0106] The device also includes an audit module for receiving a request from the cloud for a second vehicle to join the fleet, where the second vehicle is a vehicle associated with a second user; receiving an instruction from the user to agree to the second vehicle joining the fleet, and sending feedback information of agreeing to the second vehicle joining the fleet to the cloud.

[0107] The device also includes a fleet management module for receiving a user's closing and joining application instruction, and when receiving a request from the cloud for a second vehicle to join the fleet, sending feedback information of closing the joining of the fleet to the cloud; and receiving a user's disbanding fleet instruction, and disbanding the fleet according to the disbanding fleet instruction.

[0108] The action allocation module of the device is specifically used to allocate each scenario service included in the service combination to the first vehicle and / or the second vehicle in the fleet according to the user's action allocation instruction for the service combination.

[0109] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and modules can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0110] In addition, the functions in the various embodiments of the present application may be integrated into a single processing module, or each module may exist physically separately, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or software functional modules.

[0111] 9, which shows a block diagram of a computer-readable storage medium according to an embodiment of the present application. The computer-readable storage medium 900 stores program code, which can be called by a processor to execute the method described in the above method embodiment.

[0112] The computer-readable storage medium 900 can be an electronic memory such as a flash memory, an EEPROM (Electrically Erasable Programmable Read-Only Memory), an EPROM, a hard disk, or a ROM. Alternatively, the computer-readable storage medium 900 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 900 has storage space for program code 910 for executing any of the method steps described above. These program codes can be read from or written to one or more computer program products. The program code 910 can be compressed, for example, in a suitable form.

[0113] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements 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 the present application.

Claims

1. A multi-vehicle linkage method based on scenario service orchestration, characterized in that: The method comprises: receiving an action allocation synchronization instruction sent by a first user, wherein the action allocation synchronization instruction is used to synchronize a service combination obtained by arranging scene services by the first user and fleet information for executing the service combination; Generate a scenario file according to the action allocation synchronization instruction, wherein the scenario file is used to indicate a plurality of scenario service information included in the service combination and vehicle information for executing each of the scenario services; An execution instruction is sent to a vehicle executing the scenario service according to the scenario file, and the execution instruction is used to instruct the vehicle to execute the scenario service.

2. The multi-vehicle linkage method according to claim 1, characterized in that: The method further comprises: In response to a request sent by a second user to join the fleet, authenticating a second vehicle associated with the second user; After the identity verification is passed, sending a request for the second vehicle associated with the second user to join the fleet to the first user; In response to feedback information that the first user agrees that the second vehicle associated with the second user joins the fleet, the second vehicle associated with the second user is added to the fleet.

3. The multi-vehicle linkage method according to claim 1, characterized in that: The step of generating a scene file according to the action allocation synchronization instruction comprises: Parse the action allocation synchronization instruction to obtain multiple scene service information and vehicle information for executing each scene service, The scenario file is generated according to the plurality of scenario service information and the vehicle information.

4. The multi-vehicle linkage method according to claim 1, characterized in that: The sending of the execution instruction to the vehicle executing the scenario service according to the scenario file includes: Sending a first execution instruction to a vehicle executing the first scene service according to the first scene service information among the plurality of scene service information; Receive the feedback result of the vehicle executing the first scenario service after executing the first scenario service, and issue a second execution instruction to the vehicle executing the second scenario service according to the second scenario service information in the multiple scenario service information, until all the multiple scenario services are executed, wherein the execution timing of the first scenario service is earlier than the execution timing of the second scenario service.

5. The multi-vehicle linkage method according to claim 4, characterized in that: The method further comprises: Receive a command to start running a scene sent by the first user, Performing time base calibration on the vehicles in the fleet according to the start-up operation scenario instruction; After each preset time interval, the time base of the vehicles in the fleet is calibrated again.

6. The multi-vehicle linkage method according to claim 1, characterized in that: Before receiving the action allocation synchronization instruction sent by the first user, the method includes: Receiving a scene synchronization instruction sent by a first user, where the scene synchronization instruction is used to synchronize a service combination obtained by arranging scene services by the first user; Generate a first scene file according to the scene synchronization instruction, the first scene file is used to indicate that the service combination includes Multiple scene service information; The step of generating a scene file according to the action allocation synchronization instruction comprises: Parsing the action allocation synchronization instruction to obtain vehicle information for executing each scenario service; A scenario file is generated according to the first scenario file and the vehicle information.

7. A multi-vehicle linkage method based on scene service orchestration, characterized in that: The method comprises: Receive a scene service arrangement instruction from a user, arrange the scene service according to the scene service arrangement instruction, and obtain service combination information after the scene service arrangement; Receive the user's action allocation instruction for the scene, allocate multiple scene services included in the service combination to vehicles in the fleet according to the action allocation instruction, and send an action allocation synchronization instruction to the cloud, so that the cloud generates a scene file according to the action allocation synchronization instruction, and sends the execution instruction to the vehicles in the fleet according to the scene file to realize the scheduling of multi-vehicle linkage. The action allocation synchronization instruction is used to synchronize the service combination and the fleet information that executes the service combination.

8. The multi-vehicle linkage method according to claim 7, characterized in that: After sending the scene synchronization command to the cloud, it includes: Receive the user's selection instruction for the scene application vehicle, A vehicle fleet for applying the scenario is established according to the selection instruction, wherein the vehicle fleet includes at least a first vehicle associated with a first user.

9. The multi-vehicle linkage method according to claim 8, characterized in that: After establishing a fleet that applies the described scenario, it includes: Receive the user's invitation to join the fleet instruction, generate an invitation QR code or invitation link, and send it to the second user terminal.

10. The multi-vehicle linkage method according to claim 9, characterized in that: The method further comprises: receiving a request from a cloud for a second vehicle to join the fleet, where the second vehicle is a vehicle associated with a second user; An instruction from a user agreeing that the second vehicle joins the fleet is received, and feedback information of agreeing that the second vehicle joins the fleet is sent to the cloud.

11. The multi-vehicle linkage method according to claim 8, characterized in that: The method further comprises: Receive the user's instruction to close the joining application, When a request for a second vehicle to join the fleet sent by the cloud is received, feedback information of closing the joining of the fleet is sent to the cloud.

12. The multi-vehicle linkage method according to claim 10, characterized in that: The allocating the multiple scenario services included in the service combination to vehicles in the fleet according to the action allocation instruction includes: According to the user's action allocation instruction for the service combination, each scenario service included in the service combination is allocated to the first vehicle and / or the second vehicle in the fleet.

13. The multi-vehicle linkage method according to claim 10, characterized in that: The method further comprises: Receive a fleet disbanding instruction from a user, and disband the fleet according to the fleet disbanding instruction.

14. A multi-vehicle linkage device based on scene service arrangement, characterized in that: The device comprises: An instruction receiving module, used to receive an action allocation synchronization instruction sent by a first user, wherein the action allocation synchronization instruction is used to synchronize a service combination obtained by arranging scene services by the first user and fleet information for executing the service combination; A scene file generation module is used to generate a scene file according to the action allocation synchronization instruction, and the scene file is used to indicate indicating information of multiple scene services included in the service combination and information of vehicles executing each of the scene services; The scheduling module is used to send an execution instruction to a vehicle that executes the scenario service according to the scenario file, and the execution instruction is used to instruct the vehicle to execute the scenario service.

15. A multi-vehicle linkage device based on scene service arrangement, characterized in that: The device comprises: A scene service arrangement module is used to receive a scene service arrangement instruction from a user, arrange the scene service according to the scene service arrangement instruction, and obtain service combination information after the scene service arrangement; An action allocation module is used to receive a user's action allocation instruction for the scene, allocate multiple scene services included in the service combination to vehicles in the fleet according to the action allocation instruction, and send an action allocation synchronization instruction to the cloud, so that the cloud generates a scene file according to the action allocation synchronization instruction, and sends an execution instruction to the vehicles in the fleet according to the scene file to realize the scheduling of multiple vehicles in linkage. The action allocation synchronization instruction is used to synchronize the service combination and the fleet information that executes the service combination.

16. A multi-vehicle linkage system based on scene service arrangement, characterized in that: The system includes a first user terminal, a vehicle associated with the first user terminal, and a cloud; The first user terminal is used to receive a scene service arrangement instruction from a user, arrange the scene service according to the scene service arrangement instruction, and obtain service combination information after the scene service arrangement; Receive an action allocation instruction from a user for the scenario, and allocate multiple scenario services included in the service combination to vehicles in a fleet according to the action allocation instruction, wherein the fleet at least includes a vehicle associated with the first user terminal; send an action allocation synchronization instruction to the cloud, wherein the action allocation synchronization instruction is used to synchronize the service combination obtained based on the user's arrangement of the scenario services and the fleet information that executes the service combination; The cloud is used to receive the action allocation synchronization instruction sent by the first user terminal, and generate a scenario file according to the action allocation synchronization instruction, wherein the scenario file is used to indicate a plurality of scenario service information included in the service combination and vehicle information for executing each of the scenario services; An execution instruction is sent to a vehicle executing the scenario service according to the scenario file, and the execution instruction is used to instruct the vehicle to execute the scenario service.

17. A computer device, characterized in that: The computer device comprises: one or more processors; Memory; One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute the method according to any one of claims 1-6 or claims 7-13.

18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a program code executable by a processor, and when the program code is executed by the processor, the processor executes the method according to any one of claims 1 to 6 or claims 7 to 13.

Images