BIENNIAL SEMINAR OF THE RADIOCOMMUNICATION BUREAU,

1
Overview of SNS data structureand space
softwareBIENNIAL SEMINAR OF THE
RADIOCOMMUNICATION BUREAU (Geneva, 30 October
- 3 November 2006) Ravindra K.
CHOPRA BR/IAP/SAS
2
Introduction

• BR databases
• SNS (Space Network System) alphanumeric data
• INGRES Relational data base used in-house for
  production in BR, external users access by
  SNS-online
• MS-Access based, distribution of BRIFIC SRS on
  CD/DVD
• GIMS graphical data
• Others IFIC, Reference, SPS, SRS
• Appendix 4, Annex 2, (Tables A,B,C,D) used as
  basis of Data Base design

3
BR databases SNS data structure

• Objectives of SNS Database design
• Up to date information on space networks
• To ensure data completeness, correctness,
  integrity, security
• Efficient data storage, manipulation, retrieval
• Data structures are important SNS data
  structure is based on relational model - data is
  stored in multiple related tables, unique
  identification by use of keys.
• Space Software provides-Queries, reports,
  Updates, processing of space networks data

4
BR databases..

• Evolution of SNS data bases
• Based on Appendix 4, Annex-2, revised at WRCs
  in.1995, 1997, 2000,2003
• Earlier till 1999, Databases on Mainframe Siemens
  for processing, IDMS as DBMS
• Data entry- In house by SPR staff
• Data verification Manual validation
• Output as reports, Diskettes, Micro-fiche
• From 1996 some software for external users

5
BR databasesEvolution

• Data base Versions
• WRC-2000, WRC-2003, additional requirements
• New resolutions, procedures, changes in RRs, RRB
  decisions
• DB and software enhancements made to meet the new
  requirements
• System is stable, Version 5 in use since July 2004

6
Software enhancements / changes, BR information
CRs

• Reference CR/58, CR/65, CR/169 Addendum-1,
  CR/200
• Notification Capture SpaceCap versions 2.5.4, v
  4.0, enhancements announced, SpaceCap version 4.2
  higher, on-line validation
• Validation (SNSVAL) V1.5, Existing Validation
  SNSVAL1 and New SpaceVal under development,
  validation SNSVAL1 version 1.53 dated 18
  September 2002 in use, new SpaceVal version 1.1
  from December 2003

7
Software enhancements / changes, BR information
CRs

• GIMS for capture and validation of graphical data
• SpaceQry version 3.1.2 higher, allows to view
  Val results
• Some Important dates
• As of 01 January 1997 - notification of data in
  electronic format
• As of 3 June 2000, all notice data in
• electronic format
• From 1 December 2003, new SpaceVal version 1.1

8
SNS Database versions

• Version 4 in use - till June 2004
• Was in conformity with Appendix 4 of WRC-2000
• WRC-2003 revised Appendix 4 of Radio Regulations
• SNS data base restructured to Version 5
• All associated software modified accordingly
• Reference BR circular-letter CR/211, dated 10
  May 2004
• Further changes in rules, procedures, RRs
  expected at next WRC in 2007

9
SNS Database/Software versions

• CR/211 of 10 May 2004
• Appendix 4 of RRs revised by WRC-2003
• BR restructured SNS database to version 5.0 (SNS
  5.0) and notification software applications
  (capture, query, publication and validation)
  BRsoft version 5.0
• As of 1 July 2004 version 5.0 to be used
• Circular letters can be viewed at the web site
  at the URLhttp//www.itu.int/md/R00-CR-CIR/en

10
Changes version 4 to 5 contd.

• Details of changes from version 4 to 5
• Can be viewed at the ITUs web site at the URL
• http//www.itu.int/sns/sns_v5_changes.html
• Preface Section III, data items of SRS V5
• Information on changes provided srs_dbv5 on the
  SRS CD/DVD
• Existing Software tools, data structures
  modified, Conversion utilities developed

11
BR Databases

• The SNS database (Ingres) is the Master Data Base
  used in-house and external users use it through
  SNS-on-line.
