SIST ETS 300 104:1996

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.SULNOMXþLWHYIntegrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN basic access Layer 3 aspects (Candidate NET 3, Part 2)33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 104 Edition 1SIST ETS 300 104:1996en01-GHFHPEHU-1996SIST ETS 300 104:1996SLOVENSKI
STANDARD



PSIST ETS 300 104:1996



EUROPEANETS 300 104TELECOMMUNICATIONJuly 1991STANDARDSource: ETSI TC-SPSReference:ICS:33.080Key words:ISDN, ISDN basic access, Layer 3 aspectsIntegrated Services Digital Network (ISDN);Attachment requirements for terminal equipment to connect toan ISDN using ISDN basic accessLayer 3 aspects(The text of this ETS may be utilized, wholly or in part,for the establisment of NET 3 Part 2ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1991. All rights reserved.PSIST ETS 300 104:1996New presentation - see History box



Page 2ETS 300 104: July 1991Whilst 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 Editing and Committee Support Dept." at the address shown on the title page.PSIST ETS 300 104:1996



Page 3ETS 300 104: July 1991ContentsForeword.5Scope.71General.71.1Introduction.71.2Configurations at User Premises.71.3Relationship to other Attachment standards/NETs.71.4Testing and Approval Methodology.71.5Information to be provided by the Apparatus Supplier.81.6Test Environment.82Layer 3 Requirements.82.1General.82.2Static Attachment Requirements.92.2.1Functional Characteristics.92.2.1.1General.92.2.1.2Overview of Call Control.102.2.1.3Message Definition and Content.112.2.1.4Message Format and Information Element Coding.122.2.1.5Layer 3 System Parameters.132.2.2Interface Procedures.142.2.2.1Call Establishment.142.2.2.2Call Clearing.152.2.2.3Tones and Announcements.162.2.2.4Restart.162.2.2.5Call Re-arrangement.162.2.2.6User-to-user Signalling.172.2.2.7Handling of Error Conditions.172.2.2.8Packet Communications.172.2.2.9Supplementary Services.182.2.2.10SDLs.183Definitions and Abbreviations.184References.18Annex A:Test schedule for layer 3 conformance.21Annex B:Example of Information to be Provided by the Apparatus Supplier.185B.1Introduction.185B.2Information to be provided by the Apparatus Supplier.185B.2.1Information with respect to a PICS.185B.2.2Information with respect to a PIXIT.185Annex C:Test report format.1861System test report for equipment tested against the requirements specified in ETS 300 104(Candidate NET 3, Part 2).1861.1Test Laboratory.1861.2Client Information.1861.3Product.186PSIST ETS 300 104:1996



Page 4ETS 300 104: July 19911.4System Conformance Test Report.1862Test Conditions.1873System Report Summary.1873.1Layer 3 Test Report Summary.1874Summary of Error Report.1875Summary of Particular Events.187History.189PSIST ETS 300 104:1996



Page 5ETS 300 104: July 1991ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols andSwitching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI) andwas adopted, having passed through the ETSI standards approval procedure.The text of this ETS may be utilized, wholly or in part, for the establishment of NET 3 part 2.PSIST ETS 300 104:1996



Page 6ETS 300 104: July 1991Blank pagePSIST ETS 300 104:1996



