This preview shows page 1. Sign up to view the full content.
Unformatted text preview: Transfer FDU’ or a ‘Reject Response to Request to Transfer FDU’
referring to the Request. With this transfer notification signal, FOP-1 signals its acceptance
or rejection of the Request.
As long as the sending-end Lower Procedures are capable of accepting the Type-BD Transfer
Frame, it shall be accepted from the Higher Procedures and transmitted. If the Lower
Procedures cannot accept the Type-BD Transfer Frame, it shall be rejected; there is no
Wait_Queue for Type-BD Transfer Frames.
As no error recovery is performed by COP-1 for a Type-BD Transfer Frame, a copy of the
data is not kept by FOP-1 and no confirmation of acceptance of the Transfer Frame by the
receiving end is signaled.
Once an ‘Accept Response to Request to Transfer FDU’ or a ‘Reject Response to Request to
Transfer FDU’ is returned, no further action is taken by FOP-1 for the corresponding
Request. CCSDS 232.1-B-2 Page 4-9 September 2010 RECOMMENDED STANDARD FOR COMMUNICATIONS OPERATION PROCEDURE-1 5 FOP-1 5.1 FOP-1 VARIABLES 5.1.1 GENERAL This section describes the variables used by the FOP-1 state machine. The complete
meaning of these variables can only be fully understood in conjunction with a careful reading
of the FOP-1 State Tables contained in section 5.3. It is these tables and the associated
actions defined in 5.2 which, ultimately, contain the master definition of FOP-1.
The variables defined in this section are part of the definition of FOP-1. Any implementation
of FOP-1 is likely to have additional private, implementation-dependent variables.
FOP-1 maintains the following variables for each Virtual Channel:
b) Transmitter_Frame_Sequence_Number (usually referred to as ‘V(S)’);
i) Expected_Acknowledgement_Frame_Sequence_Number (usually referred to as
j) Timer_Initial_Value (also known as ‘T1_Initial’);
m) FOP_Sliding_Window_Width (also known as ‘K’);
View Full Document
This document was uploaded on 03/06/2014.
- Spring '14