General Information

Abstract

This revision of ETS 300 325 shall provide bit compatibility with Common-ISDN-API v2.0 and ETS 300 325. It shall allow further common enhancements without loosing compatibility with Common-ISDN-API v2.0. This PCI shall ensure support to both application interfaces. Remarks: (agreed at TA21) The proposed scope is technically feasible. It results in offering two interface accesses (ETS 300 325 and Common-ISDN-API v2.0). The interfaces can be offered in a way, which guarantees binary compatibility to applications conforming to either specification. The code between the interface and the hardware, may or may not be common to both interface accesses. The code for the interface accesses shall comply with the definitions made for each interface, independant of whether the code is common or only able to drive one of the interface specifications. Future enhancements can be performed in a way, which does not destroy this binary compatibility. Consequently, this revision of ETS 300 325 shall maintain both descriptions (ETS 300 325 and Common-ISDN-API v2.0) besides a part, which contains common aspects and overall features. With this development future implementations will ensure cross compatibility between both specifications. ETS 300 325 is also to be revised to include 3 groups of extensions: -New exchange mechanism (Windows NT, OS2, Netware) -New user protocols (PPP, SDLC, VMO, inverted MDLC, PCM 56 kbit/s) -Miscellaneous features (DTMF, parameter duplication, extension messages)

Status
Published
Publication Date
30-Nov-2003
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Dec-2003
Due Date
01-Dec-2003
Completion Date
01-Dec-2003

Buy Documents

Standard

SIST ETS 300 838 E1:2003

English language (546 pages)
Preview
Preview
e-Library read for
×1 day

Overview

SIST ETS 300 838 E1:2003 defines the Harmonized Programmable Communication Interface (HPCI) standard for Integrated Services Digital Network (ISDN) systems. The standard, developed by the Slovenian Institute for Standardization (SIST) and aligned with ETSI guidelines, ensures bit and binary compatibility with both Common-ISDN-API v2.0 and ETS 300 325. This harmonization enables seamless interaction with applications conforming to either specification, facilitating interoperability and future enhancements without sacrificing compatibility. By standardizing the programmable communication interface, the document supports efficient development and deployment of ISDN communication solutions across multi-vendor and multi-platform environments.

Key Topics

  • ISDN Programmable Interfaces: Outlines the design for harmonized programmable interfaces, ensuring straightforward integration with ISDN hardware and software.
  • Binary Compatibility: Maintains binary compatibility for legacy and new applications through strict compliance with both Common-ISDN-API v2.0 and ETS 300 325.
  • Multi-Platform Support: Introduces enhanced interface mechanisms to support modern operating systems including Windows NT, OS/2, and Netware.
  • User Protocol Extensions: Accommodates a range of user-side protocols (e.g., PPP, SDLC, VMO, inverted MDLC, PCM 56 kbit/s) to meet diverse communication needs.
  • Supplementary and Miscellaneous Features: Supports features such as DTMF, parameter duplication, and extension messages for broader application scenarios.
  • Error Handling and Message Conventions: Specifies conventions and models for error handling, parameter checking, and message formatting to reinforce reliable ISDN operations.

Applications

The HPCI for ISDN as specified in SIST ETS 300 838 E1:2003 provides significant practical value in the following areas:

  • ISDN Application Development: Streamlines development for telephony, data transfer, and control applications by offering a unified API compatible across systems and vendors.
  • Cross-Vendor Interoperability: Ensures that applications developed under different ISDN interface standards can execute seamlessly without re-engineering, maximizing investment in existing systems.
  • Legacy System Integration: Facilitates the migration or coexistence of legacy ISDN solutions with modern applications without sacrificing system stability or compatibility.
  • Multi-OS Deployment: Enables deployment of ISDN-based communication services on diverse operating environments, including Windows NT, OS/2, and Netware.
  • Protocol Expansion: Supports evolving communication requirements by providing for new user protocols and feature extensions, ensuring future-ready deployments.
  • Efficient Maintenance: Reduces complexity in code maintenance by standardizing interactions between application interfaces and ISDN hardware, regardless of specification.

Related Standards

  • ETS 300 325: The foundational ISDN interface standard, with which this document remains compatible.
  • Common-ISDN-API v2.0: Widely adopted API for ISDN communication, supported in parallel to ensure application flexibility.
  • ISO 7776, HDLC, PPP, SDLC, V.110, V.120: Referenced protocols supported within the user and control planes for robust ISDN data transfer and management.
  • SIST ISO/IEC 3309: Related standard for interface and interconnection equipment applicable within digital network environments.

