WO2023127997A1 - Dispositif et procédé de génération automatique d'un code de configuration de surveillance d'état dans un système d'exploitation arinc pour une plateforme de véhicule - Google Patents

Dispositif et procédé de génération automatique d'un code de configuration de surveillance d'état dans un système d'exploitation arinc pour une plateforme de véhicule Download PDF

Info

Publication number
WO2023127997A1
WO2023127997A1 PCT/KR2021/020141 KR2021020141W WO2023127997A1 WO 2023127997 A1 WO2023127997 A1 WO 2023127997A1 KR 2021020141 W KR2021020141 W KR 2021020141W WO 2023127997 A1 WO2023127997 A1 WO 2023127997A1
Authority
WO
WIPO (PCT)
Prior art keywords
health monitoring
arinc
supervision
generating
partition
Prior art date
Application number
PCT/KR2021/020141
Other languages
English (en)
Korean (ko)
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 WO2023127997A1 publication Critical patent/WO2023127997A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3696—Methods or tools to render software testable
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3664—Environments for testing or debugging software
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3684—Test management for test design, e.g. generating new test cases
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3688—Test management for test execution, e.g. scheduling of test suites
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software
    • G06F11/3668—Software testing
    • G06F11/3672—Test management
    • G06F11/3692—Test management for test results analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601—Interfaces specially adapted for storage systems
    • G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0638—Organizing or formatting or addressing of data
    • G06F3/0644—Management of space entities, e.g. partitions, extents, pools

