Mobile communications terminal for satellite communications system

[0002] This application is a continuation of International Application number PCT/US96/19905, filed Dec. 6, 1996, which claims priority from U.S. Provisional Application No. 60/011,158, filed Dec. 8, 1995 , both of which are incorporated herein by reference.

[0003] The present invention relates to mobile communications terminal in wireless communications system. More specifically, the present invention relates to mobile communications terminals sending and receiving pre-formatted text and binary messages to a central facility using a satellite communications system.

[0004] Wireless communications terminals have been used in service vehicles to receive communications messages from centralized dispatcher offices. For example, taxicab companies have installed data terminals in taxicabs that receive messages from a dispatcher via RF transmissions. Such systems, however, are limited in their communication abilities in that the mobile terminals can only receive and acknowledge messages.

[0005] One example of a currently successful and operational satellite based data service is INMARSAT's Standard-C Communications System. The major elements of the Standard-C system architecture include land or coast earth stations (LESs or CESs), and a network coordination station (NCS) in each ocean region and ship or mobile earth stations (SESs or MESs). Each CES serves as a gateway between the terrestrial network and the INMARSAT Standard-C communications system. The types of interface provided at the CES are decided by the coast earth station operator, however, Telex, EGC message processing and distress message handling are mandatory to comply with INMARSAT's Standard Definition Manual Version 1.3.1.

[0006] A SES or MES is the mobile earth station used by mobile subscribers. The system allows the use of very low G/T transceivers at the ship or mobile earth station (SES or MES). Standard-C uses all digital transmission techniques for both signalling and message data specifically based on a standard slotted ALLOHA TDMA protocol. SES equipment may therefore take advantage of the low cost trend of digital technology. Standard-C SESs do not require the use of a dedicated receiver for receiving signalling information.

[0007] The SES consists of a DCE (data circuit terminating equipment) providing the interface to the satellite network, and a DTE (data terminal equipment, for example a personal computer) which provides the user interface. For ship-to-shore message transfer, a message is formatted in the DTE and then transferred to the DCE for transmission. In the shore-to-ship direction, the DCE receives the complete message from the radio channel before passing it to the DTE for the attenuation of the user. The SES may be equipped for reception of Enhanced Group Calls (EGC) or a separate Receiver Only Terminal for EGC reception may be used. When idle, every SES tunes to and receives a TDC channel transmitted by the NCS; the NCS Common Channel. The channel is used to transmit announcements to SESs that shore-to-ship calls are ready at a CES for transmission to the SES. Enhanced Group Calls are also transmitted on this channel.

[0008] Additional optional services are available within the system and may be offered by CESs. These services include access to electronic mail and message handling services (X.400 for example), individual, group and area directed polling, and a data reporting service. The polling and data reporting services are primarily aimed at providing a service to remotely operated and land mobile terminals. More detailed information regarding the Standard-C protocol is disclosed in “INMARSAT Standard-C communications System” by Kevin Phillips, IEEE International Conference on Communications '88: Digital Technology—Spanning the Universe, Jun. 12-15, 1988, pp. 1117-1122 (Available from IEEE Service Cent (cat. #CH2538-7/88)) ©1988 IEEE, the disclosure of which is incorporated in its entirety by reference.

[0009] Standard-C protocol was not designed to be used in connection with land mobile data terminals but was designed only for maritime use. Thus, there is a need for a satellite communications system that provides effective communications for land mobile data terminals.

[0010] Conventional electronic mail and message handling services are not designed for extensive message transmissions in a satellite communication system. Service vehicles such as taxicabs, trucks, etc., need an efficient, low-cost, and reliable arrangement for receiving messages from a central dispatcher. Moreover, there is a need for providing advanced messaging capabilities where a variety of messages can be initiated mobile terminals without providing excessive loading on the satellite.

[0011] In view of the foregoing, there is a need for a low cost mobile communication system that provides efficient transport of user messages via a satellite network.

[0012] There is a also a need for an electronic mail messaging system for transporting messages between a dispatcher and mobile communication terminals that uses predetermined message forms to minimize user efforts in generating and displaying mail messages.

[0013] According to at least one aspect of the present invention, in a mobile satellite system including a satellite communication switching office having a satellite antenna for providing communication of a satellite message with a mobile communication system via a satellite, a central controller communicating with the mobile communication system via the satellite communication switching office, a communication method comprising storing a plurality of message display forms in the mobile communication system, each message display form having a predetermined display format and a form identifier, generating at the central controller a user message comprising message data, outputting from the central controller a satellite message carrying the message data and the form identifier of a selected one of the message display forms to the satellite communication switching office, transmitting the satellite message to the mobile communication system via the satellite, and displaying the satellite message received by the mobile communication system using a selected one of the stored message display forms corresponding to the form identifier in the transmitted satellite message. The communication method enables a central controller to send and receiver user messages in a compressed format, minimizing the amount of data to be transmitted to the mobile communications systems.

[0014] In another aspect of the present invention, in a mobile satellite system including a satellite communication switching office having a satellite antenna for providing communication of satellite messages with a mobile communication system via a satellite, a central controller communicating with the mobile communication system via the satellite communication switching office, the mobile communication system comprising a satellite transceiver communicating data packets carrying a first satellite message to the satellite in response to transceiver control signals a graphic user interface providing a display and accepting key inputs from a user, a software system comprising a middleware layer sending the transceiver control signals and packets carrying the satellite message to the transceiver, a network form controller storing a plurality of message forms each having a form identifier and a form definition specifying a predetermined format, an address list storing a list of station addresses identifiable by the satellite communication switching office for respective satellite stations having communication capabilities with the satellite communication switching office, a user interface controller retrieving a selected one of the form definitions and at least one station address in response to the key inputs, the user interface controller outputting a user message including the at least one station address, user inputs from the graphic user interface and the form identifier corresponding to the selected form definition, a network controller subsystem outputting the satellite message carrying the user message to the middleware layer, and an event handler controlling operations of the network controller and the user interface controller in response to network event and user event signals from the network controller and the user interface controller, respectively.

[0015] Additional objects, advantages and novel features of the invention will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following or may be learned by practice of the invention. The objects and advantages of the invention may be realized and attained by means of the instrumentalities and combinations particularly pointed out in the appended claims.

[0016] FIG. 1 is a diagram illustrating an architecture of a satellite communication system for a mobile communication system of the present invention.

[0017] FIG. 2A is a block diagram illustrating the mobile communication system of the present invention.

[0018] FIG. 2B is a diagram illustrating the layered structure of the software used by the mobile communication terminal of the present invention.

[0019] FIGS. 3A and 3B are views of a mobile communication terminal according to an embodiment of the present invention.

[0020] FIG. 4 is a diagram illustrating the software structure of the mobile communication terminal of the present invention;

[0021] FIG. 5 is a diagram illustrating the software structure of the event handler of FIG. 4.

[0022] FIG. 6 is a diagram illustrating the software structure of the user interface controller of FIG. 4.

[0023] FIGS. 7A and 7B are diagrams illustrating the software contexts of the interfaces to the software of the mobile communication system of the present invention.

[0024] FIGS. 8-1 to 8-34 are diagrams illustrating graphic displays of the mobile communication terminal of FIGS. 3A and 3B during different operations.

[0025] The present invention provides a mobile communication system that sends and receives electronic mail messages to an from other stations in a satellite communication system. The mobile communication system is designed to provide flexibility to users, while maintaining efficient terminal operations. The techniques described herein enable the mobile communication system to be implemented as a low-cost terminal requiring a minimal amount of memory. An overview of the overall satellite communication system and mobile communication system will be provided, followed by a more detailed description of the software interfaces and software functions of the mobile communication system.

[0026] FIG. 1 is a diagram of a satellite communication system architecture in communication with the mobile communication system to provide the mobile messaging service (MMS) of the present invention. The satellite communication system 10 includes a dispatcher station 12, a satellite communication switching office 14, and a satellite network 16 for transporting satellite messages between the satellite communication switching office 14 and an adaptive mobile communication (AMC) system 18. The AMC is implemented, for example, as a communications device on vehicle, for example a truck. The dispatcher 12 is located at a custom premises, for example at a management office of a trucking company having a fleet of trucks. The dispatcher 12 sends and receives signals to and from the satellite communication switching office 14 via a leased communication line of a public packet switched network 20, for example a X.25 network.

[0027] The satellite communication switching office 14 includes a satellite antenna 22, and a land earth station (LES) 24 that interfaces between the satellite antenna 22 and the public X.25 network 20. Data packets carrying satellite messages received from the dispatcher 12 via the X.25 network 20 are reassembled by the LES 24, and transmitted to the satellite network 16, preferably using an enhanced satellite communications protocol that provides packet communications between the LES 24 and the AMC 32 without the necessity of additional earth stations to transmit signaling and control messages to the satellite network 16. The communications requirements for the enhanced satellite communications protocol of the preferred embodiment is described in more detail in commonly assigned, copending application Ser. No. 08/654,453, filed May 28, 1996, entitled IMPROVED COMMUNICATION PROTOCOL FOR SATELLITE DATA MESSAGING, the disclosure of which is incorporated in its entirety herein by reference.

[0028] Satellite messages received from the mobile user via satellite network 16 by the LES have addresses identifying the recipient of the satellite message, described below. If the intended recipient is the dispatcher 12, the LES 24 transparently forwards the received message byte stream plus a header from the satellite network 16 to a customer premise gateway (CPG) 26 at the dispatcher 12 via the public X.25 network 20. The CPG 26 includes middleware software 26athat communicates with the LES 24 via the X.25 network 20. The CPG middleware 26areceives the byte stream from the X.25 network 20, reassembles the satellite message from the received byte stream, and presents the reassembled message to the CPG application software 26b.The CPG application software 26bconverts the reassembled message into a format usable by a computer-aided-dispatcher (CAD) 28 resident at the dispatcher 12, and outputs the converted message to the CAD application 28.

[0029] The dispatcher 12 and AMC stations 18 communicate using proformas—template forms to be used by the sender and having data fields. The AMC stations 18 have the proformas stored in memory, described below. Exemplary proformas include stop-over form used to inform the dispatcher 12 of an overnight stay, including date, time, and address fields. The dispatcher 12 would receive record of the address where trucker will be staying that evening. Other proformas include free form (text message), dispatch request, service request, etc. Each proformas may also include an acknowledgement field.

[0030] The proformas minimize the amount of data that needs to be transmitted over the satellite network 16 by transmitting a form identifier, and the binary data to fill in the form. Hence, there is no need for labels, screen positions, format commands, etc. to be sent, since each station can access the appropriate screen forms on the basis of the form identifier, and rebuild the original form display locally.

[0031] The computer-aided-dispatcher (CAD) application 28 provides the dispatching and e-mail messaging functions in a graphic user interface to enable a dispatcher to manage the fleet of mobile units. Proforma messages form the CAD application 28, described below, are converted and compressed by the CPG application software 26bfrom text data into a message carrying binary data. The message carrying binary data is then sent to the CPG middleware 26asoftware which converts the message to a byte stream for transmission to the LES 24 via the X.25 network 20.

[0032] The AMC 18 is the mobile component of the Mobile Messaging Service (MMS) and preferably includes an OMNIDATA RDT-3000 Data Terminal Equipment (DTE) 32 connected to a Data Communications Equipment (DCE) 34 comparable with the above-described enhanced satellite communications protocol. An exemplary layout of the DTE 32 is shown in FIGS. 3A and 3B. The DTE 32 includes middleware software 36 and application software 38 controlled by a 25 MHz Intel 386 or better microprocessor. According to the preferred embodiment, the application software 38 will execute on the DTE under DataLight's ROM-DOS Version 6.2 operating system, and will integrate with the Trimble Galaxy Inmarsat-C/GPS (for spot beam roaming) DCE 34. The middleware software 36 provides a communications protocol enabling communication between the transceiver and the CPG. An exemplary middleware software is the Enterprise Messaging Services (EMS), Ver. 3, by Complex Architectures, Inc., a Sybase Company, Wakefield, Mass.

[0033] The AMC 18 has a proforma definition file in non-volatile memory. Hence, the Dispatcher 12 can create new proformas and download them via satellite to the mobiles 18, where the mobiles would accept the new form definitions and store them in the proforma definition file.

[0034] As described below, a user of the AMC 18 sends a message by selecting a proforma, filling out the form with the appropriate information and pressing the send button. In response to the send button, the application software 38 converts and compresses the text data into a message carrying binary data. The message carrying binary data is then sent to the middleware software 36 which executes the communication functions, including controlling the transceiver 34. The middleware software supplies a byte stream of the mobile message to the transceiver, which transmits the byte stream to the LES via the satellite network.

[0035] FIG. 2A is a block diagram of the internal hardware and software structure of the AMC 18. The AMC 18 includes the communicator software 40 including the middleware software 36 and the application software 38. The DTE 32 includes hardware components interacting with the software 40, for example a keyboard 42 and a distress switch 44 on the keyboard and/or dashboard 42 that outputs an emergency message to the dispatcher 12 when depressed. The DTE 32 also includes a RAM Disk 46, for example in NVRAM, a read only memory (ROM) 48 storing the operating system, the software code, and selected configuration data. According to the preferred embodiment, the disk 46 has 2 Megabytes of random access memory that includes the standard 640 k/384 k used by the processor for the operating system, and the memory 48 includes one megabyte of protected NVRAM (flash) plurs 256 k for boot ROM. The DTE 32 also includes a piezo speaker 50, a message LED 52, a “READY” LED indicating the system is operational, and an internal clock 54. Display data is output to a display 56, described in detail below.

[0036] Additional peripheral devices may be connected to the DTE 32, including a printer 58 and a message notification device 60. The notification device 60 is preferably a localized RF paging device having a range of 100 meters for use when a driver is not within the vehicle. In such instances, the paging device 60 is activated when a satellite message having a predetermined priority level is received by the AMC 18.

[0037] FIG. 2B is a diagram illustrating the layered structure of the software used by the mobile communication terminal of the present invention. In FIG. 2B, the mobile communications software features a layered software structure in accordance with the standards of the general ESO seven layer model. The layered structure permits individual layers to be easily replaced or modified. For example, by including a separate middleware communications layer, different low level communications code can be easily inserted or modified to support different radio transceivers. The middleware router layer supports different customer protocols or communications, and allows/facilitates the insertion or modification of same. The network controller layer allows or facilitates the insertion or modification of different network functionality. Finally, the user interface layer allows or facilitates the insertion or modification of new screen designs and/or information that is displayed to the user without requiring the recompilation of the software.

[0038] FIG. 4 is a diagram of the software structure of the communicator software 40 according to an embodiment of the present invention. The Network portion 36 represents the middleware that controls the transceiver. As described below, the application layer 38 includes a network controller 60 that interfaces with the middleware 36 and an event handler 74 that manages the overall operations of the application layer 38. The network controller 60 handles all communications with the satellite network and interfaces with the middleware 36. The network controller 60 receives two types of messages from the middleware, namely user messages and device messages. A device message is a data packet including DCE data generated by the transceiver 34, for example configuration data or device status data. The communications middleware 36 recognizes DCE data from the transceiver 34 and forwards the DCE data to the network controller 60 as a device message. The network controller 60 passes the device message carrying the DCE data to the DCE controller 62.

[0039] The DCE controller 62, associated with the network controller 60, provides all control functions for the DCE 34. The DCE controller 62 allows a user to configure the transceiver as necessary for operations. In addition, the DCE controller 62 passes selected DCE data to the user interface controller 64 to enable the user of the AMC to view the state of the transceiver. The DCE controller configures the DCE or request actions at a high level. It does not participate in low-level protocol control.

[0040] The network controller 60 receives user messages from the satellite network 16, referred to as network event, and forwards the user message in accordance with the user message type. The network controller 60 can receive three different types of user messages from the satellite network, namely network messages, data messages, or user proforma messages. The network messages include messages from a network monitoring station related to performance of the satellite network. The data messages include configuration data or new proforma forms for use by the AMC user. The user proforma messages are the proforma messages that include messages for display to the user according to a selected proforma display format.

[0041] The network controller 60 forwards the data messages carrying configuration data to the configuration manager 4. The configuration manager 66 stores all configuration files for the AMC, including user-specific configuration files. Configuration files may be loaded into the configuration manager either by an external source, such as a PCMCIA card, or via the satellite network. Certain configuration files may be altered by the user as necessary, for example, user ID.

[0042] Proforma forms are handled by the network proforma controller 68. Data messages received by the network controller 60 that include new proforma forms are loaded into the network proforma controller 68.

[0043] The address list 70 manages the address book of the user. If the user attempts to send a message having an address not known to the system, the address of the message is automatically added to the address list 70. For example, if the AMC 18 receives a message from the satellite network and the user attempts to reply to the message, the address of the reply message is automatically loaded into the address list 70 if not already present. The address list 70 may include both single addresses for individual stations, or group addresses for a group of stations.

[0044] The address list 70 provides addresses based on the destination LES 24. Once a message is received by the LES, the LES determines how to route the message. Thus, if the message is intended for the dispatcher, the LES routes the message via the X.25 network. If the message is intended for another mobile, the LES retransmits the message to be intended mobile via the satellite network.

[0045] The message logs portion 72 includes an incoming message log, and outgoing message log, a network message log, a data message log, and a saved messages log. The incoming message log includes unread messages received from the satellite network. The outgoing message log includes messages to be sent to the satellite network, and includes messages to be retransmitted due to unsuccessful transmission. The network message log and data message log include the respective messages received from the satellite network related to network and AMC operations, and will also include a field specifying whether an acknowledgement of the message is transmitted by the AMC. Since the network message log and data message log are more directed to operations of the satellite network and the AMC, these logs will generally not be used by the typical user.

[0046] The user interface controller 64 handles all user interface events, including interaction with the display and keyboard inputs. FIG. 6 is a more detailed diagram of the software structure of the user interface controller 64. The user interface controller 64 includes a monitor input 84 that detects and processes all keyboard inputs from the user by outputting keyboard data to a graphics library 86 and a data switch event message to an interface controller 82. The graphics library 86 generates graphics display data for display by the LCD display. Thus, the keyboard data from the monitor input 84 is converted to a display character to provide the user with feedback of the keyed input. An example of the graphics library 86 is the commercially available QuickWindows Advanced for the C Programming Language, Rev. 2.50, from Software Interphase, Inc., Foster, R.I.

[0047] The interface controller 82 performs event handling for the user interface controller 64 in response to events detected from different portions of the software modules shown in FIG. 4. The interface controller manages the detected events by an interface event queue, that stores pending events to be processed. For example, in response to receiving message data representing a user proforma message, the interface controller 82 forwards the message data to the a display form controller 88, along with system status and proforma events that identifies a selected proforma form. The display form controller 88 in response access the configuration data for the selected proforma form from the network proforma controller 68 shown in FIG. 4, and generates the form display data including the display format for the selected proforma form, and selected system status displays, for example, “READY” and “SYNC'D” on the main transceiver screen indicating the transceiver is linked to the satellite network, etc.

[0048] The graphics library 86 also receives display data from a update static displays portion 90. The update static displays portion 90 receives system display data from the interface controller 82 (system status, date, time, etc), and periodically outputs updated static display, for example, every ten seconds. The user interface controller 64 also includes a menu controller 94 that allows a user to configure the display pull down menus, described below. Specifically, the user interface controller 64 includes a menu definition file 92 that includes default menu and at least one user-defined menu. The user can move, reorganize, and/or rename the default pull down menus and store the modified pull down menus in the menu definition file. The menu controller responds to keyboard data inputs from the user by outputting the corresponding display data to the graphics library 86. The menu controller 94 also outputs a menu event to the interface controller 82 in response to a selection by the user of a specific pull down menu function, at which point the interface controller responds to the selected pull down menu function.

[0049] The event handler 74 shown in FIG. 4 is responsible for overall operations of the AMC application software. The event handler minimizes complexity of the AMC application software, enabling AMC operations to be performed using a minimal amount of software. For example, if a data message is received by the communications middleware 36 from the satellite network, the communications middleware 36 passes the message to the network controller 60. The network controller 60 notifies the event handler 74 of the occurrence of a network event. If the data message includes configuration data, the event handler 74 passes the data message to the data message log in the message logs portion 72 and the configuration manager 66. Similarly, if the communications middleware 36 receives a user message from the satellite network, the user message is passed to the network controller 60, which notifies the event handler 74 of the network event. The event handler 74 in response transfer the user message data to the incoming message log of the message logs portion 72 and the user interface controller 64, which informs the user of the new message via the update static display portion 90.

[0050] The user accesses the received message by activating the incoming log, whereby the user interface controller responds to the keyboard data by passing an event through the event handler 74 to the message log 72. The message log 72 in response sends the data representing the contents of the incoming log to the user interface controller 64 for display to the user.

[0051] After the display of the incoming log, the event of selecting a desired message by the user causes the display form controller 88 to access the proforma form data for the proforma form corresponding to the selected message. The user interface controller 64 also access the data corresponding to the selected message from the message log 72 under the control of the event handler 74. After the data for the selected message and the proforma form are accessed, the graphics library 86 combines the data for the message with the proforma form and displays the desired message.

[0052] FIG. 5 is a diagram of the event handler 74. The even handler 74 is divided between handling events at timed intervals and handling events at random intervals. The event handler 74 includes a polling timer controller 100 having internal timers to generated specified events at predetermined intervals. For example, one timer controls the frequency at which messages are sent and received, whereby the communications middleware is checked once a second for incoming messages, and messages are sent at a rate no greater than once a second. Hence, the controlled execution of events at specified intervals ensures that the middleware is not overloaded with service requests.

[0053] Hence, the software arrangement within the AMC can be optimized for minimal hardware memory requirements by limiting the execution of events to a sufficiently slow rate to enable the middleware to serially complete execution of tasks.

[0054] Moreover, the software arrangement within the AMC provides cooperative multitasking, whereby system operations are performed in the background and transparent to the user. Hence, a user may be typing a message while an incoming message is received from the transceiver.

[0055] FIG. 7A is the AMC_Software Context Diagram, and shows the context within which the AMC software will execute. This software will interface with a driver (or ‘end-user’), a technician (or administrator) and the DCE. FIG. 7B, AMC_Software, shows the decomposition of the AMC software into its application and middleware components. The application software described herein preferably integrates with the chosen Enterprise Messaging Services middleware software, as well as other communications middleware. Each of the interfaces shown in FIGS. 7A and 7B are defined in Section 2, External Software Interfaces. The term ‘software’ refers to the ‘application software’ component whose requirements are being specified. In those instances where the middleware software component is specifically discussed, it is referred to as the ‘middleware software’.

[0056] The AMC application software will support two AMC system modes: ‘end-user’ and ‘admin’. These two modes are based on the two types of users who can operate the application software: end-users (i.e. drivers) and administrators (i.e., service technicians). The software will allow the user to perform different sets of operations based on whether the AMC system is operating in end-user or admin mode. Note that the software will provide all of the features available in end-user mode in admin mode as well. When the AMC's DTE is powered up, it will present a timed menu allowing service technicians to enter “admin” mode by entering the appropriate password. If no input is made or the password is entered incorrectly, the software will automatically boot into end-user mode. If the input is made and the password is entered correctly, then the software will present the admin user with a DOS prompt. The admin user will then be allowed to perform several functions:

[0057] Use the built-in DTE editor to edit the various configuration files used by the operating system, application and middleware software,

[0058] Place the system/software into admin mode by executing the admin application software with a command line parameter indicating ‘admin’ mode and entering the ‘admin’ password as indicated in Section User Interface; this will allow the admin user to access all software features provided in end-user mode as well as additional features only provided in admin mode (e.g. system configuration),

[0059] Automatically configure the DCE using a predefined DCE Configuration File contained on the SRAM card by executing the admin application software with a command line parameter indicating the name of the DCE configuration file.

[0060] The requirements of the application software when functioning in either end-user or admin mode will now be described. All features that will only be provided to the admin user when the software is functioning in admin mode will be identified by ‘Admin’.

[0061] The following section describes each of the application software's external interfaces shown in FIGS. 7A and 7B. The requirements for the contents of the data stores shown in FIG. 7B (e.g., Proforma_Definitions) are described below.

[0062] Address (data flow)=

[0063] *an address object, containing an alias and optionally an address type and address value*.

[0064] Config_Params (data flow)=

[0065] *all configuration parameters read from configuration files by the AMC application software; these include DTE configuration parameters, DCE configuration parameters that the software will send to the DCE, menu and function key definitions, etc.*.

[0066] Data_Messages (data flow)=

[0067] *messages transmitted between the AMC and computer equipment at an MMS dispatcher's premise containing binary data such as proforma definitions, engine monitoring data and bar code reader data*.

[0068] Driver_Controls (data flow)=

[0069] *includes all commands entered by driver via user interface, as well as activation of the dash switch*.

[0070] Driver_Displays (data flow)=

[0071] *includes all displays presented to the driver via the AMC screen*.

[0072] Local_Messages (data flow)=

[0073] *DCE Configuration, Command, Command Response and Event messages: i.e., messages exchanged between the application software and the DCE that are not transmitted over the satellite network. This also includes MW_Control_Messages and MW_Status_Messages.*.

[0074] Msg_Delivery_Acks (data flow)=

[0075] *delivery acknowledgements sent by middleware as a result of incoming messages from LES and Dispatcher Site*.

[0076] MW_Config_Params (data flow)=

[0077] *configuration parameters used by the middleware to control its operation*.

[0078] MW_Control_Messages (data flow)=

[0079] *messages sent to the middleware commanding it to perform some action; e.g., initialize, terminate, send message, receive message, query message delivery status, acknowledge message receipt; note that this flow is not shown since it is part of the Local_Messages flow*.

[0080] MW_Data_Messages (data flow)=

[0081] *a Data_Message that also contains the middleware's control information*.

[0082] MW_Local_Messages (data flow)=

[0083] *DCE Configuration, Command, Command Response and Event messages in the format the middleware uses to communicate with the DCE*.

[0084] MW_Network_Messages (data flow)=

[0085] *a Network_Message that also contains the middleware's control information*.

[0086] MW_Status_Messages (data flow)=

[0087] *a status message returned from the middleware to indicate its status or the delivery status of a message; note that this flow is not shown since it is part of the Local_Messages flow*.

[0088] MW_User_Messages (data flow)=

[0089] *a User_Message that also contains the middleware's control information*.

[0090] Network_Messages (data flow)=

[0091] *messages transmitted between the AMC and a Network Management Station containing network management commands and information; these include AMC Control, Configuration, Information and Periodic Health Messages*.

[0092] Proforma_Definition (data flow)=

[0093] *a definition of a message proforma or a field list proforma*.

[0094] Technician_Controls (data flow)=

[0095] *includes all commands entered by technician via user interface, as well as activation of the dash switch*.

[0096] Technician_Displays (data flow)=

[0097] *includes all displays presented to the technician via the AMC screen*.

[0098] Transmitted_MSG_Status (data flow)=

[0099] *delivery status from DCE (originating at LES) of a User_Message or Network_Message that application software has requested to be transmitted*.

[0100] User_Indicators (data flow)=

[0101] *all indicators to the driver or technician other than via the AMC screen; includes LED activations and audio activations*.

[0102] User_Messages (data flow)=

[0103] *all messages entered by driver or sent by dispatcher to communication information between the two*.

[0104] The following subsections detail the functional requirements of the AMC software. These requirements are organized around the system objects to which they apply.

[0105] Address

[0106] The software requirements in this section relate to the Address object. An address in this context is a destination to which (or from which) a user or network message can be sent. The software will support two address modes: single primary destination mode and multiple primary destination mode. The software will determine which mode the AMC is to function in based on the Addr_Mode configuration parameter. The distinction between the two modes is as follows. In ‘single’ mode, the software will always send messages over the network to the same physical address with varying logical addresses (i.e. address aliases). In ‘multiple’ mode, the software may send messages over the network to different physical addresses with varying logical addresses. In single mode, there is no need for the software to maintain a physical address along with each address object since it always sends to the same physical address; in multiple mode, the software will maintain a physical address for each address object since each address alias could potentially be associated with a different physical address.

[0107] The software will maintain address objects. An address object will consist of an address alias and, depending on whether the AMC is configured for single or multiple primary destination mode, an address type and an address value. The software will maintain the address alias as an alphanumeric string containing between 1 and 8 ASCII characters. The software will support optional address types of ‘DNID’, ‘Network’, ‘SAC’ (Special Access Code) and Mobile Id. The software will maintain the optional address value as an alphanumeric string containing between 1 and 14 characters. Note that if the address value is present, it will contain a number in the range of 1-65535 for ‘DNID’ address types, a 14 character address (e.g. an X.121 address) for ‘Network’ address types, a six-character alphanumeric string for ‘SAC’ address type and a number in the range of 1-999999999 for ‘Mobile Id’ address types.

[0108] The software will automatically create and delete address objects based on specific user interface actions and specific messages received at the AMC. The requirements specifying how these objects are created and deleted are specified in Section Address Book.

[0109] Address Book

[0110] The software requirements in this section relate to the Address Book object. An address book in this context is one or more lists of address objects. The software will maintain one address book, which will be a combination of two address lists; each address list will contain address objects whose contents are based on the AMC's currently configured address mode as described in Section Address. The software will maintain one address list on the Flash-ROM disk and one on the RAM disk. The maximum number of address objects that will be maintained by the software in the RAM address list will be indicated by the Max_RAM_Addresses configuration parameter.

[0111] The user interface for creating, modifying and clearing the Flash-ROM address list, as well as the software required to place the address list on the Flash-ROM disk, is external to the application software. Maintenance of the Flash-ROM address list will be performed by the admin user using external software tools. The software will provide error messages to the user in the status are described in Section User Interface when it encounters errors reading the Flash-ROM address list.

[0112] The software will automatically add address objects to the RAM address list when the AMC user sends a user message to an address alias that does not currently exist in either address list. Note that the software will not update the RAM address list when network messages are sent to address alias that do not exist in the address list. If the RAM address list is full, the software will prompt the user for whether or not they want to delete an existing address object from the RAM address list. If they do, then the software will present a list of all address aliases in the RAM address list to the user and allow them to select the one to delete. Once the user selects the desired address alias, the software will automatically delete that address object from the RAM address list and will add the address object associated with the message being sent to that address list. The specific user interface requirements for this process are described in the User Interface.

[0113] The software will automatically update the physical address of address objects in the RAM address list when the user sends a user message to an address alias that does exist in the RAM address list but has a different physical address this could only happen if the user is replying to a message and the incoming message contained a reply address and the AMC is functioning in ‘multiple’ address mode; see Section Network.

[0114] The software will allow the user to designate any address object within the address book as the ‘destination address’, and to designate one address object within the address book as the ‘Default Address’. If an entry exists in both the Flash-ROM and RAM address lists with the same address alias, the software will use the address value associated with the address object in the RAM address list. If more than one entry exists in the FLASH-ROM address list with the same address alias, then the software will use the first alias in the list and ignore the others. If more than one entry exists in the RTAM address list with the same address alias, then the software will use the first alias in the list and ignore the others. The requirements specifying how the user interfaces with the address book/lists are described in Section User Interface.

[0115] DCE

[0116] The software requirements in this section relate to the DCE object. A DCE in this context is a physical transceiver connected to the DTE that provides the underlying message transmit and receive capabilities required to communicate over the network. The application software will communicate with the DCE in order to configure and control is functionality. Note that the middleware software will also communicate with the DCE in order to perform the message send and receive functions, to monitor its health to determine if messages can be sent and received, to establish communications with the DCE upon DTE or DCE power-up, etc. The application software will use the middleware software to send the configuration and control commands described in this section.

[0117] The software will send the DCE command messages and DCE configuration messages, specified below, to the DCE as requested. The software will send these messages in order to perform the following functions:

[0118] Direct the DCE to perform an immediate action.

[0119] Query the DCE for its internal parameters.

[0120] Query the DCE for internal values that indicate its current health.

[0121] Configure the DCE's internal parameters [Admin].

[0122] The software will receive the DCE command response messages returned by the DCE when any of the DCE command and configuration messages are sent. Upon receiving a DCE command response message that indicates an error, the software will report that error to the user as described in Section User Interface, and will log that error in the AMC health log as described in Section Health Log. The software will use the data returned in the DCE command respond messages as needed for the following purposes:

[0123] To display it on the DTE's Monitor Transceiver Status screen as described in Section User Interface.

[0124] To evaluate automatic data variables contained in proforma messages to be transmitted over the network as described in Section Message Proforma.

[0125] To include it in the health log as described in Section Health Log.

[0126] To include it in a periodic health report as described in Section Network.

[0127] Each of the four purposes listed above has a corresponding configuration parameter or value that indicates the interval at which data should be retrieved for that purpose; these are the Display_Update_Interval configuration parameter, the Max_Auto_Data_Age configuration parameter, the Health_Log_Update_Interval configuration parameter and the value specified by the ENABLE-HLTH-RPT command, respectively. The software will send the necessary DCE command messages to query the DCE for the data needed for each of these purposes at an interval specified by the minimum of the four parameters and values that currently apply (e.g., if the Monitor Transceiver Status screen is not displayed, the software will not consider the Display_Update_Interval configuration parameter when determining the query interval; if periodic health reports are not currently enabled, the software will not consider the associated value when determining the query interval).

[0128] The specific format of each DCE command, configuration and response message is described in the published specifications for the Trimble transceiver, described above. The admin software will be able to read a DCE Configuration File containing aliases for the various DCE configuration parameters and the values to which they will be configured. The software will send the appropriate DCE configuration messages to the DCE in order to set each of the parameters to the values contained in the file. The software will report errors encountered during this process to the user as described in Section User Interface. The software will allow the [Admin] user to select this function and enter the name of the DCE configuration file as described below. The software will also allow the name of the file to be provided on the command line of the admin application software as described in Section 1.6, System Modes. The requirements for the contents of this file are described below. The DCE's configuration parameters can be modified via polls sent from the LES without the application software being informed. For this reason, the application software cannot assume that the DCE's configuration parameters are always set to the values last set or queried by the software.

[0129] The admin software will place an indication that the DCE's configuration has changed on the DTE's RAM disk each time it sends a DCE configuration message to the DCE. Upon initialization, the end-user software will check to see if this ‘DCE configuration change’ indication exists; if it does exist, the software will automatically send a ‘DCE Config Changed’ fixed-format message to the network management station whose address type is provided by the Default_Nms_Addr_Type configuration parameter and whose address is provided by the Default_Nms_Addr_Value configuration parameter; the end-user software will remove the ‘DCE configuration change’ indication from the DTE's RAM disk after successfully sending the message.

[0130] The software will receive DCE Event Messages generated by the DCE. These messages, whose contents are strings of ASCII characters, provide information about activities occurring within the DCE and the network. The software will display all DCE event messages on the user interface is requested by the user as described in Section User Interface. The software will recognize certain DCE event messages and will place those events in the health log described in Section Health Log. The software will also recognize the ‘distress alert acknowledgement’ event message and will indicate to the user that the acknowledgement has been received as specified in Section User Interface. The specific DCE event messages that the software will recognize are listed below.

[0131] DTE

[0132] The software requirements in this section relate to the DTE object. A DTE in this context is a device that provides the user interface of the AMC, contains and executes the software necessary to provide all system features to the AMC user and provides the overall control of the DCE. The DTE used as part of the AMC is an OMNIDATA RDT-3000, which contains a CGA monitor, a ‘Ready’ LED, a ‘Message’ LED, a keyboard, a speaker, a Boot-ROM disk, a Type-II PC-MCIA slot, a Flash-ROM disk, a RAM disk and RAM. In addition, the DTE optionally includes an distress switch and various alarm devices such as a pager, an audible alarm or a strobe light; the switch and alarm devices are physically connected to the DTE via its communication ports.

[0133] As further described below, the software will:

[0134] Maintain the state and configuration of the AMC system.

[0135] Process network messages sent to the AMC directing it to change its configuration or report on its state or configuration.

[0136] Send network messages from the AMC reporting the current AMC state and configuration.

[0137] Control the DTE's hardware devices.

[0138] Providing information pertaining to the state of the DTE hardware and software for inclusion in the AMC's health log and periodic health reports.

[0139] The software will maintain the date and time within the AMC using the DTE's date and time functions. The software will maintain these values using the UTC time system. The software will update the DTE's date and time with the date and time obtained from the DCE's GPS module every six hours to compensate for any inherent drift in the DTE's time clock.

[0140] The software will maintain the configuration of the AMC via permanent, static and dynamic configuration parameters. Permanent configuration parameters are those parameters that are built into the application software; the software will maintain its version number and the admin user password as permanent configuration parameters. Static configuration parameters are those parameters that are preset by the admin user and can only be changed by the admin user or by network messages that are received at the DTE. Dynamic configuration parameters are those parameters that can be modified by any user as described in Section User Interface.

[0141] The software will be able to read static configuration files that contain the values of all static configuration parameters. These files, described below, will be stored on the Flash-ROM disk. The user interface for creating, modifying and deleting static configuration files, as well as the software required to place these files on the Flash-ROM disk, is external to the application software. Maintenance of the static configuration files will be performed by the admin user using external software tools. The software will provide error messages to the user as described in Section User Interface when it encounters errors reading these configuration files.

[0142] Upon initialization, the software will configure the AMC system as required based on the static configuration parameters described below, and the permanent and dynamic configuration parameters described in this section. The software will use the values of these configuration parameters to control the AMC's functionality.

[0143] The software will maintain dynamic configuration parameters that can be modified by the user as described in Section User Interface. The software will store these dynamic configuration parameters on the DTE's RAM disk so they will be persistent if the software is reinitialized. The software will use the values of these configuration parameters to control the AMC's functionality as described with each dynamic configuration parameter listed below:

[0144] Current time zone

[0145] indicates the time zone that will be used when displaying all dates and times to the user; valid values are:

[0146] AST (Alaska)

[0147] ADT

[0148] EST (Eastern)

[0149] EDT

[0150] CST (Central)

[0151] CDT

[0152] GST (Greenland)

[0153] GDT

[0154] HST (Hawaii-Aleutian)

[0155] HDT

[0156] MST (Mountain)

[0157] MDT

[0158] PST (Pacific)

[0159] PDT

[0160] Default address alias

[0161] indicates the address alias within the AMC's address book to be initially selected as the destination address for all messages the user wants to send

[0162] Function key definitions

[0163] indicates the particular menu item that is to be selected when the user presses one of the OMNIDATA's 12 function keys.

[0164] The software will receive AMC Control Messages and AMC Configuration Messages (as described in Section Message) from the network. These messages will be sent to the software as proforma messages and may make use of the ‘command field type’ and ‘automatic reply’ message proforma features described below. The software will process each of these messages as required by the specific command that is sent. The commands that can be included in these messages, and the processing required for each, are listed below.

[0165] The software will automatically send AMC Information Messages (as described in Section Message) over the network in response to AMC Control Messages received from the network that request an ‘automatic reply’. AMC information messages may be proforma messages whose message proforma uses the ‘automatic data variables, or they may be fixed-format messages described and listed below.

[0166] The software will interface with and control each of the DTE's peripherals and hardware devices. The software will read and write files stored on the DTE's RAM disk and on SRAM cards inserted into the DTE's PC-MCIA slot. The software will read files stored on the DTE's Boot-ROM and Flash-ROM disks. The software will interface with the DTE's keyboard, CGA monitor, LEDs, speaker and distress switch as described in Section User Interface. The software will activate the DTE's alarm device each time a user message is received at the DTE. The software will determine the percentage of used memory within its RAM or any of its disks whenever requested by a user interface action, or by an automatic data variable within a message proforma. The software will activate the printer connected to the DTE as described in Section Printer.

[0167] The software will monitor the mobile's speed over ground reported by the DCE and will deactivate the DTE's display whenever that speed exceeds the value specified by the Max_Operating_Speed configuration parameter; if that parameter's value is a negative number, the software will not deactivate the DTE's display.

[0168] The software will evaluate the state of the DTE hardware and software as required to place information into the AMC's health log described in Section Health Log. In addition, the software will update the health log with any severe ‘exception’ or ‘error’ events it detects within the DTE hardware, operating system software, middleware software of application software.

[0169] Health Log

[0170] The software requirements in this section relate to the Health Log object. A health log in this context is an object that contains ongoing information about the health of the AMC. The software will maintain an AMC health log. The software will periodically place information about the current state of the DTE and DCE hardware into the health log. The software will update the health log based on the period indicated by the Health_Log_Update_Interval static configuration parameter. The information that will periodically be placed into the health log is described below.

[0171] In addition to this ‘periodic’ information, the software will log specific DCE events as reported by DCE Event Messages (and the event's UTC time). The DCE events that will be logged are specified below. The software will log DCE events in ‘event_code:line 2—line n’ format where ‘event_code’ is the number returned in the first line of every event message and ‘line 2—line n’ represents the exact contents of the event message beginning with the second line.

[0172] The software will log exception or error events that it detects via a DCE Command Response Message or within the DCE, DTE, network, middleware software, application software or operating system software. The software will place these events in the health log along with the UTC time they occurred. The software will monitor the size of the health log to ensure that it doesn't exceed the size specified by the Max_Health_Log_Size static configuration parameter. If data to be inserted into the health log would cause the log to exceed this size, the software will delete the oldest data from the log prior to inserting the new data (‘old’ is based on the time the data was placed into the log).

[0173] The software will maintain the AMC health log on the RAM disk. The user interface for viewing the health log is external to the application software; i.e., the admin user will use external software tools to view the health log.

[0174] Message

[0175] The software requirements in this section relate to the Message object. A message in this context is an object that is:

[0176] Presented to the user in the form of text,

[0177] Entered by the user in the form of text,

[0178] Transmitted to the application software by the middleware software, and/or

[0179] Transmitted to the middleware software by the application software.

[0180] Messages are classified into three categories: User Messages, Network Messages and Local Messages. User messages are those messages that the AMC user enters for transmission to another use of the messaging service and those messages entered by another user of the messaging service for delivery to this AMC user. All user messages will be defined and formatted according to the message performas described below, and all user messages to be transmitted from the AMC may use the message proforma automatic data variable features detailed below.

[0181] Network messages are those messages sent to the AMC from a remote network management station to control the DTE or DCE, configure the DTE or DCE, or query the DTE or DCE for configuration information or current DTE and DCE ‘health’ information that relates to network management; network messages also include the responses to these messages sent from the AMC to a remote network management station. Network messages are further classified into the following categories:

[0182] * AMC Control Messages

[0183] Messages sent to the AMC via the network to direct the DTE to perform some action (this action may include directing the DCE to perform some action.)

[0184] * AMC Configuration Messages

[0185] Messages sent to the AMC via the network commanding the DTE to change its configuration or commanding the DTE to change the configuration of the DCE.

[0186] * AMC Information Messages

[0187] Messages sent from the AMC via the network to report current DTE or DCE health or configuration information.

[0188] * AMC Periodic Health Messages

[0189] Messages sent from the AMC over the network at a given interval reporting current DTE and DCE health information.

[0190] Most network messages will be defined and formatted according to the message proformas described below, and may use the message proforma automatic data variable and command features detailed below. Note that message proformas containing commands may only be used for messages being transmitted to the AMC. Some network messages will be ‘fixed-format’ messages.

[0191] Local messages are those messages transmitted between the application software and the middleware software that are not transmitted over the network. These messages relate to DCE control and configuration, and status reporting, and are further classified as follows:

[0192] * DCE Command Messages

[0193] Messages sent from the DTE to the DCE to direct the DCE to perform some action.

[0194] * DCE Configuration Messages

[0195] Messages sent from the DTE to the DCE to direct the DCE to change its configuration.

[0196] * DCE Command Response Messages

[0197] Messages sent from the DCE to the DTE in response to a DCE command or configuration message.

[0198] * DCE Event Messages

[0199] Messages sent from the DCE to the DTE as a result of events detected by the DCE.

[0200] * Middleware Control Messages

[0201] Messages sent from the application software to the middleware software commanding it to perform some action.

[0202] * Middleware Status Messages

[0203] Messages sent from the middleware software to the application software indicating middleware status or the delivery status of messages.

[0204] All local messages will have fixed format, i.e., they will not use message proformas. The general content requirement for local messages are described below. DCE command, configuration and event messages are also described below. The software will process message objects. User and network message objects will have the following attributes:

[0205] * Type (proforma or fixed-format)

[0206] * Class (user or network)

[0207] * Identifier (proforma id or fixed-format message id)

[0208] * Alias (proforma alias for proforma messages; static alias (e.g. PVT Results) for fixed-format messages)

[0209] * Middleware identifier (unique identifier assigned by middleware for transmitted messages)

[0210] * Source address (alias, type, value)

[0211] * Destination address (alias, type, value)

[0212] * Delivery priority (distress alert, emergency, high, medium, low)

[0213] * Acknowledgment requested (device, service, router, application)

[0214] * Sent or received date/time (using UTC)

[0215] * MRN/PDN/NDN list (there may be a list of MRNs/PDNs/NDNs since the middleware software segments messages and transmits them as multiple messages compatible with the enhanced satellite communications protocol)

[0216] * Delivery status

[0217] * Failure code/reason for non-delivery

[0218] * Message-specific variable length data.

[0219] Local message objects will have the following attribute:

[0220] * Message-specific variable length data.

[0221] For user and network messages to be sent from the DTE, the software will remove unnecessary attributes prior to giving the message to the middleware software for transmission; the content requirement of each message type/identifier as it will be transmitted to and received from the middleware software is described below, and discusses sending messages over the network.

[0222] The software will be able to print any user message object; the software will use the message proforma associated with the message object to format the printed message; the software will include field labels defined in the message proforma in the formatted printout. Other processing required for message objects depends on whether the message is a user, network or local message, whether the message is being received or being sent by the application software, and the specific type/identifier of the message. The specific processing required for each category and subcategory of messages is described in the sections identified below:

[0223] * User Messages

[0224] Sections Message Logs; Network, and User Interface

[0225] * Network—AMC Control Messages

[0226] Sections DTE; Message Logs; and Network

[0227] * Network—AMC Information Messages

[0228] Sections DTE; Message Logs; and Network

[0229] * Network—AMC Periodic Health Messages

[0230] Section Network

[0231] * Local—DCE Command Messages

[0232] Section DCE

[0233] * Local—DCE Configuration Messages

[0234] Section DCE

[0235] * Local—DCE Command Response Messages

[0236] Sections DCE; and Health Log

[0237] * Local—DCE Event Messages

[0238] Sections DCE; Health Log; and User Interface

[0239] * Local—Middleware Control Messages

[0240] Section Network

[0241] * Local—Middleware Status Messages

[0242] Sections Network; and User Interface.

[0243] Note that while all requirements associated with the various categories and subcategories of messages are in the sections identified above, other sections include related information that may aid in the understand of these messages; these are:

[0244] * User Messages

[0245] Sections Message Proforma and Field List Proforma

[0246] * Network—AMC Control Messages

[0247] Section Message Proforma, and Message Proforma Automatic Data Variables and Commands

[0248] * Network—AMC Configuration Messages

[0249] Section Message Proforma, and Message Proforma Automatic Data Variables and Commands

[0250] * Network—AMC Information Messages

[0251] Periodic Health Log and Health Report Contents

[0252] * Local—DCE Command Messages

[0253] DCE Command, Configuration and Event Messages

[0254] * Local—DCE Configuration Messages

[0255] DCE Command, Configuration and Event Messages

[0256] * Local—DCE Event Messages

[0257] DCE Command, Configuration and Event Messages.

[0258] Message Proforma

[0259] The software requirements in this section relate to the Message Proforma object. A message proforma in this context is a template that defines the contents of a message to be transmitted over the network, as well as the processing required for (or by) the message. The software will use message proformas to direct the content, format, display, editing, printing and processing all ‘proforma’ (vs ‘fixed-format’) messages sent to and from the AMC. Each message proforma object will have the following attributes:

[0260] * Identifier

[0261] unique identifier for each message proforma object

[0262] * Version number

[0263] the current version number (major and minor number) for the message proforma

[0264] * Alias

[0265] the label to be used by the user interface object when referring to this message proforma

[0266] * Message class

[0267] indicates whether messages using this message proforma are user or network messages

[0268] * Priority

[0269] the priority at which messages using this message proforma should be sent (emergency [3],high[5 ], medium [7 ], low [9 ]

[0270] * Reply proforma identifier

[0271] unique identifier for the message proforma object to be used when replying to messages using this message proforma

[0272] * Reply type (automatic vs manual)

[0273] indicates whether the software should automatically reply to messages using this message proforma object or whether it should wait for the user to indicate that a message reply is desired

[0274] * Reply required

[0275] indicates whether the software should inform the user that a reply is required when a message is received that uses this message proforma; this only applies when the ‘reply type’ is ‘manual’

[0276] * List of message field proformas

[0277] Each message field proforma will have some or all of the following attributes (depending on the ‘Type’ attribute):

[0278] * Type

[0279] the type of this message field (see details below)

[0280] * Label (does not apply to automatic-data and command field types)

[0281] the ASCII-principle label to be used by the user interface object when displaying this message field

[0282] * Length (does not apply to automatic-data and command field types)

[0283] an integer indication the number of ASCII characters allowed in the field

[0284] * Value (does not apply to automatic-data and command field types)

[0285] the ASCII characters to be initially inserted into the field on the screen; this is required for protected field types and is optional for other field types

[0286] * Location (does not apply to automatic-data and command field types)

[0287] the location where the user interface object is to place this message field on the screen

[0288] * Required (does not apply to automatic-data and command field types)

[0289] boolean indication of whether or not data will be included in messages that use this message proforma

[0290] * List Name (only applies to list field types)

[0291] indicates the ASCII name of the field list proforma that contains valid values for this field

[0292] * Automatic data variable (only applies to automatic-data field types)

[0293] indicates the name of the automatic data variable whose value the AMC software will insert into the message; see below for valid automatic data variables

[0294] * Command (only applies to command field types)

[0295] indicates the command to be executed by the DTE associated with this field in the message; see below for valid commands

[0296] * Command data (only applies to command field types)

[0297] provides the data to be used with the command contained in the ‘command’ attribute, i.e., the “parameter” to the command; see below for the command data associated with each command

[0298] * Command display status (only applies to command field types)

[0299] provides the message to be displayed in the status area (described in Section User Interface) when this command is processed by the software.

[0300] The software will support the following message field proforma field types:

[0301] * Date

[0302] a fixed-length field with ‘MM/DD/YY’ format; valid values are 01-12 for MM, 01-31 for DD, and 00-99 for YY

[0303] * Time

[0304] a fixed-length field with ‘HH:MI:SS’ format; valid values are 00-23 for HH, 00-59 for MI, and 00-59 for SS

[0305] * Single-line Free-form

[0306] a variable-length field that can contain any printable ASCII characters; its length can be 0 to the value indicated by the field's ‘length’ attribute; it can only span one line on the screen

[0307] * Multi-line Free-form

[0308] a variable-length field that can contain any printable ASCII characters; its length can be 0 to the value indicated by the field's ‘length’ attribute; it can span multiple lines on the screen

[0309] * Integer

[0310] a variable length field that can contain a valid whole number with a sign; its length can be 0 to the value indicated by the field's ‘lenght’ attribute

[0311] * Float

[0312] a variable length field that can contain a valid decimal number with a sign and one decimal point; its length can be 0 to the value indicated by the fields's ‘length’ attribute

[0313] * Protected

[0314] a fixed-length field whose contents are included in the proforma field definition; it can contain any printable ASCII characters; the data is not included in the message; the data is shown on the screen by the user interface object, but the user is not allowed to modify it

[0315] * Label

[0316] a fixed-length field that only has a label, i.e., no field contents; this field is for display purposes only by the user interface object; it is not included in the transmitted message

[0317] * Yes-no

[0318] a fixed-length field whose only valid values are ‘Y’ and ‘N’

[0319] * List

[0320] a fixed-length field whose only valid values are those defined in the field list proforma named in the field's ‘list’ attribute; the value that is included in the message is defined by the position of the value within the field list proforma

[0321] * Automatic-data

[0322] a fixed-length, fixed-format field whose values are automatically included in the message by the AMC software; fields of this type are only processed for messages that be being transmitted FROM the AMC; fields of this type that exist in messages transmitted to the AMC are ignored; the data values for field of this type are never displayed on the screen by the user interface object; immediately prior to transferring a message to the middleware software for transmission over the network that uses a message proforma containing this field type, the software will perform all necessary processing to evaluate the data variable and include the resulting value in the message to be sent; valid automatic data variables are specified below.

[0323] * Command

[0324] a fixed-length field whose values indicate an action that eh DTE will perform; this field type is only valid in message proformas for messages that be being transmitted TO the AMC; the data values for fields of this type are not display on the screen by the user interface object; upon receiving a message that uses a proforma containing this field type, the software will perform the processing indicated by the common in the field' ‘command’ attribute using the data provided in the field' ‘command data’ attribute as the command “parameter”; when processing of the command begins, the software will display the string provided in the ‘command display status’ attribute in the status area of the DTE'screen described in Section User Interface.

[0325] The software will read the definitions of message proformas from disk and will process all automatic data variables and commands as messages that use message proformas are sent and received; the software will also use message proformas to direct the content and format of these messages. As described below, the software will use message proformas to control the display and editing of messages on the user interface.

[0326] Message proformas will be stored on the Flash-ROM disk. The user interface for creating, modifying and deleting message proformas, as well as the software required to place message proformas on the Flash-ROM disk, is external to the application software. Maintenance of message proformas will be performed by the admin user using external software tools. The software will provide error messages to the user as described below when it encounters errors reading message proformas. The software will also accept new message proformas via network messages and stores those message proformas on the RAM disk. In addition to User and Network, the software supports the Data message class within the proforma definition files.

[0327] Message Proforma Rules. The richness of the capabilities provided by the message proformas described in Section Message Proforma, allows many proforma definitions that are invalid or only valid in certain situation. This section states the rules and limitations associated with message proforma features and definitions. The software will assume that all message proformas adhere to the rules and limitations stated in this section; it is the responsibility of the admin user creating the message proformas to follow these rules.

[0328] The proforma features that are valid within a message proforma definition depend on whether the message proforma is a ‘user’ message proforma or a ‘network’ message proforma (as determined by the message proform's ‘Message Class’ attribute). For this reason, the following rules are divided into those that apply to user message proformas and those that apply to network message proformas. The following rules refer to ‘display ’ fields within a message proforma definition. ‘Display’ fields in this context refer to any type of field within a message proforma that can be displayed on the user interface (e.g. date, time, integer, float); display fields include all fields except automatic data variable and command fields.

[0329] User Message Proformas

[0330] * The ‘reply type’ attribute can only be ‘manual’; it cannot be ‘automatic’.

[0331] * The ‘reply proforma identifier’ attribute will designate another user message proforma; it cannot designate a network message proforma for the reply; all user message proformas will include a ‘reply proforma identifier’ attribute.

[0332] * The message proforma definition can include display fields and automatic data variable; it cannot include command fields. Automatic data variables in user message proformas for messages sent from the AMC will be automatically evaluated by the software; automatic data variables in user message proformas for messages received at the AMC will be ignored. If a message proforma definition includes automatic data variables, then all of the automatic data variables will follow any display fields included within the definition

[0333] Network Message Proformas

[0334] * The ‘reply type’ attribute can only be ‘automatic’; it cannot be ‘manual’.

[0335] * The ‘reply proforma identifier’ attribute will designate another network message proforma (if it designates any reply proforma); it cannot designate a user message proforma for the reply; network message proformas do not have to include a ‘reply proforma identifier ’ attribute (no automatic reply will be sent in this case).

[0336] * The message proforma definition can include automatic data variables or commands, but not both; the definition cannot include display fields. Automatic data variables in network message proformas for messages sent from the AMC will be automatically evaluated by the software; automatic data variables in network message proformas for messages received at the AMC will be ignored. Commands in network message proformas for messages sent to the AMC will be processed (their associated ‘status’ message will be displayed in the status area of the user interface when processing of the command begins); commands cannot be included in network message proformas that will be used for messages sent from the AMC.

[0337] Proforma Download

[0338] The software will split the menu definition file into three files: the main menu definition file, the quick menu definition file, and the enter message menu definition file. The main menu definition file (MMDF) will remain as it is in the Version 1.0 AMC except that the definition of the ‘Quick’ pull-down menu and the ‘Message-Enter’ pop-up menu is removed. The software will support these definitions being placed in the quick menu definition file (QMDF) and the enter message menu definition file (EMMDF), respectively. The software will build its menu structure upon initialization based upon these three menu definition files. The software will accept the following fixed-format data messages and process them as indicate:

[0339] * Download Proforma

[0340] Message identifier: 7

[0341] Message contents:

[0342] User/admin indicator

[0343] The exact binary contents of a proforma definition file (PDF)

[0344] Processing

[0345] The software will store this PDF on the RAM disk using the appropriate path and filename based on the user/admin indicator and the proforma id contained with the PDF. If a proforma with this path and filename already exists on the RAM disk, the software will replace it.

[0346] * Download List Proforma

[0347] Message identifier: 8

[0348] Message contents:

[0349] User/admin indicator

[0350] The exact binary contents of a list proforma definition file (LPDF)

[0351] Processing

[0352] The software will store this LPDF on the RAM disk using the appropriate path and filename based on the user/admin indicator and the name of the list, as specified in the LPDF. If a list proforma with this path and filename already exists on the RAM disk, the software will replace it.

[0353] * Download Main MDF

[0354] Message identifier: 9

[0355] Message contents:

[0356] User/admin indicator

[0357] The exact binary contents of a main menu definition file (MMDF)

[0358] Processing:

[0359] The software will store this MMDF on the RAM disk using the appropriate path and filename based on the user/admin indicator. If an MMDF already exists on the RAM disk, the software will replace it.

[0360] * Download Quick MDF

[0361] Message identifier: 10

[0362] Message content:

[0363] User/admin indicator

[0364] The exact binary contents of a quick menu definition file (QMDF)

[0365] Processing:

[0366] The software will store this QMDF on the RAM disk using the appropriate path and filename based on the user/admin indicator. If a QMDF already exists on the RAM disk, the software will replace it.

[0367] * Download Enter Message MDF

[0368] Message identifier: 11

[0369] Message contents:

[0370] User/admin indicator

[0371] The exact binary contents of a enter message menu definition file (EMMDF)

[0372] Processing

[0373] The software will store this EMMDF on the RAM disk using the appropriate path and filename based on the user/admin indicator. If and EMMDF already exists on the RAM disk, the software will replace it.

[0374] The locations where the software must look for the PDFs, and the attention it must pay to the proforma version number, depends on whether the software is executing in end-user or admin mode, and whether the software is using the PDF to allow the user to send a new message or whether it is using the PDF to allow the user to view a message in one of the message logs. Note that all of the following requirements pertaining to PDFs also pertain to the LPDFs that are referenced within PDFs.

[0375] When executing in end-user mode, and when the user selects a proforma from a menu in order to send a new message, the software will use the first PDF it finds with the appropriate proforma id by searching the various PDF storage areas in the following order:

[0376] * the ‘admin area’ on the RAM disk

[0377] * the ‘admin area’ on the ROM disk

[0378] * the ‘user area’ on the RAM disk

[0379] * the ‘user area’ on the ROM disk.

[0380] When the user selects a proforma from a menu in order to send a new message and the software is unable to locate a PDF for that proforma, the software will display an “Unable to locate form xxxxx, id nnnn” error alert, where ‘xxxxx’ is the name of the proforma as displayed in the menu and ‘nnnn’ is the proforma id for that proforma.

[0381] When the user selects a proforma from a menu in order to send a new message and the software is unable to locate and LPDF referenced by that proforma, the software will display an “Unable to locate list xxxxx” error alert, where ‘xxxxx’ is the name of the list as referenced in the PDF. When executing in end-user mode, and when the user selects a message from a message log for viewing, the software will use the first PDF it finds with the appropriate proforma id, and with the same version number that was contained in the PDF used to originally create the message, by searching the various PDF storage areas in the following order:

[0382] * the ‘user area’ on the RAM disk

[0383] * the ‘user area’ on the ROM disk.

[0384] When executing in admin mode, and when the user selects a message from a message log for viewing, the software will use the first PDF it finds with the appropriate proforma id, and with the same version number that was contained in the PDF used to originally create the message, by searching the various PDF storage areas in the following order:

[0385] * the ‘admin area’ on the RAM disk

[0386] * the ‘admin area’ on the ROM disk

[0387] * the ‘user area’ on the RAM disk

[0388] * the ‘user area’ on the ROM disk.

[0389] When the user selects a message from a message log for viewing and the software is unable to locate a PDF with the appropriate version number for that message, the software will display and “Unable to locate form xxxxx, id nnnn, vers z.z” error alert, where ‘xxxxx’ is the name of the proforma as stored in the message log, ‘nnnn’ is the proforma id for that proforma, and ‘z.z’ is the version number of the proforma used when the message was created.

[0390] When the user selects a message from a message log for viewing and the software is unable to locate and LPDF with the appropriate version number for that message, the software will display an “Unable to locate list xxxxx, vers z.z” error alert, where ‘xxxxx’ is the name of the list referenced within the PDF for that message, and ‘z.z’ is the version number of the LPDF used when the message was created.

[0391] The software will use any of the three MDFs that exist on the RAM disk, in either the end-user or admin area based on which mode the software is currently executing in, before using the corresponding ones on the Flash-ROM disk. The software will be able to utilize newly downloaded PDFs and LPDFs for incoming messages and newly created messages immediately after they are downloaded. The software will begin utilizing any newly downloaded MDF file the first time the user returns to the Main Menu screen after the file has been downloaded.

[0392] These additional requirements associated with PDFs and LPDFs require a change to the format of the ‘Proforma List’ fixed -format message (fixed-format message number 3). When requested by the TC_SEND_ALL_PROFORMA_VERS proforma command, the software will send the Proforma List fixed-format message (message number 3) with the following new data structure.

[0393] Field List Proforma

[0394] The software requirements in this section relate to the Field List Proforma object. A field list proforma in this context is a list of valid values for fields of type ‘list’ within message proformas. The software will read field list proformas from disk and will use them to control field validation when a message is being entered via the user interface. The software will also use field list proformas to encode the value entered by the user in a ‘list’ field when that value is being included in a message to be transmitted over the network. Each field list proforma object will contain the following attributes:

[0395] * Identifier

[0396] unique identifier for each field list proforma object

[0397] * Version number

[0398] the current version number for the field list proforma identified by the ‘identifier’ attribute

[0399] * List of terms.

[0400] Each item in the list of items will contain one valid value, which can be a variable length string of ASCII characters. When a message is sent that uses this field list proforma, the software will sent the position of the selected value within the list (the first item in the list is at position ).

[0401] Field list proformas will be stored on the Flash-ROM disk. The user interface for creating, modifying and deleting field list proformas, as well as the software required to place field list proformas on the Flash-ROM disk, is external to the application software. Maintenance of field list proformas will be performed by the admin user using external software tools. The software will provide error messages to the user as described below when it encounters errors reading field list proformas. (Note that future version of the software will be require to accept new field list proformas via network messages and to store field list proformas on the RAM disk.)

[0402] MESSAGE LOGS

[0403] The software requirements in this section relate to the Message Log object. A message log in this context is an object that contains a list of message objects. The software will maintain five message logs:

[0404] * Incoming Message Log(IML)

[0405] * Outgoing Message Log (OML)

[0406] * Network Message Log (NML)

[0407] * Saved Message Log (SML).

[0408] * Data Message Log (DML).

[0409] The software will place all user messages transmitted to the DTE into IML, all user messages that are transmitted from the DTE into the OMN, and all network messages (including AMC Control Messages, AMC Configuration Messages and AMC Information Messages) transmitted to or from the DTE into the NML. (Note that the software will also place a message in the OML when the user sends a distress alert.) The software will move all messages in the IML marked as ‘saved’ by the user into the SML. The software will place all incoming and outgoing data messages into the DML.

[0410] The software will ensure that the message logs do not exceed the numbers and sizes specified by the following configuration parameters:

[0411] * Max_Incoming_Msgs_In_Log

[0412] * Max_Outgoing_Msgs_In_Log

[0413] * Max_Network_Msgs_In_Log

[0414] * Max_Saved_Msgs_In_Log

[0415] * Max_Incoming_Msg_Log_Size

[0416] * Max_Outgoing_Msg_Log_Size

[0417] * Max_Network_Msg_Log_Size

[0418] * Max_Saved_Msg_Log_Size.

[0419] * Max_Data_Msg_Log_Size

[0420] * Max_Data_Msgs_In_Log.

[0421] When a message is about to be inserted into the IML, OML, DML or NML that would cause that message log to exceed its maximum number of messages or its maximum size, the software will automatically delete as many old message objects as necessary (‘old’ will be based on sent or received time) before inserting the new message. The software will always delete old ‘read’ messages from the IML prior to deleting old ‘unread’ messages. If the software will delete an ‘unread’ message from the IML to free space for inserting a new message, the software will first print the ‘unread’ message to the DTE' printer if the printer is connected (see Section Printer). When the user indicates that a message in the IML should be saved to the SML and when inserting that message would cause the SML to exceed its maximum number of messages or its maximum size, the software will inform the user that the save operation is not possible.

[0422] The application software will update messages in the OML and NUM as status information regarding the state of their transmission is received from the middleware software. As described in Section Network, this status information included the MRN(s) for the message as well as the message delivery status.

[0423] The software will maintain the message logs on the DTE' RAM disk to ensure persistence in case of software shutdown/reboot, software failure, etc. The requirements specifying how the user interacts with the message logs are described in Section User Interface.

[0424] NETWORK

[0425] The software requirements in this section relate to the Network object. A network in this context is an object over which messages can be sent and received. The software will use the Logon_Required configuration parameter to determine whether or nor the user will log on to and off of the network. (Note that this logon/logoff is a logical logon/logoff across the MMS network; it is not the Standard-C LES logon/logoff.) If logon/logoff is require, the software will allow the user to enter their alias (e.g. user name, truck id, load id) using the logon screen described in Section User Interface. ( Note that if the software is being executed in ‘admin’ mode, the admin user will also enter the ‘admin’ password.) The software will send the entered alias in a ‘Logon’ middleware message to the address specified by the Default_Dest_Addr_Value configuration parameter; note that the address′ type is specified by the Default_Dest_Addr_Type configuration parameter. The software will also include this alias as the ‘source address alias’ in all messages sent from the AMC. If logon/logoff is required, the software will allow the user to log off as described in Section User Interface. When the user logs off, the software will sent the user' alias in a ‘Logoff’ middleware message to the address specified by the Default_Dest_Addr_Value configuration parameter. If logon/logoff is not required, the software will use the value of the Default_Mobile_Alias configuration parameter as the ‘source address alias’ in all messages sent from the AMC.

[0426] The application software will interface with the middleware software to send all user and network messages to the network, receive all user and network messages from the network and to receive status information about the network. The destination address to which the software will send a user message is sometimes determined by the user and other times determined automatically by the software. If the user is initiating a new user message, the software will send the message to the address alias specified by the user when they enter the message. The software will determine the physical address based on the Default_Dest_Addr_Type and Default_Dest_Addr_Value configuration parameters if the AMC is functioning in single primary destination mode, and it will determine the physical address based on the value stored within the AMC's address book if the AMC is functioning in multiple primary destination mode. If the user is replying to an incoming user message and if the AMC is functioning in ‘single’ address mode, the software will automatically determine the reply address based on the following rules:

[0427] * The physical address will be the value of the Default_Dest_Addr_Value configuration parameter

[0428] * If a reply alias was provided in the incoming message, then that alias will be used for the destination address alias

[0429] * If the reply alias was not provided in the incoming message, then the source alias provided by the middleware's header information will be used for the destination address aliases

[0430] If the user is replying to an incoming user message and if the AMC is functioning in ‘multiple’ address mode, the software will automatically determine the reply address based on the following rules:

[0431] * If a reply alias and physical address were provided in the incoming message, then that reply alias will be used for the destination address alias and that reply physical address will be used for the destination physical address

[0432] * If a reply alias and physical address were not provided in the incoming message, then the source alias provided by the middleware's header information will be used for the destination address alias. If that alias exists in the AMC's address book, then the physical address associated with that alias in the address book will be used for the destination physical address. If that alias does not exist in the AMC's address book, then the value of the Default_Dest_Addr_Value configuration parameter will be used for the destination physical address. If the user is replying to an incoming user message, the software will also the user to modify the destination address alias that was automatically determined based on the above rules; the user does this via user interface actions as described in Section User Interface. Note that if the destination address to which a user message reply is being sent does not exist in the AMC's address book, the software will update the address book with that address as described in Section Address Book.

[0433] The destination address to which the software will send a network message is always determined automatically by the software. If the AMC is initiating a new network message, the software will send the message to the address alias named ‘NETWORK’ and the physical address specified by the Default_Nms_Addr_Type and Default_Nms_Addr_Value configuration parameters. If the software is replying to an incoming network message and if the AMC is functioning in ‘single ’ address mode, the software will automatically determine the reply address based on the following rules:

[0434] * The physical address will be the value of the Default_Nms_Addr_Value configuration parameter

[0435] * If a reply alias was provided in the incoming message, then that alias will be used for the destination address alias

[0436] * If the reply alias was not provided in the incoming message, then the source alias provided by the middleware's header information will be used for the destination address alias:

[0437] If the software is replying to an incoming network message and if the AMC is functioning in ‘multiple’ address mode, the software will automatically determine the reply address based on the following rules:

[0438] * If a reply alias and physical address were provided in the incoming message, then that reply alias will be used for the destination address alias and that reply physical address will be used for the destination physical address

[0439] * If a reply alias and physical address were not provided in the incoming message, then the source alias provided by the middleware's header information will be used for the destination address alias. If that alias exists in the AMC's address book, then the physical address associated with that alias in the address book will be used for the destination physical address. If that alias does not exist in the AMC's address book, then the value of the Default_Nms_Addr_Value configuration parameter will be used for the destination physical address.

[0440] Note that if the destination address to which a network reply is being sent does not exist in the AMC's address book, the software will not update the address book with that address; only user messages initiate address book updates; see Section Address Book.

[0441] The software will send all user and network proforma messages at the priority indicated within the message proforma. The software will send all fixed-format messages at the priority indicated by the Fixed_Fmt_Msg_Priority configuration parameter. The application software will request middleware message acknowledgments at the level indicated by the Outgoing_Msg_Ack_Level configuration parameter, and will request the middleware software to continue trying to send the message for the amount of time indicated by the Outgoing_Msg_Time_To_Live configuration parameter. After a message is sent to the network, the application software will receive Middleware Status Messages from the middleware software indicating the MRN(s) of the sent message and the delivery status of the message. The software will update the sent message stored in the Outgoing or Network Message Log with this information. The application software will ensure that it does not attempt to send a message to the middleware software whose length is greater than that specified by the Max_Transmitted_Msg_Len configuration parameter.

[0442] The software will accept ‘Invalid Alias’ fixed-format messages from the network. Upon receiving a message indicating an invalid alias, the software will display a ‘Message Sent to Invalid Address’ message in the status area described in Section User Interface. If that alias exists in the RAM address book, the software will delete that address from the address book.

[0443] Upon receiving a message from the network, the software will perform the processing necessary to acknowledge receipt of the message based on the message acknowledgement level requested by the middleware; the software will send Middleware Control Messages to the middleware software as necessary to complete this processing. (Note that the only acknowledgment level that requires application software processing is ‘application acknowledgement’.) The software will place the received message in the Incoming Message Log or the Network Message Log, depending on whether it is a user message or network message, as described in Section Message Logs.

[0444] The application software will place an indication of any severe middleware software or network errors it detects in the health log described in Section Health Log. The software will place an indication that it received an unknown message (e.g. Invalid message type or message identifier, invalid proforma identifier) into the health log any time it receives a message that it does not recognize; it will also display an ‘Unrecognized Message Received’ message in the status area of the user interface described in Section User Interface.

[0445] Upon receiving a proforma message containing the “ENABLE-HLTH-RPT” command described below, the software will send AMC Periodic Health Messages over the network indicating the current health of the DTE and DCE; the software will send these messages at the frequency indicated by the incoming proforma message and to the destination specified by the Health_Report_DNID and Health_Report_Mem_Num configuration parameters. The software will include the data listed below in these health messages, and will continue sending them until a proforma message is received that contains the “DISABLE-HLTH-RPT” command. The software will use the DCE's ‘initiate user-defined data report’ features to send these health messages.

[0446] The software will allow the user to monitor the current health of the network. The requirements specifying how the user interfaces with this function are described in Section User Interface.

[0447] PRINTER

[0448] The software requirements in this section relate to the printer object. A printer in this context is a device connected to the DTE's parallel port that can accept Epson FX-80 printer commands and ASCII-printable character; its function is to reproduce the given characters on whatever media it supports (e.g. paper, CRT).

[0449] The software will support the printer object. The software will allow the user to print messages and message log lists as described above. The software will begin each printed output at the top of a new page. The requirements specifying how the user activates the ‘print message’ and ‘print message log list’ functions are described in Section User Interface.

[0450] USER INTERFACE

[0451] The software requirements in this section relate to the User Interface object. A user interface in this content is an object that allows the user to communication with the AMC system; it allows the user to command the software to perform functions and it provides visual and audible information to the user. The user interface object in the AMC system comprises of the DTE's keyboard, display, LEDs, and speaker, as well as the optional distress switch attached to the DTE and the optional alarm device attached to the DTE.

[0452] The sections that follow describe the software requirements associated with each of the system components that comprise the user interface. It should be noted that these sections only describe the requirements associated with the user interface; the requirements associated with other system objects that are affected by specific user interface actions (e.g. address book, messages, message logs) are described in the sections that specify the requirements for those system objects. Each of the following sections that describe the user interface screens reference FIGS 8-1 to 8-34 that illustrate how the screen will look on the DTE's display. Main Menu Screen, describes how the user interacts with the DTE's menus; this interaction is the same regardless of which screen is displayed. The general layout of all of the DTE's screens (other than the Logon screen) is also described; this general layout is the same regardless of which screen is displayed. It should be noted that the user interface is the most visible part of the AMC to the user; therefore, the software should be designed in a way that minimizes user interface latency wherever possible.

[0453] Logon Screen

[0454] The software will support the Logon screen as shown in FIG. 8-1, Logon Screen. If the Logon_Required configuration parameter indicates that users will log on to and out of the AMC application software, then the software will display the logon screen upon software initialization.

[0455] If the AMC software is executing in ‘Admin’ mode, then the software will display the logon screen shown in FIG 8-1. The software will allow the user to enter their user name into the USERNAME field. When the user pressed <ENTER> in the USERNAME field, the software will allow the user to enter the ‘admin’ password into the PASSWORD field; the software will display “*” characters as the user enters the characters in the PASSWORD field. When the user presses <ENTER> in the PASSWORD field, the software will validate the entered password against the ‘admin’ password internally configured within the software. If the password passes validation, then the software will display the Main Menu screen Main Menu Screen. If the password does not pass validation, then the software will display an ‘Incorrect Password* Please Re-enter.’ message on the bottom line of the screen, beep the DTE's speaker, clear the information entered by the user in both fields and allow the user to are-enter their user name and password.

[0456] If the AMC software is executing in ‘End-User’ mode, then the software will display the logon screen shown in FIG 8-1 without the PASSWORD field. The software will allow the user to enter their user name into the USERNAME field. Once the user presses <ENTER> in the USERNAME field, the software will display the Main Menu screen.

[0457] Main Menu Screen

[0458] As shown in FIG. 8-2, Main Menu Screen, the Main Menu screen comprises of a menu bar across the top, a screen body in the middle and two information lines at the bottom. All screens displayed on the DTE's display, except for the Logon screen, follow the Main Menu screen's format. For this reason, this section describes the detailed requirements of the menu bar, screen body and information lines for all of the screens.

[0459] Menu Bar

[0460] The menu bar comprises of sic ‘pull-down’ menus. The software will determine the labels at the top of each of these menus, as well as the menu functions and the labels for those functions within each of the pull-down menus (and ‘pop-up’ menus as described below), by reading the DTE's Menu Definition File (MDF) described below. The labels and menu functions shown in the menu bar and menus in FIGS. 8-1 to 8-34, as well as all of the requirement specified above, assume a standard MDF. The software will allow the menu functions described herein to be rearranged within the menu structure based on the MDF. The software will also allow the menu labels for those functions to be changed within the MDF. The only restrictions on changes to the MDF are that there will always be six pull-down menus, the pop-up menus within the ‘Message—Enter’ menu function and the menu items within ‘Quick Send ’ pull-down menu will only designate ‘user’ message proformas, menus will be no more than three levels deep (i.e., one pull-down, a pop-up and another pop-up), and the functions specified within the MDF, i.e., menu functions may be eliminated from the MDF and duplicated within the MDF, but no new menu functions may be added. (Note that the MDF will include all user message proformas installed on the AMC if the user is to have access to them.)

[0461] The software will activate the menu bar when the user pressed the <ALT> key and will position the cursor over the left-most pull-down menu. (Refer to FIGS. 8-3, Main Menu Screen -Quick Send, through 8-9, Main Menu Screen - Terminal, to see the menus as defined in the default MDF.) After pressing the <ALT> key, the software will allow the user to select the desired pull-down menu by either pressing the key shown in parenthesis (assuming that the creator of the current MDF placed parentheses in the menu pane labels) within the menu bar or by using the ‘left’ and ‘right’ arrow keys to move across the menu bar and then pressing the ‘down’ arrow key on the desired pull-down menu. The software will allows the user to deactivate the menu bar at any time by continuing to press the <ESC> key until all pull-down and pop-up menus are closes.

[0462] Once the user has selected the desired pull-down menu, the software will allow the user to move the cursor between the functions within that menu by pressing the ‘up’ and ‘down’ arrow keys. The software will also allow the user to move to another one of the pull-down menus by pressing the ‘left’ and ‘right’ arrow keys. The software will allow the user to select the desired function within a pull-down menu by pressing the <ENTER> key when the cursor is positioned over that function or by pressing the key shown in parenthesis (assuming that the creator of the current MDF placed parentheses in the menu function labels). The software will allow the user to close a pull-down menu and exit the menu bar without selecting a menu function by pressing the <ESC> key. If the user presses <ENTER> when the cursor is positioned over a menu function that has a right arrow displayed next to it, then the software will display the ‘pop-up’ menu associated with that menu function. Once the user has selected a pop-up menu, the software will allow the user to move the cursor between the functions within that menu by pressing the ‘up’ and ‘down’ arrow keys. The software will allow the user to select the desired function within a pop-up menu by pressing the <ENTER> key. The software will allow the user to close a pop-up menu without selecting a menu function by pressing the <ESC> key.

[0463] While the user interacts with the DTE's menus in the same manner regardless of which screen is displayed on the DTE's display, the functions performed by the software when the user selects a menu function are often dependent on the screen that is displayed. When the Main Menu screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0464] When the Main Menu screen is displayed, the software will display and ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0465] Screen Body

[0466] The screen body comprises of the middle portion of the screen between the menu bar on the top and the two information lines on the bottom; this is the portion of the screen that is different among the various screens. While the contents of the screen body differs among screens, the mechanisms for displaying the screen body, exiting the screen body and for accessing the menu bar while in the screen body are the same for all screens.

[0467] The software will allow the user to display any screen by selecting the associated menu function from the DTE's menus (e.g. selecting the Message Logs - View Incoming menu function displays the Incoming Message Log screen). The software will allow the user to exit from any screen and return to the Main Menu screen by pressing the <ESC> key while displaying the screen (assuming that menus are not currently being displayed). The software will allow the user to access the DTE's menus while displaying a screen by pressing the <ALT> key.

[0468] When the Main Menu screen is displayed, the software will display the contents of the Main Menu screen body as shown in FIG. 8-2. The software will prevent the user from changing the contents of this screen.

[0469] Information Lines

[0470] The software will display two information lines on the bottom of the screen, as shown in FIG. 8-2. These two information lines are the same for every screen (other that the Logon screen), except for the screen name and the ‘Page’ numbering. The software will display the number of messages in the incoming message log that haven't been ready by the user, as well as the number of messages currently queued by the middleware software for delivery over the network, in the left-most area within the first information line. The software will display the name of the currently displayed screen in the middle area of the first information line. If the currently display screen could potentially have more than one page (e.g. the Main Menu screen will always be one page, the Enter Message screen may be one or more pages depending on the proforma being used), then the software will display the current page number and the total number of pages within that screen in the right-most area within the first information line (see FIGS. 8-10, Enter Message Screen, for an example).

[0471] The software will display status and non-critical error messages in the left-most area within the second information line (non-critical error messages are those that the user may want to be aware of, but do not require the user to take any action). The software will continue displaying a status message in this area until it displays the next status message. The software will display the current date and time, using the time zone specified by the Default_Time_Zone configuration parameter or the one selected by the user via the Terminal-Configure-Time Zone menu function, in the right-most area within the second information line. The software will update this date and time at an interval based on the Display_Update_Interval configuration parameter.

[0472] Enter Message Screen

[0473] When the Enter Message screen is displayed, the software will display the contents of the Enter Message screen body similar to that shown in FIGS. 8-10, Enter Message Screen. (This requirement says ‘similar’ since most of the screen body is dependent upon the proforma that was selected by the user. See Section Message Proformas, for a description of message proformas.) The software will display the currently select default address in the TO field at the top of the screen body. The software will display the name of the selected message proforma in the MESSAGE TYPE field at the top of the screen body. The software will display the labels for each of the ‘display’ fields (i.e. all fields except automatic data variables and commands) that are defined within the associated on the field type (e.g., integer, float, date), or if the user is exiting a field that is required without entering valid data, then the software will display a message in the status area, beep the DTE's speaker and not allow the user to move the cursor to another field.

[0474] If the user moves the cursor to a ‘list’ field defined within the message proforma, the software will ‘pop up’ a list of valid values for that field. The software will allow the user to scroll through the list of valid values using the up and down arrow keys and the <PG UP> and <PG DN> keys. The software will allow the user to select the desired value from the list by pressing the <ENTER< key when the cursor is positioned over the value. Once the user presses <ENTER> over the desired value, the software will ‘pop down’ the list of valid values and display the selected value next to the list field's label. The software will allow the user to exit the list of valid values without selecting a value by pressing the <ESC> key.

[0475] If the user moves the cursor to a ‘multi-line free-form text’ field defined within the message proforma, the software will ‘pop up’ a sub-screen where the user will be allowed to enter the data for that field. The software will allow the user to move the cursor throughout this sub-screen by pressing the arrow <ENTER>, <PG UP>, <PG DN>, <TAB>, <HOME>, <END>, <END>, <DEL> and <BACKSPACE> keys. The software will allow the user to enter any printable characters into the field. Once the user enters all desired data into this field, the software will allow them to exist this bus-screen by pressing the <ESC> key.

[0476] When the Enter Message screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0477] When the Enter Message screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0478] Incoming Message Log Screen

[0479] When the Incoming Message Log screen is displayed, the software will display the contents of the Incoming Message Log screen body similar to that shown in FIGS. 8-11, Incoming Message Log Screen. (This requirement says ‘similar’ since the screen body is dependent upon the messages currently in the incoming message log.) The software will display the indicated header information for each message currently in the incoming message log. The software will display a “*” in the UNREAD column for each message that has not been read by the user. The software will use the same time zone being used for the current data/time in the bottom information line for all message DATE/TIME RECEIVED times. The software will display a “*” in the REPLY READ column for each message that requires a user reply (based upon the definition of the message proforma for the incoming message and whether or not the user has already replied to the message). The software will sort all unread messages to the top of the list. Within unread messages, the software will sort the messages in PRIORITY order followed by DATE/TIME RECEIVED within priority. Within read messages, the software will sort the messages based on the DATE/TIME RECEIVED.

[0480] The software will initially highlight the first message displayed in the log. The software will allow the user to scroll through all messages in the log using the up and down arrow keys. If the user presses the <ENTER> key with the cursor positioned over a given message, the software will display the View Message screen with that message. When the Incoming Message Log screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0481] When the Incoming Message Log screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0482] View Message Screen

[0483] When the View Message screen is displayed, the software will display the contents of the View Message screen body similar to the two screens shown in FIGS. 8-12, view Message Screen—Incoming Message, and 8-13, View Message Screen—Outgoing Message. (This requirement says ‘similar’ since most of the screen body is dependent upon the proforma that is used by the message being displayed. See Section Message Proformas, for a description of message proformas.) The software will display the message header information in the top two lines of the screen body, along with an indication of which log this message is being viewed from (Incoming, Outgoing or Saved; network messages cannot be viewed). Note that the user can display the Message Reference Numbers (MRNs) associated with this message by selecting the ‘Message—View MRNs’ menu function (see Section View MRNs Screen).

[0484] If the message proforma used for the message being displayed spans more than one page (the right-most area of the first information line will specify more than one total pages for this screen), then the software will allow the user to display the various pages by using the <PG UP> and <PG DN> keys. The software will prevent the user from modifying the contents of the View Message screen.

[0485] When the View Message screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0486] When the View Message screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0487] View MRNs Screen

[0488] When the View MRNs screen is displayed, the software will display the contents of the View MRNs screen body as shown in FIGS. 8-14, View MRNs Screen. The software will display the Message Reference Numbers (MRNs) associated with the message that was displayed on the View Message screen when that screen was displayed. (The MRNs are determined from the Local—Middleware Status Messages described above). The software will display a ‘P’ preceding an MRN if a Positive Delivery Notification (PDN) has been received for that MRN. The software will display an ‘N’ preceding an MRN if a Negative Delivery Notification (NDN) has been received for that MRN. The software will display a ‘*’ preceding an MRN if either a PDN nor an NDN has been received for that MRN. The software will initially position the cursor over the first MRN in the list. The software will allow the user to scroll through the list of MRNs using the up and down arrow keys. The software will prevent the user from modifying the contents of this screen. The software will allow the user to exit this screen and return to the View Message screen by pressing the <ESC> key.

[0489] When the View MRNs screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function.

[0490] Outgoing Message Log Screen

[0491] When the Outgoing Message Log screen is displayed, the software will display the contents of the Outgoing Message Log screen body similar to that shown in FIGS. 8-15, Outgoing Message Log Screen. (This requirement says ‘similar’ since the screen body is dependent upon the messages currently in the outgoing message log.) The software will display the indicated header information for each message currently in the outgoing message log. The software will use the same time zone being used for the current date/time in the bottom information line for all message DATE/TIME SENT times. The software will display the current delivery status of each outgoing message; if the delivery status indicates that delivery failed, the software will display the status and reason code (as reported by the middleware software) associated with the delivery status. The software will sort the messages in an order determined by the DATE/TIME SENT for the message.

[0492] The software will initially highlight the first message displayed in the log. The software will allow the user to scroll through all messages in the log using the up and down arrow keys. If the user presses the <ENTER> key with the cursor positioned over a given message, the software will display the View Message screen with that message. When the Outgoing Message Log screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0493] When the Outgoing Message Log screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0494] Saved Message Log Screen

[0495] When the Saved Message Log screen is displayed, the software will display the contents of the Saved Message Log screen body similar to that shown in FIGS. 8-16, Saved Message Log Screen. (This requirement says ‘similar’ since the screen body is dependent upon the messages currently in the saved message log.) The software will display the indicated header information for each message currently in the saved message log. The software will use the same time zone being used for the current date/time in the bottom information line for all message DATE/TIME RECEIVED times. The software will display a “*” in the REPLY REQUIRED column for each message that requires a user reply (based upon the definition of the message proforma for the saved message and whether or not the user has already replied to the message). The software will sort the messages in an order determined by the DATE/TIME RECEIVED for the message.

[0496] The software will initially highlight the first message displayed in the log. The software will allow the user to scroll through all messages in the log using the up and down arrow keys. If the user presses the <ENTER> key with the cursor positioned over a given message, the software will display the View Message screen with that message.

[0497] When the Saved Message Log screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0498] When the Saved Message Log screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0499] Network Message Log Screen

[0500] When the Network Message Log screen is displayed, the software will display the contents of the Network Message Log screen body similar to that shown in FIGS. 8-17, Network Message Log Screen. (This requirement says ‘similar’ since the screen body is dependent upon the messages currently in the network message log.) The software will display the indicated header information for each message currently in the network message log. The software will use the same time zone being used for the current date/time in the bottom information line for all messages DATE/TIME SENT/RECEIVED times. The software will display the current delivery status of each outgoing network message; if the delivery status indicates that delivery failed, the software will display the error code associated with the delivery status. The software will sort the messages in an order determined by the DATE/TIME SENT/RECEIVED for the message.

[0501] The software will initially highlight the first message displayed in the log. The software will allow the user to scroll through all messages in the log using the up and down arrow keys. If the user presses the <ENTER> key with the cursor positioned over a given message, the software will display an ‘Invalid Selection’ message since network messages cannot be viewed on the screen.

[0502] When the Network Message Log screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0503] When the Network Message Log screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0504] Enter Address Screen

[0505] When the Enter Address screen is displayed, the software will display the contents of the enter Address screen body as shown in FIGS. 8-18, Enter Address Screen. The software will allow the user to enter an address in the ADDRESS field. When the user presses <ENTER>, the software will ensure that the entered address only contains alphanumeric characters. If it does, the software will return to the Enter Message screen and display the entered address in the TO field of that screen. If it does not, the software will display an ‘Invalid Address’ message in the status area, and allow the user to re-enter the address. The software will allow the user to exit this screen without entering an address by pressing the <ESC> key.

[0506] When the Enter Address screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function.

[0507] Select address screen

[0508] When the Select Address screen is displayed, the software will display the contents of the Select Address screen body as shown in FIGS. 8-19, Select Address Screen. The software will display the addresses in alphabetical order based on the address alia. The software will initially position the cursor over the first address in the list. The software will allow the user to scroll through the list of addresses using the up and down arrow keys. The software will allow the user to select an address by pressing <ENTER> when the cursor is positioned over the desired address. When the user selects an address, and if this screen was displayed while the user was entering a message in the Enter Message screen, the software will return to the Enter Message screen and display the selected address in the TO field of that screen. If this screen was displayed as the result of the user sending a message to an address alias that was not in the address book, the software trying to add the alias to the address book and the software determining that the address book was full, the software will delete the address selected by the user and return to the screen that was displayed when the user request the ‘send message’ menu function. The software will allow the user to exit this screen without selecting an address by pressing the <ESC> key.

[0509] When the Select Address screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function.

[0510] Select Default Address Screen

[0511] When the Select Default Address screen is displayed, the software will display the contents of the Select Default Address screen body as shown in FIGS. 8-20, Select Default Address Screen. The software will display the addresses in alphabetical order. The software will initially position the cursor over the first address in the list. The software will allow the user to scroll through the list of addresses using the up and down arrow keys. The software will allow the user to select an address by pressing <ENTER> when the cursor is positioned over the desired address. When the user selects an address, the software will save that address as the default address to be initially displayed when the user displays the Enter Message screen. The software will allow the user to exit this screen without selecting an address by pressing the <ESC> key.

[0512] When the Select Default Address screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0513] When the Select Default Address screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0514] Monitor Transceiver Status Screen

[0515] When the Monitor Transceiver Status screen is displayed, the software will display the contents of the Monitor Transceiver Status screen body similar to that shown in FIGS. 8-21, Monitor Transceiver Status Screen—Page 1, and FIGS. 8-22, Monitor Transceiver Status Screen—Page 2. (This requirement says ‘similar’ since most of the screen body is dependent upon the current status of the transceiver and DTE.) The software will display the most recently retrieved values of all of the listed transceiver and DTE values (including POSITION) when the screen is initially displayed. The software will query the transceiver and DTE for new values and display those new values on the screen at a rate no less than that specified by the Display_Update_Interval configuration parameter. The software will display the rate at which it is updating the screen in the SCREEN UPD. RATE field on the screen. If the user has elected to ‘Show Events’, the software will display all transceiver events (see ‘Local—DCE Event Messages’) received from the middleware software in the TRNCVR EVENT field on the screen in ‘event_code:last 50 characters’ format, where ‘event_code’ is the number contained in the first line of every event message and ‘last 50 characters’ represents the last 50 characters within the event message. If the ‘last 50 characters’ does not contain the entire event message, then the software will display ‘. . .’ between the ‘:’ and the ‘last 50 characters’. If the user has elected to not ‘Show Events’, the software will display “Not Shown” in the TRNSCVR EVENT field.

[0516] The software will allow the user to move between the pages of this screen using the <PG UP> and <PG DN> keys. The software will prevent the user from modifying any of the information on this screen. The software will allow the user to halt the status query process and to exit this screen at any time by pressing the<ESC> key.

[0517] when the Monitor Transceiver Status screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0518] When the Monitor Transceiver Status screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0519] Transceiver Configuration Screen

[0520] When the Transceiver Configuration screen is displayed, the software will display the contents of the Transceiver Configuration screen body similar to that shown in FIGS. 8-23, Transceiver Configuration Screen. (This requirement says ‘similar’ since most of the screen body is dependent upon the current configuration of the transceiver.) The software will query the transceiver for each of its configuration parameters shown in FIGS. 8-23, and will display each of them as they are received from the transceiver. The software will prevent the user from modifying any of the information displayed on this screen. The software will allow the user to halt the parameter query process and to exit this screen at any time by pressing the <ESC> key.

[0521] When the Transceiver Configuration screen is displayed, the software will perform the following actions when the user selects the specified menu function (note that the software will halt the parameter query process when any menu function is selected that displays another screen):

[0522] When the Transceiver Configuration screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0523] Transceiver List Configuration Screen

[0524] When the Transceiver List Configuration screen is displayed, the software will display the contents of the Transceiver List Configuration screen body similar to that shown in FIGS. 8-24, Transceiver List Configuration Screen. (This requirement says ‘similar’ since most of the screen body is dependent upon the current configuration of the transceiver.) The software will display the configuration parameter being queried at the top of the screen body where FIGS. 8-24 reads “PARAMETER NAME GOES HERE”. The software will query the transceiver for the list of values associated with the configuration parameter whose name is shown, and will display each of the values as they are received from the transceiver. The software will prevent the user from modifying any of the information displayed on this screen. The software will allow the user to scroll through the list of displayed values using the up and down arrow keys. The software will allow the user to halt the parameter query process and to exit this screen at any time by pressing the <ESC> key.

[0525] When the Transceiver List Configuration screen is displayed, the software will perform the following actions when the user selects the specified menu function (note that the software will halt the parameter query process when any menu function is selected that displays another screen):

[0526] When the Transceiver List Configuration screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0527] Enter Data Report Identifier Screen

[0528] When the Enter Data Report Identifier screen is displayed, the software will display the contents of the Enter Data Report Identifier screen body as shown in FIGS. 8-25, Enter Data Report Identifier Screen. The software will allow the user to enter the identifier for the data report to be sent in the DATA REPORT ID field. When the user presses <ENTER>, the software will ensure that the user entered a valid data report identifier. If they did, the software will command the transceiver to initiate the specified data report. If they did not, the software will display an ‘Invalid Data Report Identifier’ message in the status area, and allow the user to re-enter the data report identifier. The software will allow the user to exit this screen without entering a data report identifier by pressing the <ESC> key.

[0529] When the Enter Data Report Identifier screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function.

[0530] Login Transceiver Screen

[0531] When the Login Transceiver screen is displayed, the software will display the contents of the Login Transceiver screen body as shown in FIGS. 8-26, Login Transceiver Screen. The software will allow the user to enter the identifier for the TDM channel to be logged into in the TDM CHANNEL ID field. When the user presses <ENTER>, the software will ensure that the user entered a valid TDM channel identifier. If they did, the software will command the transceiver to log into the specified TDM channel. If they did not, the software will display an ‘Invalid TDM Channel Identifier’ message in the status area, and allow the user to re-enter the TDM channel identifier. The software will allow the user to exit this screen without entering a TDM channel identifier by pressing the <ESC> key.

[0532] When the Login Transceiver screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function.

[0533] PVT Results Screen

[0534] When the PVT Results screen is displayed, the software will display the contents of the PVT Results screen body similar to that shown in FIGS. 8-27, PVT Results Screen. (This requirement says ‘similar’ since most of the screen body is dependent upon the results of the PVT.) The software will query the transceiver for the results of its most recent PVT, and will display those results in the PVT RESULTS field. If the PVT results span more than one page, the software will allow the user to view the multiple pages using the <PG UP> and <PG DN> keys. The software will prevent the user from modifying any of the information displayed on the screen.

[0535] When the PVT Results screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0536] When the PVT Results screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0537] Enter Transceiver Configuration Filename Screen

[0538] When the Enter Transceiver Configuration Filename screen is displayed, the software will display the contents of the Enter Transceiver Configuration Filename screen body as shown in FIGS. 8-28, Enter Transceiver Configuration Filename Screen. The software will allow the user to enter the drive, pathname and filename of the file that contains transceiver configuration parameters to be modified. When the user presses <ENTER>, the software will ensure that the entered filename exists. If it does, the software will read the file and command the transceiver to change each of the configuration parameters listed in the file to the values provided in the file. If it does not, the software will display an ‘Invalid Filename’ message in the status area, and allow the user to re-enter the filename. As the software is reading each of the configuration commands and sending them to the transceiver, it will display any errors encountered during the process in the status area. The software will allow the user to halt the configuration command process at any time by pressing the <ESC> key. The software will allow the user to exit this screen without entering a filename by pressing the <ESC> key.

[0539] When the Enter Transceiver Configuration Filename screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function.

[0540] About Terminal Screen

[0541] When the About Terminal screen is displayed, the software will display the contents of the About Terminal screen body as shown in FIGS. 8-29, About Terminal Screen. The software will display the customer service phone number as provided by the Cust_Serv_Num configuration parameter in the CUSTOMER SERVICE field. The software will prevent the user from modifying any of the information displayed on the screen.

[0542] When the About Terminal screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0543] When the About Terminal screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0544] Select Time Zone Screen

[0545] When the Select Time Zone screen is displayed, the software will display the contents of the Select Time Zone screen body as shown in FIGS. 8-30, Select Time Zone Screen. The software will initially position the cursor over the first time zone in the list. The software will allow the user to scroll through the list of time zones using the up and down arrow keys. The software will allow the user to select a time zone by pressing <ENTER> when the cursor is positioned over the desired time zone. When the user selects a time zone, the software will save that time zone as the one to use when displaying all dates and times on any of the DTE's screens. The software will allow the user to exit this screen without selecting a time zone by pressing the <ESC> key.

[0546] When the Select Time Zone screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0547] When the Select Time Zone screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information lien when the user selects any menu function not listed in the table.

[0548] Terminal Configuration Screen

[0549] When the Terminal Configuration screen is displayed, the software will display the contents of the Terminal Configuration screen body similar to that shown in FIGS. 8-31, Terminal Configuration Screen—Page 1, and 8-32, Terminal Configuration Screen—Page 2. (This requirement says ‘similar’ since most of the screen body is dependent upon the current configuration of the DTE.) The software will display each of the DTE configuration parameters shown in FIGS. 8-31 and 8-32 as read from the DTE Configuration File. The software will allow the user to view the multiple pages of this screen using the <PG UP> and <PG DN> keys. The software will prevent the user from modifying any of the information displayed on this screen.

[0550] When the Terminal Configuration screen is displayed, the software will perform the following actions when the user selects the specified menu function:

[0551] When the Terminal Configuration screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function not listed in the table.

[0552] Alert Screen

[0553] When the Alert screen is displayed, the software will display the contents of the Alert screen body similar to that shown in FIGS. 8-33, Alert Screen. (This requirement says ‘similar’ since most of the screen body is dependent upon the alert being displayed.) When this screen is displayed, the software will also beep the speaker as described below. The software will display a specific alert and will continue to display the alert until the user presses the <ESC> key; the software will exit this screen when the user presses the <ESC> key.

[0554] When the Alert screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function.

[0555] Prompt Screen

[0556] When the Prompt screen is displayed, the software will display the contents of the Prompt screen body similar to that shown in FIGS. 8-34, Prompt Screen. (This requirement says ‘similar’ since most of the screen body is dependent upon the prompt being displayed.) When this screen is displayed, the software will also beep the speaker as described below. The software will display a specific prompt and will continue to display the prompt until the user presses the ‘Y’ or ‘N’ key; the software will exit this screen when the user presses one of these two keys. The software will display an ‘Invalid Selection’ message in the status area if the user presses any other key (not that the <EMG> and <SEND> keys described below are always valid keys).

[0557] When the Prompt screen is displayed, the software will display an ‘Invalid Selection’ message in the status area of the second information line when the user selects any menu function.

[0558] Message LED

[0559] Upon receipt of a user message (as opposed to a network message) from the middleware software by the application software, the software will blink the message LED continuously until the user views one ‘unread’ message in the incoming or saved message log. Once the user has viewed one unread message, the software will light the message LED until the user has viewed all unread messages. If the message LED is lit, and if the application software receives a new user message, the software will again blink the message LED continuously until the user views one unread message. The software will extinguish the message LED when there are no unread messages in the incoming or saved message logs.

[0560] Ready LED

[0561] The application software will light the ready LED whenever the middleware software reports that the DCE is available for message communications. The application software will extinguish the ready LED whenever the middleware software reports that the DCE is not available for message communications. The application software will blink the ready LED continuously for 30 seconds upon receipt of a distress alert acknowledgement event from the DCE. At the end of the 30 second period, the application software will either light or extinguish the ready LED based on the current status of the DCE as reported by the middleware software.

[0562] Speaker

[0563] The software will cause the DTE's speaker to warble (multi-frequency sound) whenever the application software receives a user message from the middleware software. If the Msg_Chirp_Int configuration parameter is set to a positive number, the software will continue to chirp (short, single-frequency sound) the speaker at the interval (in seconds) specified by the configuration parameter until the user has read all unread messages; the software will stop chirping the speaker once all unread messages have been read. If the Msg_Chirp_Squelch configuration parameter indicates that chirp squelching is enabled, and if the software is chirping the speaker due to unread messages, the software will allow the user to disable the periodic message chirps by pressing any key on the DTE's keyboard. (Note that the initial warble and the periodic chirps will resume when the software receives another user message.)

[0564] In addition to these message related speaker sounds, the software will beep the speaker any time the software displays the Alert screen or the Prompt screen. The software will beep the speaker any time the ‘Invalid Selection’ message is displayed in the status area. The software will also beep the speaker any time the user enters invalid data in a field within the Enter Message screen.

[0565] Distress Switch and Emergency/Send Keys

[0566] The software will monitor keyboard input for an indication that the user has either activated the distress switch or pressed the <EMG> key followed by the <SEND> key. Upon determining that either of these events has occurred, the software send an ‘emergency’ message to the middleware. The middleware software will immediately command the DCE to send a distress alert. The software will respond to a distress alert acknowledgement from the LES.

[0567] Alarm Device

[0568] The software will activate the DTE's alarm device each time a user message is received at the DET.

[0569] CONFIGURATION FILES AND ADDRESS BOOK

[0570] This portion describes the requirements of the static configuration files used by the AMC software and the meaning of each of the configuration parameters required within these files. It describes the Flash-ROM address list and the RAM address list that together form the AMC's address book. It also describes the message proforma and field list proforma definition files.

[0571] DTE Configuration File(s)

[0572] These files (the parameters listed below may be divided among several files for configuration management and automatic generation purposes) will contain configuration parameters read by the application software upon initialization in order to configure the state of the AMC. The parameters to be included within these files are as follows:

[0573] Addr_mode

[0574] indicates whether the AMC is to function in single primary destination address mode or multiple primary destination address mode; i.e., whether the Flash-ROM and RAM address lists only contain destination address aliases or whether they contain destination address aliases and physical addresses for each address alias.

[0575] valid values: S, M

[0576] Cust_Serv_Num

[0577] this is the phone number of a satellite network customer service center

[0578] valid values: (999)999-9999

[0579] Default_Data_Addr_Type

[0580] Indicates whether the default data address is a DNID, Network, SAC or Mobile Id.

[0581] Default_Data_Addr_Value

[0582] Indicates the default data address value. Valid values:

[0583] if Default_Data_Addr_Type is ‘D’: 0-65535

[0584] if Default_Data_Addr_Type is ‘N’: valid X.121 address

[0585] if Default_Data_Addr_Type is ‘S’: 2-6 character alphanumeric string

[0586] if Default_Data_Addr_Type is ‘M’: 1-999999999

[0587] Default_Mobile_Alias

[0588] this is the address alias of this AMC in cases where the user is not required to logon/logoff

[0589] valid values: 1-8 character alphanumeric string (e.g. AB1DE2G3)

[0590] Default_Dest_Addr_Type

[0591] if this AMC should always send messages to a default destination address (based on ‘Addr_Mode’), this indicates whether that address is a ‘DNID’, ‘Network’, SAC or Mobile Id

[0592] valid values: D, N, S, M

[0593] Default_Dest_Addr_Value

[0594] if this AMC should always send messages to a default destination address (based on ‘Addr_Mode’), this indicates the value of that address

[0595] valid values:

[0596] if Default_Dest_Addr_Type is ‘D’: 0-65535

[0597] if Default_Dest_Addr_Type is ‘N’: valid X.121 address

[0598] if Default_Dest_Addr_Type is ‘S’: 6 character alphanumeric string

[0599] if Default_Dest_Addr_Type is ‘M’: 1-999999999

[0600] Default_Nms_Addr_Type

[0601] this indicates whether the default network management station's address is a ‘Mailbox’ address or whether it is an ‘Network’ address

[0602] valid values: D, N, S, M

[0603] Default_Nms_Addr_Value

[0604] this indicates the value of the default network management station's address

[0605] valid values:

[0606] if Default_Nms_Addr_Type is ‘D’: 0-65535

[0607] if Default_Nms_Addr_Type is ‘N’: valid X.121 address

[0608] if Default_Nms_Addr_Type is ‘S’: 6 character alphanumeric string

[0609] if Default_Nms_Addr_Type is ‘M’: 1-999999999

[0610] Default_Time_Zone

[0611] indicates the default time zone that should be used when displaying all times on this AMC

[0612] valid values: AST, ADT, CST, CDT, EST, EDT, HST, HDT, MST, MDT, PST, PTD

[0613] Display_Update_Interval

[0614] indicates the number of seconds that should elapse between updates of the DCE information displayed on the DTE's monitor and the current date and time displayed on the DTE's monitor

[0615] valid values: 1-65535

[0616] Fixed_Fmt_Msg_Priority

[0617] this indicates the priority at which the software will send all fixed-format messages over the network (note that proforma messages are sent at the priority indicated within their message proforma)

[0618] valid values: 5, 7, 9

[0619] Health_Log_Update_Interval

[0620] indicates the number of seconds that should elapse between updates of the DTE and DCE health information in the AMC health log

[0621] valid values: 1-65535

[0622] Health_Report_DNID

[0623] indicates the DNID to which the periodic health reports are to be sent

[0624] valid values: 0-65535

[0625] Health_Report_Mem_Num

[0626] indicates the member number to which the periodic health reports are to be sent

[0627] valid values: 0-255

[0628] Logon_Required

[0629] indicates whether or not the application software should require the user to log on before using the AMC and to log off when finished using the AMC

[0630] valid values: Y, N

[0631] Max_Auto_Data_Age

[0632] indicates the maximum allowable age for DCE health information that is to be included in automatic data variables within message proformas; i.e., the software will query the DCE for its health information at least every n seconds, where n is specified by this parameter

[0633] valid values: 1-65535

[0634] Max_Data_Msg_Log_Size

[0635] indicates the maximum size (in Kbytes) of the data message log

[0636] Max_Data_Msgs_In_Log

[0637] indicates the maximum number of messages that can be placed in the data message log

[0638] Max_Health_Log_Size

[0639] indicates the maximum size (in Kbytes) of the AMC health log

[0640] valid values: 1-65535

[0641] Max_Incoming _Msg_Log_Size

[0642] indicates the maximum size (in Kbytes) of the incoming message log

[0643] valid values: 1-65535

[0644] Max_Incoming _Msgs_In_Log

[0645] indicates the maximum number of messages that can be placed into the incoming message log

[0646] valid values: 1-65535

[0647] Max_Network_Msg_Log_Size

[0648] indicates the maximum size (in Kbytes) of the network message log

[0649] valid values: 1-65535

[0650] Max_Network_Msgs_In_Log

[0651] indicates the maximum number of messages that can be placed into the network message log

[0652] valid values: 1-65535

[0653] Max_Operating_Speed

[0654] indicates the speed (as determined from the DCE) at which the application software will deactivate the DTE's LCD; a negative number indicates that the application software should never deactivate the DTE's LCD; zero is an invalid number

[0655] valid values: −1, 1-100

[0656] Max_Outgoing_Msg_Log_Size

[0657] indicates the maximum size (in Kbytes) of the outgoing message log

[0658] valid values: 1-65535

[0659] Max_Outgoing_Msgs_In_Log

[0660] indicates the maximum number of messages that can be placed into the outgoing message log

[0661] valid values: 1-65535

[0662] Max_RAM_Addresses

[0663] indictes the maximum number of addresses that can be placed into the RAM address list

[0664] valid values: 1-65535

[0665] Max_Saved_Msg_Log_Size

[0666] indicates the maximum size (in K bytes) of the saved message log

[0667] valid values: 1-65535

[0668] Max_Saved_Msgs_In_Log

[0669] indicates the maximum number of messages that can be placed into the saved message log

[0670] valid values: 1-65535

[0671] Max_Transmitted_Msg_Len

[0672] indicates the maximum size of any message that can be given to (or received from) the middleware for transmission over the network

[0673] valid values: 1-2147483648 (32767 for EMS)

[0674] Msg_Chirp_Int

[0675] specifies the interval (in seconds) at which the software should sound the DTE's speaker (i.e. ‘chirp’) when an incoming message exists that has not been read by the user; a negative number indicates that the speaker should never ‘chirp’ for this reason; zero is an invalid value; note that this parameter has no affect on the sound made by the speaker when a message initially arrives

[0676] valid values: 1, 1-255

[0677] Msg_Chirp_Squelch

[0678] indicates whether or not the user is allowed to squelch the ‘new message’ chirps by pressing a key on the DTE'keyboard

[0679] valid values: Y,N

[0680] Outgoing_Msg_Ack_Level

[0681] indicates the message acknowledgement level that the application software should request of the middleware software when giving it messages for transmission over the network

[0682] valid values: Dev, Serv, Tout, Appl

[0683] Outgoing_Msg_Time_To_Live

[0684] indicates the ‘time-to-live’ value (in minutes) that the application software should request of the middleware software when giving it a message for transmission over the network; the middleware will use this value to ‘expire’ the message if it can't transmit it after the given amount of time

[0685] valid values: 1-65535

[0686] Menu Definition File

[0687] This file will contain information read by the application software upon initialization in order to configure the AMC's user interface menus. The file will contain:

[0688] A list of menu panes.

[0689] For each menu pane defined within the file, the file contains:

[0690] The number of menu items in that pane

[0691] A list of menu items in that pane.

[0692] For each menu item defined within the file, the file contains:

[0693] The alias to be displayed on the screen for that menu item

[0694] The action to be performed when that menu item is selected; actions may be:

[0695] Display another menu pane (if this menu item is for a ‘cascading’ menu item)

[0696] Enter a message using the given proforma identifier

[0697] Perform a software function (e.g. display a screen, select an address, configure DCE)

[0698] DCE Configuration File

[0699] This file will contain information read by admin application software in order to configure the DCE. For each DCE configuration parameter to be set, the file will contain:

[0700] An alias for the configuration parameter

[0701] The new value for the configuration parameter.

[0702] The configuration file may be used to set any of the DCE configuration parameters listed below. Note that this file is only read by the admin software when the admin user requests that the DCE be configured; it is not meant to always contain the current configuration of the DCE.

[0703] Flash-ROM Address List

[0704] This file will contain the addresses that form the ‘Flash-ROM’ portion of the AMC address book. The contents of this file are dependant upon the Addr_Mode configuration parameter. If that configuration parameter indicates that all messages sent from the AMC should be sent to the address specified by the Default_Dest_Addr_Value configuration parameter, then this file will simply contain a list of 1-8 alphanumeric character address aliases. If the Addr_Mode configuration parameter indicates that the default address should not always be used, then this file will contain a list of addresses, where each address will contain the following information:

[0705] Address alias (1-8 alphanumeric characters)

[0706] Address type (DNID, Network, SAC or Mobile Id)

[0707] Address value (1-14 alphanumeric characters).

[0708] RAM Address List

[0709] The file will contain the addresses that form the ‘RAM’ portion of the AMC address book. The contents of this file will dynamically change based on replies to user messages and user interface actions, as described in the Address Book, and User Interface Sections. This file will contain a list of addresses, where each address will contain the following information:

[0710] Address alias (1-8 alphanumeric characters)

[0711] Address type (DNID, Network, SAC or Mobile Id)

[0712] Address value (1-14 alphanumeric characters).

[0713] Message Proforma Definition Files

[0714] These files will contain the definitions of the message proformas to be used by messages transmitted to and from the AMC. Each file will contain the definition of one message proforma object. The files will contain values for all of the attributes of a message proforma object as described in Section Message Proforma.

[0715] Field List Proforma Definition Files

[0716] These files will contain the definitions of the field list proformas referenced within message proformas used by messages transmitted to and from the AMC. Each file will contain the definition of one field list proforma object. The files will contain values for all of the attributes of a field list proforma object as described in Section Field List Proforma.

[0717] This portion specifies the data that the software will periodically place into the AMC health log, as well as the data software will periodically transmit over the network in a health report. (Note that the software also places additional data into the health log such as DCE events described below and indications of severe software, network and middleware errors.)

[0718] Health Log Data

[0719] As required by the Health Log, the software will periodically place the following data into the AMC health log:

[0720] UTC date/time that entry is being logged (from DTE)

[0721] DCE Bulletin board error rate (BBER)

[0722] DCE Signal Strength

[0723] GPS-derived lat/lon

[0724] GPS-derived course over ground (COG)

[0725] GPS-derived speed over ground (SOG)

[0726] DCE “Logged-in” state

[0727] DCE “Locked” state

[0728] DCE activity

[0729] DCE currently tuned TDM ID

[0730] DCE currently tuned TDM channel frequency

[0731] Number of unread messages in the incoming messages log

[0732] Number of outgoing messages queued by the middleware

[0733] Percentage of DTE RAM disk used

[0734] Percentage of DTE conventional RAM used.

[0735] Periodic Health Report Data

[0736] Upon request as required in Section Network, the software will periodically send the following health report data over the network:

[0737] DCE Bulletin board error rate (BBER)

[0738] DCE Signal Strength

[0739] GPS-derived lat/lon

[0740] GPS-derived course over ground (COG)

[0741] GPS-derived speed over ground (SOG)

[0742] DCE “Logged-in” state

[0743] DCE “Locked” state

[0744] DCE activity

[0745] Number of unread messages in the incoming messages log

[0746] Number of outgoing messages queued by the middleware

[0747] Percentage of DTE RAM disk used

[0748] Percentage of DTE conventional RAM used.

[0749] This portion described the ‘application’ contents of all messages transmitted between the application software and the middleware software, including user and network messages to be sent and received via the satellite network, and local messages to be sent to and received from the middleware and the DCE. Note that this section only addresses the required contents of messages at the ‘application’ level; it does not address the actual message contents transmitted over the network after the middleware software adds necessary control and routing information, nor does it address the actual data formats for each field within the messages.)

[0750] User and Network Messages

[0751] The application portion of all user and network messages will contain:

[0752] Message class (proforma [0] vs fixed-format [1])

[0753] Reply address present flag (indicates whether or not the ‘Reply’ fields are present)

[0754] Reply alias

[0755] Reply address type (DNID, ‘Network’, Special Access Code, Mobile Id)

[0756] Reply physical address.

