View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000210710000-004: Servicespublic2012-07-09 17:172013-12-10 17:19
ReporterHannes Mezger Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.02 
Summary0002107: ModifySubscription: Behavior after changing the PublishingInterval
Description

According to Part 4, 5.13.3.2:

Changes to the publishing interval become effective the next time the publishing timer expires.

Some servers might not be able to implement this behavior. Assume a server having hardcoded publishing intervals of 100, 500 and 1000 using timers that start running on server startup. If a subscription is now modified from 100 to 1000, the server would move it from one timer to the other, and the subscription would publish the next time the 1000ms timer expires. To satisfy the needs of the UA Spec, the server would need to have one timer per subscription what might be impossible on certain systems.

Another problem that might appear: a subscription is created with publishing interval 60000ms. After a while the interval is changed to 100ms, as the client wants to retrieve values as fast as possible. According to the UA Spec, in the worst case the client would have to wait up to 60000ms before the new publishing interval is set - this is no reasonable behavior.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Jim Luth

2013-09-10 17:31

administrator   ~0004987

Last edited: 2013-09-10 17:33

.NET implementation uses an algorithm where the new interval is adjusted immediately and adjusted based on the previous publish. This seems to violate the statement from Part 4.

We need to discuss this to decide on a fix/clarification to the spec.

Matthias Damm

2013-10-09 22:59

developer   ~0005044

Replaced definition in 5.13.3 ModifySubscription with
Changes to the Subscription settings shall be applied immediately by the Server. They take effect as soon as practical but not later than twice the new revisedPublishingInterval.

Also changed 5.12.3 ModifyMonitoredItems to
Changes to the MonitoredItem settings shall be applied immediately by the Server. They take effect as soon as practical but not later than twice the new revisedSamplingInterval.

Resolved in document IEC 62541-4 - Services [Pre-CDV] 1.02.06.doc

We need to add an errata for these changes

Jim Luth

2013-11-25 17:49

administrator   ~0005141

Agreed to changes in doc in telecon. Awaiting Errata to close the issue.

Jim Luth

2013-12-10 17:19

administrator   ~0005181

Agreed to Errata

Issue History

Date Modified Username Field Change
2012-07-09 17:17 Hannes Mezger New Issue
2012-07-09 17:18 Hannes Mezger Status new => assigned
2012-07-09 17:18 Hannes Mezger Assigned To => Matthias Damm
2012-07-17 16:50 Jim Luth Status assigned => acknowledged
2012-07-17 16:50 Jim Luth Assigned To Matthias Damm =>
2012-07-17 16:50 Jim Luth Project 10000-004: Services => Feature Requests
2013-09-10 17:31 Jim Luth Note Added: 0004987
2013-09-10 17:33 Jim Luth Note Edited: 0004987
2013-09-10 17:33 Jim Luth Status acknowledged => new
2013-09-10 17:34 Jim Luth Project Feature Requests => 10000-004: Services
2013-10-09 22:58 Matthias Damm Status new => assigned
2013-10-09 22:58 Matthias Damm Assigned To => Matthias Damm
2013-10-09 22:59 Matthias Damm Status assigned => resolved
2013-10-09 22:59 Matthias Damm Resolution open => fixed
2013-10-09 22:59 Matthias Damm Note Added: 0005044
2013-11-25 17:49 Jim Luth Note Added: 0005141
2013-12-10 17:19 Jim Luth Status resolved => closed
2013-12-10 17:19 Jim Luth Note Added: 0005181
2013-12-10 17:19 Jim Luth Fixed in Version => 1.02