WO2024093731A1 - 汽车开放系统架构、数据处理方法及车载设备 - Google Patents

汽车开放系统架构、数据处理方法及车载设备 Download PDF

Info

Publication number
WO2024093731A1
WO2024093731A1 PCT/CN2023/126206 CN2023126206W WO2024093731A1 WO 2024093731 A1 WO2024093731 A1 WO 2024093731A1 CN 2023126206 W CN2023126206 W CN 2023126206W WO 2024093731 A1 WO2024093731 A1 WO 2024093731A1
Authority
WO
WIPO (PCT)
Prior art keywords
system architecture
open system
layer
module
automotive open
Prior art date
Application number
PCT/CN2023/126206
Other languages
English (en)
French (fr)
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
Application filed by 长城汽车股份有限公司 filed Critical 长城汽车股份有限公司
Publication of WO2024093731A1 publication Critical patent/WO2024093731A1/zh

Links

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/321—Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers

Definitions

  • the present application relates to the field of vehicle-mounted communication technology, and in particular to an automobile open system architecture, a data processing method and a vehicle-mounted device.
  • the embodiment of the present application provides an automotive open system architecture, a data processing method and an on-board device, which can integrate the DDS protocol in the classic platform AUTOSAR.
  • the technical solution is as follows:
  • an embodiment of the present application provides an automotive open system architecture, wherein the automotive open system architecture includes a classic platform CP automotive open system architecture, wherein:
  • the CP automobile open system architecture includes a data distribution service DDS protocol stack component, and the DDS protocol stack component is integrated into the CP automobile open system architecture in a complex drive form;
  • the DDS protocol stack components include: a data-centric publish-subscribe DCPS layer and a data local reconstruction DLR layer.
  • the DCPS layer is used to receive data objects of target services published or subscribed by applications, and the DLR layer is used to reconstruct data objects of target services published or subscribed by the applications.
  • the DDS protocol stack component includes a DDS client
  • the automotive open system architecture also includes an adaptive AP automotive open system architecture
  • the AP automotive open system architecture includes a DDS agent
  • the DDS agent is used to communicate with the DDS client through a service interface, receive service data from the DDS client, and process the service data.
  • the automotive open system architecture further includes a static configuration module and a dynamic configuration module, wherein:
  • the static configuration module is used to configure the configuration items of the static resources corresponding to the DDS client and the DDS agent;
  • the dynamic configuration module is used to configure the configuration items of the dynamic resources corresponding to the DDS client and the DDS agent.
  • the CP automotive open system architecture and the AP automotive open system architecture both include an application layer, an operating environment layer and a basic software layer, and the application layer communicates with the basic software layer through the operating environment layer.
  • the automotive open system architecture further includes: a publisher module and a subscriber module, the subscriber module is arranged in the application layer of the CP automotive open system architecture, and the publisher module is arranged in the application layer of the AP automotive open system architecture, wherein:
  • the publisher module is used to provide data objects to the CP automotive open system architecture
  • the subscriber module is used to obtain required data objects from the AP automotive open system architecture.
  • the DCPS layer further includes a global data space, wherein:
  • the publisher module is used to provide data objects to the CP automotive open system architecture through the global data space;
  • the subscriber module is used to obtain required data objects from the AP automotive open system architecture through the global data space.
  • the DLR layer includes an encapsulation module and an indexing module, wherein:
  • the encapsulation module is used to encapsulate the services provided by the DCPS layer in the form of service classes, and the service classes are generated in the form of local language structures;
  • the index module is used to establish a corresponding relationship between the service class and the service corresponding to the DCPS layer.
  • an embodiment of the present application provides a data processing method, which is applied to an automotive open system architecture, wherein the automotive open system architecture includes a classic platform CP automotive open system architecture, wherein the CP automotive open system architecture includes a data distribution service DDS protocol stack component, wherein the DDS protocol stack component is integrated into the CP automotive open system architecture in a complex drive form, wherein the DDS protocol stack component includes a DCPS layer and a DLR layer, and wherein the method includes:
  • the data objects of the target service published or subscribed by the application are reconstructed through the DLR layer so that
  • an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the steps of the above-mentioned method.
  • an embodiment of the present application provides a vehicle-mounted device, comprising: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the steps of the above method.
  • FIG1 is a schematic diagram showing a system architecture of an automotive open system architecture provided according to some embodiments of the present application.
  • FIG2 shows a schematic diagram of an automotive open system architecture provided according to some embodiments of the present application.
  • FIG3 shows a schematic diagram of an automotive open system architecture provided according to some other embodiments of the present application.
  • FIG4 shows a schematic diagram of an automotive open system architecture provided according to other embodiments of the present application.
  • FIG5 is a schematic diagram showing a data processing method provided according to some embodiments of the present application.
  • FIG6 shows a schematic structural diagram of a vehicle-mounted device provided according to some embodiments of the present application.
  • DDS A middleware protocol and application program interface (API) standard that provides a low-latency, high-reliability, and scalable communication architecture standard for distributed systems.
  • DDS data sharing is based on topics, and applications can determine the type of data contained in a topic without having to rely on other contextual information.
  • DDS can automatically store, publish, or subscribe to data in a user-defined manner, allowing applications to write or read data just like accessing local data.
  • middleware In a distributed system, middleware is a software layer located between the operating system and the application. It enables the various components of the system to communicate and share data more easily. It simplifies distributed system software development by shielding the mechanism for transmitting information between the application and the system, allowing software developers to focus on application design.
  • the DDS protocol stack component is a type of middleware.
  • CAN bus The data bus in traditional vehicle architecture can carry a large amount of data and is an ISO internationally standardized serial communication protocol.
  • LIN (Local Interconnect Network) bus A data bus in traditional vehicle architecture, used to implement distributed electronic system control in automobiles. It can carry a smaller amount of data and is mainly used to control some simple in-vehicle devices. It is an auxiliary bus network.
  • SOME/IP protocol is an automotive middleware solution for control messages that enables service-oriented communication between controllers.
  • SOME/IP provides a wide range of middleware functions such as serialization, remote procedure calls, service discovery and subscription to enable ECU software to communicate with each other.
  • ARXML AUTOSAR eXtensible Markup Language
  • AUTOSAR An alliance dedicated to developing automotive electronic software standards, committed to developing an open, standardized software architecture for the automotive industry.
  • FIG1 shows a schematic diagram of a system architecture of an automotive open system architecture provided according to some embodiments of the present application.
  • the system architecture of the automotive open system architecture AUTOSAR 110 includes an application layer 110, an operating environment layer 120 and a basic software layer 130.
  • the application layer 110 and the basic software layer 130 communicate with each other through the operating environment layer 120.
  • the application layer 110 includes at least one application such as an AUTOSAR software component, an AUTOSAR sensor or actuator component, etc.
  • the runtime layer 120 is a layer that provides communication services for the application.
  • the AUTOSAR software component of the application layer 110 can communicate with other components such as ECUs or services through the runtime layer 120.
  • the basic software layer 130 mainly includes four parts: microcontroller abstraction layer, ECU abstraction layer, service layer and complex driver.
  • the microcontroller abstraction layer contains hardware-related drivers that can be used to access memory, communication and I/O, etc.
  • the ECU abstraction layer is responsible for providing a unified access interface to access communication, memory or I/O, so that there is no need to consider whether these resources are provided by the microprocessor or by external devices
  • the service layer provides various types of background services, such as network services, memory management and bus communication services, etc., and the operating system is located in this service layer.
  • the complex driver spans from the hardware to the operating environment layer 120. Its main task is to integrate non-standard functional modules with special purposes and embed these functions into the AUTOSAR basic software layer 130, so as to realize the specific functions and time requirements of processing complex sensors and actuators.
  • the complex driver is closely related to the microcontroller and ECU hardware. Its upper-level program interface is specified and implemented according to AUTOSAR; its lower-level program interface is limited by the standard interface program.
  • the complex driver can realize the evaluation of complex sensors and the control of actuators, such as injection control, solenoid valve control, incremental position detection, etc.
  • Fig. 2 shows a schematic diagram of an automotive open system architecture provided according to some embodiments of the present application.
  • the automotive open system architecture in the exemplary embodiment is described in detail below in conjunction with the accompanying drawings.
  • the automotive open system architecture 100 includes CP AUTOSAR 101, wherein: CP AUTOSAR includes a DDS protocol stack component 132 , which is integrated in the CP AUTOSAR 101 in the form of a complex driver.
  • CP AUTOSAR interacts directly with sensors and actuators by extracting the microcontroller's peripherals as signals. The extracted signals can be used by applications to process the input/output values of sensors/actuators and to send and receive bus data.
  • CP AUTOSAR connects vehicle network communication interfaces such as LIN bus, CAN bus, and Ethernet.
  • CP AUTOSAR also supports sending and receiving service-oriented resources such as events, fields, and methods.
  • the protocol converter in the runtime environment converts the service-oriented protocol interface into a standardized interface.
  • the complex driver provides the AUTOSAR interface to the upper layer through the operating environment layer 120, and can directly access the MCU (Microcontroller Unit) registers.
  • the CP AUTOSAR application-level software component encapsulates and customizes the DDS protocol stack component 132 in the form of a complex driver through the CP AUTOSAR communication service, such as encapsulating the interface of the DDS protocol stack component 132, using the DDS protocol stack component 132 as a static link library, and using DDS to communicate within the ECU and between ECUs through a standard API.
  • DDS is data-centric and is used to accommodate dynamic data from different sources. In related technologies, most middleware works by sending information between applications and systems.
  • the data-centric feature ensures that all messages sent through the DDS protocol stack component 132 contain the context information required for the application to fully understand the data it receives.
  • the essence of data-centricity is that the DDS protocol stack component 132 knows what data it stores and controls how to share the data. Programmers using traditional message-centric middleware must write code to send messages. Programmers using data-centric middleware write code only to specify how and when data is shared.
  • the link library refers to the binary file obtained after compiling and packaging the open source library files. Although the link library is a binary file, it cannot run independently and must wait for other programs to call it before it can be loaded into the memory. Static linking means that no matter whether the missing address is located in other target files or link libraries, the link library will find the missing addresses in each target file one by one.
  • the executable file generated by this linking method can be loaded into the memory and run independently; the link library used for static linking is called a static link library.
  • Dynamic linking means that the linker first finds some missing addresses from all target files, and then organizes all target files into one executable file. The executable file generated in this way is still missing the addresses of some functions and variables.
  • the file When the file is executed, it needs to be loaded into the memory together with all the link library files, and then the linker completes it. The remaining address repair work must be completed before it can be executed normally.
  • the method of linking all target files is still static linking, while the linking operation after loading into memory is called dynamic linking, and the link library used is called dynamic link library.
  • the shared global data space refers to the local data storage area. To the application, the shared global data space is like local memory accessed through an API. When the application sends data, it looks like writing to local storage. In fact, the DDS protocol stack component 132 sends messages to update the storage on the remote node. The receiving program on the remote node looks like getting data from local storage.
  • the DDS protocol stack component 132 includes: a DCPS (Data-Centric Publish-Subscribe) layer 1322 and a DLR (Data Local Reconstruction) layer 1324, the DCPS layer 1322 is used for the application to publish or subscribe to the data objects of the target service, and the DLR layer 1324 is used to reconstruct the data objects of the target service published or subscribed by the application.
  • DCPS Data-Centric Publish-Subscribe
  • DLR Data Local Reconstruction
  • the DCPS layer 1322 is the core and foundation of the DDS protocol stack component 132, and provides basic communication services.
  • the encapsulation module in the DLR layer 1324 encapsulates the services provided by the DCPS layer 1322 in the form of service classes.
  • the service classes are generated in the form of local language structures, and the services provided by the DCPS layer 1322 are abstracted.
  • the index module in the DLR layer 1324 establishes a mapping relationship between the service classes and the underlying services in the DLR layer 1324.
  • the DLR layer 1324 is built on the basis of the lower DCPS layer 1322.
  • the DDS protocol stack component is packaged and customized in the form of a complex driver and integrated into the CP AUTOSAR, so that the DDS protocol stack can be integrated into the classic platform AUTOSAR; on the other hand, the DLR layer of the DDS protocol stack component is built on the basis of the lower DCPS layer.
  • the application program can directly interact with the underlying service for data, so that the user can directly access the data changed by the underlying service, so as to achieve local The underlying services of the language structure are seamlessly connected.
  • the DCPS layer 1322 converts the user's demand for resources and the availability of resources into QoS (Quality of Service), which includes multiple policy forms, each of which describes the behavior of the service by associating it with an assigned name.
  • QoS Quality of Service
  • the DCPS layer 1322 provides the function of publishing and subscribing data. Publishing and subscribing are done through topic association, publishing information through topic association, creating publisher and subscriber entities, and setting QoS parameters for these entities.
  • FIG3 shows a schematic diagram of an automotive open system architecture provided according to other embodiments of the present application.
  • the automotive open system architecture also includes AP (Adaptive Platform) AUTOSAR102
  • AP AUTOSAR102 includes a DDS agent 320
  • the DDS protocol stack component of CP AUTOSAR includes a DDS client 310.
  • the CP AUTOSAR and the AP AUTOSAR both include an application layer, an operating environment layer and a basic software layer, and the application layer and the basic software layer communicate through the operating environment layer.
  • the DDS agent 320 is used to communicate with the DDS client 310 through the service interface 330, receive the service data of the DDS client 310, and process the service data.
  • the AUTOSAR service interface is usually defined using ARXML, which is a modeling language derived from the AUTOSAR UML metamodel. As a result of code generation, the ARXML compiler generates code for the agent and the framework for the client and server applications respectively. On the client side, the application instantiates the agent and binds it to the service instance running on the server side.
  • the AUTOSAR service provides the following function call interfaces: DDS protocol stack initialization, DDS protocol stack periodic scheduling, DDS protocol stack data sending request, DDS protocol stack data receiving notification, and DDS protocol stack deinitialization.
  • the automotive open system architecture also includes a static configuration module and a dynamic configuration module, wherein the static configuration module is used to configure the configuration items of static resources corresponding to the DDS client and the DDS agent; the dynamic configuration module is used to configure the configuration items of dynamic resources corresponding to the DDS client and the DDS agent.
  • the DDS protocol stack component of the automotive open system architecture includes a static configuration module and a dynamic configuration module.
  • the static configuration module adopts a proven mature product of the open source platform.
  • the dynamic configuration module customizes the development module definition file in ARXML format, defines the configuration items of the DDS module, and configures the configuration items of the dynamic resources corresponding to the DDS client and DDS agent.
  • a development tool chain (such as Vector Davinci) is used to import the ARXML file and set the configuration items of the dynamic resources, and the code generation tool corresponding to the DDS protocol stack component is used to realize dynamic configuration code generation and development tool chain integration.
  • the configuration items of static resources corresponding to the DDS client and the DDS agent are configured through the static configuration module; the configuration items of dynamic resources corresponding to the DDS client and the DDS agent are configured through the dynamic configuration module.
  • FIG4 shows a schematic diagram of an automotive open system architecture provided according to other embodiments of the present application.
  • AUTOSAR further includes: a publisher module 410 and a subscriber module 420, wherein the subscriber module 420 is arranged at the application layer of CP AUTOSAR, and the publisher module 410 is arranged at the application layer of AP AUTOSAR, wherein: the publisher module 410 is used as a service provider to provide data objects to CP AUTOSAR; and the subscriber module 420 is used as a service consumer to obtain required data objects from the AP AUTOSAR.
  • the DCPS layer also includes a global data space, and the physical storage space of the global data space can be located in the shared storage space of the hardware layer 350.
  • the publisher module 410 is used to provide data objects to CP AUTOSAR through the global data space; the subscriber module 420 is used to obtain the required data objects from AP AUTOSAR through the global data space.
  • DDS provides an infrastructure for data distribution to ensure that information is correctly and effectively transmitted to appropriate receivers.
  • the DCPS layer of DDS establishes the concept of a global data space. Publishers and subscribers respectively publish and subscribe to the data types they need in the global space. After being processed by the middleware, data is transmitted, transforming the traditional C/S model into a data-centric service model.
  • the DCPS layer of DDS establishes the concept of a global data space. Publishers and subscribers respectively publish and subscribe to the data types they need in the global space. After being processed by the middleware, the data is transmitted, which transforms the traditional C/S model into a data-centric service model, weakens the relationship between information publishers and subscribers, decouples the various components of the system, enhances the flexibility of the system architecture, and facilitates system maintenance and scale expansion.
  • FIG5 shows a schematic diagram of a data processing method provided according to some embodiments of the present application.
  • the data processing method is applied to an automotive open system architecture, wherein the automotive open system architecture includes a classic platform CP automotive open system architecture, wherein the CP AUTOSAR includes a data distribution service DDS protocol stack component, wherein the DDS protocol stack component is integrated in the CP AUTOSAR in a complex driver form, wherein the DDS protocol stack component includes a DCPS layer and a DLR layer, and wherein the method includes:
  • Step 510 receiving the data object of the target service published or subscribed by the application through the DCPS layer;
  • Step 520 Reconstruct the data object of the target service published or subscribed by the application through the DLR layer.
  • the automotive open system architecture further includes an adaptive AP AUTOSAR
  • the AP AUTOSAR includes a DDS agent
  • the method further includes:
  • the DDS agent communicates with the DDS client through the service interface of the DDS agent, receives service data of the DDS client, and processes the service data.
  • the automotive open system architecture further includes a static configuration module and a dynamic configuration module
  • the method further includes:
  • the configuration items of the dynamic resources corresponding to the DDS client and the DDS agent are configured through the dynamic configuration module.
  • the CP AUTOSAR and the AP AUTOSAR both include an application layer, an operating environment layer and a basic software layer, and the application layer communicates with the basic software layer through the operating environment layer.
  • the automotive open system architecture further includes: a publisher module and a subscriber module, the subscriber module is arranged in the application layer of the CP AUTOSAR, and the publisher module is arranged in the application layer of the AP AUTOSAR, and the method further includes:
  • the required data objects are obtained from the AP AUTOSAR through the subscriber module.
  • the DCPS layer further includes a global data space
  • the method further includes:
  • the publisher module provides data objects to the CP AUTOSAR through the global data space
  • the subscriber module obtains the required data objects from the AP AUTOSAR through the global data space.
  • the method further includes:
  • the services provided by the DCPS layer are encapsulated in the form of service classes, and the service classes are generated in the form of local language structures; and a corresponding relationship between the service classes and the services corresponding to the DCPS layer is established.
  • the DDS protocol stack component is encapsulated and customized in the form of a complex driver and integrated into CP AUTOSAR, so that the DDS protocol stack can be integrated into classic AUTOSAR; on the other hand, the DLR layer of the DDS protocol stack component is built on the basis of the underlying DCPS layer, and by integrating the services provided by the DCPS layer into the application layer, users can directly access the changed data, thereby achieving seamless connection with the local language structure.
  • the automotive open system architecture provided in the above embodiment is only illustrated by the division of the above functional modules when executing the automotive open system architecture.
  • the above functional allocation can be completed by different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules. functional modules to complete all or part of the functions described above.
  • automobile open system architecture and the data processing method embodiment provided in the above embodiments belong to the same concept, and the embodiment and implementation process thereof are detailed in the embodiment of the automobile open system architecture, which will not be repeated here.
  • An embodiment of the present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded by a processor and executing the data processing method as described in the above embodiment.
  • the specific execution process can be found in the specific description of the above embodiment, and will not be repeated here.
  • An embodiment of the present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded by the processor and executes the data processing method as described in the above embodiment.
  • the specific execution process can be found in the specific description of the above embodiment, and will not be repeated here.
  • An embodiment of the present application also provides a chip, which is configured to execute the data processing method as described in the above embodiment.
  • the specific execution process can be found in the specific description of the above embodiment, and will not be repeated here.
  • the vehicle-mounted device 600 may include: at least one processor 601, at least one communication module 604, an input and output interface 603, a memory 605, and at least one communication bus 602.
  • the communication bus 602 is used to realize the connection and communication between these components.
  • the input/output interface 603 may include a display screen (Display) and a camera (Camera), and the optional input/output interface 603 may also include a standard wired interface and a wireless interface.
  • the communication module 604 may optionally include a standard wired interface, a wireless interface (such as a WIFI interface).
  • the communication module 604 includes a first gateway such as an S2S gateway and a second gateway such as a C2C gateway.
  • the first gateway uses a first communication protocol for communication
  • the second gateway uses a second communication protocol for communication.
  • the processor 601 may include one or more processing cores.
  • the processor 601 uses various interfaces and lines to connect the various parts of the entire vehicle-mounted device 600, and executes various functions and processes data of the server 600 by running or executing instructions, programs, code sets or instruction sets stored in the memory 605, and calling data stored in the memory 605.
  • the processor 601 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA).
  • the processor 601 can be integrated with a central processing unit
  • the processor 601 includes one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem.
  • the CPU mainly processes the operating system, the user interface, and the application program.
  • the GPU is responsible for rendering and drawing the content to be displayed on the display screen.
  • the modem is used to process wireless communications. It is understandable that the modem may not be integrated into the processor 601, but may be implemented by a separate chip.
  • the memory 605 may include a random access memory (RAM) or a read-only memory (ROM).
  • the memory 605 includes a non-transitory computer-readable storage medium.
  • the memory 605 may be used to store instructions, programs, codes, code sets or instruction sets.
  • the memory 605 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc.
  • the memory 605 may also be at least one storage device located away from the aforementioned processor 601. As shown in FIG. 6 , the memory 605 as a computer storage medium may include an operating system, a communication module, an input/output interface module, and a data processing application.
  • the input-output interface 603 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 601 can be used to call the data processing application stored in the memory 605, so that the processor 601 executes the steps in the data processing method according to various exemplary embodiments of the present disclosure.
  • the vehicle-mounted device 600 includes an automotive open system architecture, and the automotive open system architecture includes a classic platform CP AUTOSAR, and the CP AUTOSAR includes a data distribution service DDS protocol stack component, and the DDS protocol stack component is integrated in the CP AUTOSAR in the form of a complex driver, and the DDS protocol stack component includes a DCPS layer and a DLR layer.
  • the processor 601 can execute the steps shown in FIG5 : Step 510, receiving the data object of the target service published or subscribed by the application through the DCPS layer; Step 520, reconstructing the data object of the target service published or subscribed by the application through the DLR layer.
  • the above is a schematic scheme of a vehicle-mounted device in an embodiment of this specification.
  • the vehicle-mounted device can be a central gateway or other appropriate devices such as a vehicle-mounted gateway.
  • the technical solution of the vehicle-mounted device and the technical solution of the above-mentioned automotive open system architecture belong to the same concept.
  • the technical solution of the vehicle-mounted device please refer to the above-mentioned automotive open system architecture processing. Description of the technical solution of the method.
  • the storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

