KR102630360B1 - Static setting system and method of automotive open system architecture sensor interface - Google Patents

Abstract

A system and method for static configuration of an AUTOSAR sensor interface are disclosed. Multiple developer terminals that perform application development under AUTOSAR and pre-set sensor interfaces between applications; An integrated analyst terminal that checks errors in sensor interfaces preset by each of the plurality of developer terminals; An AUTOSAR development server is configured to provide an AUTOSAR development environment to the plurality of developer terminals, analyze errors in sensor interfaces preset by the plurality of developer terminals, and provide the information to the integrated analyst terminal. According to the static setting system and method of the AUTOSAR sensor interface described above, in the development stage of each application, the request port and the provision port are set in advance between the applications communicating with each other, and the sensor interface of each port, its type, and corresponding vector information to be used are set in advance. By being configured to be set in advance, there is an effect of reducing sensor data communication errors between each application and increasing operation stability during the actual operation stage of each application. Furthermore, in the AUTOSAR distributed development environment, errors in sensor interface settings between corresponding applications are automatically detected and provided, which has the effect of increasing the accuracy and efficiency of distributed development of applications.

Description

STATIC SETTING SYSTEM AND METHOD OF AUTOMOTIVE OPEN SYSTEM ARCHITECTURE SENSOR INTERFACE}

The present invention relates to AUTOSA (automotive open system architecture), and specifically to a system and method for static configuration of an AUTOSAR sensor interface.

AUTOSAR (AUTomotive Open System Architecture) is an open standard software architecture for automotive development. AUTOSAR has a distributed development environment for software mounted on electronic/electrical devices within vehicles.

In other words, AUTOSAR provides an environment that allows developers to distribute and simultaneously develop various applications for each function, that is, software provided in various sensors or control devices of a vehicle.

AUTOSAR is divided into a classic platform and an adaptive platform. The adaptive platform mainly deals with sensor data interfaces to implement autonomous driving functions. The sensor interface of the adaptive platform is defined to transmit and receive standard sensors and standard data models presented in ISO 23150.

However, ISO 23150 considers various situations and defines a data model to include elements that do not need to be used depending on the developer's choice. And in actual use, the sensor data model is used by filtering at the real-time communication stage whether each sensor data that makes up the model is a necessary element or not.

In this case, elements that do not need to be used are included in sensor data transmitted and received between applications, which may cause functional malfunction. In other words, if data not defined in the sensor data model is not properly filtered in real time at the communication stage between each application, there is a very high probability that errors will occur during operation of the applications.

Accordingly, a method to reduce errors that may occur in existing inter-application communication is required.

Registered Patent Publication 10-1967450 Registered Patent Publication 10-1584213

The object of the present invention is to provide a static configuration system for an AUTOSAR sensor interface.

Another object of the present invention is to provide a method for static setting of an AUTOSAR sensor interface.

The static setting system for the AUTOSAR sensor interface according to the purpose of the present invention described above includes a plurality of developer terminals that perform development of applications under AUTOSAR and pre-set sensor interfaces between applications; An integrated analyst terminal that checks errors in sensor interfaces preset by each of the plurality of developer terminals; It may be configured to include an AUTOSAR development server that provides an AUTOSAR development environment to the plurality of developer terminals, analyzes errors in sensor interfaces preset by the plurality of developer terminals, and provides the data to the integrated analyst terminal.

Here, the AUTOSAR development server includes: an AUTOSAR application development device in which sensor interfaces of each application being developed by the plurality of developer terminals are set by each developer terminal; a sensor interface storage device that stores the sensor interface set by the AUTOSAR application development device; It may be configured to include a sensor interface analysis device that automatically detects errors by analyzing the sensor interface stored in the sensor interface storage device.

Additionally, the AUTOSAR application development device may be configured to store the sensor interface in the interface storage device in the form of an ARXML file.

In addition, the AUTOSAR development server may be configured to further include a tree-type list providing device that converts the sensor interface in the form of an ARXML file stored in the sensor interface storage device into a tree-type list and provides it to the corresponding developer terminal.