• contains satellite networks, earth stations,
  Radio-astronomy related info.
• Recorded in the Master International Frequency
  Register (MIFR)
• In process of coordination in accordance with
  Section II of Article 9
• Submitted under the advance publication of
  information process
• Filed under Resolution 49 (Due diligence)

12
BR Databases continued

• The srs.mdb data base (MS-Access format provided
  till recently on CD-ROM)
• CHANGE - From September 2006 on DVD-ROM, provides
  a snapshot taken half-yearly from the BR SNS
  database - contains satellite networks and earth
  stations
• Recorded in the Master International Frequency
  Register (MIFR)
• In process of coordination in accordance with
  Section II of Article 9

13
BR Databases continued

• srs.mdb continued
• Submitted under the advance publication of
  information process
• Filed under Resolution 49 (Due diligence)
• The ificxxxx.mdb file (MS-Access format on BRIFIC
  CD-ROM), is published bi-weekly and contains
  satellite networks and earth stations
• Submitted under No. 11.2 and 11.12 and published
  in Parts 1, 2 3 of the IFIC
• Submitted under No. 9.6 9.7A and published in a
  CR/C or CR/D Special Section
• Submitted under No. 9.2 and published in an API
  Special Section

14
BR Databases continued

• The ificxxxx.mdb
• The data is published in a fully merged form in
  the database
• Ific_no xxxx on CD-ROM with dd.mm.yy printed
• d_ific ific_no
• 03.10.2006 2579
• 17.10.2006 2580
• 31.10.2006 2581

15
BR Databases continued

• The sps_all_ificxxxx.mdb data base (MS-Access
  format on BRIFIC CD-ROM), is published bi-weekly
  and contains satellite networks and earth
  stations
• Data that are in AP30/30A Plans and Lists and
  pending Article 4 cases
• Notified frequency assignments that have been
  recorded in the Plan Master International
  Frequency Register (MIFR)
• That have been submitted under Article 5 of
  Appendices 30 30A
• Can be downloaded from
• http//www.itu.int/ITU-R/space/plans/MIFR/index.h
  tml

16
BR Databases continued

• The GIMS database (MS-Access format), is
  published every 6 months along with SRS on
  CD-ROM, from September 2006 on DVD-ROM. It is
  also published bi-weekly on the BRIFIC CD-ROM as
  incremental update
• Contains graphical data for geostationary
  satellites relating to
• Antenna gain contours
• Service area diagrams
• Gain towards the geostationary orbit

17
Space PC-Software Suite
SpaceVal
SpaceQry
Capture
exported ascii text
IFIC
Reports
SRS
GIBC
SpaceCap
GIMS
MSPACEg
SPS
SpaceCom
SpacePub
GIMS DB
Reports
export GXT
Local DB
IFIC TSUM

18
Space Notified Data
geo
19
Space Notified Data
20
SNS Data Structure

• Three levels
• - Station-and-related-tables
• - Group-table
• - Group-related-tables
• Table and data elements, explanations, flow
  diagrams of SNS data structure can be viewed at
  the ITUs web site at the URL
• http//www.itu.int/sns/srs_dbv5.doc

21
Station-and-related-tables

• Primary key is Notice Id number
• Tables are
• notice, strap, ngma, geo, non_geo, orbit, phase,
  c_pfd, cmr_syst and s_beam for satellite networks
• notice, e_stn, e_ant, hor_elev and e_ant_elev
  for earth stations

22
Group table

• Primary key is Group Id number
• Foreign keys are Notice Id beam_name,
  emission/reception indicator of the owning
  antenna/beam

23
Group-related-tables

• Primary key is Group Id number plus a sequence id
  (and sometimes other data) to provide uniqueness
• Tables are
• assgn, emiss, provn, srv_cls, gpub, srv_area,
  fdg_ref, e_as_stn, e_srvcls and s_as_stn

24
Attachments

• Graphical data-Visual view
• Alphanumeric data (includes epfd mask data)
• Use attch table to indicate how provided
• - attch_type P (paper), E (electronic)
• - file_name attachment file name
• - extension three character file extension
• - text additional information

