\
`\
`
`. -'.
`
`,f..
`
`_ .....
`
`-'
`
`?
`
`---.-
`
`. "'; . .,
`
`"
`
`"\':-AA'NC:'~~:~'--~-
`
`"'
`
`~
`. . - t '\'
`
`,
`
`I
`
`......
`
`.J
`
`.......
`
`\
`.-:
`
`'.'
`
`,I
`
`- .-'
`
`, / ,.
`
`~
`\~,r
`
`"'-
`
`, ,
`....
`
`"
`
`'"
`
`i::
`-.....
`~.~. ,. -' ,
`
`i,
`\
`
`/
`
`,-
`,.
`
`...
`
`t
`
`(
`
`,
`
`;: .. :
`
`:
`
`'.
`
`'
`
`\
`
`. -
`
`r
`
`./
`
`" .I
`
`.... -
`
`,"
`
`~ .. \' / -..-
`
`"
`
`'.
`
`'j
`
`"
`
`\,
`
`'...:
`
`--\
`
`, .....
`
`.....~,' -.,1
`
`/
`
`.,'
`
`_. '\
`
`...
`
`II
`
`I.
`
`'.7-
`'.
`
`';'
`
`-".::;::~
`
`/
`-..... : '-
`
`(
`
`I
`
`'1 .~
`
`I
`
`.
`...
`
`. -'~.'
`
`/' _ ......
`
`.... -
`
`v-
`
`!
`
`\
`
`.~
`
`\-
`
`... ., ,
`
`'7
`I
`
`,
`
`, /
`
`'1
`
`/
`
`"
`oS .
`
`/
`
`. .,.
`
`''''''
`
`'':
`
`'.
`
`-.J!"
`
`\
`
`,-
`I'"
`
`~ ..
`
`,'-
`
`,-.~
`
`".,_
`
`I-:....~
`
`\: .... ,
`~ .:.\"'
`
`.....
`
`-
`\ I .... ~· ......
`
`/"
`
`" I
`
`/'
`l ' .
`
`,' ..
`
`I
`
`./
`
`,'.....
`
`,'"
`
`' ....
`
`- . . . , " \
`
`\
`
`/
`
`.. "
`
`r'-
`
`"';
`
`" 1
`
`.:.:-
`
`"J ...
`
`.,
`
`.-4,!RI.GFtQIJ'N[) Cfi~R~:CT~~.~.-~qRI~I\!T~tl ~F ....
`';1 ',:-.'" ~ ~ ~,P~RO_T,OCO'~.:·_SP.E'C·I'FI·CA-TIQ'I~iF
`-... \
`, , .. ' ,
`"'--~,.., /
`-'
`- ( "" I •
`. /
`
`~'
`
`J
`
`I
`
`: ,
`
`'\
`
`....
`
`.......
`
`......
`
`"','
`
`-.. /
`
`-4.
`
`"
`
`....
`
`"
`
`"
`
`,
`
`/
`
`,.
`
`/
`
`)
`",
`
`..... -
`
`.... /
`
`/.
`
`'1-\ "
`
`",
`
`/
`
`\
`
`-\
`
`/
`
`.::;, L;. \. _.:z
`
`/
`
`\ '"
`
`"
`
`/
`
`,
`
`I
`
`,
`
`--/:
`
`-,r . .. ",
`
`'.
`"
`
`,', .
`
`j""
`
`;:/
`
`,/
`
`"
`
`.... '- - '-, ~'.
`
`.1
`
`>,.
`
`I
`I
`
`,
`
`'"
`\ -.
`
`!
`,,\--
`
`..(\
`
`.'
`
`, ~.
`
`'/
`
`"
`
`'\
`
`- \.
`
`I
`\"
`
`/ "
`.... ,.
`J ,-
`.~ ..
`
`'
`
`\
`
`/
`
`\.
`
`.,. ,',
`.
`-
`I
`,"'AN -AAINC-l)OCUMENT-
`._
`.f:."""
`\
`Prepared bY_
`""
`....] ~ .... : '"
`.' ,
`~
`AIRLII\I,ESELECTRO~C,EN'!lNEERING COMMI'IT~E
`~ ' . '
`~ "
`PUb)iahed'b}l
`"; ... :' ..
`-AERONAUTICAL RA~I\>,'iNc:. . ----
`~5S1 RIVA ROAD, ~1Ilt.JAP~S. MARYLANE 214111: .
`.
`/ .
`
`•
`
`,
`
`\
`
`\,
`
`\
`
`., ....
`
`"
`
`...,: ... )-!,
`
`'(- .
`
`y
`
`" -t
`
`, \
`
`, \
`
`'.
`
`,',
`
`~ r-'
`
`.~
`
`..... :.
`
`-' -,'
`
`.J
`
`/ --
`-
`./ ~-.....
`
`"
`
`\. /' ";:-
`
`"-
`, '. -
`
`:
`
`"'-:-.-
`
`....
`
`" ,
`
`\
`) '-
`" l~
`
`'.
`
`) /
`i
`
`,
`
`'(:
`
`.. ~
`',.
`
`'-
`
`, /.
`
`\
`
`....
`
`.
`
`/
`.... '.
`,\
`J
`,"
`f, ___
`"..
`Order Number: 02.046312
`-
`So'd 'o:MUNGER tOLLES!>. OLSON (5345761, A'GNES.VILLERO@MTO.COM;
`.-
`Nat for Resale,2015-02-.,?3 19:39:20 ld.."IC
`
`Copydght ARINC l~duSlry Activities
`..
`Provided by IHS under license with ARINC
`No teproduclio~r-networkil)gp~ilted vrilhout Ucense'lrom IHS
`..
`\
`'.
`
`\
`
`"
`
`. ,).
`....
`
`,
`....
`
`'j
`
`""'r
`.1
`
`BOEING
`Ex. 1020
`
`