The AUTOSAR application development device includes a sensor interface definition module that defines a sensor interface and its type for each application being developed by the plurality of developer terminals; It may be configured to include an information vector definition module that defines an information vector constituting the sensor interface defined in the sensor interface definition module.

The static setting method of an AUTOSAR sensor interface according to another object of the present invention described above includes the steps of having a plurality of developer terminals perform development of an application under AUTOSAR on an AUTOSAR development server, and pre-setting a sensor interface between applications; An AUTOSAR development server storing sensor interfaces preset by the plurality of developer terminals and analyzing and detecting errors in the stored sensor interfaces; The integrated analyst terminal may be configured to include the step of checking errors in sensor interfaces that are each preset by the plurality of developer terminals.

Here, the AUTOSAR development server stores sensor interfaces preset by the plurality of developer terminals, and the step of analyzing and detecting errors in the stored sensor interfaces includes the sensor interface of each application being developed by the plurality of developer terminals. , the type and port of the sensor interface can be configured to be set respectively.

And in the step of the AUTOSAR development server storing sensor interfaces preset by the plurality of developer terminals and analyzing and detecting errors in the stored sensor interfaces, the port is configured as a request port or a provision port, and the request port or Information vectors constituting each provision port may be configured to be set.

In addition, the AUTOSAR development server stores sensor interfaces preset by the plurality of developer terminals, and the step of analyzing and detecting errors in the stored sensor interfaces may be configured to store the sensor interfaces in the form of an ARXML file.

And the AUTOSAR development server stores sensor interfaces preset by the plurality of developer terminals, and the step of analyzing and detecting errors in the stored sensor interfaces includes the sensor interface in the form of an ARXML file stored in the sensor interface storage device. It can be configured to be converted into a type list and provided to the developer terminal.

According to the static setting system and method of the AUTOSAR sensor interface described above, in the development stage of each application, the request port and the provision port are set in advance between the applications communicating with each other, and the sensor interface of each port, its type, and corresponding vector information to be used are set in advance. By being configured to be set in advance, there is an effect of reducing sensor data communication errors between each application and increasing operation stability during the actual operation stage of each application.

Furthermore, in the AUTOSAR distributed development environment, errors in sensor interface settings between corresponding applications are automatically detected and provided, which has the effect of increasing the accuracy and efficiency of distributed development of applications.

1 is a block diagram of a static configuration system for an AUTOSAR sensor interface according to an embodiment of the present invention.
Figure 2 is an example diagram of a sensor interface definition screen according to an embodiment of the present invention.
Figure 3 is a block diagram showing the structure of a communication port according to an embodiment of the present invention.
Figure 4 is an exemplary diagram of an information vector definition screen according to an embodiment of the present invention.
Figure 5 is a flowchart of a method for statically setting an AUTOSAR sensor interface according to an embodiment of the present invention.

Since the present invention can make various changes and have various embodiments, specific embodiments will be illustrated in the drawings and detailed descriptions will be given for carrying out the invention. However, this is not intended to limit the present invention to specific embodiments, and should be understood to include all changes, equivalents, and substitutes included in the spirit and technical scope of the present invention. While describing each drawing, similar reference numerals are used for similar components.

Terms such as first, second, A, and B may be used to describe various components, but the components should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, a first component may be named a second component, and similarly, the second component may also be named a first component without departing from the scope of the present invention. The term and/or includes any of a plurality of related stated items or a combination of a plurality of related stated items.

When a component is said to be "connected" or "connected" to another component, it is understood that it may be directly connected to or connected to the other component, but that other components may exist in between. It should be. On the other hand, when it is mentioned that a component is “directly connected” or “directly connected” to another component, it should be understood that there are no other components in between.

The terms used in this application are only used to describe specific embodiments and are not intended to limit the invention. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this application, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the technical field to which the present invention pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and unless explicitly defined in the present application, should not be interpreted in an ideal or excessively formal sense. No.

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the attached drawings.

1 is a block diagram of a static configuration system for an AUTOSAR sensor interface according to an embodiment of the present invention. And Figure 2 is an exemplary diagram of a sensor interface definition screen according to an embodiment of the present invention, Figure 3 is a block diagram showing the structure of a communication port according to an embodiment of the present invention, and Figure 4 is an example of a sensor interface definition screen according to an embodiment of the present invention. This is an example of an information vector definition screen according to an embodiment.

