705x2b1s - CCSDS

More documents

Recommendations

Info

CCSDS HISTORICAL DOCUMENT2.3.5 RoutePacket ProcessRECOMMENDATION FOR ADVANCED ORBITING SYSTEMSThis process takes relaying information and accordingly generates subnetwork requests, or placesthe packet on the [int] gate, exiting when the relaying information has been exhausted.The process is passed four parameters:LocalTerminationonwardRelayingTablePacketPatha Boolean type which determines whether the packetshould be placed on the [int] gate to be passed out to anapplication by another process.a list of SSNSAP, DSNSAP and SubnetID tuples.the packet to be relayed.the path on which the process is operating.process RoutePacket [int, snw] (LocalTermination : Bool,onwardRelayingTable : RelayingTable,Packet : CCSDSPacket,Path : PathID) : exit :=([LocalTermination] ->(int ! Path ! Packet ;RoutePacket[int, snw] (False, onwardRelayingTable, Packet, Path))[][Not(LocalTermination)] ->([Head(onwardRelayingTable) Ne NULLRelay] ->(snw ! GetSubnetID(Head(onwardRelayingTable))! GetSourceAddress(Head(onwardRelayingTable))! GetDestAddress(Head(onwardRelayingTable))! Packet;RoutePacket [int, snw] (false,Tail(onwardRelayingTable),Packet,Path))[][Head(onwardRelayingTable) Eq NULLRelay] -> exit))endproc RoutePacketendspecCCSDS 705.2-B-1 Page 2-19 May 1994CCSDS HISTORICAL DOCUMENT
CCSDS HISTORICAL DOCUMENT3 PATH SERVICERECOMMENDATION FOR ADVANCED ORBITING SYSTEMSspecification PathService [pkt, oct, man] : noexit3.1 INTRODUCTIONThe LOTOS specification is broken down internally as shown in Figure 3-1, note thatconformance with a LOTOS specification is measured observationally, that is, when viewed as‘black boxes’ any implementation and this specification should respond in the same manner toany stimuli. It is not a requirement that any implementation should explicitly follow the internalbreakdown used here.PathServicePathOriginatorOCTOCTPKTPKTLDPPathTerminatorsOCTLDPPKTOCTLDPPKTTerminationsGeneratorMANNEXTTerminationsListNEXTFigure 3-1: LOTOS Specification Internal BreakdownCCSDS 705.2-B-1 Page 3-1 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 and 10: CCSDS HISTORICAL DOCUMENT1 INTRODUC
Page 11 and 12: 2.1.2 Logical Data PathsCCSDS HISTO
Page 15 and 16: 2.2.2 Relaying TableCCSDS HISTORICA
Page 19 and 20: 2.3 THE BEHAVIOURRECOMMENDATION FOR
Page 27: 2.3.4 TransferOut ProcessRECOMMENDA
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 79 and 80:
Path Protocol Test 10RECOMMENDATION
Page 81 and 82:
RECOMMENDATION FOR ADVANCED ORBITIN
Page 83 and 84:
CCSDS HISTORICAL DOCUMENTRECOMMENDA
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?