Keywords: ISDN, programmable communication interface, HPCI, binary compatibility, ETS 300 325, Common-ISDN-API v2.0, user protocols, telecommunication standards, multi-platform ISDN integration, cross-vendor interoperability.

This standard is essential for organizations developing ISDN-compliant systems, ensuring compatibility, ease of integration, and future scalability.

Buy Documents

Standard

SIST ETS 300 838 E1:2003

English language (546 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

BSI Group

BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.

UKAS United Kingdom Verified

NYCE

Mexican standards and certification body.

EMA Mexico Verified

ANCE

Mexican certification and testing association.

EMA Mexico Verified

Sponsored listings

Frequently Asked Questions

SIST ETS 300 838 E1:2003 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Integrated Services Digital Network (ISDN); Harmonized Programmable Communication Interface (HPCI) for ISDN". This standard covers: This revision of ETS 300 325 shall provide bit compatibility with Common-ISDN-API v2.0 and ETS 300 325. It shall allow further common enhancements without loosing compatibility with Common-ISDN-API v2.0. This PCI shall ensure support to both application interfaces. Remarks: (agreed at TA21) The proposed scope is technically feasible. It results in offering two interface accesses (ETS 300 325 and Common-ISDN-API v2.0). The interfaces can be offered in a way, which guarantees binary compatibility to applications conforming to either specification. The code between the interface and the hardware, may or may not be common to both interface accesses. The code for the interface accesses shall comply with the definitions made for each interface, independant of whether the code is common or only able to drive one of the interface specifications. Future enhancements can be performed in a way, which does not destroy this binary compatibility. Consequently, this revision of ETS 300 325 shall maintain both descriptions (ETS 300 325 and Common-ISDN-API v2.0) besides a part, which contains common aspects and overall features. With this development future implementations will ensure cross compatibility between both specifications. ETS 300 325 is also to be revised to include 3 groups of extensions: -New exchange mechanism (Windows NT, OS2, Netware) -New user protocols (PPP, SDLC, VMO, inverted MDLC, PCM 56 kbit/s) -Miscellaneous features (DTMF, parameter duplication, extension messages)

This revision of ETS 300 325 shall provide bit compatibility with Common-ISDN-API v2.0 and ETS 300 325. It shall allow further common enhancements without loosing compatibility with Common-ISDN-API v2.0. This PCI shall ensure support to both application interfaces. Remarks: (agreed at TA21) The proposed scope is technically feasible. It results in offering two interface accesses (ETS 300 325 and Common-ISDN-API v2.0). The interfaces can be offered in a way, which guarantees binary compatibility to applications conforming to either specification. The code between the interface and the hardware, may or may not be common to both interface accesses. The code for the interface accesses shall comply with the definitions made for each interface, independant of whether the code is common or only able to drive one of the interface specifications. Future enhancements can be performed in a way, which does not destroy this binary compatibility. Consequently, this revision of ETS 300 325 shall maintain both descriptions (ETS 300 325 and Common-ISDN-API v2.0) besides a part, which contains common aspects and overall features. With this development future implementations will ensure cross compatibility between both specifications. ETS 300 325 is also to be revised to include 3 groups of extensions: -New exchange mechanism (Windows NT, OS2, Netware) -New user protocols (PPP, SDLC, VMO, inverted MDLC, PCM 56 kbit/s) -Miscellaneous features (DTMF, parameter duplication, extension messages)

SIST ETS 300 838 E1:2003 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN); 35.200 - Interface and interconnection equipment. The ICS classification helps identify the subject area and facilitates finding related standards.

SIST ETS 300 838 E1:2003 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


SLOVENSKI STANDARD
01-december-2003
Digitalno omrežje z integriranimi storitvami (ISDN) – Usklajeni programirljivi
komunikacijski vmesnik (HPCI) za ISDN
Integrated Services Digital Network (ISDN); Harmonized Programmable Communication
Interface (HPCI) for ISDN
Ta slovenski standard je istoveten z: ETS 300 838 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
35.200 Vmesniška in povezovalna Interface and interconnection
oprema equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 838
TELECOMMUNICATION May 1998
STANDARD
Source: MTA Reference: RE/MTA-002040
ICS: 33.020
Key words: API, ISDN, PCI
Integrated Services Digital Network (ISDN);
Harmonized Programmable Communication Interface (HPCI)
for ISDN
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.fr - http://www.etsi.org
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998. All rights reserved.

Page 2
ETS 300 838: May 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Standards Making Support Dept." at the address shown on the title page.

