UNCLASSIFIED 1 Presented by: Dr. Richard A. Russel SCNC Chief Architect Northrop Grumman Mission Systems [email protected]ISCN ISCN Top Down and Bottom Up Top Down and Bottom Up Architecture Implementation Architecture Implementation Space Internet Workshop 2004 Space Internet Workshop 2004
21
Embed
UNCLASSIFIED 1 Presented by: Dr. Richard A. Russel SCNC Chief Architect Northrop Grumman Mission Systems [email protected] ISCN Top Down and Bottom.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
UNCLASSIFIED 1
Presented by:Dr. Richard A. RusselSCNC Chief Architect
Space Internet Workshop 2004Space Internet Workshop 2004
UNCLASSIFIED 2
Integrated Satellite Control Network (ISCN) Notional Vision
Establish an interoperable, shared ISCN based on ground elements of current DoD, NASA, NOAA, and other networks augmented by Governm ent
sponsored space-based assets
M D A/TM DM ilitarySatcom
N ationa l
N avigation
Environm enta l
R elay
D edicatedC iv il G N
C ivil D edica tedD epartm ent o f D efense (D oD ) D ed icated M ission C enters
AFS C N Sate llite O perations C enter (SO C s)
D edicatedD oD G N
Shared G round N etw ork (G N ).
See F igure 4 for D eta ils
R &D
Space Based R elay (SBR ),TC S, and TD R SS Technology O ptions
M ulti-band (U SB / SG LS), Phased Array, M ulti-C ontact, Autom ated and R em ote ly C onfigured Antennas, Softw are P rogram m able Transceivers,C entra lized NM S, P riority driven for Scheduling, M onitoring, M anagem ent,and autom ated fault m anagem ent
S030550
UNCLASSIFIED 3
Overview
• ISCN can be developed by a combination of Top-down and Bottom-up architecture development and planning
• Top-Down
• The AFSCN is the first space system that has been fully characterized using the architecture views per the DoD Architecture Framework (DODAF)
• SCNC Architecture Team is developing the ISCN views as part of FY05 task
UNCLASSIFIED 4
Overview
• Bottom-Up
• SCNC has developed an AFSCN Roadmap that characterizes all projects down to requirements, cost and schedule – this is being used for POM inputs by SMC/RN and AFSPC/DR
• The Roadmap will sequence all projects leading to ISCN by a realistic sequencing of projects based on technical and fiscal constraints, and the relationship to current legacy installations
UNCLASSIFIED 5
SCNC Progress to Date – AFSCN DoDAF ProductsTop Down
FY02 ViewsFY03 ViewsFY04 Views
UNCLASSIFIED 6
OV-2 View: AFSCN Operational Node ConnectivityTop Down
UNCLASSIFIED 7
OV-5 View: AFSCN Activity ModelTop Down
UNCLASSIFIED 8
SV-1 View: AFSCN System Interface DescriptionTop Down
UNCLASSIFIED 9
SV-3 View: AFSCN Systems2 MatrixTop Down
Dat
a D
istr
ibut
ion
Sub
syst
em
Mis
sion
Con
trol
C
ompl
ex/S
OC
Tes
t D
river
S
yste
m
OS
R N
etw
ork
Man
ager
WA
NIU
M
ultip
lexe
r
BII
DC
C
OS
R
Ant
enna
S
ubsy
stem
Data Distribution Subsystem X XMission Control Complex/SOC XTest Driver System XOSR Network Manager X X XWANIU Multiplexer XBII X XDCC X XOSR X X X XAntenna SubsystemControl and Status Subsystem X XInteroperability EnhancementsTT&C Subsystem X XPerformance Evaluation (SNAP)ESDOAS XCUE UserNon-CUE User X
CMOC CMOC
Resource Management SegmentSatellite Control Users
Communications Segment
Range Segment
Communications Segment Range Segment
Command and Control Segment
Command and Control Segment
UNCLASSIFIED 10
TV-1/TV-2 Views: AFSCN Combined Top Down
Service Area Service Mandated Standard/ Emerging Standard
Current Standard Near-Term Standard Mid-Term Standard Far-Term Standard
Communication Services
Analog Facsimile Standards
EIA/TIA-465-A , Group 3 Facsimile Apparatus for Document Transmission, Jun 95
Resource Management Segment - OAS: Same as mandated standard
Resource Management Segment - OAS: TBD
Communication Services
Analog Facsimile Standards
EIA/TIA-466-A , Procedures for Document Facsimile Transmission, May 97
Resource Management Segment - OAS: Same as mandated standard
Resource Management Segment - OAS: TBD
Communication Services
Bootstrap Protocol IETF RFC 1542, Clarifications and Exts for the Bootstrap Protocol, 27 Oct 93
Range Segment: Same as mandated standardResource Management Segment - OAS: TBD
Resource Management Segment - OAS: Same as mandated standardResource Management Segment - ESD: TBD
Range Segment: Same as mandated standardResource Management Segment - OAS: Same as mandated standard
Resource Management Segment - OAS: Same as mandated standardResource Management Segment - ESD: TBD
Resource Management Segment - ESD: TBD
UNCLASSIFIED 11
Current Works on DoDAF Products - FY04Top Down
• Maintain “As-is” Architecture– Incorporate any baseline changes– Add new DoDAF Products
• SV-2 System Communication Description• SV-6 System Information Exchange Matrix
• Provide “To-Be” ~2011 Architecture– Uses AFSCN Roadmap as Driver– Uses “As-is” Architecture as starting point– Will show operational, system and technical
architecture changes
UNCLASSIFIED 12
ISCN Roadmap Architecture EvolutionBottom Up
S 030552
User Spacecraft
H um anSpacefligh t
O ther U serC onste lla tions
N ational S cience W eather M ilita ry G P S C onste lla tion
RF Link
DedicatedUser
Assets
Data F low s(e.g. TT&C,
Payload)
U ser C ontro lC enters
(D oD , C iv il,and C om m ercia l
S O C s/M O C s)
WAN
Data F low s(e.g. TT&C,
Payload)
WAN
Contro l andStatus F low s
(e.g. Schedules, Vectors)
RF Link RF Link
Space B ased R e lay
Range Segm entSupport TT&C and
M ission Payload Data
WANContro l andStatus F low
(e.g. Schedules)
A FS C N O C N(S A FB )
A FS C N B C N(O A FS )
Network M anagem ent Segm entEnhance O rbita l Analysis and
Network M anagem ent
Current AFSC N Architecture
• R ange Segm ent: In itia l RTS upgradessta rted ; fu ll upgrade s ta rted .
• N etw ork M anagem ent Segm ent: O ASfo llow -on started
• C om m unications Segm ent: W AN IU sstill in use a t legacy system s; O S com pleteD ISN backbone in p lace.
• U ser Serv ices in S G LS ; enable S O C m igra tion aw ay from C C S.• In teroperability
R
study phase underw ay.
AFSC N RTSAssets
Range Segm ent
WANContro l andStatus F low
(e.g. Schedules)
Network M anagem ent Segm entIncreased Interoperability
AFSCN Space O perationsArchitecture
• R ange Segm ent: RTS upgrades underw ay.• C om m unications Segm ent: Increased capab ility per userrequ irem ents; W A N IU s m ay still be in p lace for legacyS O C s support.
C om m ercia l augm entation .• Support in SG LS and U S B .•
• SB IR S S Q PS K support.• O AS Phase 3 and 4 in progress.• IP N e ts in p rogress.• C C S is decom m issioned, O A S backup in p lace .• ES D 3 .0 com plete .• U pgraded com m unica tions and tim ing.• R B C Transportab le in p lace.• Enhanced capability to hand le peak load ing.• EV C F upgraded.• O ffline testbed and tra in ing .
C iv ilAugm entation
C om m ercia lAugm entation
C iv il C om m erc ia l
NavigationS ignals forTracking
M issionPayload
Data
RF Link
Range Segm ent
Contro l andStatus F low
(e.g. Schedules)
N etw orkM anagem ent S egm entIn te roperab le , R obust,and H igh ly A u tom ated
AFSCN and Partia l ISCNArchitecture
• R ange Segm ent: In te roperab ility across D oD , c iv il, and com m ercia l.
• Space S egm ent: G PS Tracking.• C om m unications Segm ent: C onnectiv ity /peering across D IS N , (G IG ),
N AS A, N O A A, and com m erc ia l netw orks.• C ustom ers/U ser: S ing le , standard based in te rface to S O C s/M O C s.• Phased a rray A C TD .• ISS com plete .• O AS Phase 3 and 4 com p lete .• R em ote opera tions in p lace .• W AN IF in progress, TC S and G IG in te roperab ility.• D LT rep lacem ent com ple te .• N M S w eb enab led and d istribu ted da tabase .
RF Link
ISCN C om pliantA rchitecture
Space Segm ent
AssetsG round Space
Segm ent
AssetsG round
A FS C N O C N(S A FB )
C om m erc ia l C iv il
WAN
Contro l andStatus F low
(e.g. Schedules)
N etw orkM anagem ent S egm entIn te roperab le , R obust,and H igh ly A u tom ated
N S S A O C N(S A FB )
C om m erc ia l C iv il
WAN
Range Segm entSupport TT&C and M ission Payload Data
• R ange Segm ent: In te roperab ility across D oD , c iv il,and com m ercia l. • Space S egm ent: D ep loyed space based re lay, In itia l
• C om m unications Segm ent: C onnectiv ity /peering across D IS N , (G IG ),c iv il, and com m erc ia l netw orks.• W AN IF com plete .
m ulti-contactan tenna capab ility.• N etw ork M anagem ent Segm ent: Federa ted scheduling system .
• Start o f phased a rray:— M ulti-band— S im u ltaneous m ulti-con tact— R adar tracking w h ile com m unicating• R B C com ple te .• Au tom ated scheduling in tegrated w ith rem ote opera tions.
Space-B asedR e lay
Tracking S egm ent
P artia lly D ep loyedSpace R e lay
AFSCN RTSAssets
DLTs U pgradedD LTs
AFSC N RTSAssets
C iv ilAugm entation
C om m ercia lAugm entation
U pgraded D LTs
AFSC N R BCAssets
C iv ilAugm entation
C om m ercia lAugm entation
U pgraded D LTs
A FS C N O C N(S A FB )
A FS C N B C N(O A FS )
C om m unications
Support TT&C and M ission Payload Data
Unattended O perations C apability
UNCLASSIFIED 13
AFSCN RTS Block Upgrade (RBC) Site Ordering Plan Bottom Up
RBC SITE ORDERING CHARTAs of: 21 August 2003
[Replace 46-ft Ant,New Location Low Power HPA Option 3rd Side]
- RFI Monitor (PD-0198, shown)- HPA Dev/Retrofit (PD-0144/0145, shown)- SQPSK Demod for ARTS (PD-0162)- RBC IDF to WANIU Comm (PD-0189/0204)- Video Downlink (PD-0197)
Med. - Integrated DLT Capability in RTS (PD-0195)- CASA (PD-0196)
Low - USB High Power (PD-0194/0199)
Other RBC-Related Projects:1) Offline RBC Simulator/Trainer2) Offline High Fidelity RBC Test Article
Site Order Constraints:1) No Transportable @ Thule due to winds (if no radome)2) 2 CONUS sites before Non-CONUS3) Minimum station downtime4) No GTS construction during typhoon season5) AFSPC/DRNS constraints:- No MUE capability degradation- No 2 sites down simultaneously- Meet SQPSK rqmts (SBIRS/NOPS)1
- No two HP sites down at same time- Maintain range capabilities (RBC vs. ARTS)
Notes:1 - SQPSK rqmts based on site ordering is articulated in SBIRS PRD Rev-A (8/28/01):
a) Test/Early On-Orbit Test: Transportable (e.g., TSTR), NHS, VTS, DGS,TCS, and GTS
b) Operations: DGS, TCS, GTS, CTS, and HTS2 - Additional costs for an RBC transportable pad3- Add capability one per site by 10/1/06 (i.e., FY07 Start)4- Potential radome replacement5 - VTS-A FDE must be completed prior to CTS-A Legacy HPA install (i.e., start ofoperational down-time)6 - VTS-B ARTS Core will be kept at Vandenberg for compatibility testing (using asmall diameter antenna)
[Replace 10m Antenna]
TCS-B Core & Antenna1
Transportable #12
LION-D CommSegment Upgrade
2 Yr Comm RFS
VTS-AHPA
[3600 1st Article HPA(s)3080 Other HPAs]
[Replace 10m Datron Ant, New Location]
CTS-A Core and Ant.1
GTS-B Core and Ant.1
Test Bed
DGS-B Antenna1
[Replace 60-ft Ant, HPUE]
VTS-A Core and Antenna1
TVCF Ant
Transportvia Boat/Aircraft
Transportvia Boat/Aircraft
Thule
Thule Construction(Seasonal)
Typhoon Typhoon Season(Guam)
TestbedHPA
DGS ConstructionPlanning
PlanningWA
PlanningWA
PlanningWA
HTS-A Core and Antenna1
NHS-B Core and Antenna1
Transportable #12
VTS-A Core and Antenna1, 5
HPA Development & Production
TVCF Ant
3400 Funds 3400 Funding Only
HPA Study[PD-0187]
Option
RFI Monitor [PD-0198]
UNCLASSIFIED 14
Roadmap Timeline - Development Project Descriptions (PDs)Bottom Up
Segment Name PD No. WA No. FY02 FY03 FY04 FY05 FY06 FY07 FY08 FY09 FY10 FY11 FY12 FY13 FY14 FY15
Development PDs
ALL Interoperability PD-0037,0211 Effort includes studies, demonstrations, and proof of concept activities
Baseline End-to-End Netw ork Loading Study PD-0003 Study
Obscura Study PD-0205 Study
Automated IRON Database Management PD-0219 Study
CRSS PD-0221
DGS-B and LION-D Impacts PD-0226 Study
Popkin/Rational Integration PD-0227 Study
SA Tool for OCN Coordination PD-0228 Study
Information Assurance PD-0004 Study
I&TSF PD-0043
ISCN Concept Refinement PD-0052 Study
RBC Loading Analysis PD-0053 Study
Next Generation Architecture Optimization F/O PD-0111 Study
NMS NMS Evolution Study PD-0026 Study
OAS F/O Phase 2 PD-0024
OAS Phase 3 PD-0190
OAS Backup PD-0182 Note - DR to define requirement
OAS Training Suite Relocation PD-0223
OAS Phase 4 - Guards PD-0074
ISS PD-0029
NMS Enhancement PD-0191
CS AFSCN Comm Segment Evolution Study PD-0039 Study
RBC Physical Interface IP Connectivity PD-0186
KAFB External Comm Connectivity PD-0020
Determine Bandw idth for RBC PD-0224
Timing Comm Mod Kit Development and Installation PD-0202,0203
VAFB External Users Connectivity PD-0047
TCA/TDRSS Augmentation PD-0057 Study
WANIF PD-0097
Comm S&P Studies - Far Term PD-0105 Study
C&CS SOC Interface Evolution PD-0008
CCS Database Rehost PD-0231 Study
Current POM Cycle
UNCLASSIFIED 15
NMS – Enabler of ISCNBottom Up
• Enterprise “Services” Subsystem (composed of “Services” and “Interface” hosts)
• “Status” Subsystem (all AFSCN status in one place)
• “Remote” Subsystem (extends EMS reach out to the remote sites)
• EMS-capable Workstations (simple browser-capable PCs bring the power of the enterprise solution to all user groups)
UNCLASSIFIED 16
Development of Interoperable Data Transfer Standards Bottom Up
• Prototyping designs for future AFSCN interfaces that enable use of Internet protocols, while maintaining DoD-unique performance requirements
• Verifying emerging international ground segment standards for Air Force operations; providing inputs to evolve these standards
Air Force
NOAA
NASA
packet switched network• Global Information Grid• Internet• leased commercial carrier
international standards
CCSDS SLElega
cy s
eria
l int
erfa
ces
DoD RTS Civil RTS Commercial RTS
Army
Navy
DoD SOC Civil SOC
UNCLASSIFIED 17
ISCN Candidate SitesBottom Up
UNCLASSIFIED 18
Excerpt from Dr. Shiang Liu brief
Phased Array Future Technology Provides Simultaneous Contact CapabilityBottom Up
Site Order Constaints1) No Transportable @ Thule due towinds (if no radome)2) 2 CONUS sites before Non-CONUS3) Minimum station downtime4) No GTS construction duringtyphoon season5) AFSPC/DRNS constraints:- No MUE capability degradation- No 2 sites down simultaneously- Meet SQPSK rqmts (SBIRS/NOPS)1
- No two HP sites down at same time- Maintain range capabilities
• Comm Evolution to IP WAN-based infrastructure• Development of interoperable data transfer
standards• Architecture Sustainment Roadmap
UNCLASSIFIED 21
• Establish ISCN Site Ordering Task Force to prioritize and coordinate integration of antennas and control nodes
• Architect Project Descriptions that implement the interoperability of the antennas with the control nodes based on DoDAF architecture and Roadmap– Implement low hanging fruit
• Submit updated POM/PBC input that accounts for the ISCN plan