SSRF Interference Incident Report

Interference Incident Reporting enables standardized reporting significant interference, rapid identification of potential sources, and resolution assistance.

Introduction

To provide full spectrum management capability it is important that all significant interference is reported. All interference has a source (the equipment causing the interference) and a victim (the system or assignment suffering from the interference), and resolving interference between the two may be achieved by either readjusting the source or victim parameters and configuration.

Since it is important to avoid causing further interference effects on other systems while trying to resolve a particular interference case the resolution process should be based on careful analysis of the relevant EM environment. Therefore the process should normally involve the use of appropriate spectrum analysis tools.

Typically, interference will be resolved at the lowest possible organizational level. This however, is not always the case, therefore the interference reports must be generated and forwarded through the spectrum management organizational hierarchy.

Assuming the victim of the interference is unable to resolve the interference, interference reports should be created at the victim site and sent to higher headquarters [IAW CJCSI 3320.02].

The lowest level receiving the interference report will attempt deconfliction using the tools available at that level (database, analysis tools applying various propagation and terrain models, etc). If the interference cannot be resolved at the point where the interference is initially detected, an interference report will be prepared and forwarded to the next level for action. In cases involving international coordination, the interference report may be forwarded to the relevant national authority.

Regardless of level at which an interference issue is resolved and the report closed the final report should be forwarded to the central database for historical reference.

Interference Incident Report Processing History

The interference resolution process may result in an interference report being forwarded through the spectrum management organizational hierarchy. As the interference report is processed through the organization, the status changes and the actions taken at each processing stage shall be recorded and made available to the requesters. A processing history of the interference and its mitigation is recorded for later reference.

A state transitions of an interference report concept is illustrated abvoe while it travels through the organizational hierarchy during a resolution process. According to this state diagram, a message is in a New state when it is first created and sent to an immediate spectrum management authority.

  • If the receiving authority decides that the message can be processed (resolved) at his/her site, the message is put into the In Process state and a resolution is attempted.
  • If the problem is handled the message is put into a Resolved state until the user accepts the resolution, moving it to a Closed state and terminating the process.
  • If the user rejects the resolution, the message is sent back to the In Process state.
  • If the first recipient can not handle the message, the message is forwarded to the next level of authority in the spectrum management organizational hierarchy. Therefore the message is put into a Forwarded state.

The forwarding process is repeated until the appropriate authority resolves the issue. An interference processing history will provide the sequence of these transitions.

Requesting an Incident Processing History

The processing history will accumulate in the Status element list under the main Interference Report (see IntfReport element). Requesting the processing history can be achieved by sending a Data Request (see Administrative Element) message containing the dataset reference of the requested IntfReport element. The resulting SSRF message sent as a response to this request MUST contain the IntfReport element including the accumulated status elements to indicate the stages of the resolution process.

Example:

<IntfReport serial="BEL:AR:IR:123" usageType="A" entry="2004-05-20" lastMod="2006-11-05T12:30:00Z">
  <... other Common elements ...>
  <Status state="ORIGINATED BY" dateTime="1995-12-31T15:33:48Z" byContact="BEL:AR:CN:UNIT1/123"/>
  <Remarks xpath="./Status[1]">Interference detected and cannot be resolved here.</Remarks>
  <Status state="FORWARDED TO" dateTime="1996-01-16T16:31:12Z"
  fromContact="BEL:AR:CN:UNIT1/123" toContact="BEL:AR:CN:COMBASE/129"/>
  <Remarks xpath="./Status[2]">This interference requires higher command involvement.</Remarks>
  <Status state="RECEIVED BY" dateTime="1996-01-17T16:31:12Z" byContact="BEL:AR:CN:COMBASE/129"/>
  <Remarks xpath="./Status[3]">Received an interference report.</Remarks>
  <Status state="IN PROCESS AT" dateTime="1996-02-01T09:12:12Z" byContact="BEL:AR:CN:COMBASE/129"/>
  <Remarks xpath="./Status[4]">We can resolve this interference here.</Remarks>
  <Status state="CLOSED BY" dateTime="1996-03-13T16:00:05Z" byContact="BEL:AR:CN:COMBASE/129"/>
  <Remarks xpath="./Status[5]">Interference resolved. The source system power was reduced.</Remarks>
  <... other Common + IntfReport elements...>
</IntfReport >
            

Joint Spectrum Interference Resolution (JSIR)

[Ref CJCSM 3320.02] Joint Spectrum Interference Resolution (JSIR) is a process designed to mitigate or define the procedures to mitigate Electromagnetic interference (EMI) that regularly hampers the Command and Control (C2) of military/non-military operations by degrading essential systems that use the electromagnetic spectrum. Since EMI can be caused by enemy, neutral, friendly, or natural sources, it generally must be resolved on a case-by-case basis.

The intent of the JSIR procedures is to resolve EMI incidents at the lowest possible level within the command structure. However, when the cause and recipient of the interference are not within the same component force or supporting element, resolution may require assistance from the command, Combined Joint Task Force (CJTF), service spectrum management HQ or higher levels of authority.

Operating Clearance

The Operating Clearance business process is not authorized for U.S. Forces but it may be used by some allied forces. It is described here for informational purposes.

The aim of the Operating Clearance process is to facilitate the timely provision of information leading to compatible systems that use the electromagnetic spectrum. It allows the operational spectrum managers to assess, with a certain degree of confidence, whether the equipment which will be brought into the operational theater will operate without creating interference. The Operating Clearance is the tactical version of the full Spectrum Supportability process; it MUST NOT be used as a replacement of the full Spectrum Supportability and MUST only be used in cases of short-term requirements in support of a critical operation. Acceptance of this abbreviated procedure is at the discretion of the commander.

A summary of the Operating Clearance process is illustrated below.

Data Object

The Interference Incident Report (IntfReport) Data Object contains information on a source and victim of an interference incident.

See the OpenSSRF Javadoc for more details.

Session Error

Your session may have timed out or encountered an error. Please refesh the page to continue.