Page 7ETS 300 104: July 1991ScopeIn accordance with CCITT Recommendation I.420 [5] and ETS 300 102-1 [2] and ETS 300 102-2 [3], thisstandard specifies the layer 3 access control protocol to be offered by terminal equipment as defined insubclause 1.1.2 at the T reference point or coincident S and T reference point at an interface to a publictelecommunications network presented at an ISDN basic access point.The static attachment requirements and tests specified in this ETS are for TEs having the capability of bothoriginating a circuit switched call and receiving an incoming circuit switched call. In addition, certain TEs ofa specialised nature may employ supplementary services as part of their default operation characteristics.The requirements and tests for these specialised terminals are also not covered in this standard.NOTE:No requirements or tests are included in this document concerning the procedures forpacket communications, user-to-user signalling or supplementary services except forthe case of the terminal portability supplementary service which can be considered asan essential feature of many ISDN terminals. However, TEs implementing packetfacilities, user-to-user signalling or supplementary services may be subject to additionaland/or alternative testing by those Administrations whose ISDNs provide the support ofpacket calls, user-to-user signalling and/or supplementary services.1General1.1Introduction1.1.1 This standard specifies the basic requirements concerning the layer 3 basic call control protocolwhich Terminal Equipment (TE) has to meet for attachment to the public ISDN basic user-network interfaceat the T reference point or coincident S and T reference point. The requirements specified in this standardare in addition to those relating to the layer 1 and 2 aspects given in NET 3, Part 1. This standard does notcover all the requirements which a specific type of TE has to meet. However, standards/NETs which defineattachment requirements relevant to a specific type of TE should refer to this standard for the attachmentrequirements within the scope of this standard.1.1.2 Unless otherwise stated, the use of the term terminal equipment (TE) within this standard refers tocustomer's terminal apparatus which may be a TE1 (Terminal Equipment Type 1), a TA (Terminal Adaptor)or an NT2 (Network Termination Type 2) as defined in CCITT Recommendation I.411 [4].1.1.3 Communication between adjacent layers (primitive procedures) is conceptual and allows thedescription of interactions between functions dedicated to different layers within a TE. These primitiveprocedures do not constrain implementation, are system internal and therefore cannot be tested inisolation.
However, as seen from outside, the design of TE shall be such that the sequence of eventsacross the user-network interface must be the same as if the primitives were implemented as described inETS 300 102-1 [2] and ETS 300 102-2 [3].1.2Configurations at User PremisesThe operational configurations specified in subclause 1.2 of NET 3, Part 1 [1] are applicable to thisstandard.1.3Relationship to other Attachment standards/NETsWhere a TE supports services specified in other NETs, additional requirements may apply and will befound in the specific terminal NET.1.4Testing and Approval Methodology1.4.1 The tests specified in Annex A of this ETS shall verify the suitability of the TE for attachment to thepublic telecommunications network. Those functions and procedures which are optional as indicated in thisETS and for which there are tests in Annex A of this ETS shall be subject to an attachment test if they areimplemented in the TE. The means of determining whether an optional function/procedure has beenPSIST ETS 300 104:1996



Page 8ETS 300 104: July 1991implemented is by either Apparatus Supplier's declaration or as a result of testing the equipment for thisfunction/procedure. Where no declaration is made by the Apparatus Supplier as to the implementation (ornot) of an optional function/procedure, and the testing of this feature reveals that the option is incorrectly(or partially) implemented, the option shall be deemed to have been implemented and the apparatus shallbe evaluated accordingly.1.4.2 The user-network interface at the T reference point or coincident S and T reference point providesthe only access for testing the terminal equipment. However, actions at the user side of the equipmentunder test (e.g. at the man-machine interface, execution of higher layer processes, at the interface at theR reference point in the case of terminal adaptors) shall be used to invoke actions at layer 3 of theD-channel protocol within the equipment under test.1.4.3 Connection of Equipment Under Test to the Tester shall be carried out in accordance with subclause1.4.3 of NET 3, Part 1 [1].1.4.4 The attachment tests for each layer of the D-channel protocol are specified separately (layers 1 and2 in NET 3, Part 1, Annex A, Parts 1 and 2 respectively and layer 3 in Annex A of this document) and thetest configuration(s) to be used in testing each layer is specified in that part of the ETS relating to theattachment tests for that layer.1.4.5 When carrying out a test, it may be necessary for the equipment under test to be maintained in theactive state of a call. In such cases, it may be necessary for the tester to achieve this by proceduralmeans related to functional entities outside the scope of this ETS (e.g. layer 4 and upwards). Theprocedural means may include:a)the tester sending a specified bit pattern within the B-channel subsequent to the CONNECT orCONNECT ACKNOWLEDGE message being sent in the D-channel; and/orb)if possible, disabling the TE timers associated with layer 4 and upwards or lower layers of the userplane (reference CCITT Recommendation I.320 [8].Any actions necessary to prevent the equipment under test from premature clearing shall be indicated bythe supplier (see subclause 1.5).1.5Information to be provided by the Apparatus SupplierThe apparatus supplier shall provide two kinds of information:-information with respect to the protocol: Protocol Implementation Conformance Statement (PICS);-information with respect to the man-machine interface: Protocol Implementation eXtra Informationfor Testing (PIXIT).The complete list of the information to be provided by the apparatus supplier is a matter between theapparatus supplier and the testing house but an example of the possible information (relating to layer 3protocol aspects) to be supplied is given for information in Annex B to this ETS.1.6Test EnvironmentThe conditions under which the tests specified in Annex A shall be carried out are specified in subclause1.7 of NET 3, Part 1 [1].2Layer 3 Requirements2.1GeneralThis section defines the requirements for TE operation relating to the D-channel Layer 3 protocol withreference to Basic Call Control.PSIST ETS 300 104:1996



Page 9ETS 300 104: July 1991A TE shall support the protocols associated with the user side in accordance with ETS 300 102-1 [2] andETS 300 102-2 [3] and where applicable meet those functional requirements which are compulsory toprovide the communication functionality specified in a ETS/NET concerned with a specific type of TE.The layer 3 D-channel protocol implemented in the TE shall satisfy ETS 300 102-1 [2] and and ETS 300102-2 [3] as indicated in the Tables 1 to 15 in section 2.2 of this ETS.2.2Static Attachment RequirementsThe static attachment requirements (SAR) define features and functions which at minimum must besupported to ensure the operational integrity of an ISDN I-series terminal. For layer 3 the SAR is specifiedin Tables 1 to 15 below.Within Tables 1 to 15, the following notation is used:-M =mandatory ie the TE implementation shall satisfy clauses in that section relatingto the operation of the layer 3 protocol in the TE.O =optional ie it is optional whether the TE implements that function but if thefunction is implemented it shall satisfy the clauses in that section relating to theoperation of the TE layer 3 protocol.N/A =not applicable ie either the requirements specified in the section on the TE shallnot be applied for attachment approval or else the section relates solely to theoperation of the network, or it relates to the operation at the man-machineinterface.GID =the section provides General Information and Definitions.ETS =ETS 300 102-1 [2].SAR =Static Attachment Requirement (minimal acceptance).COMMENT =Available field for supportive comments/values. (The comments references applyto this document).2.2.1Functional Characteristics2.2.1.1GeneralTable 1: Layer 3 Functional Characteristics RequirementsÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
FUNCTIONAL CHARACTERISTICS
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Function = General
³ ETS
³
SAR
³
COMMENTS
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ General
³ §1
³
GID
³
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙPSIST ETS 300 104:1996



