WPC  2%.Bpz W"S^11>bbu"::Dg1:11bbbbbbbbbb11gggbuuuk1Xubuukuuuk111Rb:bbXbb1bb''X'bbbb:X1bXXXX;.;g:=::m:::mmmmm::::::mm:k1mubububububXubububub11111111bbbbbbbbbuXubbkbuXmmmmumububXXXXbububububbmbbbbbb:k:k::=kmmX:uXb'b:b:b:b'bmbbbb:::uXuXuXuXk:k:k:mbbbmbuXkXkXKQmmmm^b:kbbbbmbA@mmbmmbmmmmmmm:b:mmmbbmmmmmmmmmmmmXXmmmmmmmmmmmmmmmmmmcm`m`mm`m:mmmmmm}}}mjjmmmmmmmmmmmmmmm0mm}mmmmmmmmmmmmmmmmmmmmmmm}Mmmmmmmmmmmmmjmmmtmmmmmmmmm`'mmm`mmjmlWmmmmmmmmmmmmmmmmmmmW`mmmmjmM#|xaHelveticaCourierCourier Bold4PkCQMS PS Jet Plus /800 II QPJPII.PRSPl`D4PkCg2W _a.s|x-HelveticaCourierHelveticaCourierCourier BoldHelvetica BoldmQrrr r  @C2M.IzPw@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C"S^1:Sbb1::Dg1:11bbbbbbbbbb::gggkuk1bkuukuuuk:1:gb1bkbkb:kk11b1kkkkDb:kbbbXD1Dg:=::r:::rrrrr::::::rr:k1rbbbbbbubububub11111111kkkkkkkkkubbkkkubrrrrrbbbbbbkububububkrkkkkkk:k:k::=krrb:bk1k:k:k:k1krkkkkDDDububububk:k:k:rkkkrkubkXkXKQrrrrbb:kbbbbrbA@rrbrrbrrrrrrrXb::rrbbrrrrrrrrrrrrkkrrrrrrrrrrrrrrrrrrcr`r`rr`r:rrrrrr}}}rjjrrrrrrrrrrrrrrr0rr}rrrrrrrrrrrrrrrrrrrrrrr}Mrrrrrrrrrrrrjrrrtrrrrrrrrr`'rrr`rrjrlWrrrrrrrrrrrrrrrrrrrW`rrrrjrM@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C@,dK1dD4p}wC2. ' x "S^"55U@ %8 55555555558885a@@EE@;KE0@5PEK@KE@;E@[@@;-5 55055550P5555 050E000  8 " m mmmmm mm ;m@5@5@5@5@5`UE0@5@5@5@5E5K5K5K5K5E5E5E5E5@0@5E5K;K5@0mmmmmm@5@5E0E0E0E0E5@5@5@5@5K5mmK5K5K5K5E5E5 ; ; ";mm0 @055 5 5 5E5mmE5E5K5K5`[E E E @0@0@0@0; ; ; mmE5E5E5mmE5[E@0;0;0K,mmmm45 ;5555m5$#mm5mmLL5mmmmmmm 5` mmm55Ummmmmmmmmmmm00`mmmmmmmmmmmmmmmmmm`cm5m5mm5m mmmmmJmDDDm::mdmmmmmmmmmmmmmmmmDmmmmmmmmmmmm__mmdmmmmmmmmmD*Ommmmmmmmmmmm:mmm?mmmmmmmmm5'mmm5mm:m;/mmmmmmmmmmmmmmmmmmm/H5Jmmmm:m*@ ,`H1`D4PkCmQrrr r  @CmQrrrr  `C@,dK1dD4p}wC@H4': 4D4PkC  X` hp x (#%'HP ,x--h.    3'3'Standard6'6'StandardC6QMS $=R- :(  x|@  Fascicle VII.7 Rec. T.523 i:- x|@   Fascicle VII.7 Rec. T.523 i   Recommendation T.523  COMMUNICATION APPLICATION PROFILE DM1 ă  FOR VIDEOTEX INTERWORKING ă &CONTENTS 1HScope 2HField of application 3HReferences 4HDefinitions 5HOverview of communication profile DM1 6HBasic communication requirements for DM1 7HCommunication procedure for DM1 8HElements of procedure 9HAction of the EH and the LH 10HObject identifier AnnexAbstract syntax definition of videotex specific information 1 H Scope  1.1HThe T.400 Series of Recommendations generally defines open document architecture (ODA), document architecture operations and DTAM service/protocol for document architecture transfer and manipulation under the telematic communication environment.  1.2HThis Recommendation defines a communication application profile DM1 for document unconfirmed manipulation to specify an interactive communication profile based on DTAM between videotex gateway systems.  1.3HThe use of Recommendations X.215/X.225, X.216/X.226, X.217/X.227 for this communication profile is described in this Recommendation. 2 H Field of application  2.1HThe communication application profile DM1 enables document manipulation for documents which are represented in accordance with the document application profile defined by Recommendation T.504, and the operational application profile defined by Recommendation T.541. 2.2HThe ODA documents that are manipulated should be in formatted form.  2.3HThe field of application of this Recommendation is the international videotex interworking service between videotex gateways, representing the external host (EH) and the local host (LH).  2.4HVideotex communication procedure is based on the model defined in this Recommendation in accordance with the Recommendation T.564 which defines gateway characteristics for videotex inter working. @) 3 H References H Rec.T.101:International interworking for videotex services H Rec.T.430Series:Document transfer and manipulation (DTAM) H Rec.T.504:Document application profile for videotex interworking H Rec.T.541:Operational application profile for videotex interworking H Rec.T.564:Gateway characteristics for videotex interworking  H Rec.X.215:Session service definition for open systems interconnection for CCITT applications'  H Rec.X.225:Session protocol specification for open systems interconnection for CCITT applications'  H Rec.X.216:Presentation service definition for open systems interconnection for CCITT applications'  H Rec.X.226:Presentation protocol specification for open systems interconnection for CCITT applications'  H Rec.X.217:Association control service definition for open systems interconnection for CCITT applications'  H Rec.X.227:Association control protocol specification for open systems interconnection for CCITT applications' H Rec.X.208:Specification of abstract syntax notation one (ASN.1)'  H Rec.X.209:Specification of basic encoding rules for abstract syntax notation one (ASN.1)' 4 H Definitions HTerms and their definitions are defined by the Recommendations listed above. 5 H Overview of communication profile DM1  5.1HCommunication profile DM1 defines the communication functionalities which provide a real time remote document manipulation on ODA and operational structure documents by create, delete, modify and call operations between videotex gateways under OSI ACSE and presentation communication support functions (normal mode defined in Recommendation T.432). These operations are the unconfirmed type of manipulation.  5.2HThis profile defines the communication model which consists of the local host DTAM user and the external host DTAM user as illustrated in Figure 1/T.523. Either the LH or the EH is capable of managing the initiation and termination of applicationassociation. At the association establishment phase, initial VIA structures are automatically generated in both hosts. p$ #FIGURE 1/T.523 *  A model of communication application profile DM1 ă  for videotex interworking ă  5.3HThe owner of the data token, managed by the DTAM token control function, is able to manipulate ODA and operational structure documents which are directly mapped from VIA operations defined in the Recommendation T.564.  5.4HThe manipulation provides the operations which can be applied to one or more constituents of the ODA document and/or the operational structure. In this profile, these operations do effect addition, deletion or modification of constituent to a document which existed identically between both hosts.  5.5HWhen the data token belongs to the LH DTAM user, only modify operations on operational structure are allowed to be used by the LH DTAM user. On the other hand, the EH DTAM user is able to use all of the operations defined in DTAM when it has the data token. 6 H Basic communication requirements for DM1  HDM1 is defined under the following OSI communication environment. Mapping rules of DTAM APDUs into/out of the ACSE and presentation layer are used as defined in the Recommendation T.433. 6.1HDTAM functionalities  HThe following DTAM functionalities defined in Recommendation T.432 are basic requirements for this communication profile DM1:  Hi)  document unconfirmed manipulation by using create, modify, delete and call operations;' Hii)  association use control;'  HHX HHiii)  token management for dialogue control;' Hiv)  typed data transmission.' 6.2HACSE functionalities  HThe basic functionalities of the association control service element defined by Recommenda tions X.217 and X.227 are used. 6.3HPresentation functionalities  HThe kernel functional unit is used as defined by Recommendation X.216 and X.226. Recommenda tions X.208 and X.209 are used for the definition of abstract notation and basic encoding rules of abstract notation respectively for DM1. 6.4HSession functionalities  HThe kernel functional unit, two ways alternate functional unit and typed data functional unit are used in accordance with Recommendations X.215 and X.225. 7 H Communication procedure for DM1 7.1HGeneral communication procedure  HThe general communication procedure for videotex gateway application is defined in line with the basic procedure in Recommendation T.432. The procedure consists of: H applicationassociation establishment; H applicationassociation termination; H applicationassociation abort; H data transmission. 7.2HApplicationassociation establishment  HA communication normally begins with the establishment of applicationassociation from the LH or EH DTAM user to initialize the communication environment and to set the initial parameters and the VIA structures being used. The initial data token is assigned to the EH DTAM user. After the establishment of applicationassociation, both DTAM users move to the data transmission phase. 7.3HApplicationassociation terminate and abort  HThe DTAM applicationassociation may be normally terminated by either the LH or the EH DTAM user subject to the owning of the data token. The DTAM applicationassociation may also be abruptly terminated by either the LH or the EH DTAM user or provider using the appropriate DTAM abort services. 7.4HData transmission 7.4.1HGeneral  HVideotex gateway application provides the following communication functions in the data transmission phase: H1)  manipulation of display information; H2)  manipulation of data entry information; H3)  manipulation of application control memory information; H4)  manipulation of special terminal facilities information; H5)  manipulation of administrative information; H6)  exchange of over limit information (for further study); H7)  transmission of asynchronous message. ) 7.4.2HManipulation of display information  HDisplay is performed by VIA operations, defined in Recommendation T.564, initiated by the external host on the display structure.  HTo perform VIA operations on the display structure the EH uses DCREATE, DMODIFY, DDELETE or DCALL service primitives under data token control. 7.4.3HManipulation of data entry information 7.4.3.1HGeneral HThe Recommendation T.564 defines the following four types of data entry: H1)  data entry type 1information retrieval; H2)  data entry type 2data collection; H3)  data entry type 3data entry on the fly; H4)  data entry type 4duplex data entry.  HThese data entry types are categorized into half duplex mode (data entry type 1, 2 and 3) and duplex mode (data entry type 4).  HThe EH may use DCREATE, DMODIFY, DDELETE, DCALL to perform VIA operations on each structure element of the data entry structure, except modifying the RESULTSE and its associated content portion.  HHalf duplex mode of data entry provides the dialogues between the LH and the EH under the data token control. Data entry is performed from the LH by VIA operations via DTAM manipulation (DMODIFY) on the data entry structure. In this case the EH should give the data token to the LH to perform data entry.  HDuplex mode of data entry is not dependent upon the token control. Data entry is performed from the LH by the use of typed data and the data token is always located at the EH side. 7.4.3.2HManagement of data entry mode HThe management of the data entry modes is bound to the following rule:  Hi)  the LH issues the parameter of "data entry mode" to indicate the data entry capabilities at the LH side in the DTAM association establishment phase. This parameter is a choice of (a) half duplex mode, (b) duplex mode and (c) half duplex and duplex modes;'  H ii)the EH recognizes the capabilities of data entry mode which is capable to be managed by the LH. It is not necessary to inform the LH of the EH capabilities of the data entry mode;'  HHX X  HH iii)if the LH indicates the only half duplex mode and selects the application based on the duplex mode, the EH may refuse to connect with the selected application from the LH;'  H iv)if the LH indicates the only duplex mode and selects the application based on the half duplex mode, the EH may refuse to connect with the selected application from the LH;'  H v)if the LH indicates both modes, all the applications based on the half duplex or duplex modes are available to the LH.' 7.4.3.3HOperation of data entry in half duplex mode (type 1, 2, 3)  HIn data entry type 1 or 3, the entered data are sent from the LH to the EH using DMODIFY for the RESULTSE and the content portion associated to the RESULTSE. In data entry type 2, the entered data are sent from the LH to the EH using DMODIFY for the RESULTSE and the content portions associated with the entered fields and the RESULTSE (if necessary). HThe EH gives the token to the LH to enable the LH to send the entered data.  HThe LH gives the token to the EH after having completed the data entry (i.e. after having initiated the appropriate DMODIFY corresponding to the SEs concerned with data entry). Examples are given in Figure 2/T.523 and Figure 3/T.523. & #FIGURE 2/T.523 *  Example of data entry in type 1 or 3 ă * (Information retrieval or on the fly: half duplex)   #FIGURE 3/T.523 *  Example of data entry in type 2 ă (Data collection: half duplex) 7.4.3.4HOperation of data entry in duplex mode (type 4)  HWhen the data entry type attribute of the DATAENTRYPROGRAMSE is set the data entry type 4, the LH sends the entered data and the termination reason in DTYPEDDATA with the termination reason associated. The data token remains assigned to the EH. An example is given in Figure 4/T.523.  HWhen the EH resets the data entry type attribute to another type (1, 2 or 3) under the condition that both modes are available at the LH, the LH stops sending data in DTYPEDDATA and uses again DMODIFY to send the entered data. The EH ignores the possible colliding DTYPEDDATA.  #FIGURE 4/T.523 *  Example of data entry in type 4 ă &(Duplex) 7.4.3.5HSwitching of entry type  HThe entry type is modified by the EH when sending a DMODIFY, DCREATE, DDELETE or DREBUILD for the DATAENTRYPROGRAMSE.  HAfter sending such a DMODIFY, the EH may send further VIA operations via DTAM manipulation, if required, and should send the token, even when switching to data entry type 4, in order to indicate to the LH the end of entry type redefinition and to permit echoing of characters (if any).  HWhen receiving a primitive which redefines the dataentry type, the LH should stop sending information and consider all information from the videotex user as typed ahead information. The sending of information is resumed when receiving the data token. If the new defined data entry type is 1, 2 or 3, the token remains assigned to the LH until the entry is entirely performed. If the new defined data entry type is 4, the token is immediately sent back to the EH.  HThe echoing of characters is started after the reception of the data token depending on the value of the echo attribute. The echoing is stopped in modes 1, 2, 3 when sending back the data token after completion of the data entry. The echoing is only stopped in mode 4 after redefinition of a new data entry mode (or modification of the echo attribute). HExamples are given in Figures 5/T.523 and 6/T.523.  * * #FIGURE 5/T.523  Example of mode switch ă    #FIGURE 6/T.523  Example of mode switch ă