Referring to FIG. 1, the static setting system of the AUTOSAR sensor interface according to an embodiment of the present invention may be configured to include a developer terminal 100, an integrated analyst terminal 200, and an AUTOSAR development server 300.

Hereinafter, the detailed configuration will be described.

The developer terminal 100 performs application development under AUTOSAR and may be configured to pre-set sensor interfaces between applications. Multiple developer terminals 100 can develop each application in the AUTOSAR distributed development environment. The AUTOSAR development server 300 may be configured to provide such an AUTOSAR distributed development environment.

Previously, the specific contents of the sensor interface between applications were not set in advance and were operated by dynamically filtering during the communication process between applications. However, in the present invention, the specific contents of the sensor interface are set in advance to prevent errors occurring in the actual communication process. can be reduced.

The integrated analyst terminal 200 may be configured to check errors in sensor interfaces that are each preset by a plurality of developer terminals 100.

The AUTOSAR development server 300 provides an AUTOSAR development environment to a plurality of developer terminals 100, analyzes errors in the sensor interface preset by the plurality of developer terminals 100, and provides it to the integrated analyst terminal 200. It can be configured.

Here, sensor interface errors refer to inconsistencies or configuration errors in the sensor interface definition process between applications being developed in each developer's application development environment. The integrated analyst can check errors in each sensor interface and allow developers to reflect them in application development/modification.

The AUTOSAR development server 300 may be configured to include an AUTOSAR application development device 310, a sensor interface storage device 320, a sensor interface analysis device 330, and a tree-type list providing device 340.

Hereinafter, the detailed configuration will be described.

The AUTOSAR application development device 310 may be configured so that the sensor interface of each application being developed by a plurality of developer terminals 100 is set by each developer terminal 100.

The AUTOSAR application development device 310 may be configured to include a sensor interface definition module 311 and an information vector definition module 312. Depending on the input or settings of the developer terminal 100, it can be configured to selectively define the port, the type of sensor interface, and the information vector that the application wants to use in the sensor interface.

Here, the sensor interface definition module 311 may be configured to define the sensor interface and corresponding type of each application being developed by a plurality of developer terminals 100.

And the sensor interface definition module 311 may be configured to include a request port setting unit 311a and a provision port setting unit 311a.

The request port setting unit 311a may be configured to set a request port for each application being developed by a plurality of developer terminals 100. Additionally, the provision port setting unit 311a may be configured to set the provision port of each application being developed by a plurality of developer terminals 100.

Each application may request sensor data from other applications or provide its own data according to the needs of other applications. According to this communication process, each application can be set by adding a request port for a specific application or by adding a provided port for a specific application.

Figure 2 illustrates a sensor interface definition screen for each port. And Figure 3 illustrates the sensor interface and the type of sensor interface for each port.

Meanwhile, the information vector definition module 312 may be configured to define an information vector constituting the sensor interface defined in the sensor interface definition module 311.

Information vectors are elements that make up a sensor interface, and the information vectors required by each application can be selectively defined.

Figure 4 illustrates the definition screen of an information vector. Represents the information vectors that make up the RoadObect type sensor interface. An application may only need the information vectors of Color model type and Road surface list for the other application in the corresponding sensor interface. In this case, the other application also needs to selectively provide only the above information vectors.

Previously, if communication between applications took place without defining such information vectors, each application performed dynamic filtering on its own during the communication process. Many errors occurred during this process. However, in the present invention, such errors can be prevented because the information vectors required for specific ports and sensor interfaces are predefined between applications.

The sensor interface storage device 320 may be configured to store the sensor interface set by the AUTOSAR application development device 310.

The sensor interface storage device 320 may be configured to store ARXML.

The sensor interface analysis device 330 may be configured to automatically detect errors by analyzing the sensor interface stored in the sensor interface storage device 320.

The sensor interface analysis device 330 includes an application-to-application sensor interface read module 331, a request port/provided port pair list creation module 332, an integer bit data change module 333, a bit sum operation module 334, and an error detection module. It may be configured to include a module 335 and an automatic error notification module 336.

