SNS Data Structure

1
SNS Data Structure

• Regional Radiocommunication Seminar
• (Porto Seguro, Brazil, 2125 November 2005)

Peter Major, BR/IAP/SAS
2
Introduction

• BR databases
• SNS alphanumeric data
• INGRES used for production in BR
• MS-Access distributed via CD-ROM and BRIFIC
• GIMS graphical data
• SNS version 5
• Appendix 4, Annex 2 used as basis

3
SNS Database versions

• Version 4 used previously
• Was in conformity with Appendix 4 of WRC-2000
• WRC-03 revised Appendix 4 with provisional
  application as of 1.1.04
• Version 5 now in production refer to BR
  circular-letter 211

4
Changes in SNS version 5

• Restructuring of non-geostationary satellite
  orbital data (modified tables)
• More precise specification of commitments and
  compliances with pfd/epfd limits (additional
  data)
• Many additional data items added for beams and
  frequency groups

5
Changes continued

• Additional tables added to improve notice
  processing
• Link API, Coordination Requests (CR) and
  Notifications (N)
• Resolution 49 filing linked with target
• Additional data items added due to changes in
  other parts of RR

6
BR Databases

• The SNS database (Ingres) 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
• Submitted under the advance publication of
  information process
• Filed under Resolution 49

7
BR Databases continued

• The srs.mdb file (MS-Access format on CD-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
• Submitted under the advance publication of
  information process
• Filed under Resolution 49

8
BR Databases continued

• The ificxxxx.mdb file (MS-Access format on BRIFIC
  CD-ROM and ), 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
• The data is published in a fully merged form in
  the database

9
BR Databases continued

• The sps_all_ificxxxx.mdb file (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

10
BR Databases continued

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

11
Space PC-Software Suite
SpaceVal
SpaceQry
Capture
exported ascii text
IFIC
SRS
GIBC
SpaceCap
GIMS
MSPACEg
SPS
SpaceCom
SpacePub
GIMS DB
export GXT
Local DB
IFIC TSUM
12
Space Notified Data
13
Space Notified Data
14
SNS Data Structure

• Three levels
• - Station-and-related-tables
• - Group-table
• - Group-related-tables

15
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

16
Group-related-tables

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

17
Group table

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

18
Attachments

• Graphical data
• 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

19
List of Attachments
20
Action Code

• 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)

21
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 validation will check it

22
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

23
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

24
Mod Notice - Levels

• Notice level tables are notice, geo, non_geo,
  orbit, phase, c_pfd, e_stn, hor_elev
• Antenna / beam level tables are s_beam, e_ant
• Group level tables are grp, assgn, emiss,
  provn, srvcls, gpub_ssn, srv_area, fdg_ref
• Below-group level tables are e_as_stn,
  e_srvcls, s_as_stn

25
Mod Notice Specify whats changed

• Indicate changes by using the Action-Code values
  available at various levels
• 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
• S suppress existing antenna / beam

26
Mod specify changes

• At group level
• A add new group of frequencies 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 provide target group id no.

27
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

28
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

29
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 no. and ngma id no. of the
  target are required for M and S.

30
Conclusion

• 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 completeness and
  correctness.

31
Contact

• Peter Major BR/IAP/SAS
• E-mail peter.major_at_itu.int