本申请实施例公开了一种汽车开放系统架构、数据处理方法及车载设备，该汽车开放系统架构包括经典平台CP汽车开放系统架构(101)，其中：所述CP汽车开放系统架构(101)包括数据分发服务DDS协议栈组件(132)，所述DDS协议栈组件(132)以复杂驱动形式集成在所述CP汽车开放系统架构(101)；所述DDS协议栈组件(132)包括：以数据为中心的发布订阅DCPS层(1322)和数据本地重构DLR层(1324)，DCPS层(1322)用于接收应用程序发布或订阅目标服务的数据对象，DLR层(1324)用于对所述应用程序发布或订阅的目标服务的数据对象进行重构。

Description

汽车开放系统架构、数据处理方法及车载设备
本申请要求于2022年11月1日提交的申请号为2022113528674、发明名称为“汽车开放系统架构、数据处理方法、介质及车载设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及车载通信技术领域，尤其涉及一种汽车开放系统架构、数据处理方法及车载设备。
背景技术
随着车辆智能互联技术的发展，车载电子设备的功能也越来越丰富，应用于军事、航空领域的DDS(Data Distribution Service，数据分发服务)协议凭借其独特的功能特性和性能在汽车行业逐步获得关注和认可，在汽车电子ECU(Electronic Control Unit，电子控制单元)产品中集成DDS通信中间件成为一种现实的需求。
发明内容
本申请实施例提供了一种汽车开放系统架构、数据处理方法及车载设备，能够在经典平台AUTOSAR中集成DDS协议，技术方案如下：
第一方面，本申请实施例提供了一种汽车开放系统架构，所述汽车开放系统架构包括经典平台CP汽车开放系统架构，其中：
所述CP汽车开放系统架构包括数据分发服务DDS协议栈组件，所述DDS协议栈组件以复杂驱动形式集成在所述CP汽车开放系统架构；
所述DDS协议栈组件包括：以数据为中心的发布订阅DCPS层和数据本地重构DLR层，DCPS层用于接收应用程序发布或订阅目标服务的数据对象，DLR层用于对所述应用程序发布或订阅的目标服务的数据对象进行重构。
在一些示例实施例中，基于上述方案，DDS协议栈组件包括DDS客户端， 所述汽车开放系统架构还包括自适应AP汽车开放系统架构，所述AP汽车开放系统架构包括DDS代理，
所述DDS代理用于通过服务接口与所述DDS客户端进行通信，接收所述DDS客户端的服务数据，并对所述服务数据进行处理。
在一些示例实施例中，基于上述方案，所述汽车开放系统架构还包括静态配置模块和动态配置模块，其中，
所述静态配置模块用于对所述DDS客户端和所述DDS代理对应的静态资源的配置项进行配置；
所述动态配置模块用于对所述DDS客户端和所述DDS代理对应的动态资源的配置项进行配置。
在一些示例实施例中，基于上述方案，所述CP汽车开放系统架构与所述AP汽车开放系统架构均包括应用层、运行环境层和基础软件层，所述应用层与所述基础软件层之间通过所述运行环境层通信。
在一些示例实施例中，基于上述方案，所述汽车开放系统架构还包括：发布者模块以及订阅者模块，所述订阅者模块设置于所述CP汽车开放系统架构的所述应用层，所述发布者模块设置于所述AP汽车开放系统架构的所述应用层，其中：
所述发布者模块用于向所述CP汽车开放系统架构提供数据对象；
所述订阅者模块用于从所述AP汽车开放系统架构获取需要的数据对象。
在一些示例实施例中，基于上述方案，所述DCPS层还包括全局数据空间，其中：
所述发布者模块用于通过所述全局数据空间向所述CP汽车开放系统架构提供数据对象；
所述订阅者模块用于通过所述全局数据空间从所述AP汽车开放系统架构获取需要的数据对象。
在一些示例实施例中，基于上述方案，所述DLR层包括封装模块和索引模块，其中：
所述封装模块用于对所述DCPS层提供的服务以服务类的形式进行封装，所述服务类以本地语言结构的形式生成；
所述索引模块用于建立服务类与DCPS层对应的服务之间的对应关系。
第二方面，本申请实施例提供一种数据处理方法，应用于汽车开放系统架构，所述汽车开放系统架构包括经典平台CP汽车开放系统架构，所述CP汽车开放系统架构包括数据分发服务DDS协议栈组件，所述DDS协议栈组件以复杂驱动形式集成在所述CP汽车开放系统架构，所述DDS协议栈组件包括DCPS层和DLR层，所述方法包括：
通过所述DCPS层接收应用程序发布或订阅的目标服务的数据对象；
通过DLR层对所述应用程序发布或订阅的目标服务的数据对象进行重构，以使。
第三方面，本申请实施例提供一种计算机存储介质，所述计算机存储介质存储有多条指令，所述指令适于由处理器加载并执行上述的方法的步骤。
第四方面，本申请实施例提供一种车载设备，包括：处理器和存储器；其中，所述存储器存储有计算机程序，所述计算机程序适于由所述处理器加载并执行上述的方法的步骤。
附图说明
图1示出了根据本申请的一些实施例提供的汽车开放系统架构的系统架构的示意图；
图2示出了根据本申请的一些实施例提供的汽车开放系统架构的示意图；
图3示出了根据本申请的又一些实施例提供的汽车开放系统架构的示意图；
图4示出了根据本申请的另一些实施例提供的汽车开放系统架构的示意图；
图5示出了根据本申请的一些实施例提供的数据处理方法的示意图；
图6示出了根据本申请的一些实施例提供的一种车载设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
首先，对本申请实施例中涉及的名词进行解释和说明。
DDS：一种中间件协议和应用程序接口(API)标准，它为分布式系统提供了低延迟、高可靠性、可扩展的通信架构标准。DDS的数据共享以主题Topic为单元，应用程序能够通过Topic判断其所包含的数据类型，而不必依赖其他的上下文信息。同时，DDS能够按照用户定义的方式自动地进行存储、发布或订阅数据，使应用程序能够像访问本地数据一样去写入或者读取数据。
中间件：在分布式系统中，中间件是位于操作系统和应用程序之间的软件层。它使系统的各个组件能够更轻松地通信和共享数据。它通过屏蔽应用程序和系统之间传递信息的机制，让软件开发人员专注于应用程序设计，从而简化分布式系统软件开发。在本申请实施例中，DDS协议栈组件属于一种中间件。
CAN总线：传统车载架构中的数据总线，可以承载较大的数据量，是ISO国际标准化的串行通信协议。
LIN(Local Interconnect Network，局域互联网络)总线：传统车载架构中的数据总线，用于实现汽车中的分布式电子系统控制，可以承载较小的数据量，主要用于控制一些简单的车内设备，是一种辅助的总线网络。
SOME/IP协议：是用于控制消息的汽车中间件解决方案，可以在控制器之间实现面向服务的通信。SOME/IP提供了广泛的中间件功能，如序列化、远程过程调用、服务发现和订阅，以使ECU软件能够相互通信。
ARXML(AUTOSAR eXtensible Markup Language，AUTOSAR可扩展标记语言)：该标准介绍了如何将AUTOSAR模型序列化为AUTOSAR XML描述的规则，为AUTOSAR工具之间的互操作性提供支持。
AUTOSAR：是一家致力于制定汽车电子软件标准的联盟，致力于为汽车工业开发一个开放的、标准化的软件架构。
相关技术中，随着CP(Classic Platform，经典平台)AUTOSAR(AUTomotive Open System ARchitecture，汽车开放系统架构)标准在汽车行业的广泛应用，众多主机厂在其电子电器系统研发中开始应用CP AUTOSAR方法学构建ECU产品软件架构。CP AUTOSAR标准和架构已经包含面向汽车领域的SOME/IP(Scalable service-Oriented MiddlewarE over IP，IP之上面向服务的可伸缩的中间件)协议栈，但是CP AUTOSAR中DDS协议栈并未实现标准化。
因此，如何在经典平台AUTOSAR中集成DDS协议成为了亟待解决的技术难题。
下面，将结合附图对本申请实施例的汽车开放系统架构的技术方案进行详细的说明。
图1示出了根据本申请的一些实施例提供的汽车开放系统架构的系统架构的示意图。
参照图1所示，该汽车开放系统架构AUTOSAR 110的系统架构包括应用层110、运行环境层120以及基础软件层130，应用层110与基础软件层130之间通过运行环境层120进行通信。
在示例实施例中，应用层110包括至少一个应用程序例如AUTOSAR软件组件、AUTOSAR传感器或执行器组件等。运行环境层120是为应用程序提供通信服务的层。应用层110的AUTOSAR软件组件可以通过运行环境层120与其他组件例如ECU或服务进行通信。
基础软件层130主要包括四部分：微控制器抽象层、ECU抽象层，服务层以及复杂驱动。其中，微控制器抽象层包含了跟硬件相关的驱动程序，可以用来访问内存、通信和I/O等；ECU抽象层负责提供统一的访问接口实现对通信、内存或者I/O的访问，从而无须考虑这些资源由微处理器提供还是由外部设备提供；服务层提供各种类型的后台服务，例如网络服务、内存管理和总线通信服务等，操作系统就位于该服务层。
复杂驱动从硬件跨越到运行环境层120，主要任务是整合具有特殊目的的非标准功能模块，将该部分功能嵌入到AUTOSAR基础软件层130中，从而实现处理复杂传感器以及执行器的特定功能和时间要求。复杂驱动程序跟单片机和ECU硬件紧密相关。其上层程序接口是根据AUTOSAR指定并且实施的；其下层程序接口受标准接口程序的限制。复杂驱动可以实现对复杂传感器的评估和执行器的控制，比如喷油控制，电磁阀控制，增量位置检测等。
图2示出了根据本申请的一些实施例提供的汽车开放系统架构的示意图。下面，结合附图对示例实施例中的汽车开放系统架构进行详细的说明。
参照图2所示，汽车开放系统架构100包括CP AUTOSAR101，其中：CP  AUTOSAR包括DDS协议栈组件132，DDS协议栈组件132以复杂驱动形式集成在CP AUTOSAR101。
CP AUTOSAR通过将微控制器的外设提取为信号，直接与传感器和执行器交互，提取的信号可以被应用程序用于处理传感器/执行器的输入/输出值以及发送和接收总线数据。CP AUTOSAR连接车辆网络通信接口，如LIN总线、CAN总线以及以太网。CP AUTOSAR还支持发送和接收面向服务的资源，如事件、字段和方法等，运行时环境中的协议转换器将面向服务的协议接口转换为标准化接口。
复杂驱动(Complex Driver，CDD)向上通过运行环境层120给上层提供AUTOSAR接口，向下可以直接访问MCU(Microcontroller Unit，微控制单元)寄存器。在示例实施例中，CP AUTOSAR应用程序级的软件组件通过CP AUTOSAR的通讯服务，将DDS协议栈组件132以复杂驱动形式进行封装和定制化集成，例如对DDS协议栈组件132的接口进行封装，将DDS协议栈组件132作为静态链接库，利用DDS通过标准API进行ECU内部和ECU之间的通信。DDS是以数据为中心的，用于容纳来自不同来源的动态数据。相关技术中，大多数中间件通过在应用程序和系统之间发送信息来工作。以数据为中心的特性确保所有通过DDS协议栈组件132发送的消息都包含应用程序能够完全理解其接收数据所需的上下文信息。另外，以数据为中心的本质是DDS协议栈组件132知道它存储了什么数据并控制如何共享这些数据。使用传统的以消息为中心的中间件的程序员必须编写发送消息的代码。使用以数据为中心的中间件的程序员编写代码仅需指定如何以及何时共享数据。
还有，链接库是指将开源的库文件进行编译、打包操作后得到的二进制文件。虽然链接库是二进制文件，但无法独立运行，必须等待其它程序调用，才会被载入内存。静态链接是指无论缺失的地址位于其它目标文件还是链接库，链接库都会逐个找到各目标文件中缺失的地址。采用此链接方式生成的可执行文件，可以独立载入内存运行；静态链接用到的链接库称为静态链接库。动态链接是指链接器先从所有目标文件中找到部分缺失的地址，然后将所有目标文件组织成一个可执行文件。如此生成的可执行文件，仍缺失部分函数和变量的地址，待文件执行时，需连同所有的链接库文件一起载入内存，再由链接器完 成剩余的地址修复工作，才能正常执行。其中，链接所有目标文件的方法仍属静态链接，而载入内存后进行的链接操作称为动态链接，用到的链接库称为动态链接库。
使用DDS协议栈组件132，应用程序可以直接与共享全局数据空间中的数据交互。，该共享全局数据空间是指本地数据存储区。对应用程序来说，共享全局数据空间就像通过API访问的本地内存。应用程序发送数据看起来像写入本地存储。实际上，DDS协议栈组件132会发送消息来更新远程节点上的存储。远程节点上的接收方程序看起来像从本地存储取得数据。
进一步地，在示例实施例中，DDS协议栈组件132包括：DCPS(Data-Centric Publish-Subscribe，以数据为中心的发布订阅)层1322和DLR(Data Local Reconstruction，数据本地重构)层1324，DCPS层1322用于应用程序发布或订阅目标服务的数据对象，DLR层1324用于对应用程序发布或订阅的目标服务的数据对象进行重构。
进一步地，在示例实施例中，DLR层1324包括封装模块和索引模块，封装模块用于对DCPS层1322提供的服务以服务类的形式进行封装，服务类以本地语言结构的形式生成；索引模块用于建立服务类与DCPS层对应的服务之间的对应关系或映射关系。
DCPS层1322是DDS协议栈组件132的核心和基础，提供了通信的基本服务。DLR层1324中的封装模块对DCPS层1322提供的服务以服务类的形式进行封装，服务类以本地语言结构的形式生成，将DCPS层1322提供的服务进行了抽象，DLR层1324中的索引模块在DLR层1324建立了服务类与底层服务的映射关系。DLR层1324建立在下层DCPS层1322的基础上，通过将DCPS层1322提供的服务整合到应用层，应用程序可以直接与底层服务进行数据交互，使用户能直接访问底层服务变更的数据，达到与本地语言结构无缝连接。
根据图2的示例实施例中的技术方案，一方面，将DDS协议栈组件以复杂驱动形式进行封装和定制化集成到CP AUTOSAR，能够在经典平台AUTOSAR中集成DDS协议栈；另一方面，DDS协议栈组件的DLR层建立在下层DCPS层的基础上，通过将DCPS层提供的服务整合到应用层，应用程序可以直接与底层服务进行数据交互，使用户能直接访问底层服务变更的数据，达到与本地 语言结构的底层服务无缝连接。
此外，在示例实施例中，DCPS层1322将用户对资源的需求情况和资源的可用情况都转化为QoS(Quality of Service，服务质量)，QoS包括多种策略形式，每种策略形式通过与一个赋值的名字关联来描述服务的行为。DCPS层1322提供了发布和订阅数据的功能。发布和订阅通过主题关联，通过主题关联发布信息，创建发布者和订阅者实体，并为这些实体设定QoS参数。
例如，DDS将资源可用情况、提供方对资源的占有程度及请求方对资源的期待程度分别程序化为主题QoS、发布者QoS和订阅者QoS。QoS参数虚拟了底层和整个通信机制，包括带宽限制、可靠性、等待时间和资源限制等。通过DDS中间件检查发布者QoS和订阅者QoS之间是否兼容，从而建立连接或提示异常。通过QoS控制通信过程，能够显著增加通信的灵活性。
图3示出了根据本申请的另一些实施例提供的汽车开放系统架构的示意图。
参照图3所示，汽车开放系统架构还包括AP(Adaptive Platform，自适应平台)AUTOSAR102，AP AUTOSAR102包括DDS代理320，CP AUTOSAR的DDS协议栈组件包括DDS客户端310，所述CP AUTOSAR与所述AP AUTOSAR均包括应用层、运行环境层和基础软件层，所述应用层与所述基础软件层之间通过所述运行环境层通信。
DDS代理320用于通过服务接口330与DDS客户端310进行通信，接收DDS客户端310的服务数据，并对服务数据进行处理。AUTOSAR服务接口通常使用ARXML定义，ARXML是从AUTOSAR UML元模型派生的建模语言。作为代码生成的结果，ARXML编译器分别为客户端和服务器应用程序生成用于代理和框架的代码。在客户端，应用程序实例化代理绑定到服务器端运行的服务实例。AUTOSAR服务提供以下功能调用接口：DDS协议栈初始化、DDS协议栈周期调度、DDS协议栈数据发送请求、DDS协议栈数据接收通知、DDS协议栈反初始化。同时，DDS复杂驱动提供以下资源参数：参与者(Participates)-DDS域内不同的通信节点、主题(Topic)-特定种类的数据、发布者(Publisher)-数据生产者通信节点、订阅者(Subscriber)-数据消费者通信节点。不同资源通过资源id进行标识。上层应用程序实例根据各自的实际功能需求，使用与其相应的资源参数调用协议栈接口，实现DDS域内数据交互。
根据图3的示例实施例中，一方面，由于车载电子电器架构核心ECU部件广泛采用异构多核SOC硬件芯片并同时部署CP AUTOSAR和AP AUTOSAR两套软件架构，借助DDS协议栈的客户端服务器架构，通过DDS复杂驱动将DDS协议栈集成在CP AUTOSAR，从而能够在算力和资源相对受限的CP实时核集成DDS通信功能，在异构多核SOC芯片硬件平台上实现支持面向服务功能的标准化核间通信中间件；另一方面，CP AUTOSAR能够借助AP AUTOSAR的计算资源提高数据处理能力。
此外，在示例实施例中，汽车开放系统架构还包括静态配置模块和动态配置模块，其中，静态配置模块用于对DDS客户端和DDS代理对应的静态资源的配置项进行配置；动态配置模块用于对DDS客户端和DDS代理对应的动态资源的配置项进行配置。
在示例实施例中，将汽车开放系统架构的DDS协议栈组件包括静态配置模块和动态配置模块。静态配置模块采用开源平台经验证的成熟产品。动态配置模块以ARXML格式定制开发模块定义文件，定义DDS模块的配置项，对DDS客户端和DDS代理对应的动态资源的配置项进行配置。举例而言，使用开发工具链(例如Vector Davinci)导入ARXML文件并设置动态资源的各配置项，配合DDS协议栈组件对应的代码生成工具，实现动态配置代码生成及开发工具链融合。
根据上述示例实施例中的技术方案，通过静态配置模块对DDS客户端和DDS代理对应的静态资源的配置项进行配置；通过动态配置模块对DDS客户端和DDS代理对应的动态资源的配置项进行配置，能够实现DDS协议栈在经典平台AUTOSAR平台的无缝集成，集成方案可兼容各种版本的CP AUTOSAR标准，并可与CP AUTOSAR开发工具链、开发流程充分融合。
图4示出了根据本申请的另一些实施例提供的汽车开放系统架构的示意图。
参照图4所示，AUTOSAR还包括：发布者模块410以及订阅者模块420，订阅者模块420设置于CP AUTOSAR的应用层，发布者模块410设置于AP AUTOSAR的应用层，其中：发布者模块410作为服务提供者用于向CP AUTOSAR提供数据对象；订阅者模块420作为服务消费者用于从所述AP AUTOSAR获取需要的数据对象。
进一步地，在示例实施例中，DCPS层还包括全局数据空间，全局数据空间的物理存储空间可以位于硬件层350的共享存储空间，发布者模块410用于通过全局数据空间向CP AUTOSAR提供数据对象；订阅者模块420用于通过全局数据空间从AP AUTOSAR获取需要的数据对象。DDS提供了数据分布的基础架构，确保正确有效地传输信息给适当的接收者。DDS的DCPS层建立了一个全局数据空间的概念，发布者和订阅者在全局空间中分别发布和订阅自己需要的数据类型，通过中间件处理后，再进行数据传送，将传统C/S模式转为以数据为中心的服务模式。
根据图4的示例实施例中的技术方案，DDS的DCPS层建立了一个全局数据空间的概念，发布者和订阅者在全局空间中分别发布和订阅自己需要的数据类型，通过中间件处理后，再进行数据传送，将传统C/S模式转为以数据为中心的服务模式，减弱了信息发布者与订阅者之间的关系，使得系统各个组成部分间去除耦合，增强系统架构的灵活性，便于系统的维护和规模的扩展。
下述为本申请方法实施例，对于本申请方法实施例中未披露的细节，请参照本申请汽车开放系统架构实施例。
图5示出了根据本申请的一些实施例提供的数据处理方法的示意图。
参照图5所示，该数据处理方法，应用于汽车开放系统架构，所述汽车开放系统架构包括经典平台CP汽车开放系统架构，所述CP AUTOSAR包括数据分发服务DDS协议栈组件，所述DDS协议栈组件以复杂驱动形式集成在所述CP AUTOSAR，所述DDS协议栈组件包括DCPS层和DLR层，所述方法包括：
步骤510，通过DCPS层接收应用程序发布或订阅的目标服务的数据对象；
步骤520，通过DLR层对应用程序发布或订阅的目标服务的数据对象进行重构。
在一些示例实施例中，基于上述方案，所述汽车开放系统架构还包括自适应AP AUTOSAR，所述AP AUTOSAR包括DDS代理，所述方法还包括：
通过所述DDS代理的服务接口与所述DDS客户端进行通信，接收所述DDS客户端的服务数据，并对所述服务数据进行处理。
在一些示例实施例中，基于上述方案，所述汽车开放系统架构还包括静态配置模块和动态配置模块，所述方法还包括：
通过所述静态配置模块对所述DDS客户端和所述DDS代理对应的静态资源的配置项进行配置；
通过所述动态配置模块对所述DDS客户端和所述DDS代理对应的动态资源的配置项进行配置。
在一些示例实施例中，基于上述方案，所述CP AUTOSAR与所述AP AUTOSAR均包括应用层、运行环境层和基础软件层，所述应用层与所述基础软件层之间通过所述运行环境层通信。
在一些示例实施例中，基于上述方案，所述汽车开放系统架构还包括：发布者模块以及订阅者模块，所述订阅者模块设置于所述CP AUTOSAR的所述应用层，所述发布者模块设置于所述AP AUTOSAR的所述应用层，所述方法还包括：
通过所述发布者模块向所述CP AUTOSAR提供数据对象；
通过所述订阅者模块从所述AP AUTOSAR获取需要的数据对象。
在一些示例实施例中，基于上述方案，所述DCPS层还包括全局数据空间，所述方法还包括：
所述发布者模块通过所述全局数据空间向所述CP AUTOSAR提供数据对象；
所述订阅者模块通过所述全局数据空间从所述AP AUTOSAR获取需要的数据对象。
在一些示例实施例中，基于上述方案，所述方法还包括：
对所述DCPS层提供的服务以服务类的形式进行封装，所述服务类以本地语言结构的形式生成；建立服务类与DCPS层对应的服务之间的对应关系。
根据图5的示例实施例中的技术方案，一方面，将DDS协议栈组件以复杂驱动形式进行封装和定制化集成到CP AUTOSAR，能够在经典AUTOSAR中集成DDS协议栈；另一方面，DDS协议栈组件的DLR层建立在下层DCPS层的基础上，通过将DCPS层提供的服务整合到应用层，使用户能直接访问变更的数据，达到与本地语言结构无缝连接。
需要说明的是，上述实施例提供的汽车开放系统架构在执行汽车开放系统架构时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同 的功能模块，以完成以上描述的全部或者部分功能。
另外，上述实施例提供的汽车开放系统架构与数据处理方法实施例属于同一构思，其体现实现过程详见汽车开放系统架构的实施例，这里不再赘述。
本申请实施例还提供了一种计算机存储介质，所述计算机存储介质可以存储有多条指令，所述指令适于由处理器加载并执行如上述实施例的所述数据处理方法，具体执行过程可以参见上述实施例的具体说明，在此不进行赘述。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品存储有至少一条指令，所述至少一条指令由所述处理器加载并执行如上述实施例的所述数据处理方法，具体执行过程可以参见上述实施例的具体说明，在此不进行赘述。
本申请实施例还提供一种芯片，该芯片被配置成执行如上述实施例的所述数据处理方法，具体执行过程可以参见上述实施例的具体说明，在此不进行赘述。
此外，请参见图6，为根据本申请的一些实施例提供的一种车载设备的结构示意图。如图6所示，所述车载设备600可以包括：至少一个处理器601，至少一个通信模块604，输入输出接口603，存储器605，至少一个通信总线602。
其中，通信总线602用于实现这些组件之间的连接通信。
其中，输入输出接口603可以包括显示屏(Display)、摄像头(Camera)，可选输入输出接口603还可以包括标准的有线接口、无线接口。
其中，通信模块604可选的可以包括标准的有线接口、无线接口(如WIFI接口)。通信模块604包括第一网关例如S2S网关和第二网关例如C2C网关，第一网关采用第一通信协议进行通信，第二网关采用第二通信协议进行通信。
其中，处理器601可以包括一个或者多个处理核心。处理器601利用各种借口和线路连接整个车载设备600内的各个部分，通过运行或执行存储在存储器605内的指令、程序、代码集或指令集，以及调用存储在存储器605内的数据，执行服务器600的各种功能和处理数据。可选的，处理器601可以采用数字信号处理(Digital Signal Processing，DSP)、现场可编程门阵列(Field-Programmable Gate Array，FPGA)、可编程逻辑阵列(Programmable Logic Array，PLA)中的至少一种硬件形式来实现。处理器601可集成中央处理器 (Central Processing Unit，CPU)、图形处理器(Graphics Processing Unit，GPU)和调制解调器等中的一种或几种的组合。其中，CPU主要处理操作系统、用户界面和应用程序等；GPU用于负责显示屏所需要显示的内容的渲染和绘制；调制解调器用于处理无线通信。可以理解的是，上述调制解调器也可以不集成到处理器601中，单独通过一块芯片进行实现。
其中，存储器605可以包括随机存储器(Random Access Memory，RAM)，也可以包括只读存储器(Read-Only Memory)。可选的，该存储器605包括非瞬时性计算机可读介质(non-transitory computer-readable storage medium)。存储器605可用于存储指令、程序、代码、代码集或指令集。存储器605可包括存储程序区和存储数据区，其中，存储程序区可存储用于实现操作系统的指令、用于至少一个功能的指令(比如触控功能、声音播放功能、图像播放功能等)、用于实现上述各个方法实施例的指令等；存储数据区可存储上面各个方法实施例中涉及到的数据等。存储器605可选的还可以是至少一个位于远离前述处理器601的存储装置。如图6所示，作为一种计算机存储介质的存储器605中可以包括操作系统、通信模块、输入输出接口模块以及数据处理应用程序。
在图6所示的车载设备600中，输入输出接口603主要用于为用户提供输入的接口，获取用户输入的数据；而处理器601可以用于调用存储器605中存储的数据处理应用程序，使得处理器601执行根据本公开各种示例性实施例的数据处理方法中的步骤。车载设备600包括汽车开放系统架构，所述汽车开放系统架构包括经典平台CP AUTOSAR，所述CP AUTOSAR包括数据分发服务DDS协议栈组件，所述DDS协议栈组件以复杂驱动形式集成在所述CP AUTOSAR，所述DDS协议栈组件包括DCPS层和DLR层，例如，处理器601可以执行如图5中所示的步骤：步骤510，通过所述DCPS层接收应用程序发布或订阅的目标服务的数据对象；步骤520，通过DLR层对所述应用程序发布或订阅的目标服务的数据对象进行重构。
上述为本说明书实施例的一种车载设备的示意性方案，该车载设备可以为中央网关，也可以为其他适当的设备例如车载网关等。需要说明的是，该车载设备的技术方案与上述的汽车开放系统架构的技术方案属于同一构思，车载设备的技术方案未详细描述的细节内容，均可以参见上述汽车开放系统架构处理 方法的技术方案的描述。
在本申请的描述中，需要理解的是，术语“第一”、“第二”等仅用于描述目的，而不能理解为指示或暗示相对重要性。在本申请的描述中，需要说明的是，除非另有明确的规定和限定，“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其他步骤或单元。对于本领域的普通技术人员而言，可以具体情况理解上述术语在本申请中的具体含义。此外，在本申请的描述中，除非另有说明，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体或随机存储记忆体等。
以上所揭露的仅为本申请较佳实施例而已，当然不能以此来限定本申请之权利范围，因此依本申请权利要求所作的等同变化，仍属本申请所涵盖的范围。