Page 3
ETS 300 838: May 1998
Contents
Foreword .23
Introduction.23
1 Scope .25
2 Normative references.26
3 Definitions and abbreviations .27
3.1 Definitions .27
3.2 Abbreviations .28
4 General.29
4.1 Overview .29
4.2 Requirements .30
4.3 Reader's guide.31
5 Profile A.31
5.1 Reader's guidance and overview.31
5.1.1 Reader's guide .31
5.1.2 How to use this profile .32
5.1.3 Functional overview.33
5.1.4 Connection management .33
5.1.5 The planes.33
5.1.6 Properties .33
5.1.7 External equipment (e.g. telephony) .34
5.1.8 ISDN accesses and the multi-applications environment.34
5.1.9 Exchange mechanism.34
5.2 Message overview .34
5.2.1 Functional model.34
5.2.1.1 Introduction.34
5.2.1.2 Architecture.34
5.2.1.2.1 Profile A and its components.35
5.2.1.2.2 Profile A architecture .36
5.2.1.2.3 Co-ordination cases.36
5.2.1.3 Functionality.37
5.2.1.3.1 Introduction .37
5.2.1.3.2 Resource management .37
5.2.1.3.2.1 Attribute sets.37
5.2.1.3.2.2 Network Connection Objects .38
5.2.1.3.2.3 Support of external equipment.38
5.2.1.3.2.4 Support of security features.40
5.2.1.3.2.5 Support of manufacturer specific
features.40
5.2.1.3.3 Connection management.41
5.2.1.3.3.1 Connection set-up and removal.41
5.2.1.3.3.2 Support of supplementary services .41
5.2.1.3.4 Data management .41
5.2.1.4 Relating functionality to planes .42
5.2.1.4.1 Optional features .42
5.2.1.4.2 Administration Plane.42
5.2.1.4.3 Control Plane .43
5.2.1.4.4 User Plane .43
5.2.1.5 PUF NAF interactions.43
5.2.1.6 Total interaction overview.45
5.2.1.7 Identifiers .47
5.2.1.8 Error handling .48
5.2.1.8.1 Overview.48
5.2.1.8.2 Function error handling.48

Page 4
ETS 300 838: May 1998
5.2.1.8.3 Message error handling . 49
5.2.2 Information encoding . 49
5.2.3 Conventions. 50
5.2.3.1 Address conventions. 50
5.2.3.2 Provision of information . 50
5.2.3.3 Message conventions . 50
5.2.3.4 Parameter conventions . 51
5.2.3.4.1 Parameter ordering . 51
5.2.3.4.2 Parameter repetition. 51
5.2.3.4.3 Parameter checking . 51
5.2.3.5 Default philosophy. 51
5.2.4 User Plane particularities. 51
5.3 Exchange method . 52
5.3.1 Registration phase. 52
5.3.1.1 Overview . 52
5.3.1.2 PciGetHandles . 53
5.3.1.3 PciGetProperty. 54
5.3.1.4 PciRegister. 56
5.3.2 Deregistration phase. 57
5.3.2.1 PciDeregister. 57
5.3.3 Conversation phase. 57
5.3.3.1 Sending messages . 57
5.3.3.2 Receiving messages. 57
5.3.3.3 Receiving messages using the polling method. 58
5.3.3.4 Receiving messages using signal method. 58
5.3.3.5 PCI Message Parameter Block (PCIMPB). 58
5.3.3.6 PciPutMessage . 59
5.3.3.7 PciGetMessage. 60
5.3.3.8 PciSetSignal. 60
5.4 Administration Plane messages. 61
5.4.1 ACreateNCOReq. 62
5.4.2 NCOType and conditional parameter specification . 63
5.4.3 ACreateNCOCnf. 64
5.4.4 ADestroyNCOReq . 65
5.4.5 ADestroyNCOCnf . 65
5.4.6 AGetNCOInfoReq. 65
5.4.7 AGetNCOInfoCnf. 66
5.4.8 AErrorInd . 66
5.4.9 ASecurityReq. 67
5.4.10 ASecurityCnf. 67
5.4.11 AManufacturerReq. 68
5.4.12 AManufacturerInd . 68
5.4.13 AChangeNCOReq . 68
5.4.14 AChangeNCOCnf . 69
5.5 Control Plane messages . 69
5.5.1 Introduction . 69
5.5.1.1 Control Messages classes. 69
5.5.1.2 Sequencing of Control Plane messages. 71
5.5.2 CAlertReq . 74
5.5.3 CAlertInd. 75
5.5.4 CConnectReq . 75
5.5.5 CConnectInd. 76
5.5.6 CConnectRsp . 77
5.5.7 CConnectCnf . 78
5.5.8 CDisconnectReq. 78
5.5.9 CDisconnectInd . 78
5.5.10 CDisconnectRsp. 79
5.5.11 CDisconnectCnf. 79
5.5.12 CProgressInd. 80
5.5.13 CStatusInd . 80
5.5.14 CSetupAckInd. 80
5.5.15 CConnectInfoReq . 81
5.5.16 CProceedingInd . 81

