WO2022206327A1 - Véhicule et son procédé de planification de ressources - Google Patents

Véhicule et son procédé de planification de ressources Download PDF

Info

Publication number
WO2022206327A1
WO2022206327A1 PCT/CN2022/080016 CN2022080016W WO2022206327A1 WO 2022206327 A1 WO2022206327 A1 WO 2022206327A1 CN 2022080016 W CN2022080016 W CN 2022080016W WO 2022206327 A1 WO2022206327 A1 WO 2022206327A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
vehicle
quality
network controller
service provider
Prior art date
Application number
PCT/CN2022/080016
Other languages
English (en)
Chinese (zh)
Inventor
李添泽
黎金科
郑益红
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN202110359885.4A external-priority patent/CN115190179B/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2022206327A1 publication Critical patent/WO2022206327A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/78—Architectures of resource allocation
    • H04L47/781—Centralised allocation of resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/80—Actions related to the user profile or the type of traffic
    • H04L47/805—QOS or priority aware
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/61—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources taking into account QoS or priority requirements

Definitions

  • the present application relates to the technical field of intelligent driving, and in particular, to a vehicle and a resource scheduling method thereof.
  • the embodiments of the present application provide a vehicle and a resource scheduling method thereof, so as to realize the service quality assurance of the global service flow of the vehicle.
  • the present application provides a vehicle, including a service demander, a service provider, and a network controller; the service demander is configured to send a service request message to the service provider, and the service request message is used for Request the service provider to subscribe to the first service or to call the first service; the service provider is configured to: receive the service request message; generate a resource scheduling request message according to the service request message, the resource scheduling The request message is used to instruct the service demander to request the first service from the service provider, and is also used to instruct the requested service quality, where the requested service quality is the request from the service provider to the network controller.
  • the service provider is used to provide in-vehicle services, or to act as an agent for out-of-vehicle services, or both to provide The in-vehicle service also acts as an out-of-vehicle service;
  • the network controller is configured to: receive the resource scheduling request message; determine the quality of service for the first service according to the resource scheduling request message;
  • the global network topology information of the connection relationship between the plurality of electronic control units, the communication resources that have been allocated, and the quality of service for the first service generate a configuration file, the configuration file is used to indicate a resource allocation strategy , the resource allocation strategy is used to implement the service provider to provide the first service to the service demander; and to send the configuration file to at least some of the plurality of electronic control units, the
  • the at least part of the electronic control unit is an electronic control unit for enabling the service provider to provide the first service to the service demander.
  • the vehicle in the embodiment of the present application performs resource scheduling of the global network topology by adding a new network controller as a unified node, so as to obtain the globally optimal data transmission efficiency, and solves the service problem caused by the local resource scheduling of each electronic control unit in the related art. Quality cannot be guaranteed globally.
  • the network controller is configured to use the global network topology information for indicating the connection relationship between the plurality of electronic control units in the vehicle, the allocated communication resources and the A service quality of a service, generating a configuration file, including the network controller for: according to the global network topology information used to indicate the connection relationship between a plurality of electronic control units in the vehicle, the allocated communication resources and The quality of service for the first service determines a communication path between the service demander and the service provider; wherein the at least part of the electronic control unit is located on the communication path; according to the The communication path and the quality of service for the first service generate a configuration file.
  • the quality of service for the first service is determined through a negotiation process between the network controller and the service provider.
  • the vehicle in the embodiment of the present application determines the service quality of the first service through negotiation between the network controller and the service provider.
  • the negotiation mechanism the business resources of the entire vehicle can be more reasonably scheduled, so as to meet the service quality of the first service as much as possible.
  • it optimizes the rationality of the global communication resource allocation of the whole vehicle, making the global resource allocation more flexible.
  • the network controller is configured to determine the quality of service for the first service according to the resource scheduling request message, including the network controller being configured to: determine that the requested quality of service cannot be meet; send a negotiation request message to the service provider, the negotiation request message is used to indicate the quality of service proposed by the network controller to the service provider; receive a negotiation response message from the service provider, the The negotiation response message is used to instruct the service provider to accept the proposed quality of service; and to determine that the proposed quality of service is the quality of service for the first service.
  • the service provider is used to act as an out-of-vehicle service
  • the first service is the out-of-vehicle service
  • the out-of-vehicle service is used to provide the vehicle with a service outside the vehicle
  • the allocated communication resources include resources for in-vehicle communication and resources for out-of-vehicle communication.
  • the vehicle in the embodiment of the present application optimizes the mapping relationship between service providers and service demanders in the entire in-vehicle and out-vehicle network topology through the cross-platform service quality assurance mechanism based on the network topology control of the vehicle inside and outside the vehicle, so that based on the global network
  • the information performs end-to-end resource scheduling, which further ensures the service quality of the first service.
  • the service provider before receiving the service request message, is further configured to: broadcast the service that the service provider can provide to the plurality of electronic control units.
  • the service request message includes identification information of the first service
  • the service provider is further configured to determine the requested service quality according to the identification information and a preset service quality configuration rule.
  • the network controller, the service provider and the service demander are electronic control units in the vehicle.
  • the present application provides a resource scheduling method applied to a network controller in a vehicle, the method comprising: the network controller receiving a resource scheduling request message from a service provider in the vehicle, the The resource scheduling request message is used to instruct the service demander in the vehicle to request the first service from the service provider, and is also used to indicate the requested service quality, where the requested service quality is the request from the service provider to the service provider.
  • the network controller determines the quality of service for the first service according to the resource scheduling request message; the network controller according to the global network topology information for indicating the connection relationship between the electronic control units in the vehicle, has been allocated
  • the communication resources and the quality of service used for the first service a configuration file is generated, the configuration file is used to indicate a resource allocation strategy, and the resource allocation strategy is used to implement the service provider's demand for the service the first service is provided by the service provider;
  • the network controller sends the configuration file to at least one electronic control unit in the vehicle, the at least one electronic control unit is used to implement the service provider to the service The demander provides the electronic control unit of the first service.
  • the resource scheduling method of the embodiment of the present application uses the network controller as a unified node to perform resource scheduling of the global network topology, so as to obtain the globally optimal data transmission efficiency, and solves the problem of service caused by the local resource scheduling of each electronic control unit in the related art Quality cannot be guaranteed globally.
  • the network controller is based on the global network topology information for indicating the connection relationship between the electronic control units in the vehicle, the allocated communication resources and the information for the first service.
  • the quality of service generating a configuration file, comprising: the network controller according to the global network topology information used to indicate the connection relationship between multiple electronic control units in the vehicle, the allocated communication resources and the user
  • the service quality of the first service determine a communication path between the service demander and the service provider; wherein the at least part of the electronic control unit is located on the communication path; according to the communication path and For the quality of service for the first service, a configuration file is generated.
  • the quality of service for the first service is determined through a negotiation process between the network controller and the service provider.
  • the resource scheduling method of the embodiment of the present application determines the service quality of the first service through negotiation between the network controller and the service provider.
  • the purpose of quality of service on the other hand, optimizes the rationality of the global communication resource allocation of the whole vehicle, making the global resource allocation more flexible.
  • the network controller determining the quality of service for the first service according to the resource scheduling request message includes: the network controller determining that the requested quality of service cannot be satisfied; The network controller sends a negotiation request message to the service provider, the negotiation request message is used to indicate the quality of service proposed by the network controller to the service provider; the network controller provides the service from the service provider. The provider receives a negotiation response message, the negotiation response message is used to instruct the service provider to accept the proposed service quality; the network controller determines that the proposed service quality is the service quality.
  • the service provider is an electronic control unit used to act as an off-board service
  • the first service is the off-board service
  • the off-board service is used to provide all the services to the vehicle.
  • the allocated communication resources include resources for in-vehicle communication and resources for out-of-vehicle communication.
  • the resource scheduling method of the embodiments of the present application optimizes the mapping relationship between service providers and service demanders in the entire in-vehicle and out-vehicle network topology through a cross-platform service quality assurance mechanism based on the in-vehicle and out-of-vehicle joint network topology control, so that based on The network global information performs end-to-end resource scheduling, which further ensures the service quality of the first service.
  • the network controller, the service provider and the service demander are electronic control units in the vehicle.
  • the present application further 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, where the resource scheduling request message is used to indicate The in-vehicle service demander requests the service provider for the first service, and is further used to indicate the requested service quality, where the requested service quality is the information about the service requested by the service provider from the network controller.
  • the service quality determination module is used for determining the service quality for the first service according to the resource scheduling request message;
  • the configuration file generation module is used for instructing the in-vehicle electronic control
  • the global network topology information of the connection relationship between the units, the allocated communication resources and the quality of service for the first service generate a configuration file, the configuration file is used to indicate a resource allocation strategy, the resource allocation
  • An electronic control unit is an electronic control unit for enabling the service provider to provide the first service to the service demander.
  • the configuration file generation module is configured to use the global network topology information for indicating the connection relationship between the plurality of electronic control units in the vehicle, the allocated communication resources and the The quality of service of the first service is generated, and a configuration file is generated, including the configuration file generation module used for: according to the global network topology information used to indicate the connection relationship between multiple electronic control units in the vehicle, the configuration file has been allocated the communication resources and the quality of service for the first service, determine a communication path between the service demander and the service provider; wherein the at least part of the electronic control unit is located on the communication path ; generating a configuration file based on the communication path and the quality of service for the first service.
  • the quality of service for the first service is determined through a negotiation process between the network controller and the service provider.
  • the service quality determination module is further configured to determine that the requested service quality cannot be satisfied; the communication module is further configured to send a negotiation request message to the service provider, and use receiving a negotiation response message from the service provider, wherein the negotiation request message is used to indicate the quality of service proposed by the network controller to the service provider, and the negotiation response message is used to indicate the service provider The user accepts the suggested service quality; the service quality determination module is further configured to determine that the suggested service quality is the service quality for the first service.
  • the service provider is an electronic control unit used to act as an off-board service
  • the first service is the off-board service
  • the off-board service is used to provide all the services to the vehicle.
  • the allocated communication resources include resources for in-vehicle communication and resources for out-of-vehicle communication.
  • the network controller, the service provider and the service demander are electronic control units in the vehicle.
  • the present application further provides a network controller applied to a vehicle, comprising a memory and a processor, wherein the memory stores computer program instructions, and the processor executes the computer program instructions to implement the second aspect.
  • the present application further provides a computer-readable storage medium, comprising computer instructions, which, when executed by a processor, enable the method of the second aspect to be implemented.
  • the present application further provides a computer program product, which enables the method described in the second aspect to be implemented when the computer program product is run on a processor.
  • the present application further provides a chip, including 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.
  • 1 is a schematic diagram of the architecture of SOA in the related art
  • FIG. 2 is a schematic diagram of the architecture of an SOA provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of the architecture of an SOA provided by an embodiment of the present application.
  • FIG. 4 is a flowchart of a resource scheduling method provided by an embodiment of the present application.
  • Figure 5 is a global network topology diagram of a vehicle ECU
  • FIG. 6 is an architecture diagram based on a QoS negotiation mechanism provided by an embodiment of the present application.
  • FIG. 7 is a flowchart of another resource scheduling method provided by the present application.
  • FIG. 8 is an architectural diagram of a cross-platform service-based QoS guarantee mechanism provided by 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 application.
  • FIG. 10 is a schematic structural diagram of a chip provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of the architecture of an SOA in the related art.
  • the EE architecture of the vehicle in the related art adopts the SOA shown in FIG. 1 .
  • the SOA includes an application layer, a middleware and a hardware layer.
  • the service invocation process is: a middleware-based communication protocol (such as the Ethernet SOME/IP protocol), the service provider publishes the available services, and then the service demander of the service is required to subscribe/invoke the service, and finally the business flow Generated, each ECU performs distributed communication resource scheduling, buffering and transmission based on its own situation.
  • each ECU guarantees the QoS of services through 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.
  • this kind of distributed resource allocation cannot guarantee the QoS of global services.
  • an embodiment of the present application proposes a resource scheduling method.
  • a network control layer (see FIG. 2 ) is added between the hardware layer and the middleware layer, and the network control layer is based on the global network topology.
  • Information and allocated communication resources generate scheduling policies, and ensure the QoS of global service flows.
  • FIG. 3 is a schematic diagram of the architecture of an SOA according to an embodiment of the present application.
  • the SOA includes application layer, vehicle OS layer, network control layer and hardware layer.
  • the network control layer can be understood as a unified service control plane, and the entire network is managed and controlled through the unified service control plane.
  • the network control layer can be implemented for a network controller deployed in a certain ECU of the vehicle, which is responsible for the calculation, decision-making and configuration of the global network resources of the electronic and electrical architecture of the vehicle.
  • the network controller includes at least the following modules: a communication module, a service quality determination module and a configuration file generation module.
  • the communication module is used to receive a resource scheduling request message from the service provider in the vehicle, the resource scheduling request message is used to instruct the service demander in the vehicle to request the service from the service provider, and is also used to indicate the requested service quality, the requested service quality, and the requested service quality.
  • the quality of service is the quality of service that the service provider requests from the network controller for the service.
  • the quality of service determination module is configured to determine the quality of service for the service according to the resource scheduling request message.
  • the configuration file generation module is used to generate a configuration file according to the global network topology information used to indicate the connection relationship between the electronic control units (ECUs) in the vehicle, the allocated communication resources and the quality of service for the service , the configuration file is used to indicate the resource allocation strategy, and the resource allocation strategy is used to implement the service provider to provide the service to the service demander.
  • the communication module is further configured to send a configuration file to at least one ECU in the vehicle, where the at least one ECU is an ECU for implementing the service provider to provide services to the service demander.
  • the ECU that receives the configuration file performs routing forwarding and scheduling of business resources according to the configuration file, so as to realize that the service provider provides services to the service demander.
  • the service provider, service demander and network controller can be realized by the ECU in the car, for example, MDC (Mobile Data Center, mobile data center), CDC (Continuous Damping Control, continuous damping control system), TBOX (Telematics Box, Communication box), VCU (Vehicle Control Unit, vehicle controller) and other ECUs deployed in the car.
  • the service provider is the ECU that provides the service
  • the service demander is the ECU that requests the service.
  • the service provider is called the server ECU
  • the service demander is called the client ECU.
  • FIG. 4 is a flowchart of a resource scheduling method provided by an embodiment of the present application. This approach can be applied to the architecture shown in Figure 3. As shown in FIG. 4 , the method includes at least steps S401-S404.
  • step S401 the server ECU sends a service resource scheduling request message to the network controller.
  • the services mentioned in this embodiment refer to the abstraction of various functions of the vehicle under the SOA-based architecture, such as window control services, seat control services, central control panel services, and advanced driver assistance systems ( advanced driving assistant system, ADAS) service, braking service, etc.
  • SOA-based architecture such as window control services, seat control services, central control panel services, and advanced driver assistance systems ( advanced driving assistant system, ADAS) service, braking service, etc.
  • ADAS advanced driving assistant system
  • the server ECU is an ECU that can provide services.
  • the network controller can realize the functions of the network control layer in Fig. 3, and is deployed in a certain ECU in the vehicle to be responsible for the calculation, decision-making and configuration of the global network resources of the electronic and electrical architecture of the vehicle.
  • the resource scheduling request message of the service is determined based on the client ECU sending a subscription request message/call request message to the server ECU.
  • the server ECU of the vehicle broadcasts the service information it can provide, and the client ECU that needs the service sends subscription request information to the server ECU to subscribe to the service.
  • the server ECU of the vehicle broadcasts the service information that it can provide, and the client ECU that needs to use the service initiates a request to call the service to the server ECU to realize the invocation of the service.
  • the service information broadcasted by the server ECU includes the identification information of the server ECU (for example, the IP address or MAC address of the server ECU can uniquely identify the server ECU), and the identification information of the service.
  • the information of the subscription request/call request sent by the client to the server ECU includes the identification information of the client ECU (for example, the IP address or MAC address of the client ECU, etc., which can uniquely identify the server ECU). Therefore, the resource scheduling request message of the service at least includes the matching information of the server ECU and the client ECU and the identification information of the service.
  • the server ECU sends the 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.
  • step S402 the network controller generates a configuration file based on at least the global network topology information, the allocated communication resources and the quality of service for the service.
  • the network controller After receiving the resource scheduling request message of the service sent by the server ECU, the network controller determines the communication between the server ECU and the client ECU based on the global network topology information, the allocated communication resources and the matching information between the server ECU and the client ECU path.
  • the global network topology information is used to indicate the communication connection relationship between multiple ECUs in the vehicle, and the network controller can be obtained by querying, for example, the network controller can query the storage file storing the global network topology information to obtain the global network topology information. , or the global network topology information is stored in the memory in the network controller, and the network controller directly learns the global network topology information by viewing the global network topology information stored in its own memory.
  • the target server ECU and the target client ECU can be known, and the server ECU that meets the requirements is determined in combination with the global network topology and the allocated communication resources. Communication path with client ECU.
  • FIG. 5 shows a global network topology diagram of a vehicle ECU. It can be seen from Figure 5 that there are multiple communication paths from the server ECU to the client ECU. For example, in Figure 5, path 1: server ECU-ECU1-client ECU, path 2: server ECU-ECU2-ECU3-ECU4 - Client ECU, Path 3: Server ECU-ECU5-ECU6-Client ECU and Path 4: Server ECU-ECU7-ECU8-ECU9-ECU10-Client ECU.
  • path 1 server ECU-ECU1-client ECU
  • path 2 server ECU-ECU2-ECU3-ECU4 - Client ECU
  • Path 3 Server ECU-ECU5-ECU6-Client ECU
  • Path 4 Server ECU-ECU7-ECU8-ECU9-ECU10-Client ECU.
  • the available communication resources/remaining communication resources in each communication path of the above-mentioned multiple communication paths from the server ECU to the client ECU can be known from the allocated communication resources.
  • the resource/remaining communication resource bandwidth 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
  • the available communication resource/remaining communication resource bandwidth in path 4 is 100M .
  • the communication path with the most available communication resources/remaining communication resources can be used as the communication path between the server ECU and the client ECU.
  • path 4 server ECU-ECU7-ECU8-ECU9-ECU10-client ECU.
  • the communication paths of the server ECU and the client ECU may also be determined based on global network topology information, allocated communication resources, matching information of the server ECU and client ECU, and QoS of the service.
  • the network controller After receiving the resource scheduling request message of the service sent by the server ECU, the network controller determines the QoS of the service according to the identification information of the service in the resource scheduling request message of the service. For example, the QoS corresponding to the service is determined according to the service identifier and a preset service and QoS mapping table; or the QoS of the service is determined according to the service identifier and a preset mapping rule.
  • 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.
  • the communication path between the server ECU and the client ECU is determined by combining the global network topology information, the allocated communication resources and the matching information between the server ECU and the client ECU.
  • the situation of available communication resources/remaining communication resources in each communication path of the above-mentioned multiple communication paths from the server ECU to the client ECU can be known.
  • the available communication resource/remaining communication resource bandwidth 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
  • the available communication resource/remaining communication resource bandwidth in path 4 is 100M.
  • the QoS requirement bandwidth of the service is 80M, then determine the path 4: the server ECU-ECU7-ECU8-ECU9-ECU10-client ECU is the communication path between 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 the resource allocation strategy for implementing the service provider to provide the service to the service demander.
  • 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, then the communication resources of 100M bandwidth available in the communication path server ECU-ECU7-ECU8-ECU9-ECU10-client ECU are allocated 80M bandwidth to the service, at least based on the communication of the service Path and resource allocation generate configuration files, so the resource allocation strategy includes at least the communication paths between the server ECU and the client ECU and the communication resources allocated for the service.
  • resource allocation policy may also include allocation of other communication resources, such as allocation of communication resources such as time, frequency, code, etc.
  • the network controller is provided with an allocated communication resource storage module, which is used for saving the allocated communication resources, and saves the allocation policy of the service into the allocated communication resources.
  • the resource scheduling request for the service is rejected.
  • the QoS bandwidth of the service is 120M, and the communication resource bandwidth available in the communication path between the server ECU and the client ECU is determined to be 100M, it is clear that the communication resources available in the communication path between the server ECU and the client ECU are available. If the QoS bandwidth of the service is not met, the resource scheduling request of the service is rejected, that is, a response message of rejecting the resource scheduling request is sent to the server ECU, and the server ECU rejects the subscription or call of the client ECU.
  • step S403 the network controller sends the configuration file to the relevant ECU among the plurality of ECUs of the vehicle.
  • the relevant ECU here is the ECU on the communication path between the server ECU and the client ECU.
  • the determined communication path between the server ECU and the client ECU is the server ECU-ECU7-ECU8-ECU9-ECU10- Client ECU
  • the related ECUs are server ECU, ECU7, ECU8, ECU9, ECU10 and client ECU.
  • step S404 the relevant ECU performs routing forwarding and business resource scheduling according to the configuration file, so as to realize the service subscription of the client ECU, for example, the server ECU periodically or eventually publishes the service to the client ECU; Service invocation of the client ECU, for example, the server ECU executes the service in response to the client's invocation request.
  • a network controller is added as a unified node to perform resource scheduling of the global topology, so as to obtain the globally optimal data transmission efficiency, which solves the problem that the quality of service cannot be globally guaranteed due to the local resource scheduling of each ECU in the related art. The problem.
  • the present application also provides another architecture based on the QoS negotiation mechanism.
  • the architecture includes application layer, vehicle OS layer, network control layer and hardware layer.
  • the difference from the architecture shown in Figure 3 is that a service QoS negotiation mechanism is added between the service provider and the network control layer, that is, a service QoS negotiation mechanism is added between the server ECU and the network controller.
  • the negotiation mechanism realizes more reasonable scheduling of business resources, so as to meet the QoS requirements of the service as much as possible.
  • FIG. 7 is a flowchart of another resource scheduling method provided by the present application. This method can be applied to the architecture shown in FIG. 6 . As shown in FIG. 7 , the method includes at least steps S701-S711.
  • Steps S701-S705 are similar to steps S401-S404 in FIG. 4 , for details, please refer to the description of the above-mentioned steps S401-S404 , which are not repeated here for brevity.
  • the difference between the resource scheduling method shown in FIG. 7 and the resource scheduling method shown in FIG. 4 is that a negotiation process of the QoS requirement of the service is added, that is, steps S706-S711. That is, when the feasible scheduling policy calculated by the network controller cannot meet the QoS of the service, a QoS requirement negotiation mechanism for the service is introduced between the network controller and the server ECU.
  • steps S706-S711 For the specific negotiation process, refer to the detailed description of steps S706-S711.
  • step S706 the network controller sends a negotiation request message to the server ECU.
  • the negotiation request message is used to indicate the QoS suggested by the network controller to the server ECU.
  • the network controller send negotiated QoS to the server ECU.
  • the communication path through which the network controller sends the service to the server ECU and the bandwidth available for the service in the path is 100M.
  • step S707 whether the server ECU accepts the proposed QoS.
  • step S708 is executed, that is, the network controller generates a configuration file according to the communication path between the server ECU and the client ECU and the suggested QoS of the service.
  • the communication path between the server ECU and the client ECU is server ECU-ECU7-ECU8-ECU9-ECU10-client ECU
  • the QoS of the service is 100M bandwidth
  • the communication resources of 100M bandwidth available in the communication path are allocated
  • the allocation strategy of the service at least includes that the communication path of the service is server ECU-ECU7-ECU8-ECU9-ECU10-client ECU, and the 100M bandwidth communication resources in this path are allocated to this service, then at least based on The communication path between the server ECU and the client ECU and the allocation strategy of the service generate a configuration file.
  • step S711 is executed, and the network controller rejects the resource scheduling request for the service.
  • Steps S708-S710 are similar to steps S402-S404 in FIG. 4 , for details, please refer to the description of the above-mentioned steps S402-S404 , which are not repeated here for brevity.
  • the embodiments of the present application optimize the rationality of global communication resource allocation, make global resource allocation more flexible, and further improve service quality.
  • the present application also provides another architecture based on a cross-platform service QoS guarantee mechanism.
  • the architecture includes application layer, vehicle OS layer, network control layer and hardware layer.
  • the communication network of the vehicle includes an in-vehicle communication network and an out-of-vehicle communication network
  • the in-vehicle OS layer includes in-vehicle service providers (ECUs that provide in-vehicle services) and out-of-vehicle service agents. (ECU providing off-board service).
  • the configuration file generation module in the network control layer is used to manage the scheduling information of in-vehicle and out-of-vehicle network communication resources, realize the joint network topology control inside and outside the vehicle, and maintain the mapping between the server ECU and the client ECU in the entire in-vehicle and outside network topology. relationship, and perform end-to-end resource scheduling based on the global information of the network inside and outside the vehicle.
  • the off-vehicle communication network can be, for example, a vehicle-to-everything (V2X) communication network, such as a vehicle-to-vehicle (V2V) communication network, a vehicle-to-base Vehicle-to-vehicle (V2I) communication network, vehicle-to-pedestrian (V2P) communication network, vehicle-to-network (V2N) communication network, etc.
  • V2X vehicle-to-everything
  • V2X vehicle-to-everything
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-base Vehicle-to-vehicle
  • V2P vehicle-to-pedestrian
  • V2N vehicle-to-network
  • the resource scheduling method based on the architecture shown in Fig. 8 is similar to the methods shown in Fig. 4 and Fig. 7, the difference is that the server ECU includes an in-vehicle server ECU and an out-of-vehicle server ECU, then the corresponding service resources
  • the scheduling message includes the matching information of the in-vehicle server ECU and the client ECU and the identification information of the in-vehicle service, and the matching information of the out-of-vehicle server ECU and the client ECU and the identification information of the out-of-vehicle service.
  • the communication path information of the server ECU and the client ECU includes the communication path information of the in-vehicle server ECU and the client ECU and the communication path information of the off-vehicle server ECU and the client ECU.
  • the communication path information of the in-vehicle server ECU and the client ECU is determined based on at least the matching information of the in-vehicle server ECU and the client ECU, the global network topology information and the allocated in-vehicle communication resource information.
  • the specific determination method can be found in the above figure. For the sake of brevity, the detailed description in step S402 in 4 is not repeated here.
  • the communication path information of the off-board server ECU and the client ECU is determined based on at least the matching information of the off-board server ECU and the client ECU, the global network topology information and the allocated off-board communication resource information.
  • the specific determination method is the same as that in Figure 4.
  • the method for determining the communication path in step S402 is similar, which is not repeated here for brevity.
  • the QoS of the service includes the QoS of the in-vehicle service and the QoS of the out-of-vehicle service
  • the resource allocation strategy of the service correspondingly includes the resource allocation strategy of the in-vehicle service and the resource allocation strategy of the out-of-vehicle service.
  • the configuration file of the in-vehicle service is determined by the configuration file generation module in FIG. 8 based on the communication path information of the in-vehicle server ECU and the client ECU and the QoS information of the in-vehicle service.
  • the configuration file of the out-of-vehicle service is determined by the configuration file generation module in Figure 8 based on the communication path information of the out-of-vehicle server ECU and the client ECU and the QoS information of the out-of-vehicle service.
  • the configuration file generation module in the embodiment of the present application may be physically separated into a configuration file generation module for in-vehicle services and a configuration file generation module for out-of-vehicle services, or may be integrated on the same hardware, but logically divided into in-vehicle services
  • the configuration file generation module of the in-vehicle service and the configuration file generation module of the out-of-vehicle service wherein, the configuration file generation module of the in-vehicle service is used to determine the vehicle based on the communication path information of the in-vehicle server ECU and the client ECU and the QoS information of the in-vehicle service.
  • configuration file for the service The configuration file generation module of the off-board service is used to determine the configuration file of the off-board service based on the communication path information of the off-board server ECU and the client ECU and the QoS information of the off-board service.
  • 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. Schedule execution.
  • the configuration file generation module of the off-vehicle service generates a second configuration file, and sends the second configuration file to the related ECUs outside the vehicle. Schedule execution.
  • the embodiment of the present application optimizes the mapping relationship between the server ECU and the client ECU in the entire in-vehicle and out-of-vehicle network topology through a cross-platform service QoS guarantee mechanism based on the network topology control inside and outside the vehicle, so that based on the global network information, the mapping relationship between the server ECU and the client ECU is optimized. End-to-end resource scheduling further improves service quality.
  • the embodiments of the present application also provide a network controller applied to a 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:
  • the communication module 910 is 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 the in-vehicle service demander to request a first service from the service provider, and further use for indicating a requested quality of service, the requested quality of service being the quality of service for the first service requested by the service provider from the network controller;
  • a quality of service determination module 920 configured to determine the quality of service for the first service according to the resource scheduling request message
  • the configuration file generation module 930 is configured to generate a configuration file according to the global network topology information used to indicate the connection relationship between the electronic control units in the vehicle, the allocated communication resources and the quality of service for the first service. a configuration file, where the configuration file is used to indicate a resource allocation strategy, and the resource allocation strategy is 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 used for enabling the service provider to provide the service demander with all the information. the electronic control unit of the first service.
  • the configuration file generation module 930 is configured to use the global network topology information for indicating the connection relationship between multiple electronic control units in the vehicle, the allocated communication resources and the For the quality of service of the first service, a configuration file is generated, including the configuration file generation module 930 for:
  • the service requirement is determined according to the global network topology information indicating the connection relationship between the plurality of electronic control units in the vehicle, the allocated communication resources and the quality of service for the first service a communication path between a provider and the service provider; wherein the at least part of the electronic control unit is located on the communication path; generating a configuration based on the communication path and the quality of service for the first service document.
  • the quality of service for the first service is determined through a negotiation process between the network controller and the service provider.
  • the quality of service determining 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, wherein the negotiation request message is used to instruct the network controller to the quality of service proposed by the service provider, and the negotiation response message is used to instruct the service provider to accept the proposed quality of service;
  • the quality of service determination module 920 is further configured to determine that the suggested quality of service is the quality of service for the first service.
  • the service provider is an electronic control unit used to act as an off-board service
  • the first service is the off-board service
  • the off-board service is used to provide all the services to the vehicle.
  • the allocated communication resources include resources for in-vehicle communication and resources for out-of-vehicle communication.
  • the network controller, the service provider and the service demander are electronic control units in the vehicle.
  • the network controller 900 may correspond to executing the methods described in the embodiments of the present application, and the above-mentioned and other operations and/or functions of the various modules in the network controller 900 are in order to implement the methods shown in FIG. 4 and FIG. 7 , respectively. For the sake of brevity, the corresponding processes of the respective methods are not repeated here.
  • Embodiments of the present application also provide a vehicle, which has an electronic and electrical system composed of a plurality of electronic control units (ECUs), and the electronic and electrical system may be based on a traditional distributed electronic and electrical architecture, a domain controller architecture, or an electronic and electrical system based on central computing. Electrical architecture implementation.
  • ECUs electronice control units
  • domain means that the vehicle electronic system is divided into several functional blocks according to the functions, and the system architecture inside each functional block is built by the domain controller.
  • the ECUs within each domain are interconnected.
  • the CAN or FlexRay communication bus can be used within each domain to realize the interconnection between each ECU in the domain.
  • Communication connection between different domains, for example, each domain undertakes the task of information exchange through Ethernet as the backbone network to realize interconnection between different domains.
  • the electronic and electrical architecture based on central computing is to separate the corresponding software systems from the ECUs scattered in various places and reintegrate them into the corresponding domain controllers.
  • Each domain controller communicates with the central controller.
  • the central controller Communication with other domain controllers via a central gateway and Ethernet.
  • the network controller in FIG. 9 can be deployed in an ECU in the vehicle to ensure the quality of service of the global business flow of the vehicle.
  • the network controller in FIG. 9 can be deployed in an ECU in the vehicle to ensure the quality of service of the global business flow of the vehicle.
  • the network controller in FIG. 9 can be deployed in the domain controller to ensure the quality of service of the global service flow of the vehicle.
  • the specific implementation method refer to the descriptions in FIG. 4 and FIG. 7 , which are not repeated here for brevity.
  • the network controller in FIG. 9 can be deployed in the central controller to ensure the quality of service of the global service flow of the vehicle.
  • the network controller in FIG. 9 can be deployed in the central controller to ensure the quality of service of the global service flow of the vehicle.
  • Vehicles include various electronic devices.
  • various sensors include, for example, cameras for capturing images of the surroundings of the vehicle and collecting image data; radars for acquiring position information, distance information, speed information, etc. of objects (eg, vehicles ahead, pedestrians, etc.).
  • the vehicle may also include various control systems, such as an engine management system for producing power, a transmission control system for transferring the power produced by the engine to the wheels, a braking system for slowing or stopping the vehicle, and a such as body control systems that provide driver comfort or ensure driver safety.
  • various control systems such as an engine management system for producing power, a transmission control system for transferring the power produced by the engine to the wheels, a braking system for slowing or stopping the vehicle, and a such as body control systems that provide driver comfort or ensure driver safety.
  • ECUs are deployed in various electronic devices and various control systems on the vehicle, and are used to control various electronic devices and various control systems to realize various functions of the vehicle and realize the connection between various electronic devices and various control systems. communication connection.
  • the server ECU1 is deployed in the radar, and the client ECU2 is deployed in the braking system
  • ECU2 sends a subscription/call request to ECU1
  • ECU2 sends a resource scheduling request message to the network controller
  • the network controller generates a resource scheduling strategy in the global dimension, and generates a configuration file, and sends the configuration file to the relevant ECU
  • the relevant ECU performs routing forwarding and business resource scheduling according to the configuration file, so that ECU1 can provide radar to ECU2. service, that is, the ECU1 sends the environmental information around the vehicle acquired by the radar to the ECU2.
  • the braking system controls the running speed of the vehicle according to the external information of the vehicle acquired by the ECU2.
  • the embodiment of the present application also provides a chip.
  • FIG. 10 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • 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 connected in communication, and the communication can also be realized by other means such as wireless transmission.
  • the communication interface 1003 is used to communicate with other ECUs, such as receiving resource scheduling request messages sent by other ECUs, sending configuration files to related ECUs, etc.;
  • the memory 1002 stores executable program codes, and the processor 1001 can call the memory 1002
  • the stored program code executes the resource scheduling method in the foregoing method embodiments.
  • the processor 1001 may be a central processing unit CPU, and the processor 1001 may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), application-specific integrated circuits (application-specific integrated circuits) specific integrated circuit, ASIC), field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processors
  • ASIC application-specific integrated circuits
  • FPGA field programmable gate array
  • a general purpose processor may be a microprocessor or any conventional processor or the like.
  • the memory 1002 may include read only memory and random access memory, and provides instructions and data to the processor 1001 .
  • Memory 1002 may also include non-volatile random access memory.
  • memory 1002 may also store training data sets.
  • the memory 1002 may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • Double data rate synchronous dynamic random access memory double data date SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous link dynamic random access memory direct rambus RAM, DR RAM
  • the chip 1000 according to the embodiment of the present application can execute the resource scheduling method shown in FIG. 4 and FIG. 7 according to the embodiment of the present application.
  • FIG. 4 and FIG. 7 see the specific description of FIG. 4 and FIG. 7 above. For brevity , and will not be repeated here.
  • resource scheduling method, network controller and chip mentioned above can also be applied to other similar embedded systems (eg, industrial control systems, medical systems, critical infrastructure systems) in addition to vehicles. etc.) to ensure the quality of service in the system.
  • other similar embedded systems eg, industrial control systems, medical systems, critical infrastructure systems
  • the present application also provides a computer-readable storage medium, including computer instructions, which, when executed by a processor, implement the resource scheduling method described above.
  • the present application also provides a computer program product that, when the computer program product runs on a processor, implements the resource scheduling method described above.
  • a software module can be placed in random access memory (RAM), internal memory, read only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other in the technical field. in any other known form of storage medium.
  • RAM random access memory
  • ROM read only memory
  • electrically programmable ROM electrically erasable programmable ROM
  • registers hard disk, removable disk, CD-ROM, or any other in the technical field. in any other known form of storage medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente demande concerne un véhicule et son procédé de planification de ressources. Le véhicule comprend un demandeur de service, un prestataire de services et un contrôleur de réseau. Le demandeur de service peut envoyer un message de demande de service au prestataire de services ; le prestataire de services reçoit le message de demande de service, et peut générer un message de demande de planification de ressources selon le message de demande de service, et le prestataire de services envoie le message de demande de planification de ressources au contrôleur de réseau ; et le contrôleur de réseau détermine, en fonction du message de demande de planification de ressources, une qualité de service utilisée pour un premier service, et génère un fichier de configuration selon des informations de topologie de réseau globale servant à indiquer une relation de connexion entre une pluralité d'unités de commande électronique dans le véhicule, des ressources de communication attribuées et la qualité de service utilisée pour le premier service, le fichier de configuration servant à indiquer une politique d'attribution de ressources, et la politique d'attribution de ressources servant à la mise en œuvre du prestataire de services fournissant le premier service au demandeur de service. Au moyen du procédé de planification de ressources fourni dans la présente demande, une garantie de qualité de service d'un flux de service global d'un véhicule est obtenue.