`

`'~'.
`
`, .
`
`::.
`
`\ '.,
`
`,. / ' .
`
`i -
`
`I
`
`':.
`
`'"
`
`'\.
`
`.. '
`
`...... ' ......
`
`.". .... '
`
`/
`
`-t
`
`/".. ..
`
`. (
`
`'--'" \.--
`
`/: ..
`
`,/
`
`)
`
`'> •••••
`
`,'"
`
`-'
`
`, .
`
`/
`".
`
`" "
`
`.. ~ ..
`
`t' ~,. '.
`
`-,' .
`
`....
`
`I
`
`.
`
`.
`
`....
`
`.' I .
`
`:
`
`ThiS: docUment is based.: on, milterial,'~subinitted: by variotis···
`participants.during the;' drafting process.! NeIther ABBe nor
`" -¥tINe 1Jas made any deterniinatioIfFhether these Jl]lltetjws could·'
`. besubj~t to claims .. Qf. patent or other proprietary rig4ts by third
`. parti~, an? norepresentatioh,o~.w~:ty, e?tpr~ss or impli~~jS'
`lflade-m,:thisreg~~: Any use of or ~b:mpe()n this' doc!lnlent sh~l , /
`constitute '~ 'acceptance ,hereOf ,:''.;is l~tI and be subject to this: ... ·
`• disclaimet:·:i· .
`"
`"
`.
`, "
`.
`
`.
`
`. ',
`
`',j .
`
`,.
`
`".
`
`. '
`
`..........
`
`.'
`
`'- .....
`
`"'.
`
`"'~
`
`/.,
`
`'-
`
`. ...
`
`."':;
`
`....
`
`;=-
`
`.,.. ...
`
`..... :
`
`..'
`·t; .....
`
`"
`
`.> ..
`
`:.-
`
`. "
`
`i"
`
`.•..
`
`','
`
`. '.~
`
`'.~. -'
`
`" - " "
`
`Copyright ARmc Indus!ry Activities
`Provided by IHS under1icense with ARINC
`No reproduction or networking permitted wilhoullicens.e from lHS
`
`.
`Order Number: 02046312
`Sold io:MUNG.ER TOLLES' & OLSON [5345761, AGNES.VILLERO@MTO.COM.
`Not for Resale.20.15-02-23 19:39:20 UTC
`
`BOEING
`Ex. 1020
`
`

`

`/
`
`u.~
`
`REVISED: December 30,1994
`
`r
`
`Copyright@1994by
`AERONAUTICAL RADIO, INC.
`2551 Riva Road
`Annapolis, Matyland 21401-7465 USA
`
`ARINC SPECIFICATION 618-1@
`
`AIRlGROUND CHARACTER-ORIENTED PROTOCOL SPECIFICATION
`
`Published: December 30, 1994
`
`Prepared by the Airlines Electronic Engineering Committee
`
`o \;
`
`J
`
`Specification 618
`
`Adopted by the Airlines Electronic Engineering Committee: November 4, 1992
`
`Specification 618
`
`Adopted by the Industry: JanUaty 15, 1993
`
`Specification 618-1
`Copyright ARINC IndustrY Activities
`Provided by IHS under license with ARINC,
`No reproduction or networking permitted without license from IHS
`
`AdOpted by the Airlines Electronic Engineering Committee: October 19, 1994
`Order Number: 02046312
`Sold lo:MUNGER TOLLES & OLSON 15345761- AGNES.VILLERO@MTO.COM.
`Not for Resale.201S-02-23 19:39:20 UTe
`
`b
`
`!--
`
`BOEING
`Ex. 1020
`
`

`

`FOREWORD
`
`Activities of AERONAUTICAL RADIO, INC. (ARINC)
`
`and the
`
`Putpose of ARINC Reports and Specifications
`
`Aeronautical Radio, Inc. is a cotporation in which the United States scheduled airlines
`are the principal stockholders. Other stockholders include a variety of other air transport.
`companies, aircraft manufacturers and foreign flag airlines.
`
`Activities of ARINC include the operation of an extensive system of domestic and
`overseas aeronautical land radio stations, the fulfillment of systems requirements to accomplish
`ground and airborne compatibility, the allocation and assignment of frequencies to meet those
`needs,. the coordination incident to standard airborne communications and electronics systems
`and the exchange of technical infonnation. ARINC sponsors the Airlines Electronic Engineering
`Committee (AEEC), composed of airline technical personnel. The ABBC fonnulates standards
`The establishment of Equipment
`for electronic equipment and systems for airlines.
`Characteristics is a principal function of this Committee.
`
`It is desirable to reference certain general ARINC Specifications or Reports which are
`applicable to more than one type of equipment. These general Specifications or Reports may
`be considered as supplementary to the Equipment Characteristics in which they are referenced.
`They are intended to set forth the desires of the airlines pertaining to components or equipment
`is concerned.
`
`An ARINC Report (Specification or Characteristic) has a twofold purpose which is:
`
`(1)
`
`(2)
`
`To indicate to the prospective manufacturers of airline electronic equipment the
`considered opinion of the airline technical people coordinated on an industry basis
`concerning requisites of new equipment, and
`
`To channel new equipment designed in a direction which can result in the maximum
`possible standardization of those physical and electrical characteristics which influence
`interchangeability of equipment without seriously hampering engineering initiative.
`
`Copyright ARINC:lndustry Activities
`Provided by IHS under license with ARINC
`No reproduction or networking permitted withoullicense from tHS
`
`ii
`
`Order Number: 02046312
`Sold lo:MUNGER TOLLES & OLSON {534576]- AGNES.VILLERO@MTO.COM.
`Not for Resale,2015w02·23 19:39:20 UTC
`
`BOEING
`Ex. 1020
`
`

`