Page 5
ETS 300 838: May 1998
5.5.17 CUserInformationReq .82
5.5.18 CUserInformationInd .82
5.5.19 CCongestionControlReq .83
5.5.20 CCongestionControlInd .83
5.5.21 CSuspendReq .84
5.5.22 CSuspendCnf.84
5.5.23 CResumeReq.84
5.5.24 CResumeCnf.85
5.5.25 CNotifyInd.85
5.5.26 CFacilityReq .86
5.5.27 CFacilityInd.86
5.5.28 CExtEquipAvailabalityInd .86
5.5.29 CExtEquipBlockDiallingInd.87
5.5.30 CExtEquipKeyPressedInd .87
5.5.31 CExtEquipOffHookInd .87
5.5.32 CExtEquipOnHookInd .88
5.5.33 CAddInfoReq.88
5.5.34 CAddInfoInd .88
5.5.35 CDtmfReq.89
5.5.36 CDtmfCnf .89
5.5.37 CDtmfInd .89
5.5.38 User to User information exchange.90
5.5.39 Implementation of supplementary services.90
5.5.39.1 Advice of Charge during call (AOC-D).90
5.5.39.2 Advice of Charge at End of call (AOC-E) .91
5.6 User Plane .91
5.6.1 User Plane Protocols Management Architecture .91
5.6.1.1 Introduction.91
5.6.1.2 Message access.92
5.6.1.2.1 The physical layer access
(transparent access).93
5.6.1.2.2 The link layer access .93
5.6.1.2.3 The network layer access .93
5.6.1.3 Protocols.94
5.6.1.3.1 Supported User Plane protocols.94
5.6.1.3.2 Protocol selection.94
5.6.1.3.2.1 NCOType parameter .95
5.6.1.3.2.2 UProtocol parameter.95
5.6.1.4 Co-ordination function.95
5.6.1.5 Selection criteria .97
5.6.1.5.1 NCO Selection: User Plane
information element .97
5.6.1.5.2 Action if no NCO available: User
Plane incoming call.97
5.6.1.6 User Plane error checking.97
5.6.1.7 User Plane attribute sets .97
5.6.2 Layer 1 Protocols.97
5.6.2.1 Transparent B-channel access with byte framing from the
network .97
5.6.2.1.1 Introduction .97
5.6.2.1.2 Messages .98
5.6.2.1.2.1 UDataReq .98
5.6.2.1.2.2 UDataInd.99
5.6.2.1.2.3 UErrorInd .99
5.6.2.1.3 Messages parameters .100
5.6.2.1.3.1 IdleFlag .100
5.6.2.1.3.2 NCOType.100
5.6.2.1.3.3 UProtocol .100
5.6.2.1.3.4 UAttributeName .100
5.6.2.1.3.5 UDirection .101
5.6.2.1.3.6 Cause.101
5.6.2.1.4 State diagram .101
5.6.2.1.5 Co-ordination function.101

