Service orchestration execution engine service dynamic invocation method

Abstract

The application discloses a service arrangement execution engine service dynamic calling method, which comprises the following steps: service definition and bridge configuration; defining vehicle service and configuring service bridge for the service; maintaining vehicle type service set, selecting the service set required to be configured on each vehicle type from the defined service; distributing service instruction mapping relationship table, obtaining the service instruction mapping relationship table of the vehicle type according to the service set required to be configured on each vehicle type, and distributing the service instruction mapping relationship table to the execution end where the service arrangement execution engine is located; and dynamically analyzing the instruction and calling the service, wherein the service arrangement execution engine analyzes the service instruction mapping relationship when executing the service, converts the service into corresponding service instruction according to the mapping relationship, and sends the service instruction to the configured bridge; and the bridge uses the instruction calling logic to call the service. The service arrangement execution engine has strong adaptability through the service mapping table and the integrated bridge.

Description

Technical Field

[0001] This invention belongs to the field of vehicle network service processing technology, specifically relating to a method for dynamic service invocation of a service orchestration execution engine. Background Technology

[0002] In recent years, the concept of servitization has gained increasing attention in the automotive industry, with vehicles providing various capabilities to users through combinations of services. Generally speaking, service orchestration refers to combining individual servitized services according to a specific logic or process to customize new vehicle services. The result of service orchestration is a description of the logic or process, which needs to be parsed and processed by a corresponding service orchestration execution engine.

[0003] When service orchestration is applied to the automotive field, especially when the service orchestration execution engine runs on the vehicle side, the diversity of vehicle models and the different ways they provide services can lead to the service orchestration execution engine not being able to adapt to all vehicle models. Summary of the Invention

[0004] The main objective of this invention is to overcome the shortcomings and deficiencies of the prior art and to propose a method for dynamic service invocation in a service orchestration execution engine.

[0005] To achieve the above objectives, the present invention adopts the following technical solution:

[0006] A method for dynamically invoking services in a service orchestration execution engine includes:

[0007] Service definition and its bridge configuration; define vehicle services and configure bridges for services;

[0008] Maintain the vehicle model and series service set, and select the set of services that need to be configured for each vehicle model and series from the predefined services;

[0009] Service instruction mapping table distribution: Based on the service set that needs to be configured on each vehicle model, the service instruction mapping table for each vehicle model is obtained, and the service instruction mapping table is distributed to the execution end where the service orchestration execution engine is located.

[0010] Dynamic command parsing and service invocation: When executing a service, the service orchestration and execution engine parses the service command mapping relationship, converts the service into the corresponding service command based on the mapping relationship, and sends it to the configured bridge. The bridge uses the command invocation logic to make service invocations.

[0011] Furthermore, a bridge is specifically a processor in the service orchestration execution engine that is configured for different calling methods when executing service calls, in order to adapt to different communication protocols or different service calling scenarios; each bridge needs to maintain the mapping relationship between services and actual instructions.

[0012] Furthermore, the mapping relationship between services and actual instructions is specifically the mapping relationship between services and actual project code.

[0013] Furthermore, a service can be configured with one or more bridges;

[0014] When configuring a bridge, you need to define the bridge's name, code, applicable protocol, applicable platform, and activation method.

[0015] Furthermore, the applicable protocol definitions for the bridge include, but are not limited to, FASTDD, RTIDDS, AUTOCOREDDS, FDBUS, HTTP, CAN, and DUBBO.

[0016] Furthermore, the applicable platform definition includes, but is not limited to, cloud-based EDC, vehicle-based VIU, and vehicle-mounted Android systems.

[0017] Furthermore, the definition of the activation method includes fast start and non-fast start. Fast start means that when the service orchestration execution engine is deployed on the vehicle, it can run before the vehicle is powered on, that is, it is in a runnable state before the vehicle is powered on. Non-fast start means that the service orchestration execution engine can only run after the vehicle is powered on.

[0018] Furthermore, when maintaining a set of vehicle model services, if a certain service for a particular vehicle model is configured with multiple bridges, it is necessary to determine which bridge is used for that vehicle model.

[0019] Furthermore, the execution end of the service orchestration execution engine is the vehicle's infotainment system, autonomous driving domain controller, or the cloud.

[0020] Furthermore, when the service instruction mapping table for a vehicle model or series changes, a change notification is sent to the execution end. After receiving the notification, the execution end synchronizes the mapping table. After obtaining the latest service instruction mapping table, the execution end needs to update the service instruction mapping relationships already loaded in memory, and at the same time update the locally persisted service instruction mapping relationship library.

[0021] Compared with the prior art, the present invention has the following advantages and beneficial effects:

[0022] 1. This invention decouples services and their actual instructions by setting up a bridge to adapt to the service when defining the service, and then maintaining the mapping relationship between the service and the actual instructions in different bridges. This distinguishes between user language and engineering language, making it easier for users or administrators to understand the service content and thus enabling more efficient service orchestration. By constructing a service set for vehicle models and series, a service instruction mapping table for vehicle models and series is obtained. Vehicles obtain the service instruction mapping table according to their vehicle model and series. Since the service orchestration execution engine has integrated the instruction call processing methods corresponding to various bridges, the service orchestration can be converted into corresponding service instructions according to the mapping table, realizing dynamic service invocation. Through the service mapping table and integrated bridges, the service orchestration execution engine has strong adaptability and can adapt to almost all vehicle models and series and even all service invocation scenarios. Attached Figure Description

[0023] Figure 1 This is an overall flowchart of the method of the present invention;

[0024] Figure 2 This is a flowchart of the service instruction mapping table distribution process;

[0025] Figure 3 It is a flowchart of dynamic instruction parsing and service call. Detailed Implementation

[0026] The present invention will be further described in detail below with reference to the embodiments and accompanying drawings, but the embodiments of the present invention are not limited thereto.

[0027] Example

[0028] like Figure 1 As shown, the present invention provides a method for dynamic service invocation in a service orchestration execution engine, comprising:

[0029] Service definition and its bridge configuration;

[0030] Service definitions are used to abstract away engineering descriptions and describe the provided functions and their parameters in a way that is easy for users to understand. For example, defining an ambient light service allows you to specify the parameters as color and flashing frequency. There are 64 colors to choose from, and the flashing frequency can be selected from 1 to 100 times per minute.

[0031] After defining the service, you need to set up a suitable service bridge for the service. The service can use one or more bridges.

[0032] The service bridge is actually a processor in the service orchestration execution engine that is set up for different calling methods when executing service calls, in order to adapt to different communication protocols or different service calling scenarios.

[0033] When defining a bridge, you need to define the bridge's name, encoding, applicable protocol, applicable platform, and activation method.

[0034] The bridge code uniquely identifies the bridge type, and different service call processing methods will be used by the service orchestration execution engine for different bridge codes.

[0035] The applicable protocol definitions for the bridge include, but are not limited to, FASTDD, RTIDDS, AUTOCOREDDS, FDBUS, HTTP, CAN, and DUBBO. Different protocols will result in different service call processing methods.

[0036] The platform definition for the bridge refers to the platform on which the bridge is suitable to run, such as cloud, vehicle EDC, vehicle VIU, or in-vehicle Android system. The service orchestration execution engine will execute different logic depending on the running platform. For example, if the running platform is set to vehicle VIU, the service orchestration execution engine will convert the service orchestration script into a binary protocol according to the service mapping table, which will then be used by the VIU to execute the orchestration script. At the same time, the platform will also set the protocol conversion rules for the script when maintaining the service mapping table.

[0037] The activation methods are divided into fast start and non-fast start. Fast start refers to the execution engine being able to operate before the vehicle is powered on, meaning it is operational even before the vehicle is powered on. Conversely, non-fast start requires the execution engine to be operational after the vehicle is powered on.

[0038] Each type of bridge needs to maintain a mapping between services and actual commands.

[0039] Maintaining the mapping relationship between services and actual commands refers to associating services with actual project code descriptions, as shown in Table 1 below. This table shows which specific project command a service corresponds to, and which specific project command parameter a service parameter corresponds to. For example, in the DDS bridge, the project command corresponding to the "openAtmoLight" service is "openAtmoLight," and the project command corresponding to the color parameter is "color." To facilitate user understanding and operation, some parameters in the project command parameters may not be user-configurable. In this case, default values ​​can be set for the project command parameters when establishing the mapping relationship. These default values ​​mean that when the service is called, even if the user does not set a value for the parameter, a default available value will be used, exhibiting consistent behavior without affecting the functional results.

[0040]

[0041] Table 1

[0042] A collection of maintenance services for various vehicle models and series;

[0043] Once the services are defined, not all services are suitable for a particular car model or series, so each car model or series needs to be equipped with specific services.

[0044] The configured services refer to selecting existing services from the predefined services available for that vehicle model. When a service is configured with multiple bridges, it's necessary to determine which bridge to use for that particular vehicle model. This is because a service within the same vehicle model typically only has one invocation method; even if multiple invocation methods are supported, a specific bridge needs to be determined for the execution engine to differentiate between them. Once the set of services configured for the vehicle model is complete, a service instruction mapping table for that vehicle model is obtained.

[0045] Service instruction mapping table distribution; specifically:

[0046] Having obtained the service instruction mapping table for vehicle models and series, it needs to be distributed to the execution end where the service orchestration execution engine resides.