[0757] The contents of the remainder of the application portion of messages depends on whether the ‘message class’ is ‘proforma’ or ‘fixed-format’. The remainder of the application portion for all user and network proforma messages will contain:

[0758] Message proforma identifier

[0759] Proforma version (major/minor version number)

[0760] Field values as indicated by the messages proforma.

[0761] The remainder of the application portion for all fixed-format network messages will contain (note that all user messages are proforma messages):

[0762] Message identifier

[0763] Message contents in a fixed format based on the messages identifier.

[0764] The following lists all fixed-format network messages along with their required contents:

[0765] File

[0766] Message identifier: 1

[0767] Message contents:—the exact binary contents of the file being transmitted (including cr/lf, etc.)

[0768] DCE Config Changed

[0769] Message identifier: 2

[0770] Message contents:—the serial number of the DCE

[0771] Proforma List

[0772] Message identifier: 3

[0773] Message contents:—a list of message and field list proforma identifiers and associated version numbers

[0774] PVT Results

[0775] Message identifier: 4

[0776] Message contents:—the exact contents of the PVT results

[0777] Invalid Alias

[0778] Message identifier: 5

[0779] Message contents:—the alias that is invalid

[0780] Command

[0781] Message identifier: 6

[0782] Message contents:—a list of commands, and associated status displays and command data, to be executed by the application software

[0783] Local Messages

[0784] The application portion of all local, middleware-related fixed-format messages will contain data. The application portion of all local, DCE-related fixed-format messages will contain commands and command responses from the Trimble transceiver. Note that all local messages are fixed-format messages.

[0785] This section lists the DCE Command Messages and DCE Configuration Messages that the software will send to the DCE as required; it also lists the DCE Event Messages that the software will recognize and place into the AMC health log.

[0786] DCE Command Messages

[0787] The software will be able to send the following command messages to the DCE for the format and values of associated parameters):

[0788] initiate PVT

[0789] log in to TDM [Admin]

[0790] log out of TDM [Admin]

[0791] send distress alert

[0792] send data report

[0793] initiate spot beam roam

[0794] force clear [Admin]

[0795] query login mode

[0796] query mobile number

[0797] query EGC only (out of service) flag

[0798] query diagnostics DCE feedback flag

[0799] query signalling DCE feedback flag

[0800] query DCE alarms flag

[0801] query DTE alarms flag

[0802] query DNID/member number/LES Id list

[0803] query ENID list

[0804] query generate data reports power up/down flag

[0805] query data report generation intervals

[0806] query burst retry count

[0807] query burst uncertain retry count

[0808] query power down timer

[0809] query message type routing

[0810] query transmit packet limit

[0811] query MT mode

[0812] query roaming parameters

[0813] query serial #, Inmarsat #, model #, firmware revision #,

[0814] query date/time

[0815] query current frame #

[0816] query currently tuned TDM frequency

[0817] query BBER

[0818] query INF information

[0819] query PVT results

[0820] query LES status.

[0821] DCE Configuration Messages

[0822] The software will be able to send the following configuration messages to the DCE for the format and values of associated parameters):

[0823] set login mode [Admin]

[0824] set mobile number [Admin]

[0825] set EGC only (out of service) flag [Admin]

[0826] enable diagnostics DCE feedback [Admin]

[0827] disable diagnostics DCE feedback [Admin]

[0828] enable signalling DCE feedback [Admin]

[0829] disable signalling DCE feedback [Admin]

[0830] enable DCE alarms [Admin]

[0831] disable DCE alarms [Admin]

[0832] enable DTE alarms [Admin]

[0833] disable DTE alarms [Admin]

[0834] set/clear DNID/member number/LES Id list [Admin]

[0835] set/clear ENID number

[0836] set generate data reports on power up/down flag [Admin]

[0837] set data report generation intervals [Admin]

[0838] set burst retry count [Admin]

[0839] set burst uncertain retry count [Admin]

[0840] set power down timer [Admin]

[0841] set message type routing [Admin]

[0842] set transmit packet limit [Admin]

[0843] set MT mode [Admin]

[0844] set roaming parameters [Admin]

[0845] DCE Event Messages

[0846] As required by Section DCE, the software will be able to recognize DCE event messages and will place them into the AMC Health Log. The software will place all DCE event messages into the log.

[0847] As required by Section DCE, the software will be able to recognize the following DCE event message as a distress acknowledgement:

[0848] “Protocol Indication: 1036”

[0849] “Distress Alert Transmitted and Acknowledged”

[0850] This portion lists all automatic data variables and commands that are valid within message proformas. As required by Section Message Proforma, the software will automatically include data in messages that use message proforma containing the following automatic data variables:

[0851] DCE-B-RETRY—currently configured value for DCE burst retry count

[0852] DCE-BBER—DCE's current BBER value

[0853] DCE-BEARING—current bearing the AMC as reported by the DCE

[0854] DCE-BU-RETRY_U—currently configured value for DCE burst uncertain retry count

[0855] DCE-CURR-FREQ—TDM freq. DCE is currently tuned to

[0856] DCE-DCE-ALMS_C—currently configured value for DCE's DCE alarms flag

[0857] DCE-DNID—current list of DNID/member number/LES Id values configured in DCE

[0858] DCE-DR-PWR—currently configured value for DCE data reports upon power up/down flag; valid values are 0-1, representing ‘off’ and ‘on’

[0859] DCE-DR-INTS—currently configured value for DCE data report generation intervals

[0860] DCE-DTE-ALMS_T—currently configured value for DCE's DTE alarms flag

[0861] DCE-EGCO-FLAG—currently configured value for DCE EGC only (out of service) flag; valid values are 0-1, representing ‘out of service’ and ‘in service’

[0862] DCE-ENID—current list of ENIDs configured in DCE

[0863] DCE-FRAME #—current DCE frame number

[0864] DCE-ID—DCE's serial #, Inmarsat #, model #, firmware revision #,

[0865] DCE-INF—DCE's current INF data

[0866] DCE-LES-STATUS—current LED status reported by DCE

[0867] DCE-LOGIN-MODE—currently configured DCE login mode; valid values are ‘A’ and ‘M’, representing automatic and manual

[0868] DCE-MOB #—currently configured DCE mobile number

[0869] DCE-MSG-ROUT—currently configured values for DCE's message type routing parameters

[0870] DCE-MT-MODE—currently configured value for DCE MT mode parameter

[0871] DCE-POS—DCE's current lat/lon position

[0872] DCE-POS-TIME—UTC 24 hour time of the DCE's current position

[0873] DCE-PWR-TIMER—currently configured value for DCE's power down timer

[0874] DCE-ROAM—currently configured value for DCE roaming parameters

[0875] DCE-SPEED—current speed of the AMC as reported by the DCE

[0876] DCE-TIME-C—DCE's current UTC 24 hours date/time

[0877] DCE-TRN-PKT-LIM—currently configured value of DCE transmit packet limit

[0878] DIR-DTE-BOOT—current directory listing of the DTE's Boot-ROM disk

[0879] DIR-DTE-FLASH—current directory listing of the DTE's Flash-ROM disk

[0880] DIR-DTE-RAM—current directory listing of the DTE's RAM disk

[0881] DIR-ADDR-SIZE-A—current size of each of the DTE's two address lists

[0882] DIR-MLOG-NUM—current number of messages in each of the DTE's incoming, outgoing, saved and network message logs

[0883] DTE-MLOG-SIZE-L—current size of each of the DTE's incoming, outgoing, saved and network message logs in bytes

[0884] DIR-PCT-DISK—a percentage of DTE's RAM disk that is currently used

[0885] DIR-PCT-MEM—percentage of DTE's conventional memory that is currently used

[0886] DIR-TIME-T—DTE's current 24 hour UTC day/time

[0887] FEED-DCE-DIAG—currently configured value for DCE diagnostics feedback flag; valid values are 0-1, representing ‘off’ and ‘on’

[0888] FEED-DCE-SIG—currently configured value for DCE signalling feedback flag; valid values are 0-1, representing ‘off’ and ‘on’

[0889] VERS-AMC-SW—version number (major and minor numbers) of the AMC application software being used to transmit the message that uses this proforma

[0890] VERS-PERFORMA—version number (major and minor numbers) of the proforma that includes this automatic data variable

[0891] As required by Section Message Proforma, the software will support the following commands within message proformas. The software will use the indicated command data when executing these commands:

[0892] ADD-ADDR-A

[0893] Action:—add the given address alias and physical address to the DTE's RAM address list; if the alias already exists in the address list, replace it; if the AMC is configured for single primary destination mode, only the address alias to the RAM address list

[0894] Data:—alias, physical address

[0895] DEL-ADDR-D

[0896] Action:—delete the address object identified by the given address alias from the DTE's RAM address list

[0897] Data:—alias

[0898] DISABLE-AMC-MSG-D

[0899] Action:—disable the AMC's ability to send messages over the network

[0900] Data:—none

[0901] DISABLE-HLTH-RPT-D

[0902] Action:—disable the AMC's feature that sends periodic data reports

[0903] Data:—none

[0904] ENABLE-AMC-MSG-E

[0905] Actions:—enable the AMC's ability to send messages over the network

[0906] Data:—none

[0907] ENABLE-HLTH-RPT-E

[0908] Action:—enable the AMC's feature that sends periodic health reports reporting the DCE's current health

[0909] Data:—the number of seconds between health reports

[0910] INIT-PVT

[0911] Action:—initiate a DCE PVT test and return the results using the ‘PVT Results’ fixed-format message

[0912] Data:—none

[0913] SEND-FILE

[0914] Action:—send the file whose name is specified in the ‘Data’ field using the ‘File’ fixed format message (note that this can be used for the DTE's RAM and Flash-ROM address lists, the DTE's health log, the DTE's configuration files, etc.)

[0915] Data:—the name of the file to be transmitted; this will be a valid DOS filename with drive, path and file

[0916] SEND-ALL-PROFORMA-VERS

[0917] Action:—send a list of all identifiers and version numbers for all message and field list proforma installed on the AMC using the ‘Proforma List’ fixed-format message

[0918] Data:—none

[0919] SEND-PROFORMA

[0920] Action:—send the file that contains the specified message or field list proforma's definition using the ‘File’ fixed-format message

[0921] Data:—the identifier for the proforma to be sent

[0922] AMC Adaptive Mobile Communicator

[0923] all of the hardware and software installed in each mobile unit as part of the MMS service; includes DTE and DCE

[0924] CGA Color Graphics Adapter

[0925] the type of graphics adapter and monitor included within the OMNIDATA DTE; it is implemented as a full screen LCD with 80 characters×25 lines in text mode and 640×200 pixels in graphics mode

[0926] DCE Data Communications Equipment

[0927] the transceiver and GPS receiver installed in each mobile unit

[0928] DML Data Message Log

[0929] the log into which all data messages are placed upon receipt at the AMC or transmission form the AMC

[0930] DNID Data Network Identifier

[0931] the ‘Mailbox’ within the Land Station to which AMC messages can be directed

[0932] DTE Data Terminal Equipment

[0933] the keyboard/screen operated by the AMC user of the MMS

[0934] EMS Enterprise Messaging Services

[0935] the middleware product integrated with the AMC application software that provides all lower-level network transport services

[0936] ENID Enhanced Group Call (EGC) Network Identifier

[0937] an identifier to which messages can be broadcast from the LES; all DCEs that have previously been configured with this ENID will receive the message

[0938] GPS Global Positioning System

[0939] the satellite system used by the DCE to determine the location of the DCE

[0940] IML Incoming Message Log

[0941] the log into which all user messages are placed upon the arrival at the AMC

[0942] LCD Liquid Crystal Display

[0943] the type of monitor included on the OMNIDATA; used for all displays of text and graphics information to the AMC user

[0944] LED Light Emitting Diode

[0945] the visual indicators on the OMNIDATA used to provide state information to the user

[0946] LES Land Earth Station

[0947] the ground station that dispatches messages between the satellite network and terrestrial networks according to the above-described enhanced satellite communications protocol.

[0948] MDF Menu Definition File

[0949] the DTE configuration file that specifies the organization of the functions within the DTE's menus

[0950] MMS Mobile Messaging Service

[0951] the service that is supported by the AMC

[0952] MRN Message Reference Number

[0953] the unique number returned to the AMC by the Land Earth Station (LES) when the LES receives a message packet transmitted from the AMC using normal messaging services (note that there may be list of MRNs/PDNs/NDNs returned to the AMC for each message since the middleware software segments messages and transmits them as multiple satellite messages)

[0954] MSAT Mobile Satellite

[0955] the satellite that supports the MMS.

[0956] NDN Negative Delivery Notification

[0957] a message acknowledgement indicating that the LES was not able to deliver a message to its destination, preferably transmitted according to the enhanced satellite communications protocol.

[0958] NML Network Message Log

[0959] the log into which all network messages are placed upon the receipt at the AMC or transmission for the AMC

[0960] OML Outgoing Message Log

[0961] the log into which all user messages are placed upon transmission from the AMC

[0962] PCMCIA Personal Computer Memory Card International Association

[0963] a standard that specifies the type of one of the peripherals connected to the DTE

[0964] PDN Positive Delivery Notification

[0965] a message acknowledgment in the enhanced satellite communications protocol indicating that the LES was able to send a message to its destination

[0966] PVT Performance Verification Test

[0967] a test executed within the DCE to determine whether or not it is functioning properly

[0968] RAM Random Access Memory

[0969] memory that can read and updated by the software

[0970] ROM Read Only Memory

[0971] memory that can only be read by the software

[0972] SAC Special Access Code

[0973] an address type within the LES to which AMC messages can be addressed

[0974] SML Saved Memory Log

[0975] the log into which users can place incoming messages that they want to save; these messages will only be deleted from the AMC at the request of the user

[0976] SRAM Static RAM

[0977] a type of ‘card’ that can be inserted into the DTE's PC-MCIA slot and used as a read-write disk

[0978] UTC Universal Time Coordinate

[0979] the Universal Coordinated Time system used for maintaining all times internal to the AMC and for sending all messages to and from the AMC

[0980] X.121

[0981] the protocol for addresses used within an X.25 packet network; messages sent from the AMC can be directed to one of these addresses

[0982] Data Message

[0983] Data messages are those messages that are exchanged between the AMC software and a workstation at the dispatcher's site. These messages are not initiated by AMC users and do not require the AMC user's involvement. Conceptually, they are somewhat similar to network messages, but they are used for exchanging ‘customer data’ between the AMC and the dispatcher's site. They are used by the dispatcher to download the DTE configuration data that AMSC allows the dispatcher to change (e.g., proformas, address books, DTE parameters) and they are used by the AMC to automatically send customer data to the dispatcher site (e.g., engine monitoring data, bar code reader data). Their format may be either fixed or based on a proforma definition file. If based on a proforma file, the file may contain commands or automatic data variables, but not both and not display variables; replies, if required, must be automatic (not manual) and the reply proforma must also be a data proforma. The AMC software (not the user) may initiate these messages as the result of some triggering event (e.g., engine monitor reports engine data, data is received from bar code reader.)

[0984] Fixed-Format Message

[0985] a message whose format and contents are predetermined and are built into the software; all messages are either fixed-format messages or proforma messages.

[0986] Local Message

[0987] a message that is communicated between the DTE and the DCE to configure the DCE, command the DCE to perform an action, query the DCE for information, return the results of a DCE command to the DTE or report DCE event to the DTE; these messages are not transmitted over the network.

[0988] Middleware

[0989] the software integrated with the AMC application software that provides all lower-level network transport services

[0990] Network Message

[0991] messages that are exchanged between the AMC software and a network management station, located for example at a dispatcher site. These messages are used to control and report the state of the mobile network service (i.e., the DTE and the DCE). They are not initiated by AMC users and do not require the AMC user's involvement. Conceptually, they are used for troubleshooting the DTE and DCE and for changing those configuration parameters within the DTE and DCE that the satellite communications system want to control, as opposed to allowing the dispatcher to control them. Their format may be either fixed or based on a proforma definition file. If based on a proforma definition file, the file may contain commands or automatic data variables, but not both and not display variables; replies, if required, must be automatic (not manual) and the reply proforma must also be a network proforma. The AMC software (not the user) may initiate these messages as the result of some triggering event (e.g., periodic health report timer expires, incoming network message contains a command that requires an outgoing network message to be sent).

[0992] Proforma Message

[0993] a message whose format and contents are determined by a message proforma; the exact format and content of these messages are not built into the software; all messages are either fixed-format messages or proforma messages

[0994] User Message

[0995] messages that an MMS mobile user and an MMS terrestrial user exchange with one another. They may include data automatically included in the message by the software (automatic data variables), but they are only sent at the request of a user. They may not command the AMC unit to perform some action (i.e., they may not include commands in their proforma definition files). Their format is always based on a proforma definition file.

[0996] While this invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not limited to the disclosed embodiment, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.