Definitions

  • the present invention relates to a vehicle operating system technology and an open automotive standard software architecture technology, and more particularly, to an ARINC-based operating system health monitoring setting code automatic generation method for a vehicle platform.
  • the present invention is an autonomous driving technology development innovation project (R & D) of the Ministry of Science and ICT (Task identification number: 1711134515, assignment number: 2021-0-00905-001, research project title: (3 details) Cloud, Edge, Car 3- Tier-linked recognition/determination/control SW and common SW platform technology development, research management specialized institution: National Institute of Information and Communications Technology Evaluation and Planning, supervising institution: Altist Co., Ltd., research period: 2021.04.01. ⁇ 2023.12.31.) derived from research.
  • AUTOSAR Software based on the open automotive standard software architecture (AUTomotive Open System Architecture: AUTOSAR) is software that is loaded and operated in electronic/electrical devices in vehicles, and is characterized by having a distributed and simultaneous development environment. Therefore, when developing an AUTOSAR-based system, it is very important to maintain consistent requirements and design throughout the system. To this end, AUTOSAR provides ARXML (AUTOSAR XML), an AUROSAR model in XML form, to maintain a consistent form of design.
  • ARXML AUTOSAR XML
  • AUROSAR model in XML form
  • Avionics Application Standard Software Interface is a standard for developing application software for aviation, and defines an interface between a real-time operating system and an application program running thereon.
  • ARINC configuration elements in XML form are provided separately.
  • ARINC 653-based operating system can be used as a base operating system for AUTOSAR-based platforms by providing real-time and safety.
  • the present invention proposes a method of generating health monitoring setting information usable in an ARINC 653-based operating system based on AUTOSAR setting information written in ARXML format.
  • An object of the present invention is to provide a technique for automatically generating health monitoring settings for an ARINC-based operating system from platform health management settings provided by AUTOSAR.
  • a method for automatically generating setting codes according to an embodiment of the present invention is performed in a computing device having one or more processors and a memory storing one or more programs executed by the one or more processors, always application standard software.
  • a method for automatically generating setting codes for interface (ARINC)-based health monitoring comprising: generating a SystemError element, which is one of ARINC setting elements, based on inputted open automotive standard software architecture (AUTOSAR) setting information; and generating a Partition element, which is one of the ARINC configuration elements, based on the AUTOSAR configuration information.
  • the AUTOSAR configuration information includes a PROCESS element and a GLOBAL-SUPERVISION element, and the global supervision element necessarily includes one or more LOCAL-SUPERVISION elements.
  • the local supervision element may include a LOGICAL-SUPERVISION element, a DEADLINE-SUPERVISION element, and an ALIVE-SUPERVISION element according to the configuration of process elements. .
  • the generating of the system error element may include generating one or more system error elements from the list of global supervision elements.
  • one or more partition elements may be created through one-to-one mapping with the process element.
  • the method of automatically generating the setting code may further include generating a health monitoring element based on the system error element and the partition element.
  • the generating of the health monitoring element may include analyzing a relationship between the system error element and the partition element based on AUTOSAR configuration information related to the system error element and the partition element; Analyzing a restoration level for each system error based on the correlation; generating a module health monitoring (ModuleHM) element based on the correlation and the restoration level; and generating a multipartition health monitoring (MultiPartitionHM) element based on the association relationship and the restoration level.
  • ModuleHM module health monitoring
  • MultiPartitionHM multipartition health monitoring
  • a computer-readable non-transitory storage medium having a program recorded thereon for executing the method of automatically generating setting codes for health monitoring based on ARINC is provided.
  • a computing device includes one or more processors; Memory; and one or more programs, wherein the one or more programs are stored in the memory, configured to be executed by the one or more processors, and a computing device for automatically generating setting code for ARINC-based health monitoring, wherein the one or more programs Commands for generating a SystemError element, which is one of the ARINC setting elements, based on the input AUTOSAR setting information; and a command for generating a Partition element, which is one of ARINC setting elements, based on the AUTOSAR setting information; and a command for generating a health monitoring element based on the system error element and the partition element.
  • ARINC setting elements necessary for operating health monitoring are automatically generated based on the ARINC manual and AUTOSAR setting information, so that application software developers for vehicles can use ARINC without deep understanding of the ARINC-based system. You will be able to help develop ARINC-based software for your platform easily. In addition, by automatically performing a setting operation to secure the stability of the developed application software, it is possible to improve the safety of the application software and productivity of development.
  • FIG. 1 is a diagram showing the configuration of an apparatus for automatically generating setting codes for health monitoring based on Avionics Application Standard Software Interface (ARINC) according to an embodiment of the present invention.
  • ARINC Avionics Application Standard Software Interface
  • FIG. 2 is a flowchart illustrating a method of automatically generating configuration codes for health monitoring based on Avionics Application Standard Software Interface (ARINC) according to an embodiment of the present invention.
  • ARINC Avionics Application Standard Software Interface
  • FIG. 3 is a block diagram illustrating and describing a computing environment including a computing device suitable for use in example embodiments.
  • FIG. 1 is a diagram showing the configuration of an apparatus for automatically generating setting codes for health monitoring based on an Avionics Application Standard Software Interface (ARINC) according to an embodiment of the present invention.
  • ARINC Avionics Application Standard Software Interface
  • an apparatus for automatically generating a setting code 100 may include a system error element generating module 102 , a partition element generating module 104 , and a health monitoring element generating module 106 .
  • the setting code automatic generation device 100 may be a device for automatically generating setting code elements (eg, ARINC setting elements, etc.) necessary for the operation of ARINC-based application software.
  • the system error element generating module 102 may receive AUTOSAR-based setting information and generate a SystemError element, which is an ARINC-based setting element.
  • the system error element is an element for specifying the type of error that can occur in an ARINC-based system.
  • the partition element generation module 104 may generate a SystemError element from a GLOBAL-SUPERVISION element that is an AUTOSAR XML (ARXML) element corresponding to AUTOSAR-based configuration information.
  • a SystemError element from a GLOBAL-SUPERVISION element that is an AUTOSAR XML (ARXML) element corresponding to AUTOSAR-based configuration information.
  • the GLOBAL-SUPERVISION element is an element for detecting a system error from the control flow of application software. That is, the global supervision element may be an element for expressing a system error itself to be detected for health monitoring. At this time, the global supervision element may be composed of one or more local supervision (LOCAL-SUPERVISION) to detect system errors from the control flow of application software.
  • LOCAL-SUPERVISION local supervision
  • the local supervision element is an element for detecting errors from the control flow of the application software.
  • the range of errors detected by local supervision elements is narrower than that of global supervision.
  • Local supervision elements include one or more logical-supervision (LOGICAL-SUPERVISION) elements, one or more deadline-supervision (DEADLINE-SUPERVISION) elements, and one or more alive-supervision (ALIVE-SUPERVISION) elements to detect errors from the control flow of the application software. SUPERVISION) elements.
  • the logical supervision element is an element for monitoring whether the control flow of the application software operates as designed. If it detects that the control flow of the application software operates in a form contrary to the design, the logical supervision element may determine that an error has occurred from the application software. The generated error is transferred to the local supervision element, which is the parent element.
  • the deadline supervision element is an element for monitoring whether a specific task of the application software is operated within a specified time. If the application software detects that it is taking more than the specified time to perform a particular task, the deadline supervision element may determine that an error has occurred from the application software. The generated error is transferred to the local supervision element, which is the parent element.
  • the Alive Supervision element is an element for monitoring whether the repetitive control flow in the application software operates as many times as specified. If the repetitive control flow of the application software is repeated less than or more than the specified number of times, the alive supervision element may determine that an error has occurred from the application software. The generated error is transferred to the local supervision element, which is the parent element.
  • the local supervision element determines whether there is an error based on error information transmitted from the logical supervision element, the deadline supervision element, and the alive supervision element, which are subordinate elements. If it is determined that an error has occurred, the corresponding information is transferred to the global supervision element, which is a higher level element.
  • the global supervision element determines whether there is an error based on the error information transmitted from the logical supervision element, which is a subordinate element. If it is determined that an error has occurred, the specified restoration work is performed for the error that has occurred.
  • ARINC-based health monitoring configuration can be performed by specifying restoration work for each system error based on a list of possible system errors. That is, the global supervision factor that can trigger the restoration work can be used in the same sense as the system error of the ARINC-based health monitoring setting.
  • system error element generating module 102 may derive a list of global supervision elements and generate a system error list according to the derived list of global supervision elements.
  • the partition element generation module 104 may generate a partition element from a PROCESS element that is an ARXML element corresponding to AUTOSAR-based configuration information.
  • a process element is an element for writing an execution method and constraints for a single executable file
  • a partition element is an element for specifying a single application software in an ARINC-based system for a vehicle platform.
  • the process element means application software in the AUTOSAR-based system
  • the partition element means application software in the ARINC-based system for the vehicle platform. That is, a process element and a partition element have a one-to-one mapping relationship, and one partition element can be created for a process element.
  • the health monitoring element generating module 106 may generate setting information related to ARINC-based health monitoring based on system error elements, partition elements, and AUTOSAR-based setting information.
  • the health monitoring element creation module 106 may generate a module health monitoring (ModuleHM) element and a multipartition health monitoring (MultiPartitionHM) element based on the system error element and the partition element and AUTOSAR-based configuration information. there is. That is, the health monitoring element generation module 106 may create a module health monitoring element and a multi-partition health monitoring element among ARINC configuration elements.
  • ModuleHM module health monitoring
  • MultiPartitionHM multipartition health monitoring
  • the health monitoring element generation module 106 includes a partition-system error correlation analysis unit 106a, a restoration level analysis unit 106b, a module health monitoring element generation unit 106c, and a multi-partition health monitoring element generation unit 106d.
  • the partition-system error correlation analysis unit 106a may analyze a relationship between a system error element and a partition element generated based on AUTOSAR-based configuration information.
  • the association between the system error element and the partition element may be expressed as a list of partitions in which a system error specified through a specific system error element may occur.
  • the relationship expressed in this way helps to determine the restoration level to be performed when a system error occurs. For example, in the case of a system failure involving only one partition, it may be sufficient to perform a restore operation on that partition only.
  • restoration work must be performed on all related partitions. That is, the restoration level for system errors can be identified through the relationship between system error factors and partition factors.
  • a process (PROCESS) element related to a partition element has an association with a global-supervision (GLOBAL-SUPERVISION) element related to a system error element.
  • GLOBAL-SUPERVISION global-supervision
  • Process elements can interact with the logical supervision, deadline supervision, and live supervision sub-elements of global supervision through the platform health management interface (PLATFORM-HEALTH-MANAGEMENT-INTERFACE). That is, a list of partitions that have an effect on generating a system error can be derived through the association between the process element and the global supervision element.
  • the restoration level analysis unit 106b may determine the restoration level to be performed for each system error based on the partition-system error correlation information.
  • the identified restoration level may be used to create a module health monitoring element and a multi-partition health monitoring element.
  • the module health monitoring element is an element that affects all partitions existing in the system
  • the multi-partition health monitoring element is an element that affects one or more partitions. Since restoration work through health monitoring consists of stopping and restarting modules and partitions, determining the restoration level is the same as selecting the type of partition to be stopped and restarted. In particular, since stopping and restarting a module means stopping and restarting all partitions, care must be taken not to create a module health monitoring element when the generated system error does not affect all partitions. That is, the module health monitoring element is created only when the list of partitions related to the system error is the same as the list of all partitions in the system.
  • the module level restoration is performed, and otherwise, the multi-partition level restoration is performed.
  • the module health monitoring element generation unit 106c may generate a module health monitoring element for a system error requiring restoration at the module level. At this time, the number of generated module health monitoring elements depends on the number of modules configured in the system.
  • the module health monitoring element generation unit 106c may generate module health monitoring elements limited to system error elements having a relation with all partitions in the system.
  • Restoration operations that can be performed by the module health monitoring element include stopping and restarting the module.
  • a restoration task is determined by a developer or an integrator, but in the present invention, a restart of a module is used as a basic restoration task.
  • the multi-partition health monitoring element generating unit 106d may create a multi-partition health monitoring element for a system error requiring restoration at the multi-partition level. At this time, the created multi-partition health monitoring elements must ensure that the partitions included in each other do not overlap. For example, if the associations of partitions A, B, and C for system errors X, Y, and Z are equal to (A,B), (C), and (A,B), the multi-partition health monitoring element ( Two can be created for A,B) and (C).
  • the multi-partition health monitoring element generation unit 106d generates multi-partition health monitoring elements only for system error elements that do not have a relationship with all partitions in the system, and generates partition health monitoring elements for all partitions. can create
  • the partition health monitoring element is an element for specifying a restoration method for one partition, and may be configured to separately specify restoration work at a partition and task level.
  • the present invention assumes that a partition is composed of only one task, it must be configured to perform a partition-level restoration job unconditionally. That is, the partition health monitoring element can always be configured with default values for partition-related system errors.
  • FIG. 2 is a flowchart illustrating a method of automatically generating configuration codes for health monitoring based on Avionics Application Standard Software Interface (ARINC) according to an embodiment of the present invention.
  • the method is divided into a plurality of steps, but at least some of the steps are performed in reverse order, combined with other steps, performed together, omitted, divided into detailed steps, or not shown.
  • One or more steps may be added and performed.
  • the apparatus 100 for automatically generating a setting code generates a system error element based on input AUTOSAR-based setting information (S101).
  • the apparatus 100 for automatically generating a setting code may generate a system error element by receiving a GLOBAL-SUPERVISION element that is an ARXML (AUTOSAR XML) element corresponding to AUTOSAR-based setting information.
  • a GLOBAL-SUPERVISION element that is an ARXML (AUTOSAR XML) element corresponding to AUTOSAR-based setting information.
  • the automatic setting code generation device 100 generates a partition element based on the input AUTOSAR-based setting information (S103).
  • the apparatus 100 for automatically generating a setting code may generate a partition element by receiving a PROCESS element, which is an ARXML (AUTOSAR XML) element corresponding to AUTOSAR-based setting information.
  • the automatic setting code generation device 100 analyzes the relationship between the two elements based on the previously generated system error and partition element (S105).
  • the apparatus 100 for automatically generating configuration codes may analyze a correlation between two elements based on AUTOSAR-based configuration information associated with a system error and a partition element.
  • the automatic setting code generation device 100 determines the restoration level for each system error element based on the correlation between the analyzed system error and the partition element (S107).
  • the automatic setting code generation device 100 generates a module health monitoring (ModuleHM) element based on the determined restoration level (S109).
  • the apparatus 100 for automatically generating a setting code may generate a restoration task in a module health monitoring element with a module restart (RESET) as a default value.
  • REET module restart
  • the apparatus 100 for automatically generating a setting code generates a multi-partition health monitoring (ModuleHM) element based on the identified restoration level (S111).
  • the apparatus 100 for automatically generating the setting code is configured so that the generated multi-partition health monitoring elements do not include overlapping partitions.
  • FIG. 3 is a block diagram illustrating and describing a computing environment 10 including a computing device suitable for use in example embodiments.
  • each component may have different functions and capabilities other than those described below, and may include additional components other than those described below.
  • the illustrated computing environment 10 includes a computing device 12 .
  • the computing device 12 may be the device 100 for automatically generating setting codes for application software based on AUTOSAR (AUTomotive Open System Architecture) according to an embodiment of the present invention.
  • AUTOSAR AUTomotive Open System Architecture
  • Computing device 12 includes at least one processor 14 , a computer readable storage medium 16 and a communication bus 18 .
  • Processor 14 may cause computing device 12 to operate according to the above-mentioned example embodiments.
  • processor 14 may execute one or more programs stored on computer readable storage medium 16 .
  • the one or more programs may include one or more computer-executable instructions, which when executed by processor 14 are configured to cause computing device 12 to perform operations in accordance with an illustrative embodiment. It can be.
  • Computer-readable storage media 16 may include non-transitory storage media configured to store computer-executable instructions or program code, program data, and/or other suitable form of information.
  • Program 20 stored on computer readable storage medium 16 includes a set of instructions executable by processor 14 .
  • computer readable storage medium 16 includes memory (volatile memory such as random access memory, non-volatile memory, or a suitable combination thereof), one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, other forms of storage media that can be accessed by computing device 12 and store desired information, or any suitable combination thereof.
  • Communications bus 18 interconnects various other components of computing device 12, including processor 14 and computer-readable storage medium 16.
  • Computing device 12 may also include one or more input/output interfaces 22 and one or more network communication interfaces 26 that provide interfaces for one or more input/output devices 24 .
  • An input/output interface 22 and a network communication interface 26 are connected to the communication bus 18 .
  • Input/output device 24 may be coupled to other components of computing device 12 via input/output interface 22 .
  • Exemplary input/output devices 24 include a pointing device (such as a mouse or trackpad), a keyboard, a touch input device (such as a touchpad or touchscreen), a voice or sound input device, various types of sensor devices, and/or a photographing device.
  • the exemplary input/output device 24 may be included inside the computing device 12 as a component constituting the computing device 12, or may be connected to the computing device 12 as a separate device distinct from the computing device 12. may be

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Human Computer Interaction (AREA)
  • Debugging And Monitoring (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

Un procédé et un dispositif de génération automatique d'un code de configuration de surveillance d'état ARINC sont divulgués. Le procédé de génération automatique d'un code de configuration de surveillance d'état ARINC selon un mode de réalisation divulgué dans la présente invention est exécuté dans un dispositif informatique comprenant : un ou plusieurs processeurs ; et une mémoire dans laquelle un ou plusieurs programmes exécutés par le ou les processeurs sont stockés. Le procédé comprend les étapes consistant à : générer un élément SystemError sur la base d'informations de configuration AUTOSAR d'entrée ; générer un élément de partition parmi des éléments de configuration ARINC sur la base des informations de configuration AUTOSAR ; et générer un élément de surveillance d'état sur la base de l'élément SystemError et de l'élément de partition.
PCT/KR2021/020141 2021-12-29 2021-12-29 Dispositif et procédé de génération automatique d'un code de configuration de surveillance d'état dans un système d'exploitation arinc pour une plateforme de véhicule WO2023127997A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020210190793A KR102600294B1 (ko) 2021-12-29 2021-12-29 차량용 플랫폼을 위한 arinc 기반 운영체제 헬스 모니터링 설정 코드 자동 생성 장치 및 방법
KR10-2021-0190793 2021-12-29

Publications (1)

Publication Number Publication Date
WO2023127997A1 true WO2023127997A1 (fr) 2023-07-06

Family

ID=86999280

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2021/020141 WO2023127997A1 (fr) 2021-12-29 2021-12-29 Dispositif et procédé de génération automatique d'un code de configuration de surveillance d'état dans un système d'exploitation arinc pour une plateforme de véhicule

Country Status (2)

Country Link
KR (1) KR102600294B1 (fr)
WO (1) WO2023127997A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110045722A (ko) * 2009-10-27 2011-05-04 한국전자통신연구원 오토사 플랫폼과 모스트 플랫폼 연동을 위한 통합 게이트웨이 장치 및 방법
JP2012133786A (ja) * 2010-12-21 2012-07-12 Robert Bosch Gmbh Ａｕｔｏｓａｒソフトウェアシステムのａｕｔｏｓａｒソフトウェア要素をバイパスする方法
KR20130138468A (ko) * 2012-06-11 2013-12-19 한국전자통신연구원 응용 소프트웨어와 ａｕｔｏｓａｒ 서비스를 연결하기 위한 장치 및 방법
KR102213676B1 (ko) * 2019-12-19 2021-02-05 현대오트론 주식회사 산술 연산 감시 기능을 구비하는 오토사 시스템용 단말 장치 및 오토사 시스템의 산술 연산 감시 방법
KR20210065301A (ko) * 2019-11-27 2021-06-04 주식회사 알티스트 Autosar 기반의 소프트웨어 설계 방법 및 이를 수행하기 위한 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20110045722A (ko) * 2009-10-27 2011-05-04 한국전자통신연구원 오토사 플랫폼과 모스트 플랫폼 연동을 위한 통합 게이트웨이 장치 및 방법
JP2012133786A (ja) * 2010-12-21 2012-07-12 Robert Bosch Gmbh Ａｕｔｏｓａｒソフトウェアシステムのａｕｔｏｓａｒソフトウェア要素をバイパスする方法
KR20130138468A (ko) * 2012-06-11 2013-12-19 한국전자통신연구원 응용 소프트웨어와 ａｕｔｏｓａｒ 서비스를 연결하기 위한 장치 및 방법
KR20210065301A (ko) * 2019-11-27 2021-06-04 주식회사 알티스트 Autosar 기반의 소프트웨어 설계 방법 및 이를 수행하기 위한 장치
KR102213676B1 (ko) * 2019-12-19 2021-02-05 현대오트론 주식회사 산술 연산 감시 기능을 구비하는 오토사 시스템용 단말 장치 및 오토사 시스템의 산술 연산 감시 방법

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LEE, SANG HUN ET AL.: "A Study on ARINC 653 Partition Software Fault Injection Test", PROCEEDINGS OF 2018 KSAS SPRING CONFERENCE, April 2018 (2018-04-01), pages 271 - 272, XP009547529 *

Also Published As

Publication number Publication date
KR102600294B1 (ko) 2023-11-09
KR20230101040A (ko) 2023-07-06

Similar Documents

Publication Publication Date Title
CN106325970A (zh) 编译方法和编译系统
US20130159477A1 (en) Method for configuring a distributed avionics control system
US20080320071A1 (en) Method, apparatus and program product for creating a test framework for testing operating system components in a cluster system
CN109165055B (zh) 无人驾驶系统组件加载方法、装置、计算机设备及介质
CN111796831B (zh) 一种多芯片兼容的编译方法和装置
WO2021107179A1 (fr) Procédé et dispositif de génération automatique de code de réglage de logiciel d'application basé sur autosar
US8204732B1 (en) Modeling communication interfaces for multiprocessor systems
CN103620561A (zh) n路运行时互操作调试
CN114818565A (zh) 基于python的仿真环境管理平台、方法、设备及介质
US11650810B1 (en) Annotation based automated containerization
JP2020071870A (ja) ハードウェア抽象化ソフトウェアレイヤを使用するシステムのための汎用仮想化プラットフォーム
CN112506612A (zh) 一种集群巡检方法、装置、设备及可读存储介质
CN111787045A (zh) 从私有云到公有云的迁移方法和装置
WO2023127997A1 (fr) Dispositif et procédé de génération automatique d'un code de configuration de surveillance d'état dans un système d'exploitation arinc pour une plateforme de véhicule
CN112015371B (zh) 一种非嵌入式软件平台下的软件开发装置
WO2009116748A2 (fr) Procédé et appareil de développement de logiciels basés sur un contenant de composants réservés
EP4261631A1 (fr) Système et procédé de commande
Ebraert et al. A Reflective Approach to Dynamic Software Evolution.
US20220297731A1 (en) Train signal system and linkage method therefor
Hu et al. Safety critical applications and hard real-time profile for Java: a case study in avionics
CN108021396B (zh) 适用于Windows操作系统的传感器驱动方法和驱动系统
US10445081B2 (en) Techniques of automatically generating dependencies for applications in embedded systems
Armentia et al. Model driven design support for mixed-criticality distributed systems
CN101263459A (zh) 图形xml编程系统和引擎
Gong et al. Automatic model building and verification of embedded software with UPPAAL

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

Country of ref document: EP

Kind code of ref document: A1