PCT/CN2022/080016 2021-04-02 2022-03-09 Véhicule et son procédé de planification de ressources WO2022206327A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110359885.4 2021-04-02
CN202110359885.4A CN115190179B (zh) 2021-04-02 一种车辆及其资源调度方法

Publications (1)

Publication Number Publication Date
WO2022206327A1 true WO2022206327A1 (fr) 2022-10-06

Family

ID=83457924

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/080016 WO2022206327A1 (fr) 2021-04-02 2022-03-09 Véhicule et son procédé de planification de ressources

Country Status (1)

Country Link
WO (1) WO2022206327A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106452841A (zh) * 2016-09-13 2017-02-22 中国电子科技集团公司第三十二研究所 在机器人操作系统中使用传输服务质量的方法
CN110383773A (zh) * 2017-01-05 2019-10-25 伽德诺克斯信息技术有限公司 具有相关设备的被配置成基于面向服务的体系结构实施集中式服务ecu的专门编程的计算系统及其使用方法
US20210029761A1 (en) * 2018-06-14 2021-01-28 Lg Electronics Inc. Method and apparatus for performing sidelink communication by ue in nr v2x

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106452841A (zh) * 2016-09-13 2017-02-22 中国电子科技集团公司第三十二研究所 在机器人操作系统中使用传输服务质量的方法
CN110383773A (zh) * 2017-01-05 2019-10-25 伽德诺克斯信息技术有限公司 具有相关设备的被配置成基于面向服务的体系结构实施集中式服务ecu的专门编程的计算系统及其使用方法
US20210029761A1 (en) * 2018-06-14 2021-01-28 Lg Electronics Inc. Method and apparatus for performing sidelink communication by ue in nr v2x

