CN115190179A

CN115190179A - Vehicle and resource scheduling method thereof

Info

Publication number: CN115190179A
Application number: CN202110359885.4A
Authority: CN
Inventors: 李添泽; 黎金科; 郑益红
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-04-02
Filing date: 2021-04-02
Publication date: 2022-10-14
Anticipated expiration: 2041-04-02
Also published as: WO2022206327A1

Abstract

The vehicle comprises a service demander, a service provider and a network controller, wherein the service demander can send a service request message to the service provider, the service provider receives the service request message and can generate a resource scheduling request message according to the service request message, the service provider sends the resource scheduling request message to the network controller, the network controller determines the service quality for the first service according to the resource scheduling request message and generates a configuration file according to global network topology information for indicating the connection relationship among a plurality of electronic control units in the vehicle, allocated communication resources and the service quality for the first service, the configuration file is used for indicating a resource allocation strategy, and the resource allocation strategy is used for realizing that the service provider provides the first service to the service demander. The resource scheduling method provided by the application realizes the service quality guarantee of the global service flow of the vehicle.

Description

Vehicle and resource scheduling method thereof

Technical Field

The application relates to the technical field of intelligent driving, in particular to a vehicle and a resource scheduling method thereof.

Background

The trend of new vehicles and Software Defined Vehicles (SDV) is driving the continuous evolution of Electronic Electrical Architecture (EEA) of vehicles, which gradually transits from the traditional distributed electronic electrical architecture to the domain controller architecture and then to the electronic electrical architecture based on central computing with the increase of integration level. By combining the requirement of high integration of a new-generation electronic and electrical Architecture of an automobile, a Service-Oriented Architecture (SOA) is applied to realize quick iteration and flexible recombination of business functions, and new functional requirements of a user can be quickly responded based on a standardized interface. Under the service-oriented architecture, the functions provided by each controller are disassembled according to the service dimension, and the resource acquisition of the whole vehicle capability can be fully realized. With the rapid development of technologies such as intelligent driving, internet of vehicles and the like, the functions of automobiles are continuously enriched, and the arrangement of SOA architecture on the automobiles inevitably brings more problems to the scheduling of the service resources of the whole automobiles, for example, the requirements on large flow, high concurrency, real-time performance and reliability are higher; the service mode is changeable, and the periodic service and the non-periodic mutation service coexist; the Quality of Service (QoS) of a global Service flow is difficult to guarantee by traditional distributed resource allocation.

Content of application

The embodiment of the application provides a vehicle and a resource scheduling method thereof, and service quality guarantee of a global service flow of the vehicle is realized.

In a first aspect, the present application provides a vehicle comprising a service demander, a service provider and a network controller; the service demander is used for sending a service request message to the service provider, and the service request message is used for requesting the service provider to subscribe to a first service or call the first service; the service provider is configured to: receiving the service request message; generating a resource scheduling request message according to the service request message, wherein the resource scheduling request message is used for indicating that the service demander requests the first service from the service provider and indicating the requested service quality, and the requested service quality is the service quality which is requested by the service provider to the network controller and is related to the first service; and sending the resource scheduling request message to the network controller; wherein the service provider is used for providing in-vehicle services, or acting on out-vehicle services, or both providing in-vehicle services and acting on out-vehicle services; the network controller is to: receiving the resource scheduling request message; determining a quality of service for the first service according to the resource scheduling request message; generating a configuration file according to global network topology information used for indicating connection relations among a plurality of electronic control units in the vehicle, the allocated communication resources and the service quality used for the first service, wherein the configuration file is used for indicating resource allocation strategies, and the resource allocation strategies are used for realizing that the service provider provides the first service to the service demander; and sending the configuration file to at least part of the electronic control units in the plurality of electronic control units, wherein the at least part of the electronic control units are electronic control units for realizing that the service provider provides the first service to the service demander.

According to the vehicle, the newly-added network controller serves as a unified node to conduct resource scheduling of the global network topology, so that the global optimal data transmission efficiency is obtained, and the problem that service quality cannot be guaranteed globally due to local resource scheduling of each electronic control unit in the related technology is solved.

In one possible implementation, the network controller is configured to generate a configuration file according to global network topology information indicating connection relationships among a plurality of electronic control units in the vehicle, the communication resources that have been allocated, and the quality of service for the first service, and the network controller is configured to: determining a communication path between the service demander and the service provider according to the global network topology information used for indicating the connection relationship among the electronic control units in the vehicle, the allocated communication resources and the service quality used for the first service; wherein the at least part of the electronic control unit is located on the communication path; generating a profile based on the communication path and the quality of service for the first service.

In one possible implementation, the quality of service for the first service is determined by a negotiation process between the network controller and the service provider.

According to the vehicle, the service quality of the first service is determined through negotiation between the network controller and the service provider, on one hand, service resources of the whole vehicle can be reasonably scheduled through a negotiation mechanism, the purpose of meeting the service quality of the first service as far as possible is achieved, on the other hand, the rationality of whole vehicle global communication resource allocation is optimized, and the resource allocation based on the whole vehicle is more flexible.

In another possible implementation, the network controller is configured to determine a quality of service for the first service based on the resource scheduling request message, and includes the network controller configured to: determining that a quality of service of the request cannot be satisfied; sending a negotiation request message to the service provider, wherein the negotiation request message is used for indicating the service quality suggested by the network controller to the service provider; receiving a negotiation response message from the service provider, the negotiation response message for indicating that the service provider accepts the proposed quality of service; and determining the proposed quality of service as the quality of service for the first service.

In another possible implementation, the service provider is configured to proxy an off-board service, the first service is the off-board service, the off-board service is configured to provide a service external to the vehicle, and the allocated communication resources include resources for in-vehicle communication and resources for off-board communication.

The vehicle of the embodiment of the application optimizes the mapping relation of the service provider and the service demander in the whole in-vehicle and out-of-vehicle network topology through a cross-platform service quality guarantee mechanism based on in-vehicle and out-of-vehicle combined network topology control, so that end-to-end resource scheduling is performed based on network global information, and the service quality of the first service is further guaranteed.

