Explanation of ara::com API, No.846, 2021-11
AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成
用語(terms)
| term | Description |
|---|---|
| ctor | C++ constructor |
| dtor | C++ destructor |
| IPC | Inter Process Communication |
| RT | Realtime |
| SI | Service Interface |
| WET | Worst Case Execution Time |
| Binding | This typically describes the realization of some abstract concept with a specific implementation or technology. In AUTOSAR, for instance, we have an abstract data type and interface model described in the methodology. Mapping it to a concrete programming language is called language binding. In the AUTOSAR Adaptive Platform for instance we do have a C++ language binding. In this explanatory document we typically use the tech term binding to refer to the implementation of the abstract (technology independent) ara::com API to a concrete communication transport technology like for instance sockets, pipes, shared memory, ... |
| Callable | In the context of C++ a Callable is defined as: A Callable type is a type for which the INVOKE operation (used by, e.g., std::function, std::bind, and std::thread::thread) is applicable. This operation may be performe |
英日
日本語は仮訳
| no. | count | word | 日本語 |
|---|---|---|---|
| 1 | 2215 | the | その |
| 2 | 983 | of | の |
| 3 | 745 | to | に |
| 4 | 672 | a | 一つの |
| 5 | 615 | service | 奉仕 |
| 6 | 558 | is | は |
| 7 | 495 | ara | AUTOSAR Runtime for Adaptive Applications(短縮名) |
| 8 | 450 | in | の上に |
| 9 | 383 | and | と |
| 10 | 378 | com | communication(短縮名) |
| 11 | 356 | instance | 実例 |
| 12 | 320 | this | これ |
| 13 | 300 | for | にとって |
| 14 | 276 | be | です |
| 15 | 267 | which | どれの |
| 16 | 230 | data | 与件 |
| 17 | 230 | it | それ |
| 18 | 228 | implementation | 実装 |
| 19 | 226 | proxy | 代理 |
| 20 | 223 | that | それ |
| 21 | 209 | call | 電話 |
| 22 | 209 | method | 方法 |
| 23 | 204 | api | application programming interface(短縮名) |
| 24 | 202 | an | と |
| 25 | 199 | autosar | AUTomotive Open System Architecture(短縮名) |
| 26 | 189 | ap | adaptive platform(短縮名) |
| 27 | 187 | with | と |
| 28 | 186 | event | 行事 |
| 29 | 174 | from | から |
| 30 | 173 | as | なので |
| 31 | 172 | on | の上 |
| 32 | 150 | has | もっている |
| 33 | 147 | application | 応用 |
| 34 | 147 | binding | 詰め物 |
| 35 | 147 | by | に |
| 36 | 142 | communication | 通信 |
| 37 | 141 | class | 級 |
| 38 | 140 | not | いいえ |
| 39 | 139 | or | また |
| 40 | 137 | document | 資料 |
| 41 | 133 | explanation | 説明 |
| 42 | 132 | if | もしも |
| 43 | 129 | core | 芯 |
| 44 | 128 | are | それは |
| 45 | 128 | r | r |
| 46 | 127 | future | 将来 |
| 47 | 126 | id | identifier, 識別子(短縮名） |
| 48 | 125 | we | 私たち |
| 49 | 121 | handler | 取扱者 |
| 50 | 121 | skeleton | 骨格 |
| 51 | 120 | autosar_exp_aracomapi | autosar_exp_aracomapi |
| 52 | 113 | have | 持ってる |
| 53 | 112 | state | 州 |
| 54 | 104 | you | 君 |
| 55 | 98 | get | 得る |
| 56 | 98 | type | 型 |
| 57 | 93 | at | で |
| 58 | 91 | management | 管理 |
| 59 | 90 | one | 1 |
| 60 | 86 | some | いくつかの |
| 61 | 86 | value | 価値 |
| 62 | 86 | will | 意思 |
| 63 | 85 | side | 側 |
| 64 | 82 | different | 違う |
| 65 | 82 | so | それで |
| 66 | 80 | radar | radio detection and ranging（短縮名） |
| 67 | 79 | case | 場合 |
| 68 | 76 | field | 分野 |
| 69 | 75 | result | 結果 |
| 70 | 72 | identifier | 識別子 |
| 71 | 71 | can | できる |
| 72 | 71 | process | 処理する |
| 73 | 70 | name | 名前 |
| 74 | 70 | user | 利用者 |
| 75 | 69 | return | 戻る |
| 76 | 66 | handle | 取り持つ |
| 77 | 66 | raw | 生 |
| 78 | 66 | use | 使用する |
| 79 | 65 | find | 探す |
| 80 | 65 | would | だろう |
| 81 | 64 | methods | 方法 |
| 82 | 63 | error | 誤り |
| 83 | 62 | then | それから |
| 84 | 62 | using | 使って |
| 85 | 62 | via | 経由 |
| 86 | 61 | implementer | 実装者 |
| 87 | 61 | might | かもしれない |
| 88 | 61 | std | standard(短縮名） |
| 89 | 59 | const | constant(短縮名） |
| 90 | 59 | could | たぶん......だろう |
| 91 | 59 | example | 例 |
| 92 | 59 | space | 空間 |
| 93 | 59 | subscription | 購読予約 |
| 94 | 57 | called | と呼ぶ |
| 95 | 57 | new | 新着 |
| 96 | 56 | where | どこ |
| 97 | 55 | events | 行事 |
| 98 | 55 | its | これは |
| 99 | 54 | calls | 呼び出し |
| 100 | 54 | our | 私たちの |
参照(References)
[1] Specification of RTE Software, AUTOSAR_SWS_RTE
[2] Middleware for Real-time and Embedded Systems, http://doi.acm.org/10.1145/508448.508472
[3] Patterns, Frameworks, and Middleware: Their Synergistic Relationships, http://dl.acm.org/citation.cfm?id=776816.776917
[4] Specification of Adaptive Platform Core, AUTOSAR_SWS_AdaptivePlatformCore
[5] Specification of Manifest, AUTOSAR_TPS_ManifestSpecification
[6] SOME/IP Protocol Specification, AUTOSAR_PRS_SOMEIPProtocol
[7] Serialization and Unserialization, https://isocpp.org/wiki/faq/serialization
[8] Copying and Comparing: Problems and Solutions, http://dx.doi.org/10.1007/3-540-45102-1_11
[9] SOME/IP Service Discovery Protocol Specification, AUTOSAR_PRS_SOMEIPServiceDiscoveryProtocol