Page 10ETS 300 104: July 19912.2.1.2Overview of Call ControlTable 2: Layer 3 Call States RequirementsÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
FUNCTIONAL CHARACTERISTICS
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Function = Call States
³ ETS
³
SAR
³
COMMENTS
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Overview of Call Control
³ §2
³
GID
³ Background Info.
³³ Circuit Switched Calls
³ §2.1
³
GID
³
³³ Call states at the user side
³ §2.1.1
³
GID
³
³³ of the interface
³
³
³
³³ Null state (U0)
³ §2.1.1.1 ³
M
³
³³ Call Initiated (U1)
³ §2.1.1.2 ³
M
³
³³ Overlap sending (U2)
³ §2.1.1.3 ³
O
³
³³ Outgoing call proceeding (U3)
³ §2.1.1.4 ³
NOTE
³
³³ Call delivered (U4)
³ §2.1.1.5 ³
NOTE
³
³³ Call present (U6)
³ §2.1.1.6 ³
M
³ Transitory state
³³ Call received (U7)
³ §2.1.1.7 ³
O
³ M if alerting used ³³ Connect request (U8)
³ §2.1.1.8 ³
M
³
³³ Incoming call proceeding (U9)
³ §2.1.1.9 ³
O
³ M if call proc.used³³ Active (U10)
³ §2.1.1.10³
M
³
³³ Disconnect request (U11)
³ §2.1.1.11³
M
³
³³ Disconnect indication (U12)
³ §2.1.1.12³
M
³
³³ Suspend request (U15)
³ §2.1.1.13³
O
³ M if call rearran- ³³
³
³
³
gement used
³³ Resume request (U17)
³ §2.1.1.14³
O
³ M if call rearran- ³³
³
³
³
gement used
³³ Release request (U19)
³ §2.1.1.15³
M
³
³³ Overlap receiving (U25)
³ §2.1.1.16³
O
³ M if overlap
³³
³
³
³
receiving used
³³ Call states at the network
³ §2.1.2
³
N/A
³
³³ side of the interface
³
³
³
³³ Packet mode access connections
³ §2.2
³
N/A
³ see NOTE in scope
³³ Temporary signalling connections³ §2.3
³
N/A
³ see NOTE in scope
³³ States associated with the
³ §2.4
³
O
³)
³³ global call reference
³
³
³)
³³ Call states at the user
³ §2.4.1
³
O
³)
³³ side of the interface
³
³
³) M if Restart
³³ Null (Rest 0)
³ §2.4.1.1 ³
O
³) procedure used.
³³ Restart request (Rest 1)
³ §2.4.1.2 ³
O
³)
³³ Restart (Rest 2)
³ §2.4.1.3 ³
O
³)
³³ Call states at the network
³ §2.4.2
³
N/A
³
³³ side of the interface
³
³
³
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙNote to table 2:NOTE:A given TE may not need this call state, but to fulfil procedures specified in ETS 300102-1 [2], clause 5 and all its subsections, all TEs must implement the call state.PSIST ETS 300 104:1996



