search

eclipse-sparkplug / sparkplug

Sparkplug
Eclipse Public License 2.0
109 stars 39 forks source link

Question: Device state behavior #470

Closed yh742 closed 1 year ago

yh742 commented 1 year ago

What do you want to know?

Hello,

I was hoping to get some clarification on the spec regarding the device lifecycle. According to the spec:

[tck-id-payloads-dbirth-order] All DBIRTH messages sent by an Edge Node MUST be sent immediately after the NBIRTH and before any NDATA or DDATA messages are published by the Edge Node.

In the scenario that node and device session establishes successfully, a device within the node goes down and comes back up again. Can I simply send a DBIRTH for that device or would I need to resend ALL the NBIRTH and DBIRTH certificates again.

Thanks

Is this related to a Sparkplug Listing request? If so, link the issue from https://github.com/eclipse-sparkplug/sparkplug.listings here.

No response

Version

3.0.0 (Default)

Accept EFTL Terms

bryce-nakatani commented 1 year ago

Thank you for your inquiry.

The rapid succession requirements of NBIRTHs and subsequent DBIRTHs are driven by a specific host implementation handling of templates (UDTs).

An implementation I manage produces DDEATH and DBIRTH cycles within the same stateful NBIRTH. But we don't implement templates.

If implement templates are used, you're probably fine to publish a DBIRTH (without a new NBIRTH) as long as the device's templates don't change. If they do, you'll have to publish an NDEATH and then the node and all the device birth certificates to synchronize the template changes.

On Wed, Aug 9, 2023 at 7:14 AM Sean Hsu @.***> wrote:

What do you want to know?

Hello,

I was hoping to get some clarification on the spec regarding the device lifecycle. According to the spec:

[tck-id-payloads-dbirth-order] All DBIRTH messages sent by an Edge Node MUST be sent immediately after the NBIRTH and before any NDATA or DDATA messages are published by the Edge Node.

In the scenario that a device within the node goes down and comes back up again. Can I simply send a DBIRTH for that device or would I need to resend ALL the NBIRTH and DBIRTH certificates again.

Thanks Is this related to a Sparkplug Listing request? If so, link the issue from https://github.com/eclipse-sparkplug/sparkplug.listings here.

No response Version

3.0.0 (Default) Accept EFTL Terms

  • I agree to the terms of EFTL

— Reply to this email directly, view it on GitHub https://github.com/eclipse-sparkplug/sparkplug/issues/470, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEF6AZRLKYJBWNTVWKUN6NTXUOLMDANCNFSM6AAAAAA3KCM4HE . You are receiving this because you are subscribed to this thread.Message ID: @.***>