CN114268666B - Universal domain controller supporting Service Oriented Architecture (SOA), vehicle and interaction system - Google Patents
Universal domain controller supporting Service Oriented Architecture (SOA), vehicle and interaction system Download PDFInfo
- Publication number
- CN114268666B CN114268666B CN202111493724.0A CN202111493724A CN114268666B CN 114268666 B CN114268666 B CN 114268666B CN 202111493724 A CN202111493724 A CN 202111493724A CN 114268666 B CN114268666 B CN 114268666B
- Authority
- CN
- China
- Prior art keywords
- data
- real
- soa
- module
- protocol stack
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 230000003993 interaction Effects 0.000 title claims description 10
- 102200074554 rs4304840 Human genes 0.000 claims abstract description 29
- 238000012545 processing Methods 0.000 claims abstract description 17
- 238000006243 chemical reaction Methods 0.000 claims description 47
- 230000006854 communication Effects 0.000 claims description 29
- 238000004891 communication Methods 0.000 claims description 28
- 238000000034 method Methods 0.000 claims description 18
- 230000008569 process Effects 0.000 claims description 14
- 238000013519 translation Methods 0.000 claims description 14
- 230000005540 biological transmission Effects 0.000 claims description 7
- 230000007246 mechanism Effects 0.000 claims description 5
- 230000002452 interceptive effect Effects 0.000 claims description 3
- 230000006870 function Effects 0.000 description 15
- 238000010586 diagram Methods 0.000 description 10
- 238000011161 development Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000012795 verification Methods 0.000 description 3
- 102100034112 Alkyldihydroxyacetonephosphate synthase, peroxisomal Human genes 0.000 description 2
- 101000799143 Homo sapiens Alkyldihydroxyacetonephosphate synthase, peroxisomal Proteins 0.000 description 2
- 206010063385 Intellectualisation Diseases 0.000 description 2
- 238000000848 angular dependent Auger electron spectroscopy Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 239000011159 matrix material Substances 0.000 description 2
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 238000004378 air conditioning Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000000547 structure data Methods 0.000 description 1
Abstract
The application discloses a universal domain controller supporting an SOA (service oriented architecture), which is applied to a vehicle and comprises an S32G chip provided with an SOA protocol stack module set, wherein the SOA protocol stack module set comprises a DDS protocol stack module, a SOMEIP protocol stack module and an MQTT protocol stack module, the MQTT protocol stack module is used for analyzing data received by the vehicle from a cloud server to obtain data to be processed, the data to be processed comprises first data and second data, the real-time requirement of the first data is high, and the real-time requirement of the second data is low; the SOMEIP protocol stack module is used for processing the second data; the DDS protocol stack module is used for processing the first data. Therefore, the vehicle is integrated with the universal domain controller based on the SOA, so that the vehicle has better expandability, and the intelligent level of the vehicle is improved.
Description
Technical Field
The present application relates to the field of vehicle technologies, and in particular, to a universal domain controller, a vehicle, and an interaction system supporting Service-oriented architecture (SOA).
Background
At present, the whole vehicle communication usually adopts a signal communication mode. With the development of intellectualization and networking of vehicles, services for realizing different functions on vehicles are increasing. In the signal-based communication mode, any new function needs to be realized by changing the communication matrix on the vehicle, and meanwhile, the corresponding electronic control unit (Electronic Control Unit, ECU) also needs to be correspondingly updated with software, so that the workload is large and inflexible.
Based on this, it is needed to provide a controller capable of flexibly and conveniently coping with the requirements of functions addition, deletion, change and the like on a vehicle so as to improve the level of intellectualization of the vehicle.
Disclosure of Invention
The embodiment of the application provides a universal domain controller supporting a Service Oriented Architecture (SOA), a vehicle and an interactive system, which can flexibly and conveniently cope with the requirements of adding, deleting, changing and the like of functions on the vehicle, and improve the intelligent level of the vehicle.
In a first aspect, an embodiment of the present application provides a generic domain controller supporting a service oriented architecture SOA, the generic domain controller being applied to a vehicle, the generic domain controller comprising: an S32G chip, where an SOA protocol stack module set is deployed on the S32G chip, and the SOA protocol stack module set includes: a real-time system oriented data distribution service (Data Distribution Service, DDS) protocol stack module, an internet protocol service oriented extensible middleware (Scalable service-Oriented Middleware over Internet Protocol, SOMEIP) protocol stack module, and a message queue telemetry transport (Message Queuing Telemetry Transport, MQTT) protocol stack module, wherein:
The MQTT protocol stack module is used for analyzing the data received by the vehicle from the cloud server to obtain data to be processed, wherein the data to be processed comprises first data and second data, the real-time requirement in the first data is larger than a preset first real-time threshold, and the real-time requirement in the second data is not larger than the first real-time threshold;
the SOMEIP protocol stack module is configured to process the second data;
And the DDS protocol stack module is used for processing the first data.
In some implementations, the S32G chip includes an M7 core, an a53 core, a cross-platform communication framework IPCF module, and a packet forwarding engine PFE module, wherein:
the IPCF module is configured to transmit third data, where the real-time requirement of the third data is greater than a preset second real-time threshold and the data size of the third data is less than a preset data size threshold, between the M7 core and the a53 core;
The PFE module is configured to transmit fourth data having a real-time requirement not greater than the second real-time threshold between the M7 core and the a53 core.
As an example, the generic domain controller also includes a Switch,
And the Switch is used for transmitting fifth data with the real-time requirement not greater than the second real-time threshold between the M7 core and the A53 core when the working condition of the S32G chip exceeds a preset condition, wherein the working condition comprises a load rate and a temperature.
As an example, the set of SOA protocol stack modules further includes an inter-core communication module,
And the inter-core communication module is used for grouping and unpacking data transmitted between the M7 core and the A53 core.
In some implementations, the set of SOA protocol stack modules includes a first translation module,
The first conversion module is configured to perform format conversion on data transmitted between the MQTT protocol stack module and the SOMEIP protocol stack module.
In some implementations, the set of SOA protocol stack modules includes a second translation module,
The second conversion module is configured to perform format conversion on data transmitted between the MQTT protocol stack module and the DDS protocol stack module.
As an example, the second translation module is an MQTT/DDS translation module.
As another example, the second translation module includes an MQTT/SOMEIP translation module and a SOMEIP/DDS translation module.
In some implementations, the set of SOA protocol stack modules further includes a DDS signal conversion module and SOMEIP signal conversion module,
The DDS signal conversion module is used for converting the first result data processed by the DDS protocol stack module to a first signal;
The SOMEIP signal conversion module is configured to convert the second result data processed by the SOMEIP protocol stack module to a second signal.
In some implementations, the set of SOA protocol stack modules is deployed to the a53 core of the S32G chip.
In some implementations, the generic domain controller further comprises: the memory unit is provided with a memory unit,
The storage unit is used for storing the corresponding relation between different services of the vehicle and the real-time grade, the real-time requirement is the real-time grade corresponding to the service to which the data to be processed belongs, the first real-time threshold is a target real-time grade, the target real-time grade is one of a plurality of real-time grades in the storage unit, the real-time requirement is larger than a preset first real-time threshold and is higher than the target real-time grade, and the real-time requirement is not larger than the first real-time threshold and is not higher than the target real-time grade.
In some implementations, the generic domain controller further comprises: the memory unit is provided with a memory unit,
The storage unit is configured to store correspondence between different services of the vehicle and processing protocols, where the processing protocols include a DDS protocol and a SOMEIP protocol, the real-time requirement is greater than a preset first real-time threshold and is corresponding to the DDS protocol for services to which the data to be processed belongs, and the real-time requirement is not greater than the first real-time threshold and is corresponding to the SOMEIP protocol for services to which the data to be processed belongs.
In some implementations, the DDS protocol stack module is further configured to select a supported QoS mechanism for data processing according to the configured DDS-quality of service QoS support list.
In a second aspect, an embodiment of the present application further provides a vehicle, where the vehicle includes the generic domain controller supporting the service oriented architecture SOA provided in the first aspect.
In a third aspect, an embodiment of the present application further provides an interaction system, where the interaction system includes a vehicle and a cloud server, where:
The cloud server is used for carrying out data interaction based on an MQTT protocol and the vehicle;
The vehicle is configured to interact with the cloud server through the generic domain controller supporting the service oriented architecture SOA provided in the first aspect based on the MQTT protocol.
From this, the embodiment of the application has the following beneficial effects:
The embodiment of the application provides a universal domain controller supporting a Service Oriented Architecture (SOA), which is applied to a vehicle and comprises the following components: an S32G chip, where an SOA protocol stack module set is deployed on the S32G chip, and the SOA protocol stack module set includes: the system comprises a DDS protocol stack module, a SOMEIP protocol stack module and an MQTT protocol stack module, wherein the MQTT protocol stack module is used for analyzing data received by the vehicle from a cloud server to obtain data to be processed, the data to be processed comprises first data and second data, the real-time requirement in the first data is larger than a preset first real-time threshold value, and the real-time requirement in the second data is not larger than the first real-time threshold value; the SOMEIP protocol stack module is configured to process the second data; and the DDS protocol stack module is used for processing the first data. In this way, different functional units (called services) of an application program are split by using an SOA, so that services built in various systems can interact in a unified and universal mode, a universal domain controller based on the SOA is designed on a vehicle, a plurality of SOA middleware is deployed on the universal domain controller, the cloud server is enabled to process data sent by an MQTT protocol in the vehicle by using a DDS or SOMEIP protocol, specifically, the data in the vehicle are classified into real-time low-service and real-time high-service according to real-time requirements of application scenes, the data corresponding to the real-time low-service is processed by using a SOMEIP protocol stack module corresponding to a SOMEIP protocol, and the data corresponding to the real-time high-service is processed by using a DDS protocol stack module corresponding to the DDS protocol, so that the real-time requirements in the SOA are met. Therefore, the SOA-based universal domain controller is integrated on the vehicle, on one hand, the software multiplexing degree is improved, the application development period and personnel investment are shortened, on the other hand, the software coupling degree is reduced, the influence on other modules is small when software update or hardware update occurs in the vehicle, and in addition, the vehicle has better expandability and is more beneficial to adding, deleting or modifying more functions on the vehicle. In summary, the universal domain controller enables operations such as adding, deleting, changing and the like of functions on the vehicle to be more flexible and convenient, and improves the intelligent level of the vehicle.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments described in the present invention, and other drawings may be obtained according to these drawings for those of ordinary skill in the art.
Fig. 1 is a schematic diagram of a hardware architecture of a generic domain controller according to an embodiment of the present application;
fig. 2 is a schematic diagram of a hardware architecture of an example of a generic domain controller according to an embodiment of the present application;
fig. 3 is a schematic diagram of a software architecture of a generic domain controller according to an embodiment of the present application;
fig. 4 is a schematic architecture diagram of an SOA middleware according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a generic domain controller supporting an SOA according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an interactive system according to an embodiment of the present application.
Detailed Description
In order that the above-recited objects, features and advantages of the present application will become more readily apparent, a more particular description of embodiments of the application will be rendered by reference to the appended drawings and appended drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting thereof. In addition, for convenience of description, only a part, not all, of the structures related to the present application are shown in the drawings.
Different from the traditional architecture of the vehicle based on signal communication, various functions of the vehicle are corresponding to different service components according to the service-oriented design concept, each service has unique and independent identity, and the service middleware is used for completing the release of the service, the subscription of other services and the communication work with other services. Therefore, the SOA can well solve the problem that the whole communication matrix needs to be changed due to the addition, deletion or change of certain functions in the traditional architecture. In addition, due to the "interface standard accessible" nature of the SOA, deployment of service components is no longer dependent on the particular operating system and programming language, enabling "soft-hard separation" of components.
Based on this, in order to improve flexible deployment of various services and convenient adjustment of functions on a vehicle, an embodiment of the present application provides a general domain controller supporting SOA, where the general domain controller is applied to a vehicle, and the general domain controller includes: an S32G chip, where an SOA protocol stack module set is deployed on the S32G chip, and the SOA protocol stack module set includes: the system comprises a DDS protocol stack module, a SOMEIP protocol stack module and an MQTT protocol stack module, wherein the MQTT protocol stack module is used for analyzing data received by the vehicle from a cloud server to obtain data to be processed, the data to be processed comprises first data and second data, the real-time requirement in the first data is larger than a preset first real-time threshold value, and the real-time requirement in the second data is not larger than the first real-time threshold value; the SOMEIP protocol stack module is configured to process the second data; and the DDS protocol stack module is used for processing the first data.
In this way, different functional units (called services) of an application program are split by using an SOA, so that services built in various systems can interact in a unified and universal mode, a universal domain controller based on the SOA is designed on a vehicle, a plurality of SOA middleware is deployed on the universal domain controller, the cloud server is enabled to process data sent by an MQTT protocol in the vehicle by using a DDS or SOMEIP protocol, specifically, the data in the vehicle are classified into real-time low-service and real-time high-service according to real-time requirements of application scenes, the data corresponding to the real-time low-service is processed by using a SOMEIP protocol stack module corresponding to a SOMEIP protocol, and the data corresponding to the real-time high-service is processed by using a DDS protocol stack module corresponding to the DDS protocol, so that the real-time requirements in the SOA are met. Therefore, the SOA-based universal domain controller is integrated on the vehicle, so that on one hand, the software multiplexing degree is improved, the application development period and personnel investment are shortened, on the other hand, the software coupling degree is reduced, the influence on other modules is small when software update or hardware update occurs in the vehicle, and in addition, the vehicle has better expandability, and more functions are added, deleted or modified on the vehicle. In summary, the universal domain controller enables operations such as adding, deleting, changing and the like of functions on the vehicle to be more flexible and convenient, and improves the intelligent level of the vehicle.
In order to meet the increasing computational demands of vehicles, embodiments of the present application contemplate using heterogeneous processor S32G chips as the master chip of a universal domain controller, which may be, for example, S32G274A chips. The heterogeneous processor of the S32G chip is used, so that the calculation power requirement and the real-time requirement of the vehicle are mainly considered. The system CAN process data with extremely high real-time performance such as brake, accelerator and the like on a controller area network (Controller Area Network, CAN) during M7 verification in the S32G chip, and the high computing power of the A53 core in the S32G chip CAN realize complex algorithms such as an automatic control algorithm of an air conditioner. In the S32G chip, the A53 core can operate LINUX system, and the M7 core operates.
Taking an S32G chip as an example, an S32G274A chip is used to introduce a hardware architecture and a software architecture of the universal domain controller provided by the embodiment of the present application.
The S32G274A chip includes 3 ARM M7 cores supporting real-time systems and 4 ARM A53 cores with high performance computing power. As one example, the M7 core employs a real-time operating system, such as an RTOS system, and the A53 core employs a LINUX or QNX system, such that the S32G274A chip combines real-time and high computational power requirements.
Fig. 1 is a schematic diagram of a hardware architecture of a generic domain controller according to an embodiment of the present application, referring to fig. 1, the generic domain controller 100 may include: the S32G274A chip 110, the power module 120, the storage module 130, the Ethernet Switch (Switch) 140, the interface module 150, the real-time clock module 160, the security module 170, and the CAN communication module 180. Wherein the power module 120 provides power to various modules on the universal domain controller 100, such as the PMIC 120. The storage module 130 may include a running memory 131 and a local storage 132, where the running memory 131 is configured to provide running memory for 4A 53 cores in the S32G274A chip 110, and for example, the running memory 131 may be LPDDR4 with a capacity of 2GB; the local storage 132 is used to provide storage space, and for example, the local storage 132 may be EMMC, with a specification of 32GB. Switch 140 is used to interface the a53 core with the M7 core within S32G274A chip 110, as well as to interface S32G274A chip 110 and other chips, e.g., switch 140 may provide a 6-way 100base-T1 interface. Meanwhile, the generic domain controller 100 further includes an additional interface module 150, and the interface module 150 may provide, for example, a three-way 1000base-T1 interface, directly connected to the S32G274A chip 110. The real time clock module 160 provides a timed wakeup source and a high precision clock, such as a high precision RTC 160, for the generic domain controller 100. The security module 170 is used to provide reliable data security for the domain controller 100, for example, may be an external HSM, and support secure encryption of national secret information. CAN communication module 180 may be, for example, CAN FD 16.
Wherein, the S32G274A chip 110 includes: 3M 7 cores 111, 4A 53 cores 112, a packet forwarding engine (Packet Forwarding Engine, PFE) module 113, and a cross-platform communication framework (Inter-Platform communication framework, IPCF) module 114. The PFE module 113 is configured to implement transmission of data with a larger data size between the a53 core and the M7 core; IPCF module 114 is configured to implement transmission of data with smaller data size and high real-time transmission requirement between the a53 core and the M7 core, and typically, the data is transmitted in a signal form.
In the hardware architecture diagram of the generic domain controller shown in fig. 1, each module is replaced by a specific component that implements the function of the module, and the hardware architecture diagram of a corresponding example is shown in fig. 2.
Fig. 3 is a schematic software architecture of a generic domain controller according to an embodiment of the present application, referring to fig. 3, the generic domain controller 100 includes a hardware platform 10, and the software architecture may be divided into four layers: a driver software layer 20, an automotive open system architecture (AUTOSAR) base software platform 30, software middleware 40, and an application layer 50. The driver software layer 20 may include a control abstraction layer (MCAL) 21, a Linux kernel & driver 22, and a virtual hardware platform (Hypervisor) 23; the AUTOSAR base software platform 30 may include an AUTOSAR classical platform 31 and an AUTOSAR adaptive platform 32; software middleware 40 includes SOA middleware 41 and other middleware 42; the application layer 50 includes, but is not limited to: a service 51 corresponding to the vehicle body, a service 52 corresponding to the chassis, a service 53 corresponding to the power, and a service 54 corresponding to the gateway. It should be noted that, in the embodiment of the present application, the general domain controller supports the SOA, and the core is the SOA middleware 41, which can provide unified application interfaces meeting different application scenarios, implement universality, and the application layer arranges different software modules as independent SOA middleware according to different application fields. In the embodiment of the application, the SOA middleware is also called an SOA protocol stack module.
In some embodiments, the vehicle's corresponding cloud server communicates with the vehicle using the MQTT protocol, while the vehicle interior may support DDS and SOMEIP. The universal domain controller in the embodiment of the application enables the interior of the vehicle to be classified into low-instantaneity-requirement service and high-instantaneity-requirement service according to the instantaneity requirement of an application scene, the data of the low-instantaneity-requirement service can use SOMEIP protocol in the interior of the vehicle, the data of the high-instantaneity-requirement service can be processed by using DDS protocol in the interior of the vehicle, and the DDS protocol has the advantages compared with SOMEIP protocol: the DDS protocol supports priority adopted when a designated transmission layer sends a message through a plurality of QoS mechanisms, and divides whether the transmission time of a sample from a publisher to a subscriber is an unacceptable delay interval, so that the real-time requirement in an SOA architecture is met, and the SOMEIP protocol has no real-time characteristic.
For the SOA middleware 41, some SOA middleware that can be included in the generic domain controller is designed according to the embodiments of the present application, for example, as shown in fig. 4, and may include, but not limited to:
The MQTT protocol stack module 401 is configured to be responsible for analyzing data corresponding to a service issued by the MQTT protocol and sent by the cloud server.
The DDS protocol stack module 402 is configured to be responsible for analyzing data corresponding to a service issued by using a DDS protocol in a communication process of a domain controller with a high real-time requirement, such as an advanced driving assistance system (ADVANCED DRIVING ASSISTANCE SYSTEM, ADAS). In the embodiment of the present application, the DDS protocol stack module 402 may also design a DDS-QoS support list, and select a supported QoS mechanism by configuring the DDS-QoS support list, so that the running memory occupation is reduced.
And SOMEIP the protocol stack module 403 is used for load analyzing the data corresponding to the service which is commonly used by the vehicle and has lower real-time requirement.
The MQTT/SOMEIP conversion module 404, which may be deployed at the a53 core, is responsible for format conversion between MQTT protocol data and SOMEIP protocol data.
The MQTT/DDS conversion module 405 may be deployed in the a53 core, and is configured to be responsible for format conversion between MQTT protocol data and DDS protocol data.
SOMEIP/DDS conversion module 406, which may be deployed in the a53 core, is responsible for format conversion between SOMEIP protocol data and DDS protocol data.
SOMEIP signal service conversion module 407, which may be deployed in the a53 core, is responsible for conversion between signals and SOMEIP protocol data.
The DDS signal service conversion module 408 may be disposed in the a53 core, and is configured to be responsible for conversion between signals and DDS protocol data.
The inter-core communication module 409 may be disposed in the a53 core, and is configured to package and unpack data transmitted between the M7 core and the a53 core, for example, be responsible for unpacking a signal transferred from the M7 core and providing the unpack signal to the SOMEIP signal service conversion module 407, and for example, be responsible for packing a signal obtained by converting the SOMEIP signal service conversion module 407 to the M7 core; also, for example, it is responsible for packaging the CAN signal of the M7 core end and forwarding the CAN signal to the a53 core through the PFE module or an external Switch, and for example, it is responsible for unpacking the data forwarded by the a53 core into a signal. It should be noted that, the inter-core communication module 409 adopts a private protocol in a packet unpacking manner, and the protocol is simple and the connection is faster to be established.
In order to facilitate understanding of the specific implementation of the SOA-supporting generic domain controller provided in the embodiments of the present application, the following description will be given with reference to the accompanying drawings.
Fig. 5 is a schematic structural diagram of a generic domain controller supporting SOA according to an embodiment of the present application. Referring to fig. 5, the SOA-enabled generic domain controller 500 is applied to a vehicle 50, and the SOA-enabled generic domain controller 500 includes: an S32G chip 510, where an SOA protocol stack module set a is disposed on the S32G chip 510, where the SOA protocol stack module set a includes: DDS protocol stack module A1, SOMEIP protocol stack module A2 and MQTT protocol stack module A3, wherein:
The MQTT protocol stack module A3 is configured to parse the data received by the vehicle 50 from the cloud server 60 to obtain data to be processed, where the data to be processed includes first data and second data, the real-time requirement in the first data is greater than a preset first real-time threshold, and the real-time requirement in the second data is not greater than the first real-time threshold;
The SOMEIP protocol stack module A2 is configured to process the second data;
the DDS protocol stack module A1 is configured to process the first data.
It will be appreciated that the SOA enabled generic domain controller 500 may require real-time selection of protocols for which services are applicable, e.g., services such as power and advanced driving assistance systems (ADVANCED DRIVING ASSISTANCE SYSTEM, ADAS) may select DDS protocols, comfort configuration (e.g., air conditioning) services may select SOMEIP protocols, windows and partial safety related services (e.g., lights) may select DDS protocols. In a specific implementation, the generic domain controller 500 supporting the SOA may set a protocol selection index table (cloud service may also set this table), and for the data to be processed, the service distribution protocol allocated for use according to the protocol selection index table is processed (for example, serialization or deserialization, and the common ethernet packet or signal is converted and inversed by SOMEIP protocol or DDS protocol).
As an example, the generic domain controller 500 supporting SOA may further include: and a memory cell. The storage unit is used for storing the corresponding relation between different services of the vehicle and the real-time grade, the real-time requirement is the real-time grade corresponding to the service to which the data to be processed belongs, the first real-time threshold is a target real-time grade, the target real-time grade is one of a plurality of real-time grades in the storage unit, the real-time requirement is larger than a preset first real-time threshold and is higher than the target real-time grade, and the real-time requirement is not larger than the first real-time threshold and is not higher than the target real-time grade.
As another example, the generic domain controller 500 supporting SOA may further include: and a memory cell. The storage unit is configured to store correspondence between different services of the vehicle and processing protocols, where the processing protocols include a DDS protocol and a SOMEIP protocol, the real-time requirement is greater than a preset first real-time threshold and is corresponding to the DDS protocol for services to which the data to be processed belongs, and the real-time requirement is not greater than the first real-time threshold and is corresponding to the SOMEIP protocol for services to which the data to be processed belongs.
Wherein serialization (Serialization) refers to the process of converting a data structure or object into a binary string according to a predefined rule; deserialization (Deserialization) refers to the process of reconstructing a binary string into a data structure or object according to the same rules. In AUTOSAR, the expression of data in protocol data units (Protocol Data Unit, PDU) is understood as the conversion of real data from the application layer into a fixed format byte order to achieve the transmission of data over the network. The software component passes data from the application layer to the SOME/IP converter, performing configurable data serialization or de-serialization. A SOME/IP serialization component (sequencer) serializes data in the form of a structure into data in a linear structure; the SOME/IP Deserializer component deserializes the linear structure data into structural data. At the server, the data is transmitted to a COM module of the service layer after being serialized by an SOME/IP sequencer; at the client, the data is passed from the COM module to the SOME/IP Deseriizer for deserialization before entering the RTE layer. The service end of the SOA transmits the serialized data, and the client obtains the actual data which can be used after the data after the SOA is serialized are deserialized.
As an example, the SOA-enabled generic domain controller 500 may place all SOA protocol stack modules (including but not limited to SOMEIP, DDS, and MQTT protocol stack modules) in the SOA protocol stack module set on a high-power a53 core inside the S32G chip 50, the a53 core communicating with the outside via ethernet, and the M7 core communicating with the outside via CAN. In addition, a module for serialization and deserialization can be deployed in the core of a53, and the common ethernet message or the signal transmitted through IPCF is converted and inverted by SOMEIP or DDS protocol.
The S32G chip 510 may include an M7 core, an a53 core, a IPCF module, and a PFE module, where the IPCF module is configured to transmit third data with a real-time requirement greater than a preset second real-time threshold and a data size less than a preset data size threshold between the M7 core and the a53 core; the PFE module is configured to transmit fourth data having a real-time requirement not greater than the second real-time threshold between the M7 core and the a53 core.
It should be noted that, whether the inter-core communication uses IPCF or PFE may be determined by the inter-core real-time index table to be greater than the threshold. In this implementation, the second real-time threshold may be the same as the first real-time threshold or may be different from the first real-time threshold. IPCF is a communication interruption mode of the shared memory so that the speed is faster.
As an example, the SOA-enabled generic domain controller 500 may also include a Switch. The Switch is configured to, when the working condition of the S32G chip 510 exceeds a preset condition, transmit fifth data with a real-time requirement not greater than the second real-time threshold between the M7 core and the a53 core, where the working condition includes a load factor and a temperature.
For services (or called functions) with different instantaneity, software selects an inter-core communication mode according to a pre-configured instantaneity threshold value, and data with large data volume is placed in a PFE or an external Switch.
It will be appreciated that in this example, for services with high real-time requirements, their corresponding data may be transferred between cores through PFE or Switch. And selecting the PFE or the external Switch, a System on Chip (SoC) load value and a temperature value may be periodically determined, if the load rate is too high and/or the temperature is too hot, the working condition is considered to exceed the preset condition, so that the external Switch is selected to perform inter-core communication, and the internal load of the S32G Chip 510 is shared.
As an example, the SOA protocol stack module set a further includes an inter-core communication module A4, where the inter-core communication module A4 is configured to package and unpack data transmitted between the M7 core and the a53 core. Wherein, the M7 core and the A53 core are respectively internally provided with a CAN-Ethernet (ETH) data packet unpacking unit. In the embodiment of the present application, the signal form processed by the M7 core is referred to as "signal", "CAN signal" or "CAN data", the ethernet data is processed by the a53 core, and because the communication mode between the M7 core and the a53 core is the ethernet form, the inter-core communication needs to perform the conversion of packaging or unpacking the CAN data and the ethernet data.
In one possible implementation manner, the SOA protocol stack module set a includes a first conversion module A5, where the first conversion module A5 is configured to perform format conversion on data transmitted between the MQTT protocol stack module A3 and the SOMEIP protocol stack module A2.
In one possible implementation manner, the SOA protocol stack module set a includes a second conversion module A6, where the second conversion module A6 is configured to perform format conversion on data transmitted between the MQTT protocol stack module A3 and the DDS protocol stack module A1. As an example, the second conversion module A6 may be an MQTT/DDS conversion module. As another example, the second conversion module A6 may include MQTT/SOMEIP conversion module a61 and SOMEIP/DDS conversion module a62.
In one possible implementation manner, the SOA protocol stack module set a further includes a DDS signal conversion module A7 and SOMEIP signal conversion module A8. The DDS signal conversion module A7 is configured to convert the first result data processed by the DDS protocol stack module A1 to a first signal; the SOMEIP signal conversion module A8 is configured to convert the second result data processed by the SOMEIP protocol stack module A2 to a second signal. Wherein the first signal and the second signal may be CAN signals, see the description above for serialization and deserialization in the conversion process.
In one possible implementation, considering that the a53 accounting force is much higher than the M7 core, the SOA protocol stack module and its data processing that would require the accounting force can be placed on the a53 core. Thus, as an example, the SOA protocol stack module set a is deployed on the a53 core of the S32G chip 510.
In one possible implementation manner, the DDS protocol stack module A1 is further configured to select a supported QoS mechanism for data processing according to the configured DDS-quality of service QoS support list. The A53 core has different process priorities according to different application real-time requirements, and if the Linux real-time performance is judged not to be satisfied when the architecture is designed, the Linux real-time performance can be replaced by QNX with better real-time performance. The RTOS of the M7 core can set different priorities by different tasks.
Therefore, by utilizing the characteristic that different functional units (called services) of an application program are split by an SOA, services constructed in various systems can interact in a unified and universal mode, a universal domain controller based on the SOA is designed on a vehicle, a plurality of SOA middleware is deployed on the universal domain controller, the fact that data sent by a cloud server through an MQTT protocol are processed in the vehicle by using a DDS or SOMEIP protocol is achieved, specifically, the data corresponding to the real-time low-service are classified into the real-time low-service and the real-time high-service according to the real-time requirement of an application scene in the vehicle, the data corresponding to the real-time low-service are processed by using a SOMEIP protocol stack module corresponding to the SOMEIP protocol, and the data corresponding to the real-time high-service are processed by using a DDS protocol stack module corresponding to meet the real-time requirement in the SOA. Therefore, the SOA-based universal domain controller is integrated on the vehicle, on one hand, the software multiplexing degree is improved, the application development period and personnel investment are shortened, on the other hand, the software coupling degree is reduced, the influence on other modules is small when software update or hardware update occurs in the vehicle, on the other hand, the vehicle has better expandability, and more functions are added, deleted or modified on the vehicle. In summary, the universal domain controller enables operations such as adding, deleting, changing and the like of functions on the vehicle to be more flexible and convenient, and improves the intelligent level of the vehicle.
In addition, the general domain controller supporting SOA provided by the embodiment of the application uses the heterogeneous processor S32G chip, and the characteristics are considered: the system CAN process data (such as brake, accelerator and the like) with extremely high real-time performance on the CAN during the M7 verification, and the high computational power of the A53 core CAN realize complex algorithms, such as an automatic air conditioner algorithm which is very complex and CAN be realized in the A verification, so that the universal domain controller meets the requirements of computational power requirements and real-time performance processing.
In the embodiment of the application, all protocol conversion and real-time judgment of the software can be realized by the SOA software middleware (or the SOA protocol stack module).
In addition, the embodiment of the application also provides a vehicle, which comprises the universal domain controller supporting the service oriented architecture SOA.
In addition, the embodiment of the application further provides an interaction system 1, as shown in fig. 6, the interaction system 1 includes a vehicle 50 and a cloud server 60, wherein:
The cloud server 60 is configured to perform data interaction based on an MQTT protocol and the vehicle;
The vehicle 50 is configured to interact with the cloud server 60 through the generic domain controller 500 supporting the service oriented architecture SOA provided in the embodiment of the present application based on the MQTT protocol.
It should be noted that, the vehicle 50 and the cloud server 60 may be specifically described with reference to fig. 5.
From the above description of embodiments, it will be apparent to those skilled in the art that all or part of the steps of the above described example methods may be implemented in software plus general hardware platforms. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a read-only memory (ROM), a magnetic disk, an optical disk, etc., and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network communication device such as a router) to perform the method according to the embodiments or some parts of the embodiments of the present application.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments and apparatus embodiments, since they are substantially similar to method embodiments, the description is relatively simple, with reference to the description of method embodiments in part. The above-described apparatus and system embodiments are merely illustrative, in which the modules illustrated as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed across multiple network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
The foregoing is merely a preferred embodiment of the present application and is not intended to limit the scope of the present application. It should be noted that modifications and adaptations to the present application may occur to one skilled in the art without departing from its scope.
Claims (14)
1.A generic domain controller supporting a service oriented architecture, SOA, for application to a vehicle, the generic domain controller comprising: an S32G chip, where an SOA protocol stack module set is deployed on the S32G chip, and the SOA protocol stack module set includes: the system comprises a DDS protocol stack module of a data distribution service oriented to a real-time system, a SOMEIP protocol stack module of an extensible middleware oriented to a service based on an Internet protocol and an MQTT protocol stack module of message queue telemetry transmission, wherein:
The MQTT protocol stack module is used for analyzing the data received by the vehicle from the cloud server to obtain data to be processed, wherein the data to be processed comprises first data and second data, the real-time requirement in the first data is larger than a preset first real-time threshold, and the real-time requirement in the second data is not larger than the first real-time threshold;
the SOMEIP protocol stack module is configured to process the second data;
the DDS protocol stack module is used for processing the first data;
The S32G chip comprises an M7 core, an A53 core, a cross-platform communication framework IPCF module and a data Packet Forwarding Engine (PFE) module, wherein:
the IPCF module is configured to transmit third data, where the real-time requirement of the third data is greater than a preset second real-time threshold and the data size of the third data is less than a preset data size threshold, between the M7 core and the a53 core;
The PFE module is configured to transmit fourth data having a real-time requirement not greater than the second real-time threshold between the M7 core and the a53 core.
2. The generic domain controller supporting a service oriented architecture, SOA, of claim 1, further comprising a Switch,
And the Switch is used for transmitting fifth data with the real-time requirement not greater than the second real-time threshold between the M7 core and the A53 core when the working condition of the S32G chip exceeds a preset condition, wherein the working condition comprises a load rate and a temperature.
3. The generic domain controller supporting a service oriented architecture, SOA, as recited in claim 1, wherein said set of SOA protocol stack modules further comprises an inter-core communications module,
And the inter-core communication module is used for grouping and unpacking data transmitted between the M7 core and the A53 core.
4. The generic domain controller supporting a service oriented architecture, SOA, as recited in claim 1, wherein the set of SOA protocol stack modules comprises a first translation module,
The first conversion module is configured to perform format conversion on data transmitted between the MQTT protocol stack module and the SOMEIP protocol stack module.
5. The generic domain controller supporting a service oriented architecture, SOA, as recited in claim 1, wherein the set of SOA protocol stack modules comprises a second translation module,
The second conversion module is configured to perform format conversion on data transmitted between the MQTT protocol stack module and the DDS protocol stack module.
6. The generic domain controller supporting a service oriented architecture, SOA, of claim 5, wherein said second translation module is an MQTT/DDS translation module.
7. The generic domain controller supporting a service oriented architecture, SOA, according to claim 5, wherein said second translation module comprises an MQTT/SOMEIP translation module and a SOMEIP/DDS translation module.
8. The generic domain controller supporting a service oriented architecture, SOA, as set forth in claim 1, wherein said set of SOA protocol stack modules further comprises a DDS signal conversion module and SOMEIP signal conversion module,
The DDS signal conversion module is used for converting the first result data processed by the DDS protocol stack module to a first signal;
The SOMEIP signal conversion module is configured to convert the second result data processed by the SOMEIP protocol stack module to a second signal.
9. The generic domain controller supporting a service oriented architecture, SOA, according to any of claims 1-8, wherein the set of SOA protocol stack modules is deployed on the a53 core of the S32G chip.
10. The generic domain controller supporting a service oriented architecture, SOA, according to any of claims 1-8, further comprising: the memory unit is provided with a memory unit,
The storage unit is used for storing the corresponding relation between different services of the vehicle and the real-time grade, the real-time requirement is the real-time grade corresponding to the service to which the data to be processed belongs, the first real-time threshold is a target real-time grade, the target real-time grade is one of a plurality of real-time grades in the storage unit, the real-time requirement is larger than a preset first real-time threshold and is higher than the target real-time grade, and the real-time requirement is not larger than the first real-time threshold and is not higher than the target real-time grade.
11. The generic domain controller supporting a service oriented architecture, SOA, according to any of claims 1-8, further comprising: the memory unit is provided with a memory unit,
The storage unit is configured to store correspondence between different services of the vehicle and processing protocols, where the processing protocols include a DDS protocol and a SOMEIP protocol, the real-time requirement is greater than a preset first real-time threshold and is corresponding to the DDS protocol for services to which the data to be processed belongs, and the real-time requirement is not greater than the first real-time threshold and is corresponding to the SOMEIP protocol for services to which the data to be processed belongs.
12. The generic domain controller supporting a service oriented architecture, SOA, according to any of the claims 1-8,
The DDS protocol stack module is also used for selecting a supported QoS mechanism for data processing according to the configured DDS-QoS support list.
13. A vehicle comprising a generic domain controller supporting a service oriented architecture, SOA, according to any of the previous claims 1-12.
14. An interactive system comprising a vehicle and a cloud server, wherein:
The cloud server is used for carrying out data interaction based on an MQTT protocol and the vehicle;
The vehicle is configured to interact with the cloud server through the generic domain controller supporting the service oriented architecture SOA according to any of the above claims 1-12 based on the MQTT protocol.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111493724.0A CN114268666B (en) | 2021-12-08 | 2021-12-08 | Universal domain controller supporting Service Oriented Architecture (SOA), vehicle and interaction system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111493724.0A CN114268666B (en) | 2021-12-08 | 2021-12-08 | Universal domain controller supporting Service Oriented Architecture (SOA), vehicle and interaction system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114268666A CN114268666A (en) | 2022-04-01 |
| CN114268666B true CN114268666B (en) | 2024-05-03 |
Family
ID=80826620
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111493724.0A Active CN114268666B (en) | 2021-12-08 | 2021-12-08 | Universal domain controller supporting Service Oriented Architecture (SOA), vehicle and interaction system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114268666B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114884912A (en) * | 2022-04-12 | 2022-08-09 | 阿尔特汽车技术股份有限公司 | Communication method, system, equipment and computer readable storage medium of SOA architecture |
| CN114945038A (en) * | 2022-04-18 | 2022-08-26 | 阿尔特汽车技术股份有限公司 | Communication method, system, equipment and readable storage medium based on SOA architecture |
| CN114844930B (en) * | 2022-04-21 | 2023-06-06 | 重庆长安汽车股份有限公司 | Vehicle-end remote control method and system based on SOA architecture |
| CN114979231B (en) * | 2022-05-30 | 2023-05-26 | 重庆长安汽车股份有限公司 | Vehicle control method and system based on whole vehicle DDS protocol and automobile |
| CN114839959A (en) * | 2022-05-30 | 2022-08-02 | 重庆长安汽车股份有限公司 | Vehicle remote diagnosis method and system based on SOA (service oriented architecture) service |
| CN115145241A (en) * | 2022-06-09 | 2022-10-04 | 重庆长安汽车股份有限公司 | SOA service-based remote diagnosis method for vehicle-end CAN node and storage medium |
| CN115150431A (en) * | 2022-06-22 | 2022-10-04 | 重庆长安汽车股份有限公司 | Finished vehicle MCU remote debugging system, method and storage medium |
| CN115001897B (en) * | 2022-06-30 | 2024-03-15 | 阿波罗智能技术(北京)有限公司 | Communication method and device, electronic equipment and automatic driving vehicle |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020004767A1 (en) * | 2018-06-25 | 2020-01-02 | 엘지전자 주식회사 | Telematics system provided in vehicle and method for controlling same |
| CN112527854A (en) * | 2019-09-18 | 2021-03-19 | 沈阳智信佰达科技有限公司 | Cloud computing system based on big data of Internet of things |
| CN112769767A (en) * | 2020-12-23 | 2021-05-07 | 华人运通(上海)云计算科技有限公司 | Vehicle-mounted Ethernet SOME/IP protocol data analysis method, device, medium and system |
| CN112804249A (en) * | 2021-01-28 | 2021-05-14 | 中汽创智科技有限公司 | Data communication method and system for remotely calling automatic driving platform |
| CN112953802A (en) * | 2021-02-10 | 2021-06-11 | 北京罗克维尔斯科技有限公司 | Data communication method and device |
| CN113572632A (en) * | 2021-06-09 | 2021-10-29 | 上海赫千电子科技有限公司 | Time-sensitive network communication method and device based on service-oriented architecture |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| DE102015215480A1 (en) * | 2015-08-13 | 2017-02-16 | Robert Bosch Gmbh | Method and device for transmitting a message in a vehicle |
| US11144613B2 (en) * | 2017-09-29 | 2021-10-12 | Blackberry Limited | Platform-independent publish-subscribe |
-
2021
- 2021-12-08 CN CN202111493724.0A patent/CN114268666B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020004767A1 (en) * | 2018-06-25 | 2020-01-02 | 엘지전자 주식회사 | Telematics system provided in vehicle and method for controlling same |
| CN112527854A (en) * | 2019-09-18 | 2021-03-19 | 沈阳智信佰达科技有限公司 | Cloud computing system based on big data of Internet of things |
| CN112769767A (en) * | 2020-12-23 | 2021-05-07 | 华人运通(上海)云计算科技有限公司 | Vehicle-mounted Ethernet SOME/IP protocol data analysis method, device, medium and system |
| CN112804249A (en) * | 2021-01-28 | 2021-05-14 | 中汽创智科技有限公司 | Data communication method and system for remotely calling automatic driving platform |
| CN112953802A (en) * | 2021-02-10 | 2021-06-11 | 北京罗克维尔斯科技有限公司 | Data communication method and device |
| CN113572632A (en) * | 2021-06-09 | 2021-10-29 | 上海赫千电子科技有限公司 | Time-sensitive network communication method and device based on service-oriented architecture |
Non-Patent Citations (5)
| Title |
|---|
| "Design and Implementation of a Smart Integrated Framework to Monitor and Control the Smart City using the Internet of Things";HM Al-Mashhadi;《jsju.org》;全文 * |
| "一种支持面向服务架构SOA的通用域控制器";肖猛;《火龙果工程》;正文1，4，6，11-14，19页 * |
| "面向未来汽车电子电气架构的域控制器平台";刘佳熙;《中国集成电路》;全文 * |
| 工业互联网网络技术标准化分析;楚俊生;游世林;;电信网技术(第11期);全文 * |
| 楚俊生 ; 游世林 ; .工业互联网网络技术标准化分析.电信网技术.2017,(第11期),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114268666A (en) | 2022-04-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114268666B (en) | Universal domain controller supporting Service Oriented Architecture (SOA), vehicle and interaction system | |
| US11249779B2 (en) | Accelerator interconnect assignments for virtual environments | |
| US10649924B2 (en) | Network overlay systems and methods using offload processors | |
| JP7404390B2 (en) | Domain-assisted processor peers for coherent acceleration | |
| US6697878B1 (en) | Computer having a remote procedure call mechanism or an object request broker mechanism, and data transfer method for the same | |
| DE102018210537A1 (en) | Micro-services architecture | |
| CN113253710B (en) | Control software implementation architecture of block gateway electronic control unit | |
| US20190042339A1 (en) | Techniques for invocation of a function or a service | |
| CN108028833A (en) | A kind of method, system and the relevant device of NAS data accesses | |
| CN110120919B (en) | Network resource isolation method and system for container network | |
| JPH0668729B2 (en) | How to start the execution of a new program in a multiprocessor system | |
| CN110162378B (en) | Resource scheduling method, device, equipment and system | |
| WO2022061710A1 (en) | Method and apparatus for controlling vehicle service, vehicle, device, and storage medium | |
| DE102022202554A1 (en) | METHODS, FACILITIES AND ARTICLES OF MANUFACTURE FOR DYNAMIC CACHE ALLOCATION | |
| WO2024041412A1 (en) | Storage system and method, and hardware offload card | |
| US7428730B2 (en) | Software development environment | |
| CN116820764A (en) | Method, system, electronic device and storage medium for providing computing resources | |
| Hartkopp et al. | The CAN networking subsystem of the Linux kernel | |
| US10176146B2 (en) | Integration pattern implementations using reconfigurable logic devices | |
| CN115118741A (en) | Electronic control unit, vehicle comprising an electronic control unit and computer-implemented method | |
| JP2022123826A (en) | Data processor and data processing system | |
| EP1548591B1 (en) | Method, apparatuses and instruction set for an accelerator for object-oriented communications | |
| US20150254100A1 (en) | Software Enabled Network Storage Accelerator (SENSA) - Storage Virtualization Offload Engine (SVOE) | |
| CN113589782B (en) | Method for designing whole vehicle operation platform system architecture and whole vehicle operation platform system architecture | |
| Butzkamm et al. | E/E architecture in the HARRI innovation platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |