IFD X25 v3 9 3

HUGHES
<ifd_x25_mexico.ps>
NETWORK SYSTEMS LTD
A Hughes Electronics Company
Domestic L-Band Mobile Data Service Interface Document X.25 and Asynchronous User Interface
For Telecommunicaciones De Mexico
Reference: A4-IFD-003076-1
Date: Issue: Status:
14th December 2005 3.9 Accepted
Hughes Network Systems Limited Saxon Street Milton Keynes MK14 6LD United Kingdom
Telephone Facsimile
+44 1908 221122 +44 1908 221127
Copyright Hughes Network Systems Ltd 2005
A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005
X.25 and Asynchronous User Interface
The contents of this document are proprietary to HNS Limited and cannot be disclosed, duplicated, reproduced or used in part or in whole for any purpose other than in connection with the associated binding contract between HNS Limited and the recipient. This restriction does not apply to information in this document if it is obtainable from another source without breach of this notice.
Document Source: TCM Team Doc, Library [IFD], Version X25_V3.9 To Generate Document: @IFD_X25
[ifd_x25.mss]
REVISION HISTORY Issue Status Date Author Change References
3.0A 3.0B 3.0C 3.0 3.1A 3.1 3.2A 3.2 3.3A 3.3B 3.3 3.4A 3.4 3.5a
3.5 3.6a 3.6b 3.6 3.8 3.9
F.W.Goodman Changes for spot beam systems. R80000. SCR: 61 For Review 19-Apr-95 F.W.Goodman Merged 2.4A and 2.4 changes. Plus further implementation of SCR: 61 For Review 25-Apr-95 F.W.Goodman Incorporation of review comments. Merged 2.5A and 2.5 changes. Accepted 25-Apr-95 F.W.Goodman Incorporation of review comments. SPR: 23347 For Review 29-Jun-95 F.W.Goodman Merged 2.6A and 2.6 changes. Incorporate new SCRs/SPRs. R80009. SPRs: 23465, 23719. Accepted 30-Jun-95 F.W.Goodman Incorporation of review comments. For Review 22-Aug-96 A.J.Chisholm Merge with V2.8 SCRs 514,515 SPRs 22219,24485,24603,25149,25150 Accepted 21-Nov-96 A.J.Chisholm Accepted For Review 5-Feb-97 A.J.Chisholm GSOR, SCRs 414,531,549 For Review 25-Feb-97 A.J.Chisholm SCR 531 update Accepted 6-Mar-97 A.J.Chisholm Accepted For Review 24-Apr-97 A.J.Chisholm IMR1, SCR 555 Accepted 28-Apr-97 A.J.Chisholm Accepted For Review 10-Mar-98 M.J.Williams Reinstate SCR539 for Telstra SPRs 25732, 25798. CN114 features turned on. Accepted 25-Oct-00 M.J.Williams Accepted For Review 19-Oct-00 M.J.Williams SPR26259, Make NCS failure reasons visible to all customers For Review 22-Mar-01 M.J.Williams Enable new features for TDM Remove Signoff sheet and pre 3.0 history Accepted 19-Feb-2003 M.J.Williams No comments Accepted Accepted 24-Jan-2005 M.J.Franklin 13-Dec-2005 B. Dhaliwal CN: 137. Covert Security Alerts CN141 - Enhanced Data Reports
For Review 11-Jan-95
Note: Change bars highlight changes made since Issue V3.3 of this document.
Reporting Issues with this Document

Any errors or omissions found in this document should be reported to HNS by means of a Customer Service Problem Report (CSPR). This method may also be used to raise any suggestions for future releases. The procedure for raising an CSPR is explained in Appendix F of the System Operator Console Operator Guide reference [5].
Referenced and Related Documents

Reference: 1. 2. 3. 4. 5. 6. Inmarsat-C SDM Identity: Issue: 1.3.1 plus applicable CNs Kermit, A File Transfer Protocol Identity: Frank Da Cruz, Digital Press CCITT Recommendations X1-X32 Identity: Volume viii, Fascicle viii.2 System Manual Identity: A4-OMM-003076 Issue: Issue: Blue Book
Issue: Latest
Operator Guide, System Operator Console Identity: A4-OPG-003076 Issue: Latest Satellite User Interface Document Identity: A4-IFD-003076-5 Issue: Latest
Table of Contents
Reporting Issues with this Document . . . . . . . . . . . . . . . . . . . . . . .
Referenced and Related Documents . . . . . . . . . . . . . . . . . . . . . . . . 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3. Notes to Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terrestrial User Interface Structure . . . . . . . . . . . . . . . . . . . . . . . . 2.1. Delimiters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2. Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3. Types of User Entries and Displays . . . . . . . . . . . . . . . . . . . 2.4. Response Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5. Meta-Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1. Message Entry Meta-Commands . . . . . . . . . . . . . . . 2.5.2. Other Specific Meta-Commands . . . . . . . . . . . . . . . . 2.5.3. General Meta-Commands . . . . . . . . . . . . . . . . . . . 2.5.4. Responses to Meta-Command Prompts . . . . . . . . . . . . 2.6. Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7. Message Reference Numbers . . . . . . . . . . . . . . . . . . . . . . 2.8. Command Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9. Interactive Versus Batch Mode . . . . . . . . . . . . . . . . . . . . . . 2.10. Response Delay to User Input . . . . . . . . . . . . . . . . . . . . . . 2.11. X.29 Versus X.25 Access . . . . . . . . . . . . . . . . . . . . . . . . . 2.12. Download/Deletion Originator Text . . . . . . . . . . . . . . . . . . . . 2.13. Further Considerations for Computer-Based Users . . . . . . . . . . . 2.14. Delivery Reattempts . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.15. Delivery of Data Reports and Messages . . . . . . . . . . . . . . . . . 2.16. Immediate Forwarding of Data Reports and DNID-Addressed Messages 2.17. Clearing Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.18. Delivery of Enhanced Data Reports . . . . . . . . . . . . . . . . . . . ES - Enhanced Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1. ES1 - User Connects to LES . . . . . . . . . . . . . . . . . . . . . . . 3.2. ES2 - Personal Identification Number . . . . . . . . . . . . . . . . . . 3.3. ES4 - Enter Password . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4. ES3 - Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EGC - Enhanced Group Call : Service Selection 0 . . . . . . . . . . . . . . . 4.1. EGC1 - Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2. EGC2 - Priority (C1) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3. EGC3 - Service Code (C2) . . . . . . . . . . . . . . . . . . . . . . . . 4.4. EGC4 - Address (C3) . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5. EGC5 - Repetition Code (C4) . . . . . . . . . . . . . . . . . . . . . . . 4.6. EGC6 - Presentation Code (C5) . . . . . . . . . . . . . . . . . . . . . 4.7. EGC7 - Enter Message . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8. EGC8 - Meta-Command . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.1. .SEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.2. .QUIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.3. .RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8.4. .HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9. EGC9 - QUIT [Are You Sure?] . . . . . . . . . . . . . . . . . . . . . . 2 2 2 3 4 4 4 5 6 7 7 8 8 8 9 10 11 11 12 12 13 15 16 16 16 18 18 19 19 19 20 22 23 23 23 28 29 30 30 31 32 32 32 33 33 33
2.
3.
4.
5.
6.
7. 8.
9.
4.10. EGC10 - RESTART [Are You Sure?] . . . . 4.11. EGC11 - Special Format for Binary . . . . . 4.12. EGC12 - Continue Message . . . . . . . . 4.13. EGC13 - ENID Download Command . . . . 4.14. EGC14 - Download ENID . . . . . . . . . . DNID - DNID Retrieval : Service Selection 2 . . . . 5.1. DNID1 - Selection . . . . . . . . . . . . . . 5.2. DNID2 - DNID Selection . . . . . . . . . . 5.3. DNID3 - Range . . . . . . . . . . . . . . . 5.4. DNID4 - Start Date/Time . . . . . . . . . . 5.5. DNID5 - End Date/Time . . . . . . . . . . . 5.6. DNID6 - Protocol . . . . . . . . . . . . . . 5.7. DNID7 - Kermit Protocol . . . . . . . . . . 5.8. DNID8 - Data to be Deleted . . . . . . . . . 5.9. DNID9 - DNID to Delete . . . . . . . . . . 5.10. DNID10 - Range . . . . . . . . . . . . . . 5.11. DNID11 - Start Date/Time . . . . . . . . . 5.12. DNID12 - End Date/Time . . . . . . . . . . 5.13. DNID13 - Are You Sure? . . . . . . . . . . MSG - Message Submission : Service Selection 4 . 6.1. MSG1 - Mobile Number . . . . . . . . . . . 6.2. MSG2 - Presentation . . . . . . . . . . . . 6.3. MSG3 - Enter Message . . . . . . . . . . . 6.4. MSG4 - Meta-Commands . . . . . . . . . . 6.4.1. .SEND . . . . . . . . . . . . . . 6.4.2. .QUIT . . . . . . . . . . . . . . . 6.4.3. .RESTART . . . . . . . . . . . . 6.4.4. .HELP . . . . . . . . . . . . . . 6.5. MSG5 - QUIT [Are You Sure?] . . . . . . . 6.6. MSG6 - RESTART [Are You Sure?] . . . . 6.7. MSG7 - Special Format for Binary . . . . . 6.8. MSG8 - Continue Message . . . . . . . . . CAN - Message Cancellation : Service Selection 6 7.1. CAN1 - Message Reference Number . . . 7.2. CAN2 - Date/Time Submitted . . . . . . . . ENQ - Message Status Enquiry : Service Selection 8 8.1. ENQ1 - Message Reference Number . . . 8.2. ENQ2 Date/Time Submitted . . . . . . . . 8.3. ENQ3 - Select Status . . . . . . . . . . . . POLL - Polling : Service Selection 9 . . . . . . . . 9.1. POLL1 - Region . . . . . . . . . . . . . . . 9.2. POLL2 - Command . . . . . . . . . . . . . 9.3. POLL3 - Poll Type . . . . . . . . . . . . . 9.4. POLL4 - Poll Type . . . . . . . . . . . . . 9.5. POLL5 - Poll Type . . . . . . . . . . . . . 9.6. POLL6 - Mobile Number . . . . . . . . . . 9.7. POLL7 - Area Type . . . . . . . . . . . . . 9.8. POLL8 - Area Address . . . . . . . . . . . 9.9. POLL9 - DNID . . . . . . . . . . . . . . . 9.10. POLL10 - Subaddress . . . . . . . . . . . 9.11. POLL11 - Acknowledgement . . . . . . . . 9.12. POLL12 - Presentation . . . . . . . . . . . 9.13. POLL13 - Sequence Number . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33 34 35 35 36 37 37 41 41 44 44 45 45 45 46 46 47 47 48 49 49 52 53 53 54 54 54 55 55 55 56 57 58 58 58 61 61 61 61 71 71 77 78 78 79 79 80 80 81 81 82 82 83
ii
10. 11. 12. 13.
14. 15.
16.
17. 18. 19. A.
POLL14 - Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . POLL15 - Define Macro Encoded Message . . . . . . . . . . . . . . . POLL16 - Macro Encoded Message . . . . . . . . . . . . . . . . . . . POLL17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . POLL18 - Member Number . . . . . . . . . . . . . . . . . . . . . . . . POLL19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . POLL20 - Unreserved Data Reporting Interval . . . . . . . . . . . . . . POLL21 - Enter Message . . . . . . . . . . . . . . . . . . . . . . . . POLL22 - Meta-Commands . . . . . . . . . . . . . . . . . . . . . . . . 9.22.1. .SEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.22.2. .QUIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.22.3. .RESTART . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.22.4. .HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.23. POLL23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.24. POLL24 - QUIT [Are You Sure?] . . . . . . . . . . . . . . . . . . . . . 9.25. POLL25 - RESTART [Are You Sure?] . . . . . . . . . . . . . . . . . . 9.26. POLL26 - Special Format for Binary . . . . . . . . . . . . . . . . . . . 9.27. POLL27 - Continue Message . . . . . . . . . . . . . . . . . . . . . . . 9.28. POLL28 - Response . . . . . . . . . . . . . . . . . . . . . . . . . . . EGC - Enhanced Group Call with PDN : Service Selection 10 . . . . . . . . . . MSG - Message Submission with PDN : Service Selection 14 . . . . . . . . . . POLL - Polling with PDN: Service Selection 19 . . . . . . . . . . . . . . . . . . PW - Change Password : Service Selection 80 . . . . . . . . . . . . . . . . . 13.1. PW1 - Enter Old Password . . . . . . . . . . . . . . . . . . . . . . . . 13.2. PW2 - Enter New Password . . . . . . . . . . . . . . . . . . . . . . . 13.3. PW3 - Verify New Password . . . . . . . . . . . . . . . . . . . . . . . QUIT - QUIT : Service Selection 99 . . . . . . . . . . . . . . . . . . . . . . . 14.1. QUIT1 - Are You Sure? . . . . . . . . . . . . . . . . . . . . . . . . . DNID Data Reports and Messages . . . . . . . . . . . . . . . . . . . . . . . . 15.1. Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2. DNID-Addressed Messages . . . . . . . . . . . . . . . . . . . . . . . 15.3. Enhanced Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . Outgoing Call Message Formats . . . . . . . . . . . . . . . . . . . . . . . . . 16.1. Common Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2. Delivery Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.1. Normal Message from Mobile . . . . . . . . . . . . . . . . . 16.2.2. Distress Message from Registered Maritime Mobile . . . . . . 16.2.3. Distress Message from Unregistered Maritime Mobile . . . . . 16.2.4. Distress Alert from Registered Maritime Mobile . . . . . . . . 16.2.5. Distress Alert from Unregistered Maritime Mobile . . . . . . . 16.2.6. Land Mobile Alert from Registered Mobile - Inmarsat Format . 16.2.7. Land Mobile Alert from Registered Mobile - User Defined Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.8. Land Mobile Alert from Unregistered Mobile - Inmarsat Format 16.3. Delivery Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delivery Success and Failure Reasons . . . . . . . . . . . . . . . . . . . . . . Standard Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Setting of X.29 PAD Parameters . . . . . . . . . . . . . . . . . . . .
9.14. 9.15. 9.16. 9.17. 9.18. 9.19. 9.20. 9.21. 9.22.
84 85 85 85 86 86 86 87 87 88 88 88 89 89 89 89 90 90 91 92 92 92 93 93 93 93 95 95 97 97 100 103 106 106 107 107 108 108 108 109 109 110 110 110 112 114 116 A-1
Examples of Batch Mode Submission . . . . . . . . . . . . . . . . . . . . . . .
iii
B.
User Guide for LES Kermit B.1. B.2. B.3.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B-1 B-1 B-1 B-1 B-2 B-3 C-1 C-1 C-1 C-1 C-1 C-2 C-2 C-2
Introduction . . . . . . . . . . . . . . . . . . . . . . Procedure . . . . . . . . . . . . . . . . . . . . . . . B.2.2. Parameters . . . . . . . . . . . . . . . . . . B.2.1. Example User Download Dialogue Via Kermit LES Validated Versions of Kermit . . . . . . . . . .
C.
User Guide for Asynchronous Modem and Terminal Settings . . . . . . . . . . C.1. Introduction . . . . . . . . . . . . . . . . . . . . C.2. LES Modem Capabilities . . . . . . . . . . . . . C.3. PC or Terminal Connection to the Remote Modem C.3.1. Character Format . . . . . . . . . . . . . C.3.2. DTE to Modem Data Rate . . . . . . . . C.3.3. Flow Control . . . . . . . . . . . . . . . C.4. Modem Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
List of Figures
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 A-1 A-2 B-1 Special Format for Binary Data . . . . . . . . . . . . . . . . . Network Topology for Various Types Of X.25/X.29 LES Access Enhanced Services Summary with Passwords . . . . . . . . . EGC Service Command Structure . . . . . . . . . . . . . . . . EGC Service Command Structure - Continued (1) . . . . . . . . EGC Service Command Structure - Continued (2) . . . . . . . . EGC Service Command Structure - Continued (3) . . . . . . . . Help Text for EGC Service Code - C2 Code . . . . . . . . . . . Help Text for EGC Address - C3 Code . . . . . . . . . . . . . . C4 Repetition Help Screen - Category A Codes . . . . . . . . . DNID Command Summary . . . . . . . . . . . . . . . . . . . . DNID Command Summary - Continued (1) . . . . . . . . . . . DNID Command Summary - Continued (2) . . . . . . . . . . . DNID Status Report Format . . . . . . . . . . . . . . . . . . . Example DNID Status Report . . . . . . . . . . . . . . . . . . Message Submission Command Summary . . . . . . . . . . . Message Submission Command Summary - Continued (1) . . . Message Cancellation Command Structure . . . . . . . . . . . Message Status Enquiry Command Structure . . . . . . . . . . Message Status Enquiry Response for Messages . . . . . . . . Message Status Enquiry Response Example for Messages . . . Message Status Enquiry Response for Polls . . . . . . . . . . Message Status Enquiry Response Example for Polls . . . . . Message Status Enquiry Response for EGC Messages . . . . . Message Status Enquiry Response Example for EGC Messages Polling Command Structure . . . . . . . . . . . . . . . . . . . Polling Command Structure - Continued (1) . . . . . . . . . . . Polling Command Structure - Continued (2) . . . . . . . . . . . Polling Command Structure - Continued (3) . . . . . . . . . . . Polling Command Structure - Continued (4) . . . . . . . . . . . Help Text for Poll Command . . . . . . . . . . . . . . . . . . . Help Text for Poll Area Type . . . . . . . . . . . . . . . . . . . Help Text for Poll Area Address . . . . . . . . . . . . . . . . . Change Password Command Structure Summary . . . . . . . . QUIT Command Structure . . . . . . . . . . . . . . . . . . . . Format of Data Reports . . . . . . . . . . . . . . . . . . . . . Format of Data Reports - Continued . . . . . . . . . . . . . . . Format of DNID-Addressed Messages . . . . . . . . . . . . . . Format of DNID-Addressed Messages - Continued . . . . . . . Format of Enhanced Data Reports . . . . . . . . . . . . . . . . Format of Enhanced Data Reports - Continued . . . . . . . . . Example of Batch Mode Message Submission . . . . . . . . . Example of Batch Mode Binary Message Submission . . . . . . User Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 14 21 24 25 26 27 28 29 30 38 39 40 42 43 50 51 59 63 64 65 66 67 68 69 72 73 74 75 76 77 80 81 94 96 98 99 101 102 104 105 A-2 A-3 B-2
List of Tables
1 2 3 C-1 Recommended Use of Delimiters at Prompts Before Enter Binary Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X.29 Parameters for Interactive Session . . . . . . . . . . . . . . X.29 Parameters for Non-Interactive Session and Using Kermit . . Supported Modulation Modes . . . . . . . . . . . . . . . . . . .
. . . .
. . . .
. . . .
. . . .
10 117 118 C-1
Introduction
1 Introduction 1.1 Scope This interface specification is for the following purposes: Define the interface for the implementers of the LES. Define the interface for implementers of the software for user equipment. Define for technical writers the user interface for the creation of user guides, such as the Domestic L-Band Mobile Data Services User Guide. 1.2 Overview This document describes the interface for PSDN and PSTN users to access the Enhanced Services provided by the HNS Land Earth Station (LES). The enhanced services are available only to registered users and include the following: Enhanced Group Call (EGC) DNID Retrieval Message Submission Message Cancellation Message Status Enquiry Polling Modify Password The call set-up is not described in detail since it follows the procedures for the particular type of network that is used to connect to the LES. This document will also describe the format of messages, data reports, and status enquiry responses sent to the terrestrial user from the LES. These data formats have the following distinct types: Messages sent to a user using the store and forward facility of the LES, which include distress messages, distress alerts and land mobile alerts. Data reports and DNID-addressed messages that are retrieved by the user from a Data Reporting and Polling, Data Network ID (DNID) file. Data reports immediately forwarded to a users address DNID-addressed messages immediately forwarded to a users address Store and forward messages are transmitted as soon as possible via connections established by the LES on the availability of terrestrial circuits and the operational status of the destination. The format of the content of distress messages, distress alerts and land mobile alerts is specified in the Satellite User Interface Document, Reference 6. When delivered by the X.25 interface they
2
Introduction
are treated in the same way as other store and forward messages. Messages and data reports destined for a DNID file may be stored at the LES until the user calls into the LES and retrieves them into the users own system may be immediately forwarded by the LES to the users address , or, if forwarding fails, they may be stored and then automatically retrieved and forwarded by the LES when immediate forwarding later succeeds . If they are not immediately forwarded, messages addressed to a DNID file are considered delivered once they have been stored in the DNID file. Message status enquires will show a delivered status. It is the terrestrial users responsibility to call in to the LES to retrieve messages and data reports stored in a DNID file, unless they are automatically retrieved and forwarded by the LES.. 1.3 Notes to Users 1. The term DNID defines an identifier for a set of mobiles, available for use by a specific registered user, for the purpose of sending polling commands and for identifying the file for receiving data reports and messages from the set of mobiles. In earlier issues of this document this term was defined as CNID. The related term ENID is used throughout the document to define an identifier for a set of mobiles, available for use by a specific registered user, which can respond to EGC commands associated with that ENID. In earlier issues of this document this term was defined as EGC ID. The term DNID is now used in preference to CNID, and that of ENID in preference to EGC ID, to reflect current terminology. 2. This interface is designed to be used both by people working interactively using a terminal (manual data entry), and by computer equipment that pre-processes the data (automatic data entry). Messages and data reports retrieved from a DNID file or immediately forwarded to a users address require computing equipment to process the information. As a user option the file transfer protocol Kermit is available to retrieve messages and data reports from DNID files. 3. The prompts, responses and help strings, shown in this document are the factory settings for when HNS software is delivered to the customer. These settings may be modified by the customer on-site, on request, by altering the relevant configuration files which accompany the software, although HNS are not obliged to change this document to reflect these on-site modifications. Note that certain strings are produced in more than one context, and this needs to be accounted for when making changes. The default X.29 Pad settings shown in Tables 2 and 3 are also factory settings, and are required for X.29 Pad access to the LES. These may be modified on-site by the LES operator. 4. It is understood that for everyday usage those sections which address in detail the various commands and responses will be of most interest. However, the user must be acquainted with the important general points made in Section 2 before proceeding with these more detailed sections.
Terrestrial User Interface Structure
2 Terrestrial User Interface Structure This section describes the basic structure of the terrestrial user interface. The types of messages and the syntax used to define the messages are described. The use of this interface starts only after the caller has been connected to the LES. The user is presented with a succession of prompts and the response is checked where applicable for appropriate validity at each step. Each transaction scrolls the previous transaction up the screen; screens are not cleared during the interaction. It is also possible to merge any set of consecutive entries to be used by computers or users who know the correct order. The points made in this section are basic to the operation of the LES as a whole. The user should be familiar with these points before proceeding to later sections of this document. 2.1 Delimiters All input fields must be separated by a suitable delimiter. The valid field delimiters are: <SP> or <Space> Hex 20 <CR> <LF> <CRLF> <FF> <Comma> <Colon> Notes: 1. Multiple spaces are treated as one delimiter. 2. For the remainder of this document the appearance of <SP>, <CR>, <LF>, <CRLF> and <FF> may be taken to denote space, carriage return, line feed, carriage return and line feed, and form feed characters respectively. 3. Entries can be sent to the LES in either upper or lower case letters or a mixture of the two. 4. When multiple correct entries are given on a single line, correctly delimited, the LES suppresses the prompts (since the data has already been entered). 5. If one of the other above mentioned delimiters follows one or more spaces the space characters will then be effectively ignored. 6. Restrictions apply to the delimiters that may be used at the prompts preceding the prompt for binary message data. See Section 2.6 for more information. 2.2 Timers During interactions the caller is given 30 seconds to respond to each prompt. received by that time the response: RESP:TIMEOUT Timing out Please enter data
4
Hex 0D Hex 0A Hex 0D0A Hex 0C Hex 2C Hex 3A
If no data is
is sent to the caller and a further 15 seconds is given for a response. If no response after the second timeout the response: ERROR:TIMEXP Time out expired - Call cleared is sent to the caller and the call will be cleared by the LES. These timers also apply to the input of text when part of an EGC, message submission or poll and applies to all presentation formats. Notes: 1. In batch mode, only the first timer applies. If after 30 seconds no input is received, the call will be cleared down. 2. The values of the response timers given here are as set in the factory. These timers, as well as other timers and standard prompts and responses, described in this document, may be modified on site. Users of this document should check which modifications have been made with the LES administration. 2.3 Types of User Entries and Displays The user interface has the following types of user entries and displays to the user: User Entries (Sent to the LES by the user)

Responses to LES Prompts Meta-Commands - Embedded with textual entry to provide information to the LES on how to process the entry or to request help.
User Displays (Sent by the LES to the user)
Prompts - Information indicating the next type of data a user is to enter. Prompts are suppressed when multiple correct entries are given on a single line (since the data has already been entered) and when batch mode is used. See Section 3.2 for a description of how to invoke batch mode at the PIN prompt. Prompts will be preceded by a <CRLF>, and end with a colon and a space or with a colon and a <CRLF>. Responses - Provide additional information to the user about the message entry. These include the welcome message, response to message status enquiry, and error or warning messages. There are also messages responding to user help requests, typically when .HELP is typed at a given prompt. These messages are sent to both interactive and batch users. The amount of help available is limited. Occasionally help text refers to the Domestic L-Band Mobile Data Services User Guide which LES administrations may provide for users. There are two main types of responses in response to user commands: those prefixed with ERROR: and which indicate an error condition and those prefixed with RESP: which indicates it is just a normal response. Both ERROR: and RESP: type responses are preceded and followed by a <CRLF>. If the response message, such as a DNID Status, has multiple lines, the response message is terminated with a <CRLF>.END<CRLF> . .END will never appear within the text of a message.
Multiple line responses - May be detected by the message name. Currently only RESP:MSGSTAT, RESP:EGCSTAT, and RESP:POLLSTAT have multiple lines and are produced in response of a user exercising a Message Status Enquiry command. Store and forward messages - Messages from mobiles are sent to the required destinations as soon as possible after receipt at the LES. These messages are sent via a connection established by the LES. Store and forward status - A Non Delivery Notification (NDN) is sent to a user defined address, if a message cannot be delivered to one (or more) of its destination addresses, once the final delivery outcome is known. The NDN delivery address will be the one set up by the LES operator for the user of the PIN which originated the message. A Positive Delivery Notification (PDN) will be sent to the same address used for NDN deliveries, when the final message delivery outcome is known, providing this service is enabled for the PIN user, and all deliveries are successful. Delivery notifications will not be generated if a delivery notification address has not been specified for the user. If, however, one has been specified but the address is not reachable, then the delivery notification will be delivered to an LES operator defined spill out position. If the spill out position is not reachable then the LES operator will be informed.
DNID messages - Messages retrieved by a user from a DNID file or forwarded by the LES to the users address. DNID data reports - Data reports retrieved by a user from a DNID file or forwarded by the LES to the users address.
2.4 Response Formats Many of the entries during user input are checked for validity. Upon validation the LES will return either no response or a response of the following form. Format: <CRLF> <Response_Kind><Response_Name><Space><Response_Text><CRLF> Where: <Response_Kind> is RESP: for informational or warning responses and ERROR: for error responses <Response_Name>is a text string of up to 10 alphanumeric characters which relates to the specific response being made, but whose main use is by computing equipment for detection purposes <Response_Text> consists of up to 69 characters and describes the response being made by the LES For the remainder of this document when a reference is made to a response, only <Response_Kind> and <Response_Name> will always be shown. The additional textual information which is given to the user as part of the response may be given, although it can always be found in Section 18, which provides a complete list of LES responses. Diagrams will generally show <Response_Kind> and <Response_Name> and optionally some text which further explains
6
the response meaning. Note: throughout this document angle brackets (< and >) are used to indicate to the user that what is enclosed represents the format of the data to be entered or displayed or to denote control characters. A common example is <CRLF> to indicate that a carriage return and a line feed is to be entered. The angle brackets are not entered or displayed. 2.5 Meta-Commands The interface provides meta-commands to the user to assist in controlling the interface. Some meta-commands are specific to particular user inputs and some are general to all user inputs. Meta-commands always follow a <CRLF> and start with a period .. Meta-commands always terminate with a <CRLF>. Only character sequences beginning with a period and the first character of one of the valid meta-commands shown below will be recognised as meta-commands. If the character sequence between the first and last <CRLF> is not one of those shown below the following error response will be given. ERROR:INVALMETA Invalid Meta Command During any user input where a meta-command is possible this response will be given for an invalid meta-command. This is not shown in the diagrams of the command structures. 2.5.1 Message Entry Meta-Commands The following meta-commands are used during message entry. These meta-commands are used only when information is entered using a character presentation that is non-binary, i.e. IA5. Acceptable abbreviations are shown in parenthesis. The user must be certain that the message text does not contain unintentional meta-commands. This also applies for message text entered as part of the EGC or poll sequence: 1. .SEND (.S, .SE, .SEN) Actions the transaction, for this signifies the completion of the entry of a message. The user will then receive a RESP:MSGACCEPT response, or an error response in case of error. 2. .RESTART (.R, .RE etc.) Clears the existing message text and restarts entry of text. The user receives the following prompt: Are you SURE? (Y or N): A positive response will be followed by the prompt: Enter Message terminated by one of the following: .SEND, .RESTART, .QUIT:<CRLF> A negative response will be followed by the prompt: Continue Message: 3. .QUIT (.Q, .QU, .QUI) Prompts the user with: Are you SURE? (Y or N): A positive response results in any message text and other information entered as part of a service selection sequence being discarded and the user being brought back to the main menu and invited to make another selection.
A negative response will be followed by the prompt: Continue Message: 4. .HELP (.H, .HE, .HEL) Provides the user with a description of the other metacommands. The help text provided depends on whether or not message text has already been entered. After the help text the following prompt is given: Enter <CR> to continue: After the user has entered <CR>, if no message text has yet been entered, the following prompt is given: Enter Message terminated by one of the following: .SEND, .RESTART, .QUIT:<CRLF> After the user has entered <CR>, if some message text has been entered, the following prompt is given: Continue Message: 2.5.2 Other Specific Meta-Commands The following meta-commands may be used at specific prompts only, to invoke a different command structure or cause a different command action. Acceptable abbreviations are shown in parenthesis. 2.5.3 General Meta-Commands .HELP and .QUIT can be given as a response to any command prompt, except when trying to access the LES through entering PIN and Password, or where binary message submission is required, although this is not shown in the diagrams of the command structures. If .HELP is entered the user is provided with help text indicating the type of response required for the prompt given. If no additional help is available the user will receive the message: No Additional Help is Available In either case the user will then receive the following prompt: Enter <CR> to continue: followed by a repetition of the command prompt after the <CR> is entered. If .QUIT is entered during a selection sequence the user is returned to the main menu, and if entered whilst in the main menu, the call is cleared and the following response is given: RESP:QUIT User has cleared call 2.5.4 Responses to Meta-Command Prompts Any response to the Enter <CR> to continue: prompt is accepted, providing it is terminated by a <CR>. Any characters typed before the <CR> will be discarded. Only Y or N responses are accepted in response to the Are you sure? (Y or N): prompt. For any other response the following error is returned with the user being allowed up to three attempts to enter the correct response: ERROR:INVALSEL Invalid Selection
8
2.6 Presentation When a user is prompted to specify presentation it is in order to define the character set used over the satellite between the LES and the Mobile. For calls submitted to the LES the character set used on the X.25 or PSTN terrestrial networks will be IA5 or data (binary). The specification of Binary in the presentation prompt indicates to the LES that Meta-Commands will not be used and that the data will be packaged in the special format described below. The ITA2 character set is very limited in the number of characters it can support. There is no upper and lower case. Many special characters are not available. The advantage of ITA2 is because it is only a 5 bit code it requires less satellite time to transmit a message. For a message to be sent in ITA2 the following conditions must be met: The user must specify ITA2 at the presentation prompt. The Mobile must be registered to be able to accept ITA2. If these conditions are not met, the message is sent in IA5. IA5 characters that have no equivalent in ITA2 are replaced with a question mark ?. If binary presentation is selected for messages or the additional text fields in EGCs or polls, the data must be preceeded by two bytes specifying the length, and followed by a byte containing hex FF. The length bytes and hex FF byte are removed by the LES before the message is transmitted to the mobile. The final hex FF is required by the LES in order to check the length of data. See Figure 1 for the format used when binary data is sent. Bits ->8 7 6 5 4 3 2 1 Byte ----------------------1 | Length (LSB) | ----------------------2 | Length (MSB) | ----------------------3 | | | | | | | User binary data | | | | | | | ---------------------| N | Hex FF | ---------------------^ | Length in binary counted from | byte 3 through to byte N inclusive. | Note the value of length is used by | the LES to verify the hex FF position. | | | This is the message or text of EGC or polls. The maximum size permitted by the LES is explained in subsequent sections. Any checksums CRC checks must be provided by the user as an end to end application. | v
Figure 1. Special Format for Binary Data Restrictions apply to the delimiters that may be used at the prompts preceding the prompt for binary message data, to avoid possible misinterpretation of the length field should it have certain values. Table 1 states which delimiters are recommended in each mode of operation. The following notes explain why certain delimiter sequences should not be used. Curly brackets indicate possible repetition of the enclosed delimiter. In summary, <CR> is the only recommended delimiter at the prompts preceding the prompt for binary message data. During manual input from a terminal, <CR> is entered simply by pressing the return key. Notes:
9
Delimiter Sequence {<SP>}<SP> {<SP>}<CRLF> {<SP>}<CR> {<SP>}<colon> {<SP>}<comma> {<SP>}<FF>
Interactive X.29
Interactive X.25/ Non-Interactive No (1) No (4) Yes Yes Yes Yes
No (1,2) No (3) Yes No (2) No (2) No (2)
Table 1. Recommended Use of Delimiters at Prompts Before Enter Binary Message 1. If the length field happens to start with <CR>, <colon>, or <comma>, the delimiter sequence will be mistaken, and the length will be misinterpreted. 2. This delimiter sequence does not end in <CRLF>, so the Enter Message (in special Binary Data Format): prompt will not be output and the PAD parameters may not have been downloaded when the binary message data is read, so if the message data happens to contain <CR>, the data will be corrupted by the insertion of <LF> by the PAD. 3. Depending on the PAD parameters configured, the PAD may insert <LF> after the <CR>; if so, the <LF> entered as part of the delimiter sequence will be taken as the start of the length field, and the length will be misinterpreted. 4. The <LF> will be taken as the start of the length field, so the delimiter sequence will be mistaken, and the length will be misinterpreted. The following prompts may precede the prompt for binary message data, so it is at these prompts that the above restrictions apply: EGC14 EGC6 MSG2 POLL13 POLL15 POLL16 POLL18 POLL20 Download ENID Presentation Code Presentation Code Sequence Number Define Macro Encoded Message Macro Encoded Message Code Member Number Reporting Interval
2.7 Message Reference Numbers Message reference numbers are returned to the user in the RESP:MSGACCEPT response. Message reference numbers are assigned in blocks of 10 for follow on messages. Follow on messages submitted during the same session receive sequential message reference numbers. The maximum number of messages that can be submitted in a given session is ten, the first message plus nine follow on messages.
10
2.8 Command Structure Each service has a diagram that shows the command structure (Command Flow) and the possible responses for each command. Details of each command are provided in this document. Each required entry is contained in a command block in the command structure diagrams. Each command block in the command diagram has a label and number (Such as ES1 (Section 3.1), for the top Enhanced Services diagram). Blocks containing RESP: or ERROR: are response blocks and do not contain a label. Additional details of a command can be found by looking up the explanation associated with the label. Each command block is terminated with a valid separator which is not shown. Certain blocks require two separators in which case the second one is shown explicitly. For example see Command block MSG1 in Figure 16 where a <CRLF> is explicitly shown. This means two have been entered: one implied by the command block and the one shown. The LES clears the call of an interactive user after three successive data entry errors. For each such error the appropriate ERROR: response will be sent. Only when such a response is given does the data entry error count get incremented. When that count reaches three an additional error response is given before the call is cleared: ERROR:EXCEDRETRY User has exceeded maximum retries 2.9 Interactive Versus Batch Mode There are two ways of using the commands: the first is interactive mode working, and the second is batch mode working. The user signifies the mode of operation at the PIN prompt, as described in Section 3.2. In interactive mode prompts are given for all user entries, unless the user anticipates the prompts by placing multiple correct entries on the same line. If an error is detected by the LES, the input buffer is flushed and the user is prompted to enter a correct response before continuing with the command. The user will be allowed three attempts to enter a correct response before the call is cleared. The user can type ahead, although at the PIN prompt this may prevent echo being suppressed for the password prompt. In batch (non-interactive) mode no prompts are given after batch mode has been requested at the PIN prompt by appending X to the PIN (see Section 3.2). If an error is detected by the LES, the call is cleared. The input buffer is flushed just before the LES sends the final response for a command sequence. The input buffer at this time contains any data sent by the user that was not consumed during processing of the command. The user can type ahead, except at the PIN and password prompts and between the final input for one command sequence and the first input for the next command sequence. If an interactive user enters the number of a mobile which cannot be reached, perhaps because it is barred or not logged in, the LES will give a RESP: type response reporting the mobiles status and prompt for a reachable mobile number. However, from a batch user the mobile number will be accepted, and the failure reason for the unreachable mobile will be given instead in the NDN that the LES will generate when it has completed delivery of the message (successfully or not) to any reachable mobiles entered. If no reachable mobiles are entered in batch mode, the LES will generate the NDN giving the failure reasons when the message is submitted. For information
11
about NDNs, see Section 16.3. When a user connects to the LES via a PAD, the LES will attempt to download default PAD settings for interactive working. If batch mode is subsequently requested, the LES will then attempt to download default PAD settings for non-interactive or Kermit working. Refer to Section 19. For examples of batch mode submission, see Appendix A. Notes: 1. The final response for a command sequence in either mode will be a RESP: or ERROR: type message, sent by the LES on completion of the command. In this context, completion does not necessarily mean successful completion - it means completion of processing for the command by the LES. The final response is always followed by the main menu prompt or the clearing of the call. 2. When the input buffer is flushed, the LES discards any user data typed ahead or sent from a pre-prepared script that has not been consumed so far by the processing of the current command. 3. A consequence of the input buffer being flushed for batch mode working is that subsequent commands can only be correctly processed when sent after the LES has sent the final response for the previous command. Unless the batch user employs an appropriate delay or response detection mechanism during the call, he is restricted to entering only one command in a session. 4. When the user enters his PIN and password, and when access is via X.29, commands and data (in particular, large amounts of data) should not be sent until the LES banner has been received from the LES (see Figure 3), as this may prevent the X.3 PAD profile being correctly set up, thereby preventing the LES from correctly dealing with subsequent user input. 5. Batch mode working has the advantage that all data can be prepared beforehand and submitted as scripts, but it is most suitable for an end-user application able to create scripts and process responses. 6. Batch mode is preferred for binary text submission. See Section 2.6. 2.10 Response Delay to User Input After a user has input data there may be some delay before the LES responds to the user. Several more characters could be input before the LES responds. In the case of responses to prompts the LES will respond once the termination character is received. However, in the case of text input which is part of a message, EGC or poll submission, the user could enter more than the permitted maximum number of characters before the LES responds with an error. 2.11 X.29 Versus X.25 Access Users may access the LES either by a direct X.25 call or using X.29 PAD access. The network paths involved for user to/from LES, using X.25 and X.29 access, are shown in Figure 2. The user may observe small differences as a result of these different methods of access, dependant in part on how the X.29 PAD profile is set up. For example the X.29 PAD may not echo the user entered password followed by <CRLF>. This will mean that unlike with the X.25 method of access the user will not see a blank line between the password prompt and the LES banner. Another dif12
ference is in the method used for terminating a binary message submission, such as employing time-outs or special characters. A description of these differences is outside the scope of this document. X.29 users should be careful when terminating a LES session by aborting the X.29 connection (e.g. Control P and clear command). Disconnecting the session from the network in this manner does not stop the sessions activities and may have undesired effects. For example, clearing a call while deleting DNID file entries does not cancel the deletion process. Therefore, users are recommended to terminate LES sessions by selecting the quit option from the LES Main menu. This recommendation also applies to X.25 users. If an X.29 user performs line editing, whilst in an interactive session with the LES, e.g. in order to correct a typing error, the line will be rejected by the LES, with an error indicating invalid user input, if the PAD has not been set up to support line editing. The relevant parameters are not set from the LES, rather they must be explicitly set up by the user. It should also be noted that there are two distinct forms of PAD access to the LES. The first is from a terminal, connected to a modem to the PSTN network, which then dials the public PAD which is connected to the PSDN network and thus establishes a connection to the LES via that same PSDN network. The characteristics of the modem connected to the user terminal, and procedures for connecting to the public PAD can only be obtained from the PSDN network provider. Note: the messages and enhanced services are only effective in one direction, i.e. user to MES (via LES). The second form of PAD access is also from a terminal connected via a modem, to the PSTN network, but this time a PAD connected directly to the LES is dialled, (if this is a service offered by the LES). In fact the PSDN network is not used at all, although the interface between user and LES is effectively the same as if it had been used. The characteristics required of the modem connected to the user terminal, and procedures for connecting to the LES PAD is governed by the characteristics of the modem, which connects the LES PAD to the PSTN network. See Reference 5 for details of the LES PAD and Modem settings and Appendix C for guidance on setting up the users terminal, modem and software package. The latter also gives the modulation modes, error correction and compression algorithms supported by the LES Modems. As with access via a public PAD, messages and enhanced services may be sent by the user via the LES to mobiles and in addition (if supported and configured), the LES is also capable of using the LES PAD for routing messages and data reports and delivery notifications to PSTN addresses, for receipt by a users modem, terminal and software package. 2.12 Download/Deletion Originator Text In accordance with Reference 1, the LES automatically inserts a 25-character text string in front of the text entered by the user for ENID download and deletion EGCs and DNID download and deletion polls, to identify the originator of the EGC or poll. The text string is defined as follows. Format: <LES_ID><Comma><Originator_ID> Where: <LES_ID> <Comma> <Originator_ID> is a three digit number which identifies the LES, consisting of the ocean region (first digit) and the LES station number (second and third digits) is a single comma character (,) is a 21-character text string defined for the registered users PIN by the LES operator, truncated or filled with spaces if necessary
13
1. X.29 access via public PAD (PSTN &PSDN 2. X.29 access via LES PAD (PSTN) 3. X.25 access (PSDN)
X25 DRIVER
1&3 PSDN 2 3
LES
LES PAD
PUBLIC PAD
USER TERMINAL MODEM
14
1&2
2
MODEM
1&2 PSTN
MODEM
X25_Access.vsd/.eps
X.25 and X.29 access to the LES
Figure 2. Network Topology for Various Types Of X.25/X.29 LES Access
Example: 360,XYZ Co, London, Engla The maximum length of text that the user may enter for download and delete EGCs and polls is automatically reduced by 25 characters to allow the originator text to be inserted by the satellite interface just before transmission of the EGC or poll.
[ifd_x25_origin_id.stx]
2.13 Further Considerations for Computer-Based Users 1. The LES employs the DEC proprietary software package VAXPSI to handle X.25/X.29 protocols. 2. The LES conforms to all of the requirements of the mandatory X.25/X.29 features, described in the CCITT X recommendation series, Reference 3. 3. Of the optional features, the LES supports X.29 Fast Select. This permits X.29 calls to send 124 bytes of data within the call request packet, and is useful to users who wish to submit their PIN and password via call setup. Support for any other optional feature can not be assumed. 4. The LES does not support the use of the D-bit. 5. The LES does support the use of the M-bit and uses this when sending out messages to the user. The setting of the M-bit in a packet indicates that the data sent is not the last and could be used to enhance efficiency within the remote X.25 software. As far as the LES is concerned, use is made of the fact that an M-bit is detected in an incoming packet. The LES prefers data to be sent to it this way, although there is no requirement for users to set, check or use the M-bit. 6. The method employed by the LES to clear a call after making a delivery involves waiting for a pre-determined period (default 30 seconds) after the last data packet is sent, before sending a clear packet. This time may be shortened but there is then a risk with some networks that the clear packet is sent before the preceding data packets reaches their destination, thus resulting in a failed call. 7. The user calls the LES using the X.121 address supplied to it by the LES administration. 8. A user calling the LES must provide its local DTE address (address of the DTE making the call) in the call request packet. This maybe inserted by the PSDN used, but the user should confirm this with its network provider beforehand. 9. If the LES decides to reject a call setup request, no reasons are supplied, i.e. the cause code and diag code which are present in the reject packet are zeroed. 10. The process of incoming message detection by the LES is made relatively straightforward by the command structure imposed by the LES, the use of meta-commands to detect end of text message, (see Section 2.5), and the rules imposed for data presentation to detect end of binary message, (see Section 2.6). The LES expects text received via X.25/X.29 to be IA5 no parity. The LES sends out text to the X.25 user as IA5 no parity.
15
11. The LES will send a Call User Data field (CUD) during the call set up phase. If, however, a CUD is received by the LES from an X.25 terminal during the call set up phase, it will be treated as a PIN, and the user will be re-prompted to enter a PIN. It is preferred that the X.25 user does not send a CUD since it may be misinterpreted. 2.14 Delivery Reattempts If an attempt to deliver a mobile-originated message, or a delivery notification to an X.25 user fails due to a condition which may exist only temporarily, the LES will generally make further reattempts to deliver the message. The number of reattempts and the interval between them is dependent on the reason for the first failed delivery attempt, as determined by the LES. These values are set up and alterable by the LES operator. In some cases, e.g. as a result of an LES outage or switchover a message may be delivered more than once to the X.25 user. A similar mechanism applies when the LES attempts to deliver X.25/X.29 originated messages to a mobile. 2.15 Delivery of Data Reports and Messages Data Reports and Messages are sent from a mobile to a DNID address, usually as a result of previously programming a mobile to send data reports or messages, by sending the appropriate poll commands as described in Section 9. The method by which the LES processes the data reports and DNID-addressed messages for a given DNID is under the control of the LES operator. The options are as follows. Storage at the LES in a DNID file for later retrieval at the convenience of the registered user who owns the DNID. See Section 5. Immediate forwarding to an X.121 address associated with the DNID, with optional storage if forwarding fails. See Section 2.16. The format of the data reports and DNID-addressed messages is described in Section 15. 2.16 Immediate Forwarding of Data Reports and DNID-Addressed Messages Immediate forwarding is the facility which enables the LES to send data report/messages to a pre-determined X.121 address optionally associated with the DNID, as soon as the data report/message is received from a mobile. After the DNID and corresponding X.121 address have been determined, the data report/message is immediately forwarded to that address. There can be several DNIDs associated with the same X.121 address. If the X.121 address is busy as a result of other data report/messages being sent to it, the LES will queue the data report/message until the address is no longer busy for that reason, and then forward it. While there is a queue of data report/messages to be immediately forwarded to an address, the LES will keep the call connection open. When the queue becomes empty, the LES will keep the call connection open for a hold time associated with the DNID of the last data report/message that was forwarded, in case new data report/messages are received for immediate forwarding, before clearing the call. If new data report/messages are received before the hold timer expires, the hold timer is cancelled until the queue becomes empty again. The LES operator specifies the hold time for each DNID to be used with immediate forwarding, in
16
the range from zero to 99999 seconds (although the normal call clear down timer acts as a minimum hold time, to reduce the chances of the clear overtaking the data in the network). This provides the means to reduce the call connection charges for a user on the basis of their traffic model for immediate forwarding. Immediate forwarding may fail because an ordinary message, originating from the LES or elsewhere, is being delivered to that X.121 address whilst immediate forwarding is being attempted. Similarly an attempt to deliver an ordinary message by the LES to a given X.121 address may fail if the LES is currently engaged in immediate forwarding to that address. If immediate forwarding fails, the call is cleared without waiting for the hold time. For each DNID, the operator can either specify that the data report/message be stored in the DNID file, or that it be automatically deleted, should the immediate forwarding fail for a reason other than the X.121 address being busy as a result of other data report/messages being immediately forwarded to it. The facility which provides for the storage in DNID files of data report/messages that could not be immediately forwarded, also provides an automatic reattempt mechanism. This is triggered by the arrival of new data report/messages associated with the same DNID, and takes place after all the new data report/messages have been successfully forwarded. The entire contents of the DNID file are retrieved and forwarded, possibly interspersed with new data report/messages, should any be received for immediate forwarding. Forwarding of the contents of the DNID file is suspended while the new data report/messages are immediately forwarded, and then resumed when the queue of new data report/messages becomes empty again. This suspension and resumption may happen any number of times while the contents of the DNID file are being forwarded. Immediate forwarding may also be used for delivery to the PSTN address of a terminal that uses an asynchronous modem. For delivery to PSTN addresses see Appendix C for further details. Notes: 1. Users should be aware that the delivery format requires a full eight-bit transparent data path all the way from the LES to the end users application. 2. All users who wish to make use of the immediate forwarding facility for one or more of their DNIDs must provide their own special software or suitable package to process the data report/messages which are delivered to the X.121 address. 3. It is essential that the user ensures that the modem, terminal or PC and software package are set up correctly, and ready to receive data from the LES. 4. No common header is sent when an immediate forwarding call connection is opened. The format of the data report/messages for immediate forwarding is the same as for retrieval from a DNID file, which is defined in Section 15. No data is sent between them. 5. The users software must be able to handle instances where data reports and DNIDaddressed messages are received out of time order, for any DNIDs for which the operator has specified that data report/messages be stored in the DNID file should immediate forwarding fail. The reason is, the automatic retrieval and forwarding reattempt mechanism is only invoked by the LES after successful immediate forwarding of new data report/messages, and the contents of the DNID file will be older. There is also the possibility that new data report/messages will be received and immediately forwarded while the contents of the DNID file are being forwarded.
17
[ifd_x25_immediate_fwd.stx]
2.17 Clearing Calls For LES originated calls, the LES will normally expect to clear down a call after having sent the last packet of the message. Should, however, the call be cleared by other than the LES, the call will then be regarded as unsuccessful, and the message will be deemed not to have been delivered. For user originated calls, the LES will normally wait for the call to be cleared by the user, but will clear the call itself, if this has not taken place within a pre-determined period. Providing the whole message has been previously received and secured, this will still be accepted by the LES. The user should not attempt to clear a call following submission of a message, until the RESP:MSGACCEPT has been received, for that is the users cue that the LES has received and secured the message. Should the LES send or receive a clear packet before the .SEND at the end of the message text, all subsequent packets will be lost and the LES will discard the part of the message which has been received. 2.18 Delivery of Enhanced Data Reports The Enhanced Data Reporting service is intended for transferring small quantities of data from an MES. Data is transferred on a signalling channel using unreserved access. Enhanced Data Reporting differs from Data Reporting in that the entire data report is protected by a checksum and an acknowledgement is sent from the LES to the MES on successful reception of the entire enhanced data report, as determined by the data report checksum. Enhanced Data Reporting is fully compatible with the standard Data Reporting service, but provides enhanced data integrity, reliability and additional flexibility concerning addressing. Again, as for Data Reports, Enhanced Data Reports are sent from a mobile to a DNID address, usually as a result of previously programming a mobile to send data reports or messages, by sending the appropriate poll commands as described in Section 9. The method by which the LES processes the Enhanced Data Reports for a given DNID is under the control of the LES operator. The options are as follows. Storage at the LES in a DNID file for later retrieval at the convenience of the registered user who owns the DNID. See Section 5. Immediate forwarding to an X.121 address associated with the DNID, with optional storage if forwarding fails. See Section 2.16. The format of the data reports and DNID-addressed messages is described in Section 15.
18
Enhanced Services
3 ES - Enhanced Services This section describes the commands to access Enhanced Services provided by the LES. See Figure 3 for the command structure of Enhanced Services. 3.1 ES1 - User Connects to LES The user connects to the LES using the mechanism defined for the type network being used. The connection mechanism is network specific. 3.2 ES2 - Personal Identification Number Prompt: Data Type: Size: PIN: Alphanumeric 6 to 8 characters plus an X as an optional last character following the 6 to 8 character PIN. PIN is Defined No
Validation: Help Available: Additional Information:
The Personal Identification Number controls access to the LES. Certain PINs may be designated by the LES operator to be distress PINs. This means all message submissions made using these PINs are sent at distress priority, except for EGCs. For EGCs the user must still specify the priority. The call is cleared after failure to properly enter the PIN or password three times. Invalid PIN may be caused by the PIN owner being barred by the LES operator. An optional addition to the PIN is the letter X to request batch mode instead of interactive mode. The extra X is in addition to the six to eight character PIN, regardless of whether the PIN itself ends in X. See the example below. The main difference when batch mode is selected is that all subsequent prompts including the main menu are suppressed. Batch mode is designed for use by automated end-user applications creating scripts to send to the LES and processing responses from the LES, for which prompts are superfluous. Another difference is that in batch mode, although ERROR: and RESP: type responses are not in general suppressed (see Sections 2.9 and 6.1 for the exception to this), the action of the LES after giving an ERROR: response is to clear the call, not to repeat the prompt as in interactive mode. The differences between batch mode and interactive mode are described in detail in Section 2.9. For examples of batch mode submissions see Appendix A. After successful entry of the PIN and password (see Section 3.3), the LES will send a text string of up to 30 characters containing the LES banner, which is defined by the LES administration. The LES banner is neither a RESP: nor an ERROR: type message, and is sent both in batch and interactive mode. In interactive mode, the LES banner is followed by a blank line and the main menu - see Section 3.4.
19
Enhanced Services
Example: Assuming XEOROEX is defined as a PIN, and XEOROE is not defined, then entering XEOROEX XEOROEXX XEOROEXZ XEOROE Possible Responses: ERROR:INVALPIN Invalid PIN Note: this will appear after the password entry for security reasons. 3.3 ES4 - Enter Password Prompt: Data Type: Size: Validation: Help Available: Additional Information: After successful entry of the PIN (see Section 3.2) and password, the LES will send a text string of up to 30 characters containing the LES banner, which is defined by the LES administration. The LES banner is neither a RESP: nor an ERROR: type message, and is sent both in batch and interactive mode. In interactive mode, the LES banner is followed by a blank line and the main menu - see Section 3.4. For security reasons, the ERROR:INVALPIN response does not appear until after the password is entered, even if the PIN is invalid, so that an unauthorised user of the LES trying to guess a PIN and password cannot determine when he has entered a valid PIN and now only needs to guess the password. At both PIN: and Password:prompts no .QUIT or .HELP meta-commands are permitted, also for security reasons. The password and the <CRLF> which terminates it are not echoed for X.29 users - see Section 2.11. When the users password has expired, the LES will continue to allow the user to log into the system, but the LES forces the user to change his password. If the user does not successfully change the password after three attempts the call is cleared. Possible Responses: ERROR:INVALPIN Invalid PIN RESP:PASSEXP Password expired Password: Alphanumeric 6 to 10 alphanumeric characters checks for valid password No will result in an interactive session will result in a non-interactive session will be rejected as an invalid PIN will be rejected as an invalid PIN
20
0 EGC
NOTE:
IF X is used to suppress prompts, all ERROR: XXXXX responses force the call to clear.
1 to 2 DIGITS
2 DNID
6-8 ALPHANUMERIC CHARACTERS FOLLOWED BY AN OPTIONAL X. X IS IN THE LAST CHARACTER POSITION AND SUPPRESSES ALL FUTURE PROMPTS. 6-10 ALPHANUMERIC CHARACTERS
SERVICE 0 = ENHANCED GROUP CALL 2 = DNID ACCESS 4 = MESSAGE SUBMISSION
4 MSG
CAN
USER CONNECTS TO LES ES1
PIN ES2
ENTER PASSWORD LES BANNER ES4
6 = CANCEL MESSAGE 8 = MESSAGE STATUS ENQUIRY 9 = POLLING 80 = CHANGE PASSWORD 99 = QUIT 9 MAIN MENU POLL ES3 8 ENQ
ERROR: INVALPIN INVALID PIN 80 PW
21
PASSWORD EXPIRED ERROR: INVALSEL INVALID SELECTION CLEAR CALL 3rd UNSUCCESSFUL ATTEMPT ERROR: NOTAUTH USER NOT AUTHORIZED ERROR: MAXMSGS MAX FOLLOW-ON MESSAGES
99
QUIT
Enhanced Services Commands with Password

ENSERVPW.EPS 17th August 1993
Enhanced Services
Figure 3. Enhanced Services Summary with Passwords
Enhanced Services
3.4 ES3 - Selection Prompt: 0 = Enhanced Group Call 2 = DNID Access 4 = Message Submission 6 = Cancel Message 8 = Message Status Enquiry 9 = Polling 99 = Quit Service: Data Type: Size: Validation: Help Available: Numeric characters 1 to 2 digits Valid entry from selection menu User is authorized for selected service No
Possible Responses: ERROR:INVALSEL Invalid Selection ERROR:NOTAUTH User is not authorized ERROR:MAXMSGS Maximum number of follow-on messages exceeded
22
Enhanced Group Calls
4 EGC - Enhanced Group Call : Service Selection 0 This selection is used for the submission of Enhanced Group Calls. See Figures 4, 5, and 6 for the command structure of EGC submission. 4.1 EGC1 - Region Prompt: Region (0=All, 1=AOR-East, 2=POR, 3=IOR, 4=AOR-West): (Only regions supported by LES appear in prompt) Data Type: Size: Validation: Help Available: Additional information: Only those ocean regions actually supported by the LES will be displayed in the prompt. On a multiple ocean region LES, a value of 0 is interpreted to mean the ocean regions that are supported by the LES. On a single ocean region LES, a value of 0 is rejected. Possible Responses: ERROR:INVALOCEAN Invalid Region 4.2 EGC2 - Priority (C1) The priority of the EGC message is entered. This is one of the C codes described in Reference 1. Prompt: Priority (0=Routine, 1=Safety, 2=Urgent, 3=Distress): Data Type: Size: Validation: Help Available: Help Text: Routine, Safety and Urgent are all processed at the same priority level. Numeric Characters 1 digit Valid selection from Menu User is authorized distress Yes Numeric Characters 1 digit Valid menu selection Region supported by LES No. Provided by prompt
23
1 DIGIT OCEAN REGION 0 = ALL OR BOTH 1 = AOR EAST EGC 0 EGC OK 2 = POR 3 = IOR 4 = AOR WEST EGC1 INVALID VALID
1 DIGIT PRIORITY (C1) 0 = ROUTINE 1 = SAFETY 2 = URGENT 3 = DISTRESS VALID 1
EGC2
ERROR: INVALOCEAN INVALID OCEAN REGION
24
ERROR: INVALPRI INVALID PRIORITY
ERROR: NOTAUTH NOT AUTHORIZED
MAIN MENU
RESP: CONGEST CES CONGESTION
EGC Message Input Commands

EGC0.EPS 15th November 1990
Figure 4. EGC Service Command Structure
2 DIGITS
ADDRESS AS SPECIFIED FOR SERVICE CODE
C2 SERVICE CODE
00 GENERAL CALL 02 GROUP CALL 04 URGENCY MESSAGE NAV. WARNING TO RECTANGULAR AREAS 11 INMARSAT SYSTEM MESSAGE 13 COSATA WARNING
C3 ADDRESS SERVICE CODE 00 02 04 11 13 14 23 24 31 33 34 44 72 73 ADDRESS FORMAT CHARACTERS 2 5 12 2 4 10 9 10 2 9 12 10 5 7
2 DIGITS
REPETITIION CODE (C4)

SEE REPETITION TABLE IN THE SECTION DESCRIBING REPETITION CODES (EGC5)
14 SHORE TO SHIP DISTRESS ALERT TO CIRCULAR AREA 23 EGC SYSTEM MESSAGE 24 URGENCY MESSAGE. MET/NAV. WARNING TO CIRCULAR AREA 31 MET./NAV. AREA WARNING OR MET. FORECAST 33 DOWNLOAD GROUP IDENTITY 34 SAR COORDINATION TO RECTANGULAR AREA 44 SAR COORDINATION TO CIRCULAR AREA 72 CHART CORRECTION SERVICES 73 CHART CORRECTION SERVICE FOR FIXED AREA
EGC5
ERROR:INVALREP INVALID REPETITION
EGC4
25
EGC0C1 .vsd/eps
ERROR:INVALADDR INVALID ADDRESS
EGC3
ERROR:MOBBAR MOBILE BARRED
SEVICE CODES 33 AND 23 ONLY
ERROR:INVALSERV INVALID SERVICE CODE
ERROR:NOTLOG NOT LOGGED IN
ERROR:NOTAUTH NOT AUTHORISED
ERROR:NOTCOM NOT COMMISSIONED
EGC Message Input Commands (continued).
ERROR:NOTREG NOT REGISTERED
Figure 5. EGC Service Command Structure - Continued (1)
<CRLF>
1 CHARACTER DOWNLOAD COMMAND N = NEW D = DELETE EGC13 ERROR:INVALSEL INVALID SELECTION 1 OR 2 DIGITS PRESENTATION CODE (C5) 1 or 06 = ITA2 2 or 00 = IA5 3 or 07 = BINARY MAXIMUM OF 9 ITERATIONS
5 CHARACTERS DOWNLOAD EGC NUMBER EGC14

>9 Iterations
ERROR:INVALFMT INVALID FORMAT
ERROR:NOTAUTH NOTAUTHORISED
26
EGC6 ERROR:INVALPRES INVALID PRESENTATION
EGC Message Input Commands (continued)

EGC0C2.EPS Redrawn 22/03/01
ERROR:INVALFMT INVALID FORMAT CONTINUE MESSAGE EGC12
.SEND
RESP:MSGACCEPT MESSAGE ACCEPTED ERROR:TOOLONG MESSAGE LENGTH EXEEDED

ERROR:ZEROLENMSG MESSAGE LENGTH MUST BE GREATER THAN ZERO
MAIN MENU
UP TO 32640 CHARACTERS
5 ENTER MESSAGE EGC7
META COMMAND
.SEND .QUIT .RESTART .HELP
CLEAR CALL
EGC8 ERROR:TOOLONG MESSAGE LENGTH EXEEDED
5
Y
ITA2 IA5
1 CHARACTER Y or N
CLEAR CALL
MAIN MENU
.QUIT
ARE YOU SURE ? EGC9 N
BINARY
UP TO 32640 BYTES
SPECIAL FORMAT FOR BINARY DATA EGC11
NOT OK
OK RESP:MSGACCEPT MESSAGE ACCEPTED
MAIN MENU
ERROR:INVALSEL INVALID SELECTION
27
CLEAR CALL
1 CHARACTER Y or N
ERROR:TOOLONG MESSAGE LENGTH EXEEDED
.RESTART
CLEAR CALL
RESTART ARE YOU SURE ? EGC10 N
EGC Message Input Commands (continued) EGC0C3.EPS 15th November 1996
.HELP
DISPLAY HELP TEXT
4/5
Possible Responses: ERROR:INVALPRI Invalid Priority ERROR:NOTAUTH User is not authorized ERROR:CONGEST LES Congested 4.3 EGC3 - Service Code (C2) Prompt: Data Type: Size: Validation: Help Available: Additional Information: Characters are alphanumeric. Help Text: Service Prompt ---------------------------------------------------------------00 General Call 02 Group Call 04 Urgency Message, NAV warning to rectangular area 11 INMARSAT System Message 13 Coastal Warning 14 Shore Ship Distress Alert to circular area 23 EGC System Message 24 Urgency message, MET/NAV warning to circular area 31 MET NAVAREA warning or MET Forecast 33 Download Group Identity 34 SAR Coordination to rectangular area 44 SAR Coordination to circular area 72 Chart Correction Service 73 Chart Correction Service for fixed area Figure 8. Help Text for EGC Service Code - C2 Code Possible Responses: ERROR:INVALSERV Invalid Service Selection ERROR:NOTAUTH User is not authorized Service Code: Numeric Characters 2 digits Valid Selection from menu User is authorized this service Yes (See Figure 8)
28
4.4 EGC4 - Address (C3) Prompt: Data Type: Size: Validation: Help Available: Additional Information: The value for EGC4 - Address depends on that given for EGC3 - Service Code. Possible Responses: ERROR:INVALADDR Invalid Address RESP:MOBBAR Mobile Barred <Mobile Number> RESP:NOTLOG Mobile not logged into Region <Mobile Number> RESP:NOTCOM Mobile Not Commissioned <Mobile Number> RESP:NOTREG Mobile Not Registered <Mobile Number> Help Text: Service Code Address Format ---------------------------------------------------------------00 2 digit code (Must be 00) 02 ENID (5 digits) 04 DD(N/S)DDD(E/W)DDDDD (12 characters) 11 2 digit code 13 XXBB (4 characters) 14 DD(N/S)DDD(E/W)MMM (10 characters) 23 Mobile Number (9 digits) 24 DD(N/S)DDD(E/W)MMM (10 characters) 31 2 digit NAV area 33 Mobile Number (9 digits) 34 DD(N/S)DDD(E/W)DDDDD (12 characters) 44 DD(N/S)DDD(E/W)MMM (10 characters) 72 5 digit code 73 7 digit code Characters are alphanumeric (N/S) = North or South, (E/W) = East or West Example rectangular address: 12S124E10015 The southwest corner is at 12 Degrees South, and 124 Degrees East. The extent of the rectangle is 10 Degrees North and 015 degrees East. Figure 9. Help Text for EGC Address - C3 Code Address: Alphanumeric Up to 12 characters as specified in Help screen. Proper format for service selection ENIDs are 00000 to 65535. Yes (Figure 9)
29
4.5 EGC5 - Repetition Code (C4) Prompt: Data Type: Size: Validation: Help Available: Additional Information: Possible Responses: ERROR:INVALREP Invalid Repetition Code Help Text: Code Meaning ------------------------------------------------------------------01 Transmit once on receipt 11 Transmit on receipt followed by repeat 6 minutes later 61 Transmit 1 hour after initial broadcast (2 transmissions) 62 Transmit 2 hours after initial broadcast (2 transmissions) 63 Transmit 3 hours after initial broadcast (2 transmissions) 64 Transmit 4 hours after initial broadcast (2 transmissions) 66 Transmit 12 hours after initial broadcast (2 transmissions) 67 Transmit 24 hours after initial broadcast (2 transmissions) 70 Transmit 12 hours after initial broadcast 12 hours after the second broadcast (3 transmissions) 71 Transmit 24 hours after initial broadcast 24 hours after the second broadcast (3 transmissions) See your INMARSAT-C user handbook for use of Category B Repetition Codes Figure 10. C4 Repetition Help Screen - Category A Codes 4.6 EGC6 - Presentation Code (C5) Prompt: Presentation Code: 1 or 06 =ITA2, 2 or 00 =IA5, 3 or 07 =Binary: Data Type: Size: Validation: Help Available: Help Text: IA5 is the normal character set. ITA2 is less expensive than IA5, but is only supported by certain MESs. Binary requires a special input format.
30
Repetition Code: Numeric Characters 2 digits Valid Selection from menu Yes - Figure 10
Numeric Characters 1 or 2 digits Valid Menu Selection Yes
See your INMARSAT-C user handbook for details. Additional Information: See Section 2.6 for recommendations on which delimiters may be used at this prompt when submitting binary message data. The user ought to consider the consequences if ITA2 is selected. Not all mobiles support this presentation, and therefore any EGC messages sent to those mobiles in ITA2 presentation will be received as garbled. Because of this the LES will disallow Safetynet and All Ship Calls EGCs in anything other than IA5 presentation. Possible Responses: ERROR:INVALPRES Invalid Presentation 4.7 EGC7 - Enter Message Prompt: Enter Message terminated by one of the following: .SEND, .RESTART, .QUIT:<CRLF> Data Type: Size: Validation: Help Available: Help Text: The following meta commands are available: .SEND .QUIT .RESTART .HELP The previously entered text is submitted for transmission. Returns the user to the main menu. Clear the text and reenter new text. Displays additional information for each prompt. All valid IA5 characters Up to 32640 characters Message too long Yes - .HELP
Additional Information: The Help Text given above applies only to the case where no text has been entered by the user. After entering <CR> at the Enter <CR> to continue: prompt which follows, the user will be again prompted with the EGC7 prompt. The case where some text has already been entered is covered in Section 4.12. The maximum size of message text allowed is 32640 characters, reduced to 32615 characters for ENID download and delete EGCs - see Section 2.12. Note because of the buffering which takes place for X.25 submission the fact the maximum message size has been exceeded may not be flagged until after extra characters have been entered. See Section 2.10. Possible Responses: ERROR:TOOLONG Message entered is too long
31
4.8 EGC8 - Meta-Command The following Meta-commands are available: .SEND, .QUIT, .RESTART and .HELP. These commands can be exercised at any time following the Enter Message or Continue Message prompts. For a general description concerning Meta-commands refer to Section 2.5. If .S, .Q, .R, or .H is entered followed by characters which are not recognised as part of a valid meta command the response: ERROR:INVALMETA Invalid Meta Command will be given. This is followed by the EGC7 or EGC12 prompt depending on whether no text or some text has already been entered. 4.8.1 .SEND Prompt: Data Type: Size: Validation: None Alphanumeric S, SE, SEN or SEND following the ".". Valid format Message too long Message too short No
Help Available: Possible Responses:
RESP:MSGACCEPT MSG-REF: <nnnnnn> Message Accepted <yy-mm-dd/hh-mm> ERROR:TOOLONG Message entered is too long (Call is cleared) ERROR:ZEROLENMSG Message Length Must be Greater Than Zero 4.8.2 .QUIT Prompt: Data Type: Size: Validation: Help Available: Possible Responses: None Alphanumeric Q, QU, QUI or QUIT following the ".". Valid format No None
32
4.8.3 .RESTART Prompt: Data Type: Size: Validation: Help Available: Possible Responses: 4.8.4 .HELP Prompt: Data Type: Size: Validation: Possible Responses: Help text is provided which is as described in Section 4.7, for those cases where no text has been entered and Section 4.12, for those cases where some text has been entered. 4.9 EGC9 - QUIT [Are You Sure?] Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection 4.10 EGC10 - RESTART [Are You Sure?] Prompt: Data Type: Size: Validation: Help Available: Are you SURE? (Y or N): Y or N 1 character Valid selection from menu No - provided in the prompt
33
None Alphanumeric R, RE, RES etc. following the ".". Valid format No None
None Alphanumeric H, HE, HEL, HELP following the ".". Valid format
Are you SURE? (Y or N): Y or N 1 character Valid selection from menu No - provided in the prompt
Possible Responses: ERROR:INVALSEL Invalid Selection 4.11 EGC11 - Special Format for Binary The special format for binary applies as described in Section 2.6. Prompt: Data Type: Size: Validation: Binary Data:<CRLF> 8 bit bytes, parity not checked Up to 32640 bytes, see note in Section 4.7 Conforms to special format for binary Message too long Message too short No
Help Available: Additional Information:
See Section 2.6 for recommendations on which delimiters may be used at the prompts preceding this prompt when submitting binary message data. Possible Responses: RESP:MSGACCEPT MSG-REF: <nnnnnn> Message Accepted <yy-mm-dd/hh-mm> ERROR:TOOLONG Message entered is too long (Call is cleared) ERROR:ZEROLENMSG Message Length Must be Greater Than Zero ERROR:INVALFMT Invalid Format (Binary data did not match format described in Section 2.6 - Call is cleared)
34
4.12 EGC12 - Continue Message Prompt: Data Type: Size: Validation: Help Available: Help Text: New text will be added to that already entered .SEND .QUIT .RESTART .HELP The previously entered text is submitted for transmission. Returns the user to the main menu. Clear the text and reenter new text. Any message data prior to ".HELP" is retained Continue Message: All valid IA5 characters Total size of message up to 32640 characters (see note in Section 4.7), including previously entered portions of the message No Yes - .HELP
Additional Information: After entering <CR> at the Enter <CR> to continue: prompt which follows, the user will be prompted with the EGC12 prompt. 4.13 EGC13 - ENID Download Command Prompt: Data Type: Size: Validation: Help Available: ENID Download Command (N or D): Character 1 character N or D Yes
N = New ENID to download to mobile D = Delete the specified ENID Additional Information: The user must enter at least one download command otherwise this command is rejected. <CRLF> is only accepted if a valid value for EGC13 and EGC14 has already been entered, and will be taken to indicate that all ENIDs for the download command have been entered. A maximum of 5 ENIDs can be entered. After <CRLF> or a fifth ENID is entered, the command is executed. Possible Responses: ERROR:INVALSEL Invalid Selection
35
4.14 EGC14 - Download ENID Prompt: Data Type: Size: Validation: Help Available: Help Text: ENID = 5 digits between 00000 and 65535 You must have been assigned the specific ENID See your INMARSAT-C user handbook Additional Information: See Section 2.6 for recommendations on which delimiters may be used at this prompt when submitting binary message data. Possible Responses: ERROR:INVALFMT Invalid Format (Not 5 digits) ERROR:NOTAUTH User is not authorized (5 digits, but outside allowed range or not allocated to PIN) Download ENID: Numeric characters 5 characters 00000 to 65535 ENID must be owned by PIN submitting the command Yes
36
DNID Retrieval
5 DNID - DNID Retrieval : Service Selection 2 This selection is used for the retrieval of data reports and messages from DNID files stored at the LES. DNIDs are owned by PINs and a user can only make requests for DNIDs that are owned by the users PIN. See Figures 11, 12, and 13 for the command structure of DNID Retrieval. Possible Responses: RESP:OVERFLOW One or more of the DNID files have lost data ERROR:NODNID PIN has no DNIDs 5.1 DNID1 - Selection Selects the DNID function to be performed. Prompt: Select: (S = Status, R = Retrieve, D = Delete): Data Type: Size: Validation: Help Available: Help Text: Status - Provides a status report describing the condition of the DNID files. Retrieve - A command to retrieve the contents of the DNID file(s) associated with the users PIN. Delete - A command to delete contents of DNID files that are no longer required. In general, a user should delete the contents of DNID files after the data has been safely loaded to the users local equipment. Additional Information: When retrieving data reports ensure that the device which receives the data can handle the full eight-bit code range. The data report retrieval feature is designed primarily for use by computer devices. It is quite possible when control sequences are detected by terminals that this could produce untoward effects. Possible Responses: ERROR:INVALSEL Invalid Selection RESP:DNIDSTAT (See Figure 14 for details of DNID status report) S, R, or D 1 character Valid selection from menu Yes
37
DNID Retrieval
RESP: DNIDSTAT DNID STATUS
MAIN MENU
1 CHARACTER
A (ALL) OR 5 DIGITS
RANGE U = UNSEEN S = SEEN A = ALL D = DATE

DNID 3
DNID SELECTION DNID 2
1 ALPHA CHARACTER
SELECTION
2 DNID FILES OK
ERROR:INVALIDNID INVALID DNID ERROR:INVALSEL INVALID SELECTION
DNID
DNID RETRIEVAL
S DNID STATUS R RETRIEVE DATA D DELETE DATA

DNID 1
OVERFLOWED
DNID FILES
ERROR:NOTAUTH NOT AUTHORISED BY PIN RESP:OVERFLOW DNID OVERFLOW ERROR: INVALSEL INVALID SELECTION
A (ALL) OR 5 DIGITS
38
DNID2 .vsd/eps
1 CHARACTER
RANGE U = UNSEEN S = SEEN A = ALL D = DATE

DNID 10
ERROR: NODNID NO DNID
MAIN MENU
DNID TO DELETE DNID 9
DNID Retrieval Commands.
ERROR:INVALIDNID INVALID DNID ERROR:INVALSEL INVALID SELECTION
ERROR:NOTAUTH NOT AUTHORISED BY PIN
Figure 11. DNID Command Summary
U, S, A 14 CHARACTERS YY-MM-DD/HH-MM 1 D START DATE/TIME DNID4 END DATE/TIME DNID5 14 CHARACTERS YY-MM-DD/HH-MM
1 CHARACTER K or D PROTOCOL 4 DNID6
ERROR: INVALSEL INVALID SELECTION
ERROR: INVALTIM INVALID DATE/TIME
ERROR: INVALTIM INVALID DATE/TIME
RESP: NODATA NO DATA
MAIN MENU
U, S, A 14 CHARACTERS YY-MM-DD/HH-MM 2 D START DATE/TIME DNID11 END DATE/TIME DNID12 14 CHARACTERS YY-MM-DD/HH-MM
1 CHARACTER Y or N ARE YOU SURE ? DNID13 N
39
DNID2C1.EPS 24th November 1992
RESP: DATADEL DATA DELETED
MAIN MENU
ERROR: INVALSEL INVALID SELECTION ERROR: INVALTIM INVALID DATE/TIME ERROR: INVALTIM INVALID DATE/TIME
RESP: NODATA NO DATA
MAIN MENU
DNID Retrieval Commands (continued)

DNID Retrieval
Figure 12. DNID Command Summary - Continued (1)
DNID Retrieval
KERMIT PROTOCOL
1 CHARACTER Y or N
DNID 7
RETRIEVE
4
DATA
RESP:RETRCOMP RETRIEVE COMPLETED
DATA TO BE DELETED? DNID 8
RESP:DATADEL DATA DELETED
MAIN MENU
FILE TRANSFER ERROR:INVALSEL INVALID SELECTION
DNID Retrieval Commands DNID2C2 .vsd/eps
(continued).
40
Figure 13. DNID Command Summary - Continued (2)
DNID Retrieval
5.2 DNID2 - DNID Selection Prompt: Data Type: Size: Validation: Help Available: Help Text: If the ALL option is selected, the data records are retrieved in the order in which the data records arrived at the LES regardless of DNID. Possible Responses: ERROR:INVALDNID Invalid DNID (DNID entered not between 00000 and 65535) ERROR:NOTAUTH User is not authorized (DNID does not belong to PIN or not known by LES) 5.3 DNID3 - Range This entry provides the range of DNIDs that can be selected for retrieval. Prompt: Range: (U = Unseen, S = Seen, A = All Reports, D = Date): Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection RESP:NODATA No reports in DNID files U, S, A, D 1 character Valid menu selection No. Provided in prompt. Enter DNID number or A for ALL DNID files: Numeric Characters or A (for ALL) 1 to 5 digits DNID is valid format DNID is owned by PIN Yes
41
DNID Retrieval
Format: <CRLF> RESP:DNIDSTAT<CRLF> DNID STATUS RESPONSE:<Date_Time><CRLF> TOTAL REPORTS:<NNNNNN><CRLF> TOTAL FREE SPACE:<NNNNNN><CRLF> TOTAL SIZE:<NNNNNNN><CRLF> LAST DOWNLOAD:<Date_Time><CRLF> <CRLF> DNID:<NNNNN><CRLF> DNID STATUS:<DNID_Status><CRLF> LATEST REPORT:<Date_Time><CRLF> EARLIEST REPORT:<Date_Time><CRLF> TOTAL REPORTS:<NNNNNN><CRLF> NUMBER SEEN:<NNNNNN><CRLF> NUMBER UNSEEN:<NNNNNN><CRLF> TOTAL SIZE:<NNNNNNN><CRLF> <CRLF> DNID:<NNNNN><CRLF> DNID STATUS:<DNID_Status><CRLF> LATEST REPORT:<Date_Time><CRLF> EARLIEST REPORT:<Date_Time><CRLF> TOTAL REPORTS:<NNNNNN><CRLF> NUMBER SEEN:<NNNNNN><CRLF> NUMBER UNSEEN:<NNNNNN><CRLF> TOTAL SIZE:<NNNNNNN><CRLF> .END<CRLF> Where: <Date_Time> is date and time in YY-MM-DD/HH-MM format - if DNID STATUS: is Lost Data Reports then the time of the latest data report is the time when the first overflow occurred <NNNNN> is the DNID number - up to 20 DNIDs can be allocated to one PIN <DNID_Status> is OK or Lost Data Reports <NNNNNN> or <NNNNNNN> is a six or seven digit number, respectively
Note: where there is more than one DNID, the lines from <CRLF>DNID: to TOTAL SIZE: are repeated for each DNID associated with the PIN. Figure 14. DNID Status Report Format
42
DNID Retrieval
Example: RESP:DNIDSTAT DNID STATUS RESPONSE:90-10-10/12-02 TOTAL REPORTS:000013 TOTAL FREE SPACE:0032000 TOTAL SIZE:0000658 LAST DOWNLOAD:90-02-12/09-35 DNID:50000 DNID STATUS:OK LATEST REPORT:90-04-12/12-09 EARLIEST REPORT:90-06-30/02-02 TOTAL REPORTS:000003 NUMBER SEEN:000001 NUMBER UNSEEN:000002 TOTAL SIZE:0000078 DNID:50001 DNID STATUS:OK LATEST REPORT:90-11-19/12-09 EARLIEST REPORT:90-01-12/02-02 TOTAL REPORTS:000010 NUMBER SEEN:000000 NUMBER UNSEEN:000010 TOTAL SIZE:0000260 .END Figure 15. Example DNID Status Report
43
DNID Retrieval
5.4 DNID4 - Start Date/Time The starting date and time for the retrieval. Prompt: Data Type: Size: Validation: Help Available: Additional Information: Years specified as between 00 and 89 will be considered as between 2000 and 2089, not 1900 and 1989. Possible Responses: ERROR:INVALDATE Invalid Date/Time 5.5 DNID5 - End Date/Time The ending date for the retrieval. Prompt: Data Type: Size: Validation: Help Available: Additional Information: Years specified as between 00 and 89 will be considered as between 2000 and 2089, not 1900 and 1989. Possible Responses: ERROR:INVALDATE Invalid Date/Time RESP:NODATA No reports in DNID files End Date/Time (YY-MM-DD/HH-MM): Numeric Characters plus "-" and "/" characters e.g. 18 Feb 1990, 23.43 hours = 90-02-18/23-43 14 characters Valid Format No. Provided in prompt Start Date/Time (YY-MM-DD/HH-MM): Numeric Characters plus "-" and "/" characters, e.g. 18 Feb 1990, 23.42 hours = 90-02-18/23-42 14 characters Valid Format No. Provided in prompt
44
DNID Retrieval
5.6 DNID6 - Protocol This prompt allows the user to specify if the Kermit protocol is to be used. Direct retrieve means that the records are transmitted without any overlaying file transfer protocol such as Kermit. The data reports and messages are transferred in the format as shown in Sections 15.1 and 15.2. It is assumed that the error detection and retransmission provided by X.25 or by error correcting modems for asynchronous lines will ensure data integrity. It is the responsibility of the user to store and manage the information at the users local computer equipment. Prompt: Protocol: Data Type: Size: Validation: Help Available: Help Text: Kermit is a file transfer protocol which must be on the local machine. See your INMARSAT-C user handbook for further details. Possible Responses: ERROR:INVALSEL Invalid Selection RESP:RETRCOMP DNID retrieval complete 5.7 DNID7 - Kermit Protocol At this point user enters the Kermit environment. See Appendix B for details of prompts and responses. 5.8 DNID8 - Data to be Deleted Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection RESP:DATADEL Data deleted Data to be deleted? Y or N 1 character Valid selection from menu No - provided in the prompt (Y or N): (D = Direct, K = Kermit): Alphabetic, D or K 1 character Valid menu selection Yes
45
DNID Retrieval
5.9 DNID9 - DNID to Delete This prompt allows the user to delete selected records from the DNID files. Prompt: Data Type: Size: Validation: Enter DNID number or A for ALL DNID files: Numeric Characters 5 digits Range of 00000 to 65535 DNID is valid format DNID not authorized by PIN No. Provided in Prompt
ERROR:INVALDNID Invalid DNID (DNID entered not between 00000 and 65535) ERROR:NOTAUTH User is not authorized (DNID does not belong to PIN or not known by LES) 5.10 DNID10 - Range This entry provides the range of DNIDs that can be selected for deletion. Prompt: Range: (U = Unseen, S = Seen, A = All Reports, D = Date): Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection RESP:NODATA No reports in DNID files U, S, A, D 1 character Valid menu selection No. Provided in prompt.
46
DNID Retrieval
5.11 DNID11 - Start Date/Time The starting date and time for the deletion. Prompt: Data Type: Size: Validation: Help Available: Additional Information: Years specified as between 00 and 89 will be considered as between 2000 and 2089, not 1900 and 1989. Possible Responses: ERROR:INVALDATE Invalid Date/Time 5.12 DNID12 - End Date/Time The ending date and time for the deletion. Prompt: Data Type: Size: Validation: Help Available: Additional Information: Years specified as between 00 and 89 will be considered as between 2000 and 2089, not 1900 and 1989. Possible Responses: ERROR:INVALDATE Invalid Date/Time RESP:NODATA No reports in DNID files End Date/Time (YY-MM-DD/HH-MM): Numeric Characters plus "-" character, e.g. 18 Feb 1990, 23.42 hours = 90-02-18/23-42 14 characters Valid Format No. Provided in prompt Start Date/Time (YY-MM-DD/HH-MM): Numeric Characters plus "-" character, e.g. 18 Feb 1990, 23.42 hours = 90-02-18/23-42 14 characters Valid Format No. Provided in prompt
47
DNID Retrieval
5.13 DNID13 - Are You Sure? Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection RESP:DATADEL Data deleted Are you SURE? (Y or N): Y or N 1 character Valid selection from menu No - provided in the prompt
48
Message Submission
6 MSG - Message Submission : Service Selection 4 This section describes how user messages are submitted to the LES. Message submission can be used for single messages or multiaddress messages. The end of addressing is indicated by entering <CRLF> when prompt for the next mobile number is given. See Figures 16 and 17 for the command structure of Message Submission. Possible Responses: ERROR:CONGEST LES Congested ERROR:NOTAUTH User is not authorized 6.1 MSG1 - Mobile Number Prompt: Data Type: Size: Validation: Help Available: Help Text: The Mobile Number is the 9 digit INMARSAT number It must start with the number 4 for Standard C. the user will continue to be prompted for Mobile return/line feeds are submitted in succession or entered. Additional Information: In interactive mode, if the user enters the number of a mobile which cannot be reached, perhaps because it is barred or not logged in, the LES will give a RESP: type response reporting the mobiles status and prompt for a reachable mobile number. This does not count against the maximum of 20 mobiles for multi-addressed messages. However, if an unreachable mobile number is entered three times in succession, the call is cleared. In batch mode, all mobile numbers in the correct format are accepted regardless of their status, and unreachable mobile numbers are counted against the maximum of 20 mobiles for multi-addressed messages. If a mobile number is not in the correct format, the error response ERROR:INVALMOB is given and the call is cleared. The failure reasons for the unreachable mobiles will be given in the NDN that the LES will generate when it has completed delivery of the message (successfully or not) to any reachable mobiles entered. If no reachable mobiles are entered, the LES will generate the NDN giving the failure reasons when the message is submitted. For information about NDNs, see Section 16.3. Note that <CRLF> can not be replaced by a <CR> or <LF>. that is unique to each mobile. For normal message submission, Number until two carriage until 20 mobile numbers are 9 Digit Mobile Number: Numeric Characters 9 digits Valid Format Yes
49
Message Submission
9 DIGITS STARTING WITH 4 4 MSG MSG 1 ADDITIONAL MOBILE NUMBER ERROR:INVALPRES INVALID PRESENTATION MOBILE NUMBER PRESENTATION PRESENTATION 1=ITA2 2=IA5 3=BINARY MSG2
MAIN MENU
ERROR:CONGEST CONGESTION
ERROR:INVALMOB INVALID MOBILE NUMBER
ERROR:NOTAUTH NOT AUTHORIZED
ERROR:NOMOBILE NO MOBILE
RESP:NOTLOG NOT LOGGED IN
50
Message Submission Commands MSGSUM4.EPS 15th November 1996
RESP:MOBBAR MOBILE BARRED
RESP:NOTCOM NOT COMMISSIONED
RESP:NOTREG NOT REGISTERED
Figure 16. Message Submission Command Summary
ERROR:INVALFMT INVALID FORMAT CONTINUE MESSAGE MSG8
.SEND

MAIN MENU
3 ENTER MESSAGE MSG3
META COMMAND
CLEAR CALL
MSG4
3
Y
ITA2, IA5
1 CHARACTER Y or N
CLEAR CALL
MAIN MENU
.QUIT
ARE YOU SURE ? MSG5 N
BINARY
UP TO 32640 BYTES
SPECIAL FORMAT FOR BINARY DATA MSG7
NOT OK
MAIN MENU
51
4
CLEAR CALL
1 CHARACTER Y or N
.RESTART
CLEAR CALL
RESTART ARE YOU SURE ? MSG6 N
4
.HELP
Message Submission Commands (continued) MSGSUM4C1.EPS 30th July 1996
DISPLAY HELP TEXT
2/3
Message Submission
Figure 17. Message Submission Command Summary - Continued (1)
Message Submission
Possible Responses: ERROR:INVALMOB Invalid Mobile Number ERROR:NOMOBILE User must enter a mobile RESP:MOBBAR Mobile Barred <Mobile Number> RESP:NOTLOG Mobile not logged into Region <Mobile Number> RESP:NOTCOM Mobile Not Commissioned <Mobile Number> RESP:NOTREG Mobile Not Registered <Mobile Number> 6.2 MSG2 - Presentation See Section 2.6 if the binary option is selected. Prompt: Presentation Code (1 or 06 = ITA2, 2 or 00 = IA5, 3 or 07 = Binary): Data Type: Size: Validation: Help Available: Help Text: IA5 is the normal character set. ITA2 is less expensive than IA5, but is only supported by certain MESs. Binary requires a special input format. See your INMARSAT-C user handbook for details. Additional Information: See Section 2.6 for recommendations on which delimiters may be used at this prompt when submitting binary message data. Possible Responses: ERROR:INVALPRES Invalid Presentation Numeric Characters 1 or 2 digits Valid Menu Selection Yes
52
Message Submission
6.3 MSG3 - Enter Message Prompt: Enter Message terminated by one of the following: .SEND, .RESTART, .QUIT:<CRLF> Data Type: Size: Validation: Help Available: Help Text: The following meta commands are available: .SEND .QUIT .RESTART .HELP The previously entered text is submitted for transmission. Returns the user to the main menu. Clear the text and reenter new text. Displays additional information for each prompt. All valid IA5 characters 1 to 32640 characters Message too long Yes - .HELP
Additional Information: The Help Text given above applies only to the case where no text has been entered by the user. After entering <CR> at the Enter <CR> to continue: prompt which follows, the user will be again prompted with the MSG3 prompt. The case where some text has already been entered is covered in Section 6.8. Possible Responses: ERROR:TOOLONG Message entered is too long 6.4 MSG4 - Meta-Commands The following Meta-commands are available: .SEND, .QUIT, .RESTART and .HELP. These commands can be exercised at any time following the Enter Message or Continue Message prompts. For a general description concerning Meta-commands refer to Section 2.5. If .S, .Q, .R, or .H is entered followed by characters which are not recognised as part of a valid meta command the response: ERROR:INVALMETA Invalid Meta Command will be given. This is followed by the MSG3 or MSG8 prompt depending on whether no text or some text has already been entered.
53
Message Submission
6.4.1 .SEND Prompt: Data Type: Size: Validation: None Alphanumeric S, SE, SEN or SEND following the ".". Valid format Message too long Message too short No
RESP:MSGACCEPT MSG-REF: <nnnnnn> Message Accepted <yy-mm-dd/hh-mm> ERROR:TOOLONG Message entered is too long (Call is cleared) ERROR:ZEROLENMSG Message Length Must be Greater Than Zero 6.4.2 .QUIT Prompt: Data Type: Size: Validation: Help Available: None Alphanumeric Q, QU, QUI or QUIT following the ".". Valid format No
Possible Responses: None
6.4.3 .RESTART Prompt: Data Type: Size: Validation: Help Available: None Alphanumeric R, RE, RES etc. following the ".". Valid format No
Possible Responses: None
54
Message Submission
6.4.4 .HELP Prompt: Data Type: Size: Validation: Possible Responses: Help text is provided which is as described in Section 6.3, for those cases where no text has been entered and Section 6.8, for those cases where some text has been entered. 6.5 MSG5 - QUIT [Are You Sure?] Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection 6.6 MSG6 - RESTART [Are You Sure?] Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection Are you SURE? (Y or N): Y or N 1 character Valid selection from menu No - provided in the prompt Are you sure? (Y or N): Y or N 1 character Valid selection from menu No - provided in the prompt None Alphanumeric H, HE, HEL, HELP following the ".". Valid format
55
Message Submission
6.7 MSG7 - Special Format for Binary The special format for binary applies as described in Section 2.6. Prompt: Data Type: Size: Validation: Binary Data:<CRLF> 8 bit bytes, parity not checked 1 to 32640 characters Conforms to the special format for binary Message too long Message too short No
See Section 2.6 for recommendations on which delimiters may be used at the prompts preceding this prompt when submitting binary message data. Possible Responses: RESP:MSGACCEPT MSG-REF: <nnnnnn> Message Accepted <yy-mm-dd/hh-mm> ERROR:TOOLONG Message entered is too long (Call is cleared) ERROR:ZEROLENMSG Message Length Must be Greater Than Zero ERROR:INVALFMT Invalid Format (The binary data did not match the format described in Section 2.6 - Call is cleared)
56
Message Submission
6.8 MSG8 - Continue Message Prompt: Data Type: Size: Validation: Help Available: Help Text: New text will be added to that already entered .SEND .QUIT .RESTART .HELP The previously entered text is submitted for transmission. Returns the user to the main menu. Clear the text and reenter new text. Any message data prior to ".HELP" is retained Continue Message: All valid IA5 characters Total size of message is 32640 characters maximum including previously entered portions of the message None Yes - .HELP
Additional Information: After entering <CR> at the Enter <CR> to continue: prompt which follows, the user will be prompted with the MSG8 prompt.
57
Message Cancellation
7 CAN - Message Cancellation : Service Selection 6 This selection allows the user to attempt to cancel any type of message submitted by a registered user: messages, polls, and EGC. See Figure 18 for the command structure for message cancellation. 7.1 CAN1 - Message Reference Number Prompt: Data Type: Size: Validation: Message Reference Number (6 digits): Numeric Characters 6 digits Valid format Message owned by PIN (this check is done after date/time is submitted) Yes
Help Available: Help Text:
The LES cannot guarantee that the message will be cancelled. If the message is cancelled an NDN will be returned to the message originator showing reason as cancelled by originator. Possible Responses: ERROR:INVALFMT Invalid Format 7.2 CAN2 - Date/Time Submitted Prompt: Data Type: Size: Validation: Help Available: Help Text: The time must be within +/- one hour of the original message submission time. Additional Information: When the RESP:MSGCAN response appears, in order to confirm that the cancellation has taken effect it is suggested that the user should perform a status enquiry on the message which has been cancelled. There may be instances, for example, when a message is in the process of being delivered when the cancellation request is accepted. When a message, EGC or poll is cancelled the LES will attempt to send an NDN to confirm the cancellation. Date/Time of original message (YY-MM-DD/HH-MM): Numeric Characters except for "-" and "/" separators 14 characters including "-" and "/" separators Valid date and time Yes.
58
6 DIGITS MESSAGE REFERENCE NUMBER CAN 1
14 CHARACTERS YY-MM-DD/HH-MM
CAN
6 MESSAGE CANCELLATION
DATE/TIME SUBMITTED CAN2

RESP: MSGCAN REQUEST ACCEPTED
MAIN MENU
ERROR: INVALFMT INVALID FORMAT
ERROR: INVALDATE INVALID DATE
RESP: MSGNOTCAN MESSAGE CANNOT BE CANCELLED
MAIN MENU
59
Message Cancellation Commands

MSGCAN6.EPS 25 AUGUST 1992
Figure 18. Message Cancellation Command Structure
It is possible to tell the LES to cancel a Category B EGC automatically at some time in the future. To do this the time entered must be after the current time and more than one hour after the submission time of the message. 1. Cancellation will then take place automatically at the time entered. 2. To allow for the possibility of delay in transmitting EGCs it is recommended that the time entered for a future cancellation should be just before the time of the next scheduled delivery after the final delivery that is actually required to be made. (If the future cancellation and scheduled delivery times are the same, cancellation takes precedence over transmission.) 3. If the time entered is within one hour either side of the submission time of the message, cancellation will occur immediately, as normal. 4. The future cancellation time can be changed either forwards or backwards by entering further future cancellation requests, at any time before the future cancellation takes place. 5. An immediate cancellation request can also be made at any time before the future cancellation takes place. The response RESP:MSGNOTCAN MSG-REF: <nnnnnn> Message cannot be cancelled should be interpreted as meaning one of the following. 1. The message delivery has already completed successfully. 2. The message delivery has already been cancelled. 3. The message delivery has already completed unsuccessfully. 4. The message reference number does not exist. 5. The combination of message reference number and date/time entered do not identify a message associated with the PIN used. 6. Cancellation in the future was requested for a message that is not a Category B EGC. Possible Responses: ERROR:INVALDATE Invalid Date/Time RESP:MSGCAN Request Accepted RESP:MSGNOTCAN MSG-REF: <nnnnnn> Message cannot be cancelled
60
Message Status Enquiry
8 ENQ - Message Status Enquiry : Service Selection 8 Message Status enquiries are used to check the status of EGC messages, polls, or messages. See Figure 19 for the command structure of Message Status Enquiry. 8.1 ENQ1 - Message Reference Number Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALFMT Invalid Format 8.2 ENQ2 Date/Time Submitted Prompt: Data Type: Size: Validation: Help Available: Help Text: The time must be within +/- one hour of the original message submission time. Possible Responses: ERROR:INVALDATE Invalid Date/Time 8.3 ENQ3 - Select Status Prompt: Data Type: Size: Validation: Help Available: Select Status (A=All, N=Nondelivered): Alphabetic: A or N 1 character Valid Selection from menu Messages owned by PIN No. Provided in the prompt. Date/Time of original message (YY-MM-DD/HH-MM): Numeric Characters except for "-" and "/" separators 14 characters including "-" and "/" separators Valid date and time Yes. Message Reference Number (6 digits): Numeric Characters 6 digits Valid format Message owned by PIN after the date/time is submitted No. Provided in Prompt.
61
Possible Responses: ERROR:INVALSEL Invalid Selection RESP:UNKN MSG-REF: <nnnnnn> No record of message (Note: this response is also given if the user is not authorized to know about this message.) RESP:MSGSTAT (See Figure 20 for the response to a status request for a message) RESP:POLLSTAT (See Figure 22 for the response to status request for a poll) RESP:EGCSTAT (See Figure 24 for the response to a status request for an EGC message)
62
RESP: EGCSTAT EGC STATUS 6 DIGITS MESSAGE REFERENCE NUMBER ENQ1 14 CHARACTERS YY-MM-DD / HH-MM DATE/TIME SUBMITTED ENQ2 ENQ3 1 CHARACTER SELECT STATUS A = ALL N = NON DELIVERED
ENQ
8 MESSAGE STATUS ENQUIRY
RESP: MSG STAT MESSAGE STATUS
MAIN MENU
ERROR: INVALDATE INVALID DATE
RESP: POLLSTAT POLL STATUS
63
MSGENQ8.EPS 15th November 1990
RESP: UNKN NO RECORD OF MESSAGE
Message Status Enquiry Commands
Figure 19. Message Status Enquiry Command Structure
Format: <CRLF> RESP:MSGSTAT<CRLF> STATUS RESPONSE:<YY-MM-DD/HH-MM><CRLF> MSG REF:<NNNNNN><CRLF> <CRLF> MOBILE NUMBER:<NNNNNNNNN ><CRLF> OCEAN REGION:<XXXX><CRLF> STATUS:<The_Status><CRLF> REASON:<The_Reason><CRLF> DELIVERY ATTEMPTS:<NNNN><CRLF> <CRLF> MOBILE NUMBER:<NNNNNNNNN><CRLF> OCEAN REGION:<XXXX><CRLF> STATUS:<The_Status><CRLF> REASON:<The_Reason><CRLF> DELIVERY ATTEMPTS:<NNNN><CRLF> .END<CRLF> Where: <XXXX> is AORE, AORW, IOR, POR, UNK <NNNN> is a 4 digit number. <NNNNNN> is the 6 digit message reference number. <NNNNNNNNN> is the 9 digit mobile number. <The_Status> is Delivered, Attempting Delivery, Failed or Cancelled <The_Reason> is <Success_Reason> or <Failure_Reason> <Success_Reason> is blank - REASON:is still present to facilitate automatic processing of message status enquiry responses <Failure_Reason> is the non-delivery reason, up to 40 characters - see Section 17 <YY-MM-DD/HH-MM> is the current date and time Note: for multi-addressed messages, the lines from <CRLF>MOBILE NUMBER: to DELIVERY ATTEMPTS: are repeated for each delivery associated with the message reference number. Figure 20. Message Status Enquiry Response for Messages
64
Example: RESP:MSGSTAT STATUS RESPONSE:90-03-09/23-04 MSG REF:000222 MOBILE NUMBER:489798476 OCEAN REGION:POR STATUS:Failed REASON:SD Mobile Failed To Respond DELIVERY ATTEMPTS:0003 MOBILE NUMBER:481234567 OCEAN REGION:IOR STATUS:Delivered REASON: DELIVERY ATTEMPTS:0001 .END Figure 21. Message Status Enquiry Response Example for Messages
65
Format: <CRLF> RESP:POLLSTAT<CRLF> STATUS RESPONSE:<YY-MM-DD/HH-MM><CRLF> MSG REF:<NNNNNN><CRLF> <CRLF> OCEAN REGION:<XXXX><CRLF> STATUS:<The_Status><CRLF> REASON:<The_Reason><CRLF> <CRLF> OCEAN REGION:<XXXX><CRLF> STATUS:<The_Status><CRLF> REASON:<The_Reason><CRLF> .END <CRLF> Where: <XXXX> is AORE, AORW, IOR, POR, UNK <NNNNNN> is the 6 digit message reference number. <The_Status> is Complete, Attempting Delivery, Failed, or Cancelled <The_Reason> is <Success_Reason> or <Failure_Reason> <Success_Reason> is blank - REASON: is still present to facilitate automatic processing of message status enquiry responses <Failure_Reason> is the non-delivery reason, up to 40 characters - see Section 17 <YY-MM-DD/HH-MM> is the current date and time. Note: for polls to multiple ocean regions, the lines from <CRLF>OCEAN REGION: to REASON: are repeated for each ocean region to which the poll was addressed. Figure 22. Message Status Enquiry Response for Polls
66
Example: RESP:POLLSTAT STATUS RESPONSE:90-03-09/23-04 MSG REF:000222 OCEAN REGION:POR STATUS:Cancelled REASON:Cancelled by user OCEAN REGION:IOR STATUS:Complete REASON: .END Figure 23. Message Status Enquiry Response Example for Polls
67
Format: <CRLF> RESP:EGCSTAT<CRLF> STATUS RESPONSE:<YY-MM-DD/HH-MM><CRLF> MSG REF:<NNNNNN><CRLF> <CRLF> OCEAN REGION:<XXXX><CRLF> STATUS:<The_Status><CRLF> REASON:<The_Reason><CRLF> COMPLETED BROADCASTS:<NNNN><CRLF> OUTSTANDING BROADCASTS:<NNNN><CRLF> ESTIMATED COMPLETION:<Est_Date><CRLF> <CRLF> OCEAN REGION:<XXXX><CRLF> STATUS:<The_Status><CRLF> REASON:<The_Reason><CRLF> COMPLETED BROADCASTS:<NNNN><CRLF> OUTSTANDING BROADCASTS:<NNNN><CRLF> ESTIMATED COMPLETION:<Est_Date><CRLF> .END <CRLF> Where: <XXXX> is AORE, AORW, IOR, POR, UNK <NNNN> is a 4 digit number <NNNNNN> is a 6 digit message reference number <The_Status> is Complete, Attempting Delivery, Failed, Cancelled <The_Reason> is <Success_Reason> or <Failure_Reason> <Success_Reason> is blank - REASON:is still present to facilitate automatic processing of message status enquiry responses <Failure_Reason> is the non-delivery reason, up to 40 characters - see Section 17 <Est_Date> is the estimated completion date and time in YY-MM-DD/HH-MM format or UNSPECIFIED <YY-MM-DD/HH-MM> is the current date and time Notes: 1. For EGCs to multiple ocean regions, the lines from <CRLF>OCEAN REGION: to ESTIMATED COMPLETION: are repeated for each ocean region to which the EGC was addressed. 2. The ESTIMATED COMPLETION: field takes one of the following values: a. Category A and B, all broadcasts completed - actual time of final delivery b. Category A, broadcasts outstanding - expected time of final delivery c. Category B, broadcasts outstanding, but future cancellation pending - expected time of final delivery d. Category B, broadcasts outstanding, but no future cancellation pending UNSPECIFIED
Figure 24. Message Status Enquiry Response for EGC Messages
68
Example: RESP:EGCSTAT STATUS RESPONSE:92-08-24/13-04 MSG REF:000222 OCEAN REGION:POR STATUS:Attempting Delivery REASON:Awaiting Delivery COMPLETED BROADCASTS:0001 OUTSTANDING BROADCASTS:0001 ESTIMATED COMPLETION:92-08-24/14-00 OCEAN REGION:IOR STATUS:Attempting Delivery REASON:Awaiting Delivery COMPLETED BROADCASTS:0001 OUTSTANDING BROADCASTS:0001 ESTIMATED COMPLETION:92-08-24/14-00 .END Figure 25. Message Status Enquiry Response Example for EGC Messages
69
Polling
This page is deliberately left blank.
70
Polling
9 POLL - Polling : Service Selection 9 See Figures 26, 27, 28, 29, and 30 for the command structure of polling. The maximum amount of user data that can be entered to the LES for a poll is 233 bytes. This number is derived as follows. The maximum size poll that can be transmitted is 255 bytes. The maximum size header is for an Area poll (22 bytes), leaving 255 - 22 = 233 bytes of user data as explained in Reference 1. Length bytes and checksums for binary submission do not count against this total. They are not transmitted over the satellite. (See section 9.21 below for more specific details) The LES is not currently enabled to support the Reserved (or Pre-Assigned) Data Reporting service. Possible Responses: ERROR:CONGEST LES Congested 9.1 POLL1 - Region Prompt: Region (0=All, 1=AOR-East, 2=POR, 3=IOR, 4=AOR-West): (Only regions supported by LES appear in prompt) Data Type: Size: Validation: Help Available: Additional Information: Only those ocean regions actually supported by the LES will be displayed in the prompt. On a multiple ocean region LES, a value of 0 is interpreted to mean the ocean regions that are supported by the LES. On a single ocean region LES, a value of 0 is rejected. Possible Responses: ERROR:INVALOCEAN Invalid Region Numeric Characters 1 digit Valid menu selection Region supported by LES No. Provided by prompt
71
Polling
3 DIGITS
COMMAND 000 = SEND UNRESERVED REPORT AS REQUIRED IN RESPONSE
COMMAND
000
006
1 CHARACTER
004 = PROGRAM PERIODIC DATA REPORTING
007
005 = INITIATE PERIODIC DATA REPORTING
008
POLL TYPE G = GROUP I = INDIVIDUAL A = AREA POLL3 ERROR: INVALSEL INVALID SELECTION
009
006 = STOP PERIODIC DATA REPORTING
012
007 = DEFINE MACRO ENCODED MESSAGE
POLL
9 POLLING
008 = MACRO ENCODED MESSAGE
1 CHARACTER
005
009 = DATA TRANSMISSION
POLL TYPE G = GROUP A = AREA POLL4 ERROR: INVALSEL INVALID SELECTION
010 = DOWNLOAD DNID
72
MAIN MENU RESP:CONGEST LES CONGESTED 011 = DELETE DNID 012= USER DEFINED TEXT POLL2
010 INDIVIDUAL
004 GROUP
ERROR: INVALCMD INVALID COMMAND 011
1 CHARACTER POLL TYPE G = GROUP I = INDIVIDUAL POLL5 ERROR: INVALSEL INVALID SELECTION
ERROR: NOTAUTH NOT AUTHORISED
Polling Commands
POLL9.EPS 21st December 1995
Figure 26. Polling Command Structure
1-2 DIGITS 9 DIGITS MOBILE NUMBER <CRLF> POLL 6 0 1 2 3 4 AREA TYPE ALL SHIPS NAVAREA WMO AREA RECTANGULAR AREA CIRCULAR AREA POLL 7 INDIVIDUAL POLL ADDITIONAL MOBILE ADDRESS ERROR: INVALSEL INVALID SELECTION
2 TO 12 CHARACTERS AREA ADDRESS TYPE 1-4 1 2 3 4 POLL 8 0 ALL SHIPS (NO ADDRESS) ERROR: INVALFMT INVALID FORMAT SIZE 2 characters 3 characters 12 characters 10 characters
RESP: NOTLOG NOT LOGGED IN
RESP: MOBBAR MOBILE BARRED
AREA POLLS
ERROR: INVALMOB INVALID MOBILE No.
2 RESP: NOT AUTH NOT AUTHORISED INDIVIDUAL/GROUP POLLS
1 GROUP/AREA POLLS 1 CHARACTER OCEAN REGION 0 = ALL OR BOTH 1 = AOR EAST 2 = POR 3 = IOR 4 = AOR WEST POLL1
73
Polling Commands (continued)

POLL9C1.EPS 24 June 1991
Figure 27. Polling Command Structure - Continued (1)

Polling
Polling
5 DIGITS DNID 2 POLL9
3 DIGITS 000-255 SUB ADDRESS POLL10
1 CHARACTER Y or N
ACKNOWLEDGEMENT ?
1 CHARACTER Y or N
PRESENTATION BINARY ?
3
POLL 11 POLL 12
ERROR: NOTAUTH NOT AUTHORISED

POLL9C2.EPS 17th August 1993
74
3 DIGITS 000-127 MEM 007 DEFINE MACRO ENCODED MESSAGE MEM CODE POLL15 ERROR: INVALSEL INVALID SELECTION 000
SEND TEXT 1 SEND TEXT 1
5 CHARACTERS HH-MM 004 START TIME POLL14 ERROR: INVALTIM INVALID TIME
5 CHARACTERS HH-MM
REPORTING INTERVAL POLL 20 ERROR: INVALTIM INVALID TIME
SEND TEXT 1
1 CHARACTER
RESPONSE 0 = NO RESPONSE 1 = DATA REPORT 2 = MESSAGE TRANSFER POLL 28
3 CHARACTERS 000 to 255

SEQUENCE NUMBER POLL 13
005, 006, 011
RESP: MSGACCEPT MESSAGE ACCEPTED
MAIN MENU
3 CHARACTERS (000 to 127) 008 MEM CODE POLL 16 ERROR: INVALSEL INVALID SELECTION
SEND TEXT 1
75
POLL9C3.EPS 17th August 1993

009
SEND TEXT 3
3 CHARACTERS (000 to 255) 010 MEMBER No. POLL 18 ERROR: INVALSEL INVALID SELECTION
SEND TEXT 1

012
SEND TEXT 1
Polling
Polling
ERROR:INVALFMT INVALID FORMAT CONTINUE MESSAGE POLL27
SEND TEXT 2
.SEND, ALL OTHER COMMANDS

META COMMAND
MAIN MENU
SEND TEXT 2
CLEAR CALL
ENTER MESSAGE
NOT BINARY DATA
POLL21
POLL21 ERROR:TOOLONG MESSAGE LENGTH EXEEDED
1 CHARACTER Y or N
CLEAR CALL
MAIN MENU
.QUIT
ARE YOU SURE ? EGC9 N
BINARY DATA
SEND TEXT 1
UP TO 32640 BYTES
SPECIAL FORMAT FOR BINARY DATA POLL26
SEND TEXT 3
NOT OK
MAIN MENU
76
CLEAR CALL
1 CHARACTER Y or N
.RESTART
CLEAR CALL
RESTART ARE YOU SURE ? EGC10 N
SEND TEXT 2
ERROR:INVALSEL INVALID SELECTION DATA ENTERED

SEND TEXT 2
Polling Commands (continued) POLL9RDC4.EPS 30th October 1996
.HELP
DISPLAY HELP TEXT
NO DATA ENTERED
Polling
9.2 POLL2 - Command Refer to Reference 1 for further description of the commands available to LES users. Prompt: Data Type: Size: Validation: Command Type (e.g. 000 for ordinary poll): Numeric Characters 3 digits Valid Range (000 - 127) Valid Menu selection User is authorized service. Yes, See Figure 31 for the help screen
Note that periodic data reporting is a form of unreserved data reporting which takes place at intervals which have been specified previously in the appropriate poll commands. The commands 000 - 011 are pre defined. These have to be authorized individually for the registered user by the LES operator. The range 012 - 127 are user defined and so do not have to be authorized for the registered user. Possible Responses: ERROR:INVALCMD Invalid Command ERROR:NOTAUTH User is not authorized Help Text: Command Type Function -----------------------------------------------------------------000 Ordinary Poll for Data Report Response 001 Program Reserved Data Reporting 002 Initiate Reserved Data Reporting 003 Stop Reserved Data Reporting 004 Program Periodic Data Reporting 005 Initiate Periodic Data Reporting 006 Stop Periodic Data Reporting 007 Define Macro Encoded Message 008 Macro Encoded Message 009 Data Transmisssion 010 Down Load DNID 011 Delete DNID >= 012 Send as Submitted in text field Figure 31. Help Text for Poll Command
77
Polling
9.3 POLL3 - Poll Type This command is for command options 0, 6, 7, 8, 9, and, >= 12. Prompt: Select Poll Type (G = Group, I = Individual, A = Area): Data Type: Size: Validation: Help Available: Help Text: Group Poll is a broadcast to all mobiles in Closed Network Id. Individual Poll is received only by the addressed mobile. Area Poll is received by mobiles in the specified area. Possible Responses: ERROR:INVALSEL Invalid Selection 9.4 POLL4 - Poll Type This command is for command option 5. Prompt: Data Type: Size: Validation: Help Available: Help Text: Group Poll is a broadcast to all mobiles in Closed Network Id. Area Poll is received by mobiles in the specified area. Possible Responses: ERROR:INVALSEL Invalid Selection Select Poll Type (G = Group, A = Area): Alphabetic: G or A 1 character Valid Menu Selection Yes Alphabetic: G, I, or A 1 character Valid Menu Selection Yes
78
Polling
9.5 POLL5 - Poll Type This command is for command option 11 Delete DNID. Prompt: Data Type: Size: Validation: Help Available: Help Text: Group Poll is a broadcast to all mobiles in Closed Network Id. Individual Poll is received only by the addressed mobile. Possible Responses: ERROR:INVALSEL Invalid Selection 9.6 POLL6 - Mobile Number Prompt: Data Type: Size: Validation: Help Available: Help Text: The Mobile Number is the 9 digit INMARSAT number It must start with the number 4 for Standard C. the user will continue to be prompted for Mobile return/line feeds are submitted in succession or entered. Possible Responses: ERROR:INVALMOB Invalid Mobile Number ERROR:NOTAUTH User is not authorized (Mobile has an associated PIN which is not the one being used) RESP:MOBBAR Mobile Barred <Mobile Number> RESP:NOTLOG Mobile not logged into Region <Mobile Number> RESP:NOTCOM Mobile Not Commissioned <Mobile Number> RESP:NOTREG Mobile Not Registered <Mobile Number> that is unique to each mobile. For normal message submission, Number until two carriage until 20 mobile numbers are 9 Digit Mobile Number: Numeric Characters 9 digits Valid format Yes Select Poll Type (G = Group, I = Individual): Alphabetic: G or I 1 character Valid Menu Selection Yes
79
Polling
9.7 POLL7 - Area Type Prompt: Area Type: Data Type: Size: Validation: Help Available: Additional Information: See Figure 33 for a list of commands and address size. Possible Responses: ERROR:INVALSEL Invalid Selection Help Text: Area Type --------0 1 3 4 Description ---------------All Ships NAVAREA Rectangular Area Circular Area Figure 32. Help Text for Poll Area Type 9.8 POLL8 - Area Address Prompt: Data Type: Size: Validation: Help Available: Help Text: Possible Responses: ERROR:INVALFMT Invalid Format Area Address: Alphanumeric 2 to 12 characters Valid Format Yes See Figure 33 Numeric Characters 1 digit Valid Selection (0, 1, 3 or 4) Yes, see Figure 32 for help text.
80
Polling
Help Text: Area Type --------0 1 3 4 Address Format -----------------No address required 2 digits DD(N/S)DDD(E/W)DDDDD (12 characters) DD(N/S)DDD(E/W)MMM (10 characters) (N/S) = North or South, (E/W) = East or West Example rectangular address: 12S124E10015 The southwest corner is at 12 Degrees South, and 124 Degrees East. The extent of the rectangle is 10 Degrees North and 015 degrees East. Figure 33. Help Text for Poll Area Address 9.9 POLL9 - DNID Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALFMT Invalid Format (DNID entered not between 00000 and 65535) ERROR:NOTAUTH User is not authorized (DNID does not belong to PIN or not known by LES) 9.10 POLL10 - Subaddress Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection
81
DNID (5 digits): Numeric Characters 5 digits Valid DNID format DNID is owned by the PIN No - provided in the prompt
SubAddress (000 to 255): Numeric Characters 3 digits Valid Range 0 - 255 No - provided in prompt
Polling
9.11 POLL11 - Acknowledgement Prompt: Data Type: Size: Validation: Help Available: Help Text: If the user selects the ACK option, the MES will return an acknowledgement data report that the command was received. Possible Responses: ERROR:INVALSEL Invalid Selection 9.12 POLL12 - Presentation Prompt: Data Type: Size: Validation: Help Available: Help Text: Y = Binary, which requires a special input format. N = IA5 See your INMARSAT-C user handbook for details. Possible Responses: ERROR:INVALSEL Invalid Selection Presentation Binary? (Y/N): Characters 1 character Valid menu selection Y or N Yes Acknowledgement Option (Y/N): Characters 1 Character Valid Menu Selection Y or N. Yes
82
Polling
9.13 POLL13 - Sequence Number Prompt: Data Type: Size: Validation: Help Available: Help Text: The sequence number is returned in the data report acknowledgement packet to confirm this poll command. This allows the user to associate the sequence number of the poll command with the corresponding acknowledgement. The sequence number may be used by the MES to ignore duplicate polls. Additional Information: See Section 2.6 for recommendations on which delimiters may be used at this prompt when submitting binary message data. Managing the sequence number is the responsibility of the terrestrial user originating the poll. It is passed transparently through the LES. Sending out polls with numbers which are out of sequence could end up by the polls being ignored by the mobile(s) being addressed. Possible Responses: ERROR:INVALFMT Invalid Format Sequence Number (000 to 255): Numeric Characters 3 numeric characters Valid format Range 000 to 255 Yes
83
Polling
9.14 POLL14 - Start Time Prompt: Data Type: Size: Validation: Help Available: Help Text: The MES will not start to respond with an initial periodic data report until poll command type 5 has been sent. Additional Information: All timings are approximate because the actual timing is done on the basis of TDM frame length which is 8.64 seconds. The starting time is converted to the TDM frame number in the day that is closest to the time requested by the user. The reporting interval is converted into the number TDM frames between transmissions. After the starting time and reporting interval are converted to frame numbers, the actual starting frame is determined by randomizing over the requested reporting interval. This is to prevent particular times of day from becoming congested. The interval over which the randomization occurs is limited to a maximum of 1600 frames (approximately 4 hours) regardless of the length of the requested reporting interval. For example if a user wants to transmit once per day at 9.00 am, the actual transmission assignment will be between 9.00 am and 1.00 pm, approximately. Once the assignment is made, the transmission will occur at approximately the same time each day, typically within a few TDM frames. Note that the user who wishes data reporting to start the same day as when the command is issued must allow time for the command to be processed and sent to the mobile via the NCS. Therefore Start Time must be some time after the current time so that the current frame number when received by the mobile is less than the transmitted frame number. A data report will not be sent from a MES if it is in the process of sending or receiving a message. The exact processing of data reports varies by MES manufacturer. If for any reason a data report is lost, it is the responsibility of the user to submit a poll to request the lost data from the MES. Possible Responses: ERROR:INVALTIME Invalid Time Start Time (HH-MM): Numeric Characters plus "-" separator 5 characters Valid Format Yes
84
Polling
9.15 POLL15 - Define Macro Encoded Message This command defines a Macro encoded message to a MES. Prompt: Data Type: Size: Validation: Help Available: Help Text: This Macro Encoded Message allows you to associate a code with a text string in the MES. This allows you to send only the code instead of the entire string to the MES for frequently used messages. Possible Responses: ERROR:INVALSEL Invalid Selection 9.16 POLL16 - Macro Encoded Message Prompt: Data Type: Size: Validation: Help Available: Help Text: To use this command first define the required Macro via a POLL Command type 7. This command sends the predefined code to the MES. This code is expanded by the MES into the predefined text. Additional Information: See Section 2.6 for recommendations on which delimiters may be used at this prompt when submitting binary message data. Possible Responses: ERROR:INVALSEL Invalid Selection 9.17 POLL17 No longer used (retained to maintain numbering scheme). MEM Code (000 to 127): Numeric Characters 3 digits Valid Format Yes MEM Code (000 to 127): Numeric Characters 3 digits Valid Format Yes
85
Polling
9.18 POLL18 - Member Number Prompt: Data Type: Size: Validation: Help Available: Additional Information: See Section 2.6 for recommendations on which delimiters may be used at this prompt when submitting binary message data. Possible Responses: ERROR:INVALSEL Invalid Selection 9.19 POLL19 No longer used (retained to maintain numbering scheme). 9.20 POLL20 - Unreserved Data Reporting Interval Prompt: Data Type: Size: Validation: Reporting Interval (HH-MM): Characters 5 characters HH-MM Valid hours-minutes 00 hours to 23 hours 00 minutes to 59 minutes Yes Member Number (000 to 255): Numeric Characters 3 digits Valid Range (0 to 255) No - provided in prompt
Help Available: Help Text:
This is the appoximate starting time for periodic data reporting. See your INMARSAT-C user handbook for additional details. Additional Information: See Section 2.6 for recommendations on which delimiters may be used at this prompt when submitting binary message data. Possible Responses: ERROR:INVALTIME Invalid Time
86
Polling
9.21 POLL21 - Enter Message Prompt: Enter Message terminated by one of the following: .SEND, .RESTART, .QUIT:<CRLF> Data Type: Size: Validation: Help Available: Help Text: The following meta commands are available: .SEND .QUIT .RESTART .HELP The previously entered text is submitted for transmission. Returns the user to the main menu. Clear the text and reenter new text. Displays additional information for each prompt. IA5 characters 1 to 233 characters None Yes - .HELP
Additional Information: The Help Text given above applies only to the case where no text has been entered by the user. After entering <CR> at the Enter <CR> to continue: prompt which follows, the user will be again prompted with the POLL21 prompt. The case where some text has already been entered is covered in Section 9.27. The maximum size of message text allowed is 233 characters, which is reduced to 208 characters for DNID download polls - see Section 2.12. Note because of the buffering which takes place for X.25 submission the fact the maximum message size has been exceeded may not be flagged until after extra characters have been entered. See Section 2.10. Text entry is not permitted for the following poll command types: 001 Program Reserved Data Reporting 002 Initiate Reserved Data Reporting 003 Stop Reserved Data Reporting 005 Initiate Periodic Data Reporting 006 Stop Periodic Data Reporting 011 Delete DNID Possible Responses: ERROR:TOOLONG Message entered is too long 9.22 POLL22 - Meta-Commands The following Meta-commands are available: .SEND, .QUIT, .RESTART and .HELP. These commands can be exercised at any time following the Enter Message or Continue Message prompts. For a general description concerning Meta-commands refer to Section 2.5. If .S, .Q, .R, or .H is entered followed by characters which are not recognised as part of a valid meta command the response: ERROR:INVALMETA Invalid Meta Command
87
Polling
will be given. This is followed by the POLL21 or POLL27 prompt depending on whether no text or some text has already been entered. 9.22.1 .SEND Prompt: Data Type: Size: Validation: None Alphanumeric S, SE, SEN or SEND following the ".". Valid format Message too long Message too short No
RESP:MSGACCEPT MSG-REF: <nnnnnn> Message Accepted <yy-mm-dd/hh-mm> ERROR:TOOLONG Message entered is too long (Call is cleared)
9.22.2 .QUIT Prompt: Data Type: Size: Validation: Help Available: Possible Responses: 9.22.3 .RESTART Prompt: Data Type: Size: Validation: Help Available: Possible Responses: None Alphanumeric R, RE, RES etc. following the ".". Valid format No None None Alphanumeric Q, QU, QUI or QUIT following the ".". Valid format No None
88
Polling
9.22.4 .HELP Prompt: Data Type: Size: Validation: Possible Responses: Help text is provided which is as described in Section 9.21, for those cases where no text has been entered and Section 9.27, for those cases where some text has been entered. 9.23 POLL23 No longer used (retained to maintain numbering scheme). 9.24 POLL24 - QUIT [Are You Sure?] Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection 9.25 POLL25 - RESTART [Are You Sure?] Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection Are you sure? (Y or N): Y or N 1 character Valid selection from menu No - provided in the prompt Are you sure? (Y or N): Y or N 1 character Valid selection from menu No - provided in the prompt None Alphanumeric H, HE, HEL, HELP following the ".". Valid format
89
Polling
9.26 POLL26 - Special Format for Binary The special format for binary applies as described in Section 2.6 Prompt: Data Type: Size: Validation: Help Available: Additional Information: See Section 2.6 for recommendations on which delimiters may be used at the prompts preceding this prompt when submitting binary message data. Possible Responses:
RESP:MSGACCEPT MSG-REF: <nnnnnn> Message Accepted <yy-mm-dd/hh-mm> ERROR:TOOLONG Message entered is too long (Call is cleared) ERROR:INVALFMT Invalid Format (Binary data did not match format described in Section 2.6 - Call is cleared)
Binary Data:<CRLF> 8 bit bytes, parity not checked 1 to 233 bytes (excluding length bytes and FF terminator) Check that the message is between 1 and 233 byte size. Conforms to the special format for binary. No
9.27 POLL27 - Continue Message Prompt: Data Type: Size: Validation: Help Available: Help Text: New text will be added to that already entered .SEND .QUIT .RESTART .HELP The previously entered text is submitted for transmission. Returns the user to the main menu. Clear the text and reenter new text. Any message data prior to ".HELP" is retained Continue Message: All valid IA5 characters Total size of poll data is 233 characters maximum including previously entered portions of the message None Yes - .HELP
Additional Information: After entering <CR> at the Enter <CR> to continue: prompt which follows, the user will be prompted with the POLL27 prompt.
90
Polling
9.28 POLL28 - Response This field permits the user to specify the type of response desired in response to the poll. The three possibilities are: No Response A Data Report sent on the signalling channel A message sent on the message channels. The actual action taken depends on the Mobile to which the poll is sent. Prompt: Data Type: Size: Validation: Help Available: Help Text: Types of responses available: 0 = No Response 1 = Data Report 2 = Message Transfer Possible Responses: ERROR:INVALSEL Invalid Selection Response: Numeric Character 1 character Valid menu selection 0, 1, or 2. Yes
91
EGC, Message & Polling with Delivery Notification
10 EGC - Enhanced Group Call with PDN : Service Selection 10 This command is not supported 11 MSG - Message Submission with PDN : Service Selection 14 This command is not supported 12 POLL - Polling with PDN: Service Selection 19 This command is not supported
92
Change Password
13 PW - Change Password : Service Selection 80 See Figure 34 for the command structure to change the password associated with a PIN. 13.1 PW1 - Enter Old Password Prompt: Data Type: Size: Validation: Help Available: Possible Responses: No response or error messages provided. 13.2 PW2 - Enter New Password Prompt: Data Type: Size: Validation: Help Available: Possible Responses: No response or error messages provided. 13.3 PW3 - Verify New Password Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALFMT Invalid Format RESP:PWOK New password accepted Verify new password: Alphanumeric 6 to 10 characters Matches new password No Enter new password: Alphanumeric 6 to 10 characters Valid password format and does not equal old password No ERROR: type responses given at this command No Enter old password: Alphanumeric 6 to 10 characters Valid existing password No ERROR: type responses given at this command No
93
Quit
6-10 ALPHANUMERIC CHARACTERS 80 CHANGE PASSWORD ENTER OLD PASSWORD PW1
6-10 ALPHANUMERIC CHARACTERS ENTER NEW PASSWORD PW2
6-10 ALPHANUMERIC CHARACTERS VERIFY NEW PASSWORD PW3 RESP: PWOK NEW PASSWORD ACCEPTED
PW
MAIN MENU
CLEAR CALL
3rd UNSUCCESSFUL ATTEMPT
94
Change Password
PW80.EPS 20 June 1991
Figure 34. Change Password Command Structure Summary
Quit
14 QUIT - QUIT : Service Selection 99 This selection allows the user to quit Enhanced Services and clear the call to the LES. See Figure 35 for the command structure of QUIT. 14.1 QUIT1 - Are You Sure? Prompt: Data Type: Size: Validation: Help Available: Possible Responses: ERROR:INVALSEL Invalid Selection RESP:QUIT User has cleared call Are you SURE? (Y or N): Y or N 1 character Valid selection from menu No - provided in the prompt
95
DNID Data Reports and Messages
CALL IS CLEARED
1 CHARACTER Y or N ARE YOU SURE ? QUIT1
MAIN MENU
99 QUIT
N ERROR: INVALSEL INVALID SELECTION
MAIN MENU
96
Quit Command
QUIT99.EPS 14th November 1990
Figure 35. QUIT Command Structure
15 DNID Data Reports and Messages A Data Network ID (DNID) file stores data reports and messages that have been addressed to the DNID. The terrestrial user connects to the LES and retrieves the data reports and the messages. Alternatively, the LES operator may specify that data reports and messages addressed to particular DNIDs should be immediately forwarded to an X.121 address associated with the DNID, as described in Section 2.16. The processing of data reports and messages stored in a DNID file or immediately forwarded requires computer equipment running software that can interpret the information. This section defines the format of the data reports and DNID-addressed messages. 15.1 Data Reports Figures 36 and 37 display the format of the data generated from data reports. There are two types of data reports in Reference 1: reserved (preassigned) and unreserved data reports. The LES is not currently enabled to support reserved data reports. The first two bytes are the record size in bytes. Unreserved data reports can be up to 50 bytes long, when received in this format. The one-byte checksum is an exclusive OR of byte one to byte N-2 inclusive in Figures 36 and 37. The last byte is set to hex FF, binary 11111111. These fields are for processing computers to check that they have not jumped into the middle of data during reception. For unreserved data reports, as shown in Reference 1, the data field is composed of bytes six to 13 of the first data report and bytes two to 13 of the continuation reports. The data from each continuation report is concatenated to the previous report. The length field can be 26, 38, or 50 bytes, depending on the number of continuation reports received. The data fields are forwarded as received by the LES from the mobile. The protocol in Reference 1 is designed such that a 16-bit checksum is applied separately to the first data report and to each data report that is a continuation of the first data packet. This means that there is no overall checksum for the combined data report. If an overall checksum is required, it must be supplied by the user as an end-to-end application. This user checksum will be treated as data by the LES. The eight-bit checksum shown below is a minimal check provided by the LES on the overall message to allow detection of errors on lines between terminals and X.25 PADs.
97
Bits->8 7 6 5 4 3 2 1 Byte ---------------------1 | Length (LSB) | ---------------------2 | Length (MSB) | ---------------------3 | Record type | ---------------------4 | Presentation | ---------------------5 | Year MS byte | ---------------------6 | Year LS byte | ---------------------7 | Month MS byte | ---------------------8 | Month LS byte | ---------------------9 | Day MS byte | ---------------------10 | Day LS byte | ---------------------11 | Hour MS byte | ---------------------12 | Hour LS byte | ---------------------13 | Minute MS byte | ---------------------14 | Minute LS byte | ----------------------
Length in binary counted from byte 3 through byte N inclusive. 0 = Data Report, binary Always set to data = 7 binary ^ Time when data was received at the LES | Example 12 June 1990 13:20 hours | | 9 | 0 | 0 | 6 1 2 ASCII 1 3 | 2 | 0 | | | | | | v Continued
Figure 36. Format of Data Reports
98
Bits->8 7 6 5 4 3 2 1 Byte ---------------------15 | DNID (LSB) | ^ ---------------------Binary 16 | DNID (MSB) | ---------------------- v 17 | LES ID | As received from mobile. ---------------------18 | Member number | Of mobile in DNID, 8 bit binary. ---------------------| Data Report | | | | | Further details on formats are contained | | in Reference 1. | | | | ---------------------N-1 | Checksum | Exclusive OR of above contents. ---------------------N | Hex FF | End flag ---------------------Figure 37. Format of Data Reports - Continued
99
15.2 DNID-Addressed Messages Figures 38 and 39 displays the format of the data generated from DNID-addressed messages. The first two bytes are the record size in bytes. DNID-addressed messages can be up to 32640 bytes in length. The one-byte checksum is an exclusive OR of byte one to byte N-2 inclusive in Figures 38 and 39. The last byte is set to hex FF, binary 11111111. These fields are for processing computers to check that they have not jumped into the middle of data during reception. The protocol in Reference 1 is designed such that a DNID-addressed message is not acknowledged to the mobile as accepted by the LES unless it is successfully received and stored in the DNID file or immediately forwarded to the X.121 address for the DNID.
100
Bits->8 7 6 5 4 3 2 1 Byte ---------------------1 | Length (LSB) | ---------------------2 | Length (MSB) | ---------------------3 | Record type | ---------------------4 | Presentation | ---------------------5 | Year MS byte | ---------------------6 | Year LS byte | ---------------------7 | Month MS byte | ---------------------8 | Month LS byte | ---------------------9 | Day MS byte | ---------------------10 | Day LS byte | ---------------------11 | Hour MS byte | ---------------------12 | Hour LS byte | ---------------------13 | Minute MS byte | ---------------------14 | Minute LS byte | ---------------------15 | DNID (LSB) | ---------------------16 | DNID (MSB) | ---------------------17 | LES ID | ---------------------18 | Reserved | ----------------------
Length in binary counted from byte 3 through byte N inclusive. 1 = Message, Binary As received from Mobile ^ Time when data was received at the LES | Example 12 June 1990 13:20 hours | | 9 | 0 | 0 | 6 1 2 ASCII 1 3 | 2 | 0 | | | | | | v ^ Binary v Inserted by LES for compatibility with Data report format
Continued Figure 38. Format of DNID-Addressed Messages
101
Bits->8 7 6 5 4 3 2 1 Byte ---------------------19 | Mobile number len| ---------------------20 21 22 23 24 25 26 27 28 29 30 31 | T | ---------------------| M1 | ---------------------| I2 | ---------------------| D3 | ---------------------| X4 | ---------------------| X5 | ---------------------| X6 | ---------------------| X7 | ---------------------| X8 | ---------------------| Reserved | ---------------------| Reserved | ---------------------| Reserved | ---------------------| | | | | Message | | | | | ---------------------| Checksum | ---------------------| Hex FF | ---------------------^ | | | | | | | | | | | | | | | | | | | | | v
No. of digits in mobile number, set to 9 binary 4 ASCII, see Reference 1
9 digit ASCII mobile number of MES + 3 digit future expansion
Reserved fields for future expansion to 12 digit mobile number, set to 0 binary
Variable length field
N-1 N
Exclusive OR of above contents End flag
Figure 39. Format of DNID-Addressed Messages - Continued
102
15.3 Enhanced Data Reports Figure 40 and 41 displays the format of the data generated from enhanced data reports. The first two bytes are the record size in bytes. The one-byte checksum is an exclusive OR of byte one to byte N-2 inclusive. The last byte is set to hex FF, binary 11111111. These fields are for processing computers to check that they have not jumped into the middle of data during reception. The satellite protocol in Reference 1 includes two types of checksum that are designed to ensure the integrity of both the individual EDR packets and the overall data content. These checksums are checked and then if there are no issues, the report will be stored (or forwarded). When an EDR is retrieved (or forwarded), the report is constructed with header information as shown below. A new checksum is added at the end of the report to ensure the integrity of the complete set of data transmitted via the terrestrial interface.
103
Outgoing Call Message Formats
Bits->8 7 6 5 4 3 2 1 Byte ---------------------1 | Length (LSB) | ---------------------2 | Length (MSB) | ---------------------3 | Record type | ---------------------4 | Presentation | ---------------------5 | Year MS byte | ---------------------6 | Year LS byte | ---------------------7 | Month MS byte | ---------------------8 | Month LS byte | ---------------------9 | Day MS byte | ---------------------10 | Day LS byte | ---------------------11 | Hour MS byte | ---------------------12 | Hour LS byte | ---------------------13 | Minute MS byte | ---------------------14 | Minute LS byte | ---------------------15 | DNID (LSB) | ---------------------16 | DNID (MSB) | ---------------------17 | LES ID | ---------------------18 | Reserved | ----------------------
Length in binary counted from byte 3 through byte N inclusive. 2 = Enhanced Data Report, Binary Always set to data = 7 Binary ^ Time when data was received at the LES | Example 12 June 1990 13:20 hours | | 9 | 0 | 0 | 6 | 1 | 2 ASCII 1 | 3 | 2 | 0 | | | | | | v ^ Binary v As received from mobile. Of mobile in DNID, 8 Binary.
Continued Figure 40. Format of Enhanced Data Reports
104
Bits->8 7 6 5 4 3 2 1 Byte ---------------------| | | Data Report | | | ---------------------N-11 | Mobile Number Len | ---------------------N-10 | T | ---------------------N-9 | M1 | ---------------------N-8 | I2 | ---------------------N-7 | D3 | ---------------------N-6 | X4 | ---------------------N-5 | X5 | ---------------------N-4 | X6 | ---------------------N-3 | X7 | ---------------------N-2 | X8 | ---------------------N-1 | Checksum | ---------------------N | Hex FF | ----------------------
Further details on formats are contained in Reference 1. No. of digits in mobile number, set to 9 Binary. ^ Inmarsat Standard, 4 ASCII | for Inmarsat-C. | | | | | | | 9 digit ASCII mobile number of MES. | | | | | | | v Exclusive OR of above contents. End flag.
Figure 41. Format of Enhanced Data Reports - Continued
105
16 Outgoing Call Message Formats This section defines the formats for Store and Forward Messages and Store and Forward Status Messages, as described in Section 2.3. These messages are sent to terrestrial users as outgoing calls made by the LES. They share a common header format, but the rest of the message is formatted according to the type of data which follows. The format of these messages considers human users as well as the machine-user. The following formats are defined. Common Header Delivery Message, including examples of a

Normal Message Distress Message Distress Alert Land Mobile Alert
Delivery Notification Note: these formats do not apply to outgoing calls made for the immediate forwarding of data reports or DNID-addressed messages, which are described in Section 15. 16.1 Common Header The common header is sent in front of all delivery messages and delivery notifications, once a call has been established. The common header is of the following form. Format: <CRLF> MESSAGE:<Message_Name><CRLF> <LES_Name>DATE<SP><SP><YY-MM-DD/HH-MM><CRLF> T:<Type><CRLF> Where: <Message_Name> currently contains spaces. It is reserved for future use <LES_Name> is a string of 30 characters (right filled with spaces), LES operator defined <YY-MM-DD/HH-MM> is date and time message commenced delivery <Type> is a three-character string indicating the type of data, one of NDN Non-Delivery Notification PDN Positive Delivery Notification MSG Normal Message (including Land Mobile Alert) DIS Distress Message or Alert
106
Example: MESSAGE: TELEMEX SATRED T:MSG 16.2 Delivery Message Mobile-originated messages addressed to a terrestrial user have the following form. Format: Orig:<SP><Originator><CRLF> MSG-REF:<SP><Msg_Ref><CRLF> RDATE:<SP><SP><Date_Rev><CRLF> <CRLF> <Message_Contents> Where: <Originator> is identity of originator (nine digit mobile number). Mobile numbers larger than nine digits may be used in the future <Msg_Ref> is message reference number (six digits) <Date_Rev> is date/time original message received by the LES <Message_Contents> is text of message received by LES DATE 90-07-23/16-34
Notes: 1. Messages destined for the PSDN network are received from the mobile in binary presentation. 2. For distress alerts (T:DIS) and land mobile alerts (T:MSG) the text of the message is created by the LES from the packet received from the mobile. 3. The formats of the text created by the LES for distress alerts and land mobile alerts are defined in Satellite User Interface Document, Reference 6. However, examples are given in the following sections, showing the banners sent in front on the X.25 interface. 16.2.1 Normal Message from Mobile Example: MESSAGE: TELEMEX SATRED T:MSG Orig: 412345678 MSG-REF: 003450 RDATE: 95-03-23/16-33 DATE 95-03-23/16-34
Please send an engineer to join us at the next stop as we are having problems with the engine.
107
16.2.2 Distress Message from Registered Maritime Mobile Example: MESSAGE: TELEMEX SATRED T:DIS Orig: 412345678 MSG-REF: 006540 RDATE: 95-03-23/17-20 DATE 95-03-23/17-21
Assistance required, engine has now failed. 16.2.3 Distress Message from Unregistered Maritime Mobile It is not possible for an unregistered mobile to send a message successfully (of either priority) since the mobiles return ID is not known by the LES. 16.2.4 Distress Alert from Registered Maritime Mobile Example: MESSAGE: TELEMEX SATRED T:DIS Orig: 412345678 MSG-REF: 007650 RDATE: 95-03-23/17-30 DATE 95-03-23/17-31
DISTRESS ALERT FROM REGISTERED MOBILE Mobile Number : 412345678 LES ID : TELEMEX (360) Latitude (Degs Mins) : 39 51 South Longitude (Degs Mins) : 87 29 East Position Updated At (HHMM) : 1446 Protocol : Maritime Distress Type : Undesignated Speed : 0 Course : 0 Was Position Updated In The Last 24 Hrs : NO Was Course/Speed Updated In The Last 24 Hrs : NO Was Alert Auto Activated : NO
108
16.2.5 Distress Alert from Unregistered Maritime Mobile Example: MESSAGE: TELEMEX SATRED T:DIS Orig: 400000000 MSG-REF: 008970 RDATE: 95-03-23/17-43 DATE 95-03-23/17-44
DISTRESS ALERT FROM UNREGISTERED MOBILE Mobile Number : 400000000 Return ID : 3116022 LES ID : TELEMEX (360) Latitude (Degs Mins) : 39 51 South Longitude (Degs Mins) : 87 29 East Position Updated At (HHMM) : 1446 Protocol : Maritime Distress Type : Undesignated Speed : 0 Course : 0 Was Position Updated In The Last 24 Hrs : NO Was Course/Speed Updated In The Last 24 Hrs : NO Was Alert Auto Activated : NO 16.2.6 Land Mobile Alert from Registered Mobile - Inmarsat Format Example: MESSAGE: TELEMEX SATRED T:MSG Orig: 481234567 MSG-REF: 009870 RDATE: 95-03-23/17-52 DATE 95-03-23/17-53
LAND MOBILE ALERT FROM REGISTERED MOBILE Mobile Number LES ID Latitude (Degs Mins Secs) Longitude (Degs Mins Secs) Manual Position Entered Protocol Land Alert Format Nature of Land Alert Was Alert Auto Activated Time of Position Speed Direction of Travel Extra Information (Hex) : : : : : : : : : : : : : 481234567 TELEMEX (360) 50 0 0.0 North 1 0 0.0 West False Land Mobile Inmarsat Format Severe Weather YES 1 to < 5 minutes old Fast > 70 km/h East AB
109
16.2.7 Land Mobile Alert from Registered Mobile - User Defined Format Example: MESSAGE: TELEMEX SATRED T:MSG Orig: 481234567 MSG-REF: 009890 RDATE: 95-03-23/17-54 DATE 95-03-23/17-55
LAND MOBILE ALERT FROM REGISTERED MOBILE Mobile Number LES ID Latitude (Degs Mins Secs) Longitude (Degs Mins Secs) Manual Position Entered Protocol Land Alert Format User Defined Field 1 (5 bits) User Defined Field 2 (8 bits) User Defined Field 3 (8 bits) : : : : : : : : : : 481234567 TELEMEX (360) 50 0 0.0 North 1 0 0.0 West False Land Mobile User Defined 1F A5 00
16.2.8 Land Mobile Alert from Unregistered Mobile - Inmarsat Format Example: MESSAGE: TELEMEX SATRED T:MSG Orig: 480000000 MSG-REF: 010010 RDATE: 95-03-23/18-01 DATE 95-03-23/18-03
LAND MOBILE ALERT FROM UNREGISTERED MOBILE Mobile Number Return ID LES ID Latitude (Degs Mins Secs) Longitude (Degs Mins Secs) Manual Position Entered Protocol Land Alert Format Nature of Land Alert Was Alert Auto Activated Time of Position Speed Direction of Travel Extra Information (Hex) 16.3 Delivery Notification A Non-Delivery Notification (NDN) is sent to an address assigned to the PIN of the terrestrial user, if the LES is not able to deliver a message submitted by the user to one or more mobile destinations, or unable to deliver an EGC or Poll. The delivery outcome, successful or otherwise, for each of the specified mobile destinations, or ocean regions, in the case of EGCs or Polls, is shown is shown in the NDN.
110
: : : : : : : : : : : : : :
400000000 3116022 TELEMEX (360) 50 0 0.0 North 1 0 0.0 West True Land Mobile Inmarsat Format Severe Weather YES 1 to < 5 minutes old Fast > 70 km/h East AB
A Positive Delivery Notification (PDN) is sent to that same address, if the LES operator specifies that delivery notifications are to be sent for every message, EGC or Poll submission and where the delivery outcome is successful for all destinations. The format is the same as for NDNs, except that the common header indicates T:PDN rather than T:NDN. If an NDN or PDN cannot be delivered to the users address it is sent to the LES operator spill-out position. Format: MSG-REF:<SP><Msg_Ref><CRLF> Orig:<SP><Originator><CRLF> Dest:<SP><Destination><CRLF> RDATE:<SP><SP><Date_Rev><CRLF> Reason:<SP><SP><The_Reason><CRLF> Where: <Msg_Ref> <Originator> <Destination> is the message reference number (six digits) is up to 18 character originator address is the destination address - mobile number (messages) or ocean region name (EGCs and polls) <Date_Rev> is the date and time original message was received by LES <The_Reason> is <Success_Reason> or <Failure_Reason> <Success_Reason> is the success acknowledgement, up to 40 characters - see Section 17 <Failure_Reason> is the non-delivery reason, up to 40 characters - see Section 17
Note: for multi-addressed messages the lines from Dest to Reason are repeated for each destination address associated with the original message. Example: MESSAGE: TELEMEX SATRED DATE T:NDN MSG-REF: 003456 Orig: 234299080014827 Dest: 476241987 RDATE: 90-12-27/16-29 Reason: SD Satellite Call Failed Dest: 476241988 RDATE: 90-12-27/16-29 Reason: SD Satellite Call Succeeded 90-12-27/16-34
111
Delivery Success and Failure Reasons
17 Delivery Success and Failure Reasons This section lists the possible delivery success and failure reasons the user may receive from the LES, either by using the Message Status Enquiry service (see Section 8) or by receiving a Delivery Notification from the LES (see Section 16.3). The following text string for <Success_Reason> is provided for a successful delivery: SD Satellite Call Succeeded The following text string for <Failure_Reason> is provided for a delivery not yet attempted: Awaiting Delivery One of the following text strings for <Failure_Reason> is provided for an unsuccessful call not attempted on the satellite side due to cancellation or an addressing or routing error: Clear Down Absent Subscriber Message Aborted Format Error Access to This Number Barred Network Congestion Unknown Reason For Failure Invalid Presentation Code Cancelled by user Cancelled by oper Cancelled on expiry set by user Cancelled on expiry set by oper Cancelled on expiry set by system Cancelled on TX failure Cancelled on route failure Cancelled by user without NDN Cancelled by oper without NDN Not Commissioned MH Congested MH Routing Failed MH Rerouting Failed One of the following text strings for <Failure_Reason> is provided for an unsuccessful call attempted on the satellite side: SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD Satellite Call Failed Mobile Absent Aborted By Operator Call Failed Due To Distress Invalid Address In Message Invalid Address Format Invalid Message Size Invalid Number Of Addresses Invalid Presentation LES Internal Error Mobile Already Commissioned Mobile Barred Mobile Busy Mobile Failed To Respond Mobile Forced Clear Mobile Not Commissioned Mobile Not Logged In OR Mobile Not Registered Mobile Responded Incorrectly Mobile Response Timeout
112
Delivery Success and Failure Reasons
SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD SD Notes:
Mobile Protocol Error NCS Failed To Respond NCS Forced Clear Presentation Conversion Error Protocol Failure Remote Equipment Failure Resource Limit Exceeded Satellite Network Failure Service Not Provided Call pending Invalid LES ID in data report TDM Not Available No Msg Status Information Error in Outbound Message EGC Transmission Failed By NCS EGC Packet Sequence Error Call Cleared By System Cancelled due to Distress EGC Call failed due to Login Call to incorrect Ocean Region Message Channel Overloaded
1. The above text strings are the more common responses a normal user may expect to receive. NDNs and PDNs sent to the LES operator spill-out position may contain other text strings. The full set of LES call completion code text strings is given in Reference 5. 2. SD means Satellite Driver, the LES subsystem responsible for the satellite interface, and MH means Message Handler, the LES subsystem responsible for the central store-and-forward function. 3. Though the LES systems are not part of the Inmarsat network and do not interact with the NCS system, if TDM channels are down and a Poll or EGC (i.e. calls normally handled by the NCS in an Inmarsart system) is submitted by a user that fails, then the NDN returned to the user will contain NCS failure text.
113
Response Messages
18 Standard Responses All standard responses from the LES to the X.25 user are in the following form. Format: <CRLF> <Response_Kind><Response_Name><Space><Response_Text><CRLF> An explanation of the meaning of each field is contained in Section 2.4. This section gives a complete list of standard responses. Most of these responses are included in preceding pages, as and when they occur in the command sequence. DNID Status responses, Message Status Enquiry responses, help text and prompts are not covered in this section. Notes contained in round brackets are not seen by the user but are given here to provide the user with additional explanation. Where parameters appear as part of the response, they are shown in angle brackets (< and >). The whole response is shown in typewriter font. Responses are listed here in the order ERROR: responses then RESP: responses, and in alphabetic order within these groups.
ERROR:CONGEST LES Congested ERROR:EXCEDRETRY User has exceeded maximum retries ERROR:FAILED Call Failed (Usually as a result of problems in the network) ERROR:INVALADDR Invalid Address ERROR:INVALCMD Invalid Command ERROR:INVALDNID Invalid DNID ERROR:INVALDATE Invalid Date/Time ERROR:INVALFMT Invalid Format ERROR:INVALMETA Invalid Meta Command ERROR:INVALMOB Invalid Mobile Number ERROR:INVALOCEAN Invalid Region ERROR:INVALPIN Invalid PIN ERROR:INVALPRI Invalid Priority ERROR:INVALPRES Invalid Presentation ERROR:INVALREP Invalid Repetition Code ERROR:INVALSEL Invalid Selection ERROR:INVALSERV Invalid Service Selection ERROR:INVALTIME Invalid Time ERROR:MAXMSGS Maximum number of follow-on messages exceeded ERROR:NODNID PIN has no DNIDs ERROR:NOMOBILE User must enter a mobile ERROR:NOTAUTH User is not authorized ERROR:SYSCLOSE System is closing down
114

ERROR:TIMEXP Time out expired - Call cleared ERROR:TOOLONG Message entered is too long ERROR:ZEROLENMSG Message Length Must be Greater Than Zero RESP:DATADEL Data deleted RESP:MOBBAR Mobile Barred <Mobile Number> (Mobile number is appended) RESP:MSGACCEPT MSG-REF: <nnnnnn> Message Accepted <YY-MM-DD/HH-MM> (nnnnnn is the message reference number, YY-MM-DD/HH-MM is date/time) RESP:MSGCAN Request Accepted RESP:MSGNOTCAN MSG-REF: <nnnnnn> Message cannot be cancelled (nnnnnn is the message reference number) RESP:NODATA No reports in DNID files RESP:NOTCOM Mobile Not Commissioned <Mobile Number> (Mobile Number is appended) RESP:NOTLOG Mobile not logged into Region <Mobile Number> (Mobile Number is appended) RESP:NOTREG Mobile Not Registered <Mobile Number> (Mobile Number is appended) RESP:OVERFLOW One or more of the DNID files have lost data RESP:PASSEXP Password expired RESP:PWOK New password accepted RESP:QUIT User has cleared call RESP:RETRCOMP DNID retrieval complete RESP:TIMEOUT Timing out Please enter data
Response Messages
RESP:UNAVAIL Service temporarily unavailable RESP:UNKN MSG-REF: <nnnnnn> No record of message (nnnnnn is the message reference number)
115
19 Remote Setting of X.29 PAD Parameters Users that connect to the PSDN network using a PAD must have their PAD parameters set-up as follows: Table 2: PAD parameters required for X.29 interactive working. Table 3: PAD parameters required for X.29 non-interactive working and also for Kermit file transfer (see Appendix B). The LES software will read the current PAD parameters and then attempt to set remotely those parameters which are different to those listed in Tables 2 and 3, following call connection. Should this not be possible the onus is on the user to ensure that the PAD parameters are set as listed in Tables 2 and 3. The original parameters will be restored remotely by the LES before the call is cleared by the LES. This is not possible if the call is cleared by the remote side. The LES operator is able to modify the default PAD parameters both for interactive and noninteractive/Kermit access. Tables 2 and 3 give the factory settings. Note that only a subset of the parameters listed in Tables 2 and 3 are of interest to the LES for communicating with the end user. Those parameters marked Not Set by LES will not be downloaded to the remote PAD.
116
Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Name Escape Sequence Echo Data Forwarding Chars Data Forwarding timeout Flow control by PAD Suppress PAD Service Signals Action on Break Suppress Data Padding after CR Line Folding Terminal Speed Flow Control By Terminal LineFeed Insertion Line Feed Padding Line Editing Delete Char Delete Line Line Redisplay Display Edit Restrict Echo Parity Checking Page Wait
Value Not set by LES 1= on 2= CR 0= None Not Set by LES Not set by LES Not set by LES 0= Dont 0= Dont 0= Dont Not Set by LES Not Set by LES 6= Add LF 0= Dont Not Set by LES Not Set by LES Not Set by LES Not Set by LES Not Set by LES Not Set by LES Not Set by LES Not Set by LES
Table 2. X.29 Parameters for Interactive Session
117
Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Name Escape Sequence Echo Data Forwarding Chars Data Forwarding timeout Flow control by PAD Suppress PAD Service Signals Action on Break Suppress Data Padding after CR Line Folding Terminal Speed Flow Control By Terminal LineFeed Insertion Line Feed Padding Line Editing Delete Char Delete Line Line Redisplay Display Edit Restrict Echo Parity Checking Page Wait
Value 0= Disabled 0= Off 2= CR 2= Secs Not Set by LES 0= Suppress Not set by LES 0= Dont 0= Dont 0= Dont Not Set by LES Not Set by LES 0= Dont 0= Dont Not Set by LES Not Set by LES Not Set by LES Not Set by LES Not Set by LES Not Set by LES Not Set by LES Not Set by LES
Table 3. X.29 Parameters for Non-Interactive Session and Using Kermit
118
119
Appendix A Examples of Batch Mode Submission

This appendix gives examples of scripts that can be submitted to the LES in batch mode, as described in Sections 2.9 and 3.2. Figure A-1 gives an example of a message being submitted in batch mode, character by character. A single message is transmitted to mobile number 481234567. The presentation code is IA5, the users PIN is 5A24C1, and the users password is HELLOXYZ. The users message is The quick brown fox. Prompts are suppressed by the LES once batch mode is selected. Figure A-2 gives an example of the same message being submitted using the special binary data format described in Section 2.6 in batch mode. Note the change required in the delimiters used.
A-1
Byte Input 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 5 A 2 4 C 1 X <CR> <LF> H E L L O X Y Z <CR> <LF> 4 <CR> <LF> 4 8 1 2 3 4 5 6 7 <CR> <LF> <CR> <LF> 2 <CR> <LF>
Comment
Byte Input 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 T h e <Space> q u i c k <Space> b r o w n <Space> f o x <CR> <LF> . S E N D <CR> <LF> 99 <CR> <LF>
Comment Start of message text
Future prompts suppressed End of PIN
End of password Message submission command Start of mobile address
End of text Start of meta-command
End of meta-command Quit command
End of mobile address No more mobile addresses IA5
Note: unless the user waits for the LES response after sending byte 66, the remaining bytes will be discarded when the LES flushes the input buffer before sending the response - see Section 2.9.
[ifd_x25_eg_x_batch.stx]
Figure A-1. Example of Batch Mode Message Submission
A-2
Byte Input 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 5 A 2 4 C 1 X <CR> <LF> H E L L O X Y Z <CR> <LF> 4 <CR> <LF> 4 8 1 2 3 4 5 6 7 <CR> <LF> <CR> <LF> 3 <CR> Hex 16 Hex 00
Comment
Byte Input 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
Comment
Future prompts suppressed End of PIN
End of password Message submission command Start of mobile address
T Start of message text h e <Space> q u i c k <Space> b r o w n <Space> f o x <CR> <LF> Hex FF End of text <CR> <LF> 99 Quit command <CR> <LF>
End of mobile address No more mobile addresses Binary Length LSB Length MSB
Note: unless the user waits for the LES response after sending byte 63, the remaining bytes will be discarded when the LES flushes the input buffer before sending the response - see Section 2.9.
[ifd_x25_eg_x_batch_bin.stx]
Figure A-2. Example of Batch Mode Binary Message Submission
A-3
Appendix B User Guide for LES Kermit

B.1 Introduction The Kermit file transfer protocol is provided to enable X.25 interactive users using X.29 or asynchronous users to download data from the DNID files. B.2 Procedure The user enters the LES Kermit mode by selecting option K from the Protocol prompt in the DNID Data Retrieval dialogue. See Reference 2 for a complete description of the Kermit Protocol. To download files using the Kermit protocol for file transfer, users must first run Kermit at their remote site and connect to the LES from within Kermit. This usually involves entering the LES X.121 address at a PAD prompt. Note the Kermit escape sequence shown on the screen when connecting. Typing this sequence at any time during the LES/user dialogue will return control to the remote Kermit. Hit a <CR> and the PIN: prompt should be displayed. Once connected to the LES, the LES/user dialogue proceeds as usual. Any of the commands normally available to the X.25 interactive user can be entered, up to the point the user requests DNID file retrieval, and enters K at the Protocol: (D = Direct, K = Kermit): prompt. The LES then pauses for ten seconds before initiating the Kermit send protocol, waiting for the user to initiate the receive protocol. There is no need to type a send command at the LES; the send initiates automatically once the remote user Kermit enters receive mode. The ten second delay should normally be sufficient time for the user to escape back to the remote Kermit and type the receive command to initiate the Kermit receive protocol at the remote site. If the user does not initiate the receive protocol within ten seconds the LES Kermit will send a message to the remote users Kermit which will be seen as random characters on the terminal (for instance, "+ Sp\#&13"). This may be ignored. The LES will then await a response for a further two minutes before timing out. After entering K, the user should enter the Kermit escape sequence that was noted when connection was first made to the LES. This is usually <CTRL> and ] followed by C. The remote Kermit prompt will be displayed, and the receive command RECEIVE <filename> should be entered to initiate the protocol at the remote site. The filename parameter in the receive command is optional. The LES defaults the filename to C<NNNNN>.DAT where <NNNNN> is the DNID number or CALL.DAT if the A option was selected at the Enter DNID number or A for ALL DNID files: prompt. Some indication of the success or failure of the file transfer will be displayed, depending on the type of Kermit software running at the remote site. After the file transfer is complete, reconnect to the LES by typing the CONN command. The LES dialogue continues with the Data to be deleted? (Y or N): prompt. The dialogue is shown diagrammatically in Figure B-1 B.2.2 Parameters At the start of the Kermit protocol, both Kermits exchange a set of parameters which control the transfer of the data. Most data transfer failures are a result of improper setup of parameters. The following is a guide to setting up the remote Kermit parameters.
B-1
B.2.1 Example User Download Dialogue Via Kermit Async or X.29 End User Makes connection request from a package that has a Kermit option -------------------> <------------------Enters PIN Enter 2 (DNID Retrieval) Enter R (Retrieve Data) Enter A or 5 digits -------------------> <-------------------------------------> <-------------------------------------> <-------------------------------------> <------------------Enter U,S,A or D& time range -------------------> <------------------Prompt for protocol option: Kermit, Direct Prompt for range: Unseen, Seen, All, Date Prompt for DNID or All Prompt for service: Status, Retrieve,Delete If PIN Valid, provide menu selection Accepts connection and prompts for the PIN LES
Enter K. -------------------> Enter escape sequence, then receive command at remote prompt (10 + 120 seconds allowed for this operation) <------------------or <------------------if no kermit response, poll the remote kermit (you may see some random characters here) and retry for 120 seconds until the remote kermit connects. then send data reports Wait 10 seconds for the remote kermit to connect then send the data reports.
<------------------Providing operation successful, reconnect to LES -------------------> <------------------(Normally respond) Y -------------------> <------------------Further selection or quit -------------------> <-------------------
Prompt: Data to be Deleted? Delete data. Send Main menu prompt Menu selection or Session times out and call is cleared
Figure B-1. User Dialogue

B-2
The default LES Kermit parameters sent in the initiation packet to the remote Kermit are as follows. MaxL Time NPad PadC EOL QCTL QBIN CHKT Notes: 1. The parameters are controlled by the LES operator. 2. Maximum packet length at the remote Kermit can vary up to 94 bytes, depending on the size of the buffer at the remote Kermit. The MaxL defined at the LES means the LES can receive a maximum packet size of 80 characters. The remote parameter determines the size of the packets the LES sends. 3. Padding characters are sent at the start of each packet unless NPad is set to 0 at the remote Kermit. The LES does not require padding characters. 4. End of line should be set to <CR> at the remote Kermit. 5. Control prefix at the remote Kermit can be any valid control prefix character in the range ASCII 33-63 or ASCII 96-126, as long as it is not the same as the eighth-bit prefix below, if eighth-bit prefixing is used. 6. To initiate eighth-bit prefixing, which should be used if binary data is downloaded, the remote QBIN parameter must be Y or &. 7. Block check type 1 is the only checksum the LES Kermit supports. The remote CHKT parameter must also be 1 for the download to be successful. B.3 LES Validated Versions of Kermit There are many versions of Kermit available. HNS certifies that the following communications packages will work with the LES Kermit implementation. Cross Talk VAX Kermit MSDOS Kermit maximum packet length timeout number of pad characters padding character end of line character control prefix literal eighth bit prefix literal block check type literal 80 60 0 blank <CR> # & 1
ASCII ASCII ASCII ASCII ASCII
32 13 35 38 49
B-3
Appendix C User Guide for Asynchronous Modem and Terminal Settings

