nato unclassified - Ham-pages ... No indexes at this level

More documents

Recommendations

Info

NATO UNCLASSIFIED STANAG 5066: PROFILE FOR MARITIME HF DATA COMMUNICATION V1.0.2 The Radio Equipment Sublayer comprises the equipment required to establish a radio link between two or more nodes, i.e. transmitters, receivers, transceivers, antennas, etc. This sublayer is not defined in this document. A NATO STANAG (STANAG 4203) exists which specifies minimum standards for transmitters and receivers. The Subnet Management Sublayer is shown in Figure 1 as a vertical column with interfaces to each sublayer. The main subnet management function, in the context of this STANAG, is automatic link maintenance (ALM) in the form of adaptive control of the HF modem. The management sublayer messages and associated procedures which are required for ALM are defined in Annex C of this document, in the context of the MANAGEMENT D_PDU. The other functions of the Subnet Management Sublayer, which may be critically important to a successful implementation, need not be standardized for interoperability and are not addressed further in this document. AdditionalList of Annexes Annex A: Subnetwork Interface Sublayer (mandatory) Annex B: Channel Access Sublayer (mandatory) Annex C: Data Transfer Sublayer (mandatory) Annex D: Interface between Data Transfer Sublayer and Communications Equipment (mandatory) Annex E: HF Modem Remote Control Interface (information only) Annex F: Subnetwork Client Definitions (information only) Annex G: Waveforms for Data Rates Above 2400 BPS (information only) Annex H: Implementation Guide and Notes (information only) Annex I: Messages and Procedures for Frequency Change (information only) Annex G provides a definition of waveforms which will provide data rates above 2400 bps. The mandatory annexes are written to support data rates up to 9600 bps, however no standards currently exist for HF modems at these data rates. Annex H provides implementation guidance and notes. References 1. Clark, D., and N. Karavassillis, “Open Systems for Radio Communications: A Subnet Architecture for Data Transmission over HF Radio”, TM-94037 (in preparation) 2. Miller, T., and P. Reynolds, “Experience with Approved Cryptographic Equipment in HF ARQ Systems”, NC3A TN 638, NATO CONFIDENTIAL, November 1996 NATO UNCLASSIFIED 8
NATO UNCLASSIFIED STANAG 5066: PROFILE FOR MARITIME HF DATA COMMUNICATION V1.0.2 Annex A: Subnetwork Interface Sublayer (mandatory) This annex defines the interface between the users of the HF subnetwork and the node through which the user accesses the subnetwork. A.1 Subnetwork Service Definition The interaction between the HF subnetwork and the users of the subnetwork are governed by a Client-Server relation. The users (clients) request the services provided by the HF subnetwork (server). The service provided by the server is application independent and common to all clients irrespective of the task they may perform. Clients are attached to the Subnetwork Interface Sublayer at Subnetwork Access Points (SAPs). There can be multiple clients simultaneously attached to the Subnetwork Interface Sublayer. Each SAP is identified by its SAP Identifier (SAP ID). 2 The SAP ID is a number in the range 0-15; hence there can be a maximum of 16 clients attached to the Subnetwork Interface Sublayer of a single node. Annex F contains a recommended definition of the various subnetwork clients. For the purposes of this STANAG, the subnetwork client definitions in Annex F are not mandatory. Data submitted by the clients to the Subnetwork Interface Sublayer must be in the form of primitives with the format as described in this document. Clients are responsible for segmenting larger messages into U_PDUs. A U_PDU format which supports this segmentation is defined in Annex F. The Subnetwork Interface Sublayer treats all clients connected to it in the same manner irrespective of the application performed by these clients. The only distinguishing factor between clients is their Rank which is a measure of their importance. See Annex H.5 for further information on the rank of clients. Certain service requests made by higher ranked clients may take precedence over requests made by lower ranked clients. A.1.1 Initiating Data Exchange Sessions The Subnetwork Interface Sublayer is responsible for initiating the establishment and termination of Sessions with its peers at remote nodes. There are four types of sessions: 1. Soft Link Data Exchange Session 2. Hard Link Data Exchange Session 3. Broadcast Data Exchange Session 4. Reserved All sessions apart form the broadcast data exchange session require the making of a point-topoint physical link with a specified remote node. A.1.1.1 Soft Link Data Exchange Session 2 SAPs are equivalent to the “ports” of the TCP protocol. NATO UNCLASSIFIED 1
Page 1 and 2: NATO UNCLASSIFIED NATO Standardizat
Page 3 and 4: NATO UNCLASSIFIED STANAG 5066: PROF
Page 7: NATO UNCLASSIFIED STANAG 5066: PROF
Page 59 and 60:
NATO UNCLASSIFIED STANAG 5066: PROF
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
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:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155:
show all

nato unclassified - Ham-pages ... No indexes at this level

Create successful ePaper yourself

Delete template?

Save as template?