Claims (15)

  1. 一种汽车开放系统架构，包括经典平台CP汽车开放系统架构(101)，其中：
    所述CP汽车开放系统架构(101)包括数据分发服务DDS协议栈组件(132)，所述DDS协议栈组件(132)以复杂驱动形式集成在所述CP汽车开放系统架构(101)；
    所述DDS协议栈组件(132)包括：以数据为中心的发布订阅DCPS层(1322)和数据本地重构DLR层(1324)，DCPS层(1322)用于接收应用程序发布或订阅目标服务的数据对象，DLR层(1324)用于对所述应用程序发布或订阅的目标服务的数据对象进行重构。
  2. 根据权利要求1所述的汽车开放系统架构，其中，DDS协议栈组件(132)还包括DDS客户端(310)，所述汽车开放系统架构(100)还包括自适应AP汽车开放系统架构(102)，所述AP汽车开放系统架构(102)包括DDS代理(320)，所述DDS代理(320)用于通过服务接口(330)与所述DDS客户端(310)进行通信，接收所述DDS客户端(310)的服务数据，并对所述服务数据进行处理。
  3. 根据权利要求2所述的汽车开放系统架构，其中，所述汽车开放系统架构(100)还包括静态配置模块和动态配置模块，所述静态配置模块用于对所述DDS客户端(310)和所述DDS代理(320)对应的静态资源的配置项进行配，所述动态配置模块用于对所述DDS客户端(310)和所述DDS代理(320)对应的动态资源的配置项进行配置。
  4. 根据权利要求2所述的汽车开放系统架构，其中，所述CP汽车开放系统架构(101)与所述AP汽车开放系统架构(102)均包括应用层(110)、运行环境层(120)和基础软件层(130)，所述应用层(110)与所述基础软件层(130)之间通过所述运行环境层(120)通信。
  5. 根据权利要求4所述的汽车开放系统架构，其中，所述汽车开放系统架构(100)还包括：发布者模块(410)以及订阅者模块(420)，所述订阅者模块(420)设置于所述CP汽车开放系统架构(101)的所述应用层(110)，所述发布者模块(410)设置于所述AP汽车开放系统架构(102)的所述应用层(110)，所述发布者模块(410)用于向所述CP汽车开放系统架构(101)提供数据对象，所述订阅者模块(420)用于从所述AP汽车开放系统架构(102)获取需要的数据对象。
  6. 根据权利要求2所述的汽车开放系统架构，其中，所述DCPS层(1322)还包括全局数据空间、发布者模块(410)以及订阅者模块(420)，所述发布者模块(410)用于通过所述全局数据空间向所述CP汽车开放系统架构(101)提供数据对象，所述订阅者模块(420)用于通过所述全局数据空间从所述AP汽车开放系统架构(102)获取需要的数据对象。
  7. 根据权利要求1至6中任一项所述的汽车开放系统架构，其中，所述DLR层(1324)包括封装模块和索引模块，所述封装模块用于对所述DCPS层(1322)提供的服务以服务类的形式进行封装，所述服务类以本地语言结构的形式生成，所述索引模块用于建立服务类与DCPS层(1322)对应的服务之间的对应关系。
  8. 一种数据处理方法，应用于权利要求1-7任一项所述的汽车开放系统架构(100)，所述方法包括：
    (510)通过DCPS层(1322)接收应用程序发布或订阅的目标服务的数据对象；
    (520)通过DLR层(1324)对所述应用程序发布或订阅的目标服务的数据对象进行重构。
  9. 根据权利要求8所述的方法，其中，所述汽车开放系统架构(100)还包括自适应AP汽车开放系统架构(102)，所述AP汽车开放系统架构(102)包括DDS代理(320)，所述方法还包括：
    通过所述DDS代理(320)的服务接口(330)与DDS客户端(310)进行通信，接收所述DDS客户端(310)的服务数据，并对所述服务数据进行处理。
  10. 根据权利要求9所述的方法，其中，所述汽车开放系统架构(100)还包括静态配置模块和动态配置模块，所述方法还包括：
    通过所述静态配置模块对所述DDS客户端(310)和所述DDS代理(320)对应的静态资源的配置项进行配置；
    通过所述动态配置模块对所述DDS客户端(310)和所述DDS代理(320)对应的动态资源的配置项进行配置。
  11. 根据权利要求9所述的方法，其中，CP汽车开放系统架构(101)与所述AP汽车开放系统架构(102)均包括应用层(110)、运行环境层(120)和基础软件层(130)，所述应用层(110)与所述基础软件层(130)之间通过所述运行环境层(120)通信。
  12. 根据权利要求11所述的方法，其中，所述汽车开放系统架构(100)还包括：发布者模块(410)以及订阅者模块(420)，所述订阅者模块(420)设置于所述CP汽车开放系统架构(101)的所述应用层(110)，所述发布者模块(410)设置于所述AP汽车开放系统架构(102)的所述应用层(110)，所述方法还包括：
    通过所述发布者模块(410)向所述CP汽车开放系统架构(101)提供数据对象；
    通过所述订阅者模块(420)从所述AP汽车开放系统架构(102)获取需要的数据对象。
  13. 根据权利要求12所述的方法，其中，所述DCPS层(1322)还包括全局数据空间，所述方法还包括：
    所述发布者模块(410)通过所述全局数据空间向所述CP汽车开放系统架构(101)提供数据对象；
    所述订阅者模块(420)通过所述全局数据空间从所述AP汽车开放系统架构(102)获取需要的数据对象。
  14. 根据权利要求12所述的方法，其中，所述DLR层(1324)包括封装模块和索引模块，所述方法还包括：
    所述封装模块对所述DCPS层(1322)提供的服务以服务类的形式进行封装，所述服务类以本地语言结构的形式生成；
    所述索引模块建立服务类与DCPS层(1322)对应的服务之间的对应关系。
  15. 一种车载设备(600)，包括：处理器(601)和存储器(605)，所述存储器(605)存储有计算机程序，所述计算机程序适于由所述处理器(601)加载并执行如权利要求8-14任一项所述方法的步骤。
