1、5TD.ETSI EN 301 061-1-ENGL 1778 3400855 0284733 358 EN 301 061 -1 1.2.2 (1998-04) European Standard (Teiecommunications series) Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSSI) protocol; Generic functional protocol for the support of supplementary servi
2、ces at the “b“ service entry point for Virtual Private Network (VPN) applications; Part 1 : Protocol specification STD.ETSI EN 301 061-I-ENGL 1998 3400855 0284914 294 = 2 EN 301 061-1 V1.2.2 (1998-04) Reference DEN/SPS-05110-1 (9tO90ipC.PDF) Keywords DSS1, generic, ISDN, supplementary service, VPN E
3、TSI Postal address F-O6921 Sophia Antipolis Cedex - FRANCE Office address 650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 O0 Fax: +33 4 93 65 47 16 Siret No 348 623 562 00017 - NAF 742 C Association h but non lucratif enregistre ti la Sous-prfecture de Grasse (06) No
4、 7803/88 internet secretariata etsi.fr http:iiwww.etsi .fr http:/www. etsi.org COR vriaht Notifcaton No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards Institut
5、e 1998. All rights reserved. ETSI STDeETSI EN 301 ObL-L-ENGL 1778 3400855 0284715 120 9 3 EN 301 061-1 V1.2.2 (1998-04) Contents Intellectual Property Rights 5 Foreword 5 1 2 3 3.1 3.2 4 4.1 4.2 4.3 5 5.1 5.2 5.3 5.4 6 7 7.1 7.1.1 7.1.2 7.1.3 7.2 7.2.1 Scope 6 Normative references . 6 Definitions an
6、d abbreviations . .7 . 7 . 7 supplementary services 8 . 8 8 Coexistence of generic protocols for t Support of various generic protocols . Coexistence of generic protocols . Arrangements by which coexistence of protocols may be supported by a network. General principles applied for the functional con
7、trol of supplementary services . 8 . 8 . 8 8 . 9 Categories of procedures . VPN services in the context of CN . Control of supplementary services using the separate message approach . 9 Control of supplementary services using the common information element approach .9 General 9 Introduction. . 9 Sco
8、pe of the procedures . 9 Distinction between public network and VPN context 9 . 10 Transport of components . 10 Procedures applicable for signalling in a VPN context. 7.2.1.1 7.2.1.1.1 7.2.1.1.2 7.2.1.2 7.2.1.2.1 7.2.1.2.1.1 7.2.1.2.1.1.1 7.2.1.2.1.1.2 7.2.1.2.1.1.3 7.2.1.2.1.1.4 7.2.1.2.1.1.5 7.2.1
9、.2.1.2 7.2.1.2.1.2.1 7.2.1.2.1.2.2 7.2.1.3.1.2.3 7.2.1.2.1.2.4 7.2.1.2.1.2.5 7.2.1.2.1.2.6 7.2.1.2.1.3 7.2.1.2.1.3.1 7.2.1.2.1.3.2 7.2.1.2.1.3.3 7.2.1.2.1.3.4 7.2.1.2.1.4 7.2.1.2.1.5 7.2.1.2.1.6 7.2.1.2.1.7 7.2.1.2.2 Bearer-related transport mechanism . Connec tion-oriented bearer-independent transp
10、ort mechanism. . 10 Protocol control requirements . Generic Functional Transport (GFT)-Control requirements . 10 11 Connection establishment at the originating interface . 11 Connection request . Invalid connection information. . Call proceeding . Connection connected . 12 Connection rejected Connec
11、tion establishment at the destination interface 12 Incoming connection . Connection confirmation . . 13 Called user clearing during incoming connection establishment . 13 Connection failure . 13 Connection accept . 13 Active indication . 13 Connection clearing . 14 Exception conditions . 14 Cleanng
12、initiated by the user . Clearing initiated by the network Clear collision . . 15 Interaction with call rearrangements _. . _ _. Handling of error conditions . 15 Protocol timer values . 16 GFT-Control requirements 16 Protocol control requirements Interaction with restart procedure ETSI 4 EN 301 061-
13、1 V1.2.2 (1998-04) 7.2.1.3 Connectionless bearer-independent transport mechanism 16 8 8.1 Categories of notifications . 16 8.2 Non-standardized notifications 16 Generic notification procedures applicable in a VPN context . 16 8.3 Protocol control requirements . . . 17 8.4 GFT-Control requirements 17
14、 9 Application layer requirements 17 9.1 Coordination Function requirements 17 9.2 ROSE requirements . . . 17 9.3 ACSE requirements . 17 9.4 DSE requirements 17 9.5 10 Other generic procedures . 18 11 Coding requirements 18 1 1.1 Message functional definitions and content . 18 11.1.1 Messages for be
15、arer-related signalling . Non-standardized operations and non-standardized additions to standardised operations 11.1.1.1 FACILITY 18 11.1.1.2 NOTIFY . 19 11.1.2 11.1.2.1 CALL PROCEEDING 19 11.1.2.2 CONNECT . 11.1.2.3 CONNECT ACKNOWLEDGE 11 S.2.4 FACILY . . 20 11.1.2.5 RELEASE . . 21 11.1.2.6 RELEASE
16、 COMPLETE . 22 11.1.2.7 SETUP . 23 11.1.2.8 STATUS 11.1.2.9 STATUS ENQUIRY . 24 11.2 24 11.2.1 Facility . 24 1 1.2.2 Notification indic ator . 25 . 26 1 1.2.3 11.2.4 . 26 Messages for bearer-independent, connection-oriented signalling . 19 General message format and information element coding Annex
17、A (normative): Dynamic descriptions 28 A.l Dynamic description of the Hold and Retrieve functions. 28 A.2 A.3 A.4 Annex B (normative): Dynamic description of the status request procedure 28 Dynamic description of the supplementary service management function . 28 Dynamic description of the connectio
18、n oriented bearer independent transport mechanism . 28 Formal definition of data types 29 Annex C (normative): Flow control . 30 History 31 ETSI STD-ETSI EN 301 ObL-L-ENGL 1998 3400855 0284937 TT3 M 5 EN 301 061-1 V1.2.2 (1998-04) Intellectual Property Rights IPRs essential or potentially essential
19、to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members , and can be found in ETR 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI i
20、n respect of ETSI standards“, which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/www.etsi.fr/ipr or http:/www.etsi.org/ipr). Pursuant to the ETSI Interim IPR Policy, no investigation, including IPR searches, has been carried out by
21、 ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETR 3 14 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This European Standard (Telecommunications series) has been produced by ETSI Technica
22、l Committee Signalling Protocols and Switching (SPS). The present document is part 1 of a multi-part European Standard (Telecommunications series) covering the Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol: Generic functional protocol for th
23、e support of supplementary services for Virtual hvate Network (VPN) applications, as identified below: Part 1: “Protocol specification“; Part 2: Part 3: Part 4: Part 5: Part 6: “Protocol Implementation Conformance Statement (PICS) proforma specification“; “Test Suite Structure and Test Purposes (TSS
24、 “Abstract Test Suite (ATS), user“; “Test Suite Structure and Test Purposes (TSS or b) all versions up to and including the identified version (identified by “up to and including“ before the version identity); or c) all versions subsequent to and including the identified version (identified by “onwa
25、rds“ following the version identity); or d) publications without mention of a specific version, in which case the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. il EN 300 196-1: “integrated Services D
26、igital Network (ISDN); Generic functional protocol for the support of supplementary services; Digital Subscriber Signalling System No. one (DSS 1) protocol: Part 1: Protocol specification“. EN 300 403-1: “Integrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1)
27、 protocol; Signalling network layer for circuit-mode basic call control; Part 1: Protocol specification ITU-T Recommendation Q.911 (1993), modified“. ETSI - - STD-ETSI EN 301 061-1-ENGL 1778 M 3400855 0284717 87b 31 7 EN 301 061-1 Vl.2.2 (1998-04) EN 301 060-1: “Integrated Services Digital Network (
28、ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call applications: enhancement at the “b“ service entry point for Virtual Private Network (VPN) applications; Part 1 : Protocol specification“. 4 1 ETS 300 402-2: “Integrated Services Digital Network (ISDN); Digital Subscribe
29、r Signalling System No. one (DSS 1) protocol; Data link layer; Part 2: General protocol specification ITU-T Recommendation Q.921 (1 993), modified“. ISO/IEC 11582 (199.5): “Information technology - Telecommunication and information exchange between systems - Private Integrated Services Network - Gen
30、eric functional protocol for the support of supplementary services - Inter-exchange signalling procedures and protocol“. ITU-T Recommendation X.219 (1988): “Remote operations: Model, notation and service definition“. L.51 i61 171 t 81 ITU-T Recommendation X.229 (1988): “Remote operations: Protocol s
31、pecification“. ISO/iEC 15056 (1997): “Information technology - Telecommunications and information exchange between systems - Private Integrated Services Network - Inter-exchange signalling protocol - Transit counter additional network feature“. 3.1 Definit ions and abbreviations Definitions Clause 3
32、 of EN 300 196-1 i shall apply with the following addition: Corporate telecommunication Network (CN): Consists of sets of equipment (Customer Premises Equipment and/or Customer Premises Network) which are located at geographically dispersed locations and are interconnected to provide networking serv
33、ices to a defined group of users. NOTE 1: The ownership of the equipment is not relevant to this definition NOTE 2: In the present document, even equipment which is not geographically dispersed (e or if the request is invalid or cannot be accepted, follow the procedures of subclause 7.2.1.2.1.1.2. -
34、 The FACILITY message shall be exchanged only once the NCICS connection has reached the Active state. 7.2.1.2.1.1.2 invalid connection information If the NCICS connection request is invalid or cannot be accepted, the network shall: - return a RELEASE COMPLETE message; - release the call reference; a
35、nd - remain in the Null state. The RELEASE COMPLETE message shall contain an appropriate cause value. If the network determines that a bearer- independent signalling connection is not authorized or available, cause #63, “service or option not available, unspecified“, shall be used. ETSI 12 EN 301 06
36、1-1 Vl.2.2 (1998-04) 7.2.1.2.1.1.3 Call proceeding If the NCICS connection request is valid and can be processed, the network shall: - return a CALL PROCEEDING message; - - enter the Outgoing Call Proceeding state; and attempt to establish the NCICS connection towards the terminating entity (for exa
37、mple, see subclause 7.2.1.2.1.2). Upon receipt of the CALL PROCEEDING message, the user shall: - stop timer T303; - enter the Outgoing Call Proceeding state; and - start timer T310. If timer T310 expires, the user shall initiate NCICS connection clearing towards the network in accordance with subcla
38、use 7.2.1.2.1.3 using cause # 102, “recovery on timer expiry“. 7.2.1.2.1.1.4 Connection connected Upon the network receiving an indication that the NCICS connection request has been accepted, the network shall send a CONNECT message across the originating user-network interface, and either: - enter
39、the Active state; or - start timer T3 13 and enter the Connect Request state. This message indicates to the originating user that a NCICS connection has been established through the network. On receipt of the CONNECT message, the originating user shall: - send a CONNECT ACKNOWLEDGE message; stop tim
40、er T3 10; and - - enter the Active state. On receipt of a CONNECT ACKNOWLEDGE message, the network shall: - if it perceives the NCICS connection to be in the Active state, take no action; or if in the Connect Request state, stop timer T313 and enter the Active state. - If timer T3 13 expires before
41、a CONNECT ACKNOWLEDGE message is received, the network shall initiate NCICS connection clearing with a RELEASE message using cause #102, ,jecovery on timer expiry“. 7.2.1.2.1.1.5 Connection rejected Upon receiving an indication that the network or the terminating entity is unable to accept the NCICS
42、 connection request, the network shall initiate NCICS connection clearing at the originating user-network interface as described in subclause 7.2.1.2.1.3, using the cause provided by the terminating network or the terminating entity. 7.2.1.2.1.2 Connection establishment at the destination interface
43、Before these procedures are invoked, a reliable data link connection shall be established between the user (TE/NT2) and the network. Ail layer 3 messages shall be sent to the data link layer using a DL-DATA request primitive, using the data link services described in ETS 300 402-2 4. The call refere
44、nce contained in ail messages exchanged across the user-network interface shall contain the call reference value specified in the SETUP message delivered by the network. In selecting a call reference, the dummy call reference shall not be used in conjunction with NCICS connections. ETSI STD.ETS1 EN
45、301 061-1-ENGL 1998 3400855 0284925 07T EN 301 061-1 V1.2.2 (1998-04) 13 7.2.1.2.1.2.1 Incoming connection To initiate a NCICS connection establishment, the network shall transfer a SETUP message across the interface. Refer to subclause 11.1.2.7 for the contents of the SETUP message. The network sha
46、ll include the Channel identification information element and the VPN indicator information element containing a CN identifier in the SETUP message. If the PINX receives a SETUP message and can determine that the indicated CN is not associated with the access, then the connection shall be rejected w
47、ith cause #50 ,Requested facility not subscribed“. After sending the SETUP message, the network shall start timer T303, and enter the Call Present state. If the network does not receive a response to the SETUP message prior to the expiry of timer T303, the network shall retransmit the SETUP message
48、and restart timer T303. The FACILITY message can only be exchanged when the NCICS connection is in the Active state. 7.2.1.2.1.2.2 Co nnec t io n confirmation When the user determines that sufficient NCICS connection set-up information has been received, the user shall respond with a CALL PROCEEDING
49、 message and enter the Incoming Call Proceeding state. Upon receipt of the CALL PROCEEDING message, the network shall: - stop timer T303; - enter the Incoming Call Proceeding state; and - start timer T310 7.2.1.2.1.2.3 If a RELEASE or RELEASE COMPLETE message is received before a CONNECT message has been received, the network shall: Called user clearing during incoming connection establishment - - stop timer T303 or T310 (if running); continue to clear the terminating entity as described in subclause 7.2.1.2.1.3; and - clear the NCICS connecti