In another possible implementation, prior to receiving the service request message, the service provider is further configured to: broadcasting services that the service provider is capable of providing to the plurality of electronic control units.

In one example, the service request message includes identification information of the first service, and the service provider is further configured to determine the requested quality of service according to the identification information and a preset quality of service configuration rule.

In another possible implementation, the network controller, the service provider, and the service demander are electronic control units within the vehicle.

In a second aspect, the present application provides a resource scheduling method applied to a network controller in a vehicle, the method including: the network controller receives a resource scheduling request message from a service provider in the vehicle, the resource scheduling request message being used for indicating that a service demander in the vehicle requests a first service from the service provider and also indicating a requested service quality, the requested service quality being a service quality which the service provider requests from the network controller about the first service; wherein the service provider is used for providing in-vehicle services, or acting on out-vehicle services, or both providing in-vehicle services and acting on out-vehicle services; the network controller determines the service quality for the first service according to the resource scheduling request message; the network controller generates a configuration file according to global network topology information used for indicating connection relations among electronic control units in the vehicle, the allocated communication resources and the service quality used for the first service, wherein the configuration file is used for indicating resource allocation strategies, and the resource allocation strategies are used for realizing that the service providers provide the first service to the service demanders; the network controller sends the configuration file to at least one electronic control unit in the vehicle, the at least one electronic control unit being an electronic control unit for enabling the service provider to provide the first service to the service demander.

According to the resource scheduling method, the network controller is used as the unified node to perform resource scheduling of the global network topology, so that the globally optimal data transmission efficiency is obtained, and the problem that the service quality cannot be globally guaranteed due to local resource scheduling of each electronic control unit in the related art is solved.

In another possible implementation, the network controller generates a profile according to global network topology information indicating a connection relationship between the in-vehicle electronic control units, the communication resources that have been allocated, and the quality of service for the first service, including: the network controller determines a communication path between the service demander and the service provider according to the global network topology information used for indicating the connection relationship among the electronic control units in the vehicle, the allocated communication resources and the service quality used for the first service; wherein the at least part of the electronic control unit is located on the communication path; generating a profile based on the communication path and the quality of service for the first service.

In another possible implementation, the quality of service for the first service is determined by a negotiation process between the network controller and the service provider.

According to the resource scheduling method, the service quality of the first service is determined through negotiation between the network controller and the service provider, on one hand, service resources of the whole vehicle can be scheduled more reasonably through a negotiation mechanism, the purpose of meeting the service quality of the first service as far as possible is achieved, on the other hand, the rationality of whole vehicle global communication resource allocation is optimized, and the resource allocation based on the whole vehicle is more flexible.

In another possible implementation, the network controller determining a quality of service for the first service according to the resource scheduling request message includes: the network controller determining that a quality of service of the request cannot be satisfied; the network controller sends a negotiation request message to the service provider, wherein the negotiation request message is used for indicating the service quality suggested by the network controller to the service provider; the network controller receiving a negotiation response message from the service provider, the negotiation response message for indicating that the service provider accepts the proposed quality of service; the network controller determines the proposed quality of service to be the quality of service for the first service.

In another possible implementation, the service provider is an electronic control unit for brokering an off-board service, the first service is the off-board service, the off-board service is for providing a service outside the vehicle to the vehicle, and the allocated communication resources include resources for in-vehicle communication and resources for off-board communication.

According to the resource scheduling method, the mapping relation of the service provider and the service demander in the whole in-vehicle and out-of-vehicle network topology is optimized through a cross-platform service quality guarantee mechanism based on in-vehicle and out-of-vehicle combined network topology control, so that end-to-end resource scheduling is performed based on network global information, and the service quality of the first service is further guaranteed.

In a third aspect, the present application also provides a network controller for a vehicle, comprising: a communication module for receiving a resource scheduling request message from a service provider in the vehicle, the resource scheduling request message being indicative of a first service requested by a service demander in the vehicle from the service provider and also indicative of a requested quality of service, the requested quality of service being a quality of service requested by the service provider from the network controller in relation to the first service; a service quality determining module, configured to determine a service quality for the first service according to the resource scheduling request message; a configuration file generation module, configured to generate a configuration file according to global network topology information indicating a connection relationship between electronic control units in the vehicle, allocated communication resources, and the quality of service for the first service, where the configuration file is used to indicate a resource allocation policy, and the resource allocation policy is used to enable the service provider to provide the first service to the service demander; the communication module is further configured to send the configuration file to at least one electronic control unit in the vehicle, where the at least one electronic control unit is an electronic control unit configured to enable the service provider to provide the first service to the service demander.

In one possible implementation, the profile generation module is configured to generate a profile according to global network topology information indicating connection relationships among a plurality of electronic control units in the vehicle, the communication resources that have been allocated, and the quality of service for the first service, and includes the profile generation module configured to: determining a communication path between the service demander and the service provider according to the global network topology information for indicating the connection relationship among the electronic control units in the vehicle, the allocated communication resources and the service quality for the first service; wherein the at least part of the electronic control unit is located on the communication path; generating a configuration file according to the communication path and the service quality for the first service.

In another possible implementation, the quality of service determination module is further configured to determine that the requested quality of service cannot be satisfied; the communication module is further configured to send a negotiation request message to the service provider, and receive a negotiation response message from the service provider, where the negotiation request message is used to indicate a proposed quality of service for the service provider by the network controller, and the negotiation response message is used to indicate that the service provider accepts the proposed quality of service; the quality of service determination module is further configured to determine the proposed quality of service as the quality of service for the first service.

In a fourth aspect, the present application further provides a network controller for a vehicle, comprising a memory storing computer program instructions and a processor executing the computer program instructions to implement the method of the second aspect.

In a fifth aspect, the present application also provides a computer readable storage medium comprising computer instructions which, when executed by a processor, cause the method of the second aspect to be carried out.

In a sixth aspect, the present application also provides a computer program product enabling the method of the second aspect to be implemented when the computer program product is run on a processor.

In a seventh aspect, the present application further provides a chip, which includes a memory and a processor, where the memory stores computer program instructions, and the processor executes the computer program instructions to implement the method of the second aspect.

Drawings

Fig. 1 is a schematic diagram of an architecture of an SOA in the related art;

fig. 2 is a schematic structural diagram of an SOA according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of an SOA according to an embodiment of the present application;

fig. 4 is a flowchart of a resource scheduling method according to an embodiment of the present application;

FIG. 5 is a global network topology diagram of a vehicle ECU;

fig. 6 is an architecture diagram of a QoS negotiation mechanism according to an embodiment of the present application;

FIG. 7 is a flow chart of another resource scheduling method provided in the present application;

fig. 8 is an architecture diagram of a cross-platform service QoS guarantee mechanism according to an embodiment of the present application;

FIG. 9 is a schematic structural diagram of a network controller applied to a vehicle according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a chip according to an embodiment of the present application.

Detailed Description

The technical solution of the present application is further described in detail by the accompanying drawings and examples.

Fig. 1 is a schematic diagram of an architecture of an SOA in the related art. The EE architecture of the vehicle in the related art employs the SOA shown in fig. 1, which includes an application layer, middleware, and a hardware layer, as shown in fig. 1. The service calling process comprises the following steps: based on the communication protocol of the middleware (such as the ethernet SOME/IP protocol), the service provider publishes the available service, then the service demander needing the service subscribes/invokes the service, and finally the service flow is generated, and each ECU performs distributed communication resource scheduling, caching and transmission based on the self condition. In this architecture, each ECU guarantees QoS of a service by local communication resource scheduling, which is a QoS guarantee mechanism for distributed resource allocation.

The QoS guarantee mechanism of distributed resource allocation can only guarantee the QoS of local service flows, and when the requirements of large flow, multiple services, high concurrency, instantaneity and reliability are gradually improved, the QoS of global services is difficult to guarantee by the distributed resource allocation.

In order to solve the above problem, an embodiment of the present application provides a resource scheduling method, where in a platform architecture based on an SOA, a network control layer (see fig. 2) is added between a hardware layer and a middleware layer, and the network control layer generates a scheduling policy based on global network topology information and allocated communication resources, so as to guarantee QoS of a global service flow.

Fig. 3 is a schematic diagram of an SOA architecture according to an embodiment of the present application. The SOA comprises an application layer, a vehicle-mounted OS layer, a network control layer and a hardware layer. The network control layer can be understood as a uniform service control plane, and service management and control are carried out on the whole network through the uniform service control plane.

The network control layer can be implemented by a network controller deployed in a certain ECU of the vehicle and is responsible for calculation, decision and configuration of global network resources of the electronic and electrical architecture of the whole vehicle. The network controller at least comprises the following modules: the system comprises a communication module, a service quality determining module and a configuration file generating module. The communication module is used for receiving a resource scheduling request message from a service provider in the vehicle, wherein the resource scheduling request message is used for indicating that a service demander in the vehicle requests service from the service provider and indicating requested service quality, and the requested service quality is the service quality which is requested by the service provider from the network controller and is related to the service. The service quality determining module is used for determining the service quality used for the service according to the resource scheduling request message. The configuration file generating module is used for generating a configuration file according to global network topology information used for indicating connection relation among Electronic Control Units (ECUs) in the vehicle, the distributed communication resources and service quality used for the service, wherein the configuration file is used for indicating resource distribution strategies used for realizing service provided by a service provider to a service demander. The communication module is further configured to send the configuration file to at least one ECU within the vehicle, the at least one ECU being an ECU for enabling the service provider to provide the service to the service demander.

And the ECU receiving the configuration file performs routing forwarding and scheduling of service resources according to the configuration file so as to realize that the service provider provides service for the service demander.

The service provider, the service demander, and the network controller may be implemented by an in-Vehicle ECU such as an MDC (Mobile Data Center), a CDC (Continuous Damping Control), a TBOX (Telematics Box), a VCU (Vehicle Control Unit), and the like, which are deployed in a Vehicle. The service provider is an ECU providing services, and the service demander is an ECU requiring services, and hereinafter, for convenience of description, the service provider is referred to as a service-side ECU, and the service demander is referred to as a client-side ECU.

Fig. 4 is a flowchart of a resource scheduling method according to an embodiment of the present application. The method can be applied to the architecture shown in fig. 3. As shown in fig. 4, the method comprises at least steps S401-S404.

In step S401, the server ECU transmits a resource scheduling request message for service to the network controller.

It can be understood that the service mentioned in the embodiment refers to abstraction of various functions of the vehicle based on the SOA architecture, such as window control service, seat control service, center control screen service, advanced Driving Assistance System (ADAS) service, brake service, and the like.

In the embodiment of the application, the service-side ECU is an ECU capable of providing services. The network controller can realize the functions of the network control layer in fig. 3, is deployed in a certain ECU in the vehicle, and is responsible for the calculation, decision-making and configuration of the global network resources of the electronic and electrical architecture of the entire vehicle.

The resource scheduling request message for the service is determined based on the client ECU sending a subscription request message/invocation request message to the server ECU. For example, a service-side ECU of a vehicle broadcasts service information that it can provide, and a client-side ECU that needs the service sends subscription request information to the service-side ECU to subscribe to the service. Or the service-side ECU of the vehicle broadcasts the service information which can be provided by the vehicle, and the client ECU using the service initiates a request for calling the service to the service-side ECU so as to call the service.

The service information which the service-side ECU can provide by broadcasting includes identification information of the service-side ECU (for example, an identification which can uniquely identify the service-side ECU, such as an IP address or a MAC address of the service-side ECU), and identification information of the service. The client sends the subscription request/call request information to the server ECU including identification information of the client ECU (e.g., an identification that can uniquely identify the server ECU, such as an IP address or a MAC address of the client ECU). Therefore, the resource scheduling request message of the service at least includes matching information of the server ECU and the client ECU and identification information of the service.

