TS-0004 : handling of beaconRequester attribute is missing in procedures of 7.4.70.2.1 and 7.4.70.2.3
The special handling of the <timeSyncBeacon>'s beaconRequester attribute is missing the CREATE and UPDATE procedure in TS-0004, clauses 7.4.70.2.1 and 7.4.70.2.3 . The description for this attribute in TS-0001:
This attribute is configured with the AEID or CSE-ID of the entity requesting beacon notifications from the Hosting CSE (see note).
This attribute shall be configured if the beaconCriteria attribute is set to "Loss of Synchronization".
This attribute is not applicable if the beaconCriteria attribute is set to "Periodic".
And the mentioned note:
NOTE: The AE-ID and CSE-ID identifiers should be shortened to use CSE-Relative or SP-Relative formats when appropriate based on their context of use (see clause 7.2).
The nature of this attribute implies that the request receiver as well as the originator need to take special care of this attribute.
Proposal
Add procedures to TS-0004, 7.4.70.2.1 and 7.4.70.2.3, for the originator and receiver:
Originator
- Add new text:
The originator shall set the beaconRequester attribute in the request if the beaconCriteria attribute is set to "LOSS_OF_SYNCHRONIZATION".
Receiver
- Add a new point after 1 b) and renumber c) to d)
- Add new Text
c) The Hosting CSE shall check that the beaconRequester attribute is present in the request only if the value of the beaconCriteria attribute its set to "LOSS_OF_SYNCHRONIZATION". If the value of the beaconCriteria attribute is "PERIODIC" then the beaconRequester attribute must not be present in the request.