Page 11ETS 300 104: July 19912.2.1.3Message Definition and ContentTable 3: Layer 3 Message Definition and Content RequirementsÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
FUNCTIONAL CHARACTERISTICS
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Function = Message definition
³ ETS
³
SAR
³
COMMENTS
³³
and content
³
³
³
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Message Functional Definitions ³ §3
³
GID
³ NOTE 1
³³ and Content
³
³
³
³³ Messages for Circuit Mode
³ §3.1
³
GID
³ Summary of
³³ Connections
³
³
³ message repertoire ³³ ALERTING
³ §3.1.1
³ NOTE 2 ³
³³ CALL PROCEEDING
³ §3.1.2
³ NOTE 2 ³
³³ CONGESTION CONTROL
³ §3.1.3
³
N/A
³ see NOTE in Scope
³³ CONNECT
³ §3.1.4
³
M
³
³³ CONNECT ACKNOWLEDGE
³ §3.1.5
³ NOTE 2 ³
³³ DISCONNECT
³ §3.1.6
³
M
³
³³ FACILITY
³ §3.1.7
³
N/A
³ see NOTE in Scope
³³ INFORMATION
³ §3.1.8
³ NOTE 2 ³
³³ NOTIFY
³ §3.1.9
³ NOTE 2 ³
³³ PROGRESS
³ §3.1.10
³ NOTE 2 ³
³³ RELEASE
³ §3.1.11
³
M
³
³³ RELEASE COMPLETE
³ §3.1.12
³
M
³
³³ RESUME
³ §3.1.13
³
O
³ NOTE 4
³³ RESUME ACKNOWLEDGE
³ §3.1.14
³
O
³ NOTE 4
³³ RESUME REJECT
³ §3.1.15
³
O
³ NOTE 4
³³ SETUP
³ §3.1.16
³
M
³
³³ SETUP ACKNOWLEDGE
³ §3.1.17
³
O
³
³³ STATUS
³ §3.1.18
³
M
³
³³ STATUS ENQUIRY
³ §3.1.19
³
O
³
³³ SUSPEND
³ §3.1.20
³
O
³ NOTE 4
³³ SUSPEND ACKNOWLEDGE
³ §3.1.21
³
O
³ NOTE 4
³³ SUSPEND REJECT
³ §3.1.22
³
O
³ NOTE 4
³³ USER INFORMATION
³ §3.1.23
³
N/A
³ see NOTE in Scope
³³ Messages for Packet Mode
³ §3.2
³
N/A
³ see NOTE in Scope
³³ Connections
³
³
³
³³ Messages for user to user
³ §3.3
³
N/A
³ see NOTE in Scope
³³ signalling not associated
³
³
³
³³ with circuit switched calls
³
³
³
³³ Messages used with the
³ §3.4
³
³
³³ Global Call Reference
³
³
³
³³ RESTART
³ §3.4.1
³ NOTE 3 ³
³³ RESTART ACKNOWLEDGE
³ §3.4.2
³ NOTE 3 ³
³³ STATUS
³ §3.4.3
³
O
³
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙNotes to table 3:NOTE 1:Refer to ETS 300 102-1 [2], subclause 3.1.1 to subclause 3.1.23 for the content ofeach message.NOTE 2:It is optional whether a TE ever transmits this message but all TEs must be able toreceive the message and handle it correctly as defined in the procedures specified inETS 300 102-1 [2], clause 5 and all its subsections.NOTE 3:The implementation of both the RESTART and the RESTART ACKNOWLEDGEmessages is optional. However, if the capability to transmit the RESTART message isimplemented then it is mandatory to implement the capability to receive the RESTARTACKNOWLEDGE message. Similarly, if the capability to receive the RESTARTmessage is implemented, it is mandatory to implement the capability to transmit theRESTART ACKNOWLEDGE message.NOTE 4:The support of the call re-arrangement procedure is optional. However, if call re-arrangement is implemented then all the messages RESUME, RESUMEACKNOWLEDGE, RESUME REJECT, SUSPEND, SUSPEND ACKNOWLEDGE,SUSPEND REJECT must be implemented.PSIST ETS 300 104:1996