Hereinafter, the detailed configuration will be described.

The inter-application sensor interface reading module 331 may be configured to read the inter-application sensor interface corresponding to the sensor interface stored in the sensor interface storage device 320.

The request port/provided port pair list creation module 332 may be configured to generate a list consisting of pairs of corresponding request ports and provided ports from the inter-application sensor interface read by the inter-application sensor interface reading module 331.

The integer bit data change module 333 may be configured to change each pair of request ports and offer ports in the list generated by the request port/provided port pair list creation module 332 into integer bit data. For example, if there are 4 information vectors of a specific sensor interface and only the 1st and 3rd information vectors are used in order, set '1' to the information vector to be used. Otherwise, set '1' to the information vector to be used. You can set '0'. At this time, the integer bit data can be set to '1010'.

The bit sum operation module 334 may be configured to perform a bit sum operation on the integer bit data changed in the integer bit data change module 333 for each pair of request port and provision port. In the request port set in application A, the integer bit data is '1010', and in the provision port set in application B that communicates with application A, the integer bit data is set to '1010', so the sensor data is set. This can be seen as normal.

The bit sum operation may be configured to perform an AND operation on the bits of each digit. For example, the bit sum operation of '1010' and '1011' can be '1010'.

The error detection module 335 may be configured to detect an error according to the result of the bit sum operation performed by the bit sum operation module 334. If the result of the bit sum operation and the integer bit data of the request port match, it can be judged as normal, and if they do not match, it can be judged as having an error.

For example, if the integer bit data of the request port is '1010' and the integer bit data of the provision port is '1000', the bit sum operation is '1000'. In this case, the 3rd digit information vector cannot be obtained from the request port, so it can be viewed as an error.

At this time, in the bit sum operation, even if the integer bit data of the provision port is '1X1X', the bit operation sum with the integer bit data of the request port is always '1010'. In other words, since '1010' is displayed regardless of whether

The automatic error notification module 336 may be configured to automatically notify the integrated analyst terminal 200 and the corresponding developer terminal 100 of the error detected in the error detection module 335.

The tree-type list providing device 340 may be configured to provide the sensor interface stored in the sensor interface storage device 320 to the corresponding developer terminal 100 in the form of a tree-type list. A tree-like list format can be provided for developer visibility.

Figure 5 is a flowchart of a method for statically setting an AUTOSAR sensor interface according to an embodiment of the present invention.

Referring to FIG. 5, first, a plurality of developer terminals 100 perform application development under AUTOSAR of the AUTOSAR development server 300, and sensor interfaces between applications are set in advance (S110).

Next, the AUTOSAR development server 300 defines and stores the sensor interface of the application under development according to the settings of the plurality of developer terminals 100 (S120).

Here, the sensor interface, type, and corresponding request port/provision port of the application under development are set (S121), and the information vector of the request port or provision port is set (S122).

Next, the AUTOSAR development server 300 analyzes and detects errors in the sensor interface between applications (S130).

Specifically, it is as follows:

First, the corresponding inter-application sensor interfaces are read (S131), a list consisting of pairs of corresponding request ports and provision ports is generated from the inter-application sensor interface (S132), and each request port and provision port pair is selected from the list. It is changed to integer bit data (S133), a bit sum operation is performed on the integer bit data for each pair of request ports and provision ports (S134), and an error is detected according to the result of the bit sum operation (S135).

Next, the AUTOSAR development server 300 automatically notifies the integrated analyst terminal 200 and the corresponding developer terminal 100 of the inter-application sensor interface (S140).

Next, the integrated analyst terminal 200 and the corresponding developer terminal 100 check errors in the sensor interface (S150).

Although the description has been made with reference to the above examples, those skilled in the art can understand that various modifications and changes can be made to the present invention without departing from the spirit and scope of the present invention as set forth in the claims below. There will be.