25
List of Attachments
26
ap4_v5 data base tables
27
Action Code - important

• Indicates how to process the notice
• Add a notice for a new satellite / earth station
• Modify an existing satellite / earth station
• Suppress an existing satellite / earth station
• Must provide value for Action-Code at the notice
  level (in the notice table)

28
Add Notice

• Notify a new satellite network / earth station
• Should contain A in the field act_code in the
  notice table
• Action-Code values in other tables should not be
  provided
• All data as required by Appendix 4 should be
  provided.
• Note Some on line validation is built in
  SpaceCap BUT validation should be run

29
Sup Notice

• Suppress a previously notified satellite network
  / earth station
• Should contain S in field act_code in the
  notice table and notice id number of the target
  in field tgt_ntc_id in the notice table
• Only key data to identify clearly the target
  should be provided, in the notice and geo /
  non_geo / e_stn table no other data should be
  provided

30
Mod Notice

• Modify an existing satellite network / earth
  station
• Should contain M in field act_code in the
  notice table and notice id number of the target
  in field tgt_ntc_id in the notice table
• Can be complex action-codes exist in other
  tables / levels in order to indicate clearly the
  modification desired

31
Mod Notice - Levels

• Notice level tables are notice, geo, strap,
  ngma, non_geo, orbit, phase, c_pfd, e_stn,
  hor_elev
• Antenna / beam level tables are s_beam, e_ant
• Group level and below tables are grp, assgn,
  emiss, provn, srvcls, gpub, srv_area, fdg_ref,
  e_as_stn, e_srvcls, s_as_stn

32
Mod Notice Specify whats changed

• At beam level
• A add a new antenna / beam to existing network
• M modify existing antenna / beam data
• and / or make changes at lower level
• Note Appropriate value for Action-code at levels
  below the beam
• S suppress existing antenna / beam

33
Mod specify changes

• At group level
• A add new group of frequencies and associated
  data to an existing beam
• M modify existing frequency group and / or
  group-related data (below-group level)
• S suppress existing frequency group
• IMPORTANT In case of M or S target group id is
  required

34
Mod specify changes

• Group level continued
• When adding / modifying / suppressing
  frequencies, emissions, coordination data,
  class-of-station / nature-of-service,
  special-section references, service-area
  countries, the entire list must be provided as
  they would look following the modification

35
Mod specify changes

• At level below-group applies to associated
  earth / space stations
• A add associated station to existing frequency
  group
• M modify an existing associated station
• S suppress an existing associated station

36
Mod specify changes

• Strap and noise-gamma (ngma) data
• A add new strap / ngma row to an existing
  satellite network
• M modify existing strap / ngma row
• S suppress existing strap / ngma row
• Important strap id and ngma id of the target
  are required for M and S.

37
Action code
M/S of the notice previously notified
Station
A/M/S Attachments
A/M/S Strapping
M/S Beam previously notified
ADD Beam new
A/M/S Noise gama
ADD Group new
M/S Group previously notified
Groupn
38
Overview of SNS Software

• Used with BR Space service data bases
• Presentations on most of Software will be made
• Workshops to provide hands on experience
• Description and relevant information on software
  installation its use are provided at the URL
• http//www.itu.int/ITU-R/software/space/index.html
  

39
Space Software Main Features

• Distribution of BRsoft every 6 months
• SpaceCap
• SpaceVal
• SpaceQry
• SpacePub
• SpaceRefdb
• GIMS
• GIBC
• MSPACEg
• SNS On-line Available to TIES users or
  Subscribers

40
SPACECAP - Notice Capture

• Appendix 4, Annex-2a and 2b notification,
  notification of assignments to Radio astronomy
  stations
• AP4 GSO or non-GSO satellite system subject to
  coord. under Section II of Article 9
• AP4 GSO or non-GSO satellite system not subject
  to coord. under Section II of Article 9
• BSS networks App. 30 and 30A (WRC-2000)
• FSS networks Appendix 30B (WRC-2000)
• Due diligence information RES 49 (WRC-03)
• Latest version 5.3.6