Page 6
ETS 300 838: May 1998
5.6.2.1.6 Selection criteria. 101
5.6.2.1.7 Specific error handling . 101
5.6.2.1.8 Static attributes. 101
5.6.2.1.8.1 AttributeSet parameters . 101
5.6.2.1.8.2 Static attribute content. 102
5.6.3 Layer 2 Protocols. 102
5.6.3.1 ISO 7776 protocol . 102
5.6.3.1.1 Introduction. 102
5.6.3.1.2 Messages. 103
5.6.3.1.2.1 UConnectReq. 103
5.6.3.1.2.2 UConnectInd . 103
5.6.3.1.2.3 UConnectRsp. 103
5.6.3.1.2.4 UConnectCnf. 104
5.6.3.1.2.5 UDisconnectReq . 104
5.6.3.1.2.6 UDisconnectInd. 104
5.6.3.1.2.7 UDataReq. 104
5.6.3.1.2.8 UDataInd . 105
5.6.3.1.2.9 UReadyToReceiveReq. 105
5.6.3.1.2.10 UReadyToReceiveInd . 106
5.6.3.1.3 Messages parameters. 106
5.6.3.1.3.1 L2ConnectionMode . 106
5.6.3.1.3.2 L2FrameSize. 107
5.6.3.1.3.3 L2WindowSize . 107
5.6.3.1.3.4 L2XID . 107
5.6.3.1.3.5 NCOType . 107
5.6.3.1.3.6 UProtocol. 108
5.6.3.1.3.7 UAttributeName. 108
5.6.3.1.3.8 UDirection. 108
5.6.3.1.3.9 Cause. 108
5.6.3.1.3.10 Origin. 109
5.6.3.1.4 State diagram. 109
5.6.3.1.5 Co-ordination function . 110
5.6.3.1.6 Selection criteria. 110
5.6.3.1.7 Specific error handling and codes. 110
5.6.3.1.8 Static attributes. 110
5.6.3.1.8.1 AttributeSet parameters . 110
5.6.3.1.8.2 Static attribute content. 110
5.6.3.2 HDLC protocol. 111
5.6.3.2.1 Introduction. 111
5.6.3.2.2 Messages. 111
5.6.3.2.2.1 UDataReq. 111
5.6.3.2.2.2 UDataInd . 112
5.6.3.2.3 Messages parameters. 112
5.6.3.2.3.1 NCOType . 112
5.6.3.2.3.2 UProtocol. 112
5.6.3.2.3.3 UAttributeName. 113
5.6.3.2.3.4 UDirection. 113
5.6.3.2.4 State diagram. 113
5.6.3.2.5 Co-ordination function . 113
5.6.3.2.6 Selection criteria. 113
5.6.3.2.7 Specific error handling and codes. 113
5.6.3.2.8 Static attributes. 114
5.6.3.2.8.1 AttributeSet parameters . 114
5.6.3.2.8.2 Static attribute content. 114
5.6.3.3 HDLC protocol with error. 114
5.6.3.3.1 Introduction. 114
5.6.3.3.2 Messages. 115
5.6.3.3.2.1 UDataReq. 115
5.6.3.3.2.2 UDataInd . 115
5.6.3.3.3 Messages parameters. 115
5.6.3.3.3.1 NCOType . 116
5.6.3.3.3.2 UProtocol. 116
5.6.3.3.3.3 UAttributeName. 116

Page 7
ETS 300 838: May 1998
5.6.3.3.3.4 UDirection .116
5.6.3.3.3.5 Cause.117
5.6.3.3.3.6 State diagram .117
5.6.3.3.4 Co-ordination function.117
5.6.3.3.5 Selection criteria .117
5.6.3.3.6 Specific error handling .117
5.6.3.3.7 Static attributes .117
5.6.3.3.7.1 AttributeSet parameters.117
5.6.3.3.7.2 Static attribute content .117
5.6.3.4 PPP protocol.117
5.6.3.4.1 Introduction .117
5.6.3.4.2 Messages .118
5.6.3.4.2.1 UConnectReq .119
5.6.3.4.2.2 UConnectInd.119
5.6.3.4.2.3 UConnectRsp .119
5.6.3.4.2.4 UConnectCnf .120
5.6.3.4.2.5 UDisconnectReq.120
5.6.3.4.2.6 UDisconnectInd .120
5.6.3.4.2.7 UDataReq .120
5.6.3.4.2.8 UDataInd.121
5.6.3.4.2.9 UErrorInd .121
5.6.3.4.3 Messages parameters .121
5.6.3.4.3.1 NCOType.122
5.6.3.4.3.2 UProtocol .122
5.6.3.4.3.3 UAttributeName .122
5.6.3.4.3.4 UDirection .122
5.6.3.4.3.5 PPPCause .123
5.6.3.4.3.6 PPPDiagnostic.123
5.6.3.4.3.7 PPPNegotiation.124
5.6.3.4.3.8 PPPOrigin .125
5.6.3.4.4 State diagram .126
5.6.3.4.5 Co-ordination function.126
5.6.3.4.6 Selection criteria .126
5.6.3.4.7 Specific error handling and codes .126
5.6.3.4.7.1 Errors .126
5.6.3.4.7.2 Causes.127
5.6.3.4.8 Static attributes .127
5.6.3.4.8.1 AttributeSet parameters.127
5.6.3.4.8.2 Static attribute content .128
5.6.3.4.9 Protocol specific NAF property
information .128
5.6.3.5 SDLC protocol .128
5.6.3.5.1 Introduction .128
5.6.3.5.2 Messages .129
5.6.3.5.2.1 UConnectReq .130
5.6.3.5.2.2 UConnectInd.130
5.6.3.5.2.3 UConnectRsp .130
5.6.3.5.2.4 UConnectCnf .131
5.6.3.5.2.5 UDisconnectReq.131
5.6.3.5.2.6 UDisconnectInd .131
5.6.3.5.2.7 UDataReq .131
5.6.3.5.2.8 UDataInd.132
5.6.3.5.2.9 UExpeditedDataReq .132
5.6.3.5.2.10 UExpeditedDataInd.132
5.6.3.5.2.11 UReadyToReceiveReq .133
5.6.3.5.2.12 UReadyToReceiveInd.133
5.6.3.5.3 Messages parameters .133
5.6.3.5.3.1 L2ConnectionMode.134
5.6.3.5.3.2 L2FrameSize.134
5.6.3.5.3.3 L2WindowSize .135
5.6.3.5.3.4 L2XID.135
5.6.3.5.3.5 NCOType.135
5.6.3.5.3.6 ReadyFlag.135