C.1 Introduction This section gives guidance for users who access the LES by means of a terminal or PC equipped with an asynchronous modem. The exact set up required by the user is dependant on the make and model of the modem, terminal and software package used. The following notes are therefore intended as general guidance. Standard Hayes AT commands are used in the examples. C.2 LES Modem Capabilities The modems at the LES are capable of several speed, error correction and data correction modes. It is advisable to set the users remote modem to select the highest common standard automatically to reduce the transmission charges and increase the call success rate. The LES modem will initially attempt to negotiate the highest common modulation mode as shown in Table C-1. CCITT Mode V.32 bis V.32 V.22 bis V.22 V.21 Data Rate 14400 BPS 9600 BPS 4800 BPS 2400 BPS 1200 BPS 300 BPS Table C-1. Supported Modulation Modes If the remote modem is using LAPM error correction the LES modem will attempt to negotiate V.42 bis compression. If the remote modem is using MNP error correction the LES modem will attempt to negotiate V.42 or MNP5 compression. If this negotiation fails no compression will be used. Note: if the remote modem does not support V.42 bis the user may wish to disable compression if it is known that the data is already in compressed form as MNP5 may induce lower transmission rates in this case. C.3 PC or Terminal Connection to the Remote Modem C.3.1 Character Format The interface between the users PC or terminal (the DTE) and its modem is critical to the operation. The LES modem uses V.25 bitsynch 10-bit characters which means that the following format must be set up.
C-1
For 8-bit data - use 1 start bit, 8 data bits, no parity, 1 stop bit For 7-bit data - use 1 start bit, 7 data bits, space parity, 1 stop bit It should be noted that any call from the LES or direct DNID download to the remote user will be full 8-bit binary data. The user must ensure that the 8-bit mode is set and that the communications package will capture 8-bit data. Users who only access the LES user interface and retrieve DNID data via Kermit may prefer to set 7-bit access as above, this ensures that Kermit uses 8th-bit prefixing to transfer binary data. C.3.2 DTE to Modem Data Rate The interface between the DTE and the modem is normally buffered. However, it is desirable to set the date rate to the highest possible value to ensure that flow control problems do not occur when receiving calls from the LES and to a moderate rate (that is, one compatible with the modems maximum transmission rate) when sending data to the LES. See Section C.3.3 for notes on flow control. C.3.3 Flow Control There are normally three options for flow control. XON/XOFF Do not use as this interferes with binary transfers
Hardware (or CTS/RTS) Preferred None Problems may occur if the DTE modem rate is too low
Hardware flow control is preferred. The use of no flow control requires care in the setting of the DTE modem data rate. C.4 Modem Set Up The DTE interface part of the modem set up is given in previous sections. To allow the modem to be called by the LES it must be set to auto answer. This is normally achieved by a command such as ATS0=n where n is the number of rings before the modem answers. By default this will normally be set to 0 which disables auto answer. A common value to use is ATS0=5. Consult your modem handbook to determine the best setting compatible with those given in previous sections or set it to allow the modem to automatically negotiate the highest common standard with the LES.
[ifd_x25_async.app]
C-2