[0047] The execution end where the service orchestration execution engine is located can be the vehicle's infotainment system, autonomous driving domain controller, or the cloud.

[0048] like Figure 2 As shown, when the service instruction mapping table for a vehicle model / series changes—for example, when an administrator adds services to that model / series, or modifies or deletes existing services because they are no longer suitable—a change notification is sent to the execution end. Upon receiving the notification, the execution end synchronizes the mapping table. After obtaining the latest service instruction mapping table, the execution end first needs to update the service instruction mappings already loaded in memory for immediate effect. Simultaneously, it updates the locally persisted service instruction mapping database so that the latest service instruction mappings will be used the next time the service orchestration execution engine starts on that end.

[0049] Dynamic command parsing and service invocation, specifically:

[0050] When the service orchestration execution engine executes a service in the service orchestration, it uses the service to look up the mapping relationship in the service instruction mapping relationship table of vehicle models and series, and then converts the service into the corresponding service instruction according to the mapping relationship and sends it to the corresponding bridge. The bridge then uses the default corresponding instruction invocation logic to make the service call.

[0051] like Figure 3As shown, the service orchestration execution engine traverses the service orchestration script to execute services. When executing a service in the service orchestration, it uses the service to look up the mapping relationship used in the service instruction mapping relationship table of vehicle models and series. Then, based on the mapping relationship, it converts the service into the corresponding service instruction and sends it to the corresponding bridge. The bridge then uses the default pre-written corresponding instruction calling logic to make the service call.

[0052] It should also be noted that, in this specification, terms such as "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0053] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for dynamically invoking services in a service orchestration execution engine, characterized in that, include: Service definition and its bridge configuration; define vehicle services and configure bridges for services; Maintain the vehicle model and series service set, and select the set of services that need to be configured for each vehicle model and series from the predefined services; Service instruction mapping table distribution: Based on the service set that needs to be configured on each vehicle model, the service instruction mapping table for each vehicle model is obtained, and the service instruction mapping table is distributed to the execution end where the service orchestration execution engine is located. Dynamic command parsing and service invocation: When executing a service, the service orchestration and execution engine parses the service command mapping relationship, converts the service into the corresponding service command based on the mapping relationship, and sends it to the configured bridge. The bridge uses the command invocation logic to make service invocations.

2. The method for dynamic service invocation in a service orchestration execution engine according to claim 1, characterized in that, A bridge is a processor in the service orchestration and execution engine that is configured for different calling methods when executing service calls, in order to adapt to different communication protocols or different service calling scenarios; each bridge needs to maintain the mapping relationship between services and actual instructions.

3. The method for dynamic service invocation in a service orchestration execution engine according to claim 2, characterized in that, The mapping relationship between services and actual instructions is specifically the mapping relationship between services and actual project code.

4. The method for dynamic service invocation in a service orchestration execution engine according to claim 1, characterized in that, A service can be configured with one or more bridges; When configuring a bridge, you need to define the bridge's name, code, applicable protocol, applicable platform, and activation method.

5. The method for dynamic service invocation in a service orchestration execution engine according to claim 4, characterized in that, The applicable protocol definitions for the bridge include, but are not limited to, FASTDD, RTIDDS, AUTOCOREDDS, FDBUS, HTTP, CAN, and DUBBO.

6. The method for dynamic service invocation in a service orchestration execution engine according to claim 4, characterized in that, Applicable platforms are defined as including, but not limited to, cloud-based EDC, vehicle-based VIU, and vehicle-mounted Android systems.

7. The method for dynamic service invocation in a service orchestration execution engine according to claim 4, characterized in that, The definition of the activation method includes fast start and non-fast start. Fast start means that when the service orchestration execution engine is deployed on the vehicle, it can run before the vehicle is powered on, that is, it is in a runnable state before the vehicle is powered on. Non-fast start means that the service orchestration execution engine can only run after the vehicle is powered on.

8. The method for dynamic service invocation in a service orchestration execution engine according to claim 1, characterized in that, When maintaining a set of vehicle model services, if a certain service of a vehicle model is configured with multiple bridges, it is necessary to determine which bridge is used for that vehicle model.

9. The method for dynamic service invocation in a service orchestration execution engine according to claim 1, characterized in that, The service orchestration execution engine is located at the vehicle's infotainment system, autonomous driving domain controller, or cloud platform.

10. The method for dynamic service invocation in a service orchestration execution engine according to claim 1, characterized in that, When the service instruction mapping table for a vehicle model changes, a change notification is sent to the execution end. After receiving the notification, the execution end synchronizes the mapping table. After obtaining the latest service instruction mapping table, the execution end needs to update the service instruction mapping relationships already loaded in memory, and at the same time update the locally persisted service instruction mapping relationship library.

Images