Electronic Notifications and the SNS database

1
Electronic Notifications andthe SNS database

• Nangapuram Venkatesh
• Radiocommunication Bureau

2
How to notify electronically

• In Microsoft Access (MS-Access) version 97
  database
• Appendix S4, Annex 2A used as basis
• Design takes notice form into account
• Database container provided

3
Database Design

• MS-Access is a relational database
• Relational theory used to model data
• Entity-relationship diagram provided

4
Relational Theory

• Relational model of E. F. Codd (1969)
• Relational database design
• Tables, uniqueness, keys
• Relationships
• Normalization
• Integrity rules

5
Space Notified Data
6
Space Notified Data
7
SNS Data Structure

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

8
Station-and-related-tables

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

9
Group table

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

10
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, srvcls, gpub_ssn,
  srv_area, e_as_stn, e_srvcls and s_as_stn

11
Attachments

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

12
List of Attachments
13
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)

14
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 S4 should be
  provided validation will check it

15
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

16
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

17
Mod Notice - Levels

• Notice level tables are notice, geo, non_geo,
  orbit, phase, 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
• Below-group level tables are e_as_stn,
  e_srvcls, s_as_stn

18
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

19
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.

20
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

21
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

22
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.

23
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.