ISO 23103:2020 pdf free download – Space link extension一Cross support transfer service一Specification framework.
4.1 OVERVIEW
This section specifies the procedures defined in this Recommended Standard. Subsection 4.2 specifies behaviors that are generally applicable to all procedures. Subsections 4.3 through 4.12 specify common procedures defined in this Recommended Standard.
NOTE — Unless otherwise specified all statements made in this section shall be understood to refer to a single procedure instance only.
4.2 COMMON PROCEI)LRES BEHAVIOR
4.2.1 PROCEDURE INSTANCES CREATION
4.2.1.1 The Association Control procedure shall be instantiated at service instance creation and shall exist for the lifetime of the service instance.
4.2.1.2 All procedures other than the Association Control procedure shall be instantiated as soon as a positive BIND return is issued by the service provider.
4.2.1.3 The service provider shall not accept and process any operations except BIND until it returns a positive BIND return. Exception to that statement is the reception of a PEER-ABORT following the reception of a BIND invocation and preceding the issue of the BIND return.
4.2.2 TERMINATION OF THE ASSOCIATION
4.2.2.1 On reception of an UNBIND invocation, the Association Control procedure shall issue a ‘terminate procedure’ event to all procedure instances of the service instance.
4.2.2.2 On protocol abort (see 1.6.1.6.40) or reception of a PEER-ABORT invocation (see 3.6), the Association Control procedure shall communicate a ‘terminate procedure’ event to all procedure instances of the service instance.
4.2.2.3 If any procedure other than the Association Control procedure initiates an abort, it shall issue a ‘procedure to association abort ‘xxx” event to the Association Control procedure.
4.2.2.4 On reception of the ‘procedure to association abort ‘xxx” event from any other procedure, the Association Control procedure shall abort the association.
4.2.2.5 In aborting the association the Association Control procedure shall invoke the PEER-ABORT operation.
4.2.2.6 When invoking the PEER-ABORT, the Association Control procedure of the service provider shall communicate a ‘terminate procedure’ event to all procedure instances of the service instance.
4.2.3 TERMINATING
4.2.3.1 The Association Control procedure is responsible for sending the ‘terminate procedure’ event to all procedures of the service instance.
4.2.3.2 On reception of a ‘terminate procedure’ event from the Association Control procedure all procedures shall terminate all their activities, shall release their resources and shall cease to exist, unless otherwise specified by the procedures.
NOTE — If a procedure is terminated prior to action completion. the service provider will not report on the result of the on-going operations after re-establishing the association.
4.2.4 PROCEI)URE STATES
4.2.4.1 Once the association is established all stateful procedures shall he in state ‘inactive’.
4.2.4.2 For stateful procedures that have a START and a STOP operation:
a) the transition from ‘inactive’ to ‘active’ occurs after the procedure accepts the START invocation (i.e., when the procedure has sent a positive START return);
b) the transition from ‘active’ to ‘inactive’ occurs after the procedure accepts the STOP invocation (i.e., when the procedure has sent a positive STOP return).
4.2.4.3 For stateful procedures that do not have a START and a STOP operation, the state transition shall be specified by the procedure.
NOTE — Annex G should also be consulted for a description of the service state tables.