PCT/CN2023/126206 2022-11-01 2023-10-24 汽车开放系统架构、数据处理方法及车载设备 WO2024093731A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211352867.4 2022-11-01
CN202211352867.4A CN115766915A (zh) 2022-11-01 2022-11-01 汽车开放系统架构、数据处理方法、介质及车载设备

Publications (1)

Publication Number Publication Date
WO2024093731A1 true WO2024093731A1 (zh) 2024-05-10

Family

ID=85354930

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/126206 WO2024093731A1 (zh) 2022-11-01 2023-10-24 汽车开放系统架构、数据处理方法及车载设备

Country Status (2)

Country Link
CN (1) CN115766915A (zh)
WO (1) WO2024093731A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115766915A (zh) * 2022-11-01 2023-03-07 长城汽车股份有限公司 汽车开放系统架构、数据处理方法、介质及车载设备

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105205183A (zh) * 2015-10-29 2015-12-30 哈尔滨工业大学 一种基于xml的dds分布式系统自动构建方法
US20180007076A1 (en) * 2016-06-29 2018-01-04 Argus Cyber Security Ltd. System and method for detection and prevention of attacks on in-vehicle networks
CN112104536A (zh) * 2020-11-02 2020-12-18 奥特酷智能科技(南京)有限公司 基于dds协议的汽车以太网总线设计方法
US20210294889A1 (en) * 2020-03-20 2021-09-23 Infineon Technologies Ag Data link layer authenticity and security for automotive communication system
CN114172938A (zh) * 2022-02-10 2022-03-11 诚迈科技（南京）股份有限公司 智能座舱soa化的实现方法、系统和智能汽车
CN115242565A (zh) * 2021-04-22 2022-10-25 华为技术有限公司 一种基于autosar实现dds通信的系统架构、通信方法及设备
CN115766915A (zh) * 2022-11-01 2023-03-07 长城汽车股份有限公司 汽车开放系统架构、数据处理方法、介质及车载设备

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105205183A (zh) * 2015-10-29 2015-12-30 哈尔滨工业大学 一种基于xml的dds分布式系统自动构建方法
US20180007076A1 (en) * 2016-06-29 2018-01-04 Argus Cyber Security Ltd. System and method for detection and prevention of attacks on in-vehicle networks
US20210294889A1 (en) * 2020-03-20 2021-09-23 Infineon Technologies Ag Data link layer authenticity and security for automotive communication system
CN112104536A (zh) * 2020-11-02 2020-12-18 奥特酷智能科技(南京)有限公司 基于dds协议的汽车以太网总线设计方法
CN115242565A (zh) * 2021-04-22 2022-10-25 华为技术有限公司 一种基于autosar实现dds通信的系统架构、通信方法及设备
CN114172938A (zh) * 2022-02-10 2022-03-11 诚迈科技（南京）股份有限公司 智能座舱soa化的实现方法、系统和智能汽车
CN115766915A (zh) * 2022-11-01 2023-03-07 长城汽车股份有限公司 汽车开放系统架构、数据处理方法、介质及车载设备