Also Published As

Publication number Publication date
CN115190179A (zh) 2022-10-14

Similar Documents

Publication Publication Date Title
Truong et al. Software defined networking-based vehicular adhoc network with fog computing
Shah et al. vFog: A vehicle-assisted computing framework for delay-sensitive applications in smart cities
WO2022061843A1 (fr) Procédé et appareil de valorisation de véhicule
CN109906585B (zh) 网络切片的管理方法、管理单元及系统
Hussain et al. Realization of VANET-based cloud services through named data networking
CN115242565B (zh) 一种基于autosar实现dds通信的系统架构、通信方法及设备
WO2021051882A1 (fr) Procédé, appareil, système, et dispositif de transfert de paquet, et support de stockage
CN110650197B (zh) 信号传输方法及装置
CN112740642B (zh) 通信方法及多接入边缘计算服务器
Farzaneh et al. An ontology-based Plug-and-Play approach for in-vehicle Time-Sensitive Networking (TSN)
Cakır et al. A QoS aware approach to service-oriented communication in future automotive networks
CN112995315B (zh) 一种面向服务的智能汽车车载网络QoS保障方法
CN109981473B (zh) 一种实时消息总线系统
Ernst et al. Application-centric network management-addressing safety and real-time in v2x applications
US11025753B2 (en) Method and device for inter-process communication in network
WO2022206327A1 (fr) Véhicule et son procédé de planification de ressources
CN113765825A (zh) 一种链式业务流调度的规划方法和系统架构
CN115190179B (zh) 一种车辆及其资源调度方法
Ayaz et al. [Retracted] A Content Dissemination Technique Based on Priority to Improve Quality of Service of Vehicular Ad Hoc Networks
WO2024026593A1 (fr) Procédé de commande coopérative de véhicule et dispositif associé
WO2023221131A1 (fr) Procédé et dispositif de commande de véhicule, et véhicule
Wagner et al. Service-oriented communication for controller area networks
WO2021072647A1 (fr) Procédé, dispositif et système de configuration de ressources pour tranches de service embarqué
Johansson et al. Enabling tomorrow’s road vehicles by service-oriented platform patterns
Wagner et al. A CAN-based communication model for Service-oriented Driver Assistance Systems

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22778511

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22778511

Country of ref document: EP

Kind code of ref document: A1