1、 NOT MEASUREMENT SENSITIVE MIL-STD-188-220D w/CHANGE 1 23 June 2008 SUPERSEDING MIL-STD-188-220D 29 September 2005 DEPARTMENT OF DEFENSE INTERFACE STANDARD DIGITAL MESSAGE TRANSFER DEVICE SUBSYSTEMS AMSC N/A AREA TCSS DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited P
2、rovided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-188-220D w/ Change 1 ii FOREWORD This military standard (MIL-STD) is approved for use by all Departments and Agencies of the Department of Defense (DoD). It applies to all inter- and intra-Depart
3、ment of Defense (DoD) Digital Message Transfer Devices (DMTDs) and Command, Control, Communications, Computers and Intelligence (C4I) systems that exchange information with DMTDs. This standard contains technical parameters for the data communications protocols that support DMTD interoperability. It
4、 provides mandatory system standards for planning, engineering, procuring, and using DMTDs in tactical digital communications systems. This standard specifies the lower layer (Physical through Intranet) protocol for interoperability of C4I systems over combat net radio (CNR) on the battlefield. This
5、 standard provides the information required to pass digital data via CNR on the battlefield. The Preparing Activity (PA) for this standard is USA CECOM LCMC, ATTN: AMSEL-SE-CD (Chairman, CNRWG), Fort Monmouth, NJ 07703. The custodians for the document are identified in the Defense Standardization Pr
6、ogram, “Standardization Directory (SD1)” under Standardization Area Telecommunications Systems Standards (TCSS). Beneficial comments (recommendations, additions, deletions) and any pertinent data that may be of use in improving this MIL-STD should be addressed to the PA at the above address by lette
7、r. Comments, suggestions, or questions on this document should be addressed to CDR, USA CECOM LCMC, ATTN: AMSEL-SE-CD (Chairman, CNRWG), Building 1209, Fort Monmouth, NJ 07703 or emailed to CNRWGconus.army.mil. Since contact information can change, you may want to verify the currency of this address
8、 information using the ASSIST Online database at http:/assist.daps.dla.mil. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-188-220D w/ Change 1 CONTENTS iii PARAGRAPH PAGE FOREWORD .ii 1 SCOPE .1 1.1 Purpose. .1 1.2 Scope. 1 1.3 Application
9、guidance.1 1.4 Version interoperability.1 1.5 Clarification of examples. .1 2 APPLICABLE DOCUMENTS .2 2.1 General. .2 2.2 Government documents.2 2.2.1 Specifications, standards, and handbooks. 2 2.2.2 Other Government documents, drawings, and publications2 2.3 Non-Government publications. .3 2.3.1 I
10、nternational Organization for Standardization (ISO).3 2.3.2 International Telecommunications Union (ITU).3 2.3.3 Internet Engineering Task Force (IETF) standards.3 2.3.4 Other4 2.4 Order of precedence. .4 3 DEFINITIONS.5 3.1 Definitions of terms.5 3.2 Abbreviations and acronyms.8 4 GENERAL REQUIREME
11、NTS .14 4.1 Digital message transfer device (DTMD). 14 4.2 Interoperability. .14 4.3 Framework.15 4.4 DMTD capabilities16 4.5 System standards and design.17 5 DETAILED REQUIREMENTS18 5.1 Physical layer. .18 5.1.1 Transmission channel interfaces. 18 5.2 Physical-layer protocol18 5.2.1 Physical-layer
12、Protocol Data Unit (PDU). 18 5.2.1.1 Communications security preamble and postamble19 5.2.1.2 Phasing. .19 5.2.1.3 Transmission synchronization field.19 5.2.1.4 Data field. 24 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-188-220D w/ Change
13、 1 CONTENTS iv PARAGRAPH PAGE 5.2.1.5 Bit synchronization field. 25 5.2.2 Network Access Control (NAC) related indications.25 5.2.3 Physical-layer to upper-layer interactions.25 5.3 Data Link layer27 5.3.1 Transmission Header.27 5.3.1.1 Selection bits. 27 5.3.1.2 MIL-STD-188-220 Version. .28 5.3.1.3
14、 Transmission Queue field28 5.3.2 Network access control. 30 5.3.2.1 Scheduler.31 5.3.3 Types of operation.31 5.3.3.1 Type 1 operation31 5.3.3.2 Type 2 operation31 5.3.3.3 Type 3 operation32 5.3.3.4 Type 4 operation32 5.3.3.5 Station class.32 5.3.4 Data Link frame.32 5.3.4.1 Types of frames. 32 5.3.
15、4.2 Data Link frame structure32 5.3.4.3 Data Link PDU construction. 50 5.3.5 Operational parameters51 5.3.5.1 Type 1 operational parameters. .51 5.3.5.2 Type 2 operational parameters. .51 5.3.5.3 Type 3 operational parameters. .53 5.3.5.4 Type 4 operational parameters. .54 5.3.6 Commands and respons
16、es. 54 5.3.6.1 Type 1 operation commands and indications55 5.3.6.2 Type 2 operation commands and responses56 5.3.6.3 Type 3 operation commands and responses62 5.3.6.4 Type 4 operation commands and responses63 5.3.7 Description of procedures by type.65 5.3.7.1 Description of Type 1 procedures. 65 5.3
17、.7.2 Description of Type 2 procedures. 67 5.3.7.3 Description of Type 3 procedures. 77 5.3.7.4 Description of Type 4 procedures. 79 5.3.8 Data Link initialization81 5.3.8.1 List of Data Link parameters.82 5.3.9 Frame transfer85 5.3.9.1 PDU transmission85 5.3.9.2 Data Link concatenation86 5.3.9.3 Phy
18、sical Layer (PL) concatenation. 86 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-188-220D w/ Change 1 CONTENTS v PARAGRAPH PAGE 5.3.9.4 PDU transmissions. .88 5.3.10 Flow control. .88 5.3.10.1 Type 1 flow control. 88 5.3.10.2 Type 2 flow co
19、ntrol. 88 5.3.10.3 Type 3 flow control. 88 5.3.10.4 Type 4 flow control. 88 5.3.11 Acknowledgment and response.89 5.3.11.1 Acknowledgment.89 5.3.11.2 Quiet Mode89 5.3.11.3 Immediate retransmission90 5.3.12 Invalid frame. 90 5.3.13 Retransmission. .90 5.3.14 Error Detection and Correction (EDC). 91 5
20、.3.14.1 Forward-Error-Correction (FEC) coding. .91 5.3.14.2 Forward-Error-Correction preprocessing91 5.3.14.3 Time-Dispersive Coding (TDC)91 5.3.15 Data scrambling.93 5.3.16 Data Link Layer interactions.96 5.4 Network Layer.100 5.4.1 Intranet Protocol100 5.4.1.1 Intranet Header100 5.4.1.2 Topology U
21、pdate.110 5.4.1.3 Topology Update Request message. .113 5.4.1.4 Forwarding of group multicast packets.113 5.4.1.5 Intranet Layer (IL) interactions.116 5.4.2 Subnetwork Dependent Convergence Function (SNDCF). 119 5.4.2.1 Determine Destination function. .120 5.4.2.2 Address Mapping function. .120 5.4.
22、2.3 Type of Service function. 121 5.4.2.4 Intranet send request121 5.4.3 Implementation directions.121 5.5 Lower layer protocol network settings121 5.5.1 Reason for table.121 5.5.2 Table description. 122 5.5.2.1 Table map. .122 5.5.3 Table use123 5.5.4 Changing from OPS parameters123 5.5.5 Custom OP
23、S. .123 5.5.6 Requirements prior to new OPS code insertions.123 5.5.6.1 Values. .125 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-188-220D w/ Change 1 CONTENTS vi PARAGRAPH PAGE 6 NOTES.133 6.1 Subject term (key word) listing.133 6.2 Issue
24、 of the DoD index of specifications and standards133 6.3 Interoperability considerations133 6.3.1 Transmission channel134 6.3.2 Physical interface. .134 6.3.2.1 SINCGARS System Improvement Program (SIP) Receiver/Transmitter (R/T) interface. .134 6.3.2.2 SINCGARS Integrated COMSEC (ICOM) R/T interfac
25、e. .136 6.3.2.3 HAVEQUICK II R/T interface. 137 6.3.2.4 COMSEC interoperability.137 6.3.3 Data Link Layer.138 6.3.3.1 Frequency of Access Ranking (FOAR).138 6.3.3.2 Generation of unique six octet Data Link Layer address for IPv6139 6.3.4 Intranet Layer. .140 6.3.4.1 Allocation of memory required for
26、 reassembly. .142 6.3.4.2 Deallocation of memory used for reassembly.142 6.3.5 CNR Management process using XNP. 142 6.3.6 Interoperation with Internet Protocols.142 6.4 Changes from previous issue.143 APPENDIX A ABBREVIATIONS AND ACRONYMS .144 A.1 General. .144 A.1.1 Scope. 144 APPENDIX B DOD STAND
27、ARDIZED PROFILE IMPLEMENTATION CONFORMANCE STATEMENTS (DSPICS) REQUIREMENTS LIST (DPRL)145 B.1 General. .145 B.1.1 Scope. 146 B.1.2 Application. .146 B.2 Applicable documents. 147 B.3 Notation.147 B.4 Implementation requirements148 B.5 Detailed requirements148 ANNEX A149 A.1 MIL-STD-188-220D Profile
28、 Protocol Stack.149 A.2 Implementation Identification. 149 A.2.1 Protocol Summary.149 A.3 CNR Requirements List. .150 A.3.1 Basic Requirements.150 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-188-220D w/ Change 1 CONTENTS vii PARAGRAPH PAG
29、E A.4 Physical Layer DPRL150 A.4.1 Transmission Channel Interfaces. .150 A.4.2 Physical Layer Protocol.151 A.5 Data Link Layer DPRL. 156 A.5.1 Transmission Header.157 A.5.2 Net Access Control (NAC)159 A.5.3 Types of Procedures. .160 A.5.4 Data Link Frame161 A.5.5 Operational Parameters. 174 A.5.6 Co
30、mmands and Responses. .179 A.5.7 Description of Procedures by Type.193 A.5.8 Data Link Initialization. 224 A.5.9 Frame Transfer. .231 A.5.10 Flow Control233 A.5.11 Acknowledgment and Response. 233 A.5.12 Invalid Frame. .235 A.5.13 Retransmission. .236 A.5.14 Error Detection and Correction. 236 A.5.1
31、5 Data Scrambling239 A.5.16 Data Link Layer Interactions.240 A.6 Network Layer DPRL. 241 A.6.1 Intranet Protocol241 A.6.2 Subnetwork Dependent Convergence Function (SNDCF). 259 A.6.3 Standard network settings. 260 A.7 Appendixes260 A.7.1 This paragraph was intentionally left blank for paragraph conf
32、ormity.261 A.7.2 Network Access Control Algorithm (NAC)261 A.7.3 Communications Security Standards.280 A.7.4 CNR Management Processes using XNP284 A.7.5 Golay Coding Algorithm.306 A.7.6 Packet Construction and Bit Ordering. .307 A.7.7 Intranet Topology Update. 308 A.7.8 Source Directed Relay.309 A.7
33、.9 Robust Communications Protocol.311 A.7.10 Bose-Chaudhuri-Hocquenghem (15, 7) Coding Algorithm321 A.7.11 Transmission Channel Interfaces. .321 APPENDIX C NETWORK ACCESS CONTROL ALGORITHM 327 C.1 General. .327 C.1.1 Scope. 327 C.1.2 Application. .327 Provided by IHSNot for ResaleNo reproduction or
34、networking permitted without license from IHS-,-,-MIL-STD-188-220D w/ Change 1 CONTENTS viii PARAGRAPH PAGE C.2 Applicable documents. 327 C.3 Network Timing Model.327 C.3.1 Network Timing Model definitions.327 C.3.2 Network Timing Model parameters. .328 C.3.2.1 Equipment Preamble Time (EPRE).328 C.3
35、.2.2 Phasing Transmission Time (PHASING). 330 C.3.2.3 Data Transmission Time (DATA).330 C.3.2.4 Coupled Acknowledgment Transmission Time (S). .330 C.3.2.5 Equipment Lag Time (ELAG).331 C.3.2.6 Turnaround Time (TURN). .331 C.3.2.7 DTE ACK Preparation Time (DTEACK). 332 C.3.2.8 DTE Processing Time (DT
36、EPROC)332 C.3.2.9 DTE Turnaround Time (DTETURN)333 C.3.2.10 Tolerance Time (TOL). .333 C.3.2.11 Maximum Transmit Time (MTT). 333 C.4 Network Access Control. 333 C.4.1 Network Busy Sensing function333 C.4.1.1 Data Network Busy Sensing333 C.4.1.2 Voice Network Busy Sensing334 C.4.1.3 Network Busy Dete
37、ct Time.334 C.4.2 Response Hold Delay. .334 C.4.3 Timeout Period335 C.4.4 Network Access Delay (NAD). 337 C.4.4.1 Random - Network Access Delay (R-NAD).339 C.4.4.2 Prioritized - Network Access Delay (P-NAD)339 C.4.4.3 Hybrid - Network Access Delay (H-NAD).339 C.4.4.4 Radio Embedded - Network Access
38、Delay (RE-NAD). .341 C.4.4.5 Deterministic Adaptable Priority - Network Access Delay (DAP-NAD).348 C.4.4.6 Data and Voice - Network Access Delay (DAV-NAD)358 C.4.5 Voice/data network sharing.364 APPENDIX D COMMUNICATIONS SECURITY STANDARDS 366 D.1 General. .366 D.1.1 Scope. 366 D.1.2 Application. .3
39、66 D.1.3 Interoperability. .366 D.2 Applicable Documents. .366 D.3 Definitions.366 D.4 General requirements. .366 D.5 Detailed requirements367 D.5.1 Traditional COMSEC transmission frame. .367 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1
40、88-220D w/ Change 1 CONTENTS ix PARAGRAPH PAGE D.5.1.1 COMSEC preamble field. .367 D.5.1.2 Phasing. .368 D.5.1.3 Transmission synchronization field.369 D.5.1.4 Data field. 369 D.5.1.5 COMSEC postamble field.369 D.5.1.6 COMSEC algorithm. .369 D.5.1.7 COMSEC modes of operation.369 D.5.2 Embedded COMSE
41、C transmission frame.369 D.5.2.1 Phasing. .370 D.5.2.2 Frame Synchronization subfield370 D.5.2.3 Robust Frame Format subfield. .370 D.5.2.4 Message Indicator field. 370 D.5.2.5 Transmission Word Count subfield.370 D.5.2.6 Data Field. .370 D.5.2.7 COMSEC Postamble field.370 D.5.2.8 COMSEC algorithm.
42、.370 D.5.2.9 COMSEC modes of operation.371 APPENDIX E CNR MANAGEMENT PROCESSES USING XNP 372 E.1 General. .372 E.1.1 Scope. 372 E.1.2 Application. .372 E.1.3 Clarification of examples 372 E.2 Applicable documents. 372 E.3 Network configuration. .373 E.3.1 Network Control Station. 373 E.3.1.1 NCS mod
43、e. 373 E.3.2 Dynamic and Static stations. .374 E.3.3 IPv4/v6 address assignment and resolution. .374 E.3.4 Multicast address assignment375 E.4 Exchange Network Parameters (XNP) messages375 E.4.1 XNP message structure. 375 E.4.1.1 Forwarding. .376 E.4.1.2 Message and data block structure377 E.4.2 XNP
44、 message formats. 380 E.4.2.1 Join Request. .380 E.4.2.2 Join Accept382 E.4.2.3 Join Reject. 384 E.4.2.4 Hello message386 E.4.2.5 Goodbye message387 E.4.2.6 Parameter Update Request message387 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-1
45、88-220D w/ Change 1 CONTENTS x PARAGRAPH PAGE E.4.2.7 Parameter Update message388 E.4.2.8 Status Notification message. .390 E.4.2.9 NCS Handover Request.393 E.4.2.10 NCS Handover Accept/Reject.394 E.4.3 XNP data block formats. .394 E.4.3.1 Block 2, Optional Services394 E.4.3.2 Block 3, Basic NAD Con
46、figuration parameters396 E.4.3.3 Block 4, Type 3 parameters.399 E.4.3.4 Block 5, Number of NAD Priorities.399 E.4.3.5 Block 6, H-NAD parameters. 400 E.4.3.6 Block 7, RE-NAD parameters.401 E.4.3.7 Block 8, Wait time.402 E.4.3.8 Block 9, Type 2 parameters.403 E.4.3.9 Block 10, Type 4 parameters.404 E.
47、4.3.10 Block 11, NAD ranking.405 E.4.3.11 Block 12, Intranet parameters. 406 E.4.3.12 Block 13, Error408 E.4.3.13 Block 14, Address designation parameters. 409 E.4.3.14 Block 15, Digital Signature.411 E.4.3.15 Block 16, Link Address Extension411 E.4.3.16 Block 17, XNP Parameters412 E.4.3.17 Block 18
48、, Robust parameters.413 E.4.3.18 Block 19, IPv6 top level/site level address. 414 E.4.3.19 Block 20, Predefined OPS.414 E.4.3.20 Block 21, S/R basic. 416 E.5 XNP message exchange. .417 E.5.1 Data Link addressing.417 E.5.2 Poll/Final bit418 E.5.3 Network Access.418 E.6 Network joining procedures. .41
49、8 E.6.1 Basic joining418 E.6.2 Basic join using unicast addressing.420 E.6.3 Join and election of a NCS421 E.6.4 Basic Leaving422 E.6.5 Leaving without sending Goodbye423 E.7 Example Messages 424 E.7.1 Join Request Message .424 E.7.2 Join Accept message. 426 APPENDIX F GOLAY CODING ALGORITHM 434 F.1 Gene
