Publish/Subscribe with link loss at client (figure ignoring timings)

Publish/Subscribe Registration/Deregistration behavior (figure ignoring timings)

Publish/Subscribe with link loss at Server (figure ignoring timings)

Publish/Subscribe State Diagram (server behavior for unicast eventgroups)

Publish/Subscribe State Diagram (server behavior for multicast eventgroups

Publish/Subscribe State Diagram (server behavior for adaptive unicast/multicast eventgroups)

Publish/Subscribe Example for Endpoint Options and the usage of ports

• Example
• following Figure shows an example with the different Endpoint and a Multicast Option:
  下圖展示了一個例子，使用不同的Endpoint和Multicast Option
  • The Server offers the Service Instance on Server UDP-Endpoint SU and Server TCP-Endpoint ST
    服務器提供了一個服務實例，通過UDP-Endpoint （簡稱SU） 和 TCP-Endpoint ST（簡稱ST）
  • The Client opens a TCP connection
    客戶端打開一個TCP連接（Socket）
  • The Client sends a Subscribe Eventgroup entry with Client UDP-Endpoint CU (unicast) and a Client TCP-Endpoint CT
    客戶端發(fā)送一個Subscribe Eventgroup entry，帶有客戶端UDP-Endpoint (unicast)(簡稱CU)和一個客戶端TCP-Endpoint （簡稱CT）
  • The Server answers with a Subscribe Eventgroup Ack entry with Multicast MU
    服務器通過多播option（簡稱MU）回復一個Subscribe Eventgroup Ack entry

• Then the following operations happen:
  接下來這么運行：
  • The Client calls a method on the Server
    客戶端調(diào)用服務器端的method
  • Request is sent from CU to SU and Response from SU to CU
    Request從客戶端通過UDP發(fā)給服務器端，回復消息從服務器端通過UDP發(fā)回客戶端
  • For TCP this would be: Request dyn to ST and RESPONSE from ST to CT
  • The Server sends a Unicast UDP Event: SU to CU
    服務器端發(fā)送一個Unicast UDP Event:到客戶端：SU到CU
  • The Server sends a Unicast TCP Event: ST to CT
    服務器端發(fā)送一個Unicast TCP Event到客戶端: ST到CT.
  • The Server sends a Multicast UDP Event: SU to MU
    服務器端發(fā)送一個Multicast UDP Event到客戶端：SU到MU

• Keep in mind that Multicast Endpoints use a Multicast IP Address on the receiver side,i.e. the client, and TCP cannot be used for Multicast

• If the Service Discovery Module receives an OfferService Entry, the following step(s) shall be performed in the following order:
  如果服務發(fā)現(xiàn)模塊收到OfferService entry，則應按以下順序執(zhí)行以下步驟：
  • If received TTL is not equal to the max value, update the timer by the received TTL value.
    如果收到的TTL不等于最大值，則按接收的TTL值更新定時器。
  • Open TCP connection if SdClientServiceTcpRef is configured and was not opened before.
    如果配置了SdClientServiceTcpRef并且之前未打開，則打開TCP連接。
• Note注意：
  The amount of separate Service Discovery messages shall be reduced, i.e.: Combine as much information as possible into one Service Discovery message before calling the Socket Adaptor’s transmit API. 應減少單獨的Service Discovery消息的數(shù)量，即：在調(diào)用套接字適配器的傳輸API之前，將盡可能多的信息合并到一個服務發(fā)現(xiàn)消息中。

• If an OfferService entry was received and its TTL timer did not expire yet, the associated Socket Connections are in state SOAD_SOCON_ONLINE in the Main phase:
  如果在主階段收到OfferService entry且其TTL計時器尚未到期，相關的套接字連接處于狀態(tài)SOAD_SOCON_ONLINE：
  • If the client service has not been reported as SD_CLIENT_SERVICE_AVAILABLE:
    如果客戶端服務尚未報告為SD_CLIENT_SERVICE_AVAILABLE：
    • the API SoAd_EnableSpecificRouting() shall be called with SdClientServiceActivationRef (see SdConsumedMethods) and the relevant Socket Connections for this Client Service Instance.
      應使用SdClientServiceActivationRef（請參閱SdConsumedMethods）和此客戶端服務實例的相關套接字連接來調(diào)用API SoAd_EnableSpecificRouting（）。
    • SD_CLIENT_SERVICE_AVAILABLE shall be indicated to the BswM module by calling the API BswM_Sd_ClientServiceCurrentState().
      應通過調(diào)用API BswM_Sd_ClientServiceCurrentState()向BswM模塊指示SD_CLIENT_SERVICE_AVAILABLE。

• If an OfferService entry was received and its TTL timer did not expire yet, the associated Socket Connections are in state SOAD_SOCON_ONLINE in the Main phase:
  如果在主階段收到OfferService entry且其TTL計時器尚未到期，且相關的套接字連接處于狀態(tài)SOAD_SOCON_ONLINE：
  • For each currently requested Consumed Eventgroup of this Client Service Instance (Consumed Eventgroups are requested using Sd_ConsumedEventGroupSetState() and with state SD_CONSUMED_EVENTGROUP_REQUESTED or automatically on startup if SdConsumedEventGroupAutoRequire is configured to true), the following shall be done in exactly this order:
    對于此客戶端服務實例的每個當前請求的Consumed Eventgroup （使用Sd_ConsumedEventGroupSetState（）和狀態(tài)SD_CONSUMED_EVENTGROUP_REQUESTED請求Consumed Eventgroups ，或者如果SdConsumedEventGroupAutoRequire配置為true，則在啟動時自動啟用），以下內(nèi)容應按以下順序完成：
    • StopSubscribeEventgroup entry shall be sent out, if the last SubscribeEventgroup entry was sent as reaction to an OfferService entry received via Multicast, it was never answered with a SubscribeEventgroupAck, and the current OfferService entry was received via Multicast.
      如果最后一個SubscribeEventgroup entry作為對OfferService entry的響應而發(fā)送，它從未通過SubscribeEventgroupAck被回復，并且當前的OfferService entry是通過Multicast接收的，則發(fā)送StopSubscribeEventgroup entry。
    • A SubscribeEventgroup entry shall be sent out.
      然后發(fā)送SubscribeEventgroup entry。

• Note:
  • The transmission of a response to an Offer received via multicast shall be delayed with the configured delay.
    通過多播接收的Offer的響應消息的傳輸應被延遲，這個延遲可以被配置。
  • When the request response delay elapses before the associated Socket Connections are in state SOAD_SOCON_ONLINE, the StopSubscribeEventgroup and SubscribeEventgroup shall be delayed until the Socket Connections are online and shall not be considered as reaction to an OfferService entry received via Multicast.
    當在關聯(lián)的套接字連接處于SOAD_SOCON_ONLINE狀態(tài)之前請求響應延遲已經(jīng)結束，StopSubscribeEventgroup和SubscribeEventgroup將被延遲，直到Socket Connections在線，并且不應被視為對通過Multicast接收的OfferService entry的反應。
  • When the request response delay elapses while the ClientService is in state RELEASED, there shall be no response to this Offer entry.
    當ClientService處于RELEASED狀態(tài)時，如果請求響應延遲已經(jīng)結束，則不會對此Offer entry 做出響應。

• When the Client Service is reported as SD_CLIENT_SERVICE_DOWN to the BswM by calling the API BswM_Sd_ClientServiceCurrentState() :
  當通過調(diào)用API BswM_Sd_ClientServiceCurrentState()將客戶端服務向BswM報告為SD_CLIENT_SERVICE_DOWN:
  • The API SoAd_DisableSpecificRouting() shall be called with SdClientServiceActivationRef (see SdConsumedMethods) and the relevant Socket Connections for this Client Service Instance.
    應使用SdClientServiceActivationRef（請參閱SdConsumedMethods）和此客戶端服務實例相關的套接字連接去調(diào)用API SoAd_DisableSpecificRouting()。

• If a StopSubscribeEventgroup and SubscribeEventgroup for the same Eventgroup (i.e. same Service ID, Instance ID, Eventgroup ID, Counter, and Major Version) have to be sent out, these entries have to be directly after each other in the same SD message (no entry between them).
  對于相同事件組（即相同的服務ID，實例ID，事件組ID，計數(shù)器和主版本），如果必須發(fā)送StopSubscribeEventgroup和SubscribeEventgroup，則這些entry必須在相同的SD消息中直接相繼連續(xù)發(fā)送，而無entry在它們之間。
  • StopSubscribeEventgroup entry shall be sent out, if the last SubscribeEventgroup entry was sent as reaction to an OfferService entry received via Multicast, it was never answered with a SubscribeEventgroupAck, and the current OfferService entry was received via Multicast.
    如果發(fā)送最后一個SubscribeEventgroup entry是用來響應OfferService entry，但從沒有收到SubscribeEventgroupAck，且這個OfferService entry是以Multicast接收到的，則StopSubscribeEventgroup entry需要被發(fā)送。
  • A SubscribeEventgroup entry shall be sent out .
    然后發(fā)送SubscribeEventgroup entry。

• If the Service Discovery Module receives a SubscribeEventgroupAck fitting this Consumed Eventgroup for the first time after this Consumed Eventgroup was requested, the following step(s) shall be performed in the following order:
  如果服務發(fā)現(xiàn)模塊在請求此Consumed Eventgroup后第一次收到適合此Consumed Eventgroup的SubscribeEventgroupAck，則應按以下順序執(zhí)行以下步驟：
  • Use the information of the Multicast Option (if existing) to set up relevant Multicast Information in SoAd (see SoConId related to SdConsumedEventGroupMulticastActivationRef).
    使用Multicast Option （如果存在）的信息在SoAd中設置相關的多播信息（請參閱與SdConsumedEventGroupMulticastActivationRef相關的SoConId）。
  • Call the API SoAd_RequestIpAddrAssignment() using the IP address received by the SubscribeEventgroupAck message.
    使用SubscribeEventgroupAck消息接收的IP地址調(diào)用API SoAd_RequestIpAddrAssignment（）。
  • Call BswM_Sd_ConsumedEventGroupCurrentState with SD_CONSUMED_EVENTGROUP_AVAILABLE.
    使用SD_CONSUMED_EVENTGROUP_AVAILABLE調(diào)用BswM_Sd_ConsumedEventGroupCurrentState。
  • Setup TTL timer with the TTL of the SubscribeEventgroupAck entry.
    使用SubscribeEventgroupAck entry的TTL設置TTL計時器。

• If a Service Discovery Message contains only a SubscribeEventgroupNack entry but no SubscribeEventgroupAck entry for the same Eventgroup, Service Discovery shall do the following:
  如果服務發(fā)現(xiàn)消息僅包含SubscribeEventgroupNack entry但不包含同一事件組的SubscribeEventgroupAck entry，則Service Discovery將執(zhí)行以下操作：
  • Report the DEM error SD_E_SUBSCR_NACK_RECV (and restart the TCP connection (if applicable)
    報告DEM錯誤SD_E_SUBSCR_NACK_RECV 并重新啟動TCP連接（如果適用）
  • call the API SoAd_CloseSoCon()with parameter abort set to TRUE to close all socket connections associated to this service instance
    將參數(shù)abort設置為TRUE并調(diào)用API SoAd_CloseSoCon()以關閉與此服務實例關聯(lián)的所有套接字連接
  • call the API SoAd_OpenSoCon() to reopen all socket connections associated to this service instance
    調(diào)用API SoAd_OpenSoCon()以重新打開與此服務實例關聯(lián)的所有套接字連接

• If the Service Discovery Module receives a StopOfferService Entry, the following step(s) shall be performed in the following order:
  如果服務發(fā)現(xiàn)模塊收到StopOfferService條目，則應按以下順序執(zhí)行以下步驟：
  • Stop the TTL timers of this Client Service Instance and all related Consumed Eventgroups.
    停止此客戶端服務實例和所有相關的Consumed Eventgroup的TTL計時器。
  • Report this Client Service as DOWN if it was reported AVAILABLE before (call BswM_Sd_ClientServiceCurrentState with SD_CLIENT_SERVICE_DOWN and the Client Service’s handle ID)
    如果之前報告了AVAILABLE，則將此客戶端服務報告為DOWN（使用SD_CLIENT_SERVICE_DOWN和客戶服務的句柄ID調(diào)用BswM_Sd_ClientServiceCurrentState）。
  • Report all Consumed Eventgroups as DOWN that were reported AVAILABLE before (call BswM_Sd_ConsumedEventGroupCurrentState with SD_CONSUMED_EVENTGROUP_DOWN and the Consumed Eventgroup’s handle ID).
    將之前報告為AVAILABLE的所有Consumed Eventgroup報告為DOWN（使用SD_CONSUMED_EVENTGROUP_DOWN和Consumed Eventgroups的句柄ID調(diào)用BswM_Sd_ConsumedEventGroupCurrentState）。
  • Close all Socket Connections associated with this Client Service Instance that have been opened before.
    關閉之前打開的與此客戶端服務實例關聯(lián)的所有套接字連接。
  • Stay in Main Phase and do not send FindService entries.
    保持主階段，不發(fā)送FindService條目。

• If Sd_LocalIpAddrAssignmentChg() is called with a state other than “TCPIP_IPADDR_STATE_ASSIGNED” while being in Main Phase:
  如果在主階段中調(diào)用Sd_LocalIpAddrAssignmentChg() 時狀態(tài)不是“TCPIP_IPADDR_STATE_ASSIGNED”：
  • The Down Phase shall be entered. 應進入Down Phase。
  • “SD_CLIENT_SERVICE_DOWN” shall be indicated to the BswM module by calling the API BswM_Sd_ClientServiceCurrentState(), if the present state is SD_CLIENT_SERVICE_AVAILABLE.
    如果當前狀態(tài)為SD_CLIENT_SERVICE_AVAILABLE，則應通過調(diào)用API BswM_Sd_ClientServiceCurrentState()向BswM模塊指示“SD_CLIENT_SERVICE_DOWN”。
  • “SD_CONSUMED_EVENTGROUP_DOWN” shall be indicated to the BswM module by calling the API BswM_Sd_ConsumedEventGroupCurrentState() for all associated ConsumedEventgroups, if the present state is SD_CONSUMED_EVENTGROUP_AVAILABLE.
    如果當前狀態(tài)為SD_CONSUMED_EVENTGROUP_AVAILABLE，則應通過為所有關聯(lián)的ConsumedEventgroup調(diào)用API BswM_Sd_ConsumedEventGroupCurrentState()向BswM模塊表明“SD_CONSUMED_EVENTGROUP_DOWN”。
• If the TCP/IP connection has been lost (Socket connection is other than SOAD_SOCON_ONLINE), the Service Discovery Module shall leave the Main Phase, enter the Wait Phase, and stop the TTL timers of the associated Client Service Instances and EventGroups.
  如果TCP / IP連接丟失（套接字連接不是SOAD_SOCON_ONLINE），服務發(fā)現(xiàn)模塊應離開主階段，進入等待階段，并停止相關客戶端服務實例和事件組的TTL定時器。

• The Service Discovery Module shall stay in the Main Phase as long as the following conditions apply:
  只要滿足以下條件，服務發(fā)現(xiàn)模塊應保持在主階段：
  • Client Service is needed (i.e. Sd_ClientServiceSetState()has been called with State “SD_CLIENT_SERVICE_REQUESTED”)
    需要客戶端服務（即已使用狀態(tài)“SD_CLIENT_SERVICE_REQUESTED”調(diào)用Sd_ClientServiceSetState()
  • IP address assigned and can be used (i.e. Sd_LocalIpAddrAssignmentChg has been called with status TCPIP_IPADDR_STATE_ASSIGNED).
    分配并可以使用的IP地址（即已調(diào)用狀態(tài)為TCPIP_IPADDR_STATE_ASSIGNED的Sd_LocalIpAddrAssignmentChg）。
• The Service Discovery Module shall leave the Main Phase and enter the state SD_CLIENT_SERVICE_DOWN if at least one of the listed conditions described as above does not apply any more.
  如果上述至少一個列出的條件不再適用，則服務發(fā)現(xiàn)模塊應離開主階段并進入狀態(tài)SD_CLIENT_SERVICE_DOWN。

• If the Client goes DOWN which is indicated by a call of Sd_ClientServiceSetState () with State “SD_CLIENT_SERVICE_RELEASED” while all other conditions listed in SWS_SD_00375 still apply, the Service Discovery module shall perform the following steps:
  如果客戶端進入DOWN，這是通過調(diào)用狀態(tài)為“SD_CLIENT_SERVICE_RELEASED”的API Sd_ClientServiceSetState（）引發(fā)的，而SWS_SD_00375（上頁）中列出的所有其他條件仍然適用，則服務發(fā)現(xiàn)模塊應執(zhí)行以下步驟：
  • Enter the Down Phase and indicate the state SD_CLIENT_SERVICE_DOWN to the BswM by calling the API BswM_Sd_ClientServiceCurrentState ().
    進入Down Phase并通過調(diào)用API BswM_Sd_ClientServiceCurrentState（）向BswM指示狀態(tài)SD_CLIENT_SERVICE_DOWN。
  • For all subscribed eventgroups of this Client Service,
    對于此客戶服務的所有訂閱事件組，
    • a StopSubscribeEventgroup shall be sent
      應發(fā)送StopSubscribeEventgroup。
    • the status shall be set to SD_CONSUMED_EVENTGROUP_DOWN and reported to BswM by calling the API BswM_Sd_ConsumedEventGroupCurrentState().
      狀態(tài)應設置為SD_CONSUMED_EVENTGROUP_DOWN并通過調(diào)用API BswM_Sd_ConsumedEventGroupCurrentState()報告給BswM_Sd_ConsumedEventGroupCurrentState（），

• If the Consumed Event Group is not requested anymore as indicated by a call of Sd_ConsumedEventGroupSetState with state SD_CONSUMED_EVENTGROUP_RELEASED, the Service Discovery module shall perform the following steps for the consumed event group:
  如果通過調(diào)用狀態(tài)為SD_CONSUMED_EVENTGROUP_RELEASED的Sd_ConsumedEventGroupSetState表明不再請求Consumed Event Group ，則服務發(fā)現(xiàn)模塊將對Consumed Event Group執(zhí)行以下步驟：
  • A StopSubscribeEventgroup shall be sent.
    應發(fā)送StopSubscribeEventgroup。
  • The status shall be set to SD_CONSUMED_EVENTGROUP_DOWN and be reported to BswM_Sd_ConsumedEventGroupCurrentState(), if the status is not currently SD_CONSUMED_EVENTGROUP_DOWN.
    如果狀態(tài)當前不是SD_CONSUMED_EVENTGROUP_DOWN，則狀態(tài)應設置為SD_CONSUMED_EVENTGROUP_DOWN并報告給BswM_Sd_ConsumedEventGroupCurrentState

• If the TTL Timer of a Client Service expires, the Service Discovery module shall perform the following steps:
  如果客戶端Service的TTL定時器到期，則服務發(fā)現(xiàn)模塊應執(zhí)行以下步驟：
  • Enter the Initial Wait Phase and indicate the state SD_CLIENT_SERVICE_DOWN to the BswM by calling the API BswM_Sd_ClientServiceCurrentState ().
    輸入初始等待階段，并通過調(diào)用API BswM_Sd_ClientServiceCurrentState（）向BswM提供狀態(tài)信息SD_CLIENT_SERVICE_DOWN。
  • All subscribed Eventgroups of this Client Service shall expired in this instance (stop TTL timer) and the expiration shall be handled as describe in SWS_SD_00601.
    此客戶端服務的所有已訂閱事件組在此實例中將到期（停止TTL計時器），并且應按照SWS_SD_00601中的描述處理該到期失效。
• If the TTL Timer of an Eventgroup expires, the Service Discovery module shall perform the following step(s):
  如果Eventgroup的TTL定時器到期，則服務發(fā)現(xiàn)模塊應執(zhí)行以下步驟：
  • The status shall be set to SD_CONSUMED_EVENTGROUP_DOWN and reported to BswM by calling the API BswM_Sd_ConsumedEventGroupCurrentState().
    狀態(tài)應設置為SD_CONSUMED_EVENTGROUP_DOWN，并通過調(diào)用API BswM_Sd_ConsumedEventGroupCurrentState（）報告給BswM。
• When the Main Phase is left,
  當主階段離開時，
  • The API SoAd_DisableSpecificRouting()shall be called for all Socket Connections associated with this Client Service ID that have been opened before.
    應為之前打開過的與此客戶端服務ID關聯(lián)的所有套接字連接調(diào)用API SoAd_DisableSpecificRouting。
  • Close all Socket Connections associated with this Client Service Instance that have been opened before.
    關閉之前打開的與此客戶端服務實例關聯(lián)的所有套接字連接。

• When the Repetition Phase is entered, the Service Discovery Module shall start the timer SdClientTimerInitialFindRepetitionsBaseDelay ?()
  當進入Repetition階段后，服務發(fā)現(xiàn)模塊應啟動計時器SdClientTimerInitialFindRepetitionsBaseDelay
• When the timer SdClientTimerInitialFindRepetitionsBaseDelay expires within the Repetition Phase, a FindOffer Message shall be sent. ?()
  當計時器SdClientTimerInitialFindRepetitionsBaseDelay在重復階段到期時，應發(fā)送FindOffer消息。
• In the Repetition Phase up to SdClientTimerInitialFindRepetitionsMax FindServer entries shall be sent with doubling intervals (BaseDelay, first FindService Entry, 2x BaseDelay, second FindService Entry, 4x BaseDelay, third FindService Entry, …).
  在重復階段，直到SdClientTimerInitialFindRepetitionsMax FindServer條目應以雙倍間隔發(fā)送（BaseDelay，第一個FindService條目，2x BaseDelay，第二個FindService條目，4x BaseDelay，第三個FindService條目，……）。

• Note: Example config and resulting behavior (no OfferService received during example):

SdClientTimerInitialFindRepetitionBaseDelay=30
SdClientTimerInitialFindRepetitionMax=3

[Initial Wait Phase starts]
Wait Initial Wait Delay based on Configured Min and Max
Send entry.
[Initial Wait Phase ends]

[Repetition Phase starts]
Wait 30ms (=30ms * 20).
Send entry.

Wait 60ms (=30ms * 21).
Send entry.

Wait 120ms (=30ms * 22).
Send entry.
[Repetition Phase ends]

• If the Service Discovery Module receives an OfferService Entry while the current state SD_CLIENT_SERVICE_REQUESTED is for this Client Service Instance, the following step(s) shall be performed in the following order:
  如果服務發(fā)現(xiàn)模塊收到OfferService條目，而該服務實例的當前狀態(tài)是SD_CLIENT_SERVICE_REQUESTED，則應按以下順序執(zhí)行以下步驟：
  • Cancel the repetition timer.
    取消重復計時器。
  • If received TTL is not equal to the max value, set the TTL timer for this entry to the received TTL value.
    如果收到的TTL不等于最大值，則將該條目的TTL定時器設置為接收的TTL值。
  • Open TCP connection if SdClientServiceTcpRef is configured and was not opened before.
    如果配置了SdClientServiceTcpRef并且之前未打開，則打開TCP連接。
  • Leave the Repetition Phase immediately and enter the Main Phase.
    立即離開Repetition階段并進入Main階段。

• After sending the maximum repetitions (defined by SdClientTimerInitialFindRepetitionsMax) of FindService entries, the Repetition Phase shall be left and the Main Phase shall be entered.
  在發(fā)送FindService條目的最大重復次數(shù)（由SdClientTimerInitialFindRepetitionsMax定義）后，應離開Repetition階段并輸入Main階段。
• If Sd_ClientServiceSetState()is called with state SD_CLIENT_SERVICE_RELEASED while being in Repetition Phase, this phase shall be left and the service instance shall enter Down Phase.
  如果在處于Repetition階段時使用狀態(tài)SD_CLIENT_SERVICE_RELEASED調(diào)用Sd_ClientServiceSetState()，則應離開此階段，并且服務實例應進入Down Phase。
• If Sd_LocalIpAddrAssignmentChg() is called with a state other than “TCPIP_IPADDR_STATE_ASSIGNED” while being in Repetition Phase the Down Phase shall be entered.
  如果在處于Repetition階段時使用“TCPIP_IPADDR_STATE_ASSIGNED”以外的狀態(tài)調(diào)用Sd_LocalIpAddrAssignmentChg()，則應輸入Down Phase。
• If the TCP/IP connection has been lost (Socket connection is other than SOAD_SOCON_ONLINE), the Service Discovery Module shall leave the Repetition Phase, enter the Wait Phase, and stop the TTL timers of the associated Client Service Instances and EventGroups.
  如果TCP / IP連接丟失（套接字連接不是SOAD_SOCON_ONLINE），服務發(fā)現(xiàn)模塊應離開Repetition階段，進入Wait階段，并停止相關客戶端服務實例和事件組的TTL定時器。

• If the following conditions apply, the Initial Wait Phase for this configured Client Service Instance shall be entered:
  如果滿足以下條件，則應進入此已配置客戶端服務實例的Initial Wait Phase
  • Sd_Init() has been called.
    已調(diào)用Sd_Init（）
  • Sd_ClientServiceSetState() with SD_CLIENT_SERVICE_REQUESTED has been called OR SdClientServiceAutoRequired = TRUE.
    已調(diào)用狀態(tài)為SD_CLIENT_SERVICE_REQUESTED的Sd_ClientServiceSetState（）或SdClientServiceAutoRequired = TRUE。
  • Sd_LocalIpAddrAssignmentChg() with state “TCPIP_IPADDR_STATE_ASSIGNED” has been called for the first IpAddrId associated with the SdInstanceTxPdu.
    已為與SdInstanceTxPdu關聯(lián)的第一個IpAddrId調(diào)用狀態(tài)為“TCPIP_IPADDR_STATE_ASSIGNED”的Sd_LocalIpAddrAssignmentChg（）。
• When the Initial Wait Phase is entered, the API SoAd_EnableSpecificRouting() shall be called with SdClientServiceActivationRef (see SdConsumedMethods) and the relevant Socket Connections for this Client Service Instance.
  進入Initial Wait Phase后，應使用SdClientServiceActivationRef（請參閱SdConsumedMethods）和此客戶端服務實例的相關套接字連接調(diào)用API SoAd_EnableSpecificRouting（）。
• When a OfferService for a required Client Service is received and SoAd_OpenSoCon()was not called before, the API SoAd_OpenSoCon() shall be called for all Socket Connections associated with this Client Service Instance.
  當收到所需客戶端服務的OfferService并且之前未調(diào)用SoAd_OpenSoCon（）時，API SoAd_OpenSoCon（）應被調(diào)用，以滿足此客戶端服務實例關聯(lián)的所有套接字連接的需要。

• This Client Service Instance shall stay in the Initial Wait Phase for a time within the configured range of SdClientTimerInitialFindDelayMin and SdClientTimerInitialFindDelayMax unless an OfferService entry for this Client Service Instance is received or this random timer expires.
  此客戶端服務實例應在SdClientTimerInitialFindDelayMin和SdClientTimerInitialFindDelayMax的配置范圍內(nèi)保持初始等待階段一段時間，除非收到對此客戶端服務實例的OfferService entry或此隨機計時器到期。
• If an OfferService Entry for this Client Service Instance is received within the Initial Wait Phase,
  如果在初始等待階段內(nèi)收到此客戶服務實例的OfferService entry，
  • The calculated random timer, which has been started when entering the Initial Wait Phase, shall be canceled.
    計算的隨機計時器（在進入初始等待階段時已啟動）將被取消。
  • If received TTL is not equal to the max value, set the TTL timer for this entry to the received TTL value.
    如果收到的TTL不等于最大值，請將此條目的TTL定時器設置為接收的TTL值。
  • Open TCP connection if SdClientServiceTcpRef is configured and was not opened before.
    如果配置了SdClientServiceTcpRef且之前未打開，則打開TCP連接。
  • Leave the Initial Wait Phase Enter the Main Phase.
    離開初始等待階段進入主階段。

• When the calculated random timer based on the parameters SdClientTimerInitialFindDelayMin and SdClientTimerInitialFindDelayMax expires (i.e. no OfferService has been received within this timespan), the following shall be done in the following order:
  當基于參數(shù)SdClientTimerInitialFindDelayMin和SdClientTimerInitialFindDelayMax的計算隨機計時器到期時（即在此時間段內(nèi)未收到OfferService），應按以下順序進行以下操作：
  • FindService Entry shall be sent.
    應發(fā)送FindService Entry
  • If the SdClientTimerInitialFindRepetitionsMax>0, enter the Repetition Phase
    如果SdClientTimerInitialFindRepetitionsMax> 0，則進入重復階段
  • If the SdClientTimerInitialFindRepetitionsMax=0, enter the Main Phase
    如果SdClientTimerInitialFindRepetitionsMax = 0，則進入主階段

• If Sd_ClientServiceSetState() is called with state SD_CLIENT_SERVICE_RELEASED while being in Initial Wait Phase, this phase shall be left and the Service shall enter Down Phase.
  如果在初始等待階段使用狀態(tài)SD_CLIENT_SERVICE_RELEASED調(diào)用Sd_ClientServiceSetState()，則服務應離開此階段并進入Down Phase。
• If for any reasons the Initial Wait Phase is left, the calculated random timer (of the Initial Wait Phase) for this Service Instance shall be stopped.
  如果出于任何原因離開初始等待階段，則應停止為此服務實例計算的（初始等待階段的）隨機定時器。
• If Sd_LocalIpAddrAssignmentChg() is called with a state other than “TCPIP_IPADDR_STATE_ASSIGNED” while being in Initial Wait Phase, the Down Phase shall be entered.
  如果在初始等待階段中調(diào)用Sd_LocalIpAddrAssignmentChg()并且狀態(tài)不是“TCPIP_IPADDR_STATE_ASSIGNED”，則應進入Down階段。
• If the API Sd_Init() is called while being in Initial Wait Phase, the Down Phase shall be entered.
  如果在初始等待階段調(diào)用API Sd_Init()，則應進入Down階段。

Timings and repetitions for Client Service and Consumed Eventgroups

• The Service Discovery phases allow minimizing the number of Service Discovery messages sent while allowing for very fast synchronization upon ECU start.
  Service Discovery各階段允許最小化發(fā)送的Service Discovery消息的數(shù)量，同時允許在ECU啟動時進行非常快速的同步
• This de-emphasis is realized by the following Phases:
  • Down
  • Requested
    • Initial Wait Phase
    • Repetition Phase
    • Main Phase

Down Phase for Client Services

• As long as a service is not requested by the BswM, the Service Discovery shall not send FindService Entry entries.
  只要BswM沒有請求服務， Service Discovery就不應發(fā)送FindService Entry。
• If an OfferService Entry is received during Down Phase,
  如果在Down階段收到OfferService entry，
  • The Service Discovery shall store the state of this Service instance.
    ServiceDiscovery應存儲此Service實例的狀態(tài)。
  • A timer shall be set/reset to the TTL value of the received OfferService entry (TTL timer).
    計時器應設置/重置為收到的OfferService條目（TTL計時器）的TTL值。
  • Until the TTL Timer expires or a StopOfferService entry is received, the Service instance is considered Available.
    在TTL計時器到期或收到StopOfferService條目之前，服務實例被視為可用。

• If Sd_ClientServiceSetState() is called with state SD_CLIENT_SERVICE_REQUESTED while being in Down Phase:
  如果在處于Down Phase狀態(tài)時調(diào)用狀態(tài)為SD_CLIENT_SERVICE_REQUESTED的API Sd_ClientServiceSetState（）：
  • If no OfferService entry was received before or its TTL timer expired already:
    如果之前未收到OfferService條目或其TTL計時器已到期：
    • The Initial Wait Phase shall be entered,
      應進入初始等待階段，
  • If an OfferService entry was received and its TTL timer did not expire yet:
    如果收到OfferService條目且其TTL計時器尚未到期：
    • If SoAd_OpenSoCon() was not called before, the API SoAd_OpenSoCon() shall be called for all Socket Connections associated with this Client Service Instance.
      如果之前未調(diào)用SoAd_OpenSoCon（），則應為與此客戶端服務實例關聯(lián)的所有套接字連接調(diào)用API SoAd_OpenSoCon（）。
    • The API SoAd_EnableSpecificRouting() shall be called with SdClientServiceActivationRef (see SdConsumedMethods) and the relevant Socket Connections for this Client Service Instance.
      應使用SdClientServiceActivationRef（請參閱SdConsumedMethods）和此客戶端服務實例的相關套接字連接來調(diào)用API SoAd_EnableSpecificRouting（）。
    • Open TCP connection if SdClientServiceTcpRef is configured and was not opened before.
      如果配置了SdClientServiceTcpRef并且之前未打開，則打開TCP連接。
    • The Main Phase shall be entered.
      應當進入Main階段。