1、 II 48b259L 0657268 Bob H INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU X.634 Addendum 1 (09/98) SERIES X: DATA NETWORKS AND OPEN SYSTEM COM M U N I CATI ON S OS1 networking and system aspects - Efficiency Information technology - Open Systems Interconne
2、ction - Transport Fast Byte Protocol Addendum I : SDL specifications ITU-T Recommendation X.634 - Addendum 1 (Previously CCITT Recommendation) ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS UBLIC DATA NETWORKS Services and facilities Interfaces Transmission, signalling a
3、nd switching Network aspects Maintenance Administrative arrangements )PEN SYSTEMS INTERCONNECTION Model and notation Service definitions Connection-mode protocol specifications Connectionless-mode protocol specifications PICS proformas Protocol Identification Security Protocols Layer Managed Objects
4、 Conformance testing NTERWORKING BETWEEN NETWORKS General Satellite data transmission systems MESSAGE HANDLING SYSTEMS DIRECTORY OS1 NETWORKING AND SYSTEM ASPECTS Networking X.l-X.19 X.20-X.49 X.50-X. 89 X.90-X.149 X.150-X.179 X.180-X. 199 X.200-X.209 X.210-X.219 X.220-X.229 X.230-X.239 X.240-X.259
5、X.260-X.269 X.270-X.279 X.280-X.289 X.290-X.299 X.300-X.349 X.350-X.399 X.400-X.499 X.500-X.599 X.600-X.629 Y Quality of service Naming, Addressing and Registration Abstract Syntax Notation One (ASN.l) OS1 MANAGEMENT Systems Management framework and architecture Management Communication Service and
6、Protocol Structure of Management Information Management functions and ODMA functions SECURITY OS1 APPLICATIONS Commitment, Concurrency and Recovery Transaction processing Remote operations OPEN DISTRIBUTED PROCESSING X.640-X.649 X.650-X.679 X.680-X.699 X.700-X.709 X.710-X.719 X.720-X.729 x.730-x.799
7、 X.800-X.849 X.850-X.859 X.860-X. 879 X.880-X.899 X.900-X.999 ForJurther details, please refer to ITU-T List of Recommendations. - - . 4862591 Ob57270 464 ITU-T RECOMMENDATION X.634 INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - TRANSPORT FAST BYTE PROTOCOL ADDENDUM 1 SDL specifications Sum
8、mary This Addendum to Recommendation X.634 contains an SDL specification of the Transport Fast Byte Protocol description. The Transport Fast Byte Protocol eliminates the roundtrip delay associated with the establishment and release of a transport connection, and requires very low PCI overhead. The T
9、ransport Fast Byte Protocol is intended for use in situations in which enhancements to the network QoS are not required, and efficiency of operation (e.g. reduction of roundtrip delays on establishment and release) is of primary concern. Source Addendum to ITU-T Recommendation X.634, was prepared by
10、 ITU-T Study Group 7 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 25th of September 1998. Recommendation X.634/Add.l (09/98) 1 II 4862591 Ob57271 3T0 b FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telec
11、ommuni- cations. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The Wor
12、ld Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid
13、 down in WTSC Resolution No. 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation the term recognized operating agency (ROA) includes any individual, company, corporati
14、on or governmental organization that operates a public correspondence service. The terms Administration, ROA and public correspondence are defined in the Constitution of the ITU (Geneva, 1992). INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementatio
15、n of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As
16、 of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly u
17、rged to consult the TSB patent database. O ITU 1999 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. 11 Recommendation X.634/Add.l (0
18、9/98) I 4862591 Ob57272 237 m CONTENTS Page C.l C.3 The system and block structure of the Transport Fast Byte Protocol entity C.2 Interaction with Management and Control Planes 1 Procedure of the Transport Fast Byte Protocol entity . 1 1 . Recommendation X.634/Add.l (09/98) 111 1111 YB62591 Ob57273
19、173 m Recommendation X.634 INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - TRANSPORT FAST BYTE PROTOCOL ADDENDUM 1 SDL specifications (Geneva, 1998) Annex C SDL specification of the Transport Fast Byte Protocol entity C.l The SDL system diagram of the Transport Fast Byte Protocol entity is s
20、hown in Figure C.l and the SDL block structure in Figure C.2. The system and block structure of the Transport Fast Byte Protocol entity C.2 C.2.1 Management Plane No interactions with the Management Plane are specified. C.2.2 Control Plane No interactions with the Control Plane are specified. Intera
21、ction with Management and Control Planes C.3 The SDL diagrams of the procedure of the Transport Fast Byte Protocol entity are given in this subclause. If there exists any difference between the prose description also given in this subclause and the SDL diagrams, the SDL diagrams take precedence. On
22、the other hand, if there exists differences between the specification in this Annex and the one in clause 6K.634, the specification in clause 6K.634 take precedence. NOTE - In the SDL diagrams of this subclause, the octets in all PDUs and SDUs, Le. the TSDU, are numbered from “1“ to at most “65535”.
23、 The operation of the Transport Fast Byte Protocol entity is modeled as a state machine consisting of the following states: Procedure of the Transport Fast Byte Protocol entity Idle: Each Transport Fast Byte Protocol entity is conceptually initiated in the Idle state and returns to this state upon t
24、he release of a connection. Outgoing Connection Pending: A Transport Fast Byte Protocol entity requesting a connection with its peer is in the Outgoing Connection Pending state until it receives acknowledgment from its peer. Incoming Connection Pending: A Transport Fast Byte Protocol entity that has
25、 received a connection request from its peer and is waiting for its users response is in the Incoming Connection Pending state. Data Transfer Ready: Upon successful completion of the connection establishment, both peer Transport Fast Byte Protocol entities will be in Data Transfer Ready state and da
26、ta transfer can take place. No TSDU is currently reassembled. Data Transfer RAS: Some but not all information for a TSDU currently being reassembled has arrived and is being buffered. Data Transfer Abort: The maximum permissible length of a TSDU has been exceeded during reassembly. The Transport Fas
27、t Byte Protocol entity remains in this state until an end of a TSDU is received (EOT-bit). The state transition diagram for the Transport Fast Byte Protocol entity is shown in Figure C.3. Recommendation X.634/Add.l (09/98) 1 System tfb 2 I 1 I I TF B .(TOuiCgnals; T (NOutCignals; N Figure C.lK.634 -
28、 Transport Fast Byte system Recommendation X.634lAdd.l (09/98) BlockTFB ; , lsgai T-CO MIEdhquest. “ , T-CO MIECT.indiralion. -T:OZ)-MIECTjesponse, T-CO WECT confin , T-WTArequesl. T-DATAJndlcation. 1) T-MPEMTEDDATAreqiest, T-MPECITEDDATAindica60n T-CISCONNECT requesi, T-MCCONNECT indication ; siga1
29、 NCON NET. reqiesl, NCONNECT.indication I NCONNECT.response, I NCONNECT.mnfirrn, NDAT A request, NDATAindicaticn KEXPEDlTED-DiTA.request, I KEXPEDlTED-DATA.i ndhtion.j NDISCONNCT.mquest NDISCONNCT.indEation ; j i T-MEMTEDDATAreqest, T-CO MIECT .requed. T-WMIECTresporse. T-DATA requesl, T-MCCONNECT.r
30、equesl ; 1 sl gal Li ThSignais = 8 gal list TOuiSignais = T- CO MI ECT .indi catbn. T- W MI ECT .confi m, T-DATA.indicatbn. T-MPEMTEDDATAindicaon T-CISCONNECT.indication; TFactByk sgiallist NnSigrsls= NCONNECT rquesi, I NCONNECT rejoonse NDATAiequest, NEXPEDlT ED-DATA.reques1, NDISCONNCT.request : s
31、igialit KJutSignais = NCONNECT. indicatim. NCONNECT.mnfirrn. NDAT Aindicahn, NE XP ED lT ED-D ATA .i nd cat ior NDiSCONKCTjndicabn ; N Figure C.2X.634 - Transport Fast Byte block structure Recommendation X.634/Add.l (09/98) tfbbl(1) 3 T-DICCO“ECT.reguest N-DISCONNECT.indication N-DISCONNECT.request
32、T-DISCONNECT.indication I N-DATAmdication T-DATA.indication N-DATAmdication L ms 7E OP F N-DATA.indica1ion N-DATAhdication N-DATA.indication . . N-EXPEDITED-DATA.indication T-EXPEDITED-DATAhdication TO73244-99 T-EXPEDITED-DATA.indication N-EXPEDITED-DATA.indication T-EXPEDITED-DATA.indication N-EXPE
33、DITED-DATAhdication N-EXPEDITED-DATAhdication T-EXPEDITED-DATA.indication 1) 2) 3) 4) N-DATA.indication received and end of the TCDU detected. N-DATAhdication received and no end of the TSDU detected. ConnRcvTPDULength exceeded and end of the TSDU detected. ConnRcvTPDULength exceeded and no end of t
34、he TSDU detected. Figure C.3Bc.634 - State transition diagram for the Transport Fast Byte Protocol entiy The description of the operations of the Transport Fast Byte Protocol entity make use of the following state variables: CdAddr A character string holding the “Called Address“ as extracted out of
35、a TPDU. CgAddr A character string holding the “Calling Address“ as extracted out of a TPDU. RsAddr A character string holding the “Responding Address“ as extracted out of a TPDU. TPDU An octet string holding the TPDU being constructed in the outgoing direction or the TPDU just having been received.
36、TSDU An octet string holding the TSDU being reassembled in the incoming direction. ptrRAS An index into the variable TSDU indicating where to place the next information during reas- sembly. ptrSEG An index into the parameter TSUserData indicating where to extract data during segmentation. ptrPDU An
37、index into the variable TPDU having been received indicating where to retrieve the next information during interpretation of the received TPDU. lenPDU The length of a TPDU having been received. IenSDU The (remaining) length of a TSDU being segmented. len Temporary variable holding the length of a ch
38、aracter string. EOTbit A boolean variable being set to TRUE if the EOT-bit in the received TPDU has been set. SndTPDULength A temporary integer variable during connection establishment used for negotiation of the maximum size of a TPDU in the outgoing direction. ConnSndTPDULength An integer variable
39、 indicating the maximum size of a TPDU in the outgoing direction. 4 Recommendation X.634lAdd.l (09/98) 111 48b259L Ob57277 819 RcvTPDULength A temporary integer variable during connection establishment used for negotiation of the maximum size of a TPDU in the incoming direction. ConnRcvTPDULength An
40、 integer variable indicating the maximum size of a TPDU in the incoming direction. tmpNullPCI A temporary boolean variable during connection establishment used for negotiation of the NullPCI capability. ConnSndNullPCI A boolean variable indicating the NullPCI capability in the outgoing direction. Co
41、nnRcvNullPCI A boolean variable indicating the NullPCI capability in the incoming direction. Terminate A boolean variable being set to TRUE after leaving state “Idle“ if the process should stop after return to “Idle“. The Transport Fast Byte Protocol entity maintains the following parameters: NmaxRc
42、vLmgth NmaxSndLength TmaxRcvLength TmaxSndLength CPlaneNegotiation NullPCI Termination The maximum size of the NSUserData parameter in the incoming direction. The maximum size of the TSUserData parameter in the outgoing direction. The maximum size of the TSUserData parameter in the incoming directio
43、n. The maximum size of the TSUserData parameter in the outgoing direction. A boolean value being set to TRUE if the parameter negotiation takes place outside the Transport Fast Byte Protocol entity, e.g. in the C-plane. A boolean value being set to TRUE if NullPCI procedures are enabled. A boolean v
44、alue being set to TRUE if if the Transport Fast Byte Protocol entity should stop after return to the state “Idle“. The SDL definition of the Transport Fast Byte Protocol entity process is shown in Figure C.4. C.3.1 1) Procedures in the state “Idle“ Upon receipt of a T-CONNECT.request, a TPDU is cons
45、tructed that is then transferred in the NS-User-Data of the N-CO“ECT.request; the process enters state “Outgoing Connection Pending“. If negotiation takes place outside the Transport Fast Byte Protocol entity, no TPDU is transmitted. Otherwise, the TPDU constructed follows the specification in claus
46、e 7K.634. The NullPCI capability is enabled as indicated in the parameter “NullPCI“, the TPDU lengths are taken from the parameter “TmaxSndLength“ and “TmaxRcvLength“, and the called and calling addresses were received as parameters of the T-CONNECT.request. If TS-User-Data was also received with th
47、e primitive, this is also copied into the TPDU. NOTE 1 - The variable “Terminate“ is set to TRUE after leaving state “Idle“ if the parameter “Termination“ has been set to TRUE also. 2) If the TPDU constructed above exceeds the maximum permissible length of the NS-User-Data, a T-DISCONNECThdication i
48、s returned to the Transport Fast Byte Protocol entity user; the process remains in state “Idle“. Upon receipt of an N-CONNECThdication, the TPDU received in the NS-User-Data is verified and the data extracted (if negotiation takes place outside the Transport Fast Byte Protocol entity, no TPDU is ver
49、ified and no data is extracted). The data items are then sent in the parameters of the T-CONNECThdication to the Transport Fast Byte Protocol entity user; the process enters state “Incoming Connection Pending“. The verification and extraction is specified in macro “Verify ICP TPDU“ and is as follows: a) b) c) 3) If no TPDU has been received or the first octet does not contain the value “101000102 or the extension bit in octet 2 is set, the connection establishment is rejected with an N-DISC0NNECT.request. If octet 3 contains the value “000000012“, the next 4 octets contai