IFD X25 v3 9 3

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IFD X25 v3 9 3

Uploaded by

Copyright:

Available Formats

HUGHES

Date: Issue: Status:

14th December 2005 3.9 Accepted

+44 1908 221122 +44 1908 221127

Copyright Hughes Network Systems Ltd 2005

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

X.25 and Asynchronous User Interface

X.25 and Asynchronous User Interface

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

REVISION HISTORY Issue Status Date Author Change References

3.5 3.6a 3.6b 3.6 3.8 3.9

For Review 11-Jan-95

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

X.25 and Asynchronous User Interface

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

X.25 and Asynchronous User Interface

Reporting Issues with this Document

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

X.25 and Asynchronous User Interface

Referenced and Related Documents

X.25 and Asynchronous User Interface

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

X.25 and Asynchronous User Interface

X.25 and Asynchronous User Interface

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

X.25 and Asynchronous User Interface

10. 11. 12. 13.

17. 18. 19. A.

9.14. 9.15. 9.16. 9.17. 9.18. 9.19. 9.20. 9.21. 9.22.

Examples of Batch Mode Submission . . . . . . . . . . . . . . . . . . . . . . .

X.25 and Asynchronous User Interface

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

User Guide for LES Kermit B.1. B.2. B.3.

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

X.25 and Asynchronous User Interface

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

X.25 and Asynchronous User Interface

10 117 118 C-1

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

Terrestrial User Interface Structure

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

Hex 0D Hex 0A Hex 0D0A Hex 0C Hex 2C Hex 3A

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

Terrestrial User Interface Structure

User Displays (Sent by the LES to the user)

Terrestrial User Interface Structure

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

Terrestrial User Interface Structure

Terrestrial User Interface Structure

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

Terrestrial User Interface Structure

Terrestrial User Interface Structure

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

Delimiter Sequence {<SP>}<SP> {<SP>}<CRLF> {<SP>}<CR> {<SP>}<colon> {<SP>}<comma> {<SP>}<FF>

Interactive X.25/ Non-Interactive No (1) No (4) Yes Yes Yes Yes

No (1,2) No (3) Yes No (2) No (2) No (2)

A4-IFD-003076-1 Issue 3.9 - Accepted 14th December 2005

Terrestrial User Interface Structure