1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMM UN CATION STANDARDIZATION SECTOR OF ITU X.633 Addendum I (09/98) SERIES X: DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS OS1 networking and system aspects - Efficiency Information technology - Open Systems Interconnection - Network Fast Byte Protoc
2、ol Addendum I : SDL specifications ITU-T Recommendation X.633 - Addendum 1 (Previously CCIlT Recommendation) ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATIONS UBLIC DATA NETWORKS Services and facilities Interfaces Transmission, signalling and switching Network aspects Maint
3、enance Administrative arrangements 3PEN SYSTEMS INTERCONNECTION Model and notation Service definitions Connection-mode protocol specifications Connectionless-mode protocol specifications PICS proformas Protocol Identification Security Protocols Layer Managed Objects Conformance testing INTERWORKING
4、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 X.260-X.269 X.270-X.279 X.280-X.
5、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 Quality of service Naming, Addressing and Registration Abstract Syntax Notation One (ASN.l) OS1 MANAGEMENT Systems Management framework and architecture Management Communication Service and Protocol Structure of Management I
6、nformation 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.7 10-X.719 X.720-X.729 X.730-X.799 X.800-X.849 X.850-X.859 X.860-
7、X. 879 X.880-X.899 X.900-X.999 For further details, please refer to ITU-T List of Recommendations. I 4Bb2591 Ob57219 LL7 ITU-T RECOMMENDATION X.633 INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - NETWORK FAST BYTE PROTOCOL ADDENDUM 1 SDL specifications Summary This Addendum to Recommendation
8、 X.633 contains an SDL specification of the Network Fast Byte Protocol description. The Network Fast Byte Protocol applies to the provision of the OS1 Connection-mode Network Service in end systems, and eliminates the roundtrip delay associated with the establishment and release of a network connect
9、ion, and requires very low PCI overhead. The Network Fast Byte Protocol is intended for use in situations in which enhancements to the data link QoS are not required, and efficiency of operation (e.g. reduction of roundtrip delays on establishment and release) is of primary concern. Source Addendum
10、1 to ITU-T Recommendation X.633, was prepared by IT-T Study Group 7 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 25th of September 1998. Recommendation X.633IAdd.l (09/98) 1 D 4862593 Ob57220 939 FOREWORD ITU (International Telecommunication Union) is the United Nati
11、ons Specialized Agency in the field of telecommuni- 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 tele
12、communications on a worldwide basis. The World 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 o
13、f the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. In some areas of information technology which fall within ITU-T?s purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation the term recognized operating agency (ROA
14、) includes any individual, company, corporation 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 p
15、ossibility that the practice or implementation 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
16、of the Recommendation development process. As 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 la
17、test information and are therefore strongly urged 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 f
18、rom the ITU. 11 Recommendation X.633/Add.l (09/98) . I 4862593 Ob57223 875 U TABLE OF CONTENTS Annex C . SDL specification of the Network Fast Byte Protocol entity The system and block structure of the Network Fast Byte Protocol entity . Procedure of the Network Fast Byte Protocol entity . Annex D .
19、 SDL specification of Annex B of the Network Fast Byte Protocol . Interaction with Management and Control Planes Procedure of the Synchronization and Coordination entity C.l C.2 C.3 Interaction with Management and Control Planes D.l D.2 D.3 The system and block structure . Page 1 1 1 1 25 25 28 28 .
20、 Recommendation X.633/Add.l (09/98) 111 Addendum 1 to Recommendation X.633 INFORMATION TECHNOLOGY - OPEN SYSTEMS INTERCONNECTION - NETWORK FAST BYTE PROTOCOL ADDENDUM 1 SDL specifications (Geneva, 1998) Annex C SDL specification of the Network Fast Byte Protocol entity C.l The SDL system diagram of
21、the Network Fast Byte Protocol entity is shown in Figure C.l and the SDL block structure in Figure C.2. The system and block structure of the Network Fast Byte Protocol entity C.2 Interaction with Management and Control Planes C.2.1 Management Plane The data transfer with the Q-bit set is modeled as
22、 a data transfer between the Layer Management entities of the Network Fast Byte Protocol entities. The service primitives are defined as: 0 0 The parameters of these service primitives are identical to the N-DATA.request and N-DATAhdication primitives. No other interactions with the Management Plane
23、 are specified. MN-DATA.request (from Layer Management entity to Network Fast Byte Protocol entity); and MN-DATAhdication (from Network Fast Byte Protocol entity to Layer Management entity). C.2.2 Control Plane Interaction between the Network Fast Byte Protocol entity and the Control Plane (C-plane)
24、 is outside the scope of this annex. C.3 The SDL diagrams of the procedure of the Network 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 the ot
25、her hand, if there exists differences between the specification in this annex and the one in clause 6K.633, the specification in clause 6K.633 takes precedence. NOTE -In the SDL diagrams of this subclause, the octets in all PDUs and SDUs, i.e. the TSDU, are numbered from “1“ to at most “65535“. The
26、operation of the Network Fast Byte Protocol entity is modeled as a state machine consisting of the following states: - Procedure of the Network Fast Byte Protocol entity Idle: Each Network Fast Byte Protocol entity is conceptually initiated in the Idle state and returns to this state upon the releas
27、e of a connection. Outgoing Connection Pending: A Network 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 Network Fast Byte Protocol entity that has received a c
28、onnection request from its peer and is waiting for its users response is in the Incoming Connection Pending state. Outgoing Resynchronization Pending: A Network Fast Byte Protocol entity requesting resynchronization (RESET) of the connection with its peer is in the Outgoing Resynchronization Pending
29、 state. - - - Recommendation X.633/Add.l (09198) 1 I 4862593 Ob57223 648 = - Incoming Resynchronization Pending: A Network Fast Byte Protocol entity that has received a resynchronization request (RESET) from its peer and is waiting for its users response is in the Incoming Resynchronization Pending
30、state. 2 Recommendation X.633/Add.l (09/98) 1 N NFB DL Figure C.lK.633 -Network Fast Byte system Recommendation X.633/Add.l (09/98) 3 E Y862594 Ob57225 440 . 4 signalkt DLhSignak = DL-COFNECTreques, DL-COFNECTresponse, DL-DATA requed. DL-RESET.mquest. DL-RESET.response, DL-DICCONNECT.iequest ; j sig
31、nallist DLOulSgnals = DL-COFNECTjndbatbn, DL-COFNECT.confirm , DL-DATA hdi cat ion. DL- RES ET. indca on, DL-RES ET.cmf irm, DL-DWONNECT.mdkaon 4 Bbck NFB signai N-COFNECtmques N-COFNECkdimtin. _- N-COFNECTLesponse. N-COFNECT. N.DATA request N-DATAiirlimtbn, N-RESET.rquesl. N-RESET.mdcation, N-RESET
32、.reiponse, N-RESET.conrm, N-DsCONNECT.mquest, N-DsCONNECT.ndication; signai MNDATA.iequesl.4 I MNDATAindca6on;j LM JL ignalst NhSignak = N-COWECT.requed N-COWECT.regonie, I N-DATAsequeS, N-RESET. squesl, N-RESCET.ssponse, j N-DWONNECT.mquest ; I ignallist j NOutSgnals = N-COWECT.iidicatwn, I N-COFNE
33、CT.conrm. i N-DATAhdi catbn, N-RESET.hdicstim, N-RESEF.corlirm, N-DICCONNECT.ndbaUon ;I M NDATA. ndcaknl rMN-DATArequesl DL-COW ECT.regonse, NFastByte Itbbl(1) (NOUTSi mal s) N (NhSignak; (DLOuSignals) 1 DL (DLhSLgnalsd Figure C.2B1.633 - Network Fast Byte Block structure Recommendation X.633lAdd.l
34、(09/98) 4Bb259L Ob57226 357 from any from any DL-RESETxonfirm state below state below L N-RESET.response N-RESET.confirm Outgoing Incoming DL-RESET.response nization nizalion Pending Pending A A N-RESET.request DL-RESET.indication DL-RESET.request N-RESET.indica1ion I 4 Resynchro- Resynchro- . - Dat
35、a Transfer Ready: Upon successful completion of the connection establishment, or resynchronization procedures, both peer Network Fast Byte Protocol entities will be in Data Transfer Ready state and data transfer can take place. No NSDU is currently reassembled. Data Transfer RAS: Some but not all in
36、formation for an NSDU currently being reassembled has arrived and is being buffered. Data Transfer Abort: The Q-bit of the different segments of the NSDU are not equal or the maximum permissible length of an NSDU has been exceeded during reassembly. The Network Fast Byte Protocol entity remains in t
37、his state until an end of an NSDU is received (EON-bit). - - The state transition diagram for the Network Fast Byte Protocol entity is shown in Figure C.3. DL-DISCONNECTh DL-DAT Amdication c DL-DATAmdicaiio To73?.4%93 -DATA.indication . . 1) 2) 3) 4) DL-DATAhdication received and end of the NSDU det
38、ecled. DL-DATAmdication received and no end of the NSDU detected ConnRcvNPDULength exceeded or Q-bit change and end of lhe NSDU deeded. ConnRcvNPDULength exceeded or Q-bit change and no end of the NSDU detected. Figure C.3K.633 - State transition diagram for the Network Fast Byte Protocol entity The
39、 description of the operations of the Network Fast Byte Protocol entity make use of the following state variables: CdAddr CgAddr RsAddr A character string holding the “Called Address“ as extracted out of an NPDU. A character string holding the “Calling Address“ as extracted out of an NPDU. A charact
40、er string holding the “Responding Address“ as extracted out of an NPDU. NPDU An octet string holding the NPDU being constructed in the outgoing direction or the NPDU just having been received. Recommendation X.633/Add.l (09/98) 5 NN 4862591 Ob57227 293 I NSDU An octet string holding the NSDU being r
41、eassembled in the incoming direction. ptrRAs An index into the variable NSDU indicating where to place the next information during reas- sembly. ptrSEG An index into the parameter NSUserData indicating where to extract data during segmentation. ptrPDU An index into the variable NPDU having been rece
42、ived indicating where to retrieve the next information during interpretation of the received NPDU. lenPDU The length of an NPDU having been received. lenSDU The (remaining) length of an NSDU being segmented. len EONbit Temporary variable holding the length of a character string. A boolean variable b
43、eing set to TRUE if the EON-bit in the received NPDU has been set. SndNPDULength A temporary integer variable during connection establishment used for negotiation of the maximum size of an NPDU in the outgoing direction. ConnSndNPDULength An integer variable indicating the maximum size of an NPDU in
44、 the outgoing direction. RcvNPDULength A temporary integer variable during connection establishment used for negotiation of the maximum size of an NPDU in the incoming direction. ConnRcvNPDULength An integer variable indicating the maximum size of an NPDU in the incoming direction. I tmpNullPC1 A te
45、mporary boolean variable during connection establishment used for negotiation of the NullPCI capability. ConnSndNullPCI A boolean variable indicating the NullPCI capability in the outgoing direction. ConnRcvNullPCI A boolean variable indicating the NullPCI capability in the incoming direction. currQ
46、bit A boolean variable being set to TRUE if the Q-bit in the received NPDU has been set. Con n Q b i t Terminate A boolean variable being set to TRUE if Layer Management data transfer (the use of the Q-bit) is allowed on this connection. A boolean variable being set to TRUE after leaving state “Idle
47、“ if the process should stop after return to “Idle“. The Network Fast Byte Protocol entity maintains the following parameters: DLmaxLength The maximum size of the DLSUserData parameter. NmaxRcvLength The maximum size of the NSUserData parameter in the incoming direction. NmaxSndLength The maximum si
48、ze of the NSUserData parameter in the outgoing direction. QbitAllowed A boolean value being set to TRUE if Layer Management data transfer (the use of the Q-bit) is enabled. CPlaneNegotiation A boolean value being set to TRUE if the parameter negotiation takes place outside the Network Fast Byte Prot
49、ocol entity, e.g. in the C-plane. NullPCI A boolean value being set to TRUE if NullPCI procedures are enabled. Termination A boolean value being set to TRUE if if the Network Fast Byte Protocol entity should stop after return to the state “Idle“. The SDL definition of the Network Fast Byte Protocol entity process is shown in Figure C.4. 6 Recommendation X.633/Add.l (09/98) roces NFastByte par 1i -_-_-_ DLmabengh NATURPL, $ NrnaSndLfngthNATURA, I NrnaxRcirCengh NATURN I biWllowed BOOLEAN. I CPhn
