STAR ARMY

Sci-fi roleplaying and worldbuilding community

User Tools

Site Tools

Trace:
guide:aerospace_communication_protocols

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
guide:aerospace_communication_protocols [2014/04/16 16:01] – external edit guide:aerospace_communication_protocols [2023/12/20 18:20] (current) – external edit 127.0.0.1
Line 11: Line 11:
 The standard message contains several key components. The first is the designation of the calling station and the intended receiving stations. This can be given in several formats, including: The standard message contains several key components. The first is the designation of the calling station and the intended receiving stations. This can be given in several formats, including:
  
-“[receiving station], [calling station]”\\ +“[receiving station], [calling station]” 
-“[receiving station], this is [calling station]”\\ +“[receiving station], this is [calling station]” 
-“this is [calling station], calling [receiving station]”\\+“this is [calling station], calling [receiving station]”
  
 Then follows the message traffic. The body of the message ought to be as short as possible. Leaving out unnecessary grammatical features is acceptable, even preferable, as long as the meaning of the message remains clear. Particularly long message out to include a pause, in the event that other critical traffic can be heard across the network. This pause is signaled by saying, “break,” followed by dead air before the message is resumed. Finally, the end of the communication ought to indicate the intention of future communication. If the calling station expects a response or thinks that a response is likely, the communication should be finished with “over.” For messages bearing critical or complex instructions that require concrete confirmation, the phrase “confirm copy” can be given before “over,” with the expected response being “I copy all,” “solid copy,” or some other form of confirmation. If the calling station is concluding an exchange or is given some general information that will not require or likely elicit a response, the communication should be finished with “out.” Then follows the message traffic. The body of the message ought to be as short as possible. Leaving out unnecessary grammatical features is acceptable, even preferable, as long as the meaning of the message remains clear. Particularly long message out to include a pause, in the event that other critical traffic can be heard across the network. This pause is signaled by saying, “break,” followed by dead air before the message is resumed. Finally, the end of the communication ought to indicate the intention of future communication. If the calling station expects a response or thinks that a response is likely, the communication should be finished with “over.” For messages bearing critical or complex instructions that require concrete confirmation, the phrase “confirm copy” can be given before “over,” with the expected response being “I copy all,” “solid copy,” or some other form of confirmation. If the calling station is concluding an exchange or is given some general information that will not require or likely elicit a response, the communication should be finished with “out.”

guide/aerospace_communication_protocols.txt · Last modified: 2023/12/20 18:20 by 127.0.0.1

Page Tools

Content copyright StarArmy.com and/or individual contributors and used under license. Star Army is a registered trademark.
Terms of Service - Privacy Policy