SSRF Administrative Messaging

An Administrative SSRF message has several usages:

• Request datasets from another data repository;
• Reject an incoming dataset which cannot be validated against the local repository, for example is it refers to unknown datasets;
• Set up an Area of Interest (AOI) where data is forwarded to or pulled by a user to maintain a data repository needed by the user to meet mission requirements.

Within an Administrative transaction other SSRF data object elements specify which the action must apply. For example:

• It can be used to inform other data repositories that datasets have been deleted from a data repository;
• It can also be used to reject an incoming dataset which cannot be validated against the local repository, for example is it refers to unknown datasets.
• Automated local data repository changes are not permitted on US systems.

Examples of Administrative message use include:

• Request a Table of Allocation (TOA) record
• Request an Interference Report Processing History
• Distribution of data sets.

Distribution of referenced data is decided at the initial handshake or specified using the external attribute of the Administrative element.

The Administrative message is used to request dataset(s) from other spectrum management systems. This element can be used to request specific datasets by specifying the dataset identifier required. Alternatively it can be used to query another repository for information. It is the responsibility of each spectrum management system to manage and control the release of information.

If a received document contains invalid or missing data then the Administrative message SHOULD be used to request that the document is re-sent with the necessary amendments.

If an invalid document is received the sender SHOULD be informed that the document could not be processed and requesting that the data is re-issued. This is accomplished using the Administrative message with reason="INVMSG".

Data element Administrative has several usages:

• It can be used to inform other data repositories that datasets have been deleted from a data repository;
• It can also be used to reject an incoming dataset which cannot be validated against the local repository, for example if it refers to unknown datasets.
• Automated local data repository changes are not permitted on US systems.

Sub-Elements are CodeList, Dataset.

Administrative Data Object

Example: Rejecting an Assignment for which the recipient does not have the referenced Transmitter dataset:

<Administrative cls="U">
  <Serial cls="U">DEU:NFA:DR:123</Serial>
  <MessageRef cls="U">DEU:NFA:MS:123</MessageRef>
  <EntryDateTime cls="U">2011-12-25T00:00:00Z</EntryDateTime>
  <Action cls="U">Missing Refs</Action>
  <Dataset>
    <Serial cls="U">USA::AS:456</Serial>
    <MissingRef cls="U">USA::TX:123</MissingRef>
  </Dataset>
</Administrative>

See the OpenSSRF Javadoc for more details.