View Issue Details

IDProjectCategoryView StatusLast Update
000567410000-004: ServicesSpecpublic2020-06-01 19:19
ReporterSendMatt Assigned ToJim Luth  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionno change required 
Summary0005674: Missing (or hard to find) explicit definition of keep-alive interval / time interval in context of subscriptions
Description

As far as I understood so far Subscriptions are independent of ClientSession like described here "7.11 Subscription Service Set" https://reference.opcfoundation.org/v104/Core/docs/Part1/7.11/ ) or at "CloseSession" parameter "deleteSubscriptions" ( https://reference.opcfoundation.org/v104/Core/docs/Part4/5.6.4/ );

Therefore also corresponding parameters at "CreateSubscription" ( https://reference.opcfoundation.org/v104/Core/docs/Part4/5.13.2/ ) exist like e.g. "revisedLifetimeCount":
"...
revisedLifetimeCount Counter The lifetime of the Subscription shall be a minimum of three times the keep-alive interval negotiated by the Server.
..."
Unfortuneatly those parameters are mostly "counters" (and not time values / time intervals), but I could NOT find a concrete time / time interval mentioned e.g. by "keep-alive interval negotiated by the Server" or other occurences of "keep-alive time interval". I would assume that e.g. TCP keep-alive is not what is meant here, or?

I have only come across "KeepAliveTime" at "6.2.5 WriterGroup Parameters" ( https://reference.opcfoundation.org/v104/Core/docs/Part14/6.2.5/#6.2.5.3 )
"...
6.2.5.3 KeepAliveTime
The KeepAliveTime with DataType Duration defines the time in milliseconds until the Publisher sends a keep alive DataSetMessage in the case where no DataSetMessage was sent in this period by a DataSetWriter. The minimum value shall equal the PublishingInterval.
..."

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2020-06-01 19:18

administrator   ~0012153

https://reference.opcfoundation.org/v104/Core/docs/Part4/5.13.1/ states:
"6. Subscriptions have a keep-alive counter that counts the number of consecutive publishing cycles in which there have been no Notifications to report to the Client. When the maximum keep-alive count is reached, a Publish request is de-queued and used to return a keep-alive Message."

The period of the "publishing cycle" is defined by the revisedPublishingInterval returned by the CreateSubscription() service.

Issue History

Date Modified Username Field Change
2020-05-29 10:16 SendMatt New Issue
2020-06-01 19:18 Jim Luth Note Added: 0012153
2020-06-01 19:19 Jim Luth Assigned To => Jim Luth
2020-06-01 19:19 Jim Luth Status new => closed
2020-06-01 19:19 Jim Luth Resolution open => no change required