And the service end ECU sends a resource scheduling request message of the service to the network controller so that the network controller allocates communication resources for the service in the global dimension.

In step S402, the network controller generates a profile based on at least the global network topology information, the communication resources that have been allocated and the quality of service for the service.

After receiving a resource scheduling request message of service sent by a server ECU, the network controller determines communication paths of the server ECU and a client ECU based on global network topology information, allocated communication resources and matching information of the server ECU and the client ECU.

As can be understood, the global network topology information is used to indicate the communication connection relationship between multiple ECUs in the vehicle, and the network controller may obtain the global network topology information by querying, for example, the network controller queries a storage file in which the global network topology information is stored to obtain the global network topology information, or the global network topology information is stored in a memory in the network controller, and the network controller directly obtains the global network topology information by looking at the global network topology information stored in its own memory.

And determining a communication path of the server-side ECU and the client-side ECU, which meets the requirement, according to the server-side ECU and the client-side ECU which are known by the server-side ECU and the client-side ECU in the resource scheduling request message of the service in the step S401 and by combining the global network topology and the distributed communication resources.

For example, fig. 5 shows a global network topology of an entire vehicle ECU. As can be seen from fig. 5, there are multiple communication paths from the server ECU to the client ECU, for example, path 1 in fig. 5: server ECU-ECU 1-client ECU, path 2: server ECU-ECU2-ECU3-ECU 4-client ECU, path 3: service side ECU-ECU5-ECU 6-client side ECU and path 4: service-side ECU7-ECU8-ECU9-ECU 10-client-side ECU.

The available communication resource/remaining communication resource bandwidth in each of the communication paths from the server ECU to the client ECU can be known from the allocated communication resources, and for example, the available communication resource/remaining communication resource bandwidth in path 1 is 10M, the available communication resource/remaining communication resource bandwidth in path 2 is 50M, the available communication resource/remaining communication resource bandwidth in path 3 is 70M, and the available communication resource/remaining communication resource bandwidth in path 4 is 100M, which are known from the allocated communication resources. The communication path having the most available communication resources/remaining communication resources can be used as the communication path of the server ECU and the client ECU. For example, path 4: service side ECU-ECU7-ECU8-ECU9-ECU 10-client side ECU.

In another example, the communication paths of the server ECU and the client ECU may also be determined based on the global network topology information, the allocated communication resources, the matching information of the server ECU and the client ECU, and the QoS of the service.

After the network controller receives the resource scheduling request message of the service sent by the service-side ECU, the QoS of the service is determined according to the identification information of the service in the resource scheduling request message of the service. For example, determining the QoS corresponding to the service according to the identifier of the service and a preset service and QoS mapping table; or determining the QoS of the service according to the identification of the service and a preset mapping rule.

It is to be understood that the QoS of the service may include one or more of bandwidth requirement information, delay requirement information, packet loss rate requirement information, delay jitter requirement information, and priority requirement information.

And after the QoS of the service is determined, determining the communication paths of the server ECU and the client ECU by combining the global network topology information, the distributed communication resources and the matching information of the server ECU and the client ECU.

For example, the available communication resources/remaining communication resources in each of the communication paths from the server ECU to the client ECU are known from the allocated communication resources, and for example, the available communication resources/remaining communication resources bandwidth in path 1 is 10M, the available communication resources/remaining communication resources bandwidth in path 2 is 50M, the available communication resources/remaining communication resources bandwidth in path 3 is 70M, and the available communication resources/remaining communication resources bandwidth in path 4 is 100M. And the QoS requirement bandwidth of the service is 80M, then path 4 is determined: the server ECU-ECU7-ECU8-ECU9-ECU 10-client ECU are the communication path of the server ECU and the client ECU.

The network controller generates a configuration file based on at least the communication path information of the server ECU and the client ECU and the QoS information of the service.

The configuration file is used to indicate resource allocation policies for implementing the service provider to provide services to the service demanders.

For example, after the communication paths of the server ECU and the client ECU are determined as the server ECU-ECU7-ECU8-ECU9-ECU 10-client ECU, the resource allocation of the service is determined according to the QoS of the service. For example, if the QoS of the service is bandwidth 80, a communication resource of 100M bandwidth available in the communication path server ECU-ECU7-ECU8-ECU9-ECU 10-client ECU is allocated 80M bandwidth to the service, and a profile is generated based on at least the communication path and the resource allocation of the service, so that the resource allocation policy includes at least the communication path of the server ECU and the client ECU and the communication resource allocated to the service.

It will be appreciated that the resource allocation policy may also include allocation of other communication resources, such as time, frequency, code, etc. communication resources.

In one example, the network controller is provided with an allocated communication resource storage module for storing the allocated communication resources and storing the allocation policy for the service in the allocated communication resources.

And if the available communication resources in the communication paths of the server-side ECU and the client-side ECU determined in step S402 do not satisfy the QoS of the service, rejecting the resource scheduling request of the service.

For example, if the QoS bandwidth of the service is 120M, and the determined available communication resource bandwidth in the communication path between the server ECU and the client ECU is 100M, it is obvious that the available communication resource in the communication path between the server ECU and the client ECU does not satisfy the QoS bandwidth of the service, the resource scheduling request of the service is rejected, that is, response information for rejecting the resource scheduling request is sent to the server ECU, and the server ECU rejects the subscription or invocation of the client ECU.

In step S403, the network controller transmits the configuration file to the relevant ECU of the plurality of ECUs of the vehicle.

It is easily understood that the relevant ECUs are ECUs on the communication paths of the server ECU and the client ECU, for example, the determined communication paths of the server ECU and the client ECU are server ECU-ECU7-ECU8-ECU9-ECU 10-client ECU, and the relevant ECUs are server ECU, ECU7, ECU8, ECU9, ECU10 and client ECU.

