Notification Events 通知事件

• Notifications describe a general Publish/Subscribe-Concept. Usually the server publishes a service to which a client subscribes. On certain events the server will send the client a event, which could be for example an updated value or an event that occurred.
  Notification描述了一般的發(fā)布/訂閱概念。通常，服務器端發(fā)布服務而客戶端前來訂閱。在某些事件上，服務器端向客戶端發(fā)送event，該event可以是例如更新的值 或者發(fā)生的事件。

• SOME/IP is used only for transporting the updated value and not for the publishing and subscription mechanisms. These mechanisms are implemented by SOME/IP-SD.
  SOME / IP僅用于傳輸更新的值，而不用于發(fā)布和訂閱機制。這些機制由SOME / IP-SD實現(xiàn) 。

• When more than one subscribed client on the same ECU exists, the system shall handle the replication of notifications in order to save transmissions on the communication medium. This is especially important, when notifications are transported using multicast messages.
  當同一ECU上有多個訂閱客戶端時，系統(tǒng)應對notification進行復制以便節(jié)省通信介質(zhì)上的傳輸。當使用多播消息傳輸通知時，這尤其重要。

Strategy for sending notifications發(fā)送notification的策略

For different use cases different strategies for sending notifications are possible and shall be defined in the service interface. The following examples are common:
對于不同的用例，可以使用不同的發(fā)送通知策略，并且應在服務接口中定義。 以下是常見的例子：?

• Cyclic update循環(huán)更新
  send an updated value in a fixed interval (e.g. every 100 ms for safety relevant messages with Alive).
  以固定間隔發(fā)送更新值（例如，每100毫秒用于Alive的安全相關消息）。
• Update on change變化更新
  send an update as soon as a “value” changes (e.g. door open).
  一旦“值”發(fā)生變化（例如開門）就發(fā)送更新。
• Epsilon change Epsilon更改
  only send an update when the difference to the last value is greater than a certain epsilon. This concept may be adaptive, i.e. the prediction is based on a history; thus, only when the difference between prediction and current value is greater than epsilon an update is transmitted.
  僅當與最后一個值的差異大于某個閾值時才發(fā)送更新。 該概念可以是自適應的，比如預測是基于歷史值; 因此，只有當預測值和當前值之間的差值大于epsilon時才發(fā)送更新。