Page 8
ETS 300 838: May 1998
5.6.3.5.3.7 UProtocol. 136
5.6.3.5.3.8 UAttributeName. 136
5.6.3.5.3.9 UDirection. 136
5.6.3.5.3.10 UserData . 136
5.6.3.5.3.11 SDLCCause . 136
5.6.3.5.3.12 SDLCOrigin . 137
5.6.3.5.4 State diagram. 137
5.6.3.5.5 Co-ordination function . 137
5.6.3.5.6 Selection criteria. 137
5.6.3.5.7 Specific error handling and codes. 138
5.6.3.5.7.1 Invalid use of user messages. 138
5.6.3.5.7.2 Causes . 138
5.6.3.5.8 Static attributes. 138
5.6.3.5.8.1 AttributeSet parameters . 138
5.6.3.5.8.2 Static attribute content. 139
5.6.3.6 V.110 protocol. 139
5.6.3.6.1 Introduction. 139
5.6.3.6.2 Messages. 140
5.6.3.6.2.1 UConnectReq. 140
5.6.3.6.2.2 UConnectInd . 140
5.6.3.6.2.3 UConnectRsp. 140
5.6.3.6.2.4 UConnectCnf. 141
5.6.3.6.2.5 UDisconnectReq . 141
5.6.3.6.2.6 UDisconnectInd. 141
5.6.3.6.2.7 UDataReq. 141
5.6.3.6.2.8 UDataInd . 142
5.6.3.6.2.9 UReadyToReceiveReq. 142
5.6.3.6.2.10 UReadyToReceiveInd . 142
5.6.3.6.3 Messages parameters. 143
5.6.3.6.3.1 NCOType . 143
5.6.3.6.3.2 ReadyFlag . 143
5.6.3.6.3.3 UProtocol. 144
5.6.3.6.3.4 UAttributeName. 144
5.6.3.6.3.5 UDirection. 144
5.6.3.6.3.6 V.110Cause. 144
5.6.3.6.3.7 V.110Origin . 144
5.6.3.6.3.8 FlowControlMechanism. 145
5.6.3.6.3.9 FlowControlCharacters . 145
5.6.3.6.3.10 MomentNumber . 145
5.6.3.6.3.11 V.110BChannelDisconnection. 145
5.6.3.6.4 State diagram. 146
5.6.3.6.5 Co-ordination function . 146
5.6.3.6.6 Selection criteria. 146
5.6.3.6.7 Specific error handling and codes. 146
5.6.3.6.7.1 Invalid use of User Plane messages. 147
5.6.3.6.7.2 Causes . 147
5.6.3.6.8 Static attributes. 147
5.6.3.6.8.1 AttributeSet parameters . 147
5.6.3.6.8.2 Static attribute content. 147
5.6.4 Layer 3 protocols . 147
5.6.4.1 ISO 8208 protocol and ETS 300 080 protocol . 148
5.6.4.1.1 Introduction. 148
5.6.4.1.2 Description of messages. 148
5.6.4.1.2.1 UConnectReq. 150
5.6.4.1.2.2 UConnectInd . 150
5.6.4.1.2.3 UConnectRsp. 151
5.6.4.1.2.4 UConnectCnf. 152
5.6.4.1.2.5 UDisconnectReq . 152
5.6.4.1.2.6 UDisconnectInd. 153
5.6.4.1.2.7 UDataReq. 153
5.6.4.1.2.8 UDataInd . 153
5.6.4.1.2.9 UExpeditedDataReq. 154
5.6.4.1.2.10 UExpeditedDataInd . 154