100: Developer terminal
200: Integrated analyst terminal
300: AUTOSAR development server
310: AUTOSAR application development device
311: Sensor interface definition module
311a: Request port setting unit
311a: Provided port setting unit
312: Information vector definition module
320: sensor interface storage device
330: Sensor interface analysis device
331: Inter-application sensor interface readout module
332: Request port/provided port pair list creation module
333: Integer bit data change module
334: Bit sum operation module
335: Error detection module
336: Error automatic notification module
340: Tree-type list providing device

Claims (10)

Multiple developer terminals that perform application development under AUTOSAR and pre-set sensor interfaces between applications;
An integrated analyst terminal that checks errors in sensor interfaces preset by each of the plurality of developer terminals;
An AUTOSAR development environment is provided to the plurality of developer terminals, an information vector is defined by setting a request port and a provision port for each application being developed by the plurality of developer terminals, and sensors corresponding to each other based on the information vector An AUTOSAR development server that extracts the request port and the provision port from an interface, analyzes errors in the corresponding sensor interfaces using the extracted request port and the provision port, and provides the analysis to the integrated analyst terminal,
The AUTOSAR development server converts the extracted request port and the provided port into integer bit data, performs an AND operation, and analyzes the error by comparing it with the integer bit data of the request port. A static setting system for the AUTOSAR sensor interface.
According to paragraph 1,
The AUTOSAR development server is,
An AUTOSAR application development device in which sensor interfaces of each application being developed by the plurality of developer terminals are set by each developer terminal;
a sensor interface storage device that stores the sensor interface set by the AUTOSAR application development device;
A static setting system for an AUTOSAR sensor interface, comprising a sensor interface analysis device that automatically detects the error by analyzing the sensor interface stored in the sensor interface storage device.
According to paragraph 2,
The AUTOSAR application development device is,
A static setting system for an AUTOSAR sensor interface, characterized in that it is configured to store the sensor interface in the interface storage device in the form of an ARXML file.
According to paragraph 3,
The AUTOSAR development server is,
A static setting system for an AUTOSAR sensor interface, characterized in that it further includes a tree-type list providing device that converts the sensor interface in the form of an ARXML file stored in the sensor interface storage device into a tree-type list and provides it to the corresponding developer terminal.
According to paragraph 3,
The AUTOSAR application development device is,
a sensor interface definition module that defines a sensor interface and its type for each application being developed by the plurality of developer terminals;
A static setting system for an AUTOSAR sensor interface, characterized in that it is configured to include an information vector definition module that defines the information vectors constituting the sensor interface defined in the sensor interface definition module.
A plurality of developer terminals perform development of applications under AUTOSAR on an AUTOSAR development server, and pre-setting sensor interfaces between applications;
The AUTOSAR development server defines an information vector by setting the request port and provision port for each application being developed by the plurality of developer terminals, and extracts the request port and provision port from the corresponding sensor interface based on the information vector. and analyzing and detecting errors in the corresponding sensor interfaces using the extracted request port and the provision port; and
Comprising a step of the integrated analyst terminal checking errors in the sensor interfaces each preset by the plurality of developer terminals,
The step of analyzing and detecting errors in the sensor interface is,
The AUTOSAR development server converts the extracted request port and the provided port into integer bit data, performs an AND operation, and analyzes the error by comparing it with the integer bit data of the request port. Static setting method of an AUTOSAR sensor interface.
According to clause 6,
The step of analyzing and detecting errors in the sensor interface is,
A static setting method of an AUTOSAR sensor interface, characterized in that the sensor interface, sensor interface type, and port of each application being developed by the plurality of developer terminals are respectively set.
In clause 7,
The step of analyzing and detecting errors in the sensor interface is,
The port is configured as the request port or the provision port, and an information vector constituting the request port or the provision port, respectively, is configured to be set.
According to clause 6,
The step of analyzing and detecting errors in the sensor interface is,
A static setting method of an AUTOSAR sensor interface, characterized in that the sensor interface is configured to be saved in the form of an ARXML file.
According to clause 9,
The step of analyzing and detecting errors in the sensor interface is,
A static setting method of an AUTOSAR sensor interface, characterized in that it is configured to convert the sensor interface in the form of an ARXML file stored in the sensor interface storage device into a tree-type list and provide it to the corresponding developer terminal.

Images