In step S404, the relevant ECU performs route forwarding and service resource scheduling according to the configuration file to implement service subscription of the client ECU, for example, the server ECU periodically or event-type issues the service to the client ECU; and implementing a service call of the client ECU, for example, the server ECU executes the service in response to a call request of the client.

According to the embodiment of the application, the newly added network controller is used as a unified node to carry out global topological resource scheduling so as to obtain global optimal data transmission efficiency, and the problem that the service quality cannot be guaranteed globally due to local resource scheduling of each ECU in the related technology is solved.

The application also provides another architecture based on a QoS negotiation mechanism. As shown in fig. 6, the architecture includes an application layer, a vehicle OS layer, a network control layer, and a hardware layer. The difference from the architecture shown in fig. 3 is that: a service QoS negotiation mechanism is added between a service provider and a network control layer, namely, the service QoS negotiation mechanism is added between a service end ECU and a network controller, and more reasonable scheduling of service resources is realized through the service QoS negotiation mechanism so as to fulfill the aim of meeting the service QoS requirement as far as possible.

Fig. 7 is a flowchart of another resource scheduling method provided in the present application. The method can be applied to the architecture shown in fig. 6. As shown in fig. 7, the method comprises at least steps S701-S711.

Steps S701 to S705 are similar to steps S401 to S404 in fig. 4, and refer to the description of steps S401 to S404, which is not repeated herein for brevity. The resource scheduling method shown in fig. 7 is different from the resource scheduling method shown in fig. 4 in that a QoS requirement negotiation procedure of the service is added, i.e., steps S706 to S711. Namely, when the feasible scheduling strategy calculated by the network controller cannot meet the QoS of the service, a QoS requirement negotiation mechanism of the service is introduced between the network controller and the service end ECU. The detailed description of the negotiation process is referred to in steps S706-S711.

In step S706, the network controller transmits a negotiation request message to the server ECU.

The negotiation request message is used to instruct the network controller to propose QoS to the service-side ECU.

For example, when the determined available communication resource bandwidth in the communication path between the server ECU and the client ECU is 100M, the QoS requirement bandwidth of the service is 120M, and the resource allocation policy at this time does not satisfy the QoS of the service, the network controller sends the negotiated QoS to the server ECU. For example, the network controller sends the service to the service-side ECU over a communication path and the bandwidth available for the service in the path is 100M.

In step S707, whether the service-side ECU accepts the proposed QoS.

If yes, step S708 is executed, i.e. the network controller generates a configuration file according to the communication path of the service-side ECU and the client-side ECU and the proposed QoS of the service. For example, if the communication path between the server ECU and the client ECU is the server ECU-ECU7-ECU8-ECU9-ECU 10-client ECU, and the QoS of the service is the bandwidth 100M, then the communication resource of the bandwidth 100M available in the communication path is allocated to the service, then the allocation policy of the service at least includes that the communication path of the service is the server ECU-ECU7-ECU8-ECU9-ECU 10-client ECU, and the communication resource of the bandwidth 100M in the path is allocated to the service, then a profile is generated based on at least the communication path between the server ECU and the client ECU and the allocation policy of the service.

If not, step S711 is executed, the network controller rejects the resource scheduling request of the service.

Steps S708 to S710 are similar to steps S402 to S404 in fig. 4, and refer to the description of steps S402 to S404, which is not repeated herein for brevity.

According to the embodiment of the application, the rationality of global communication resource allocation is optimized through the framework based on the QoS negotiation mechanism, so that the global resource allocation is more flexible, and the service quality is further improved.

The application also provides another framework based on the cross-platform service QoS guarantee mechanism. As shown in fig. 8, the architecture includes an application layer, an in-vehicle OS layer, a network control layer, and a hardware layer. The difference from the architecture shown in fig. 3 is that: the communication network of the vehicle includes an in-vehicle communication network and an out-vehicle communication network, and the in-vehicle OS layer includes an in-vehicle service provider (ECU providing in-vehicle service) and an out-vehicle service agent (ECU providing out-vehicle service). And the configuration file generation module in the network control layer is used for managing scheduling information of network communication resources inside and outside the vehicle to realize vehicle internal and external combined network topology control, maintaining the mapping relation of the service end ECU and the client end ECU in the whole vehicle internal and external network topology, and performing end-to-end resource scheduling based on the vehicle internal and external network global information.

It will be readily appreciated that the off-board communication network may be, for example, a vehicle-to-everything (V2X) communication network, such as, by way of example, a vehicle-to-vehicle (V2V) communication network, a vehicle-to-infrastructure (V2I) communication network, a vehicle-to-pedestrian (V2P) communication network, a vehicle-to-external (V2N) communication network, and so forth. Off-board services refer to functions outside of the vehicle that are available through an off-board communication network, such as (over the air, OTA) over-the-air services, remote control services, and the like.

The resource scheduling method based on the architecture shown in fig. 8 is similar to the method shown in fig. 4 and 7, except that the server ECU includes an in-vehicle server ECU and an out-vehicle server ECU, and the resource scheduling message of the corresponding service includes matching information of the in-vehicle server ECU and the client ECU and identification information of in-vehicle service, matching information of the out-vehicle server ECU and the client ECU and identification information of out-vehicle service.

The communication path information of the server ECU and the client ECU comprises the communication path information of the in-vehicle server ECU and the client ECU and the communication path information of the out-vehicle server ECU and the client ECU.

The communication path information of the in-vehicle service-side ECU and the client ECU is determined based on at least the matching information of the in-vehicle service-side ECU and the client ECU, the global network topology information, and the allocated in-vehicle communication resource information, and the specific determination method may refer to the detailed description in step S402 in fig. 4, which is not described herein again for brevity.

The communication path information of the vehicle exterior service side ECU and the client side ECU is determined based on at least the matching information of the vehicle exterior service side ECU and the client side ECU, the global network topology information, and the allocated vehicle exterior communication resource information, and the specific determination method is similar to the communication path determination method in step S402 in fig. 4, and is not repeated here for brevity.