Page 9
ETS 300 838: May 1998
5.6.4.1.2.11 UResetReq .154
5.6.4.1.2.12 UResetInd.155
5.6.4.1.2.13 UResetRsp .155
5.6.4.1.2.14 UResetCnf .155
5.6.4.1.2.15 UDataAcknowledgeReq.156
5.6.4.1.2.16 UDataAcknowledgeInd .156
5.6.4.1.2.17 UReadyToReceiveReq .156
5.6.4.1.2.18 UReadyToReceiveInd.157
5.6.4.1.3 Messages parameters .157
5.6.4.1.3.1 Algorithm.158
5.6.4.1.3.2 Bilateral closed user group (Bcug).158
5.6.4.1.3.3 Bit_DQM .159
5.6.4.1.3.4 CalledDTEAddress .159
5.6.4.1.3.5 CalledDTEAddressExt .159
5.6.4.1.3.6 CallingDTEAddress .160
5.6.4.1.3.7 CallingDTEAddressExt .160
5.6.4.1.3.8 ExpeditedData .160
5.6.4.1.3.9 FacilityData .160
5.6.4.1.3.10 FastSelect.161
5.6.4.1.3.11 GroupID .161
5.6.4.1.3.12 L2ConnectionMode.161
5.6.4.1.3.13 L2FrameSize.162
5.6.4.1.3.14 L2WindowSize .162
5.6.4.1.3.15 L2XID.162
5.6.4.1.3.16 L3ConnectionMode.162
5.6.4.1.3.17 L3IncomingVCCount.162
5.6.4.1.3.18 L3OutgoingVCCount.163
5.6.4.1.3.19 L3TwoWayVCCount .163
5.6.4.1.3.20 NCOType.163
5.6.4.1.3.21 PacketSize.163
5.6.4.1.3.22 QOSParameters .164
5.6.4.1.3.23 ReadyFlag.165
5.6.4.1.3.24 ReceiptConfirm.165
5.6.4.1.3.25 RespondingDTEAddress .165
5.6.4.1.3.26 RespondingDTEAddressExt.165
5.6.4.1.3.27 TEI .165
5.6.4.1.3.28 UProtocol .166
5.6.4.1.3.29 UAttributeName .166
5.6.4.1.3.30 UDirection .166
5.6.4.1.3.31 UserData.166
5.6.4.1.3.32 WindowSize .167
5.6.4.1.3.33 X213Cause .167
5.6.4.1.3.34 X213Origin.167
5.6.4.1.3.35 X25Cause .167
5.6.4.1.3.36 X25Diagnostic.168
5.6.4.1.4 State diagram .168
5.6.4.1.5 Co-ordination function.169
5.6.4.1.6 Selection criteria .170
5.6.4.1.6.1 NCO Selection .170
5.6.4.1.6.1.1 Packet size negotiation.170
5.6.4.1.6.1.2 Window size negotiation .170
5.6.4.1.6.1.3 Effective packet size and window size
negotiation .170
5.6.4.1.6.2 Action if no NCO available.170
5.6.4.1.7 Specific error handling and codes .170
5.6.4.1.7.1 Invalid use of User Plane messages .171
5.6.4.1.7.2 Other errors .171
5.6.4.1.7.3 Causes.171
5.6.4.1.8 AttributeSet .172
5.6.4.1.8.1 AttributeSet parameters.172
5.6.4.1.8.2 Static attribute content .172
5.6.4.2 T.70NL protocol .173
5.6.4.2.1 Introduction .173