Page 12ETS 300 104: July 19912.2.1.4Message Format and Information Element CodingTable 4: Layer 3 Message Format and Coding RequirementsÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
FUNCTIONAL CHARACTERISTICS
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Function = Message Format and
³ ETS
³
SAR
³
COMMENTS
³³
Information Element ³
³
³
³³
Coding
³
³
³
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ General Message Format and
³ §4
³ NOTE 1 ³
³³ Information Element Coding
³
³
³
³³ Overview
³ §4.1
³
M
³
³³ Protocol Discriminator
³ §4.2
³
M
³
³³ Call Reference
³ §4.3
³
M
³
³³ Message Type
³ §4.4
³
M
³
³³ Other Information Elements
³ §4.5
³
³
³³ Coding Rules
³ §4.5.1
³
M
³
³³ Codeset 0
³ §4.5.1.1 ³
M
³
³³ Codeset 5
³ §4.5.1.2 ³ NOTE 6 ³
³³ Extensions of Codesets
³ §4.5.2
³
M
³
³³ Locking Shift Procedure
³ §4.5.3
³ NOTE 2 ³
³³ Non-locking Shift Procedure
³ §4.5.4
³ NOTE 2 ³
³³ Bearer Capability
³ §4.5.5
³
M
³
³³ Call Identity
³ §4.5.6
³
O
³ NOTE 3
³³ Call State
³ §4.5.7
³
M
³
³³ Called Party Number
³ §4.5.8
³
M
³
³³ Called Party Subaddress
³ §4.5.9
³
N/A
³ see NOTE in Scope
³³ Calling Party Number
³ §4.5.10
³
N/A
³ see NOTE in Scope
³³ Calling Party Subaddress
³ §4.5.11
³
N/A
³ see NOTE in Scope
³³ Cause
³ §4.5.12
³
M
³
³³ Channel Identification
³ §4.5.13
³ NOTE 2 ³
³³ Congestion Level
³ §4.5.14
³
N/A
³ see NOTE in Scope
³³ Display
³ §4.5.15
³ NOTE 7 ³
³³ High Layer Compatibility
³ §3.1.16
³
O
³
³³ Keypad Facility
³ §4.5.17
³
N/A
³ see NOTE in Scope
³³ Low Layer Compatibility
³ §4.5.18
³
O
³
³³ More Data
³ §4.5.19
³
N/A
³ see NOTE in Scope
³³ Network-specific Facilities
³ §4.5.20
³
N/A
³ see NOTE in Scope
³³ Notification Indicator
³ §4.5.21
³ NOTE 2 ³
³³ Progress Indicator
³ §4.5.22
³ NOTE 2 ³
³³ Restart Indicator
³ §4.5.24
³
O
³
³³ Segmented Message
³ §4.5.25
³
N/A
³
³³ Sending Complete
³ §4.5.26
³ NOTE 4 ³
³³ Signal
³ §4.5.27
³
N/A
³ see NOTE in Scope
³³ Transit Network Selection
³ §4.5.28
³
O
³
³³ User to user
³ §4.5.29
³
N/A
³ see NOTE in Scope
³³ Date/Time
³ §4.6.1
³ NOTE 5 ³
³³ Facility
³ §4.6.2
³
N/A
³ see NOTE in Scope
³³ Information Element
³
³
³
³³ Information Element for
³ §4.7
³
N/A
³ see NOTE in Scope
³³ Packet Communications
³
³
³
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙNotes to table 4:NOTE 1:Refer to ETS 300 102-1 [2], subclause 4.2 to subclause 4.5.28 for the content of eachinformation element.NOTE 2:It is optional whether a TE ever transmits this information element but all TEs must beable to receive the information element and handle it correctly as defined in theprocedures specified in ETS 300 102-2 [2], clause 5 and all its subsections.NOTE 3:The support of the call re-arrangement procedure is optional. However ETSs/NETsrelating to a specific terminal type may require the procedure to be mandatory forthose specific types of terminals. Furthermore, even if the call re-arrangementprocedure is used, the support of this information element is optional.NOTE 4:It is optional for a TE to generate this information element, but TEs which implementthe Overlap receiving procedure shall recognize the information element and handle itcorrectly as defined in the procedures specified in ETS 300 102-2 [2], clause 5 and allits subsections.PSIST ETS 300 104:1996



Page 13ETS 300 104: July 1991NOTE 5:It is mandatory that the TE recognises the Date/time information element meaning thatno error handling procedures shall be initiated upon its reception. ETSs/NETs relatingto a specific terminal type may require the use of the contents of the Date/timeinformation element but otherwise it may be ignored.NOTE 6:It is mandatory for the TE to handle correctly the shifting procedures between differentcodesets. It is optional whether the TE recognizes or generates any of the informationelements in codeset 5.NOTE 7:It is mandatory that the TE recognizes the Display Information Element meaning that noerror handling procedures shall be initiated upon its reception but it is optional whetherthe contents of the information element are displayed.2.2.1.5Layer 3 System ParametersTable 5: Layer 3 System Parameter RequirementsÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
FUNCTIONAL CHARACTERISTICS
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Function = Layer 3 System
³ ETS
³
SAR
³
COMMENTS
³³
Parameters
³
³
³
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ List of System Parameters
³ §9
³
³
³³ Timers in the Network Side
³ §9.1
³
N/A
³
³³ Timers in the User Side
³ §9.2
³
³
³³ T301
³
³
N/A
³
³³ T302
³
³
NOTE
³
³³ T303
³
³
O
³
³³ T304
³
³
O
³
³³ T305
³
³
M
³
³³ T308
³
³
M
³
³³ T309
³
³
O
³
³³ T310
³
³
O
³
³³ T313
³
³
M
³
³³ T314
³
³
NOTE
³
³³ T316
³
³
NOTE
³
³³ T317
³
³
NOTE
³
³³ T318
³
³
NOTE
³
³³ T319
³
³
³
³³ T321
³
³
N/A
³
³³ T322
³
³
NOTE
³
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙNote to table 5:NOTE:Mandatory if the corresponding procedure is implemented, otherwise not applicable.PSIST ETS 300 104:1996