The QoS of the service comprises the QoS of the service inside the vehicle and the QoS of the service outside the vehicle, and the resource allocation strategy of the service correspondingly comprises the resource allocation strategy of the service inside the vehicle and the resource allocation strategy outside the vehicle.

The profile of the in-vehicle service is determined by the profile generation module in fig. 8 based on the communication path information of the in-vehicle service-side ECU and the client ECU and the QoS information of the in-vehicle service. The profile of the offboard service is determined by the profile generation module in fig. 8 based on the communication path information of the offboard service-side ECU and the client ECU and the QoS information of the offboard service.

The configuration file generation module in the embodiment of the application can be physically separated into an in-vehicle service configuration file generation module and an out-vehicle service configuration file generation module, or can be integrated on the same hardware, but is logically separated into the in-vehicle service configuration file generation module and the out-vehicle service configuration file generation module; the configuration file generation module of the in-vehicle service is used for determining the configuration file of the in-vehicle service based on the communication path information of the in-vehicle service end ECU and the client ECU and the QoS information of the in-vehicle service. The configuration file generation module of the off-board service is used for determining the configuration file of the off-board service based on the communication path information of the off-board service end ECU and the client ECU and the QoS information of the off-board service.

And the configuration file generation module of the in-vehicle service generates a first configuration file, and sends the first configuration file to the relevant ECU in the vehicle, and the relevant ECU in the vehicle carries out routing forwarding and service resource scheduling according to the first configuration file, so that scheduling execution of the in-vehicle service is realized.

And the configuration file generation module of the vehicle exterior service generates a second configuration file, and sends the second configuration file to the vehicle exterior related ECU, and the vehicle exterior related ECU performs routing forwarding and service resource scheduling according to the second configuration file to realize scheduling execution of the vehicle exterior service.

According to the embodiment of the application, the mapping relation of the service-side ECU and the client-side ECU in the whole in-vehicle and out-vehicle network topology is optimized through a cross-platform service QoS guarantee mechanism based on in-vehicle and out-vehicle combined network topology control, so that end-to-end resource scheduling is performed based on network global information, and the service quality is further improved.

The embodiment of the application also provides a network controller applied to the vehicle.

Fig. 9 is a schematic structural diagram of a network controller applied to a vehicle according to an embodiment of the present application. As shown in fig. 9, the network controller 900 includes at least:

a communication module 910, configured to receive a resource scheduling request message from a service provider in the vehicle, where the resource scheduling request message is used to instruct a service demander in the vehicle to request a first service from the service provider and is also used to instruct a requested service quality, and the requested service quality is a service quality requested by the service provider from the network controller, for the first service;

a quality of service determining module 920, configured to determine a quality of service for the first service according to the resource scheduling request message;

a profile generation module 930, configured to generate a profile according to global network topology information indicating a connection relationship between electronic control units in the vehicle, allocated communication resources, and the quality of service for the first service, where the profile is used to indicate a resource allocation policy used to enable the service provider to provide the first service to the service demander;

the communication module 910 is further configured to send the configuration file to at least one electronic control unit in the vehicle, where the at least one electronic control unit is an electronic control unit configured to enable the service provider to provide the first service to the service demander.

In one possible implementation, the profile generation module 930 is configured to generate a profile according to the global network topology information indicating the connection relationship among the plurality of electronic control units in the vehicle, the allocated communication resources and the service quality for the first service, and includes the profile generation module 930 configured to:

determining a communication path between the service demander and the service provider according to the global network topology information used for indicating the connection relationship among the electronic control units in the vehicle, the allocated communication resources and the service quality used for the first service; wherein the at least part of the electronic control unit is located on the communication path; generating a profile based on the communication path and the quality of service for the first service.

In another possible implementation, the quality of service determination module 920 is further configured to determine that the requested quality of service cannot be satisfied;

the communication module 910 is further configured to send a negotiation request message to the service provider, and receive a negotiation response message from the service provider, where the negotiation request message is used to indicate a proposed quality of service for the service provider by the network controller, and the negotiation response message is used to indicate that the service provider accepts the proposed quality of service;

the qos determination module 920 is further configured to determine the proposed qos as the qos for the first service.

The network controller 900 according to the embodiment of the present application may correspondingly execute the method described in the embodiment of the present application, and the above and other operations and/or functions of each module in the network controller 900 are respectively for implementing corresponding flows of each method in fig. 4 and fig. 7, and are not described again here for brevity.

Embodiments of the present application also provide a vehicle having an electronic-electrical system made up of a plurality of electronic control units ECUs, which may be implemented based on a conventional distributed electronic-electrical architecture, a domain controller architecture, or a central computing-based electronic-electrical architecture.

It can be understood that the term "domain" means that the vehicle electronic system is divided into a plurality of functional blocks according to functions, and a system architecture inside each functional block is mainly built by a domain controller. The ECU in each domain is interconnected, for example, the interconnection between the ECUs in each domain CAN be realized by adopting a CAN or FlexRay communication bus. For example, each domain is used as a backbone network through the ethernet to undertake an information exchange task, thereby realizing interconnection among different domains.

The electronic and electrical architecture based on central computing is to strip out the corresponding software system from the ECUs distributed everywhere and to re-integrate it in the corresponding domain controller, and each domain controller is connected to the central controller in communication, for example, the central controller is connected to other domain controllers in communication through a central gateway and an ethernet.

When implemented based on a conventional distributed electronic and electrical architecture, the network controller in fig. 9 may be deployed in a certain ECU within the vehicle to implement quality of service guarantees for global traffic of the vehicle. For the sake of brevity, the detailed description of the specific implementation method is omitted with reference to the descriptions in fig. 4 and fig. 7.

When the communication network of the vehicle is implemented as a domain controller architecture, the network controller in fig. 9 may be deployed in the domain controller, so as to implement quality of service guarantee of the global service flow of the vehicle. For the sake of brevity, the detailed description of the specific implementation method is omitted with reference to the descriptions in fig. 4 and fig. 7.