Also Published As

Publication number Publication date
CN115766915A (zh) 2023-03-07

Similar Documents

Publication Publication Date Title
US8078357B1 (en) Application-independent and component-isolated system and system of systems framework
US7865597B2 (en) Method for smart device network application infrastructure (SDNA)
US6226692B1 (en) Method and system for constructing software components and systems as assemblies of independent parts
US6947965B2 (en) System and method for communications in a distributed computing environment
US6484214B1 (en) Method for distributed object communications based on dynamically acquired and assembled software components
WO2022016848A1 (zh) 一种根据服务角色的进行应用部署的方法及装置
US20030037174A1 (en) Common adapter/connector architecture
US20070192768A1 (en) Computer processing and programming method using dynamic block, streaming and synchronizing data handling
WO2024093731A1 (zh) 汽车开放系统架构、数据处理方法及车载设备
Tigli et al. Lightweight service oriented architecture for pervasive computing
WO2022222901A1 (zh) 一种基于autosar实现dds通信的系统架构、通信方法及设备
US20200334401A1 (en) Modeling with digital twins
US20180011705A1 (en) Melding of mediation flow service component architecture (sca) components
US20200278891A1 (en) Dynamic Load Balancing In Network Centric Process Control Systems
Jan et al. Flex‐eWare: a flexible model driven solution for designing and implementing embedded distributed systems
CN116389552A (zh) 一种基于发布订阅模型的异构数据传输系统
Aguirre et al. MCSARCH: An architecture for the development of manufacturing control systems
Lee et al. RSCA: Middleware supporting dynamic reconfiguration of embedded software on the distributed URC robot platform
Wang Component-based performance-sensitive real-time embedded software
de Almeida Rust-based SOME/IP implementation for robust automotive software
CN116996551B (zh) 一种基于soa化中央网络控制器的车载服务控制系统及方法
CN117170738B (zh) Python与Fortran互调用的方法、系统、设备及存储介质
Mihajlović et al. Challenges of Integrating Machine Vision Algorithms Based on Franca IDL into Adaptive AUTOSAR Environment
Kampmann A dynamic service-oriented software architecture for the automotive domain
CN109901826B (zh) 用于Java程序的数据处理方法、装置和电子设备

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: 23884663

Country of ref document: EP

Kind code of ref document: A1