SANA Activities Update

Marc Blanchet, Audric Schiltknecht

Viagénie

CCSDS London

2014-11-19

Marc.Blanchet@viagenie.ca

audric.schiltknecht@viagenie.ca

http://www.viagenie.ca

SpacecraftID Registry

Assignment Request FormProcess

Requests are handled by a web request form and its processing engine

Request by the Agency Representative:

Request by the End-User:

Cleanup

Finished. New DB in production. Duplicate assignments found during the process:

Contacted agencies to check status/confirm information of those GSCID:

Replies from CNES, NSPO Waiting for replies from NASA, ESA notification is being resent

summary: out of the 9 IDs (18 spacecrafts), 3 IDs (which means 6 spacecrafts) are remaining as unknown conflict:

10D4: NASA-GALEX, ESA INTELSAT-K-TV 10A5: NASA-LRO, NASA MAP 10F7: ESA-SYRACUSE-3B, NSPO ROCSAT-2

Possible Conflicts

0D4: GALEX was initially assigned « other » GSCIDs but NASA requested D4 for it and it was assigned although already used by INTELSAT-K-TV. There are differences in the frequencies used. No mention whether the projects were notified or not.

0A5: There are only a few MHz difference in the frequencies used. The projects had already been informed by the previous SCID registry maintainer.

0F7: There are differences in the frequencies used. The projects had already been informed by the previous SCID registry maintainer.

Spacecraftid Assignments Assigned Ids since 6 months:

25 V1, 29 V2, 2 V3 Current state of the registry (unassigned, returned):

V1 (1024 total): (22%+5%)= 27% can be assigned (if no returns).

current assignment rate ~ 4%/year at this rate (with no returns): full in 6 years

V2 (256 total): (5%+8%)=13% can be assigned (if no returns)

current assignment rate ~ 20%/year at this rate (with no returns): full in 6 months

V3 (1024 total): (98%) can be assigned current assignment rate ~ 0,2%/year

Considerations

Sometimes, assignment requests come for a block of IDs, so rate can be higher in a short period

Assess the risk More aggressive V2 relinguishing from agencies? Recommend not using V2 unless very required? Recommend using a new version of the frame

protocol (in development)?

Other Activities (not Spacecraftid related)

Ticket system Creation of IOAG communication assets registry

from excel document, with authentication system for read/write, using email as credentials

Creation of DAI XML, CSTS Functional Resources Registries

Updated Registries: Glossary, CBHE, CBHE Node allocation, LTP, NDMXML, Protocol ID, Packet Version Number, Agency Representatives, CAO updates

Add a dynamic tree view for OID registry. Creation of RNG schemas for some registries

(Agencies, CAO/CAO contacts, OID, Terms).

Done during the period

Upcoming Work

IOAG communication assets normalization IOAG optical assets registry creation (separate from

communication assets registry) Finer improvements on spacecraftid work flow combining various contact registries into a single and

coherent registries RESTful API (programmatic interface) in production mode,

announce availability and provide access info Web site Explore how to best support ontology / OWL registries (SOIS

and other) Assist CCSDS working groups to

create/modify/enhanceregistries

Backup

Spacecraftid Assignments SCID Version 1 Not assigned: 229 (22%)

white Returned: 61 (5%)

blue Assigned: 729 (71%)

green Strange: 5 (0%)

red

Spacecraftid Assignments SCID Version 2 Not assigned: 15 (5%)

white Returned: 23 (8%)

blue Assigned: 217 (84%)

green Strange: 1

red

Spacecraftid Assignments SCID Version 3 Not assigned: 1009 (98%)

white Returned: 2 (0%)

blue Assigned: 13 (1%)

green Strange: 0

red