When the communication network of the vehicle is implemented by an electronic and electrical architecture based on central computing, the network controller in fig. 9 may be deployed in the central controller, so as to implement quality of service guarantee for the global service flow of the vehicle. For the sake of brevity, the detailed description of the specific implementation method is omitted with reference to the descriptions in fig. 4 and fig. 7.

The vehicle includes various electronic devices. Such as various sensors. The various sensors include, for example, a camera for taking an image of the surroundings of the vehicle and collecting image data; a radar for acquiring position information, distance information, speed information, and the like of an object (e.g., a preceding vehicle, a pedestrian, and the like).

The vehicle may also include various control systems such as an engine management system for generating power, a transmission control system for transmitting power generated by the engine to wheels, a brake system for decelerating or stopping the vehicle, and a body control system for providing comfort to the driver or ensuring safety of the driver, etc.

A plurality of ECUs are disposed in various electronic devices and various control systems on the vehicle for controlling the various electronic devices and the various control systems to implement various functions of the vehicle and to implement communication connections between the various electronic devices and the various control systems.

For example, a server ECU1 is deployed in a radar, a client ECU2 is deployed in a braking system, when the braking system needs to acquire environment information outside a vehicle, the ECU2 sends a subscription/call request to the ECU1, the ECU2 sends a resource scheduling request message to a network controller, the network controller generates a resource scheduling policy in a global dimension, generates a configuration file, and sends the configuration file to a related ECU, and the related ECU performs routing forwarding and scheduling of service resources according to the configuration file, so that the ECU1 provides radar service to the ECU2, that is, the ECU1 sends the environment information around the vehicle acquired by the radar to the ECU2. The brake system controls the vehicle running speed according to the vehicle external information acquired by the ECU2.

The embodiment of the application also provides a chip.

As shown in fig. 10, the chip 1000 includes a processor 1001, a memory 1002, and a communication interface 1003. The processor 1001, the memory 1002, and the communication interface 1003 are communicatively connected, and communication may be achieved by other means such as wireless transmission. The communication interface 1003 is used for performing communication connection with other ECUs, for example, receiving resource scheduling request messages sent by other ECUs, sending configuration files to relevant ECUs, and the like; the memory 1002 stores executable program code, and the processor 1001 may call the program code stored in the memory 1002 to perform the resource scheduling method in the aforementioned method embodiments.

It should be understood that, in the embodiment of the present application, the processor 1001 may be a central processing unit CPU, and the processor 1001 may also be other general processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or any conventional processor or the like.

The memory 1002 may include a read-only memory and a random access memory, and provides instructions and data to the processor 1001. The memory 1002 may also include non-volatile random access memory. For example, the memory 1002 may also store a training data set.

The memory 1002 may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and direct bus RAM (DR RAM).

It should be understood that the chip 1000 according to the embodiment of the present application may execute the resource scheduling method shown in fig. 4 and fig. 7 according to the embodiment of the present application, and for a specific implementation manner, refer to the above detailed description of fig. 4 and fig. 7, and for brevity, details are not described here again.

It is understood that the above-mentioned resource scheduling methods, network controllers and chips are applicable to other similar embedded systems (e.g., industrial control systems, medical systems, critical infrastructure systems, etc.) in addition to vehicles to achieve quality of service guarantees in the system.

The present application also provides a computer-readable storage medium comprising computer instructions which, when executed by a processor, implement the resource scheduling method described above.

The present application also provides a computer program product for implementing the above-described resource scheduling method when the computer program product runs on a processor.

It will be further appreciated by those of ordinary skill in the art that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether these functions are performed in hardware or software depends on the specific application of the solution and design constraints. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, a software module executed by a processor, or a combination of the two. A software module may reside in Random Access Memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

The above-mentioned embodiments, objects, technical solutions and advantages of the present application are described in further detail, it should be understood that the above-mentioned embodiments are merely exemplary embodiments of the present application, and are not intended to limit the scope of the present application, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present application should be included in the scope of the present application.

Claims

1. A vehicle comprising a service demander, a service provider and a network controller;

the service demander is used for sending a service request message to the service provider, and the service request message is used for requesting the service provider to subscribe to a first service or call the first service;

the service provider is configured to:

receiving the service request message;

generating a resource scheduling request message according to the service request message, wherein the resource scheduling request message is used for indicating the service demander to request the first service from the service provider and indicating the requested service quality, and the requested service quality is the service quality which is requested by the service provider to the network controller and is related to the first service; and

sending the resource scheduling request message to the network controller;

the network controller is configured to:

receiving the resource scheduling request message;

determining a quality of service for the first service according to the resource scheduling request message;

generating a configuration file according to global network topology information used for indicating connection relations among a plurality of electronic control units in the vehicle, the allocated communication resources and the service quality used for the first service, wherein the configuration file is used for indicating resource allocation strategies, and the resource allocation strategies are used for realizing that the service providers provide the first service to the service demanders; and

sending the configuration file to at least part of the electronic control units in the plurality of electronic control units, wherein the at least part of the electronic control units are electronic control units for realizing that the service provider provides the first service to the service demander.

2. The vehicle of claim 1, wherein the quality of service for the first service is determined through a negotiation process between the network controller and the service provider.

3. The vehicle of claim 1 or 2, wherein the network controller is configured to determine a quality of service for the first service based on the resource scheduling request message, comprising the network controller configured to:

determining that a quality of service of the request cannot be satisfied;

sending a negotiation request message to the service provider, wherein the negotiation request message is used for indicating the service quality suggested by the network controller to the service provider;

receiving a negotiation response message from the service provider, the negotiation response message indicating that the service provider accepts the proposed quality of service; and

determining the proposed quality of service as the quality of service for the first service.

4. The vehicle of any of claims 1-3, wherein the service provider is configured to proxy an off-board service, the first service is the off-board service, the off-board service is configured to provide services external to the vehicle, and the allocated communication resources include resources for on-board communications and resources for off-board communications.

