View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000563410000-004: ServicesSpecpublic2020-05-08 15:082021-12-14 17:12
ReporterPaul Hunkar Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Summary0005634: Subscription publish Min 02 - retransmission queue
Description

States that support for a retransmission queue is not required, but this statement does not provided enough details on how the server should function with regard to acknowledgement of sequence numbers. This cause interoperability issue with regards to clients that send an ack for the received sequence number. The specification say to return an error is the sequencenumber is not in the list.

This conformance unit should either:
1) not allow a 0 size, but at least have a size of 1 (i.e. the message that just went out (which will allow clients to ack it) [preferred]
2) add text about behavior with regard to client ack of the sequence number - i.e. all number passed if no queue is present are always just accepted (no Bad_SequenceNumberUnknown is returned - just a good) - review all other specification section since multiple other location in the spec describe that a retransmission queue is required and describe behavior related to it. - this may require updates more updates in other parts also.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0004795 closedMatthias Damm 10000-004: Services Handling of Publish unclear if retransmission queue is disabled 
related to 0006033 closedRandy Armstrong NodeSets, XSDs and Generated Code Subscription publish Min 02 - retransmission queue 
related to 0006034 assignedAlexander Allmendinger Compliance Test Tool (CTT) Unified Architecture Subscription publish Min 02 - retransmission queue 
related to 0006089 closedAlexander Allmendinger Compliance Test Tool (CTT) Unified Architecture Clarification [Subscription Client Basic] [Err-010] sequence number handling 
related to 0007467 closedMatthias Damm 10000-004: Services Remove "shall" that makes retransmission queue mandatory 

Activities

Jim Luth

2020-05-19 15:17

administrator   ~0012072

Last edited: 2020-05-19 15:22

Add return code: Good-RetransmissionQueueNotSupported to be returned in the Publish.
Possibly add a ServerCapabilities to indicate support for Retransmission (Part 5).

Matthias Damm

2020-09-16 19:17

developer   ~0012885

5.13 Subscription Service Set
5.13.1.1 Description
Replace i) with the following text:
Sessions maintain a retransmission queue of sent NotificationMessages. NotificationMessages are retained in this queue until they are acknowledged. The Session shall maintain a retransmission queue size of at least two times the number of Publish requests per Session the Server supports. A Profile in OPC 10000-7 may make the retransmission queue support optional. The minimum number of Publish requests per Session the Server shall support is defined in OPC 10000-7. Clients are required to acknowledge NotificationMessages as they are received if the Publish response parameter availableSquenceNumber is not an empty array. An empty array in availableSquenceNumber indicates that the Server does not support a retransmission queue and acknowledgemet of NotificationMessages. In the case of a retransmission queue overflow, the oldest sent NotificationMessage gets deleted. If a Subscription is transferred to another Session, the queued NotificationMessages for this Subscription are moved from the old to the new Session.

5.13.5 Publish

Table 95 – Publish Service Parameters
Replace availableSequenceNumbers description with the following text:
A list of sequence number ranges that identify unacknowledged NotificationMessages that are available for retransmission from the Subscription’s retransmission queue including the sequence number of this response if it is not a keep-alive Message. This list is prepared after processing the acknowledgements in the request (see 7.8 for Counter definition).
The list shall be empty if the Server does not support the retransmission queue. If the list is empty, the Client should not acknowledge sequence numbers.

Table 97 – Publish Operation Level Result Codes
Add status code to table
Good_RetransmissionQueueNotSupported
The Server does not support retransmission queue and acknowledgement of sequence numbers is not available.

Updated in OPC 10000-4 - UA Specification Part 4 - Services 1.05.0 Draft11.docx
Errata is prepared

Jim Luth

2020-09-17 15:19

administrator   ~0012917

Agreed to changes edited in Virtual F2F including 1.04 and 1.03 Errata.

Issue History

Date Modified Username Field Change
2020-05-08 15:08 Paul Hunkar New Issue
2020-05-19 15:17 Jim Luth Note Added: 0012072
2020-05-19 15:17 Jim Luth Relationship added related to 0004795
2020-05-19 15:18 Jim Luth Project 10000-007: Profiles => 10000-004: Services
2020-05-19 15:18 Jim Luth Assigned To => Matthias Damm
2020-05-19 15:18 Jim Luth Status new => assigned
2020-05-19 15:22 Jim Luth Note Edited: 0012072
2020-09-16 19:17 Matthias Damm Status assigned => resolved
2020-09-16 19:17 Matthias Damm Resolution open => fixed
2020-09-16 19:17 Matthias Damm Note Added: 0012885
2020-09-17 15:16 Jim Luth Issue cloned: 0006033
2020-09-17 15:16 Jim Luth Relationship added related to 0006033
2020-09-17 15:17 Jim Luth Issue cloned: 0006034
2020-09-17 15:17 Jim Luth Relationship added related to 0006034
2020-09-17 15:19 Jim Luth Status resolved => closed
2020-09-17 15:19 Jim Luth Fixed in Version => 1.05
2020-09-17 15:19 Jim Luth Note Added: 0012917
2021-04-01 14:43 Paul Hunkar Relationship added related to 0006089
2021-12-14 17:12 Jim Luth Relationship added related to 0007467