41
SpaceVal - Space Validation Software

• Validation of notices (satellite networks / earth
  stations)
• Objective is to ensure data correctness and
  completeness
• To ensure validity of SNS data
• Simple field checks, range checks, Cross
  reference checks-across many fields
• Inter-record validation at different levels of
  network like strap validation

42
SpaceVal - Space Validation Software

• Validates electronic notices captured by the BR
  SpaceCap software
• Notices from any other source as long as it is in
  the same format and stored as MS-Access database
  in compliance as used by SpaceCap.
• Val results stored in a table, error messages can
  be viewed printed with SpaceQry
• SpaceCap can be used to correct errors

43
SpaceQry

• Retrieve and view the space notice data
• Access to the SRS data which is supplied on the
  CD-ROM or DVD-ROM (SRS.MDB)
• Update your local SRS data with any IFICxxxx.mdb
  
• Retrieve and view any space IFICxxxx data from
  the BR IFIC CD-ROM Provides access to the related
  graphical data through GIMS
• Many type of queries, options to view, print

44
SPACEPUB - Print Satellite Networks / Earth
Stations

• Utility for printing satellite networks / earth
  stations TSUM from the SRS database
• Creates a MS-Word version 7.0 document in IFIC
  Parts or Special Section format to be printed at
  a local printer
• Associated graphical data (taken from the GIMS
  database) may be included in the document

45
SNS On-line

• SNS Online gives access to the Space Networks
  Systems Database
• Access to the latest up to date information
• Provides for
• Database structure, details
• Query system statistics, graphics, news,
• Submission system
• Reference system
• Demo Pages
• Discussion Fourm
• Web linkhttp//www.itu.int/sns/

46
SpaceRefdb - Space Reference Database Update 

• The SpaceRefdb that will update the reference
  tables used by BR software like SpaceCap,
  SpacePub, SpaceQry, SpaceVal and others
• An up-to-date copy of this reference tables
  database will be provided on each BR IFIC (as of
  BR IFIC 2555/18.10.2005)
• The SpaceRefdb setup will update your local BR
  Soft reference tables database accordingly.

47
GIMS - Graphical Interference management System

• Capture, modify and validate graphical data
  (service areas, antenna gain contours and gain
  towards the gso) relating to the electronic
  notification of satellite networks
• Calculate PFD using graphical data captured via
  this product either by using the digitizer or by
  importing a file in the GXT format.
• Export captured diagrams in GXT format for
  electronic notification.

48
GIBC - Graphical Interface for Batch Calculations

• Technical Examinations on satellite networks for
• Power Flux Density (PFD) examinations with
  respect to
• PFD limits in Article 21
• PFD limits in Appendix 30
• Appendix 8
• Determines coordination requirements

49
Space Plans System software

• Technical Examinations for the Geostationary
  Networks of the Space Plans in Appendices 30, 30A
  and 30B
• Mspaceg
• Technical Examination software
• SPS_Report
• SPS Reporting Tool
• SPS Utilities
• Tools for updating the reference situation and
  storing results

50
Future?

• Presently SNS DB contains AP4 data of almost
  10500 geo satellite filings, 1100 n-geo and 8000
  earth station
• Further developments at WRC and advances in
  technology ?
• WRC 2007 would lead to version 6.
• Change of requirements, new procedures and
  regulations
• Your feedback and comments would help BR to
  improve its services and the software

51
Conclusion

• SNS data base its data Structures, notice
  exploration and submission are important
• Usage of BR Software SpaceCap, SpaceVal,
  SpaceQry, SpacePub, SNS-Online, GIMS and other
  software tools would be useful
• Best way to create electronic notice is to use
  BRs SpaceCap software
• MS-Access database can be loaded from other
  sources but the coherence and integrity of the
  data should be ensured
• BRs space validation software should be run on
  the notice to check its validity and correctness.
• Regular reference to BR web site for latest
  Updates and versions

52
Questions and comments

• Contact
• Ravindra K. CHOPRA
• BR/IAP/SAS
• E-mail ravindra.chopra_at_itu.int
• Telephone [phone]