Page 14ETS 300 104: July 19912.2.2Interface Procedures2.2.2.1Call EstablishmentTable 6: Layer 3 Call Establishment RequirementsÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
INTERFACE PROCEDURES
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Procedure = Call Establishment
³ ETS
³
SAR
³
COMMENTS
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Circuit Switched Call Control
³ §5
³ NOTE 1 ³
³³ Procedures
³
³
³
³³ Call Establishment at
³ §5.1
³
M
³
³³ Origination Interface
³
³
³
³³ Call Request
³ §5.1.1
³
M
³
³³ B-channel Selection -
³ §5.1.2
³
M
³
³³ originating
³
³
³
³³ Overlap Sending
³ §5.1.3
³
O
³ NOTE 2
³³ Invalid Call Information
³ §5.1.4
³
N/A
³
³³ Call Proceeding
³ §5.1.5
³
³
³³ Call Proceeding, enbloc sending ³ §5.1.5.1
³
M
³ NOTE 2
³³
overlap sending ³ §5.1.5.2
³
M
³
³³ Notification of interworking at ³ §5.1.6
³
³
³³ the originating interface
³
³
³
³³
- receipt of
³
³
M
³
³³
- generation of
³
³
O
³ M for NT2
³³
³
³
³ if interworking
³³
³
³
³ occurs
³³ Call Confirmation Indication
³ §5.1.7
³
M
³
³³ Call Connected
³ §5.1.8
³
M
³
³³ Call Rejection
³ §5.1.9
³
N/A
³
³³ Transit Network Selection
³ §5.1.10
³
N/A
³ refer to network ³³
³
³
³ operations only
³³ Call Establishment at
³ §5.2
³
M
³ NOTE 4
³³ Destination Interface
³
³
³
³³ Incoming Call
³ §5.2.1
³
M
³
³³ Compatibility Checking
³ §5.2.2
³
M
³
³³ B-channel Selection -
³ §5.2.3
³
³
³³ destination
³
³
³
³³ SETUP message delivered by
³ §5.2.3.1
³
M
³
³³ point-to-point data link
³
³
³
³³ SETUP messages delivered by
³ §5.2.3.2
³
M
³
³³ broadcast data link
³
³
³
³³ Overlap Receiving
³ §5.2.4
³
O
³
³³ Call Confirmation
³ §5.2.5
³
³
³³ Response to en-bloc SETUP or
³ §5.2.5.1
³
M
³
³³ Completion of Overlap Receiving ³
³
³
³³ Receipt of CALL PROCEEDING
³ §5.2.5.2
³
N/A
³
³³ and ALERTING
³
³
³
³³ Called user clearing during
³ §5.2.5.3
³
N/A
³ refer to network ³³ call establishment
³
³
³ operations only
³³ Call Failure Procedures
³ §5.2.5.4
³
N/A
³
³³ Notification of interworking at ³ §5.2.6
³
³
³³ terminating interface
³
³
³
³³
- receipt of
³
³
M
³
³³
- generation of
³
³
O
³ M for NT2
³³
³
³
³ if interworking
³³
³
³
³ occurs
³³ Call Accept
³ §5.2.7
³
M
³
³³ Active Indication
³ §5.2.8
³
M
³
³³ Non-selected User Clearing
³ §5.2.9
³
M
³
³³ Call collision
³ §5.7
³
M
³
³³ Compatibility Checking
³ Annex B
³
M
³
³³ Transit Network Selection
³ Annex C
³
O
³
³³ Extension
...