705x2b1s - CCSDS

More documents

Recommendations

Info

CCSDS HISTORICAL DOCUMENT2 PATH PROTOCOLRECOMMENDATION FOR ADVANCED ORBITING SYSTEMSspecification PathProtocol [pkt, oct, man, snw](packetType : PacketType,dataLossFlag : Bool) : noexit2.1 INTRODUCTIONThe CCSDS Path service provides an optimised connectionless data transfer service between asingle source user application and one or more destination applications.2.1.1 Path ArchitectureThe architecture of the CCSDS Path service with respect to other elements of the CCSDSarchitecture is given in Figure 2-1. The internal architecture of the Path service used in thisspecification is given in Figure 2-3.APPLICATIONAPPLICATIONCCSDSPATHLAYERMANAGEMENTANDSIGNALLINGMANAGEMENTANDSIGNALLINGCCSDSPATHLAYERLOCALSUBNETWORKLOCALSUBNETWORKINTERVENINGSUBNETWORKSFigure 2-1: Path Service ArchitectureNote that this diagram is a very simplistic representation of the Path service architecture, it does,however, provide a useful overview of the CCSDS system. Applications communicate overLogical Data Paths (see section 1.2) provided by the Path service, each application may usemany Logical Data Paths, but each Path may be used by only one source application.CCSDS 705.2-B-1 Page 2-1 May 1994CCSDS HISTORICAL DOCUMENT
2.1.2 Logical Data PathsCCSDS HISTORICAL DOCUMENTRECOMMENDATION FOR ADVANCED ORBITING SYSTEMSThe Logical Data Path is the backbone of the path service, it is a single start point,single/multiple endpoint route which transports CCSDS packets unreliably between applications.Logical Data Paths are referenced by Path IDs; each Path ID is constructed from an ApplicationID and an optional Application ID Qualifier. Application IDs are 11-bit identifiers which arepassed to the Path service by applications wishing to transfer data. Because of the internationalnature of the CCSDS Recommendations, it was felt that 2048 Logical Data Paths would beinsufficient, and therefore the concept of an Application ID (APID) Qualifier was introduced;Path naming domains (typically a spacecraft) can therefore be defined which have access to all2048 Application IDs, and the Path IDs are formed and kept unique by the addition of the APIDQualifier. The qualifier is represented by addressing mechanisms local to each subnet (thespacecraft ID in the SLS). The APID Qualifier is an optional part of the Path Identifier; if theQualifier is not to be used, then the value “NullAPIDQual” should be applied.As is shown in Figure 2-2, Path IDs have a Service Access Point (SAP) like quality; each Pathmay be used by only one application, but each application may use many Paths (by passing adifferent Application Process ID in each case), thus applications may have a range of endapplications (or sets of end applications) to communicate with.APPLICATIONAPPLICATIONAPPLICATIONAPPLICATIONAPPLICATIONS S S1 2 3 4 5 6 7A B CFigure 2-2: Path ID CharacteristicsThere are several points worth noting in the above diagram:Three Paths are shown; the start points are labelled with a lower case ‘s’. The first Path runsfrom the SAP labelled 2 on node A to the SAP labelled 3 on node B. The second Path runsfrom the SAP labelled 5 on node B to the SAP labelled 6 on node C. The final Path runsfrom SAP 7 on node C to SAP 1 on node A, and SAP 4 on node B.The SAP numbers are a convenience; they bear no resemblance to ‘real’ SAP numbers whichwould effectively be derived from the PathID.Path entity A does not ‘know’ where the first Path ends, only that Path entity B is the next‘step’ in the Path; the Path is effectively re-evaluated at each step, B’s ‘idea’ of the first Pathis completely different to A’s.CCSDS 705.2-B-1 Page 2-2 May 1994CCSDS HISTORICAL DOCUMENT
Page 1 and 2: CCSDS HISTORICAL DOCUMENTConsultati
Page 3 and 4: CCSDS HISTORICAL DOCUMENTRECOMMENDA
Page 5 and 6: RECOMMENDATION FOR ADVANCED ORBITIN
Page 9: CCSDS HISTORICAL DOCUMENT1 INTRODUC
Page 15 and 16: 2.2.2 Relaying TableCCSDS HISTORICA
Page 19 and 20: 2.3 THE BEHAVIOURRECOMMENDATION FOR
Page 27 and 28: 2.3.4 TransferOut ProcessRECOMMENDA
Page 29 and 30: CCSDS HISTORICAL DOCUMENT3 PATH SER
Page 31 and 32: 3.2.2 Packet QueueCCSDS HISTORICAL
Page 41 and 42: Path Protocol Test 1RECOMMENDATION
Page 43 and 44: Path Protocol Test 1aRECOMMENDATION
Page 45 and 46: Path Protocol Test 2RECOMMENDATION
Page 47 and 48: Path Protocol Test3RECOMMENDATION F
Page 61 and 62:
RECOMMENDATION FOR ADVANCED ORBITIN
Page 63 and 64:
Page 65 and 66:
CCSDS HISTORICAL DOCUMENTRECOMMENDA
Page 67 and 68:
Page 69 and 70:
Path Protocol Test7RECOMMENDATION F
Page 71 and 72:
Page 73 and 74:
Path Protocol Test8RECOMMENDATION F
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Path Protocol Test 10RECOMMENDATION
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Path Service Test 1RECOMMENDATION F
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Path Service Test 3aRECOMMENDATION
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Path Service Test 5aRECOMMENDATION
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
show all

705x2b1s - CCSDS

Create successful ePaper yourself

Delete template?

Save as template?