Network and Spectrum
Management Use Cases
Spectrum and Tactical Network Management Use Cases
TR170
Draft V0.3
July 2011
TM Forum 2011
Spectrum and Network Management Use Cases
Notice
No recipient of this document and code shall in any way interpret this material as representing a
position or agreement of TM Forum or its members. This material is draft working material of TM
Forum and is provided solely for comments and evaluation. It is not “Forum Approved” and is
solely circulated for the purposes of assisting TM Forum in the preparation of final material in
furtherance of the aims and mission of TM Forum.
Although it is copyrighted material of TM Forum:

Members of TM Forum are only granted the limited copyright waiver to distribute this
material within their companies and may not make paper or electronic copies for
distribution outside of their companies.

Non-members of the TM Forum are not permitted to make copies (paper or electronic) of
this draft material other than for their internal use for the sole purpose of making
comments thereon directly to TM Forum.

If this material forms part of a supply of information in support of an Industry Group
Liaison relationship, the document may only be used as part of the work identified in the
Liaison and may not be used or further distributed for any other purposes
Any use of this material by the recipient, other than as set forth specifically herein, is at its own
risk, and under no circumstances will TM Forum be liable for direct or indirect damages or any
costs or losses resulting from the use of this material by the recipient.
This material is governed, and all recipients shall be bound, by all of the terms and conditions of
the Intellectual Property Rights Policy of the TM Forum
(http://www.tmforum.org/Bylaws/1094/home.html) and may involve a claim of patent rights by
one or more TM Forum members or by non-members of TM Forum.
Direct inquiries to the TM Forum office:
240 Headquarters Plaza,
East Tower – 10th Floor,
Morristown, NJ 07960 USA
Tel No. +1 973 944 5100
Fax No. +1 973 944 5110
TM Forum Web Page: www.tmforum.org
TR170, Version 0.3
© TM Forum 2011
Page 2 of 39
Spectrum and Network Management Use Cases
Table of Contents
Notice...................................................................................................................................................................2
Table of Contents ..............................................................................................................................................3
1.1.
Introduction ..........................................................................................................................................4
1.2.
Net Service Area (NSA).......................................................................................................................5
1.3.
Other Factors Affecting Spectrum Re-Use. ....................................................................................8
1.4.
Scenario ................................................................................................................................................9
1.5.
Actors ................................................................................................................................................. 11
2. Use Case 1 – Spectrum Planning............................................................................................................. 17
2.1.
Characteristic Information .............................................................................................................. 18
2.2.
Main Success Scenario 1 ................................................................................................................ 20
2.3.
Scenario Extensions ........................................................................................................................ 22
3. Use Case 2 – Interference and Re-Planning........................................................................................... 23
3.1.
Characteristic Information .............................................................................................................. 24
3.2.
Main Success Scenario ................................................................................................................... 26
3.3.
Scenario Extensions ........................................................................................................................ 28
4. Use Case 3 – Dynamic Spectrum Management .................................................................................... 29
4.1.
Characteristic Information .............................................................................................................. 30
4.2.
Main Success Scenario ................................................................................................................... 32
4.3.
Scenario Extensions ........................................................................................................................ 34
5. Open Issues ................................................................................................................................................. 35
6. Administrative Appendix ........................................................................................................................... 36
6.1.
Document History............................................................................................................................. 37
6.2.
Company Contact Details ............................................................................................................... 38
6.3.
Acknowledgments............................................................................................................................ 39
TR170, Version 0.3
© TM Forum 2011
Page 3 of 39
Spectrum and Network Management Use Cases
1.1.
Introduction
These Use Cases draw on research on interactions between existing Spectrum Management
and Tactical Network Management Systems. Neither of these management systems were
specifically developed using TM Forum guidelines or standards, however, due to following
industry best practices, there are similarities. Although a number of data formats were used,
Spectrum Management Allied Data Exchange Format – eXtensible Markup Language
(SMADEF- XML)1 was used where possible. The purpose of the research was to increase the
effective bandwidth available to Tactical Communication System in operations.
These Use Cases are provided to inform the Network Management and Spectrum Management
Integration Project and are a reflection of current processes constrained by current technical
solutions. They can assist in identifying where clearer processes, definition and coherence
between Spectrum Management and Network Management are required. In addressing
Spectrum Management within Network Management, the need for coherence with other network
related elements became apparent, e.g., deployment of waveforms, security and crypto
management. It also pointed to the conclusion, that while elements of Spectrum Management
are contained within Network Management, Spectrum is a resource which needs to be managed
at the Enterprise Level. The objects of each Use Case will assist readers to understand the
benefits of Dynamic Spectrum Management.
In presenting theses Uses Cases, the concept of a Net Service Area is introduced to provide
background.
A military operational scenario is used to derive three Use Cases addressing:

Spectrum and Network Planning

Interference and Re-Planning

Dynamic Spectrum Management
Actors common to all Use Cases presented are also shown.
1
AC/322(SC/3)D(2007)0003-Rev7, SMADEF XML 2.0.0. 07 April 2010
TR170, Version 0.3
© TM Forum 2011
Page 4 of 39
Spectrum and Network Management Use Cases
1.2.
Net Service Area (NSA)
The majority of spectrum users within the tactical domain are mobile and their exact locations at
any point in time are uncertain and changing2. The concept of Net Service Areas (NSA) is used
to provide defined areas in which network users can use the same spectrum without it having a
detrimental effect on either net.
Figure 1 – Net Service Area (NSA)
The use of NSA in the Network Communications Plan takes into account the geographical use of
the network to allow re-use. If two networks are sufficiently separated, taking into account factors
such as geographical distance, topography, technical characteristics of the radio frequency
systems used and the spectrum involved, then the same spectrum can be re-used without it
having a detrimental effect on either net. This is known as spectrum re-use within the Spectrum
Community. In order to determine the level of protection required between the two networks to
allow spectrum re-use, a co-ordination distance (or level of protection) must be determined.
Figure 2 below provides an indication of the protection that is required.
While the focus of this work forces’ is on military handset/backpack/vehicle mounted radios, there are civilian radios that
employs dynamic spectrum access
2
TR170, Version 0.3
© TM Forum 2011
Page 5 of 39
Spectrum and Network Management Use Cases
Figure 2: NSA Showing Co-ordination Limit.
The coordination limit area is the region around an NSA that is considered sterilized due to
possible signals originating from the edges of the NSA. The range of this area around the NSA
will vary at different parts of the NSA due to various factors mentioned and is known as the
Coordination Limit. This is effectively the furthest distance that any transmission originating from
within the NSA will travel at a signal level that may cause interference to another service.
Figure 3 illustrates two NSA where the networks cannot re-use the same spectrum.
Figure 3 – Overlap of Co-ordination Limits of two NSA
TR170, Version 0.3
© TM Forum 2011
Page 6 of 39
Spectrum and Network Management Use Cases
Figure 4 below illustrates that the same spectrum can be re-used by both networks in NSA 1
and NSA 3 and therefore would provide increased spectrum efficiency which could then lead
to improvements in the plan allow additional network capacity.
Fi
Figure 4 -Spectrum Re-Use
The Coordination Limit also must consider all the different RF spectrum bands that are required
to support tactical movements within each NSA on a constant basis. As the operational tempo
changes so does the requirements for specific spectrum, therefore the limit of protection will
adjust.
TR170, Version 0.3
© TM Forum 2011
Page 7 of 39
Spectrum and Network Management Use Cases
1.3.
Other Factors Affecting Spectrum Re-Use.
Area of Responsibility (AOR) is a military concept indicating a geographical area in which a
military organization has operational responsibility. To undertake this responsibility, the military
organization will be supported by various spectrum using communities, including Tactical
Communication Networks. Spectrum usage within the AOR “Battlespace” requires co-ordination.
There will rarely be a direct mapping of an AOR with an NSA as they are defined by different
criteria. There may be several NSA within an AOR.
Today these different AORs are occupied by forces from different services, countries and
agencies, therefore the coordination must be even more detailed to ensure full spectrum support
is given to all spectrum users and that potential interference is also avoided. It also points to the
need for hierarchical spectrum management processes for planning, escalation and
management to be addressed. Factors which need to be addressed include the following:

In a tactical environment spectrum re-use and efficiency can be more effectively
accomplished when coordination with other spectrum using communities are
synchronized because a lot of tactical movements are timed based. This means that all
spectrum is not needed on a 24X7 basis.

Another area to be addressed is the level of security clearances of all the different
spectrum users. Not all spectrum user communities have the same security clearances
or need to know, therefore spectrum or network planners may not be aware of all the
users or requirements within their respective Areas of Responsibility (AOR).

Timed based coordination is critical to ensure spectrum efficiency.

Another consideration that must be taken into account is the difference between fixed and
mobile spectrum users. Fixed site users typically stay within a certain limit whereas
mobile users can cover an entire AOR. Therefore within an AOR you may have subAORs of different spectrum users, so spectrum limits may vary within each AOR and the
NSA needed to support Users as they move within the AOR.
.
TR170, Version 0.3
© TM Forum 2011
Page 8 of 39
Spectrum and Network Management Use Cases
1.4.
Scenario
Figure 5: Two Military Patrols Scenario
Figure 5 depicts two military patrols are moving East from a base on roughly parallel routes
initially separated by high terrain. Terrain separation reduces as patrols move East and the routes
converge. There are hostile and neutral emitters in the area. The patrols are supported by
Tactical Communications. This give rise to numerous potential scenarios and Use Cases related
to Spectrum Management.
The NSA for each patrol taking into account planned moves is depicted by the overlays as shown
in Figure 6.
TR170, Version 0.3
© TM Forum 2011
Page 9 of 39
Spectrum and Network Management Use Cases
Figure 6 : NSA Overlays Indicating Movement Areas where Re-Use is Possible.
Spectrum re-use is possible while the Patrols are operating within the defined NSA. As Patrols
move further East, the ability for re-use ceases unless movements of the Patrols are coordinated
and time-based. If not, new Spectrum allocations would be required to support operations outside
the NSA. In operations, movements of Spectrum Users can be highly dynamic and can
frequently change from anything planned. This highlights the need for co-ordination between
operations and Spectrum Management and for a dynamic Spectrum Management capability to
respond to changing operational needs.
By exploiting existing Spectrum Situational Awareness data allows Spectrum Management to
monitor for potential spectrum conflict and detect potential interference and connectivity between
Spectrum Users.
TR170, Version 0.3
© TM Forum 2011
Page 10 of 39
Spectrum and Network Management Use Cases
1.5.
Actors
Within the scenarios there are several potential Use Cases involving various roles /actors within
the network and spectrum management stakeholder communities. Significant work has been
done in the spectrum community in development of SMADEF-XML and these are depicted in
Figure 7.
Figure 7: Actors from SMADEF-XML3
Additional actors have been identified when considering NSA management and the Scenario
involving both Spectrum Management and Network Management. While not of these actors will
be depicted in the Use Cases, they are illustrated in the Figures 8 and 9 to provide a context for
the Use Cases presented and for defining future Use Cases.
3
SMADEF- XML Release 2.0 approved at CCB 14
TR170, Version 0.3
© TM Forum 2011
Page 11 of 39
Spectrum and Network Management Use Cases
Figure 8: Actors – Network Management
Figure 8 shows the relationship between the Tactical Network Management System (TacNMS) and
other actors involved in Network Management, including Superior and Subordinate Tactical Network
Management Systems (SupNMS and SubNMS) and the Global NMS which has management
responsibilities to TacNMS in various the operational and tactical environments throughout the world.
Also depicted is the relationship to the Battlespace Spectrum Management System (BSpMS)
operating in the operational; area as the TacNMS, other Spectrum User Management Systems and
any Management Systems supporting Coalition Networks.
TR170, Version 0.3
© TM Forum 2011
Page 12 of 39
Spectrum and Network Management Use Cases
Figure 9: Hierarchy of Actors Operating in a Coalition Environment
Figure 9 depicts Spectrum Users and Tactical Networks from Nation “X” operating within a Coalition
Operation in a Host Nation the following should be noted:
 The Host Nation has a National Regulator of Spectrum which allocates spectrum to the
Coalition Forces and to other Spectrum Users in the Host Nation, including Commercial
Service Providers (CSP).
 The Coalition Management exercises control over the Spectrum Users and Networks
provided by various Nations contributing to Coalition Forces.
 Nation X Spectrum Users and Networks operate under Coalition Management within that
environment, but are also subject to management on Spectrum and Network
Management from home ie Nation “X”.
o Co-ordination of Spectrum is managed at the various levels between Coalition
and other Spectrum Users, eg CSP, by the Host Nation Regulator,
o Between Coalition Partners, eg Nation A and Nation “X”, at Coalition
Management level
o Between different Spectrum Users of Nation X Coalition Force, by Nation”X”
Management in that operational area.
o Between Nation “X” Spectrum Users globally, by Nation X Defence Management.
 Escalation of Spectrum Issues is upwards as depicted in the Figure.
TR170, Version 0.3
© TM Forum 2011
Page 13 of 39
Spectrum and Network Management Use Cases
Use Case Actors
.The following Actors appear in the Use Cases in this document:



Superior Spectrum Management System (SupSpMS). This represents the notional
system supporting the Superior Spectrum Manager in Figure 7. It could be a Coalition
Spectrum MS, a National Defence Spectrum MS or an amalgam of both (Figure 9). It will
provide:
o
Core Data, including Reference datai
o
Spectrum parametric data
o
Allotment of Spectrum for use in the specific Battlespace area.
Battlespace Spectrum Management System (BSpMS). This represents the notional
system supporting the Spectrum Manager in Figure 2. It provides tooling to support the
following activities. (No attempt has been made to determine the System boundary of the
BSpMS.)
o
Receive and maintain reference and parametric data
o
Receive requests for Spectrum from all spectrum-using systems.
o
Conduct spectrum planning and re-planning.
o
Allocate Spectrum.
o
Manage Spectrum Use, non-Use and Defragmentation.
o
Define Net Service Areas and export definitions
o
Accept Network and Spectrum User Plans and Situational Awareness
o
Share Spectrum Situational Awareness
Tactical Network Management System (TacNMS). The TacNMS supports the Tactical
Network Manager and will:
TR170, Version 0.3
o
Generate Spectrum Requests
o
Provide Network Situational Awareness.
© TM Forum 2011
Page 14 of 39
Spectrum and Network Management Use Cases


o
Receive Spectrum Allotments.
o
Receive Net Service Area allotments.
o
Conduct Network Planning, Re-planning and management.
o
Disseminate Network Plans, including frequency allocation to SubNMS
Subordinate Network Management System (SubNMS). The SubNMS supports the
Subordinate Tactical Network Managers responsible for specific networks established for
particular operations. These are likely to be established for particular areas and for
specified time periods. The SubNMS will:
o
Provide network input to User planning of operations
o
Provide operational and network input into Spectrum planning.
o
Receive Network Plan from TacNMS
o
Undertake Radio Fill,
o
Generate Interference Reports
Other Spectrum Systems. These are other Systems consuming and/or monitoring and
managing spectrum and which contribute to Shared Situational Awareness which
includes:
TR170, Version 0.3
o
All other National Battlespace Spectrum Users, including other networks, radar
systems, Counter IED systems etc.
o
All other Coalition Forces’ Spectrum Users impacting on the particular National
Battlespace (Spectrumspace)
o
All; other Host Nation Spectrum Users impacting on the particular National
Battlespace.
o
All other hostile and neutral emitters known.
o
Hostile emitters discovered;
o
Previously unknown Coalition emitters discovered;
o
Previously unknown neutral emitters discovered;
© TM Forum 2011
Page 15 of 39
Spectrum and Network Management Use Cases
TR170, Version 0.3
o
Coalition communications retuned;
o
Erroneous Coalition emissions.
© TM Forum 2011
Page 16 of 39
Spectrum and Network Management Use Cases
2. Use Case 1 – Spectrum Planning
Use Case ID Spectrum 1: Spectrum Planning
TR170, Version 0.3
© TM Forum 2011
Page 17 of 39
Spectrum and Network Management Use Cases
2.1.
Characteristic Information
Figure 10: Nets Separated by Terrain
The planning process considers all available Spectrum Situational Awareness (SpSA) data held
by the BSpMS and TacNMS at the Nation HQ, including geographical separation of patrols. The
situation allows each to have an NSA thereby permitting spectrum re-use.
The following information characterizes this particular use case.
Table 1
Type:
New Process
Scope:
Spectrum Management and Network Management
Level:
Operations and Enterprise
Audience:
Network Management and Spectrum Management Integration
Project Team Members
Battlespace Spectrum Management System (BSpMS)
Tactical Network Management System ( TacNMS)
Superior Spectrum Management System (SSpMS)
Other Spectrum Systems
SubNMS
 Sharing Spectrum Parametric Data;
 Automation of spectrum request/response via XML Allotment
message;
 Unused spectrum identified and re-farmed;
 Exploits planning data to improve re-use;
Primary Actor(s):
Supporting Actor(s):
Stakeholder Goals:
TR170, Version 0.3
© TM Forum 2011
Page 18 of 39
Spectrum and Network Management Use Cases


Geographic de-confliction exploiting BSpMS algorithms and
parametric data;
Awareness of TacNMS use to allow broader re-use across
Theatre plan;
BSpMS meet requirement with minimum spectrum
Policies Used:

NA
Processes Used:
NA
Pre-Conditions:
Provision of Shared Spectrum Situational Awareness data and
Reference Data from SSpMS and other Systems using and
monitoring Spectrum use. TacNMS conducts initial network planning
to generate spectrum request
Post-Conditions:
Triggers:
TR170, Version 0.3
Spectrum Request from TacNMS
© TM Forum 2011
Page 19 of 39
Spectrum and Network Management Use Cases
2.2.
Main Success Scenario 1
This Scenario describes the steps that are taken from trigger event to goal completion when
everything works without failure. It also describes any required cleanup that is done after the goal
has been reached. The steps are listed below:
Figure 11: Use Case - Spectrum Planning
TR170, Version 0.3
© TM Forum 2011
Page 20 of 39
Spectrum and Network Management Use Cases
Table 2
Step
Actor
Action Description
Comment
PreCond
SSpMS
Provide Reference and Spectrum
Parametric Data
PreCond
1
Other Spectrum
Systems
TacNMS
Share Spectrum Situational Awareness
Enterprise resources.
Reference and
Parametric Data
(SMADEF-XML).
Enterprise information
2
BSpMS
Plan Spectrum
Provides AOR to be
supported
Initial Planning
3
BSpMS
Allot Spectrum
Provisional Allotment
4
BSpMS
Define NSA
5
TacNMS
Plan Network
6
TacNMS
Export Network Plan
7
BSpMS
Update Spectrum Picture (Shared
Spectrum Situational Awareness)
8
TacNMS
Disseminate Plan
9
SubNMS
Do Radio Fill
TR170, Version 0.3
Request Spectrum
© TM Forum 2011
On receipt of NSA
Allotment
To Enterprise shared
information. On receipt
of Network Plan
For Implementation by
SubNMS
In accordance with
Disseminated Plan
Page 21 of 39
Spectrum and Network Management Use Cases
2.3.
Scenario Extensions
Planning is an iterative process between Network and Spectrum Managers and may require
several iterations before the User Requirements for Network Services can be met. This will
require “tuning” of the Spectrum and Network Plans with each other and may require Superior
Spectrum Management involvement when resolution cannot be achieved. These 2 situations are
shown in Table 3.
Table 3
Step
Condition
Action Description
6
6a
Export Network Plan
Spectrum Plan requires
revision to meet Network
requirements
Plan Spectrum
6b
Allot Spectrum
6c
Define NSA
6d
Plan Network
6
TR170, Version 0.3
.
Export Network Plan
Network and Spectrum Plans
compatible - Success
Requirement not able to be
met by resolution between
TacNMS and BSPMS
To Step 7
Escalation to SupSpMS – Separate Use Case.
© TM Forum 2011
Page 22 of 39
Spectrum and Network Management Use Cases
3. Use Case 2 – Interference and Re-Planning
Use Case Spectrum 2: Interference and Re-Planning
TR170, Version 0.3
© TM Forum 2011
Page 23 of 39
Spectrum and Network Management Use Cases
3.1.
Characteristic Information
Figure 12: Enemy Spectrum Emitters
In Figure 12, hostile spectrum emitters adversely affect Net 1, giving rise to an Interference Report by
Patrol 1.
Even with improved up-front spectrum planning and management, there are still scenarios in which
Tactical Radio users will suffer from service degradation or complete service loss as a result of
harmful interference. An example of such a scenario is a Radio User encountering interference from
another type of emitter, be it an enemy jammer or a neutral or allied force’s communications
equipment.
Currently in such circumstances, due to the complexity involved with re-planning a Tactical network,
all but the most extreme communications issues are worked around. The only real mechanism
available to the TacNMS operator is to utilize any “spare” spectrum allotted to them by the BSpMS to
work around the interference encountered. When spectrum is heavily congested, particularly in a
coalition environment, this “spare” spectrum may not always be available.
Within a system where TacNMS is tightly coupled to a BSpMS, interference is a much more
manageable situation.
As with the initial planning phase, the BSpM can use BSpMS to keep an accurate picture of all
spectrum assignments within their section of the Nation Battlespace allocation, as well as the
requirements of the Tactical Network. Interference\service loss can be mitigated by storing the details
of the problem in BSpMS and then using the assignment and allotment engine to re-plan the
assignments. With all of this data, BSpMS will be positioned to move spectrum allotted to systems
around in the plan, and providing TacNMS with an updated allocation away from the interference.
This re-planning works to ensure less instances of persistent service loss and a maintained level of
data throughput without requiring extra spectrum allocations as “spare” channels. The achievement
of the required data throughput to meet the military operational information requirements is the key
driver in network planning and for allocation of spectrum. Providing an appropriate balance between
TR170, Version 0.3
© TM Forum 2011
Page 24 of 39
Spectrum and Network Management Use Cases
providing optimum spectrum and “spare” spectrum at each level in the hierarchy would need to be
established to ensure the right balance between agility and efficiency can be achieved.
The following information characterizes this particular use case.
Table 4
Type:
New Process
Scope:
Spectrum Management and Network Management
Level:
Operations and Enterprise
Audience:
Primary Actor(s):
Network Management and Spectrum Management Integration
Project Team Members
BSpMS, TacNMS
Supporting Actor(s):
SubNMS
Stakeholder Goals:
Policies Used:





NA
Processes Used:
NA
Pre-Conditions:
Network Operating and Spectrum Allocation as per current Plan
Post-Conditions:
Network Operating and Spectrum Allocation as per Revised Plan
Triggers:
Interference Report
TR170, Version 0.3
Improved business process & benefit to users;
Integrate into existing toolsets;
Use of ADaTP3 and/or SMADEF-XML;
Record work around to help improve planning;
Amount of data to be entered minimized.
© TM Forum 2011
Page 25 of 39
Spectrum and Network Management Use Cases
3.2.
Main Success Scenario
This Scenario describes the steps that are taken from trigger event to goal completion
when everything works without failure. It also describes any required cleanup that is
done after the goal has been reached. The steps are listed below:
Figure 13: Use Case - Interference and Re-Planning
TR170, Version 0.3
© TM Forum 2011
Page 26 of 39
Spectrum and Network Management Use Cases
Table 5
Step
Actor
Action Description
Comment
1
SubNMS
Report Interference
SMADEF-XML = Generate
Interference Report
2
TacNMS
Report Interference
3
BSpMS
Conduct Re-Planning
4
BSpMS
Allot Spectrum
5
TacNMS
Plan Spectrum Re-Use
6
TacNMS
Update Network Plan
7
TacNMS
Disseminate Plan
8
SubNMS
Undertake Radio Fill
9
BSpMS
Update Spectrum Picture
10
BSpMS
Generate Interference
Mitigation Report
TR170, Version 0.3
© TM Forum 2011
Trigger – Interference not
temporary and Re-Planning is
necessary
SMADEF-XML
Page 27 of 39
Spectrum and Network Management Use Cases
3.3.
Scenario Extensions
In some situations, the Interference reported may be minor or known to be short-lived
and Re-planning is considered unnecessary. In such cases, an Interference
Mitigation Report is still raised and the network continues to operate in accordance
with the original Spectrum and Network Plans.
Where it is detected that the interference is due to an illegal Spectrum emission, this
will generate another Use Case to address illegal emissions. This will occur whether
the original Network Plan is followed or whether Re-planning is undertaken.
Table 6
Step
Condition
Action Description
2
2a
Report Interference
Interference is assessed as
minimal or temporary. No RePlanning Required
2
2a
TR170, Version 0.3
To Step 10 - Generate Interference Mitigation Report
Report Interference
Interference caused by illegal
emission originating from:
 Own Nation Spectrum User
 Coalition Force Spectrum
User
 Host Nation Spectrum User
 Unknown Spectrum User
 Hostile Spectrum User
Go to Step 3 or 10 as appropriate and
Go To appropriate Use Case to address illegal
emission.
© TM Forum 2011
Page 28 of 39
Spectrum and Network Management Use Cases
4. Use Case 3 – Dynamic Spectrum Management
Use Case Spectrum 3: Dynamic Spectrum Management
TR170, Version 0.3
© TM Forum 2011
Page 29 of 39
Spectrum and Network Management Use Cases
4.1.
Characteristic Information
Figure 14: Neutral Spectrum Emitter
Dynamic spectrum management involves up-front spectrum planning, and re-planning to
mitigate instances of service degradation, but differs in that it involves sensing the spectrum
activity in theatre and pro-actively changing the spectrum plan to provide the greatest
communications capability.
In order for such a system to operate, the spectrum management tool needs to be provided
with spectrum data from Shared Spectrum Situation Awareness (SSpSA). This should be
available to all systems in the Enterprise.
Figure 14 shows potential interference to both Net 1 and Net 2 from a neutral source reported
from Other Spectrum Systems
A process to raise alerts to a Spectrum Management System when such sources are
discovered, allows pro-active re-planning and re-allotment of spectrum to systems in the
affected Spectrumspace to avoid or mitigate service loss. This avoids the need for spare
spectrum being held in reserve (increasing efficiency) or a loss of data throughput for the
same spectrum usage.
This example includes a higher level planning than that used in the previous Use Case. In
this instance, Tactical Network Planning including Channel allocation is undertaken at a
higher level than the BSpMS, and reflected in the current plan. The process to get to this
point is shown in the Activity Table as a Pre-Condition, to provide background of the start
point of the Use Case.
The following information characterizes this particular use case.
TR170, Version 0.3
© TM Forum 2011
Page 30 of 39
Spectrum and Network Management Use Cases
Table 7
Type:
New Process
Scope:
Spectrum Management and Network Management
Level:
Operations and Enterprise
Audience:
Primary Actor(s):
Network Management and Spectrum Management Integration
Project Team Members
SupSpMS, TacNMS
Supporting Actor(s):
Other Spectrum Systems, Net User.
Stakeholder Goals:
Policies Used:




NA
Processes Used:
NA
Pre-Conditions:
Tac Network Operating as per current Plan.
Post-Conditions:
Tac Network operating as per revised Spectrum and Network Plan
Triggers:
Report of a Unexpected Spectrum User.
TR170, Version 0.3
Pro-active interference mitigation;
Dynamic over-the-air (OTA) re-tuning;
Free Channel Search (FCS);
Exploit Spectrum Situational Awareness
© TM Forum 2011
Page 31 of 39
Spectrum and Network Management Use Cases
4.2.
Main Success Scenario
This Scenario describes the steps that are taken from trigger event to goal completion when
everything works without failure. It also describes any required cleanup that is done after the
goal has been reached. The steps are listed below:
Figure 15:Dynamic Spectrum Management
Table 8
Step
Actor
Action Description
Comment
Pre
Cond
P1
Enterprise Level
TacNMS
Previous Planning provided
Channel Allocation
Request Spectrum Picture
P2
SupSpMS
Provide Current Picture
P3
TacNMS
Plan Network Channels
P4
TacNMS
Export Network Channel Plan
P5
SupSpMS
Assign Tac Network Channels
TR170, Version 0.3
© TM Forum 2011
This assumes that the
Network Channels planned
Page 32 of 39
Spectrum and Network Management Use Cases
(P3) fit with overall Spectrum
Planning, allowing formal
assignment of Channels to
TacNMS.
P6
SupSpMS
Confirm Spectrum Allotment
P7
TacNMS
Disseminate Plan
P8
SubNMS
Do Radio Fill
1
Report Unexpected Spectrum User
2
Other Sp
System
SupSpMS
3
SupSpMS
Allot new Spectrum
4
TacNMS
Revise Network Plan
5
TacNMS
Export Revised Channel Plan
To SupSpMS
6
TacNMS
Disseminate Network Plan
To the SubNMS to implement
7
Detect Tac Network Radio Re-tune
8
Other Sp
System
SupSpMS
9
SupSpMS
Confirm Spectrum Allotments
10
SubNMS
Do Radio Fill
11
SupSpMS
Update Spectrum Picture
12
BSpMS
Generate Interference Mitigation
Report
TR170, Version 0.3
Completion of Higher Level
Planning – Pre-Cond
Initiation of this Use Case
Revise Spectrum Plan
Revise Spectrum (Channel) Plan
© TM Forum 2011
Assumes Revised Plan
submitted by TacNMS is
acceptable. This then
requires the overall Channel
Plan for all Tac Networks to
be revised.
Assumes that revision of
overall Channel Plan reveals
no issues, ie it is successful.
This gives Formal
Confirmation of Spectrum
Allotment to TacNMS.
On final Confirmation Step 9
SMADEF-XML
Page 33 of 39
Spectrum and Network Management Use Cases
4.3.
Scenario Extensions
This is a listing of how each step in the Main Success Scenario can be extended. Another way to
think of this is how can things go wrong. The extensions are followed until either the Main
Success Scenario is rejoined or the Failed End Condition is met. The Step refers to the Branch
Step in the Main Success Scenario and has a letter associated with it. I.E. if Step 3 branches the
Extension Step is 3a.
There are several steps in the Main Success Scenario where things could go wrong and iteration
or further steps may be required before the Main Success Scenario can be re-joined or a failed
end condition is met, possibly initiating another Use Case, Some of the assumptions have been
identified in the Comments column of Table 8.It is not intended to address these at this stage.
This may be appropriate at a later stage of this work.
TR170, Version 0.3
© TM Forum 2011
Page 34 of 39
Spectrum and Network Management Use Cases
5. Open Issues
The following table provides insight to any unresolved problems or questions. These
are the things that seem to apply but could not be fit into these Use Cases on this
pass. The Table also identifies priority areas where further work is required.
Issue ID
1
2
3
4
5
6
7
8
9
TR170, Version 0.3
Issue Description
Terminology and Abbreviations. SMADEF-XML uses SM as Spectrum
Management/Manager abbreviation. SpM has been used in this document to avoid
conflict with other use of SM to mean Service Manager/Management in other areas.
Agreed use of terminology and abbreviations in general requires resolution to avoid
misunderstanding as Project progresses.
Need to gain agreement that Spectrum should be viewed and managed as an
Inventory Resource rather than under Asset Management. Need to determine
whether existing generic Resource attributes are applicable to Spectrum or some
revision is required.
Priority Areas for deeper development of the Use cases and to map to eTOM are:
Planning and Management of Spectrum, Change Management and Trouble
Management
Priority of Effort should be to
(1)
Identify the Spectrum Management process flows and map to the eTOM.
(2)
Flesh out the integration between Spectrum Management processes and
Network Management processes as a second activity
Need to ensure coherence with Use Cases in SMADEF – XML as far as possible,
e.g., consistent use of terms allocation, allotment and assignment according to their
official definitions (explained in SMADEF-XML doc)
Clarify the difference between Spectrum Plans versus Spectrum Allotments, if any Is
the spectrum plan just the collection of all allotments?
Define the role of SSpMS – Why should he approve/confirm new plans? This is not
always the case, if the re-assignment is done within the current allotment the SSpMS
just needs to be informed
The hierarchical relationship between actors/roles needs to be confirmed. In the
military context. This is especial so between Spectrum Management and Network
Management roles, to clearly delineate role responsibilities.
Determine if there are same or similar business process flows for both military and
commercial Spectrum Management and how both relate to the National Regulator.
Note that in some countries, the military is the National Regulator.
© TM Forum 2011
Page 35 of 39
Spectrum and Network Management Use Cases
6. Administrative Appendix
This Appendix provides additional background material about the TM Forum and this
document. In general, sections may be included or omitted as desired, however a
Document History must always be included.
TR170, Version 0.3
© TM Forum 2011
Page 36 of 39
Spectrum and Network Management Use Cases
6.1.
Document History
6.1.1. Version History
Version Number
Date Modified
Modified by:
V0.1
V0.2
04/APR/11
13/JUNE/11
John Lowis (Logica)
Christy Coffey
V0.3
13/JULY/11
John Lowis (Logica)
TR170, Version 0.3
© TM Forum 2011
Description of
changes
First Draft
Comments from
NATO HQ, DISA,
MITRE, Northrop
Grumman, Telcordia,
JHU APL, AlcatelLucent
Addressed all of the
comments from v0.2,
and added to the
document for clarity.
Page 37 of 39
Spectrum and Network Management Use Cases
6.2.
Company Contact Details
Company
TR170, Version 0.3
Team Member
Representative
Logica UK
250 Brook Drive
Reading RG2 6UA
United Kingdom.
John Lowis
Managing Consultant Battlespace Service
Management
[email protected]
+44(0)7968 297 176
TM Forum
Christy Coffey
Gov’t/Defense Market Support Center
[email protected]
© TM Forum 2011
Page 38 of 39
Spectrum and Network Management Use Cases
6.3.
Acknowledgments
This document was prepared by the members of the TM Forum Network
Management and Spectrum Management Integration Project team:
o
John Lowis, Logica, Managing
Management (Technical Lead)
o
David Fritz, MITRE, Principal Communications Engineer, Join Network
Operations and Cyber Defense (Project Lead)
o
Howard McDonald, DoD,
Organization (Project SME)
o
Serge Basso, NATO HQ, Spectrum Management Technical Expert,
Chairman of the SMADEF-XML Configuration Control Board (SME)
o
Gary Coffey, Northrop Grumman, Sr. Communications Engineer/Spectrum
Manager (Project SME)
o
Dr. Ritu Chadha, Telcordia, Executive Director & Telcordia Fellow,
Knowledge-Based Systems Department (Project SME)
o
Xi Jiang, John Hopkins University Applied Physics Lab (Project SME)
o
Mark Cheboldaeff, Alcatel-Lucent, Product and Solution Manager for EMEA
(Project SME)
o
Christy Coffey, TM Forum (Project Champion)
Team
Consultant
Lead-DSA,
Battlespace
Defense
Service
Spectrum
Additional input was provided by the following people:
o
Jason Wiltshire-Brown, Logica UK
i
From AC/322(SC/3)D(2007)0003-Rev7, SMADEF XML 2.0.0. 07 April 2010
2.2.1 Overview
Reference data consists of several types of background information which are used in the various
stages of the normal frequency management process:
 TOA: Definition of a Table of Allocation (see paragraph 2.2.3)
 Application: Definitions of systems used in various frequency bands (used in TOA)
 Codes: Definition of code entries within code list categories which have been designated
as "user
 expandable" (see annex G)
 ChnlPlan: Description of the various channel plans used in TOA
 CoordStd : Description of the various coordination standards used in national and
international coordination
 (used in TOA)
 CurveStd: Description of the various curve standards used in coordination (used in TOA)
 Note: Description of the footnotes used in TOA and Asgn
 Users: Definitions of users using the various frequency bands (used in TOA)
TR170, Version 0.3
© TM Forum 2011
Page 39 of 39