`1(:-:=-:-:-·'
`
`ARINC SPE(;IFI~ADON 618
`TABLE OF CONTENTS
`
`REVISED: December 30, 1994
`
`SUBJECT
`
`PAGE
`
`ITEM
`
`1.0
`1.1
`1.2
`1.3
`1.4
`1.5
`1.5.1
`1.5.2
`1.6
`1.6.1
`1.6.2
`1.7
`1.8
`
`:2.0
`'2.1
`2.2
`2.2.1
`":2.2.2
`:2.2.2.1
`'.2.2.2.2
`2.2.2.3
`2.2.3
`2.2.4
`2.2.5
`2.2.6
`2.2.7
`2.2.8
`2.2.9
`2.2.10
`2.3
`2.3.1
`2.3.2
`2.3.2.1
`2.3.2.2
`2.3.3
`2.3.3.1
`2.3.3.2
`2.3.3.2.1
`2.3.3.2.2
`2.3.3.2.3
`2.3.4
`2.3.5
`2.3.6
`2.3.7
`2.3.8
`2.3.9
`2.3.10
`
`3.0
`3.1
`3.1.1
`3.1.2
`3.2
`3.2.1
`3.2.2
`3.3
`3.3.1
`3.3.1.1
`3.3.1.2
`
`I
`
`I
`
`1 ,--
`
`J
`
`1.0 AIRlGROUND COMMUNICATION
`Introduction
`Purpose of this Document
`Document Organization
`ACARS System Description
`ACARS Components
`Ground System Equipment
`Airborne System Equipment
`ACARS Messages
`Downlink Messages
`Uplink Messages
`Relationship to Other Documents
`Documents Referenced
`
`AIRlGROUNDBLOCKSTRUCTURE
`General Format Description
`Downlink Block Format
`Start of Header
`Mode Character
`Category A Mode Character
`Category B Mode Character
`SAT Mode Character
`Address
`Positive Technical Acknowledgement
`Label
`Downlink Block Identifier
`End of Preamble
`Text
`Suffix
`Block Check Sequence
`Uplink Block Format
`Start of Header
`Mode Character
`Category A Mode Character
`Category B Mode Character
`Address Recognition
`Aircraft Registration Uplink Address
`Flight Identifier Uplink Address
`Airline Identifier
`Flight Number
`S~tter Address
`Positive Tec
`. cal Acknowledgement
`Label Recognition
`Uplink Block Identifier
`End of Preamble
`Text
`Suffix
`Uplink BCS Check
`
`ACARS MESSAGE PROTOCOL
`Basic Message Protocol
`Downlinks
`Uplinks
`Acknowledgement Protocols
`Acknowledgement of a Downlink Block
`Acknowledgement of an Uplink Block
`Message Addressing
`Uplinks
`Aircraft Address
`SITE Address
`
`1
`1
`1
`1
`1
`1
`2
`2
`2
`2
`2
`2
`3
`
`4
`4
`4
`4
`4
`4
`4
`4
`4
`4
`5
`5
`5
`5
`5
`5
`6
`6
`6
`6
`6
`6
`7
`7
`7
`7
`7
`7
`7
`7
`7
`7
`7
`7
`
`8
`8
`8
`8
`8
`8
`9
`9
`9
`9
`9
`
`-"-
`
`I
`~
`
`I
`
`i"-
`
`Copyright ARINC Industry Aclivlties
`Provided by IHS under license with ARINC
`No reproduction or networking permitted withoullicense from lHS
`
`iii
`
`Order Number: 02046312
`Sold lo,MUNGER TOLLES & OLSON [534576[ • AGNES.VILLERO@MTO.COM,
`Not for Resale.2015-02-23 19:39:20 UTe
`
`BOEING
`Ex. 1020
`
`

`

`ARINC SPECIFICATION 618.
`TABLE OF CONTENTS
`
`SUBJECT
`
`Onboard Routing
`Downlinks
`Aircraft Address
`SITE Address
`End User Address
`Supplementary Addresses
`Message Sequencing
`Downlink Message Sequencing
`Message Originator
`Message Number
`Block Sequence Character
`Uplink Message Sequencing
`Retransmissions
`Uplink Retransmission Detection
`Downlink Retransmission Detect
`Multi-Block Processing
`Store and Forward
`Multiblock Downlinks
`Incomplete Multiblock Downlink
`Nesting of Multiblock Downlinks
`Interleaving of Multiblock Downlinks
`Aborting a Multiblock Downlink
`Reblocking a Multiblock Downlink
`Restart Multiblock Downlink
`Multiblock Uplinks
`Message Assembly Timer
`Interblock Timer
`Ground No ACK Timer
`Ground Message Reject Timer
`Restart Multiblock Uplink
`Nesting of Multiblock Uplinks
`Interleaving of Multiblock Uplinks
`Unable to Handle Uplink
`Unable to Deliver Messages
`Printer Reject Messages
`Unusable Messages
`User Defined Messages
`Undelivered Uplink Messages
`Message Prioritization
`Priority of System Control Messages
`User Defined Priority Messages
`Regulatory Guidance on Priority
`
`YHFACARS
`Radio Frequency Environment
`Equipment Architecture
`Equipment Functions
`VHF Preamble
`Pre-key
`Bit Synchronization
`Character Synchronization
`BCS Suffix
`Modem Interface
`Data Rate
`Data Encoding
`Parity Bit
`Bit Transmission Order
`Modulation
`Modulation Measurement Technique
`Modulator Characteristics
`
`3.3.1.3
`3.3.2
`3.3.2.1
`3.3.2.2
`3.3.2.3
`3.3.3
`3.4
`3.4.1
`3.4.1.1
`3.4.1.2
`3.4.1.3
`3.4.2
`3.5
`3.5.1
`3.5.2
`3.6
`3.6.1
`3.6.2
`3.6.2.1
`3.6.2.2
`3.6.2.3
`3.6.2.4
`3.6.2.5
`3.6.3
`3.6.4
`3.6.4.1
`3.6.4.2
`3.6.4.3
`3.6.4.4
`3.6.4.5
`3.6.4.6
`3.6.4.7
`3.7
`3.7.1
`3.7.2
`3.7.3
`3.7.4
`3.7.5
`3.8
`3.8.1
`3.8.2
`3.8.3
`
`4.0
`4.1
`4.1.1
`4.1.2
`4.2
`4.2.1
`4.2.2
`4.2.3
`4.3
`4.4
`4.4.1
`4.4.2
`4.4.2.1
`4.4.2.2
`4.4.3
`4.4.3.1
`4.4.4
`
`REVISED: December 30, 1994
`
`9
`9
`9
`10
`10
`10
`10
`10
`11
`11
`11
`11
`12
`12
`12
`12
`12
`13
`13
`13
`13
`13
`13
`13
`13
`14
`14
`14
`14
`14
`15
`15
`15
`15
`15
`15
`15
`15
`15
`16
`16
`16
`
`17
`17
`17
`17
`17
`17
`17
`18
`18
`18
`18
`18
`18
`18
`18
`18
`18
`
`Copyright ARINC Industry Activities
`Provided by IHS under license with ARINC
`No reproduction or networking permitted withoullicense from IHS
`
`iv
`
`Order Number: 02046312
`Sold !o:MUNGER TOLLES & OLSON [534576)- AGNES.VILLERO@MTO.COM,
`Not for Resale,2015-02-23 19:39:20 UTe
`
`BOEING
`Ex. 1020
`
`

`

`REVISED: December 30,1994
`
`I~
`
`I'...::=J
`.....
`
`ITEM
`
`4.4.5
`4.4.6
`4.5
`4.5.1
`4.5.2
`4.6
`4.6.1
`4.6.2
`4.6.2.1
`4.6.2.2
`
`5.0
`5.1
`5.2
`5.3
`5.4
`5.4.1
`5.4.2
`5.4.3
`5.4.4
`5.S
`5.6
`5.6.1
`5.6.2
`5.6.2.1
`5.6.2.1.1
`5.6.2.1.2
`5.6.2.1.3
`5.6.2.1.4
`5.6.2.2
`5.6.2.3
`5.7
`5.7.1
`5.8
`5.8.1
`5.8.2
`5.8.3
`5.9
`5.9.1
`5.9.2
`5.9.3
`5.9.4
`5.10
`5.11
`5.11.1
`5.11.2
`5.1I.3
`
`6.0
`6.1
`6.2
`6.2.1
`6.2.2
`6.2.3
`6.3
`6.3.1
`6.3.2
`6.4
`6.4.1
`6.4.2
`
`ARINC SPECIFICATION 618
`TABLE OF CONTENTS
`
`SUBJECT
`
`Demodulation
`Demodulator Characteristics
`Medium Access Control
`Channel Sensing
`Radio Channel Access
`Transceiver Control
`Transmitter Keying
`Radio Transceiver Tuning
`Serial Digital Tuning
`2 x 5 Tuning
`
`VHF UNK MANAGEMENT
`Functional Capability of the Airborne Sub-System
`Permission To Send
`No Communications (NOCOMM)
`Tuners and Counters
`Ground Based Timers
`Airborne Timers
`Ground Counters
`Airborne Counters
`Retransmission Logic
`Frequency Management
`Manual Base Frequency Management
`Automatic Base Frequency Management
`Base Frequency Acquisition. State
`Frequency Selection Algorithm.
`Automatic Permission to Send Algorithm
`Scan Timer
`Uplink Squitter - Label SQ
`Base Frequency Establishment State
`Base Frequency Maintenance State
`Operation on Alternate Frequencies
`Data Transceiver Autotune Command - Label :;
`Category A Network Operation
`Establishment
`Contact Timer
`Tracker Message
`Cat~gory B Network Operation
`Ground Station (Site) Address Table
`Initial Operational Selection
`Logical Channel Establishment
`Channel Maintenance State
`Statistical Data Collection
`Statistical Data Reports
`Summary Reports
`Detailed Reports
`No Data Reports
`
`6.0 VOICE MODE OPERATION
`Introduction
`Manual Channel Changes (VOICE/DATA)
`ACARS CDU Changes
`Remote VOICE/DATA Mode Select
`VOICEIDATA Mode Input
`Automatic Channel Changes (VOICE/DATA)
`DATA to VOICE
`VOICE to DATA
`Configuration Programming Functions
`Voice Frequency Control Program Pin
`Auto/Manual Channel Change Program Pin
`
`Copyright ARINC Industry Activities
`Provided by IHS under license with ARINC
`No reproduction or networking permitted without license from IHS
`
`V
`Order Number: 02046312
`Sold lo:MUNGER TOLLES & OLSON [5345761- AGNES.vILLERO@MTO.COM.
`Not for Resale.2015-02-23 19:39:20 UTe
`
`I r I
`
`18
`19
`19
`19
`19
`19
`19
`19
`20
`20
`
`21
`21
`21
`21
`21
`21
`22
`23
`24
`24
`24
`24
`24
`24
`24
`25
`25
`25
`25
`2S
`2S
`25
`26
`26
`26
`26
`26
`27
`27
`27
`27
`28
`28
`28
`28
`28
`
`29
`29
`29
`29
`29
`29
`29
`29
`29
`29
`29
`30
`
`BOEING
`Ex. 1020
`
`

`

`REVISED: Derember 30, 1994
`
`ARlNC SPECIFICATION 618
`TABLE OF CONTENTS
`
`SUBJECT
`
`Dedicated Transceiver Program Pin
`SP/Q6 Enable "Software" Program
`VOICE Mode Enable Software Program
`AOC Voice Channel Signalling
`Voice Contact Request (CALSEL) - Label S4
`Voice Go-Ahead (SELCAL) - Label S4
`VOICE Mode Advisories to the Crew
`Voice Go-Ahead Advisories
`VOICE/DATA Mode Annunciation Outputs
`VOICE Mode Advisories to the DSP
`Dedicated Data Transceiver Advisory - Label F3
`Temporary Suspension - Label SP
`Voice to Data Advisory - Label Q6
`Mode Transition Logic
`DATA Mode to VorCE Mode
`VOICE Mode to DATA Mode
`
`SATCOM INTERFACE
`Overview
`Data Bus Interface
`Command and Control Interface
`SDU Subsystem Identifier (Label 172)
`ACARS MU Status to SDU (Label 270)
`SDU Status to ACARS MU (Label 270)
`Link Interface
`ACARS Message Protocol
`Acknowlei:lgement of a Downlink Block
`Acknowledgement of an Uplink Block
`SATCOM Link Management
`Ground Based Timers
`Airborne Timers
`Ground Counters
`Airborne Counters
`Media Utilization
`
`HFINTERFACE
`Overview'
`Data Bus Interface
`Command and Control Interface
`HFDUIHFDR Subsystem Identifier (Label 172)
`ACARS MU Status to HFDUIHFDR (Label 270)
`HFDUIHFDR Status to ACARS MU (Label 270)
`Link Interface
`ACARS Message Protocol
`HF Link Management
`Acknowlci1gement of a Downlink Block
`Acknowledgement of an Uplink Block
`Timers and Counters
`Ground-Based Timers
`Airborne Timers
`Ground Counters
`Airborne Counters
`Media Utilization
`
`MEDIA UTIUZATION
`Overview
`ACARS BOP Data File
`Media Advisory
`VHF/SATCOM
`SATCOM Channel Operation
`Media Advisory
`VHFIHF
`VHFIHF Channel Operation
`Media Advisory
`
`6.4.3
`6.4.4
`6.4.5
`6.5
`6.5.1
`6.5.2
`6.6
`6.6.1
`6.6.2
`6.7
`6.7.1
`6.7.2
`6.7.3
`6.8
`6.8.1
`6.8.2
`7.0
`7.1
`7.2
`7.3
`7.3.1
`7.3.2
`7.3.3
`7.4
`7.5
`7.5.1
`7.5.2
`7.6
`7.6.1
`7.6.2
`7.6.3
`7.6.4
`7.7
`8.0
`8.1
`8.2
`8.3
`8.3.1
`8.3.2
`8.3.3
`8.4
`8.5
`8.6
`8.6.1
`8.6.2
`8.7
`8.7.1
`8.7.2
`8.7.3
`8.7.4
`8.8
`9.0
`9.1
`9.1.1
`9.1.2
`9.2
`9.2.1
`9.2.2
`9.3
`9.3.1
`9.3.2
`
`30
`30
`30
`30
`30
`30
`30
`30
`31
`31
`31
`31
`31
`32
`32
`32
`
`33
`33
`33
`33
`33
`33
`33
`33
`34
`34
`34
`34
`34
`35
`35
`35
`35
`
`36
`36
`36
`36
`36
`36
`36
`36
`37
`37
`37
`37
`37
`37
`37
`38
`38
`38
`
`39
`39
`39
`39
`39
`39
`40
`40
`40
`40
`
`Copyright ARINC Industry Activities
`Provided by IHS under license with ARINC
`No reproduction or networking permitted without license from IHS
`
`vi
`
`Order Number: 02046312
`Sold lo:MUNGER TOLLES & OLSON [5345761- AGNES.vILLERO@MTO.COM,
`Not for Resale,2015-02-23 19:39:20 UTe
`
`BOEING
`Ex. 1020
`
`

`

`I~
`
`ITEM
`
`9.4
`9.4.1
`9.4.2
`
`ATTACHMENTS
`
`1
`2
`3
`4
`5
`6
`7
`8
`X
`
`ARINC SPECmCATION 618
`TABLE OF CONTENTS
`
`SUBJECT
`
`VHF/SATCOMIHF
`VHF/SATCOMIHF Channel Operation
`Media Advisory
`
`Air/Ground Communications
`Frequency Management Diagrams
`ISO 5 Character Format
`Multiblock Timing Diagrams
`MSK Waveform
`Mode Character
`Voice/Data Notification
`Data Record Contents and Format
`Future Work
`
`APPENDICES
`
`A
`B
`
`Protocol History
`ACARS OvervIew
`
`REVISED: December 30, 1994
`
`PAGE
`
`40
`40
`40
`
`41
`42-46
`47-48
`49-56
`57
`58
`59
`60-62
`63
`
`64-66
`67-73
`
`I
`i
`
`r L.
`
`1 ,
`
`J
`
`Copyright ARINC Industry Activities
`Provided by IHS under license with ARINC
`No reproduction or networking permitted withoullicense from IHS
`
`vii
`
`order Number: 02046312
`Sold to:MUNGER TOLLES & OLSON 15345761- AGNES.VILLERO@MTO.COM,
`Not for Resale.2015-02-23 19:39:20 UTe
`
`BOEING
`Ex. 1020
`
`

`

`Copyright ARINC Industry Activities
`Provided by IHS under license with ARINC
`No reproduction or networking permitted without license from IHS
`
`Order Number: 02046312
`Sold lo:MUNGER TOLLES & OLSON [534576)- AGNES.VILLERO@MTO.COM,
`Not for Resale.2015-02-23 19:39:20 UTC
`
`BOEING
`Ex. 1020
`
`

`

`f
`I~
`
`1.0 AIR/GROUND COMMUNICATION
`
`1.1 Introduction
`
`Chapter 4 describes the VHF ACARS.
`
`REVISED: December 30,1994
`ARINC SPECIFICATION 618 - Page 1
`
`Th~ Aircraft Communications Addressing and Reporting
`System, known by the acronym ACARS, is a data link
`system which allows communication of character-oriented
`data between aircraft systems and ground systems. This
`communications facility enables the aircraft to operate as
`part of the airline's command, control and management
`system.
`
`The Aircraft Communications Addressing and Reporting
`System (ACARS), was introduced as an air-ground
`communications network utilizing the VHF aeronautical
`radio band. Later ACARS was extended to use satellite
`The
`communications system (SATCOM) as well.
`ACARS consists of an airborne subsystem and a ground
`station network. The ground network is attached to the
`networks of subscriber airlines and other users, such as
`aviation authorities.
`
`With the support of the ground based service providers
`network, the airborne part of this air-ground data link
`enables equipment onboard an aircraft to function as a
`mobile communications terminal, and therefore, as if it
`were an integral part of an airlines internal data
`communications system.
`
`1. 2 Putpose of this Document
`
`This Sp~ification contains a compendium of provisions
`previously defined in ARINC Characteristics 546, 566,
`716, 597, 724 and 724B. These Characteristics contained
`redundant material, which, when updated at various times
`created contradictions and confusion'as to which text was
`correct.
`
`The purpose of this Specification is to bring this
`redundant material into one document which Should serve
`as the description of operation within the ACARS
`air-ground environment. This specification also serves
`to clarify contradictions
`in
`the above-mentioned
`documents and present new material which will bring the
`overall ACARS documentation into the current state
`which it has evolved over many years. The provisions
`listed herein are included by reference in the originating
`documents, as appropriate, and therefore continue to
`apply as provisions of systems described in the originating
`documents.
`
`In this document a reference to ARINC 724/B refers to
`BOTH ARINC Characteristic 724
`and ARINC
`Characteristic 724B.
`
`1.3 Document Organization
`
`This Chapter provides an, overview of ACARS and
`introduces the elements necessary for the communications
`function.
`
`Chapter 2 outlines the air-ground block format in its
`entirety. Each of the fields of the message is introduced,
`followed by a definition of the range of characters, from
`the ISO-5 character set, that are authorized for use in the
`field.
`
`' .. ~.
`
`Chapter 5 describes Link Management for a VHF air(cid:173)
`ground network.
`
`Chapter 6 defines an optional capability of the ACARS
`MU to allow the VHF transceiver, which is used for Data
`communications, to be used for VOICE as well.
`
`Chapter 7 describes the air-ground satellite link protocol
`for transporting character-oriented ACARS messages.
`
`Chapter 8 describes the air/ground HF data protocol for
`transporting character-oriented ACARS messages.
`
`Chapter 9 describes the processes needed to operate
`multiple communications media simultaneously and when
`needed, discontinue use of one or more media.
`
`¢-1
`
`1.4 ACARS System Description
`
`ACARS enables airborne devices to function as mobile
`See Attachment 1 which
`communications terminals.
`shows a typical end-to-end communications environment
`and applicable Characteristics/manuals.
`
`COMMENTARY
`
`Generally, the airlines own and control their ground
`network and the aircraft network. Normally, a Data
`link Service Provider (DSP) supplies the air-ground
`network to pass messages between the airlines'
`airborne and ground networks. Some airlines, own
`and operate their own VHF air-ground network.
`These airlines may also offer this service to other
`airlines as a service provider.
`
`There are currently three types of air-ground networks.
`The first system introduced was the VHF ACARS which
`uses a VHF signal between the aircraft and a ground
`station. SATCOM ACARS was introduced later and uses
`a signal which passes
`to a
`from
`the aircraft
`communications satellite which itself is linked to a ground
`station. The ACARS message protocol described in this
`document is used over all media.
`
`HF ACARS was introduced later and uses an HF signal I
`
`between the aircraft and an HP ground station.
`
`¢-1
`
`The format and protocols used to transfer messages
`between the ACARS User's ground system and the Data
`link Service Provider's network differs from the format
`and protocol used to exchange messages between the
`airborne user and the data link service provider. It is the
`responsibility of the data link service provider to provide
`translation between these formats and to provide message
`routing. Those two functions are described in ARINC
`Specification 620.
`
`This document defines the protocol and message format
`for exchange of information by airborne user and the DSP
`across the air-ground link.
`
`1.5 ACARS Components
`
`I
`
`Chapter 3 defines the ACARS MU Message Handling
`Protocols including priorities and multi-block handling.
`Copyright ARINC Industry Activities
`Provided by IHS under license with ARINC
`No reproduction or networking pennitted without license from IHS
`
`ACARS is the portion of the system incorporated by the
`Order Number: 02046312
`Sold to:MUNGER TOLLES & OLSON {534576]- AGNES.VILLERO@MTO.COM,
`Not for Resa[e,2015-02-23 19:39:20 UTe
`
`F
`i I
`
`l
`
`BOEING
`Ex. 1020
`
`

`

`ARINC SPECIFICATION 618 - Page 2
`
`1.0 AIR/GROUND COMMUNICATION (cont'd).
`
`REVISED: December 30, 19.94
`
`1.5 ACARS Components (cont'd)
`
`service provider's ground network and the equipment on
`board the aircraft needed to facilitate the transfer of the
`messages.
`
`provider. ACARS message formats used across. the RF
`link with the aircraft are designed for efficient use of the
`Other formats are used when data is
`spectrum.
`exchanged between the service provider and the user
`
`1.5.1 Ground System Equipment
`
`airline's ground facilities. See Chapter 2 of ARINC
`
`The service provider's ground network consists, as a
`minimum; of an ACARS data link service processor and
`a communications network connecting the processor and
`the ground stations.
`
`For VHF ACARS, the ground stations consist of a
`microcomputer connected
`to a VHF receiver and
`transmitter. For SATCOM ACARS, the ground stations
`to a ground earth
`are connected
`station of a
`
`I communications satellite operator. For HF ACARS the
`
`¢-l ground stations consist of a computer connected to an HF
`receiver and transmitter.
`
`1.5.2 Airborne System Equipment
`
`The airborne equipment consists of an ACARS
`Management Unit (MU) which is connected to a
`control/display unit (either dedicated or multi-purpose)
`and any ancillary equipment which supports the.MU in its
`function such as the Optional Auxiliary Terminal (OA1),
`Digital Flight Data Acquisition Unit (DFDAU) orcockpit
`printer.
`
`To access the VHF ACARS air-ground network, the
`ACARS MU is connected to a VHF transceiver.
`
`To access the SATCOM ACARS air-ground network, the
`ACARS MU is connected to the Satellite Data Unit
`(SDU). The satellite system is described by ARINC
`Characteristic 741.
`
`COMMENTARY
`
`ACARS MUs are not designed to support the
`Network Layer functions required by SATCOM as
`described within ARINC Characteristic 741 and
`commonly referred to as Data Level 3 SATCOM (as
`described within the INMARSAT System Definition
`Manual (SDM). However, an ACARS MU may be
`designed to support Data Level 0, 1, or 2 SATCOM
`as described within the INMARSAT SDM. The
`ACARS MU/SATCOM SDU protocol interface and
`a definition of SATCOM Data Levels are described
`withln Section 7.0 of this specification.
`
`¢-l
`
`To access the HF ACARS air-ground network, the
`ACARS MU is connected to the HF Data Unit (HFDU)
`or HF Data Radio (HFDR). The HF datalink system is
`described by ARINC Characteristic 753.
`
`1.6 ACARS Messages
`
`Specification 620 for further definition of the interaction
`of the service provider with user facilities.
`
`The format of ACARS air-ground'messages is defined in
`Chapter 2 of this Specification. The definition of the text
`portion to be inserted "for each specific message is
`contained in Chapter 6 of ARINC Specification 620,
`"Data Link Ground Systems Standard and Interface
`Specification". The messages passed between the air~e's
`ground facilities and the service provider's ground
`network, should be formatted and processed in accordance
`with the ATAIIATA Interline Communications Manual
`(leM).
`
`1.6.1 Downlink Messages
`
`transmitted from
`Air-to-ground (downlink) messages
`aircraft are received by the service provider's ground
`station(s). One or more of these stations pass the
`message
`to a central processor for processing in
`accordance with the provisions of ARINC Specification
`620.
`
`1.6.2 Uplink Messages
`
`Ground-to-air (uplink) messages are passed from the
`airlines' network to the service provider who in turn
`converts it to data link format and sends the message to
`a ground station in its network for transmission to the
`aircraft.
`The air-ground protocol for the aircraft
`equipment then acknowledges receipt of the message.
`
`1. 7 Relationship to Other Documents
`
`The documentation of the protocols to be exercised within
`the ACARS environment is shown pictorially in Figure I(cid:173)
`I of Attachment 1 to this S~ecification.
`
`to be used
`for
`The protocols and procedures
`communications between the airborne user and the data
`link service provider network are described in this
`Specification. The protocols used onboard the aircraft by
`subsystems participating in ACARS are defined in Project
`Paper 619, "Airborne Equipment Protocols for File
`Transfer of Character Data."
`
`The capabilities of the onboard equipment are defined in
`ARINC Characteristics 597, 724 or 724B as applicable.
`Information from these Specifications and Characteristics
`is not duplicated in this document except as necessary to
`clarify the data link service provider to data link user
`interface.
`
`The ACARS
`a
`link provides
`air-ground data
`general-purpose data link capable of handling a wide
`variety of character-oriented messages.
`
`The protocols and procedures to be administered by the
`data link service provider are contained in ARINC
`Specification 620, "Data Link· Ground System Standard
`and Interface Specification (DGSSIIS)".
`. Two· message formats are utilized by the ground service
`Copyright ARINC Industry Activities
`Order Number: 02046312
`Provided by IHS under license with ARINC
`Sold to:MUNGER TOLLES & OLSON [534576]- AGNES.vILLERO@MTO.COM,
`No reproduction or networking permitted without license from IHS
`Not fer Resale,2015-02-2319;39:20 UTe
`
`BOEING
`Ex. 1020
`
`

`

`1(_-_'
`
`1.0 AIR/GROUND COMMUNICATION (cont'dl
`
`ARINC SPECIFICATION 618 • Page 3
`
`The protocols used between the ground-based user and the
`data link serVice provider network are described in the
`ATAIIATA Interline Communications Manual (lCM).
`
`1.8 Documents Referenced
`
`This Specification refers to a number of other documents.
`Most of these documents are published by ARINC.
`References to ARINC standards should be interpreted as
`the most recent version of the mentioned document.
`
`ARINC Specification 410,
`Mark 2 Standard Frequency Selection System
`ARINC Specification 429,
`Mark 33 Digital Information Transfer System
`(DITS)
`ARINC Characteristic 546.
`Airborne VHF Communications Receiver
`ARINC Characteristic 566,
`Airborne VHF Communications Transceiver
`& Mark 1 VHF SATCOM System
`ARINC Characteristic 566A,
`Mark 3 VHF Transceiver
`ARINC Characteristic 597,
`Aircraft Communications Addressing and
`Reporting System (ACARS)
`ARINC Specification 619,
`Airborne Equipment Protocols for
`File Transfer of Character Data
`ARINC Specification 600.
`Air Transport Avionics Equipment Interfaces
`ARINC Specification 620,
`Data Link Ground System Standard and
`Interface Specification (DGSSIIS)
`ARINC Specification 623,
`Character--Oriented Air Traffic Service
`Applications
`ARINC Characteristic 716.
`Airborne VHF Communications Transceiver
`ARINC Characteristic 124,
`Mark 2 Aircraft Communications Addressing
`and Reporting System (ACARS)
`ARINC Characteristic 724B,
`Aircraft Communications Addressing and
`Reporting System (ACARS)
`ARINC Characteristic 741,
`Aviation Satellite Communications System
`(SATCOM)
`PART 1 Aircraft Installation Provisions
`PART 2 System Design
`PART 3 Circuit Mode Voice and Data Services
`PART 4 Specification and Description Language
`
`(ATS)
`
`Proceedings of the IRE, January 1961, "Cyclic Codes for
`Error Detection".
`
`Code of Federal Regulations (USA)
`
`I --==:J
`
`Copyright ARINC Industry Activities
`Provided by IHS under license with ARINC
`No reproduction or networking permitted without license from IHS
`
`Order Number: 02046312
`Sold to:MUNGER TOLLES & OLSON [534576)- AGNES,VILLERO@MTO.COM.
`Not for Resale,2015M02~23 19:39:20 UTe
`
`l
`
`BOEING
`Ex. 1020
`
`

`

`ARINC SPECIFICATION 618 - Page 4
`
`REVISED: December 30, 1994
`
`2.1 General Format Description
`
`2.2.2.1 Category A Mode Character
`
`2.0 Am/GROUND BLOCK STRUCTURE
`
`The ACAR8 air-ground messag~ structure closely follows
`the recommendations of RTCA Document No. DO-136
`dated March 17, 1968.
`
`The fields of ACARS messages are encoded according to
`the seven-unit convention specified in IeAO Annex 10.
`The ISO-5 character set is illustrated in Table 3-1 of
`Attachment 3. An eighth bit is added to each character to
`complete the octet and render character parity odd. In
`this Specification, the ISO 5 characters are represented
`symbolically with an expression in the general form. of
`(column/row) such as (1/6) to represent the "SYN"
`character.
`
`The Block Check Sequence (error detection scheme) is
`composed of 16 bits which do not comply with this
`coding convention. The BCS characters are distinguished
`from communications control characters by their relative
`position.
`
`Message blocks prepared for transmission should have the
`following format:
`.
`
`NAME OF FIELD
`
`FIELD LENGTH
`. (CHARTERS)
`
`NOTES
`
`1
`1
`7
`1
`
`2
`1
`
`Start of Heading
`Mode
`Address
`Technical
`Acknowledgement
`Label
`Uplink/Downlink
`Block Identifier
`Start of Text
`Text
`Suffix
`Block Check
`Sequence
`ill This character is used only for messages containing
`text.
`
`1
`220 (maximum)
`1
`16 bits
`
`1
`
`All Category A downlinks are uniquely identified with a
`2 (3/2) in the Mode character position.
`
`2.2.2.2 Category B Mode Cha