intelligent that it can read documents with a text header and address list, to transmit and store them in IR, while notifying the addressees through MP that the T- cument is stored in IR. Later the addressees ma-y access IR and retrieve the-file on their own facsimile device TXX2. At the recipients’ option
( or possibly the sender’s To mimic “recorded delivery”) each addressee may automatically inform the originator that the document was received. In addition, we wish to store the facsimile data in a canonical form, so that it may be retrieved from different facsimile devices. There is an important difference between the storage of facsimile and short text messages. Such textual information is usually small (less then 500 bytes), whereas the facsimile data is much larger typically 25 K bytes for an A4 size page with optimum data compression. Hence the textual data can be stored in multiple copies, one for each addressee in his “mailbox”. The facsimile information is stored only once in IR, and the path name to retrieve it is known by the addressees from their text messages. In our implementation of this system we have used ARPANET as the data network. For FAXi, we attached a Micro-Processor to an analogue 4-6 minute facsimile device ksection 3). This was then connected via an asynchronous link to the UCL TIP. However, for reasons of speed and flow-control, this llni was switched over to one of the UCL PDP-9 as described in Section For the MP of Fig. 1, we use one of the Tenex systems on ARPANET,supporting the message systom MSG TRef 2]. For IR the Data-Computer at CCA [Ref. 3) with =- on-line storage capac-ity -of 10**12 T”5Tts, is a natural candidate, and has been used exclusively. As for FAX2 we are using the XGP printer (Ref. 4] at ISI, whichis controlled by a PDT-! Tenex configuration as Tecribed in Section 5. o:i-. i_ 1 1 i II 1 I + I ‘ 1 i i i ‘1
72 1.3 FA X1 TIP Fig.1 Overview of on Idealised FocSIMile System FAXOO p.x C 3RPNE Fig.? UCL Facsimile Terminal
73 ,-., ” UCL Facsimile Terminal and its Use 3.1 Introduction A system such as the one outlined in Section 2 can be described at many different levels. In this section we will describe the UCL facsimile terminal itself [Section 3.2) and give examples of its use in message transmission. The examples given contain two user dialogues, one for message transmission [Section and the other for message retrieval [Section 3.4.2). The message transmission dialogue is mainly concerned with the composition of a message file [containing textual and facsimile information), its local verification, its submission to the MSG system and the Data-Computer, and confirmation of deliv-e-r. This dialogue also illustrates the binding of linkages between the two portions of the message and the supervision of message transmission which are almost transparent to the user.
ups lost tracking number is not find is that amazing
The retrieval of a message can have either one or two stages. Because the notification comes via the text message system MSG, the user may receive notification of facsimile message-s–uring straightforward text retrieval from a conventional terminal. In this case the retrieval of the facsimile portion must be a separate exercise. Alternatively, as illustrated in the retrieval dialogue, the user may access the MSG system via the facsimile terminal. In this, somewhat–impler case, the notification and retrieval become an integrated operation. 3.2 The UCL Facsimile Terminal Fig. 2 shows the basic components of the facsimile terminal we have developed. Physically it consists of : [(1 FAXD : The facsimile device which is a Plessey 4-6 minute analogue tranceiver [ KD-111 incorporated with a two level Analogue-to-dgi-tal converter.jita [2) up An Intel 8080 mico-processor with 24K [8-bTFword] Random ccess Memory, and peripheral interfaces. [3) FDD. A Fjlopy-Disc driver. [4) KBT: A Keyboard Terminal. [5) ACI An asynchronous communications _ interface.