Page 10
ETS 300 838: May 1998
5.6.4.2.2 Messages. 173
5.6.4.2.2.1 UDataReq. 174
5.6.4.2.2.2 UDataInd . 174
5.6.4.2.3 Messages parameters. 174
5.6.4.2.3.1 Bit_DQM. 175
5.6.4.2.3.2 NCOType . 175
5.6.4.2.3.3 PacketSize . 175
5.6.4.2.3.4 UProtocol. 176
5.6.4.2.3.5 UAttributeName. 176
5.6.4.2.3.6 UDirection. 176
5.6.4.2.4 State diagram. 176
5.6.4.2.5 Co-ordination function . 176
5.6.4.2.6 Selection criteria. 176
5.6.4.2.7 Specific error handling and codes. 176
5.6.4.2.8 Static attributes. 176
5.6.4.2.8.1 AttributeSet parameters . 176
5.6.4.2.8.2 Static attribute content. 177
5.6.5 V.120 Protocol . 177
5.6.5.1 Introduction . 177
5.6.5.2 Messages. 177
5.6.5.2.1 UDataReq. 178
5.6.5.2.2 UDataInd . 178
5.6.5.2.3 UReadyToReceiveReq. 178
5.6.5.2.4 UReadyToReceiveInd . 179
5.6.5.2.5 UErrorInd. 179
5.6.5.3 Messages parameters . 179
5.6.5.3.1 NCOType . 180
5.6.5.3.2 ReadyFlag . 180
5.6.5.3.3 UProtocol. 180
5.6.5.3.4 UAttributeName. 180
5.6.5.3.5 UDirection. 181
5.6.5.3.6 Cause. 181
5.6.5.3.7 LowerLayerReference. 181
5.6.5.3.8 BlockType. 181
5.6.5.3.9 V120FunctionMode . 181
5.6.5.4 State diagram. 182
5.6.5.5 Co-ordination function. 182
5.6.5.6 Selection criteria. 182
5.6.5.7 Specific error handling . 182
5.6.5.8 Static attributes . 182
5.6.5.8.1 AttributeSet parameters . 182
5.6.5.8.2 Static attribute content. 182
5.6.5.9 Protocol specific NAF property information. 182
5.6.5.10 Impact on the Control Plane . 182
5.6.6 T.30 protocol. 183
5.6.6.1 Overview of T 30 messages . 183
5.6.6.2 Sequencing of User Plane messages. 185
5.6.6.3 Detail of T.30 protocol messages . 185
5.6.6.3.1 UConnectReq. 185
5.6.6.3.2 UConnectInd . 186
5.6.6.3.3 UConnectRsp. 186
5.6.6.3.4 UConnectCnf. 186
5.6.6.3.5 UDisconnectReq . 186
5.6.6.3.6 UDisconnectInd. 187
5.6.6.3.7 UDataReq. 187
5.6.6.3.8 UDataInd . 187
5.6.6.3.9 UDataAcknowledgeReq . 188
5.6.6.3.10 UDataAcknowledgeInd. 188
5.6.6.3.11 UReadyToReceiveReq. 188
5.6.6.3.12 UReadyToReceiveInd . 189
5.6.6.3.13 UInformationInd. 189
5.6.6.3.14 URegisterMailBoxReq. 189
5.6.6.3.15 URegisterMailBoxCnf. 190

Page 11
ETS 300 838: May 1998
5.6.6.3.16 UDestroyMailBoxReq.190
5.6.6.3.17 UDestroyMailBoxCnf.190
5.6.6.3.18 ULocalPollingInd.190
5.6.6.3.19 ULocalPollingRsp.191
5.6.6.3.20 URemotePollingReq .191
5.6.6.3.21 URemotePollingInd.191
5.6.6.3.22 USwitchToVoiceModeReq.191
5.6.6.3.23 USwitchToVoiceModeCnf.192
5.6.6.3.24 USwitchToVoiceModeInd.192
5.6.6.3.25 USwitchToVoiceModeRsp .192
5.6.6.4 Message parameters.193
5.6.6.4.1 CalledDTEAddress .193
5.6.6.4.2 NCOType.193
5.6.6.4.3 DataBlock .194
5.6.6.4.4 DataDescription .195
5.6.6.4.5 MailBoxMnemonic .195
5.6.6.4.6 MailBoxNumber .196
5.6.6.4.7 MailBoxType .196
5.6.6.4.8 NegociatedCharacteristic.197
5.6.6.4.9 OctetInverted .198
5.6.6.4.10 PageAcknowledgement .198
5.6.6.4.11 Password .198
5.6.6.4.12 PollingNumber .198
5.6.6.4.13 PollingFlag .198
5.6.6.4.14 ReceivePageQuality .199
5.6.6.4.15 RemoteDesignation .199
5.6.6.4.16 SwitchFlag .199
5.6.6.4.17 T30Cause .199
5.6.6.4.18 T30Characteristics.200
5.6.6.4.19 UseOfStrips .200
5.7 Message parameters.200
5.7.1 AdditionInformation .200
5.7.2 Algorithm .201
5.7.3 BearerCap .201
5.7.4 CalledNumber .201
5.7.5 CalledSubaddress .202
5.7.6 CallingNumber.202
5.7.7 CallingSubaddress .203
5.7.8 CAttributeName.203
5.7.9 CauseToNAF.203
5.7.10 CauseToPUF.203
5.7.11 CDirection.204
5.7.12 ChannelIdentification.204
5.7.13 ChargingInfo.
...