5. The vehicle of any of claims 1-4, wherein prior to receiving the service request message, the service provider is further configured to:

broadcasting services that the service provider is able to provide to the plurality of electronic control units.

6. The vehicle of any of claims 1-5, wherein the service request message includes identification information of the first service, and wherein the service provider is further configured to determine the requested quality of service based on the identification information and a predetermined quality of service configuration rule.

7. The vehicle of any of claims 1-6, characterized in that the network controller, the service provider, and the service demander are electronic control units within the vehicle.

8. The vehicle according to any one of claims 1 to 7, wherein the network controller is configured to generate a profile based on global network topology information indicating connection relationships between a plurality of electronic control units in the vehicle, the communication resources that have been allocated, and the quality of service for the first service, and comprises the network controller configured to:

determining a communication path between the service demander and the service provider according to the global network topology information for indicating the connection relationship among the electronic control units in the vehicle, the allocated communication resources and the service quality for the first service; wherein the at least part of the electronic control unit is located on the communication path;

generating a profile based on the communication path and the quality of service for the first service.

9. A resource scheduling method is applied to a network controller in a vehicle, and comprises the following steps:

the network controller receiving a resource scheduling request message from a service provider in the vehicle, the resource scheduling request message being used for indicating that a service demander in the vehicle requests a first service from the service provider and also indicating a requested quality of service, the requested quality of service being the quality of service requested by the service provider from the network controller for the first service;

the network controller determines the service quality for the first service according to the resource scheduling request message;

the network controller generates a configuration file according to global network topology information used for indicating connection relations among electronic control units in the vehicle, the distributed communication resources and the service quality used for the first service, wherein the configuration file is used for indicating resource distribution strategies, and the resource distribution strategies are used for realizing that the service providers provide the first service to the service demanders;

the network controller sends the configuration file to at least one electronic control unit in the vehicle, the at least one electronic control unit being an electronic control unit for enabling the service provider to provide the first service to the service demander.

10. The method of claim 9, wherein the quality of service for the first service is determined through a negotiation process between the network controller and the service provider.

11. The method according to claim 9 or 10, wherein the network controller determines the quality of service for the first service according to the resource scheduling request message, comprising:

the network controller determining that a quality of service of the request cannot be satisfied;

the network controller sends a negotiation request message to the service provider, wherein the negotiation request message is used for indicating the service quality suggested by the network controller to the service provider;

receiving, by the network controller, a negotiation response message from the service provider, the negotiation response message indicating that the service provider accepts the proposed quality of service;

the network controller determines the proposed quality of service to be the quality of service for the first service.

12. The method of any of claims 9-11, wherein the service provider is an electronic control unit for brokering an off-board service, the first service is the off-board service, the off-board service is for providing services external to the vehicle, and the allocated communication resources include resources for on-board communications and resources for off-board communications.

13. The method of any of claims 9-12, wherein the network controller, the service provider, and the service demander are electronic control units within the vehicle.

14. The method according to any one of claims 9 to 13, wherein the network controller generates a profile based on global network topology information indicating a connection relationship between the in-vehicle electronic control units, the communication resources that have been allocated, and the quality of service for the first service, including:

the network controller determines a communication path between the service demander and the service provider according to the global network topology information for indicating the connection relationship among the electronic control units in the vehicle, the allocated communication resources and the service quality for the first service; wherein the at least part of the electronic control unit is located on the communication path;

generating a configuration file according to the communication path and the service quality for the first service.

15. A network controller for use in a vehicle, comprising:

a communication module, configured to receive a resource scheduling request message from a service provider in the vehicle, the resource scheduling request message being used to indicate that a service demander in the vehicle requests a first service from the service provider and being used to indicate a requested quality of service, the requested quality of service being a quality of service requested by the service provider from the network controller regarding the first service;

a service quality determining module, configured to determine a service quality for the first service according to the resource scheduling request message;

a configuration file generation module, configured to generate a configuration file according to global network topology information indicating a connection relationship between electronic control units in the vehicle, allocated communication resources, and the quality of service for the first service, where the configuration file is used to indicate a resource allocation policy, and the resource allocation policy is used to enable the service provider to provide the first service to the service demander;

the communication module is further configured to send the configuration file to at least one electronic control unit in the vehicle, where the at least one electronic control unit is an electronic control unit configured to enable the service provider to provide the first service to the service demander.

16. The network controller of claim 15, wherein the quality of service for the first service is determined through a negotiation process between the network controller and the service provider.

17. The network controller according to claim 15 or 16,

the quality of service determination module is further configured to determine that the requested quality of service cannot be satisfied;

the communication module is further configured to send a negotiation request message to the service provider, and receive a negotiation response message from the service provider, where the negotiation request message is used to indicate a proposed quality of service for the service provider by the network controller, and the negotiation response message is used to indicate that the service provider accepts the proposed quality of service;

the quality of service determination module is further configured to determine the proposed quality of service as the quality of service for the first service.

18. The network controller according to any one of claims 15-17, wherein the service provider is an electronic control unit for brokering an off-board service, the first service is the off-board service, the off-board service is for providing services external to the vehicle, and the allocated communication resources include resources for on-board communication and resources for off-board communication.

19. The network controller of any of claims 15-18, wherein the network controller, the service provider, and the service demander are electronic control units within the vehicle.

20. The network controller according to any one of claims 15 to 19, wherein the profile generation module is configured to generate a profile according to global network topology information indicating connection relationships among a plurality of electronic control units in the vehicle, the allocated communication resources, and the quality of service for the first service, and comprises the profile generation module configured to:

21. A network controller for application to a vehicle, comprising a memory storing computer program instructions and a processor executing the computer program instructions to implement the method of any one of claims 9 to 14.

22. A computer readable storage medium comprising computer instructions which, when executed by a processor, cause the method of any one of claims 9-14 to be carried out.

23. A computer program product enabling the method according to any of claims 9-14 to be implemented when the computer program product is run on a processor.